Develop Bugs

Boot Manager

I just started using boot manager and after some frustration it appears that I have it working now. I was wondering though after booting into a rom from slot 2, getting the settings, sounds, wallpapers, folders, widgets, etc.. setup will all that stay the same after booting into a rom from another slot or going back to the phone rom and then back to slot 2 rom. Thanks for your help.

scott7044 said:
I just started using boot manager and after some frustration it appears that I have it working now. I was wondering though after booting into a rom from slot 2, getting the settings, sounds, wallpapers, folders, widgets, etc.. setup will all that stay the same after booting into a rom from another slot or going back to the phone rom and then back to slot 2 rom. Thanks for your help.
Click to expand...
Click to collapse
Yes, everything you change/mod/add/delete will save to this slot. I have fully customized ROM's running on each slot and I like to use this as an evaluation for new ROM's.

Has any one had any luck getting skyraider zeus to work with BM. It will install to a slot just fine but it won't boot. I do have the force large boot.img checked.

The only way i got Zeus to work was to load onto phone then restore to a slot on boot manager an it will run fine.Sense roms seem to be more tricky to run with boot manager.

I tried installing a nandroid twice and each time it finished the notification said click here for boot options. I clicked it and it just went back to BM and the only option was to stop install. Any ideas?

Don't mean to hijack, but I get an error when installing cm7, when boot manager is making a boot.img. I already set the setting for larger boot.img. Any body got ideas?
Sent via My Incredible 2 fully rooted and cookie wasted going 110mph. Imma GeeK it, till it MegaHertz™

Make sure logging is disabled in Superuser settings and make sure to turn on "screen on during install" in Boot Manager settings along with the force large boot.img. If both those settings are set like that and it still won't work just keep trying it will after a few attempts. I have struggled with this app but have stuck with it and now I love it. I started a thread in the General section called, "Boot Manager Discussion", I am hoping to get some user support, tips and tricks started like I have seen in other forums on XDA but for other phones.

RRF12 said:
The only way i got Zeus to work was to load onto phone then restore to a slot on boot manager an it will run fine.Sense roms seem to be more tricky to run with boot manager.
Click to expand...
Click to collapse
can you explain how you did this? I am not sure how to restore to a slot. I would like to have MIUI as my phone rom (since you can't get data as a slot rom) and restore my phone rom (bindroid) to slot 3. I looked under all the settings I could find, but can't seem to find the answer.
thanks in advance!

420fan said:
can you explain how you did this? I am not sure how to restore to a slot. I would like to have MIUI as my phone rom (since you can't get data as a slot rom) and restore my phone rom (bindroid) to slot 3. I looked under all the settings I could find, but can't seem to find the answer.
thanks in advance!
Click to expand...
Click to collapse
Install the ROM like normal, (ie: wipe and install via recovery) set it up like you want, backup, and restore the backup of whatever you want to, start up boot manager, then select this option. "restore nandroid"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

So to brake it down, install Rom like normal, make a backup and use that backup to move Rom to a slot instead of being the phone Rom?
Sent via My Incredible 2 fully rooted and cookie wasted going 110mph. Imma GeeK it, till it MegaHertz™

JHumBL3 said:
So to brake it down, install Rom like normal, make a backup and use that backup to move Rom to a slot instead of being the phone Rom?
Sent via My Incredible 2 fully rooted and cookie wasted going 110mph. Imma GeeK it, till it MegaHertz™
Click to expand...
Click to collapse
Essentially yes.

Ok I will try that now
Sent via My Incredible 2 fully rooted and cookie wasted going 110mph. Imma GeeK it, till it MegaHertz™

tylerlawhon said:
Install the ROM like normal, (ie: wipe and install via recovery) set it up like you want, backup, and restore the backup of whatever you want to, start up boot manager, then select this option. "restore nandroid"
View attachment 869251
Click to expand...
Click to collapse
Thanks a lot, I don't know how many times I have looked for this and went right by it. Trying it now.
Edit: Tried that with a sense rom (bindroid) and it hangs at splash screen. Had to do the two finger salute and get back into recovery. hmm. Got large boot.img checked, any other thoughts?

Still not working but every now and again I will try it again to see if it works.
Sent via My Incredible 2 fully rooted and cookie wasted going 110mph. Imma GeeK it, till it MegaHertz™

Besides checking "force large boot.img", also make sure to check "screen on during install" in boot manager settings. You also need to disable logging in the settings of superuser. It was suggested to me and seems to work, use ext2 instead of ext4 as long as boot manager detects ext2 for the rom you want to install to a slot.

JHumBL3 said:
Still not working but every now and again I will try it again to see if it works.
Sent via My Incredible 2 fully rooted and cookie wasted going 110mph. Imma GeeK it, till it MegaHertz™
Click to expand...
Click to collapse
I had a couple of times the boot process stuck at splash screen. What worked for me, in addition to checking the large boot image, disable su logging, screen on during flashing etc- was choosing ext2, not ext4.
The splash screen lingers a little longer than usual, so be patient for a couple of minutes before giving up and pulling battery.
However, after trying a few roms and although boot manager is really cool, I can't say it is different than wiping, flashing a rom and then restoring other roms from recovery- it takes more or less the same amount of time (and sdcard storage).
Also, I noticed that although I have flashed gasps, after boot it didn't recognize them, Boot Manager doesn't like it (don't know why, maybe some licence check? is this really necessary???). So, to revert back to phone rom I always need to go through recovery and flash boot.zip again.
The same applies if for whatever reason with the booted rom one cannot gain Wifi access or data, then BM won't start, back again to recovery.
IMHO it is just a hassle to use, takes too much time, but is nice if one doesn't like to go too much through recovery, doesn't trust rom manager and so on. Or, if one wants to keep several roms and go back and forth between them.
Sent from my HTC Glacier using Xparent Cyan Tapatalk

[Q] Boot Manager stuck at HTC screen?

I am running RCMIX3d on my Telus Desire HD. I downloaded Boot manager and installed cyanagen 7 to the second slot. I installed gapps and clicked button to reboot into new rom. It just hung at the HTC logo and would not load. I copied PD98img.zip to a sdcard to reload in Hboot. and rerooted and flashed back to RCmix. I have it working again but I would like to know: Was there another way of recovering from that and what did I do wrong with boot manager.
Josh

Don't know how many use the Boot Manager but if there is a thread about is you might get a faster answer asking there.

jbplumbing.ca said:
I am running RCMIX3d on my Telus Desire HD. I downloaded Boot manager and installed cyanagen 7 to the second slot. I installed gapps and clicked button to reboot into new rom. It just hung at the HTC logo and would not load. I copied PD98img.zip to a sdcard to reload in Hboot. and rerooted and flashed back to RCmix. I have it working again but I would like to know: Was there another way of recovering from that and what did I do wrong with boot manager.
Josh
Click to expand...
Click to collapse
yeah there is: if you make a nandroid backup before doing anything, the next time it hangs you should reboot to recovery (either from bootloader or with adb), full wipe then restore the backup.
Much easier than going back to stock re rooting and re flashing

htc stuck and not rooted
How about a phone that may not be rooted and will only boot to the HTC screen? Anyway to get this rolling again...bought one like this for parts but...will the PD98img.zip file on an sd card and Hboot work for this? Other options? thanks.

What Rom are u trying to push if I may ask because I have that same problem
Sent from my HTC Sensation 4G with Beats Audio using XDA App

None at the moment...would be happy with any that might get it working at this point. That said I am using ICS Quattro RC2 on my "good" phone and very pleased with it..before my 4.0 trials, the MUIU rom was great...I would probably load the latest Muiu if and when..pretty stable.

I would love to run rcmix3d and cyanogenmod 7. If someone could help me do that it would be awesome.

Think you need Boot Manager from Market...$1.99-cheap...can run up to 5 rom's without having to wipe and format etc between every time. Has 'slots' and you choose which rom to boot

If you would have read all instructions (yeah, there really is something they call "manual"), you wouldnt have to mess up your phone like this
The first time you start BootManager, you need to set up your phone rom. It then creates a folder on your SD (BootManager/PhoneROM). Inside it, you'll find a "update.zip" - whenever you get stuck in an SD ROM, go to recovery and apply that update.zip - and your good to go.
Worked for me a hundred times - when you change your phone rom, remember to set up phone rom in BootManager again.
DN41

I did setup my phone. Then I installed cm7 and had the update.zip but when I restarted it hung on the HTC screen. I could not get it to go back in to recovery. the only thing I could do was get it to hboot. Is there a way to get to recovery from hboot? I read the manual twice.

Yeah if you're in Bootloader, choose recovery and you're done?
If fastboot is enabled, you first need to get into "normal" Bootloader mode:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you're in HBoot, you're able to get into recovery:
(was connected to USB that time, but doesn't matter)
DN41

Thanks I didn't see that. It was probably there though.
So why did it not boot into cm7. Do I have to use different Kernel? Was it that I installed the Gapps after the ROM?

No problem man, next Time you'll know it better.
I have no Problem with cm7 on Sd card, with gapps. Did you use the latest versions?
DN41
Sent from my DHD @ ARHD 6.3.1

Had a buddy root my phone and I have some issues 2.3.6

Had a buddy root my phone because my defy was very slow and clunky. I didnt do it because he has done it a bunch of times on other phones and I had no idea what I was doing.
He first did liquid arc 2.0 and it was AWESOME except when making calls. I couldnt hang up calls...so I had to wait until someone else hung up and then it would drop the call.
I heard great things about cm7 and cm9 so I told him to try those.He but he said it would error everytime he tried those roms?
He then put on 2.3.6 and its OK but for some reason I only get 3G. I also cannot use my camera!?
I told him about these issues and he said there is no way of getting a different rom because its non-down-gradable?
Is the stuff he is telling me accurate? If anyone could help me I would appreciate it. I wouldnt mind this rom if I had 3g and a camera but I would really like CM7 or CM9 but like I said, he couldnt get them to work, unless he is doing something wrong.
Thanks

Is true. He must have tried to flash it like other android phones. Your current ROM is indeed undowngradeable. It's a ROM got the defy+. These have different camera modules as most of the original ones.
You can still instal CM7 you just have to look for defy+ ones (for defy + kernel) but camera will not work.
You should read the threat in dev category that's something like bl6 go to froyo. Don't know it your on a bl6 or 7.
Give the dude a slap on his face and do it yourself now. ;-)
Edit:
Someone in the same situation as you. You can try the solution proposed here:
http://forum.xda-developers.com/showthread.php?t=1485009
Sent from my MB525

Try this. http://forum.xda-developers.com/showthread.php?t=1486731 I stuck at Android 2.3.6. too. Then I flashed this ROM via RSDlite. now everthing is fine again.

OK good...it sounds like it can be fixed.
Customromfan: I would like to give that a try BUT I have no clue on what to do.
I could do a lot of research and probably be able to get it done but since my scenerio is a little different than most step by step instructions could someone please help me on this?
All I do know is I need to download RSDlite but I dont know anything else from there. Heck, I dont even know how to get to the bootloader screen....
Any help would be much appreciated. It sucks being stuck on only the edge network, no camera and the battery life is horrible along with other issues...

He who takes the short path soon stumbles & falls
Here's what I would do ^^
Make your mate buy ph off you 2/3 the $$
Buy another one... ebay or like - & start off slow & do it yourself...
You'll appreciate your ph more & you'll look after it better...
-=or=- drop it in some salt water, for like an hour!! (heard this fubar's defy) Then claim your warranty ;-)
...then start from scratch

Why would I do that when its fixable?

mgp32 said:
Why would I do that when its fixable?
Click to expand...
Click to collapse
:mmm: you could ask the guy that broke it to fix it ^^

Most info: http://forum.xda-developers.com/showthread.php?t=1216982
Stock recovery is when you press power + Vol down (could also be up, don't know) and when you get a triangle press both Vol keys
The root tool = superoneclick (Google is your friend)
To instal CM7 afterwards: search for 2nt init defy apk, put it on you sd card, unable unknown sources in settings> app> dev
Find the apk in an explorer app (if the room doesn't have one, get it from the market) follow instructions, reboot twice. Then press Vol down with blue let, go to custom recovery, wipe data and cache and instal the zip you have put on your sd earlier.
Sent from my MB525

So all I do is flash the ROM that Customromfan posted. Find CM7 and install to SD card(anyone know a good link?). Then install 2nd init. Then go to custom recovery, clear cashe/data and then install CM7?
Anything Im missing? I dont have to re-root right since its already rooted?
Once again this is ALL new to me so the more details the better!
Thanks!

nepotu said:
You've mentioned in the OP that you have flashed the 2.3.6 Full SBF. To get your camera working all you have to do is follow next steps:
1) download this SBF (link); I think it's the same SBF jianbangguo suggested
2) restart in stock recovery(Vol down + power) a do a full wipe (wipe data + cache)
3) restart in bootloader mode (Vol Up+Power)
4) plug in the USB and flash with RSD Lite (v>= 4.9) the SBF downloaded at 1)
5) your Defy should be running on Froyo kernel now.
6) activate USB debugging and root it with SuperOneClick 2.3.3
7) install Defy 2nd init (i recommend you to look for v1.4.2, because this app has all required files in it)
8) download a froyo CEE nandroid backup (SBF's topic, Froyo CEE topic or search for it on Google) and put it on your SD Card
9) restart your phone in custom recovery (Vol Down on the blue [email protected])
10) restore Froyo CEE nandroid
11) do a full wipe (data, cache and dalvik cacke) in custom recovery, then reboot.
Click to expand...
Click to collapse
Fist try the first 5 steps. If it boots, you have your camera back, otherwise please tell. The ROM you are on then is rubbish. It's a Chinese without a market and stuff. To instal a new ROM, you will have to instal 2nt init (this starts up before android to modify it). To do so, look at step 6 and 7. If you want to go back to a stock ROM, follow the next steps. If you want to instal CM7, there are a few options. I am on the cherrypicks version and don't have many bugs. The others won't have them to I think.
Just download the zip and instead of restore the nand, instal the zip. If you want I'll edit the post with links later.
Edit:
For CM7 you can use this one:
http://www.defy-cm.net/jordan-cm7.2-nightly/cm72-120212.0129-NIGHTLY-Defy.zip
(It's from Epsylon3's latest build)
I think you also need to install the right kernel:
http://forum.xda-developers.com/attachment.php?attachmentid=811082&d=1323463612
And the gapps (market and stuff):
http://cmw.22aaf3.com/gapps/gapps-gb-20110828-signed.zip
So step 10 would be: Press install zip, navigate to the place you placed the files. Install the three (the order doesn't mather).
If you want to restore the nand to go to the original froyo:
http://ge.tt/9Gj23TD Place it in clockworkmod/backup on your sd.

Labsin, I did steps 1-5 and everything is looking good!
Now, Im lost on what to do with 2nd init. Do I download it from the phone or my computer? How do I get it downloaded to the phone? Detailed instructions on these steps would be much appreciated!
Labsin, have you tried miui? Ive heard good things, is this easier to install than CM7...thinking maybe I give this a try...
Thanks again man....thanks to you Im starting to understand this stuff a little bit...

Download latest apk in the Attached Files of the threat. Place it on your sd. On your phone: go to settings>apps>activate 'unknown sources'. Search the apk on your phone and open it (go trough your apps as there will be an app to explorer sd content). When installed, open and follow instructions.
If you want miui, you have to replace the cm7 zip with that of the miui. There are many different versions. WIUI has many languages and didn't have any problems with it:
http://forum.xda-developers.com/showthread.php?t=1161110
You can use that guide to install. No need for the gapps. I suggest however to install te Kernel of my previous post.

I browsed the files on my phone and found 2nd init. I dont see any instructions though?
At this point am I OK to boot into custom recovery and load CM7, Kernal and gapps(the links you provided in an early post) ?
Thanks again...

I think you didn't root it. On phone, go to strings> apps> development> enable 'usb ...". Google for super one click root. Download it, extract it on pc, run it, connect phone, press root.
If you get no errors, reboot the phone.
To instal the apk, you have to get something like
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
.
After that, you can find the app in your appdrawer.
Sent from my MB525

You arent going to believe this........I got it!!!
Now I got another question...how do you get the cool looking clocks and animated weather stuff?
Thanks again labsin and all the others that posted, you guys are awesome!

Update...
I seem to be having the same issue I had with liquid arc. I love the rom so far BUT during a call when I take the phone off my ear it will sometimes not show the screen where I can hang up. I try hitting the top power button but it still won't. It will only "come back to life" when the person on the other end hangs up. So in other words if this decides to happen when someone doesnt answer I have to pop out the battery otherwise I would be leaving a LONG message.
any help on this would also be appreciated. Ive searched and searched but it seems no one else is having this issue.

mgp32 said:
Update...
I seem to be having the same issue I had with liquid arc. I love the rom so far BUT during a call when I take the phone off my ear it will sometimes not show the screen where I can hang up. I try hitting the top power button but it still won't. It will only "come back to life" when the person on the other end hangs up. So in other words if this decides to happen when someone doesnt answer I have to pop out the battery otherwise I would be leaving a LONG message.
any help on this would also be appreciated. Ive searched and searched but it seems no one else is having this issue.
Click to expand...
Click to collapse
flash MIUI

Do you have a link for miui? Any other files I have to flash (gapps or anything).
To go to miui would I just have to put the file on my SD card, go into custom recovery, clear date/cache, and then flash the miui file?
No need to re-root or do anything else right?
Edit: Its getting ridiculous now...even when the other end hangs up it stays locked most of the time and I have to reboot
Thanks for any help...

Have you flashed to kernel I posted earlier?
http://forum.xda-developers.com/attachment.php?attachmentid=811082&d=1323463612
It's the kernel that's used for the liquidArc. Seems not to go well with the kernel of the bld6 kernel you installed to downgrade. Just install it in custom recovery. No need to wipe this time.
If you want to go to MIUI:
WIUI is a spinoff with about the same looks but with tweaks that are specific for the Defy. It also packs with many languages. MIUI(en.miui.com) is only in Chinees and MIUIAndroid (http://miuiandroid.com) translates it only in English.
There are really a lot of sites that translate MIUI and add tweaks (galnet,...)
The steps are as you describe. If you get a blue let when you power on your phone DONT install 2nt init again. If you have a superuser app, you are already rooted. LiquidArc is rooted stock.
Info for WIUI:
http://forum.xda-developers.com/showthread.php?t=1161110
Edit:
Just checked, WIUI contains gapps and kernel so you only have to download the zip (and maybe addons you want) place them on your sd and install them. And wipe data/cache
As long as you flash without a low battery or don't let your pc crash when you flash a sbf and don't flash a bld 7 sbf. You will not be able to brick it

Just flashed 2.1.20 MIUI....
Only played with it for a couple minutes but it can do the main thing a phone should do and that is being able to hang up a phone call(atleast so far...)
I did notice it is only showing "e" when I should be in "3G"....is this rom not capable of picking up 3g?
Labsin- I did flash that kernal you suggested. Later today Ill probably try flashing again and just adding the gapps....

[Q] Flash nightmares and figuring out the aftermath

Hey everyone,
Sort of an odd problem here. So I've been flashing ROMs for over a year without only a few scares and oopses. Recently, I tried to use
the in-ROM updater, and it crashed the phone. Then after being unable to reboot the phone or get into CWM, I tried to use a one click restore
to get back to stock and then install the update through CMW. But something went wrong with ODIN and the phone became unrecogizable by the computer. Long story short, after hours of reading, the phone went to Sprint, where i was handed a new phone.
Got home, stuck in my old microSD card, to restore my data from my Nandroid. I rooted the phone, installed CMW, installed Blu Kuban with no issues. BUT THEN, I restored my data. It took a long time...like almost half an hour. The majority of that time on the MD5 check. The phone seemed to work fine. Then, in the middle of launching an app, it crashed...and it crashed HARD. But I could get into CMW. Any attempt to wipe did not help. I reinstalled the ROM, it would fail in the middle. The only way to break out of this and make progress was to throw a DIFFERENT ROM on the microSD and install that. I got Kuban back on, restored my data, and had it crash again, same symptoms, same problems. My question is: Could all this be caused by a corrupt nandroid? If it isn't that, what is causing all of this?
HELP!!

hint, stop restoring your data lol.
But yeah, def your data(probably). Try installing a rom and without restoring your data(after a full wipe) and go from there
Sent from my SPH-D710 using xda premium

Agreed, consider your restore toasted. Wouldn't the first fail or two deter you from trying to restore anymore? Haha, no offense or anything.
Sent from my SPH-D710 using XDA

Well it all just seems so mysterious. The latest is that rather than restoring data, I did a full restore. Then I updated to the latest zip in CWM. The phone ran fine most all day.....and then crashed and burned again. I'm wondering if it could be a disagreement between the Tegrak program and the kernel? I'm going to try to do a full restore and, while it's still on the old version, uninstall Tegrak, then update and see what happens. Why do you suppose the data is passing the MD5 test if it's corrupt? Any input is greatly appreciated.

Okay, got it up and running again. Uninstalled Tegrak and I'm not going to update to the latest and see what is what. If I were to install Titanium and do an app backup while it's still running, would that suffer from the same corruption as Nandroid backup? I'm assuming doing a Android backup of it while it's running would do nothing to address whatever corruption is there?

Titanium pro can pull apps and data from nandroids btw.
sent from MY BAD A$$ ET4G

I would suggest odin back to stock then reformat you sd card from within settings/storage/unmount ext sd/format then start fresh. Reroot, reinstall CWM, do a fresh install of all your apps from the playstore then do your backups. I have heard of new phones having conflicts with sd cards maybe that will fix your problem

bigdaddy619 said:
I would suggest odin back to stock then reformat you sd card from within settings/storage/unmount ext sd/format then start fresh. Reroot, reinstall CWM, do a fresh install of all your apps from the playstore then do your backups. I have heard of new phones having conflicts with sd cards maybe that will fix your problem
Click to expand...
Click to collapse
He is right some times that's the best way to go. Also along with titanium backup I use rom toolbox to back up apps. It backs up the actual apk so its the fastest way to start fresh.
Sent from my SPH-D710 using xda app-developers app

Titanium backs up the actual apk too. Just when restoring choose app only.
sent from MY BAD A$$ ET4G

TiBu also makes a flashable zip of your apps now too that you can just flash in recovery
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

So after Titaniuming things after a restore I waited to see if the phone would crash. Sure enough, it did. So I did one click Odin back to stock rooted I27. Added CWM. Then after a double wipe, flashed Blue Kuban 1.5.1. Then installed Titanium, restored my apps, signed back into Google....etc, etc.....and, on the way to the gym it CRASHED AGAIN. HOW IS THIS POSSIBLE? What could possibly have come with the phone? Does my particular phone just not play nicely with this ROM? Any suggestions would be appreciated. My next experiment is to go from stock again and install a different ROM, restore apps, and see what happens. If that crashes too I don't know what to think.

Macros746 said:
So after Titaniuming things after a restore I waited to see if the phone would crash. Sure enough, it did. So I did one click Odin back to stock rooted I27. Added CWM. Then after a double wipe, flashed Blue Kuban 1.5.1. Then installed Titanium, restored my apps, signed back into Google....etc, etc.....and, on the way to the gym it CRASHED AGAIN. HOW IS THIS POSSIBLE? What could possibly have come with the phone? Does my particular phone just not play nicely with this ROM? Any suggestions would be appreciated. My next experiment is to go from stock again and install a different ROM, restore apps, and see what happens. If that crashes too I don't know what to think.
Click to expand...
Click to collapse
Did you reformat your sd card?

No. Is doing the X2 wipe in CWM not enough? How would I do that? Anyway I could keep the MASSIVE downloads from various games? If I shifted them to my harddrive and then moved them back?

Macros746 said:
No. Is doing the X2 wipe in CWM not enough? How would I do that? Anyway I could keep the MASSIVE downloads from various games? If I shifted them to my harddrive and then moved them back?
Click to expand...
Click to collapse
Transfer your games to your pc, then go to settings/storage/unmount ext sd card/ then it will give you the option to format

also, seeing as this saga started on a different phone...and obviously that SD card is no more, I don't understand how it could be that. Or are you suggesting it's an issue with the external microSD?

Macros746 said:
also, seeing as this saga started on a different phone...and obviously that SD card is no more, I don't understand how it could be that. Or are you suggesting it's an issue with the external microSD?
Click to expand...
Click to collapse
From what I understand from seeing other posts the data on your card is not matching your phone

bigdaddy619 said:
From what I understand from seeing other posts the data on your card is not matching your phone
Click to expand...
Click to collapse
Okay, so I'm formatting my internal SD card correct? And I'm doing this through CWM? I just tried in the format/sdcard and I got an error mounting it. Sorry to be thick here. By the way, it's Kuban_recovery 0.0.1
Thanks for the help so far, I really appreciate it.

Macros746 said:
Okay, so I'm formatting my internal SD card correct? And I'm doing this through CWM? I just tried in the format/sdcard and I got an error mounting it. Sorry to be thick here. By the way, it's Kuban_recovery 0.0.1
Thanks for the help so far, I really appreciate it.
Click to expand...
Click to collapse
external sd card!!!!!!! your micro sd card. that can be done settings/storage/unmount ext sd card/ then it will give you the option to format

bigdaddy619 said:
external sd card!!!!!!! your micro sd card. that can be done settings/storage/unmount ext sd card/ then it will give you the option to format
Click to expand...
Click to collapse
Reformatted....crashed. Operating without external SD....crashed. Clean install of Blu Kuban with no restore except though account sign in with Google.....crash. Clean install of Venum's ROM....crash. My final test is a restore of system ROM....but I am beginning to suspect that the replacement phone they gave me at Sprint is faulty. Because now it obviously has nothing to do with a corrupt backup. Anyone have any last minute suggestions?
Macros

Macros746 said:
Reformatted....crashed. Operating without external SD....crashed. Clean install of Blu Kuban with no restore except though account sign in with Google.....crash. Clean install of Venum's ROM....crash. My final test is a restore of system ROM....but I am beginning to suspect that the replacement phone they gave me at Sprint is faulty. Because now it obviously has nothing to do with a corrupt backup. Anyone have any last minute suggestions?
Macros
Click to expand...
Click to collapse
So the verdict is in all: Faulty phone AND faulty battery WOO HOO! Thanks for checking those refurbs Sprint....grrr....when I think of the hours of grief.....sigh. New phone arriving tomorrow. Thanks so much for all of your help. Everyone who tried to help I SO appreciate it! Can't wait until I have Blu up and running on the new phone.
Macros746

[Q] Soft Bricked? GS3 Sprint

So I had to create account just to post my problem before taking any drastic measures. I have been on the XDA forums for a while and I'm not a complete n00b(disclaimer here) when it comes to rooting and ROMing but I done messed up.
So I had this ROM installed which was being a little finicky with the screen. It would flash randomly when either texting or in Facebook. Mostly when the keyboard was up(swiftkey 3). Anyways, I had no real expertise in flashing Kernels so I thought a would give that a try to see if that might help anything.
Went into the forums about intalling custom kernels and came across this thread.
Followed ChaseBroyles steps that he gave, the exact method( this may where I have messed up) then I reboot, it shows the SAMSUNG logo but then turns its self off. So I try to go into recovery, shows at the top Recovery Booting, then shows Samsung Galaxy SIII logo then turns its self off.
So the next logical step is to go into Download mode. It boots into download just fine, then I try to get it to connect to the computer. Tried all of my USB ports and all the cables that I have for Micro USB, still nothing. Odin wont detect it and neither will my computer. I tried removing the battery and letting it sit for a while, and that didn't work either.
So all the help will be apprecited, I do have a jtag but not available to me til this weekend sadly. If that is what I need to do, I'll try that but if I can get it fixed today or sometime this week it would be most appreciated!

Korumaru said:
So I had to create account just to post my problem before taking any drastic measures. I have been on the XDA forums for a while and I'm not a complete n00b(disclaimer here) when it comes to rooting and ROMing but I done messed up.
So I had this ROM installed which was being a little finicky with the screen. It would flash randomly when either texting or in Facebook. Mostly when the keyboard was up(swiftkey 3). Anyways, I had no real expertise in flashing Kernels so I thought a would give that a try to see if that might help anything.
Went into the forums about intalling custom kernels and came across this thread.
Followed ChaseBroyles steps that he gave, the exact method( this may where I have messed up) then I reboot, it shows the SAMSUNG logo but then turns its self off. So I try to go into recovery, shows at the top Recovery Booting, then shows Samsung Galaxy SIII logo then turns its self off.
So the next logical step is to go into Download mode. It boots into download just fine, then I try to get it to connect to the computer. Tried all of my USB ports and all the cables that I have for Micro USB, still nothing. Odin wont detect it and neither will my computer. I tried removing the battery and letting it sit for a while, and that didn't work either.
So all the help will be apprecited, I do have a jtag but not available to me til this weekend sadly. If that is what I need to do, I'll try that but if I can get it fixed today or sometime this week it would be most appreciated!
Click to expand...
Click to collapse
Let me make a summary and you can correct me if I'm wrong:
You had a rooted phone with a custom Rom (JellyBam) and a custom Recovery (CWM or TWRP). Please clarify which Recovery you had (and version, if you remember it). Also, please clarify which version of JellyBam you had installed (latest is 7.6.2).
You decided to flash a new Kernel, thinking it'd help with the random screen flickers. Please clarify which Kernel you flashed.
Now when you try to boot into the Rom, you get stuck in a bootloop (phone doesn't progress past or turns off at the Samsung Logo).
When you boot into Recovery Mode, it gets to the recovery loading screen then turns off.
Download mode works fine, but your computer doesn't recognize it.
You have a JIG.
So it sounds like you flashed a Kernel which was not meant for your Rom. JellyBam is a 4.2.2 Rom, but there are two types of kernels for 4.2.X Roms: those based off of Linux 3.0 and those based on Linux 3.4. After a little searching, I couldn't find which version JellyBam is using, but if it's based off of 3.0 and you flashed a 3.4 Kernel, it'll give you a bootloop. It doesn't exactly explain why your recovery got messed up, but others have had their recovery partition borked by a bad kernel flash, so it's not out of the realm of possibility. Tis is why I want to know which version of JellyBam you had and which kernel you flashed. This will help us know how to help you.
Ok, so your phone is not beyond repair. I'm a little disconcerted that you cannot boot into Recovery, but that happens every once in a while when flashing, so it's not the worst thing to happen. You can, however, boot up into download mode. This is very good. Make sure you have the latest Samsung drivers on your computer and that you don't have Kies installed (Kies has been known to interfere with Odin). See if that works to get Odin to recognize the phone.
If the above works, all you have to do is follow the rooting guide to get a custom recovery back.

Okay so you followed instructions on how to flash a kernel but what kernel did you flash? I think you flashed a kernel for the gsm variant which is completely different than the Sprint kernels. Well if you flashed the kernel he recommended you flashed kt747 Koontz kernel. Which is correct but did you download the correct one? There is one for Touchwiz one for AOSP and there are several for AOSP depending on the romantic and build date. So if you can provide this info it should be easy, but quick way to fix your problem is to just refresh your room right now.
Edit: hats off to Topherk beat me to it...
Transmitted with a portable device using Xparent Blue Tapatalk 2

topherk said:
Let me make a summary and you can correct me if I'm wrong:
You had a rooted phone with a custom Rom (JellyBam) and a custom Recovery (CWM or TWRP). Please clarify which Recovery you had (and version, if you remember it). Also, please clarify which version of JellyBam you had installed (latest is 7.6.2).
You decided to flash a new Kernel, thinking it'd help with the random screen flickers. Please clarify which Kernel you flashed.
Now when you try to boot into the Rom, you get stuck in a bootloop (phone doesn't progress past or turns off at the Samsung Logo).
When you boot into Recovery Mode, it gets to the recovery loading screen then turns off.
Download mode works fine, but your computer doesn't recognize it.
You have a JIG.
So it sounds like you flashed a Kernel which was not meant for your Rom. JellyBam is a 4.2.2 Rom, but there are two types of kernels for 4.2.X Roms: those based off of Linux 3.0 and those based on Linux 3.4. After a little searching, I couldn't find which version JellyBam is using, but if it's based off of 3.0 and you flashed a 3.4 Kernel, it'll give you a bootloop. It doesn't exactly explain why your recovery got messed up, but others have had their recovery partition borked by a bad kernel flash, so it's not out of the realm of possibility. Tis is why I want to know which version of JellyBam you had and which kernel you flashed. This will help us know how to help you.
Ok, so your phone is not beyond repair. I'm a little disconcerted that you cannot boot into Recovery, but that happens every once in a while when flashing, so it's not the worst thing to happen. You can, however, boot up into download mode. This is very good. Make sure you have the latest Samsung drivers on your computer and that you don't have Kies installed (Kies has been known to interfere with Odin). See if that works to get Odin to recognize the phone.
If the above works, all you have to do is follow the rooting guide to get a custom recovery back.
Click to expand...
Click to collapse
To answer your questions in order:
1) I had CWM v 5.x.x I cannot remember correctly. It is the one Zedo max gives in his tutorial. And for Jellybam, I had the latest stable build that was released from their website which is 7.6.2
2) I used this Kernel (http://forum.xda-developers.com/showthread.php?t=1800576) from the thread I stated, another user provided it.
3) Yes that is correct
4) Yes
5) Yes again
6) Yes that is what it is called, bought cause of something dumb I did months ago.
I thank you for the info, it is really appreciated.
So I just updated my Samsung drivers(forgot to do it when I reformatted) and that worked! Odin recognized it and now I'm on the road to recovery!
Thank you so much for my help
So for future reference, what kernel should I install with that ROM just so I don't **** crap up this time?

I wasn't able to find it in the jellybam forums with a brief search, but you could ask over there to see if they can tell you. Also, there are two types of 3.4 kernels, one built before 4/19 and those after 4/19. Make sure you're using the court one.
Hope you can figure it out, and please post back here if you can find it!
Sent from my SPH-L710 using xda app-developers app

I think I might have found a reference to what kernel you're you need to flash: http://www.bam-android.com/forum/showthread.php?3443-Fix-For-D2SPR-7-0-Screen-Issue. From the link, it seems like JellyBam uses 3.0 kernel.
On a separate note. This post might give you direction on fixing the screen flicker issue.
Hope this helps!
Sent from my SPH-L710 using xda app-developers app

Oh, I'm a dolt! You can check your version by going to settings ---> About phone. The kennel version box tells you what version it's running. Look arty mine (from LiquidSmooth):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SPH-L710 using xda app-developers app