Related
So it seems like we'll need to fight over at the Microsoft forums if we're to try to stay up-to-date. I need you to contribute to my post over at msdn here: http://forums.create.msdn.com/forums/p/78753/476964.aspx#476964
Maybe if enough of us hit'em, we can get some kind of answer. Dev phones should have been the first to be updated.
Still no updates for Taylor.
It says in the forums that you linked to that there will be no updates for the Samsung Taylor phones.
the92playboy said:
It says in the forums that you linked to that there will be no updates for the Samsung Taylor phones.
Click to expand...
Click to collapse
Seems like there won't be and update for LG Panthers either.
Anyone wanna trade for an Android device?
Might be a newb question here but....
Did people have to pay for these developer phones? Or did MS just send them out to registered/respected developers?
I suppose, you can flash your phone with the Omnia 7/Quantum ROM at your own risk.
the92playboy said:
Might be a newb question here but....
Did people have to pay for these developer phones? Or did MS just send them out to registered/respected developers?
Click to expand...
Click to collapse
Yup, Microsoft just sent them out.
day2die said:
I suppose, you can flash your phone with the Omnia 7/Quantum ROM at your own risk.
I would like to give th Quantum ROM a try , but I do not know where to start. I am a Bell user in Canada so I think they have the Quantum. I used to flash old WM and Android Devices all the time, but WP7 is new to me. Anyone have a thread or no if anyone has sucessfully flashed a LG Panther to anything else? I can get into a bootloader, but it is probably just Microsofts bootloader.
Click to expand...
Click to collapse
NevinM said:
day2die said:
I suppose, you can flash your phone with the Omnia 7/Quantum ROM at your own risk.
I would like to give th Quantum ROM a try , but I do not know where to start. I am a Bell user in Canada so I think they have the Quantum. I used to flash old WM and Android Devices all the time, but WP7 is new to me. Anyone have a thread or no if anyone has sucessfully flashed a LG Panther to anything else? I can get into a bootloader, but it is probably just Microsofts bootloader.
Click to expand...
Click to collapse
Looks like it's really possible, because i succesfully connected to the phone using QXDM, and even downloaded NAND's image (it's raw, so for extracting page size required, because size in the partition table is relative to page size). Though may flash it, i think bootloader will work. But you probably can get bricked device. Unfortunally i have no enough time for explorations.
Click to expand...
Click to collapse
Useless guy said:
Looks like it's really possible, because i succesfully connected to the phone using QXDM, and even downloaded NAND's image (it's raw, so for extracting page size required, because size in the partition table is relative to page size). Though may flash it, i think bootloader will work. But you probably can get bricked device. Unfortunally i have no enough time for explorations.
Click to expand...
Click to collapse
I think flashing the unbranded Optimus 7 ROM would be the best bet for us. There is a registry key named "HasKeyboard" that's defaulted to 0 that we can change to 1. That might be the way to go. Also I'm wondering if we'd have to go the goldcard method to move over to a Quantum or Optimus rom.
The problem is I don't have another phone and there's no MTTY process to unbrick our phones so I'm a little hesitant to try.
fb401 said:
Useless guy said:
I think flashing the unbranded Optimus 7 ROM would be the best bet for us. There is a registry key named "HasKeyboard" that's defaulted to 0 that we can change to 1. That might be the way to go. Also I'm wondering if we'd have to go the goldcard method to move over to a Quantum or Optimus rom.
The problem is I don't have another phone and there's no MTTY process to unbrick our phones so I'm a little hesitant to try.
Click to expand...
Click to collapse
Goldcard isn't required. Only HTC devices require it.
I've dumped my ROM, so if bootloader will work (i hope), device can be easily flashed.
Is anyone wanna to try? QPST can flash certain partitions (looks like only dsp1 and efs are required for succesful update). Unfortunally i can't risk my phone, because i'm developing an application.
Click to expand...
Click to collapse
Not being rude, but are people complaining that a phone that they received for free is not getting the update and not being continued? If you never paid anything for it in the first place, what are you out then?
the92playboy said:
Not being rude, but are people complaining that a phone that they received for free is not getting the update and not being continued? If you never paid anything for it in the first place, what are you out then?
Click to expand...
Click to collapse
Not every got it free.
Me to...
I am not sure if it is worthwhile attempting a flash. The problem is we are all developers and having no device is probably not worth the risk. I have not flashed anything WP7 so I am pretty hesitant. Is this the link to flashing info you guys are considering?
http://forum.xda-developers.com/showthread.php?t=935605
In reading the other threads, there is no real confirmation on the Panther not getting updated. It is clear the the Taylor will not. I am curious if we are running the exact ROM that another device is? If so, ROM from those devices may work. I am trying to remember what the download name was (was it Pacific or something?). I deleted the file. If I still had it I would consider giving flashing a try. I wish Microsoft had not shut down the microsoft connect site for these phones. Any thoughts?
the92playboy said:
Not being rude, but are people complaining that a phone that they received for free is not getting the update and not being continued? If you never paid anything for it in the first place, what are you out then?
Click to expand...
Click to collapse
I got mine off of eBay due to it being the best keyboard phone out at the time (the Quantum is a joke), so it wasn't free for me. Once we get a HTC 7 Pro here that's compatible with AT&T's 3G bands, I'll switch over to that.
NevinM said:
I am not sure if it is worthwhile attempting a flash. The problem is we are all developers and having no device is probably not worth the risk. I have not flashed anything WP7 so I am pretty hesitant. Is this the link to flashing info you guys are considering?
http://forum.xda-developers.com/showthread.php?t=935605
In reading the other threads, there is no real confirmation on the Panther not getting updated. It is clear the the Taylor will not. I am curious if we are running the exact ROM that another device is? If so, ROM from those devices may work. I am trying to remember what the download name was (was it Pacific or something?). I deleted the file. If I still had it I would consider giving flashing a try. I wish Microsoft had not shut down the microsoft connect site for these phones. Any thoughts?
Click to expand...
Click to collapse
I was thinking more the Europe Open Optimus 7 rom here: http://forum.xda-developers.com/showthread.php?t=935578
Like you said, I can't be without a device so I'm really hesitant to try flashing
Well there is going to be a point where and update or feature will make our phones aka gw910 or Taylor completely useless as for development or testing, so this is something to consider.
Yeah connect has been down since a long time ago I have been struggling to find the FW file provided in the msdn/connect/internet forums, I’m guessing the only way now is to contact either a developer/evangelist/god/msdn who has that file available in storage, with the firmware we can create our own updated custom FW way easier than creating one from scratch and/or experiment with other FW like the optimus 7/Q.
And idea can we consider spoofing the gw910 to an optimus 7/Q .7004 using the registry editor? Making ZUNE update just the components needed.
also im willing to give it a go flashing mi gw910 UsellesGuy any info on how can i dump mi firmware. and posible explanation as in how to recover.I read the bootloader post before but is there anything else i need ?
dragoxt said:
Well there is going to be a point where and update or feature will make our phones aka gw910 or Taylor completely useless as for development or testing, so this is something to consider.
Yeah connect has been down since a long time ago I have been struggling to find the FW file provided in the msdn/connect/internet forums, I’m guessing the only way now is to contact either a developer/evangelist/god/msdn who has that file available in storage, with the firmware we can create our own updated custom FW way easier than creating one from scratch and/or experiment with other FW like the optimus 7/Q.
And idea can we consider spoofing the gw910 to an optimus 7/Q .7004 using the registry editor? Making ZUNE update just the components needed.
also im willing to give it a go flashing mi gw910 UsellesGuy any info on how can i dump mi firmware. and posible explanation as in how to recover.I read the bootloader post before but is there anything else i need ?
Click to expand...
Click to collapse
Microsoft delivers updates using binary patches, they apply only to concrete file version, else they will be broken (or updating will be failed).
Thank you, but i think better way is to wait a bit, until situation about updates will clear up. If update will be not received - i'll begin my work
Useless guy said:
Microsoft delivers updates using binary patches, they apply only to concrete file version, else they will be broken (or updating will be failed).
Thank you, but i think better way is to wait a bit, until situation about updates will clear up. If update will be not received - i'll begin my work
Click to expand...
Click to collapse
On twitter I've tired contacting @winphonesupport as far as our phones being updated. They replied: "Let us see if our team knows and we'll get back to you. ^EB"
I haven't gotten another answer back yet. I doubt I'll get one at all honestly.
quick question about updating a developer device
Hi
I'm a complete newby about wp7.
I've two Optimus 7 in my possession that seem to be developer devices.
Here the phones info:
OS Version: 6516Mainline
SW Version: LG-E900AT-00-V08d-ORG-UK-JUL-24-2010
HW Version: E
More info:
OS Version: 6516Mainline (buildlab).20100713-1228
Firmware revision number: 0.8.4.10
Hardware revision number: 0.1.5.0
Bootloader version: 1.4.1.0
Chip SOC version: 0.30.2.0
Now I've tried to update the firmware like in this post:
http://forum.xda-developers.com/showthread.php?t=935578
But it doesn't work (LGDP2 connect to phone start the update but give the error 1002)
Is there a way to flash these phones to be like normal phones? (I don't intent to develop on them) Or my hardware version is to old (prototype)
Thanks for the help
fb401 said:
I think flashing the unbranded Optimus 7 ROM would be the best bet for us. There is a registry key named "HasKeyboard" that's defaulted to 0 that we can change to 1. That might be the way to go. Also I'm wondering if we'd have to go the goldcard method to move over to a Quantum or Optimus rom.
The problem is I don't have another phone and there's no MTTY process to unbrick our phones so I'm a little hesitant to try.
Click to expand...
Click to collapse
so you are relying on a dev phone that MS was gracious enough to give you as your only device and are complaining that you didn't get the update???
edit: after reading your replies, this wasn't a publicly released phone, so if you don't get the updates, I don't feel you have a complaint.
Because crowds keep sending me PMs about their blocked devices here is tutorial how to fix it:
SEND YOUR PHONE TO REPAIR SERVICE. YOU NEED A NEW MAINBOARD.
lozohcum said:
Because crowds keep sending me PMs about their blocked devices here is tutorial how to fix it:
SEND YOUR PHONE TO REPAIR SERVICE. YOU NEED A NEW MAINBOARD.
Click to expand...
Click to collapse
If i relock bootloader and go back to stock, will this regain me warranty?
It may give you big chance that they will take it to warranty.
lozohcum said:
It may give you big chance that they will take it to warranty.
Click to expand...
Click to collapse
Im sending it in after hollidays ( approx 2 weeks, still need music on the plane ) and I'll let you guys know.
No need fo dat.
There must be a better solution
Hi lozohcum,
Please can you explain how this problem comes about further for us. At the moment I am failing to see why this has to be the only solution.
I'm no expert but have been messing around with this sort of thing for years and I have never come across something that cannot be fixed through a software hack. The only thing that comes close is the S4's flash counter - and users are only speculating that it is some sort of hardware counter, there are work arounds to avoid increasing it and seasoned devs such as ChainFire[pretty sure it was him] say that it will be reversible. Now if all that is correct I can't see Sony implementing something such as this - that can't be undone on a older and much cheaper device.
Also, I have read your post about how dev's should avoid it from happening while building their ROMs but it didn't explain why this makes it irreversible.
So, like I have asked - please explain to us whats going on that there is no way we can fix this. I feel like there must be a way!
Kind regards
Jono
PS: Taking my friends Xperia J into the service centre tomorrow
JonoIrwinRSA said:
Hi lozohcum,
Please can you explain how this problem comes about further for us. At the moment I am failing to see why this has to be the only solution.
I'm no expert but have been messing around with this sort of thing for years and I have never come across something that cannot be fixed through a software hack. The only thing that comes close is the S4's flash counter - and users are only speculating that it is some sort of hardware counter, there are work arounds to avoid increasing it and seasoned devs such as ChainFire[pretty sure it was him] say that it will be reversible. Now if all that is correct I can't see Sony implementing something such as this - that can't be undone on a older and much cheaper device.
Also, I have read your post about how dev's should avoid it from happening while building their ROMs but it didn't explain why this makes it irreversible.
So, like I have asked - please explain to us whats going on that there is no way we can fix this. I feel like there must be a way!
Kind regards
Jono
PS: Taking my friends Xperia J into the service centre tomorrow
Click to expand...
Click to collapse
I'll try answer it.
the custom rom trigger sony's security system and lock the phone. you need to flash the security system partition to fix it. the stock rom tft bundle doesn't have the image file needed to flash the security partition. thus, reflash a stock rom won't fix it. sony's security system is also very secure and at this time no one is able to hack it.
S4's flash counter - and users are only speculating that it is some sort of hardware counter, there are work arounds to avoid increasing it and seasoned devs such as ChainFire[pretty sure it was him] say that it will be reversible. Now if all that is correct I can't see Sony implementing something such as this - that can't be undone on a older and much cheaper device.
Click to expand...
Click to collapse
samsung have similar security system on their galaxy phone but it relatively not as secure as sony's. on samsung device, the security partition can be modified simply by bmtunlock tool. nevertheless, in the case of sony devices, no one know how to modify sony's security partition.
EDIT: if you're on stock rom, you can dial this code to get your lock status *#*#7378423#*#* . there's a 'simlock.ta' file in sony's tft bundle and it might related to how simlock still work after phone got locked. you can try to remove it from the tft bundle and reflash your stock rom and see what'll happen. i think it's worth to try.
Thanks for the info kurotsugi! Lock status = full lock and I've flashed it about 20 times with different roms in different ways. This one isn't coming back
I hope someone comes up with a solution soon. There must be many people with the same problem. Also I hope the issue gets stickied a bit more - I'm not blaming anyone but myself, I know the dangers of flashing, however I never knew of the issue until it was too late.
Jono
Sent from my GT-I9500 using XDA Premium 4 mobile app
kurotsugi said:
I'll try answer it.
the custom rom trigger sony's security system and lock the phone. you need to flash the security system partition to fix it. the stock rom tft bundle doesn't have the image file needed to flash the security partition. thus, reflash a stock rom won't fix it. sony's security system is also very secure and at this time no one is able to hack it.
samsung have similar security system on their galaxy phone but it relatively not as secure as sony's. on samsung device, the security partition can be modified simply by bmtunlock tool. nevertheless, in the case of sony devices, no one know how to modify sony's security partition.
EDIT: if you're on stock rom, you can dial this code to get your lock status *#*#7378423#*#* . there's a 'simlock.ta' file in sony's tft bundle and it might related to how simlock still work after phone got locked. you can try to remove it from the tft bundle and reflash your stock rom and see what'll happen. i think it's worth to try.
Click to expand...
Click to collapse
thanks @kurotsugi
Flashtool skip simlock.ta file while flashing btw
lozohcum said:
thanks @kurotsugi
Flashtool skip simlock.ta file while flashing btw
Click to expand...
Click to collapse
It's (i think) not in the TA partition, because I had a TA backup from my phone and it didn't unlock again after restoring it.
Hi there,
My phone has android 6.0.1 and i want it downgraded to android lollipop because ive got problems with android 6.0.1.
Im a total noob with all this stuff, so can someone please advise step by step how i can do this? I have the MOTO G 3rd Gen, SKU is "XT1541", Ram is 1GB and ROM 8GB. My current system version is 24.61.55.osprey_reteu.reteu.en.EU reteu. Build number is MPI24. 107-55. This phone will accept any phone network. Can someone please help? thanks in advance!
There are multiple threads discussing downgrading, it can be done if your device has the bootloader unlocked (which wipes data and voids the warranty)... There are some inherent dangers in doing so, some immediate and some long-term dealing with future updates which have the potential to brick the device.
What are the issues you are having, many times it is better to solve those then to downgrade.
acejavelin said:
There are multiple threads discussing downgrading, it can be done if your device has the bootloader unlocked (which wipes data and voids the warranty)... There are some inherent dangers in doing so, some immediate and some long-term dealing with future updates which have the potential to brick the device.
What are the issues you are having, many times it is better to solve those then to downgrade.
Click to expand...
Click to collapse
Some apps wont run well on android 6.0.1 such as facebook etc (personal and buisness use) and my phone generally ran better with the previous android version. The phone does not have a warranty on it anyway so that does not matter. Trust me, it really cudnt be much worse than it is atm, ive factory reset it and its just not up to standard as it was with android 5. I did have android 6.0 which i didnt like and then i got 6.0.1, which was putting ice on the cake, (in a bad way!). I am 1000% sure i want to downgrade my device. Can you help?
Ryanm353 said:
Some apps wont run well on android 6.0.1 such as facebook etc (personal and buisness use) and my phone generally ran better with the previous android version. The phone does not have a warranty on it anyway so that does not matter. Trust me, it really cudnt be much worse than it is atm, ive factory reset it and its just not up to standard as it was with android 5. I did have android 6.0 which i didnt like and then i got 6.0.1, which was putting ice on the cake, (in a bad way!). I am 1000% sure i want to downgrade my device. Can you help?
Click to expand...
Click to collapse
Not much to it... Unlock the bootloader, factory reset, then use the lollipop factory image from the factory images thread, gpt.bin will fail, just continue to flash everything all the way through. Follow the instructions in how to flash factory images, it's all done in fastboot.
Sent from my Motorola XT1575 using XDA Labs
acejavelin said:
Not much to it... Unlock the bootloader, factory reset, then use the lollipop factory image from the factory images thread, gpt.bin will fail, just continue to flash everything all the way through. Follow the instructions in how to flash factory images, it's all done in fastboot.
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
Thanks. But can you explain all that in more detail step by step? I need clear instructions on how to do all that as ive literally no idea about anything.
Ryanm353 said:
Thanks. But can you explain all that in more detail step by step? I need clear instructions on how to do all that as ive literally no idea about anything.
Click to expand...
Click to collapse
No offense, but this is not something to be taken lightly... there are many steps.
First, backup all your data... it will be lost.
Start by reading the first few posts in this thread... This will give the basics of what is needed to be done, what tools you need, how to do it, and the factory firmware images (you will need the correct one for your device, all the ones available are in this thread.
Next, read the first two posts in this thread... this is the instructions in detail of exactly how to flash a firmware image. Pay attention to the warnings and follow the linked threads with more information and make sure you understand all of it.
Once you have read and understand this part, you need to get fastboot working... this tool is essential to making all this work. Both of the threads I mentioned above have links to the drivers and Minimal ADB & Fastboot you will need. Install them and make sure they are working.
Now you can unlock the bootloader, this will wipe all data on your device. The instructions and process are done directly with Moto here.
Once you have unlocked the bootloader, reboot and start the bootloader and follow the instructions in the threads above, noting that the part where enter the command "fastboot flash partition gpt.bin" will likely fail because you are downgrading, but no other pieces should fail, if they do enter them again (radios are known to need to be done 2-3 times sometimes before taking), and continue all the way to the end. Pay attention to the number of sparcechunks in your image, it can will vary and you need to flash all pieces in order for your device, there could be anywhere from 5-9 pieces.
Keep a log of everything, it is much easier to tell what happened if something goes wrong by looking at the terminal log (scroll back of the terminal window) than just guessing.
TBH... I am not endorsing this method, but it generally does work, and although it is difficult to brick the Moto G 2015 it is not impossible. After you are done, you will need to root the device and freeze the updater service so you are not constantly prompted to update, and taking an OTA update can be problematic since your bootloader and/or partition table will not match the rest of the ROM correctly.
Personally I think since you have to unlock the bootloader anyway, you are probably better off just looking for a custom ROM like CM13, Resurrection Remix, or something like that since there are lots of rock solid Marshmallow aftermarket ROMs. Or if you are dead set on Lollipop, using CyanogenMod 12.1 instead of downgrading.
I know there is a downgrade utility out there, and not to take away from the developers work but I would suggest avoiding it.
My question current is really about better understanding something in this whole Root and Linux learning adventure I think I am totally confused about.
Basically if no custom ROM exist or your device is not listed on the supported list of devices in any recovery program....
OR as in my case you want desperately to get the thing back running on it's true stock what do you do?
Your rooted, but stuck.
So my main question is:
What is the best way to bring a device back to stock if there is no stock ROMs available and factory reset will not work?
On any device in this situation. Mostly I am hoping to have it explained in a way I can really finalize this confusing hole in my logic.
Like can a recovery program find it if it is still on the device somewhere and if not, why not?
Thanks in advance.
Additional backstory if helpful.
I have a Wacom Cintiq Hybrid running Android 4.1 that is ( now ) rooted..
This is a very bad thing. The Real Stock ROM has palm rejection and all the drivers to make it work as a tool. So stock is the ideal but it is clearly not stock as my device supposedly came in the
box running 4.2 and with software and drivers to make it work properly with the pen. This has nothing. No software and the smallest amount of apps possible. Worse this is no custom ROM its on ( I think) as it would be the worst one ever and it was not rooted on arrival. I have no idea what happened before I got it. I may have made the mistake of rooting it really as I found out to my dismay there is no ROM support. So back to square one. I bought it ( very cheap for one of these ) "stuck and unable to go to the play store" and I did not realize until I got it, on a version of Android it was not meant for. Wacom is totally and woefully unhelpful in every way. They seem to want to quietly put this device behind them at the expense literally of their customers.
I have discussed this problem in another thread if more details on all this specific to this device are of interest.
Duende101 said:
My question current is really about better understanding something in this whole Root and Linux learning adventure I think I am totally confused about.
Basically if no custom ROM exist or your device is not listed on the supported list of devices in any recovery program....
OR as in my case you want desperately to get the thing back running on it's true stock what do you do?
Your rooted, but stuck.
So my main question is:
What is the best way to bring a device back to stock if there is no stock ROMs available and factory reset will not work?
On any device in this situation. Mostly I am hoping to have it explained in a way I can really finalize this confusing hole in my logic.
Like can a recovery program find it if it is still on the device somewhere and if not, why not?
Thanks in advance.
Additional backstory if helpful.
I have a Wacom Cintiq Hybrid running Android 4.1 that is ( now ) rooted..
This is a very bad thing. The Real Stock ROM has palm rejection and all the drivers to make it work as a tool. So stock is the ideal but it is clearly not stock as my device supposedly came in the
box running 4.2 and with software and drivers to make it work properly with the pen. This has nothing. No software and the smallest amount of apps possible. Worse this is no custom ROM its on ( I think) as it would be the worst one ever and it was not rooted on arrival. I have no idea what happened before I got it. I may have made the mistake of rooting it really as I found out to my dismay there is no ROM support. So back to square one. I bought it ( very cheap for one of these ) "stuck and unable to go to the play store" and I did not realize until I got it, on a version of Android it was not meant for. Wacom is totally and woefully unhelpful in every way. They seem to want to quietly put this device behind them at the expense literally of their customers.
I have discussed this problem in another thread if more details on all this specific to this device are of interest.
Click to expand...
Click to collapse
Hello & welcome to xda-assist,
If you rooted the device you changed the system /kernel in the process, if root is all you done you should be able to unroot by using the unroot option in your root management application, if you did further changes like deleting system apps and so on it gets more complex, the best and easiest way to get back to the original state would be a copy of the latest firmware.. If it doesn't exist you're somewhat out of luck, please refer to this link for further help & information..
http://forum.xda-developers.com/android/help
Sam Nakamura said:
Hello & welcome to xda-assist,
If you rooted the device you changed the system /kernel in the process, if root is all you done you should be able to unroot by using the unroot option in your root management application, if you did further changes like deleting system apps and so on it gets more complex, the best and easiest way to get back to the original state would be a copy of the latest firmware.. If it doesn't exist you're somewhat out of luck, please refer to this link for further help & information..
http://forum.xda-developers.com/android/help
Click to expand...
Click to collapse
Thanks for the reply. So no way to get the extract the original firmware? I don't wish to un-root. The device was set to a very sad state of affairs when I got it, unrooted, with something very unlike the stock firmware and factory date reset not helping at all. Persistently locked into a lower version of Android than it was not meant for and not running the drivers or software it would seem I need to make it function properly that came with the device.
Basically it lead to my curiosity of how one goes about extracting or mining the data that is stored somewhere on the device if all I did was root. Which is all I did.
It should still be there. Basically how do I get to it?
The link takes me back to the forums for help, however I found no help there after much searching before I asked here but thanks
Duende101 said:
Thanks for the reply. So no way to get the extract the original firmware? I don't wish to un-root. The device was set to a very sad state of affairs when I got it, unrooted, with something very unlike the stock firmware and factory date reset not helping at all. Persistently locked into a lower version of Android than it was not meant for and not running the drivers or software it would seem I need to make it function properly that came with the device.
Basically it lead to my curiosity of how one goes about extracting or mining the data that is stored somewhere on the device if all I did was root. Which is all I did.
It should still be there. Basically how do I get to it?
The link takes me back to the forums for help, however I found no help there after much searching before I asked here but thanks
Click to expand...
Click to collapse
The intended of xda-assist is to direct you to the most suitable board of xda, we do not solve issues for you or do technical support, please be patient, it often takes time for exotic devices / questions to be seen by someone who can give hints and answers..
Edit: but it's not that the original firmware is stored somewhere on the device by default where you can grab it and reinstall it..
Sent from my OnePlus 2 using XDA Labs
Sam Nakamura said:
The intended of xda-assist is to direct you to the most suitable board of xda, we do not solve issues for you or do technical support, please be patient, it often takes time for exotic devices / questions to be seen by someone who can give hints and answers..
Edit: but it's not that the original firmware is stored somewhere on the device by default where you can grab it and reinstall it..
Sent from my OnePlus 2 using XDA Labs
Click to expand...
Click to collapse
Totally cool. It's a tough question.
The OG firmware thing is the toughest part to understand. Just wanted to make sure I was clear in my explanation and question.
HI there.
i read this :
Soft Brick
Soft brick is the state of android device due to some software problems like bootloops or device freezing at some point during boot. This may occur if some software problem occurred in the device mainly during OS upgrade or flashing something such as a custom ROM, camera mod or app in your custom recovery mode. A soft-bricked device is only half-dead. Because of this, your device is not booting anymore or is constantly crashing but can be recognised by a computer.
When your phone is soft brick, don't be panic. You can revive your Android device as long as it is only soft-bricked. The basic solution for this issue is flashing a clean and working version of Android to your device. While, during this process, you may need to restore a backup, flash a custom ROM or stock images to your device.
Hard Brick
Hard brick is the state of android device that occurs when your device is unbootable without a bootloop. A hard Brick device generally show little to no signs of life. If this happens, you had better to buy a new device since your device is showing you a black or grey screen at this point.
A phone get hard-bricked due to trying install ROM not made for the device or use ROM Manager incorrectly. Hard brick is more difficult to resolve and you may require an expert to give you professional advice. However you can recover from hard brick by using JTAG or send your Phone to JTAG service center to get it fixed, which means you no longer need to buy a new one.
Click to expand...
Click to collapse
Is it true that even hard bricked device can be high percent recoverable?
I own service and want to know the things good and be normally good. If i have to i will take loan to buy nessesary stuff to be successful.
Is that with JTAG true for tablets too? I have buyd from AliExpress Phone Box 2017 version but still havent used it.
If i have to be more specific. Have one client`s tablet here. It is recognised by Windows as MTK something and gone after seconds from device manager then recognised again and that...
history : it was virused and install OS to it was really needed. I shot in the dark and install it some OS for these parameters:
mt6582 1G+16G and flashed it successfull with SP Flash Tool but now the device does not boot and is half recogniseable in Device Manager. I did that because the device/'beauty' chinese tablet/ has no ID on the back side of it.
I hope this time someone to tell something good and usefull.
Thanks
diretouch said:
HI there.
i read this :
Is it true that even hard bricked device can be high percent recoverable?
I own service and want to know the things good and be normally good. If i have to i will take loan to buy nessesary stuff to be successful.
Is that with JTAG true for tablets too? I have buyd from AliExpress Phone Box 2017 version but still havent used it.
If i have to be more specific. Have one client`s tablet here. It is recognised by Windows as MTK something and gone after seconds from device manager then recognised again and that...
history : it was virused and install OS to it was really needed. I shot in the dark and install it some OS for these parameters:
mt6582 1G+16G and flashed it successfull with SP Flash Tool but now the device does not boot and is half recogniseable in Device Manager. I did that because the device/'beauty' chinese tablet/ has no ID on the back side of it.
I hope this time someone to tell something good and usefull.
Thanks
Click to expand...
Click to collapse
Yes, it is "possible" to recover hard bricked devices with a JTAG but there are no guarantees it will work and no way to guarantee each customer that there device will be fixed.
As for the MTK device you are trying to repair, you can't just flash a firmware from another mt6582 device, there is quite a bit more involved than just the same CPU. Firmware from another device must be ported to work with the other hardware on the device.
You need to identify more about the device than just it's CPU if you want to find a firmware that will work without modifications.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Can you help me identify the device ? Please...
https://drive.google.com/drive/folders/0Bxome1ZSCRIaSW5fNTZrY3NsU2s?usp=sharing
diretouch said:
Can you help me identify the device ? Please...
https://drive.google.com/drive/folders/0Bxome1ZSCRIaSW5fNTZrY3NsU2s?usp=sharing
Click to expand...
Click to collapse
If that's the device after you flashed it, it seems to be booting fine. Is it having issues where some features and functions aren't working correctly?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Unfortunately this is the device before flash.
It`s labeled as pc703 in the seller site/bulgarian not China/
The back cover of the device is
https://drive.google.com/file/d/0Bxome1ZSCRIaOGpIWjcxaGg5ek0/view?usp=sharing
diretouch said:
Unfortunately this is the device before flash.
It`s labeled as pc703 in the seller site/bulgarian not China/
The back cover of the device is
https://drive.google.com/file/d/0Bxome1ZSCRIaOGpIWjcxaGg5ek0/view?usp=sharing
Click to expand...
Click to collapse
Can you give me a link to the seller site?
Usually these cheap off branded Chinese tablets are almost impossible to identify properly because the hardware varies so much even among separate devices with the same model number. It is like this because there is no actual "manufacturer", these devices are pieced together with cheap discounted components that were bought in bulk and they use whatever they can get to work, even if it involves using completely different components. This makes it virtually impossible to say exactly which firmware you need.
When a device is bricked and the device is one of these cheap devices that can't be identified properly and has no available stock firmware or stock source code and has no support from the manufacturer, typically, the only solution is to just try different firmwares and hope one works or piece together your own firmware with pieces of others that might compatible.
You'd have to have a lot of time and android development skills to make your own firmware.
You've got a difficult road ahead, I'd suggest they replace the device because the cost of repair will be more than the device costs.
When you flashed the device with SP Flashtool, did you happen to pull anything important from the device or did you by chance make a backup of some sort before you flashed it?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Man usually understand his mistakes after he did it.
Maybe I will never take again unknown tablet for service. The problem is that the customers are waiting and I am tired of buy customers devices either second hand or new.
The site should be 4sales.BG
That said the woman.
The 'cool' is that I find there version not with 1g+16g
Good night.
In simple words, Soft brick is messing a little with your Android from which you can recover easily.
Hard Brick is like screwing up your device completely, yes, you can recover, but it needs lots of technical process.
---------- Post added at 09:33 AM ---------- Previous post was at 09:31 AM ----------
In simple words, Soft brick is messing a little with your Android from which you can recover easily.
Hard Brick is like screwing up your device completely, yes, you can recover, but it needs lots of technical process.
Technical or not that`s not bad. Just want to have the nessesary tools if they are not too expensive. I just wont desolder very very small smd resistances and transistors
If someone can help in my chinese tablet case i will be a little more not unhappy.