I have a cell phone which name is Huawei Ascend P1. Now I have a problem, that is the devices can not bootup into Android's home and I can not write anything into flash, even using fastboot.
When booting, the screen stays on the welcome logo, and stay there forever, and adb could connect to linux shell on the phone. I can see all file on the phone, and I can save files after "mount -o remount / /", but after reboot, the file is gone.
If I use fastboot to flash a recovery into my phone, by follow command:
fastboot flash recovery recovery.img
The command line prompt says OK, but when it reboots, it still reboot into the previous recovery.
Who hnows why this happens? And how can I resolve this problem?
Is there anyone who can help me?
mikewootc said:
I have a cell phone which name is Huawei Ascend P1. Now I have a problem, that is the devices can not bootup into Android's home and I can not write anything into flash, even using fastboot.
When booting, the screen stays on the welcome logo, and stay there forever, and adb could connect to linux shell on the phone. I can see all file on the phone, and I can save files after "mount -o remount / /", but after reboot, the file is gone.
If I use fastboot to flash a recovery into my phone, by follow command:
fastboot flash recovery recovery.img
The command line prompt says OK, but when it reboots, it still reboot into the previous recovery.
Who hnows why this happens? And how can I resolve this problem?
Click to expand...
Click to collapse
Is there anyone who can help me?
I had try to upgrade firmware with my pc
Solo1977 said:
Dear sir, you should try to connect pc with you phone and upgrade firmware
Also you can modify phone settings, swap positions for flash memory and external sd card
Click to expand...
Click to collapse
First of all,
I have tried to connect pc with my phone by fastboot. And I have tried to flash the original version of recovery by using command:
fastboot flash recovery recovery.img
And it says success, but when I reboot the phone, it still boot into the old version recovery(which is 3rd party version).
Secendly,
I have tried to upgrade firmware from SD card, and it tell me success and no effect when reboot.
Is there anything I can do else?
Related
Short version - is it possible to copy files from my phone to my PC using fastboot (or perhaps adb)? The cyanogenmod WIKI for fastboot, among others, imply that you can (under the section Examples -> Manual Nandroid Restore it says "Make a Nandroid backup, and copy the folder off your SD card to your desktop."). Sorry I'm not allowed to post the link due to being a new user, but this is what it says:
"Make a Nandroid backup, and copy the folder off your SD card to your desktop.
cd ~/Desktop/path/to/backup/
fastboot flash userdata data.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot"
If it is possible, is "flash" the correct command to be using? The description of the flash command when you run "fastroot help" implies it writes data to the phone, not from the phone to the PC... Unfortunately almost everything I search for around the flash command is examples showing how to load ROMs etc, I can't seem to find anything else that points to it being used to backup data...
[UPDATE] - From what I understand you can't copy files off the phone using fastboot commands, but can using adb - so a few questions:
- Does anyone know why adb wouldn't see my device (when I run "adb devices") but fastboot does (note that I'm on the fastboot screen)?
- Does adb require debugging mode to be on?
[UPDATE-2] - Still can't get adb working, suspect it's because USB debugging isn't enabled (though not sure how I can check?). I did try using fastboot to erase the /cache partition in case the lockout data was stored in there - but this didn't work unfortunately. Looking likely I'll just have to wipe it with fastboot oem unlock
Long version / background info:
Using a Samsung Nexus S with Android 4.1
The other night someone down the pub decided to try to unlock my phone, and apparently got the pattern wrong so many times it's now requiring me to enter my Google account details.
Fine, I enter the username / pass, only it says they're wrong - I know they're correct because I've just confirmed they are by logging into Gmail. It says they're incorrect so quickly that I suspect it's not even connecting to the web to check. The icons at the top imply there is signal, but it looks as though 3G / data is off, and there's no WiFi icon even though I'm sat next to my wireless router. I can't find any way to re-enable WiFi / 3G without first unlocking the phone - which requires a net connection. So I got into Fastboot Mode and selected Recovery and the device looks as though it's doing something (deleting all user data I assumed), but when it starts up it's exactly the same - which implies the user data hasn't been erased.
Then I installed fastboot, and the drivers for the Nexus S.
When I run "fastboot devices" I can see the phone listed, however bizarrely "adb devices" lists nothing.
"fastboot oem unlock" seems to work (the phone prompts me to confirm I want to give root access & delete all user data). I haven't done this yet as I want to see if I can save my data somehow using adb or fastboot commands.
For adb to work, your phone must be booted and USB debugging enabled. In your current situation, as far as I know, a factory reset is the only option.
The phone is either in ADB mode or in Fastboot mode. It can never be in both ADB and Fastboot at the same time. ADB requires the phone is up and running, Fastboot requires the phone is in bootloader mode. ADB requires debugging turned on.
If you unlock your bootloader, you can boot the phone using fastboot and your own recovery image using "fastboot boot myrecovery.img" (notice, no flash keyword here). Booting your device with this recovery image, you can do whatever you like and the image permits, e.g. running ADB and copying files. You'll need this recovery image, though.
Thanks, I did try fastboot with a recovery image, but it currently doesn't work because I need to unlock the bootloader (which will wipe all data anyway). Sounds like I will need to just wipe it
kuisma said:
The phone is either in ADB mode or in Fastboot mode. It can never be in both ADB and Fastboot at the same time. ADB requires the phone is up and running, Fastboot requires the phone is in bootloader mode. ADB requires debugging turned on.
If you unlock your bootloader, you can boot the phone using fastboot and your own recovery image using "fastboot boot myrecovery.img" (notice, no flash keyword here). Booting your device with this recovery image, you can do whatever you like and the image permits, e.g. running ADB and copying files. You'll need this recovery image, though.
Click to expand...
Click to collapse
Facing same issue.
Is there anyway so I could copy userdata.img to my pc and then delete gesture.key file (I am running Lollipop) with NO USB DEBUGGING ON in Fastboot mode.
I have gone through "unpacking and packing .img files"http://forum.xda-developers.com/galaxy-s2/general/ref-unpacking-repacking-stock-rom-img-t1081239
But it is out of my knowledge range can anyone get through it and explain me the same.
Hi! I am in the same situation... ADB not working, only fastboot... Any way to save my data? Do I need to unlock bootloader to install a stock recovery? Thank you!
Hi - I am in exactly same situation as well. I am using Oneplus 8t. Any help is greatly appreciated. thanks
Hello all
I have installed the paranoid android 3+ rom but now I cannot access TWRP or the bootloader screen. Android boots normally and the tablet is perfectly functional. When the tablet is off, there is no way to get to TWRP using the keys (power on with Vol- pressed etc. I have used all possible combinations). Also, there is no option to boot into recovery mode from the menu in "Backup & reset". Also, when I try to boot into recovery through a terminal emulator it again boots into andoid normally as if I just did a normal reboot. The "reboot recovery" command issued from the terminal emulator does not boot into TWRP. Trying to boot into recovery mode from within Phoenix Suite again boots the machine normally rather than in recovery mode. It's driving me nuts. Could it be a corrupt/locked bootloader? Is it something else? It seems to me that the only possible path for the bootloader is to load Android.
Is there any way to blind flash the bootloader again? It seems that this is the culprit since I can copy TWRP to nandg through the terminal emulator ("cat /extsd/recovery.img > /dev/block/nandg; sync; sync ;sync" but then again rebooting goes into android rather than recovery mode. Could there be a similar solution like "cat /extsd/boot.img > /dev/block/nanda" for example?).
The tablet connects normally through USB to my PC and adb sees it properly.
Any ideas?
Thanks in advance
Nobody?
Try it via adb.
Command: adb reboot bootloader
It works for me.
Sent from my PC36100
merden765 said:
Try it via adb.
Command: adb reboot bootloader
It works for me.
Sent from my PC36100
Click to expand...
Click to collapse
Whatever I tried it does not boot into the bootloader, be it adb, Phoenix suite, or the terminal emulator. Is there any way to write the original booloader raw to the respective nand partition? And where can I get the original bootloader?
tzoykas said:
Whatever I tried it does not boot into the bootloader, be it adb, Phoenix suite, or the terminal emulator. Is there any way to write the original booloader raw to the respective nand partition? And where can I get the original bootloader?
Click to expand...
Click to collapse
I have same your problem and now i use goomanager this app can bring you to recovery mode or install in to your tablet.
I did the most stupidest thing and tried to place a boot animation zip from the nexus 4 onto my phone. I renamed it ATT_Bootanimation.zip (like the normal bootanimation) and placed it in system/customize/resource. Now the phone wont boot. I tried going to TWRP's file manager, deleting the new zip and copying the old zip back but it still doesn't work. Can anyone help me please?
Edit: It also appears that TWRP can't mount sd card onto my computer so I can't place the ROM file onto my phone to flash. Can someone confirm this or teach me another way to fix this?
JustinBieber said:
I did the most stupidest thing and tried to place a boot animation zip from the nexus 4 onto my phone. I renamed it ATT_Bootanimation.zip (like the normal bootanimation) and placed it in system/customize/resource. Now the phone wont boot. I tried going to TWRP's file manager, deleting the new zip and copying the old zip back but it still doesn't work. Can anyone help me please?
Edit: It also appears that TWRP can't mount sd card onto my computer so I can't place the ROM file onto my phone to flash. Can someone confirm this or teach me another way to fix this?
Click to expand...
Click to collapse
Reflash rom without wipe using adb sideload command. Vitrual sdcard on this phone can't be mounted in recovery yet, so you have chose ADB Sideload in TWRP and use the command
Code:
adb sideload name_of_your_rom_file.zip
May take some minutes for your computer to recognize your phone in adb sideload state, so be patient.
reaper90 said:
Reflash rom without wipe using adb sideload command. Vitrual sdcard on this phone can't be mounted in recovery yet, so you have chose ADB Sideload in TWRP and use the command
Code:
adb sideload name_of_your_rom_file.zip
May take some minutes for your computer to recognize your phone in adb sideload state, so be patient.
Click to expand...
Click to collapse
Thank you for helping me! So I only have the rom.zip on my computer and not on my phone, will the cmd command still work? since the command prompt does not seem to use file location.
Edit: I started ADB Sideload on my phone and it's stuck at 'starting ADB slideload feature..." for about 30 minutes
JustinBieber said:
Thank you for helping me! So I only have the rom.zip on my computer and not on my phone, will the cmd command still work? since the command prompt does not seem to use file location.
Edit: I started ADB Sideload on my phone and it's stuck at 'starting ADB slideload feature..." for about 30 minutes
Click to expand...
Click to collapse
you have to put the rom.zip file into your adb folder.
maybe you want to read this:
http://forum.xda-developers.com/showthread.php?t=2066390
reaper90 said:
you have to put the rom.zip file into your adb folder.
maybe you want to read this:
http://forum.xda-developers.com/showthread.php?t=2066390
Click to expand...
Click to collapse
I am actually trying that right now. My phone's adb sideload is still in the "starting adb feature.." so it isn't working.
Also when I press the ADB slideload on the toolkit, the command prompt opens and says
Code:
'C:\Documents' is not recognized as an internal or external command, operable program or batch file.
How do you place the rom.zip into the adb folder?
I'm still stuck, do you think flashing a kernel will help?
JustinBieber said:
I am actually trying that right now. My phone's adb sideload is still in the "starting adb feature.." so it isn't working.
Also when I press the ADB slideload on the toolkit, the command prompt opens and says
Code:
'C:\Documents' is not recognized as an internal or external command, operable program or batch file.
How do you place the rom.zip into the adb folder?
I'm still stuck, do you think flashing a kernel will help?
Click to expand...
Click to collapse
you have to place the toolkit into some path without spaces, or it won't work. best is to copy the toolkit folder to the root of any of your drives.
reaper90 said:
you have to place the toolkit into some path without spaces, or it won't work. best is to copy the toolkit folder to the root of any of your drives.
Click to expand...
Click to collapse
I placed the toolkit on the root of C:. Pressing the adb sideload on the toolkit launches the command prompt showing a bunch of adb shortcuts and help, but nothing happens on the phone (I attached a picture of the command prompt)
JustinBieber said:
I placed the toolkit on the root of C:. Pressing the adb sideload on the toolkit launches the command prompt showing a bunch of adb shortcuts and help, but nothing happens on the phone (I attached a picture of the command prompt)
Click to expand...
Click to collapse
did you start adb sideload on your phone too in before? also was your phone recognized in adb sideload state by your computer?
i have to admit that i did not use the toolkit for adb sideload...
you can set up your adb/fastboot files on your computer using this:
forum.xda-developers.com/showthread.php?t=2213910
then copy your rom to this folder, rename it to something simple, for example "rom.zip".
connect your phone to your computer, start adb sideload in recovery.
open a command prompt (navigate to your adb/fastboot folder if necessary), type "adb devices". if your device is not listet there, wait a few minutes and type adb devies again, repeat this until you see your device has been recognized by your computer, it should then be listed as in sideload state under your latest "adb devices" command.
now you can type "adb sideload rom.zip" and you should get progress of sideload displayed in %.
when sideload is complete, your phone should automatically start installation of this rom. if it does not, the rom.zip is now saved on your phone's internal memory as "sideload.zip"
hope this helps!
reaper90 said:
did you start adb sideload on your phone too in before? also was your phone recognized in adb sideload state by your computer?
i have to admit that i did not use the toolkit for adb sideload...
you can set up your adb/fastboot files on your computer using this:
forum.xda-developers.com/showthread.php?t=2213910
then copy your rom to this folder, rename it to something simple, for example "rom.zip".
connect your phone to your computer, start adb sideload in recovery.
open a command prompt (navigate to your adb/fastboot folder if necessary), type "adb devices". if your device is not listet there, wait a few minutes and type adb devies again, repeat this until you see your device has been recognized by your computer, it should then be listed as in sideload state under your latest "adb devices" command.
now you can type "adb sideload rom.zip" and you should get progress of sideload displayed in %.
when sideload is complete, your phone should automatically start installation of this rom. if it does not, the rom.zip is now saved on your phone's internal memory as "sideload.zip"
hope this helps!
Click to expand...
Click to collapse
After command prompt has successfully listed my device with its code, I typed in adb sideload (therom).zip and it says * cannot read 'sideload' * The tutorial that you posted doesnt have sideloading a rom
Edit: Okay, I installed SDK Manager did those things and this link really helped me on pushing files through adb. I will test to see if dirty flashing the rom will allow the phone to boot
Edit 2: Damn.. had to wipe everything and do a clean install. Never replace a bootanimation from another phone cause it ****s up your phone and time
http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/
JustinBieber said:
I did the most stupidest thing and tried to place a boot animation zip from the nexus 4 onto my phone. I renamed it ATT_Bootanimation.zip (like the normal bootanimation) and placed it in system/customize/resource. Now the phone wont boot. I tried going to TWRP's file manager, deleting the new zip and copying the old zip back but it still doesn't work. Can anyone help me please?
Edit: It also appears that TWRP can't mount sd card onto my computer so I can't place the ROM file onto my phone to flash. Can someone confirm this or teach me another way to fix this?
Click to expand...
Click to collapse
Tried factory reset? That might solve the issue...
Or use adb sideload to copy the ROM?
Addicted2xda said:
Tried factory reset? That might solve the issue...
Or use adb sideload to copy the ROM?
Click to expand...
Click to collapse
Yep, I downloaded SDK manager and opened the folder in command prompt, that was the only way I could sideload any files into my phone. I sideloaded the rom, reset everything (including system) and fresh install of the rom. Idk what went wrong the only thing I changed was the boot animation zip, which is very peculiar
But I have to thank reaper90 for helping me tons though
ive stumpled on upon a quite annoying problem..i have an HTC ONE X+ which i unlocked my bootloader on and everything went smooth until i wanted to start recovery via hboot.
it did not start and i tried several times and restarted etcetc, i then tried to flash in another recovery and then tried more and more but nothing..
then i cant remember now exaclty how i did it, but i have several RUU, kernel, recovery, boot and roms n such items downloaded
so i tried to feed in another flash or rom or whatever its called to get the recovery funtion to work (i am not very pro at this) and then when i wanted to start my phone normally it all of a sudden wont boot properly.
it freezes on the bootscreen.. i can turn off and go in to bootloader but i cant do ANYTHING from there, i cant do a factory reset (wich i also tried when the recovery did not want to work) i cant do **** there. tried to lock and unlock bootloader.. feels like im out of options..
the only thing i can do now is command the phone via cmd and the toolkit i use from here "Hasoon2000s htc one x AIO kit"
using this guide on this thread mostly..
ive tried so many things now, searched this and other forums since friday and i still can not get anywhere... starting to think this is what the definition of a bricked unit is??
if you need any more info please just ask.. i bought the phone a week ago so kinda sucks if it would be useless for me right away haha..
i would appreciate som help and tips... please
Sincerely Jeff
Did u flash the recovery after unlocking the bootloader.....?????
Sent from my One X+ using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:22 PM ----------
VivaSativa said:
ive stumpled on upon a quite annoying problem..i have an HTC ONE X+ which i unlocked my bootloader on and everything went smooth until i wanted to start recovery via hboot.
it did not start and i tried several times and restarted etcetc, i then tried to flash in another recovery and then tried more and more but nothing..
then i cant remember now exaclty how i did it, but i have several RUU, kernel, recovery, boot and roms n such items downloaded
so i tried to feed in another flash or rom or whatever its called to get the recovery funtion to work (i am not very pro at this) and then when i wanted to start my phone normally it all of a sudden wont boot properly.
it freezes on the bootscreen.. i can turn off and go in to bootloader but i cant do ANYTHING from there, i cant do a factory reset (wich i also tried when the recovery did not want to work) i cant do **** there. tried to lock and unlock bootloader.. feels like im out of options..
the only thing i can do now is command the phone via cmd and the toolkit i use from here "Hasoon2000s htc one x AIO kit"
using this guide on this thread mostly..
ive tried so many things now, searched this and other forums since friday and i still can not get anywhere... starting to think this is what the definition of a bricked unit is??
if you need any more info please just ask.. i bought the phone a week ago so kinda sucks if it would be useless for me right away haha..
i would appreciate som help and tips... please
Sincerely Jeff
Click to expand...
Click to collapse
After unlocking the bootloader....boot in hboot connect the phone in fastboot usb mode to the computer and then if u flash the recovery via cmd by typing "fastboot flash recovery TWRPrecovery.img" (the TWRPrecovery.img will be ur recovery file) u should get the message saying success.
Now u can disconnect the phone from the computer and use the volume down to choose the recovery and hit power button........
the TWRP logo is the one u ll be seeing.....that means all worked as it should......:good:
I dont knw whether u have tried the same but try this would work perfectly......
Danny Samuel said:
Did u flash the recovery after unlocking the bootloader.....?????
Sent from my One X+ using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:22 PM ----------
After unlocking the bootloader....boot in hboot connect the phone in fastboot usb mode to the computer and then if u flash the recovery via cmd by typing "fastboot flash recovery TWRPrecovery.img" (the TWRPrecovery.img will be ur recovery file) u should get the message saying success.
Now u can disconnect the phone from the computer and use the volume down to choose the recovery and hit power button........
the TWRP logo is the one u ll be seeing.....that means all worked as it should......:good:
I dont knw whether u have tried the same but try this would work perfectly......
Click to expand...
Click to collapse
well i tried that before and it still didnt want to work, like it was priorotizing the first one i put in there or something.. but now i came to a wall... since i waited so long to find a sulution i had the device completely empty and just in bootloader.. it seems i dont have the driver or such for it to charge.. so i plugged it into the wall for a while whilst in fastboot thinking it was charging which it was not..
Now it is completely dead i cannot charge it and my computor cant detect it anymore.. seems i found the meaning of a bricked device
worked great up until i had to flash the supersu, it reboots it, but it eeps getting stuck at a screen with a triangle and a !, first time ive seen this on my phone, works fine after i shut it down and restart without entering recovery
brattQueen92 said:
worked great up until i had to flash the supersu, it reboots it, but it eeps getting stuck at a screen with a triangle and a !, first time ive seen this on my phone, works fine after i shut it down and restart without entering recovery
Click to expand...
Click to collapse
The screen with an exclamation mark is the stock recovery screen. If you want to root your phone, better to do it manually using adb and fastboot commands:
Download and install the latest android sdk-tools package (adb and fastboot) on your computer
Download and install latest HTC drivers on your computer.
If HTC Sync is installed on your computer, uninstall it (not closing it, uninstall !!)
Download twrp recovery for your device: zara_ul here, zara_cl here and save the file in your android sdk tools/platform-tools folder (where adb and fastboot are installed)
Open a terminal window from that folder (shift + right click --> start command window here)
Unlock your bootloader folowwing instructions at htcdev.com/bootloader if not already done
With the phone in bootloader mode, select "fastboot" and make sure "fastboot usb" is shown in red in the terminal window type:
Code:
fastboot flash recovery twrp-2.8.7.0-zara.img
fastboot erase cache
fastboot reboot-bootloader
Then download supersu2.46.zip from here and save the file at the root of your phone storage
Boot in twrp recovery, select "install" and then select" update-supersu2.46.zip and swipe the buttom slider to confirm.
Reboot the phone and its now rooted.
I 're-did the windroid toolkit and can get into the twrp recovery....but supersu doesn't work, and no matter how I transfer the zip file it doesn't show up, the supersu file says iopens and there's nothin by in it when I go to twrp recovery and install, and it fails every time I try the adv sideload. The phone connects no. Problem to my computer, any other files I transfer show up.
brattQueen92 said:
I 're-did the windroid toolkit and can get into the twrp recovery....but supersu doesn't work, and no matter how I transfer the zip file it doesn't show up, the supersu file says iopens and there's nothin by in it when I go to twrp recovery and install, and it fails every time I try the adv sideload. The phone connects no. Problem to my computer, any other files I transfer show up.
Click to expand...
Click to collapse
Boot in twrp main menu with the phone connected to your computer.
Open a terminal window from your android sdk tool/platform-tools folder
type:
Code:
adb push UPDATE-SuperSU-v2.46.zip /data/media/0
Then select the "install" menu, make sure you are browsing your internal sd card (as opposed to your external sd card) , find the UPDATE-SuperSU-v2.46.zip file, select it and flash it.
btw quote me or mention me if you want faster answer so i'll get a notification because I'm not coming in the Desire 601 forums really often since its a dead place
Ok I'm having this problem which I can't sort out. I had pixel experience 23/08019 rom installed in my phone and today I decided to install the latest miui stable eu 10.3.7.0 but in twrp it asked for my pin for decrypt. And at that time it accepted my password and I installed the rom with dfe 19.3 and then rebooted my device. It stuck on boot showing enter pin to continue which is kind of new to me, because it wasn't present before. Though I gave my pin there but the device showed wrong pin, retry. I didn't understand what the problem was. Now I tried to install the rom hoping maybe some fault during installation. So coming to twrp I saw that it's asking for pin and this time after I provided correct pin it's showing wrong pin decryption failed. Still ok for me. I thought that I will format my data thus removing the crap encryption. But formatting data showed unable to mount storage. Now no matter whatever I try it's showing the same. I don't seem to understand anything now.
download this twrp
https://forum.xda-developers.com/showpost.php?p=80122987&postcount=305 (mega link)
boot via
fastboot boot twrp.img
flash this vendor https://mirror.akhilnarang.me/MIUI/beryllium/beryllium-9.6.27-9.0-vendor-firmware.zip
then switchoff, boot in to twrp again (via fastboot )_ and try formatting the data,
if it doesn't work, downgrade to miui10.3.2 and repeat the process!
YasuHamed said:
download this twrp
https://forum.xda-developers.com/showpost.php?p=80122987&postcount=305 (mega link)
boot via
fastboot boot twrp.img
flash this vendor https://mirror.akhilnarang.me/MIUI/beryllium/beryllium-9.6.27-9.0-vendor-firmware.zip
then switchoff, boot in to twrp again (via fastboot )_ and try formatting the data,
if it doesn't work, downgrade to miui10.3.2 and repeat the process!
Click to expand...
Click to collapse
Please can you write the steps. I'm a beginner in this so need a little explained steps.
YasuHamed said:
download this twrp
https://forum.xda-developers.com/showpost.php?p=80122987&postcount=305 (mega link)
boot via
fastboot boot twrp.img
flash this vendor https://mirror.akhilnarang.me/MIUI/beryllium/beryllium-9.6.27-9.0-vendor-firmware.zip
then switchoff, boot in to twrp again (via fastboot )_ and try formatting the data,
if it doesn't work, downgrade to miui10.3.2 and repeat the process!
Click to expand...
Click to collapse
Moreover platform tools command prompt window not showing my device in list of devices attached. The poco also after connecting to usb on fastboot mode is going to power on mode and bootlooping. I can't even install any other twrp . What is the solution?
srinrox said:
Moreover platform tools command prompt window not showing my device in list of devices attached. The poco also after connecting to usb on fastboot mode is going to power on mode and bootlooping. I can't even install any other twrp . What is the solution?
Click to expand...
Click to collapse
seems like drivers aren't attached, please install MiFlashTool and from initial start it will give your prompt to install QUALCOM drivers inf, click install ALL, also install MI PC SUITE and make test connection
if you have done both! then simply command prompt in c drive wont show anything you must run command prompt from ADB folder!
---------- Post added at 08:22 AM ---------- Previous post was at 08:01 AM ----------
Srinrox99 said:
Please can you write the steps. I'm a beginner in this so need a little explained steps.
Click to expand...
Click to collapse
thats was quite self explainatory
anways!
ASSUMING YOU HAVE ALL THE DRIVERS INSTALLED AND TEST CONNECTION is PASSED in Fastboot
put these files in SDcard OR usb storage
a. vendor firmware , from https://mirror.akhilnarang.me/MIUI/beryllium/beryllium-9.6.27-9.0-vendor-firmware.zip
b. magisk18.3.zip
c. google apps from openapps.org (take arm64>android9.0>MICRO package and hit download) 250+mb filesize
d. (optional) optimus drunk kernel (check development forum for post)
e. custom rom, (i use Havo2.8)
1. download twrp 3.3.1 unofficial from https://mega.nz/#F!bdwQVIyK!OWNLH72HNT-ecmC-vAVmPw , and put it on desktop
2. open folder C:\Program Files (x86)\Minimal ADB and Fastboot , while PRESSING SHIFT KEY on keyboard, Right click on the blank area of window and CLICK "open Command Prompt here",
3. press volume down + power on your poco until Green Robot appears and connect device with your pc
4. type fastboot devices and enter in minimal adb window, it should show you hexadecimal code ensuring you device is connected
5. now type fastboot boot ... and drag twrp.img from desktop and DROP it over cmd window. the line should look like this
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot C:\Users\<username>\Desk
top\twrp3.3.1unofficial.img
and press enter, it will sent boot in temporary memory to your poco and device will boot in to twrp from memory (not from bootsection) this twrp usually have better control over things where encryption is concern.
6. now wipe /system /cache /delvik /data
6b. FORMAT /DATA (type YES) and proceed, this will delete everything in your device
7. (optional) select /data partition, click change file system from .ext4 to some exfat & once done , COME BACK and select again /data partition again and change file system back to .ext for
8. flash VENDOR >> StockRom >> kernel (optional)>>GAPPS>>Magisk >> then wipe cache >> REBOOT
srinrox said:
Moreover platform tools command prompt window not showing my device in list of devices attached. The poco also after connecting to usb on fastboot mode is going to power on mode and bootlooping. I can't even install any other twrp . What is the solution?
Click to expand...
Click to collapse
You can try connecting your device with a usb hub. That was the solution for me.