Related
So ive searched for what im looking for but im unsure which way to go with rooting because i guess some software versions arent compatible
I just came home with a 16gb wifi flyer, and i'd very much like to root. Ive tried every samsung epic and htc hero rom available, so i know the benefits.
I have Software number: 1.36.1540.32, 2.3.3, htc sense 2.1
Could someone point me in the right direction for rooting with this software version? Thanks
US BB wifi version?
Easy to root, just follow the guide. Then you can run any custom GB ROM or keep it stock.
Only issue is if you take the plunge to Honeycomb, you can never go back since there is no compatible RUU.
DigitalMD said:
US BB wifi version?
Easy to root, just follow the guide. Then you can run any custom GB ROM or keep it stock.
Only issue is if you take the plunge to Honeycomb, you can never go back since there is no compatible RUU.
Click to expand...
Click to collapse
Yeah, that one. I was looking at the rooting guide, but it has my software version listed under 32gb 3G and thats not mine.
myke66 said:
Yeah, that one. I was looking at the rooting guide, but it has my software version listed under 32gb 3G and thats not mine.
Click to expand...
Click to collapse
I've used that guide for my BB Flyer. Everything but flashing clockwork worked.
Zlatty said:
I've used that guide for my BB Flyer. Everything but flashing clockwork worked.
Click to expand...
Click to collapse
Thanks for the reply, i did a bit of research into Revolutionary and it turns out its the HBOOT version that matters not the software version. So having HBOOT 1.10 it worked fine. CW installed, and FlyHigh Rom/Kernal flashed.
Apps run very smooth, but oddly the live wallpaper im running lags now, before the flash it didnt. Im wondering if its from the CPU settings. Possible underclocked too much sitting at the home screen or something.
Update: Changed the govener to performance and the LW no longer lag. Thats what i assumed it was. Ill have to find which one has the best battery conservation while still running smooth. Cant do too much testing while im at work though
myke66 said:
Thanks for the reply, i did a bit of research into Revolutionary and it turns out its the HBOOT version that matters not the software version. So having HBOOT 1.10 it worked fine. CW installed, and FlyHigh Rom/Kernal flashed.
Apps run very smooth, but oddly the live wallpaper im running lags now, before the flash it didnt. Im wondering if its from the CPU settings. Possible underclocked too much sitting at the home screen or something.
Update: Changed the govener to performance and the LW no longer lag. Thats what i assumed it was. Ill have to find which one has the best battery conservation while still running smooth. Cant do too much testing while im at work though
Click to expand...
Click to collapse
WTG! Now, did you flash CW through the instructions? I have tried to do this again from the hboot with no luck. Any pro tips?
Also, LWP should still pause in between screen switches on the flyhigh....
Zlatty said:
WTG! Now, did you flash CW through the instructions? I have tried to do this again from the hboot with no luck. Any pro tips?
Also, LWP should still pause in between screen switches on the flyhigh....
Click to expand...
Click to collapse
I flashed CW through the revolutionary program. When it gave me the option to download and flash it, i just said yes.
And yes, i know about the LWP "pausing" while moving screens, but this was running very choppy till i messed with the CPU settings.
What part were you getting stuck on? Its pretty linear once the script starts the install.
myke66 said:
I flashed CW through the revolutionary program. When it gave me the option to download and flash it, i just said yes.
And yes, i know about the LWP "pausing" while moving screens, but this was running very choppy till i messed with the CPU settings.
What part were you getting stuck on? Its pretty linear once the script starts the install.
Click to expand...
Click to collapse
I've downloaded it from recovery and it installed, but it would always go into recovery like CW was never there
maybe i should go back and try again :|
Zlatty said:
I've downloaded it from recovery and it installed, but it would always go into recovery like CW was never there
maybe i should go back and try again :|
Click to expand...
Click to collapse
You mean it boots to the white screen with the Android guy skateboarding or whatever?
Menu down to where it says "Recovery" and select that, and it reboots the device into CW.
myke66 said:
You mean it boots to the white screen with the Android guy skateboarding or whatever?
Menu down to where it says "Recovery" and select that, and it reboots the device into CW.
Click to expand...
Click to collapse
Yes, but when I choose recovery I go into recovery 5.0 or something like that (blue screen), and not CW
Zlatty said:
Yes, but when I choose recovery I go into recovery 5.0 or something like that (blue screen), and not CW
Click to expand...
Click to collapse
Im not sure what the stock recovery looks like on the Flyer (ive yet to see it) but it sounds like i would reflash the CW recovery, that is infinitely important.
So, you are rooted but not using any custom rom?
myke66 said:
Im not sure what the stock recovery looks like on the Flyer (ive yet to see it) but it sounds like i would reflash the CW recovery, that is infinitely important.
So, you are rooted but not using any custom rom?
Click to expand...
Click to collapse
rooted...S-OFF and all that jazz
using 1.2 version of fly high rom
Zlatty said:
rooted...S-OFF and all that jazz
using 1.2 version of fly high rom
Click to expand...
Click to collapse
So how did you go about flashing the flyhigh rom to start with? Was CWM working at some point?
myke66 said:
So how did you go about flashing the flyhigh rom to start with? Was CWM working at some point?
Click to expand...
Click to collapse
Through the adb recovery tool thingy ... blue screen ... don't have the flyer on me, so I cannot tell ... but as far as I understand recovery is different than CWM ... riiiight?
Zlatty said:
Through the adb recovery tool thingy ... blue screen ... don't have the flyer on me, so I cannot tell ... but as far as I understand recovery is different than CWM ... riiiight?
Click to expand...
Click to collapse
CWM IS the recovery. Its a custom version that allows you to do a hell of a lot more than the stock recovery. Any shot of getting a pic of what your bluescreen looks like?
I rooted my old Viewsonic GTablet to put a better ROM on it, this HTC Flyer is great, what would be th advantage of rooting it?
Sorry for the noobish question.
Sent from my HTC Flyer P512 using xda premium
TidBit said:
I rooted my old Viewsonic GTablet to put a better ROM on it, this HTC Flyer is great, what would be th advantage of rooting it?
Sorry for the noobish question.
Sent from my HTC Flyer P512 using xda premium
Click to expand...
Click to collapse
Long story short personal preference that's it. Some people love it the way it is. Some people love it but just want a little more. rooting gives them that extra access to make it better. If you get me.
myke66 said:
CWM IS the recovery. Its a custom version that allows you to do a hell of a lot more than the stock recovery. Any shot of getting a pic of what your bluescreen looks like?
Click to expand...
Click to collapse
I feel like a dummy ... clearly on the bottom it says Recovery CWM v#.##....
TidBit said:
I rooted my old Viewsonic GTablet to put a better ROM on it, this HTC Flyer is great, what would be th advantage of rooting it?
Sorry for the noobish question.
Sent from my HTC Flyer P512 using xda premium
Click to expand...
Click to collapse
I rooted because i wanted to be able to install a custom kernel to be able to overclock to have the best gaming performance on the tablet. My original reason for getting it was to play Order & Chaos big screen.
Also the custom roms are almost always faster and take up less memory.
Zlatty said:
I feel like a dummy ... clearly on the bottom it says Recovery CWM v#.##....
Click to expand...
Click to collapse
glad we could figure it out
myke66 said:
I rooted because i wanted to be able to install a custom kernel to be able to overclock to have the best gaming performance on the tablet. My original reason for getting it was to play Order & Chaos big screen.
Also the custom roms are almost always faster and take up less memory.
glad we could figure it out
Click to expand...
Click to collapse
What do you have it clocked at?
Also HTC sense is such a BLOAT. New roms definitely help with the weight control.
Hey guys. I just got my brand new galaxy s2 and I'm loving it. But as of right now the latest software update is 2.3.6. Now I'm on 2.3.4 and I checked for a software update and it says I'm on the latest software.
Sent from my SAMSUNG-SGH-I777 using Tapatalk
You're not blind...
My understanding is that AT&T is rolling it out to in waves. Eventually you'll see the update. They just can't, and don't want to, put it out to every [email protected] at the same time.
From what I've read, if you're planning to root your phone, it's much easier and better supported to do it from an earlier version.
Galaxee said:
My understanding is that AT&T is rolling it out to in waves. Eventually you'll see the update. They just can't, and don't want to, put it out to every [email protected] at the same time.
From what I've read, if you're planning to root your phone, it's much easier and better supported to do it from an earlier version.
Click to expand...
Click to collapse
OK. So basically don't be worried? Lol. I just got it today and w
Saw all the roms in the development section talking about stock 2.3.6 and I'm like wtf? And yes I'm planning to root my phone but I want to experience it this way first. I love it. And its so fast
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Galaxee said:
My understanding is that AT&T is rolling it out to in waves. Eventually you'll see the update. They just can't, and don't want to, put it out to every [email protected] at the same time.
From what I've read, if you're planning to root your phone, it's much easier and better supported to do it from an earlier version.
Click to expand...
Click to collapse
AT&T does this in case the update has a problem that missed their QA process.
I'm fairly certain they are rolling out the update fairly slowly - there were even rumors that it might have been pulled for a while. People getting the OTA have had a LOT of complaints.
MysticKing32 said:
OK. So basically don't be worried? Lol. I just got it today and w
Saw all the roms in the development section talking about stock 2.3.6 and I'm like wtf? And yes I'm planning to root my phone but I want to experience it this way first. I love it. And its so fast
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Click to expand...
Click to collapse
The reason you see so many 2.3.6 based ROMs in development is because a few developers took a gamble - they guessed that the UCKK6 leak might be a final release that could go official, and they were right. We had access to a full UCKK6 2-3 weeks before anyone received an OTA.
Note that many of those ROMs are appearing to have a few issues:
1) Weird wifi compatibility issues not present in UCKH7
2) Bluetooth HID is broken - no mouse/keyboard pairing
Entropy512 said:
AT&T does this in case the update has a problem that missed their QA process.
I'm fairly certain they are rolling out the update fairly slowly - there were even rumors that it might have been pulled for a while. People getting the OTA have had a LOT of complaints.
The reason you see so many 2.3.6 based ROMs in development is because a few developers took a gamble - they guessed that the UCKK6 leak might be a final release that could go official, and they were right. We had access to a full UCKK6 2-3 weeks before anyone received an OTA.
Note that many of those ROMs are appearing to have a few issues:
1) Weird wifi compatibility issues not present in UCKH7
2) Bluetooth HID is broken - no mouse/keyboard pairing
Click to expand...
Click to collapse
Thanks bro. I appreciate that. Now I'm about to root using either super one click or the zedomax way and I just wanted to confirm this with you. When the Att update comes I just use your guide to flash your kernel that comes with stock recovery right? Then I'm done right and I can just apply the ota update regularly right? Thanks again
Sent from my SAMSUNG-SGH-I777 using Tapatalk
MysticKing32 said:
Thanks bro. I appreciate that. Now I'm about to root using either super one click or the zedomax way and I just wanted to confirm this with you. When the Att update comes I just use your guide to flash your kernel that comes with stock recovery right? Then I'm done right and I can just apply the ota update regularly right? Thanks again
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Click to expand...
Click to collapse
If you root using either Super One Click, or Doomlords version of the zergrush exploit, you will still retain the stock kernel and be able to get the update without additional changes. If you update while rooted, you will retain root on UCKK6.
I'm not sure, but if you use the zedomax kernel to root, you may lose device manager and therefore not be able to check for the update.
creepyncrawly said:
If you root using either Super One Click, or Doomlords version of the zergrush exploit, you will still retain the stock kernel and be able to get the update without additional changes. If you update while rooted, you will retain root on UCKK6.
I'm not sure, but if you use the zedomax kernel to root, you may lose device manager and therefore not be able to check for the update.
Click to expand...
Click to collapse
Hey buddy. How do you get out of download mode on the gs2. I was trying to do the odin thing and turns out the drivers were'nt correctly installed. So mind lending a noob a hand lol .
MysticKing32 said:
Hey buddy. How do you get out of download mode on the gs2. I was trying to do the odin thing and turns out the drivers were'nt correctly installed. So mind lending a noob a hand lol .
Click to expand...
Click to collapse
Am I supposed to take the battery out or something. It says do not turn off so I'm a bit confused.
You should not interrupt download mode during a flash, of course, because bad things will happen. However, if the flash is finished, or if you put the phone into download mode without starting a flash, just hold down the power button until the download screen goes away, and the boot screen appears. You can also just pull the battery.
creepyncrawly said:
You should not interrupt download mode during a flash, of course, because bad things will happen. However, if the flash is finished, or if you put the phone into download mode without starting a flash, just hold down the power button until the download screen goes away, and the boot screen appears. You can also just pull the battery.
Click to expand...
Click to collapse
Lol. Yeah. I didn't start a flash at all. I used pda net to get the drivers and upon connecting it didn't work. So thanks. I think I'll use the zedomax way and then flash entropy's daily driver through clockwork mod. I can do that right?
That should work fine.
Hey guys. I have an over the air update available for the 2.3.6 and I accidentally pressed cancel and it says I have to wait another 20 hours to try again. Is there a way around this or am I stuck.
(PS. I rooted the phone and I'm on stock kernel so I should be fine in terms of keeping root)
Sent from my SAMSUNG-SGH-I777 using Tapatalk
MysticKing32 said:
Hey guys. I have an over the air update available for the 2.3.6 and I accidentally pressed cancel and it says I have to wait another 20 hours to try again. Is there a way around this or am I stuck.
(PS. I rooted the phone and I'm on stock kernel so I should be fine in terms of keeping root)
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Click to expand...
Click to collapse
Try this, go to menu/settings/applcations/manage applications/all tab/device manager and hit the clear data button. Then go to menu/settings/check for updates and it should let you download.
creepyncrawly said:
Try this, go to menu/settings/applcations/manage applications/all tab/device manager and hit the clear data button. Then go to menu/settings/check for updates and it should let you download.
Click to expand...
Click to collapse
OK. I'll try it now
Sent from my SAMSUNG-SGH-I777 using Tapatalk
creepyncrawly said:
Try this, go to menu/settings/applcations/manage applications/all tab/device manager and hit the clear data button. Then go to menu/settings/check for updates and it should let you download.
Click to expand...
Click to collapse
Hey man. That worked but the install failed. I read about this somewhere though. Don't I have to wipe data or something. Or will I need to apply the update manually?
Sent from my SAMSUNG-SGH-I777 using Tapatalk
MysticKing32 said:
Hey man. That worked but the install failed. I read about this somewhere though. Don't I have to wipe data or something. Or will I need to apply the update manually?
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Click to expand...
Click to collapse
You mean it wouldn't download, or after it downloaded it wouldn't install?
creepyncrawly said:
You mean it wouldn't download, or after it downloaded it wouldn't install?
Click to expand...
Click to collapse
Right. After it downloaded it wouldn't install.
Sent from my SAMSUNG-SGH-I777 using Tapatalk
creepyncrawly said:
You mean it wouldn't download, or after it downloaded it wouldn't install?
Click to expand...
Click to collapse
It fails at 67 percent and I tried seven times by moving the date forward and clearing the data to get the update each time. And I even turned off wiring and used data. It just keeps failing for some reason
Sent from my SAMSUNG-SGH-I777 using Tapatalk
MysticKing32 said:
It fails at 67 percent and I tried seven times by moving the date forward and clearing the data to get the update each time. And I even turned off wiring and used data. It just keeps failing for some reason
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Click to expand...
Click to collapse
I don't know what would be causing the problem. Some posters indicated that you need to have all the bloatware on the phone, as well as the stock kernel, but I don't know if that is true or not.
I know that when I tested it, I started out on UnNamed. I Used the Odin One-click downloader to put UCKH7 stock plus root, and then updated succesfully. The first time I did it, I forgot to do a data wipe, so after I pulled the files I was getting, I did a data wipe, installed the UCKH7 stock plus root and updated again. The update worked flawlessly on both occasions, retaining root.
So the only thing I can suggest is do a wipe data/factory reset in recovery, install the Return/Unbrick to stock UCKH7 plus root package, and then update. I would think that would clear anything out that would prevent the update.
creepyncrawly said:
I don't know what would be causing the problem. Some posters indicated that you need to have all the bloatware on the phone, as well as the stock kernel, but I don't know if that is true or not.
I know that when I tested it, I started out on UnNamed. I Used the Odin One-click downloader to put UCKH7 stock plus root, and then updated succesfully. The first time I did it, I forgot to do a data wipe, so after I pulled the files I was getting, I did a data wipe, installed the UCKH7 stock plus root and updated again. The update worked flawlessly on both occasions, retaining root.
So the only thing I can suggest is do a wipe data/factory reset in recovery, install the Return/Unbrick to stock UCKH7 plus root package, and then update. I would think that would clear anything out that would prevent the update.
Click to expand...
Click to collapse
OK. I'll flash that. I'll let you know.
Sent from my SAMSUNG-SGH-I777 using Tapatalk
It's not clear to me why some people had a successful webOS 3.0.5 update with Android installed, others didn't. And some people even had stock Touchpads which have problems now after the update? Wow!
If I'm on 3.0.4 with XRON 2.9 installed; what is it I have to do in order to successfully update without having to wipe everything and start anew?
I've read this thread two or three times, plus this other thread, which seems to be ONLY for people who had a failed update, and I'm not entirely sure.
Can someone help with a 1,2,3 kind of scenario?
Thanks!
Well, it seems so far(that I have noticed) that the update will fail if you are using moboot 0.3.3 or 0.3.4. Follow this, and all should be good.
1.) Make a nandroid backup of your android in CWM
2.) Make a backup of webOS(Launcher>Settings>Backup
3.) Make sure you have moboot 0.3.5
4.) Click System Updates in webOS and let it download.
5.) Once finished, try to install.
6.A) Based on my observations, it should install fine.
6.B) If for some reason it doesn't work, that's ok, because you have backed up everything. Follow standard procedure for removing android, and getting webOS back to stock, and install everything(moboot, cwm, android). Then once everything is back, restore your backups.
Sent from my Legendary 2.2 infused device.
FWIW, I did the update yesterday without any major issues.
Prior to the update I had CM7 A3.5 installed and WebOS 3.04. My moboot was still on 0.3.3 as I had never updated it since my initial Android install.
I did the update in WebOS and let it do its thing for a while. When I rebooted the only difference was the bootloader was gone and it would just boot straight into WebOS 3.0.5.
I reinstalled Moboot (0.3.5 this time) and then booted back up into Android and all was fine. I hadn't backed anything up and I hadn't lost anything.
Of course, as always, YMMV.
I was on moboot 0.33 and webos 3.02 and the ota update locked into a boot loop.
Just had to doctor and re-acme CWM, CM7.1 and moboot before restoring my nandroid backup.
Sent from my HTC G2
Thanks guys; I just rebooted to see the menu, and indeed I have the lastest MoBoot (0.3.5). So I am going to back everything up and do this tomorrow.
Thanks for taking the confusion away. I love XDA, but let's be honest, there is so much information, so many threads with thousands of posts, that the whole thing becomes impossible to digest.
Too much information is sometimes worse than having not enough information!
Xaltotun said:
Thanks guys; I just rebooted to see the menu, and indeed I have the lastest MoBoot (0.3.5). So I am going to back everything up and do this tomorrow.
Thanks for taking the confusion away. I love XDA, but let's be honest, there is so much information, so many threads with thousands of posts, that the whole thing becomes impossible to digest.
Too much information is sometimes worse than having not enough information!
Click to expand...
Click to collapse
Good luck bud. Just be sure to back up both as I stated just in case the install doesn't work.
Sent from my Legendary 2.2 infused device.
not to add more confusion to this, but I upgraded without any trouble and I later found out I'm on moboot 3.3. once the upgrade was done I shut off the tp and when I restarted it went straight into moboot. So I'm not sure the moboot version is the critical factor here.
As long as you backup both webos and android I think you should be fine. Although I might ask if you still use webos enough to bother. I didn't see a whole lot new but I didn't spent much time on it.
I failed twice updating, restored palm kernels removed all preware patches and success. Moboot 3.0.4, xron 2.9 were untouched.
Will we be able to run tablet compatible apps in ics?
Sent from my Touchpad using xda premium
sLiKK said:
Will we be able to run tablet compatible apps in ics?
Sent from my Touchpad using xda premium
Click to expand...
Click to collapse
Yes.
Sent from my Legendary 2.2 infused device.
I'm on 0.3.5 and its failed everytime. I unistalled kernels, etc.
zanderman112 said:
Yes.
Sent from my Legendary 2.2 infused device.
Click to expand...
Click to collapse
Can't wait .....
Sent from my SGH-T959 using xda premium
sLiKK said:
Can't wait .....
Sent from my SGH-T959 using xda premium
Click to expand...
Click to collapse
I cant wait for CM9.
Sent from something with a Ｋモ尺れモㄥ.
Well I backed-up everything and did the update. It seems to have worked.
I did get a couple of random reboots, but I got those before. Not sure if the reboots are due to the update or not.
Thanks to all who have contributed to this thread.
Since the "Buttery Biscuit" rom is still in development, which is better, Classicnerd_SE or Classicnerd_ICS_Buttah? I am currently running SE and it is quite amazing! I'm. Just looking for some input while I anxiously await the official release. Thanks guys!
And if you haven't checked out classicnerd yet, DO IT!!
Flashed Buttah earlier. Superuser works correctly now. Seems smoother than SE. CPUtuner works correctly on buttah as well.
Thanks for the reply! It took a great deal of work, but I finally got SE to work for me last night. It seems that I have the Buttah zip installed as well because when moboot comes up I have an option to boot Classicnerd and an option to boot ICS, but no matter which one I choose, my "about phone" screen always shows SE. Its weird in my opinion, but it works and that's all I care about.
Where do I find these roms? There is no link anywhere
Sent from my Optimus 2X using XDA App
Netuser said:
Where do I find these roms? There is no link anywhere
Sent from my Optimus 2X using XDA App
Click to expand...
Click to collapse
Check classicnerds.net n it'll be in the ics beta section
Sent from my GT-I5700 using Tapatalk
Netuser said:
Where do I find these roms? There is no link anywhere
Sent from my Optimus 2X using XDA App
Click to expand...
Click to collapse
click the blue box in my signature, note: please if you are running cm9 or xrom/cm7 ACMEuninstall and ACMEinstall moboot and clockworkmod and then flash the rom from recovery.
N00Bextrordinaire said:
Thanks for the reply! It took a great deal of work, but I finally got SE to work for me last night. It seems that I have the Buttah zip installed as well because when moboot comes up I have an option to boot Classicnerd and an option to boot ICS, but no matter which one I choose, my "about phone" screen always shows SE. Its weird in my opinion, but it works and that's all I care about.
Click to expand...
Click to collapse
The correct entry is Classicnerd. I don't think running from the ICS entry will cause you any problems but you may want to clean it out so future updates have the space they need on the /boot partition.
I am on SE, and it is quite smooth. I probably won't upgrade until the KY edition drops.
Dude never believe what other says abt any rom..flash urself....as it might be good for u but not for others...as not everyone use all the features in Android....
viny2cool said:
Dude never believe what other says abt any rom..flash urself....as it might be good for u but not for others...as not everyone use all the features in Android....
Click to expand...
Click to collapse
I agree, you definitely need to form your own opinions, but sometimes I like to know what others think as well.
I've been following both the XRON and classicnerd threads pretty much since they started...
The "SE" build was a preview originally put together for a closed test team, and came before the "Buttah" version which was offered in the open (although still alpha status, even though they put it into a "beta" directory).
They're both made by the same team from the same sources. Buttah should be more polished (and from what everyone is saying in the dev thread, it sounds phenomenal already).
I'm waiting 'til it comes out of alpha before I switch away from 2.9.1, but I'm definitely drooling over what I've read.
I have tried all four classic nerd ics versions and buttah is the first one that has my touch pad charging quickly and battery life is very good.
Sent from ClassicNerd ICS 4.03 HPtouchpad.
glabifrons said:
I've been following both the XRON and classicnerd threads pretty much since they started...
The "SE" build was a preview originally put together for a closed test team, and came before the "Buttah" version which was offered in the open (although still alpha status, even though they put it into a "beta" directory).
They're both made by the same team from the same sources. Buttah should be more polished (and from what everyone is saying in the dev thread, it sounds phenomenal already).
I'm waiting 'til it comes out of alpha before I switch away from 2.9.1, but I'm definitely drooling over what I've read.
Click to expand...
Click to collapse
oh man you're missing out! ics buttah is sooo silky smooth and pretty much stable (minus the major problem all ics roms have). the major difference between SE and buttah is the charger fix. my TP now charges when I use it while it's plugged in. before it would keep on running down
if you do decide to update from SE to buttah remember to wipe data, wipe cache, and wipe dalvik cache several times before flashing on. also i would run the remove moboot entries just to be sure
mmikeee said:
oh man you're missing out! ics buttah is sooo silky smooth and pretty much stable (minus the major problem all ics roms have). the major difference between SE and buttah is the charger fix. my TP now charges when I use it while it's plugged in. before it would keep on running down
if you do decide to update from SE to buttah remember to wipe data, wipe cache, and wipe dalvik cache several times before flashing on. also i would run the remove moboot entries just to be sure
Click to expand...
Click to collapse
i think leo included the wipe moboot entries in this release not sure tho but he mentioned it before releasing this one. when i flashed buttah i didnt have to flash the remove moboot entries.
life_420 said:
i think leo included the wipe moboot entries in this release not sure tho but he mentioned it before releasing this one. when i flashed buttah i didnt have to flash the remove moboot entries.
Click to expand...
Click to collapse
true he did say that. scratch what i said about flashing the remove moboot entries
Sweet Buttah!
I flashed Buttah about an hour ago. This is really, really nice and smooth. Amazing for an alpha software version.
A few things not working on my tablet:
Headphone audio
Dolphin HD browser crashes when trying to play Flash video
That's it so far.
If you are moving from a cm from there is no need for acme uninstall just do factory reset and wipe cache. Do this at least 3 times (just to be safe) and then flash the from and gapps from clockwork mod.
Sent from my Touchpad using Tapatalk
calash said:
The correct entry is Classicnerd. I don't think running from the ICS entry will cause you any problems but you may want to clean it out so future updates have the space they need on the /boot partition.
Click to expand...
Click to collapse
I was finally able to get Buttah to install last night via CWM by downloading the .zip straight to the touch pad instead of transferring from my PC. In the spirit of the Xron roms, I decided to try installing it as an "overlay" to the SE rom and so far I haven't had any issues. I had to reflash the gapps, but I was expecting that. Now in my Moboot I only have an option for Classicnerd and no ICS option.
N00Bextrordinaire said:
I was finally able to get Buttah to install last night via CWM by downloading the .zip straight to the touch pad instead of transferring from my PC. In the spirit of the Xron roms, I decided to try installing it as an "overlay" to the SE rom and so far I haven't had any issues. I had to reflash the gapps, but I was expecting that. Now in my Moboot I only have an option for Classicnerd and no ICS option.
Click to expand...
Click to collapse
Yup moboot clear script has been incorporated in the from it removed any previous cm or ics UI image files.
Sent from my Touchpad using Tapatalk
rbarkus said:
I flashed Buttah about an hour ago. This is really, really nice and smooth. Amazing for an alpha software version.
A few things not working on my tablet:
Headphone audio
Dolphin HD browser crashes when trying to play Flash video
That's it so far.
Click to expand...
Click to collapse
do you have adobe flash installed from the market?
This is the second time this has happened!! i happen to reboot my phone, i cant get it to fully boot back up. it only gets as far as the Samsung Galaxy Note3 screen with the yellow and red writing in the top corner. The only way i can get back up and running is if i flash a rom or an old backup. Any pointers or ideas would be greatly appreciated..
btw... Im running fre3 2.13 with calm kernel
Thanks
UPDATE: I re-flashed fre3 rom did a clean install. What im finding out is when i "Titanium Backup" freeze an like "Polaris Office" or any other bloat, i cannot defrost it back and if i reboot the phone right after good luck getting it booted back up. Now im really left clueless...
ImEVO said:
This is the second time this has happened!! i happen to reboot my phone, i cant get it to fully boot back up. it only gets as far as the Samsung Galaxy Note3 screen with the yellow and red writing in the top corner. The only way i can get back up and running is if i flash a rom or an old backup. Any pointers or ideas would be greatly appreciated..
btw... Im running fre3 2.13 with calm kernel
Thanks
UPDATE: I re-flashed fre3 rom did a clean install. What im finding out is when i "Titanium Backup" freeze an like "Polaris Office" or any other bloat, i cannot defrost it back and if i reboot the phone right after good luck getting it booted back up. Now im really left clueless...
Click to expand...
Click to collapse
That may help me as well, I reflashed everything this morning, with that 2.13 update, clean install. Then proceeded to debloat, I typically don't freeze anything I just uninstall what I don't want. Today was the first time I uninstalled Polaris, would not boot, had to flash again and start fresh. I know this doesn't really help, but at least maybe this narrows things down a bit.
Update: It's not Polaris, left that intact, just cleaned up the rest of the crap that I usually do and now my phone won't boot. Wonder if it has anything to do with the ART framework that was added in this update, Think I'm going back to 2.12
SanityBroken said:
That may help me as well, I reflashed everything this morning, with that 2.13 update, clean install. Then proceeded to debloat, I typically don't freeze anything I just uninstall what I don't want. Today was the first time I uninstalled Polaris, would not boot, had to flash again and start fresh. I know this doesn't really help, but at least maybe this narrows things down a bit.
Update: It's not Polaris, left that intact, just cleaned up the rest of the crap that I usually do and now my phone won't boot. Wonder if it has anything to do with the ART framework that was added in this update, Think I'm going back to 2.12
Click to expand...
Click to collapse
I'm thinking its the kernel ,I flashed previous version of beast.. I'm going to debloat some now, I'll report back
ImEVO said:
I'm thinking its the kernel ,I flashed previous version of beast.. I'm going to debloat some now, I'll report back
Click to expand...
Click to collapse
Went back to 2.12, uninstalled all of the same things and booted right up. I'm really leaning towards the framework changes in the update being the culprit. Let me know how the Kernel change works.
SanityBroken said:
Went back to 2.12, uninstalled all of the same things and booted right up. I'm really leaning towards the framework changes in the update being the culprit. Let me know how the Kernel change works.
Click to expand...
Click to collapse
Kernel was no go same problems.. I re flashed free rom and 2.12 update and debloated and I have no issue now. .
you may have found the culprit lol
Same thing happened to me yesterday I thought I just removed something important but seeing this makes me think differently I want to ditch all the crap I have never even once used and I did a reboot and got the Samsung screen with the lettering then black screen lame
harrybear25 said:
Same thing happened to me yesterday I thought I just removed something important but seeing this makes me think differently I want to ditch all the crap I have never even once used and I did a reboot and got the Samsung screen with the lettering then black screen lame
Click to expand...
Click to collapse
Just go back to 2.12 and go nuts on the debloating lol.. That's what I did
SanityBroken said:
Went back to 2.12, uninstalled all of the same things and booted right up. I'm really leaning towards the framework changes in the update being the culprit. Let me know how the Kernel change works.
Click to expand...
Click to collapse
Have you tried debloating in 2.12 and flashing 2.13 on top??
UnAshamed 1:1six
ImEVO said:
Have you tried debloating in 2.12 and flashing 2.13 on top??
UnAshamed 1:1six
Click to expand...
Click to collapse
No, I did a clean install. That might be worth a shot, nothing wrong with a little dirty flashing now and then. Today is my monday, don't like taking too many chances with the phone during the week. If you get the chance to try it lmk how it works out.
ImEVO said:
Have you tried debloating in 2.12 and flashing 2.13 on top??
UnAshamed 1:1six
Click to expand...
Click to collapse
Got bored, dirty flashed 2.13 over de-bloated 2.12, so far, so good. Kind of a pain, but it's a workaround. Good thinking thx
SanityBroken said:
Got bored, dirty flashed 2.13 over de-bloated 2.12, so far, so good. Kind of a pain, but it's a workaround. Good thinking thx
Click to expand...
Click to collapse
What was the pain?
UnAshamed 1:1six
ImEVO said:
What was the pain?
UnAshamed 1:1six
Click to expand...
Click to collapse
Only a hassle if you start fresh again. Plus, I found another app I want to get rid of, but I can't. I'm going to try to remove it manually when I get home from work, see if TiBu is the problem.
In original post, you stated you get stuck at Sammy screen with yellow and red writing... are you referring to the pre recovery screen? If so, try booting into download mode, but select reboot phone when the option comes up. I've experienced issues with the N3 not wanting to boot a couple times after rooting and/or flashing, but was able to get it to fire up by doing that...
Sent from my SM-N900P using xda app-developers app
SanityBroken said:
Only a hassle if you start fresh again. Plus, I found another app I want to get rid of, but I can't. I'm going to try to remove it manually when I get home from work, see if TiBu is the problem.
Click to expand...
Click to collapse
Which app? Maybe I removed it already..lol
UnAshamed 1:1six
emazzy72 said:
In original post, you stated you get stuck at Sammy screen with yellow and red writing... are you referring to the pre recovery screen? If so, try booting into download mode, but select reboot phone when the option comes up. I've experienced issues with the N3 not wanting to boot a couple times after rooting and/or flashing, but was able to get it to fire up by doing that...
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
I'll try it next time thanks
UnAshamed 1:1six
ImEVO said:
Which app? Maybe I removed it already..lol
UnAshamed 1:1six
Click to expand...
Click to collapse
Ok, just got home. Went to system-app with Root Browser, deleted the app I didn't want, rebooted, everything is fine. Kinda makes me want to wipe everything, and flash without 2.12 and see if it is Titanium that was screwing everything up. Haven't decided yet, I'll let ya know what happens if I do.
Problem Solved
@ImEVO, just wiped everything and did a clean install of 2.1 and went straight to 2.13. I downloaded a random "root uninstaller" from the playstore and debloated with no issues, must be something with Titanium not playing well with the update.
SanityBroken said:
@ImEVO, just wiped everything and did a clean install of 2.1 and went straight to 2.13. I downloaded a random "root uninstaller" from the playstore and debloated with no issues, must be something with Titanium not playing well with the update.
Click to expand...
Click to collapse
Nice, I'm going to have to do that, thanks
I guess it's just us 2 with this issues lol
UnAshamed 1:1six