Database Develop

Fastboot Unlocked?

So I decided just to see what my fastboot looked like - attached.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is that normal for it to be unlocked? Everything I've heard says this is supposed to be super locked down.

mxgoldman said:
So I decided just to see what my fastboot looked like - attached.
Is that normal for it to be unlocked? Everything I've heard says this is supposed to be super locked down.
Click to expand...
Click to collapse
I think it says "bootloader LOCKED" in the fastboot screen. That means, you can ONLY flash motorola compiled operating systems (specifically kernels).;
If you want to try, run a fastboot unlock-bootloader command when running in fastboot. A locked bootloader will tell you something along the lines of "command not valid"

Do not flash anything on your phone. That looks to be a unlocked bootloader!
Sent from my DROID4 using Tapatalk 2

jsnweitzel said:
Do not flash anything on your phone. That looks to be a unlocked bootloader!
Click to expand...
Click to collapse
Wait, wouldn't that be a positive that would make flashing them easier?

I emailed someone who knows these things. He says its an engineering model. So it doesn't help the rest of us.
Sent from my DROID4 using Tapatalk 2

mxgoldman said:
Wait, wouldn't that be a positive that would make flashing them easier?
Click to expand...
Click to collapse
I think he meant "don't flash anything that might overwrite your unlocked bootloader" :laugh:
Anyway we could pull it or something? Probably not eh? OP, where did you get?!

podspi said:
I think he meant "don't flash anything that might overwrite your unlocked bootloader" :laugh:
Anyway we could pull it or something? Probably not eh? OP, where did you get?!
Click to expand...
Click to collapse
Makes more sense.
That's my little secret.
I could probably pull whatever from it, but I'd need some help for what you'd like pulled. Haven't rooted it or anything yet.

didnt this happen with a GSM RAZR before? dont get me wrong, i'd love to unlock my bootloader! someone bring this to their attention

FYI, on Milestone XT720, Motorola left a partially working fastboot--we can "fastboot boot boot.img" to boot self-built kernels and this bypasses the signature checks. But you have to boot via USB each time, if you use "fastboot flash boot.img" fastboot will write the kernel and reboot, but the signature check will fail after reboot.
http://forum.xda-developers.com/showthread.php?t=821210
Here's one way to muck with a kernel to change uname strings:
http://forum.xda-developers.com/showthread.php?p=11975260#post11975260

jsnweitzel said:
I emailed someone who knows these things. He says its an engineering model. So it doesn't help the rest of us.
Click to expand...
Click to collapse
FWIW, the "SE" is the giveaway. If it said "S", you would be in business.

Rzrbck, how so, if it could be retrieved from the phone? Maybe I'm not understanding, but if we had that bootloader is it not like the normal S model with full permissions to the phone?

what makes it an engineering model? are the physical components the same, or is it a software setting that if we changed could unlock the phone?

would it be possible via hardware to dump an SE bootloader, and flash it to a S devic? I would be willing to give this a go if its possible.

if we could get the bootloader images off that phone an unlock for the Droid 4 might be possible. Assuming, of course that both the S and the SE model use the same keys.

Tell me what I can do to help.

I wish I knew what to do, but in the mean time, here's some literature on how the lock works (it's for the milestone, but the d4 might use the same infrastructure).
The bootchain:
http://www.droid-developers.org/wiki/Booting_chain
The mbmloader: this loads the bootloader, if this is replaced with a version that doesn't check signatures, the bootloader can be permanently replaced:
http://www.droid-developers.org/wiki/Mbmloader
The mbm (bootloader) does it's own signature check of the kernel before booting it.
If either the key burned into the phone's fuse, or the key the mbmloader uses to check the mbm are the same on both devices, one or both of those partitions can be flashed with with the unlocked version. If they're both different, this is a dead end.
The only other option after this (aside from espionage)would be to crack the signature system directly by either creating an unlocked version of the bootloader and patching it in a way that it generates the same hash, or discover a new way to factorize large (2048 bit) numbers, and reverse engineer motorola's private signing key. (If you were to discover this factoring method, nearly every security company would have to retool.)
edit: careful updating your phone, an OTA can relock your phone. The more I read, it seems less likely that the bootloader is encrypted. Dumps should be made, but this is going to require someone with greater knowledge than I.

how would we go about doing this?

dewhashish said:
how would we go about doing this?
Click to expand...
Click to collapse
It seems like you load a special kernel module to unhide the bootloader partitions then simply use the dd command to make an image copy onto the sdcard.
iow, we need a dev.

well the only ones i know might be kholk, hashcode, and p3droid

This got quiet. No news on this yet?

[Q] HTCDev Unlocking issue !

Hi guys,
I'm facing a problem with my HTC Sensation XL, I'm trying to unlock it via HTCDev Method & Phone refuses to take the "Unlock_token.bin file when I push it using fastboot as you can see in the first picture. It stays at "sending ..... (0KB) and nothing seems to happen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just one think, after pressing Enter there is a green bar appearing right after and phone doesn't seem to react until I pull out the Battery and restart it again. I've tried too many ways and the result is always the same.
Any bright ideas ?
Thanks in Advance.

Well after a period since I started this thread, the phone act weirdly If I want to use GSM/Data (Radio), once it tries to get signal, it starts lagging until the system crash, I've also analysed kmsg log and found it's something to do with RADIO before the system crashed.
Now I have to keep airplane mode on all the time or the phone will slip into an infinite bootloop.
Since the main reason that pushed me to unlock the Bootloader is to gain S-OFF so I can re-flash RADIO and see what could happen.
Another weird thing is it can only be detected if I plug the phone to a computer with AMD Processor/Chipset, It works well with any AMD based computers. I tried with more than 10 computers with Intel and nada, like it's just plugged to an AC-Charger.
Does anybody's got an idea what to do? I'm also searching for an RUU supporting VODAP110 (Swisscom-DE) CID.
Thanks in advance.

Raz0r1911 said:
Well after a period since I started this thread, the phone act weirdly If I want to use GSM/Data (Radio), once it tries to get signal, it starts lagging until the system crash, I've also analysed kmsg log and found it's something to do with RADIO before the system crashed.
Now I have to keep airplane mode on all the time or the phone will slip into an infinite bootloop.
Since the main reason that pushed me to unlock the Bootloader is to gain S-OFF so I can re-flash RADIO and see what could happen.
Another weird thing is it can only be detected if I plug the phone to a computer with AMD Processor/Chipset, It works well with any AMD based computers. I tried with more than 10 computers with Intel and nada, like it's just plugged to an AC-Charger.
Does anybody's got an idea what to do? I'm also searching for an RUU supporting VODAP110 (Swisscom-DE) CID.
Thanks in advance.
Click to expand...
Click to collapse
Like you said, i also think you can solve the problem flashing an RUU. but it will be hard to find this specific RUU. What i can suggest you is change the CID of your phone and flash the stock ICS RUU of your choice.
In this links you can find all available stocks RUU for sensation XL maybe one of HTC Europe have your CID.
http://gsmffflash.blogspot.pt/2013/03/htc-runnymede-sensation-xl-x315-stock.html
http://www.full-firmware.com/htc-runnymede-sensation-xl-x315-stock-roms.html
http://forum.gsmhosting.com/vbb/9187811-post11.html
Download the RUU of your choice and look in the rom.zip file what CID is supported. If your CID is not supported by any RUU, you have no choice. You have to change the CID of your phone to superCID.
Hope is help.
Regards.

francocrack said:
Like you said, i also think you can solve the problem flashing an RUU. but it will be hard to find this specific RUU. What i can suggest you is change the CID of your phone and flash the stock ICS RUU of your choice.
In this links you can find all available stocks RUU for sensation XL maybe one of HTC Europe have your CID.
http://gsmffflash.blogspot.pt/2013/03/htc-runnymede-sensation-xl-x315-stock.html
http://www.full-firmware.com/htc-runnymede-sensation-xl-x315-stock-roms.html
http://forum.gsmhosting.com/vbb/9187811-post11.html
Download the RUU of your choice and look in the rom.zip file what CID is supported. If your CID is not supported by any RUU, you have no choice. You have to change the CID of your phone to superCID.
Hope is help.
Regards.
Click to expand...
Click to collapse
I would like to thank you for your time.
I must say I'm cursed because I downloaded all of these RUU even the arabic one just to make sure that I have no luck, and NADA, none of them support VODAP110.
Anyhow, after a good searching I found a post by fardjad here : http://forum.xda-developers.com/showpost.php?p=26318550&postcount=2
It's for those who want to install an official ROM with different CID, woe betide, the link of his tool gives a 404 error. but I think I saw its source somewhere and I'm gonna keep searching until I find it to start a new battle with this pickle.
Edit:
Well I found the source of sigtool at fardjad's github, It's written in C, I'll compile it and try if I can get any further.

Raz0r1911 said:
I would like to thank you for your time.
I must say I'm cursed because I downloaded all of these RUU even the arabic one just to make sure that I have no luck, and NADA, none of them support VODAP110.
Anyhow, after a good searching I found a post by fardjad here : http://forum.xda-developers.com/showpost.php?p=26318550&postcount=2
It's for those who want to install an official ROM with different CID, woe betide, the link of his tool gives a 404 error. but I think I saw its source somewhere and I'm gonna keep searching until I find it to start a new battle with this pickle.
Edit:
Well I found the source of sigtool at fardjad's github, It's written in C, I'll compile it and try if I can get any further.
Click to expand...
Click to collapse
Great. Good Luck!

[SOLVED]Can't unlock bootloader-fake Hong Kong HTC One version

After a lot of troubles I finally determined that my HTC One is actually a fake Hong Kong custom version with different hardware but amazingly similar look. If your HTC One:
- doesn't have Sense preinstalled,
- lack proper identification,
- came with BeatsAudio headphones,
- is made of plastic,
- has Chinese factory mode,
- different barebone bootloader
- and anything else which doesn't look right in regard to HTC One
There's even post on Engadget.
It's probably fake...
After I found that I have different bootloader then usual one I tried to unlock it but when I come to 'fastboot oem get_identifier_token' step cmd just outputs tree dots so I left it for a while but nothing happens after that. It's same for every other oem command. Device is recognized by fastboot and every command that I try works like it should, 'fastboot reboot' reboots device, 'fastboot reboot-bootloader' boots to bootloader, 'fastboot -w' clears userdata and cache so it doesn't seem that adb and drivers aren't set properly.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is how my fastboot menu looks like(picture below);nothing like one on picture above:
Is there anything I can do to unlock my HTC One?

BUMP

Where did you get this one?

I got it second hand but I checked via IMEI and H/P on HTC site and they say it's valid device from England.
Sent from my iPad using Tapatalk HD

BUMP

Jon2555 said:
After I found that I have different bootloader then usual one I tried to unlock it but when I come to 'fastboot oem get_identifier_token' step cmd just outputs tree dots so I left it for a while but nothing happens after that. It's same for every other oem command. Device is recognized by fastboot and every command that I try works like it should, 'fastboot reboot' reboots device, 'fastboot reboot-bootloader' boots to bootloader, 'fastboot -w' clears userdata and cache so it doesn't seem that adb and drivers aren't set properly.
This is how my fastboot menu looks like(picture below);nothing like one on picture above-background is black and words are in white(I'll upload picture as soon as I make one):
Code:
Select Boot Mode:
[VOLUME_UP to select. VOLUME_DOWN is OK.]
[Recovery Mode]
[Fastboot Mode]
[Normal Boot] <<==
[UART Boot]
Is there anything I can do to unlock my HTC One?
Click to expand...
Click to collapse
Have you tried the Revone S-Off method, I know it's still in early stages, but it worked great for me.
No need for the OEM token method if you use it.
I know it took a few tries but just keep at it and you shoul get there

Thanks for answer, I already tried that but I keep getting same error all over time which other users don't get(as far as I saw)

Jon2555 said:
Thanks for answer, I already tried that but I keep getting same error all over time which other users don't get(as far as I saw)
Click to expand...
Click to collapse
I kept on getting errors even following the instructions to the T. it took me about 2 and a half hours of trying-rebooting and trying again.
But which errros are you recieving?

I always get error code 1

try this unlock toolkit by hasoon2000 .. worked for me ..
http://forum.xda-developers.com/showthread.php?t=2183942

Thanks, tried that too but didn't help.

The only other thing I could suggest is to go back to stock with an RUU and try it all again bro
Sent from my HTC One using xda app-developers app

Yea...I gave a try to that too but I can't figure out CID and other needed ID, getvar in fastboot display nothing related to CID and as I said in main post I can't execute oem commands for flashing. Anything else...

From you've said it's either a custom HBOOT or it's a fake...
Sent from my Nexus 4 using xda premium

If I flash other HBOOT and something go wrong, can I fix things? You can't access fastboot without it and stock recovery is pretty useless.

Jon2555 said:
If I flash other HBOOT and something go wrong, can I fix things? You can't access fastboot without it and stock recovery is pretty useless.
Click to expand...
Click to collapse
Take a photo of the current HBOOT and post it up - we'll go from there

EddyOS said:
Take a photo of the current HBOOT and post it up - we'll go from there
Click to expand...
Click to collapse
Here's the photo of bootloader(it's really bad quality, can't make good one with my One X's camera, letters are too small, I hope it'll help):
I described boot menu in first post.

Jon2555 said:
Here's the photo of bootloader(it's really bad quality, can't make good one with my One X's camera, letters are too small, I hope it'll help):
I described boot menu in first post.
Click to expand...
Click to collapse
Photo doesn't work...

Is this one OK:

Jon2555 said:
Is this one OK:
Click to expand...
Click to collapse
Nope, dead link. just attach it to your post on here

[Q] Stuck On White HTC Boot Screen PLEASE HELP!!!

When I first turn on it'll stay stuck in HTC white screen logo till battery dies.
If I hold volume rocker and power button to try to factory reset it'll try to initiate but then show and a phone logo with red exclamation mark.
I am almost positive i can restore this phone to working order because i remember a while back i put a galaxy s3 into similar condition and restored it using a program.. Ive been out of this stuff for a while so i forgot how i did it with the s3.
I WAS GIVEN THIS HTC AND IT WAS LIKE THIS WHEN I GOT IT.

plotgee said:
When I first turn on it'll stay stuck in HTC white screen logo till battery dies.
If I hold volume rocker and power button to try to factory reset it'll try to initiate but then show and a phone logo with red exclamation mark.
I am almost positive i can restore this phone to working order because i remember a while back i put a galaxy s3 into similar condition and restored it using a program.. Ive been out of this stuff for a while so i forgot how i did it with the s3.
I WAS GIVEN THIS HTC AND IT WAS LIKE THIS WHEN I GOT IT.
Click to expand...
Click to collapse
Don't worry, this problem has cropped up before, and you're right, it is fixable. This is most commonly attributed to some weirdness with the boot.img flashed to your phone. Firstly, do you have a Vivid, Velocity, or Raider? And what provider does it use (e.g. AT&T)?
The first thing you'll want to try and do is pop out the battery, put it back in, then hold "volume down" and "power" until you get to the bootloader (it sounds like you've already gotten there):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You'll notice in the top portion, mine says "unlocked". Yours may say this, but may also say "locked" or "re-locked".
First thing's first; you'll want to download FASTBOOT (http://www.mediafire.com/download/9ylow29klhccc0x/Fastboot.zip)
and the HTC drivers (this is what I had in my flashing folder, so I upped it to mega: https://mega.co.nz/#!CV5RxY7L!Z_VNph4KoGyYKJJjoUCGPAFZ7xZPOWRbvH2UKsCXCi0)
just run the htc drivers and follow directions, nothing too major. Extract the contents of "fastboot.zip" to somewhere that's easy to access and remember (such as c:\FASTBOOT).
We're not going to do anything yet, this is just preparation.
If your bootloader is "locked" or "re-locked", then you can try restoring the original firmware with RUU. You'll want to read this thread first though:
http://forum.xda-developers.com/showthread.php?t=1562890
Always need to be careful.
If you are "unlocked", then you need to boot your phone into the bootloader, select "fastboot" (by pressing power when "fastboot" is highlighted), and connect the phone to your computer via a data usb cable. Then, open a command prompt window, and type in: "<c:\FASTBOOT\fastboot.exe> oem lock", where <c:\FASTBOOT\fastboot.exe> is replaced with the location of your fastboot.exe.
I would recommend flashing the recovery image located in the thread I linked to just before (follow instructions provided), and only THEN applying an RUU update. Which RUU you apply is dependent on which device you have.
If anything is unclear, or you have any questions, PLEASE ask in reply to this post; it's better to go slowly and be sure of what you're doing.
sidenote:
I noticed you said you had previously owned an S3 and managed to fix the problem with that; if you are pretty familiar with flashing roms, you can also try to flash a custom ROM and see if that fixes your problem (guides should be on Vivid General or Q&A).

projectisaac said:
Don't worry, this problem has cropped up before, and you're right, it is fixable. This is most commonly attributed to some weirdness with the boot.img flashed to your phone. Firstly, do you have a Vivid, Velocity, or Raider? And what provider does it use (e.g. AT&T)?
The first thing you'll want to try and do is pop out the battery, put it back in, then hold "volume down" and "power" until you get to the bootloader (it sounds like you've already gotten there):
You'll notice in the top portion, mine says "unlocked". Yours may say this, but may also say "locked" or "re-locked".
First thing's first; you'll want to download FASTBOOT (http://www.mediafire.com/download/9ylow29klhccc0x/Fastboot.zip)
and the HTC drivers (this is what I had in my flashing folder, so I upped it to mega: https://mega.co.nz/#!CV5RxY7L!Z_VNph4KoGyYKJJjoUCGPAFZ7xZPOWRbvH2UKsCXCi0)
just run the htc drivers and follow directions, nothing too major. Extract the contents of "fastboot.zip" to somewhere that's easy to access and remember (such as c:\FASTBOOT).
We're not going to do anything yet, this is just preparation.
If your bootloader is "locked" or "re-locked", then you can try restoring the original firmware with RUU. You'll want to read this thread first though:
http://forum.xda-developers.com/showthread.php?t=1562890
Always need to be careful.
If you are "unlocked", then you need to boot your phone into the bootloader, select "fastboot" (by pressing power when "fastboot" is highlighted), and connect the phone to your computer via a data usb cable. Then, open a command prompt window, and type in: "<c:\FASTBOOT\fastboot.exe> oem lock", where <c:\FASTBOOT\fastboot.exe> is replaced with the location of your fastboot.exe.
I would recommend flashing the recovery image located in the thread I linked to just before (follow instructions provided), and only THEN applying an RUU update. Which RUU you apply is dependent on which device you have.
If anything is unclear, or you have any questions, PLEASE ask in reply to this post; it's better to go slowly and be sure of what you're doing.
sidenote:
I noticed you said you had previously owned an S3 and managed to fix the problem with that; if you are pretty familiar with flashing roms, you can also try to flash a custom ROM and see if that fixes your problem (guides should be on Vivid General or Q&A).
Click to expand...
Click to collapse
I have the vivid , and yes it says *** locked ***
I downloaded and installed everything you listed above and I am currently going through RUU process as I type this..
Thanks, I hope this works.

Fingers crossed here. Let me know what happens.
Sent from my Vivid 4G using xda app-developers app

Alright! So apparently this solution worked (got a PM from OP)!

How to Solve hboot corrupted ?

hello
i try to downgrade hboot to install kitkat on my HTC M7 sprint using this guide
http://forum.xda-developers.com/showthread.php?t=2447531
but i can't flash compleatlty
i stack on installing screen near 70% for more than 1 hour
so i reboot my phone
after reboot i got screen just stayed black dots
when I try to get into Hboot, Fastboot, or a regular boot - all that happens is a black dot screen
how can i solve this
please help
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

shanchu said:
hello
i try to downgrade hboot to install kitkat on my HTC M7 sprint using this guide
http://forum.xda-developers.com/showthread.php?t=2447531
but i can't flash compleatlty
i stack on installing screen near 70% for more than 1 hour
so i reboot my phone
after reboot i got screen just stayed black dots
when I try to get into Hboot, Fastboot, or a regular boot - all that happens is a black dot screen
how can i solve this
please help
Click to expand...
Click to collapse
So you've flashed a verizon hboot on your sprint phone ?
There's still a slim chance to save your phone. even if nothing is displayed on your screen, the hboot might be there and if yes, you should be able to use fastboot commands to flash back the correct verizon hboot. You'll either need to use a Windows 7 pc, Linux or Mac. Windows 8/10 is a no go with hboot 1.44 (fastboot commands won't work). So get your hands on a Win7 pc, install the appropriate drivers and check if your devices is detected with the "fastboot devices" command..

alray said:
So you've flashed a verizon hboot on your sprint phone ?
There's still a slim chance to save your phone. even if nothing is displayed on your screen, the hboot might be there and if yes, you should be able to use fastboot commands to flash back the correct verizon hboot. You'll either need to use a Windows 7 pc, Linux or Mac. Windows 8/10 is a no go with hboot 1.44 (fastboot commands won't work). So get your hands on a Win7 pc, install the appropriate drivers and check if your devices is detected with the "fastboot devices" command..
Click to expand...
Click to collapse
devices is not detected by ubuntu and windows
fast boot says waiting for device
what can i do now?

shanchu said:
devices is not detected by ubuntu and windows
fast boot says waiting for device
what can i do now?
Click to expand...
Click to collapse
What version of windows? It must be 7 or older. But if ubuntu fails to detect fastboot it's probably dead. Maybe someone with a riff box could fix it.

alray said:
What version of windows? It must be 7 or older. But if ubuntu fails to detect fastboot it's probably dead
Click to expand...
Click to collapse
it is windows 7
if dead waht can i do?
any other solution ?
some one says can use riffbox
can i recover with riffbox ?
if can i can search who have riffbox locally

shanchu said:
it is windows 7
if dead waht can i do?
any other solution ?
some one says can use riffbox
can i recover with riffbox ?
if can i can search who have riffbox locally
Click to expand...
Click to collapse
Your local repair shop probably have one. You can also buy one online but honestly, will be cheaper to buy another m7 than a riff box

alray said:
Your local repair shop probably have one. You can also buy one online but honestly, will be cheaper to buy another m7 than a riff box
Click to expand...
Click to collapse
i ask some shop but the not have
if i can recover back i can search near city also
can you tell me any chance to recover with riffbox ?

shanchu said:
i ask some shop but the not have
if i can recover back i can search near city also
can you tell me any chance to recover with riffbox ?
Click to expand...
Click to collapse
Never used one so it's hard to tell but if the riffbox can't fix it, nothing will. Might worth a try depending the price...