Hello. I flashed TWRP and then LineageOS onto my Mi 9T. I didn't like it too much so I started downloading the global rom. In preparations to reflash the stock rom, I wiped the phone from TWRP and then turned the phone off until it was completed downloading. I was planning to install the ROM through OTG, but when I tried to go into recovery, nothing happens and I go back to boot screen. I tried reflashing TWRP with adb, but it seems I forgot to turn USB debugging back on when I was transferring files. What can I do now? Is my phone bricked?
No it's not bricked.
Just flash fastboot rom and then
Flash twrp again ,free to do any job
Masih_zh said:
No it's not bricked.
Just flash fastboot rom and then
Flash twrp again ,free to do any job
Click to expand...
Click to collapse
Will it still work even though USB debugging is off? Sorry I am new to this.
tagkd said:
Hello. I flashed TWRP and then LineageOS onto my Mi 9T. I didn't like it too much so I started downloading the global rom. In preparations to reflash the stock rom, I wiped the phone from TWRP and then turned the phone off until it was completed downloading. I was planning to install the ROM through OTG, but when I tried to go into recovery, nothing happens and I go back to boot screen. I tried reflashing TWRP with adb, but it seems I forgot to turn USB debugging back on when I was transferring files. What can I do now? Is my phone bricked?
Click to expand...
Click to collapse
Flash stock dtbo.img and recovery.img from fastboot
tagkd said:
Will it still work even though USB debugging is off? Sorry I am new to this.
Click to expand...
Click to collapse
The "USB debugging" you're talking about assumes there's a running OS on your system. It's not applicable here. Boot into fastboot and see if the phone is recognized. If yes, you're good. Flash twrp via fastboot then boot into recovery and go from there with removing old files and flashing new rom
Thanks for the help everyone. I found a v 10.3.6 fastboot rom and was able to get phone working again.
Related
Hi. Looks like I fkced my phone. Was using Darkobas twrp, flashed this room and it boot-looped at the beginning (phone was turning on and off on the "Coolpad" screen). I can enter the recovery however can't transfer roms into the card. While pushing big files with ADB push (it takes few minutes) it randomly stops responding/hangs in the middle of a transfer. Tried multiple times and it stops randomly ( I've wiped/formatted whole storage )
I managed to flash another recovery 3.1.0.0 but still I need to push some rom to see if I can flash it. After PC reboot it stopped detecting my phone...
Fastboot is not working, power + vol down goes to black screen / turning off the phone.
Tool_all_in_one does not detect my phone. In fact I do not see it in Windows Device Manager. Tried different usb 3/2 ports
Commands in console like fastboot oem device info gives:
< waiting for any device >
adb reboot bootloader gives:
adb server version (39) doesn't match this client (36); killing...
* daemon started successfully *
error: no devices/emulators found
It's done guys?
Update: somehow managed to restore connection, so phone is visible in Device Manager as "Android Composite ADB Interface" .
Managed to push AICP ROM with adb but can't see it on sdcard. Usually, it was in the main directory, now nothing is there.
Adb sideload? It still seems to me like youre having connection issues w/the pc. Tried rebooting to fastboot from twrp menu?
1 - Enter Twrp Recovery
2 - Wipe -> Format Data then type "yes". This command gonna wipe your internal storage behold.
3 - After this reboot recovery and go to mount then enable mtp.
4 - Transfer rom file.And after a clean wipe flash it.
That rom have bootloader and some modem file that can bring up some issue mate.And those files belongs to Changer not to our beast.
Both device very very familiar but its different product anyway you can't trust it.
I RECOMMEND ALL OF PEOPLE GONNA FLASH ROM please first check the firmware files .If there, then clean it and wipe from the updater-script.
For an alternative you can flash your stock firmware files from QFİL but it's risky too.
Thanks for the replies. MTP was enabled all the time in the recovery. I have unmounted all partitions, repaired, formatted etc. After multiple tries, I managed to push and flash AICP rom. Good it's only ~500Mb. Transfer of bigger files was interrupted every time.
By the way this JUI ROM has replaced the starting screen. Phone is quietly squeaking for few seconds (in fastboot all the time) after every reboot on 'CoolPad' screen, similar to this 42sec 12000Hz. Any way to back to 'original' LP3 one?
Thes1ev said:
Thanks for the replies. MTP was enabled all the time in the recovery. I have unmounted all partitions, repaired, formatted etc. After multiple tries managed to push and flash AICP rom. Good it's only ~500Mb. Transfer of bigger files was interrupted every time.
By the way this JUI ROM has replaced the starting screen. Phone is quietly squeaking for few seconds (in fastboot all the time) after every reboot on 'CoolPad' screen, similar to this 42sec 12000Hz. Any way to back to 'original' LP3 one?
Click to expand...
Click to collapse
Make sure you are not using a USB hub, or extension cable. Also make sure you are plugged directly into the PC motherboard, not one of the front ports. I had transfers stalling and it was my USB extension cable.
Thes1ev said:
Thanks for the replies. MTP was enabled all the time in the recovery. I have unmounted all partitions, repaired, formatted etc. After multiple tries, I managed to push and flash AICP rom. Good it's only ~500Mb. Transfer of bigger files was interrupted every time.
By the way this JUI ROM has replaced the starting screen. Phone is quietly squeaking for few seconds (in fastboot all the time) after every reboot on 'CoolPad' screen, similar to this 42sec 12000Hz. Any way to back to 'original' LP3 one?
Click to expand...
Click to collapse
Sure, you need to flash the firmware files, download 23s from the official site, and fastboot flash all the files, that'll return you to stock fastboot, splash, etc.
Follow this guide (no need to format data, and flash system again, just the files in firmware update folder).
https://forum.xda-developers.com/le-pro3/how-to/guide-how-to-manually-upgrade-firmware-t3609786
trizex said:
Sure, you need to flash the firmware files, download 23s from the official site, and fastboot flash all the files, that'll return you to stock fastboot, splash, etc.
Follow this guide (no need to format data, and flash system again, just the files in firmware update folder).
https://forum.xda-developers.com/le-pro3/how-to/guide-how-to-manually-upgrade-firmware-t3609786
Click to expand...
Click to collapse
Can't flash anything using fastboot - "fastboot flash xxx.img" gives me: < waiting for any device > and nothing happens.
At the moment trying to flash stock 23s but it's hanging on "Patching system image unconditionally" for 5+ minutes already.
This JUI fcked bootloader in my phone somehow. It's blocked/can't be replaced or no idea what's going on here.
Edit: so ye after 20+ minutes of "Patching system image unconditionally" looks like I'm unable to flash stock 23s using TWRP 3.1.0.0.
Probably it wants to replace this fkn JUI bootloader and freeze there.
Wait, are you trying to flash complete official update.zip via twrp?? You cant do that. Find a 23s package customised for flashing via twrp, I think I used alba's package from 4pda
trizex said:
Wait, are you trying to flash complete official update.zip via twrp?? You cant do that. Find a 23s package customised for flashing via twrp, I think I used alba's package from 4pda
Click to expand...
Click to collapse
Yap, was flashing official stock 23s from this site via twrp.
Okay today gonna try Alba ROM as you suggested.
trizex said:
Wait, are you trying to flash complete official update.zip via twrp?? You cant do that. Find a 23s package customised for flashing via twrp, I think I used alba's package from 4pda
Click to expand...
Click to collapse
That helped, thanks a lot!
Is there any solution to restore Leeco bootloader? I just cant flash anything because device is unknown during fastboot mode. Tried to uninstall and reinstall driver but no luck.
I am stuck with coolpad bootloader which is not recognised from my pc. Serves me right because i didnt check the zip of jui which i flashed that had another bootloader, fml.
If any kind soul has any info on that please say it, thanks.
testreaper said:
Is there any solution to restore Leeco bootloader? I just cant flash anything because device is unknown during fastboot mode. Tried to uninstall and reinstall driver but no luck.
I am stuck with coolpad bootloader which is not recognised from my pc. Serves me right because i didnt check the zip of jui which i flashed that had another bootloader, fml.
If any kind soul has any info on that please say it, thanks.
Click to expand...
Click to collapse
That is litterally what this whole topic was about? See my responses, if you still have access to twrp (dont see why wouldnt you), you can use it to flash a 23s "stock" rom through it (such a package will contain, among others, the leeco bootloader etc)
---------- Post added at 08:00 PM ---------- Previous post was at 07:59 PM ----------
Thes1ev said:
That helped, thanks a lot!
Click to expand...
Click to collapse
Youre welcome, everything back to normal?
trizex said:
Youre welcome, everything back to normal?
Click to expand...
Click to collapse
Yeah, I got rid of this JUBU bootloader after flashing stock-like rom. Also thanks to this there is no more strange noise during the boot sequence.
Thes1ev said:
Yeah, I got rid of this JUBU bootloader after flashing stock-like rom. Also thanks to this there is no more strange noise during the boot sequence.
Click to expand...
Click to collapse
Ya, I heard that squeeling too, when booting, and in fastboot mode
Thes1ev thank you so much pal, i flashed 2 different 23s with all wipes and they gave me errors but your rom installed perfectly.
I accidently formated everything in twrp and ended without OS and was stuck in custom twrp. I tried to flash stock recovery and that went ok. Now whatever i do i cant sideload stock zip file using adb. Fastboot is recognized but adb is not. When connected to pc shows error. I have tried to install, reinstall all sorts of drivers but all the same. Is there a way to get back to stock using fastboot commands manualy? Please help !!
Use fastboot to flash twrp again and then flash the stock rom. You can transfer the stock rom to the device by connecting it to your PC while being in TWRP.
himanshuladia said:
Use fastboot to flash twrp again and then flash the stock rom. You can transfer the stock rom to the device by connecting it to your PC while being in TWRP.
Click to expand...
Click to collapse
You mean stock twrp or custom because i have stock but when connected i cant copy files on device because it is not recognized by PC
Del.
TWRP is always a custom recovery. What you currently have is the stock oxygen OS recovery. Flash TWRP again and boot into twrp. Then, while being in TWRP, conmect your phone to PC.
himanshuladia said:
TWRP is always a custom recovery. What you currently have is the stock oxygen OS recovery. Flash TWRP again and boot into twrp. Then, while being in TWRP, conmect your phone to PC.
Click to expand...
Click to collapse
Ok will try !
Del.
Finaly i did it after a few hours of trying to find a solution and figuring out why my PC doesn't recognize phone in adb I tried on an old PC with win7 installed and sideload went smooth like butter on first attempt. I have tried on two computers with win10 installed, tried with all sorts of USB cables, usb on computer 3.0 , 2.0, tried all sorts of drivers and nothing helped. I hope that someone else will have a benefit of this post and sort of a solution if he will have the same issue. Thanks to everyone that tried to help out!
so my whole pc doesnt even know that i have plugged my phone in to it... i cant boot up because i tried to install custom rom and it failed.... now i have just fastboot,,, stock recover, stock erecovery and that dload thing,, but i installed adb drivers in my pc and fastboot still doesnt see my phone. so how do i fix it? i have backup but i need just twrp but i cant flash it because of phone is not seen by device D:
edit: fastboot now detects my phone
edit2: can flash twrp but it gets overwritten,, i used this tutorial to flash twrp https://forum.xda-developers.com/p10-lite/development/recovery-twrp-3-2-1-0-t3783447 and i had the same twrp from start
edit3: somehow got twrp working and restored the backup,, now im runnin custom rom elemental v3
Voutsjude said:
so my whole pc doesnt even know that i have plugged my phone in to it... i cant boot up because i tried to install custom rom and it failed.... now i have just fastboot,,, stock recover, stock erecovery and that dload thing,, but i installed adb drivers in my pc and fastboot still doesnt see my phone. so how do i fix it? i have backup but i need just twrp but i cant flash it because of phone is not seen by device D:
edit: fastboot now detects my phone
edit2: can flash twrp but it gets overwritten,, i used this tutorial to flash twrp https://forum.xda-developers.com/p10-lite/development/recovery-twrp-3-2-1-0-t3783447 and i had the same twrp from start
Click to expand...
Click to collapse
If you have wifi boot to erecovery and download full stock rom...
nemanjsb said:
If you have wifi boot to erecovery and download full stock rom...
Click to expand...
Click to collapse
does it lock my bootloader? i dont want to pay 12 eur to unlock it again
Voutsjude said:
does it lock my bootloader? i dont want to pay 12 eur to unlock it again
Click to expand...
Click to collapse
I'm not 100% sure but I think bootloader is ulocked. I did it a few days ago but I can't remember...
Hello,
I recently tried to degoogle my phone with Lineage and twrp. It's been a bit of a brick wall. Long story short i'm stuck in twrp. It boots into recovery fine from that. Everything else is DOA. When I plug it in the pc recognizes it and I can see my storage. I run adb devices and it comes up. When I reboot to bootloader I see download as I should on the phone screen and I hear it connect to the pc. Then that's it, it doesn't show up as storage or when I run adb of fastboot commands. I fairly certain TWRP F'd this all up. I have the recovery image for lineage but like I said nothing gets done.
So the question is, is it totally bricked or is there a soulotion I haven't found yet?
Thanks for the listen.
Some LineageOS build working with own recovery so you can try to flash with LineageOS recovery via sideload option...
gouthamram said:
Some LineageOS build working with own recovery so you can try to flash with LineageOS recovery via sideload option...
Click to expand...
Click to collapse
That's the whole problem. I can't even do that.
mech1164 said:
That's the whole problem. I can't even do that.
Click to expand...
Click to collapse
First of all flash LineageOS recovery on fastboot mode then restart to LineageOS recovery & flash LineageOS rom via adb sideload...
Everything you will do even working fastboot mode...
A/B partition system is caused whole problem so this is only the method to flash custom rom...
As I said this has been the whole problem. I boot back to bootloader where It says Download Mode. When I try to flash the recovery image this is what I get.
C:\Users\rpwor\NexusTools>fastboot flash recovery lineage-18.1-20210831-recovery-PL2.img
< waiting for any device >
And there it sits never to move again. Now do you understand what i'm dealing with?
The problem might be the recovery image you want to flash as it's for a Nokia 6.1 (PL2) not Nokia 6.1 Plus (DRG).
If your device is actually a Nokia 6.1, then you could try the `Install Recovery Ramdisk` option in TWRP, under `Advanced`.
mech1164 said:
As I said this has been the whole problem. I boot back to bootloader where It says Download Mode. When I try to flash the recovery image this is what I get.
C:\Users\rpwor\NexusTools>fastboot flash recovery lineage-18.1-20210831-recovery-PL2.img
< waiting for any device >
And there it sits never to move again. Now do you understand what i'm dealing with?
Click to expand...
Click to collapse
How is your brick? Did you find a way to revive it?
So long story short I recently decided to install stock kernel on my Nexus 6P. I flashed boot.img from oreo firmware using twrp. Accidentally I flashed it into system instead of boot. Now system is corrupted stuck on google logo. But USB debuging is enabled. so I tried to activate OEM using fastboot but it says unknown command. Later on I try to format, wipe all partitions, repair file system using twrp still no success.
Did I break my phone completely?
vu1ture said:
So long story short I recently decided to install stock kernel on my Nexus 6P. I flashed boot.img from oreo firmware using twrp. Accidentally I flashed it into system instead of boot. Now system is corrupted stuck on google logo. But USB debuging is enabled. so I tried to activate OEM using fastboot but it says unknown command. Later on I try to format, wipe all partitions, repair file system using twrp still no success.
Did I break my phone completely?
Click to expand...
Click to collapse
No, I don't think you completely broke your phone. I would try reflashing using fastboot. Or you could try an OTA update to return it to stock.
No. You just need to reflash stock system.img using stock flashing application for your fone and nothing else. Just do this in edl mode.
To get there, turn fone off completely while unplugged from pc. start your stock flashing application, and load your stock rom, once it verify's, you should be able to select system.img ONLY, dont flash any other img you see for now.
Hit start in this application, then plug fone into usb, watch what happens
Write back ?
Edit The No is to the OP, not to disagree with above post
Pachacouti said:
No. You just need to reflash stock system.img using stock flashing application for your fone and nothing else. Just do this in edl mode.
To get there, turn fone off completely while unplugged from pc. start your stock flashing application, and load your stock rom, once it verify's, you should be able to select system.img ONLY, dont flash any other img you see for now.
Hit start in this application, then plug fone into usb, watch what happens
Write back ?
Edit The No is to the OP, not to disagree with above post
Click to expand...
Click to collapse
you are genius. thank you so much