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.
hi guys,
When i see this forum there is not a lot of development. i rooted the phone but i am looking to install a custom recovery on my g flex 2, but i can not find anything about that on this forum (probably because it is so new). so i wondered could i check the g flex 1 forum for a custom recovery or would this just destroy my phone?
BZander said:
hi guys,
When i see this forum there is not a lot of development. i rooted the phone but i am looking to install a custom recovery on my g flex 2, but i can not find anything about that on this forum (probably because it is so new). so i wondered could i check the g flex 1 forum for a custom recovery or would this just destroy my phone?
Click to expand...
Click to collapse
The safest rule to live by is to never flash anything designed for one phone to a different phone. While they are both made by LG and both have the name Flex on them, they are completely different in hardware. Flashing the recovery of one phone to an unrelated phone could even brick your phone.
Flash it and check
Sent from my LGLS996 using xda Forum
Hmmmm i guess we'll kust have to wait.
Alwats thought recovery on your phone was something like a BIOS in your pc and Android was the Windows.
Guess i was wrong.
Hope someone makes a recovery than.
You're not that far off, but to extend the analogy you're asking to flash a Pentium 4 BIOS onto an i7 motherboard.
The recovery is technically a "ROM" in itself. It has a kernel compatible with the hardware, drivers for the hardware, and the partitioning scheme of the hardware, among other things.
While it's based on the Linux Kernel, Android (and most ARM based Linux) does not build global images that work with every device. This is for several reasons:
1. It wasn't even possible until relatively recently. (http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=9cd11c0c47b8690b47e7573311ce5c483cb344ed http://www.phoronix.com/scan.php?page=news_item&px=MTE5ODI
2. Embedded devices have limited storage. Historically, this meant that saving every kb of storage was very important and thus kernels were and are compiled only with the code that is needed for the specific device being used.
3. OEMs do not use a global source code. They fork their version of the Android Linux Kernel fork for each and every single device. Making changes to the source code for a single device without breaking other devices can be tedious so OEMs do what they can with the time constraints that they have.
Of course, I could be very wrong, but that is my understanding of it.
Any news on a recovery for G Flex 2?
I'm wondering if anyone has had any luck finding a recovery that will work on the G Flex 2, I found something called clockworkmod builder (cannot post a link because I am too new) but don't know enough yet to use it, or if it will even work.
Let's get the ball rolling with this thing... I am new to blu
Search shows SP Flash tool as a main flash tool.
I expect to get root with towel root or kingroot.
If we do acquire root, the next step is to dump a stock ROM, I haven't done much dev. since jellybean, but hopefully we could map partitions (important), and do a raw dump (.img) backup, etc. A secure kernel, could prevent that, I think. If we are able to make or acquire a stock ROM, we have something to fall back on. There's always hope, they will allow unlock of bootloader from developer options in settings, or fastboot oem unlock. It looks like quite a few other blu devices have been unlocked. If worst came to worst, I'm sure we could pony up some donations to get this device into a developers hands to help.
Once we get bootloader unlocked, all we need is a custom recovery, and some source code bits, and its off to the builds, we hope!
Please share any beginning steps to help get things moving here....
this looks promising.. http://androidxda.com/download-mtk-droid-tool
Thanks!
Yes let's get the ball rolling. I'm eagerly waiting for this device. The source for the x10 is released so it looks like we're in the green for now.
Sent from my A0001 using Tapatalk
Rooting
chrisrotolo said:
I expect to get root with towel root or kingroot.
Click to expand...
Click to collapse
No luck with either of those. I've tried a lot of "one-click" apks and none of them work. It looks like I'm going to have to dig out an old desktop from my basement and make myself a Windows machine (urgh!!). I agree, Sp Flash Tools and MK Droid Tools look like a good place to start.
SP Flash Tool for Linux
I've been trying to get my linux (Ubuntu 14.04) to recognize the phone with this s/w but no luck so far, even though the system finds it (see screenshot).
http://forum.xda-developers.com/general/rooting-roms/tutorial-how-to-setup-spflashtoollinux-t3160802
You kernel messages suggest you have the Allview version... Is it possible that software or partitioning differences in the default load of the Allview vs. the Blu may make a difference in whether the root apps work?
clipcarl said:
You kernel messages suggest you have the Allview version... Is it possible that software or partitioning differences in the default load of the Allview vs. the Blu may make a difference in whether the root apps work?
Click to expand...
Click to collapse
I have no way of knowing.
I sure hope the developers jump all over this phone.
xathras said:
I have no way of knowing.
Click to expand...
Click to collapse
So it could be too soon to assume that the current rooting apps won't work on the Blu phone just because they don't work on the Allview.That is, if Blue has their own software stack they install that is different than the Allview...
Rooting from PC failed
I now have a Windows 7 machine running so I've tried a couple of root from pc apps.
Drivers http://androidxda.com/download-gionee-usb-drivers
I installed the Gionee E8 drivers from here successfully - or so Windows said.
Root Genius v2.4.1 http://androidxda.com/download-root-genius-application
First ticked "USB debugging" under "Developer options" on phone. Ran Root Genius and it found the phone first time. Click on "Allow Computer" box that pops up on phone. Root Genius started, got to a couple of % and then crashed. Rebooted PC, clicked on "Revoke USB debugging authorisation" for a clean start and tried again. Same result; click "Allow computer", start program and crash. Tried a couple more times with same result.
iRoot v1.8.5 http://androidxda.com/download-iroot-application-all-versions
Used same procedures as with Root Genius. iRoot started, found the phone, went all the way though it's operations before reporting that rooting failed (i.e. it did not crash). Retried a couple of times with the same result.
The only plus is that the driver I used appears to be OK for Windows 7 at least (both programs found the phone).
Later I tried Kingo Root http://androidxda.com/root-android-device-using-kingo-root
It couldn't find the phone using the driver I previously used or it's own driver, although the "Allow computer" box popped up on the phone both times
xathras said:
I now have a Windows 7 machine running so I've tried a couple of root from pc apps.
Drivers http://androidxda.com/download-gionee-usb-drivers
I installed the Gionee E8 drivers from here successfully - or so Windows said.
Root Genius v2.4.1 http://androidxda.com/download-root-genius-application
First ticked "USB debugging" under "Developer options" on phone. Ran Root Genius and it found the phone first time. Click on "Allow Computer" box that pops up on phone. Root Genius started, got to a couple of % and then crashed. Rebooted PC, clicked on "Revoke USB debugging authorisation" for a clean start and tried again. Same result; click "Allow computer", start program and crash. Tried a couple more times with same result.
iRoot v1.8.5 http://androidxda.com/download-iroot-application-all-versions
Used same procedures as with Root Genius. iRoot started, found the phone, went all the way though it's operations before reporting that rooting failed (i.e. it did not crash). Retried a couple of times with the same result.
The only plus is that the driver I used appears to be OK for Windows 7 at least (both programs found the phone).
Click to expand...
Click to collapse
Cool... It's good to test this stuff. More information is always a good thing.
BUT, since the software / partitions of the Blu Pure XL phone will almost certainly be different than the Allview phone you have your tests really don't really tell us anything about the Pure XL for certain. The hardware may be exactly the same (or there may be differences in the radios) but if the software and / or partition layout is different then what works on your phone may not work on the Pure XL and vice versa.
So I'd request that you keep posting your useful information... BUT that you clearly post that you don't actually have a Blu Pure XL but the Allview phone so you don't confuse people. Yes, they may be based on the same hardware but that does not make them exactly the same as one another. For example, there are different versions of the LG G4 and they all have pretty much the same hardware but they can't all use the same ROMS or the same rooting techniques.
So what you are posting helps because more data is better, but is not definitive for the Pure XL because your phone is NOT a Pure XL.
Thanks,
Carl
clipcarl said:
Cool... It's good to test this stuff. More information is always a good thing.
BUT, since the software / partitions of the Blu Pure XL phone will almost certainly be different than the Allview phone you have your tests really don't really tell us anything about the Pure XL for certain. The hardware may be exactly the same (or there may be differences in the radios) but if the software and / or partition layout is different then what works on your phone may not work on the Pure XL and vice versa.
So I'd request that you keep posting your useful information... BUT that you clearly post that you don't actually have a Blu Pure XL but the Allview phone so you don't confuse people. Yes, they may be based on the same hardware but that does not make them exactly the same as one another. For example, there are different versions of the LG G4 and they all have pretty much the same hardware but they can't all use the same ROMS or the same rooting techniques.
So what you are posting helps because more data is better, but is not definitive for the Pure XL because your phone is NOT a Pure XL.
Thanks,
Carl
Click to expand...
Click to collapse
Thanks Carl, you're quite right of course. I'll check back in a couple of weeks once you guys have actually got your hands on some genuine Blu. When you do these adb tools (http://androidxda.com/download-best-android-adb-driver) and MTK Droid Tools worked v2.5.3 work on my Allview.
xathras said:
Thanks Carl, you're quite right of course. I'll check back in a couple of weeks once you guys have actually got your hands on some genuine Blu. When you do these adb tools (http://androidxda.com/download-best-android-adb-driver) and MTK Droid Tools worked v2.5.3 work on my Allview.
Click to expand...
Click to collapse
Please don't stop posting your test results! Just let people here know they're for the Allview and thus may not be the same as what would happen on the Pure XL. But it's also quite possible that your phone is exactly the same with the same software and layout just with cosmetic changes. We just don't know yet. It's also possible that your phone could be flashed to be exactly the same as the Pure XL even if it's not out of the box. In any case it's definitely useful information you are providing!
@xathras - Have you tried flashing SuperSU from recovery or otherwise injecting root from a recovery package?
http://www.recovery-mode.com/android/gionee-elife-e8.html
neatojones said:
@xathras - Have you tried flashing SuperSU from recovery or otherwise injecting root from a recovery package?
http://www.recovery-mode.com/android/gionee-elife-e8.html
Click to expand...
Click to collapse
Flashing SU from recovery fails and although I haven't tried the other option I'm fairly sure that that would fail too, due to /system being a secure read only partition. It is going to take someone with the necessary skills to extract boot.img, make the needed changes and re-packing it. I've seen a webpage for a china wholesaler for the Gionne version of this phone who offers an "unlock and root" option for $2.99 per device, so it must be doable.
Bootloader unlocked
Have look at post #108
http://forum.xda-developers.com/pur...v-friendly-t3197751/post63383416#post63383416
xathras said:
Have look at post #108
http://forum.xda-developers.com/pur...v-friendly-t3197751/post63383416#post63383416
Click to expand...
Click to collapse
Great! You were one step ahead, that was going to be my next suggestion. Now with an unlocked bootloader you should be able to make a TWRP and flash whatever you want including injecting su or flashing a completely modified ROM with root.
Posting this here so we can have a to go to thread.
xathras said:
Now that some of you look like your'e about to get your hands on this device I'll post a few of the resources you might need. The MediaTek X10 Helio (mt6795 based) is only now beginning to appear in phones; there is little help from devs as yet (Hey! Your'e An Early Adopter). The Gionee version has just gone on sale in India so something (in English) might appear there soon. Due to MTK devices being common in Asia you'll find a lot of help in sites there.
Blu related sites
BLU Products Development Team - Community - Google+
https://plus.google.com/communities/117846429749085694805
BLU Developers Repository
http://www.blu-dev.com/
Asian sites
China Devices
https://www.china-devices.com/
China Phone Arena
http://www.chinaphonearena.com/forum/Forum-MTK-General-Tools
Android Urdu
http://androidurdu.net/mediatek-scatter-files-download/
http://androidurdu.net/sp-flash-tool-database/
MTK Roms
http://www.mtkroms.com/
http://www.mtkroms.com/2015/03/mtk-bootimg-unpack-repack-tool.html
http://www.mtkroms.com/2015/02/how-to-root-your-mediatek-device.html
http://www.mtkroms.com/2015/03/philz-touch-recovery-for-all-mtk-devices.html
and many others.
Rooting and flashing
http://whiteboard.ping.se/Android/Rooting
http://whiteboard.ping.se/Android/BootLoader
https://wiki.cyanogenmod.org/w/Doc:_fastboot_intro#Common_fastboot_commands
https://wiki.cyanogenmod.org/w/Template:Fastboot_oem_unlock
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
MTK Droid Tools 2.5.3
http://forum.xda-developers.com/showthread.php?t=2160490
http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5
This tool does not work on this phone because it can't recognize the new 64-bit SOCs. I thought that when it found my phone it might work but the "TotalBytesPerChunk Not Found" error (see attached screenshot) is fatal. However, it does do one useful thing in that it displays a blocks map even thought it can't create a scatter file. I'd like to know if the Allview and Blu blocks maps match.
MTK Droid Tools is sadly no longer being maintained.
Attached files are the MTK Droid Tools screenshot (too big - had to zip it) and the Allview build.prop file. I'd be interested in seeing the Blu version.
Click to expand...
Click to collapse
---------- Post added at 12:28 PM ---------- Previous post was at 12:24 PM ----------
Can we as a community keep hammering Mediatek to release the helio x10 sources so we can start porting roms to the pure xl? I'm doing my fair share of posting on their social media sites. We'll be able to get 6.0 if they post up the sources. They had them up on github but they removed them I don't know why.
FuMMoD said:
Can we as a community keep hammering Mediatek to release the helio x10 sources so we can start porting roms to the pure xl? I'm doing my fair share of posting on their social media sites. We'll be able to get 6.0 if they post up the sources. They had them up on github but they removed them I don't know why.
Click to expand...
Click to collapse
This is probably where I stop being useful since I'm a "monkey see, monkey do" kind of guy as far as rom development goes, although I'm up for testing stuff.
Is this any of use to you?
http://www.mediafire.com/download/dx698xy19xg5xq8/MT6795.kernel-master.zip
https://github.com/jawad6233/MT6795.kernel/tree/master/alps/kernel-3.10
Both from this link:
http://forum.xda-developers.com/mei...elio-x10-kernel-source-code-released-t3225886
xathras said:
This is probably where I stop being useful since I'm a "monkey see, monkey do" kind of guy as far as rom development goes, although I'm up for testing stuff.
Is this any of use to you?
http://www.mediafire.com/download/dx698xy19xg5xq8/MT6795.kernel-master.zip
https://github.com/jawad6233/MT6795.kernel/tree/master/alps/kernel-3.10
Both from this link:
http://forum.xda-developers.com/mei...elio-x10-kernel-source-code-released-t3225886
Click to expand...
Click to collapse
Dude you're awesome at researching and finding useful Intel! I'm going to go over everything you've provided over course of today and tomorrow and start working on the phone. I should get it by tomorrow evening. I built my own rom before privately so hopefully I have enough know how to get Development rolling in here. I just hope I can motivate others of better skills to come over once it's proven roms can be ported over and such.
Sent from my A0001 using Tapatalk
FuMMoD said:
Dude you're awesome at researching and finding useful Intel
Click to expand...
Click to collapse
I can resist anything except flattery!
In my Allview build.prop there's a line that says "ro.gn.gnromvernumber=GiONEE ROM5.0.16". I'd be very interested in knowing what your Blu build.prop has to say.
Thanks to the senior members who are helping me to get around the XDA site. I will get the hang of it
At the beginning of the week I had posted this thread in the XDA-Assist section and I am now starting it here. I am not sure if my old post was moved to here or not so here goes. If this is a duplicate I am sorry.
Thanks
"I recently bought this tablet from Amazon and I've been scouring the net looking for root solutions. Ive tried most of the popular one-click tools without any success. Here is what I did learn, this tablet has a mediatek MT8127 chipset, running stock Android 5.0.1 on a 3.10.54 kernel. The build number is ALPS.KK1.MP10.V 1.18. Ubuntu 14.04 recognized my tablet only after updating 51-android udev rules. I was finally able to execute adb shell successfully. I was able to reboot into fastboot, but not able to unlock it. Some interesting information that I learned along the way....when I plug my tablet into my PC it's seen as a MT65xx Android device, but when it's in fastboot my PC sees it as a HTC device. I had to update adb_usb.ini to recognize both a mediatek and a HTC device in order to reboot through my Linux command line. I contacted Hipstreet customer service and ask for any information that they would be willing to impart to me, but they weren't much help. I haven't tried building any cwm as of yet since my bootloader is still locked. Any help would be great. Any progress that I make I would love to share. If more information is needed about this tablet just reply and I will do my best.
Thanks,
MitMat"
Just thought would leave this here.
The Alcatel 3v supports project treble it's probably the cheapest on the market that supports this
If there is a way to unbrick it, I might try flashing a GSI to see if it will actually work. The thing is that for some reason my 3v has a MT6735
nintendobuster420 said:
If there is a way to unbrick it, I might try flashing a GSI to see if it will actually work. The thing is that for some reason my 3v has a MT6735
Click to expand...
Click to collapse
Ok just to give you guys an update, GSIs actually work! I managed to unlock the bootloader by typing in fastboot oem unlock and ticked oem unlock in developer options. Then I followed XDA's guide on flashing a GSI and it actually worked. Now we have stock android on the alcatel 3v. The only problem is that the phone is really slow and the stock camera app is upside down so its probably best to stay on stock
Have you had any luck trying out different gsi's, perhaps there's a certain one that works better? Also, would you happen to have a stock rom for an Alcatel 3v 5099a? Or at least a boot.img?
Laney613 said:
Have you had any luck trying out different gsi's, perhaps there's a certain one that works better? Also, would you happen to have a stock rom for an Alcatel 3v 5099a? Or at least a boot.img?
Click to expand...
Click to collapse
Oreo seems to be less laggy also I have a 5099y which is the nfc version I could try and dump my rom
I just really want to fix the youtube lag on this phone as it always lags at 1080p or 720p
how did you unlock the bootloader ? i have the 5099y, i tried adb fastboot oem unlock,i have adb installed ,i have google usb installed,ive got updated drivers, but it still says waiting for device,it boots into fastmode fine ,but then once i do adb devices it doesnt see it,it does show in the device manager as alcatel,usb debugging is allowed, oem unlock is ticked
CrunchyKevlar said:
how did you unlock the bootloader ? i have the 5099y, i tried adb fastboot oem unlock,i have adb installed ,i have google usb installed,ive got updated drivers, but it still says waiting for device,it boots into fastmode fine ,but then once i do adb devices it doesnt see it,it does show in the device manager as alcatel,usb debugging is allowed, oem unlock is ticked
Click to expand...
Click to collapse
It's fastboot OEM unlock, when in fastboot
The procedure was fairly easy and I'm now running phhussons AOSP 9 v114 on my 5099Y.
Very smooth and much faster than stock 8.0.
No camera issues at all.
Google play verification was an issue but soon sorted
This device needs further development though, it has a few random glitches running pie, but nothing than stops it working well.
After reading @ivan1972 comments I've today also flashed a couple of gsis on my 5099Y and had good success all round.
I unlocked the bootloader, this device has the easiest unlocking bootloader ever!
I then tried lineage 15.1 with Go gapps and that worked really well.
I tried Descendants 3.0 and flashed via fast boot (fastboot flash system system.img - I obviously renamed the GSI to "system.img") I have that installed on my Moto E5 play but it was far too glitchy on the Alcatel and I had huge problems trying to get the play store certification working, so I was bombarded with notifications about my 3V not being Google play verified almost every three seconds!!!
I'm also using AOSP 9 v114.
The battery life is double that of stock oreo, the phone works twice as fast as it did on stock, and I had no issue with Google device certification.
I suggest any user wanting to flash a Gsi on a 3V spectrum should aim to install lineage 15.1 or AOSP 9 as they are both great gsis.
Edit, the Gsi was flashed in fastboot as I haven't rooted or flashed (found) a twrp for the 3v yet.
Some screenshots from my 3V Spectrum (using the latest Lawn chair V2 as default launcher)
You will note the status bar is glitchy and doesn't show until a notification is received, then it appears in the middle of the screen, not at the top.
The only major issue I've seen so far.
The device is listed as "PHH treble" in device settings
After a week's usage Ive found one major flaw.
Whilst you can make an out going call with no problems, with good clarity and good service, no one can actually phone you.....!
Incoming calls are diverting straight to voicemail, nothing in settings to explain why.
Everything else is perfect on pie, flawless and way better than stock.
But this phone is no use if you cannot use it for its primary function - to receive a phone call :crying:
Edit - I'm told it's an AOSP issue on mediatek chips, and it's not an easy fix.
And as there is no way to go back to stock, I'm now stuck with a device that cannot receive any calls.
Just putting that out here incase anyone does read this and feels the need to flash pie.
Don't bother!
I'm done with this Alcatel - no one really seems that interested in this device anymore.
Edit.
My Alcatel has been traded in (as non functional) for a Nokia 4.2
I'm not quite sure why are people sending me private messages asking if I can send them the custom recovery for the Alcatel 3V?
I have quite clearly stated in my previous posts that I flashed the GSIs I tried via FASTBOOT - there is NO custom recovery for 3V that I can find - so please don't message me requesting the custom recovery.
*WARNING*
I also recommended users do not flash android pie gsis on this device as it breaks RIL / modem function and there is no current fix - but for a strange reason people are still asking me about the process and any bugs / issues.
Please read things properly before posting private messages - whilst I'm happy to help anyone, I'm not prepared to keep unnecessarily repeating myself for the sake of repeating myself when the information is already there for everyone to see.......
bubba1601 said:
After reading @ivan1972
I unlocked the bootloader, this device has the easiest unlocking bootloader ever!
Click to expand...
Click to collapse
I wish that was easy to believe, but I have an Alcatel 3v (5032W) and I CANNOT unlock the bootloader for the life of me!
@mattchusquirtle420
I'm not sure why you find what I said one year ago so hard to believe, but I'll explain it to you.
Are you sitting comfortably?
Then I'll begin.....
This thread deals with the 2018 Alcatel 3v (5099Y)
It's a 2gb ram 16gb ROM / 3gb ram 32gb ROM on Android 8.0 (Oreo)
That had a standard MTK (Mediatek) chip so was super easy to bootloader unlock.
All you had to do was enter fastboot and use the "fastboot OEM unlock" command and press enter.
The bootloader was now unlocked, no unlock codes were needed or necessary.
https://www.gsmarena.com/alcatel_3v-9004.php
********************
You have the 2019 Alcatel 3v (5032w) which is a 3gb ram 32gb ROM device running Android 9 (pie)
Which has a MTK Helio chip and a locked bootloader that cannot be unlocked.
None of the Helio or Snapdragon Alcatel 2019 devices can be bootloader unlocked, infact the only 2019 Alcatel device than can be bootloader unlocked is the 1C.
I'm not being rude to you here, but this thread began back in May 2018 - and you also just replied to a comment I made in July 2019 - That's a whole SIX months before your 3v 2019 became commercially available.....so I don't understand why you even commented, your device isn't relevant, or even has the same processor / chip as the 2018 version, so how can you honestly disbelieve our experience if you have a completely different device?
I now have this device.
Alcatel 3 (2019) 5053Y (Snapdragon 439 chip with 3gb ram and 32gb ROM on Android 9 pie)
https://www.gsmarena.com/alcatel_3_(2019)-9599.php
It's not possible to unlock this device because bootloader unlocking is not supported.
I'm going to ask you now very politely and without being rude to NOT private message me about your device.
Your device is not relevant or related to our discussion or this post.
You are going to have to find a dedicated thread for the 3v 2019 because posting and commenting in the 2018 device thread is not really very clever and achieves nothing, and helps no one, including you.
Oh dear.
You seem to be annoyed and disbelieve what we are saying.....
Well how about you actually read the post properly first before you start telling people you find it hard to believe what they say?
Did it occur to you at any point that we may have been discussing a different device to one you have?
There is more than one version of the Alcatel 3v and they are all different.
Nothing annoys me more than comments from people who don't take time to read the information Infront them properly.
You've commented here saying you can't believe us but you've commented in a device thread that you don't have or have any experience of at all, so your comments are completely unfair and totally unnecessary.
I thought how old the the thread was it would have been completely obvious to you that we were not discussing the same device as yours, or you were just stupid and assumed it was the same.
@bubba1601
@ivan1972
Y'all should go easy on the dude. I made the same mistake thinking this was a 5032w thread simply bc it's the leading search result on Google. He's just a newb and probably linked in to this thread from a Google search and there is NOT distinguishing information that this thread is specifically for the 2018 version. Until you two fire off at a new member bc he annoyed you.
Aballamis said:
USER=7682183]@bubba1601[/USER]
@ivan1972
Y'all should go easy on the dude. I made the same mistake thinking this was a 5032w thread simply bc it's the leading search result on Google. He's just a newb and probably linked in to this thread from a Google search and there is NOT distinguishing information that this thread is specifically for the 2018 version. Until you two fire off at a new member bc he annoyed you.
Click to expand...
Click to collapse
Really?
Don't you think it's just a bit sad that you felt the need to take me to task over comments I make 16 months ago?
Who cares now?
It's not my fault or my problem if you blindly follow Google links.
It's not my fault you made a mistake, at least you admitted to it, so many here don't.
I'm sorry you made the same mistake but rather than sound off to me about it a year and 4 months later, learn from your mistake, move on and forget about it.
What happened here is none of your business, the "new" guy concerned made a heartfelt and genuine apology privately to me and we both moved on 16 months ago, but now you come along and you have to have the audacity to tell me off!
I can always refer you to the mods here if you are really concerned and upset about my comments, but seeing as it was resolved so long ago I don't really see the point.
Or I could just report you for harassing me, the choice is yours
Aballamis said:
@bubba1601
@ivan1972
Y'all should go easy on the dude. I made the same mistake thinking this was a 5032w thread simply bc it's the leading search result on Google. He's just a newb and probably linked in to this thread from a Google search and there is NOT distinguishing information that this thread is specifically for the 2018 version. Until you two fire off at a new member bc he annoyed you.
Click to expand...
Click to collapse
No one has annoyed me only you.
I don't take kindly to getting XDA notifications at 3 am, especially for something I said here so long ago.
So what I need to know is why are you replying to something I said almost 2 years ago?
So you really think I care what you think?
I think it's absurd you come here telling me and the other guy off for something we said 16 months ago - AND after you admit to making a mistake and follow Google links without checking.
That's just stupid.
Did you actually read the thread properly? I think not, you come charging in here with all guns blazing without knowing the full facts.
The other guy apologized to me for his mistake privately and there was no problems between us.
So why are you telling me off now 16 months later without knowing the full facts?
When did you check the facts?
You just charged in here telling people off.
I'm not happy about this as it was resolved 16 months ago with good intentions privately, amicably and in good spirits.
I will be reporting this matter to the moderation team here, as I certainly don't take kindly to being told off by people who cannot check the facts first.
Hello, can someone please send me the official recovery of the alcatel 3v 5099a?
.