yashsingh1/xdaforums huggingface dataset:
[Motorola Droid Bionic] nobe1976:
That cannot be the reason since there was 2 TIBU folders that I had in place. The newer of the 2 I left on the internal and the 2nd one was a older one I created awhile back which I left on the external storage for safe keeping. I run a tablet with both 4.1.2 and also 4.2.2 and on both of them the backup had to be on the internal storage in order to have TIBU see them. That is how TIBU is setup because most smartphones out there only have the single storage area. Even if it is a SD card that is there main storage. Hell I even went a bit further into it and tryed restoring from a nandroid backup and it saw the TWRP folder with the ROM slots, but once I started the restoring process it force closed and crashed TIBU. That is why I ended up just using the update.zip method with TWRP and just disabled the flashplayer app after everything settled in.
[Motorola Droid Bionic] codygs83:
Re: [ROM][JB] [4.2.2] Avatar ROM for Motorola Bionic (targa) - Updated [Mar 26,2013]

Wow. I dunno man. Ive always moved them to external SD and tibu picks it up. There's also an option in tibu to select where u want to backup and restore from. I've never had this problem you're talking about though. Any jb roms I've ran will see backups on the external SD.
[Motorola Droid Bionic] nobe1976:
I figured it out. It seems that the directory was created and the backup was there, but for some reason or another the directory was empty :silly: . Went ahead and guided myself to the sdcard-ext and copied the 2nd backup to the internal storage and bam TIBU was back in business. It is still strange that when using ES file browser that both external and internal storage show up as sdcard0 where in the fstab that the internal is mounting as sdcard0 and external is being mounted as sdcard-ext. Just got to be cautious on which one I choose in ES when I start moving stuff around. Thanks in Advance.:cool:
[Motorola Droid Bionic] bippi79:
ChangeLog (Mar 31, 2013)

03/31/2013 - AvatarROM 2.5b Release

Latest CM 10.1 code merges for 2.5b release(upto Mar 28th 2013)

Included new theme chooser based on Aptoide(Alpha release)

Lockscreen - Enable/Disable vibration when unlocking from settings -> Lockscreen -> Screen Security -> Vibrate

Launcher - Option to edit workspace in menu

Weebo - Bug fixes and now you can create your own rules (see - http://avatarrom.com/weebo-rules/)

OTA - Full support from client side. Next update will be via OTA.

General bug fixes
[Motorola Droid Bionic] tw1n5nak35:
Re: [ROM][JB] [4.2.2] Avatar ROM for Motorola Bionic (targa) - Updated [Mar 31,2013]

Thank you for the update.. Will give this a try :D

Sent from my Icarus HD Bionic using Xparent Skyblue Tapatalk 2
[Motorola Droid Bionic] chrisp6825:
Re: [ROM][JB] [4.2.2] Avatar ROM for Motorola Bionic (targa) - Updated [Mar 31,2013]

Very cool, this project is very impressive, I can't wait to try.

The weebo thing is interesting, I could imagine an easily made export/import from tasker.

OTA updates sound pleasing as well. I see no reason so far this wouldn't be my new daily driver.

BTW, I know it's early but you've got a lot of typos and mistakes in your weebo web page.

And I'd love to be able to flash this in another ROM slot.
[Motorola Droid Bionic] merlin3:
Installed this a couple days ago and it has been working great and fast till this morning. Twice now after the device goes to sleep it will not wake back up. I push the power button to turn screen on and only the bottom 4 buttons light up and i have to pull battery to get it back on. Any help?
[Motorola Droid Bionic] tw1n5nak35:
Just finished flashing. I like the ability to swap and change themes very fast. The optimus prime theme looks fantastic. GPS lock issues as from CM 10.1 remain here as well but it's no biggie. I'm going to play with the themes for a little bit. Thank you for this rom :D
[Nexus 4 Q&A, Help & Troubleshooting] anto.danny:
1.wifi stops at obtaining ip address

2.wifi stops responding when the phone goes to sleep

solution I've taken for the time being

1.set up a static ip

2.keep the screen on until the download completes :crying:
[Nexus 4 Q&A, Help & Troubleshooting] FSRBIKER:
There are some threads relating to this issue as it's in the Android code but doesn't seem to affect everyone. I'm using WiFi Fixer app currently to hold the connection until Google fixes the deep sleep issue.
[HTC Flyer, EVO View 4G] Douglasarah:
I HAD this info on the hboot screen

****unlocked****

flyer pvt ship s-on

hboot-1.11.0011

microp-0950

radio-3822.10.08.07_m

emmc-boot

After I found the correct RUU, I was able to follow globatron's instructions to downgrade to stock Gingerbread. The device booted OK into Gingerbread.

I then got S-OFF with Revolutionary and upgraded to Honeycomb by running ARUWizard.exe in RUU_3G_B09.zip. The device then booted OK into Honeycomb.

I then flashed DextersJB18 and gapps-jb-20121011-signed.zip.

The device now boots into Jelly Bean! But i dont have wirless connection. It searches for wifi but dont find nothing.What should i do?
[HTC Flyer, EVO View 4G] AlexusR:
Hi,

do you have a hidden wifi network? If yes, I have the same problem. But if you have a visible wifi network, it should work.

The flyer finds my wifi network, when it is not hidden and I can use it. As soon as I hide the network in my router, the flyer is disconnected and cannot use the network. I tried several things in the wpa_supplicant.conf, but without luck. I only can use visible networks.

Greets

AlexusR
[HTC Flyer, EVO View 4G] cacthanian:
I think you should come back to GB and S-OFF by revolution :)

Don't use RUU now, you must be flash boot.img.... (please see it on Flyer android development)

After S-Off, you upgrade your flyer to HC and check your wifi function. If it work fine, you upgrade your tablet to JB

Pray for you :)

Sr my English don't well
[Verizon Samsung Galaxy Note II] Mandolin Bee:
The short of it is during my attempt to use the CASUAL one-click, it failed to do... something, and said my phone should be rebooting. It isn't.

Basically, I am stuck with my phone saying "Downloading... Do not turn off target !!" I have no idea what to do, and am scared to death I have done something unfixable.

For the record, I did find people who reported this problem in the development thread... but if they were answered, it must have been in jargon that I am not familiar with. Half the time I cannot tell what people are saying in that thread, I am just not well informed enough with what's going on to follow everything. So please don't get too upset with me for posting.... I need a fairly plain english explanation of what I can do...

I wasn't sure if the log would be helpful. Here's a chunk toward the end of it. If having all of it is better, I can do that.

Driver Problems suck. Lemme make it easy.

1. Check that your device is download mode and connected up.

2. Select the one that says ---Gadget Serial--- in the main window

3. Click ---install driver---.

4. Close out zadig and use CASUAL.Note: the USB port which you install this driver will be converted

to use Heimdall instead of Odin for download mode. It only affects

ONE usb port.

Open-Source Heimdall Drivers...21504kb Open-Source Heimdall Drivers config...8kb Heimdall v1.4 RC2

Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna

This software is provided free of charge. Copying and redistribution is

encouraged.

If you appreciate this software and you would like to support future

development please consider donating:

Initialising connection...

Detecting device...

Claiming interface...

Setting up interface...

Checking if protocol is initialised...

Protocol is not initialised.

Initialising protocol...

Releasing device interface...

ERROR: Protocol initialisation failed!Your device should be rebooting into Android now.

Mandolin

==================

EDIT: OK, so I got impatient and took a leap of faith that I was reading the forum correctly.... I popped out the battery, disconnected the cable, replaced the battery, and plugged it back into the pc and hoped that it booted, then appeared to finish the process. However, when trying to run GL to SD, an app that requires root access, it said I don't actually have it.

What should I do? How do I know if CASUAL changed anything? Do I need to do anything before trying again?
[Verizon Samsung Galaxy Note II] ml3000:
Having the same issue, can anyone help?

Weird? after about the 10th try today and on two seperate computers, it worked
[Verizon Samsung Galaxy Note II] MPeterson21:
You can download Rootchecker from the play store to verify root. Also generally if you can't open a root only app, you are not rooted. Sometimes you have to try again. I would redownload the file and start over. Sometimes you can get a corrupt file. Also it's good practice to reboot your PC as well.
[Verizon Samsung Galaxy Note II] Mandolin Bee:
Sorry for being ignorant on this. I get that the root failed, but... I really don't want to end up with a broken or bricked phone. Is just re - running it "safe"?

Or do I need to somehow make sure the previous attempt didn't leave anything behind first? And should I be concerned at all about why it may have failed the first time?
[Verizon Samsung Galaxy Note II] droidstyle:
if ya just want root then odin root66.
[Verizon Samsung Galaxy Note II] Mandolin Bee:
Not to be terribly impertinent, but you may as well have just suggested that I smackerdip the hallywagon.

If it hasn't already been made pretty evident by my previous posts, I can't seem to wrap my head around mobile jargon in this respect. As far as I have been able to tell, there's no way to "only" want root to start with, you MUST both root and something else or I will get some kind of evil triangle (and if I do, is that bricked?)

All I really want to do is be able to move apps onto my SD card, and everything I can find says I must root my phone for that.

I'm sorry if it's irritating for some that I really need people to reply without assuming some kind of prior knowledge. I'm pretty tech savvy in general, but this whole mobile thing is new to me, and nothing I ever tried to do on my PC was going to potentially cause me $700 of irreversible damage. So if anyone could just take the time to treat me like the mobile noob I am and not just throw words at me like I am supposed to know what they mean or what to do with them, that'd be appreciated.

Thanks.
[Verizon Samsung Galaxy Note II] buckman341:
I'm pretty new to this too, at least new to this phone. I rooted my Thunderbolt but that was pretty easy compared to the Note it seems. I spent a considerable amount of time last night researching this stuff and I have gone from 'extremely limited' to 'somewhat capable.' Takes a bit of time.

What droidstyle is suggesting is that you use the Odin app (lots of links on this forum) to load ROOT66 factory image, also known as the "alternate restore file", to your phone. root66 does not attempt to modify the bootloader (harder to do with note2 due to verizon).

Read this for some more information: http://xdaforums.com/showthread.php?t=2196891
[Verizon Samsung Galaxy Note II] MPeterson21:
No one will ever tell you that rooting is 100% safe. Of course you are taking risk but if you follow the walk through you should be fine. When I first rooted/unlocked I had issues completing it, and I had to re download and start over. It should cause no harm as long as you follow the steps.
[Verizon Samsung Galaxy Note II] Lepryy:
Dude. I have the EXACT same thing right now. Still stuck on this screen and I have no clue what to do. Anyone PLEASE help me.

EDIT: here's the Casual log:
[Verizon Samsung Galaxy Note II] Mandolin Bee:
It's scary, right? Here's what you do:

LEAVE THE PROGRAM ON!

1) Disconnect the usb cable from your phone

2) Open the back cover and pull out the battery

3) Put the battery back in

4) put the cover back on your phone and reconnect the usb cable

5) hold your power button until it starts booting

OK, now the program will take over again and look like it's installing things. I don't know what it's actually doing, but at some point, it will tell you that "you should be rooted now".

Then you'll end up on some screen that also looks scary with some options for rebooting. I picked the one that was closest to "reboot normally", and my phone booted up just fine.

However, my phone was NOT actually rooted..... but at least it isn't a brick.

Now I am trying to figure out if it's safe to try this whole process again, but I can't get a straight, non-jargon answer out of these people.
[Verizon Samsung Galaxy Note II] Mandolin Bee:
In fairness, I'm not looking for anyone to tell me it's 100% safe. I'm looking for information that to most of the people around here is probably considered "common knowledge". I'm admitting I lack any level of "common knowledge" when it comes to mobile technology.

Like.. it may be "common knowledge" that if the CASUAL one-click fails, you have to go in and delete files x, y, and z before retrying or you might brick your phone. Or perhaps you need to go and make sure directories a, b, or c didn't get renamed/deleted/copied/turned into cake.

There's any number of things that I should perhaps need to "be careful" of now that I have attempted to root my phone, but failed.... or perhaps there is NOTHING I need to "be careful" or watch out for. That's what I want to know.

You know... like if I show back up and say "I followed the directions and now my phone doesn't work at all!" and someone comes along and says "Well, did you do it more than once without doing a factory reset between attempts? You shouldn't have done that."

I'd rather avoid such a dialog, tyvm. Hence, I am asking if it is "safe" to run the program again, meaning am I running the -same- risk as I was for attempt number 1, or is a second attempt likely to screw me over harder because I didn't do something ELSE first?
[Verizon Samsung Galaxy Note II] Lepryy:
Thanks dude. In another thread I asked the same question. You and I should be at the same point right now. I ran the process again and, it worked perfectly. I would go ahead.
[Verizon Samsung Galaxy Note II] FitchVA:
big high-5 to you my new friend. this saved me. thanks! :highfive:
[Verizon Samsung Galaxy Note II] omegamerc:
Thanks, had the same issue, saved my phone :) :laugh:

Keep getting this error trying to do this root - doesn't seem successful.

Downloading device's PIT file...

PIT file download successful.

Uploading BOOT

0%

ERROR: Failed to send file part packet!

ERROR: BOOT upload failed!

Ending session...

ERROR: Failed to receive session end confirmation!

Releasing device interface...
[Verizon Samsung Galaxy Note II] dannymac77:
Blargh, unfortunately pulling battery soft bricked me. I got stuck at same spot the OP did. Kept app running, pulled USB, then battery. Put battery back, then plugged in and powered on. CASUAL ran thru the rest of it's script, obviously failing at certain points as OP mentioned, but then mine got to:

Beginning session...

This device may take up to 2 minutes to respond.

Please be patient!

Session begun.

Downloading device's PIT file...

PIT file download successful.

Uploading recovery

0%12%25%37%50%62%75%87%100%

ERROR: Failed to confirm end of file transfer sequence!

ERROR: recovery upload failed!

Ending session...

ERROR: Failed to send end session packet!

Releasing device interface...

It again hung in Download mode for several minutes, so I tried the same trick as above, unplugged, removed battery etc but mine is doing a fast loop on the Samsung Galaxy Note 2 screen. Will pop up for about 1 second, reboots repeat. This is actually the original reason why started this journey. URL of my story: http://xdaforums.com/showthread.php?t=2264319 as you can see OP I too struggle with getting the answers I need LOL.

I'm going to restore to stock and will just root with the APK and give up hope for now of custom recovery and ROMs. One thing I could ask, though i seems you did a good job of following instructions was if you did enable USB Debugging.

Try a restart of PC, etc. I believe you said in a previous post that you were just looking for root. If that is true and you don't want a custom recovery or ability to install ROMS, and just want root access to uninstall and move app's. Reply back to thread, there is an application you can launch from the phone itself that will give you root. Just don't make mistake of trying to install the recovery or roms as you will get a nasty VZW has bricked your phone for unauthorzied software. Easily fixed but highly inconvenient as it requires restoring to Stock aka hard reset
[Verizon Samsung Galaxy Note II] USHwy129:
What application are you talking about here? Can you give some detail? I really only need root as well, just to get all the VZW bs out of my face and run droid wall.

I attempted CASUAL and it hung at the exact same spot as OP, "protocol initilisation failed". I unplugged phone, pulled/replaced battery, powered on and the phone started normally and has worked perfectly since (week ago).

I got a few helpful hints but no one knew exactly the problem, I think one of the few people who could say exactly what has caused it to crash there is the original developer, and they don't seem to watch these details. One person did suggest I try a different USB cable, and I've noticed bad cables have caused problems for many people on here. Haven't tried yet. I have rooted a few Droid Xs before, but I am tired of people on here with the "oh its easy, perfect, run CASUAL it's great, I've run it 1,583,000 times and never had 1 problem". I don't have time anymore to waste hours trying to recover my phone.
[Verizon Samsung Galaxy Note II] Chance77:
Im pretty sure casual is not working on the ota 4.1.2, you probably have to wait till Adam updates casual bevause of recent update, also wont work on windows 8
[Verizon Samsung Galaxy Note II] craigbailey1986:
Adam himself said it does work...
[Verizon Samsung Galaxy Note II] ccllabel:
I have tried three different computers and nine different USB ports......three different USB cables as well including the OE one. I am rooted but still have the OE recovery. I have uninstalled and re-installed the drives countless times. To my knowledge I am using the latest build of BackAtchaVerizon-CASUAL-Revision465b that was posted late last night. I have also posted many log files.
[Verizon Samsung Galaxy Note II] bladerealm124:
I had the same issue as many others here this past weekend. Initialisation failed and I was stuck in the "downloading" state. I followed the advice of a few others and unplugged and pulled my battery and then rebooted. After plugging back in others stated it would simply continue the process but I had to press "do it" again in casual for it to finish. It took another couple minutes but did root and unlock my bootloader after this. I am now running cleanrom and am thinking about making the switch to beans rom for more customization. Anyone know if build 15 will be out soon so I don't have to wipe twice?
[Verizon Samsung Galaxy Note II] Oh_wow:
I am SO jealous...I'm still looking for a solution! On a positive note, I did verify that my cable is good. After using an upgrade on my account, I now have a new phone and everything worked great. Now if I could just get odin to see the old phone...
[Verizon Samsung Galaxy Note II] Noobism:
I'm actually having the problem where the "Samsung Galaxy Note II" splash screen just loops every second. Been searching online for hours and still haven't found a fix for it

EDIT: FIXED
[Verizon Samsung Galaxy Note II] PeteKT:
Mine fails also, tried 4 computers 5 usb cables and 40+ usb ports now
[Verizon Samsung Galaxy Note II] savagerider750:
So after I did the same thing I found out that if u downloaded the newest update casual root wont work. They're working on the update. All I did was using odin I pushed the PIT file and got my phone to reboot with root just no custom recovery. Ill try to find the link with package and post it. Hope all goes well.
[Verizon Samsung Galaxy Note II] jon2020:
Hi - I'm stuck here too. How did you fixed this?

Thanks very much
[Verizon Samsung Galaxy Note II] Noobism:
Which Casual root version are you talking about? I believe i have 2 different versions (at work currently, will check later today)

Here's how I fixed my problem with the samsung boot loop.

1.Tried unlocking bootloader using Casual.

1a. Casual fails on recovery and doesnt reboot.

2. Battery pull, samsung bootloop every second or so.

2a. Plug device into second computer, will install driver automatically (takes a few min)

2b. Access device with odin off external HDD

2c. Flash PIT/PDA Restore files and reboot.

Should solve the issue of logo reboot. Basically factory Reset is what your doing. You'll be on stock unrooted device.

Just make sre you grab the restore PDA file. That's what gets you back to stock 4.1.1
[Verizon Samsung Galaxy Note II] PeteKT:
Thats what i did but you dont even need the pda file, just flash the pit file and it reboots your phone rooted, but not unlocked.
[Verizon Samsung Galaxy Note II] Noobism:
I did it more as a precaution lol
[Verizon Samsung Galaxy Note II] jon2020:
Thanks! This worked.

No matter what I try I keep getting stuck here(On CASUAL)

Ending session...

ERROR: Failed to send end session packet!

Releasing device interface...

[Heimdall Error Report] Detected:

Heimdall uncontinuable error; Script halted

[/Heimdall Error Report]

I have a verizon galaxy note 2 (White) android 4.1.1

Any ideas?

Thanks for the help guys

---------- Post added at 03:56 PM ---------- Previous post was at 03:40 PM ----------

So if I only use the pit file my phones reboots rooted? That's all I need?
[Verizon Samsung Galaxy Note II] AdamOutler:
[MENTION=4611378]MendonMafia[/MENTION] turn off your virus scanner. Also, please use Pastebin to post.
[Verizon Samsung Galaxy Note II] maxicat1960:
How did you fix yours? I am having the exact same problem. :crying:
[Verizon Samsung Galaxy Note II] gerg004:
Edit: After a few reboots and continious tries it worked! Wish I had some sort of help for anyone else getting stuck at the same place, but I don't really know what I did. Eventually casual just worked for me.
[Verizon Samsung Galaxy Note II] Rootabaga:
I got stuck in Download Mode twice this morning while using the latest nightly R821b. I did as others have done and went back to R515 and it worked. I did have to install drivers on my own though. CASUAL wouldn't even see my phone without drivers being installed prior to running it.