Develop Bugs

[Q] wildfire cannot downgrade to create s-off

Hello hoping someone can help, I'm a noob have not had much success in rooting yet...
Have a wildfire (Australian Telstra 3G)
Trying to downgrade firmware from HBOOT 1.01.0002 to 1.010001 so i can get s-off.
I'm following the instructions posted in http://forum.xda-developers.com/showthread.php?t=1132028
I've downloaded htc drivers (and uninstalled htc sync)as per instructions
Also loaded android drivers via device manager (screen dump attatched)
I can "talk" to my SD card OK with windows explorer but i don't think I am "talking to my phone or card via adb and the command prompt"
Got the full SDK package installed.
All the obvious things.. Andrtoid debugging enabled / Charge only
So When I attempt to run Step 1 bat I get the following error message:adb server is out of date..killing..*daemon server started successfully... error device not found..(screen dump attatched)
also i tried to make a "goldcard" and extract the serial no of the sd card on the phone. . same deal.. as soon as i get into adb ....error. device not found
note i am using windows 7.
my theory is that i'm don't have a propper usb link when i go into the dos cammand prompt/adb but i have loaded the drivers. I think this is happening when i try to root other phones also (eg zte blade)
can anyone help me. be kind to me I'm a noob...I've attatched three relevant screen dumps

wattamega said:
Hello hoping someone can help, I'm a noob have not had much success in rooting yet...
Have a wildfire (Australian Telstra 3G)
Trying to downgrade firmware from HBOOT 1.01.0002 to 1.010001 so i can get s-off.
I'm following the instructions posted in http://forum.xda-developers.com/showthread.php?t=1132028
I've downloaded htc drivers (and uninstalled htc sync)as per instructions
Also loaded android drivers via device manager (screen dump attatched)
I can "talk" to my SD card OK with windows explorer but i don't think I am "talking to my phone or card via adb and the command prompt"
Got the full SDK package installed.
All the obvious things.. Andrtoid debugging enabled / Charge only
So When I attempt to run Step 1 bat I get the following error message:adb server is out of date..killing..*daemon server started successfully... error device not found..(screen dump attatched)
also i tried to make a "goldcard" and extract the serial no of the sd card on the phone. . same deal.. as soon as i get into adb ....error. device not found
note i am using windows 7.
my theory is that i'm don't have a propper usb link when i go into the dos cammand prompt/adb but i have loaded the drivers. I think this is happening when i try to root other phones also (eg zte blade)
can anyone help me. be kind to me I'm a noob...I've attatched three relevant screen dumps
Click to expand...
Click to collapse
you might want to have a look at this alternative thread: http://forum.xda-developers.com/showthread.php?p=19746165
Swyped from my HTC Wildfire (Buzz)

no usb comms when in command prompt / adb
eventcom said:
you might want to have a look at this alternative thread: http://forum.xda-developers.com/showthread.php?p=19746165
Swyped from my HTC Wildfire (Buzz)
Click to expand...
Click to collapse
--------------------
Thanks eventcom, but I've followed that link and numrerous others and they all follow the same theme.
here is the problem as I see it...
1/I have installed the android driver when in hboot and it works ok as per attatched image
2/ I have installed htc_sync_setup 3.2.20.exe which is the latest driver availiable from the htc website.I then uninstall HTC sync, which leaves HTC driver installer & HTC BMP USB driver remaining as installed ( as per instructions)
3/ I have uninstalled any other USB programs which might conflict including Itunes and ascociated garbage (no i didn't put it there my kids did!).
USB debugging is turned on & when i plug in USB i go charge only (as per instructions)
Here's a hint...
When I execute an adb commandwithin command prompt eg [adb devices] i get no devices. When I issue a adb copy command I get the result "device not found" I'm know i'm going nowhere on this until I can get device to properly talk via adb and this is the assistance that i am seeking
further info.
I've tried this procedure on another (winxp) machine with same results.
Ive tried this procedure on another wildfire "s" (that is already rooted) same results
I've temporarily disabled the AVG 2012 virus protection & firewall.
As well as being in the directory that the file adb.exe exists I have also installed SDK so adb appears to run in any directory (please explain ?)
If i plug in usb and go "mount sd card" I can access the sd card on the phone viawindows explorer . in my mind this tells me that I have correct usb driver working.
I've tried a different usb cable AND a different phone
before I uninstalled htc sync i tried it out. it doesn't work and the phone won't sync up to this program ( it rarely works this program, tried it on numerous pc with different htc devices and more often than not it doesn't work)
I'm hoping that someone who is experienced in adb can help me get the phone talking with my pc, keeping in mind that I've done almost everything that I can think of to get my phone to "talk: via usb cable and issue commands. If I can't get my phone to communicate via adb then there is no way I can get past step one
please help me

wattamega said:
--------------------
please help me
Click to expand...
Click to collapse
i shall do my very best
ok so what system are you currently running? (win7,vista,xp ect)
are you using the stock usb cable that came with the phone?
when you connect the device to the pc with usb debugging turned on do you get the usb debugging notification in your status bar on the phone?
when you plug your device into the pc with debugging enabled what does your device manager recognize it as? mine shows up as attached...
did your antivirus flag up when you were installing the skd or downloading the adb.exe?

Success with debranding but problems with Revolutionary recovery
Thank you heavy_metal_man.
I finally solved the USB driver issue. I ended up completely uninstalling HTC driver installer & HTC BMP USB driver. I then installed HTCDriver3.00.007.exe as a stand alone only. Finally I got it to recognise in device manager.
Important lesson learned. Installing the latest HTC driver off the website which is htc_sync_setup_3.2.20 (which installs 3 modules HTC Sync, HTC driver installer & HTC BMP USB driver) then uninstalling HTC sync did not work for me...I now just have HTC driver installer only.
I asked to install clockwork mod during the revolutionary process, but I suspect it didn't work
Anyway I have now succesfully debranded and "sort of" have root. my Hboot screen now looks like this...
-Revolutionary-
BUZZ PVT SHIP S-OFF
HBOOT-6.01.1002
MICROP -0622
TOUCH PANEL - ATMEL224_16ab
RADIO-3.35.20.10
Nov 17 2010 12:08:53
Problem is when I go into recovery I get the "revolutionary CWM V4.0.1.4" Menu... So far so good.however When I select any item EG bacup & restore, intead of going to the next level menu it just goes to a revolutionary screen with no menu and just hangs. pressing the power button takes me back a level but the vol+ vol- buttons do nothing as there is no menu to select from.
So i can't flash with this current screen. the only way I can get out of it is to remove the battery as the reboot & power off menu items do not work.
.
I have tried re-running the revolutionary Exe file again. It prompts me if i would liketo install CWM and I say yes . It says it's done and takes me into Fastboot USB where I can reboot. but CWM ( The wierd revolutionary model) DOES not work like the CWM that i am accustomed to...
So i STILL can't flash CM7...but I'm getting closer...

wattamega said:
Thank you heavy_metal_man.
I finally solved the USB driver issue. I ended up completely uninstalling HTC driver installer & HTC BMP USB driver. I then installed HTCDriver3.00.007.exe as a stand alone only. Finally I got it to recognise in device manager.
Important lesson learned. Installing the latest HTC driver off the website which is htc_sync_setup_3.2.20 (which installs 3 modules HTC Sync, HTC driver installer & HTC BMP USB driver) then uninstalling HTC sync did not work for me...I now just have HTC driver installer only.
I asked to install clockwork mod during the revolutionary process, but I suspect it didn't work
Anyway I have now succesfully debranded and "sort of" have root. my Hboot screen now looks like this...
-Revolutionary-
BUZZ PVT SHIP S-OFF
HBOOT-6.01.1002
MICROP -0622
TOUCH PANEL - ATMEL224_16ab
RADIO-3.35.20.10
Nov 17 2010 12:08:53
Problem is when I go into recovery I get the "revolutionary CWM V4.0.1.4" Menu... So far so good.however When I select any item EG bacup & restore, intead of going to the next level menu it just goes to a revolutionary screen with no menu and just hangs. pressing the power button takes me back a level but the vol+ vol- buttons do nothing as there is no menu to select from.
So i can't flash with this current screen. the only way I can get out of it is to remove the battery as the reboot & power off menu items do not work.
.
I have tried re-running the revolutionary Exe file again. It prompts me if i would liketo install CWM and I say yes . It says it's done and takes me into Fastboot USB where I can reboot. but CWM ( The wierd revolutionary model) DOES not work like the CWM that i am accustomed to...
So i STILL can't flash CM7...but I'm getting closer...
Click to expand...
Click to collapse
That's ok , power is meant to do that, its the back button you need to use the trackball to select stuff also if I remember correctly that recovery has an issue where it will not charge the phone when it is turned off, so I would update that asap I shall give you a link when I'm out of bed, but for the mean time, backup, wipe everything and install cm7+ gapps
ok here is the most up tp date cwm recovery for the buzz as far as i know. and here is the thread it came from something to note, when you jump up tp gingerbread the type of recovery changes as well, so, the new one will not flash sense roms unless the rom has been designed for the new edify type recovery. not sure how many support this though. also the new recovery will NOT flash radios. it does not play well with others but you can always downgrade your recovery temporarily if you need to, or use the rom manager app (which ic an app interface for the recovery) to flash what you need
Sent from my HTC Sensation using xda premium

Success at last
Thanks Heavy_metal_man
Success I now have CM 7.2.0- buzz. I also installed google apps ok.
I guess I shouldv'e read the instructions on flashing a bit closer. I've also got a wildfire "s" as well and it uses the power button to enter so I suppose I just assumed...Truth is that I've only just got this phone last week and I didn't even realise that it had a trackball button ...
This is my first ever root/flash that I have done and I have learned alot from the experience. I specifically got this phone ($10 on ebay) so I coul;d learn to do this without the risk of damaging my own phone. This phone had "issues" when I bought it which is why i got it so cheap. now I have upgraded to CM7 it the issues (eg wireless hotspot would not remain on) have gone.
Soon I hope to have the experience and courage to flash my own phone and my kids phones.
Thanks to H_M_M and all of the XDA forum for helping me out.

wattamega said:
Thanks Heavy_metal_man
Success I now have CM 7.2.0- buzz. I also installed google apps ok.
I guess I shouldv'e read the instructions on flashing a bit closer. I've also got a wildfire "s" as well and it uses the power button to enter so I suppose I just assumed...Truth is that I've only just got this phone last week and I didn't even realise that it had a trackball button ...
This is my first ever root/flash that I have done and I have learned alot from the experience. I specifically got this phone ($10 on ebay) so I coul;d learn to do this without the risk of damaging my own phone. This phone had "issues" when I bought it which is why i got it so cheap. now I have upgraded to CM7 it the issues (eg wireless hotspot would not remain on) have gone.
Soon I hope to have the experience and courage to flash my own phone and my kids phones.
Thanks to H_M_M and all of the XDA forum for helping me out.
Click to expand...
Click to collapse
no problem man glad your all kitted out!
wow that cheap this phone cost me £140 when i bought it!!! ( a few years ago) man i got ripped off.... still glad to hear you got sorted out you should always read everything you can carefully before you go flashing your phones
also, just so you know, this wildfire is code named BUZZ and your wildfire s is code named MARVEL just to avoid confusion of course if you need any help with the marvel just let me know. i imagine you've been over to the marvel forum ect but if you get lost pm me. i have experience with that phone as well aside from the name they are completely different, and the marvel does not have s-off yet :/ not by software anyway so everything is different to do :/ still i am rambling now glad your sorted mate :good:

Fastboot does not work but ADB does

Hey guys,
The power button on my phone stopped working this morning (without water damage). I'm preparing the phone to return to Samsung warranty, and in the process of reseting to stock and re-locking the OEM I noted that the phone does not respond to fastboot commands in the bootloader despite this working on the same system a week ago, no change in drivers or anything else. I installed PDAnet, still broken on Win 7 although I can reboot with adb.
I then tried this on OSX, again I can reboot with ADB, but the phone is unresponsive in fastboot.
I have three working hypotheses and I'm hoping someone can help me:
a) in some process of flashing my phone and being an uninformed n00b maybe I flashed something I shouldn't have or used some combination of partial fastboot flashes I shouldn't have. has this happened to anyone else?
b) whatever hardware damage knocked out the power button might have partially knocked out the bootloader
c) I just have really bad luck with driver set up and I just happened to mess up two different computer driver configurations but the phone is fine. to this end, I am setting up another Win 7 system fresh on a virtual drive as I'm typing, though I have little faith it will be different

update: fastboot commands didn't work on the other windows 7 virtual system, although adb reboot bootloader did
freaking a this is annoying.
i have a fully stock ROM and radio, anybody to know how to flash a new recovery image and lock the bootloader without accessing fastboot? Just have to get this ready to go back to Samsung so they can fix their own hardware mess ups.

they are 2 different drivers.

As much as I don't like using/recommending the Galaxy Nexus Toolkit (only because I feel it's better to actually learn everything you're doing), it's the easiest way I've found to get the Fastboot drivers installed.
http://forum.xda-developers.com/showthread.php?t=1392310

Thanks guys for your comments.
I've tried Android SDK drivers, PDANet, Universal Naked Driver, and now the one click toolkit mentioned above, some on three different operating systems (Win 7, Win 8, OSx) on 32 and 64 bit.
The wierdest part is that under device manager, no device shows up when the phone is in fastboot, no is there any noise or any recognition of the device being connected at all. It is completely, 100% silent. (again, ADB works when the phone is booted).
I recognize that this may not be possible, but does anyone know how to flash a recovery image without being in the bootloader mode?

If fastboot isnt working like it should, and you are sure it isnt user error, then take it for warranty.
Sent from my i9250

yeah fastboot + the power button (which was defunk in clockwork mod) are back online again, dunno for how long. agreed seems like a hardware/warranty issue.

Recoveries can be flashed with ROM Manager assuming you have SuperUser permissions, but otherwise you or the toolkit need fastboot working.
Sent from my Galaxy Nexus using xda app-developers app

HELP!!! Why Can't I unlock my device {Fixed}

I have spent 2 days trying to unlock my new Nexus 7 HD. I'm not a noob, my last 7 phones I have rooted, flashed, unlocked and messed around with, my last 3 tablets I've unlocked and rooted including my 2012 Nexus 7.
Everytime I try to unlock it says fastboot not found. I'm using Nexus Root Toolkit 1.7.1. I can boot into the bootloader using the toolkit, and when it's in bootloader mode, I can also reboot the bootloader using the toolkit. When I click unlock, i get the fastboot device no found. When the Nexus 7 is turned on, my device manager shows "Android Composite ADB device" when the Nexus is in bootloader mode my devices show "Android bootload interface" USB debugging is enabled which don't effect fastboot anyways.
I've tried all 4 of my USB ports, I've followed the driver instructions to a "T", I've uninstalled all the
- Android ADB Interface device's,
- Samsung USB devices,
- Google USB drivers
- or ANYTHING else you see that resembles your Nexus.

budco2000 said:
I have spent 2 days trying to unlock my new Nexus 7 HD. I'm not a noob, my last 7 phones I have rooted, flashed, unlocked and messed around with, my last 3 tablets I've unlocked and rooted including my 2012 Nexus 7.
Everytime I try to unlock it says fastboot not found. I'm using Nexus Root Toolkit 1.7.1. I can boot into the bootloader using the toolkit, and when it's in bootloader mode, I can also reboot the bootloader using the toolkit. When I click unlock, i get the fastboot device no found. When the Nexus 7 is turned on, my device manager shows "Android Composite ADB device" when the Nexus is in bootloader mode my devices show "Android bootload interface" USB debugging is enabled which don't effect fastboot anyways.
I've tried all 4 of my USB ports, I've followed the driver instructions to a "T", I've uninstalled all the
- Android ADB Interface device's,
- Samsung USB devices,
- Google USB drivers
- or ANYTHING else you see that resembles your Nexus.
Click to expand...
Click to collapse
Is the fastboot command not found or the device is the one not found? Unlocking the bootloader is very easy using fastboot. I've never run any of the toolkits.
Once the device is connected to your computer and in bootloader mode (vol+down and power), you should get the device id returned if you run "fastboot devices". Then it is a simply matter of just running "fastboot oem unlock", use the vol to scroll to yes, and press the power to select. That is pretty much there is to it.

cowabunga said:
Is the fastboot command not found or the device is the one not found? Unlocking the bootloader is very easy using fastboot. I've never run any of the toolkits.
Once the device is connected to your computer and in bootloader mode (vol+down and power), you should get the device id returned if you run "fastboot devices". Then it is a simply matter of just running "fastboot oem unlock", use the vol to scroll to yes, and press the power to select. That is pretty much there is to it.
Click to expand...
Click to collapse
It says fastboot device not found. I know this is a driver issue, and I've tried different drivers. I unlocked my 2012 nexus 7 in under 3 minutes, but this is not going to smoothy lol

budco2000 said:
It says fastboot device not found. I know this is a driver issue, and I've tried different drivers. I unlocked my 2012 nexus 7 in under 3 minutes, but this is not going to smoothy lol
Click to expand...
Click to collapse
And you are booted to the bootloader, right?
I use a mac. No crazy drivers to deal with. Just plug and go.

cowabunga said:
And you are booted to the bootloader, right?
I use a mac. No crazy drivers to deal with. Just plug and go.
Click to expand...
Click to collapse
I got my bootloader unlocked. Now I can't root it. I downloaded like 3 toolkits, all of them are failing. I've never had so many problems with one device as this one. Wug's toolkit didn't see the device in bootloader, but N-cry toolkit had no problem seeing the device in bootloader mode, which unlocked bootloader, but it wont flash recovery or root. Wug's tool kit will push the files for recovery and root, but then when the Nexus goes into bootloader wug's toolkit fails because it don't see the device in bootloader mode. The quick root tool doesn't do anything at all. The problem here is I'm using windows 8 and I just read that android SDK drivers have to be manually installed, but even that is giving me problems. I have a bad ass laptop, A dell alienware that's never gave me a problem. It came with windows 7, and i put windows 8 on it about 8 months ago, thinking about running the restore CD's and downgrading back to windows 7. ADB commands aren't responding from a command promt. I just want root, and its being a real pain in the ass.

budco2000 said:
I got my bootloader unlocked. Now I can't root it. I downloaded like 3 toolkits, all of them are failing. I've never had so many problems with one device as this one. Wug's toolkit didn't see the device in bootloader, but N-cry toolkit had no problem seeing the device in bootloader mode, which unlocked bootloader, but it wont flash recovery or root. Wug's tool kit will push the files for recovery and root, but then when the Nexus goes into bootloader wug's toolkit fails because it don't see the device in bootloader mode. The quick root tool doesn't do anything at all. The problem here is I'm using windows 8 and I just read that android SDK drivers have to be manually installed, but even that is giving me problems. I have a bad ass laptop, A dell alienware that's never gave me a problem. It came with windows 7, and i put windows 8 on it about 8 months ago, thinking about running the restore CD's and downgrading back to windows 7. ADB commands aren't responding from a command promt. I just want root, and its being a real pain in the ass.
Click to expand...
Click to collapse
Now that I think about it, I don't think I had to even deal with installing a root. I installed twrp2 for recovery and it automatically detected that I did not have root as I was rebooting and it prompted me if I wanted to install root. I remember select yes and after it rebooted, I had root.
Make sure you enable root access for "Apps and ADB" in developer options. You may find you already have root.

cowabunga said:
Now that I think about it, I don't think I had to even deal with installing a root. I installed twrp2 for recovery and it automatically detected that I did not have root as I was rebooting and it prompted me if I wanted to install root. I remember select yes and after it rebooted, I had root.
Make sure you enable root access for "Apps and ADB" in developer options. You may find you already have root.
Click to expand...
Click to collapse
I got it. I ended up using the rootkit for the 2012 nexus 7, i remembered it had an option to push image files, I push the recovery file, then flashed super user. all is good

[Q] ADB no devices found please help

I recently got an insurance replacement for my HTC ONE M8, I converted my (original) HTC one m8 into a GPE w/ OTA.
Now with the replacement I want to again change it to a GPE but I am unable to unlock the device I have platform tools from the HTC Developer. It recognizes the devices when it is on and fully booted up but when I use ADB reboot bootloader to reboot the device it no longer shows on adb device list once booted to fastboot. I have tried booting the device manually (power+Volume down) and then connecting through usb and again adb can not see it.
Just to clarify I am trying to unlock the device I do not have s off or the unlock token, the device is completely stock as of right now
The usb ports on my laptop are 2.0 I used this same laptop to convert the my original htc one m8 to gpe
Please help

I had a similar problem with my nexus 7 (2012) at one point. I had to update the Android SDK to the latest version because something had changed in the way the device talked to the computer with adb. Under SDK>Tools you will find a file called "android" that opens the SDK through terminal so you can take updates.

[UNLOCK] [H815] Fastboot won't recognize my LG G4 in fastboot mode...

First I must say, I searched all over the internet for answer to this problem. None of the topics I read had matched my problem.
I want to unlock my bootloader so I can flash custom recovery and get root access.
When I want to access the bootloader ("adb reboot bootloader"), in my phone all goes fine (I see on my phone the Fastboot instructions, etc). The problem is in my computer that fastboot won't recognise my phone anymore. When I want to get the device-id, fastboot is stuck on "waiting for all devices". When I want to see the list of devices, ("fastboot devices"), I get nothing, wether my phone is on bootloader mode or not.
I installed all the LG drivers, including the ADB one. I am in USB debugging mode, and I disabled OEM protection.
Android version is Lollipop.
I need help on this matter, thanks in advance.

notrium dweller said:
First I must say, I searched all over the internet for answer to this problem. None of the topics I read had matched my problem.
I want to unlock my bootloader so I can flash custom recovery and get root access.
When I want to access the bootloader ("adb reboot bootloader"), in my phone all goes fine (I see on my phone the Fastboot instructions, etc). The problem is in my computer that fastboot won't recognise my phone anymore. When I want to get the device-id, fastboot is stuck on "waiting for all devices". When I want to see the list of devices, ("fastboot devices"), I get nothing, wether my phone is on bootloader mode or not.
I installed all the LG drivers, including the ADB one. I am in USB debugging mode, and I disabled OEM protection.
Android version is Lollipop.
I need help on this matter, thanks in advance.
Click to expand...
Click to collapse
not all phones can be unlocked.. search for g4 list of bootloader unlock youll see the list if yours isnt there you cant . only root 5.1 no twrp.

raptorddd said:
not all phones can be unlocked.. search for g4 list of bootloader unlock youll see the list if yours isnt there you cant . only root 5.1 no twrp.
Click to expand...
Click to collapse
I know mine can be unlocked. I actually can get to the bootloader via ADB. The problem is that fastboot won't recognise my phone afterwards. (I believe it's the european version of the H815 model, and according to one-click-root app, my phone can be safely rooted. Also my Lollipop version is 5.1.)
There are other few issues also:
Fastboot won't recognise my phone, even if the phone is not in bootloader mode.
Windows will recognise all of the LG related drivers including the ADB related driver, while the phone is powered on normally.
However, it fails to do so, in bootloader mode. I see non working driver in Windows 7 Device Manager, under "Other Devices" by the name "Android" with yellow exclamation mark. Nothing else.
Still looking for advice...

notrium dweller said:
I know mine can be unlocked. I actually can get to the bootloader via ADB. The problem is that fastboot won't recognise my phone afterwards. (I believe it's the european version of the H815 model, and according to one-click-root app, my phone can be safely rooted. Also my Lollipop version is 5.1.)
There are other few issues also:
Fastboot won't recognise my phone, even if the phone is not in bootloader mode.
Windows will recognise all of the LG related drivers including the ADB related driver, while the phone is powered on normally.
However, it fails to do so, in bootloader mode. I see non working driver in Windows 7 Device Manager, under "Other Devices" by the name "Android" with yellow exclamation mark. Nothing else.
Still looking for advice...
Click to expand...
Click to collapse
am sorry i cant help ive nver unlocked mine..

Still looking for suggestions, people...

I have the same problem, adb detects my phone but fastboot does not. Same Phone btw

Still no solution until now ? I have the same problems
My device is H815

Hi !
I have had this problem too...solved with strong battle to understand myself...
My solution : when you have installed driver ,when your phone go to fastboot mode and the pc don't want to reconize the phone : on the pc on windows go to harware manager (config panel) and you can see in theory "android" with a "?" ==> you have to install manually the driver by searching somewhere on the harware list "android adb interface " (i don't remember where it is) ==> your phone wil be reconized ! And you will have the 2 lines of ID on the adb comand interface....and follow the tutorial...

I have read hundreds of issues with driver problems when it comes to windows.
Please try Linux instead. There are live distributions like Ubuntu available. Install it on USB stick and start from there.
No driver issues anymore. Just works.
.

@steadfasterX it need some knowledge for to use Linux OS for adb thingsv (unlock bootloader ,instal TWRP,rom,apps...etc...) ? maybe you can do a small tutorial for to help ?
For windows i have found these pictures for an eventual help (see ZIP on attach file)

@Loulou-13 , now i can see my device-id - solved -
but now have another problems, my imei is not match with my device-id ...
my device is H815

yes...i know i have sent an answer too late ... but my solution is one of this problem and eventualy can be useful for other people.
for your new problem ,what happen ? .......have you enter the corect number ,without space or other ?

Loulou-13 said:
@steadfasterX it need some knowledge for to use Linux OS for adb thingsv (unlock bootloader ,instal TWRP,rom,apps...etc...) ? maybe you can do a small tutorial for to help ?
For windows i have found these pictures for an eventual help (see ZIP on attach file)
Click to expand...
Click to collapse
Well there are hundreds of guides out there just use google...
adb and fastboot working the same way under Linux so there is no need to have a specific guide for linux.
I haven't tested that guide here but it looks very good as a starting point:
http://forum.xda-developers.com/showpost.php?p=44739402&postcount=1
As said there are other maybe better guides but Google will tell you.
.

@steadfasterX thank for your link ,it's useful for people who have problem and read this thread
It's not for me .... i have my bootliader unlocked ,twrp...( and this fabulous Imperium MM rom !!!! )