Develop Bugs

I9000XWJG5 released

did any one know it support Chinese or not?

great! gonna check it out later

daduzzo888 said:
great! gonna check it out later
Click to expand...
Click to collapse
I'm downloadin' it now! Wait a while...

New European FW - I9000XWJG5
Changelog:
- improved energy management in suspend mode
- updated YouTube, Google Maps
- Change Low-memory Killer Thread
- many minor fixes

Where did you find the changelog for this release?
Thanks

I am having trouble getting this firmware to work :S Anyone get it working?
EDIT: After I flash the 3 files including the CSC, MODEM and CODE file.
I get this error after flashing:
update media, please wait
E:Can't mount /dev/block/stl10
(Invalid Argument)
E:copy_dbdata_media:Can't mount DBDATA:
copy default media content failed.
Click to expand...
Click to collapse
What the hell is that error?

galaxy_s said:
I am having trouble getting this firmware to work :S Anyone get it working?
EDIT: After I flash the 3 files including the CSC, MODEM and CODE file.
I get this error after flashing:
What the hell is that error?
Click to expand...
Click to collapse
re-partition maybe, if you had the lag fix, that might mess something up... perhaps

buddy01 said:
re-partition maybe, if you had the lag fix, that might mess something up... perhaps
Click to expand...
Click to collapse
Yeah I had the lag fix problem before, I now formatted the internal SD and now re-partitioning it, hopefully it works.
EDIT:
Still no use! It did not work, it's weird, I can downgrade but cannot upgrade to this firmware? WHY!!

galaxy_s said:
I am having trouble getting this firmware to work :S Anyone get it working?
EDIT: After I flash the 3 files including the CSC, MODEM and CODE file.
I get this error after flashing:
What the hell is that error?
Click to expand...
Click to collapse
I get exactly the same

welshlad said:
I get exactly the same
Click to expand...
Click to collapse
Did you use the speed fix?

galaxy_s said:
Yeah I had the lag fix problem before, I now formatted the internal SD and now re-partitioning it, hopefully it works.
EDIT:
Still no use! It did not work, it's weird, I can downgrade but cannot upgrade to this firmware? WHY!!
Click to expand...
Click to collapse
Try checking the re-partition field in Odin before flashing.
MaNIaC

same here, now i can't even flash an older firmware

galaxy_s said:
Did you use the speed fix?
Click to expand...
Click to collapse
No, just the standard XWJG3 installation

MaNIaCv1 said:
Try checking the re-partition field in Odin before flashing.
MaNIaC
Click to expand...
Click to collapse
Hey,
Re-partition did not work. I tried multiple times. Going to flash without the CSC & Modem.

HansBaer2000 said:
same here, now i can't even flash an older firmware
Click to expand...
Click to collapse
I can downgrade back to JG3 no probs...its a shame as the battery for me at the moment is shocking!!

welshlad said:
I can downgrade back to JG3 no probs...its a shame as the battery for me at the moment is shocking!!
Click to expand...
Click to collapse
Same here, well I tried flashing JUST the CODE file and it didn't work. I give up, I tried flashing this firmware 4 times now. I re-parition 3 times.

wow lucky we got people here always ready to take a plunge on new firmwares... ill hold out..thanks for the feedback.. and good luck guys i hope all goes well...

kindly let me know if anyone successfully installed this firmware, currently downloading now but it seems nobody ever get it working, just yet :S

Yeah tried several combinations myself too with and without repartitioning, looks like its gonna be crappy battery time a while longer yet...

well, i give up, no success

5.1.1.....I have an update downloading NOW

I think we might have 5.1.1.....

ksprelude01 said:
I think we might have 5.1.1.....
Click to expand...
Click to collapse
Definitely looks like 5.1.1 possibility!
I'm still on 4.4.4, this update is a hard decision because there is no downgrade...
But update your post an confirm it 5.1.1 after? Also would b nice to know the build number
Update:
Sent from my SAMSUNG-SM-N910A using Tapatalk

Will samsung galaxy grand prime sm-g530h get lollipo 5.1.1?
Sent from my SM-G530H using XDA Free mobile app

will do....im using an att wifi location so the download is taking forever

I'm updating as well, I'm guessing its 5.1.1. T-mobile, however, announced they are already testing 6.0 for their devices including note 4

Failed the update.....going to advance the date on the phone and try the update again.

omair2005 said:
I'm updating as well, I'm guessing its 5.1.1. T-mobile, however, announced they are already testing 6.0 for their devices including note 4
Click to expand...
Click to collapse
Any links or source?
Sent from my SAMSUNG-SM-N920A

Update done for me
Sent from my SAMSUNG-SM-N910A

downloading my update as we speak.. will inform when its done

Downloading right now ..... will update on complete.

Failed Update #2 as well....wondering what is causing it to mess up.....cleared cache and trying one more time.

nemopsp said:
Update: IMG
Click to expand...
Click to collapse
Quick question: does the 5.1.1 update include the theme store for the Note 4?

ap3604 said:
Quick question: does the 5.1.1 update include the theme store for the Note 4?
Click to expand...
Click to collapse
Nope

omair2005 said:
ap3604 said:
Quick question: does the 5.1.1 update include the theme store for the Note 4?
Click to expand...
Click to collapse
Nope
Click to expand...
Click to collapse
Sigh
Oh well, I guess I should simply be happy we're finally getting the 5.1.1 update. Really wish it included the theme store though (especially since we can't root)...
Thanks for the quick reply omair :good:

Does I need to be on the US and use an ATT simcard to update? I've recently bought an att note4 and it's on transit to my country.

No firmware?
After the update my device still says update available, however, it says 5.1.1 under device info. When I press continue update, it flashes "no firmware" and the icon at the top of the notification bar shows the arrows in opposite directions as if its trying to update, but nothing is happening. Any ideas as to why this occurs? Im using att straight talk and never had any issues with updates prior. Thanks in advance.

update try #3 failed as well......oh well i will be nuking the phone and trying it again.

Just finished the 5.1.1 update - no issues & phone's responsiveness is great now.
For once, add me to the list of people whose update went off without a hitch & promised enhancements actually are there.
There was a bit of sluggishness after the first reboot after install, but I'm thinking that was due to some kind of initial indexing going on in the background.
Aside from that, all apps, including Android Pay are working as before and no lag in the Recent Apps button. Text scrolling is noticibly smoother, especially when scrolling, for example, the list of installed apps in App Manager.
crp

ksprelude01 said:
update try #3 failed as well......oh well i will be nuking the phone and trying it again.
Click to expand...
Click to collapse
you are not alone my first one failed too. downloading the damn thing again right now...

jbeef86 said:
you are not alone my first one failed too. downloading the damn thing again right now...
Click to expand...
Click to collapse
Mine failed too at 1%, on reboot it said the update was interrupted. Same thing happened in the initial update to Lollipop. Going to go out on a limb and guess this is related to my phone being encrypted. Wiping the phone was the only way I could get that update to take. (The little interim ones did work for me). Sure makes me wise I could backup my phone with Titanium Backup like I used to.

Unlocked Bootloader Message

Is there a way to avoid the message you get when you reboot after unlocking the Bootloader? The black screen where you can wait 5 seconds or tap the power to go on...
I understand that is correct to show it...but it's boring and I'm already aware of it.

http://forum.xda-developers.com/nextbit-robin/general/guide-install-twrp-root-robin-t3334171/page7
maybe try and follow the instruction on post number 69

Thanks for the reply but that's for Moto X. Actually before Robin I was using a Moto X and I know that procedure, point is that on Moto X was just a screenshot before booting and nothing else, here looks a bit different and you can also skip it pressing the power button. Plus I would avoid to flash/use the logo.bin of Moto X...
Can anyone of Nextbit team provide any info? Thanks !

I also don´t like the screen... the opportunity to hide would be great.

here's the same, maybe someone can make a xposed module?

kcl0801 said:
here's the same, maybe someone can make a xposed module?
Click to expand...
Click to collapse
Hi, firmware/bootloader guy here - work for a Android vendor so I decided to have a quick look at the bootloader for you guys..
It's stored in the bootloader (aboot) if you are interested so you can't make a xposed module, it runs before Android (before init or zygote) does (or the Linux kernel). I haven't checked if Secure boot is on (if not, I suppose I could build a replacement aboot and just patched out the logic for that screen ) but I hope it's on for security reasons.

uberlaggydarwin said:
Hi, firmware/bootloader guy here - work for a Android vendor so I decided to have a quick look at the bootloader for you guys..
It's stored in the bootloader (aboot) if you are interested so you can't make a xposed module, it runs before Android (before init or zygote) does (or the Linux kernel). I haven't checked if Secure boot is on (if not, I suppose I could build a replacement aboot and just patched out the logic for that screen ) but I hope it's on for security reasons.
Click to expand...
Click to collapse
got it, in that case i will keep this message, but just hope it can pass faster, it says 5 secs but i feel it's about 30s to skip it...

kcl0801 said:
got it, in that case i will keep this message, but just hope it can pass faster, it says 5 secs but i feel it's about 30s to skip it...
Click to expand...
Click to collapse
Hey everyone, our team is looking into that nag screen. One of our devs pointed it out, so we're trying to see what we can do. :good:

any luck on the nag screen yet? maybe gone in the july update? =D lol

I get this message Everytime, any ideas? Help would be great

Akoolive said:
I get this message Everytime, any ideas? Help would be great
Click to expand...
Click to collapse
Make sure that the recovery.img is in the same folder as your adb/fastboot files. Let me know if that works!

makbomb said:
Make sure that the recovery.img is in the same folder as your adb/fastboot files. Let me know if that works!
Click to expand...
Click to collapse
Thanks that worked

Akoolive said:
I get this message Everytime, any ideas? Help would be great
Click to expand...
Click to collapse
Replace "recovery.img" at the end with the actual twrp filename and it should work.

I'd love to get rid of that error message on my new Robin, but I'm confused about whether or not the previous two posts were a solution to the problem. I had flashed TWRP after unlocking the bootloader, and the recovery was in the same folder as the ADB and Fastboot files, but I'm not sure what that has to do with removing the error message.
Thanks in advance!

Saaber said:
I'd love to get rid of that error message on my new Robin, but I'm confused about whether or not the previous two posts were a solution to the problem. I had flashed TWRP after unlocking the bootloader, and the recovery was in the same folder as the ADB and Fastboot files, but I'm not sure what that has to do with removing the error message.
Thanks in advance!
Click to expand...
Click to collapse
The last several message in this thread regarding 'recovery.img' was for someone trying to flash TWRP in fastboot, it has nothing to do with the 5-second nag screen.
Since khang never responded, I'm assuming this won't change and the nag screen will remain. I'm so used to keeping my finger on the power button when i reboot that it's almost habit now, so really doesn't bother me too much.

How can a device that is marketed for its unlockable bootloader and warranty coverage have an jnlockable bootloader experience that is worse than basically all devices. You don't see unlocked Sony or LG phones having boot screens that require user input. The only device I know of that is worse is the Pixel c, which has a 30 second "integrity check" if the bootloader is unlocked.

Nextbit_Khang said:
Hey everyone, our team is looking into that nag screen. One of our devs pointed it out, so we're trying to see what we can do. :good:
Click to expand...
Click to collapse
IS this going to change? really annoyed by it

..It's only 5 seconds, the only reason it seems longer is the fact that the message merges in with the boot logo

Nextbit_Khang said:
Hey everyone, our team is looking into that nag screen. One of our devs pointed it out, so we're trying to see what we can do. :good:
Click to expand...
Click to collapse
Very old thread here, but could you guys maybe release an optional "developer/enthusiast" bootloader update that gets rid of that nag screen? Or at least give the option to confirm the warning in future updates, like "I have read and understood this warning. Don't show again."

I am posting hoping some progress may or may not have been made on this. Its atrocious.

Stuck on Bootloop [7.1.1 ]

Hi,
A few hours ago I randomly got into a some kind of bootloop. It's not the "normal" bootloop where simply the boot animation is played forever. Instead my boot continues afterwards like normal until there's this short black screen before entering your SIM's pin card. This never appears and it begins again with the "Your bootloader is unlocked. Please lock it...."-message.
I already flashed the Factory Image twice via the ADB console on my PC and Wugfresh's Toolkit.
Additionally I can't seem to acess the stock recovery, the "red android guy" never appears and it only reboot itself after choosing the recovery in Fastboot Mode.
Any help is appreciated!
Vulkaistos

Try to flash TWRP, in TWRP wipe every partition and then try to flash the stock image again
Sent from my Nexus 5X using Tapatalk

dc239 said:
Try to flash TWRP, in TWRP wipe every partition and then try to flash the stock image again
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I already tried that, same problem as Stock Recovery.

Vulkaistos said:
I already tried that, same problem as Stock Recovery.
Click to expand...
Click to collapse
It seems like your partitions are messed up, did you tried to flash it via the flash-all script that is included in the stock image zip file?

dc239 said:
It seems like your partitions are messed up, did you tried to flash it via the flash-all script that is included in the stock image zip file?
Click to expand...
Click to collapse
Nope, I flashed them one by one. I may try the flash-all script now. Thanks!

Vulkaistos said:
Nope, I flashed them one by one. I may try the flash-all script now. Thanks!
Click to expand...
Click to collapse
OK, I now tried the flash-all script with the newest factory image drectly from Google but still the same issue.
I'll now contact Lg to at least try to get a RMA because I think I tried the most solutions.
If there's anyone that has another Idea, feel free to post it here

Vulkaistos said:
OK, I now tried the flash-all script with the newest factory image drectly from Google but still the same issue.
I'll now contact Lg to at least try to get a RMA because I think I tried the most solutions.
If there's anyone that has another Idea, feel free to post it here
Click to expand...
Click to collapse
Yea, that would be the best idea. Maybe it's slowly getting into that "classic" bootloop, which everyone talks about
Sent from my Nexus 5X using Tapatalk

dc239 said:
Yea, that would be the best idea. Maybe it's slowly getting into that "classic" bootloop, which everyone talks about
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I got a very interesting update on my issue.
My phone worked for a few minutes now, it booted normally and I could even set it up completely. But now it's the same problem again so I more and more think it could be faulty hardware.
Anyways I contacted LG for a RMA and we'll what happens.
Thanks for your help

Vulkaistos said:
I got a very interesting update on my issue.
My phone worked for a few minutes now, it booted normally and I could even set it up completely. But now it's the same problem again so I more and more think it could be faulty hardware.
Anyways I contacted LG for a RMA and we'll what happens.
Thanks for your help
Click to expand...
Click to collapse
You'll get the RMA, that is a hardware failure.

Last Update:
LG accepted my RMA request and I'll send them it ASAP.
Thank you everyone for helping me!
I'll mark this thread as solved.

Vulkaistos said:
Last Update:
LG accepted my RMA request and I'll send them it ASAP.
Thank you everyone for helping me!
I'll mark this thread as solved.
Click to expand...
Click to collapse
Little OT, but how long have you had your 5X? It looks like all the 5x's are just time bombs in case of that hardware bootloop. I'm thinking about selling my 5x and buying something that will not die on me some day.
Sent from my Nexus 7 using Tapatalk

dc239 said:
Little OT, but how long have you had your 5X? It looks like all the 5x's are just time bombs in case of that hardware bootloop. I'm thinking about selling my 5x and buying something that will not die on me some day.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I bought my Nexus in December 2015 so around 2 1/2 years ago. It's a nice phone never had any serious problems with it except now.

getting "your device is corrupt and cannot be trusted pixel"

So after a few months of using my google pixel 2 xl, while I was using it I randomly got a black screen with the message:
"Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co./ABH
PRESS POWER BUTTON TO CONTINUE".
Now it happens every time I turn on my phone. :/
I Have tried doing a factory reset and it still appears.
My phone is not rooted, I have the official OS that I got it with it (updated it through the phone's updater).
The phone was purchased directly from the us google online store.
I've tried to contact their support but they didn't have a solution.
Please help me!!

almogsad said:
So after a few months of using my google pixel 2 xl, while I was using it I randomly got a black screen with the message:
"Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co./ABH
PRESS POWER BUTTON TO CONTINUE".
Now it happens every time I turn on my phone. :/
I Have tried doing a factory reset and it still appears.
My phone is not rooted, I have the official OS that I got it with it (updated it through the phone's updater).
The phone was purchased directly from the us google online store.
I've tried to contact their support but they didn't have a solution.
Please help me!!
Click to expand...
Click to collapse
Sounds like one of those non harmful, annoying messages at boot up. Is your bootloader still locked I assume? If so, have you tried side loading the March OTA. I think sometimes during the OTA updater process that some files don't always make it to the system, which is why you get those messages. Is your phone still functioning properly??

Badger50 said:
Sounds like one of those non harmful, annoying messages at boot up. Is your bootloader still locked I assume? If so, have you tried side loading the March OTA. I think sometimes during the OTA updater process that some files don't always make it to the system, which is why you get those messages. Is your phone still functioning properly??
Click to expand...
Click to collapse
First of all thanks for the response!
yes my bootloader is still locked.
Badger50 said:
have you tried side loading the March OTA
Click to expand...
Click to collapse
How do I do that? ^^
and it seems like the phone still functions properly, but I guess only time will tell

almogsad said:
First of all thanks for the response!
yes my bootloader is still locked.
How do I do that? ^^
and it seems like the phone still functions properly, but I guess only time will tell
Click to expand...
Click to collapse
Just follow these instructions if you want to side load an OTA. It's really not that hard ??
https://developers.google.com/android/ota

Badger50 said:
Just follow these instructions if you want to side load an OTA. It's really not that hard
Click to expand...
Click to collapse
Thanks! I'll try that...
Do you think it might fix the problem?
Edit:
it says in the guide:
"find the appropriate driver for your device from the OEM drivers"
but I don't know which one is mine ^^

almogsad said:
Thanks! I'll try that...
Do you think it might fix the problem?
Edit:
it says in the guide:
"find the appropriate driver for your device from the OEM drivers"
but I don't know which one is mine ^^
Click to expand...
Click to collapse
Once you choose the proper OS version for your pc, and install SDK, when you plug your phone in, it should automatically update your device drivers :good:
And yes, there's a good chance it'll fix your problem. Never any guarantees with this tech stuff though

Badger50 said:
Once you choose the proper OS version for your pc, and install SDK, when you plug your phone in, it should automatically update your device drivers :good:
And yes, there's a good chance it'll fix your problem. Never any guarantees with this tech stuff though
Click to expand...
Click to collapse
Hey! It seems like it worked!!!! Thanks!!
I only wish I hadn't listened to the google support team , and hadn't done a factory reset to phone before lol they don't seem to understand too much about their phones, the guy told me he thinks it's just an add
Thanks again man!

almogsad said:
Hey! It seems like it worked!!!! Thanks!!
I only wish I hadn't listened to the google support team , and hadn't done a factory reset to phone before lol they don't seem to understand too much about their phones, the guy told me he thinks it's just an add
Thanks again man!
Click to expand...
Click to collapse
Oh sweet! Glad to hear it my friend, well done. Now you can help others out with the same issue if it comes up :good: Yeah, the Google folks are kinda funny sometimes. The factory reset is their standard MO! And right, an add on the boot up screen....yeah that's funny! I'd be willing to bet most of them use iPhones!!??????

Badger50 said:
Oh sweet! Glad to hear it my friend, well done. Now you can help others out with the same issue if it comes up :good: Yeah, the Google folks are kinda funny sometimes. The factory reset is their standard MO! And right, an add on the boot up screen....yeah that's funny! I'd be willing to bet most of them use iPhones!!
Click to expand...
Click to collapse
How ironic! lol ???

Badger50 said:
Sounds like one of those non harmful, annoying messages at boot up. Is your bootloader still locked I assume? If so, have you tried side loading the March OTA. I think sometimes during the OTA updater process that some files don't always make it to the system, which is why you get those messages. Is your phone still functioning properly??
Click to expand...
Click to collapse
Thanks!! I also had this issue and following your suggestion to sideload the latest OTA, it appears to have fixed the problem.

I've been getting the same corrupt error on reboots on my xl 2(also not rooted), but I have not been able to get the latest OTA to sideload. It nearly completes but aborts last second and gives a Status 1 error. I'm not sure what I'm doing wrong here. Any help will be appreciated.
Got a similar run-around with Google support. When the factory reset was unsuccessful, they've recommended replacing the phone since it's under warranty, however they think replacing my virtually brand new phone with a refurbished phone is appropriate.

Apsel said:
I've been getting the same corrupt error on reboots on my xl 2(also not rooted), but I have not been able to get the latest OTA to sideload. It nearly completes but aborts last second and gives a Status 1 error. I'm not sure what I'm doing wrong here. Any help will be appreciated.
Got a similar run-around with Google support. When the factory reset was unsuccessful, they've recommended replacing the phone since it's under warranty, however they think replacing my virtually brand new phone with a refurbished phone is appropriate.
Click to expand...
Click to collapse
Are adb/fastboot tools the very newest?

Apsel said:
I've been getting the same corrupt error on reboots on my xl 2(also not rooted), but I have not been able to get the latest OTA to sideload. It nearly completes but aborts last second and gives a Status 1 error. I'm not sure what I'm doing wrong here. Any help will be appreciated.
Got a similar run-around with Google support. When the factory reset was unsuccessful, they've recommended replacing the phone since it's under warranty, however they think replacing my virtually brand new phone with a refurbished phone is appropriate.
Click to expand...
Click to collapse
Unlock then re-lock your bootloader(/s) maybe?

Great job guys, this solution with sideload latest OTA worked for me too with no need to unlock bootloader! :good::good::good:

I can confirm this working again. Pixel 2 XL with 9.0 and November security update.

Thanks!
I just had the corrupt message pop up (bootloader locked), and the sideload ota update seems to have worked!

michaelbsheldon said:
Are adb/fastboot tools the very newest?
Click to expand...
Click to collapse
I'm experiencing the same problem as Apsel, yes the adb/fastboot are the latest.
Error applying update: 15 (ErrorCode : kNewRootfsVerificationError)
E:Error in /sideload/package.zip (status 1)

Badger50 said:
Just follow these instructions if you want to side load an OTA. It's really not that hard ??
https://developers.google.com/android/ota
Click to expand...
Click to collapse
I know this is an old post but I'm having the same issue. Also cannot connect to pc due to, I'm assuming daughterboard issue this and previous pixel models have. I have been rooting phones since the S3 and am no virgin to the sdk. I tried to take it to ubreakifix which was a 4 hour round trip for me. I was told I would have to sign a waiver since the screen is glued to the phone and that was the only way to get to the internals. When I arrived I watched 4 bozos poke at the charging port for 20 min and then contradicting what I was told the night before over the phone that they were not comfortable doing the repair and then they tried to sell me a new device. I just got off chat with google and they want to charge me 270 dollars to fix even though I went to an authorized service center when it was in warranty. Will fastboot work over wifi?

Toolmighty said:
Will fastboot work over wifi?
Click to expand...
Click to collapse
'fraid not. Both the bootloader and recovery have stripped down hardware support, limited essentially to the display and storage. Neither has WiFi support that I know of, thus you have to use a USB cable.

I figured it out after I figured out how to fix the daughterboard issue w/o replacing the daughterboard. Verizon are some sneaky *^&$^s. Thx for the reply tho. I'm sure ur quite busy.