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?
Related
HTC implemented security on their newer generation phones. This flag, called @secuflag, controls whether your phone has
it's NAND or flash unlocked. Most noticeably, S-ON (security on) will read-lock your /system and /recovery partition, to name a few. Also, secuflag controls whether zip files being flashed through recovery or fastboot, are signed by HTC.
The now notorious S-OFF (security off) will disable this NAND security.
Since we are unable to access the Radio NVRAM itself (where secuflag is stored), we turned our attention to HBOOT.
AlphaRev has patched HBOOT images for several phones, whereas the HTC Desire (GSM) was our first victim.
Soon to be supported devices:
HTC Legend GSM
HTC Aria GSM (Liberty)
HTC Wildfire GSM (Buzz)
The following patches were made:
First and foremost, the security flag is ignored. HBOOT now always thinks the phone is S-OFF.
Second, Fastboot extended commands are enabled. This is similar to engineering HBOOTS, these allow you to use commands like 'fastboot flash system system.img' (flashing a system image), or 'fastboot boot boot.img' (downloading and directly booting a kernel image and ramdisk).
Is there any risk involved?
Yes, there is. Flashing HBOOT will flash a critical part of your phone, if that gets corrupted, your phone WILL be bricked.
We do not accept any responsibility for bricked phones, even though we've attempted to make the actual flashing method as safe as possible.
If your phone no longer turns on anymore, please return to HTC for warranty purposes.
Should you still run this hack/program, you then hereby accept full responsibility.
So how does this work?
The image provided is an ISO image. You can either burn that on CD, and boot it. Instructions will be provided when you run the CD.
The actual tool is packaged in a Linux livecd, to ensure maximum compatibility.
On a sidenote: yes, you should be able to run this in VMWare or Virtualbox, as long as you enable the USB device to be routed to the livecd running.
Will my phone stay S-OFF forever?
Yes and no. As soon as you decide to flash a stock RUU that has a HBOOT update in it, this hacked HBOOT will be overwritten.
You do have the option to remove the HBOOT update from the rom.zip inside the RUU. Since your phone no longer checks signatures, you could easily do that.
Also, you then still have the option to flash custom recovery, or different kernels using the fastboot functions described above (fastboot flash, et al).
http://alpharev.shadowchild.nl/
http://forum.xda-developers.com/showthread.php?t=794314&page=5 (Desire thread)
{
"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"
}
NIIIICE *cheer*
I cant wait for this to arrive.
That are awesome news
Sent from my HTC Wildfire using XDA App
That means we can flash new roms (or single images) via `adb fastboot [...]`?
Great news tho.
Sent from my HTC Wildfire using XDA App
nice, keepup good work.
p.s. i hate word "soon", hope its soon not later
Just tryd this on my HTC Desire.. (so dont try it on wildfire yet)
Im soooooooo happy right now
Agghh, I loaded up the RUU with the .25 image, and now im locked in s-on. Can't wait for this to come out =) no more HTC stock images for me =)
Wow
Thanx to IEF @ alpharev my wildfire is now s-off!!!!!! damn so nice... thanx man!
Is it out for the wildfire then?
Nice one.
what version of hboot is suported? lots of peopel flashed froyo ruu as i see in treads
updated first post
Very nice, were do i get it from?
you lucky sob
whats the issues with having nand security off?
and what real benefits will we see from this?
Sorry for asking maybe quite numb questions
Nice leaf!
Is it out officially for the wildfire yet Danne?
Phinxy said:
Nice leaf!
Click to expand...
Click to collapse
You know now when autumn have came alot of leaf is flying around in the air
tigger69 said:
Is it out officially for the wildfire yet Danne?
Click to expand...
Click to collapse
Not yet but now when its proven it wont be long
Good news to see it working
Thank You. Thank You. Thank You =)
I have a smile on my dial, was kickin meself last week when i put on the RUU_Buzz_HTC_WWE_1.25.405.1_Radio_13.45.55.24_3.35.15.31_release_142189_signed rom and found I could no longer flash stuff.
Gonna make sure I never flash a boot image again once this is done.
Isn't this what Unrevoked Forever does?
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
So, my friend recently bought a water damaged ZR online (don't ask me why, I don't know why would he either), and the issue seems to be severe.
The phone won't boot at all, there's nothing, when I plug it in, no charging animations, nothing comes up.
However we did notice one thing, we could still access the QPST when we plug it into a computer, and the app does recognize it.
The problem now is that I've never used QPST and tbh, I don't even know what exactly it's for.
It's the only thing we could access, the phone doesn't boot into bootloader mode either.
At this point, is the device still recoverable or a motherboard replacement is a must?
Thanks,
no flashtool? no fastboot?
the kernel won't boot up? then you never know what is going on!
so let's flash with qpst => www.youtube.com/watch?v=D-YmQ_8OVuY
after done if you get to kernel and could get to recovery you're the locky person, after that you can see the error massages from kernel or even better log it! or to see if things going up or not! you might need a new lcd as it might be broken because of the water damage (it's the first thing that damage after water damage).
hope you get successfully bring back the phone
sijav said:
no flashtool? no fastboot?
the kernel won't boot up? then you never know what is going on!
so let's flash with qpst => www.youtube.com/watch?v=D-YmQ_8OVuY
after done if you get to kernel and could get to recovery you're the locky person, after that you can see the error massages from kernel or even better log it! or to see if things going up or not! you might need a new lcd as it might be broken because of the water damage (it's the first thing that damage after water damage).
hope you get successfully bring back the phone
Click to expand...
Click to collapse
Alright, thanks, time to fire up my virtual machine.
sijav said:
no flashtool? no fastboot?
the kernel won't boot up? then you never know what is going on!
so let's flash with qpst => www.youtube.com/watch?v=D-YmQ_8OVuY
after done if you get to kernel and could get to recovery you're the locky person, after that you can see the error massages from kernel or even better log it! or to see if things going up or not! you might need a new lcd as it might be broken because of the water damage (it's the first thing that damage after water damage).
hope you get successfully bring back the phone
Click to expand...
Click to collapse
Ran into trouble already, it could only boot into Download Mode, thus I can't even get Service Programming working.
{
"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"
}
EDIT: After looking everywhere, I think I might need MPRG8064.hex and some other MBN files to get it working. I have no idea how to obtain the files, I mean no one has the files for ZR.
Perhaps anyone with a working ZR could try to dump them out for me?
EDIT2: Found them, but I can't get it to work properly, whenever I try in eMMC Download App and hit download, I just get Image Download Failed. Cookie not received.
I think it has something to do with the locked bootloader.
EDIT3: Nope, apparently I can't just grab some random hex and mbn files. I need a partition table in XML format, I need someone to make an XML for me with every partition laid out, anyone?
@341464 wow! it has more than 25 partitions! how can I do it just point me to a correct direction and I will do it for you
sijav said:
@341464 wow! it has more than 25 partitions! how can I do it just point me to a correct direction and I will do it for you
Click to expand...
Click to collapse
Tbh, I don't even know how to do this. Also I'm not sure whether the Hex and MBN files work, they're probably device specific.
There's this Chinese post mentioning how to dump these files, but I'm like extremely confused.
http://blog.csdn.net/benjaminwan/article/details/8854437
(I can read in Chinese, but Google Translate should work.)
EDIT: Apparently MBN files should have every partitions laid out, change the extension name to img and analyze it, we should be able to get an XML.
But I need someone to dump the MBN file first.
I very much doubt that this device can be recovered, due to the locked bootloader, LB might lock out the entire download mode from working.
341464 said:
Tbh, I don't even know how to do this. Also I'm not sure whether the Hex and MBN files work, they're probably device specific.
There's this Chinese post mentioning how to dump these files, but I'm like extremely confused.
http://blog.csdn.net/benjaminwan/article/details/8854437
(I can read in Chinese, but Google Translate should work.)
EDIT: Apparently MBN files should have every partitions laid out, change the extension name to img and analyze it, we should be able to get an XML.
But I need someone to dump the MBN file first.
I very much doubt that this device can be recovered, due to the locked bootloader, LB might lock out the entire download mode from working.
Click to expand...
Click to collapse
really? umm I thought lb is just for fastboot not download mode as everything can be flash in flashtool download mode! (which ofcourse needs cert .sin files to flash!)
sijav said:
really? umm I thought lb is just for fastboot not download mode as everything can be flash in flashtool download mode! (which ofcourse needs cert .sin files to flash!)
Click to expand...
Click to collapse
According to the posts there, when you try to utilize download mode you'll get an error if you have LB.
341464 said:
According to the posts there, when you try to utilize download mode you'll get an error if you have LB.
Click to expand...
Click to collapse
damn you're right! this device can't be flashable! it needs ub!
sry pal but if anything else you need and you think it can be fixed just ask!!
where i can download mpgr 8064 and patition layout. for zr, i have same problem with my zr
Hi brothers i have a problem with my Nexus 6. Please help to resolve that rpoblem. Thanks for all to 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"
}
You've posted some pictures, but that isn't telling anyone anything. Care to describe your problem?
And also make the title a bit more meaningful...?
https://forum.xda-developers.com/announcement.php?f=3708
3. Post using a clear and descriptive subject and message.
You're most likely to receive a helpful answer to your question, if you use a short subject title that describes your problem and a message that explains in detail, what your problem is and what you've done to try solving it.
Strephon Alkhalikoi said:
You've posted some pictures, but that isn't telling anyone anything. Care to describe your problem?
Click to expand...
Click to collapse
have a problem with loading android. and i dont know what i do. i am not proffesional =)
Glen2017 said:
have a problem with loading android. and i dont know what i do. i am not proffesional =)
Click to expand...
Click to collapse
Don't need to be a professional, just give us more specific info like:
What are you trying to install?
What version of Android are you on?
What, exactly, are the steps you've used so far?
We need as much detail as you can give
garywojdan81 said:
Don't need to be a professional, just give us more specific info like:
What are you trying to install?
What version of Android are you on?
What, exactly, are the steps you've used so far?
We need as much detail as you can give
Click to expand...
Click to collapse
1. Android 7.0
2.Try to Nexus Root Toolkit for resolve problem unlock.
3. Try to install android 7.0 from NRT
4. But not working and phone stuck in google logo.
P.S. fastboot oem unlock not work
Glen2017 said:
1. Android 7.0
2.Try to Nexus Root Toolkit for resolve problem unlock.
3. Try to install android 7.0 from NRT
4. But not working and phone stuck in google logo.
P.S. fastboot oem unlock not work
Click to expand...
Click to collapse
Your first mistake was in trying to use the toolkit. If you've never used fastboot before, learn to use it before trying to use a toolkit. In order to unlock you need to be in Android, need to enable developer options in settings, enable OEM unlock in developer options, shut off the N6, and then enter bootloader mode. Only then will fastboot oem unlock work.
Since you're in a bootloop, your immediate tasks are to enter the recovery and perform a factory reset. If those fix the bootloop, then follow the guidance above. Otherwise you need to flash one of Google's OTA zips through the recovery, then factory reset, and then follow the guidance above.
There are help guides in the general section that you want to read and understand, before you accidentally turn your N6 into a paperweight.
Strephon Alkhalikoi said:
Your first mistake was in trying to use the toolkit. If you've never used fastboot before, learn to use it before trying to use a toolkit. In order to unlock you need to be in Android, need to enable developer options in settings, enable OEM unlock in developer options, shut off the N6, and then enter bootloader mode. Only then will fastboot oem unlock work.
Since you're in a bootloop, your immediate tasks are to enter the recovery and perform a factory reset. If those fix the bootloop, then follow the guidance above. Otherwise you need to flash one of Google's OTA zips through the recovery, then factory reset, and then follow the guidance above.
There are help guides in the general section that you want to read and understand, before you accidentally turn your N6 into a paperweight.
Click to expand...
Click to collapse
Thank you very much for help. Everything works perfectly. :good: I am very happy
By mistake I reemplace the Abl_a instead laf_a and phone gets in that State, LG up doesnt recognize the phone only says Unknow model and doesnt let me get the Flash screen , lg flashtool isnt working neither, pls 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"
}
Madness_logic said:
By mistake I reemplace the Abl_a instead laf_a and phone gets in that State, LG up doesnt recognize the phone only says Unknow model and doesnt let me get the Flash screen , lg flashtool isnt working neither, pls help
View attachment 5166381View attachment 5166383
Click to expand...
Click to collapse
Well first, you're posting in the wrong forum for help of this sort. This is for roms, kernels etc, for problems like this it should be in questions and answers.
Anyway, you don't say what firmware you're running? AT&T? Sprint? T-mo? When u say u replaced the abl_a instead of laf_a, do u mean u erased the abl_a instead of laf_a?
Assuming that's what u meant, just mention which version firmware you're running and I'd bet someone has an abl_a for it.
cheers
AsItLies said:
Well first, you're posting in the wrong forum for help of this sort. This is for roms, kernels etc, for problems like this it should be in questions and answers.
Anyway, you don't say what firmware you're running? AT&T? Sprint? T-mo? When u say u replaced the abl_a instead of laf_a, do u mean u erased the abl_a instead of laf_a?
Assuming that's what u meant, just mention which version firmware you're running and I'd bet someone has an abl_a for it.
cheers
Click to expand...
Click to collapse
Oh thanks, i dont know how to send the post overthere, but i will do it, lineageOs 17.1. on a At&t lg variant, and nope, i send laf.img to Abl_a, and it was v35eng.img the one i need to send, i get distracted and after that, phone enter in that status, they tell me about Box service, looks like is the only method
Madness_logic said:
Oh thanks, i dont know how to send the post overthere, but i will do it, lineageOs 17.1. on a At&t lg variant, and nope, i send laf.img to Abl_a, and it was v35eng.img the one i need to send, i get distracted and after that, phone enter in that status, they tell me about Box service, looks like is the only method
Click to expand...
Click to collapse
I don't think you need any 'service'. It sounds like your situation isn't that dire. You could just send the v35eng to abl_a now. You may think you're stuck because the phone won't boot, so from the directions, to get to edl, the phone should be booted...
but that's not true. You can get to edl mode (qfil) from any screen. Try this: hold down all 3 buttons for about 5 secs or so. Wait until the screen changes (from whatever it was prior), then keep the pwr and vol - held, but press on off on off on off the vol+ key. Make sure the usb cable is plugged in pc when doing this.
You should hear the windows 'chime' sound indicating a edl connection. Then use qfil to flash the v35eng.
cheers
Have You unbricked it?
Kakanman said:
Have You unbricked it?
Click to expand...
Click to collapse
yes, sorry for the late answer, i forgot to close the topic, i buy this service and goes like charm, they had the medusa box (200$ on ebay) and was faster, less than 40 min and they install all again the system, even unlock again the bootloader
Madness_logic said:
yes, sorry for the late answer, i forgot to close the topic, i buy this service and goes like charm, they had the medusa box (200$ on ebay) and was faster, less than 40 min and they install all again the system, even unlock again the bootloader
Click to expand...
Click to collapse