HI
I have unfortunately flashed a rom from another phone (ZTE NUBIA Z5 mini), now my screen is black, but I can hear that the phone is working; sound when turn on/off phone and sound when I adjust sound level. I have tried to use fastboot mode, but phone will not boot into fastboot, only into ADB mode where my device are listed. Due to my “ROM” fault, USB debugging mode is not turned on, so many of the tools I have tried does not work. Is the phone totally bricked or is there some possibilities that I can try?? Help will be much appreciated.
ROM is root, when I did a test with ONECLICK root, tools tells me that phone is root, so something are working just not my screen.
PS I cant remove battery, it is built into the phone
Basmand
UPDATE: HELP PLEASE
By a luck I was able to install a new ROM "ZTE-nubia-Z5-cm-10.2-20140115-" but be course I didn't have any picture on the screen I may have touch the phone, because the rom is booting up, but don't work probably due to uncompleted install. Now I have picture on the screen, I can go to recovery and bootloader mode, but still no picture on the screen in these 2 modes. I can use adb but not fastboot maybe driver issue, I have tried nearly every driver on the internet including SDK manager tool.
So is there any change that I can flash via adb mode?
Basmand
basmand said:
HI
I have unfortunately flashed a rom from another phone (ZTE NUBIA Z5 mini), now my screen is black, but I can hear that the phone is working; sound when turn on/off phone and sound when I adjust sound level. I have tried to use fastboot mode, but phone will not boot into fastboot, only into ADB mode where my device are listed. Due to my “ROM” fault, USB debugging mode is not turned on, so many of the tools I have tried does not work. Is the phone totally bricked or is there some possibilities that I can try?? Help will be much appreciated.
ROM is root, when I did a test with ONECLICK root, tools tells me that phone is root, so something are working just not my screen.
PS I cant remove battery, it is built into the phone
Basmand
UPDATE: HELP PLEASE
By a luck I was able to install a new ROM "ZTE-nubia-Z5-cm-10.2-20140115-" but be course I didn't have any picture on the screen I may have touch the phone, because the rom is booting up, but don't work probably due to uncompleted install. Now I have picture on the screen, I can go to recovery and bootloader mode, but still no picture on the screen in these 2 modes. I can use adb but not fastboot maybe driver issue, I have tried nearly every driver on the internet including SDK manager tool.
So is there any change that I can flash via adb mode?
Basmand
Click to expand...
Click to collapse
Solved this problem? If not, write to the Skype oleg_gutov. I can help you
olezhek1975 said:
Solved this problem? If not, write to the Skype oleg_gutov. I can help you
Click to expand...
Click to collapse
Hi
Thanks for offering your help, my phone is still bricked! I have searched on Skype and there are more than one person with the name oleg_gutov
My Skype name is Michael.jensen123
Basmand
Related
Hi.! Guys i really need help.! I Know There is a "NON - ZTE Blade" Thread in The ZTE Blade Forums for All The NON ZTE Devices (Obviously) But this need more Help than a Quick Reply and i Dont Know Where to put It.!
Well The Problem is.. i Got a ZTE Nubia Z5 ("2nd Hand") With a Software Camera Problem (I Think is a Software problems Because the Camera Works Sometimes), I Tried To Hard Reset the Phone But i Just Got a White Screen, And i Tried To enter in Recovery Mode And Get The Same White Screen (The Phone in ADB its Recognized as "NX501 Recovery" Normally is in "NX501 Device"), That means Something in The Recovery NAND or Something i Dont Know is Bad.!
(The Phone was Normally Working Fine, Since... My Brother Installed Chainfire 3D and is Stuck in the Boot Logo, Sounds Normal like is Entering in the OS (That music that sound when u Turn on a Phone) But Still Stuck on the Boot Logo, i Read is a Chainfire Problem in some Devices)
So I Start to try To Install Some Custom Recovery CWM, TWRP etc.! Was TOO HARD to find a Recovery Because ALL The Information you can find on the Internet about This Phone is in Chinese (i Dont know Chinese) And Some Russian Too (Dont know Russian to (lol))..
So i Found a TWRP Recovery (Also a CWM Too) But both in Chinse (I Dont care if is in Chinese).! So I Tried To Enter in Bootloader Mode To Install The Custom Recovery, Ok The Phone ENTERS in Bootloader (i Think so) The phone Gets on the Boot logo and get "Recognized" as a "Sooner ADB Device", but in ADB dont get Recognized, With ANY of the ADB Drivers, ADB Composite, ADB Interface etc.! So i Dont Know What to Do Now.! Looks Like the Bootloader is Blocked or Something.!
So i Hope Someone Here Can Help Me .!
(Sorry For my bad English) Cheers!
Seriously No One Here have a Clue.? Some Admin Can Move This to The More Appropiate Place.? :crying:
Bumb!
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:
While trying to set up a new boot animation, I came across an error which prevented my phone form booting up into the OS and instead showed me the Fastboot screen every time. I tried reflashing twrp, as well as flashing another boot animation into it. While reflashing TWRP for the third time (I didn't really know what to do so I just hoped it would work eventually), it seems like it corrupted some of my phone data, meaning preloader and I believe some other stuff. The phone now won't boot at all, and also isn't getting recognized by SPFlashTool. While plugging it into my PC I can still hear the "connected" and "disconnected" sound though.
Any ideas on what I could do?
I know its kinda late but
Have you tried using adb or fastboot and check if your device is recognized with the adb devices command?
noah_bfn said:
Have you tried using adb or fastboot and check if your device is recognized with the adb devices command?
Click to expand...
Click to collapse
I don't know how to do it But I'm having the same problem the screen is black , can you guys help me ?
Your phone sounds like it is soft bricked.
emersonsamuel said:
I don't know how to do it But I'm having the same problem the screen is black , can you guys help me ?
Click to expand...
Click to collapse
Your phone sounds as though it is soft bricked. It can be brought back to life.
Follow here to un-brick your device:
https://forum.xda-developers.com/android/general/ulefone-power-5-twrp-root-project-treble-t3943714
Loyal_Guardian said:
While trying to set up a new boot animation, I came across an error which prevented my phone form booting up into the OS and instead showed me the Fastboot screen every time. I tried reflashing twrp, as well as flashing another boot animation into it. While reflashing TWRP for the third time (I didn't really know what to do so I just hoped it would work eventually), it seems like it corrupted some of my phone data, meaning preloader and I believe some other stuff. The phone now won't boot at all, and also isn't getting recognized by SPFlashTool. While plugging it into my PC I can still hear the "connected" and "disconnected" sound though.
Any ideas on what I could do?
Click to expand...
Click to collapse
Just use the spflashtool. Try multiple times and try my updated guide. Make sure you installed the drivers properly AND USE A GOOD CABLE. I had some hard times flashing with spflashtool, but it was just the cable.
I'm in a bit of a pickle right here. My friend's P20 Lite got dropped and now the screen is dead. Backlight turns on, but the LCD is really, really broken. I can boot it up and unlock it using his swipe-code (by guessing where the dots are), but I cannot recover his data, because USB debugging is disabled
If I reboot into fastboot mode (Power + Vol Down), I can indeed see it on my PC as a fastboot device, but I can't use that for anything, as far as I know.
If I reboot into recovery mode (Power + Vol Up), adb doesn't work.
If I turn it on, unlock it, and plug in a Type-C to HDMI dongle (with power), it does not mirror the screen onto the display. I know the dongle works, as I've tested it with several devices.
HiSuite detects the device is in recovery mode, but then continues to say the device is not supported for system recovery.
What other options do I have? I can plug in a keyboard after it's unlocked, so maybe it's possible to navigate it that way? Like "press KEY to access settings, press down key 20 times, press enter to enter menu" etc. etc. Unfortunately I don't have a P20 spare laying around, so I can't use that for guidance.
The phone's bootloader is NOT unlocked, so I can't even flash TWRP and get into adb that way.
Hopefully someone can help!
Hi,
I sent you a private message.
I have the same problem. Any help, please?
-Alf- said:
Hi,
I sent you a private message.
Click to expand...
Click to collapse
Hi,
Cloud you maybe help me too? Because I have nearly the same problem. I have a Huawei P20 with a broken screen, the touch does not work and I have a password and therefore I cannot unlock it, I would like to be able to get all the data back from the phone and I have tried in many ways how to do it without being able to use it and the only solution is do it through a computer, I have already tried to activate usb debugging with a program, only it shows me the notification but I can not approve, I checked if there was active ADB but it says it is unauthorized and now I wonder if I should send the phone in recovery mode or fastboot mode so that I can control it from a pc or somehow receive the data, the question is how can I do? I have no idea how fastboot or recovery mode can be and whether it will make me lose everything or not so I would like to make sure by asking an expert, I would be very grateful if you could help me.
Hi.
Do anyone has a solution to this ? I'm in the exact same situation...
- normal mode no adb devices
- fastboot mode works, but... what to do in it ?
- recovery mode, no adb devices, nothing
- download Mode too, "adb devices" list it, but unauthorized... Maybe there is a way to copy a custom thing through SD ?
Need help please :'(
TurtleMaster said:
Maybe there is a way to copy a custom thing through SD ?
Click to expand...
Click to collapse
What do you mean by that?
-Alf- said:
What do you mean by that?
Click to expand...
Click to collapse
When is see on the internet what Download Mode is for, i imagine it's possible to copy a custom firmware/OS on the SD card, and then, install it automatically by this special mode.
I just want to retrieve my data... The only viable solution for the moment, is to buy a new P20 Lite screen and change it...
TurtleMaster said:
The only viable solution for the moment, is to buy a new P20 Lite screen and change it...
Click to expand...
Click to collapse
Exactly.
I would recommend this guide:
https://www.ifixit.com/Guide/Huawei+P20+Lite+Screen+++Frame++Replacement/119776
I accidentally flashed the wrong logo.img and now my phone does not boot anymore, its just a black screen
idk if there is a way to write the phone without booting it, if someone got an idea what I could do, please help me :'(
GiantMurloc said:
I accidentally flashed the wrong logo.img and now my phone does not boot anymore, its just a black screen
idk if there is a way to write the phone without booting it, if someone got an idea what I could do, please help me :'(
Click to expand...
Click to collapse
can you boot into fast boot mode
muneeb rizwan said:
can you boot into fast boot mode
Click to expand...
Click to collapse
nope, the screen stays black and it doesn't even vibrate anymore
GiantMurloc said:
nope, the screen stays black and it doesn't even vibrate anymore
Click to expand...
Click to collapse
does your computer detects it
muneeb rizwan said:
does your computer detects it
Click to expand...
Click to collapse
the device list in linux stays the same when i plug or unplug it, so I think its not detected by the pc
It would be better if you told us exactly what you did. Step by step. Then we can more easily assess how serious the error may have been.
StaryMuz said:
It would be better if you told us exactly what you did. Step by step. Then we can more easily assess how serious the error may have been.
Click to expand...
Click to collapse
so, I broke my system img today, the phone was in a bootloop and I downloaded the system img and boot img from c.mi.com, then I found out that there is actually a logo.img for the splashscreen and tried to create my own, I thought it would be alright if I flash it and I could get back to fastboot if its not working. well seems like that was wrong, now the phone is not booting anymore :'(
I there any way to the phone before it tried to start the logo.img?
On my old lenovo tablet there was a software called mtk tool that was able to flash the device before it starts anything
so I found out that I could try to boot my phone into the edl mode, so I can flash it with mi flash tool, but I would need to remove the phone cover for that, so it would be my last option, any other idea?
The question is whether the phone doesn't actually report anything when connected to a PC. In Windows detection is easy, how it is verifiable in Linux I have no idea. The phone can report to different kinds of drivers, including the COM port. EDL mode can be triggered by test points from the phone's motherboard, but sometimes also by button combinations. I don't know of a suitable button combination yet, but it is used from the off state of the phone when the phone is connected to a PC.
As for the tablet connection you mentioned, it was definitely an MTK CPU and it has different procedures to upload than Qualcomm. With us, you have to connect the phone first.
So I tried it on my windows and it also didn't show up in device manager. Anyway I will buy a phone repair kid and try to fix it in the EDL mode, thank you ^^