Related
I dont think the 3 button recovery mode "fix" that samsung released for Bell Canada i9000m and that was ported to work for other models is really a "Fix".
As dicussed in other threads, the original bug is on the PCB. It's a timing issue on the motherboard. The "fix" installs a software hook in the 4th level bootloader to the 3 buttons in order to trigger the recovery mode.
If you brick your phone such that it does not get to the 4BL stage ...
OR
If your phone freezes even after the 4BL stage ...
then you are **** out of luck.
Only a phone that had the 3BR working before the fix or a phone that gets a MB changed will be able to recover from being bricked.
This fix is only slightly better than installing a software that triggers recovery or using adb to force recovery mode. Basically it only works in conditions where you would not need recovery in the first place.
thats an assumption, but where is the proof and source?
I don't know about you but for me the recovery menu fix works great. I rooted my phone after I used that fix with the update.zip method so unless you have proves I think is better to not scary users.
I thought three limit was cause by the telco not Samsung? Read it from a post where the telco confirm they disable it.
Sent from my GT-I9000 using XDA App
The idea is I don't think Samsung replaced the motherboard of the mobile phones and the prove is that Samsung Canada or something posted a method to enable recovery mode back.
bigl666 said:
thats an assumption, but where is the proof and source?
Click to expand...
Click to collapse
I did say "I think".... but added an ? to the title.
Based my opinion on these posts:
http://forum.xda-developers.com/showpost.php?p=8217641&postcount=390
and the serious part of this one:
http://forum.xda-developers.com/showpost.php?p=8156981&postcount=287
My reply from another thread: http://forum.xda-developers.com/showthread.php?p=8230653
That was my first hypothetis when Samsung released the fix.
That's why I asked technical details and get some after contacting Samsung technical department, to finally speak with a tech, instead of those clueless helpdesk first and secondline helpdesk coworkers. But he couldn't give me more pointers, other than the original working 3br devices do not use the spl at all.
My hypothetis seems right if the bootloader gets overwritten by other firmware who's using spl on the respective partition.
My assumption, like I said before in this thread, is that the original 3br working devices gets triggered via the pcb, which loads the pbl with the safemode, if not on a dedicated module, maybe... That way, the users of such device can always be assured they can flash every firmware. This is how it's done with other many devices too. And that's exactly why I don't buy the story of 'not'-controlled batches by another guy here on the forums in another thread. I can understand why and that's why I'm so disappointed they continue to ship the phone with Android.
If you are like me, you need to test new firmware releases in order to test your own written code in Eclipse. Plus, I want the latest releases...
That's why I suggested to get your mobo replaced now you have the change, before Samsung goes with the spl fix as a standard procedure for future bricked phones.
But, for now, we will not know, unless somebody is disassembling a working 3br and a non working 3br device and have the electronic skills to confirm this.
Click to expand...
Click to collapse
blackdeath09 said:
I don't know about you but for me the recovery menu fix works great. I rooted my phone after I used that fix with the update.zip method so unless you have proves I think is better to not scary users.
Click to expand...
Click to collapse
There is no proof, if there was, there was probably a fix already or at least the technical details published.
xtrememorph said:
I thought three limit was cause by the telco not Samsung? Read it from a post where the telco confirm they disable it.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
No, I got my phone from a Samsung distro, not from any provider and it has 3br disabled.
blackdeath09 said:
The idea is I don't think Samsung replaced the motherboard of the mobile phones and the prove is that Samsung Canada or something posted a method to enable recovery mode back.
Click to expand...
Click to collapse
That could be, then if you have 3br enabled with a firmware without the integrated fix back, it's probably a new phone without replacement.
The prove that a temporary fix exist doesn't mean it's permanent, which is for the original 3br enabled devices.
So then someone should brick his phone after installed the fix and see if he can repair it back (as a user said in the original thread)
blackdeath09 said:
So then someone should brick his phone after installed the fix and see if he can repair it back (as a user said in the original thread)
Click to expand...
Click to collapse
Under what kind of circumstances?
That doesn't prove anything, other than the fix works if the sbl isn't overwritten.
Then flash back to a firmware who does without the fix and tell me the results.
I've read in http://forum.xda-developers.com/showthread.php?p=8230653 that someone flashed back and the fix is gone. Now you have your proof this fix isn't permanent, like I already said a bunch of times. I believe it was firmware JM1 if I can remember correctly. It was tested one time though. Try it and please report your results back.
Proof will come when someone bricks a phone other than by flashing firmware and can not use the 3BR combo even though the "fix" was applied.
Prroving that the "Fix" works is just about impossible. No reports of the condition described above will constitute proof that it works.
I do have an idea for a test:
- With battery fully charged, USB unplugged and phone off,
- Initiate 3BR.
- Calculate time to reach recovery screen.
Compare "fixed" phone with originally working one.
If different assume that fix is not as good as a real working 3BR phone.
My Buddy just had a bad flash and and bricked the phone.. and the recovery saved him so yes it does work....
he did not have the 3 buttons working before but did the update and started flashing roms.. and it saved him... its not a hardware issue.. its always been software.
so it does work.. if this fix didn't come out he would have a good door stop.
TriC_101 said:
My Buddy just had a bad flash and and bricked the phone.. and the recovery saved him so yes it does work....
Click to expand...
Click to collapse
Like I said, proof comes when someone recovers from a brick OTHER than because of a bad flash.
Because, in general, that doesnt touch the BL.
davidke said:
Like I said, proof comes when someone recovers from a brick OTHER than because of a bad flash.
Because, in general, that doesnt touch the BL.
Click to expand...
Click to collapse
why does it really matter? isn't that normally the problem anywayz, bricking from a bad flash?
but then again, this appears to be one of those you can't prove anything to be true, but only to be false scenarios...
TriC_101 said:
My Buddy just had a bad flash and and bricked the phone.. and the recovery saved him so yes it does work....
he did not have the 3 buttons working before but did the update and started flashing roms.. and it saved him... its not a hardware issue.. its always been software.
so it does work.. if this fix didn't come out he would have a good door stop.
Click to expand...
Click to collapse
I disagree.
Without pcb, rom and human-machine-interaction, there is no way the bootloader will load. So you are telling me it's not a hardware issue that 3br isn't working? I fully disagree. IT IS. Why? Because Android already have the recovery / download mode adressesed... Please study mobile phone architecture or at least computer architecture and how the android kernel and os works.
No one knows the exact architecture of sgs here, but one thing is for sure. 3br isn't working, because it doesn't get handled BEFORE spl... And if it is, it's disabled on purpose in bml1 and otherwise there is probably another rom, handling all 3 buttons first, before launching ipl.
Please tell your buddy to flash back to JM1 and let his phone brick and post back your results...
I hope Richthofen and / or some other members can exclude this theory by hexcomparing bml1 from working and not working 3br devices and analyze that, so we can exclude that. If it matches, then it's probably a hardware issue. Like I told you before... Android already adressed the safemode space. So the parameters must come via the 3 buttons by pcb. You are happy now?
Casio1987 said:
I hope Richthofen and / or some other members can exclude this theory by hexcomparing bml1 from working and not working 3br devices and analyze that, so we can exclude that. If it matches, then it's probably a hardware issue. Like I told you before... Android already adressed the safemode space. So the parameters must come via the 3 buttons by pcb. You are happy now?
Click to expand...
Click to collapse
It seems BML1 to BML4 that triggers 3BR recovery mode are differents between countries and could be related to CSC version.
So it seems to be a software problem.
Until you dont flash BLM/SPL everything will be fine, just check before flashing.
I find it hard to believe that it would be a hardware issue.
The first retail European I9000 phones had I9000XXJF3 factory firmware version.
As far as I know all of them had a functional 3-button "wake" function for download and recovery modes.
When Samsung started using I9000XXJM1 as a factory firmware, I have seen only one phone with a functional "3-button wake". And even with that one I could not tell if it was a brand new one or a factory refurbished one.
For some odd reason the first release using the new secondary bootloader was I9000XXJM1. All of the previous versions (from I9000XXJE2 thru I9000XWJFF) have been using the same bootloader. As far as I know none of these phones ever had problems.
Also there is no indication that Samsung would have modified the hardware.
Samsung always makes bulletin about the changes in hardware and I have not seen any. Also the hardware revision has remained the same from the start.
Richthofen said:
I find it hard to believe that it would be a hardware issue.
The first retail European I9000 phones had I9000XXJF3 factory firmware version.
As far as I know all of them had a functional 3-button "wake" function for download and recovery modes.
When Samsung started using I9000XXJM1 as a factory firmware, I have seen only one phone with a functional "3-button wake". And even with that one I could not tell if it was a brand new one or a factory refurbished one.
For some odd reason the first release using the new secondary bootloader was I9000XXJM1. All of the previous versions (from I9000XXJE2 thru I9000XWJFF) have been using the same bootloader. As far as I know none of these phones ever had problems.
Also there is no indication that Samsung would have modified the hardware.
Samsung always makes bulletin about the changes in hardware and I have not seen any. Also the hardware revision has remained the same from the start.
Click to expand...
Click to collapse
Very odd indeed, because how is it possible that some have working 3br and others not with the same firmware jm1, coming from the same csc, coming from the same batch? Maybe the 8gb differs from the 16gb (I don't think so). Maybe asked too much, but it would be great if people can start publishing all their bml's, with the exception of the containing imei.
Because the safemode must be somewhere and it isn't in bml4.
Maybe there is a special ic for it, but it's locked for the 3br disabled phones and it's overridden by the sbl.
Are you sure there isn't a special module with the safemode in it?
That would clarify why the hw still preserves the same revision.
Casio1987 said:
I disagree.
Without pcb, rom and human-machine-interaction, there is no way the bootloader will load. So you are telling me it's not a hardware issue that 3br isn't working? I fully disagree. IT IS. Why? Because Android already have the recovery / download mode adressesed... Please study mobile phone architecture or at least computer architecture and how the android kernel and os works.
No one knows the exact architecture of sgs here, but one thing is for sure. 3br isn't working, because it doesn't get handled BEFORE spl... And if it is, it's disabled on purpose in bml1 and otherwise there is probably another rom, handling all 3 buttons first, before launching ipl.
Please tell your buddy to flash back to JM1 and let his phone brick and post back your results...
Click to expand...
Click to collapse
I do know how phone architecture works and computer architecture as well....... in the end its very simple... it works its saved lots of people from having a bricked phone.. and the recovery mode is different between countries. besides you should not be flashing the SPL/BLM in the 1st place. and like you said your self you don't know how the exact architecture works on the SGS so how can you say its not a software issue. if you fully don't understand it.
Today I though let's get cm9 on my nice nitro.
What did I do:
Rooted and installed cwm bytes version
installed custom 0.3 of kernelpanic
Today I installed cmw from the market and installed the new version.
Then I installed the cm9 but it stated that the sd card was not mounted (sdcard pointer wasn't right or something).
I tried all kind of things, but cmw would not work.
So I tried to install cwm bytes version again
[HOW TO]Install ClockworkMod Recovery The easy way
and did: dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096 and dd if=/sdcard/_ExternalSD/recovery.img of=/dev/block/mmcblk0p6 bs=4096
Then I did a restart
Nothing happened, nothing at all
No screen no download mode
When I connected it to the pc, it has some usb drivers:
qualcomm hs-usb qdloader 9008
Now what?
I am from holland, so getting it back to the US is not a good option, I also don't have an email address from the seller (ebay). I already send him an ebay message, but I don't know if he is still member or something (2 months ago I bought it).
Does someone has a solution?
The name of the windows driver is Qualcomm HS-USB Qdloader 9008
Oh ****, it looks like you flashed CWM to the wrong partition. Um, I think you're going to have to try to unbrick using a .kdz, possibly the SU640 one. My unbricking guide is out of date (my fault, but real life has kept me busy), but all the information you will need is in this thread somewhere. Please read all the posts, particularly ones toward the end of the thread that will tell you how to edit your hosts file and set up a server so that the kdz update tool will let you flash the .kdz file.
Edit, I forgot to mention this will only work if you are able to get into Download Mode. Please confirm if this is the case.
Malnilion said:
Oh ****, it looks like you flashed CWM to the wrong partition. Um, I think you're going to have to try to unbrick using a .kdz, possibly the SU640 one. My unbricking guide is out of date (my fault, but real life has kept me busy), but all the information you will need is in this thread somewhere. Please read all the posts, particularly ones toward the end of the thread that will tell you how to edit your hosts file and set up a server so that the kdz update tool will let you flash the .kdz file.
Edit, I forgot to mention this will only work if you are able to get into Download Mode. Please confirm if this is the case.
Click to expand...
Click to collapse
I doubt it. p6 is the SBL (secondary bootloader), I think emergency mode depends on it.
I cannot get into download mode, I only see ethe qualcomm driver in windows, nothing else. No screen, no nothing.
Your situation is not good. Your best bet at this point is probably getting it repaired by LG/AT&T unless aremcee or someone more knowledgeable than myself can help you rescue it somehow. Whoever's post you followed that told you to flash to p6 was horribly, horribly misguided. Unfortunately, as you know now, flashing roms the manual way can be really dangerous if you overwrite the incorrect partition. I'm sorry it ended the way it did for you...
Yeah I think I screwed up... I just wanted to get ICS on the phone, anyway.
How can I repair it? My seller does not respond, is there a possibility that someone else can get it to at&t for repairs? or wouldn't that be possible?
maybe ask someone to pull (dd if=) their sbl p6 and you could try to overwrite whatever is on yours now.
worth a shot, I know on samsung phones if this happens you need a .pit files, which will help repartition. I dont know if LG has a similar option.
what software do I have to use to get the new p6 on the phone, for samsung there is ODIN, but for lg?
See, that's the thing, the closest thing we have to Odin is the KDZ update tool and as far as I know they both kind of have a caveat of needing the emergency/download mode intact. I really don't know if there is any way to rescue your device without physically getting in it and reflashing, which most people are not equipped to do.
adb probably is no go as well huh? or you would see android/LG driver...
if this was another device I may have more ideas, but I have no exp. with LG.
{tell them you just hooked it up to Itunes to sync your playlist....an it went all weird.. hahahah}
Not sure how releveant this is but I think one of the Qualcomm Phone tools may have an option for raw memory read & raw memory write.
For example READ_MEM from address 0x0200000 to 0x0250000 (from a device with a working sbl of course) and dump it to a file.
Then WRITE_MEM and cross your fingers. Very dangerous and would take some research to find the sbl memory address.
A long shot more geared towards the technically inclined.
Is there someone who can make my phone work again? I can pay you for it, otherwise I will sell the phone, broken as it is.
My seller won't respond, so I have nowhere to go. If someone want to help me, you are welcome.
search an try a jtag solution
roydejong said:
Is there someone who can make my phone work again? I can pay you for it, otherwise I will sell the phone, broken as it is.
My seller won't respond, so I have nowhere to go. If someone want to help me, you are welcome.
Click to expand...
Click to collapse
You know, you could always ship it off to LG. I sent them mine after having the EXACT same problem, and they fixed it and it's on its way home right now!
Did you have to pay for this? Do you have the contact info? Thanks.
foxdl99 said:
Did you have to pay for this? Do you have the contact info? Thanks.
Click to expand...
Click to collapse
Don't have to pay, they can't turn it on, so how would they know ? Just go to their website and fill out a warranty support form.
rani9990 said:
Don't have to pay, they can't turn it on, so how would they know ? Just go to their website and fill out a warranty support form.
Click to expand...
Click to collapse
Does it have to be within one year of original purchase and do you have to show proof of original purchase?
Sent from my LG-P930 using xda app-developers app
i can help with jtag method
or you can buy the medusa box (like me) but it's not easy to solder the wire
nickmatine said:
i can help with jtag method
or you can buy the medusa box (like me) but it's not easy to solder the wire
Click to expand...
Click to collapse
i have the same issue with my lg connect ms 840.
would you mind to share how to unbrick it.
i only have riff box here
tyvm
For the jtags you first need to check if the cpu is supported. If it is, all you have to do is disassemble the device, locate the pins solder up and go for it. Some other model may have same pinout. Just make sure it is same layout, and check if vref and gnd are in the same place. If successful connection is achieve, you just need converted files from box support. Send them full stock rom for your model. If cpu is not supported, it will take longer and will be harder. Get into the forum support of either, medusa and riff. For the OP, see if you can send it to LG but if you can't, someone at forum that lives nearby you could help you. Only solution afaik is jtag.
Sent from my Abacus
so i was flashing a nougat 7.0 update on moto z play and then all of a sudden my phone wouldnt even power on the screen was all black so i decided to use blank flash. Blank flash did take me to the bootloader but even when trying to boot to recovery and system it wont work.
help plz.
Jaderalves said:
In Device Manager how is it listed? Fastboot Android S
Click to expand...
Click to collapse
what do you mean
Jaderalves said:
In Device Manager how is it listed? Fastboot Android S
Click to expand...
Click to collapse
is their any ways for me to access recovery and my device because at the moment I'm just stuck on the fast boot screen if so please tell me btw thanks for replying.
ahmed12389 said:
is their any ways for me to access recovery and my device because at the moment I'm just stuck on the fast boot screen if so please tell me btw thanks for replying.
Click to expand...
Click to collapse
Do you see the device listed in Windows?
Flashqueen said:
Do you see the device listed in Windows?
Click to expand...
Click to collapse
yes I can see it
Flashqueen said:
Do you see the device listed in Windows?
Click to expand...
Click to collapse
what do you suggest I do
ahmed12389 said:
what do you suggest I do
Click to expand...
Click to collapse
Have you flashed the stock ROM onto your device? What bootloader version or stock ROM build did you have before you flashed the stock 7.0 build and took the update?
Downgrading to older stock firmware and then attempting to update is generally what caused that hard brick. If you can let us know what device/territory you had, we can try to point you to the right firmware to flash.
echo92 said:
Have you flashed the stock ROM onto your device? What bootloader version or stock ROM build did you have before you flashed the stock 7.0 build and took the update?
Downgrading to older stock firmware and then attempting to update is generally what caused that hard brick. If you can let us know what device/territory you had, we can try to point you to the right firmware to flash.
Click to expand...
Click to collapse
Yes I have flashed stock firmware on my device I remember downgrading to marshmallow then updating back to nougat then my device fully shut down it was all black. After this incident, i did what you would normally do and that was to use blank flash to at least get the bootloader back, as I did get the bootloader I could not use the boot options such as recovery mode. so I am basically stuck on the bootloader and can do nothing. My device is an addison XT1635-02 and before I flashed nougat ota I had the marshmallow December security update.
echo92 said:
Have you flashed the stock ROM onto your device? What bootloader version or stock ROM build did you have before you flashed the stock 7.0 build and took the update?
Downgrading to older stock firmware and then attempting to update is generally what caused that hard brick. If you can let us know what device/territory you had, we can try to point you to the right firmware to flash.
Click to expand...
Click to collapse
I also believe my device is hard bricked as I cant access boot options at all it just keeps boot looping once I try to access a boot option. also is it normal for my bootloader to say that my software status is modified because I think after you flash blank flash your software status modified. finally, I have been trying to flash stock firmware but for some reason, gpt and bootloader.img always fail to flash. Thanks for the reply I hope you can help.
echo92 said:
Have you flashed the stock ROM onto your device? What bootloader version or stock ROM build did you have before you flashed the stock 7.0 build and took the update?
Downgrading to older stock firmware and then attempting to update is generally what caused that hard brick. If you can let us know what device/territory you had, we can try to point you to the right firmware to flash.
Click to expand...
Click to collapse
this is a dumb question but do you think that it is possible to get out of a hard brick without sending it to a moto service center.
ahmed12389 said:
this is a dumb question but do you think that it is possible to get out of a hard brick without sending it to a moto service center.
Click to expand...
Click to collapse
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.
echo92 said:
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.
Click to expand...
Click to collapse
ok the thing is I am certain I used the wrong blank flash zip therefore meaning that I flashed the wrong things this is probably why I'm boot looping do you have any idea how to revert the changes of blank flash so I can flash the propper blank flash. Is their even any blank flash for Moto z play anyways
echo92 said:
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.
Click to expand...
Click to collapse
I was flashing the July security patch stock firmware and it's giving me these errors
echo92 said:
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.
Click to expand...
Click to collapse
if i flash that stock frimware it takes straight to 7.1.1 is that correct
echo92 said:
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.
Click to expand...
Click to collapse
is blank flash universal and works for all version and models for Motorola phone or is their specific ones because if their is I might have used the wrong one
ahmed12389 said:
is blank flash universal and works for all version and models for Motorola phone or is their specific ones because if their is I might have used the wrong one
Click to expand...
Click to collapse
As far as I know, blankflashes are CPU specific, and may also be device specific, though we've had some success using a Moto Z2 play blankflash to rescue Moto Z Play devices that are hard bricked. There's some more info here https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page19 and here https://forum.xda-developers.com/showpost.php?p=73474192&postcount=249
Which blank flash did you use? Also, which July security patch firmware are you flashing? sounds like your need 7.0 or 7.1.1 firmware to proceed. That firmware link would take you up to 7.1.1, yes, but I would advise not to downgrade in future.
Also, please edit your posts rather than making new replies. I understand you're wanting to get your device fixed without paying a lot of money to fix it, give us time to respond.
echo92 said:
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.
Click to expand...
Click to collapse
I just checked its all good i was using the right one. it appears that if you use blank flash, in general, it will modify your software status. I will flash that stock rom I just hope it would work and yes i was flashing the july marshmallow 6.0.1 update and it had no effect on my phone what so ever lets hope this 7.1.1 does. also sorry for all these replies I am in desperate need for my phone and I'm not thinking straight
ahmed12389 said:
I just checked its all good i was using the right one. it appears that if you use blank flash, in general, it will modify your software status. I will flash that stock rom I just hope it would work and yes i was flashing the july marshmallow 6.0.1 update and it had no effect on my phone what so ever lets hope this 7.1.1 does. also sorry for all these replies I am in desperate need for my phone and I'm not thinking straight
Click to expand...
Click to collapse
If your device was ever on stock Nougat (7.0 or 7.1.1), then flashing that marshmallow ROM won't likely work in repairing your bootloader. You need a firmware that is the same or newer than the latest firmware your device had. Downgrading stock firmware does not usually downgrade your bootloader, hence the corruption and need to have same or newer firmware to repair. Your bootloader would otherwise reject old firmware via preflash validation errors.
Hopefully the 7.1.1 firmware will help fix things. You will lose data however in the process of flashing your device, so hopefully you have backups.
echo92 said:
As far as I know, blankflashes are CPU specific, and may also be device specific, though we've had some success using a Moto Z2 play blankflash to rescue Moto Z Play devices that are hard bricked. There's some more info here https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page19 and here https://forum.xda-developers.com/showpost.php?p=73474192&postcount=249
Which blank flash did you use? Also, which July security patch firmware are you flashing? sounds like your need 7.0 or 7.1.1 firmware to proceed. That firmware link would take you up to 7.1.1, yes, but I would advise not to downgrade in future.
Also, please edit your posts rather than making new replies. I understand you're wanting to get your device fixed without paying a lot of money to fix it, give us time to respond.
Click to expand...
Click to collapse
oh my freaking god you fixed it!!! you are literraly my idol thanks to you i dont need to take it to service from now on I'm never flashing again. but thank you very much you fixed my phone you absolute legend.
ahmed12389 said:
what do you mean
Click to expand...
Click to collapse
how is it recognized by the PC in device manager?
I have a used ellipsis 8 qtaqz3 that I want to root. I would like an admin to help me so I can upload the rom here for others to have. It has Android 4.4.2 on it and it has been reset.
Please advise Admins!
Thanks,
Mark
mcorkins said:
I have a used ellipsis 8 qtaqz3 that I want to root. I would like an admin to help me so I can upload the rom here for others to have. It has Android 4.4.2 on it and it has been reset.
Please advise Admins!
Thanks,
Mark
Click to expand...
Click to collapse
I can give you root, but I need the original rom to change it.
[email protected]
Android 4.4.2?????
I have a QTAQZ3 currently running 4.2.2. I captured the OTA url and downloaded an update bin file. I'm not exactly sure how bins compare to flashable zips, nor do I know what to do with a bin file. It seems as though this file has been hard to come by. I am hoping that by posting it, someone with the right know-how can help us fix all these bricked tablets.
https://drive.google.com/open?id=1LmyrA3eGcVL3sCMB3okBdsoqA0Gv5RZE
I've looked through every possible thread on the internet. I rooted and then the device updated now it is bricked.
Does anyone have any of the original firmware?? Pleassseeeee.
I can get it into download mode and recovery but that does nothing.
I really don't want to replace the logic board I can donate!
sirtweak0 said:
I've looked through every possible thread on the internet. I rooted and then the device updated now it is bricked.
Does anyone have any of the original firmware?? Pleassseeeee.
I can get it into download mode and recovery but that does nothing.
I really don't want to replace the logic board I can donate!
Click to expand...
Click to collapse
My device faced the same, "I rooted and then the device updated now it is bricked."
Did you get the original firmware? or Did you manage to solve it?
Thank you in advance.
Please help.
I don't know what happened LG up went wonky and I had to reflash didn't know who h version of the os I was on and may have triggered the downgrade thing not sure what that is. I can now flash any of the kdz that are for my model 9 or 10 version of Android. I've tried qfil and cdma tools everything I can think of to get the modem and data working. I've even poured through the efs of my phone and one not broken but without a firehose I am screwed am I right? I have never been so frustrated with a phone and I've been doing Android since the beginning and am no stranger to 9008 and edl. I used to work on symbian os way back when so I understand the systems for radios but I have overlooked or misunderstood something. I need the bootloader unlocked than I could totally flash new abl and everything else. I may resolve to using a xiaomi firehose and just spraying away find an sm8150 a f let it rip. Idk just asking in case anyone knew something I don't.
atsuisofu said:
I don't know what happened LG up went wonky and I had to reflash didn't know who h version of the os I was on and may have triggered the downgrade thing not sure what that is. I can now flash any of the kdz that are for my model 9 or 10 version of Android. I've tried qfil and cdma tools everything I can think of to get the modem and data working. I've even poured through the efs of my phone and one not broken but without a firehose I am screwed am I right? I have never been so frustrated with a phone and I've been doing Android since the beginning and am no stranger to 9008 and edl. I used to work on symbian os way back when so I understand the systems for radios but I have overlooked or misunderstood something. I need the bootloader unlocked than I could totally flash new abl and everything else. I may resolve to using a xiaomi firehose and just spraying away find an sm8150 a f let it rip. Idk just asking in case anyone knew something I don't.
Click to expand...
Click to collapse
Wdym? You wanna replace your CPU? I don't know if that's the best idea if you don't have any other special tools for it, but you can do it if you want. The firehose won't get leaked for a while but the octopus box tool will hopefully support it soon enough, so then you could pay someone to fix it