Long story short, I received a new 2nd Gen 7 yesterday, it was built on 07/13 and its running JWR66N. I found that odd, but figured I would update the build but I haven't been able to. I check for an update and it is telling me by device is up to date. I know this is not true as there are newer builds out there and now KitKit is rolling out. Is there a chance that I will not be able to updated the 7 until KitKat is rolled out to me?
Curious if my device is bad, or if there are no updates actually available to me at this time.
Thanks!
Is it an LTE or a Wifi-Only model? Go to settings >apps> >all> Google Services Framework. Force stop and clear data, then try to check for updates again. Repeat this process a few times for good measure and see if you get anything. If still no updates, get the factory image from here https://developers.google.com/android/nexus/images (JSS15R for the WiFi version) and flash it with fastboot to get yourself ready for the kitkat update to roll out. Don't flash any images unless you know for sure what kind you have and know what you are doing.
Have you tried to manually update your device with the latest 4.3 image posted on Google's development site? I haven't done it myself but they have instructions there that should help you do it. Make sure you download the right image for your particular device.
https://developers.google.com/android/nexus/images
Paten said:
Have you tried to manually update dur device with the latest 4.3 image posted on Google's development site? I haven't done it myself but they have instructions there that should help you do it. Make sure you download the right image for your particular device.
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Thanks for the help, unfortunately I am not quite tech savvy enough to take these steps... I have cleared the data with no luck and hard reset a few times with no luck. Am I stuck with having to return yet another tablet?
vulcaninvt said:
Thanks for the help, unfortunately I am not quite tech savvy enough to take these steps... I have cleared the data with no luck and hard reset a few times with no luck. Am I stuck with having to return yet another tablet?
Click to expand...
Click to collapse
Unfortunately I think you may be stuck if you can't update manually. I had the same problem I had to update from about 3 versions back. It may just be best to take it back and hope for a new one.
PS From what I under stand this was a very old build on the nexus 7 that showed up on the first batch of tablets produced, this would explain why the default wallpaper is different.
Found that out from this link: http://forum.xda-developers.com/showthread.php?t=2416793
That is strange, since JWR66 is a 2012 Nexus 7 rom. You are sure it is a 2013 model? It is all black, not gray-ish?
GSLEON3 said:
That is strange, since JWR66 is a 2012 Nexus 7 rom. You are sure it is a 2013 model? It is all black, not gray-ish?
Click to expand...
Click to collapse
It's all black, 2gb Ram. It's definitely 2nd gen, it's pretty jacked... getting more errors when trying to reset. Unfortunately after having five faulty 7s I am moving on. I really wanted to stick it out, but I have lost trust in the device.
vulcaninvt said:
It's all black, 2gb Ram. It's definitely 2nd gen, it's pretty jacked... getting more errors when trying to reset. Unfortunately after having five faulty 7s I am moving on. I really wanted to stick it out, but I have lost trust in the device.
Click to expand...
Click to collapse
Contact google and tell them your problem, they usually help really fast like when my friends nexus 4 came with a off build number.
---------- Post added at 09:29 PM ---------- Previous post was at 09:12 PM ----------
vulcaninvt said:
It's all black, 2gb Ram. It's definitely 2nd gen, it's pretty jacked... getting more errors when trying to reset. Unfortunately after having five faulty 7s I am moving on. I really wanted to stick it out, but I have lost trust in the device.
Click to expand...
Click to collapse
Contact google and tell them your problem, they usually help really fast like when my friends nexus 4 came with a off build number.
GSLEON3 said:
That is strange, since JWR66 is a 2012 Nexus 7 rom. You are sure it is a 2013 model? It is all black, not gray-ish?
Click to expand...
Click to collapse
The first OS they had on the original 2013 nexus7 shipments were JWR66N.
I'm getting this on my N7 2013LTE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My nexus 7 32GB came with the same firmware JWR66N, but there is an easier way to flash the latest 4.3 or 4.4 if you wish to
First of all download the right firmware from google, somebody already posted a link.
Next you need Nexus rootkit 1.7.6
http://www.wugfresh.com/
When you first run rootkit 2 boxes will pop up, just cancel these you can root ect later if you wish.
Then what you need to do is pretty simple
in your nexus 7 enable dev option, then put it into debug mode
then in storage option "top right" select camera PTP
Connect your nexus 7, if ADB or whatever is called isn't working, then there is an option in rootkit to install the universal drivers, you need to do this before you can flash it found in the initial setup option at the top just follow the guide, once that installed it will test and if everything is then working your good to go.
Next you need to unlock it first click the option saying unlock, this will wipe your nexus 7.
Once that done, next you need to click Flash stock+Unroot
Then click other browse
bit futher down click the option called I downloaded a Factory image myself, then click ok, and goto were you downloaded the firmware to.
click on firmware, it do some checks to make sure the MD5 is ok then it extract it from then on it begin to flash to the new firmware for you.
Once that done you can relock your nexus 7 by clicking OEM lock if you wish to.
and job a good un new firmware installed :good:
Related
Hello guys,
I have a Motorola Xoom and I can't wait to get ICS. When I browse the ICS topics, I see a lot of people who changed their xoom version to US, fe from Canadian to US. I don't know wich version I have, but it's not a US version, because I still don;t have the upgrade. If someone could maybe give a short description of how to change it to US, I would be so gratefull!!!
These steps worked great for me
http://lanlith.blogspot.com/2011/07/xoom-wifi-non-us-ie-ukcan-301-32-in-few.html
Just follow up to step 3 ...then just wait for the OTA updates
My xoom was the UK version... now running the oh so smooth ICS with US rom and lovin it!
Thanks! I only hope this will work for mine, since mine is probably Dutch or European and the description is for UK or Canadion Xooms. But i don't think that should be a proble. Anyway, I'm gonna try and pray that it works!
Got a problem
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can anyone help please?
Don't do it
Tried this last night and confirmed that it does not work. US image does not work on a Canadian device for some reason. Tried to post details here but the thread seems to have been deleted.
I believe the method on this thread is the easiest, and you preserve root
http://forum.xda-developers.com/showthread.php?t=1446469
echus said:
Tried this last night and confirmed that it does not work. US image does not work on a Canadian device for some reason. Tried to post details here but the thread seems to have been deleted.
Click to expand...
Click to collapse
It works fine. I did it myself a few months ago, flashing my Canadian Xoom with the US ROM, after which I was obtaining the US OTA updates. I don'T remember which procedure I used however, but I can confirm that there's a working procedure somewhere here on the forums.
I got it unlocked and every image would flash ok, apart from system.img. I really don't understand why. I followed the tutorial word for word and obviously I was doing something right or I wouldn't have been able to flash the other images.
In the end I just installed CWM and flashed Team EOS ICS from the recovery.
Worked Great and First Time on my brand new UK Wifi Xoom
Just bought a Wifi only xoom today from carphone warehouse and was a bit dubious about doing this, not wanting to brick my brand new Tablet.
I thought stuff it though, if doesn't work it can go back in the same afternoon that I bought it and I'll get a Refund (was last one in stock, due to them selling them for £249)
Anyway,
Worked a charm once I found the folder where the fast boot was hiding within the zip file.
Took a little while to do, but dead easy
The one thing I did wrong at first was not noticing that each image file had the same filename name written after FLASH and before the filename.img too
(i.e written twice on the command, must be going blind in my old age)
The longest part was going through all the updates on the xoom until finally getting ICS.
Working great now though.
Thanks guys for a great tutorial.
Dean
Are you HK or taiwan version? These problem is almost in these two version.
echus said:
Tried this last night and confirmed that it does not work. US image does not work on a Canadian device for some reason. Tried to post details here but the thread seems to have been deleted.
Click to expand...
Click to collapse
Were you able to convert yours? I've got a US wifi version, but my dad has a Canadian version and he wants me to convert it to a US version for him.
What happened with the system.img the screen shot seems to suggest it started? Couldn't see any error?
It takes longer to push the system.img over if I recall correctly its a much larger file ...
Edit oh, checked again and saw the fail. Odd. I can probably find and upload the system.img that I used if it would help.
Sent from my HTC Desire using xda premium
matthewsammut said:
These steps worked great for me
http://lanlith.blogspot.com/2011/07/xoom-wifi-non-us-ie-ukcan-301-32-in-few.html
Just follow up to step 3 ...then just wait for the OTA updates
My xoom was the UK version... now running the oh so smooth ICS with US rom and lovin it!
Click to expand...
Click to collapse
Can I use on MZ605? Is a wifi/umts 3g by H+....
Sent from my MZ605 using xda premium
matthewsammut said:
These steps worked great for me
http://lanlith.blogspot.com/2011/07/xoom-wifi-non-us-ie-ukcan-301-32-in-few.html
Just follow up to step 3 ...then just wait for the OTA updates
My xoom was the UK version... now running the oh so smooth ICS with US rom and lovin it!
Click to expand...
Click to collapse
Sent from my MZ605 using xda premium
So here is the link to the 4.4.4 file. Interesting......
If you install this let us know what you find new...prob just a quick bug fix I would imagine.
https://developers.google.com/android/nexus/images
Update:
Nexus 5 Software Update - KTU84P
Enhancements/Fixes
Security Fix
Important Notes
- Software version is KTU84P
- This update will be rolled out to device in batches.
- Refer to the Nexus 5 Software Update article in Support for install instructions
I just saw it . GOOGLE WHAT ARE YA DOIN.... haha was just about to create this thread.
Me right now. The third guy.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Seriously, Google. ... what's with the LTE hate?
This is probably plugging the towelroot exploit .
Sent from my Nexus 7 using xda premium
I hate that feeling when you JUST finish updating your Nexus 5 phone to Android 4.4.3 and literally two minutes later an update to 4.4.4 gets released! UGH! Still waiting for LTE for Nexus 7.
What in the world Google... Something musta been a big time fail in the code for them to release a full update like this that quick...
Sent from my Nexus 7 using Tapatalk
cokey77 said:
This is probably plugging the towelroot exploit .
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
nope, it's related to the heart bleed
Sent from my Nexus 7 using Tapatalk
Soldier 2.0 said:
nope, it's related to the heart bleed
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Nope, it is SSL related, but not heartbleed.
Well people, the OTA doesn't look like it affected very much. I usually just flash whatever image from the factory image that I need because of the changes I make in the system but I just now decided for grins to flash the OTA and see if I would get any errors and I was pleasantly surprised to not see the "unexpected contents error." It happens, rarely, but it does happen. Running ElementalX kernel, busybox installed, modified calculator app in system/app, 4.4 sounds in system/media/audio/ui, modified mixer_paths.xml in system/etc, Z2 bionic and dalvik, running xposed and the OTA flashed with no errors! Woop Woop! Did have to flash the supersu zip in recovery. All good!
changes on 4.4.4 http://www.xda-developers.com/android/heres-everything-thats-changed-in-android-4-4-4-ktu84p/
Whats wrong with you GOOGLE ? Why just Razorg ?
What is wrong with Google? Why is Deb being left out?
Sheesh... Feeling abandoned...
I don't understand why Deb is being left out either. Maybe we'll just jump into the new android version when it's announced at Google I/O.
Maverick-DBZ- said:
I don't understand why Deb is being left out either. Maybe we'll just jump into the new android version when it's announced at Google I/O.
Click to expand...
Click to collapse
Somehow I don't expect that'll be what happens.
Considering there had to be a 4.4.2_r2 for deb before, I suspect that whatever inspired that (which was Verizon compatibility) is the holdup now.
Does anyone have the OTA URL?
lotherius said:
Me right now. The third guy.
Seriously, Google. ... what's with the LTE hate?
Click to expand...
Click to collapse
My guess it's because of Verizon
I hope they've included the driver for the Logitech Unifying receiver...
Can some one grab the OTA file name, URL, or the OTA itself and upload it?
lotherius said:
Somehow I don't expect that'll be what happens.
Considering there had to be a 4.4.2_r2 for deb before, I suspect that whatever inspired that (which was Verizon compatibility) is the holdup now.
Click to expand...
Click to collapse
Well, 4.4.4 does put us 2 releases behind now.
I can imagine a *good* developer working out a DRY unified patch (verizon & others) for 4.4.3 and 4.4.4. But, along comes management and says either (a) verizon does not accept, or (b) others like att/t-mobile/etc do not accept. A drama ensues and we have big delays.
Anyway, "4.4.2 really?" is the perfect question to *pound* on google during IO. lol
There's a theory going around that it's Verizon that is to blame for the delay, but maybe it's not the reason
? Great news,
The new firmware "Maintenance" update "21.11.56" is out today.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
? Check your phone for updates!!
maybe one day the xt1045 will be updated.
What about full firmware (about 500 MB)? Is it possible to get it somewhere? I can't find even 4.4.4 (previous update) of GB UK update, only EU.
Oh nice, thanks for the heads up. Nothing here on my XT1039 en.EU at the moment, but these things rolls out in waves.
Will hope.
Gesendet von meinem XT1039 mit Tapatalk
And......any new experiences? Will it fix the SD-Card problems generally??
All input will be welcome.....
Someone doesn`t know the meaning of "NDA".
anything-but said:
Someone doesn`t know the meaning of "NDA".
Click to expand...
Click to collapse
What ? Who is under NDA here ?
anything-but said:
Someone doesn`t know the meaning of "NDA".
Click to expand...
Click to collapse
Motorola is rolling this out to select users. There is no NDA involved.
Well,i`ll admit i`m in the trial (tho won`t comment on it) and one of the steps to getting it involved agreeing to a NDA. If it was just a "all agreeing" one or something specific to this update alone i`m not sure.
anything-but said:
Well,i`ll admit i`m in the trial (tho won`t comment on it) and one of the steps to getting it involved agreeing to a NDA. If it was just a "all agreeing" one or something specific to this update alone i`m not sure.
Click to expand...
Click to collapse
hmm mm, that is interesting...
Please tell us more?!
? No, I'm not taking part to any trial or anything like that.
You claiming to be in a trial!
Please can you elaborate a bit more?
And you agreed to some "NDA" ?!
? And now you are commenting about it in here!!!
Clearly:
anything-but said:
Someone doesn`t know the meaning of "NDA".
Click to expand...
Click to collapse
☺ here the Wikipedia link to help you:
http://en.m.wikipedia.org/wiki/Non-disclosure_agreement
Your comments are definitely interesting,
You are boasting about being part to some kind of a secret experiment, and you signed some NDA to take part on it...
?I think you have just broken your "NDA".
Kxb21.14-l1.56
I have not received an update KXB21.14-L1.56, where it can be downloaded?
Did anyone receive this update for en.uk firmware?
Just received this update for Moto G 4G - en.EU
Have just received this for the en.GB retgb version! (Sunday 21st September). Could this late delivery be related to using ART?
Installed no problem on the rooted device. After installing, all apps were updated. Took less than 10 minutes from start to finish.
Did you capture the ota file?
MarisPiper said:
Have just received this for the en.GB retgb version! (Sunday 21st September). Could this late delivery be related to using ART?
Click to expand...
Click to collapse
ART? There aren't any changes to ART in 4.4.4.
Don't know if anyone has posted the actual OTA for XT039 EU. But here it is.
Motorola Moto G XT1039 (EU)
Old Version: 21.1.46.en.EU
Information: 21.11.56.en.EU
Dam you smoke pot you beat me to it. Was just uploading the OTA update to mega and made a post Will now go and get that thread of mine closed.
Just updated myself will come back with any improvements BTW just to the gpt.bin and fsg.mbn being touch it makes the Stock firmware before it useless will there be a new version of the Full firmware for us that wish to return to stock.
Edit: This is a first the OTA didn't take out my root, although i did need to uninstall xposed before updating.
hacktrix2006 said:
Dam you smoke pot you beat me to it. Was just uploading the OTA update to mega and made a post Will now go and get that thread of mine closed.
Just updated myself will come back with any improvements BTW just to the gpt.bin and fsg.mbn being touch it makes the Stock firmware before it useless will there be a new version of the Full firmware for us that wish to return to stock.
Edit: This is a first the OTA didn't take out my root, although i did need to uninstall xposed before updating.
Click to expand...
Click to collapse
I'm a complete technical newbie, so I apologise for what might be stupid questions. I used to own a HTC Desire which had to be rooted to make it suit my requirements, and now I have a rooted Moto G LTE (4.4.4, 21.1.46 from Tesco) which I've had to root to suit most of my requirements.
I'd like to install this update to (maybe) fix the SD card issue. I have "CWM recovery" installed which seems to break the installation of this update. I get a 'install zip' question in the recovery, I swipe yes and then swipe to install root again. At this point the phone boots normally, and immediately after boot it reboots into the CWM recovery screen again (and over). I rebooted into CWM recovery and paniced when I realised that the SD Card isn't there with my backup and so I wiped the cache. This fixed the reboot problem, but I'd still like to update, but don't want to risk breaking my phone.
Can I use the zip 2 posts above me to update to the latest version? Will that be compatible with a Tesco version phone?
How do I create a backup that is located somewhere the phone can see in CWM recovery mode?
Apologies again if this is a silly question, stupid question or anything else. I'm not technically minded, but I'm forced into these corners to make my phone work how I'd like it to.
Thanks!
Hi guys, i just received my new prime exclusive moto g 4th, once i turned on my devices an update appears so i installed it (OTA), i remember there was something in the name like MPJ24.139-64, once it finished updating i wanted to remove the ads following this tutorial MOTO G 4th Gen How to Remove the Amazon Lock Screen Ads and Bloat Ware . i did it all exactly as it is on the post. now my device can't start and i am not able to install the stock firmware cause all the stock rom versions available are actually lower that the installed on my phone and i think i can't downgrade because of the locked bootloader and it seems to be unlockable .
also it says on the recovery mode the next legancy: WE HAVE DETECTED AN ATTEMPT TO FLASH UNAUTHORIZED SW ON YOUR DEVICE. CONTACT CUSTOMER SERVICE FOR ASSISTANCE.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Already tried
stkpxl said:
Try the above firmware. Should be the current version for your phone.
Click to expand...
Click to collapse
thanks for your help, i have already tried with that one, i flashes completely then when i reboot the devices it starts into recovery mode and says WE HAVE DETECTED AN ATTEMPT TO FLASH UNAUTHORIZED SW ON YOUR DEVICE. CONTACT CUSTOMER SERVICE FOR ASSISTANCE.
I think flashing S/W posted on Motorola site should bring your phone back to life.
See the thread - http://forum.xda-developers.com/showpost.php?p=68502532&postcount=381 for the link to the same.
mobile-junky said:
I think flashing S/W posted on Motorola site should bring your phone back to life.
See the thread - http://forum.xda-developers.com/showpost.php?p=68502532&postcount=381 for the link to the same.
Click to expand...
Click to collapse
The moto G 4th X1625 image is not available.
Cclown98 said:
The moto G 4th X1625 image is not available.
Click to expand...
Click to collapse
I would still give it a try as there is nothing to loose.
Or contact Motorola customer care to see what they say.
mobile-junky said:
I would still give it a try as there is nothing to loose.
Or contact Motorola customer care to see what they say.
Click to expand...
Click to collapse
hello, i've already tried those files and im still getting the same problem
Cclown98 said:
hello, i've already tried those files and im still getting the same problem
Click to expand...
Click to collapse
Did you try the files posted by Motorola at their site or the ones posted on android file host ..
If not by Motorola then I would try the same again.
mobile-junky said:
Did you try the files posted by Motorola at their site or the ones posted on android file host ..
If not by Motorola then I would try the same again.
Click to expand...
Click to collapse
there are no files for the xt1625 on the motorola website
Cclown98 said:
there are no files for the xt1625 on the motorola website
Click to expand...
Click to collapse
Please read the thread in http://forum.xda-developers.com/moto-g4/how-to/update-9-1-16-t3453726
It looks like somehow the firmware for the Indian XT1624 was put on your device. As far as I know, no one has been able to install XT1625 firmware on their device after installing the firmware for the XT1624.
---------- Post added at 10:02 AM ---------- Previous post was at 09:46 AM ----------
granny smith said:
Please read the thread in http://forum.xda-developers.com/moto-g4/how-to/update-9-1-16-t3453726
It looks like somehow the firmware for the Indian XT1624 was put on your device. As far as I know, no one has been able to install XT1625 firmware on their device after installing the firmware for the XT1624.
Click to expand...
Click to collapse
After a little research, it does appear that an OTA was released for the AMZ XT1625. Sorry, I can't think of anything else that hasn't already been suggested.
It seems Moto has changed their site and updated the s/w it now shows XT1625.
I am currently downloading from motorola right now. I am also making a backup like normal. I will let you know if it works for the XT1625 as mine is retail US.
OK I downloaded and flashed it. While it came to the July 1 security update build still said -49. There was no Amazon ad crap and I got a system UI fc and retail something fc. Beyond that it was working just fine after about 5 mins.
the problem is that on mine phone the bootloader is unlockable
stkpxl said:
I'm assuming you've tried a factory reset from recovery?
Click to expand...
Click to collapse
yes i have
stkpxl said:
Have you tried unlocking the bootloader? I know you have an Amazon model but it doesn't hurt to try.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a/session/L2F2LzEvdGltZS8xNDc1MjY0MDkwL3NpZC9mSENuX1hfbQ%3D%3D
Click to expand...
Click to collapse
yes i have tried and it says that my device is no eligible for bootloader unlocking
stkpxl said:
Mine is booting up now, so far the same results as you. Although, I couldn't relock the bootloader. Could you?
EDIT: Trying a factory reset to see if those FCs get fixed....
EDIT2: They don't get fixed with a factory reset. Restarting it FCs File Manager. Restarting a 3rd time, it's fine. Weird
---------- Post added at 11:16 AM ---------- Previous post was at 10:32 AM ----------
Looks like QuadRooter got fixed. Used the CheckPoint scanner to check. I'll take a security update even without updating the build number lol
Click to expand...
Click to collapse
I never tried to relock the bootloader. I still have a few more things to test before I will truly be happy lol.
stkpxl said:
Well it turns out you can't downgrade after flashing this. I tried flashing the previous firmware and got an error. I went ahead and nuked it all and put a build of CM13 on. Bonus for me is that I got received calls to work for once. So I'm fairly happy bow.
Click to expand...
Click to collapse
I restored my backup. I didn't try to downgrade. I will try that tomorrow.
I reflashed the moto firmware from moto website. Tried to downgrade and got an error myself. However I did have the factory -48 firmware. I don't remember where I got it from so sorry I cannot link it. I was able to flash twrp and wiped all data then flashed -48. I instantly received software update after I finished the normal setup. It updated to build number MPJ24.139-64. As soon as everything finishes reinstalling on my XT1625 I will post a screenshot.
Okay I found it again. Hope this will help out. Also this is only for Retail US. I do not think that it will work for AMZ
Firmware That I flashed. http://www.filefactory.com/file/3t2...PJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip
im in the same situation with a soft bricked, bootloder locked, amazon g4. and i would like to try to update with a zip file of the update if there is one to be found somewhere.
Hey all! I am embarking in bringing oreo to our device, but i might need help from the more experienced devs in this instance. I have made successful builds of slimrom 7 and crdoid nougat for this device but i just wanted to let you all know that i will be trying this. any support is greatly appreciated!!
Status update
So i am building now(had some directory and cmaction errors i had to get rid of). It is going well and actually building oreo based off of lineageos.
How many people would like an oreo rom for this phone lol?
Ill keep you all updated
Bring it mate!
build errors
This post will be held for build errors.
so the first error i have is this one, which is odd because the file is there
system/core/init/log.h:20:10: fatal error: 'android-base/logging.h' file not found
#include <android-base/logging.h>
Oreo for Style? Cool!! I stand
Good luck
kaibsora said:
This post will be held for build errors.
so the first error i have is this one, which is odd because the file is there
system/core/init/log.h:20:10: fatal error: 'android-base/logging.h' file not found
#include <android-base/logging.h>
Click to expand...
Click to collapse
Keep in mind that Lineage 15 is still actively being developed. For any build errors, you may first want to do a "make clean", "repo sync" then lunch or whatever build method you are using. If that doesn't fix it, look at https://review.lineageos.org/ to see if there is anything related to the error that is pending.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ThrillerAtPlay said:
Keep in mind that Lineage 15 is still actively being developed. For any build errors, you may first want to do a "make clean", "repo sync" then lunch or whatever build method you are using. If that doesn't fix it, look at https://review.lineageos.org/ to see if there is anything related to the error that is pending.
Click to expand...
Click to collapse
Thanks! i managed to fix that error by adding the full path, but now im stuck at property_get errors
UPDATE: i updated my device, kernel, and proprietary tree to fix that issue. im currently working with lineageos devs via irc on this
New update: i am stuck on development due to xlat errors. im going to try to find another source for my device tree
UPDATE
Its been a couple days and im sorry for the wait but my progress has gotten further. i am building right now and it has been going to 52 percent now. will let you know when i have failed.
You got this! Thanks for being an amazing dev!
Build is done
So my first successful build of lineageos 15 is done for my device. will test.
kaibsora said:
So my first successful build of lineageos 15 is done for my device. will test.
Click to expand...
Click to collapse
link link link , please!!!
Broke
HPAR said:
link link link , please!!!
Click to expand...
Click to collapse
The rom did not boot, it kept relooping into bootloader. whats odd is after i restored to slim 7.1 now my device is completely broke. wont even charge anymore
so needless to say, i think that this project will be dead to me unless i get another moto x pure( which i will not be buying) oh well, it had a good run. im sorry guys, if you want me to continue on this project you will have to donate, as i do not have a working device anymore
Fixed
The issue might now be fixed, i took the phone apart and removed the battery and reconnected everything. I went out and bought a samsung note8 yesterday due to this phone being dead and that i have to have a phone for work, so if i did fix this phone i will be able to work on this project more.
kaibsora said:
The issue might now be fixed, i took the phone apart and removed the battery and reconnected everything. I went out and bought a samsung note8 yesterday due to this phone being dead and that i have to have a phone for work, so if i did fix this phone i will be able to work on this project more.
Click to expand...
Click to collapse
Nice! I wonder what happened in the first place? I rarely hear of roms effecting the hardware like that.
I expect to see this ROM fully working long before the XT1575 official 7.0 just saying
strafer69 said:
I expect to see this ROM fully working long before the XT1575 official 7.0 just saying
Click to expand...
Click to collapse
Funny you say that because people are getting 7.0 on their XT1575s right now. Its rolling out on Sprint right now haha.
tzuba12 said:
Funny you say that because people are getting 7.0 on their XT1575s right now. Its rolling out on Sprint right now haha.
Click to expand...
Click to collapse
No way that's actually awesome. About time. But also kinda weird seeing as the unlocked version hasn't even gotten it yet
Spencervb256 said:
No way that's actually awesome. About time. But also kinda weird seeing as the unlocked version hasn't even gotten it yet
Click to expand...
Click to collapse
There's only one version of the Pure Edition, retail unlocked. Moto is likely rolling out in batches based on IMEI or carrier or whatever they feel like.
quakeaz said:
There's only one version of the Pure Edition, retail unlocked. Moto is likely rolling out in batches based on IMEI or carrier or whatever they feel like.
Click to expand...
Click to collapse
Okay that's what I thought but then when he mentioned Sprint it made me wonder. That's interesting though
Spencervb256 said:
No way that's actually awesome. About time. But also kinda weird seeing as the unlocked version hasn't even gotten it yet
Click to expand...
Click to collapse
Makes sense. Sprint is the crappiest carrier out there so if it's got tons of bugs they won't know whether to blame the phone or the service. LMAO!