like i said i ran everything and backed up everything that needed to be backed up with nvflash. i am still on .26 and i am kind of stuck on where to go. i want to try clean rom out but it says i need to be on the jelly bean bootloader, do i get this from asus? do i have to update to stock jelly bean and then go to the rom?
That's one way to go. I haven't flashed any official JB ROM yet, and run CleanROM at the moment (though that might be different tomorrow, or it may stay a wek ). I flashed ZEUS 34, the unofficial CM10 builds by hiemanshu, Baked Bean... Guess I tried them all, and I didn't touch the bootloader in any explicit way. I guess the AndroidRoot bootloader (which, as you should know by now, is installed prior to installing Nvflash) is able to tackle these ROMs all by itself.
MartyHulskemper said:
That's one way to go. I haven't flashed any official JB ROM yet, and run CleanROM at the moment (though that might be different tomorrow, or it may stay a wek ). I flashed ZEUS 34, the unofficial CM10 builds by hiemanshu, Baked Bean... Guess I tried them all, and I didn't touch the bootloader in any explicit way. I guess the AndroidRoot bootloader (which, as you should know by now, is installed prior to installing Nvflash) is able to tackle these ROMs all by itself.
Click to expand...
Click to collapse
alright awesome. i just wanted to make sure before i did anything. thank you!
Related
Before I started to flash a new ICS Rom (which I am quite excited about) I had a D2G on Hexen. I flashed the CM9 ROM and got bricked, so I SBF flashed back to stock and tried again. Again, a brick. I tried a third time with the same result and then decided to try Gummy instead (thinking there may be some issues with CM9 because it is in Beta). It also bricked. In the end I just flashed back to my backup that I saved from right before I began this process, but I would really like to take advantage of these new ROMs. If anyone has any advice I would be most thankful.
Some notes:
I was the the newest CWM Recovery Version
I checked all the MD5 and they all aligned perfectly
Thanks for any help I receive, if you want to know something else about my phone data during this procedure, just let me know.
so you flashed back to.33 or .608 before you flash cm9?
Sent from my DROID2 GLOBAL using xda premium
odnanreh12 said:
Before I started to flash a new ICS Rom (which I am quite excited about) I had a D2G on Hexen. I flashed the CM9 ROM and got bricked, so I SBF flashed back to stock and tried again. Again, a brick. I tried a third time with the same result and then decided to try Gummy instead (thinking there may be some issues with CM9 because it is in Beta). It also bricked. In the end I just flashed back to my backup that I saved from right before I began this process, but I would really like to take advantage of these new ROMs. If anyone has any advice I would be most thankful.
Click to expand...
Click to collapse
Hexen was made for 2.4.x stock firmware (Android 2.2 and the corresponding Motorola kernel).
All newer ROMs (CM7, CM9, Gummy, Apex, etc.) are based on 4.5.x. Update to 4.5.608 (preferably via SBF; do NOT accept any OTA updates once you're on 4.5.608) and proceed from there.
Ah thanks so much, I forgot that Android Firmware numbers had to match up, I will try again later tonight
forgot that Android Firmware numbers had to match up,
Click to expand...
Click to collapse
just fyi, not android firmware, moto's system version/firmware
Firmware must be watched
Sent from my GT-I9001 using xda premium
Well, it won't let me post in the official thread so I'm forced to put it here.
I recently installed the Team EOS Jelly Bean nightly (Stingray MZ602) their gapps, and reflashed the ICS radio as recommended using Rogue Recovery. Things have been working well except the WiFi. It tends to cut out randomly. It will be connected yet not transmit or receive. I have to turn it off and on frequently in order for it to work. No, it's not the router or my network. I am hoping for a solution other than going back to ICS.
First thing I would do is to full wipe and format /system
And flash twrp recovery that is advised as stable flasher.
Then redownload the ROM and gapps and make sure check sum is OK,
Then flash and reboot.
This way, you would id the source of your issue, ROM bug or recovery flasher? Cuz I know other guys face no issues like yours with twrp. Worth to try. Good luck.
The twrp page hasn't been updated since April and the project itself hasn't been updated since October of 2011. How can you be sure that it'll work with the radio zip better than Rogue? Or even the Team EOS JB build?
Twrp is advised by team eos. They asked to use it. And you need twrp for Xoom,
http://forum.xda-developers.com/showthread.php?p=28988754
Installation method 4 thru goo manager.
I remember one of the stingray users had an issue with the radio flashing and it went great with twrp.
Good luck.
Didn't work. I still have to reset the WiFi every 5 minutes or so. Also, the twrp recovery takes a LOT longer to load than Rogue's. Almost thought it wasn't going to work for a bit until the 'curtain' finally rose.
Over 24-hour bump...
Just put on EOS 138 and reflashed the radios after going back to Rogue. Still radio issues with WiFi. Found some other threads detailing that Jelly Bean in general seems to have WiFi issues. As much as I hate it, I'm starting to think that I will have to 1) revert to ICS, 2) wait for an updated radio file, or 3) deal with it.
Wifi Issue
First Aid Computing said:
Just put on EOS 138 and reflashed the radios after going back to Rogue. Still radio issues with WiFi. Found some other threads detailing that Jelly Bean in general seems to have WiFi issues. As much as I hate it, I'm starting to think that I will have to 1) revert to ICS, 2) wait for an updated radio file, or 3) deal with it.
Click to expand...
Click to collapse
I always have that problem with their roms. Flash a kernel, thats always helped my situation.
Also I have zero issues with wifi on JB with my GNexus, N7, Infuse and Atrix. Its not JB, at least not as far as I have seen. Granted none are stock.
Which kernel would you recommend?
Also, until JB I have not had this issue with EOS builds.
issues
First Aid Computing said:
Which kernel would you recommend?
Also, until JB I have not had this issue with EOS builds.
Click to expand...
Click to collapse
I flashed Eos 138 last night (was on CNA), without doing the radios, nor a kernel, and didn’t have any problems.
The Eos forum states that it has the kernel baked into the rom, so flashing the kernel is likely redundant.
However, for ****s and giggles I tried flashing the Eos 3.0.15 kernel and it would not flash, but I was able to flash the Eos 3.0.5 kernel instead and it took. I haven’t seen any issues, either before or after the kernel flash, so perhaps you should try re-flashing the entire rom sans radios and see what happens.
One of the nice things about the Xoom is its pretty easy to fix anything you could do to it via ADB and fastboot, so try some different combos, or start all the way over (from stock). If that doesn’t help, try a different JB rom and see if you get the same problem.
Also make sure you are flashing the right rom, there are several variants for the Xoom - 3G, 4G, Euro, and of course wifi only.
Just flashed CM10 and the non-EOS gapps without flashing radios. Running on WiFi for about 20 minutes so far without issue. Will try more testing later today.
EOS 4 & Kindle
Thanks EOS for 4.2.1! Feels like most things are working...except Kindle locks up on start-up. Just sayin'....
Hey guys, I'm new to the community and I just wanted to post my 1st experience with rooting etc and follow up with a few questions!
A bit of background on my device: I've had my NS for just over 3 years now and I just recently decided (when I bought my Xperia V) that I'd like to play around with it a bit. To my knowledge, my device was one of the 1st in the country and a test dummy, and I purchased it from a friend who was working and testing for Samsung at the time. It was not linked or affiliated to Vodacom (who, if I'm correct, was the only network provider to offer the NS in S. Africa) or any other carrier for that matter. So basically due to the lack of link to any carrier, I've never received any updates or notifications to update, and have been running my stock 2.3.5 for 3 years!
Anyway, my story from yesterday was a huge learning experience. I decided that I wanted to root my NS and possibly try out a new kernel before deciding whether or not I wanted to install a custom ROM. I followed this link and managed to root my NS, install CWM recovery and everything was working pretty well using UPDATE-SuperSU-v1.65.
http://forum.xda-developers.com/showthread.php?t=2034264
However I think I flashed the wrong kernel (marmite_v9.1) or for some other reason messed up, keep in mind that I was still running my stock GB which the phone came with. Either way, I was stuck on the Google boot screen for more than an hour. I fired up into fastboot and then recovery, but couldn't boot from there (I just realized that I DIDN'T make an actual backup ). To top it off I wiped the device (another great idea) and the device wouldn't boot into fastboot, giving me a "fastboot mode no boot recovery img" message. Somehow through flashing the CWM I managed to get the device into the correct fastboot mode, and eventually after digging for a few hours I managed to find this (stock?) soju GB ROM download, and managed to flash the boot and system images using fastboot, for some reason " fastboot flash userdata data.img" refused to flash. http://forum.xda-developers.com/showthread.php?t=478820
Anyway, I managed to get back to GB 2.3.5, but get this, after about half an hour on charge, I was given an update to ICS 4.0.4 which I obviously jumped at, and to top it off, I also have JB 4.1.1 available. My NS has finally seen the light of ICS and JB!!
I have a few questions for those who have used ICS and JB though. On the NS, does stock JB provide a notable difference in battery life and speed? With it's hardware, is it capable of handling ICS and JB effectively?
Also, which version of marmite would be compatible with ICS? From what I've picked up, marmite 9.1 is compatible with JB, but is it compatible with ICS too, and if not, can someone please point me in the right direction for kernel(s) which work with ICS (not just marmite).
Second, are the Oxygen and Rasbeanjelly ROMs still up to date? When searching for Oxygen for NS on the forum, the most recent version I find is this which was posted over a year ago: http://forum.xda-developers.com/showthread.php?t=1605273
And this for Rasbeanjelly (among others): http://forum.xda-developers.com/showthread.php?t=2028718
When checking out fitsnugly.euroskank, I don't see anything for the NS. . But maybe I'll consider a shot at the PA and CM ROMs and try them both in a few days
Finally, and this 1 is way over my head, but how does CWM work? If I do a wipe before flashing a ROM/kernel, won't that wipe my backups? Do I need to partition my sd before wiping, or does CWM do that for me, and if it not, does wiping not touch the backups?
Anyway, thanks in advance, and I hope I haven't asked too many questions which have been answered before. If I have, please bare with me and point me to the correct discussion(s) and I'll go bug some other people.
uwais27 said:
Hey guys, I'm new to the community and I just wanted to post my 1st experience with rooting etc and follow up with a few questions!
A bit of background on my device: I've had my NS for just over 3 years now and I just recently decided (when I bought my Xperia V) that I'd like to play around with it a bit. To my knowledge, my device was one of the 1st in the country and a test dummy, and I purchased it from a friend who was working and testing for Samsung at the time. It was not linked or affiliated to Vodacom (who, if I'm correct, was the only network provider to offer the NS in S. Africa) or any other carrier for that matter. So basically due to the lack of link to any carrier, I've never received any updates or notifications to update, and have been running my stock 2.3.5 for 3 years!
Anyway, my story from yesterday was a huge learning experience. I decided that I wanted to root my NS and possibly try out a new kernel before deciding whether or not I wanted to install a custom ROM. I followed this link and managed to root my NS, install CWM recovery and everything was working pretty well using UPDATE-SuperSU-v1.65.
http://forum.xda-developers.com/showthread.php?t=2034264
However I think I flashed the wrong kernel (marmite_v9.1) or for some other reason messed up, keep in mind that I was still running my stock GB which the phone came with. Either way, I was stuck on the Google boot screen for more than an hour. I fired up into fastboot and then recovery, but couldn't boot from there (I just realized that I DIDN'T make an actual backup ). To top it off I wiped the device (another great idea) and the device wouldn't boot into fastboot, giving me a "fastboot mode no boot recovery img" message. Somehow through flashing the CWM I managed to get the device into the correct fastboot mode, and eventually after digging for a few hours I managed to find this (stock?) soju GB ROM download, and managed to flash the boot and system images using fastboot, for some reason " fastboot flash userdata data.img" refused to flash. http://forum.xda-developers.com/showthread.php?t=478820
Anyway, I managed to get back to GB 2.3.5, but get this, after about half an hour on charge, I was given an update to ICS 4.0.4 which I obviously jumped at, and to top it off, I also have JB 4.1.1 available. My NS has finally seen the light of ICS and JB!!
I have a few questions for those who have used ICS and JB though. On the NS, does stock JB provide a notable difference in battery life and speed? With it's hardware, is it capable of handling ICS and JB effectively?
Also, which version of marmite would be compatible with ICS? From what I've picked up, marmite 9.1 is compatible with JB, but is it compatible with ICS too, and if not, can someone please point me in the right direction for kernel(s) which work with ICS (not just marmite).
Second, are the Oxygen and Rasbeanjelly ROMs still up to date? When searching for Oxygen for NS on the forum, the most recent version I find is this which was posted over a year ago: http://forum.xda-developers.com/showthread.php?t=1605273
And this for Rasbeanjelly (among others): http://forum.xda-developers.com/showthread.php?t=2028718
When checking out fitsnugly.euroskank, I don't see anything for the NS. . But maybe I'll consider a shot at the PA and CM ROMs and try them both in a few days
Finally, and this 1 is way over my head, but how does CWM work? If I do a wipe before flashing a ROM/kernel, won't that wipe my backups? Do I need to partition my sd before wiping, or does CWM do that for me, and if it not, does wiping not touch the backups?
Anyway, thanks in advance, and I hope I haven't asked too many questions which have been answered before. If I have, please bare with me and point me to the correct discussion(s) and I'll go bug some other people.
Click to expand...
Click to collapse
Follow the link in my signature for a ROM review... I've heard debates over the best versions for battery life, but JB in my opinion is far superior to ICS... Oxygen is a great ROM, but it won't get more updates and kernels/mods ect.. Are harder to obtain.. It may be a bit challenging to do, but I'd use 4.1.2 JB (follow my chart) or skip to 4.3 JB (Mokee or Slimbean)
Sent from my Nexus S using xda premium
good flashing
uwais27 said:
On the NS, does stock JB provide a notable difference in battery life and speed?
Click to expand...
Click to collapse
Speed yes. Battery life no.
uwais27 said:
With it's hardware, is it capable of handling ICS and JB effectively?
Click to expand...
Click to collapse
There are stutters here and there. You need to overclock to obtain "optimal" ICS and JB performance. JB is smoother than ICS.
uwais27 said:
Second, are the Oxygen and Rasbeanjelly ROMs still up to date?
Click to expand...
Click to collapse
No.
uwais27 said:
If I do a wipe before flashing a ROM/kernel, won't that wipe my backups?
Click to expand...
Click to collapse
No.
uwais27 said:
Do I need to partition my sd before wiping,
Click to expand...
Click to collapse
No.
uwais27 said:
....does wiping not touch the backups?
Click to expand...
Click to collapse
Normally it does not. Unless you select "wipe external sd card"
Hey all, need a quick hand with my T-Mo LG G2 d801- 4.4.2 stock rom.
Process so far: towelroot>supersu>autorec>twrp>...
Tried flashing CM11, but after about 20min I figured I did something wrong, lol.
What version of cyanogenmod should I be flashing, 10 or 11? From the description of what AutoRec does to deal with the bootloader, it downgrades to the last vulnerable rom to install/enable custom recovery, correct? If so, does it stay downgraded or is that just to get the custom recovery in place?
Don't want to brick my phone experimenting, so here I am. Thanks in advance!
Also should have waited till after work, as I have no more time tonight to mess with it unfortunately. Back in 8hrs! :silly:
Nevermind, I got it working.
fleshybits said:
Nevermind, I got it working.
Click to expand...
Click to collapse
Consider that while others might not have had an answer to your question, your thread could have been frequented in order to see the answer.
So, how did you resolve your issue? ?
fleshybits said:
Hey all, need a quick hand with my T-Mo LG G2 d801- 4.4.2 stock rom.
Process so far: towelroot>supersu>autorec>twrp>...
Tried flashing CM11, but after about 20min I figured I did something wrong, lol.
What version of cyanogenmod should I be flashing, 10 or 11? From the description of what AutoRec does to deal with the bootloader, it downgrades to the last vulnerable rom to install/enable custom recovery, correct? If so, does it stay downgraded or is that just to get the custom recovery in place?
Don't want to brick my phone experimenting, so here I am. Thanks in advance!
Also should have waited till after work, as I have no more time tonight to mess with it unfortunately. Back in 8hrs! :silly:
Click to expand...
Click to collapse
Autorec just flashes an older boot loader, with a stock based KK kernel that's compatible. Once up and running any stock based kernel can be flashed if running a stock ROM. It also supports running any after market ROM, however, if running a jb based ROM one needs to be on a jb modem, and if running KK a compatible modem. These are pretty much the only prerequisites.
Sorry, that was rather rude of me wasn't it? Apologies. Not fair to ask for help if I can't return the favor when I can.
Well, instead of looking around on the CM downloads page to get the most stable release, I just got the most recent snapshot of CM 11. Silly me
Turns out the right file to flash first was, of course, the last stable release for the G2 D801, which was CM 10.2.0 (at least at the time of this writing, as far as I know.) After getting the right file and trying again, I was rocking my first custom ROM. Go me! :good:
I have not yet tried the snapshot again to see if I could upgrade to CM11, as I hit another snag: I can't connect to my carrier anymore. I can see T-Mobile in the list for networks but selecting them does nothing, I get no service. Restoring the stock ROM works just fine, its like nothing happened, but running CM I can't connect. Any suggestions?
Hi all,
I am using OMNIROM 4.4.4 bigpart in my old EU Wingray XOOM 32GB but I have lots of performance and stability issues (browser crashes, apps freezing, very slow system....). After reinstalling it I still have problems and I want to check if it's due to the device itself...
To test that, I would like to go back to the stock Android 4.0.4 ICS that I was using in my European xoom before the jump to EOS, CM and OMNI.
Could anybody help me on how to go back to stock? Where to download the stock rom? how to remove bigpart? Is it really required to remove bigpart to install the stock rom?
Thanks for any help given.
The best way to go back to factory image is to go back to Android 3.1 honeycomb , firmware HW169
http://morningbeat.blogspot.ca/2012/02/convert-uk-or-other-motorola-xoom-to.html
once you are back to android 3.1, keep check update. until you get the latest 4.12 or stop at 4.0.4 if you wish.
valent|n0 said:
The best way to go back to factory image is to go back to Android 3.1 honeycomb , firmware HW169
http://morningbeat.blogspot.ca/2012/02/convert-uk-or-other-motorola-xoom-to.html
once you are back to android 3.1, keep check update. until you get the latest 4.12 or stop at 4.0.4 if you wish.
Click to expand...
Click to collapse
Thanks a lot for answering.
So... I have to download the original Honeycomb software, "reflash it" and update until I get 4.0.4 or 4.1.2 ...
My doubt is ... do I have to "undo" the "bigpart"? Or will the stock firmware install perfectly in my "bigpart" xoom?
Thanks!
the bigpart issue I am not to sure of
Of course you need to undo BigPart. It's well document in Xoom Android development section of this forum.
You need to flash the non-big-part TWRP (2.8.0 or other), wipe everything, reboot intot TWRP, format Data, wipe everything again, reboot into TWRP again. Then you can flash original image using fastboot.
Just to stick my nose in, (and go slightly off topic) have you tried My Android Jellybean 4.2? before you go back to honeycomb you might want to give it a go, runs very smooth and very few bugs (if any!)
machina77 said:
Just to stick my nose in, (and go slightly off topic) have you tried My Android Jellybean 4.2? before you go back to honeycomb you might want to give it a go, runs very smooth and very few bugs (if any!)
Click to expand...
Click to collapse
... Sorry
jkd said:
... Sorry
Click to expand...
Click to collapse
Eh?
I didn't find anything in forum, could somebody help me how can i go back from bigpart to stock partition?
I tried to go back to stock last month and it was a nightmare trying to get it to boot back after the update. My only advise is to leave the thing alone. Or do a wipe in twrp or cwm. BTW, I still can not get my device to boot or enter recovery after my dumb ass tried to get back stock firmware.
nomadman said:
I tried to go back to stock last month and it was a nightmare trying to get it to boot back after the update. My only advise is to leave the thing alone. Or do a wipe in twrp or cwm. BTW, I still can not get my device to boot or enter recovery after my dumb ass tried to get back stock firmware.
Click to expand...
Click to collapse
I just flashed mine from omni bigpart back to stock 3.1 cause my 1yr old daughter can't keep her hands off my phone...was time consuming researching how to do it. But it works perfectly...I wound up running some script somebody wrote and it pretty much did everything for me... not in front of my PC at the moment but if you are still fighting it PM me and I'll give ya everything you need...