Database Users

Un-rooting a rooted N1?

So I bought a N1 yesterday, cant wait till it gets here, The phone is rooted and has 2.2 on it, Is there anyway I can un root it and just be at the latest stock android? I just prefer to be at the normal stock updates, never really been big into rooting and ROMS etc unless I have too, anyway so yea thats my question and is it difficult?
Thanks in advance!

Take a look in the Development board, there is a sticky that shows you how to restore stock 2.1. Then it will prompt you to upgrade to Froyo.

solidkevin said:
So I bought a N1 yesterday, cant wait till it gets here, The phone is rooted and has 2.2 on it, Is there anyway I can un root it and just be at the latest stock android? I just prefer to be at the normal stock updates, never really been big into rooting and ROMS etc unless I have too, anyway so yea thats my question and is it difficult?
Thanks in advance!
Click to expand...
Click to collapse
Yeah, you can't re-lock the bootloader, but you can load up the stock ROM as the post above says. But since it's all already done, you might consider looking into a ROM which fits you. There are several which are "almost stock" but have nice enhancements, like the Enom rom.
I too am an unrooted stock ROM kinda guy, I don't have the time or patience to deal with fiddly stuff on my phone anymore, as I need to pull it out, see where my next meeting is, and get there. Not pull it out and realize it's in a Standby of Death or some other random problem. There are pluses and minuses to using a non-stock ROM, weigh them.. I'm starting to myself... I want a black notification bar and a handful of other small things, but to get them it requires a lot of work (unlock, flash new rom, set up all of my apps again, figure out new stuff in ROM, etc..)

Yeah you could also use modaco ROM. Those are stock ROMs with a few extras like super user access, which is a must have. Etc.

Is rooting similar or at least easy like the HD2? I had one of those and putting Custom ROMS was so simple!

Should be fairly simple if cyanogen is on it.
Sent from my Nexus One using XDA App at 35000 feet

uberamd said:
Take a look in the Development board, there is a sticky that shows you how to restore stock 2.1. Then it will prompt you to upgrade to Froyo.
Click to expand...
Click to collapse
Can you please link the thread, Ive looked and looked and I cant find a unrooting tutorial.

Nexus One Android Development -> Original Shipping - Tutotrial
The thread is stuck right at the top of the forum -_-

GldRush98 said:
Nexus One Android Development -> Original Shipping - Tutotrial
The thread is stuck right at the top of the forum -_-
Click to expand...
Click to collapse
WOW....I feel dumb....thanks lol

I am assuming you know how to use ADB and Fastboot
Hmm, Is there a thread explaining those 2 things?

solidkevin said:
I am assuming you know how to use ADB and Fastboot
Hmm, Is there a thread explaining those 2 things?
Click to expand...
Click to collapse
If all you want to do is flash stock rom, you don't even need to know what those two are. The stickied tutorials are dead simple.

Can somoene confirm Im gonna be doing this correctly.
Step 1. Disable backup my settings under privacy settings.
Step 2. unzip the original shipping ROM and put it somewhere you can find.
Step 3. Plug in Nexus One with USB to computer (enable usb and debug modes)
Step 4. adb reboot bootloader (which will boot into the bootloader)
Step 5. Confirm fastboot connection fastboot devices
Step 6*. fastboot erase userdata
Step 7*. fastboot erase cache
*If step 6 and 7 does not work, and if you have Amon_RA's recovery installed, you can do a factory data wipe from there.
Alternately, you can also do a factory data wipe within Android. Settings => Privacy Settings => Factory Data Reset.
Thanks to Brian and setzer715.
Step 8. Go to the directory that you stored your unzipped files.
Step 9. fastboot flash userdata userdata.img
Step 10. fastboot flash boot boot.img
Step 11. fastboot flash system system.img
Step 12. Skip to step 13 if you want to keep recovery (assuming you have a modified recovery such as Amon_RA's recovery). If not fastboot flash recovery recovery.img
Step 13. fastboot reboot
Step 14. After the system boots up and while setting up skip setting up with the google account and you can setup accounts later. This will prevent the phone from pulling down the previous settings (downloaded apps, wallpaper etc) from google.
Step 15. You are done. Enjoy.
Ok so I downloaded, installed and updated Android SDK, it seems to be all set, now when I follow those steps, I connect the phone first then for instance step 4 I should start "adb" then type in reboot bootloader, and for step 5 I should start up "fastboot" then type devices, etc etc? Is that correct?
thanks in advance.

Anyone? Please.

solidkevin said:
Anyone? Please.
Click to expand...
Click to collapse
look here to learn how to setup adb
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/

[3g STOCK .IMG] VZ WIRELESS MX600 5/3/2011

Here are the .IMG files that Motorola has posted on their MOTODEV site. .
ATTENTION: DO NOT ATTEMPT TO FLASH THIS FILE ON ANYTHING BUT THE VERIZON WIRELESS MOTOROLA XOOM Z600 (3G MODEL) OR YOU WILL HAVE A SHINEY PAPER WEIGHT!!!!
These files are from Motorola's Development site but I take no liability with anything that happens with your device if something goes wrong.
Official HRI39 Motorola .IMG files:
http://www.multiupload.com/9XP1B8LSWC
Official HRI66 Motorola .IMG files:
http://www.multiupload.com/POUDJY1255
The following are the steps from the MOTODEV site
1. Extract files into android sdk /tools folder.
2. Start command prompt/ terminal from the android sdk tools folder. (How this is done on Mac I do not know, Windows: shift+left click and select "open command window here")
3. adb reboot bootloader
4. fastboot flash boot boot.img
5. fastboot flash system system.img
6. fastboot flash recovery recovery.img
7. fastboot flash userdata userdata.img
8. fastboot erase cache
9. fastboot oem lock
The device will lock and reboot.
You are now back to out of box state. However I do not know if it is still detectable by VZ Moto if you have unlocked the device after doing this.
Also fyi the sbf file is still an option but you will have to go in and do the fastboot oem lock after it completes

u mispelled cache

Fixed. Thanks had a long day and missed that at proof reading

Thanks for the files, does seem a lot simpler to just use the sbf file though.

bwcorvus said:
Thanks for the files, does seem a lot simpler to just use the sbf file though.
Click to expand...
Click to collapse
Its always good to have more options and the Xoom gives us many and hopefully soon sdcard support will provide the final key piece, the CM recovery!
In the meantime it is very good to have all of the official files at our disposal.
If anyone is wondering what the the reflash file from the first leak is, it is an SBF format installation of the stock boot image and a blank user data image to wipe data and return to stock via RSD Lite without touching the system partition.
This provides yet another way to reset that should be examined, especially if it works over a modified system partition.
We also may be able to use any or all of these files to build our own SBF files and other one step solutions for recovering and or modifying the Xoom. This can be very valuable and must also be thoroughly explored along with the NVM so we can really start to tak better control of the radio functions.
Lots to look at...

I am in love with fastboot. I am so use to the days of the OG Droid where the bootloader wasnt locked but you didnt have fastboot as an option. I can see a lot of easier days in the Dev community coming.

jmc2543 said:
I am in love with fastboot. I am so use to the days of the OG Droid where the bootloader wasnt locked but you didnt have fastboot as an option. I can see a lot of easier days in the Dev community coming.
Click to expand...
Click to collapse
Yea having these images is one BIG step...now we just need sdcards

Just finished doing this. I'm back at stock. Of course no I'll b the last to get an update. And by the same time tomorrow I'll be unlocking and re-rooting.

by doing this does it erase everything on your xoom?

bishop72 said:
by doing this does it erase everything on your xoom?
Click to expand...
Click to collapse
Yes it would. Itll bring it back to what it was like when you first bought it.

For those that updated, were you able to reroot?

17akota said:
Yes it would. Itll bring it back to what it was like when you first bought it.
Click to expand...
Click to collapse
I saw multiple threads about Titanium backup not working with the Xoom. Are there alternative apps that will save all my configuration like home screen layout etc? It was a lot of work B-)
Sent from my Xoom using Tapatalk

It is just Android 3.0
3.0.1 is HRI66

Do I need to do this if I have rooted, just unlocked? Can I just "fastboot oem lock" and be good to go?

Aaron636r said:
Do I need to do this if I have rooted, just unlocked? Can I just "fastboot oem lock" and be good to go?
Click to expand...
Click to collapse
Oh no. I did the "fastboot oem lock" and now I get "Failed image LNX 0x0002". Cant boot past Dual Core logo screen.

Ok, re-unlocking it fixed it.

Ok so we have the original flash so we can get the OTA thats great. And Moto confirmed on their forum they will upgrade devices that have been unlocked and rooted. If they cannot install the software they will ship it back with just the new hardware. Can't wait to see what people can really start doing now.

For those of you that are like me and hate having to using mega upload and crap to download things here is a direct link on my web server to the file released by Moto.
DMCA Noticed by Moto
This was taken directly from the Moto Dev site myself.
If you browse the directory, which I think I left on for this one... There is also the sbf archive and RSD there to download. If anyone needs a place to store some files let me know. I have unlimited storage and bandwidth. When some of the OG Droid releases came out I was pumping over 11GB a week in downloads with no issues. It's the least I can do to help the community.

I got to be honest I don't know what the hell i should do to get the update and what will cause me to either have a clean install or lose root

All reports so far indicate it will not break root and rooted users have been getting the notification. They are also probably doing a controlled rollout if you have not yet gotten the notification. My XOOM is at home right now which sucks I won't be able to get my hands on it for about 6 hours and see what I can all do.

Ok got a problem, it won't boot up

So tonight I decided I wanted Netflix so I decided to root.
I followed the steps in this thread here
http://forum.xda-developers.com/showthread.php?t=1125714
I have Windows 7 and everything was running perfectly fine until step
4b. (OPTIONAL) if you want clockwork mod recovery, then go ahead and double click cwm.bat [Follow STEP 6 to update CWM]
I double clicked cwm.bat and proceeded to step 6.
I downloaded 84411.zip and placed it on my micro sd and put it in the transformer.
Then I turned off the transformer pressed vol down and power until the writing writing came up. So then I pressed vol up and it stated
Booting recovery kernel image and will not change from this. Vol buttons don't do anything. If I turn it off and on again it just stays at the Eee PAD ASUS screen and never changes.
What do I do? This thing won't boot and I don't know how to fix it.
Any help is appreciated.
Thanks
Martin

go to the sticky thread about nv_flash unbricking. The same thing happened to me, and that unbricking method restored it back to 3.1

Make sure you have the boot.img and recovery.img in place before you start anything.
Start over with these files in place and you're golden.
You don't have to unbrick it. Just start over with the files in place.
sassafras

Or even better, use the prime 1.6 rom with nv_flash and you'll have the thing rooted at the same time. nv_flash allows you to overwrite the rom/kernel at one time with one button.

AustinMartin said:
Or even better, use the prime 1.6 rom with nv_flash and you'll have the thing rooted at the same time. nv_flash allows you to overwrite the rom/kernel at one time with one button.
Click to expand...
Click to collapse
This will work. But correct me if I'm wrong, but I believe the Prime contains a data.img which will overwrite your settings. If you want to keep them, just don't include the data.img in the working folder.
sassafras

I ran the NV flash from the sticky. The Dos window showed it was updating and then closed.
Now it won't turn on. No matter how long I hold the power button. I just tried plugging it into the wall for juice but nada. It won't turn on.

i had it too the tf is running but screen is off get prime 1.5 nvflash version put it in nvdir flash it and ghen update to 1.6 using recovery

proplayer44 said:
I ran the NV flash from the sticky. The Dos window showed it was updating and then closed.
Now it won't turn on. No matter how long I hold the power button. I just tried plugging it into the wall for juice but nada. It won't turn on.
Click to expand...
Click to collapse
You can't brick this thing, just start over and make sure all of the files are in place. 9/10 times it's because you forgot to put the boot.img or the system.img in the same folder as the .bat file.
sassafras

sassafras_ said:
You can't brick this thing, just start over and make sure all of the files are in place. 9/10 times it's because you forgot to put the boot.img or the system.img in the same folder as the .bat file.
sassafras
Click to expand...
Click to collapse
Just a couple thoughts, questions.
Where should I start over? Its already rooted right? So I just need to install Prime?
The instructions for installing say to leave the zip in tact. So I assume that means put the zip on the micro sd card right? Both the bootimg and system.img files are on the microsd. I'm not sure there is a .bat file in there though.
I'm confused.

sassafras_ said:
You can't brick this thing, just start over and make sure all of the files are in place. 9/10 times it's because you forgot to put the boot.img or the system.img in the same folder as the .bat file.
sassafras
Click to expand...
Click to collapse
Also I'm just not sure what you mean, just start over. It won't turn on. My only option is the nvflash and I did it again but the device is still stuck in black screen.
I'm quite lost here. I'm in IT industry so I understand instructions fine but some of your terms I don't understand exactly. I've never really grasped flashing a the rom and upidating the kernal or updating the cwm. I don't understand what each really is.
Regardless if someone can give me step by step instructions. I'm told to use NVflash to install Prime 1.5. But all the Prime instructions I see say to use CWM.
Can you provide Something similar to this
Step one, go to ______ this thread and download _______
Take the ____ file and the _____ file from _____ and place them in the _____
Now do this or that.
Keep in mind if your first instructions are to put files on the sd card and then hit volume up and power that won't help because it won't turn on.
At this point I'm completely stuck and really appreciate the help you can provide.

proplayer44 said:
Also I'm just not sure what you mean, just start over. It won't turn on. My only option is the nvflash and I did it again but the device is still stuck in black screen.
I'm quite lost here. I'm in IT industry so I understand instructions fine but some of your terms I don't understand exactly. I've never really grasped flashing a the rom and upidating the kernal or updating the cwm. I don't understand what each really is.
Regardless if someone can give me step by step instructions. I'm told to use NVflash to install Prime 1.5. But all the Prime instructions I see say to use CWM.
Can you provide Something similar to this
Step one, go to ______ this thread and download _______
Take the ____ file and the _____ file from _____ and place them in the _____
Now do this or that.
Keep in mind if your first instructions are to put files on the sd card and then hit volume up and power that won't help because it won't turn on.
At this point I'm completely stuck and really appreciate the help you can provide.
Click to expand...
Click to collapse
Do you need your settings at all? This means all your data.
If you don't then I'll write up a quick guide.
- Download NVFlash & .tar.bz2 of a ROM you want (not all ROMs have .tar.bz2s). If you can't pick download PRIME 1.4 .tar.bz2 in NVFlash OP thread
- Set the tablet in APX mode
- Set up the drivers if you haven't already while tablet is in APX.
- Extract .tar.bz2
- Cut the files extracted by the .tar.bz2 (boot.img,recovery.img,system.img) into /nvflash/
So you should see... the 3 files (boot.img,recovery.img,system.img) next to bootloader.bin,download.bat,download,sh.. etc etc
- Double click download.sh if you're using linux.
download.bat if you're using windows
- Watch magic happen in a black box.
- Grats. You have PRIME 1.4.
- Download a ROM you want and place it in /Removable/microSD/ (Your SD CARD.. you must have one)
- Flash it in Clockwork Recovery. Note, ROM manager is incompatible with the Transformer so don't use it.
- Flash it like any other ROM as you would on any other Android device.
- You're done.
Hit the thanks. Hope this helps.
And getting into Clockwork should be VOL DOWN + POWER then hit Volume up (or whatever it says on the screen).

My first problem
I cannot find a thread with this
Download NVFlash & .tar.bz2 of a ROM you want (not all ROMs have .tar.bz2s). If you can't pick download PRIME 1.4 .tar.bz2 in NVFlash OP thread
I've searched and cannot find a link to 1.4 anywhere. I searched the form for terms prime and nvflash.
The 1.6 thread has no link to 1.4 but it does to 1.5.

Ok. I see your problem now. nv_flash is dangerous because it is a raw flash utility that will essentially wipe out anything on the flash unit of your device. The upside is that it's baked into the CPU so you can never lose the ability to NV_flash even if you completely bork the ROM.
First, download this: http://www.sdx-downloads.com/devs/roach2010/flash_roms/prime_v1.4.tar.bz2
This is the actual ROM image you will need.
Next, download this: http://www.filefactory.com/file/ccda97c/n/nvflash.zip
This is the nvflash utility for windows that will do the heavy lifting. It should also contain the apx drivers for your device.
Now:
Unzip the second zip somewhere that is easy to find.
Unzip the contents of the first zip into the same folder as the download.bat file from the second zip. There should be a boot.img and a system.img (and maybe more, I can't recall)
If your device is powered on, turn it off.
Plug your device in and simultaneously hold Power and Volume UP (this is sort of tricky, I know)
When the device shows up in windows, go to your device manager and manually install the drivers from the nvflash folder for the 'APX device that appeared' they will be in the usbpcdriver directory in that second zip.
With the APX drivers installed, run download.bat and wait. Your device should indicate that it is writing the partitions. When done it will turn off and reset.
Voila. You should be all better now.
sassafras

Awesome thanks.
Now when I use winrar to unzip the 1.4 it only has one file. System.img is that right?
Also I completed your steps already if that is correct, by reading the other responses. But now I'm stuck loading hc to it. I did do a wipe and now it is just continually rebooting. I put a clockwork zip file on the microsdcard as well as a Ultimate edition revenge as Iassumed thats what I need.
I need to boot to cwm and load hc to it right. What are those steps? Man I feel like a total noob. I think I'll make instructions for all this and request it be a sticky.
Edit, doing some research.
I don't know how important these instructions are with the advent of new technology, and ways to root but do I first need to complete Step 2 in this thread first?
http://forum.xda-developers.com/showthread.php?t=1106587

proplayer44 said:
Awesome thanks.
Now when I use winrar to unzip the 1.4 it only has one file. System.img is that right?
Also I completed your steps already if that is correct, by reading the other responses. But now I'm stuck loading hc to it. I did do a wipe and now it is just continually rebooting. I put a clockwork zip file on the microsdcard as well as a Ultimate edition revenge as Iassumed thats what I need.
I need to boot to cwm and load hc to it right. What are those steps? Man I feel like a total noob. I think I'll make instructions for all this and request it be a sticky.
Edit, doing some research.
I don't know how important these instructions are with the advent of new technology, and ways to root but do I first need to complete Step 2 in this thread first?
http://forum.xda-developers.com/showthread.php?t=1106587
Click to expand...
Click to collapse
No. The NV_Flash tool is so dangerous because it completely ignores the Android OS. You can literally flash anything you want with NV_Flash and no root or preparation in Android is possible or required.
The .zip that contains the system.img should also contain these two files:
http://dl.dropbox.com/u/10724980/nvflash/recovery.img
http://dl.dropbox.com/u/10724980/nvflash/boot.img
Put those along with system.img in the same folder as the nvflash file.
Also, make sure these two files are in that folder as well:
http://dl.dropbox.com/u/10724980/nvflash/flash.cfg
http://dl.dropbox.com/u/10724980/nvflash/transformer.bct
With all six of the files (the four I linked plus system.img and nvflash) run the download.bat file again with the transformer in apx mode.
sassafras

Awesome awesome awesome. That worked and was successful.
So then I put prime 1.6 on the card and successfully booted into CWM. YAAAAA!!!
I installed prime 1.6 successfully and choose to reboot. It then loaded on the eeepad screen with a blue bar going across. But now it just stays at the eee pad screen again. But I know I'm close because "powered by Nvidia Tegra" is back at the bottom.
So I must need to load something else here right to actually load hc?

proplayer44 said:
Awesome awesome awesome. That worked and was successful.
So then I put prime 1.6 on the card and successfully booted into CWM. YAAAAA!!!
I installed prime 1.6 successfully and choose to reboot. It then loaded on the eeepad screen with a blue bar going across. But now it just stays at the eee pad screen again. But I know I'm close because "powered by Nvidia Tegra" is back at the bottom.
So I must need to load something else here right to actually load hc?
Click to expand...
Click to collapse
haha. You fixed it then broke it again what a hopeless wreck.
Re-download 1.6 and check the MD5 against what is in the first post to make sure it's not corrupt then flash it again in recovery. Make sure you also wipe your dalvik-cache and cache before you try to boot.
sassafras

sassafras_ said:
haha. You fixed it then broke it again what a hopeless wreck.
Re-download 1.6 and check the MD5 against what is in the first post to make sure it's not corrupt then flash it again in recovery. Make sure you also wipe your dalvik-cache and cache before you try to boot.
sassafras
Click to expand...
Click to collapse
Ok I downloaded some MD5 check software and ran it and it compared the newest downloaded prime 1.6zip with the number in the prime 1.6 thread and they were the same. After reflashing 1.6 again I cleared both caches and rebooted but I'm still at the same spot. No boot.
When you first said I fixed it and rebroke it I thought, huh, because I tried to boot up after running the download.bat but it also stayed at the asus screen. I then installed the 1.6.
Now in the beginning, I'm talking about last night I went into the other linux option by not choosing volume up in the first 5 seconds and I accidentally choose the wipe option because my finger slipped on the volume toggle. Could that have something to do with it?

Maybe, but honestly, the point of the nvflash file is to wipe it fresh, even if you wiped it out entirely.
Maybe start again from APX mode with the 1.4 set of files (ensure that system.img is good. That's the real important one. Download it again just for good measure). Get it to boot in 1.4 first before you go trying any funny business.
sassafras

Working now, Thanks again.

How to fix/unbrick Motorola Xoom GUIDE

NOTE: THIS FOR WIFI ONLY MODEL XOOMS
For those of you who have managed to stuff up your android device like i have, and who have reached out to the community and received a set of vague comments barely outlining how to do something along the lines of fixing it from people who aren't really interested in helping you, this guide is for you. I've managed to fix my xoom by flashing a stock android 3.0 rom to it
For the sake of anyone who was in the same predicamant as me, the steps I took to fix it were:
1) Go to this link: http://developer.motorola.com/products/software/ link and download the US release (122 mb, down the bottom of first table). This is the stock release of android that my device was shipped with.
2) Unzip it and extract the contents (should be a set of .img files) to your android-sdk/tools folder (You will need the android SDK, fortunately, there are plenty of tutorials on how to obtain/install it, just search it in Google or right here on xda)
3) Put your xoom into fastboot mode (power on and during the motorola logo repeatedly press volume down until the menu appears in top left of screen, press volume down until you see fastboot, then press volume up, will show starting fastboot protocols)
4) Open a command window in your /tools directory (select tools folder and shift+right click and choose it from the menu that appears in windows)
5) Type the following: fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
6) Once that is done, type fastboot reboot or hold power+volume up (reboots device). you are now done and it should boot into android. From there, you can start again and re-root or flash new firmware or whatever, just remember to regularly back up your roms so you can just restore them from clockwork recovery!
**IF ANYONE FOUND THIS HELPFUL, PLEASE SAY SO!**

Why use the stock when there images of tiamat roms on the forum here. I've screwed mine up once but figured how to get into recovery and flashed tiamat back.

Tiger62651 said:
Why use the stock when there images of tiamat roms on the forum here. I've screwed mine up once but figured how to get into recovery and flashed tiamat back.
Click to expand...
Click to collapse
Please, really? Not everyone shares your opinion on everything. Some people, myself included, prefer to run stock. (Actually, I'm running stock rooted with CWM for Nandroid backup and screenshot purposes.)
Some people may need to go back to factory for warranty or upgrade service fron Motorola as well.
Sometimes, you have to see past your own view.

I personally prefer stock, as with the upcoming android 4.0 upgrade (!) just around the corner i want to have the ability to upgrade to it as soon as it comes out.

Thanks for this post! In the event I get the itch to do some flashing, this guide will help when I'm in a pinch.

dbam987 said:
Thanks for this post! In the event I get the itch to do some flashing, this guide will help when I'm in a pinch.
Click to expand...
Click to collapse
I second you.

It works but if your a 3g/4g owner and you do this you will lose your baseband because they wont let you pass 3.2 in OTA updates, when it is required to have 3.2.2
Sorry for being noob but I have the bootloader to 1.5 i have all stock images for 3.2.2 but my xoom wont see 3g or 4g any ideas!!!

Are you talking about the method, itself, or about the stock image realated in the link ?

localizador said:
Are you talking about the method, itself, or about the stock image realated in the link ?
Click to expand...
Click to collapse
The stock images they change something in the bootloader for the 4g card to work

THANKS, just saved me from my boot loop after trying a modified update script for 4.0.3 ;-)

Saved my chops too we must buy beer for him

Thanks for this guide, I will be making use of this this week.

HD2wally said:
Saved my chops too we must buy beer for him
Click to expand...
Click to collapse
Make it a Blue Moon!!!!!

amysdadforever said:
It works but if your a 3g/4g owner and you do this you will lose your baseband because they wont let you pass 3.2 in OTA updates, when it is required to have 3.2.2
Sorry for being noob but I have the bootloader to 1.5 i have all stock images for 3.2.2 but my xoom wont see 3g or 4g any ideas!!!
Click to expand...
Click to collapse
I thought that was fixed? See -> http://www.mydroidworld.com/forums/...la-xoom-3-2-2-recovery-images.html#post106459 and/or starting around post #331 of -> http://forum.xda-developers.com/showpost.php?p=18753267&postcount=331

But what can be fix if there is no way to get to Fastboot screen? no matter how Vol up + Power or Vol dn + power ... there is only "Dual core screen" ... i guess for those that have got that screen the Xoom is totally bricked

y2k-inc said:
But what can be fix if there is no way to get to Fastboot screen? no matter how Vol up + Power or Vol dn + power ... there is only "Dual core screen" ... i guess for those that have got that screen the Xoom is totally bricked
Click to expand...
Click to collapse
Hmmmm dont know what to tell you never had my xoom just stick at the dual core screen for sure you already tried boot xoom up wait 2 sec and vol down button twice!!!
---------- Post added at 08:38 AM ---------- Previous post was at 08:36 AM ----------
KidJoe said:
I thought that was fixed? See -> http://www.mydroidworld.com/forums/...la-xoom-3-2-2-recovery-images.html#post106459 and/or starting around post #331 of -> http://forum.xda-developers.com/showpost.php?p=18753267&postcount=331
Click to expand...
Click to collapse
Yes I see the fixed and spend 3 days trying to fix this I made a section where its 10x faster to fix using a actual mz602 .sbf file heres the link to it
http://forum.xda-developers.com/showthread.php?t=1445135
---------- Post added at 08:38 AM ---------- Previous post was at 08:38 AM ----------
KidJoe said:
I thought that was fixed? See -> http://www.mydroidworld.com/forums/...la-xoom-3-2-2-recovery-images.html#post106459 and/or starting around post #331 of -> http://forum.xda-developers.com/showpost.php?p=18753267&postcount=331
Click to expand...
Click to collapse
Yes I see the fixed and spend 3 days trying to fix this I made a section where its 10x faster to fix using a actual mz602 .sbf file heres the link to it
http://forum.xda-developers.com/showthread.php?t=1445135

Thanks you this guide is great!!!!

Because the stock images come in a set with separate roms for the different sections

LG aristo 2 (K8 2018)

Since the majority of the hardware between the devices is gonna be almost exactly the same, I'mma give a shot at rooting it. Picking up tomorrow, so hopefully it goes well

I just got this phone. Let me know how what happens please.

tge101 said:
I just got this phone. Let me know how what happens please.
Click to expand...
Click to collapse
Yeah, I'll keep a heads up. I'm sitting in metro now tryna see what's going on, small argument. Their commercials in Philly don't mention that you need to switch carriers for the rebates.

I'll probably be getting one next week. Says it has 7.1.2 an it weighs less? Cool

attempt
Ok so I tried to root this and everything went well up ubtil I flashed Team win. When i try to open it, the program starts HOWEVER something is up with the touch screen. Im unable to click anything the only power button works. I tried flashing versions 3.0.0, 3.0.1, 3.0.2, 3.0.3. No luck! Is the problem they are old versions? Should i use 3.1.1 which was designed for Nougat supposedly?
Any advice this is my first attempt in to rooting android devices. Forgive me if any of my lingo is incorrect.

tribal1209 said:
Ok so I tried to root this and everything went well up ubtil I flashed Team win. When i try to open it, the program starts HOWEVER something is up with the touch screen. Im unable to click anything the only power button works. I tried flashing versions 3.0.0, 3.0.1, 3.0.2, 3.0.3. No luck! Is the problem they are old versions? Should i use 3.1.1 which was designed for Nougat supposedly?
Any advice this is my first attempt in to rooting android devices. Forgive me if any of my lingo is incorrect.
Click to expand...
Click to collapse
Are you trying to root the aristo or aristo 2?

Aristo 2. Sorry, kind of diving in head first with this whole process. If im doing something obviously wrong go easy on me lol.
---------- Post added at 11:26 PM ---------- Previous post was at 11:25 PM ----------
Aristo 2

Hmm and you flashed the twrp that was for the aristo right?

Well the TWRP files i used were on *How To* forums posts and youtube videos for the original LG Aristo. Everything was going fine but the touch screen while in TWRP does not work. Maybe there os a different version I can try? Do any of you guys have any ideas, my understanding though is that TWRP has to be created for a specific device once released. Is thats whats going wrong?

you unlocked the bootloader and flashed the aristo 1 recovery thats what you did so far right?

The aristo 1 recovery will not work at all.
The screens are of the same build, but different composition.
That's why I wanted to test this myself before posting further on the subject.
I can risk my phone, most of you cant.

I figured as much. Thanks for the info! Just got mine today. Glad the aristo's battery works in the aristo2 as i bought a couple batteries for it. I still do like the aristo though it feels a bit better in my hand.

Well luckily It seems i have not screwed up my phone. Have reset and wiped it multiple times which was annoying, but seems to be ok. It sucks because it looks like the touch screen alone is whats screwing me over. If only i had a way around it. Then again im sure you guys have a better idea of whats going on. Guess ill just be patient until more is posted on subject.

We need a new recovery for this anyway. Since the aristo 2 isn't gonna have multiple versions (besides the Korean base model the 2 is built after), we should be able to build just one recovery using the model number as it's target, we can make it borderline universal if a new version were to pop up.
I decided against going the metro route, buying mine in bulk. So I'll have one to smash when this is all over.

The TWRP method works the same as the Aristo, and the TWRP recovery IS compatible. However the touch screen does not function.. Is there a way to get it to work?

@ninjasinabag @teknoweanie @tribal1209 Hey guys, spent a few hours figuring out how to root. Pretty Simple
1) Enable Developer Options, USB Debugging & OEM Unlock
2) Reboot to Fastboot Mode (Using ADB via PC type: adb reboot bootloader)
3) Add root_boot.img into your adb folder
4) In ADB type: fastboot flash boot root_boot.img
5) After flash successful, type: fastboot reboot
6) Install Magisk Manager App

brad2192 said:
@[email protected]@tribal1209 Hey guys, spent a few hours figuring out how to root. Pretty Simple
1) Enable Developer Options, USB Debugging & OEM Unlock
2) Reboot to Fastboot Mode (Using ADB via PC type: adb reboot bootloader)
3) Add root_boot.img into your adb folder
4) In ADB type: fastboot flash boot root_boot.img
5) After flash successful, type: fastboot reboot
6) Install Magisk Manager App
Click to expand...
Click to collapse
Not to sound sceptical but is this the real deal?

spirithandler said:
Not to sound sceptical but is this the real deal?
Click to expand...
Click to collapse
Please someone let me know! I want this phone rooted (Its an awesome phone) but want some verification before I start flashing and downloading random files.

spirithandler said:
Not to sound sceptical but is this the real deal?
Click to expand...
Click to collapse
Yes, it is. What I did was use LG firmware extractor and extracted the boot image, then I proceeded to patch the boot image with magisk manager. Enabling OEM unlock allows me to flash the boot image with the newly-created custom one. Remember though, you should create a backup of your device because enabling OEM unlock will completely erase everything.

brad2192 said:
@ninjasinabag @teknoweanie @tribal1209 Hey guys, spent a few hours figuring out how to root. Pretty Simple
1) Enable Developer Options, USB Debugging & OEM Unlock
2) Reboot to Fastboot Mode (Using ADB via PC type: adb reboot bootloader)
3) Add root_boot.img into your adb folder
4) In ADB type: fastboot flash boot root_boot.img
5) After flash successful, type: fastboot reboot
6) Install Magisk Manager App
Click to expand...
Click to collapse
Supposedly the img you posted is simply a modified version of Magisk you posted. Someone please explain to me (Who is new to this whole process) why this supposed explanation does not involve any recovery program or requiring of wiping/clearing any cache or what have you?