Hello to all.
My first post was about One mini with unlocked bootloader and failed system. Situation changed so I describe all "story" wondering that sb clever would tell me what to do now...
At the beginning, I visited some "specialist", who applied me a fantasy about bootloader rebuilding and took cash for nothing. Because thay said that tried to flash European ROM on device bought in USA with ATT brand and S ON (look attach) I had to learn a little to do anything by myself.
First of all I flashed TWRP Recovery using AllinOne. First CMD window replied "device not found" but second one responded that Recovery was flashed succesfully. In fact TWRP run. And it was all.
Than I tried to do anything by ADB. Drivers were installed correctly but any command form adb responded "device not found"
Device manager showed QHSUSB DLOAD when connected not powered one mini. (Yes I know what it means)
Sideload in TWRP was not working too.
Flashing wih USB OTG mounted under TWRP was not working too.
Newest RUU_M4_UL_K44_SENSE60_MR_Cingular_US_4.13.502.3_ from htc site (.htc.com / us / support / htc-one-mini-att / news / ) was showing connection error at the beginngin but was detecting system version and suggested update. Always failed after reboot.
Today I tried to flash RUU.zip (ver same as installed on my bricked one mini). AllinOne asked about Bootloader lock so I relocked bootloader. Flashing failed so I started mentioned newest original RUU from HTC. Bootloader was rebooted and procedure started. (with unlocked bootloader it failed at this moment) Unfortunaelly it stopped at 95% with comunicate "signature error".
Cell restarted, htc logo appeared ("by android" sign was added) and device manager detected HTC device and mass memory. Unfortunetelly system havent boot up and now manager shows only "not recognized device" but QHSUSB DLOAD not appeared again
What would you advice to do now? Try to update again? When you check Fastboot reply at CMD screenshot than it seems to be ALMOST updated. But still sth is wrong
I read RUU log and edited fonts colour to make it more readable.
I can see that all time ADB has a problem with "adb devices" command and it asks fastboot (i coloured it on pink).
Later it flash two almost 400MB each zip files but after second one gives signature fail. If Update comes from HTC and almost all update was correct what may it mean now?
I attach
1 image with bootloader details when bought broken
2 image of ADB fastboot report after 95% Update to 4.13.502
3 log from Updater
Related
I would have put this in development but I don't have permission yet.
Situation:
I'm using a Chinese tf300t
I tried to root my tablet using the cwm all firmware compatible method. you can find it on youtube as i am not yet allowed to post outside links.
unlocked my tablet. downloaded sdk and all the applications necessary. followed their directions to the letter. I go to cmd to put in the code and when I hit enter after typing: fastboot -i 0x0blah... i get: "waiting on device"
What I think the problem is:
with the sdk fastboot my computer never makes the usb found sound so i thought maybe something with the fastboot driver might be causing a problem so i looked online and someone with the same problem found that a different version of fastboot fixed his waiting problem. I tried what worked for him and now I get a weird stutter version of the usb found sound and i still get a waiting message when i enter the code in cmd. so i think that there might be a problem with the drivers, but my tablet works fine with my comp when its booted up normally.
good news is that I have always been able to reboot device and run normally.
Anybody got any sugestions?
i would like to suggest you to copy these files: fastboot + cwr into 1 new folder, then run fastboot again ( do this while your device is showing ""waiting on device", don't need to reboot it)
Hi everybody, i am really sorry about my english i hope you guys can understand what i am trying to say.
a few mounths ago i rooted my Htc one m8 using the AIO toolkit. I flashed it with the TWRP 2.7.0.2 recovery.
Last week i wanted to update my Htc and found a guide how to update but i messed up. It said something like that I have to remove the root then install a file they had on their site on my phone.( I can't say which guide it was because i don't have the pc i used last week to do this.)
After i did that my Htc got stuck in a bootloop- I can access the Fastboot menu but when i choose Recovery or Factory reset option my phone just reboots but doesnt get past the HTC logo.
I am trying fixing it with the AIO toolkit but an error message shows up saying "device not found" or
"waiting for device" my pc is on windows vista an recognizes my phone- I installed the right drivers and on the fastboot menu it says "fastboot usb" highlighted in red.
I am a really noob at this so have you guys any idea how I can fix this? Why do i get the message "device not found" , when my pc recognized my phone and all the drivers are installed?
And also my pc is in safe mod with network because i get a blue screen when booting the normal way-
Do you think thats why i get the error message " device not found"?
AL10 was flashed to kangvip b170 L29 eu. All fine few month but emergency calls for my region (UA) not work properly (call to police and listen fire dept answer). I think that problem was in location and try to flash from TWRP ru location file. But after this i see next problems:
- changes ROM ver from b170 to b152 (NXT-C900B152) //only locale file was flashed//
- cant boot now to TWRP (was 3.0.2)
- during boot red letters warning "your device has failed verification and may not work properly"
- when i try to run italian knife (sometime earlier i fix this problem with it) - it looong booting (yellow letters WAIT), and as i detect problem: "device is unauthorised" (see after run a cmd <<adb devices>>). So problem is dual :
1) on phone - i see red letters during booting "your device has failed verification and may not work properly"
2) on PC - device is unauthorised (earlier all was fine), i try to reinstall adb, nothing changed. I try to delete adb keys with their folders, on/off USB debugging switch...
Phone is unlocked and rooted, bootloader shows "phone unlocked".
Trying flash firmware using sdcard upgrade, flash stock recovery but device is rebooting and stops - because probably link path to recovery is broken. Few tools i try stops on <<waiting device>> because dev is unauthorised and i cant receive authorisation by on/off USB debugging
How fix this problems ?
SOLVED BY UPDATING FROM SD CARD TO NEW FIRMWARE, AND NORMAL ASKING FOR RSA KEY I RECEIVED AT LAST !!!
Hello
As you can see i'm new here, so hello to you all.
I have the following problem with my Oneplus One.
In the past i rooted my phone, put on TWRP and flashed a Rom on it.
Yesterday i wanted to install another Rom on my device so i did what i normally do, put on a Rom, deleted everything (also data) and flashed it. But the phone always gave the same error with different roms, my phones name was not mentioned.
I looked it up and i thougth i found a sollution, my TWRP version was out of date (it was stil version 2.8.7.0). So i wanted to update it using TWRP. I put on the TWRP version 3.3.1.0 image on the phone and flashed it. It said the flash was succesfull and completed. I shut down the phone and restarted it to enter the new TWRP version.
Problem is, the phone did not start up, i only get the Oneplus One logo.
If i connect the phone to my pc (windows 10) my computer doesn't recognize my phone. It is not in the my pc list. I can see it in the devices in configuration as an uknown device (android).
I searched over the entire internet (or just a very small part of it ) and found that i should upgrade my android usb drivers. I downloaded them, but the computer says i already have the latest drivers.
I think i might flashed a wrong version of TWRP on my phone and that's why it's stuck.
I can start it up in fastboot mode. I think, so, i can see the fastboot mode logo but it is not so bright.
Then i tried to enter my phone with ADB through command prompt.
So i got the ADB files (platform tools), put them in a folder under C:, added them to the environmental variables path and restarted my computer.
But if i want to use a command with ADB, i get the error that "program 'adb' failed to run : there is no application linked to the given up file for this operation. (i had to translate it, because on my pc it's mensioned in Dutch).
So the problem is that my pc doesn't recognise my phone, or not correct so i can't enter it and there is a problem with the ADB.
I'm not that smart in all this stuff and all my info and actions come from the world wide web. It's not my primary phone so i don't mind experimenting with it.
Anybody that can help me?
Sorry if my English is not that well written.
If you need additinal info, shoot.
Thanks in advance
Hello, I am new here!
I have a problem with my P20. Yesterday I tried downgrading with HiSuite Proxy from Emui 9.1 to 8.1. The update went well, the emui loading circle with percentage appeared on the phone, then at 80 percent there appeared an error on the screen that the update has failed and I should either enter recovery or reboot. I clicked on reboot (I am dumb, I know) and since then the phone is showing a black screen and I cannot do anything. The phone is in Fastboot and it responds to fastboot commands from adb tools.
I think the problem is, that in Hisuite proxy I selected "normal update" instead of "rollback". That made Hisuite perform an update over a newer version of emui.
In the beginning, the phone was recognised by windows as "Andoid device" with a subname "HI3650". After switching drivers in device-manager, I got "ADB device" there.
What I tried so far:
- switching ADB drivers in device manager in windows
- system recovery in Hisuite. It fails, tried with several HiSuite versions so far.
- "fastboot flashing unlock" (most fastboot commands return errors like "FAILED (remote: check password failed!)" or "FAILED (remote: Command not allowed)"
I am not a pro with these things but understood that I could flash a recovery image with fastboot. Someone on this forum said something about .pac images which could be flashed even with a locked bootloader, mine is locked. Could somebody with good knowledge help me out? I did plenty of google searching before and also browsed through this forum, i did not find a solution, at least not with locked bootloader.
I would appreciate any help to save the phone before having to trash it!
Servus2403 said:
Hello, I am new here!
I have a problem with my P20. Yesterday I tried downgrading with HiSuite Proxy from Emui 9.1 to 8.1. The update went well, the emui loading circle with percentage appeared on the phone, then at 80 percent there appeared an error on the screen that the update has failed and I should either enter recovery or reboot. I clicked on reboot (I am dumb, I know) and since then the phone is showing a black screen and I cannot do anything. The phone is in Fastboot and it responds to fastboot commands from adb tools.
I think the problem is, that in Hisuite proxy I selected "normal update" instead of "rollback". That made Hisuite perform an update over a newer version of emui.
In the beginning, the phone was recognised by windows as "Andoid device" with a subname "HI3650". After switching drivers in device-manager, I got "ADB device" there.
What I tried so far:
- switching ADB drivers in device manager in windows
- system recovery in Hisuite. It fails, tried with several HiSuite versions so far.
- "fastboot flashing unlock" (most fastboot commands return errors like "FAILED (remote: check password failed!)" or "FAILED (remote: Command not allowed)"
I am not a pro with these things but understood that I could flash a recovery image with fastboot. Someone on this forum said something about .pac images which could be flashed even with a locked bootloader, mine is locked. Could somebody with good knowledge help me out? I did plenty of google searching before and also browsed through this forum, i did not find a solution, at least not with locked bootloader.
I would appreciate any help to save the phone before having to trash it!
Click to expand...
Click to collapse
Hello there! I can help you with this since I got exact same problem. Do you have any messaging app? add me on telegram t.me/dexxik or discord Dexxo#0295 if you want quicker response.
First of all, you f*cked up. I can help you recover your phone but you won't be able to use that phone for calling/messaging again.