Okay, so I bought the n7 v2, went home, unlocked the boot loader, and rooted it. I've tried to flash versions of vanir I built my self, the betas that are posted here on the forums, and I also tried carbon ROM. Every time I flash a ROM, my device bootloops, so I just hold power + vol down to get to boot loader mode so I can boot into recovery. Any fix for this? I've tried flashing a stock IMG and re rooting to. No luck.
Bump
frap129 said:
Bump
Click to expand...
Click to collapse
Did you even wipe, and perform a factory reset before flashing a ROM?
Sent from my Nexus 7 using xda app-developers app
TheMrcool212 said:
Did you even wipe, and perform a factory reset before flashing a ROM?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes, I wiped data, cache, and dalvik every single time.
Bump? Anyone?
try redownloading the rom and install, could of been a bad download
Sent from my Nexus 7 using xda app-developers app
shortyboy said:
try redownloading the rom and install, could of been a bad download
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
With four different ROMs, 2 transfered via adb and 2 from different download hosts, I doubt its a bad download.
frap129 said:
With four different ROMs, 2 transfered via adb and 2 from different download hosts, I doubt its a bad download.
Click to expand...
Click to collapse
you should've mentioned that in your original post. id try to reflash to complete stock and start all over. it seems like something you modified in the first rom you've flash isn't being removed from another flash,so going back to stock,you can be sure everything is working first.hope this helps
shortyboy said:
you should've mentioned that in your original post. id try to reflash to complete stock and start all over. it seems like something you modified in the first rom you've flash isn't being removed from another flash,so going back to stock,you can be sure everything is working first.hope this helps
Click to expand...
Click to collapse
I did mention that in the original post, as well as the fact that ive flashed stock a few times already.
Did you boot into the tablet after unlocking the bootloader but before rooting it? If not, try formatting data (not factory resetting) in recovery. I had the same experience and my sdcard never got populated with the default folders and files, remaining at 0MB. Apparently, symptoms of this problem include being unable to factory reset from recovery, being stuck on the splash screen, and having TWRP demand a password.
bananagranola said:
Did you boot into the tablet after unlocking the bootloader but before rooting it? If not, try formatting data (not factory resetting) in recovery. I had the same experience and my sdcard never got populated with the default folders and files, remaining at 0MB. Apparently, symptoms of this problem include being unable to factory reset from recovery, being stuck on the splash screen, and having TWRP demand a password.
Click to expand...
Click to collapse
I'll try that, maybe its because I restore my data after I wipe it that this happens. Another thing I've found is that after I flash and the restore my system partition that I backed up, su says that no subject binary was found, even though I've flashed it a million times. And some root apps don't work because it says no binary is found.
Related
Ok I'm really irritated right about now. I am unable to flash any custom ROMS on my phone. Actually let me rephrase, I can flash them but many things do not work. I have tried Wicked, FreeGS3 and CapROM. They all have the same issues. Let me explain.
Once the ROM is booted I get odd string of numbers and TXT in the status bar, (goes away, think nothing of it)
Root not avail/accessible by root apps.
Home button does not work
Play store missing
standard Google login prompt at first boot is missing, it never asks me to login
Using CWM 5.8.4.5 Touch Recovery
TMO GS3 Rooted with Odin no trip method
I don't get it. I am i just stuck using stock ROM? If anyone can help I would love you forever.
are you clearing /cache and dalvik-cache before you reboot to the custom rom?
mrmako777 said:
are you clearing /cache and dalvik-cache before you reboot to the custom rom?
Click to expand...
Click to collapse
If you mean clearing those after the install (in recovery completes) then no. Basically after the install I just reboot. Obviously clear and reset everything before I install though.
hd2Raz said:
Ok I'm really irritated right about now. I am unable to flash any custom ROMS on my phone. Actually let me rephrase, I can flash them but many things do not work. I have tried Wicked, FreeGS3 and CapROM. They all have the same issues. Let me explain.
Once the ROM is booted I get odd string of numbers and TXT in the status bar, (goes away, think nothing of it)
Root not avail/accessible by root apps.
Home button does not work
Play store missing
standard Google login prompt at first boot is missing, it never asks me to login
Using CWM 5.8.4.5 Touch Recovery
TMO GS3 Rooted with Odin no trip method
I don't get it. I am i just stuck using stock ROM? If anyone can help I would love you forever.
Click to expand...
Click to collapse
Touch recovery might be your problem
Sent from my SGH-T999 using Tapatalk 2
horr1blek1tten said:
Touch recovery might be your problem
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Really? A recovery can cause these kinds of issues. Haven't heard of that before. Any other thoughts? What recovery are you using?
Try TWRP 2.2.1.1
hd2Raz said:
Really? A recovery can cause these kinds of issues. Haven't heard of that before. Any other thoughts? What recovery are you using?
Click to expand...
Click to collapse
Yeah I've heard touch recovery has its problems so I don't use it. Try using the recovery rom manager gives you.
Sent from my SGH-T999 using Tapatalk 2
horr1blek1tten said:
Yeah I've heard touch recovery has its problems so I don't use it. Try using the recovery rom manager gives you.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I use TWRP and have no problems.
Do a Factory reset, wipe cache, wipe dalvik cache, fix permissions.
If that doesn't work, flash stock and reroot and try again.
I use touch recovery 5.8.4.7 and flashed it with adb. I've flashed almost everything. Cyanogenmod and every other ROM. NEVER had a problem with an instalation. Or even lost IMEI. I think people specifically aren't reading over OP's and figuring out what's safest for their devices and end up with these kind of results. Just my input.
Sent from my SGH-T999 using xda premium
Use mskips tool for our phones. It does everything you can image and then some. I have been using his tools since the HD2 and no issues to date.
The odd string of numbers that flashes upon boot in the status bar sounds like it's just identifying your external sd card. Totally normal.
OK so nothing worked. TWRP did the same thing. Tried diff ROM, same thing. I flashed back to 100% stock, unrooted ROM. Wiped the phone in the standard Android recovery. Then I rooted again, installed TWRP and flashed my ROM of choice and voila. Everything works. Problem solved. Thanks all for the inputs.
I was running AOKP Jellybean and rebooted my phone which updated the OTA Jellybean update I was unaware of (not like Verizon ever gets things done) and now it bootloops. I can access recovery, ODIN, and have tried my back ups which none of them can load /data, and have tried to simply reflash the rom, which bootloops with the roms boot animation, and have tried wiping data/cache/dalvik/battery stats and nothing worked. Is there anyway to wipe it completely and start from there, or at least get a backup working/computer-saved backup on there? It appears I can't access the phone from my computer because I last used fast charge and now the computer doesn't know it's plugged in. Am I screwed?
try to format system in cwm...and reflash your rom
good luck
Sent from my Galaxy Nexus using xda app-developers app
kizakiyuria said:
try to format system in cwm...and reflash your rom
good luck
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
No luck, it still bootloops
Go back to ics....then factory reset and then reinstall jb
If i helped you in any way then do click thanks
Sent by XDA Premium
coolprateek.kumar said:
Go back to ics....then factory reset and then reinstall jb
If i helped you in any way then do click thanks
Sent by XDA Premium
Click to expand...
Click to collapse
I second the factory reset.
Do you have access to Fastboot? If so, why not push commands to the phone and factory reset it and start fresh?
Sorry for the late reply, it still was bootlooping after a factory reset, I just got a replacement GNex. Thanks to those who replied though.
Hi guys, so I was using wicked ROM, whenever I tried to boot into recovery, it just rebooted back to system. Odin'ed back to stock, flashed twrp through goo manager app, but still no use. Any help greatly appreciated
Sent from my Nexus 7 using xda premium
eggydrums said:
Hi guys, so I was using wicked ROM, whenever I tried to boot into recovery, it just rebooted back to system. Odin'ed back to stock, flashed twrp through goo manager app, but still no use. Any help greatly appreciated
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
What methods have you tried?
adb reboot recovery is the easiest way to get to recovery
Maybe try flashing CWM, seeing if that works, and then flashing TWRP (I've never flashed TWRP through Goo Manager so I don't know how that works)?
If you don't have adb set up, get quick boot from market and try recovery through that.
If that doesn't work, I honestly don't know. I'm assuming you've done the power off then volume up+home+power at the same time trick already.
EtherealRemnant said:
What methods have you tried?
adb reboot recovery is the easiest way to get to recovery
Maybe try flashing CWM, seeing if that works, and then flashing TWRP (I've never flashed TWRP through Goo Manager so I don't know how that works)?
If you don't have adb set up, get quick boot from market and try recovery through that.
If that doesn't work, I honestly don't know. I'm assuming you've done the power off then volume up+home+power at the same time trick already.
Click to expand...
Click to collapse
With the goo app, I can boot directly into recovery, but my issue is that I get to the Recovery's splash screen, it hangs there for a second and immediately reboots back to system. I'm thinking to get the stock recovery back and try again I'm really not sure what the Hecks going on
Sent from my Nexus 7 using xda premium
Mhm OK, got cwm working, guess I'll just use that one for the time being
Sent from my Nexus 7 using xda premium
eggydrums said:
Mhm OK, got cwm working, guess I'll just use that one for the time being
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I would highly recommend putting TWRP back on there. The CWM was more for testing... people have reported issues using CWM with certain ROMs. Glad you were able to get CWM on though.
Nothing wrong with CWM.
Aerowinder said:
Nothing wrong with CWM.
Click to expand...
Click to collapse
There are a number of ROMs that do not support CWM so that statement is false. FreeGS3 loses update functionality, for example.
Also, there have been complaints in the case of CWM touch of it being too easy to wipe your entire device.
Not to mention there is no Goo Manager functionality without TWRP as well.
Lots of benefits of TWRP versus CWM. I used CWM for years then had to switch to a modified TWRP for my MAXX and was more than happy when I found out the SGS3 used TWRP as well (although I wish we had the ROM slots like the MAXX though - that was actually cool)
The statement is not false. I think FreeGS3 hasn't been updated for 4.5 months? Maybe not the best example. And I still think you should use as few automated tools as possible where flashing is concerned (Goo/ROM Manager).
It can be easy to wipe the wrong partition in CWM, if you are careless or illiterate. In the 6 months that I've used it (nearly every day), I have never once wiped the wrong partition, or my entire device. Never had a backup that wouldn't restore.
I like some of what TWRP offers. But I still experience showstopping bugs with it on my device. At this time, the devs are unable to track down the cause of the problems.
Aerowinder said:
The statement is not false. I think FreeGS3 hasn't been updated for 4.5 months? Maybe not the best example. And I still think you should use as few automated tools as possible where flashing is concerned (Goo/ROM Manager).
It can be easy to wipe the wrong partition in CWM, if you are careless or illiterate. In the 6 months that I've used it (nearly every day), I have never once wiped the wrong partition, or my entire device. Never had a backup that wouldn't restore.
I like some of what TWRP offers. But I still experience showstopping bugs with it on my device. At this time, the devs are unable to track down the cause of the problems.
Click to expand...
Click to collapse
Don't get me wrong, I've used CWM on many devices for years and even have a premium license for ROM Manager but I've seen a number of ROMs explicitly say not to use CWM, FreeGS3 was just the first that came to mind. I don't flash often because quite frankly, I have no problems with Wicked v8 and see no reason to switch to anything else.
And I am neither careless nor illiterate but I have accidentally borked things using CWM before in the past (it was a modified CWM Touch recovery) and I was not happy.
I think most of the complaints about CWM these days though come from CWM Touch, not regular CWM. Sorry TWRP has issues for you.
OK, so I'm getting a new issue, I changed to AOKP and I had problems with the ROM saying I needed to wipe data, I did, the issue persisted for few reboots, now apps won't install, and for some reason the /data folder still displays apps from my previous ROM ugh I don't know what's happening
Oh and for some reason the app exchange service kept force closing
Sent from my Nexus 7 using xda premium
eggydrums said:
OK, so I'm getting a new issue, I changed to AOKP and I had problems with the ROM saying I needed to wipe data, I did, the issue persisted for few reboots, now apps won't install, and for some reason the /data folder still displays apps from my previous ROM ugh I don't know what's happening
Oh and for some reason the app exchange service kept force closing
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Which recovery? Try erasing data, cache, and system three times each and reinstalling the ROM... If that doesn't work you might consider doing a back up of everything internally stored on your phone and then wiping the internal storage entirely and starting over.
EtherealRemnant said:
Which recovery? Try erasing data, cache, and system three times each and reinstalling the ROM... If that doesn't work you might consider doing a back up of everything internally stored on your phone and then wiping the internal storage entirely and starting over.
Click to expand...
Click to collapse
I tried. I think for some reason, the recovery isn't wiping data, even though it says so. I'm using twrp
Managed to install apps through the play website, still no go with the play store app though
Sent from my Nexus 7 using xda premium
eggydrums said:
I tried. I think for some reason, the recovery isn't wiping data, even though it says so. I'm using twrp
Managed to install apps through the play website, still no go with the play store app though
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Hmmm... Have you tried doing it through CWM? Its starting to sound like your partitions are messed up.
EtherealRemnant said:
Hmmm... Have you tried doing it through CWM? Its starting to sound like your partitions are messed up.
Click to expand...
Click to collapse
I think that's a possibility I just tried through clockwork, and it's all good now but exchange service fcs here and there
Sent from my Nexus 7 using xda premium
eggydrums said:
I think that's a possibility I just tried through clockwork, and it's all good now but exchange service fcs here and there
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Did you fix permissions?
EtherealRemnant said:
Did you fix permissions?
Click to expand...
Click to collapse
I tried while I was in twrp, it failed, something about a an error "failed to chmod data/data/ email.apk" (not exactly like that)
Sent from my Nexus 7 using xda premium
I was wondering how in the hell do i get updated to all the new updates and such.
Currently i'm rooted with Twrp 2.3.1.0, i used the toolkit back some time ago and game me the option to basically install custom roms and such but never did anything except for a kernel.
So my question is Im still on LJC, 4.1.1, and i'm sick of the pop ups for the install update, and i know its going to fail so i'd figure can i just install a custom rom and it will take care of all that crap like for instance just go ahead and start fresh and install CyanogenMod?
XxLostSoulxX said:
I was wondering how in the hell do i get updated to all the new updates and such.
Currently i'm rooted with Twrp 2.3.1.0, i used the toolkit back some time ago and game me the option to basically install custom roms and such but never did anything except for a kernel.
So my question is Im still on LJC, 4.1.1, and i'm sick of the pop ups for the install update, and i know its going to fail so i'd figure can i just install a custom rom and it will take care of all that crap like for instance just go ahead and start fresh and install CyanogenMod?
Click to expand...
Click to collapse
That could be an option if you're looking to move over to AOSP but if you wanted to stick with TW you could always just flash a ROM based off stock 4.1.2, MA7 or MC2.
Sent from my Nexus 4 using xda premium
LuigiBull23 said:
That could be an option if you're looking to move over to AOSP but if you wanted to stick with TW you could always just flash a ROM based off stock 4.1.2, MA7 or MC2.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Well i tried to install CM 10 getting stuck at bootani its seriously pissing me off. i wiped everything and followed directions and nothing is working
XxLostSoulxX said:
Well i tried to install CM 10 getting stuck at bootani its seriously pissing me off. i wiped everything and followed directions and nothing is working
Click to expand...
Click to collapse
Will need more info, like your exact installation process to help you any further.
Sent from my SGH-T999 using xda premium
LuigiBull23 said:
Will need more info, like your exact installation process to help you any further.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Okay Well i wiped(factory reset under TWRP 2.5) then did advanced wipe and chose system option; then wiped. Then i had flashed CM10 then after flashed GApps, rebooted and bam into bootloop, and as i typing this i 'm doing the avatar rom and same thing bootloop. also i should mention it skips the md5 check and says there is no md5 file.
Just tried rootbox same thing gets as far as the boot ani then bam sits there
XxLostSoulxX said:
Okay Well i wiped(factory reset under TWRP 2.5) then did advanced wipe and chose system option; then wiped. Then i had flashed CM10 then after flashed GApps, rebooted and bam into bootloop, and as i typing this i 'm doing the avatar rom and same thing bootloop. also i should mention it skips the md5 check and says there is no md5 file.
Click to expand...
Click to collapse
When you say CM 10 I'm assuming you're referring to CM 10.1? If so make sure your using the correct gapps and if you still face issues I suggest redownloading the ROM and gapps through Goomanager, make sure the MD5 match up, and then fully wipe and flash again. Keep me updated.
Sent from my Nexus 4 using xda premium
LuigiBull23 said:
When you say CM 10 I'm assuming you're referring to CM 10.1? If so make sure your using the correct gapps and if you still face issues I suggest redownloading the ROM and gapps through Goomanager, make sure the MD5 match up, and then fully wipe and flash again. Keep me updated.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Yess 10.1, and yes i did exactly as it says im uploading a youtube video for you to watch so you can see what im doing exactly.
Just followed Rootbox instructions as i just literally tried that rom out, and same results. i cant match the md5 as it skips it during install process as it says there is no md5 file
XxLostSoulxX said:
Click to expand...
Click to collapse
Thanks. I'll watch it and get back to you asap.
Sent from my Nexus 4 using xda premium
---------- Post added at 02:36 AM ---------- Previous post was at 02:06 AM ----------
XxLostSoulxX said:
Yess 10.1, and yes i did exactly as it says im uploading a youtube video for you to watch so you can see what im doing exactly.
Just followed Rootbox instructions as i just literally tried that rom out, and same results. i cant match the md5 as it skips it during install process as it says there is no md5 file
Click to expand...
Click to collapse
Ok I see what you're doing. My brother had a similar problem and there seems to be something wrong with the kernel script not running through properly and to fix this you will need to perform a factory reset as the OP instructs BUT I would try it twice. Once before the flash and another after the flash. Try it and if that doesn't work try the same steps with a 3rd party kernel. Flashing a kernel after the ROM is not recommended but if it helps to boot up the phone then you'll know it was the stock kernel. Let me know
Sent from my Nexus 4 using xda premium
LuigiBull23 said:
Thanks. I'll watch it and get back to you asap.
Sent from my Nexus 4 using xda premium
---------- Post added at 02:36 AM ---------- Previous post was at 02:06 AM ----------
Ok I see what you're doing. My brother had a similar problem and there seems to be something wrong with the kernel script not running through properly and to fix this you will need to perform a factory reset as the OP instructs BUT I would try it twice. Once before the flash and another after the flash. Try it and if that doesn't work try the same steps with a 3rd party kernel. Flashing a kernel after the ROM is not recommended but if it helps to boot up the phone then you'll know it was the stock kernel. Let me know
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
tried with 3rd party kernel i.e matrix kernel and nope still not working WTF.
XxLostSoulxX said:
tried with 3rd party kernel i.e matrix kernel and nope still not working WTF.
Click to expand...
Click to collapse
No AOSP ROMs at all? I would go back to complete stock, update to MA7 or MC2 then reroot and try flashing again.
Sent from my Nexus 4 using xda premium
XxLostSoulxX said:
Okay Well i wiped(factory reset under TWRP 2.5) then did advanced wipe and chose system option; then wiped. Then i had flashed CM10 then after flashed GApps, rebooted and bam into bootloop, and as i typing this i 'm doing the avatar rom and same thing bootloop. also i should mention it skips the md5 check and says there is no md5 file.
Just tried rootbox same thing gets as far as the boot ani then bam sits there
Click to expand...
Click to collapse
Wipe 3X. Data, System, cache, Dalvik.
Anything less and you're bound to get problems.
Skripka said:
Wipe 3X. Data, System, cache, Dalvik.
Anything less and you're bound to get problems.
Click to expand...
Click to collapse
i did; wiped data 3x, system 3x, cach and dalvik 3x, installed cm 10.1 then right after Gapps but again says skip md5 check there is no md5 file and bootloops on CM 10 boot animation
XxLostSoulxX said:
i did; wiped data 3x, system 3x, cach and dalvik 3x, installed cm 10.1 then right after Gapps but again says skip md5 check there is no md5 file and bootloops on CM 10 boot animation
Click to expand...
Click to collapse
Does it bootloop...or have you just been impatient? 1st boots of a new ROM can take a while.
Presuming it is stuck at boot splash...either an unstable build, or a corrupt download are possible. Verify the MD5 of your downloads.
Skripka said:
Does it bootloop...or have you just been impatient? 1st boots of a new ROM can take a while.
Presuming it is stuck at boot splash...either an unstable build, or a corrupt download are possible. Verify the MD5 of your downloads.
Click to expand...
Click to collapse
did you watch my video? it was sitting for 5 minutes,on the cyanogenmod boot animation.
i just restored and back on ljc perfectly fine. but i guess my phone does not like flashing as i said and in the video it hangs and skips the md5 check
okay i used Toolkit 4.1.0 and chose to flash to stock and it didnt work because i still have root and still on ljc, and same setup as before, i cant update to ma7, however i chose to install stock recovery, but i know if i do update it will fail.
EDIT: **** it wont even reboot to install the update. says rebooting now and nothing. F THIS PHONE.
I CANT EVEN UNROOT
XxLostSoulxX said:
did you watch my video? it was sitting for 5 minutes,on the cyanogenmod boot animation.
i just restored and back on ljc perfectly fine. but i guess my phone does not like flashing as i said and in the video it hangs and skips the md5 check
Click to expand...
Click to collapse
Every device handles things differently, including first boot up times. It can take anywhere from 5-10min. So don't worry about how short Josh's boot up time was in his video. I highly suggest you:
1) Wipe system, data, cache/dalvik 3x
2) flash ROM and Gapps
3) Go back and perform a "factory reset" 3x
4) Reboot
5) Let phone sit at most 15min.
Just do this one final time exactly as instructed and assuming you've tried earlier nighties, if it doesn't boot up by 15 min then you'll know it's the phone and NOT you.
Sent from my Nexus 4 using xda premium
LuigiBull23 said:
Every device handles things differently, including first boot up times. It can take anywhere from 5-10min. So don't worry about how short Josh's boot up time was in his video. I highly suggest you:
1) Wipe system, data, cache/dalvik 3x
2) flash ROM and Gapps
3) Go back and perform a "factory reset" 3x
4) Reboot
5) Let phone sit at most 15min.
Just do this one final time exactly as instructed and assuming you've tried earlier nighties, if it doesn't boot up by 15 min then you'll know it's the phone and NOT you.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
what do i do if its the phone? i cant even unroot, i cant even flash to stock WTF! tried using toolkit but nothing. only thing i accomplished was being able to install stock recovery, and went back into android and chose to reboot to install update from OTA wont even reboot when it says rebooting now.
XxLostSoulxX said:
what do i do if its the phone? i cant even unroot, i cant even flash to stock WTF! tried using toolkit but nothing. only thing i accomplished was being able to install stock recovery, and went back into android and chose to reboot to install update from OTA wont even reboot when it says rebooting now.
Click to expand...
Click to collapse
Ok... Do you still have that LJC nandroid backup?
Sent from my Nexus 4 using xda premium
LuigiBull23 said:
Ok... Do you still have that LJC nandroid backup?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
correct yeah because i restored so i can atleast use my phone to try to fix it using toolkit
EDIT: Hooray i finally got it that did the trick this time. however basband is still LJC but is 4.2.2 because i went through setup this time and was able to boot up
Alright, im not completely new to rooting but I have encountered a new problem.
I rooted my phone through odin (galaxy s3 T999), had some hiccups with that so I ended up downloading the stock rom tar and reflashed using that, problem solved good to go still rooted. awesome.
So, I attempted to flash the cyanogen rom using clockwork mod. it wouldn't come past the load screen, went into clockwork mod to recover my backup but for some reason it wouldn't let me access the SD card to get it. next thought was to go back to odin and flash the same file I used previously to get back to where I was, for some reason this is not working, I can get to download, use odin to flash it, says success and all that, then upoon rebooting it stays at the Samsung loading screen.
So from there I went and downloaded the GS3 toolkit and tried all of their recovery files, all having the same issue. about 18 flashes later I tried reformatting from the phone itself, same issue with the samsung logo being stuck. And now, I am currently baffled, anyone wanna help me out? I have a feeling it has something to do with the .pit option on odin, but I am not that advanced and its just a hunch. so...thanks in advance guys!
So I understand not to touch pit, roger, reading other posts makes that clear, but still cant find a fix, the top right of my download says
ODIN MODE
Product Name SGH-T999
Custom Binary yes: 19 counts
Current Binary Samsung Offical
System Status Custom
Qualcomm secureboot Enable
Okay, what is the current state of the device?
Whst do you see when you boot into recovery ( take battery out of phone the put it back in and do the following: hold volume up, home button and power button, let go of all buttons when you feel the phone vibrate and blue text flashes in the upper left corner of the screen)?
Sent from my SGH-T999 using XDA Premium 4 mobile app
I just tried to send a rom over that had CWM 6.0.2.3 and it installed that, but still stuck on logo. going into recovery I am in CWM 6.0.2.3
have the standard options wipe/factory, install from zip etc.
You flashed a rom that had cwm 6.0.2.3 or did you flash a rom while on 6.0.2.3?
Sent from my SGH-T999 using XDA Premium 4 mobile app
I'd say about 98% of the time, when it hangs like that you just need to factory reset.
Sent from my SGH-T999L using XDA Premium 4 mobile app
Flashed a rom that had 6.0.2.3. I do not have any roms on my ZIP, been doing everything through ODIN. Very confused as to why it suddenly stopped working.
DocHoliday77 said:
I'd say about 98% of the time, when it hangs like that you just need to factory reset.
Sent from my SGH-T999L using XDA Premium 4 mobile app
Click to expand...
Click to collapse
tried to factory reset and it does the same logo stuck business. That was the last thing i tried after attempting to back up and reflash numerous times. tried flashing again recently, it will install CWM if it is attached to the rom but still gets stuck on the logo. tried re installing odin as well, it is working as usual, starts, restarts the phone, sits awhile, success. then i restart the phone and never get past logo.
I would do what Doc said.
If it still doesnt work, download a rom of your choice (in the t-999 section) and do a full wipe before flashing the rom you picked.
Sent from my SGH-T999 using XDA Premium 4 mobile app
Da Kine said:
I would do what Doc said.
If it still doesnt work, download a rom of your choice (in the t-999 section) and do a full wipe before flashing the rom you picked.
Sent from my SGH-T999 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
what do you mean by full wipe, factory reset? or something else?
connorjiy said:
what do you mean by full wipe, factory reset? or something else?
Click to expand...
Click to collapse
When flashing a new rom, you have to do a full wipe or youll run into problems like you are currently having.
If you dont know what a full wipe is, then stop what you are doing and put your phone down. Just about every rom thread here on xda explains what a full wipe is, it will be in the first post of the thread.
Like I said, find a rom you like in the t-999 section and flash it after doing a full wipe.
Sent from my SGH-T999 using XDA Premium 4 mobile app
Da Kine said:
When flashing a new rom, you have to do a full wipe or youll run into problems like you are currently having.
If you dont know what a full wipe is, then stop what you are doing and put your phone down. Just about every rom thread here on xda explains what a full wipe is, it will be in the first post of the thread.
Like I said, find a rom you like in the t-999 section and flash it after doing a full wipe.
Sent from my SGH-T999 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Looked it up, that is what I do by default, didn't know thats what was considered a full wipe, just tried it with similar results, didn't know about the dalvik cache though. im on a work computer so I cannot currently DL a new rom from the site, I hope thats what the issue is, but I still cannot see why my other ones would suddenly not work.
connorjiy said:
tried to factory reset and it does the same logo stuck business. That was the last thing i tried after attempting to back up and reflash numerous times. tried flashing again recently, it will install CWM if it is attached to the rom but still gets stuck on the logo. tried re installing odin as well, it is working as usual, starts, restarts the phone, sits awhile, success. then i restart the phone and never get past logo.
Click to expand...
Click to collapse
I'm just not sure what you mean by it installing CWM attached to a Rom? Recoveries shouldn't be included with a Rom.
Odin flash the root66 firmware, then reboot to STOCK recovery and factory reset. This will wipe all user data, including your internal sd card. Then try rebooting again.
Sent from my SGH-T999L using XDA Premium 4 mobile app