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
Related
Background - I rooted and installed CWM recovery through Toolkit. Realized every time I "Factory Reset" in CWM recovery it would complete wipe my internal storage. Ok so I installed TWRP using the tookit. Then installed other roms and notice EVERY rom I've installed errors right after boot-up with "Unfortunately, the process com.android.phone has stopped". Upgrading to latest TWRP didn't fix it.
I've tried to wipe everything. Even tried format internal storage. Flash multiple roms again and still same error.
I'm thinking it was CWM "Factory Reset" wiping all my internal storage could of messed up my internals... maybe the file format? Something else I can try?
Phone is still usable, just every time it starts up - error shows up twice. It might pop up again once in a while when i'm using it.
BTW when I was "Factory Reset" in CWM it always made my phone "Activate with sprint" again... like it was a brand new phone.
Try odining back to stock then redo root and ROM flashing and see if that helps.
Sent from my SPH-L900 using Tapatalk 2
slick_rick said:
Try odining back to stock then redo root and ROM flashing and see if that helps.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
Should I 1st flash stock recovery then odining back to stock ?
mxl180 said:
Should I 1st flash stock recovery then odining back to stock ?
Click to expand...
Click to collapse
no, if you ODIN back to the stock unrooted with the file from -viperboy-'s thread it will change your recovery as well.
t3project said:
no, if you ODIN back to the stock unrooted with the file from -viperboy-'s thread it will change your recovery as well.
Click to expand...
Click to collapse
holy crap. Ran Viper's ODIN instructions back to stock now. Error show up again.
mxl180 said:
holy crap. Ran Viper's ODIN instructions back to stock now. Error show up again.
Click to expand...
Click to collapse
Does this set the flash timer to ZERO so I can return to sprint?
mxl180 said:
Does this set the flash timer to ZERO so I can return to sprint?
Click to expand...
Click to collapse
No....but flash counter should not matter.
Sent from my SPH-L900 using xda app-developers app
00mred00 said:
No....but flash counter should not matter.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
Well reverting back to CWM fixes the process error, but it also completely wipes the device in recovery. So every time I wipe it needs to "hands-free activate" w/ sprint and lose all my internal storage. Oh well, no process errors!
Hey guys, I'm really new to rooting, flashing roms, and Android in general (I've used iOS since 2007 until a month ago... please have mercy on my soul). I have an AT&T GN2 that I would like to remove the bloatware from, hence why I began investigating rooting, but it's snowballed into my desire to try out some of the amazing ROMs that the developers here have produced. Since the Note 2 uses the Exynos 4, I rooted using the ExynosAbuse exploit and downloaded Titanium Backup to freeze the AT&T apps. So far, so good.
However, I am wanting to get into how to flash custom ROMs, like CyanogenMod, so I downloaded the CWM RomManager and flashed the CWM Recovery. I downloaded the CyanogenMod 10.1 release for the i317 model (here: http://forum.xda-developers.com/showthread.php?t=2024495) and the latest gApps package (for 4.2.1), and flashed both from CWM RomManager. When it rebooted, it showed the CyanogenMod boot screen, but it appears to be stuck there. I'm not sure what to do at this point, and am hoping I didn't brick my phone. Is there anything I can do at this point?
Use the three button combo to get into recovery, should be volume up, home, and power, and then wipe data or install a stock rooted ROM. That should help get you to a bootable stage.
Sent from my GT-N7105 using xda premium
Have you changed kernel???
Sent from my MT11i using xda app-developers app
id10terrordfw said:
Use the three button combo to get into recovery, should be volume up, home, and power, and then wipe data or install a stock rooted ROM. That should help get you to a bootable stage.
Sent from my GT-N7105 using xda premium
Click to expand...
Click to collapse
When I booted into recovery, I got the CWM recovery (which is a good thing, I suppose). I wiped the cache, and then installed the CM 10.1 zip and gApps zip. However, I think I still need to wipe data/factory reset, right?
So, at this point, I've:
1. Rooted the device using Chainfire's ExynosAbuse apk (super easy).
2. Installed RootChecker (success) and TI backup (froze bloatware apps).
3. Downloaded CWM RomManager.
4. Flashed CWM Recovery.
5. Downloaded CM 10.1 port for i317 (the AT&T GN2 model) and the 4.2.1 gApps zips.
6. Chose to install ROM from SD card in RomManager, added both CM 10.1 and gApps, and only selected install (did not wipe cache or user data at this point).
7. Received blue CyanogenMod boot screen... excited... but it remains on the boot screen. Sad face.
8. Removed battery to power the device off, placed battery back in, and then booted into recovery mode (CWM recovery).
9. Installed the CM 10.1 zip and gApps zip from SD, then wiped cache.
10. ???
Wipe data factory reset. Wipe cache/dalvik. Flash cm, flash gapps. Reboot
And dont use rom manager. Do it in recovery
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Peleus16 said:
Have you changed kernel???
Sent from my MT11i using xda app-developers app
Click to expand...
Click to collapse
This is a great point, at no point op has mentioned kernel.
Sent from my SAMSUNG-SGH-I317 using xda premium
cdshepherd said:
Wipe data factory reset. Wipe cache/dalvik. Flash cm, flash gapps. Reboot
And dont use rom manager. Do it in recovery
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
Okay, booted into CMW recovery and performed all in that order. It booted! Hurrah. Only problem: the AOSP keyboard crashes constantly, making text input not possible. Sigh...
NowhereOutThere said:
Okay, booted into CMW recovery and performed all in that order. It booted! Hurrah. Only problem: the AOSP keyboard crashes constantly, making text input not possible. Sigh...
Click to expand...
Click to collapse
Boot back into recovery and fix permissions. That may help
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
cdshepherd said:
Boot back into recovery and fix permissions. That may help
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
Okay, I booted into recovery mode and fixed permissions... the keyboard still crashes, which means I can't type anything. Do I have to do anything with the kernel? I didn't wipe the dalvik cache, should I have done that?
EDIT: wiped dalvik cache, didn't do anything... apparently, this was a fine release so I'm not sure what could be causing the keyboard issues.
NowhereOutThere said:
Okay, I booted into recovery mode and fixed permissions... the keyboard still crashes, which means I can't type anything. Do I have to do anything with the kernel? I didn't wipe the dalvik cache, should I have done that?
EDIT: wiped dalvik cache, didn't do anything... apparently, this was a fine release so I'm not sure what could be causing the keyboard issues.
Click to expand...
Click to collapse
Im not exactly sure either. I have yet to flash cm. Read the cm thread?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
cdshepherd said:
Im not exactly sure either. I have yet to flash cm. Read the cm thread?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
So what ROM are you using? I just picked cyanogenmod because I've heard of it before, but I would like something that works. Is there a way to add another ROM onto the phone's storage, as I don't have an SD card... And since I can't type anything, it's not like I can download it from the phone's browser?
NowhereOutThere said:
So what ROM are you using? I just picked cyanogenmod because I've heard of it before, but I would like something that works. Is there a way to add another ROM onto the phone's storage, as I don't have an SD card... And since I can't type anything, it's not like I can download it from the phone's browser?
Click to expand...
Click to collapse
Plug it into your computer and see if you can mount your internal sd. If you can download a new rom to your computer and transfer it to sd. Did you make a backup before flashing?
Im just running stock rooted for now.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Well, I'm downloading CleanROM right now. I also downloaded another cm 10.1 file just in case, perhaps it's because I downloaded it on the mobile Chrome browser that I'm having problems? I also downloaded a kernel from the thread to help with performance. However, if I can't get these on the phone, it doesn't matter. Since I'm on a Mac, I have to use Android File Transfer, and it isn't registering my phone, unfortunately. I may have to go out and buy a cheap SD card and throw the files on there. It may not hurt to have one around, anyways.
Text yourself the download link to CleanRom. :thumbup:
And chrome shouldnt have made a difference. I take it you didnt make a nandroid backup before you flashed cm?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
cdshepherd said:
Text yourself the download link to CleanRom. :thumbup:
And chrome shouldnt have made a difference. I take it you didnt make a nandroid backup before you flashed cm?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
No... I thought that a backup of the original ROM was made when flashing CWM recovery, but I am a noob and that did not happen. Unfortunately, the browser doesn't even work! So I cannot text myself the link for the download. I should be able to flash a zip file from a micro sdhc, right?
Flash the right GAPPS, the crashing keyboard is a symptom of incorrect GAPPS. The December one is for 4.2.1 only, which is what CM10.1 is based on. Make sure you flash the right GAPPS with the right CM version.
Sent from my GT-N7105 using xda premium
The CM you linked in the OP is CM10 not 10.1, so you flashed the wrong GAPPs
ManelScout4Life said:
The CM you linked in the OP is CM10 not 10.1, so you flashed the wrong GAPPs
Click to expand...
Click to collapse
Oh... crap. Is there any way I can get the correct gApps on my phone? Ugh... I'm going to have access to a Windows machine today, so I can download the correct GAPPS and put them on my flash drive. I can still put it in USB debugging mode, but will the PC recognize it? Android File Transfer software for Mac does not recognize the phone any more, so I'm a bit limited in what I can do. Unless, like I said before, I can just pop in an SD card with the correct file.
Just grab goo manager from the market and dl the correct gapps to your phone. Either that or use your phones browser. No need for a pc. Boot in recovery, wipe cache and dalvik and flash correct gapps. Should be gtg.
Edit: just saw your browser isn't working. Goo manager's your best bet. Could always try another browser from the market as well. Good luck.
NowhereOutThere said:
Oh... crap. Is there any way I can get the correct gApps on my phone? Ugh... I'm going to have access to a Windows machine today, so I can download the correct GAPPS and put them on my flash drive. I can still put it in USB debugging mode, but will the PC recognize it? Android File Transfer software for Mac does not recognize the phone any more, so I'm a bit limited in what I can do. Unless, like I said before, I can just pop in an SD card with the correct file.
Click to expand...
Click to collapse
While in recovery plug usb into computer (make sure drivers are installed) in recovery menu navigate to mount usb storage. See if that works
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
I flashed TWRP 2.5 and then flashed Task's AOKP 4/9 ROM and everything went down hill from there. The phone kept rebooting after a minute or so, so I did a factory reset and reflashed the ROM. That didn't help, it actually made it worse in that it would not get past the kernel splash screen. So I did another wipe and the same thing. I wiped again and flashed an older version of AOKP 4/5 and again would only get to the kernel splash. After another hour or so I decided I'll just go back to rooted stock, so using Odin 3 3.07 I flashed my trusted root69.stock_ATT_I747UCALG1 image and now it just stays on the Samsung screen.
I've run out of thoughts on what the hell is the problem and thought I'd ask.
Anyone have any suggestions on what I can do to get this paper weight working again?
dhostetter said:
I flashed TWRP 2.5 and then flashed Task's AOKP 4/9 ROM and everything went down hill from there. The phone kept rebooting after a minute or so, so I did a factory reset and reflashed the ROM. That didn't help, it actually made it worse in that it would not get past the kernel splash screen. So I did another wipe and the same thing. I wiped again and flashed an older version of AOKP 4/5 and again would only get to the kernel splash. After another hour or so I decided I'll just go back to rooted stock, so using Odin 3 3.07 I flashed my trusted root69.stock_ATT_I747UCALG1 image and now it just stays on the Samsung screen.
I've run out of thoughts on what the hell is the problem and thought I'd ask.
Anyone have any suggestions on what I can do to get this paper weight working again?
Click to expand...
Click to collapse
Not sure about the problem with aokp. But your bootloop just pull the battery, reinstall battery, go into stock recovery, factory reset and voilà
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
KorGuy123 said:
Not sure about the problem with aokp. But your bootloop just pull the battery, reinstall battery, go into stock recovery, factory reset and voilà
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
This will do it. Flashing back to 4.0.4 will bootlopp until you factory reset in stock recovery
Sent from my SAMSUNG-SGH-I747 using xda premium
Same thing happened to me. Boot loop with 4/9 AOKP task so I Odin to the same file as you but that ran just fine. I would try to Odin again.
Oh and after stock with root I flashed 4/9 and all was good. By chance did you have custom boot animation?
Sent from my SGH-I747 using xda premium
drock212 said:
Same thing happened to me. Boot loop with 4/9 AOKP task so I Odin to the same file as you but that ran just fine. I would try to Odin again.
Oh and after stock with root I flashed 4/9 and all was good. By chance did you have custom boot animation?
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Yes I had a custom boot image.
Getting ready to factory reset and reboot. Hope all goes well.....
dhostetter said:
Yes I had a custom boot image.
Getting ready to factory reset and reboot. Hope all goes well.....
Click to expand...
Click to collapse
I think it's the custom boot causing this issue. Anyway good luck. I know my heart skipped a beat when my phone would boot loop while to get into recovery. Once I Odined back to stock with root first/only thing I downloaded was goomanager and installed TWRP then flashed 4/9.
Sent from my SGH-I747 using xda premium
drock212 said:
I think it's the custom boot causing this issue. Anyway good luck. I know my heart skipped a beat when my phone would boot loop while to get into recovery. Once I Odined back to stock with root first/only thing I downloaded was goomanager and installed TWRP then flashed 4/9.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
I'm back up and running again. A little embarrassed I forgot the factory reset last night.
Thanks for the reminder!
AOKP is a great ROM.
When flashing ROMs always follow these steps and you will be fine.
1- nandroid backup
2- format system
3- wipe cache
4- wipe Dalvik
5- factory reset.
Most suggest doing each 3 times.
6- install ROM and reboot
7- flash gapps
Let sit for 10 minutes.
Follow those instructions and everything will be fine.
Sent from my SGH-I747M
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
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.