Hi guys, sorry for my english
I have a nexus rooted, stock room and cwm installed but i didint recive the ota update to 4.2.2
Its normal?
Enviado desde mi Nexus 7 usando Tapatalk 2
I concur, precisely the same situation, stock ROM, stock kernel but rooted
Have also tried to flash using the downloaded .zip but fails with an error code of 7.
Any ideas guys?
Sent from my Nexus 7 using XDA Premium HD app
AW: I cant recive ota update
It depends on which country you're in. I live in Germany and I still haven't got the update
Sent from my Nexus 7 using xda app-developers app
I live in chile, but the nexus was buy in EEUU
Enviado desde mi Nexus 7 usando Tapatalk 2
UK. Sat next to my sister who had received the update...
Could rooting be causing as problem because that's threw only difference between our devices, besides storage sizes, mine being a 16gb, hers being a 32gb.
I'm sure that won't matter, would it?
Sent from my Nexus 7 using XDA Premium HD app
Force stop and clear data in google play services a couple times. ( I think that's what it is) worked for me.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Numerous threads popping up all over asking the same questions, Mods are going to shut & lock many of these out soon - suggest that one read and use the SEARCH button. My OTA was downloaded already and ready to install but choose to wait 48 hours first.
4.2.2 rollout is for USA / North America now - gradually - and OTA if you are essentially running stock rom & kernel - simple update without losing Apps or data (CWM backup, always, as best practices) - took me 15 minutes from downloading, prep & backup to actual flashing and reboot, etc.
I opted to take a shortcut and went from 4.1.2 directly to 4.2.2 using the zipped, deodexed rooted version w busy box - bootloader stayed on 3.41 running JDQ39 now, smooth. I uninstalled the DSP/Beats Audio/Noozxoide EIZO-rewire audio Apps, just in case - and reinstalled EIZO from Play Store afterward, freeze Chrome browser & switched back on Boat Browser w. Flash Player, OTG mount is working for external USB, etc.
Using N7 from other regions of the world, download using the links here on XDA, check MD5's and then go thru the steps - profit & enjoy.
Just to confirm then, and this will help a lot of other users:
Being on a stock but rooted rom with a stock kernel would make no hindrance to receiving the ota update, and the advice for people experiencing this situation would be to just be patient and wait?
Sent from my Nexus 7 using XDA Premium HD app
licaxda said:
I concur, precisely the same situation, stock ROM, stock kernel but rooted
Have also tried to flash using the downloaded .zip but fails with an error code of 7.
Any ideas guys?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I had same problem, I downloaded stock image of 4.1.2, flashed and found my n7 going in to the bootloop. Downloaded stock image of 4.2.2, flashed and everything is ok. Restored with carbon backup. That is all.
Sent from my Nexus 7 using Tapatalk HD
licaxda said:
Just to confirm then, and this will help a lot of other users:
Being on a stock but rooted rom with a stock kernel would make no hindrance to receiving the ota update, and the advice for people experiencing this situation would be to just be patient and wait?
Click to expand...
Click to collapse
Yes, my N7 was on rooted 4.1.2 factory rom & stock kernel, with minor tweaks for audio, Chrome browser frozen but no major mods otherwise, and the OTA file was downloaded already on the device when I checked yesterday, ready to install. From various threads posted in the last 48 hours, it's a mixed bags - some install easily while others ran into problems, reasons varied & solutions simple to unknown. I opted for a safer approach - reverse some of my tweaks/uninstalled the audio tweaks, unfreeze Chrome, rebooted & then wipe, before using CWM to flash. It was easy, rebooted and up & running in less than 10 minutes, ALL of the apps & data intact and no FC'd.
For (folks in Europe or Asia, etc.) not willing to wait or access to OTA and prepared to do it on your own (thus, taking the risks, however - small, do your backup first and save your data/settings/etc. with CWM or TWRP and Titanium Backup - to a HDD or USB drive (suggested: 8GB & up) or PC - just in case, for restoration in the "unlikely event" that something go wrong.
Here's the XDA-linked Factory IMG 4.2.2 Nakasi file links, either odexed or deodexed (rooted, insecure boot, etc.) that I used - also, download the bootloader zip in post #2 (not required or needed, but in case you needed it or wanted to use it as the latest bootloader) - http://forum.xda-developers.com/showthread.php?t=2148337
Download, check MD5's and transfer to the N7. Next - launch into bootloader (make sure USB debugging is enabled & unknown source is allowed too) and WIPE dalvik cache and cache (2 times or 3 times each) - then selected the zip to flash. Once done, exit & reboot and wait for it to boot up for the 1st. time and allow it to settle for a few minutes. Click Settings & confirmed that I'm on 4.2.2 and check a few Apps for functionality. Let it sit & shutdown, reboot & proceed to restore most of my tweaks, played videos & music, surf the web to reconfirm that it's running smooth - next, do a new baseline CWM Backup.
Of course, YMMV - if it doesn't work for you, re-trace your steps and take your time, do not RUSH. If all else failed, go back to stock first 4.1 or 4.2 - then, update to 4.2.1 in its rooted state - your saved Apps & data, settings, etc. saved to your PC or USB/portable drive will eventually help you "rebuild" - just a matter of time. (If my other 2 HTC's are that easy to update from GB to JB, I would be very, very happy)
Please give credit for "thanks" to "teshxx" for preparing the Roms and refer to that thread for future questions ...
Good Luck to all.
Great information, thanks for the hefty reply, may be worth stickying for a few weeks I'm sure others will have the same questions.
I believe installing Beats audio can screw things up too? Can some one confirm?
Sent from my Nexus 7 using XDA Premium HD app
Related
hello, i have locked moto and wonder do i need 4.2.2 root to install this rom or 4.4 cause i get bootloop after installing the rom.
Are you currently running jellybean? Sounds like you are not running the KitKat kernel.
Sent from my XT1060 using Tapatalk
Same Bootloop
Hey Nitro,
Moto X VZW Dev.Ed.
Unlocked BL
TWRP 2.6.3.1
Stock rom 4.4.2
SuperSU
Rom Toolbox Pro for my needs
Had Eclipse installed and was running great. Screen started to flash between operations and loading apps. Thought it was just a misbehaving app, deleted everything I installed and it kept happening. Reinstalled the Eclipse ROM, no-joy. So I brought the phone back to complete stock. I was running on stock for about a week, the OTA came for 4.4.2 and I took it.
Flashed TWRP and installed SU again. When I go to install Eclipse 3.3.2 it shows that everything is loading correctly (love the "mounting your system like a horse"). When it restarts itself it gets stuck in a bootloop with just the Eclipse image. I've left the phone alone for a half hour at a time and it never completes (at 45 minutes on the latest install attempt). Downloaded from the primary and mirror and tried those, same issue, tried it dirty at first, then wiped the dalvik/cache. I've read the main ROM thread - nothing that I could find where someone got stuck in a bootloop like this. Just wanted to pick your brain and see what you thought.
^^^It's long, my bad. I just wanted to make sure you had every detail possible.
Really appreciate it, it's a great ROM when I don't jack things up.
d33pblue said:
Hey Nitro,
Moto X VZW Dev.Ed.
Unlocked BL
TWRP 2.6.3.1
Stock rom 4.4.2
SuperSU
Rom Toolbox Pro for my needs
Had Eclipse installed and was running great. Screen started to flash between operations and loading apps. Thought it was just a misbehaving app, deleted everything I installed and it kept happening. Reinstalled the Eclipse ROM, no-joy. So I brought the phone back to complete stock. I was running on stock for about a week, the OTA came for 4.4.2 and I took it.
Flashed TWRP and installed SU again. When I go to install Eclipse 3.3.2 it shows that everything is loading correctly (love the "mounting your system like a horse"). When it restarts itself it gets stuck in a bootloop with just the Eclipse image. I've left the phone alone for a half hour at a time and it never completes (at 45 minutes on the latest install attempt). Downloaded from the primary and mirror and tried those, same issue, tried it dirty at first, then wiped the dalvik/cache. I've read the main ROM thread - nothing that I could find where someone got stuck in a bootloop like this. Just wanted to pick your brain and see what you thought.
^^^It's long, my bad. I just wanted to make sure you had every detail possible.
Really appreciate it, it's a great ROM when I don't jack things up.
Click to expand...
Click to collapse
Did you do a factory reset wipe? Also, are you running the 4.4.2 kernel?
Sent from my HTC6525LVW using Tapatalk
Info
nitroglycerine33 said:
Did you do a factory reset wipe? Also, are you running the 4.4.2 kernel?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I did not do a factory reset wipe the first time. I did the second time. Same situation.
The kernel I'm using is:
3.4.42-g3385454
- Jan 23 17:09
System Version:
164.55.2.ghost_verizon.Verizon.en.US
Build #:
KXA20.16-1.25.2
I appreciate you taking the time out to look at this, thank you.
Hello.
I recently received an update to my TF701. I already had 4.3 and this update boot looped and made me wipe data twice. After the tablet starts I have 4.2.2. How can I update manual to 4.3, because I can't find in system updates a new update and I downloaded the manual update from asus website, but I don't know how to install it. Any help will be very very big appreciated.
popab said:
Hello.
I recently received an update to my TF701. I already had 4.3 and this update boot looped and made me wipe data twice. After the tablet starts I have 4.2.2. How can I update manual to 4.3, because I can't find in system updates a new update and I downloaded the manual update from asus website, but I don't know how to install it. Any help will be very very big appreciated.
Click to expand...
Click to collapse
Please, I really need help
I've got the exact same problem. I received an update and now he's in a boot loop for 40 minutes now...
Same don't know what to do Stuck on the Asus boot screen with the flashing circle.
Sent from my GT-I9505 using Tapatalk
I got the solution guys! First wipe data in bootloader (hold power and vol down(I wiped data twice, still had some problems after the first wipe)). Then your device will boot and you will have 4.2.2. Then download the firmware from ASUS support ( page worked for me 6 hours ago, but now it does not work, I will give you the link when I will get to my pc) and place the firmware on the tablet (not in a folder, just directly where all the folders are) and your tablet will automatically notify you about the update found on the memory (is really easy). Hope I was helpful for you guys, ASUS ruined this day for me, I had 20 gigs on my memory and they were all ereased...
Sent from my GT-I9505 using XDA Premium 4 mobile app
Hi thanks haven't checked who version yet but had to wipe. Didn't lose much other than game data.
Sent from my GT-I9505 using Tapatalk
This is the link if you want to manual update to 4.3: http://www.asus.com/au/supportonly/ASUS Transformer Pad (TF701T)/
Yep back on 4.2.2
Sent from my GT-I9505 using Tapatalk
popab said:
This is the link if you want to manual update to 4.3: http://www.asus.com/au/supportonly/ASUS Transformer Pad (TF701T)/
Click to expand...
Click to collapse
All Firmware is in the General thread in one of the first posts available for download, no need to go to Asus website for that.
Sent from my Asus Infinity TF700 with Dock
and all neccessary information regarding the false update of Asus can be found in this thread http://forum.xda-developers.com/showthread.php?t=2586847
Thread http://forum.xda-developers.com/showthread.php?t=2554930 updated with latest firmware.
Except for WW version that is unavailable atm.
[Rom][N910VVRU1ANJ5][4.4.4] Stock Root Odex/Knox-Free
Here is the Stock Flashable N910VVRU1ANJ5 Rooted, Odex, Knox Free. Built from the original factory image
This is for the DE Phone!!!
I will build a Safe Strap version as soon as you retail guys get root with Safe Strap!!!
I need some testers for my new Rom. Please PM me if you are interested.
Requirments are TWRP Recovery
Features:
Odex
Rooted
Init.d support
Knox Free
Native WiFi Hotspot
Removed Verizon OTA updater
Removed How To Nonsense from Verizon.
Read/Write to external storage
ROM Zips
Verizon Note 4 NJ5 V1.0 ported for the DE Phone-Download: NJ5 V1.0 Odex Note 4
Verizon Note 4 NJ5 V1.1 ported for the DE Phone-Download: NJ5 V1.1 Odex Note 4
Verizon Note 4 NJ5 V1.2 ported for the DE Phone-Download: NJ5 V1.2 Odex Note 4
Code:
[B][U]V1.1 - Full Wipe[/U][/B]
-Various Bug Fixes
Code:
[B][U]V1.2 - Full Wipe[/U][/B]
-App fixes
-Gear VR working
-This version should be BUG Free let me know!!
Installation Instructions:
1: DO A NANDROID
2: Download the ROM and copy it to your external SD card.
3: Do a complete wipe by checking Dalvik Cache, Data, Cache, Internal Storage and System from TWRP.
4: Install the ROM via TWRP.
5: Reboot and Enjoy
6. You will get a few fc's on boot. You need to update Google Services as soon as possible.
I also would set Play Store so it does not auto update apps.
It will take a few hours for the phone to index and settle down.
Please be patient when the phone reboots. It will sit on the boot animation for as long as 5 min.
PLEASE DON'T FORGET TO HIT THANKS!! THIS TOOK MANY HOURS TO PUT TOGETHER!!!!
If any other Dev's want to use this as a base, please feel free to do so with proper credit!! No need to ask me!!
Just in Case
uhhh isnt there another thread for this rom already ?
solidunit said:
uhhh isnt there another thread for this rom already ?
Click to expand...
Click to collapse
Uhhh This is NJ5 based ... other Rom is NI1
odex
How about bloat free odex version?
or a list of apps and supporting files removed from your original release?
Hey I have a problem here. I'm coming from your very first ROM to this one. It was running great smooth as butter until now. I tried flashing this new ROM but my phone wouldn't boot up, it wouldn't get past the first Samsung screen just keeps restarting. I made sure to follow step by step instructions. Wiped everything but my SD card. Tried it 2 more times and nothing. Tried to wipe cache and all that. Nothing helped. So I decided to restore back to my backed up ROM. Once restored it started to act weird. My finger print scanner doesn't work and I can't download anything another than apps from app store...the phone is very glitchy almost like it has a virus. I tried and tried to reset things but no luck. I don't have a backup of stock Dev ROM unfortunately... Anyone help please?
Sent from my SM-N910V using XDA Free mobile app
shpotik said:
Hey I have a problem here. I'm coming from your very first ROM to this one. It was running great smooth as butter until now. I tried flashing this new ROM but my phone wouldn't boot up, it wouldn't get past the first Samsung screen just keeps restarting. I made sure to follow step by step instructions. Wiped everything but my SD card. Tried it 2 more times and nothing. Tried to wipe cache and all that. Nothing helped. So I decided to restore back to my backed up ROM. Once restored it started to act weird. My finger print scanner doesn't work and I can't download anything another than apps from app store...the phone is very glitchy almost like it has a virus. I tried and tried to reset things but no luck. I don't have a backup of stock Dev ROM unfortunately... Anyone help please?
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
Go here download the StockRestore tar, flash that in odin and you should be good to go. Then you can flash this rom if you like. You shouldn't have to wipe anything but if you run into errors just do a factory reset. FYI the stock restore is pretty much the same as this rom without knox removed, SU will ask if you want to disable it or you can freeze/remove it with TB so technically there is really no reason to flash this after the odin restore.
solidunit said:
uhhh isnt there another thread for this rom already ?
Click to expand...
Click to collapse
One is deodexed and one is odexed.
ifly4vamerica said:
Uhhh This is NJ5 based ... other Rom is NI2
Click to expand...
Click to collapse
The other ROMs are actually NI1.
Is there an ad block zip I can flash? I'm so sick of ads
EMSPilot,
Is there a way you can update this rom with a StageFright fix?
how to flash thise rom ,icant flashe recovery on ni1 can you tellme??
Back to KitKat
EMSpilot said:
[Rom][N910VVRU1ANJ5][4.4.4] Stock Root Odex/Knox-Free
Here is the Stock Flashable N910VVRU1ANJ5 Rooted, Odex, Knox Free. Built from the original factory image
This is for the DE Phone!!!
I will build a Safe Strap version as soon as you retail guys get root with Safe Strap!!!
I need some testers for my new Rom. Please PM me if you are interested.
Requirments are TWRP Recovery
Features:
Odex
Rooted
Init.d support
Knox Free
Native WiFi Hotspot
Removed Verizon OTA updater
Removed How To Nonsense from Verizon.
Read/Write to external storage
ROM Zips
Verizon Note 4 NJ5 V1.0 ported for the DE Phone-Download: NJ5 V1.0 Odex Note 4
Verizon Note 4 NJ5 V1.1 ported for the DE Phone-Download: NJ5 V1.1 Odex Note 4
Verizon Note 4 NJ5 V1.2 ported for the DE Phone-Download: NJ5 V1.2 Odex Note 4
Code:
[B][U]V1.1 - Full Wipe[/U][/B]
-Various Bug Fixes
Code:
[B][U]V1.2 - Full Wipe[/U][/B]
-App fixes
-Gear VR working
-This version should be BUG Free let me know!!
Installation Instructions:
1: DO A NANDROID
2: Download the ROM and copy it to your external SD card.
3: Do a complete wipe by checking Dalvik Cache, Data, Cache, Internal Storage and System from TWRP.
4: Install the ROM via TWRP.
5: Reboot and Enjoy
6. You will get a few fc's on boot. You need to update Google Services as soon as possible.
I also would set Play Store so it does not auto update apps.
It will take a few hours for the phone to index and settle down.
Please be patient when the phone reboots. It will sit on the boot animation for as long as 5 min.
PLEASE DON'T FORGET TO HIT THANKS!! THIS TOOK MANY HOURS TO PUT TOGETHER!!!!
If any other Dev's want to use this as a base, please feel free to do so with proper credit!! No need to ask me!!
Click to expand...
Click to collapse
Is this the way, on my newly unlocked, rooted DE, US Verizon note 4, running 5.1.1 android, to get back to Kitkat? I loved the speed, and battery life for two days, in the original Kitkat. Unfortunately, I lost the ability to go back with OTA updates .
Had to rub my eyes to make sure I was seeing a new rom for 4.4.4!!!!! YeeeeHaaaa!
Thank you so much.
On Definitive ROM now, but will try this when i get home.
What kernel would you recommend?
thanks again!
Can't seem to figure out how to install this, with my newly unlocked, rooted DE, Verizon Note 4. I would love to go back to original Kit Kat!
evolovernow said:
Can't seem to figure out how to install this, with my newly unlocked, rooted DE, Verizon Note 4. I would love to go back to original Kit Kat!
Click to expand...
Click to collapse
I've got to echo this question/statement. I've been going around in circles for about two months on and off trying various methods and combinations of kernels and roms and firmwares in order to downgrade. I've unlocked the bootloader about 4 times now in my quest and every time eventually have ended with the "software update failed" screen forcing me to re-partition and flash MM again. A few random places on the internet seem to infer that it's nigh impossible to get back to kitkat. If that's the case then so be it, but why?
I've searched and searched and experimented and experimented some more but can't seem to find a way past 5.1.1. Heck I can't even seem to get to OAF flashed successfully (one website instructs being at 5.0.1 before being able to dgrade to kitkat). Any help would be appreciated. I've thought about starting a thread but with the derision this kind of question gets (even though I've tried quite a bit on my own), this seems like a better place to post for now.
Cheers!
Due to the request of various members I have started a topic here for the rom for the xt1096 verizon model with android 6.0 marshmallow. This rom was developed by @hutchjim using the xt1097 marshmallow as a base.
Installation:
To install the rom, flash the zip from a custom recovery such as TWRP/CWM/etc.
Root:
To root this rom @donslade has stated that the files for the XT1095 work for it. They can be found here: http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
Known issues:
None as of now.
Downloads:
Current version
Custom rom with new build.prop by yahya1054:
Download
AGISCI said:
Due to the request of various members I have started a topic here for the rom for the xt1096 verizon model with android 6.0 marshmallow. This rom was developed by @hutchjim using the xt1097 marshmallow as a base.
Installation:
To install the rom, flash the zip from a custom recovery such as TWRP/CWM/etc.
Root:
To root this rom @donslade has stated that the files for the XT1095 work for it. They can be found here: http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
Known issues:
Some people are experiencing an issue where it says they are roaming.
Downloads:
Main download
Mirror 1
Click to expand...
Click to collapse
What the difference between this rom and 1095 MM Rom
kaktusmaier125 said:
What the difference between this rom and 1095 MM Rom
Click to expand...
Click to collapse
This one has support for verizon cdma. It is only useful for people who use verizon service.
Sent from my XT1095 using Tapatalk
AGISCI - Thanks for creating this thread. I hope we will have participation from folks who will test and provide feedback. I also hope that hutchjim will also provide info on how this ROM was created and what changes he made.
I believe the ROM is debloated from most of the Verizon apps and installs TWRP 2.8.7 as recovery. All of the Motorola Apps are there and function as expected from my experience. My phone connected to Verizon for voice and data. I do not know what other changes were made.
My experience to date has been mostly positive with just a few issues. I'll list those in a message a bit later. For now here is my interpretation of hutchjim's installation instructions:
1. Perform factory reset/wipe. THIS WILL WIPE YOUR PHONE AND ALL DATA ON IT. Either the built in reset/wipe of using TWRP. I used TWRP 3
2. Flash ROM
3. Perform another reset/wipe. I used TWRP 3
4. Phone will boot to initial setup. Follow prompts. Hutchjim says not to setup wifi during this phase but I see no way to avoid that. I connected to my home wifi at this point and continued setup.
5. As soon as you can go into Settings go to Cellular Networks > CDMA and select RUIM. No other changes should be made in the Cellular settings. You can also go to Backup & Reset > Reset Network Settings and reset there. Verify that the CDMA > RUIM setting is still selected.
6. Reboot and verify network settings.
7. Continue setup/restore from previous backup from Google. Any apps that need updating for MM will do so during the restore.
Doing the above results in a phone running 6.0.1 which identifies itself as a XT1097. I'll post a screen shot of the ABOUT phone screens later.
To root I used the files from here:http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
Flash using TWRP
1. root-boot-6.0-xt1095.zip
2. UPDATE-SuperSU-2.65.zip (there might be a newer one out there but this one worked for me. It should update later if needed)
After this I was able to install the latest Exposed framework and app, Gravity MM, XGELS and AOSPSignal icons modules with no problems.
I had been using this ROM with no real issues since last Friday. Legacystar reported that his phone was Roaming after he installed the ROM. Mine was not Roaming worked great - until this morning when it went into Roaming a couple of hours ago. Nothing I did could make it change back. I restored a backup of this ROM from Saturday but the phone is still Roaming. I've now gone back to my last 5.0 backup and will try to reinstall the ROM later when am back home. Will update then.
Here is a list of items I think we need more info on:
1. What was the base ROM for this? I think it is XT1097 based but it may be XT1095 since the XT1095 root files work.
2. What changes were made to get this to work wit the XT1096 radio and allow CDMA operation?
3. How do the Cellular settings work and how can they be improved for this ROM?
4. How to bypass the network setup screen during initial MM setup?
Hope this helps. I'll update more after work and when I reinstall the ROM. Until then I hope more testers chime in with their experiences.
Don Slade
donslade said:
AGISCI - Thanks for creating this thread. I hope we will have participation from folks who will test and provide feedback. I also hope that hutchjim will also provide info on how this ROM was created and what changes he made.
I believe the ROM is debloated from most of the Verizon apps and installs TWRP 2.8.7 as recovery. All of the Motorola Apps are there and function as expected from my experience. My phone connected to Verizon for voice and data. I do not know what other changes were made.
My experience to date has been mostly positive with just a few issues. I'll list those in a message a bit later. For now here is my interpretation of hutchjim's installation instructions:
1. Perform factory reset/wipe. THIS WILL WIPE YOUR PHONE AND ALL DATA ON IT. Either the built in reset/wipe of using TWRP. I used TWRP 3
2. Flash ROM
3. Perform another reset/wipe. I used TWRP 3
4. Phone will boot to initial setup. Follow prompts. Hutchjim says not to setup wifi during this phase but I see no way to avoid that. I connected to my home wifi at this point and continued setup.
5. As soon as you can go into Settings go to Cellular Networks > CDMA and select RUIM. No other changes should be made in the Cellular settings. You can also go to Backup & Reset > Reset Network Settings and reset there. Verify that the CDMA > RUIM setting is still selected.
6. Reboot and verify network settings.
7. Continue setup/restore from previous backup from Google. Any apps that need updating for MM will do so during the restore.
Doing the above results in a phone running 6.0.1 which identifies itself as a XT1097. I'll post a screen shot of the ABOUT phone screens later.
To root I used the files from here:http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
Flash using TWRP
1. root-boot-6.0-xt1095.zip
2. UPDATE-SuperSU-2.65.zip (there might be a newer one out there but this one worked for me. It should update later if needed)
After this I was able to install the latest Exposed framework and app, Gravity MM, XGELS and AOSPSignal icons modules with no problems.
I had been using this ROM with no real issues since last Friday. Legacystar reported that his phone was Roaming after he installed the ROM. Mine was not Roaming worked great - until this morning when it went into Roaming a couple of hours ago. Nothing I did could make it change back. I restored a backup of this ROM from Saturday but the phone is still Roaming. I've now gone back to my last 5.0 backup and will try to reinstall the ROM later when am back home. Will update then.
Here is a list of items I think we need more info on:
1. What was the base ROM for this? I think it is XT1097 based but it may be XT1095 since the XT1095 root files work.
2. What changes were made to get this to work wit the XT1096 radio and allow CDMA operation?
3. How do the Cellular settings work and how can they be improved for this ROM?
4. How to bypass the network setup screen during initial MM setup?
Hope this helps. I'll update more after work and when I reinstall the ROM. Until then I hope more testers chime in with their experiences.
Don Slade
Click to expand...
Click to collapse
1) It is based on xt1097, specifically on retla which is the retail latin america variant. I am not surprised that the root files for xt1095 work since the xt1097 and xt1095 are extremely similar.
2) He sent me a list of some of the changes, I will dig through the files modified to get more details on what changed.
I was sent a new version by @hutchjim, it is uploading to google drive now. Hopefully in the new version the roaming problem is fixed.
Sent from my XT1095 using Tapatalk
Thanks for the update. I had notice that it did say retla in the system version. Need to pay attention to the baseband info.. Based on that I don't need to upload the About Phone screens then.
Very excited for this. Do gapps need to be flashed as well?
Sent from my XT1096 using Tapatalk
RamAir02 said:
Very excited for this. Do gapps need to be flashed as well?
Sent from my XT1096 using Tapatalk
Click to expand...
Click to collapse
It's a stock rom, gapps are in it already.
Sent from my XT1095 using Tapatalk
AGISCI said:
1) It is based on xt1097, specifically on retla which is the retail latin america variant. I am not surprised that the root files for xt1095 work since the xt1097 and xt1095 are extremely similar.
2) He sent me a list of some of the changes, I will dig through the files modified to get more details on what changed.
I was sent a new version by @hutchjim, it is uploading to google drive now. Hopefully in the new version the roaming problem is fixed.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
has this new version been uploaded yet?
Legacystar said:
has this new version been uploaded yet?
Click to expand...
Click to collapse
It's uploading right now, for some reason my connection is super slow today. I will post as soon as it's done uploading.
Sent from my XT1095 using Tapatalk
AGISCI said:
It's uploading right now, for some reason my connection is super slow today. I will post as soon as it's done uploading.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
awesome, thank you. any idea what he did to fix the roaming issue?
Legacystar said:
awesome, thank you. any idea what he did to fix the roaming issue?
Click to expand...
Click to collapse
He said he added a verizon app in priv-apps.
Sent from my XT1095 using Tapatalk
AGISCI said:
He said he added a verizon app in priv-apps.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
might have been the verizon apn app
Alright, sorry for the long delay. My internet is messed up right now. I started the upload last night and left it running. I woke up to a failed upload message. I started it again and it took 5 hours to upload... anyway, I have updated the first post with the link to the new version. Please try it out and let us know if you have issues with roaming still.
I have had the roaming issue since I installed the original MM posted a few days ago but even though the R is showing by 4g it still allows me to access data through 4g. Hope I am not going to incur the financial wrath of big red. lol. I was reading this forum using it. Anyway, I want to say thanks for those putting in the work to try and figure this out and support a stock MM rom for the xt1096. I will test the new version as soon as I get it downloaded and report back if the roaming issue persists for me.
I have updated to the latest version of stock MM offered on first post and can confirm that the R roaming symbol is gone. I have rebooted several times and finished setting my phone up how I want it. The only issue I had during the process of installing and setting up this version of MM is that upon rebooting the first 2 times I had a pop up saying "Unfortunately, Verizon Login has stopped."
I rebooted into twrp and installed reinstalled the root and su zips and upon reboot the pop up went away. I guess I was wrong to assume that the order for installing the zips were 1)root boot for 1095, 2)Super SU and 3) MM Rom. After reading that in order it makes more sense to load the Rom then the root and su zips. Oh well, all is well that ends well.
Has anyone figured out how to bypass the wifi setup screen during setup?
Wrong forum.
i just loaded the new version and still getting the roaming. also having the verizon app crash on startup.
To skip WiFi setup, put sim card in on welcome screen so after boot put sim,
also roaming is gone for me but I just get data, no voice on some reboots voice aval even when it says out of service same last build.
Roaming was an issue older build new build fixed, voice still wonky for me
[ROM] [STOCK] Optimized Stock ROMs for Amazon Fire 7 (Ford & Austin) [APR 12 2019]
Optimized Stock ROM for the Amazon Fire 7 (the Ford and Austin models ONLY). Do not use any FireOS versions LOWER than what you are already using, or you will bootloop. In other words, no downgrading to an older version.
- Ford Firmware is based off of Amazon FireOS 5.3.1.0 (update-kindle-global-37.5.5.2_user_552153420.bin) and rebuilt using @superR Kitchen. Do not downgrade from a newer version. Austin firmware is based off the latest current release. As of April 12, that's 5.3.6.4.
- Deodexed. When uninstalling system apps, the odex files are left behind. The process of deodexing, making a long story short, puts those files back where they belong. In turn, when or if you uninstall the system application(s) associated with them, you gain a little more space. This also makes the uninstall process smoother with less risks of screwing up. I am down to about 93 Apps. 89 if you take away the 4 user apps installed
- Ford: Rooted. During installation, the ROM will be rooted with the last and final version of SuperSU, v2.82 by @Chainfire and contain the latest Busybox by @osm0sis.
- Austin: You must flash SuperSU or Magisk separately, after installing your firmware.
- Zipaligned. For smooth operations and better performance.
- No OTA. Both APKs associated with over the air updates (OTA) have been removed. This means no more waiting to connect to WiFi. You can safely sign into your network on the very first boot.
-YOU decide what you want. No apps have been removed aside from the above mentioned and none have been added aside from the above mentioned. Which means NO Gapps or Xposed. You are in control of your device therefore you should also decide what you want to keep, install or uninstall.
- STOCK. This ROM does NOT include my modifications or any other modifications not mentioned here.
Requirements and Installation
1. For Amazon Fire 7 Ford and Austin ONLY. Must already have root access or already have your bootloader unlocked.
2. If TWRP: Disconnect the tablet from PC and power it off. Reboot to recovery, hold down the volume down button and power button until the white amazon logo appears. When in recovery, tap wipe and select dalvik, cache, system and data ONLY and swipe to confirm. When done, tap home then reboot then recovery and swipe to confirm.
3b. If FlashFire (UNTESTED): First refer to step 2. When done open FlashFire. Tap the '+' and select OTA package or zip. Select the ROM fire_7_ford_stock_deodexed_rooted_no_ota-signed.zip. Tap the checkmark to confirm. Tap the '+' again and select wipe. Make sure EVERYTHING is selected EXCEPT storage. Tap the checkmark. Long press the wipe option on the screen and move it ABOVE the ROM zip. If Ever-root appeared, tap it and make sure ONLY preserve recovery is selected. Tap the flash button and confirm.
4 (TWRP continued). When back in recovery, navigate to the storage location of the New ROM and tap on it: fire_7_ford_stock_deodexed_rooted_no_ota-signed.zip and swipe to confirm installation. When done, reboot system.
5. Enjoy.
Downloads
- Ford Optimized ROM: fire_7_ford_stock_deodexed_rooted_no-ota_stock_rom-signed.zip
- Austin Optimized ROM: fire_7_austin_deodexed_rooted_no-ota_stock_rom-signed.zip
DragonFire1024 said:
Optimized Stock ROM for the Amazon Fire 7 (Ford)
- Based off of Amazon FireOS 5.3.1.0 (update-kindle-global-37.5.5.2_user_552153420.bin) and rebuilt using @superR Kitchen
- Deodexed. When uninstalling system apps, the odex files are left behind. The process of deodexing, making a long story short, puts those files back where they belong. In turn, when or if you uninstall the system application(s) associated with them, you gain a little more space. This also makes the uninstall process smoother with less risks of screwing up. I am down to about 93 Apps. 89 if you take away the 4 user apps installed
- Rooted. During installation, the ROM will be rooted with the last and final version of SuperSU, v2.82 by @Chainfire and contain the latest Busybox by @osm0sis.
- Zipaligned. For smooth operations and better performance.
- No OTA. Both APKs associated with over the air updates (OTA) have been removed. This means no more waiting to connect to WiFi. You can safely sign into your network on the very first boot.
-YOU decide what you want. No apps have been removed aside from the above mentioned and none have been added aside from the above mentioned. Which means NO Gapps or Xposed. You are in control of your device therefore you should also decide what you want to keep, install or uninstall.
- STOCK. This ROM does NOT include my modifications or any other modifications not mentioned here.
Requirements
1. For Amazon Fire 7 Ford ONLY. Must already have root access or already have your bootloader unlocked.
2. Plug your tablet into the PC and Download the zip attached to this post. Place it on internal or external storage. Go to the Open Gapps website and download the PICO Gapps Package for ARM, 5.1.1 and place it on your tablet's internal or external storage.
3. If TWRP: Disconnect the tablet from PC and power it off. Reboot to recovery, hold down the volume down button and power button until the white amazon logo appears. When in recovery, tap wipe and select dalvik, cache, system and data ONLY and swipe to confirm. When done, tap home then reboot then recovery and swipe to confirm.
3b. If FlashFire (UNTESTED): First refer to step 2. When done open FlashFire. Tap the '+' and select OTA package or zip. Select the ROM fire_7_ford_stock_deodexed_rooted_no_ota-signed.zip. Tap the checkmark to confirm. Tap it again. Tap the '+' again and select OTA/zip and select the Gapps zip. Tap the checkmark when done. Tap it again. Tap the '+' again and select wipe. Make sure EVERYTHING is selected EXCEPT storage. Tap the checkmark. Long press the wipe option on the screen and move it ABOVE the ROM zip. If Ever-root appeared, tap it and make sure ONLY preserve recovery is selected. Tap the flash button and confirm.
4 (TWRP continued). When back in recovery, navigate to the storage location of the ROM and Gapps zips. Tap the ROM: fire_7_ford_stock_deodexed_rooted_no_ota-signed.zip and swipe to confirm installation. When done, tap BACK and select the Gapps zip. Swipe to install. When done, reboot system.
5. Enjoy.
Downloads
- ROM: fire_7_ford_stock_deodexed_rooted_no_ota-signed.zip
- Gapps: Arm, 5.1.1, Pico. Open Gapps Project.
Click to expand...
Click to collapse
Good Job!
Waiting for the 7th gen..
PS: If you want to implement custom otas pm me. I know a method that works.
Rortiz2 said:
Good Job!
Waiting for the 7th gen..
PS: If you want to implement custom otas pm me. I know a method that works.
Click to expand...
Click to collapse
I just need the firmware .bin file. I can't test a build but I can build it and you can test it. In theory it should work. I'm pretty sure now, unless amazon changes something drastically, I think every fireOS version under 6 can be rooted on the spot from here on out. In other words FireOS can be permanently rooted.
Sent from my MotoG3 using XDA Labs
Gapps is optional. I recommend you uninstall the apps you don't want and flash gapps after.
Sent from my MotoG3 using XDA Labs
Didn't work for me. Just sat on the Fire animation screen for about 30 minutes.
riverstyxxx said:
Didn't work for me. Just sat on the Fire animation screen for about 30 minutes.
Click to expand...
Click to collapse
I think that it don't work because uses the 5.3.1.0 boot.img and the new preloader doesn't seem to be compatible with this boot.img.
Should follow in the footsteps of the other one, Fire OS Revamped. It's running on 5.6.3.0 perfectly.
Rortiz2 said:
I think that it don't work because uses the 5.3.1.0 boot.img and the new preloader doesn't seem to be compatible with this boot.img.
Click to expand...
Click to collapse
The boot.img isn't unpacked. It's simply a system install. No imgs are unpacked.
Sent from my MotoG3 using XDA Labs
Rortiz2 said:
I think that it don't work because uses the 5.3.1.0 boot.img and the new preloader doesn't seem to be compatible with this boot.img.
Click to expand...
Click to collapse
This is only for the Ford tablet too. I will have to optimize the more recent firmware releases for newer tablets.
Sent from my MotoG3 using XDA Labs
riverstyxxx said:
Should follow in the footsteps of the other one, Fire OS Revamped. It's running on 5.6.3.0 perfectly.
Click to expand...
Click to collapse
This is only for the Ford model. Essentially for those who remain and continue to remain on 5.3.1. ill have some more ready this week. Please note when I specify a device, it's only for that device.
Sent from my MotoG3 using XDA Labs
DragonFire1024 said:
This is only for the Ford model. Essentially for those who remain and continue to remain on 5.3.1. ill have some more ready this week. Please note when I specify a device, it's only for that device.
Sent from my MotoG3 using XDA Labs
Click to expand...
Click to collapse
Yeah, Ford. KFFOWI. Flashed it and gapps with TWRP. Didn't work.
riverstyxxx said:
Yeah, Ford. KFFOWI. Flashed it and gapps with TWRP. Didn't work.
Click to expand...
Click to collapse
We're you already on 5.3.1? I made a note that this likely only works if you're already on 5.3.1.
Sent from my MotoG3 using XDA Labs
DragonFire1024 said:
We're you already on 5.3.1?
Sent from my MotoG3 using XDA Labs
Click to expand...
Click to collapse
I downgraded to whatever was in the twrp tutorial and went from the latest lineage to this. If that helps.
riverstyxxx said:
I downgraded to whatever was in the twrp tutorial and went from the latest lineage to this. If that helps.
Click to expand...
Click to collapse
Yeah you shouldn't downgrade again once you've moved on from 5.3.1. even taking out the boot.img, the old versions just aren't compatible with the new generation of fire 7s. I apologize. I have made a note in the OP. At least this time you can recover form it. I now know how it feels for those back in the day only they couldn't recover from this. Again apologies.
Sent from my MotoG3 using XDA Labs
DragonFire1024 said:
Yeah you shouldn't downgrade again once you've moved on from 5.3.1. even taking out the boot.img, the old versions just aren't compatible with the new. I apologize. I have made a note in the OP.
Sent from my MotoG3 using XDA Labs
Click to expand...
Click to collapse
It's understandable. If you work on the latest build, that would be awesome because I do like what the other developer did but he left in a few things (and left out a few things) that he shouldn't have.
riverstyxxx said:
It's understandable. If you work on the latest build, that would be awesome because I do like what the other developer did but he left in a few things (and left out a few things) that he shouldn't have.
Click to expand...
Click to collapse
Link me to the latest firmware for your tablet, and give me the model of your tablet and I'll see what I can do.
Sent from my MotoG3 using XDA Labs
DragonFire1024 said:
Link me to the latest firmware for your tablet, and give me the model of your tablet and I'll see what I can do.
Sent from my MotoG3 using XDA Labs
Click to expand...
Click to collapse
I assume it's this: https://www.amazon.com/gp/help/customer/display.html?nodeId=201830180
The one on my tablet is FireOS Revamped 5.3.6.0, in the other part of the forums.
riverstyxxx said:
I assume it's this: https://www.amazon.com/gp/help/customer/display.html?nodeId=201830180
The one on my tablet is FireOS Revamped 5.3.6.0, in the other part of the forums.
Click to expand...
Click to collapse
Ok I'll look at it in the next day or two. So far I've tried 2 firmwares, fire 7 ford, and HD 10. Both can already be rooted. So let's see if that makes any difference. I'm hoping it doesn't. If it works, then every amazon update from here on out, unless they change something, can be pre rooted.
Sent from my MotoG3 using XDA Labs
DragonFire1024 said:
Ok I'll look at it in the next day or two. So far I've tried 2 firmwares, fire 7 ford, and HD 10. Both can already be rooted. So let's see if that makes any difference. I'm hoping it doesn't. If it works, then every amazon update from here on out, unless they change something, can be pre rooted.
Sent from my MotoG3 using XDA Labs
Click to expand...
Click to collapse
If you want to PM Me test versions for austin i can test it. But use 5.6.3.4 as base:
https://fireos-tablet-src.s3.amazon...z43/update-kindle-55.6.2.6_user_626533320.bin
Regards!
Rortiz2 said:
If you want to PM Me test versions for austin i can test it. But use 5.6.3.4 as base:
https://fireos-tablet-src.s3.amazon...z43/update-kindle-55.6.2.6_user_626533320.bin
Regards!
Click to expand...
Click to collapse
I have a few days off starting tomorrow. I'll see what I can accomplish.
Sent from my MotoG3 using XDA Labs