Running a TF201, I tried to flash latest TeamWin Recovery and ClockworkMod Recovery. I can no longer get into recovery. But I can get into CM 10.1. Recovery just hangs at the volume down/up selection screen after I choose to start recovery.
I have tried the following commands (with jelly bean files)
fastboot -i 0x0b05 flash recovery twrp.blob
fastboot flash recovery twrp.img
I have also tried directly writing the partition in terminal on the Transformer Prime via:
dd if=twrp.blob of=/dev/block/mmcblk0p4
Symptoms:
1. I power on with volume down pressed. I see "Android cardhu-user bootloader <1.00 e> released by "US_epad-10.4.2.18-20121122" A03
2. In fastboot, if I immediately execute "fastboot reboot-loader" then the tf201 reboots but does not enter recovery. So fastboot is definitely communicating.
3. In fastboot, if I first use the flash recovery command and then try "reboot-loader" then fastboot gives the error: FAILED (command write failed (Unknown error))
4. In fastboot, both methods for flashing recovery say they are writing. (i.e. with and without the "-i 0x0b05")
Guesses:
My guess is the bootloader is corrupted. It is able to boot the OS but can't boot the recovery partition. Hopefully I didn't corrupted it by not including "-i 0x0b05".
I haven't worked with block devices much. I see I have /dev/block/mmcblk0p[1-10] and mmblck0boot[0-1]. I find it interesting there are two block devices beginning with "mmblck0boot" but that could just be showing my lack of knowledge.
Any ideas? I am stumped.
Thanks,
Tim
timandjulz said:
Running a TF201, I tried to flash latest TeamWin Recovery and ClockworkMod Recovery. I can no longer get into recovery. But I can get into CM 10.1. Recovery just hangs at the volume down/up selection screen after I choose to start recovery.
I have tried the following commands (with jelly bean files)
fastboot -i 0x0b05 flash recovery twrp.blob
fastboot flash recovery twrp.img
I have also tried directly writing the partition in terminal on the Transformer Prime via:
dd if=twrp.blob of=/dev/block/mmcblk0p4
Symptoms:
1. I power on with volume down pressed. I see "Android cardhu-user bootloader <1.00 e> released by "US_epad-10.4.2.18-20121122" A03
2. In fastboot, if I immediately execute "fastboot reboot-loader" then the tf201 reboots but does not enter recovery. So fastboot is definitely communicating.
3. In fastboot, if I first use the flash recovery command and then try "reboot-loader" then fastboot gives the error: FAILED (command write failed (Unknown error))
4. In fastboot, both methods for flashing recovery say they are writing. (i.e. with and without the "-i 0x0b05")
Guesses:
My guess is the bootloader is corrupted. It is able to boot the OS but can't boot the recovery partition. Hopefully I didn't corrupted it by not including "-i 0x0b05".
I haven't worked with block devices much. I see I have /dev/block/mmcblk0p[1-10] and mmblck0boot[0-1]. I find it interesting there are two block devices beginning with "mmblck0boot" but that could just be showing my lack of knowledge.
Any ideas? I am stumped.
Thanks,
Tim
Click to expand...
Click to collapse
I'm no expert but did you try booting to recovery right from CM10.1? Enable the option in the power options menu (I think?) then try that? For me to get to recovery sometimes I need to power on with both volume up AND down held. Try either, but like I said this knowledge comes from a using 10.1-10.2 every day from its release.
Bricked!
TheYoz said:
I'm no expert but did you try booting to recovery right from CM10.1? Enable the option in the power options menu (I think?) then try that? For me to get to recovery sometimes I need to power on with both volume up AND down held. Try either, but like I said this knowledge comes from a using 10.1-10.2 every day from its release.
Click to expand...
Click to collapse
Something is preventing me from posting as timandjulz so I had to create a new account.
Rebooting recovery from CM10.1 would yield the same results. It reboots, hangs and never goes into recovery.
I didn't get a response here (except for yours... and thanks for trying!) so I decided to roll the dice. After trying everything else I did a wipe. Which thoroughly bricked the device. So now I get to open it up and see what parts I can salvage. It sucks. But sometimes it is better to finally figure out you are dead.
I hope the LCD can be used with a Raspberry Pi or BeagleBone Black with some additional hardware.
timandjulz2 said:
Something is preventing me from posting as timandjulz so I had to create a new account.
Rebooting recovery from CM10.1 would yield the same results. It reboots, hangs and never goes into recovery.
I didn't get a response here (except for yours... and thanks for trying!) so I decided to roll the dice. After trying everything else I did a wipe. Which thoroughly bricked the device. So now I get to open it up and see what parts I can salvage. It sucks. But sometimes it is better to finally figure out you are dead.
I hope the LCD can be used with a Raspberry Pi or BeagleBone Black with some additional hardware.
Click to expand...
Click to collapse
No bootloader menu at all now ?
flumpster said:
No bootloader menu at all now ?
Click to expand...
Click to collapse
Nope. Based on what I have read, it is now thoroughly bricked.
Related
Not quite sure what has gone wrong with my tablet but it seems that my recovery partition has been wiped (no recovery) and my boot.img has also gone.
What caused it:
I was installing Ubuntu onto my Prime and I got to the stage where I flash the boot.img. However, fastboot said it was sending the file, then writing the file and reported both "<OKAY>". However, I am not receiving a blue bar as other people say they do, yet I have done before when following the NVFlash guide (yes, I have all my blobs and things backed up).
Anyway, I have tried installing the Universal Driver and it seems to work (shows up in Device Manager). However, any commands that I send to the tablet do not seem to work (fastboot FLASH COMMANDS).
Commands I've entered: fastboot -i 0x0b05 flash boot prime-sdlinux.blob, fastboot -i 0x0b05 flash recovery twrp.blob
Also, "commands such as fastboot -i 0x0b05 erase recovery" result in: erasing 'recovery' ... FAILED (command write failed (Unknown error))
I'm really stuck and it's getting late, not sure what to do. Hope you guys can help me out.
PS: Not sure if this helps but, I cannot turn off the device. It constantly reboots just to hang at the Asus Eee Pad Screen or to hang at the Fastboot screen (when volume_down is held).
EDIT: After troubleshooting some more I have found that uninstalling the naked driver and letting Windows find a driver will actually allow me to send a reboot command (and it'll work). However, any fastboot flash commands do not seem to work. No Progress Bar appears and any commands sent after a flash command do not work (can't reboot after sending a flash command).
Hold the volume up while pressing the power button for about 15 seconds or until it vibrates then release them and it should power off for you.
did you make an nvflash backup?
else try
Code:
downloaded the latest Virtuous Prime ROM.
extract the ZIP file and pull the file called 'blob'
rename the file as boot.blob and move it to the TOOLS folder and open Command Prompt
from the TOOLS folder, type: fastboot -i 0x0b05 flash boot boot.blob
then type: fastboot -i 0x0b05 reboot
this should make you capable to go to recovery again
Open a command prompt; type adb push virtuous_prime.....zip /sdcard/
Wait until you get a confirmation message
Flash the rom like you normally do
Done
found this solution somewhere....
I do have an NVFlash backup, just not with me right now. Will test the above method first. And thanks for the method of turning it off! Although I know it's still on. Just in APX mode.
EDIT: Windows XP (run through VirtualBox on my laptop) seems to pickup my tablet in fastboot devices now. However, I'm still not seeing a progress bar after flashing again, and have the same problems as before (cannot reboot from fastboot). Still doesn't work. I've run fastboot through a native Windows 7 machine and a Windows XP installation on a Mac. Not sure what else I can try if fastboot isn't working.
EDIT2: It seems that I no longer have the error "FAILED (command write failed (Unknown error))" with certain commands.
First, you are in the wrong section, it should be in Q&A.
Second why didn't you try nvflash?
See this: http://forum.xda-developers.com/showpost.php?p=29204285&postcount=228
I believe the reason why fastboot is not working is because you are flashing blobs whilst using AndroidRoot.mobi bootloader.
http://forum.xda-developers.com/showpost.php?p=28875606&postcount=80
I believe you'll have to blobunpack the blob and then flash the raw img files instead.
That actually makes perfect sense! Would have taken me ages to figure out by myself. Thought it was perm-bricked until I got back to my NVFlash backup files. Will try it out.
kokopuphz said:
I believe the reason why fastboot is not working is because you are flashing blobs whilst using AndroidRoot.mobi bootloader.
http://forum.xda-developers.com/showpost.php?p=28875606&postcount=80
I believe you'll have to blobunpack the blob and then flash the raw img files instead.
Click to expand...
Click to collapse
I was in a similar situation until someone pointed me in this direction. Using BlobUnpack on both recovery and boot images gives you boot.LNX.SOS and Recovery.img.SOS (or similar names)
Flashing these solved my issues.
Yea, it worked. Thanks a lot for the help guys. Just takes one extra step to flash something now, kinda annoying, but definitely worth knowing that your tablet is brick-proof.
Asus TF201 stuck on Asus Logo screen + "this device is unlocked" -- Newbie here!
Hi guys,
First off- I have to clarify that I don't know squat about Android..
I got this TF201 tablet from a technology-ill friend who asked if I can do something about it.
I've encountered many posts of people with this issue:
* Powering On the tablet get it stuck on the Asus Logo screen, with the "this device is unlocked" writing on the top left corner (and the nVidia Logo on the bottom right).
* Trying to power off the tablet only causes a power cycle, and it gets stuck in the same screen all over again.
* Trying to boot into fastrecovery (I think that's how it's called? - pressing the down volume button+power button) gets to the same stuck on screen as mentioned.
* Only way I got it to power off (I think) is by pressing the up volume button+power button and then first releasing the power button after the screen is blank (and only after the volume button).
* Connecting the tablet to the computer doesn't seem to work - it won't recognize the USB device (I do see "APX" under the list of Other Devices on the Device Manager) - can't seem to find (working) drivers.
I've read that there's a way to solve this using NVFlash -- don't think I have that..
Found other workarounds, but as I mentioned - I don't know how to get around much in this territory.
Anyone who's patient enough to help me out (if such thing is even remotely possible) ?
It will be much appreciated !
help?
I tryed install the v30, and later v26 version, but do not work.
When powering On the tablet get it stuck on the Asus Logo screen, with the "this device is unlocked" writing on the top left corner and the nVidia Logo on the bottom right.
Trying start with power mode, but boot do not start, only RCK mod recovery/fastboot started.
I think, that device is not unlocked. How to check/verify the device really unlocked? Or any idea? Please help me. Thanks.
Have one pf you @msarg77 or @skew01 got the tablet working again?
I am stuck with a tf201 which has TWRP 2.8 but after installing Katkiss 6 it won't boot; keeps rebooting...
deltabet, Can you get into the TWRP console?
NP
I'am sorry Nektopoli that i did not answer you any sooner.
The original fault was that i had formatted the tab with the wrong file system; it should have been f2fs.
After that is was Murphy, i run into other problems ending up with no fastboot, no adb, no TWRP only APX mode.
Luckily i had made the NvFlash backup of my tab with the important tab id files...
But i managed to get my tablet working with Android 6, but had to reinstall the original Asus firmware with the nvflash backup i had made.
An other problem i run into was that my tablet had an older bootloader 10.4.2.15 and this should have been 10.4.2.18.
With the reinstall of the latest Asus firmware (from support site Asus) i received the correct bootloader.
Anyhow, I am glad the tab is working again. And i have learned a lot about installing a rom on an Android tab.
Good to hear, but you should try be on BootLoader: 10.6.1.27.1 if you want to use one of the newer KANG-TWRP
NP
Check out this link for info on the bootloader;
https://forum.xda-developers.com/transformer-prime/help/bootloader-questions-tf201-t3104884
Same Problem... Different Day...
Nektopoli said:
Good to hear, but you should try be on BootLoader: 10.6.1.27.1 if you want to use one of the newer KANG-TWRP
NP
Check out this link for info on the bootloader;
https://forum.xda-developers.com/transformer-prime/help/bootloader-questions-tf201-t3104884
Click to expand...
Click to collapse
Hya Gang... I seem to have the same problem.....
The good news here is that I am able to get into the bootloader, and I do have BootLoader: 10.6.1.27.1 and I am able to fastboot into my windows computer... I have tried fastboot flashing both the flatline TWRP and the latest TWRP but here is my problem..
It will start into the TWRP recovery screen for a few seconds... then goes black. This computer was working fine running KatKiss a few weeks ago, then one night just crashed, went into the above described bootloop and got me stuck in this situation...
Unidave199, you might have to do a full wipe (via a laptop or computer), flash KANG's TWRP [found here: https://basketbuild.com/devs/Captain_Throwback/TF201T/TWRP ].
Boot into the new TWRP and then flash the ROM, GAAPs and SuperSU. I was able to send these commands to my TF201 to up-brick it;
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
Then flash the TWRP and reboot
fastboot -i 0x0B05 flash recovery c:\your\DIRECTORY\path\BLOB.FILE <TWRP zip file
fastboot -i 0x0B05 reboot
Good Luck
NP
Nektopoli said:
Unidave199, you might have to do a full wipe (via a laptop or computer), flash KANG's TWRP [found here: https://basketbuild.com/devs/Captain_Throwback/TF201T/TWRP ].
Boot into the new TWRP and then flash the ROM, GAAPs and SuperSU. I was able to send these commands to my TF201 to up-brick it;
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
Then flash the TWRP and reboot
fastboot -i 0x0B05 flash system c:\your\DIRECORY\path\HERE
fastboot -i 0x0B05 reboot
Good Luck
NP
Click to expand...
Click to collapse
Regarding this line:
fastboot -i 0x0B05 flash system c:\your\DIRECORY\path\HERE
Is this a directory of the TWRP .img file that you've included in your post?
Luckily i had made the NvFlash backup of my tab with the important tab id files...
But i managed to get my tablet working with Android 6 said:
what did you use to restore your id files?
Click to expand...
Click to collapse
Krysiul said:
Regarding this line:
fastboot -i 0x0B05 flash recovery c:\your\DIRECTORY\path\HERE
Is this a directory of the TWRP .img file that you've included in your post?
Click to expand...
Click to collapse
Yes, but I made a mistake, it needs to be flashed to the recovery partition NOT system
NP
asus tf201 stucked on "the device is unblocked"
I seem to have the same problem with my asus tf201
Have you solved this problem?
shehada said:
I seem to have the same problem with my asus tf201
Have you solved this problem?
Click to expand...
Click to collapse
You need a computer or laptop (windows 7 or XP is preferred) with;
Universal_Naked_Driver_0.72: https://forum.xda-developers.com/attachment.php?attachmentid=1489873&d=1353190173
and
Minimal ADB and Fastboot: https://forum.xda-developers.com/showthread.php?t=2317790
Then you can plug the TF201 into the computer and see if you can receive fastboot commands like: adb reboot
NP
I am very new to this, I rooted my Moto G4 and now I need to download SUHide in order to play Pokemon Go. When I try to enter recovery via my fastboot/abd folder I get a < waiting for any device > message. When I hold down the power + volume down button my phone just turns on as normal without entering bootloader even though my bootloader is unlocked. I tried downloading an app that loads recovery for me but when I tried that I got a "no command" screen with a little green robot.
From what I've read, it's possible I didn't flash my trwp properly? I don't know how this is possible since I just rooted my phone. I would appreciate some help, I'm afraid to take any random guesses at the risk of ruining my phone. Sorry if I'm missing something obvious or not giving enough info, I'm not very tech savvy.
levijoseph said:
I am very new to this, I rooted my Moto G4 and now I need to download SUHide in order to play Pokemon Go. When I try to enter recovery via my fastboot/abd folder I get a < waiting for any device > message. When I hold down the power + volume down button my phone just turns on as normal without entering bootloader even though my bootloader is unlocked. I tried downloading an app that loads recovery for me but when I tried that I got a "no command" screen with a little green robot.
From what I've read, it's possible I didn't flash my trwp properly? I don't know how this is possible since I just rooted my phone. I would appreciate some help, I'm afraid to take any random guesses at the risk of ruining my phone. Sorry if I'm missing something obvious or not giving enough info, I'm not very tech savvy.
Click to expand...
Click to collapse
Try power plus volume up button to go to fastboot mode.
If it not working then connect your android to pc and enable adb. Type "adb devices" enter then type "adb reboot bootloader" and enter. It boots your android in fastboot mode.
If adb commands not working then install adb and fastboot drivers and try again.
https://forum.xda-developers.com/showthread.php?t=2317790
In most devices, volume up + power boots up the recovery options, volume down + power boots the device into fastboot mode (volume buttons first plus power, pressing power button first would boot the device normally).
levijoseph said:
When I try to enter recovery via my fastboot/abd folder I get a < waiting for any device > message. When I hold down the power + volume down button my phone just turns on as normal without entering bootloader even though my bootloader is unlocked.
Click to expand...
Click to collapse
How did you install the custom recovery? Try flashing the recovery.img again (I'm guessing, since you have root, that you did not "flash" (fastboot flash recovery recovery.img) TWRP but just "boot" (fastboot boot recovery.img) it and installed SuperSU).
Ashwinrg said:
Try power plus volume up button to go to fastboot mode.
If it not working then connect your android to pc and enable adb. Type "adb devices" enter then type "adb reboot bootloader" and enter. It boots your android in fastboot mode.
If adb commands not working then install adb and fastboot drivers and try again.
https://forum.xda-developers.com/showthread.php?t=2317790
Click to expand...
Click to collapse
Okay, so that did work, and I was able to enter fastboot mode. However, once I scrolled down to "recovery mode" and tried to enter, I got the same "no command" screen.
rolland.arriza said:
In most devices, volume up + power boots up the recovery options, volume down + power boots the device into fastboot mode (volume buttons first plus power, pressing power button first would boot the device normally).
How did you install the custom recovery? Try flashing the recovery.img again (I'm guessing, since you have root, that you did not "flash" (fastboot flash recovery recovery.img) TWRP but just "boot" (fastboot boot recovery.img) it and installed SuperSU).
Click to expand...
Click to collapse
I used the official moto g4 root guide on this website to root my phone and I'm pretty sure I booted, not flashed, the recovery img (mine is named twrp-3.0.2-0-athene). So, I tried using the command you provided to flash the recovery img and I got a < waiting for any device > message in the command prompt. My phone is plugged in and my recovery img is in the adb / fastboot folder. Any idea what this means? Thank you for the help guys
edit: If it helps to know this, my phone has usb debugging enabled and it is recognized by my pc. I type adb devices and my moto g4 serial number does indeed show up.
levijoseph said:
I am very new to this, I rooted my Moto G4 and now I need to download SUHide in order to play Pokemon Go. When I try to enter recovery via my fastboot/abd folder I get a < waiting for any device > message. When I hold down the power + volume down button my phone just turns on as normal without entering bootloader even though my bootloader is unlocked. I tried downloading an app that loads recovery for me but when I tried that I got a "no command" screen with a little green robot.
From what I've read, it's possible I didn't flash my trwp properly? I don't know how this is possible since I just rooted my phone. I would appreciate some help, I'm afraid to take any random guesses at the risk of ruining my phone. Sorry if I'm missing something obvious or not giving enough info, I'm not very tech savvy.
Click to expand...
Click to collapse
If you are trying to flash twrp recovery on your android then rename your twrp to recovery.
Boot your android in fastboot mode,
Navigate to folder that you have recovery. Press shift and right click and click on open command here and type "fastboot devices" and enter
"fastboot flash recovery recovery.img
It flash your recovery to your android.
Ashwinrg said:
If you are trying to flash twrp recovery on your android then rename your twrp to recovery.
Boot your android in fastboot mode,
Navigate to folder that you have recovery. Press shift and right click and click on open command here and type "fastboot devices" and enter
"fastboot flash recovery recovery.img
It flash your recovery to your android.
Click to expand...
Click to collapse
Did all that, getting:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
error: cannot load 'recovery.img'
Also, per the suggestion of other users on these forums, I tried to hold down power and press volume up during the "no command" screen after attempting to enter recovery. That sent me into Android Recovery but it's not the twrp platform I used when originally rooting my phone.
How did you unlock the bootloader? have you tried: fastboot oem unlock?
You need to "allow oem unlocking" on developer options (which I guess you already did). Then reboot in bootloader: (a) adb reboot bootloader. In fastboot, you need to unlock the bootloader first: (b) fastboot oem unlock (or unlock-go). Then you can try to flash that recovery.img: (c) fastboot flash recovery "name of the file.img"
edit: fastboot oem unlock restores the device to factory settings. You need to configure and enable again "usb debugging" and "oem unlocking" (which are disabled by default). You can then proceed to fastboot flash
Hey guys - while trying to unlock the bootloader on my HDX 7, I flashed the older aboot per instructions and now cant get the HDX to boot. It shows a backlit black screen when attempting to boot, IT IS recognized by the computer, and I have ADB composite drivers installed, so thats what it is seen as in device manager. I can't see the system mounted as a file folder, however, I can get it to semi-respond to fastboot commands. fastboot devices lists the serial number, fastboot reboot will reboot it back to the backlit screen, fastboot -w did its thing and wiped it, fastboot flash boot boot.img seems to flash the boot.img, but it still will not boot. Also, NO adb commands are working, and it is not seen when adb shell or adb devices is executed. Am I totally F*cked, or is there hope that I can somehow flash a recovery via fastboot and get a system img flashed? any help or thoughts would be great.
sunapeelakers said:
Hey guys - while trying to unlock the bootloader on my HDX 7, I flashed the older aboot per instructions and now cant get the HDX to boot. It shows a backlit black screen when attempting to boot, IT IS recognized by the computer, and I have ADB composite drivers installed, so thats what it is seen as in device manager. I can't see the system mounted as a file folder, however, I can get it to semi-respond to fastboot commands. fastboot devices lists the serial number, fastboot reboot will reboot it back to the backlit screen, fastboot -w did its thing and wiped it, fastboot flash boot boot.img seems to flash the boot.img, but it still will not boot. Also, NO adb commands are working, and it is not seen when adb shell or adb devices is executed. Am I totally F*cked, or is there hope that I can somehow flash a recovery via fastboot and get a system img flashed? any help or thoughts would be great.
Click to expand...
Click to collapse
Barring a hardware problem your device is likely recoverable. Sounds like you may have flashed the wrong aboot; verify you're using the appropriate image. Aboot-13 is for the 7" (Thor); aboot-14 for the 8.9" (Apollo).
If that's not the issue you will need to coax the device into 'bulk mode' and rebuild from there. Not hugely difficult if comfortable with Android devices and working at the command prompt. There are random posts describing the process in the unlock thread. I'm not in a position to post links ATM so you'll have to do some digging. Read carefully; details and sequence of operations matter.
Davey126 said:
Barring a hardware problem your device is likely recoverable. Sounds like you may have flashed the wrong aboot; verify you're using the appropriate image. Aboot-13 is for the 7" (Thor); aboot-14 for the 8.9" (Apollo).
If that's not the issue you will need to coax the device into 'bulk mode' and rebuild from there. Not hugely difficult if comfortable with Android devices and working at the command prompt. There are random posts describing the process in the unlock thread. I'm not in a position to post links ATM so you'll have to do some digging. Read carefully; details and sequence of operations matter.
Click to expand...
Click to collapse
I flashed aboot 13, but the device never booted after I flashed that and twrp. I figured I could get into twrp since I had flashed it one step previous, but I cant. So i wiped it using fastboot -w thinking I could get rid of the aboot file, then flashed twrp again using fastboot flash recovery recovery.img, it ran through its thing and seemed to flash successfully, but I still cant boot to anything but a blank black screen. no logos or anything. It does respond to all the fastboot commands, of which I only know enough to be dangerous. I've tried changing the drivers around to get adb working to no avail. It seems to be stuck in fastboot mode, even when i fastboot reboot and quickly unplug it. Just not sure where to go from here - it had 4.5.5.2 on it before all of this.
sunapeelakers said:
I flashed aboot 13, but the device never booted after I flashed that and twrp. I figured I could get into twrp since I had flashed it one step previous, but I cant. So i wiped it using fastboot -w thinking I could get rid of the aboot file, then flashed twrp again using fastboot flash recovery recovery.img, it ran through its thing and seemed to flash successfully, but I still cant boot to anything but a blank black screen. no logos or anything. It does respond to all the fastboot commands, of which I only know enough to be dangerous. I've tried changing the drivers around to get adb working to no avail. It seems to be stuck in fastboot mode, even when i fastboot reboot and quickly unplug it. Just not sure where to go from here - it had 4.5.5.2 on it before all of this.
Click to expand...
Click to collapse
Bulk mode and rebuild.
Davey126 said:
Bulk mode and rebuild.
Click to expand...
Click to collapse
Ok, I executed fastboot -i 0x1949 erase aboot and seemingly put the HDX into bulk mode - I can now see a bunch of disk drives on the computer, and it is now recognized as "other devices" "QHSUSB_BULK" in device manager. I still am unable to execute adb commands at this time.
sunapeelakers said:
Ok, I executed fastboot -i 0x1949 erase aboot and seemingly put the HDX into bulk mode - I can now see a bunch of disk drives on the computer, and it is now recognized as "other devices" "QHSUSB_BULK" in device manager. I still am unable to execute adb commands at this time.
Click to expand...
Click to collapse
https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post71430759
Davey126 said:
https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post71430759
Click to expand...
Click to collapse
ok sick, I was able to execute those commands for aboot and twrp 3.1.1.1 and get the HDX booted into TWRP. now my issue is that I have nothing to install to get a system image going. Any suggestions on something safe?
Got slimrom installed and running 7.1.2 - awesome! Thanks so much for the help!
First time poster.... please go gentle on me. Not entirely new to custom roms and TWRP, but really stuck here. I am trying to install a CrDroid ROM. Phone is not networked locked and brand new. What I managed to do so far:
1. Reset the phone
2. reboot into Recovery (Mi Recovery)
3. Wipe data
4. Unlocked the phone (using offical Mi Unlock)
I then proceeded to boot into Fastboot and flashed the TWRP (twrp-3.7.0_12-0-onclite), renamed to recovery. But after flashing and rebooting I can only get into Fastboot, or boot it normally. Holding down the Volume+Up and Power button doesn't get me anywhere but Fastboot. (Same for Volume-Down and Power Up). I tried both un-pluggin the phone from the PC immediately after flashing is finished, and using Fastboot Reboot command, but all to no avail. Its Fastboot or normal boot only.
I also tried whats suggested here upto the vbmeta image, but didn't make a difference. When sending the 'fastboot boot recovery.img' command, I get the following error:
C:\adb>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.939s]
booting...
FAILED (remote: unknown reason)
finished. total time: 1.502s
Trying this guide for a 'custom' boot image from this page also didnt help
Really hoping there is a way to get this resolved. But totally stuck here. Have access to both Mac OS and Windows 10. If anyone can point me in the right direction it would be wonderful!
Ok, small update - in hope to help others...
I went ahead and used 'XiaoMiTool V2'to see if it might help to load a different ROM. When starting the app, I choose the 'Bricked' device option, even it wasnt bricked. I choose the Global ROM 12. (The phone showed up as unknown and I didnt sign in with the Mi Account).
After the new ROM was on it, phone started normally and went through the setup. Had to re-enable Developer Options, USB Debugging, but even so it still didnt work - installing the TWRP just kept bringing me back to Fastboot.
However, the TWRP from this page did work: https://twrp.me/xiaomi/xiaomi-mi439.html
I also took no chances and held the Volume up button pressed and with the Command window open and 'fastboot reboot'typed out, hit the Enter key at the same time as pressing the Power button on the phone.
Worked for me!
Try to install PitchBlack Recovery it's very compable PBRP-pine-3.1.0 _OFFICIAL
Timesnaps said:
First time poster.... please go gentle on me. Not entirely new to custom roms and TWRP, but really stuck here. I am trying to install a CrDroid ROM. Phone is not networked locked and brand new. What I managed to do so far:
1. Reset the phone
2. reboot into Recovery (Mi Recovery)
3. Wipe data
4. Unlocked the phone (using offical Mi Unlock)
I then proceeded to boot into Fastboot and flashed the TWRP (twrp-3.7.0_12-0-onclite), renamed to recovery. But after flashing and rebooting I can only get into Fastboot, or boot it normally. Holding down the Volume+Up and Power button doesn't get me anywhere but Fastboot. (Same for Volume-Down and Power Up). I tried both un-pluggin the phone from the PC immediately after flashing is finished, and using Fastboot Reboot command, but all to no avail. Its Fastboot or normal boot only.
I also tried whats suggested here upto the vbmeta image, but didn't make a difference. When sending the 'fastboot boot recovery.img' command, I get the following error:
C:\adb>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.939s]
booting...
FAILED (remote: unknown reason)
finished. total time: 1.502s
Trying this guide for a 'custom' boot image from this page also didnt help
Really hoping there is a way to get this resolved. But totally stuck here. Have access to both Mac OS and Windows 10. If anyone can point me in the right direction it would be wonderful!
Click to expand...
Click to collapse
You are trying to install onclite (Redmi 7) recovery on pine (Redmi 7A) ???
mi439 TWRP works for me as well & even successfully flash the rom/gapps. but when it comes to rooting with Magisk, i failed to flash nor install it properly. hope someone/somebody would make a tutorial for flashing/installing Magisk.