lol....bootloop already..

[beatdroppah]

well i got my Ring about 4 hours ago...got it home, got it rooted and whatnot, put wifi tether on it. it found root, wifi tether worked fine.

ended up doing a TiBu of my apps on my other phone, and then made a nandroid via recovery, and saved it to my sdcard. i then put my SDcard in my Ring, installed Tibu, and restored a handful of apps+data via my nandroid. no system apps or anything special. installed a font from Font Installer app, and rebooted, only to be stuck in a bootloop....

got it into bootloader, wiped cache, wiped data/factory reset, rebooted, still stuck at Samsung screen.. tried several times with SDcard in and with it out.

i know its new, but has anyone ran into a bootloop, and found any fix? pleaseee lol

 

[rbheromax]

If u made a nandroid why can't u restore?

 

[beatdroppah]

If u made a nandroid why can't u restore?

well i said i made it on my OTHER phone...the one i got all my apps from...sooo not gonna help...dont have a custom recovery anyways..

 

[rbheromax]

Okay well adb? Logcat find us error then fix it?

 

[beatdroppah]

dunno how to logcat via ADB....

 

[rbheromax]

Well DL this: http://db.tt/e093WLw0
Unzip to C:/
Open cmd by going to start>run
Type cmd then enter
Type "cd C:/"
then if needed "cd (folder-created-name) "
Then type "adb wait-for-device logcat > logcat.txt"
Plug your phone in powered off
Turn it on
Let the magic happen
Upload that file somewhere then post the link here

 

[beatdroppah]

Well DL this: http://db.tt/e093WLw0
Unzip to C:/
Open cmd by going to start>run
Type cmd then enter
Type "cd C:/"
then if needed "cd (folder-created-name) "
Then type "adb wait-for-device logcat > logcat.txt"
Plug your phone in powered off
Turn it on
Let the magic happen
Upload that file somewhere then post the link here

soon as i hit enter after "adb wait-for-device logcat > logcat.txt" i get access is denied

 

[rbheromax]

If u know how, run cmd as admin then try

 

[beatdroppah]

okay got past that. hit enter, then the next line is blank except for the flashing cursor, then i turned the phone on...should the terminal be showing anything in terms of progress? or does it just stay on the flashing cursor? is it working?

EDIT: yup still sitting there on the flashing cursor. cant stop the process or anything. doesnt appear to be doing anything at all..

 

[rbheromax]

Check for a file called logcat.txt

 

[beatdroppah]

there is nothing. never did anything after i turned the phone on, just say there saying waiting for device in the title bar of cmd, and the last line just has a flashing cursor. didnt say anything, didnt do anything. phone still sitting at samsung screen

 

[rbheromax]

Then your SOL, take it to the store, say u installed some rogue app and they'll replace it

 

[beatdroppah]

awesome

 

[rbheromax]

awesome

Sarcasm at its best

 

[beatdroppah]

Sarcasm at its best

well i'm not exactly thrilled about it...

 

[rbheromax]

Im not u and I'm not happy about it... I'm sad I can't fix it

 

[beatdroppah]

thanks for the concern...i just dont understand how ive only had it for like 8 hours, barely did anything to it, and it just wont boot. factory reset wont even fix it...like wtf.

 

[rbheromax]

Happens to the best of us... Did that before...3 times

 

[beatdroppah]

Happens to the best of us... Did that before...3 times

been googling for like 3 hours to figure out how to make adb work, to no avail. back to the store tomorrow i guess

 

[rbheromax]

Well...when u get a new one, can you get me a system dump (I can walk you through it) so you guys came brick like thism, and you can just flash through Odin everytime u mess up. I wanna save ppl headaches. (I don't own the phone)

 

[beatdroppah]

Well...when u get a new one, can you get me a system dump (I can walk you through it) so you guys came brick like thism, and you can just flash through Odin everytime u mess up. I wanna save ppl headaches. (I don't own the phone)

yeah i just got home from work. about to clean up, then back to bestbuy. hopefully theyll exchange it, and ill be good to go, and when i get back, yeah, help me do a system dump.

i did come across the odin method of unbricking during my googling last night. but quickly realized it doesnt apply, because i have none of the files to push thru Odin, seeing as i had no way to dump the files, and not even a Nandroid.

ahhh Odin, i remember using odin alot back in my Captivate days ill report back soon

 

[rbheromax]

Yeah let's get this done. Lol

 

[Curtis1973]

just going from your post,it appears something from the tibu borked the booting process or odd as it sounds,the font. unless the font was installed direct to system/fonts..I can't imagine how that could have done it..even if it did install to system/font. tibu...who knows. I'm betting somehow the build.prop got changed. is it possible tibu imported something from the other device causing the boot loop? sounds likely to me.

 

[joemossjr]

well i got my Ring about 4 hours ago...got it home, got it rooted and whatnot, put wifi tether on it. it found root, wifi tether worked fine.

ended up doing a TiBu of my apps on my other phone, and then made a nandroid via recovery, and saved it to my sdcard. i then put my SDcard in my Ring, installed Tibu, and restored a handful of apps+data via my nandroid. no system apps or anything special. installed a font from Font Installer app, and rebooted, only to be stuck in a bootloop....

got it into bootloader, wiped cache, wiped data/factory reset, rebooted, still stuck at Samsung screen.. tried several times with SDcard in and with it out.

i know its new, but has anyone ran into a bootloop, and found any fix? pleaseee lol

You could try putting it in recovery and adb works when you do that download my system dump and adb push the font files to the phone font folder that's what I think broke your phone. There's plenty of tutorials on how to do adb

 

[Artine]

just going from your post,it appears something from the tibu borked the booting process or odd as it sounds,the font. unless the font was installed direct to system/fonts..I can't imagine how that could have done it..even if it did install to system/font. tibu...who knows. I'm betting somehow the build.prop got changed. is it possible tibu imported something from the other device causing the boot loop? sounds likely to me.

Those were some of my thoughts as well.

I'm guessing the other phone was the Capivate? My apologies if I misunderstood based on the wording in the OP (I can't really focus too well today either, but meh), but it sounds as though you used both TiBu and Nandroid to restore the stuff from the other phone.

Titanium Backup has been known to have issues when restoring data from one phone to a completely different phone, or even just across different ROMs for one phone. There's a setting in it to help get around this issue, but all in all its very likely that it may have 1.) restored corrupt data, 2.) restored data that corrupted mid-restore, 3.) corrupted the /data partition, or 4.) restored data to the wrong partition altogether. If an uber factory (firmware) reset is available through Samsung KIES, I would have recommended it. Also, some phones have different formats for their partitions (EXT4, yaffs2, etc.).

Any number of things could have gone wrong, but one easy way to circumvent the issue is to have your apps' data be synced with Google directly. Then the apps can be re-downloaded through Google Play, or whatever other App Store you use, and their data restored by re-synching with Google.

Hopefully that's helpful.