Related
Just incase anyone with an Atrix 4G and 4.5.145 firmware, I followed the instructions in the following threads to successfully install Atrix-MROM on a brand new Atrix 4G ATT with the latest update.
1- Bootloader Unlock: http://forum.xda-developers.com/showthread.php?t=1182871
2- Root: http://forum.xda-developers.com/showthread.php?t=1769497
3- CWM Flash: http://wiki.cyanogenmod.org/w/Install_CM_for_olympus#Installing_recovery_using_fastboot
4- Atrix-MROM Flash: http://www.montuori.net/android-mrom/atrix-mrom/
Thank you Michael Montuori, the Atrix-MROM is awesome.
Rooting (step 2) is completely irrelevant and unnecessary. I've said this before. Still not sure why people constantly think rooting does anything if they're going to flash a new ROM anyway.
ravilov said:
Rooting (step 2) is completely irrelevant and unnecessary. I've said this before. Still not sure why people constantly think rooting does anything if they're going to flash a new ROM anyway.
Click to expand...
Click to collapse
I think this is because, normally, they would need it to flash CWM. But it doesn't happen on Atrix. .
Yeah, that's pretty much what I thought. People scarred/traumatized by other brands/phones and thinking everything is the same on all the other ones.
Oh well. Hopefully they'll learn one day. Hopefully a little sooner than the Atrix REALLY becomes obsolete.
ravilov said:
Yeah, that's pretty much what I thought. People scarred/traumatized by other brands/phones and thinking everything is the same on all the other ones.
Oh well. Hopefully they'll learn one day. Hopefully a little sooner than the Atrix REALLY becomes obsolete.
Click to expand...
Click to collapse
This is my first smart phone, and I am absolute noob in this field.
I have been using Nokia 1216 and similar monochrome display phones before it.
In that case, I gues you're actually doing quite well really... If you came from mono dumbphones straight to this and have already flashed a custom ROM, that's actually kinda impressive.
Thanks!!!
Much thanks my friend I thoght I was stuck in 145, I applied numbers 1 and 3 and now Im unlocked and have CWM
pinofly said:
Much thanks my friend I thoght I was stuck in 145, I applied numbers 1 and 3 and now Im unlocked and have CWM
Click to expand...
Click to collapse
Glad it helped you.
pinofly said:
Much thanks my friend I thoght I was stuck in 145, I applied numbers 1 and 3 and now Im unlocked and have CWM
Click to expand...
Click to collapse
Please can you tell me, where i found the tool for unlock bootloader of step 1, because the link is outdated, thank you.
aarizaga said:
Please can you tell me, where i found the tool for unlock bootloader of step 1, because the link is outdated, thank you.
Click to expand...
Click to collapse
It is in that thread. You can search: automatic_unlock_v4.2.zip
Or here it is:
h t t p s:// w w w . d r o p b o x . com/s/sr6ooho4zf9wqvo/automatic_unlock_v4.2.zip
Scan it first..
The MROM is simply amazing. Best battery life so far trying the cm7 based roms!
Sent from my MB860 using xda app-developers app
I am a neewbie, and when i learned how to flash custom roms, i was wondering, it is really necesary to root if you want a custom ROM?
now i was clarified.
So if want original firmware, and root acces, i just need an unlocked bootloader? And for rooting, can i just flash a fruitcake?
Sent from my MB860 using xda app-developers app
Hi, Thank you mmontuori for the excellent Rom and hard work to do it, and to Ravilov for the help.
I want to thanks in the post of the MROM in the development forum, but I can't do it because I don't have enough posts.
Well I finish yesterday to put all in order, only my contacts information I fail to restore.
The Go Backup didn't work.
One question, I don't installed the sv kernel, is necesary? because I feel that the battery it drain very quickly.
The rest appear so far to work very well, checking the holo launcher.
are you 100% sure everything on first post works with an ATRIX 4G 4.15.1455 from AT&T wiht the original motoblur?
i am newbee but wants to learn. its probably could i kill the phone?
thx!
Atrix 4g ATT 4.5.145 working well with CM 7.2
I have an Atrix 4g that was about to be retired or sold, and decided to instead make it an android project to learn about modding and possibly make something useful out of an old device.
After combing the forums on this site and others, realized there was some risk involved of a hard brick, but since this is not my main phone anymore, I wasnt too worried about. I'll share the results...
The phone was running gingerbread 2.3.6, ATT 4.5.145 build
#1) Root phone (http://forum.xda-developers.com/showthread.php?t=1769497)
Step 10 did generate an error for me, I had to issue the alternate command and it worked fine.
I downloaded root checker by JOEYKRIM on google play store to ensure it was rooted properly afterwards.
#2) Backup the phone in case of trouble (I used titanium backup from google play store, requires rooting from step 1)
Add a schedule to backup all and execute the schedule now. Pretty easy stuff
#3) Unlock bootloader (http://forum.xda-developers.com/show....php?t=1182871)
This is probably the most dangerous step. I used the link above and would like to add a few comments. The link above is a script written to automate the process for those not terribly familiar with the android tools ADB and fastboot. This script is capable of unlocking your bootloader, fixing some common problems that happen along the way, and installing clockworkmod so you can access android recovery mode to install custom ROMs. However, it seems to come with an older version of the clockworkmod, therefore I used it for the bootloader only (option 1 from main menu). I also had to execute option 3 afterwards as I did get the failure to boot 0x1000 error. Long story short.. I used option 1, then option 3 and skip the rest.
#4) PUSH ROM files of your choice to phone (I used Cryogenmod 7.2 latest from http://download.cyanogenmod.org/?device=olympus)
You should also copy any other addon ROMs of your choice to the phone at this time as well. Google store app is one that is not included with CM 7.2 and you can get here (make sure to pick the one for the version of CM you are choosing) http://wiki.cyanogenmod.org/w/Google_Apps
To push the files to your phone, simply boot your phone in the stock ROM, connect it to your PC with usb, and make sure the USB connection notification is set to USB mass storage. You can then copy the ROM files in zip form to the root directory of the drive letter of the phone from your PC just like you'd copy to a USB stick. Change the USB notification/communication mode on the phone back to stock setting of motorola phone app afterwards, as this dismounts the internal SDCARD storage and the phone wont remount it until you do.
This is out of order from some of the other guides. The reason to place the ROM files first before anything else, is so you can install clockworkmod to make recovery possible, then go right into it and install the ROMs from recovery mode. I had some issue with installing recovery with CWM first, then CWM not working if the phone booted into the stock rom (looks like the recovery was overwritten. I simply had to have the ROM files ready to go then do CWM all at once to make this work.
#5) Install CWM clockworkmod. (http://wiki.cyanogenmod.org/w/Install_CM_for_olympus#Installing_recovery_using_fastboot)
Follow the steps under installing recovery under fastboot. A link is provided for the latest CWM 5.0.2.0, which is what I used instead of the 4.0 version included in the unlock bootloader script mentioned in MY step 2.
At step 7, my phone appeared to hang at Flash boot: SOS. Some other users reported this as well. I just let the phone sit there for 3-5 minutes to make sure it was done with the operation. I then manually rebooted the phone holding down volume down button and holding power button until the phone powered down. If the phone is still connected to the PC, it will automatically power back on, so continue to hold the volume down until fastboot appears, then tapped volume down to cycle through the menu and chose Android recovery from the boot menu and press volume UP to execute it. CWM loaded up just fine and I was able to choose recovery ROMs we pushed in step #3 of my guide there and reboot.
Sorry if this is not as detailed as it could be, but I wrote this a bit after the fact without taking screenshots or writing down every step of the way. This is my best recollection of what I went through and figured I'd share as many consider this a gamble with the Atrix 4g and ATT 4.5.145.
Overall experience with the CM 7.2 ROM:
I've been running the phone for a bit now with cryogenmod 7.2 without issue. The battery life is fanastic and there are many nifty options included with CM 7.2 I have not experienced the random reboots or overheating some others have mentioned.
The only issues I've ran into so far, the latest youtube app from google store does not seem to play videos. You can install a QR code scanner app from google play store of your choice, then download the youtube app that worked for me via QR code from http://forum.xda-developers.com/showthread.php?p=18157961#post18157961
Additionally, internal storage (what's considered the SDCARD on this phone) was not mounted by default in CM 7.2. Reference this to fix it. http://forum.xda-developers.com/showthread.php?t=1481252
I hope this helps users out there with old Atrix 4g's considering giving them new life. I'm going to try CM 10.x soon to see how jellybean runs on the Atrix 4g. Wish me luck!
Vengaence
Vengaence said:
I have an Atrix 4g that was about to be retired or sold, and decided to instead make it an android project to learn about modding and possibly make something useful out of an old device.
After combing the forums on this site and others, realized there was some risk involved of a hard brick, but since this is not my main phone anymore, I wasnt too worried about. I'll share the results...
The phone was running gingerbread 2.3.6, ATT 4.5.145 build
#1) Root phone (http://forum.xda-developers.com/showthread.php?t=1769497)
Step 10 did generate an error for me, I had to issue the alternate command and it worked fine.
I downloaded root checker by JOEYKRIM on google play store to ensure it was rooted properly afterwards.
#2) Backup the phone in case of trouble (I used titanium backup from google play store, requires rooting from step 1)
Add a schedule to backup all and execute the schedule now. Pretty easy stuff
#3) Unlock bootloader (http://forum.xda-developers.com/show....php?t=1182871)
This is probably the most dangerous step. I used the link above and would like to add a few comments. The link above is a script written to automate the process for those not terribly familiar with the android tools ADB and fastboot. This script is capable of unlocking your bootloader, fixing some common problems that happen along the way, and installing clockworkmod so you can access android recovery mode to install custom ROMs. However, it seems to come with an older version of the clockworkmod, therefore I used it for the bootloader only (option 1 from main menu). I also had to execute option 3 afterwards as I did get the failure to boot 0x1000 error. Long story short.. I used option 1, then option 3 and skip the rest.
#4) PUSH ROM files of your choice to phone (I used Cryogenmod 7.2 latest from http://download.cyanogenmod.org/?device=olympus)
You should also copy any other addon ROMs of your choice to the phone at this time as well. Google store app is one that is not included with CM 7.2 and you can get here (make sure to pick the one for the version of CM you are choosing) http://wiki.cyanogenmod.org/w/Google_Apps
To push the files to your phone, simply boot your phone in the stock ROM, connect it to your PC with usb, and make sure the USB connection notification is set to USB mass storage. You can then copy the ROM files in zip form to the root directory of the drive letter of the phone from your PC just like you'd copy to a USB stick. Change the USB notification/communication mode on the phone back to stock setting of motorola phone app afterwards, as this dismounts the internal SDCARD storage and the phone wont remount it until you do.
This is out of order from some of the other guides. The reason to place the ROM files first before anything else, is so you can install clockworkmod to make recovery possible, then go right into it and install the ROMs from recovery mode. I had some issue with installing recovery with CWM first, then CWM not working if the phone booted into the stock rom (looks like the recovery was overwritten. I simply had to have the ROM files ready to go then do CWM all at once to make this work.
#5) Install CWM clockworkmod. (http://wiki.cyanogenmod.org/w/Install_CM_for_olympus#Installing_recovery_using_fastboot)
Follow the steps under installing recovery under fastboot. A link is provided for the latest CWM 5.0.2.0, which is what I used instead of the 4.0 version included in the unlock bootloader script mentioned in MY step 2.
At step 7, my phone appeared to hang at Flash boot: SOS. Some other users reported this as well. I just let the phone sit there for 3-5 minutes to make sure it was done with the operation. I then manually rebooted the phone holding down volume down button and holding power button until the phone powered down. If the phone is still connected to the PC, it will automatically power back on, so continue to hold the volume down until fastboot appears, then tapped volume down to cycle through the menu and chose Android recovery from the boot menu and press volume UP to execute it. CWM loaded up just fine and I was able to choose recovery ROMs we pushed in step #3 of my guide there and reboot.
Sorry if this is not as detailed as it could be, but I wrote this a bit after the fact without taking screenshots or writing down every step of the way. This is my best recollection of what I went through and figured I'd share as many consider this a gamble with the Atrix 4g and ATT 4.5.145.
Overall experience with the CM 7.2 ROM:
I've been running the phone for a bit now with cryogenmod 7.2 without issue. The battery life is fanastic and there are many nifty options included with CM 7.2 I have not experienced the random reboots or overheating some others have mentioned.
The only issues I've ran into so far, the latest youtube app from google store does not seem to play videos. You can install a QR code scanner app from google play store of your choice, then download the youtube app that worked for me via QR code from http://forum.xda-developers.com/showthread.php?p=18157961#post18157961
Additionally, internal storage (what's considered the SDCARD on this phone) was not mounted by default in CM 7.2. Reference this to fix it. http://forum.xda-developers.com/showthread.php?t=1481252
I hope this helps users out there with old Atrix 4g's considering giving them new life. I'm going to try CM 10.x soon to see how jellybean runs on the Atrix 4g. Wish me luck!
Vengaence
Click to expand...
Click to collapse
Cwm 5.0.2.7 is the up to date recovery (possibly outdated now, see new 4.3.1 for recovery (haven't tried it out yet))
Everything you just posted has already been mentioned over several threads over the past 3 yrs. We all are well aware of these instructions, long before you essentially copied, pasted, and edited into your own words, that detail the process of rooting, unlocking the bootloader, flashing a custom recovery, and flashing a custom ROM.
Sent from my MB886 using xda app-developers app
palmbeach05 said:
Cwm 5.0.2.7 is the up to date recovery (possibly outdated now, see new 4.3.1 for recovery (haven't tried it out yet))
Everything you just posted has already been mentioned over several threads over the past 3 yrs. We all are well aware of these instructions, long before you essentially copied, pasted, and edited into your own words, that detail the process of rooting, unlocking the bootloader, flashing a custom recovery, and flashing a custom ROM.
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
The tone of your response implies that I'm trying to take some sort of credit for other people's work. The reason I posted is I've noticed some folks fairly recently with doubts about this process working specifically with this exact phone and ATT 4.5.145, and I wanted to share my experience and encourage others to do it if they were on the fence. I appreciate the work of this forum and other folks who have poured hours of time into these custom projects to make the android experience better.
I notice that you are a senior member. I'd suggest that replies are restricted on this forum to constructive responses, and not negative ones.
Thank you!
Vengaence said:
The tone of your response implies that I'm trying to take some sort of credit for other people's work. The reason I posted is I've noticed some folks fairly recently with doubts about this process working specifically with this exact phone and ATT 4.5.145, and I wanted to share my experience and encourage others to do it if they were on the fence. I appreciate the work of this forum and other folks who have poured hours of time into these custom projects to make the android experience better.
I notice that you are a senior member. I'd suggest that replies are restricted on this forum to constructive responses, and not negative ones.
Thank you!
Click to expand...
Click to collapse
Actually it was more along the lines of you were repeating things that have been said already time and time again. That was the true meaning of my post. I do apologize if it may not have been conveyed in a manner that my intention clear.
Also, the recovery. I just flashed the new one from the new 4.3.1 thread. It is indeed an update, bringing it up to revision 6.0.4.6. This is a huge step forward and lays the groundwork for 4.4 (most kk roms require at a minimum cwm 6.0.4.4)
Sent from my MB886 using xda app-developers app
CWM versions for Atrix 4g
palmbeach05 said:
Actually it was more along the lines of you were repeating things that have been said already time and time again. That was the true meaning of my post. I do apologize if it may not have been conveyed in a manner that my intention clear.
Also, the recovery. I just flashed the new one from the new 4.3.1 thread. It is indeed an update, bringing it up to revision 6.0.4.6. This is a huge step forward and lays the groundwork for 4.4 (most kk roms require at a minimum cwm 6.0.4.4)
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------------------
I notice you have an MB886, Atrix HD according to your signature. This thread is for the Atrix 4G. I'm not sure if you realized this. Maybe that is the reason why we are not seeing eye to eye. The Atrix 4g is older and is quirky and there have been many horror stories. I havn't seen many of those stories with the Atrix HD and things are more straight forward.
According to http://www.clockworkmod.com/rommanager
the latest CWM for the Atrix 4G is 5.0.2.0 and that's what is used by http://forum.xda-developers.com/showthread.php?t=2613829
as well to install later versions of CM such as 10.2 on the Atrix 4g. It's also what I used for CM 7.2
On your Atrix HD, CWM 6.0.4.x should be used.
Vengaence
Vengaence said:
--------------------------------------------------------------------------------------------------------------------------------
I notice you have an MB886, Atrix HD according to your signature. This thread is for the Atrix 4G. I'm not sure if you realized this. Maybe that is the reason why we are not seeing eye to eye. The Atrix 4g is older and is quirky and there have been many horror stories. I havn't seen many of those stories with the Atrix HD and things are more straight forward.
According to http://www.clockworkmod.com/rommanager
the latest CWM for the Atrix 4G is 5.0.2.0 and that's what is used by http://forum.xda-developers.com/showthread.php?t=2613829
as well to install later versions of CM such as 10.2 on the Atrix 4g. It's also what I used for CM 7.2
On your Atrix HD, CWM 6.0.4.x should be used.
Vengaence
Click to expand...
Click to collapse
Ah, correct and incorrect my friend. While my signature may point out what device i am currently on, it does not reflect my past. A peice of supporting evidence is over in AtrICS v2.0 (see home button fix)
As far as cwm goes, cwm has unofficial builds as well. Look through one of the threads, it will point you to a link about recoveries and there does exist a 5.0.2.8. EDIT It was Romracer's recovery, accesed through the unlock bootloadrr thread a few threads down from this one. The 5.0.8.x i think was more like a 5.8.1.8, but i think that was a touch version? Now CM and the other threads may say the 5.x is ok for all of our roms, but as android moves forward, so must our support from libs, apps, kernels, scripts, and of course, recoveries. That is why i promoted the 6.0.4.6 revision both here and in the new 4.3.1 thread.
Sent from my MB886 using xda app-developers app
I recently received Acer Iconia A500 with stock 4.0.3 ROM (unrooted). I'd like to have root, flash recovery (prefer TWRP-like recoveries) and custom ROM (OmniROM 5.1.1 to get apps like MS Office/Word which 4.0.3 does not support). I've done a lot of background research on this matter but I'm really lost. There seem to be so many different methods of achieving this and none of them are written so that an unexperienced person (and I flash recoveries and custom ROMs many times a week to my Samsung phones) could completely understand what they do. There seem to be other problems as well such as dead links to installation files or executables that are problematic in Win8/10 environments (giving errors like 'install .NET 2.0 framework').
So here's what I currently understand. I get that I first need to root the A500 and that many rooting methods also unlock the bootloader (those are not familiar to me) and add an older recovery which then can be used to flash a newer recovery (with which I can flash ROM and GAPPS zips). I'vet got my ACER CPUID (used ES Explorer app to find it) and my SBK. I've copied zips and MD5s of OmniROM 5.1.1 V11 ROM, its GAPPS and TWRP based recovery REV2.0 beta4 to a MicroSD card which is inside the A500. I've got USB Debugging (and unknown sources) on.
Could someone please give me a good step-by-step guide with working links which describes how can I get from the current state of A500 (stock 4.0.3, unrooted, factory reset made) to the point where I can start flashing zips of recoveries and ROMs (which I know how to do)? I realize that this is an older device but for someone who has spent many hours within the last few days browsing XDA, Tegraforums and other places for information, there seem to be many A500-owners who still in 2015 are doing their first rooting and flashing experiments.
Please help!
I am in the same boat, totally overwhelmed by the information in many different places. My A500 is on 4.0.3 also.
So if someone would help US....I'd really appreciate it.
rampart51 said:
I am in the same boat, totally overwhelmed by the information in many different places. My A500 is on 4.0.3 also.
So if someone would help US....I'd really appreciate it.
Click to expand...
Click to collapse
you folks are all TEGRA OWNERS right? You should definitely check there instead...
Sent from my SM-G900V using Tapatalk
You can follow this which i wrote in other forum:
For basic step, follow if you are coming from stock. Make sure you flash all as mentioned in below forum
http://forum.tegraowners.com/viewtopic.php?f=9&t=363
In that forum, step2,
you can use Touchrecovery mentioned there or from: http://forum.tegraowners.com/viewtopic.php?f=8&t=1490
Also, for latest ROM, use the rom from first post of this forum.
Make sure you have Root access on tab, as well as you check MD5 sum for all file you flush it on the source from where you flush it. Usually, you put your files on microSD so check MD5 sum on MicroSD file.. (if you don't know how to, google it)
Basically, it is boiling down to below steps:
1. you need to root your device.
2. go to your existing recovery and install TWRP recovery. (http://forum.tegraowners.com/viewtopic.php?f=8&t=1490)
3. Once you install, go back to new recovery
4. tap on Partition Format
5. Tap on Storage. (Screen has only one big button)
6. Select Data from left side.
7. Select f2fs from right side.
This will format all your existing data. You will lose everything that you have.
8. Do same for Cache.
9. Reboot back in recovery to make sure that both partitions are formatted as intended.
10. Go back to main menu in recovery
11. Install ROM
12. Install GAAP.
13. Reboot.
14. Thank Thor.
Click to expand...
Click to collapse
I managed to get a Vista laptop so I've been able to get pass the compatibility issues with my Win10 PCs. However, I'm still a little unsure what to do. Could someone please clarify this for me? Can I use the quoted guide to get my A500 4.0.3 unrooted tablet rooted and with a recovery I can use to flash TouchRecovery, OmniROM and GAPPS zips? More specifically, does Step 1 work with 4.0.3 unrooted:
I wanted to write a consolidated tutorial for people on the latest/unrooted 3.2.1 OTA and how to flash it to rooted Jelly Bean ROM. If you follow step 1, it actually installs an old version of Touch Recovery for you, so you do not need to bother with Acer Recovery Installer. All links are derived from the FAQ stickied thread.
1. First you need to obtain root. Follow this guide to install a rooted 3.2.1 image.
[tab=30]All data will be lost. The 10 step guide is included as a PDF in the download:
[tab=30] http://forum.xda-developers.com/showthread.php?t=1307539
[tab=30]Confirm you have the Superuser app installed once completed.
Click to expand...
Click to collapse
I also found this piece of information from XDA:
Its an old thread used to upgrade you to rooted 3.2.1 -
It can also be used to downgrade/rollback/reset partition table - from ICS BUT there's a slight difference in the steps you need to take to do that...and alot of folks have come to grief here - so for the downgrade -
after running the "test.cmd" which checks the right drivers are installed correctly - run dotnetdetector.exe - follow the instructions UNTIL
You see a window asking you to connect your usb cable and that the EUU will check you "image versions" If you are downgrading DO NOT connect your cable!!!
This will "force" the "cannot detect your Iconia" window and then give instructions to put your tab into "manual apx mode" - once you have done that you can connect your cable - enter your cpuid - then you'll see the green status bar and the "update" will begin - it should take no longer than 10 minutes -
Click to expand...
Click to collapse
So which is it? Do I follow the 3.2.1 OTA method as is or do I take into consideration the alternative step to downgrade? Or does the method even work for A500 4.0.3 unrooted?
Some of you may have seen my post in the Original Shield Tablet MM 4.0 Update thread, but now I'm finally making a new thread for these to help people out.
DISCLAIMER: I'm not responsible for your tablet. You own it, be smart about what you do with it. Not my problem if you screw something up.
This is an all-in-one MM update for the specific version of your Shield (select the right link at the bottom).
If you have already used my first zip, this will remote TegraOTA and upgrade TWRP to 3.0.
If you're already on MM, rooted, removed TegraOTA, and on TWRP 3.0, this won't add anything.
What does this contain?
Stock Rooted MM - Full Nvidia Update
TWRP 3.0.0 (thanks to @romracer)
TegraOTA Removed (Nobody needs that nonsense anyway)
SuperSU
What does this not contain?
Anything else - Read: Stock. Rooted.
What's broken?
OTA. You won't get any OTA updates (You don't want them if you're rooted anyway)
What do I need to do?
Be Unlocked
Have TWRP installed
Drop correct zip to device, then flash (if you need me to explain this, you shouldn't be doing it)
You CAN dirty flash this and not wipe /data partition (except the RoW LTE if flashing on a US LTE tab).
You also need to have a little patience. First boot takes some time. Chill. It's not hanging.
IGNORE the message in TWRP stating that the device isn't rooted. It is. TWRP just doesn't believe me. IGNORE IT.
Links Below:
(Be sure to download the one that you need. Not my problem if you can't handle that yourself.)
**RoW means Rest of World. Not my terminology, but that's what you use if you have anything other than a US tablet**
US WiFi Shield Tablet: Temporarily Removed
RoW WiFi Shield Tablet: Temporarily Removed
Flashing RoW LTE on US LTE tablet will cause you to be missing some buttons. Follow the instructions below to get them back.
RoW LTE Shield Tablet: Temporarily Removed
For US LTE on RoW LTE rom:
* Flash the rom
* Reboot to system
* Connect to PC (or maybe open Terminal Emulator if you have it installed)
* Run the following in adb if on PC
Code:
adb shell am start -n com.google.android.setupwizard/.SetupWizardTestActivity
* Do what you can, reboot, and finish if it fails or crashes on the first attempt.
* Reboot
Thanks to @bill0405 for button fix when using the RoW LTE rom on a US LTE device.
**Note: I put this in General instead of Dev, because I didn't really do any dev work. Just some scripting to have it flash the way I want and do what I want.
I'll add International WiFi in a bit. I'm going to be downloading it when I get home. :highfive:
Hello, I haven't looked in your other threads but will these files automatically install the MM firmware?? Or will I need to do that separately??
Thanks.
Mojar7070 said:
Hello, I haven't looked in your other threads but will these files automatically install the MM firmware?? Or will I need to do that separately??
Click to expand...
Click to collapse
All-in-one install. No need to flash anything else. Just need to be unlocked and running TWRP recovery.
RoW WiFi model is added.
Install went well, thank you.
Just a heads up, first boot will take some time. There are no boot animations. Just the stock Nvidia splash screen. It will look like the boot hangs on the splash screen but be patient, it will get to the set up screen with time.
Edit: All is working well. Multi window option is not present on dev option, will modify in build prop. Thanks again.
Are any of these safe to install on a US LTE model? I never have and never will use the LTE modem, so it doesn't matter to me if it doesn't work as long as everything else does.
I heard the RoW LTE works fine on the US LTE and connects to Tmobile... I'm going to try it out now.
Awe, man. I was all excited and then I was ready and thought I'd boot into fastboot and...Ugh, I am still locked. If I just flash this it won't work right? Should I just unlock and then push everything over or is there a better way now? I am on 5.1.1 LP rooted with TWRP. Thanks for your help.
I'm currently on stock rooted 5.1.1, with TWRP installed, and Bit-O-Kernel. If I install this 6.0 update, will it wipe my tablet? I'm really not up for reinstalling and setting up everything all over again right now... I know I'll lose the kernel during the install, I'm ok with that as it's an easy quick reinstall.
That's what nandroids are for.
bluegizmo83 said:
I'm currently on stock rooted 5.1.1, with TWRP installed, and Bit-O-Kernel. If I install this 6.0 update, will it wipe my tablet? I'm really not up for reinstalling and setting up everything all over again right now... I know I'll lose the kernel during the install, I'm ok with that as it's an easy quick reinstall.
Click to expand...
Click to collapse
Dirty flash is fine. Just make sure the kernel you want to use supports M.
Installation worked but weird things happening.
This flashed perfectly on my US Wifi coming from a rooted stock LP.
TWRP 3.0.0 is very sluggish and behaves strangely. Also, trying to flash Xposed framework results in errors regarding "read only" even though the Mount System As Read Only option is unchecked.
I've tried all day to figure out a solution but I've found nothing.
As anyone else ran into these issues.
2kool2Bcruel said:
Also, trying to flash Xposed framework results in errors regarding "read only" even though the Mount System As Read Only option is unchecked.
Click to expand...
Click to collapse
What zip are you using to flash xposed? I bet I can fix the issue.
Any word from anyone who flashed one of these onto a US LTE model? Also, why isn't there a US LTE version available?
great stuff Harfainx, I was lazy so just sideloaded over the top of LP - worked an absolute charm :good:
Is it safe for OG tablet? Anyone confirm it's working without be killed.
Sent from my SHIELD Tablet using Tapatalk
I flashed the LP stock rooted and I was still locked. Can I flash this MM stock rooted and not be unlocked? Just was hoping I didn't have to unlock and loose everything and start over.
quangv said:
Is it safe for OG tablet? Anyone confirm it's working without be killed.
Sent from my SHIELD Tablet using Tapatalk
Click to expand...
Click to collapse
Yes, working good on OG shield. Been for 2 days now, still functional.
Device doesn't seem to be rooted? I downloaded SuperSU, but it complains. Is there a better binary?
So let me put in a disclaimer that I am a complete novice when it comes to rooting, installing and using custom recovery, and installing custom ROMs, but nothing ventured, nothing gained so I thought I'd give it a go.
I have a Samsung Galaxy S5 SM-G900i running Android Lollipop 5.0, and I absolutely detest the stock OS with all its bloatware. So I was looking into installing the custom PAC ROM for it. After what I presumably thought was enough research into how to perform a root of the device, how to install the custom recovery and finally install the custom ROM, I set off on my journey to begin rooting, it couldn't be that hard right? How wrong I was.
Downloading the latest version of Odin for my particular device, and installing the latest Samsung Drivers was a breeze. I followed the tutorial for rooting the Galaxy S5 , although the UI of Odin differed slightly to what was described. I made my way through it, doubly making sure to not have Re-Partition checked. It installed, or "flashed", if I'm using the term correctly, very quickly. I booted up my device and found the SuperSu app installed. Opening the app, the tutorial says I should have received a prompt to do an update, one which I did not receive. I closed down the app, opened it again, once again no prompt, so I rebooted the device. After several reboots, I googled the issue and found I should try a manual install of SuperSu using the .apk from the ChainFire website. I did as instructed, and the next time SuperSu was opened the update prompt appeared. So I proceeded to follow the steps of the tutorial again, until I was not prompted to disable KNOX. Once again after google searches, I found that this was probably not a big deal, and I could still grant root permissions so I continued on. I've also performed a root check with Root Checker, which has assured me that my device is rooted successfully.
Next I installed TWRP, it went without any relative hitches. But after trying to create a NANDbackup, which everywhere tells me I should do before trying to flash custom ROMs, my microSD card will no longer allow me to write to it from Windows. All attempts result in "Cannot copy item - The device has either stopped responding or been removed", I've formatted the microSD card, I've unmounted and mounted it again. But I can still not write to it via Windows. I'm trying to copy the two .zip files for the PAC ROM and GApps, onto it so I can install from there. But no luck.
I apologise if this post seems long winded, I just wanted as much information in here as possible so that I could get some assistance in fixing my issue, as well as anyone that also has any similar issues can find this as descriptive as possible.
Rooting sm-g900i
Hi thanks for the thread i hope you get your answer, another way is to kind of chat with one of the senior XDA members. i think i'm much more new to this android rooting technology and am hoping to follow in your footsteps (without your current issue). could you pls give a NOOB some sound advise to what i need to do. i would like to go the ODIN way as i want to learn that program, but now there s that "oneclickroot" with the .APK file. which way do you think i should follow. Also what other preperations do i need to take eg NANObackup, remove bootloader(?) etc.
thanks for your time
I'm having trouble finding the answers and, I must apologize, the search function shows me everything EXCEPT what I am looking for...
I'm trying to get Jasmine to work, but I am having trouble. I bought a spare Note 3 on 4.4.2 NC4, rooted, unlocked the bootloader, installed TWRP, and installed lk_hltevzw-v6.4.zip (wiped everything (data, cashe, delvac, etc.)before and after the install). Installed via TWRP. I wanted to try the changes and figured I'd deal with the modem later if need be. I rebooted and everything appears to be just like a stock rom. What am I missing?
paramax55 said:
I'm having trouble finding the answers and, I must apologize, the search function shows me everything EXCEPT what I am looking for...
I'm trying to get Jasmine to work, but I am having trouble. I bought a spare Note 3 on 4.4.2 NC4, rooted, unlocked the bootloader, installed TWRP, and installed lk_hltevzw-v6.4.zip (wiped everything (data, cashe, delvac, etc.)before and after the install). Installed via TWRP. I wanted to try the changes and figured I'd deal with the modem later if need be. I rebooted and everything appears to be just like a stock rom. What am I missing?
Click to expand...
Click to collapse
By "trouble" do you mean "unmet expectations", or something else? Usually "trouble" indicates broken functionality, an inability to reproduce instructions because of a departure from expected behavior. From what you reported, I don't see any indications of "trouble installing".
The original series of Jasmine ROMs for retail devices had to live within the constraints of using a stock, signed Samsung boot image (kernel+DTB+ramdisk). And so they were a "heavily modified stock" (framework changes, different pre-installed apps, etc). The developer editions had a little more flexibility in that a custom kernel / recovery could be flashed, but the "ROM" (i.e. /system partition) - which is 95% of the user experience - was essentially the same between the two. Which is to say... stock derived, not a port from something else.
Not sure if that helps; refine your question if need be.
I guess by "trouble" I would mean that everything appeared to go as expected during the install process, but I see no evidence of there being a change to the phone. It is still on KitKat and the "about phone" page shows exactly the same items as the unmodified phone.
So what should I expect? I followed the instructions for installing the rom so I expected to find some evidence somewhere. Every time I had installed a rom in the past, it sure had different functionality than stock.
You know, I just looked at your OP again, and I notice that you ONLY mentioned
lk_hltevzw-v6.4.zip
and nothing else besides that.
If that was the only thing that you flashed, and nothing but that, then all you flashed was a boot image and the ROM ( /system image) would indeed look identical... because it is identical.
I just assumed that you followed the instructions in the Jasmine thread and had also flashed the ROM as well.
Well, step 1 under "developer edition" says to flash the file that I listed, then the modem, then other things if you use them. Then there is a big warning about NOT flashing the retail firmware. What was I supposed to flash before step 1? Any other instructions are for retail edition...
Quote:
FOR DEVELOPER EDITION:
FLASH*lk_hltevzw-v6.4.zip*in recovery
FLASH*N900VVRUEOF1*modem*viaOdin
UPDATE*Play Movies &*INSTALLNetflix v1.8.1, if you use them.
DO NOT FLASH RETAIL FIRMWARE, IT WILL LOCK YOUR DEVICE !
@paramax55
You didn't flash the ROM, that's why it looks identical. LOL. The only thing you flashed was the boot image.
If you look at the instructions at
https://forum.xda-developers.com/showpost.php?p=62769340&postcount=11940
You'll see there are *three* parts:
part1, everbody do this
part2 locked retail devices
part3 DE devices (and now also unlocked bootloader devices which are essentially DE devices)
You only did part 3
That's just what I needed! I didn't even have to mess with the modem. Thanks!