I am trying recovery,but every time when i write fastboot oem unlock i gives me back with a message "waiting for devices",and just holds there....what should i do to make recovery....Thanks in fowards...
mimi12 said:
I am trying recovery,but every time when i write fastboot oem unlock i gives me back with a message "waiting for devices",and just holds there....what should i do to make recovery....Thanks in fowards...
Click to expand...
Click to collapse
Are you following any of the guides in the Development section?
Are you Mac or Windows or Linux?
Your post is a little hard to understand, but I think you're trying to push the clockwork recovery to your phone, is that correct, or are you just trying to get into normal recovery?
Assuming you're on the white screen that says fastboot mode at the top of it, then your problem is that you don't have the proper drivers on your computer to talk to the phone. You need to install the drivers from the SDK (or if on Windows you can use PDANet).
The best guide on there, AllGamer's, has full instructions on how to get the phone and the computer talking to each other properly.
May I ask why you want to oem unlock the phone? You're aware it's not necessary to do this to root the phone or flash clockwork recovery or even flash custom roms? There's nothing wrong with running unlocked (I do), but just be aware that the fastboot oem unlock command will totally WIPE ALL DATA off your phone, including your pics and music off the USB storage area.
My guide to rooting has you skip the oem unlock, but you can follow any guide and just skip that step to avoid wiping your phone.
Sorry for the short post.I run on Windows,i dont know what is clockwork recovery,i read something about it,but i didnt understand,i think that i need normal recovery.I installed sdk on my computer and i go to load drivers(browse....etc)and it cant "find" drivers,i installed pdanet also and i get the same message "waiting for devices",i installed some application and it started to freeze every 5-10min,i dont have that much data on him self,so its ok if recovery wipe all data,i will try that guides and will get back to you how it went,btw THANKS for everything....
This thread might help you out as well. http://forum.xda-developers.com/showthread.php?t=878786
Thank you for everything,i did it,i wipe out everything and now is working like new.......i had troubles with installing adb and fastboot drivers,but i managed to figure it out,and everything went smooth))One again thank you very,very,very,very,very,very,very,very,very,very much....
P.S -sorry if my english is bad...
Related
Hi Guys, since monday im the owner of a htc one s. I unlocked the booloader and flashed the team win recovery. Then I flashed the TrickDroid Custom Rom, because I thought i would have a nice battery life like it was told in the title. But the fact is that my One S looses extremly much battery in standby-mode and i dont know why. So i would flash a RUU. But I couldnt do this. Like in some Threads i flashed the Stock-Recovery and the I relocked the bootloader. Now I tried to start my phone to flash the RUU but i coulndt, the One S wasnt booting. Then I tried to flash the Recovery over the Bootloader and ive got the failure-code 171 (ruu cant find a fastboot device -> usb). But i realy want to go back to stock. Can you help me?
iZodiac
never done an ruu, so can't help much there other than what is already posted
assuming you are up on your adb/fastboot stuff, try reinstalling the htc drivers. then open command window, cd to fastboot.exe folder, usually in something like tools or platform-tools and at command prompt type fastboot devices and see if phone is recognized.
And thats the Point, if I install Android SDK my CMD Console says me, that I cant open this and then my cmd isnt available anymore on my pc. i tried this 2 times and every time I needed to restore my pc to a earlier time..
not sure
can you reinstall htc sync or try new usb or different pc port
you need the fastboot.exe and adb.exe and 2 windll files in your tools folder. If they are missing--might be issue
did you check and see on phone if usb debugging is checked under Settings/Development and fastboot is unchecked under Settings/Power
oh, if you haven't and get to a point you can, get a nandroid. i know you can't bu sdcard to pc--but, first chance you get, do it
Thanks first for your Support, 2nd
Can you give me a link of the (if available) latest RUU-Nandroid? Would be great if you'll find something
Hello xda,
a friend of mine just gave me his HTC Sensation because it isnt running quite a while. The problem is that i haven't had a HTC device ever and I don't really know what to do and what information you need to help me so I'd be happy if u just tell me what information you need and I will try to get them for you.
The Information I got so far is:
- if I want to boot it, it stays at the HTC Logo
- CWM starts with some errors but you can't perform a wipe (just turns off)
- Bootloader starts as well but you can't perform wipe either, nor flash new CWM
- If i connect it with the computer while in fastboot it changes to "fastboot usb" but adb cannot find the device, though i installed first the drivers, lateron htc sync. Windows just calls it "myhtc"
bootloader says:
"PYRAMID PVT SHIP S-OFF RL
HBOOT . 1.27.1100
RADIO - 11.22.3594.07_M
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
Jan 13 2012, 17:33:34"
So what should I try to do or what information will you need.
I would be very happy if u can help me
fnstGoliath said:
Hello xda,
a friend of mine just gave me his HTC Sensation because it isnt running quite a while. The problem is that i haven't had a HTC device ever and I don't really know what to do and what information you need to help me so I'd be happy if u just tell me what information you need and I will try to get them for you.
The Information I got so far is:
- if I want to boot it, it stays at the HTC Logo
- CWM starts with some errors but you can't perform a wipe (just turns off)
- Bootloader starts as well but you can't perform wipe either, nor flash new CWM
- If i connect it with the computer while in fastboot it changes to "fastboot usb" but adb cannot find the device, though i installed first the drivers, lateron htc sync. Windows just calls it "myhtc"
bootloader says:
"PYRAMID PVT SHIP S-OFF RL
HBOOT . 1.27.1100
RADIO - 11.22.3594.07_M
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
Jan 13 2012, 17:33:34"
So what should I try to do or what information will you need.
I would be very happy if u can help me
Click to expand...
Click to collapse
Hi,
Go HERE
Install 4 EXT recovery,using one of the 3 methods available.(probably third)
Then,try to install ARHD ROM.(same guide)
No need to change the firmware.
So I just tried to flash 4 EXT Recovery but it doesn't work..
It finds the zip, ask me whether i want to start the update, i press vol up and "Update is in progres.." appears but nothing more, I'm waiting since 5 minutes and will probably have to power off the phone now.. the same happened when i tried to install cwm so theres something wrong with the bootloader?
What can I do now?
fnstGoliath said:
So I just tried to flash 4 EXT Recovery but it doesn't work..
It finds the zip, ask me whether i want to start the update, i press vol up and "Update is in progres.." appears but nothing more, I'm waiting since 5 minutes and will probably have to power off the phone now.. the same happened when i tried to install cwm so theres something wrong with the bootloader?
What can I do now?
Click to expand...
Click to collapse
Hi,
Maybe you should run a RUU.
Look HERE
I also thought about this but as I said adb doesn't find the device.
Since I never ran a RUU, can I still flash or do I have to get adb to run with the device.
Anyway, I cannot read out the CID of the device so if it is possible, which RUU should I flash?
Thanks for your help
fnstGoliath said:
I also thought about this but as I said adb doesn't find the device.
Since I never ran a RUU, can I still flash or do I have to get adb to run with the device.
Anyway, I cannot read out the CID of the device so if it is possible, which RUU should I flash?
Thanks for your help
Click to expand...
Click to collapse
Hi,
Try installing these windows 7 & 8 drivers (assuming you have a windows 7 or 8 machine)
Reboot your PC and see if your phone is recognized in ADB.
You are s-off,so you do not have to match it 100%
Just get a RUU that is close to your region or carrier.
If you get the wrong one,it is not a problem.
It will just give you an error.
Then,just try another.
)
Well I just installed those drivers but same result as before..
Windows says "MyHTC" and after i write "adb devices" into the cmd window it says "daemon not running. starting it on port 5037. daemon started succesfully. List of devices attached." and the next time i write adb devices it just says "List of devices attached".
Bootloader still says Fastboot USB.
So maybe there's something wrong with my adb?
Well can i flash RUU without adb finding my device or cant I?
fnstGoliath said:
Well I just installed those drivers but same result as before..
Windows says "MyHTC" and after i write "adb devices" into the cmd window it says "daemon not running. starting it on port 5037. daemon started succesfully. List of devices attached." and the next time i write adb devices it just says "List of devices attached".
Bootloader still says Fastboot USB.
So maybe there's something wrong with my adb?
Well can i flash RUU without adb finding my device or cant I?
Click to expand...
Click to collapse
Hi,
Not sure what is happening with your ADB.
Look HERE for help.
In order to run a RUU ,you need to put the bootloader into fastboot,and plug in the USB.
It should show what yours is showing.
So, it should work.
After "List of devices attached" there is no device shown, I didn't leave anything adb shows, so this is still right? Usually it always shows my device ^^
So my adb is probably not running right or it is about my phone
So my next step should be adb showing my device and therefore reinstall android sdk, java, stuff until it might show the phone
or just do something with the phone?
I still think that i cannot run a ruu without any device shown? Didnt really get an answer on this question I guess or I didnt realize it
fnstGoliath said:
After "List of devices attached" there is no device shown, I didn't leave anything adb shows, so this is still right? Usually it always shows my device ^^
So my adb is probably not running right or it is about my phone
So my next step should be adb showing my device and therefore reinstall android sdk, java, stuff until it might show the phone
or just do something with the phone?
I still think that i cannot run a ruu without any device shown? Didnt really get an answer on this question I guess or I didnt realize it
Click to expand...
Click to collapse
Hi,
Just run the RUU.
It will only show error if it does not work.
No big deal,and no damage done.
Just try another one.
if you enable usb debugging might help too
Well.. I just started "RUU_Pyramid_HTC_Europe_1.50.401.1_Radio_10.56.9035.00U_10.14.9035.01_M_release_223042_signed" and everything went fine until installation, no errors at all. Now the installer is stuck at "restarting bootloader" (or something equal, the installation is german) and the phone didnt do anything at all. It's now 15 minutes since the installation started so I probably will try another one but isn't it weird that ther is no error at all?
What should I do if the next RUU does exactly the same?
*edit:
just seeing page 2. How should I enable usb debugging without booting the phone?
*edit2:
second RUU: Same thing, no error but it didnt go further then "Restarting bootloader".
What to do now?
Any further Ideas what I could try?
Puuuush
fnstGoliath said:
Any further Ideas what I could try?
Puuuush
Click to expand...
Click to collapse
Put phone into bootloader then connect to pc and run the RUU
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
The phone was in fastboot usb while running the ruu for sure ..
fnstGoliath said:
The phone was in fastboot usb while running the ruu for sure ..
Click to expand...
Click to collapse
Hi,
Try running a RUU with the same radio (11.22) that you have installed.
You will not damage the phone.
It is not always an exact science with RUU.
Sometimes it is just trial and error.
So it is often that there is no error at all?
I just thought flashing wrong RUU will cause an error and not stopping at restarting bootloader. And anyway the bootloader seems pretty broken since it is not flashing anything at all ^^
Still i gonna try it
fnstGoliath said:
So it is often that there is no error at all?
I just thought flashing wrong RUU will cause an error and not stopping at restarting bootloader. And anyway the bootloader seems pretty broken since it is not flashing anything at all ^^
Still i gonna try it
Click to expand...
Click to collapse
Hi,
Probably ,the only thing that will fix your problem is a RUU.
So,keep trying different ones until it works.
I finally managed to find the phone via adb! I think that's a great step.
The biggest problem is that I lose any contact to the phone when i reboot it into bootloader.
I can just boot the phone into recovery and use any other adb function but as soon as I boot it into bootloader I can't do anything anymore.
That's why I cannot use any fastboot commands to flash a zip, neither run a RUU completely i guess.
So I think that i need any rom to either flash via recovery or just via PC not using fastboot/bootloader at all.
Are there any possibilities for me now?
fnstGoliath said:
I finally managed to find the phone via adb! I think that's a great step.
The biggest problem is that I lose any contact to the phone when i reboot it into bootloader.
I can just boot the phone into recovery and use any other adb function but as soon as I boot it into bootloader I can't do anything anymore.
That's why I cannot use any fastboot commands to flash a zip, neither run a RUU completely i guess.
So I think that i need any rom to either flash via recovery or just via PC not using fastboot/bootloader at all.
Are there any possibilities for me now?
Click to expand...
Click to collapse
Hi,
Plug your phone into the PC.
Go to device manager,and where it says MyHTC,right click and update driver.
Browse to the windows 7 & 8 drivers I gave you earlier.
Update,unplug phone ,and reboot PC.
Get a RUU that shows 3.32 or 3.33 in the title,and matches your region
Pull your battery.
Put it back in,and hold volume down and power button together.
Scroll to fastboot.
Plug in usb and run RUU from the PC
Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max
Use this guide to recover your device.
Thanks, but my issue is that I can't install the drivers, could it be a windows 8 thing?
Everything seems to require that I enter USB debugging first, which is impossible for me now.
I think the ADB driver is impossible to install, unless I can do it over CWM, and every fastboot driver I've tried has failed too.
How did you erase everything? Was it through fastboot or CWM?
I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.
maxmalynowsky said:
I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.
Click to expand...
Click to collapse
In my opinion, its safer to erase everything from fastboot.
If fastboot recognizes your phone, then you can erase or install whatever you want.
If fastboot does not recognize your phone, then you can't erase it. You then need to find out why. Bad drivers, wrong folders, bad usb cable...In the meantime you phone will still work.
On my windows 7 box, under the administrator account, it took a while to set up the drivers, don't know why, but windows would not take it at first.
Maybe you can mail the phone to a xda member to get it going again...
maxmalynowsky said:
Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max
Click to expand...
Click to collapse
I am sorry to hear about your phone. You are not alone I did the exact same thing a few days ago. Don't beat yourself up I have done that enough for both of us. Through my research into this i found there a few things that you might try (I don't own a PC so I haven't yet)
To get the drivers, I read a couple people had success downloading PDANet and installing them that way. I think they are located in "legacy drivers"
From the original "root, un-root" thread for your model download the stock boot img and try to flash that using ADB
follow the instructions to un-root and start over with rooting.
I also was going to look into Wug's toolkit (in the dev section) it looks like that may be an easy option to flash a working boot and recovery img.
I hope this helps please let me know.
I gave up to quick and ordered a GNex but I'm not touching that until I get my NS4G sorted out (my faith in my abilities is shaken and I could not handle bricking a brand new phone). I will be going to a friends house tonight to use their PC and try to get my NS running. I will be back to let you known what works and what doesn't. If you try or find anything would you please post? Two heads working on this issue are better then one. Thanks and good luck.
Sent from my temp PC36100 while my Nexus is sick using Tapatalk 2
*** success ***
The solution was an easy one thanks to our developers, the hard part was finding the answer and of course, beating myself up for making the mistake in the first place. Here's what you do...
Leave your phone with the battery out for a while. Download "Wug's Nexus Toolkit" In found it in the NS4G dev section but I believe it covers all variants (not sure which you have) at the select your model and custom JB ROM download the drivers (from the actual toolkit) turn on, plug in and select flash stock img, relock boot loader, pick the stock ROM you want and press go and your phone will be flashed and reboot in under a minute. Sign in on your phone (the toolkit should auto populate your new ROM and then just follow the steps to unlock, flash and install a custom recovery then pick any ROM you want and start over.
I really hope this helps you as I'm sure you find the whole situation as stomach-churning as I did. Please PM me and let me know.
If it does work please leave a thank you or donation to the dev for creating such an awesome tool. Again, good luck hope you get your nex back online.
Sent from my Galaxy Nexus using Tapatalk 2
The Nexus Toolkit was actually my first option, it's helped me out before. I went back and tried installing the drivers using the 3 options it gives. # 3 & #2, RAW and Samsung signed drivers don't work. Option #1, the PDAnet drivers didn't work last time I tried it (all 3 options require USB debugging enabled). However, I just tried #1 again by turning on the device in CWM and that seemed to work, but I'm not sure (installation went according to the guide). However, once I tried to flash stock img, it gave me errors about not being able to reach the device in fastboot. Can you elaborate on those two steps, driver installation and flashing? As soon as I can get fastboot to recognize my device I can pretty much take it from there. BTW, I've got a i9020A and using NRT 1.6.1; and what's the significance of leaving the phone with the battery out for a while?
Mine was in the box with the battery out overnight. When I had access to a PC and plugged it in it said something at the bottom of the fastboot screen in grey that it did not before and I actually think that was the trick (System normal or system OK or something like that and when replugged to the USB the message just repeated and stacked up on the lower left of the fastboot screen). Try letting the phone sit for a while. All driver options failed for me except the tool kit.
Sent from my Galaxy Nexus using Tapatalk 2
Tried your fix, but the phone remains unable to have it's drivers installed. It's always giving "USB device not recognized" errors no matter what I do. I'm just going to shelf it and accept my loss. Thanks for the help though!
edit: Tried using some Linux tools, much greater success! This guide finally got my device listed under fastboot: http://forum.xda-developers.com/showthread.php?t=1447040
edit2: Up and running again with the android-tools-fastboot package for Linux and a standard stock image flash: http://forum.xda-developers.com/showthread.php?t=1572307
I am so glad to hear it! I stayed subscribed to the nexus s forum just to keep up on your progress and to try and help. Good for you.
Sent from my Galaxy Nexus using Tapatalk 2
Hi guys
Desire S.
Unrooted, no custom recovery, basically everything default.
HBoot 2.00.0002
.
To root, i need the 0.98 version.
Using HTCdev.com, i tried to unlock, but at step 5, where i should type fastboot oem get_identifier_token, the phone doesnt come up at all, and cmd just continues to wait for device.
Before you ask, I HAVE (i hope) followed all steps.
This includes updating drivers manually, using htc sync (latest and older versions), swapping usb port and cable, reunzipping adb and fastboot material from other sources, and reading for a decent number of hours throughout xda and other external forums and guides.
But there is still no success.
Anyone help please? I don't just want fast, "get it working for me" type answers, but actually want to know why it refuses to greet me!
Cheers
BTW, i'm on a windows 8.1 laptop, and have updated the relevant drivers, still to no avail.
InV15iblefrog said:
Hi guys
Desire S.
Unrooted, no custom recovery, basically everything default.
HBoot 2.00.0002
.
To root, i need the 0.98 version.
Using HTCdev.com, i tried to unlock, but at step 5, where i should type fastboot oem get_identifier_token, the phone doesnt come up at all, and cmd just continues to wait for device.
Before you ask, I HAVE (i hope) followed all steps.
This includes updating drivers manually, using htc sync (latest and older versions), swapping usb port and cable, reunzipping adb and fastboot material from other sources, and reading for a decent number of hours throughout xda and other external forums and guides.
But there is still no success.
Anyone help please? I don't just want fast, "get it working for me" type answers, but actually want to know why it refuses to greet me!
Cheers
BTW, i'm on a windows 8.1 laptop, and have updated the relevant drivers, still to no avail.
Click to expand...
Click to collapse
your phone must be in FASTBOOT bootloader mode..not in the HOME of your ROM..
if you don't wan to turn off your phone first and pressing volume down + power to go to bootloader..then you can using a adb command on cmd while your phone is still in the HOME of your ROM.. type "adb reboot bootloader" then select "FASTBOOT" now you can type "fastboot oem get_identifier_token"
don't forget to disabled Fast boot mode and enable USB Debuging first from the system settings and just connect your phone to pc as charge mode..
hope this help..
Sorry mate. Tried that before your post though.
However the person for whom I was doing this no longer needs it doing, and plans for a newer device, so I no longer have this device available. Thus, i thanked you, since it was a cue for me to mention that.
Cheers.
This model of HTC is died
So far I always found answers to all my questions here without ever asking. This forum is awsome! Thanks to everyone here doing good work!
My problem: I have the European version of the Honor View 10. I opened bootloader, I installed the Magisk correctly with the 15.4 version, worked all fine. (thank you topjohnwu)
Then MY mistake ... I wanted to install Xposed Installer. I was not concentrated that moment and took the wrong version! From my other Honor phone (android 6.0, version 89, arm64). Absolutely stupid!
Phone restarted ... bootloop ... and goes into eRecovery. I tried everything I could there, clear dalvik cache, factory reset. > no change!
Then I thought ok, connect to PC, safe mode ... adb ... but no success. adb devices brings no result. PC does not find my phone anymore. I hoped I could get into my phone by connecting with PC, but it seems I am unable. So I can not help myself this way.
Next try was to force the phone to update with SD card. I only found asian update software, but I already did not care. I want to save my phone. Update starts, but after 5% it stops, update fail.
Now I hope that someone here can help. I have no idea what else I could do. Best regards, Markus
mark_at said:
So far I always found answers to all my questions here without ever asking. This forum is awsome! Thanks to everyone here doing good work!
My problem: I have the European version of the Honor View 10. I opened bootloader, I installed the Magisk correctly with the 15.4 version, worked all fine. (thank you topjohnwu)
Then MY mistake ... I wanted to install Xposed Installer. I was not concentrated that moment and took the wrong version! From my other Honor phone (android 6.0, version 89, arm64). Absolutely stupid!
Phone restarted ... bootloop ... and goes into eRecovery. I tried everything I could there, clear dalvik cache, factory reset. > no change!
Then I thought ok, connect to PC, safe mode ... adb ... but no success. adb devices brings no result. PC does not find my phone anymore. I hoped I could get into my phone by connecting with PC, but it seems I am unable. So I can not help myself this way.
Next try was to force the phone to update with SD card. I only found asian update software, but I already did not care. I want to save my phone. Update starts, but after 5% it stops, update fail.
Now I hope that someone here can help. I have no idea what else I could do. Best regards, Markus
Click to expand...
Click to collapse
Did you already try ro flash ramdisk and system sith stock images via fastboot?
alohahe3000 said:
Did you already try ro flash ramdisk and system sith stock images via fastboot?
Click to expand...
Click to collapse
I would flash anything ... if I could! That is my problem at the moment and I can not solve it.
When I start phone I get into Huawei eRecovery after two tries to boot > does not help!
When I connect to PC > phone gets not detected! (during boot try it gets connected shortly ... but then gets disconnected after some seconds, in between I can not get into phone via PC)
So when I would want to use fastboot .... not possible because of that issue. I tried to connect in fastboot mode ... but no difference. Actually I do not understand why I can not connect to PC anymore!
The only way I can imagine now is flash or update something via SD card. I tried with asian update.zip, but it will only go to 5% .... and then ends.
But to be honest ... I am not very optimistic about finding any solution. I think only some very smart pro from this site might have an idea. But not sure if these guys read questions about bootloops.
mark_at said:
Next try was to force the phone to update with SD card.
Click to expand...
Click to collapse
Try to flash via Fastboot the stock rom... do a full wipe and reboot.
here the link to the stock ROM:
https://mega.nz/#!W9hjiTgZ!_ZGq7V83bkWPF_Ue7_c41wVXNrQ_YjnsQUxRS0_MevU
Taobaibai said:
Try to flash via Fastboot the stock rom... do a full wipe and reboot.
Click to expand...
Click to collapse
Thanks for the link. But how can I flash via fastboot when my phone is not detected from the PC? That is my main problem at the moment!
That is why I wrote about all things I had tried already. And being unable to connect to the computer is really worrying me!
"adb devices" will not find my phone!
mark_at said:
Thanks for the link. But how can I flash via fastboot when my phone is not detected from the PC? That is my main problem at the moment!
That is why I wrote about all things I had tried already. And being unable to connect to the computer is really worrying me!
"adb devices" will not find my phone!
Click to expand...
Click to collapse
You have to boot into fastboot modus. When booting, push power and Volume down button. A white screen appears if device is connected with PC.
Then try "fastboot devices". If your device is displayed, you can flash with "fastboot flash" system image. Stock system.img download link can be found in AOSP thread, second post.
alohahe3000 said:
You have to boot into fastboot modus. When booting, push power and Volume down button. A white screen appears if device is connected with PC.
Then try "fastboot devices". If your device is displayed, you can flash with "fastboot flash" system image.
Click to expand...
Click to collapse
Exactly
alohahe3000 said:
Stock system.img download link can be found in AOSP thread, second post.
Click to expand...
Click to collapse
Or just use my link. I copied it from the AOSP Thread
I managed to get my phone displayed when I entered fastboot devices.
And I managed to flash the img!! Hurra !!
Thank you very very much to everyone here helping me ...
I thought that nothing would work because when I typed "abd devices" nothing happened. But when I typed "fastboot devices" the phone was there.
mark_at said:
I managed to get my phone displayed when I entered fastboot devices.
And I managed to flash the img!! Hurra !!
Thank you very very much to everyone here helping me ...
I thought that nothing would work because when I typed "abd devices" nothing happened. But when I typed "fastboot devices" the phone was there.
Click to expand...
Click to collapse
It wasn't so difficult.
Viel Spaß mit dem Smartphone!!!
one more thing I have to add:
after flashing the system.img from the link above .... I have FRP lock .... that was not before.
does it mean I have to relock my bootloader and then unlock it once again? In some other thread I found that information.
mark_at said:
one more thing I have to add:
after flashing the system.img from the link above .... I have FRP lock .... that was not before.
does it mean I have to relock my bootloader and then unlock it once again? In some other thread I found that information.
Click to expand...
Click to collapse
and now I relocked bootloader .... and guess what? bootloop again ... and I can not unlock it again, because I did not think about enable OEM unlock! It says necessary to unlock FRP before.
I am terribly sorry for being such an idiot!!
mark_at said:
and now I relocked bootloader .... and guess what? bootloop again ... and I can not unlock it again, because I did not think about enable OEM unlock! It says necessary to unlock FRP before.
I am terribly sorry for being such an idiot!!
Click to expand...
Click to collapse
Never ever relock bootloader untill you have a backup plan. We have dload method till emui 7 buut not sure on EMUI 8 so can't suggest you anything at the moment. Someone played with EMUI 8 can guide you through it.
I understand that I was not allowed to relock bootloader! I feel awful and stupid about it ... believe me!
I was able to erase FRP with HCU client from DC Phoenix.
After that I was in phone again
And afterwards I could open the bootloader again.
Halleluja!!
Thanks for everyone's help here ...