My device is Spice Dream Uno mi-498. So I flashed the TWRP recovery on my device via fastboot it ended successfully. So i entered the command ' fastboot reboot' in the command prompt. And since, the device is not booting, stuck in bootloop, I guess. Help me?
Related
So I'm in the process of trying to Root my ZTE Smarttab 10 on firmware v03b.
Ive been following instructions on the following pages:
http://forum.xda-developers.com/showthread.php?t=1629630
http://forum.xda-developers.com/showthread.php?t=1473555
The instructions are spread out across those threads and my problem starts kind of early in the process.
My goal is to use ADB to boot in to the Bootloader and then use a recovery rom to use TWRP to install a rom.
What i have done:
I have installed the ZTE Drivers
I have installed the SDK tools and updated it.
Now when the tablet is running normally I can see it in ADB and is able to run the command.
ADB Reboot Bootloader
This reboots the devices to a black screen (I assume this is the bootloader) and windows recognizes that a device is there.
The problem is that when I try to see this from ADB i cannot see the device when running ADB Devices.
This makes the next step impossible as I need to use ADB to boot a recovery rom.
So I would have posted in the development treads listed above but as I dont have 10 posts (this being my first post) I cannot post in the threads above.
I'm confident that this is a driver problem and I have uninstalled and re-installed all the drivers related to this including SDK.
But no luck yet.
Where other people say they have succeeded is when in the device manager they have ADB interface and ZTE Handset ADB interface listed.
This is the state where I'm at but I still cannot see the device in ADB.
Anyone have any insight on this kind of problem and can offer any help for a solution or direction to get to the solution.
Thank you for your help and attention!
//Nagarutu
Vodafone (ZTE) SmartTab10 3.2 HoneyComb
You can't use adb in bootloader mode, you want fastboot. So when you do 'adb reboot bootloader'. It reboots to the black screen (that is the bootloader). Try typing 'fastboot devices' and see if you're device comes up. It should if you have all drivers installed correctly and fastboot on your system. Then you'll be able to do 'fastboot flash recovery recovery.img' to install the custom recovery, then a 'fastboot reboot' and lastly an 'adb reboot recovery' will get you into your custom recovery to flash a new rom. Don't forget to make a backup.
matt4321 said:
You can't use adb in bootloader mode, you want fastboot. So when you do 'adb reboot bootloader'. It reboots to the black screen (that is the bootloader). Try typing 'fastboot devices' and see if you're device comes up. It should if you have all drivers installed correctly and fastboot on your system. Then you'll be able to do 'fastboot flash recovery recovery.img' to install the custom recovery, then a 'fastboot reboot' and lastly an 'adb reboot recovery' will get you into your custom recovery to flash a new rom. Don't forget to make a backup.
Click to expand...
Click to collapse
Thank you for the help ! it cleared things up for me.
Now the trouble's continue.
With the firmware im on (v03b) you cannot use the fastboot flash method but only fastboot.
And they way it is supposed to be done is that you run
fastboot boot recovery.img (recovery being a twrp recovery for my device)
When its booted to TWRP i should be able to see it in ADB to be able to run the following commands to it:
--> adb remount
--> adb shell
--> ln -s /system/xbin/su /system/bin/su
However I cannot get it to show in ADB (or fastboot) when its booted in to TWRP.
Any ideas?
I managed to solve the last bit to.
Now it was actually a driver problem, so i just updated the driver in device manager and located the ADB driver from ZTE and it worked to boot in to TWRP and then to flash the device.
Now I have CM10 installed and is smiling!
Took me 4 days but damn it its done!
Thanks for the help!
Glad you've figured it out
1a
2a
3a
4a
5a
I have a Micromax Canvas A1. I unlocked bootloader with ADB. Then I downloaded a recovery.img from Android File Host and stored in package-tools. Then in the command prompt I rebooted to fastboot and then "fastboot flash recovery recovery.img". It seemed to have completed successfully so I typed "fastboot reboot" and rebooted the phone. To check if it installed properly, I typed "adb reboot recovery" and after a loading screen with the Micromax logo (and RECOVERY MODE written at the bottom) a photo of an Android with an open flap and an exclamation mark appeared with "No command." written at the bottom.
What do I do? I retried with the same result and even reinstalled recovery. I downloaded an Android One toolkit and flashed CWM using that, but the same thing happened again.
I have a LeEco Le Pro 3 phone firstly i tried to root it using the tutorial i found here on how to flash the TWRP Recovery & Root the Le Pro 3 device. I followed the instructions and got to flashing the twrp recovery successfully but it wouldn't boot to the twrp recovery using the power+volume up button neither would it boot up normally the LeEco logo would just flash and it went blank. I eventually got it to boot to the recovery by putting it into the fastboot mode and using the adb fastboot method by typing "fastboot boot recovery recovery.img" i then tried to install the supersu and it install but it still wouldn't boot up normally nor to the twrp recovery still had to use the adb fastboot method. I made the mistake of not doing a back up before I did the wipe. I then figured maybe the OS got corrupted so I downloaded a stock rom and use adb sideload to get it on the storage of the phone. i made another mistake of not wiping the data before i restarted the phone now i can only get it into fastboot mode and i can see it when i do a "fastboot devices" check but it will take no other command as the bootloader is locked. Is there any solution to get the bootloader unlocked again. when i try to unlock it using the adb command "fastboot oem unlock-go" it return the reply "(failed remote oem unlock is not allowed)" fastboot error command failed. Please any help would be greatly appreciated
I wiped my phone to change the rom, but I couldn't find the rom file, so I restart the phone and get stuck at mi logo. I can enter into fastboot, but not in twrp. My computer recognizes fastboot through "fastboot devices", but I can't use "fastboot reboot recovery", I get the output "fastboot: usage: unknown reboot target recovery". What can I do?
Hey,
if fastboot works, you should be able to reboot to EDL and flash stock system image with Xiaomiflash.
Good luck!
Hello all,
I am stuck in this problem. Would appreciate any help.
Working in LINUX ubuntu 18.
Got a MI pad 1 with locked bootloader.
flashed TWRP recovery using fastboot. Booted into TWRP successfully.
Flashed the files from this
https://www.techeia.com/2018/10/best-custom-rom-for-mi-pad-1-2018.html
Everything flashed successfully.
Rebooted only to be stuck into MI logo screen. Bootloop probably because of locked bootloader.
Hence, I decided to wipe the bootloader itself
got the hint from here https://forum.xda-developers.com/mi-pad/how-to/fix-fastboot-bootloop-fix-xiaomi-mi-pad-t4008653
but I didn,t wiped recovery. but erased everything else. Then powered off to boot into previously installed TWRP recovery.
From there, I am trying to boot into fastboot or TWRP but the screen is showing blank. I am using the key pattern for fastboot or recovery and trying to detect the device into any mode through ubuntu terminal using
sudo fastboot devices and
adb devices
but its not detecting the device there also. USB debugging was enabled already.
Any clues for how can I boot into fastboot or TWRP from this.
Regards
Hiteshkartik
@hiteshkartik
A device with erased boot-loader never can work: you simly get a black screen. You no longer can communicate with it - neither via ADB nor via Fastboot.
Can I have a way around ?? I mean installing bootloader or somehow booting into fastboot or TWRP directly with any toolkit or terminal.