Related
Hey,
Im on nexus i9023 with NSCollab rom and netarchy
Today i decided i wanted to try Cyanogen mod and downloaded it throug rommanager, al good up until that point!
Download was complete and i selected to contineu with the rom, it asked me if i wanted to backup my current rom and wipe cache/dalvik wich i said yes to!
Then it shutdown and stayed on the Google logo with the unlocked lock , i left it hanging to see what would happen but it just remained like it was stuck, so i decided to pull the battery and fired up again, all seems back to normal still running NSCollab!
But i cant get into Clockwork recovery anymore, it always shows the Google logo as said before, as we all need CWR, can you guys tell me what to do or what is going on?
Thnx!
If you can't get into CWR through the bootloader, just flash it again using fastboot like you did the first time.
deejaylobo said:
If you can't get into CWR through the bootloader, just flash it again using fastboot like you did the first time.
Click to expand...
Click to collapse
or just flash the recovery in rom manager again
bringonblink said:
or just flash the recovery in rom manager again
Click to expand...
Click to collapse
did this, didnt help, still stuck on logo!
ROM Manager has never worked right for me when I try updating CWR.
Can you explain exactly what happens when you try to get into recovery from the bootloader? Your phone reboots and is stuck on the Google logo? Or do you get a message along the lines of "no recovery img"? or what?
deejaylobo said:
ROM Manager has never worked right for me when I try updating CWR.
Can you explain exactly what happens when you try to get into recovery from the bootloader? Your phone reboots and is stuck on the Google logo? Or do you get a message along the lines of "no recovery img"? or what?
Click to expand...
Click to collapse
Yeah stuck on google logo without message!
I reflashed the recovery image through command, like when first setting up CWR, and it worked, i have recovery back!
Thnx!
Hello guys, I recently received my refurb phone back from Bestbuy. I flashed MIUI on to it and about 2 days later I'm caught in this boot loop. After reading several threads, I called and got the battery replaced. That did not resolve my issue. I used GTG's unbrick method with KEIS downloaded. ODIN "passed" it and I got rebooted into 3e recovery (not sure where my clockworkmod recovery went, unless that went with the reset). I selected reboot now, and I'm still stuck in the boot loop with samsung popping up. Any ideas?
Thanks in advance
Try this... all credit and thanks to qkster, one of the most helpful people on the infuse forums. http://forum.xda-developers.com/showthread.php?t=1524081
I would run Odin again
Sent from my SGH-I997 using XDA
I've now tried Heimdall, it allowed the phone to turn on. When I turned the phone off it got caught back in the boot loop again. So I retried while checking "flash bootloaders". All seemed to be well, it turned off and the battery charge indicator came on. I turned it back on and checked a few things out, I didn't download or change anything. Shut it back down and it's caught back in the boot loop again.
I've retried Odin 3 times too.
What the heck do I do now?!
j_e said:
I've now tried Heimdall, it allowed the phone to turn on. When I turned the phone off it got caught back in the boot loop again. So I retried while checking "flash bootloaders". All seemed to be well, it turned off and the battery charge indicator came on. I turned it back on and checked a few things out, I didn't download or change anything. Shut it back down and it's caught back in the boot loop again.
I've retried Odin 3 times too.
What the heck do I do now?!
Click to expand...
Click to collapse
after using the one click did you do a factory reset/wipe with in 3e recovery...or if you using one click, and put cwm on just do a data/factory wipe to clean all...
what i would do...because something is not cleaning...
do the one click reboot
and do the one click to get cwm....
then go into CWM
When in CWM:
1. Wipe data/factory reset.
2. Wipe Cache.
3. Go to Advance: wipe dalvik cache.
4 Go back and into Mount and Storage: format system, format data, format cache.
5. Go back and one click again to put gb back on with nothing left over...if you want to stay stock...of if you want to add custom rom
put cwm again to go to a custom rom...
may seem time consuming but sometimes it take a few strokes to clean up...
believe me i have had to do this before...
and let us know...kk
Ok guys, thanks for all of the replies.
I've tried and tried this Heimdall now 4 times, twice clicking flash bootloaders. I've gone into 3e recovery and wiped everything.
It will start and get to the setup wizard (for first time use). I click through it and I get to the main screen. I locked the screen and went to unlock it and after I "swiped" it shut down and went back into the boot loop. I retried the Heimdall again, samething happened with the setup wizard, got to the main screen, unplugged the USB cable and it shut down and back into the boot loop.
Any other ideas? I'd love to use this thing...I just got it back and haven''t been able to use it because of this.
Something similar happened to me like a week ago ..i did not know what to do so i odin back to stock about 7 times before i could reach de home screen,the first 3 times i had bootloops,3 other time i went to initial setup but as soon as i was finishing it ..bootloops,the last time i tried i was able to go into the homescreen but it had some apk left over from previous flash..so i use sgs kernel flasher to flash infusion and get back my red recovery ,then i flashed qster total wipe and flashed emencipation.....im so scared now ..i dont think i will flash anything for a while...anyway hopefully you will find the perfect combination to save your infuse good luck
Sent from my SGH-I997 using Tapatalk 2
iTchill said:
Something similar happened to me like a week ago ..i did not know what to do so i odin back to stock about 7 times before i could reach de home screen,the first 3 times i had bootloops,3 other time i went to initial setup but as soon as i was finishing it ..bootloops,the last time i tried i was able to go into the homescreen but it had some apk left over from previous flash..so i use sgs kernel flasher to flash infusion and get back my red recovery ,then i flashed qster total wipe and flashed emencipation.....im so scared now ..i dont think i will flash anything for a while...anyway hopefully you will find the perfect combination to save your infuse good luck
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
How do I use SGS kernal flasher if I can't get it to turn on? From what I read it requires root and superuser?
So I retired Odin again with no luck. Retried Heimdall by selecting Flash Bootloaders, loaded to main screen, it went back into the boot loop after I locked the phone.
update #3, got into 3e recovery and it rebooted itself from there too.
If you flashed miui you must be rooted ...and yes to use shs kernel flasher you must be in the homescreen ..can you acces cwm? If so flash qster total wipe
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2
iTchill said:
If you flashed miui you must be rooted ...and yes to use shs kernel flasher you must be in the homescreen ..can you acces cwm? If so flash qster total wipe
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
I may be confused now, when I reflashed to stock didn't that unroot my phone? 3e recovery is all I can get to.
j_e said:
I may be confused now, when I reflashed to stock didn't that unroot my phone? 3e recovery is all I can get to.
Click to expand...
Click to collapse
When you reflash to stock, it does not take out the root unless you erase the proper files yourself. The only thing you lose is the modded 3e recovery and CWM recovery.
Sent from my SAMSUNG-SGH-I997 using xda premium
So, today I trade my HTC One for a RAZR XT925, $350, and a water proof 32GB Sandisk ultra sd card on Kijiji. I thought it was kinda weird to get all of this stuff, but it seemed fine at the time. Afterwards however, I found out that every time you turn off or reboot the phone, it tried to go into recovery mode or something with the android guy and a bar at the bottom in a loop and always factory reset the phone, so no matter what, every time you turned it off, it'd reset it. After hours and hours of work, I have the bootloader unlocked, rooted, CWM installed, and Cynogenmod also installed. It no longer factory resets it (I think, but i sent a text to a random number and when I rebooted it was still there), however, everytime i power off and power on, it goes into recovery mode. This is very annoying and will make it very hard to sell again, but if I can fix this last thing, I'll have a solid phone until the waterproof S4 comes out as well as having made like $100.
So basically, I need to know what to do to make it boot into the rom by default and not the recovery. Also, I searched it up and someone else had a problem where they kept booting into AP fastboot mode I think, I tried that line, it said successful, but it didnt work. For me, it's booting into the recovery by default.
Does it boot into stock recovery?
Sent from my Galaxy Nexus using xda premium
recovery
jmcdonald58 said:
Does it boot into stock recovery?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I root it, unlocked the boot loader, flashed cwm recovery, and installed CyanogenMod. Now it boots into cwm recovery by default and if I click reboot system now, it just boots back into cwm. Only way to get to the system is to go to the boot menu by pressing all three buttons and selecting boot normally.
Stock recovery is gone. Cwm asked to replace it so that the phone doesn't reinstall it on reboot. Cwm doesn't, but when the phone booted it stock recovery, it used to get wiped.
roguezz said:
I root it, unlocked the boot loader, flashed cwm recovery, and installed CyanogenMod. Now it boots into cwm recovery by default and if I click reboot system now, it just boots back into cwm. Only way to get to the system is to go to the boot menu by pressing all three buttons and selecting boot normally.
Stock recovery is gone. Cwm asked to replace it so that the phone doesn't reinstall it on reboot. Cwm doesn't, but when the phone booted it stock recovery, it used to get wiped.
Click to expand...
Click to collapse
Strange If it was me I would try a toolkit and redo the whole process something went wrong somewhere wish I could help Good Luck
recovery
jmcdonald58 said:
Strange If it was me I would try a toolkit and redo the whole process something went wrong somewhere wish I could help Good Luck
Click to expand...
Click to collapse
No the problem was in stock. When I got it it wasn't rooted or anything, rooting helped fix the problem partially by not making it wipe every time I boot it. Now the only problem is that whenever I boot it up after a shut down or restart, it boots into recovery mode instead of the ROM.
roguezz said:
No the problem was in stock. When I got it it wasn't rooted or anything, rooting helped fix the problem partially by not making it wipe every time I boot it. Now the only problem is that whenever I boot it up after a shut down or restart, it boots into recovery mode instead of the ROM.
Click to expand...
Click to collapse
did you ever find a solution for this? I just bought a used phone and am facing the same problem - I can't even boot into recovery, it will just start bootlooping again. Only thing that seems to be working is fastbood mode. (or regular reboot, but then everything is wiped every time)
coldtech said:
did you ever find a solution for this? I just bought a used phone and am facing the same problem - I can't even boot into recovery, it will just start bootlooping again. Only thing that seems to be working is fastbood mode. (or regular reboot, but then everything is wiped every time)
Click to expand...
Click to collapse
Fastboot the stock ROM. That should return the phone to it's bone stock condition.
Sent from my DROID RAZR HD using Tapatalk 4
mentose457 said:
Fastboot the stock ROM. That should return the phone to it's bone stock condition.
Sent from my DROID RAZR HD using Tapatalk 4
Click to expand...
Click to collapse
trying right now. RSDLite is giving me an "unknown fastboot command getvar" error...still trying to figure out why.
coldtech said:
trying right now. RSDLite is giving me an "unknown fastboot command getvar" error...still trying to figure out why.
Click to expand...
Click to collapse
I wouldnt mess with RSDLite. Google gave us fastboot for a reason.
mentose457 said:
I wouldnt mess with RSDLite. Google gave us fastboot for a reason.
Click to expand...
Click to collapse
is there an alternative to flash the stock ROM on a locked device?
coldtech said:
is there an alternative to flash the stock ROM on a locked device?
Click to expand...
Click to collapse
Use this utility: http://forum.xda-developers.com/showthread.php?t=2241788
Use the 'Lite' version as it includes the stock rom.
mentose457 said:
Use this utility: http://forum.xda-developers.com/showthread.php?t=2241788
Use the 'Lite' version as it includes the stock rom.
Click to expand...
Click to collapse
Thanks for the hint, will give it a try. RSDLite just completed flashing, but the odd behaviour of the phone is still the same. Guess I might just have a broken phone... :/
mentose457 said:
Use this utility: http://forum.xda-developers.com/showthread.php?t=2241788
Use the 'Lite' version as it includes the stock rom.
Click to expand...
Click to collapse
After a few hours, I (somehow) ended up being able to enter recovery. On the downside though, now it always goes automatically into fastboot, because everything seems to be screwed up. I even got CWM installed though (unlocked the device because I didn't know what else to do).
Now every time it goes into fastboot, the reason given is: "sticky bit fastboot"
Any ideas left?
Oh btw, I have a german phone, in case that matters somehow. I can't flash in any fastboot way anymore, now I always get some message about a downgraded version. Of course details can be supplied if needed.
edit: was now able to flash CM, no idea what I did so that it didn't give me errors anymore. It still goes into fastboot by default on every reboot though, I always need to select "reboot device" manually every time.
coldtech said:
After a few hours, I (somehow) ended up being able to enter recovery. On the downside though, now it always goes automatically into fastboot, because everything seems to be screwed up. I even got CWM installed though (unlocked the device because I didn't know what else to do).
Now every time it goes into fastboot, the reason given is: "sticky bit fastboot"
Any ideas left?
Oh btw, I have a german phone, in case that matters somehow. I can't flash in any fastboot way anymore, now I always get some message about a downgraded version. Of course details can be supplied if needed.
edit: was now able to flash CM, no idea what I did so that it didn't give me errors anymore. It still goes into fastboot by default on every reboot though, I always need to select "reboot device" manually every time.
Click to expand...
Click to collapse
Sounds like you are able to use the phone. That’s good.
The error is saying it can’t downgrade the trust zone (tz) right? That is normal for a phone with an unlocked bootloader. You can simply ignore that.
The sticky bit fastboot problem looks like it can be fixed by issuing this command while in fastboot mode: fastboot oem fb_mode_clear
mentose457 said:
Sounds like you are able to use the phone. That’s good.
The error is saying it can’t downgrade the trust zone (tz) right? That is normal for a phone with an unlocked bootloader. You can simply ignore that.
The sticky bit fastboot problem looks like it can be fixed by issuing this command while in fastboot mode: fastboot oem fb_mode_clear
Click to expand...
Click to collapse
the fb_mode_clear was the culprit, thanks a lot!
and the error says: "downgraded security version. update gpt_main version failed. preflash validation failed for GPT" - which is still keeping me from flashing stuff via fastboot.
since I can't fastboot flash at the moment: do you happen to know where I can get the german modem image so that I can flash it using CWM? I think through all the flashing and trying I have a corrupt or wrong modem file (probably the US version). I can not log into the carrier network right now. it asks me for my SIM PIN and unlocks the SIM, but that's it. so I can't make phone calls or anything right now.
I unlocked and rooted my tablet yesterday and everything appeared to be working fine. After using it for a couple hours and restarting it a few times it stopped working and is now locked in a boot loop. When I try boot the tablet it comes on and gets to the animation where the glint of light goes across the Asus logo but it does not finish and instead it stops there and I get the moving circles at the bottom. I've left it running there for several hours and it just hangs.
I've tried erasing the data and booting to linux but the same thing happens when I try either of those.
I've also tried flashing a number of different ROMs, but all that happens is it starts installing and then I get the Android guy on his side error screen.
I hadn't done anything to the ROM and was still running 10.6.1.14.4. I even downloaded that same ROM from http://forum.xda-developers.com/showthread.php?t=2266519 but I get the same error message when I try flash that ROM.
I would really, REALLY appreciate any ideas at all - and thanks in advance for any suggestions.
stuck on animation loop
slap_shot_12 said:
I unlocked and rooted my tablet yesterday and everything appeared to be working fine. After using it for a couple hours and restarting it a few times it stopped working and is now locked in a boot loop. When I try boot the tablet it comes on and gets to the animation where the glint of light goes across the Asus logo but it does not finish and instead it stops there and I get the moving circles at the bottom. I've left it running there for several hours and it just hangs.
I've tried erasing the data and booting to linux but the same thing happens when I try either of those.
I've also tried flashing a number of different ROMs, but all that happens is it starts installing and then I get the Android guy on his side error screen.
I hadn't done anything to the ROM and was still running 10.6.1.14.4. I even downloaded that same ROM from http://forum.xda-developers.com/showthread.php?t=2266519 but I get the same error message when I try flash that ROM.
I would really, REALLY appreciate any ideas at all - and thanks in advance for any suggestions.
Click to expand...
Click to collapse
this gonna sound odd but i had exact same prob when i rooted and flashed chromix rom. it went. what i did was flash it once with the rom with secure wipe, then i flashed again. and it got stuck at optimizing apps,then i tried reflashing couldnt get it to boot, what i ended up doing was using clockwork mod to factory reset my tablet, then had to restart, and reflash, this time it actually got to main screen. dont let it discharge/reboot for awhile as im bout to post a issue im having with it. but thats what i did to make it work for me.
shadowarez said:
this gonna sound odd but i had exact same prob when i rooted and flashed chromix rom. it went. what i did was flash it once with the rom with secure wipe, then i flashed again. and it got stuck at optimizing apps,then i tried reflashing couldnt get it to boot, what i ended up doing was using clockwork mod to factory reset my tablet, then had to restart, and reflash, this time it actually got to main screen. dont let it discharge/reboot for awhile as im bout to post a issue im having with it. but thats what i did to make it work for me.
Click to expand...
Click to collapse
I'm not sure I understand --- how do I get to the clockwork mod if i can't get past the startup animation? And I've tried a bunch of roms with secure wipe and i get an error from every one of them.
didnt you install clockwork mod first?
slap_shot_12 said:
I'm not sure I understand --- how do I get to the clockwork mod if i can't get past the startup animation? And I've tried a bunch of roms with secure wipe and i get an error from every one of them.
Click to expand...
Click to collapse
the thing i found showed me to installed the clockwork mod first before i did any flashing, i rooted device then i flashed once clockwork mod was installed, i had to root, then install rom manager and goo manager, from within there i installed the clockwork recovery script/mod then i proceeded to flash chromi-X DEODEX.
Did you flash the correct bootloader? I had the same problem, look for my posts in the last few pages of ChromiX.
Here: http://forum.xda-developers.com/showpost.php?p=41658701&postcount=2716
slap_shot_12 said:
I unlocked and rooted my tablet yesterday and everything appeared to be working fine. After using it for a couple hours and restarting it a few times it stopped working and is now locked in a boot loop. When I try boot the tablet it comes on and gets to the animation where the glint of light goes across the Asus logo but it does not finish and instead it stops there and I get the moving circles at the bottom. I've left it running there for several hours and it just hangs.
I've tried erasing the data and booting to linux but the same thing happens when I try either of those.
I've also tried flashing a number of different ROMs, but all that happens is it starts installing and then I get the Android guy on his side error screen.
I hadn't done anything to the ROM and was still running 10.6.1.14.4. I even downloaded that same ROM from http://forum.xda-developers.com/showthread.php?t=2266519 but I get the same error message when I try flash that ROM.
I would really, REALLY appreciate any ideas at all - and thanks in advance for any suggestions.
Click to expand...
Click to collapse
Seems to me you installed Asus factory stock rom JB 4.2.1 (10.6.1.14.4), which means you have the latest bootloader, then you unlocked and rooted your device, however, you never installed any custom recovery like TWRP or CWM (clockmod). Now your device is boot looping. You need to boot into stock recovery by turn off your device, hold volume down and power button until you see white text on the screen, now release both buttons, you should see 3 icons (RCK, Android and wipe data). NOW you are in fastboot mode. Let me know at least you can get that far, before we continue....
buhohitr said:
Seems to me you installed Asus factory stock rom JB 4.2.1 (10.6.1.14.4), which means you have the latest bootloader, then you unlocked and rooted your device, however, you never installed any custom recovery like TWRP or CWM (clockmod). Now your device is boot looping. You need to boot into stock recovery by turn off your device, hold volume down and power button until you see white text on the screen, now release both buttons, you should see 3 icons (RCK, Android and wipe data). NOW you are in fastboot mode. Let me know at least you can get that far, before we continue....
Click to expand...
Click to collapse
buhohitr -- You're exactly right. I can boot into stock recovery. When I select Android or wipe data it goes back to the animation screen and hangs up. When I select RCK it goes to the Android guy and says installing update but then it show him fallen over and the word Error. I've tried RCK with a memory card that has a number of different ROMs on it but the same thing keeps happening.
slap_shot_12 said:
buhohitr -- You're exactly right. I can boot into stock recovery. When I select Android or wipe data it goes back to the animation screen and hangs up. When I select RCK it goes to the Android guy and says installing update but then it show him fallen over and the word Error. I've tried RCK with a memory card that has a number of different ROMs on it but the same thing keeps happening.
Click to expand...
Click to collapse
Give this a try, the factory Asus firmware zip file that you downloaded, unzip the file, you should see another zip file, rename this new zip file to "EP201_768_SDUPDATE.zip" (without quotation), then copy it to the root of your sdcard then boot into stock recovery and execute the RCK again. Make sure you don't have any other zips laying around in the root of your sdcard.
You are truly a god among men.
buhohitr said:
Give this a try, the factory Asus firmware zip file that you downloaded, unzip the file, you should see another zip file, rename this new zip file to "EP201_768_SDUPDATE.zip" (without quotation), then copy it to the root of your sdcard then boot into stock recovery and execute the RCK again. Make sure you don't have any other zips laying around in the root of your sdcard.
Click to expand...
Click to collapse
THIS WORKED!!! Thanks so much. I was really worried I had bricked it.
So now one last question --- WHY did that work? Is there somewhere I could go to read up on this kind of stuff? I've tried surfing the XDA forum but there's a lot of stuff like this where someone gets there problem solved, but not much explaining why something worked so I can learn more about it.
slap_shot_12 said:
THIS WORKED!!! Thanks so much. I was really worried I had bricked it.
So now one last question --- WHY did that work? Is there somewhere I could go to read up on this kind of stuff? I've tried surfing the XDA forum but there's a lot of stuff like this where someone gets there problem solved, but not much explaining why something worked so I can learn more about it.
Click to expand...
Click to collapse
Somehow the stock recovery was reinstalled on your tablet, thus letting this method work. It however does not on CWM or TWRP. All you did was manually reinstall a stock rom back onto your tablet. How it got the stock recovery is beyond me unless you flashed a stock ROM from CWM and didnt realize what you were installing.
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
slap_shot_12 said:
THIS WORKED!!! Thanks so much. I was really worried I had bricked it.
So now one last question --- WHY did that work? Is there somewhere I could go to read up on this kind of stuff? I've tried surfing the XDA forum but there's a lot of stuff like this where someone gets there problem solved, but not much explaining why something worked so I can learn more about it.
Click to expand...
Click to collapse
Since the JB 4.2.1 upgrade, this is the most reliable method to install Asus full stock firmware. Also, since you're unlocked, let root the device by go here http://forum.xda-developers.com/showthread.php?t=2230763 download the tool and root it. Once rooted, I suggest that you should install TWRP custom recovery, by download Goomanager from the market, open the app and tab on the 3 little boxes on the top right hand corner, select "install recovery scripts" , this will shutdown your device and install custom TWRP recovery script, once this installed, you can download "rebooter" from the market and this app has many options, one of them is allowed you easily boot into custom recovery.
I pulled a boneheaded move and ended up formatting my phone from within the TWRP menu. Now the stock operating system is gone.
I wanted to put on one of the Gummy Nightly builds, but I'm new to TWRP and selected the wrong options while wiping.
So now I have the Gummy ROM on my PC, the phone is connected to my PC and in TWRP (in the advanced adb sideload feature), but adb will not recognize my phone.
When I check device manager, SAMSUNG_Android_SCH-I535 is there, but with a yellow "cauton" symbol. When I look at properties, it tells me that "The drivers for this device are not installed (Code 28).
I went out to the Samsung page and got the exe to unpack drivers on my machine... I've tried "update driver" and pointing to the root of the directory containing the Samsung drivers, but my PC claims none of them are applicable.
So what I'm looking for here is:
(1) How do I get this ROM on my phone so that I can install the zip and have a working OS again?
(2) Assuming that using the ADB Sideload feature of TWRP is my best option, how do I get the device drivers for my galaxy s3 installed to my windows 8 PC and get adb to detect it?
Thanks in advance.
Ok, so it seems to have gotten worse.
I cannot get my windows installation to recognize the phone without it being able to boot an android OS, it seems.
I had it in TWRP 2.6.0.0, but as I was trying to reboot to see if I could get into download mode (my thought being to change out TWRP for Clockwork; I seem to remember Clockwork Recovery having a "mount as USB" option which TWRP seems to lack), it tried to root the file system.
After that, the screen went black and nothing happened... the phone was unresponsive. I would remove the battery and replace it to have it vibrate once and then not respond to any key presses.
I removed the battery, SD card, and SIM card, replacing only the battery and got it to turn on and show a Samsung Galaxy SIII logo... but it's just sitting there... I'm assuming it's frozen because there's no OS to boot on the internal storage.
Please help me recover my phone!
Ok, so I've found I can still get into download mode, but not into recovery.
Recovery seems to lead to a black screen with nothing on it.
Trying to boot normally leads to the statis Samsung Galaxy SIII logo.
Can I fix my phone from the download menu?
Please help me.
Install kies and at the end of the install make sure you check install unified drivers. Then flash root66 through Odin. After that you should be good to install ROMs again.
ThePagel said:
Install kies and at the end of the install make sure you check install unified drivers. Then flash root66 through Odin. After that you should be good to install ROMs again.
Click to expand...
Click to collapse
Thanks for the reply!
Sorry, I'm a little out of date on the flashing and stuff -- I was just over in the thread where the poster thought he half softbricked his phone and was asking about 4.1.2 vs. 4.3
I see this at the top of my screen sitting here in download mode:
ODIN MODE
PRODUCT NAME: SCH-I535
CUSTOM BINARY DOWNLOAD: YES (6 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
It seems my bootloader got relocked somehow -- is this why my phone just goes to black screen when I attempt to boot into recovery -- even if I have TWRP or CWR installed? Odin claims I just pushed philz custom CWR to my PDA section, but it still won't go into recovery.
What are my options here?
You are pre 4.3 I'll help you more in the morning if no one else does first.
ThePagel said:
You are pre 4.3 I'll help you more in the morning if no one else does first.
Click to expand...
Click to collapse
Ok, thanks -- I appreciate that someone's willing to help! Googling stuff is just getting me more and more confused.
I'll stay tuned for help and turn off my phone so I don't screw things up further in the meantime.
My desired result here, I think is to have my bootloader remain unlocked (as I was under the impression it was, since I was running TWRP with rooted stock ROM), with CWR as the custom recovery software and Gummy as my current ROM.
Side note: I've noticed I don't even get a battery indicator on the main screen now when I press the home button -- is this because of whatever's causing my recovery to not work (and the potential lack of an OS)?
Thanks in advance.
corrosivefrost said:
Ok, thanks -- I appreciate that someone's willing to help! Googling stuff is just getting me more and more confused.
I'll stay tuned for help and turn off my phone so I don't screw things up further in the meantime.
My desired result here, I think is to have my bootloader remain unlocked (as I was under the impression it was, since I was running TWRP with rooted stock ROM), with CWR as the custom recovery software and Gummy as my current ROM.
Side note: I've noticed I don't even get a battery indicator on the main screen now when I press the home button -- is this because of whatever's causing my recovery to not work (and the potential lack of an OS)?
Thanks in advance.
Click to expand...
Click to collapse
Once you in download mode, can your Odin see your phone?
buhohitr said:
Once you in download mode, can your Odin see your phone?
Click to expand...
Click to collapse
I believe it can. After TWRP stopped working, I tried to replace it with CWR and the digital flash count went up (Odin showed no errors on the flash) -- recovery still won't work though, holding vol+/home/power simply gives me a black screen after I see the SAMSUNG logo with the recovery boot text in the upper left.
corrosivefrost said:
I believe it can. After TWRP stopped working, I tried to replace it with CWR and the digital flash count went up (Odin showed no errors on the flash) -- recovery still won't work though, holding vol+/home/power simply gives me a black screen after I see the SAMSUNG logo with the recovery boot text in the upper left.
Click to expand...
Click to collapse
What stock version do you have on your phone right now?
buhohitr said:
What stock version do you have on your phone right now?
Click to expand...
Click to collapse
None? :silly:
I think before this fiasco, it was running whatever version was previous to the new VZW update.
It was the fact that the new update was trying to install and failing repeatedly (because my bootloader was unlocked, I think?) that prompted me to look into finally switching to a ROM. However, my unfamiliarity with TWRP led to me formatting my phone (everything, it seems, including the SD card)... so I'm not really sure what' "on the phone right now". :\
I'm really not sure what kind of state anything is in at this point -- other than Odin seemingly working and being able to get into download mode.
Again, short version of what happened:
(1) Accidentally did a full wipe (factory reset?) in TWRP -- this wiped the ROM I was going to install with TWRP off the phone.
(2) While trying to ADB sideload from TWRP and telling TWRP to reboot, TWRP tried to install supersu.
(3) After (2), I was unable to get back into recovery mode. I got into Odin and tried to flash philz customer clockwork recovery and it seemed successful. Reboot and attempt to enter recovery still fails. Samsung logo with recovery mode text appears, but then the screen goes black.
(4) Normal boot leaves the screen stuck on the Samsung Galaxy SIII logo indefinitely.
corrosivefrost said:
None? :silly:
I think before this fiasco, it was running whatever version was previous to the new VZW update.
It was the fact that the new update was trying to install and failing repeatedly (because my bootloader was unlocked, I think?) that prompted me to look into finally switching to a ROM. However, my unfamiliarity with TWRP led to me formatting my phone (everything, it seems, including the SD card)... so I'm not really sure what' "on the phone right now". :\
Click to expand...
Click to collapse
OK, download this image and flash with Odin(you should be using Odin version 3.07) http://goo.im/devs/invisiblek/i535/stock.vzw_root66.tar This should bring your phone back from the dead.
Edit: after you have your phone up and running, download goo manager and install cwm recovery since your phone is pre rooted already.
buhohitr said:
OK, download this image and flash with Odin(you should be using Odin version 3.07) http://goo.im/devs/invisiblek/i535/stock.vzw_root66.tar This should bring your phone back from the dead.
Edit: after you have your phone up and running, download goo manager and install cwm recovery since your phone is pre rooted already.
Click to expand...
Click to collapse
Ok, that looks like some version of the stock vzw ROM with root already installed?
This is what ThePagel seemed to recommend as well before I ended up with more questions about what was going on before I did it.
What part of Odin do I flash to? PDA again, just like a custom recovery?
corrosivefrost said:
Ok, that looks like some version of the stock vzw ROM with root already installed?
This is what ThePagel seemed to recommend as well before I ended up with more questions about what was going on before I did it.
What part of Odin do I flash to? PDA again, just like a custom recovery?
Click to expand...
Click to collapse
Yes, it's pre rooted stock image and yes flash with PDA.
buhohitr said:
Yes, it's pre rooted stock image and yes flash with PDA.
Click to expand...
Click to collapse
Standard auto-reboot and f_reset_time options? nothing else necessary?
corrosivefrost said:
Standard auto-reboot and f_reset_time options? nothing else necessary?
Click to expand...
Click to collapse
Correct. When you click on PDA and select the image, give it time to showup in Odin cause the size is big.
buhohitr said:
Correct. When you click on PDA and select the image, give it time to showup in Odin cause the size is big.
Click to expand...
Click to collapse
Alright, I'll give it a shot and report back.
Thank you!
corrosivefrost said:
Alright, I'll give it a shot and report back.
Thank you!
Click to expand...
Click to collapse
If that doesn't work you'll need to flash the bootchain first. I don't have a link but I could find it if you need to use it.
ThePagel said:
If that doesn't work you'll need to flash the bootchain first. I don't have a link but I could find it if you need to use it.
Click to expand...
Click to collapse
Yes if the bootloader is still locked he needs boot chain can be found here http://forum.xda-developers.com/showthread.php?t=2046439
ThePagel said:
If that doesn't work you'll need to flash the bootchain first. I don't have a link but I could find it if you need to use it.
Click to expand...
Click to collapse
It did work! Hooray!
buhohitr said:
Yes if the bootloader is still locked he needs boot chain can be found here http://forum.xda-developers.com/showthread.php?t=2046439
Click to expand...
Click to collapse
Didn't need to go that far -- but now that I'm back up and running, signed into google play, and downloaded goo manager, can you point me in the right direction for getting it to install cwm recovery?
Thanks guys!