Database Info

[Q] Urgent Help with Sensation phone

My phone has for some unknown reason has stopped working, as when i switch the phone on the screen light comes on but it wont charge or anything, if i am trying to connect it to linux, it does show up, and i am able to see the content of the phone but for the life of me i cant get it to go to recovery mode or anything else, it is not rooted, or anything i was in the process of using JB rooting with the wire connection when it failed, or should i say stop reponding, chances it in a loop or something but i am not too sure.
HBOOT 1.27
Sensation
locked to Network
Anyone out there able to help me get this phone working

remove battery,sim and sdcard and charge the device for 5-6 hours.put them again and see if it worked
best wishes

it the above doesnt works
then u need to unbrick ur soft bricked fone
use this >> http://forum.xda-developers.com/showthread.php?t=1522351
THANK me n the dev if it works for u

fkardame said:
it the above doesnt works
then u need to unbrick ur soft bricked fone
use this >> http://forum.xda-developers.com/showthread.php?t=1522351
THANK me n the dev if it works for u
Click to expand...
Click to collapse
tried that method and it say i dont have access in linux or rights to access the phone
rzr86 said:
remove battery,sim and sdcard and charge the device for 5-6 hours.put them again and see if it worked
best wishes
Click to expand...
Click to collapse
what does that method do?? also what could be the possibility of this phone working ??

morning guy i tried the 5-6 hrs without the battery and sd a sim in the phone and as we speak i have tried to switch on the phone, the phone just show lights on the screen around the edges but that is it, maybe i did something i also tried the power button down and down volume key, still no love or money....anymore advise

when i try to access it via linux i keep getting this "You do not have the permissions necessary to view the contents of"57f8f4bc-abf4-0000-675f-946fc0f9f25b_" what does that mean in plain english?? i have attached the files below i hope you will be able to see what the problem is thanks

darkwildchild79 said:
when i try to access it via linux i keep getting this "You do not have the permissions necessary to view the contents of"57f8f4bc-abf4-0000-675f-946fc0f9f25b_" what does that mean in plain english??
Click to expand...
Click to collapse
it means you messed up while rooting your device.
1srt i would try to boot into bootloader, i m sure you ll got screen and information on bootloader.
once you got those info check what hboot you got on it - if it is 1-27-xxx you go to follow this tut h-boot 1.27 s-on
http://forum.xda-developers.com/showthread.php?t=1631861
m2c

no bootloader the screen just light but nothing to show

darkwildchild79 said:
no bootloader the screen just light but nothing to show
Click to expand...
Click to collapse
okay are you sure you have do this right?
pwr button + vol down and let start phone booting.
if this is what you ve done and you don t see anything on bootloader screen... do you have tried some fastboot command??
phone plug on usb comp.
open terminal and type fastboot devices. (you should seee serial number)
if you got it type => 'fastboot oem boot' w/o quote
give output (you shoud see you cid_number
edit: just saw the file you attached (h-boot.img) this was a very bad idea. h-boot must be flashed only if s-off. hope you didn't brick your phone.
get see and read this post, it s a usefull post s-off or s-on => http://forum.xda-developers.com/showpost.php?p=21989063&postcount=1
you should know if your device is s-on or s-off...

darkwildchild79 said:
tried that method and it say i dont have access in linux or rights to access the phone
what does that method do?? also what could be the possibility of this phone working ??
Click to expand...
Click to collapse
u are suppose to get the phone driver in ur linux first then doo all the processses
well ur fone is bricked n u need to unbrick it using the above link only
no other method for time being
install ur fone driver using the codes in linux and then do as the unbricking method says

[Q] HTC Sensation bootloop

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

Trying to update Sensation OTA fails need help

Hi there,
I'm tearing my hair out here. I have an HTC sensation which I inherited off my girlfriend. I tried to update it OTA and it says something like "variant system version htc" etc. I thought oh maybe somehow the bootloader has been tampered with. I previously had a rooted HTC desire for a couple years. I thought oh I'll just root this as well. I've tried on two occassions over 6+ hours to unlock this sensation via HTC Dev and it just doesn't work. I download sdk and put fastboot and adb in a folder. Connect the phone with USB and go into terminal and type cd and drag the folder in to make sure location is right. Then type ./fastboot oem get_identifier_token and it has either said "permission denied" or most commonly "waiting for device". So after shedding tears of rage, I gave up on that route. I thought instead ok lets see if I can go via OTA. So I called HTC and they rain my IMEI and apparently this phone is French (I'm in Australia) and thats why the OTA updates aren't working. He recommended I call the French HTC support and see what they can do. Funny thing is, I don't speak French.
Before I throw this phone off the highest place I can, is there any way I can get this OTA French update online off someone or a download website?
Model number: HTC sensation z710e
Thanks in advance for any helpful comments. I've done lots of reading and seem to be going in circles. From what I've read there doesn't appear to be a one click root app for the Sensation as existed for my HTC desire.
:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:

you can easily unlock the device !!!
i think you are missing few points here
1. uncheck fastboot in settings -> power/battery
2. also enable "usb debugging" in settings ->developer options
3.then once you connect the phone from bootloader to the pc
( to go to bootloader ..power off phone ..remove battery , reinsert it ..then hold power + volume down buttons together until you get the bootloader screen a few seconds ))
4. if the connection is proper and you have proper drivers installed the phone says "FASTBOOT USB"
if the phone is saying :HBOOT" press power button once then it should say "FASTBOOT USB"
if the phone is just saying "FASTBOOT" that means connection is not proper or drivers are not installed
for proper connection : you can only use usb 2.0 ports ..usb 3.0 port and usb hubs dont work properly ..also if using pc connect to back usb ports
for proper drivers: you need to have HTC sync installed ..or if you have windows 7/8 32 bit install these drivers ..if you have windows 7/8 64 bit install these drivers (NOTE: if you plan to use these drivers .uninstall every HTC related software from control panel then reboot and install these ..and dont install HTC sync any more)
5. to check proper connection
type this command from your adb/fastboot folder
fastboot devices (it should list your device )
6. then continue with the rest of process

success
Thanks for your reply.
I have good news and bad news.
The good news is I have S-OFF and rooted my phone.
The bad news is that both JB roms I have tried I am unable to get passed choosing my language after the phone has started. I select any language (say english US) and it just freezes and then after 10 seconds restarts. This is with the CM 10.1 and AOSP 4.2.2 roms from development section. When installing these roms I make a nand backup, then wiped data and cache as well as dalvik cache. Then install the rom and JBapps. Any ideas on what to try to fix this? For now I have reverted to my backup.
Onto how I unlocked and rooted.
I was consistently getting an error in terminal when typing ./fastboot oem get_identifier_token
It would say .... ERROR
After a lot of googling I discovered that I was most likely getting that error because my HBOOT was too old for the HTCDEV method.
So I tried the revolutionary method which worked perfectly. Than installed clockwork recovery, gained root (did a dance for joy) and now here I am very close to JB goodness just need to figure out why it keeps on rebooting.
Any help is appreciated. :laugh:

lui8906 said:
Thanks for your reply.
I have good news and bad news.
The good news is I have S-OFF and rooted my phone.
The bad news is that both JB roms I have tried I am unable to get passed choosing my language after the phone has started. I select any language (say english US) and it just freezes and then after 10 seconds restarts. This is with the CM 10.1 and AOSP 4.2.2 roms from development section. When installing these roms I make a nand backup, then wiped data and cache as well as dalvik cache. Then install the rom and JBapps. Any ideas on what to try to fix this? For now I have reverted to my backup.
Onto how I unlocked and rooted.
I was consistently getting an error in terminal when typing ./fastboot oem get_identifier_token
It would say .... ERROR
After a lot of googling I discovered that I was most likely getting that error because my HBOOT was too old for the HTCDEV method.
So I tried the revolutionary method which worked perfectly. Than installed clockwork recovery, gained root (did a dance for joy) and now here I am very close to JB goodness just need to figure out why it keeps on rebooting.
Any help is appreciated. :laugh:
Click to expand...
Click to collapse
You've done soff via revolutionary means you've got 1.17 firmware.. For ics and jellybeans you need 3.32/3.33 firmware.. Grab the latest firmware from kohr-ah firmware thread in sensation development section and flash it.. Then flash any ics/jb rom
Sent from my HTC Sensation using xda premium

Phone wont connect

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

need bootloop help please

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 ...