Related
I just flashed from Truly Epic 1.2 (was working) to Truly Epic 1.5 using CW. After rebooting the phone gets stuck on the Samsung screen. I tried wiping and re-installing 1.2 and it gets stuck on the Samsung screen also. Any suggestions? Thanks.
When I try to flash 1.5 I get the message cant open cache/recovery/log
chrylaser said:
When I try to flash 1.5 I get the message cant open cache/recovery/log
Click to expand...
Click to collapse
Odin time for you
Epic 3.5g | Syndicate Rom
Nook Color|My own honeybunches (sd), nookie froyo (eMMC)
I don't know to much about that rom but are you using the correct cwm version?
Sent from my Evo Killer!!!
Yes. CWM. I went back to stock DK28 with ODIN and still get stuvk when trying to flash 1.2 or 1.5.
chrylaser said:
Yes. CWM. I went back to stock DK28 with ODIN and still get stuvk when trying to flash 1.2 or 1.5.
Click to expand...
Click to collapse
Does your CWM have green or orange text?
Green. Any help is appreciated.
Ditto ya gotta find cwm3.0.0.5
Sent from my SPH-M900 using XDA App
chrylaser said:
Green. Any help is appreciated.
Click to expand...
Click to collapse
You need to convert from RFS to EXT4 by flashing CWM 3.0.0.1. Follow this link, then click the link in Step 1 of the install instructions. You'll have to create an AndroidCentral user in order to download the files needed, but this is the guide I used to convert my phone over so I know it works.
I installed CWM 3.0.0.5 and it still gets stuck. Now I am getting boot loops. Thanks for all the input.
I got Truly Epic 1.2 to run and select update.zip by mistake. Think that might be affecting everything? I cant even get 1.2 to flash now.
chrylaser said:
I installed CWM 3.0.0.5 and it still gets stuck. Now I am getting boot loops. Thanks for all the input.
Click to expand...
Click to collapse
hmm, everything you're describing is pointing towards the FS being RFS still.
If you are flashing TER 1.5 with a CWM with green text, your flash of CWM3 (orange text) didn't take.
Here's what I would do in this situation:
1. Odin back to DK28
2. Reflash CWM3
3. Flash TER 1.5
Again, I would use the thread I linked in my previous post as I know it works.
chrylaser said:
I got Truly Epic 1.2 to run and select update.zip by mistake. Think that might be affecting everything? I cant even get 1.2 to flash now.
Click to expand...
Click to collapse
That may have something to do with it, depending what update.zip was on you SD card.
i think theres definately something up with truly epic.. i had to restart my phone just now and i got stuck in a boot loop.. tried to reflash.. same problem.. tried to flash a different rom.. same problem.. i had to delete everything to get it to work again.. sucks
Anyone having a problem going from TER v1.2 to TER v1.5 using the full version (auto backup/restore) try using the TER v1.5 clean version now offered. It has the auto backup/restore removed.
TrulyEpic Rebirth v1.5 Clean Install
Make a NANDROID backup in CWM3 as usual
Wipe 3x
Flash and Enjoy
Any FC's from framework.google (FC errors) try rebooting into CWM3 and select Fix Permissions. That should do the trick.
Should I try to delete all the files off my SD card, ODIN back to stock DK28 and put on a fresh CWM 3?
Curious to know how different 1.2 and 1.5 are. Been on 1.2 for a week and is very stable. Only complaint is with multitasking in browser. Seems like it pauses page load if you run another app while waiting completed loading. Definately liked the benchmark scores. Sql even beats viperrom on ext4
tpike said:
Curious to know how different 1.2 and 1.5 are. Been on 1.2 for a week and is very stable. Only complaint is with multitasking in browser. Seems like it pauses page load if you run another app while waiting completed loading. Definately liked the benchmark scores. Sql even beats viperrom on ext4
Click to expand...
Click to collapse
See the changelog.
This post is only for discussing all issues regarding the use of the Bonsai roms. We can talk here about any version from 1.0.0 to x.x.x
Due to some political issues please do not post any links to the Bonsai website! This thread is just for us users and don't expect the developers of Bonsai to ever visit here.
One last thing >
nor
Yes this try to keep this thread open.
Sent From My Evo Killer!
So is there a way to get a 600mhz step in the kernal for bonsai 4.0 last i heard he was going t put it in back in 3.0.1 but still not there. Or is there an easy way to included it in the kernal page file or something that set cpu uses? Also is there a way to get the voodoo color fix or a tweak that works that will make the brightness lower at the lowest setting for 4.0 becase the brightness on this screen is way to brght at night time. I used to have a tweak like this in syndicate rom for 2.1 it was great. Any info would be great thanks guys.
Sent from my SPH-D700 using XDA App
I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force
forcelite said:
I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force
Click to expand...
Click to collapse
Were you using CWM 3.0.0.6 or 3.0.0.5 ?
Sent from my SPH-D700 using Tapatalk
Good question as i was just going to as a question about EXT4 and CW.
The rom manger is version 3.0.1.4
however the CW mod flashed is version 3.0.2.4
It only has 2 to choose from in rom manger, 3.0.2.4 or an older 3.0.1.4
Not sure were people are getting these other versions from.
Force
PS I booted into CW and saw it was v2.5.1.0
am I way off?
abrcrmdl23 said:
So is there a way to get a 600mhz step in the kernal for bonsai 4.0 last i heard he was going t put it in back in 3.0.1 but still not there. Or is there an easy way to included it in the kernal page file or something that set cpu uses? Also is there a way to get the voodoo color fix or a tweak that works that will make the brightness lower at the lowest setting for 4.0 becase the brightness on this screen is way to brght at night time. I used to have a tweak like this in syndicate rom for 2.1 it was great. Any info would be great thanks guys.
Click to expand...
Click to collapse
I can't remember what stepping is on the kernel as we have been beta testing 4.0.1 and have been mainly dealing with a new setCPU governor called interactive. Were also still working on the other governor called smartass as well. I think that the stepping goes directly from 400 to 800, but we are always looking to go faster and with better battery life. I'll bug Randy and Mammon about it.
The sound will be Voodoo version 7, but I don't think the Voodoo color fix is going to make it into 4.0.1. Sorry, but we can't do everything...at least not all at the same time.
forcelite said:
I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force
Click to expand...
Click to collapse
Did I see a similar post on the Bonsai website earlier today? I just want to verify that you were using CWM 3.0.0.6 as anything else will cause problems like that. Also when you get to these kinds of problems you should attempt a second flash of Bonsai before going to the trouble of a ODIN job. A second flash seems to fix a whole variety of odd kind of problems.
As you can imagine with all the beta testing I do I'm always finding ways to corrupt my phone. Some days I have managed to bork it 3-5 times.
I decided to test out today a 4.0.1 install directly from DI18 > CWM 3.0.0.6 > Bonsai 4.0.1 full rom. It went great with no problems at all and running just fine, so far
I think that is my problem, I am using a the CW that came with the one click unroot.
So I guess I need to do this, even if I am already rooted?
http://forum.xda-developers.com/showthread.php?t=897612&highlight=EXT4
PS
I booted into CW and saw it was v2.5.1.0
bluetooth
I could not get bonsai 3.0.1 or 4.0.0 to pair with my bluetooth headset. Tried pairing on an epic with acs 1.1 and paired fine. Anyone else have a pairing problem?
forcelite said:
Good question as i was just going to as a question about EXT4 and CW.
The rom manger is version 3.0.1.4
however the CW mod flashed is version 3.0.2.4
It only has 2 to choose from in rom manger, 3.0.2.4 or an older 3.0.1.4
Not sure were people are getting these other versions from.
Force
PS I booted into CW and saw it was v2.5.1.0
am I way off?
Click to expand...
Click to collapse
Do not use Rom Manager to be installing the beta CWM files. The correct way is with one of the 1 step CWM tools in the development forum. 3.0.2.4 is half-finished and is very difficult even to navigate through the various menu's. I know this because I tried out that CWM version for some grins one day. It will majorly screw your Epic if your not extremely careful. When DI18 was prevalent Rom Manager worked great to root your phone. When we started the move into the Froyo roms Rom Manager quit working and that is why the 1 click then became more prevalent.
Just follow the directions posted all over the place and Bonsai will install just fine and you will be a happy camper.
I am installing it now after updating to CW3 (from CW2.5) . I think it will come out fine now, I am an idiot and didn't realize the original one click root installed an older version of CW.
Thx All,
Force
forcelite said:
I think that is my problem, I am using a the CW that came with the one click unroot.
So I guess I need to do this, even if I am already rooted?
http://forum.xda-developers.com/showthread.php?t=897612&highlight=EXT4
PS
I booted into CW and saw it was v2.5.1.0
Click to expand...
Click to collapse
The linked one is the correct one for Bonsai version 4.x.x.
olddocwhite said:
I could not get bonsai 3.0.1 or 4.0.0 to pair with my bluetooth headset. Tried pairing on an epic with acs 1.1 and paired fine. Anyone else have a pairing problem?
Click to expand...
Click to collapse
Some people do and some don't I do know that Randy has instituted quite a few bluetooth linux upgrades into 4.0.1 rom. Some people are able to clear the data, but the problem usually reappears. Mattalica76 has the link to a more permanent fix to this problem, give him a PM.
Duplicate... Sorry
forcelite said:
I am installing it now after updating to CW3 (from CW2.5) . I think it will come out fine now, I am an idiot and didn't realize the original one click root installed an older version of CW.
Click to expand...
Click to collapse
Don't beat yourself up as we all have been there. It's a process of learning new skills and a new language. Give yourself a pat on the back for getting through this when 98% of the world would have said screw it or not even tried at all.
Actually it didnt boot this time either, it installed the firs ttime fine, then kept booting after samsung in a loop,
So I went into CW3 and tried to flash bonsai 4.0.01 again and it gave me this error. It is long, however I shortened it, I have the whole error photo copied)
Finding package
Opening package
Install update
Assert failed getprop (“ro.product.device)”)
Sph-700
E:error in /SDcard/bonsai……….
(status 7)
Installation aborted
Top Nurse said:
Don't beat yourself up as we all have been there. It's a process of learning new skills and a new language. Give yourself a pat on the back for getting through this when 98% of the world would have said screw it or not even tried at all.
Click to expand...
Click to collapse
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.
forcelite said:
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.
Click to expand...
Click to collapse
CWM3 will convert your filesystem to ext4 the first time you boot into it. It won't touch the sdcard so that won't be converted. After CWM is finished with the conversion, do not reboot the phone, you will then flash Bonsai.
forcelite said:
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.
Click to expand...
Click to collapse
After flashing the boot script of cwm 3.0.0.6 you then have to power off. Then hold down the camera button, vol down, and power keys at the same time and the EXT4 script will automatically start to format your system. Please keep in mind that it is not formatting the SD card, but only the read only memory of the phone.
After you finished a few beers it will be done and will drop you back to cwm. Do not reboot, but flash bonsai. After bonsai is finished then reboot.
Sent from Bonsai 7.0.3
REQUIREMENTS:
Please Nvflash to 3588 (VERY IMPORTANT)
Here's a link for instructions of 3588 by roebeet
http://forum.xda-developers.com/showthread.php?t=861950
Releasing an alpha version for xda-members to experience Honeycomb in their GTABS. First and foremost, thanks to Roebeet, MrGUY, DJ_Steve, pershoot and the rest of adam devs who helped us port Honeycomb.
WARNING:
This will update your bootloader to 1.2 version (need to be on 3588 for this combo to work)
Whats working..
1. Wifi, BT
2. Touchscreen
3. buttons
4 Browser, Gmail
5. Market
6 gapps
What is not working..
1. OpenGL
2. Camera (because of OpenGl)
3. No flash yet
Link..
https://rapidshare.com/files/541902742/Roebeet_ClemsynHoneycombo.alpha.zip
******* YOU NEED TO BE ON 3588 STOCK and STOCK RECOVERY (NO CWM) BEFORE FLASHING THIS COMBO******
INSTRUCTIONS #1
1. Nvflash to 3588 STOCK DO NOT USE CWM FOR 3588
2. Do not install CWM (we need the stock recovery)
3. DO NOT INSTALL CWM (we need the stock recovery)
4. PLEASE DO NOT INSTALL CWM
5. Reboot
6. RENAME COMBO FILE NAME TO Update.zip
7. Move Update.zip to /sdcard folder
8. Unzip recover.zip and move recovery folder to /sdcard folder
8. Turn off
10. Press Power+Volume up then this will install Update.zip
The reason we don't install CWM for 3588 is because this won't install the bootloader
Instruction #2
1. Rename Combo file to Update.zip and place in /sdcard folder
2. Unzip recovery.zip and put recovery folder in /sdcard
3. Update to NVFLASH to 1.2-4349 using this image
http://www.mediafire.com/?g7vorg66iiq29vm
4. Enter recovery by pressing Power Button+Volume up
IF YOU WOULD LIKE TO GO BACK TO FROYO AND STAY IN 1.2 bootloader here is a link for my Combo version 6
https://rapidshare.com/files/1095733302/Clemsyn_Caulkinver6.zip
BTW, if you like our work, buy us a beer
I am currently running gojimi vegan ginger rc1. What will I have to do if I want to go back,and how are storage partitions mapped on this Rom ?
cool! can't wait to try this. waiting patiently for rom to be uploaded and installation instructions to be posted...
Can't wait to finally try this when I get a few days off!
Question: After trying this and having the bootloader upgraded, will I be able to easily revert back to Clemsyn -Calkulin 1.5 with the new bootloader or will I have to nvflash?
I had to use nflash to go between the two bootloaders. My apps are usually remaining or you can use Titanium to get them back.
Awesome build running smooth already glad someone posted this here
Sent from my GTablet-HC using XDA Premium App
Thanks for posting it here Clemsyn. I really didn't want to sign up for another forum so I can ask question haha.
Anyways, when you say gmail is working, is it fully functional? I thought there were shader (or something like that) issues that prevented us to see the body of the email.
Also, is flash in the browser working?
Those are my two must haves if I am going to switch to HC.
Thanks in advance.
xmr405o said:
Thanks for posting it here Clemsyn. I really didn't want to sign up for another forum so I can ask question haha.
Anyways, when you say gmail is working, is it fully functional? I thought there were shader (or something like that) issues that prevented us to see the body of the email.
Also, is flash in the browser working?
Those are my two must haves if I am going to switch to HC.
Thanks in advance.
Click to expand...
Click to collapse
No flash yet. There is a hacked gmail.apk that works fine. I am using it now, and only flash is not working of everything I personally use. The devs are very close now.
I apologize for the delay, it wasn't done uploading yet and I needed to go to my kid's science project (he won 5th place). Just got home so I posted the link on first page. BTW, gmail is also fixed.
SirhanSirhan said:
No flash yet. There is a hacked gmail.apk that works fine. I am using it now, and only flash is not working of everything I personally use. The devs are very close now.
Click to expand...
Click to collapse
actually flash is technically working just fine...it's the opengl shader issues causing it not to display properly...opengl is also causing the gmail app issues (alt app in place as a temp fix, now) and opengl issues are causing a few other apps to have issues as well...once opengl is resolved then this will be a practically perfect build, imo been running it for about a week now with all the updating and love it!!
clemsyn said:
Releasing an alpha version for xda-members to experience Honeycomb in their GTABS.
Click to expand...
Click to collapse
Thanks clemsyn for sharing this, so whats the difference between this and Roebeets versions released on slatedriod ?
hey, clemsyn...when you get back online, I have a question for you. A lot of the current talk in the Adam dev chat is that a .36 or newer kernel will resolve many of the current issues (OpenGL specifically)...I was wondering if maybe you had a newer version kernel in the works or not for the gtab? If so, how's it coming along? If not, how tough do you think it would be to develop a .36 version of the kernel? Thanks for everything, man. Have a good one.
Is Dolphin HD working on this?
Thanks to clemsyn & roebeet for porting this from the Adam.
Stuck on boot
Hey Roebeet, its been awhile but I'm back and ready for HoneyComb. I folowed your directions. I used NvFlash to get back to 3588. I then installed CWM .08 and partitioned internal 2048 and 0. I put the zip on internal and installed via CWM. Now it hangs on the viewsonic white screen? Any Ideas?
Theres already a 2.3.32.40 overclocked kernal out. Is that not what you are wanting?
jlytle1234 said:
Theres already a 2.3.32.40 overclocked kernal out. Is that not what you are wanting?
Click to expand...
Click to collapse
it's 2.6.32.40...the 40 is the version number of the .32 kernel...they are looking for a x.x.36.x kernel to possibly resolve the issues with opengl...
acuralegendz said:
Hey Roebeet, its been awhile but I'm back and ready for HoneyComb. I folowed your directions. I used NvFlash to get back to 3588. I then installed CWM .08 and partitioned internal 2048 and 0. I put the zip on internal and installed via CWM. Now it hangs on the viewsonic white screen? Any Ideas?
Click to expand...
Click to collapse
Most of us got this issue. When reading on the other website it says to do wipe data after flashing so do that and see
Sent from my SGH-T959 using XDA App
Djapatos said:
Most of us got this issue. When reading on the other website it says to do wipe data after flashing so do that and see
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I think this guys issue stems from the fact that he installed cwm. This rom needs to be installed with the stock bootloader.
Well I have the same issue, I wiped, but nothing. When I flashed the file, it said unknown command bootloader, bla bla.
Pretty sure thats the issue, I was running 3588 ...dont know whats up.
I get the same results with the unknown command bootloader. I've tried wiping all data after the installing the rom and the gtab still gets hung up. This is coming from using nvflash to 3588 and a repartition.
I was running on a rooted 3.1 with tiamat 1.7 overclock
What I did was:
tried to follow [UPDATE][US WIFI ONLY]Android 3.2 on Xoom WiFi, Root, via ClockworkMod Recovery
then I did this: Note also if you are coming over from a custom ROM, wipe your cache partition (under main menu) and dalvik cache (under Advanced) in ClockworkMod Recovery prior to performing the following steps.
next I applied the 3.2 update
Now Im stuck in the boot animation.
From what I understand Im getting this because I was not on the stock kernel, can anybody help me fix this and get me to 3.2
Thank you
download the stock images here http://forum.xda-developers.com/showthread.php?t=1080963
and flash via fastboot, this will get you out of the boot loop, i had the same issue
should I try and flash the 3.2 or the 3.1 given my current situation?
If you made a backup in cwm just restore it. If not, I would say go back to the beginning and flash stock 3.0. If you plan on rooting unlock the bootloader right then. Setup the Xoom, connect to wifi and take the 3.1 ota update. Setup and connect to wifi again and wait a bit to see if 3.2 ota update notification appears. If it does, take it and root it (see my guide in dev section). If it does not pop up, you can update manually (see bauxite's guide in dev section) then root. This way you should have no issues. I know it sounds like a lot to do, but it all should take you less than hour. I did one for a friend and it took me 34min to do everything. After your rooted you can restore apps with titanium if you have made and saved the backups. Good luck.
Sent from my HD2
jase33 said:
If you made a backup in cwm just restore it. If not, I would say go back to the beginning and flash stock 3.0. If you plan on rooting unlock the bootloader right then. Setup the Xoom, connect to wifi and take the 3.1 ota update. Setup and connect to wifi again and wait a bit to see if 3.2 ota update notification appears. If it does, take it and root it (see my guide in dev section). If it does not pop up, you can update manually (see bauxite's guide in dev section) then root. This way you should have no issues. I know it sounds like a lot to do, but it all should take you less than hour. I did one for a friend and it took me 34min to do everything. After your rooted you can restore apps with titanium if you have made and saved the backups. Good luck.
Sent from my HD2
Click to expand...
Click to collapse
You probably should wipe user data in recovery along with the caches. That's what got me out of the bootloop and into the updated stock 3.2.
i flashed the stock images from the first link provided via fastboot and it worked perfect, the thread said you can flash from whatever to whatever by using those images so i flashed 3.2 and it fixed everything. Took about 5 minutes to do, I wonder if this way will give me problems when I try to root (pretty sure I lost root) but everything now seems to work fine
Hi,
I had the same issue. i fix by going back in cwm making factory reset and install again the same image.
after the first reboot i restored soft with titanium and all working good.
Tomate2K8 said:
Hi,
I had the same issue. i fix by going back in cwm making factory reset and install again the same image.
after the first reboot i restored soft with titanium and all working good.
Click to expand...
Click to collapse
Yep, that's the easiest solution, but whatever works!
I just tried to flash Tiamat 2.0 and the boot image with it (I followed the directions and did them in the correct order), and it's now stuck at the Motorola boot screen (not the animation). Any suggestions? I'm not sure how to get back in to CWM now.
Edit: Managed to get in to CWM, did a factory/data reset and wiped cache before re-flashing. Still stuck on the boot screen.
i updated my aussie telstra xoom 3g to tiamat 2 (3.2) and booted fine but did not see 3g, so i used a bul.prop from 3.1 and got the bootloop prob, rebooted to recovery and did wipe erase, when it booted up again tried the euro build.prob and all worked, i suspect the issue relates to buil.prop so a bit of tinkering will always win in the end, bassically these things seem to be bullet proof when it comes to screwing summin up
phekno said:
I just tried to flash Tiamat 2.0 and the boot image with it (I followed the directions and did them in the correct order), and it's now stuck at the Motorola boot screen (not the animation). Any suggestions? I'm not sure how to get back in to CWM now.
Edit: Managed to get in to CWM, did a factory/data reset and wiped cache before re-flashing. Still stuck on the boot screen.
Click to expand...
Click to collapse
What HC version were you on when you flashed 2.0? I'm just wondering if you needed to flash the boot image. It's hard to help you if we don't know what configuration you are coming from. Also Is your Xoom US wifi or 3G or Euro wifi or 3G?
zbee said:
i updated my aussie telstra xoom 3g to tiamat 2 (3.2) and booted fine but did not see 3g, so i used a bul.prop from 3.1 and got the bootloop prob, rebooted to recovery and did wipe erase, when it booted up again tried the euro build.prob and all worked, i suspect the issue relates to buil.prop so a bit of tinkering will always win in the end, bassically these things seem to be bullet proof when it comes to screwing summin up
Click to expand...
Click to collapse
Yeah, they really are almost bullet-proof. Good thing too, seeing all the abuse they have to take.
: )
okantomi said:
What HC version were you on when you flashed 2.0? I'm just wondering if you needed to flash the boot image. It's hard to help you if we don't know what configuration you are coming from. Also Is your Xoom US wifi or 3G or Euro wifi or 3G?
Click to expand...
Click to collapse
My fault, I guess some information would have been helpful. The Xoom is a US WiFi version and I was running 3.1 when I started this, which I now realize was probably really stupid. I should have probably gotten 3.2 on there before I started. Is there a way to update to 3.2 at this point? Or do I need to go back to stock and start over?
I appreciate the help.
Edit: Or should I just install another ROM per these directions.
phekno said:
My fault, I guess some information would have been helpful. The Xoom is a US WiFi version and I was running 3.1 when I started this, which I now realize was probably really stupid. I should have probably gotten 3.2 on there before I started. Is there a way to update to 3.2 at this point? Or do I need to go back to stock and start over?
I appreciate the help.
Edit: Or should I just install another ROM per these directions.
Click to expand...
Click to collapse
Are you rooted? If so, you can flash the Tiamat Xoom Rom 1.1 which is for 3.1. You don't need to flash any additional kernel. You can get it from the appropriate thread in Development. You will probably have to do a full wipe in CWM Recovery (user data, cache).
From there, you can flash the Team Tiamat Xoom Rom 2.0 Manta Ray right on top of the Rom 1.1, no wipe needed. That should get you the HC3.2 update, preserve your root, and give additional functionality. I love it. I updated in a more roundabout method...I could have done it this way if I had waited...
If you are not rooted, you need to root first..see any one of the guides to root in HC3.1.
Good luck!
okantomi said:
Are you rooted? If so, you can flash the Tiamat Xoom Rom 1.1 which is for 3.1. You don't need to flash any additional kernel. You can get it from the appropriate thread in Development. You will probably have to do a full wipe in CWM Recovery (user data, cache).
From there, you can flash the Team Tiamat Xoom Rom 2.0 Manta Ray right on top of the Rom 1.1, no wipe needed. That should get you the HC3.2 update, preserve your root, and give additional functionality. I love it. I update in a more roundabout method...I could have done it this way if I had waited...
If you are not rooted, you need to root first..see any one of the guides to root in HC3.1.
Good luck!
Click to expand...
Click to collapse
Yeah, I was rooted before all of this. I had done a full wipe in CWM and then did the boot/kernel and now I'm here. I think I should have just done the Tiamat Xoom Rom 2.0 in stead. Can I just flash the 2.0 ROM over what's on there now?
Edit: Now, I can't seem to get in to CWM. I'm not really sure how to other than using adb reboot recovery, but windows isn't picking up the device now.
Edit #2: I got back in to CWM. I'm running CWM 3.0.2.5, FYI.
I just flashed Tiamat Xoom Rom 1.1 and now it's back up and running. Thanks a ton for helping! I'll probably be putting 2.0 on there pretty quickly.
phekno said:
I just flashed Tiamat Xoom Rom 1.1 and now it's back up and running. Thanks a ton for helping! I'll probably be putting 2.0 on there pretty quickly.
Click to expand...
Click to collapse
Great! Have fun with it. I think you'll love it.
I have a problem restoring my xoom to stock.
I flashed the Katana OC kernel onto my Wifi Only US Xoom with 3.2. I oc'd to 1.5 ghz and it worked fine. Then I left it on during the night. When I woke up the next morning it was stuck in a boot loop, so I though maybe I should flash the Katana without OC instead. That I tried but It got stuck halfway through (Maybe I should have waited longer...).
After this the xoom wouldnt boot (not that surprising..) so I flashed it back to stock with the official Motorola images. However the Xoom still wont boot up, gets stuck either on Moto logo or on the Honeycomb boot screen.
When I flash the 3.2 images and a custom kernel (Tiamat 2.0) then I can get into Android but it stops responding after a few minutes.
The Xoom seems to be running good before it freezes, I cant find a solution to get my Xoom back to life.
Any ideas?
blee00 said:
I have a problem restoring my xoom to stock.
I flashed the Katana OC kernel onto my Wifi Only US Xoom with 3.2. I oc'd to 1.5 ghz and it worked fine. Then I left it on during the night. When I woke up the next morning it was stuck in a boot loop, so I though maybe I should flash the Katana without OC instead. That I tried but It got stuck halfway through (Maybe I should have waited longer...).
After this the xoom wouldnt boot (not that surprising..) so I flashed it back to stock with the official Motorola images. However the Xoom still wont boot up, gets stuck either on Moto logo or on the Honeycomb boot screen.
When I flash the 3.2 images and a custom kernel (Tiamat 2.0) then I can get into Android but it stops responding after a few minutes.
The Xoom seems to be running good before it freezes, I cant find a solution to get my Xoom back to life.
Any ideas?
Click to expand...
Click to collapse
Have you done a full wipe user data/factory reset in CWM recovery? You may need a clean slate to proceed.
Also, do you know if debugging is set to on? If you can't boot you can't get into settings but that could prevent you from accessing your Xoom from your pc.
okantomi said:
Have you done a full wipe user data/factory reset in CWM recovery? You may need a clean slate to proceed.
Also, do you know if degugging is set to on? If you can't boot you can't get into settings but that could prevent you from accessing your Xoom from your pc.
Click to expand...
Click to collapse
Thanks for your reply! =)
I have done the "Wipe user data/factory reset" in CWM, If I do that I usually can boot Honeycomb, but I rarely get past the setup wizard (although sometimes I do), but then after a few minutes it freezes again.
Also, I can access my Xoom through ADB.
Hi Guys,
I am trying to change my ROM from Criskelo 5.1 (has speedmod kernel but dont think that should make a difference) to LiquidSmooth 3.2. Usually this is a pretty straight froward process but for some reason I just cant get past CWM. Here is what I've done so far.
Reboot into recovery.
Flash AbyssNote 3.2 (redtouch) and reboot into AybssNote.
Wipe everyting (inlcuding dalvik and battery)
Flash LiquidSmooth 3.2
On doing this the phone restarts - as is expected - but then it just reboots in CWM. I've tried various permutations of this (even tried wipes from CWM before going into Abyss) in the hope that it might work but nothing seems to work. Before this I tried to go Criskelo 5 to 8 and got stuck on boot screen.
Thanks God for nandroid or this would have become an extremely frustrating experience. Any ideas ?
EDIT: Used AbyssNote 4.2 and not 3.2 .... sorry about that
tariqsaleem said:
Hi Guys,
I am trying to change my ROM from Criskelo 5.1 (has speedmod kernel but dont think that should make a difference) to LiquidSmooth 3.2. Usually this is a pretty straight froward process but for some reason I just cant get past CWM. Here is what I've done so far.
Reboot into recovery.
Flash AbyssNote 3.2 (redtouch) and reboot into AybssNote.
Wipe everyting (inlcuding dalvik and battery)
Flash LiquidSmooth 3.2
On doing this the phone restarts - as is expected - but then it just reboots in CWM. I've tried various permutations of this (even tried wipes from CWM before going into Abyss) in the hope that it might work but nothing seems to work. Before this I tried to go Criskelo 5 to 8 and got stuck on boot screen.
Thanks God for nandroid or this would have become an extremely frustrating experience. Any ideas ?
Click to expand...
Click to collapse
Bump .... anyone ?
Get a stock gb rom and flash via pc odin.
Sent from my GT-N7000 using xda app-developers app
tariqsaleem said:
Bump .... anyone ?
Click to expand...
Click to collapse
Have you try other ROM besides LiquidSmooth? Since it stuck in CWM, I suspect the installation script for LiquidSmooth is not compatible with Abyss 3.2 CWM.
praetorius said:
Get a stock gb rom and flash via pc odin.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
I was hoping you wouldn't say that .... I have a really slow net connection at the moment and don't have any GB stock roms saved (next time I'll think twice before I delete stuff ). Is there any other way I can do this or is this the only option I have ?
lenrek said:
Have you try other ROM besides LiquidSmooth? Since it stuck in CWM, I suspect the installation script for LiquidSmooth is not compatible with Abyss 3.2 CWM.
Click to expand...
Click to collapse
I tried to update to Criskelo v8 and in that case I got stuck on the boot screen. Had to do a hard reset and get back into recovery manually.
Sorry about the confusion, I actually used Abyss 4.2 (which I got from the Liquid Smooth thread) so I don't think there should be any compatibility issues.
Go back to abyss42 and factory reset from within abyss42 (red menu). Also do cache and dalvik wipe.
Reinstall your custom rom.
And since you have a slow connection, there is a chance your files are corrupt.
Sent from my GT-N7000 using xda app-developers app
Do a unzip -t <zipfile> to verify the file is not corrupted. As above post stated, it maybe a corrupted zip file.
praetorius said:
Go back to abyss42 and factory reset from within abyss42 (red menu). Also do cache and dalvik wipe.
Reinstall your custom rom.
And since you have a slow connection, there is a chance your files are corrupt.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Did all of that i.e Factory reset from within Abyss42, clear cache and dalvik wipe.
I guess I'll try downloading again but why I doubt that would fix anything since this is the 2nd ROM I've had the same issue with. Well not exactly same, in the case of Criskelo 8 it gets stuck on boot screen where as with liquid smooth 3.2 it keeps going back into CWM . Still worth a try though. will update tonight once I get to download again.
Anyway of verifying whether my files are corrupt or not ?
lenrek said:
Do a unzip -t <zipfile> to verify the file is not corrupted. As above post stated, it maybe a corrupted zip file.
Click to expand...
Click to collapse
Thanks...I'll give that a go later today. Currently the rom in on my phone. Can I do something similar via the terminal on my mobile ?
tariqsaleem said:
Thanks...I'll give that a go later today. Currently the rom in on my phone. Can I do something similar via the terminal on my mobile ?
Click to expand...
Click to collapse
Is a zip file, so just get one of those app that can open zip/compressed file from the Google Play. I use AndroZip, FYI. I believe there are more choices in Google Play.
lenrek said:
Is a zip file, so just get one of those app that can open zip/compressed file from the Google Play. I use AndroZip, FYI. I believe there are more choices in Google Play.
Click to expand...
Click to collapse
Tried to open it with ES Zip Viewer and it opens up without any issues, so does that mean that the file is not corrupted ?
tariqsaleem said:
Anyway of verifying whether my files are corrupt or not ?
Click to expand...
Click to collapse
check for MD5 checksum
try abyss 3.9
my phone stuck on bootanimation endlessly with Liquid black 3.2, i was using abysss 4.2 with red interface, i moved on to asylum
rraaka said:
try abyss 3.9
my phone stuck on bootanimation endlessly with Liquid black 3.2, i was using abysss 4.2 with red interface, i moved on to asylum
Click to expand...
Click to collapse
Tried flashing with abyss 3.9 but still have the same issue. The phone reboots into CWM
For the benefit of others....went back to stock Samsung GB image and flashed paranoid android from there and it worked
Sent from my GT-N7000 using xda app-developers app