Related
Hi, today I've received an OTA update for my IdeaPad A3000-H (3G+WiFi, 16GB).
Old version: A3000_A422_011_022_140127_WW_CALL_FUSE
New OTA version: A3000_A422_013_025_140624_WW_CALL_FUSE
For now, the only thing I noticed was the different boot animation.
I have attached the image of the updated version (The language is set to Italian).
Download old version (140127) from here:
https:*//copy.com/qCjNzpBfyFrRB4hp
and Flash Tool (ver. 3.1336.0.198) from here
https:*//copy.com/fmqX4YR9FphdBAQS
Source: http:*//lenovo-forums.ru/topic/6218-rom-a3000-a422-011-022-140127-ww-call-fuse/
NOTE: remove * from links!
Hi there,
I received the same update today, but after downloading and rebooting, nothing happened, the update simply not installed!
After some useless retries, I used the CWM to install the archive from the folder sdcard0/googleota/ and it did work, for no clear reasons..
The difference so far I notice is only the boot logo ? but I believe there should be other benefits
Sent from my Lenovo A3000-H using XDA Premium 4 mobile app
faissl said:
Hi there,
I received the same update today, but after downloading and rebooting, nothing happened, the update simply not installed!
After some useless retries, I used the CWM to install the archive from the folder sdcard0/googleota/ and it did work, for no clear reasons..
The difference so far I notice is only the boot logo ? but I believe there should be other benefits
Sent from my Lenovo A3000-H using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi, its very strange... but its important that you were able to install it!
However, my device isn't rooted and maybe, in your case, CWM has blocked update... (this happened to me on a rooted smartphone!)
With this OTA update, my A3000 seems more stable, with fewer reboots than before (old version: once a day; new version: once a week!)
Plz link of update
Where is the link for the new update
Braveheart850 said:
Where is the link for the new update
Click to expand...
Click to collapse
This new update is only OTA!
To get this OTA update, you must have the "old" version, dated 2014-01-27!
Then search new version, from Android settings (see attached image)!
Here is the link! (remove * )
https:*//copy.com/qCjNzpBfyFrRB4hp
brunix86 said:
Hi, its very strange... but its important that you were able to install it!
However, my device isn't rooted and maybe, in your case, CWM has blocked update... (this happened to me on a rooted smartphone!)
With this OTA update, my A3000 seems more stable, with fewer reboots than before (old version: once a day; new version: once a week!)
Click to expand...
Click to collapse
Strange, this is never happened with my Sony Xperia tipo.. Anyway, you are missing a lot with your mobile not being rooted ?
I noticed the battery life got somewhat longer, there still no way to move apps to the sdcard.
And the Android version still the same ???? #I_want_Kitkat (Heh, don't be silly.. The update was just 3.5Mb or so)
I forget to tell you that it you use my method of CWM upgrade and tried to check for other system updates you will be greeted with the same update install screen! Don't panic, Your system has already been updated.
Fix: just remove/rename the Googleota folder and retry update check, You should be refreshed with calming screen that tells you how you already have the latest version..
Sent from my Lenovo IdeaPad A3000-H using XDA mobile app
faissl said:
Strange, this is never happened with my Sony Xperia tipo.. Anyway, you are missing a lot with your mobile not being rooted ?
I noticed the battery life got somewhat longer, there still no way to move apps to the sdcard.
And the Android version still the same ???? #I_want_Kitkat (Heh, don't be silly.. The update was just 3.5Mb or so)
I forget to tell you that it you use my method of CWM upgrade and tried to check for other system updates you will be greeted with the same update install screen! Don't panic, Your system has already been updated.
Fix: just remove/rename the Googleota folder and retry update check, You should be refreshed with calming screen that tells you how you already have the latest version..
Sent from my Lenovo IdeaPad A3000-H using XDA mobile app
Click to expand...
Click to collapse
You're right! On smartphone I have TWRP, not CWM!
However, for now, I'm fine with the stock firmware (In the future I will evaluate to flash an unofficial ROM)
The battery works two days (over 24 hours, tablet is turned off at night) of normal use (wifi on, 3g on, bluetooth on, several phone calls every day, several app with push notifications).
In addition, 16 GB are so many, while having numerous apps installed (more than smartphone).
In the MicroSD card (the other 16 GB) I'll put my music, pictures and videos made with the camera!
I think it's unlikely that we'll see KitKat on A3000... All I want is find a solution to the problem of BT headset that does not detect anything when I use voice commands or voice recorder!!
The stock rom is just too good to be replaced ? the only feature I really miss is CM theme chooser because I don't like the default white on black theme of the settings' screens.. Sigh, you can't have everything, this device is by far the best I ever had.
Sent from my Lenovo IdeaPad A3000-H using XDA mobile app
update
brunix86 said:
Hi, today I've received an OTA update for my IdeaPad A3000-H (3G+WiFi, 16GB).
Old version: A3000_A422_011_022_140127_WW_CALL_FUSE
New OTA version: A3000_A422_013_025_140624_WW_CALL_FUSE
For now, the only thing I noticed was the different boot animation.
I have attached the image of the updated version (The language is set to Italian).
Download old version (140127) from here:
https:*//copy.com/qCjNzpBfyFrRB4hp
and Flash Tool (ver. 3.1336.0.198) from here
https:*//copy.com/fmqX4YR9FphdBAQS
Source: http:*//lenovo-forums.ru/topic/6218-rom-a3000-a422-011-022-140127-ww-call-fuse/
NOTE: remove * from links!
Click to expand...
Click to collapse
Even though there seems to be no new feature, I noticed that my tablet seems more responsive to touch and the boot animation and boot time have changed. The boot time has considerably come down. Thank you for providing the link and info
Hello,
A few months ago I purchased a previously owned Samsung Galaxy Tab Pro 8.4. The tab has been rooted, as SuperSU is " installed " and functioning. To be sure I don't brick the device, I am reaching out for suggested next steps.
Long story short, the battery life of this tab has become horrible. To rub salt in the wound, I generally have to reboot it 3-5 times just to get it to start charging. I have read on a different thread that this isn't uncommon, and that the ROM might have a bug in it causing this.
I believe the next step is to flash a different ROM. However, I don't know which way to go as I cant tell what recovery this device is running, or even what mod could be running. (I have a feeling the stock recovery is still intact.)
I would imagine that my next step is dependent on confirming the recovery that is running. If so, is it possible to figure out ? (picture of recovery boot attached) ...Just found out new members are not allowed to include pictures in posts )
Device detail, all obtained from Settings>Device>About:
-Model: SM-T320 (wifi only version)
-Android version: 4.4.2
-Kernel version: 3.4.0-3264497
[email protected] #1 - Tue Nov 11, 2014
-Build Number: KOT49H.T320UEU1ANK1
-When clicking the Status menu, it is noted that the device status is " Custom "
When attaching the picture, i just realized that the Build number reflected within the settings app differs from the build listed in the recovery boot screen........
Thank you all in advance! I am VERY new to android and a huge rookie.
Flash TWRP via Odin and flash CM12.1 in that. Ditch TouchWiz for a better experience.
And for the battery problem you mentioned, you might want to take a look at the battery reseating thread which is somewhere around our device subforum.
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
AndyYan said:
Flash TWRP via Odin and flash CM12.1 in that. Ditch TouchWiz for a better experience.
And for the battery problem you mentioned, you might want to take a look at the battery reseating thread which is somewhere around our device subforum.
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
Click to expand...
Click to collapse
Thank you !
I am finding that the CM12.1 ROM is Lollipop. Do I need to update my tab to lollipop first, or is the OS with the ROM ?
again, i am very new to Android. i apologize if this is a silly question...
APT082 said:
Thank you !
I am finding that the CM12.1 ROM is Lollipop. Do I need to update my tab to lollipop first, or is the OS with the ROM ?
again, i am very new to Android. i apologize if this is a silly question...
Click to expand...
Click to collapse
Nope, just start flashing from whatever version you're already on. The TabPRO 8.4 doesn't have official Lollipop yet, by the way.
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
AndyYan said:
Nope, just start flashing from whatever version you're already on. The TabPRO 8.4 doesn't have official Lollipop yet, by the way.
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
Click to expand...
Click to collapse
I apologize for the delay. My ISP has been down for a few days now.
I flashed TWRP via Odin and downloaded the latest release of CM 12.1 ( mondrianwifi ).
When flashing the zip through TWRP;
Cant install this package on top of incompatible data. Please try another package or run a factory resetE: Error executing update binary in zip 'file location and name'
I wiping cache/dalvik, but this didnt help.
Any additional advice ?
again, thank you.
-- I just performed a factory data reset, and experience the same error when trying to flash the CM12.1 ZIP via TWRP.
APT082 said:
I apologize for the delay. My ISP has been down for a few days now.
I flashed TWRP via Odin and downloaded the latest release of CM 12.1 ( mondrianwifi ).
When flashing the zip through TWRP;
Cant install this package on top of incompatible data. Please try another package or run a factory resetE: Error executing update binary in zip 'file location and name'
I wiping cache/dalvik, but this didnt help.
Any additional advice ?
again, thank you.
-- I just performed a factory data reset, and experience the same error when trying to flash the CM12.1 ZIP via TWRP.
Click to expand...
Click to collapse
Sorry I missed your post. It should just be a matter of wiping both /data and /system - at least it worked for me that way.
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
Unofficial LineageOS 13 (Android Marshmallow) for JBBL dated March 18, 2017 from the 4PDA forums courtesy of developer ilichva!
Again, this is only for JBBL. Flash at your own risk and please do a nandroid backup prior to doing so!
All credits and thanks go to the original developer ilichva!
____________________________________________
Latest Build - LineageOS 13:
lineage-13.0-20170318-port-ilichva-xt907_jbbl.zip (405.4 MB)
Mega
SolidFiles
PCloud
MD5 :: 63FB23666399844E5BB7A8D9C347374D
____________________________________________
Prior Build - CM13:
cm-13.0-20161205-ilichva-xt907_jbb.zip (411.9 MB)
Original Link
Mega
SolidFiles
PCloud
MD5 :: 3c786a57929d024010a0fce36287ea7d
____________________________________________
NOTE: If you are on KitKat Bootloader (KKBL), you will need to revert to the JellyBean Bootloader (JBBL) before you can flash this ROM. Instructions on how to do so may be found here and here and here
____________________________________________
Latest TWRP 3.0.2 recovery by ilichva may be found/downloaded here
Updated to 03.25.2016 build
Hallo Rahimali
Thanks for the share. I have tried this and apparently works ok. I'm unable to get WiFi working. Tried different gapps but there are force close issues. Any recommended gapps versions available?
Opengapps usually does the job. Flashing gapps with marshmallow is different than with prior android versions. With MM you have to flash gapps immediately after you flash the ROM (before booting up the ROM for the first time). Try and see if that resolves your FC issues
Updated to April 02, 2016 build!
I managed to get the force close issues resolved. Everything works fine except Wifi. I am unable to enable wifi as the button is greyed out. I tried enabling wifi from terminal using svc wifi enable, it enabled the button but wouldnt detect any available wireless networks. Any fixes for this?
Updated to April 05, 2016 build!
ultrasoniic said:
I managed to get the force close issues resolved. Everything works fine except Wifi. I am unable to enable wifi as the button is greyed out. I tried enabling wifi from terminal using svc wifi enable, it enabled the button but wouldnt detect any available wireless networks. Any fixes for this?
Click to expand...
Click to collapse
Sorry no idea. Nobody is complaining in the 4pda forums about any WiFi issues. Did you do a clean flash? Maybe the developer, @ilichva can help?
bootloader and recovery
My XT907 is showing that my bootloader is "0x109B" and I am unsure what version of TWRP supports 6.0.1 (currently running 2.8.6.0)
Can anyone verify their settings and let me know?
I am running CM12.1 currently, so I should be able to dirty flash correct?
Thanks guys!
KKBL?
Anyone know of a marshmallow based rom that works with the kitkat bootloader for this device?
crzypcdude said:
Anyone know of a marshmallow based rom that works with the kitkat bootloader for this device?
Click to expand...
Click to collapse
Marshmallow not yet available on KKBL
rahimali said:
Marshmallow not yet available on KKBL
Click to expand...
Click to collapse
Are there any significant reasons to stay on the KitKat bootloader? Otherwise I'll just downgrade now that I'm rooted with an unlocked bootloader.
One of the most compelling reasons to stick with the KKBL would be the availability of the 3.4x kernel as opposed to the 3.0x kernel on the JBBL but feel free make your own decision. I was on the JBBL (by choice) for a considerable length of time without any apparent side effects...
Would you mind adding dates to post #1?
Any updatefor this rom?
crzypcdude said:
Would you mind adding dates to post #1?
Click to expand...
Click to collapse
The dates are already present in post #1 as well as in the filenames.
dedik46 said:
Any updatefor this rom?
Click to expand...
Click to collapse
Updated!
Are all the builds being updated in the 4PDA post linked in #1 as well as TWRP builds?
crzypcdude said:
Are all the builds being updated in the 4PDA post linked in #1 as well as TWRP builds?
Click to expand...
Click to collapse
That is correct.
Confirmed Working!
Can confirm this works, flashed the recovery included in the 4pda post, used it to flash the rom, gapps, and supersu. Initially booted up in Russian, but after waiting for 30 seconds or so, switched to English on its own. Setup was flawless after that, no issues to report as of now. Anyone that needs help installing the rom or downgrading from kitkat to jellybean just message me.
I thought I was the only one that ended up with default language in Russian... All the previous builds defaulted to English on install... Also when I downloaded the latest update it downloaded on my phone as a .bin not a .zip I checked the file size and contents vs what is online (after changing the extension to .zip) and everything seemed to be Ok so I installed and been up and running on latest version for 24 hours....
Had a few FC's in the beginning while changing the language to English (I have a feeling that some of my already installed apk's caused the issue) . I did do a test run before restoring my stuff and didn't have any issues during initial setup and the phone auto corrected language based off sim during initial setup.
Haven't gotten a chance to fully test this build, but I know that the issue that I was having with the native tethering soft rebooting the phone every couple of hours when active is gone! After a few more days of messing with it I will post any other issues that I come across
Sent from my Moto Razr M on cm13 4-16-16 using XDA Free mobile app
Any clue about why I'm getting error 7 while finishing the last steps of the ROM flashing procedure?
Stock ROM Elephone P90000_Android_6.0_20160401 (Beta)
Download - https://mega.nz/#!w4BBnKaR!_WU3BeucmEURhgo8VpvspHMVZngL7ctzd29mx6cn2BQ
XDA:DevDB Information
[ROM] Stock ROM Elephone P9000_Android_6.0_20160401_Beta, ROM for the Elephone P9000
Contributors
Jonny
ROM OS Version: 6.0.x Marshmallow
Based On: AOSP
Version Information
Status: Beta
Current Beta Version: 20160401
Beta Release Date: 2016-04-04
Created 2016-04-19
Last Updated 2016-04-19
Has someone give this Beta a try?
Trying now, just be aware that flashing WILL completely wipe your phone again... Everything is gone...
Seriously though, how hard is it to NOT wipe everything like, oh i don't know, every other phone out there...
There is not much difference between this and the last OTA update, I have found the fingerprint sensor a little better but even the security patch level says 1 March 2016... Can't say anything about battery life yet, I find it usually takes 3 days for that to settle but I really haven't seen much difference in UI or settings. Most changes must be "under the hood" so to speak... Doesn't help there's no changelog...
Found the case doesn't seem to register being closed easily so it just leaves the phone on even though I have the original case that has the screen cutout for clock and whatnot.
Keyboard still doesn't support swype...
ultramag69 said:
Trying now, just be aware that flashing WILL completely wipe your phone again... Everything is gone...
Seriously though, how hard is it to NOT wipe everything like, oh i don't know, every other phone out there...
There is not much difference between this and the last OTA update, I have found the fingerprint sensor a little better but even the security patch level says 1 March 2016... Can't say anything about battery life yet, I find it usually takes 3 days for that to settle but I really haven't seen much difference in UI or settings. Most changes must be "under the hood" so to speak... Doesn't help there's no changelog...
Found the case doesn't seem to register being closed easily so it just leaves the phone on even though I have the original case that has the screen cutout for clock and whatnot.
Keyboard still doesn't support swype...
Click to expand...
Click to collapse
Untick the userdata.img if you don't want your data to be wiped.
racer290 said:
Has someone give this Beta a try?
Click to expand...
Click to collapse
Been running this for a number of days now, not run into any problems except it was slightly more difficult to root, lot of trial and error but I'm going to post a tutorial on how I rooted it later today.
Jonny said:
Been running this for a number of days now, not run into any problems except it was slightly more difficult to root, lot of trial and error but I'm going to post a tutorial on how I rooted it later today.
Click to expand...
Click to collapse
Correction, someone has already posted the method here >>> http://forum.xda-developers.com/elephone-p9000/how-to/how-to-root-elephone-9000-stock-rom-t3359315
The tutorial in the link above works for this firmware version as well.... could have saved myself a lot of time if I'd read that first lol. For convenience I've put all the files needed in a zip file (link below). Just use SP Flash Tool to flash the recovery, then flash the 2 other zip files from TWRP
ZIP File >>> https://mega.nz/#!IlgxgDhS!r6_OpFYLVv07o025ecJ9rDul2db1KMsoWAlZbabWMxI
trying to flash this but SPTools (5.1520.00) giving me "Error: Initializing scatter file failed. Please check the name of the scatter file which you load is legal" any ideas as to why? I have tried the other rom listed that isn't the BETA and get the same error...
Also, I don't appear to have the Allinone.bin file for the DownloadAgent, can someone please share that too me?
Thanks
Ignore that, I seem to have got it working.
Where do you get these ROMS from? I'm looking for rom version 20160318 for the p9000 lite.
karl0ss said:
trying to flash this but SPTools (5.1520.00) giving me "Error: Initializing scatter file failed. Please check the name of the scatter file which you load is legal" any ideas as to why? I have tried the other rom listed that isn't the BETA and get the same error...
Also, I don't appear to have the Allinone.bin file for the DownloadAgent, can someone please share that too me?
Thanks
Ignore that, I seem to have got it working.
Click to expand...
Click to collapse
use ever latest sp flashtool!
5.1604 or newer for Android 6 and P10 chipset
megthebest said:
use ever latest sp flashtool!
5.1604 or newer for Android 6 and P10 chipset
Click to expand...
Click to collapse
I could only get 5.1604 working, 5.1612 wouldn't work for me at all on Windows 10 in VirtualBox.
This is officiel or not ? and GPS work for you on this rom ? is it based on 20160315 ?
Bradco said:
This is officiel or not ? and GPS work for you on this rom ? is it based on 20160315 ?
Click to expand...
Click to collapse
please read.. is not based on 20160315 .. is a new stock rom 1st of April.. but still in beta stage..
I hear about a new OTA here http://forum.xda-developers.com/elephone-p9000/help/ota-update20160319-t3364691
megthebest said:
please read.. is not based on 20160315 .. is a new stock rom 1st of April.. but still in beta stage..
I hear about a new OTA here http://forum.xda-developers.com/elephone-p9000/help/ota-update20160319-t3364691
Click to expand...
Click to collapse
Ok thanks
Hi and sorry for the potential newb post
Been using CM / Lineage for years and never come across an individual firmware upgrade requirement until now.
I am on Lineage nightly Feb 8th and cant go any further due to:
comparing tz version TZ.BF4.0.1-83199 to tz.bf.4.0.1-76917
assert failed: oppo.verify_trustzone("TZ.BF.4.0.1-81399") == "1"
updater process ended with ERROR: 7 error installing zip file
I have the working 1+3 TWRP installed so Is it possible to upgrade the firmware only?
Or do I have to wipe and install the latest OOS then go back to Lineage?
I downloaded OOS 41 and there is a firmware folder in there with a few bin / mbn files so kinda hoping I can somehow flash just the firmware and keep my build.
Appreciate any help....
Cheers
Gaz
Here is the latest firmware (4.0.3). Download firmware + modem and flash in TWRP before LineageOS.
Spot on - thanks Fam im sorted
Familotel said:
Here is the latest firmware (4.0.3). Download firmware + modem and flash in TWRP before LineageOS.
Click to expand...
Click to collapse
great work!thanks
Familotel said:
Here is the latest firmware (4.0.3). Download firmware + modem and flash in TWRP before LineageOS.
Click to expand...
Click to collapse
Hey there, sorry to bug you guys. Unfortunately I'm noob so I can't comment on the main LOS thread, but I have an issue that hopefully someone can help with. Originally on CM14 nightlies, without any dramas, obviously with the change from CM on LOS I've flashed the experimental build, then the LOS nightly to get started, all went fine until the change to unified requiring the firmware update. I've installed 2nd March nightly (by editing the file to ignore the trustzone version) in case it was that, but no seems not.
I've flashed the latest FW as mentioned, and the Baseband version is M8996FAAAANAQM-1.85373.1.86546.1 so it appears I'm running definitely running the latest FW (and there were no errors on install) I then reboot to system, download the latest nightly and go to install - still getting the TZ.BF.4.0.1-83199 to TZ.BF.4.0.1-85373 error.... Have I missed a step somewhere? or is this blindingly obvious and I'm a muppet?
Any helps appreciated! cheers
Same issue with the same parameters!
Z-master said:
Hey there, sorry to bug you guys. Unfortunately I'm noob so I can't comment on the main LOS thread, but I have an issue that hopefully someone can help with. Originally on CM14 nightlies, without any dramas, obviously with the change from CM on LOS I've flashed the experimental build, then the LOS nightly to get started, all went fine until the change to unified requiring the firmware update. I've installed 2nd March nightly (by editing the file to ignore the trustzone version) in case it was that, but no seems not.
I've flashed the latest FW as mentioned, and the Baseband version is M8996FAAAANAQM-1.85373.1.86546.1 so it appears I'm running definitely running the latest FW (and there were no errors on install) I then reboot to system, download the latest nightly and go to install - still getting the TZ.BF.4.0.1-83199 to TZ.BF.4.0.1-85373 error.... Have I missed a step somewhere? or is this blindingly obvious and I'm a muppet?
Any helps appreciated! cheers
Click to expand...
Click to collapse
Hi, I have the exact same issue. I've flashed the firmware to 4.0.3 and successfully installed the nightly from 08/02/2017. Now when I try to flash the nightly from 09/03/2017 I get this issue again! This time nothing helps so far.
Please, if you find a solution - let me know!
devianity said:
Hi, I have the exact same issue. I've flashed the firmware to 4.0.3 and successfully installed the nightly from 08/02/2017. Now when I try to flash the nightly from 09/03/2017 I get this issue again! This time nothing helps so far.
Please, if you find a solution - let me know!
Click to expand...
Click to collapse
Install the firmware from the Open Beta here:
https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
Yeah i had the same issue - open beta 12 is required for the 9th Mar build