Related
New firmware released! :laugh:
Now It's only minor update for 4.0.4.
Code:
Version 4.0.28 - February 18th, 2012
HDMI: avoid interference of CEC detected as DPAD with some games such as Max Payne
Video: fix playback of some MP4 files
Video: fix aspect ratio on some H264 files
Touchscreen panel: ensure on some devices a proper wakeup when powering screen back on
You can get update by OTA (Settings --> About Tablet --> Update firmware (Check Updates)) Or by this link (by use *.aos file).
Download links:
Yandex Disc
Hello !
I'll release soon root version, and later root-deodex version !
So, stay tuned ! :good:
Ok I wait it!
surdu_petru said:
Hello !
I'll release soon root version, and later root-deodex version !
So, stay tuned ! :good:
Click to expand...
Click to collapse
Hmmm root de odex sounds sexy
TrOjAn
I tested it in sitetic benchmark.
Quadrant ~ 4145 marks
Antutu benchmark 3.x ~ 8740 marks
It's more than 4.0.26 firmware, but it's only sintetic tests!
Is this a sign that Archos 101 G9 will not get Jelly Bean?
XS version gets even 4.1.2...
when archos gve us 4.1? when the 5 is out?.. or nevr for g9?
Sent from my ARCHOS 80G9 using xda app-developers app
Here is a quote taken from the Archos Facebook website:
"""
Archos Worldwide Marco Antunes - Unfortunately after many months of analysis and
testing it has been decided that, due to the multiple hardware configurations
available on our G9 range and the complexities these add, we will not release an
Android 4.1 “Jelly Bean” update to the G9 range tablets. The G9 Range, originally
released in the autumn of 2011, running Honeycomb, saw 15 firmware updates taking
it across many versions of Honeycomb and Ice Cream Sandwich, making 4.0.26 the
final firmware that will be provided to this device range.
"""
I assume that the 4.0.26 was a typo because 4.0.28 was released at about the exact same time as the above was posted.
Personally, I'm glad all this nonsense about Jelly Bean is finally over! Since new devices come out just about every 6 months these days now... why would anybody have actually expected Archos to update their (now several years old) G9 tablets? Just about all electronic devices are now considered as "throw away" devices and not expected to even be in use 2 years after they first come out.
55mls said:
(now several years old) G9 tablets?
Click to expand...
Click to collapse
More like a year and a half. At least 4.0.28 seems to work pretty well. It's the first 4.0.x version I'll stick with I think.
You are certainly correct in saying that consumer electronics are EOLed very quickly because the consumer hive mind moves on to the next exciting barely-supported junk without much delay. Thankfully these are open-source devices and so can be improved further, perhaps beyond incompetent Archos abilities.
surdu_petru said:
Hello !
I'll release soon root version, and later root-deodex version !
So, stay tuned ! :good:
Click to expand...
Click to collapse
And a [email protected] v05.... ???????
MrMmmkay after deodex realese, I wiil build my rom with mods.
Mods are ready, and you can install it manualy (go to PM, I upload it for you)
swaaye said:
More like a year and a half. At least 4.0.28 seems to work pretty well. It's the first 4.0.x version I'll stick with I think.
You are certainly correct in saying that consumer electronics are EOLed very quickly because the consumer hive mind moves on to the next exciting barely-supported junk without much delay. Thankfully these are open-source devices and so can be improved further, perhaps beyond incompetent Archos abilities.
Click to expand...
Click to collapse
I just wish my touchscreen worked on my $250 tablet I bought 9 months ago. Archos has been pathetic through this process. I could have bought a nexus 7 and had cash leftover. And the damn thing would work correctly.
Sent from my Galaxy Nexus using xda premium
I had sideloaded flash player after upgrading to ICS and although it is not officially supported by google, it was working great for viewing flash content (e.g. Amazon Instant videos) in certain browsers (Firefox, Opera Mobile, Dolphin). After upgrading to the latest firmware on Wednesday night, I am no longer able to play these videos using the flash player. Things I have tried:
1. Rebooted tablet several times after firmware upgrade (read somewhere that doing so can help clear up any post upgrade playback/plugin issues).
2. Uninstalled and re-installed Adobe Flash using the same apk I had downloaded onto the tablet and used with prior versions of the official ICS on this tablet. (Rebooted couple times between uninstalling and reinstalling for same reason as above - couldnt hurt):
a) Uninstalled Adobe Flash, rebooted (couldnt hurt), cleared cache and data for various browsers, rebooted and re-installed Adobe flash.
However, I am still unable to get flash video (specifically Amazon Instant Videos) working on the table with any of the browsers listed above. Would appreciate if anyone could confirm whether or not this might be due to the new firmware or if there are other browsers that are confirmed working with flash videos on this new firmware.
Thanks,
-Topper
There are multiple variations of 4.0.28
Are you people aware of the fact that Archos has changed their official 4.0.28 firmware file released on their website several times already?
Listed below are the dates I downloaded what was listed as the 4.0.28 firmware, the size that was listed on the website at that time, and the true downloaded file size.
Feb. 25 -- Listed on site: 210,030 Kb -- Actual size: 215,070,152 bytes
Feb. 28 -- Listed on site: 210,040 Kb -- Actual size: 215,080,008 bytes
Mar. 02 -- Listed on site: 210,046 Kb -- Actual size: 215,086,104 bytes
And who knows just which one surdu_petru has been using for his rooted and custom ROM's?
Don't much matter to me anymore though because I've already found out that NO firmware (official from Archos, rooted, or custom ROM's) after 4.0.7 work correctly on my devices anyway.
My tablet not recognizing the aos file anywhere I put it
I downloaded the update this morning , at least they pushed out an update at all ...
Sent from my R800at
nswana said:
My tablet not recognizing the aos file anywhere I put it
Click to expand...
Click to collapse
Hi !
Yes, I know ...you need to reset your device to be able to put .aos file !
216Monster said:
I downloaded the update this morning , at least they pushed out an update at all ...
Sent from my R800at
Click to expand...
Click to collapse
Were did you place the update coz I have tried everywhere nothing is happening and I think i am missing aosupdate APk
55mls said:
Are you people aware of the fact that Archos has changed their official 4.0.28 firmware file released on their website several times already?
Listed below are the dates I downloaded what was listed as the 4.0.28 firmware, the size that was listed on the website at that time, and the true downloaded file size.
Feb. 25 -- Listed on site: 210,030 Kb -- Actual size: 215,070,152 bytes
Feb. 28 -- Listed on site: 210,040 Kb -- Actual size: 215,080,008 bytes
Mar. 02 -- Listed on site: 210,046 Kb -- Actual size: 215,086,104 bytes
And who knows just which one surdu_petru has been using for his rooted and custom ROM's?
Don't much matter to me anymore though because I've already found out that NO firmware (official from Archos, rooted, or custom ROM's) after 4.0.7 work correctly on my devices anyway.
Click to expand...
Click to collapse
Hi !
Root Firmware 4.0.28 was : 215,070,152 bytes :good:
Downloaded right now and you are right : 215.1 MB (215,086,104 bytes)
surdu_petru said:
Hi !
Yes, I know ...you need to reset your device to be able to put .aos file !
Click to expand...
Click to collapse
I just did the reset and still no luck and i cant even go in recovery mode when i press power and + volume
Hi all,
This is the rooted version of the stock firmware 4.0.28 published the 2nd Mach 2013 on Archos website.
As you know, Archos release 3 versions of the last firmware 4.0.28:
Feb. 25 -- Listed on site: 210,030 Kb -- Actual size: 215,070,152 bytes
Feb. 28 -- Listed on site: 210,040 Kb -- Actual size: 215,080,008 bytes
Mar. 02 -- Listed on site: 210,046 Kb -- Actual size: 215,086,104 bytes
surdu_petru rooted the first file version and had no time to root the last file version.
With this version, there was a bug during the boot: black screen and boot logo Archos for 3 sec just before the loock screen.
This issue is corrected in the firmware of the 2nd March.
So, with surdu_petru help, and with letama's scripts, i built a rooted firmware based on the 2nd March file.
Download :
please download from here all necessary files :
archos.ext4.update
zImage
initramfs.cpio.lzo
Archos_4.0.28_20130302.zip
Mirror:
Archos_4.0.28_20130302.zip
Installation :
connect USB cable ;
unzip Archos_4.0.28_20130302.zip into Archos_4.0.28_20130302 directory
copy archos.ext4.update in your device, or > adb push archos.ext4.update /mnt/storage
go to recovery SDE and Remove android kernel if you have already installed any official firmware !
go to Flash kernel & Initramfs and copy here zImage and initramfs.cpio.lzo from ( Archos_4.0.28_20130302)
Ok ! ... & wait to boot !
Now you have rooted the last Archos Firmware 4.0.28 - Android 4.0.4 !!!
Important :
1)Busybox 1.20.2r2 from linusyang is installed in /system/bin/
2)I used SuperSU from Chainfire for this release instead of Superuser.
So, after the first boot, you need to launch SuperSU in order to complete its installation.
The application will popup "SuperSU need to be upgraded. Continue?"
Click YES
On the new window, choose "NORMAL", and then click "YES" when the installation is succeed.
Best Regards.
SirOch
Hello.
Great job. I will replace my rom to this build.
Thanks.
freezenook said:
Hello.
Great job. I will replace my rom to this build.
Thanks.
Click to expand...
Click to collapse
You are welcome
Good luck for your ROM :good:
download impossible
SirOch said:
Hi all,
This is the rooted version of the stock firmware 4.0.28 published the 2nd Mach 2013 on Archos website.
http://uptobox.com/2rsli69gi9sy
SirOch
Click to expand...
Click to collapse
Hi,
i cannot download the firmware from your file hoster. Any other way to get the file? Can anybody share with me?
regards
4carlos said:
Hi,
i cannot download the firmware from your file hoster. Any other way to get the file? Can anybody share with me?
regards
Click to expand...
Click to collapse
Hi,
I added a mirror to hotfile :good:
Regards.
David
Nice
SirOch said:
I added a mirror to hotfile :good:
Click to expand...
Click to collapse
I got it.
Thanks!
Carlos
4carlos said:
I got it.
Thanks!
Carlos
Click to expand...
Click to collapse
good :good:
happy for you
Someone put file @ dropbox or else...
Very unpleasure those lame hotfile.com and other.!!!!
third revision is much better!
SirOch said:
good :good:
happy for you
Click to expand...
Click to collapse
firmware 4.0.28 / Mar. 02 fixes for me
- boot animation work again
- wifi is stable again - random disconnects are gone
- indexing of files during start up is much shorter
use 4.0.28 / Mar. 02 instead of 4.0.28 / Feb. 25 if you have the same problems from above :good:
in general it's nearly by my favorite 4.0.7.
regards
4carlos
4carlos said:
firmware 4.0.28 / Mar. 02 fixes for me
- boot animation work again
- wifi is stable again - random disconnects are gone
- indexing of files during start up is much shorter
use 4.0.28 / Mar. 02 instead of 4.0.28 / Feb. 25 if you have the same problems from above :good:
in general it's nearly by my favorite 4.0.7.
regards
4carlos
Click to expand...
Click to collapse
Hi,
Thank you for your feedback :good:
David
SirOch said:
As you know, Archos release 3 versions of the last firmware 4.0.28:
Feb. 25 -- Listed on site: 210,030 Kb -- Actual size: 215,070,152 bytes
Feb. 28 -- Listed on site: 210,040 Kb -- Actual size: 215,080,008 bytes
Mar. 02 -- Listed on site: 210,046 Kb -- Actual size: 215,086,104 bytes
surdu_petru rooted the first file version and had no time to root the last file version.
With this version, there was a bug during the boot: black screen and boot logo Archos for 3 sec just before the loock screen.
This issue is corrected in the firmware of the 2nd March.
Click to expand...
Click to collapse
Let's clarify things here... "as you know" is bogus crap... **I AM THE PERSON** that first posted any info about there being 3 different versions with the SAME firmware number (both here and over on archosfans.com). Very few people would actually know about it otherwise.
Second, you are also wrong about the boot screen fix. That WAS already in the Feb. 28 Archos firmware. I really do not know what the heck they changed between that one and the last release (I could not find anything at all that worked different other than the file size).
As such, the ONLY thing you got right is the fact that surdu_petru (as always) rushed out a firmware far to quickly and (since he no longer even has an Archos G9, can't even test it).
I DO appreciate your effort in making a more 'current' rooted version available for those people that 'think' it is worth having though. So, one thumb up, and one thumb down LOL.
i wonder
55mls said:
I really do not know what the heck they changed between that one and the last release (I could not find anything at all that worked different other than the file size).
Click to expand...
Click to collapse
Hmm, nobody said that surdu_petru did a bad job.
Maybe you could not find differences between the first and the third version of firmware, but the result is different (for me).
The firmware of 2nd march fixes 2 issues on my Archos 101 G9 that comes with the 1st rev. and i never had before and 1 older problem :
- Bootanimation,
- WiFi-Disconnections (faced up with 1st revision, always stable in the past),
- Endless file indexing after reboot since 4.0.26 (decreases from about 4 minutes to few seconds) and my tablet is now much faster ready to work.
I had/have no pictures, videos, music or other media files on my tablet.
I'm happy now to have my tablet back without (small) issues.
regards and thanks to all for the work
4carlos
Thanks for posting this rom. I went from the latest stock to the rooted 4.0.7, than to this rooted 4.0.28.
I will now see how things run rooted. Thanks again. :good:
4carlos said:
Hmm, nobody said that surdu_petru did a bad job.
Click to expand...
Click to collapse
I did not say, nor did I ever mean to imply that surdu_petru did a bad job (with any firmware he has released). What I WAS saying though is that he rushes out new releases within hours of any official Archos firmware release WITHOUT knowing what flaws are in the official firmware first. And, now he no longer even has a G9, so he can not even check problems in the official firmware anymore.
Just never made much sense to be spitting out new rooted versions BEFORE people even had a chance to report the flaws and problems with the official stock Archo version first. Anyway...
Maybe you could not find differences between the first and the third version of firmware, but the result is different (for me).
Click to expand...
Click to collapse
I did not say between the 1st and the 3rd. What I did say is that the 2nd one fixed the boot animation and I could not find anything else that worked any differently between the 2nd and the 3rd (other than the file size being different).
If anyone knows what else Archos changed/fixed in the 3rd one I'd love to hear about it? Of course, it WOULD be much nicer if Archos would be more honest and actually post that information in their change log to start with.
I am having some issues with this rom. Wi-fi is unable to connect if I used my Inet at work unless I did a reboot. When I returned home, it auto connected just fine. Some apps are dropping out unexpectedly like Asphalt 6 and Nook. I will have to keep playing with it and see what else happens.
Tweakurr said:
I am having some issues with this rom. Wi-fi is unable to connect if I used my Inet at work unless I did a reboot. When I returned home, it auto connected just fine. Some apps are dropping out unexpectedly like Asphalt 6 and Nook. I will have to keep playing with it and see what else happens.
Click to expand...
Click to collapse
Oh cheese I'm really sorry to hear that... NOT. I may come off sounding rude and obnoxious, but the fact of the matter is that ANY firmware after 4.0.7 is just horrible GARBAGE. Many people do not notice all the very little tiny flaws in the newer 4.0.2x firmware versions, but if you are seriously using you device for MANY things, well....
Various games do not run correctly, or the graphics do not display correctly... or the sound sometimes works, sometimes it doesn't, other times just quits somewhere in the middle.
Sometimes, even playing a video file is messed up... plays slightly faster than it should. There ARE a number of other things, but I won't list them all here... anyway...
I will not say that 4.0.7 was ever 100% perfect, but it did NOT have all the little idiot annoying flaws that are in the 4.0.2x firmware. Guess SOME PEOPLE don't do much more than web surffing, e-mail, or reading e-books. For those of us that do OTHER THINGS the flaws start showing up rather quickly.
I assume at some point the MOD's here will just start deleting my posts, but until they do I am going to keep repeating what I have said... any firmware above 4.0.7 is just PURE GARBAGE! Don't know why anyone would want it (official or rooted versions).
back to 4.0.7
i'm back on 4.0.7!
tired with nightly reboots, reboots during work. reboot within anywhere. my next tablet comes from anywhere but not from archos.i agree with @55mls and 4.0.7 should be the last firmware for my archos until it dies.
a disapointed customer
The problem with these devices is said to be that there are many hardware revisions. So some people see bugs that others do not. It's probably something to with hardware drivers not behaving identically across all revisions, or that some revisions simply have hardware problems. I've been on 4.0.28 for months and have been fine with it. 4.0.7 has annoying wifi problems on my 80 G9.
I would give Archos another chance but only after carefully reading the forums for the device. My 80G9 experience really hasn't been that bad, but that's mostly because I just got it 4 months ago and so didn't have to deal with the initial year of total **** firmware releases. I waited because 1) I had a Nook Color 2) I had read the forums early in 80G9 release days and saw it was a disaster.
swaaye said:
The problem with these devices is said to be that there are many hardware revisions. So some people see bugs that others do not. It's probably something to with hardware drivers not behaving identically across all revisions, or that some revisions simply have hardware problems. I've been on 4.0.28 for months and have been fine with it. 4.0.7 has annoying wifi problems on my 80 G9.
Click to expand...
Click to collapse
Maybe you are right, but 4.0.7 was the best for my 101G9 (first Generation, delivered with HC). Torture starts with 4.0.25 and 4.0.28 was much better, but it's not STABLE on my device. Unusable for me.
swaaye said:
I would give Archos another chance but only after carefully reading the forums for the device. My 80G9 experience really hasn't been that bad, but that's mostly because I just got it 4 months ago and so didn't have to deal with the initial year of total **** firmware releases. I waited because 1) I had a Nook Color 2) I had read the forums early in 80G9 release days and saw it was a disaster.
Click to expand...
Click to collapse
The 101G9 was'nt my first device. I had a 101G8 before and changed 3 times(!) because the USB-Connector did not work. Allways broken after view weeks and the second device did not charge properly. Bad hardware design i guess and I hoped the G9 was better, but it is not really! GPS did not work from the first day on until now, WiFi was problematic too (with Honeycomb) and the firmware? Some problems seems fixed, but i got new trouble every time with other things. I can accept small glitches but not reboot orgies even the device is untouched or is charging over night. My G9 lives a life of its own.
That's my experience. I surrender after 4 years. Archos, take my money and run.
Cyanogenmod 10.1 is looking really good. There are a few bugs left yet though. It could turn out to be the best firmware available. It's ridiculous that Archos said 4.2 on G9 was impossible.
Has anybody taken a look at the new official JB release that popped up at http://sbf.droid-developers.org/cdma_maserati/list.php ? (Although, I can't access it currently)
It's been mentioned on another thread (http://forum.xda-developers.com/showthread.php?t=2277830 ) regarding the ability to root, but it doesn't look like it's been looked at in any depth whether it includes any fixes, etc. The build date has changed to the 5th April, and the version is 9.8.20-72_VZW-18-2.
Cheers,
Steve.
This should probably be in q&a section... but yeah I wonder what is in it too... either way, I'm pretty happy sitting on eclipse 1.0.6 right now
Xoom'd using the XDA-Developers Android app
alex94kumar said:
This should probably be in q&a section... but yeah I wonder what is in it too... either way, I'm pretty happy sitting on eclipse 1.0.6 right now
Xoom'd using the XDA-Developers Android app
Click to expand...
Click to collapse
You could be right regarding the location, apologies if people object - I just thought the ROM guys would probably be the ones most likely to be all over it.
File Mirror
FWIW - I found that droid-developers.org seemed a little hit and miss, so I've set up a private file mirror for this new release. If somebody wants access to it, then just PM me. I'm trying to sort out a public mirror too, and will update this post when/if I get that sorted out.
Cheers,
Steve,
I am uploading cdma_maserati/cdma_maserati_9.8.2O-72_VZW-18-2_1ff.xml.zip
to my http://d-h.st/users/sd_shadow/?fld_id=12041#files
via remote url upload, usually doesn't take very long, quite a bit faster than uploading from my pc
This same version upgrade for XT926 HD appeared and was said to be a bugfix for the 4.1.2 OTA and that another more significant update would appear shortly for all devices but still remain 4.1.2 and would include Isis.
So we should expect to see a couple of OTAs pushed out on accelerated schedule that will match this XML file and the subsequent update.
sd_shadow said:
I am uploading cdma_maserati/cdma_maserati_9.8.2O-72_VZW-18-2_1ff.xml.zip
to my http://d-h.st/users/sd_shadow/?fld_id=12041#files
via remote url upload, usually doesn't take very long, quite a bit faster than uploading from my pc
Click to expand...
Click to collapse
Nice one - I'm currently 66% of the way through uploading to FileDropper (which I've never used before, but it was free, and didn't require sign up).
cellzealot said:
This same version upgrade for XT926 HD appeared and was said to be a bugfix for the 4.1.2 OTA and that another more significant update would appear shortly for all devices but still remain 4.1.2 and would include Isis.
So we should expect to see a couple of OTAs pushed out on accelerated schedule that will match this XML file and the subsequent update.
Click to expand...
Click to collapse
So is the "more significant update" meant to be coming after this April 5th release?
Cheers,
Steve.
It's safe for now...
StevePritchard said:
Nice one - I'm currently 66% of the way through uploading to FileDropper (which I've never used before, but it was free, and didn't require sign up).
So is the "more significant update" meant to be coming after this April 5th release?
Cheers,
Steve.
Click to expand...
Click to collapse
Yes, and I just flashed the boot, system and radio images from the MR2 XML and then rerooted using razr_blade.
So, we are safe to use this file to upgrade the firmware without any loss of root or any other issues.
The secure version did not increment so it is also possible to revert to the prior -18 release without risk of soft bricking.
This follows the pattern of the update for the HD and will likely be the same for the other devices that just recieved 4.1.2 in this cycle.
The next update is the one the will include ISIS and may also have security enhancements that will need to be carefully scrutinized.
That is conjecture on my part, at this stage, we don't know.
It would be nice to know what changes the release addresses. My hope is that it sorts out the hardware keyboard problem of unsticky shift keys in some applications.
Cheers,
Steve
Hello ,
I got my P7 for about 4 Months now,
and I wanted to have the EMUI 3.0 and Lolipop
but I think the Original System is 4.4.2 and Emui 2
I want to ask What can I do to Root or make a ROM (Sorry I really dont know he defrance total newbie ) , but I dont want to lose the support of Google or the Google Market , what should I do , can anyone help me in that ???
give me details and tell me what to do
thanks
look at this: http://forum.xda-developers.com/asc...7en-rom-v3-0-emui-3-0-4-4-2-18-11-14-t2945104
darkzero2022 said:
Hello ,
I got my P7 for about 4 Months now,
and I wanted to have the EMUI 3.0 and Lolipop
but I think the Original System is 4.4.2 and Emui 2
I want to ask What can I do to Root or make a ROM (Sorry I really dont know he defrance total newbie ) , but I dont want to lose the support of Google or the Google Market , what should I do , can anyone help me in that ???
give me details and tell me what to do
thanks
Click to expand...
Click to collapse
If you are newbie than do nothing ! Wait for official upgrade ! Because you will cry !
Sent from my HUAWEI P7-L10
Ziolek67 said:
If you are newbie than do nothing ! Wait for official upgrade ! Because you will cry !
Sent from my HUAWEI P7-L10
Click to expand...
Click to collapse
Really ???? Why ?? Huawei is too slow in making the Updates , all now is Andoird 5 and P7 is stuck in 4.4.2
It's proberly better staying on 4.4.2 than on lolipop. Many bugs on lolipop.
Sent from my HUAWEI P7-L10 using XDA Free mobile app
darkzero2022 said:
Really ???? Why ?? Huawei is too slow in making the Updates , all now is Andoird 5 and P7 is stuck in 4.4.2
Click to expand...
Click to collapse
Ok than lest go to update.... I will waiting for yours requests for help
darkzero2022 said:
Really ???? Why ?? Huawei is too slow in making the Updates , all now is Andoird 5 and P7 is stuck in 4.4.2
Click to expand...
Click to collapse
Wow do you realize android 5 has been out officially for a week or two and pretty much every phone apart from nexus which uses the software directly from Google themselves who make android, still don't run it yet and expect to be running it in 2015.
Not even big teams that use the aosp code directly such as cyanogen or paranoid have got a stable fully functional rom out yet.
It takes time for the 3rd party developers to customize and test android for there devices once the official version gets released as they all use the final source code which only has been out 3-4 weeks.
Also no company apart from Google is much better, Samsung are still rolling out 4.4 to some of there devices with some like the s2 still on 4.2 and end of life presumably others will jump straight to lollipop from 4.3 etc.
Also on rooting what do you wish to achieve by doing so?
Rooting can be very dangerous if you don't know what your doing with devices like ours.
Take a look for example at all the posts in this forum asking to downgrade their l10's from emui 3 to 2 which they upgraded to custom versions etc without thinking and the issues they now have with boot loops and stuff.
If you want to run xposed you can find many people with similar things recently in this forum that can't get it to work.
Also rooting etc you lose the ability for any future updates via OTA and recovery and would need to manually update your device potentially bricking it every single time which bricking means you can no longer use your device and have to buy a new one.
Also are you capible on the PC with using it, command prompt Linux shell etc and doing things like installing Windows and other things.
If not then rooting is not for you.
Also do you know how to code in Linux C etc and know the workings of the Linux os, if not then there is no way you are going to make a custom rom. All you might be able to achieve is just repackaging someone else's ROM with minor edits and even then the tools to do that mainly use Linux to run as it's native windows doesn't have all the stuff Linux has natively in this regard.
Ziolek67 said:
If you are newbie than do nothing ! Wait for official upgrade ! Because you will cry !
Sent from my HUAWEI P7-L10
Click to expand...
Click to collapse
drguild said:
Wow do you realize android 5 has been out officially for a week or two and pretty much every phone apart from nexus which uses the software directly from Google themselves who make android, still don't run it yet and expect to be running it in 2015.
Not even big teams that use the aosp code directly such as cyanogen or paranoid have got a stable fully functional rom out yet.
It takes time for the 3rd party developers to customize and test android for there devices once the official version gets released as they all use the final source code which only has been out 3-4 weeks.
Also no company apart from Google is much better, Samsung are still rolling out 4.4 to some of there devices with some like the s2 still on 4.2 and end of life presumably others will jump straight to lollipop from 4.3 etc.
Also on rooting what do you wish to achieve by doing so?
Rooting can be very dangerous if you don't know what your doing with devices like ours.
Take a look for example at all the posts in this forum asking to downgrade their l10's from emui 3 to 2 which they upgraded to custom versions etc without thinking and the issues they now have with boot loops and stuff.
If you want to run xposed you can find many people with similar things recently in this forum that can't get it to work.
Also rooting etc you lose the ability for any future updates via OTA and recovery and would need to manually update your device potentially bricking it every single time which bricking means you can no longer use your device and have to buy a new one.
Also are you capible on the PC with using it, command prompt Linux shell etc and doing things like installing Windows and other things.
If not then rooting is not for you.
Also do you know how to code in Linux C etc and know the workings of the Linux os, if not then there is no way you are going to make a custom rom. All you might be able to achieve is just repackaging someone else's ROM with minor edits and even then the tools to do that mainly use Linux to run as it's native windows doesn't have all the stuff Linux has natively in this regard.
Click to expand...
Click to collapse
Thanks For your Valuable words,
I really enjoyed them and get my mind open
well I do have Good Experience in linux and Command line , C Programming actually didnt go deep with it really ,
But i think I will stick to your opinion and wait ,and while I do so I will learn more about the whole subject ,and maybe increase my knowledge in this Field . (Android Programming - the C Programming - how things work in Android , ROMS , ETC)
but would you mind telling me from where to start ???
darkzero2022 said:
Thanks For your Valuable words,
I really enjoyed them and get my mind open
well I do have Good Experience in linux and Command line , C Programming actually didnt go deep with it really ,
But i think I will stick to your opinion and wait ,and while I do so I will learn more about the whole subject ,and maybe increase my knowledge in this Field . (Android Programming - the C Programming - how things work in Android , ROMS , ETC)
but would you mind telling me from where to start ???
Click to expand...
Click to collapse
Apologies if I came across about abit hard this forum has had allot of impatient people jumping in recently trying to run Emui 3 on l10's then asking to downgrade as you may have noticed the other teams like paranoid are already dealing with lots of people saying there to slow for not having lollipop out within a hour of aosp.
I had the same issue running a custom Minecraft server that people got really angry then refused to play and bad mouth the server if we didn't update that day when update time for us was about a week given the number of customizations we had 41 plugin's in the end, sometimes longer if there were more changes the mod and custom server devs had to deal with.
Emui 3 and lollipop has more bugs more as it's new from what I found I may start a proper consolidated emui talk thread later for those running it opposed to all the l10 when are we getting it out help me downgrade threads.
The place I think you should start is to download the source code for your version from the emui webpage and start analyzing it out of interest.
There's another Dev on here doing the same thing so you might want to contact him for info.
Also there are tools on Linux that easily let you unpack stock image files and the ext container and repack them.
That way you can see the full file structure and how a rom is packaged.
It's good just to see what's inside roms and how the first roms are usually made by a repackage before source.
I will stress the same as above that while these are starting points you would need to know what you are doing and something more hackable like a cheap nexus or or Chinese tab (about $50 USD) with easy upgradable firmware something would be better to start on.
Also grab down the android tools with eclypse for Linux, the sdk virtual device and have a play around making a app and stuff also you can edit the virtual rom safely etc.
The Linux version of the tools is far superior as you can natively mount the virtual ext cards for host file transfer and do other things which you can't under windows.
By ext above I mean the virtual partition files which are either ext 3 or 4 last time I looked.
I'm not a coder myself and I only did basic stuff in the past as I had a Chinese android 2.2 tablet the MID ones as my first device, I used a custom rom on which was just a repack with file system changes with bloat removed etc.
I looked into this out of interest and curiosity, each rom update I repacked it with the apps I used so I didn't need to reinstall them, there was probably a better (proper) way than just unpacking the ext file system from the img adding my apps in to the deploy folder and repacking.
Also I unpacked a APK weather app etc to make changes and use a custom background and others like themes to grab icons and assets this is a good start with looking at app packages and how that all works as well as making your own app in various tools eclipse for one which is the official tool but there's hundreds of android programming softwares online even to do simple stuff as make a stand alone html5 app from a webpage.
The tools on Windows I found were lacking and harder to find for the rom stuff, with Linux it was built into the system a lot of things.
What Linux is the best for doing Android stuff I don't know so that will need to be researched.
As mentioned devices can be dangerous for custom stuff especially newer ones with bootloader security, the older Chinese style ones and some others you could reflash easily from sdcard with a update.img file as they didn't contain that lock out security on boot and debugging.
I nearly bricked a few devices in the past, once having to rely on the bootloader and Android Commander a powerful tool and device terminal to mount the partition rw while in the bootloader to rename a file backI renamed as a test that caused the system to stop booting.
You can still get some tabs that do that about 50 USD on eBay etc I think.
darkzero2022 said:
Hello ,
I got my P7 for about 4 Months now,
and I wanted to have the EMUI 3.0 and Lolipop
but I think the Original System is 4.4.2 and Emui 2
I want to ask What can I do to Root or make a ROM...
Click to expand...
Click to collapse
I'd strongly advise that you wait. My experience. You can root v4.4.2 VERY easily using vroot. Wait for lollipop, honestly. Is a nightmare recovering your position if you try to move now.
Sent from my HUAWEI P7-L10 using XDA Premium HD app
Hello, it appears that ever since I switched to Project Fi from ATT, I'm starting to see some 'bugs'. I noticed that my current build number of LYM48I is older, and a generic firmware image. I'm wondering if I should upgrade to LVY48H, which according to (https://developers.google.com/android/nexus/images) appears to be the latest Project Fi image for the Nexus 6?
Quick details about my setup:
- I am on the Nexus 6 (purchased directly from Google)
- Android version 5.1.1
- Build number LMY48I
- Baseband version MDM9625_104446.01.02.101R
- I don't want to upgrade to 'Marshmallow' as from what I've read, is not officially supported by Fi
- My phone was rooted before switching over to Fi using the following procedure: http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481 (did not create a custom recovery, etc)
Thanks in advance
gil_happy said:
Hello, it appears that ever since I switched to Project Fi from ATT, I'm starting to see some 'bugs'. I noticed that my current build number of LYM48I is older, and a generic firmware image. I'm wondering if I should upgrade to LVY48H, which according to (https://developers.google.com/android/nexus/images) appears to be the latest Project Fi image for the Nexus 6?
Quick details about my setup:
- I am on the Nexus 6 (purchased directly from Google)
- Android version 5.1.1
- Build number LMY48I
- Baseband version MDM9625_104446.01.02.101R
- I don't want to upgrade to 'Marshmallow' as from what I've read, is not officially supported by Fi
- My phone was rooted before switching over to Fi using the following procedure: http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481 (did not create a custom recovery, etc)
Thanks in advance
Click to expand...
Click to collapse
lol, not officially supported by fi. you do realize that the n5x and n6p are both fi phones, right? and you do realize that they both come with marshmallow, right? marshmallow is the build that you should be on, as in its the latest. and there isnt a special m build for fi. there's only ine build if marshmallow, and its for fi as well.
..
Great! Thanks so much.... I guess my question is this , which method should I use to upgrade to Marshmallow? Will I lose all of my data? Keep in mind I 'only' rooted my device using the link in my original post.
..
gil_happy said:
Great! Thanks so much.... I guess my question is this , which method should I use to upgrade to Marshmallow? Will I lose all of my data? Keep in mind I 'only' rooted my device using the link in my original post.
Click to expand...
Click to collapse
cam30era said:
You're going to get plenty of advice on that question from other members. Let's just say, read, understand, and pick your poison.
Click to expand...
Click to collapse
fastest and easiest thing to do would be to flash the factory image. right way is via fastboot while youre in the bootloader. but there are ways using a toolkit as well.
..
cam30era said:
While Project Fi team did originally state that they did not recommend flashing MRA58K, that position changed about 10/15, when the OTA started rolling out to Fi users.
Click to expand...
Click to collapse
Source, please? In the official Project Fi support forum, the company line has not changed. See the relevant thread from the forum's most official spokesperson. It has never been superseded.
Thanks for this... do both methods completely 'wipe' the phone of all its data?
..
cam30era said:
The best source is the OTA from LVY48H to MRA58K that is rolling out to Fi users.
Click to expand...
Click to collapse
I know that the OTAs exist and that most of their URLs have been discovered by the community. That's not the point. I was challenging your assertion that the official policy of Project Fi opposing the flashing of factory image MRA58K has been withdrawn. It has not. For that matter, they have never announced an official rollout of the Marshmallow OTAs. With previous OTAs, there has been such an announcement.
..
cam30era said:
Granted. Google is in an untenable position here. Caught between a rock and a hard point when they started pushing OTAs to Fi users on the one hand...
So, what's your advice to the OP?
Click to expand...
Click to collapse
Depends on his risk tolerance. As a purely technical matter, nothing prevents him from flashing any build he wants. If he prefers an officially sanctioned OTA path, he should probably sit tight and wait for Marshmallow to be pushed out to him.
His concern that he is on the "wrong" build within 5.1.1 is misplaced. Project Fi officially supports three different Lollipop forks: the Fi-specific builds, the T-Mobile builds, and the generic Nexus builds. There will be an OTA path from each fork to the new unified Marshmallow. (But one messy detail is that the most recent round of security updates also spawned a fourth AT&T fork build LMY48W, which so far has no OTA path to 6.0. Some Fi users report that they have been OTAed to LMY48W .)
Personally, I use a daily driver on FI that runs the T-Mobile fork, and I want to keep it stock. I am in no hurry to flash the Marshmallow build because of multiple reports that doing so would probably break my existing Band 12 data service, which I want to keep as long as possible. So I am awaiting the OTA to be pushed out officially, and hoping that the Band 12 issue gets resolved soon somehow, even if that is a subsequent build.
I would assume the reason for the 3 forks is that there must be specific fixes or enhancements to each firmware load, otherwise what is the point of having 3 forks? Meaning, since I'm on Project Fi, it would make sense to be on the specific Project Fi load and not the T-Mobile or generic Nexus build.
gil_happy said:
I would assume the reason for the 3 forks is that there must be specific fixes or enhancements to each firmware load, otherwise what is the point of having 3 forks? Meaning, since I'm on Project Fi, it would make sense to be on the specific Project Fi load and not the T-Mobile or generic Nexus build.
Click to expand...
Click to collapse
We really don't know what was different about the Fi-specific build. Google claimed the difference was not very significant, but never disclosed what it was. The T-Mobile fork was created to support TMO's proprietary WiFi calling. And of course the generic Nexus fork was mainstream Android. It might be that Project Fi management just kept all three as officially supported because they wanted to test performance with three different radios. Remember, it is all beta (or beta-like), and we are all lab rats.
People speculated about the relative merits of the Fi build for months, with no rigorous testing that really proved anything beyond anecdotal placebo effects. But all this specualtion is about to become ancient history with the unification in Marshmallow. This is supposed to happen OTA any day now, and already has happened for some. So I can't see any great value in flashing the old Fi build at this point because it isn't worth the hassle. But it would do no harm.
boomerbubba said:
We really don't know what was different about the Fi-specific build. Google claimed the difference was not very significant, but never disclosed what it was. The T-Mobile fork was created to support TMO's proprietary WiFi calling. And of course the generic Nexus fork was mainstream Android. It might be that Project Fi management just kept all three as officially supported because they wanted to test performance with three different radios. Remember, it is all beta (or beta-like), and we are all lab rats.
People speculated about the relative merits of the Fi build for months, with no rigorous testing that really proved anything beyond anecdotal placebo effects. But all this specualtion is about to become ancient history with the unification in Marshmallow. This is supposed to happen OTA any day now, and already has happened for some. So I can't see any great value in flashing the old Fi build at this point because it isn't worth the hassle. But it would do no harm.
Click to expand...
Click to collapse
Thanks again.... I will attempt to upgrade to Marshmallow in the next day or so after a little more reading about 'how' to do this. As mentioned, I am rooted (no recovery) and will need to find out which of the 2 upgrade methods erase the phone.
I'm on a custom Marshmallow ROM (PureNexus) and easily activated Fi on it. Here's what I did, using a custom recovery (TWRP):
- downloaded M bootloader and M radio, PureNexus ROM and Gapps, and FiFix for dialer
- rebooted into TWRP
- removed my old carrier's SIM and left the SIM slot empty
- flashed M bootloader and M radio
- wiped everything except internal storage
- flashed PureNexus and its Gapps, and Fi Fix for dialer.
- booted and setup wizarded the new ROM on wifi, and updated ALL apps (most importantly Fi, Hangouts and Messenger, though I don't use the latter two) in Play. Had to enable Fi in Settings/Apps/Fi for it to updated by Play. Also allowed all permissions for Fi.
- put the Fi SIM into phone
- finally, ran the Fi app...
DONE.
Hope this is helpful to someone!
Sent from my Nexus 6 using Tapatalk
gil_happy said:
Thanks again.... I will attempt to upgrade to Marshmallow in the next day or so after a little more reading about 'how' to do this. As mentioned, I am rooted (no recovery) and will need to find out which of the 2 upgrade methods erase the phone.
Click to expand...
Click to collapse
I'm on Fi and upgraded to MM using the recovery flashable mages found in this thread. Make sure to read the entire op and also flash the bootloader and radio zips. Fi activated on my first boot and has functioned properly since.
A follow up to this... now today, my phone indicates I have a 'System upload downloaded' notification. When I try to install it, it fails. I believe this is because I have read something in the past that indicated it fails because my phone is rooted (and would need to be manually installed). If I'm going to attempt to manually install, is there any way to figure out via shell, ES File Explorer, etc what the name of this firmware is so that I can attempt to find it online somewhere and download?
Thanks in advance