Database Info

Stuck on Google startup screen

New to xda, so I'll just let you in everything in the last 2 hours. I flashed Bugless Beast (2002-06-09), wiping cache and dalvik cache and it ran fine. Then I installed the Matr1x bfs v22.5 from bootloader and rebooted once more. After that, it stayed on the Google screen until I removed the battery. So far the only possible solution that I've looked into is this thread called [HOW TO] Return to Stock Using Odin (VZW and GSM) -- you can google the link to see what I'm talking about. I can't seem to get the process to succeed. The attempts always end up as successful: 0 failed: 0 I tried using both the VZW from the first link given and the GSM: CF_ODIN_YAKJU_IMM76D_full for the PDA button on Odin. Nothing comes up on Odin when I mount the phone to the PC so I'm not sure if I'm even connecting, although I was able to connect the phone to the PC early today to transfer files. Could I be using incorrect files to start Odin? Am I connecting to Odin? Are there any other possibilities besides using Odin to return this phone to normal?
I was running early versions of Bugless Beast and Matr1x before flashing the new versions. Please, I need to get this phone fixed before this weekend. Thanks, in advance.

itsTnTg said:
New to xda, so I'll just let you in everything in the last 2 hours. I flashed Bugless Beast (2002-06-09), wiping cache and dalvik cache and it ran fine. Then I installed the Matr1x bfs v22.5 from bootloader and rebooted once more. After that, it stayed on the Google screen until I removed the battery. So far the only possible solution that I've looked into is this thread called [HOW TO] Return to Stock Using Odin (VZW and GSM) -- you can google the link to see what I'm talking about. I can't seem to get the process to succeed. The attempts always end up as successful: 0 failed: 0 I tried using both the VZW from the first link given and the GSM: CF_ODIN_YAKJU_IMM76D_full for the PDA button on Odin. Nothing comes up on Odin when I mount the phone to the PC so I'm not sure if I'm even connecting, although I was able to connect the phone to the PC early today to transfer files. Could I be using incorrect files to start Odin? Am I connecting to Odin? Are there any other possibilities besides using Odin to return this phone to normal?
I was running early versions of Bugless Beast and Matr1x before flashing the new versions. Please, I need to get this phone fixed before this weekend. Thanks, in advance.
Click to expand...
Click to collapse
you flash jelly bean kernel on ICS rom !(v.22.5 and higher are Jelly Bean, v.22.0 and lower are ICS)
you can boot on recovery ?

like leap said you flashed a JB kernel on a ICS ROM. Just download Matr1x v20 and flash it from the CWM recovery, it should boot right away. If not just go in CWM wipe factory reset and reflash Bugless Beast, or any other ROM, and the proper kernel (Matrix v20 for ICS, 20.5 for JB). Don't mess with Odin if you don't have experience or flash a wrong ROM stock into your Nexus, unless you want a nice paperweight.

Thanks
leap_ahead said:
you flash jelly bean kernel on ICS rom !(v.22.5 and higher are Jelly Bean, v.22.0 and lower are ICS)
you can boot on recovery ?
Click to expand...
Click to collapse
Wow, thanks! I run v. 22.0 and it works fine now.. I feel embarrassed of how simple it is to fix it.

Thanks
DeuXGod said:
like leap said you flashed a JB kernel on a ICS ROM. Just download Matr1x v20 and flash it from the CWM recovery, it should boot right away. If not just go in CWM wipe factory reset and reflash Bugless Beast, or any other ROM, and the proper kernel (Matrix v20 for ICS, 20.5 for JB). Don't mess with Odin if you don't have experience or flash a wrong ROM stock into your Nexus, unless you want a nice paperweight.
Click to expand...
Click to collapse
Thanks for the instructions! You saved me like a whole day of trying to fix this phone.

[How to] Flash Gingerbread ROM from Jelly Bean

I flashed Jelly Bean unofficial CM10. For some reason, I feel it is slow in response, and I want to go back to Gingerbread. When I flash GB ROM (Zeus 6), It just boot loops.
Am I missing something? Or Do I have to go to ODIN stock before flashing GB?
Any help

You can try flashing a gb kernel in cwm.
Wipes and Format the usual
Go to voodoo, make sure voodoo conversion and lagfix is on.
Reboot into cwm
Reflash gb rom

qkster said:
You can try flashing a gb kernel in cwm.
Wipes and Format the usual
Go to voodoo, make sure voodoo conversion and lagfix is on.
Reboot into cwm
Reflash gb rom
Click to expand...
Click to collapse
At this point, I am stuck @ boot loop How do I get GB kernel to flash in CWM?

paluinfusion said:
At this point, I am stuck @ boot loop How do I get GB kernel to flash in CWM?
Click to expand...
Click to collapse
the kernel can be flashed in recovery or in download mode.
start here if you don't know what I'm talking about.
http://forum.xda-developers.com/showthread.php?t=1437548

You have to Odin or heimdal back...you need something with a working pit...problem is there is no conversion for going back through any cwm zips...so Odin or heimdal is the only way back
Cm10 is in mtd format...no gingerbread or ics Rom is in mtd format
Sent from my HTC Holiday using Tapatalk 2

mg2195 said:
You have to Odin or heimdal back...you need something with a working pit...problem is there is no conversion for going back through any cwm zips...so Odin or heimdal is the only way back
Cm10 is in mtd format...no gingerbread or ics Rom is in mtd format
Sent from my HTC Holiday using Tapatalk 2
Click to expand...
Click to collapse
yup, aosp re-purposes some samsung partitions. the needed data for touchwiz roms is gone. need a full pit flash with preferably all the partitions, might have to take param.ifs, cache, and/or dbdata from a froyo rom. can't remember atm what came in the gb updates but it wasn't everything.

Dani897 said:
yup, aosp re-purposes some samsung partitions. the needed data for touchwiz roms is gone. need a full pit flash with preferably all the partitions, might have to take param.ifs, cache, and/or dbdata from a froyo rom. can't remember atm what came in the gb updates but it wasn't everything.
Click to expand...
Click to collapse
Has anyone successfully gone back to ICS or GB from JB? I dont want to mess up my phone any more than it is.

Dani897 said:
yup, aosp re-purposes some samsung partitions. the needed data for touchwiz roms is gone. need a full pit flash with preferably all the partitions, might have to take param.ifs, cache, and/or dbdata from a froyo rom. can't remember atm what came in the gb updates but it wasn't everything.
Click to expand...
Click to collapse
I was hoping that a gb kernel flash (entropy or zen + others) will auto voodoo a non voodoo file system. The first flash will convert the file system. The second flash will install the firmware.
Sort of like a reverse cm7, cm9 or miui that uses mtd.
as for the successful return from cm10, when in doubt, odin or heimdall back to stock with a repartition should get you back to the starting point.

Dani897 said:
yup, aosp re-purposes some samsung partitions. the needed data for touchwiz roms is gone. need a full pit flash with preferably all the partitions, might have to take param.ifs, cache, and/or dbdata from a froyo rom. can't remember atm what came in the gb updates but it wasn't everything.
Click to expand...
Click to collapse
It's not that aosp uses partions differntly..its that the new jb is in mtd which is A whole new file system format with different partions completely...with any ics or older jb Rom i could go back to gb with one simple flash
I think what you meant was this: mtd uses partions differently requiring a full pit flash to go back
madpb said:
Has anyone successfully gone back to ICS or GB from JB? I dont want to mess up my phone any more than it is.
Click to expand...
Click to collapse
With the older jb roms (prior to mtd) I could.go back with a simple flash...with usual wipes of course...after mtd builds I've always heimdaled back using qkster uclb3 one click...thanks qkster
qkster said:
I was hoping that a gb kernel flash (entropy or zen + others) will auto voodoo a non voodoo file system. The first flash will convert the file system. The second flash will install the firmware.
Sort of like a reverse cm7, cm9 or miui that uses mtd.
as for the successful return from cm10, when in doubt, odin or heimdall back to stock with a repartition should get you back to the starting point.
Click to expand...
Click to collapse
Never thought of that...seems possible...ill give it a try when I get home tonight (referring to the voodoo system)
Sent from my HTC Holiday using Tapatalk 2

Originally Posted by madpb
Has anyone successfully gone back to ICS or GB from JB? I dont want to mess up my phone any more than it is.
Click to expand...
Click to collapse
I've also become a big fan of qkster's UCLB3 Heimdall 1-click when it comes time to revert from 4.x.x to 2.3.x. I Heimdall back to stock UCLB3, then Heimdall Zen's A16 OC kernel/CWM combo, and finally boot into CWM Red and restore whatever compatible GB backup I want. I've long since gotten into the habit of keeping several backups stored on internal memory. I got sick of noobing it up and ending up with bootloops. This method's been good to me so far, and I'm sticking with it.

Flashing TW from 4.2 JB

Can I flash back to TW from the 2.3.3.0 recovery or would I need to revert back to the previous TWRP.
Sent from my SCH-I535 using xda premium

nativesmiley said:
Can I flash back to TW from the 2.3.3.0 recovery or would I need to revert back to the previous TWRP.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
You come back to TW at your own risk. This where most bricks happen. Best practice is to Odin back to stock and then come back to TW. Luckily you survived CM so far but flashing back to TW could cause a problem. If you don't want to Odin first wipe all partitions till raw and give it a shot.

ok just to clarify....Say I was on Synergy then flashed CM 10.1 now I decided I wanted to come back to Synergy. I would need to Odin back to stock, then flash Synergy? I just couldn't flash Synergy from Cm 10.1? Is this true for CM10 as well? What about flashing my nandroid backup instead of Odin back to stock?
Thanks

Rudy_Ruettiger said:
ok just to clarify....Say I was on Synergy then flashed CM 10.1 now I decided I wanted to come back to Synergy. I would need to Odin back to stock, then flash Synergy? I just couldn't flash Synergy from Cm 10.1? Is this true for CM10 as well? What about flashing my nandroid backup instead of Odin back to stock?
Thanks
Click to expand...
Click to collapse
you do take the risk anytime you flash anything. HOWEVER, i have SYNERGY, MIUI, and CM10.1 along with Liquid (4.2) on my phone. YOU will have problems with finding your files, as 4.2 will create the 0 folder, and it may look like you have lost files. TWRP 2.3.3 does an excellent job of finding back-ups, or just scroll to find the TWRP folder to find your backups.
Gallery also has been known to "lose" pictures. IMO, they are still there, just have to find them. i've actually opened gallery and had it be empty, but a quick close, and then re-open and they show up. Sort of like it has to find them.
YMMV, make backups of everything, and flash away! just know what chances you are setting yourself up for, and be prepared.
edit: AND... i'm not responsible for anything YOU do to your phone... yada yada yada...
just thought i had to throw that out as well...
:cyclops:

goldsmitht said:
you do take the risk anytime you flash anything. HOWEVER, i have SYNERGY, MIUI, and CM10.1 along with Liquid (4.2) on my phone. YOU will have problems with finding your files, as 4.2 will create the 0 folder, and it may look like you have lost files. TWRP 2.3.3 does an excellent job of finding back-ups, or just scroll to find the TWRP folder to find your backups.
Gallery also has been known to "lose" pictures. IMO, they are still there, just have to find them. i've actually opened gallery and had it be empty, but a quick close, and then re-open and they show up. Sort of like it has to find them.
YMMV, make backups of everything, and flash away! just know what chances you are setting yourself up for, and be prepared.
edit: AND... i'm not responsible for anything YOU do to your phone... yada yada yada...
just thought i had to throw that out as well...
:cyclops:
Click to expand...
Click to collapse
so i can use 2.3.3 to flash between TW and CM right? the last time i went back to TW was when i was on 2.3.2.3 and they were say i had to revert back to the recovery before 2.3.2.3. and with that i never had problems flashing between both ROMs. i just want to know if i can flash between TW and CM with 2.3.3 and not revert back to old recoveries.

nativesmiley said:
so i can use 2.3.3 to flash between TW and CM right? the last time i went back to TW was when i was on 2.3.2.3 and they were say i had to revert back to the recovery before 2.3.2.3. and with that i never had problems flashing between both ROMs. i just want to know if i can flash between TW and CM with 2.3.3 and not revert back to old recoveries.
Click to expand...
Click to collapse
Stay on TWRP 2.3.3. I've been using TWRP 2.3.3 just fine while flashing multiple Beans JB TW builds. Not sure what issues others had but it works fine for me. Also, if you intend to install 4.2 AOSP in the future then you'll have to update TWRP again anyway if you downgraded it.

nativesmiley said:
so i can use 2.3.3 to flash between TW and CM right? the last time i went back to TW was when i was on 2.3.2.3 and they were say i had to revert back to the recovery before 2.3.2.3. and with that i never had problems flashing between both ROMs. i just want to know if i can flash between TW and CM with 2.3.3 and not revert back to old recoveries.
Click to expand...
Click to collapse
yes, you can use TWRP 2.3.3 to flash old backups made with any version TWRP. with no problems.
however, you can NOT flash old backups made with CWM. different system and will definitely NOT work.
:cyclops:

thank you very much guys! appreciate the input!

what is the proper way to flash between TW and CM (10.1) so I dont get stuck in roaming mode again?

Yea I am about to do this to correct me if I am wrong please but we are suppose to Odin back to 4.0.4 stock coming from 10.1 then up grade to stock JB from there
Sent from my SCH-I535 using xda app-developers app

Nopi45 said:
Yea I am about to do this to correct me if I am wrong please but we are suppose to Odin back to 4.0.4 stock coming from 10.1 then up grade to stock JB from there
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
know that if you go the ODIN route, you will have to re-root and re-unlock your bootloader.
if you have the MOST up to date recover (CWM OR TWRP - I prefer TWRP 2.3.3) and you have a backup made of a TW ROM, and are on 10.1 currently, then just clear dalvic, cache, and restore your TW ROM.
however, if you do not have one, then would suggest factory reset and then clean install of TW.
there are always "chances" of issues, mainly the 0 folder, but i've been flashing back and forth between MIUI bV, Synergy, and CM10.1 and only problem i had was when my mobile network got switched, and i had to go back in and change to RUIM/SIM. and that was the only thing.
just know what you are doing and know where to go to get answers to help fix things that may go wrong.
and, "insert legal comments here"... no one is responsible for what YOU do to YOUR phone, except YOU.
:cyclops:

The only bad experiences I've had going from 4.2 to TW is when I only briefly installed 4.2 but didn't get data working. That left me with no data in TW. So I had to odin back to stock then re-root, unlock bootloader and flash.

will i be able to go from CM 10.1 to AOKP 4.2.1 without any issue?

Rudy_Ruettiger said:
will i be able to go from CM 10.1 to AOKP 4.2.1 without any issue?
Click to expand...
Click to collapse
I haven't had a problem going from one 4.2 AOSP rom to another. YMMV tho. Just flash a nandroid before you do it just in case.

Jelly Bean OTA

FOTA ripped for your enjoyment.
https://mega.co.nz/#!xoZigSqS!YHUa5Umv-8qjyFV1dtHs4lDQXMIn1q7plTz3zWeYSwY
That's completely unmodified. (I tried just installing it in CWM. Think I probably bricked doing something silly...)

I pulled this as well, but I'm curious if you had to flash back to stock firmware and recovery to get it. I tried using a rooted stock rom and the software update screen would give me a "modified devices don't get updates" message. I actually had to have stock recovery and system installed so that it would download. Did you have to do the same thing?

gee one said:
I pulled this as well, but I'm curious if you had to flash back to stock firmware and recovery to get it. I tried using a rooted stock rom and the software update screen would give me a "modified devices don't get updates" message. I actually had to have stock recovery and system installed so that it would download. Did you have to do the same thing?
Click to expand...
Click to collapse
Interestingly enough, it downloaded perfectly fine for me, even though my device was "modified"...

bigleague4040 said:
Interestingly enough, it downloaded perfectly fine for me, even though my device was "modified"...
Click to expand...
Click to collapse
I have a modified boot.img- perhaps that blocks the ota?

My device is rooted.
It is on 4.2.1 genuine T-mobile software.
When I want to update OverTheAir this message pop out.
See attachement (I don't know how to put image here).
What can I do to update OTA?

I played around with this a while ago (my flash counter is at 29 last time I checked).
I think you have a few options:
1) maybe unroot and that might remove the modified status
2) use heimdall or odin to flash back to unrooted stock, including stock recovery and boot.img
3) flash one of the rooted JB roms, either stock, cyanogen, or our very own Teamapexq rom
4) download the OTA or the JB rom from the web and repackage it yourself to a flashable zip.
Option 1 might not work. Option 2-4 will work, 4 would be the most fun.
sent while running with scissors

gee one said:
I played around with this a while ago (my flash counter is at 29 last time I checked).
I think you have a few options:
1) maybe unroot and that might remove the modified status
2) use heimdall or odin to flash back to unrooted stock, including stock recovery and boot.img
3) flash one of the rooted JB roms, either stock, cyanogen, or our very own Teamapexq rom
4) download the OTA or the JB rom from the web and repackage it yourself to a flashable zip.
Option 1 might not work. Option 2-4 will work, 4 would be the most fun.
sent while running with scissors
Click to expand...
Click to collapse
OMG, I would like to do it with no hassle.
I just want something to work ... grrr.

Option 2 would probably be the most straightforward. Essentially, you are unrooting. I just remembered, Samsung has Kies which might restore it to stock. You can download it from their website.
sent while running with scissors

mazak23 said:
My device is rooted.
It is on 4.2.1 genuine T-mobile software.
When I want to update OverTheAir this message pop out.
See attachement (I don't know how to put image here).
What can I do to update OTA?
Click to expand...
Click to collapse
the update in this thread is only about JB 4.1.2 that is officially the latest and the last one for our mobile. your message box is normal, there is no need for the usage of the OTA anymore since then. if u want to update to JB 4.3 follow this unofficial image:
http://forum.xda-developers.com/showthread.php?t=2463661

Holy thread resurrection Batman!!!
Oh boy. Here we go. Having troubles here.
I am trying to re-flash my phone to stock so I can return it under the protection plan. I firmly believe my radio might be on the fritz.
Anyway, I used the directions here:
http://theunlockr.com/2013/04/25/how-to-unroot-the-samsung-galaxy-s-relay-4g-sgh-t699/
Now it all completed successfully, and the phone is chilling at the SAMSUNG screen trying to boot. Not sure what to do at this point. Its been sitting there for a good 5 minutes.
Please help!!
UPDATE: Went into stock recovery, cleared Cache and Data, then rebooted it again, and it booted!

Which JelyBean Version...!!!
After installing this update what will be my os (JB 4.X.X) version???

saurabhsaurabhrai said:
After installing this update what will be my os (JB 4.X.X) version???
Click to expand...
Click to collapse
it is just from stock, will be updated to JB 4.1.2

Quick question about going from 4.1 to 4.4 (Been gone for a while)

So like the title says I have been out of the ROM game for a little bit. Every couple of months I check in and see whats new and flash something else.
I was on the Jelly Beans ROM (Build 16 I think) and Android 4.1. I did some searching last night as was going to try flashing Gummy ROM…bad idea. I am guessing I needed something prior to jumping up to a 4.4 base. I booted to recovery and wiped everything and tried to flash with no luck. So the phone would not boot and I could only get into recovery and download mode. I did not have my micro SD adapter in order to get jelly beans back on it to flash so I ended up having to use odin to flash a stock rooted 4.1 image. Finally got everything back up and running but I still want to try some of the 4.4 ROMs. So what exactly do I need first in order to flash one? (Modem maybe)…if you know for sure why that happened and what I need to do please let me know. Thanks!
My Current "About Phone" Info...
Android Version - 4.1.2
Baseband version - I535VRBMB1
Jelly Beans - Build 20
P.S. I have tried doing the research and nothing I have found has been clear but one thing I came across is the official 4.3 update was bad news and broke the root methods? So should I stay away from 4.3 ROMs and is the old root method blocked in 4.4 as well or is that a different case since it wasn't actually released for our phone. If that makes sense lol

aholeinthewor1d said:
So like the title says I have been out of the ROM game for a little bit. Every couple of months I check in and see whats new and flash something else.
I was on the Jelly Beans ROM (Build 16 I think) and Android 4.1. I did some searching last night as was going to try flashing Gummy ROM…bad idea. I am guessing I needed something prior to jumping up to a 4.4 base. I booted to recovery and wiped everything and tried to flash with no luck. So the phone would not boot and I could only get into recovery and download mode. I did not have my micro SD adapter in order to get jelly beans back on it to flash so I ended up having to use odin to flash a stock rooted 4.1 image. Finally got everything back up and running but I still want to try some of the 4.4 ROMs. So what exactly do I need first in order to flash one? (Modem maybe)…if you know for sure why that happened and what I need to do please let me know. Thanks!
My Current "About Phone" Info...
Android Version - 4.1.2
Baseband version - I535VRBMB1
Jelly Beans - Build 20
P.S. I have tried doing the research and nothing I have found has been clear but one thing I came across is the official 4.3 update was bad news and broke the root methods? So should I stay away from 4.3 ROMs and is the old root method blocked in 4.4 as well or is that a different case since it wasn't actually released for our phone. If that makes sense lol
Click to expand...
Click to collapse
you need the latest recoveries to flash kk roms. cwm is here https://www.clockworkmod.com/rommanager
and twrp is here http://teamw.in/project/twrp2/102. make sure you download the d2vzw version
if you're rooted you should have no problems flashing 4.4 rom. I recommend beanstalk from here http://forum.xda-developers.com/showthread.php?t=2354113. has worked great for me. you have to also update the modem to ML1 from here http://forum.xda-developers.com/showthread.php?t=1788313
as always do a nandroid before you do anything and you should backup your sd card to your computer. they probably will move post this to another thread.
good luck

dandydon414 said:
you need the latest recoveries to flash kk roms. cwm is here https://www.clockworkmod.com/rommanager
and twrp is here http://teamw.in/project/twrp2/102. make sure you download the d2vzw version
if you're rooted you should have no problems flashing 4.4 rom. I recommend beanstalk from here http://forum.xda-developers.com/showthread.php?t=2354113. has worked great for me. you have to also update the modem to ML1 from here http://forum.xda-developers.com/showthread.php?t=1788313
as always do a nandroid before you do anything and you should backup your sd card to your computer. they probably will move post this to another thread.
good luck
Click to expand...
Click to collapse
ahh I didn't even think of that? I do know for a fact whatever version of CWM i had was not recent..Are you sure that is the only issue? so with a newer recovery...like I have now that I fixed my phone..I can flash a 4.4 ROM no problem? I could have sworn I remember hearing something about needing a certain modem...or something similar

aholeinthewor1d said:
ahh I didn't even think of that? I do know for a fact whatever version of CWM i had was not recent..Are you sure that is the only issue? so with a newer recovery...like I have now that I fixed my phone..I can flash a 4.4 ROM no problem? I could have sworn I remember hearing something about needing a certain modem...or something similar
Click to expand...
Click to collapse
yes. flash the ML1 modem. I provided the link in my previous post. it's a fact that earlier recoveries won't flash kk roms. I found out the hard way myself. hopefully you'll have titanium or rom toolbox to backup your apps with data.

dandydon414 said:
yes. flash the ML1 modem. I provided the link in my previous post. it's a fact that earlier recoveries won't flash kk roms. I found out the hard way myself. hopefully you'll have titanium or rom toolbox to backup your apps with data.
Click to expand...
Click to collapse
Thanks a lot!!.. So how do I know if my recovery is new enough? I was never a fan of the touch recoveries because I felt like it would be easier to do something on accident so I haven't tried one in a while...I am using clockwork mod recovery 6.0.4.5. Is that new enough??
Also one lasttttt question I swear...can someone give me a quick list of the different recovery options that are out there now...and maybe list some features of each...thank you

aholeinthewor1d said:
Thanks a lot!!.. So how do I know if my recovery is new enough? I was never a fan of the touch recoveries because I felt like it would be easier to do something on accident so I haven't tried one in a while...I am using clockwork mod recovery 6.0.4.5. Is that new enough??
Also one lasttttt question I swear...can someone give me a quick list of the different recovery options that are out there now...and maybe list some features of each...thank you
Click to expand...
Click to collapse
that recovery is fine. i've only used cwm and twrp.. had some problems with philz recovery so I ditched it. basically they're all the same. twrp lets you name your back where as cwm just uses some default name which of course you can change with a file manager. twrp also wipes all 3 (system, cache and dalvik) with one swipe where as cwm requires 3 separate operations. I really haven't done much in recovery other than wiping and flashing. I'm actually on the latest twrp and have had no problems flashing kk roms. keep in mind that you can't backup in cwm and restore it using twrp and vice versa. it's really more a personal preference as far as I'm concerned.