I was upgrading the current Stock rom on my ZTE Nubia Z5s Mini, I went through the recovery mode to load the new rom and got a message saying that the rom installed correctly, I rebooted the device and now its stuck at the MIUI logo or if I try to load the recovery mode I get the Nubia logo just to load back to the miui logo again. I got the rom from the MIUI site its v5.
I've left the phone for over an hour hoping it was just loading up but no change, the phone heats up and even has a charger screen when plugged in.
Anyway to get back into the recovery mode to load the original rom again or any other way of fixing this? help :crying:
I've no idea how to help you with this but I'm bumping the thread because I know how you feel.
Sent from my HUAWEI Y536A1
I'm trying to flush the rom by using adb but with an issue, even thou my device is recognized as Nubia Z5s Mini in device manager it still gives a driver error "these have been installed" and in cmd adb it does not see the device.
Update : Got drivers for install from Clockwordmod website but it will only accept the drivers if I set the phone as a modem in device manager when installing them, still not recognized by adb using CMD.
Solved driver issue and qusb_download issue, ADB drivers are done through all drives in device manager pointing to the Google USB drivers and select adb interface then run CMD from within the Google SDK program folder in platform-tools to read the device.
Now using emmc but need to generate EMMCBLD.HEX & 7x30_msimage.mbn if anyone can help, I can enter adb using recovery mode but blocked from making changes in fastboot mode, currently in download mode which can see a drive H but need the two files to proceed any further.
Related
Hi!
First off let me say thanks to R_a_z_v_a_n for redirecting me and hope that I'll find my answer here ^^
So I Have this device called HP 7 VoiceTab 1321RA (not with Slate just HP 7 Voicetab), wanting to have a custom recovery then I tried to flash a CWM Custom Recovery for HP Slate 7 VoiceTab because I thought it was the same and ends up bricking my phone. It ends up in a bootloop which only shows HP sign for a few seconds and dead. But I managed to find out that I can access the recovery menu (or so I thought it is), but the options was choosing between Fastboot Mode, Normal Boot, Recovery Mode, and VART Mode.
I tried to enter Fastboot Mode before and tried to access it via PC but somehow I can't find the device by entering adb devices and fastboot devices. Anyways, I have downloaded a stock update.zip for it but not the original KitKat one which I get from the first time I bought it but rather the JB ones. I think by flashing this would help me recover the device but the only problem is I don't know which method should I use to Flash it. Since I don't have the Stock Recovery or ANY kind of recovery at all, I guess I'm stuck. And it won't start to the home page so I can't set the USB debugging options. Please guide me through this >.<
Thanks a lot!
Been fighting with it for 2 days now and still no result came.
So here's the update so far....
I tried on my other device in order to understand how my PC reads ADB and now I kinda gets it. But the problem is now can't get the device to enable USB Debugging because I can't access options at all.
Secondly, since I left it on for the night because charging seems to trigger the bootloop too, now I can't access the fastboot mode like I was last night. And it constantly repeating this sequence: [battery scene with the "charging battery" symbol] > [HP Powered by Android screen] repeated for 2-3 times > [low battery need charging screen] > repeat. And once I tried to connect to the PC, it goes to the same sequence too. When I tried to access the boot options (the screen which displays Fastboot Mode, Normal Boot, Recovery Mode, and UART Mode which I mention in Thread Starting post), it shows the low battery need charging scene and then repeating the same sequence as mentioned above.
I seem to figure out how to fix this but I still can't manage to access the fastboot mode yet. Will give update once I can try to.
Anyone can help me on this?
Thanks a lot!
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
I found my self in a deadlock!
PLEASE HELP :crying:
Could you unbrick yours
What service centre says about that problem i also ran in this problrm but i m trying to go to service centre for that
first off install drivers in your PC as admin
then use the official flashtool to flash ur stock firmware by entering fastboot or flashmode simple as that
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
jithinraj said:
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
Click to expand...
Click to collapse
Dude urs is a mtk device so sp flash tool should do the trick.... Just don't forget to install correct drivers....run both drivers and flash tool as admin..... Tell me when it's solved k
jithinraj said:
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
Click to expand...
Click to collapse
That is what im trying. To tell you urs is a mediatek device the official flashtool is sp flashtool
rikicchi said:
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
Click to expand...
Click to collapse
try to push the update.zip via adb sideload (Choose "update via ADB sideload" on recovery mode)using adb terminal on PC,as long as your tab can access the recovery mode.remember to backup all your data before u do it.
have a try it's 100% work on me
where I can download update.zip file? anyone can help?
rikicchi said:
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
Click to expand...
Click to collapse
can you explain how did you managed to charge the device??? please its a request......jst help me out :crying::crying:
first I rooted my device following this http://en.miui.com/thread-30617-1-1.html
then I started super SU and selected normal.
then I opened GLtools i downloaded from here http://forum.xda-developers.com/ ... tools-1-29-t2828630
I installed the GLtools apk and opened it, it asked me to select TEX(DE)coder and install, I did that, super SU asked for root permission, I granted. Mipad rebooted, I opened GLtools nothing changed, it still asks me to install texdecoder, weird, so I installed that again and rebooted and now mipad is bricked and stuck at the MI logo.
I can go into fastboot, however when I tried to use mi pc suite or miflash they do not detect the device so I cant flash fastboot.
when in fastboot device manager shows "android phone fastboot" and it says no drivers are installed for this device, I tried installing drivers like adb driver and fastboot driver etc but it doesnt help.
I am able to boot up the device by using system two, but I need to unbrick system one in case system two gets screwed up.
when in system two, device manager shows android composite device and mi pad and says drivers are up to date. however I still cant anything in fastboot.
I have tried installing android SDK to flash from command prompt but again it doesnt detect hte device and is stuck on waiting for device.
Similar Issue
Without installing TWRP or CWM , I Selected TWRP/CWM in Supersu Binary Installation. Now my MI Pad is stuck at a blank screen
Any help with rebooting the device and flash it
Intall from fastboot
Wassup aliens!
So I got this gionee M3 and I rooted it with iRoot and tried to flash recovery in nearly every way possible....... I tried using Flashify, Rashr, TWRP manager..... Nothing worked.
1) On Flashify: I kept selecting Flash recovery but the message I get every time is "Error copying the file, please send me the log file".
2) On Rashr and TWRP Manager: They both say they flashed the file but when I boot into recovery all I see is gray screen with a gionee logo. I also lost my stock recovery this way.
3) On PC: My PC never detects my phone as an adb or VCom device........To check for VCom I tried SP Flash Tools..... didn't detects the device. For Adb I tried Adb devices in command prompt but the devices list is empty.
Some info:
I have USB debug mode enabled.
I have stock 5.0.2 android rom with no recovery just factory safe mode through which I can perform some tasks.
If you need any pics or any info just tell me in the comments.
I hope you guys help me.... Been trying for the last 6 days.
HELP ASAP SOS
Love,
Justin Biebar
Tarun0101 said:
Wassup aliens!
So I got this gionee M3 and I rooted it with iRoot and tried to flash recovery in nearly every way possible....... I tried using Flashify, Rashr, TWRP manager..... Nothing worked.
1) On Flashify: I kept selecting Flash recovery but the message I get every time is "Error copying the file, please send me the log file".
2) On Rashr and TWRP Manager: They both say they flashed the file but when I boot into recovery all I see is gray screen with a gionee logo. I also lost my stock recovery this way.
3) On PC: My PC never detects my phone as an adb or VCom device........To check for VCom I tried SP Flash Tools..... didn't detects the device. For Adb I tried Adb devices in command prompt but the devices list is empty.
Some info:
I have USB debug mode enabled.
I have stock 5.0.2 android rom with no recovery just factory safe mode through which I can perform some tasks.
If you need any pics or any info just tell me in the comments.
I hope you guys help me.... Been trying for the last 6 days.
HELP ASAP SOS
Love,
Justin Biebar
Click to expand...
Click to collapse
Hey i have the same problem. Can you suggest me something regarding this.
A very big question
Hello! I have an argentine copy of the M3, called Hyundai Ultra Energy, same processor, same storage, camera quality, all in the same place. My question is how do I install a custom rom and how do I flash the recovery at first. I use adb commands, but I know that I have to do it with spflash. How is the process? I download the rom, charge the scatter and tilt only in recovery? Would be dangerous? Is more safe to root with King Root?
Hey guys,
Got my tablet sorted, I flashed a ftf rom which was new to me entirely, did the process via flashtool and the tab worked perfectly!
I now face an issue where the tablet is not found by fastboot and I need i am looking to get custom recovery for a new rom so I need access. I've tried a bunch of drivers, adb versions, ways of doing it, and now even flashtool doesnt pick the tablet up.
I get the blue light, but I always get "update driver version" from flash tool - didn't work.
I have updated drivers with signature verification turned off, didnt work. I could only boot into fastboot mode and that was with the tablet having faulty or non working drivers installed (still had and still have yellow triangle)
I had this issue but sorted it as I had root and such beforehand. Ideally I just want a custom recovery to install the custom oreo rom in the dev forum, but have had no such luck at all.
thanks for help in advance!
Same problem
CptUnicorns said:
Hey guys,
Got my tablet sorted, I flashed a ftf rom which was new to me entirely, did the process via flashtool and the tab worked perfectly!
I now face an issue where the tablet is not found by fastboot and I need i am looking to get custom recovery for a new rom so I need access. I've tried a bunch of drivers, adb versions, ways of doing it, and now even flashtool doesnt pick the tablet up.
I get the blue light, but I always get "update driver version" from flash tool - didn't work.
I have updated drivers with signature verification turned off, didnt work. I could only boot into fastboot mode and that was with the tablet having faulty or non working drivers installed (still had and still have yellow triangle)
I had this issue but sorted it as I had root and such beforehand. Ideally I just want a custom recovery to install the custom oreo rom in the dev forum, but have had no such luck at all.
thanks for help in advance! [/QUOTE
Hello
Have you found a solution since then? Once my tablet is in Fastboot mode (bluelight) i can not give it commands any more. adb devices works.reboot workswhen in normal mode. but no other commands afterwards
Thanks
Click to expand...
Click to collapse
I actually just solved this same problem.
The problem is a Windows thing--it doesn't like the Fastboot drivers because they're not digitally signed.
Here's what I did:
1. Disable Signed Driver Enforcement (see below)
2. Download the Flashtool tool
3. Run c:\flashtools\drivers\Flashtools-drivers.exe
3. Install Fastboot and Flashboot, and the driver for the Z3C.
4. When the scary windows box with the Red bar at the top appears, cllick "Install the driver software anyway."
5. Flashtool now works.
------
Disable Signed Driver Enforcement: Step-by-step instructions
Click the Start Start menu and select Settings.
Click Update and Security.
Click on Recovery.
Click Restart now under Advanced Startup.
Click Troubleshoot.
Click Advanced options.
Click Startup Settings.
Click on Restart.
On the Startup Settings screen press 7 or F7 to disable driver signature enforcement.
Hi People,
I hope I am putting this question in the proper location.
I have had several attempts ate flashing a new ROM to my device as it was the Chinese version & kinda useless to me not having Play store or several other APPs I want. I also wanted to try ROOT a phone for the first time.
I managed to get as far as getting ADB & fastboot working & TWRP installed on the device. The first ROM I had put in my file storage was corrupt so I tried the Lineage 17 version which "seemed"to install with a success message, but the phone would only boot into TWRP. so I tried the Havoc ROM from the thread in this site area. Same thing, would only boot into TWRP. Then I thought I would start over & install the factory ROM from: https://xiaomifirmwareupdater.com/miui/olivelite/stable/V12.0.2.0.QCPMIXM/ with ADB & fastboot. I got a success message from the MiFlash tool but the device is now saying the "MIUI verson cannot be installed on this device" in one screen from the Redmi-Recovery 3.0 menu that's now on it.
From here I can Reboot, wipe data or connect with MiAssistant. When I try MiAssistant (PC Suite) the phone does not connect to my PC but I can see the ADB device from device manager and ./adb fastboot devices shows a serial number -but connected as sideload if that makes a difference?
I hope I explained well enough to be understood. Is there anything I can do from here to get it working or is it fully stuffed?
Ur device's bootloader still unlocked?
T0B3R said:
Hi People,
I hope I am putting this question in the proper location.
I have had several attempts ate flashing a new ROM to my device as it was the Chinese version & kinda useless to me not having Play store or several other APPs I want. I also wanted to try ROOT a phone for the first time.
I managed to get as far as getting ADB & fastboot working & TWRP installed on the device. The first ROM I had put in my file storage was corrupt so I tried the Lineage 17 version which "seemed"to install with a success message, but the phone would only boot into TWRP. so I tried the Havoc ROM from the thread in this site area. Same thing, would only boot into TWRP. Then I thought I would start over & install the factory ROM from: https://xiaomifirmwareupdater.com/miui/olivelite/stable/V12.0.2.0.QCPMIXM/ with ADB & fastboot. I got a success message from the MiFlash tool but the device is now saying the "MIUI verson cannot be installed on this device" in one screen from the Redmi-Recovery 3.0 menu that's now on it.
From here I can Reboot, wipe data or connect with MiAssistant. When I try MiAssistant (PC Suite) the phone does not connect to my PC but I can see the ADB device from device manager and ./adb fastboot devices shows a serial number -but connected as sideload if that makes a difference?
I hope I explained well enough to be understood. Is there anything I can do from here to get it working or is it fully stuffed?
Click to expand...
Click to collapse
You should flash China factory rom, if you can.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com