yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 10.1 Android Development] ralexand:
I/O tab with the latest version (as of 7/30) with bootloop issues checking in

saw the instructions in post 121 but they refer to older versions of this ROM (0.1.3 & 0.1.4) which i cannot find

flashed the lastest version by using ODIN to revert to 3.0.1. then fastbooted into recovery, wiped cache, tried to flash ROM with stock recovery -- got an error.

so booted into CWM, wiped data and cache again, flashed ROM and after about 10 minutes I had the Bonsai Rom booted up fine (the next boot would not go so well). I setup google and all of my market apps began restoring. after everything "cooled down" on the tab, I tried to reboot with no luck.

So I am currently stuck in a helluva bootloop. I tried using ODIN to get back to 3.0.1 but even after using that I get in a bootloop.

Any advice or ideas as to why I'm stuck in a bootloop and how to get out of it?
[Galaxy Tab 10.1 Android Development] torremitsu:
Me too :( I'll let you know if I can get mine going again.

Guys be careful with this rom.
[Galaxy Tab 10.1 Android Development] torremitsu:
You have to go completely stock, you will lose everything on your SDCARD. Flash 3.0.1 with ODIN and before you reboot get into stock recovery mode. Wipe data factory reset and wipe cache partition. Also make sure you are not plugged into your computer while it's rebooting. Fixed the issue for me.
[Galaxy Tab 10.1 Android Development] ralexand:
That's how I did it on mine, but still got the issue. Is yours I/O, because the uncontrollable bootloops seem to affect only the IO tabs. Thanks for the help, though!
[Galaxy Tab 10.1 Android Development] ralexand:
I was able to get out of the bootloop.

After my initial attempts of simply reflashing through ODIN with no success, I fastbooted into the STOCK recovery and did a data wipe. From there I immediately booted into download mode to re-apply ODIN and it was successful.

Good luck!
[Galaxy Tab 10.1 Android Development] Dupontrocks11:
Thanks man, it looks great.
[Galaxy Tab 10.1 Android Development] Jaydawgx7:
The Bonsai 0.2.0 w/Touchwiz may have ruined my Tab today. Just though I should warn others out there. It froze while on standby, and got insanely hot. I could barely touch the thing. It was cooking itself inside my samsung case. When I first turned it on, there was a big chunk of the screen that didn't work, but by the time it started up it was all working fine. Now, everything seems to be operating ok, but i notice the screen looks wavy when theres a white background. It also drained the battery down 4% (from 100% with 0 use) in a matter of hours. I really don't know the exact cause, but it is the kernel or the rom.
[Galaxy Tab 10.1 Android Development] hshah:
When you say a big chuck didn't work, was it like white noise / static?
[Galaxy Tab 10.1 Android Development] SS2006:
can u update this with the latest update that allows Google movies to install and play

we cant do a system update cause were not stock

also android 3.2 netime soon?
[Galaxy Tab 10.1 Android Development] torremitsu:
I agree, this rom is dangerous
[Galaxy Tab 10.1 Android Development] torremitsu:
Have you noticed any lasting affects? after dodging the bullet with this rom I installed another rom from a different dev. Its been days and all of a sudden I'm getting endless bootloops again.
[Galaxy Tab 10.1 Android Development] drae52:
I've had no issues with Bonsai, beyond having to clear cookies in chrome to sign into his website.

I've been running bonsai since the first iteration without a hitch. Both the Touchwiz and the Stock Honeycomb versions.

And it's FAST. Just don't be lazy, install it in CWM NOT Rom manager.
[Galaxy Tab 10.1 Android Development] Roadk1ng:
+1 been running since the becoming with the basic static screen issue at start. I also didn't use Tom Anger to flash and will neveruse it to flash anything.
[Galaxy Tab 10.1 Android Development] Randy_T:
I think it is unfair to blame the ROM for your experience. Your experience is unique whether you accept that or not. I have run and continue to run every ROM I put out and am putting it through far more stress than the average user doing dev on it. I've not once had any experience even close to the one you describe.

It is far more likely that shoving the tablet in a bag with the screen not properly shut off, or a runaway app would produce the results you have described. It would be more helpful to me and other users if you would take the time to gather some data about what was happening rather than making accusations that are really based on nothing conclusive.
[Galaxy Tab 10.1 Android Development] drae52:
Randy, I'd just like to say;

Thanks. Great ROM.
[Galaxy Tab 10.1 Android Development] rainby:
Used the latest rom w/wo tw, both are stable and responsive. Oc = 1.2 interactive I got score 2500 and am very happy.

Salute, randy!
[Galaxy Tab 10.1 Android Development] Dupontrocks11:
Bug report (maybe): Online YouTube videos are not loading (on Facebook mostly) even with the latest flash. Thanks.
[Galaxy Tab 10.1 Android Development] nakedninja42:
delete... wrong thread :(
[Galaxy Tab 10.1 Android Development] ralexand:
I've been okay since I was able to reset via ODIN. I once I got it to boot after ODIN, I flashed a CWM backup of a TWUX ROM. No issues at all.
[Galaxy Tab 10.1 Android Development] rainby:
So what is new for 0.30 w. Tw?
[Galaxy Tab 10.1 Android Development] BlackOtaku:
I have. I flashed back to my stock backup and I still have the boot lag from Bonzai. Can someone please tell me what partition I need to reflash to get my Tab back to normal here?
[Galaxy Tab 10.1 Android Development] smalis:
Is there a way to change the battery icon to the battery gauge, like in the photo below? Can I use the UOT kitchen for this, or does UOT only work with Froyo and GB, and not HC?

TY.
[Galaxy Tab 10.1 Android Development] DustinDD:
I loaded Bonsai without TW, it was awesome but when I switched to the TW version it was laggy and unresponsive all around the UI. I switched back to stock by wiping data, cache, and flashing the stock 3.1 OTA through CWM.

I had the weird scrambled boot thing before (http://i.imgur.com/FxiOU.jpg) , and it's still there even after switching back to stock. I'm running stock fine, but the boot thing just annoys my OCD. Any way to fix it? :confused:

Probably will switch back to non-TW Bonsai soon. Don't know why TW was so laggy, stock TW was fine.

EDIT:Flashed Bonsai non TX, scrambled boot is still there. Is that happening to everyone?
[Galaxy Tab 10.1 Android Development] hoodoomagic:
As far as I know the only guaranteed way to get rid of the scrambled boot is to make a nandroid (if you want to go back to bonsai), flash 3.01 OTA, flash stock recovery, factory wipe, flash cwm, restore nandroid.

The key part is the factory wipe using the stock recovery. For some reason CWM doesn't quite do the job with some problems.
[Galaxy Tab 10.1 Android Development] DustinDD:
Yeah I followed that guide, but when I tried to restore the backup i got a md5 mismatch error. Any idea why that happened? I made sure there were no spaces or anything in the folder or file names, I didn't change any names really.

Do you know if there are any fixes planned for this?
[Galaxy Tab 10.1 Android Development] Jaydawgx7:
Ok. I understand each device may handle things differently, so you saying you haven't experienced anything similar to what I did doesn't say much. There are many people who run many roms and kernels with extremely different results. The fact is, I performed a complete factory reset (odin and all), and had a clean install of this rom, and my particular outcome ruined my tablet. I am not the only one who experienced this issue with the tab, I'm just the only one (from what i've read) that happened to have it in a place where it had no chance of cooling off while it was in a sleep of death draining my battery.

That being said, I'm not trying to accuse the developers of ruining my tab. I understand there are risks, thats why I purchased the warranty from best buy. I truly appreciate devs working on this device, and wish I could've had more information to help out. The fact is, I don't and I am only stating the problem I had to warn others. Maybe had I read my own post prior to going to the airport, I'd have not casually put my tab in my bag and would have made sure there weren't any glitches for a longer period of time before I trusted it. The rom may run great on your tab and plenty of others, but you just never know how a particular device is going to handle it. I do not want to cause people not to try your rom; even I will probably try it again on my new tab. I just wanted people to know what happened in my case, no matter how isolated it may be, just so they are careful. I'm disappointed that I'll have to go a month without my tab while I wait for the warranty exchange, I'd hate for someone to have to lose their tab completely.
[Galaxy Tab 10.1 Android Development] Ingenium13:
CPU usage

After updating from Bonsai 0.1.5 to 0.3.0, there's always an android system process using 30-50% CPU. Which process it is varies (only one of them does it per boot, but there is always one), but it's either DRM Protected Storage, Media Storage (or a similar name), Media Downloader (or a similar name). There may be one or 2 more, but they seem to all be related to content/app/media storage. I can kill the process but it comes back about 10 minutes later. It doesn't usually appear until 10 minutes or so after booting.

I at first upgraded to 0.3.0 without wiping data, but I have since reverted to my backup of 0.1.5 (and verified that this CPU issue did not exist) and re-installed 0.3.0 but wiped data in addition to cache and dalkiv. I thought that it was something to do with my apps and not wiping data, but the issue is still there.

Is anyone else having this problem?
[Galaxy Tab 10.1 Android Development] DustinDD:
How can I check my could frequency accurately? I edited the file to 1200000 and it saved successfully after reboot but quadrant says its running at 1000mhz.
[Galaxy Tab 10.1 Android Development] PhantomHacker:
OS Monitor or System Panel.
[Galaxy Tab 10.1 Android Development] Jaydawgx7:
This is a permissions issue. I had the same problem. Download es file explorer (or possibly root explorer, haven't tried it). navigate to the /system/etc/init.d/24-cpufreq file. Long press on the file and scroll down to "properties" and hit "change." Then select the all tick boxes for read, write, and execute. Should solve your problem and let you hit 1.2Ghz
[Galaxy Tab 10.1 Android Development] DustinDD:
Thanks for the help, successfully hit 1.2ghz. How has it impacted battery and performance for you?
[Galaxy Tab 10.1 Android Development] Jaydawgx7:
No problem. To be honest, I've switched roms and kernels, OCed and not so many times its really hard to say. However, the battery life on this device is quite impressive, and even running at 1.4, i haven't noticed a decrease in battery life.
[Galaxy Tab 10.1 Android Development] rtoussaint:
Had to do a factory reset after flashing due to numerous FCs, but after that it's running like a charm.
[Galaxy Tab 10.1 Android Development] nj777:
hi,

I just installed Bonsai 0.3 TW, and I am stuck at Samsung Logo after restarting from recovery. How long it should ~ be to boot?

I am past 30 min now and getting worried.

Pls help!

Edit: Never mind took ~ 45 min to boot :) happy now, will be testing...
[Galaxy Tab 10.1 Android Development] yungfresh:
For those running TW version of bonsai, how is the battery life and is there plenty of lag still? does both kernels work for tw versions?
[Galaxy Tab 10.1 Android Development] verusevo:
Just wanted to say i love this Rom. but was just curious to know is there an issue with BT on this rom. Ive been tying to connect my wiimote to my tab as i would using the stock rom and the wiimote conectionapp. But wheni try to conect it under bonsai nothing happens. No errors nor any conections. Not sure why this is.

Edit noticed this is the same for transferring files. I paired my evo with the tab and it tells me that its sending the file to the tab. But the tab doesnt respond in any way that tells me it recieving the file. Plus on my evo it says " paired butnot conected"
[Galaxy Tab 10.1 Android Development] MagicOnline:
just flashed bonsai 0.3.0 from stock.

how long does the first boot take?

i have the glowing samsung logo for 5-10min at least .... :confused:

Edit: NM, after flashing stock TW rom I reflashed bonsai. now its running. thanks anyway.
[Galaxy Tab 10.1 Android Development] IXIKelsonIXI:
I'm experiencing a problem, and I'm not sure if it is a kernel issue or a rom issue. Which I guess doesn't matter, since the kernel I am using came with the rom. When I lock my tab and leave it for an extended period of time, maybe ten minutes or so, and I come back, my Wi-Fi is dead. It isn't disconnected, as I have checked the settings to make sure wifi is set to never sleep. I even installed advanced Wi-Fi lock. Nothing seems to change it. When I come back to the tab, the Wi-Fi is still connected, and signal strength even changes. But the color of the Wi-Fi icon is grey. I have to disconnect and reconnect to my network every time. Has this been discussed? I'm assuming it is a kernel issue...but idk.
[Galaxy Tab 10.1 Android Development] Breezer23:
Version 0.3.0 is out on the Bonsai4Android website

http://bonsai4android.com/content/bonsai-operating-system-rom-v020-samsung-galaxy-tab-101-touchwiz

EDIT: Apparently this is old news I would have known had I actually read any of the posts here... Haha!
[Galaxy Tab 10.1 Android Development] FordTaurus:
I installed this awhile back with no issues. Like others I did have to manually reboot after it hung at the last step.

I did have the color static strip during boot, but it didn't seem to slow things down appreciably. Oddly enough after a dozen or so reboots it went away.

Looking forward to future developments.
[Galaxy Tab 10.1 Android Development] StuMcBill:
Can I install the Non-TouchWiz on my P7510, which currently HAS TouchWiz without wiping Data?

Just so I keep my App's etc?

Stew
[Galaxy Tab 10.1 Android Development] killer23d:
Titanium Backup works very well, just backup your own apps but not the system apps.

If you do not want TW, you need to install the OTA Update, otherwise the current KMB is the latest (see Doc's post) with TW.
[Galaxy Tab 10.1 Android Development] quinn12:
Play it again Sam

NM i figured it out. Fast.
[Galaxy Tab 10.1 Android Development] Sharky444:
Is sweeping TW pages with this rom as laggy as with stock?
[Galaxy Tab 10.1 Android Development] cotvi:
Does it work right click on RDP on this ROM?
[Galaxy Tab 10.1 Android Development] djrajir:
yeah you might have to odin again, but thanks for trying again it gave me some insight on a possible issue. please check your messages on the forums here.

Before using odin you can try to wipe cache and dalvik
[Galaxy Tab 10.1 Android Development] tiny4579:
I'm curious if this ROM has the keyboard lag experienced in the stock 3.1 honeycomb ROM.

For those wondering about the long initial boot, that is because it is deodexed and it has to rebuild dalvik cache at boot.

I have not flashed yet but am debating it. Is it using the pershoot 7/2 kernel? I could not find any info in the thread or on the developer's site about which one. Also, if it is not and I flash pershoot 7/2 over it would I lose the voodoo sound?
[Galaxy Tab 10.1 Android Development] djrajir:
straight from the dev.

As for the keyboard lag yes its still there but only in the browser

As for voodoo sound
[Galaxy Tab 10.1 Android Development] tiny4579:
This post pushed me to try it. I followed directions and unfortunately it started bootlooping.

EDIT: Reflashed and same issue. I think the cause is voltage-related.
[Galaxy Tab 10.1 Android Development] djrajir:
could be, can you post some details about your tab version, size, bootloader status.
[Galaxy Tab 10.1 Android Development] tiny4579:
It's an unlocked retail Galaxy Tab 10.1 16GB edition silver. Bootloader is unlocked.

Now, I'm having a more serious issue. I can't restore my nandroid due to error read-only filesystem. It only succeeds in restoring system but still bootloops.

I usually wipe data before restoring nandroids but is not wiping data here the cause of the error in recovery.log?

I attached last_kmsg and recovery.log.
[Galaxy Tab 10.1 Android Development] DroidHam:
Shouldnt the OP say something about all the bootlooping? Might save some people....
[Galaxy Tab 10.1 Android Development] djrajir:
Ok i will pass on your logs to the dev, as for getting it restored you might have to use odin

however I have the feeling you just confirmed my suspicions about what has been causing some of the bootloops some users have been experiencing.

as soon as i can confirm this with the dev I will post a fix here in the OP
[Galaxy Tab 10.1 Android Development] djrajir:
its in there but its not as detailed i plan on making an edit on it soon.

keep in mind the bootloops are not common even though you see them posted in the forums, the number of successful installs far exceeds them.
[Galaxy Tab 10.1 Android Development] tiny4579:
Can you add this to the OP?

An ODIN restore was not enough. I had to wipe data from stock recovery and was then able to boot.
[Galaxy Tab 10.1 Android Development] djrajir:
I am starting to wonder if CWM is not mounting partitions like its supposed to.

there is no reason you should have had to wipe with stock recovery.

I have been talking with the dev and he has a new compile on the kernel that should fix this I will update the OP when he has it posted
[Galaxy Tab 10.1 Android Development] EvoXOhio:
I have edited that file with root explorer, saved the file, but then when I reopen it my changes are not there. The date stamp of the file doesn't reflect the changed date either. What am I doing wrong?
[Galaxy Tab 10.1 Android Development] tiny4579:
Thanks!

While it is frustrating to have to fix a tab or phone that's bricked or seems bricked, I learn a lot more about the devices that way.

EDIT: Appears to be working fine now. Do you think reflashing CWM from ROM manager without erasing previous recovery could have been the cause of my issue? Or is it just related to the way the ROM flashed that broke my system?
[Galaxy Tab 10.1 Android Development] djrajir:
using init scripts can get a bit confusing, I edited my review to include a free app on the market called OS Monitor that you can use to change the profile and frequency of the CPU.

When you install the app its in the Misc tab, this differs from apps like setCPU because it adjusts the systems governor and doesn't try to use its on.
[Galaxy Tab 10.1 Android Development] djrajir:
Do you mean you have Bonsai working or the stock rom is back up and running?

Either way I'm not sure about the recovery, I was under the impression that flashing recovery via rom manage was not working correctly.
[Galaxy Tab 10.1 Android Development] EvoXOhio:
I've tried osmonitor, but the setting doesn't persist through a reboot. There is an option to set it on boot but its grayed out. I have enabled root mode so not sure what the issue is.
[Galaxy Tab 10.1 Android Development] tiny4579:
I have the stock rom with pershoot 1.4 GHz kernel running. I did a successful nandroid restore after my previous process. I think I might have been ok with reflashing recovery via nvflash. I forgot about RM's manual override. I will try Bonsai once more now that I know CWM can restore. That way I'll know for a fact if if was the RM CWM flash that caused my issue in the first place.
[Galaxy Tab 10.1 Android Development] djrajir:
That would be awesome would really like to know the results of that.

Worst case is you will have to go though odin again.
[Galaxy Tab 10.1 Android Development] djrajir:
yeah that is true, i'm not sure why your init script isnt saving unless you had union filesystem mounted over /system
[Galaxy Tab 10.1 Android Development] mark1962nc:
The first time I flashed recovery through RM and got stuck on the gt 10.1 logo, restored my backup then reflashed through CWM and it worked!
[Galaxy Tab 10.1 Android Development] tiny4579:
Already bootlooping. Darn.

Reflashed CWM. No dice. Odin time.

Also here is my mount command from recovery after the system breaks and mounting /data.

~ # mount

mount

rootfs on / type rootfs (rw)

tmpfs on /dev type tmpfs (rw,relatime,mode=755)

devpts on /dev/pts type devpts (rw,relatime,mode=600)

proc on /proc type proc (rw,relatime)

sysfs on /sys type sysfs (rw,relatime)

/dev/block/mmcblk0p5 on /cache type ext4 (rw,nodev,noatime,nodiratime,barrier=1,

data=ordered)

/dev/block/mmcblk0p8 on /data type ext2 (rw,relatime,barrier=1,data=ordered)

Notice that /data is ext2.

I tried restoring boot.img and rebooting into recovery but same issue. Even a manual format won't wipe data.
[Galaxy Tab 10.1 Android Development] EvoXOhio:
I got the setting ungrayed so I am able to use osmonitor now. Its not updating the init script though and the tab fells and benchmarks slower then when I set the same settings via setcpu.
[Galaxy Tab 10.1 Android Development] Framedtrash:
flashed this last night and have had no dramas apart from the corrupt looking boot screen

just take note that if you dont want to have to reinstall all your apps dont do a full wipe just wipe the cache and dalvik before flashing the rom

cheers
[Galaxy Tab 10.1 Android Development] djrajir:
Ok I am not sure what is causing this, it seems to only be happening to a select few users, the dev has a few ideas and is working on finding the solution.

Any information that you think might be relevant is welcome, however untill we find the thing all these users have in common it might take a while.

Information like the method used to get root what you did to flash CWM and recovery logs from right after the flash all would help. Also list the tab version you have size, retail or i/o version, locked unlocked boot loader, even color and where you got the cab couldn't hurt.

Even logcats if you have them from when you are trying to boot.
[Galaxy Tab 10.1 Android Development] bodiecon:
google i/o tab.

rooted with this link originally (i believe) - http://goo.gl/jrYvl

3.1 HC with this method - http://goo.gl/QcEpq (pershoot's)

had some issues with cwm but pershoot made adjustments and got it up and running. it wouldn't restore backups.

was running stock kernel.

currently, i went back to 3.0.1 unrooted and did the ota 3.1 through samsung

rooted with pershoot's zip from droidbasement

pushed cwm 4.0.0.4 from pershoot.

that's where i sit now. haven't done a lot in case you need me to test.