So I was installing modaco switch on my phone and it worked for a bit but then when I rebooted it it wouldn't turn on. I've tried flashing it in odin and nothing happened and it still doesn't work. I was wondering if anyone else had any ideas.
Can you access Odin? If so, I recommend flashing back to stock first.
joshua.justice said:
So I was installing modaco switch on my phone and it worked for a bit but then when I rebooted it it wouldn't turn on. I've tried flashing it in odin and nothing happened and it still doesn't work. I was wondering if anyone else had any ideas.
Click to expand...
Click to collapse
Are you able to get your device into ODIN/Download mode?
If so, flash the Samsung Stock Firmware as macboy3000 suggested.
To get your device into ODIN mode:
Power down device
Press Power and Vol down buttons and hold
Device should show an image
Press Vol up and you'll be in ODIN mode
Some helpful tips:
Follow the instructions via the red link in my sig.
Be sure to have enough juice in your battery
Have a good usb cord. This is the reason many ODIN flashes fail.
Check your md5 checksum match between the download file and your download prior to flashing the stock Firmware.
macboy3000 said:
Can you access Odin? If so, I recommend flashing back to stock first.
Click to expand...
Click to collapse
Biker1 said:
Are you able to get your device into ODIN/Download mode?
If so, flash the Samsung Stock Firmware as macboy3000 suggested.
To get your device into ODIN mode:
Power down device
Press Power and Vol down buttons and hold
Device should show an image
Press Vol up and you'll be in ODIN mode
Some helpful tips:
Follow the instructions via the red link in my sig.
Be sure to have enough juice in your battery
Have a good usb cord. This is the reason many ODIN flashes fail.
Check your md5 checksum match between the download file and your download prior to flashing the stock Firmware.
Click to expand...
Click to collapse
I tried flashing it twice and it still said successful when it finished flashing but continued to boot loop.
I'm not sure what would cause think
joshua.justice said:
I tried flashing it twice and it still said successful when it finished flashing but continued to boot loop.
I'm not sure what would cause think
Click to expand...
Click to collapse
After you flashed ODIN, did you go into stock recovery and Factory reset, then reboot, both from within Recovery?
Biker1 said:
After you flashed ODIN, did you go into stock recovery and Factory reset, then reboot, both from within Recovery?
Click to expand...
Click to collapse
No, I don't think it'll boot the stock recovery but I'll try that
If you flash stock and still receive boot loops, try going into recovery and wiping data and cache.
take out your sdcard too just for the hell of it.
I just reread your post, and your device is working fine, it's just that you want to know how to get Modaco Switch to work on your device with stability, because it stops working shortly after it's installed.
I had thought your device stopped working. I don't think ODIN will be your answer, and I don't about Modaco.
Maybe:
See if others have Modaco Switch working with stability, and if so:
try wiping cache & dalvik cache in Recovery, or try wiping first.
Biker1 said:
I just reread your post, and your device is working fine, it's just that you want to know how to get Modaco Switch to work on your device with stability, because it stops working shortly after it's installed.
I had thought your device stopped working. I don't think ODIN will be your answer, and I don't about Modaco.
Maybe:
See if others have Modaco Switch working with stability, and if so:
try wiping cache & dalvik cache in Recovery, or try wiping first.
Click to expand...
Click to collapse
It's not working fine. It doesn't boot at all. I tried going into recovery and it still boot loops even after flashing with odin.
joshua.justice said:
It's not working fine. It doesn't boot at all. I tried going into recovery and it still boot loops even after flashing with odin.
Click to expand...
Click to collapse
Ah, so I did read it right the first time. I saw the title the 1st time but I didn't see it the 2nd time, which is why I thought just Modaco wasn't turning on when I read your post without reading the title the 2nd time.
Plus I missed all the follow up posts. That's what I get for running around on my phone trying to read threads
With that being said, then what I wrote should resolve your issues.
Follow my RED link in my sig, and that should help to resolve your issues. I wrote out the steps previously, but looking at the link may help you
Biker1 said:
Ah, so I did read it right the first time. I saw the title the 1st time but I didn't see it the 2nd time, which is why I thought just Modaco wasn't turning on when I read your post without reading the title the 2nd time.
Plus I missed all the follow up posts. That's what I get for running around on my phone trying to read threads
With that being said, then what I wrote should resolve your issues.
Follow my RED link in my sig, and that should help to resolve your issues. I wrote out the steps previously, but looking at the link may help you
Click to expand...
Click to collapse
It doesn't boot into recovery so how can I wipe those?
joshua.justice said:
It doesn't boot into recovery so how can I wipe those?
Click to expand...
Click to collapse
You mentioned in the op you tried flashing in ODIN.
What exactly is your phone able to do?
Do you see anything on the display?
Does it boot into anything?
Etc...
What does 'tried going into recovery but it still boot loops' mean?
If you go step by step what you did before the issue and after, including Exactly what status your device is in, it will help in attempting to troubleshoot and resolve your issues.
I can get it into download mode but flashing Odin does nothing. When I hit the power button to turn it on it goes all the way until the t mobile logo and stalls. Sometimes it just vibrations off and on with a dark screen. When I try to go into recovery with the volume up and power keys or says 'rebooting recovery' in blue like it always does but then it just goes to booting normally and then hangs there.
joshua.justice said:
I can get it into download mode but flashing Odin does nothing. When I hit the power button to turn it on it goes all the way until the t mobile logo and stalls. Sometimes it just vibrations off and on with a dark screen. When I try to go into recovery with the volume up and power keys or says 'rebooting recovery' in blue like it always does but then it just goes to booting normally and then hangs there.
Click to expand...
Click to collapse
Can you confirm what version of the S4 you have?
The SGH-M919?
Not trying to be stupid or anything, just making sure.
Have you tried this..
1. Flash a recovery image using Heimdall (I'd suggest ClockworkMod)
2. Reboot to recovery. (Hopefully it goes through this time)
3. adb sideload a ROM to your device.
4. Flash the ROM.
5. Win?
Just trying to think of ways you can get your device back up and running.
joshua.justice said:
I can get it into download mode but flashing Odin does nothing. When I hit the power button to turn it on it goes all the way until the t mobile logo and stalls. Sometimes it just vibrations off and on with a dark screen. When I try to go into recovery with the volume up and power keys or says 'rebooting recovery' in blue like it always does but then it just goes to booting normally and then hangs there.
Click to expand...
Click to collapse
You have to:
Power down device
Don't power up
Press Power and Vol down buttons simultaneously
Press Vol up button
You should be in ODIN mode
Biker1 said:
You have to:
Power down device
Don't power up
Press Power and Vol down buttons simultaneously
Press Vol up button
You should be in ODIN mode
Click to expand...
Click to collapse
I did that. It's caked download mode. That's where I flashed Odin off my computer.
I noticed after flashing stock with Odin, I get bootloops, unless I do a factory reset. After stock flashes, it reboots into recovery and wipes cache by itself. When it finishes that and it starts to reboot by itself, I press the volume up button and go into recovery. I do a factory reset and reboot and all is fine, no bootloops.
norml said:
I noticed after flashing stock with Odin, I get bootloops, unless I do a factory reset. After stock flashes, it reboots into recovery and wipes cache by itself. When it finishes that and it starts to reboot by itself, I press the volume up button and go into recovery. I do a factory reset and reboot and all is fine, no bootloops.
Click to expand...
Click to collapse
Mine doesn't do that though. It just boot loops without going into recovery.
joshua.justice said:
Mine doesn't do that though. It just boot loops without going into recovery.
Click to expand...
Click to collapse
I understand that, my post is describing what happens when you flash a stock tar, not bootlooping, I am describing exactly what happens during the process of flashing a stock tar and how to avoid bootlooping, step by step. I guess you weren't paying attention when you flashed a stock tar with Odin, it reboots for the first time by itself and goes into stock recovery and wipes cache by itself, it's a normal process, maybe that part confused you. Any hows, good luck, I have explained step by step what I do to avoid bootloops and my directions are clear and simple. Bye.
Related
Well, something strange happened and i have no idea what the prob is
yesterday i installed a new kernel for my gnex and made a backup (using CWM) before flashing. Today i decided to go back to the previous kernel so i just went to recovery and restored from the backup. It installed successfully and then i rebooted my phone twice just to be sure everything was working and it was untill 4-5 hours later, I was playing a game (temple run) when suddenly the phone turned off and restarted by itself, i though maybe the game crashed and its restarting but i kept waiting for an hour but the phone was just stuck at the google logo. After waiting, i decided to go to recovery and flash a new kernal or restore but when i went to the bootloader and selected recovery, the phone didnt go into recovery but its stuck in google loop again. so somehow i think the recovery has been deleted of something like that because it gets stuck in loop if i go to recovery :/
i am on 4.0.3 codenamed android rom
Thanks
EDIT: I have already tried removing the battery for some time but still i am not able to enter recovery. i thought recovery was to prevent such things :$
You should probably use search next time. It's happened to quite a few people (myself included).
Use fastboot/ODIN to flash stock rom again.
case0 said:
You should probably use search next time. It's happened to quite a few people (myself included).
Use fastboot/ODIN to flash stock rom again.
Click to expand...
Click to collapse
Thanks but i wont be able to recover my data using this right?:/
No I don't think so, it sucks. I thought they had fixed this bug in 4.0.3 though which is strange. I lost my data twice within a month because of this, when I was on 4.0.2 (or maybe 4.01). Haven't had it since I rooted and updated.
Try flashing the recovery again. Maybe it will work.
case0 said:
No I don't think so, it sucks. I thought they had fixed this bug in 4.0.3 though which is strange. I lost my data twice within a month because of this, when I was on 4.0.2 (or maybe 4.01). Haven't had it since I rooted and updated.
Click to expand...
Click to collapse
can you tell me which tut to follow? i searched and found ODIN files for 4.0.4 and 4.0.2 but i'm on 4.0.3
sry but this is my first android phone and i have no previous knowledge
efrant said:
Try flashing the recovery again. Maybe it will work.
Click to expand...
Click to collapse
already tried that. manually and also using toolkit but i get the same error something like "recovery status read failed too many links"
Thanks for replies btw
rollerdyke44 said:
can you tell me which tut to follow? i searched and found ODIN files for 4.0.4 and 4.0.2 but i'm on 4.0.3
sry but this is my first android phone and i have no previous knowledge
already tried that. manually and also using toolkit but i get the same error something like "recovery status read failed too many links"
Thanks for replies btw
Click to expand...
Click to collapse
Use the Odin files for 4.0.4. Why are you looking for 4.0.3?
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
Use the Odin files for 4.0.4. Why are you looking for 4.0.3?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
well i am on codenamed android based on 4.0.3 so i was looking for 4.0.3 files for ODIN. this will flash my firmware to stock 4.0.4 right?
And do you know of ANY WAY i can fix my phone so that i can recover my data? I have tried everything but to no avail. i have tried flashing recovery, booting recovery (not flashing) using different usb ports and cables, flashing boot.img from codename android and everything i read online :/
rollerdyke44 said:
this will flash my firmware to stock 4.0.4 right?
Click to expand...
Click to collapse
Yes.
rollerdyke44 said:
And do you know of ANY WAY i can fix my phone so that i can recover my data? I have tried everything but to no avail. i have tried flashing recovery, booting recovery (not flashing) using different usb ports and cables, flashing boot.img from codename android and everything i read online :/
Click to expand...
Click to collapse
What happens when you boot CWM?
In order to recover anything, you need to be booted either into Android or CWM.
Maybe try using the "no-wipe" odin files, which may allow you to either boot into the ROM or allow you to boot CWM, and then you can retrieve your data. However, if this does work, I would recommend you wipe right after you retrieve your data, then restore your files, as you may have issues later on running with that data on your device.
efrant said:
Yes.
What happens when you boot CWM?
In order to recover anything, you need to be booted either into Android or CWM.
Maybe try using the "no-wipe" odin files, which may allow you to either boot into the ROM or allow you to boot CWM, and then you can retrieve your data. However, if this does work, I would recommend you wipe right after you retrieve your data, then restore your files, as you may have issues later on running with that data on your device.
Click to expand...
Click to collapse
thanks for your quick reply mate
I am not able to boot into recovery. When i select enter recovery from bootloader then it just loops on the google logo. When i try to reinstall cwm then it fails everytime with the error i mentioned above
ohh and btw, sometimes when the cwm installation fails then the bootloader gets stuck and the screen becomes kind of blurry and i have to take out the battery...... is that normal?
And i'll first try the no wipe files (from here http://forum.xda-developers.com/showthread.php?t=1586807&highlight=odin) and see if that works
rollerdyke44 said:
thanks for your quick reply mate
I am not able to boot into recovery. When i select enter recovery from bootloader then it just loops on the google logo. When i try to reinstall cwm then it fails everytime with the error i mentioned above
ohh and btw, sometimes when the cwm installation fails then the bootloader gets stuck and the screen becomes kind of blurry and i have to take out the battery...... is that normal?
And i'll first try the no wipe files (from here http://forum.xda-developers.com/showthread.php?t=1586807&highlight=odin) and see if that works
Click to expand...
Click to collapse
What happens when you boot CWM via fastboot?
fastboot boot cwm.img
efrant said:
What happens when you boot CWM via fastboot?
fastboot boot cwm.img
Click to expand...
Click to collapse
i get a blurry recovery mode picture (that hat kind of thing) for a couple of secs and then the phone reboots and again in boot loop[
rollerdyke44 said:
i get a blurry recovery mode picture (that hat kind of thing) for a couple of secs and then the phone reboots and again in boot loop[
Click to expand...
Click to collapse
Oou, that doesn't sound good. Not sure you'd be able to save your data.
efrant said:
Oou, that doesn't sound good. Not sure you'd be able to save your data.
Click to expand...
Click to collapse
well lets hope for the best
And i was on codenamed 4.0.3 so if i use the "no-wipe" files for 4.0.4 it should not cause anymore problems right?
I'll first use ODIN with no wipe files and if that doesnt work then i guess i'll say bye bye to my data and do a full wipe.
Thanks for you help mate and i will reply with the result in an hour or so (dinner time now )
Thanks again
EDIT:
so i ran ODIN but now its stuck. the start button has been greyed out with the following message
"<ID:0/011> Added!!
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
"
and the phone is on the ODIN download mode screen :/
EDIT 2:
when i use the full image, then the ODIN downloading screen on my nexus becomes blurry when ODIN on pc shows "<ID:0/011> NAND Write Start!! "
PLease help as i really dont know what else can i do
Fu*kkkkk
i think its bricked now i cant even access the bootloader the phone doesnt even turn on now i cant even get the google logo just a black screen
rollerdyke44 said:
Fu*kkkkk
i think its bricked now i cant even access the bootloader the phone doesnt even turn on now i cant even get the google logo just a black screen
Click to expand...
Click to collapse
It may not be bricked. Not being able to get into the bootloader can happen when you flash via odin.
Can you not boot into download mode (hold volume down and then press and hold power)? If you can, then you can still flash via odin.
I haven't really used odin too much, so I won't be able to help you troubleshoot too much (maybe ask in Chainfire's thread), but: if you can boot into download mode, do it, and re-follow the instructions in this post to-the-letter. Use the full odin image, not the no-wipe one.
efrant said:
It may not be bricked. Not being able to get into the bootloader can happen when you flash via odin.
Can you not boot into download mode (hold volume down and then press and hold power)? If you can, then you can still flash via odin.
I haven't really used odin too much, so I won't be able to help you troubleshoot too much (maybe ask in Chainfire's thread), but: if you can boot into download mode, do it, and re-follow the instructions in this post to-the-letter. Use the full odin image, not the no-wipe one.
Click to expand...
Click to collapse
noooooo
i cant even get the fone in download mode. the phone screen is completely black!!!! Wont even vibrate which shows its starting up
pleaaassseeee heeelppp
now i am getting scared for my nexus
rollerdyke44 said:
noooooo
i cant even get the fone in download mode. the phone screen is completely black!!!! Wont even vibrate which shows its starting up
pleaaassseeee heeelppp
now i am getting scared for my nexus
Click to expand...
Click to collapse
Take a slow deep breath and exhale. Take out the battery. Wait for a while. Put the battery back in.
Hold down the volume down button (not the volume up) and then press and hold power for 15 secs. See if that gets you into download mode. Even if nothing shows up on the screen, try following the steps in the odin thread.
You did make sure only the checkmarks that needed to be there were there in odin, correct?
efrant said:
Take a slow deep breath and exhale. Take out the battery. Wait for a while. Put the battery back in.
Hold down the volume down button (not the volume up) and then press and hold power for 15 secs. See if that gets you into download mode. Even if nothing shows up on the screen, try following the steps in the odin thread.
You did make sure only the checkmarks that needed to be there were there in odin, correct?
Click to expand...
Click to collapse
Which checkmarks should be used?
TwinkyOfHope said:
Which checkmarks should be used?
Click to expand...
Click to collapse
Why don't you take a look at the linked (a few posts up) odin thread and see for yourself?
Here's a video tutorial on how to root your Nexus 10 for noobs!
Windows video tutorial:
Mac video tutorial:
Linux video tutorial:
All the files you need in one zip (adb+SuperSU+fastboot+Windows drivers):
http://downloadandroidrom.com/file/Nexus10/Nexus10RootNew.zip
Step-by-Step tutorial with photos here:
http://nexus10root.com/nexus-10-root/how-to-root-nexus-10-easiest-method/
Also, if you get stuck on bootloop after unlocking bootloader (This happened to me couple times), do a factory reset in stock recovery to fix:
Thanks to shimp208 for the sideload method and working CWM, ChainFire for awesome SuperSU and to all the developers who are worked on CWM recovery!
So the CWM that was just updated by Koushik on CWM does not work properly or does it work? Was asking based on this
While CWM Recovery is still being fixed
Click to expand...
Click to collapse
Edit: There's no driver issue if it were on a Mac right? Especially adb sideloading the CWM SuperSu zip?
How do I flash the stock recovery? CWM isn't working and I tried to update the driver like in the video but couldn't find the "manta" that I needed to update. I'm just stuck in bootloop animation now. I'm downloading the stock image right now to try and flash it back to stock..
johno86 said:
How do I flash the stock recovery? CWM isn't working and I tried to update the driver like in the video but couldn't find the "manta" that I needed to update. I'm just stuck in bootloop animation now. I'm downloading the stock image right now to try and flash it back to stock..
Click to expand...
Click to collapse
If you go into fastboot mode then choose recovery to get to the screen with the red triangle, keep pressing the power button and volume buttons randomly until the stock recovery pops up. From there do a factory reset and it'll work, I just did it to mine!
I flashed the CWM recovery img so when I do what you say it takes me to the bootloader screen and says Downloading. No red triangle. It boots into CWM and then after 20 seconds restarts itself and hits the bootanimation loop. Any clue what to do next? Trying to flash the stock image but having issues using cmds in windows cmd
*edit
I cleared cache through cmd and i got to the red triangle...thank ****ing the lord. DTWAZERE, I will remember tonight. Thank you for your help.
johno86 said:
I flashed the CWM recovery img so when I do what you say it takes me to the bootloader screen and says Downloading. Any clue what to do next? Trying to flash the stock image but having issues getting it into fastboot now...
Click to expand...
Click to collapse
Thing is it will delete the CWM recovery when you leave it so you'll have to reflash it, which is why this is so unstable!
I had the exact same thing as you and this is what I did:
Press the power button to turn it off while it says downloading
Hold both volume buttons down and power on to get into fastboot
Choose recovery
Press power and volume buttons randomly when the red triangle appears until you get stock recovery
Choose Factory Reset
Reboot
You should be able to get back into the rom that way,
to root it you need to boot into fastboot again, reflash the recovery, and sideload the superuser apk
dtwazere said:
Thing is it will delete the CWM recovery when you leave it so you'll have to reflash it, which is why this is so unstable!
I had the exact same thing as you and this is what I did:
Press the power button to turn it off while it says downloading
Hold both volume buttons down and power on to get into fastboot
Choose recovery
Press power and volume buttons randomly when the red triangle appears until you get stock recovery
Choose Factory Reset
Reboot
You should be able to get back into the rom that way,
to root it you need to boot into fastboot again, reflash the recovery, and sideload the superuser apk
Click to expand...
Click to collapse
Yeah this is exactly what I did and it worked. I'll wait on flashing anything until there's a stable recovery. I was fairly confident in what I was doing until that happened. Not being able to input commands from cmd prompt made me sick so I'll wait for a dev to release something that works without having to quickly install the drivers again within a 15-20 second timeframe. Too much stress.
cant boot
I got a huge problem.
I follow the step and going on. Ive seen the done in CWMR. But the tablet cant boot.
It stops in the second animation( X mark) cant boot in os.
Anyone can help me?
lc684760 said:
I got a huge problem.
I follow the step and going on. Ive seen the done in CWMR. But the tablet cant boot.
It stops in the second animation( X mark) cant boot in os.
Anyone can help me?
Click to expand...
Click to collapse
Heh im having the same issue.
lc684760 said:
I got a huge problem.
I follow the step and going on. Ive seen the done in CWMR. But the tablet cant boot.
It stops in the second animation( X mark) cant boot in os.
Anyone can help me?
Click to expand...
Click to collapse
I'm having the same issue. Stuck on the 2nd splash screen with the Nexus Logo.
I received successful messages after every entry.
deevooneh said:
I'm having the same issue. Stuck on the 2nd splash screen with the Nexus Logo.
I received successful messages after every entry.
Click to expand...
Click to collapse
sucks. But we can boot in fastboot and downloading . I think we may have some tricks to fix.
i did everything, and it all went successfully after a few tried. Now i am stuck with the JB X load screen.
How do i get the stock google rom and how do i flash it?
lc684760 said:
sucks. But we can boot in fastboot and downloading . I think we may have some tricks to fix.
Click to expand...
Click to collapse
Ok. Let me know if you figure something out. Hopefully we didnt brick it.
deevooneh said:
Ok. Let me know if you figure something out. Hopefully we didnt brick it.
Click to expand...
Click to collapse
I just called service phone. But goole play agent told me that they didnt know how to deal with that. Its the new device. They dont know much. Damn it!
lc684760 said:
I just called service phone. But goole play agent told me that they didnt know how to deal with that. Its the new device. They dont know much. Damn it!
Click to expand...
Click to collapse
How do we get back to stock? Might need to reattempt this.
If you are stuck on the boot animation (X) screen... power off your device and enter fastboot mode and then type fastboot -w... I has this problem and this fixed it!
NOTE: fastboot -w will wipe your internal storage completely
dtwazere said:
If you go into fastboot mode then choose recovery to get to the screen with the red triangle, keep pressing the power button and volume buttons randomly until the stock recovery pops up. From there do a factory reset and it'll work, I just did it to mine!
Click to expand...
Click to collapse
deevooneh said:
How do we get back to stock? Might need to reattempt this.
Click to expand...
Click to collapse
Stock is here
https://developers.google.com/android/nexus/images#mantarayjop40c
Still need a way to get CWM stable, so we have time to copy to sd
craigacgomez said:
If you are stuck on the boot animation (X) screen... power off you devices and enter fastboot mode and then type fastboot -w... I has this problem and this fixed it!
NOTE: fastboot -w will wipe your internal storage completely
Click to expand...
Click to collapse
THIS WORKED!!
Youre a genius. thanks!
When I try to install the manta drivers manually and tell it to search the same area that it searched and found the android bootloader drivers for fastboot mode it says that the drivers couldn't be found and installed. Am I missing something? Also if i try to do fastboot flash recovery it gives me an error message stating that it cannot determine the image filename for the recovery image.
Well i guess i did it the long way around.
Went to https://developers.google.com/android/nexus/images#mantarayjop40c
and downloaded the Nexus 10 file. extracted, and the actual files in the Nexus10Root folder.
Opened the flash-all.sh and entered each command manually because it was erroring out running the script.
After the 3rd command it booted right into android!
i need some help here guys. i was running AOKP for the longest time and loving it. then today i tried to update to the latest version. i downloaded the rom and went to flash the .zip in CWM. i've done this dozens of times. this time things were completely different. i kept getting FCs over and over. so i booted into recovery again to reflash. for whatever reason, it seemed like my file system was corrupted. folders i had never seen were all over the place. it was a big mess. i decided to flash back to stock. i booted into DL mode and did this with odin successfully. then upon reboot, the phone was stuck at the Samsung logo. looking into this i saw that i needed to boot into recovery, wipe data/factory reset, wipe cache, and wipe dalvik cache. i tried doing this but no matter what, my phone will not boot into recovery. i have even used odin to flash CF-SGS3-CWM-v5.5-v1.0.tar. when i press volume up+home+power i get the first samsung logo with the tiny blue text up at the top saying "recovery booting" but then nothing happens and the phone just goes to a normal boot attempt, which stalls at the samsung logo. please help guys. just for a quick overview. was on [ROM] AOKP(Jellybean 4.2.1 )Task & Ktoonsez (12/23) (AT&T/Rogers), potential file system corruption during a routine upgrade, flashed back to stock with odin (meaning i can still boot into DL mode), but CANNOT boot into RECOVERY mode. i'm freaking out
jamesquags said:
i need some help here guys. i was running AOKP for the longest time and loving it. then today i tried to update to the latest version. i downloaded the rom and went to flash the .zip in CWM. i've done this dozens of times. this time things were completely different. i kept getting FCs over and over. so i booted into recovery again to reflash. for whatever reason, it seemed like my file system was corrupted. folders i had never seen were all over the place. it was a big mess.
i decided to flash back to stock. i booted into DL mode and did this with odin successfully. then upon reboot, the phone was stuck at the Samsung logo. looking into this i saw that i needed to boot into recovery, wipe data/factory reset, wipe cache, and wipe dalvik cache. i tried doing this but no matter what, my phone will not boot into recovery.
i have even used odin to flash CF-SGS3-CWM-v5.5-v1.0.tar. when i press volume up+home+power i get the first samsung logo with the tiny blue text up at the top saying "recovery booting" but then nothing happens and the phone just goes to a normal boot attempt, which stalls at the samsung logo. please help guys.
just for a quick overview. was on [ROM] AOKP(Jellybean 4.2.1 )Task & Ktoonsez (12/23) (AT&T/Rogers), potential file system corruption during a routine upgrade, flashed back to stock with odin (meaning i can still boot into DL mode), but CANNOT boot into RECOVERY mode. i'm freaking out
Click to expand...
Click to collapse
First of all, good job on searching before posting! :good:
Second, if you want help, try using capital letters at the start of a sentence and using paragraphs. It makes it sooo much easier to read that way.
Third, just keep trying. But from what you're saying about a file-system issue, that could be bad? It's not familiar to me anyways. Hope it didn't damage the internal SD.
If nothing else works, then try the USB-JIG to access Recovery mode. They're like $5 on eBay.
Okay, try these things.
1) Odin a non-rooted, stock ROM that comes with a 3E recovery and try to access that recovery.
If that doesn't work, move onto this step:
2) Odin a different recovery. I attached one to this post. Just unzip it and then odin it. :CWM-Recovery-LTE-SGS3-v5.tar:
Try to get recovery again after a battery pull.
If that doesn't do it, then try this next:
1) Odin a rooted ROM onto the phone.
2) Download the attached "openrecovery-twrp-2.3.1.0-d2att" and unzip it.
3) Download this ADB & Fastboot tool and extract it to your C:/ drive with subfolders using this path: "C:/Android/platform-tools/".
Here is the file to download:
http://www.androidfilehost.com/?fid=9390135922294523275
4) Rename the openrecovery-twrp-2.3.1.0-d2att to "recovery" and place it into the Platform-tools folder.
5) Open the JPEG and follow the EXACT same commands in the pic. This will install TWRP recovery for you.
Then try once again to get into recovery.
If it still doesn't work, then buy a USB Jig.
REPLY
Thanks so much for the advice.
Regarding the TWRP installation, is the phone connected to the computer in DL mode for this?
I am currently downloading a rooted stock ROM. This might help shed light on what is going on here.... I unzipped the .tar you attached to your first post and stuck it in the PDA slot with the phone connected and in DL mode. ODIN did nothing and the returned a FAIL message saying that it "Failed to Open Serial [COM] Port". Hmmmm. Anyways I am going to try to install the TWRP recovery. If not I will buy the USB jig. Thanks again for you help. -jim
jamesquags said:
"Failed to Open Serial [COM] Port".
Click to expand...
Click to collapse
Have you installed the phone drivers? They're linked from the Odin thread.
smelenchuk said:
Have you installed the phone drivers? They're linked from the Odin thread.
Click to expand...
Click to collapse
Yes i have installed the drivers. I have flashed multiple .tar files today.
jamesquags said:
Thanks so much for the advice.
Regarding the TWRP installation, is the phone connected to the computer in DL mode for this?
I am currently downloading a rooted stock ROM. This might help shed light on what is going on here.... I unzipped the .tar you attached to your first post and stuck it in the PDA slot with the phone connected and in DL mode. ODIN did nothing and the returned a FAIL message saying that it "Failed to Open Serial [COM] Port". Hmmmm. Anyways I am going to try to install the TWRP recovery. If not I will buy the USB jig. Thanks again for you help. -jim
Click to expand...
Click to collapse
The TWRP doesn't use Odin. You have to use ADB/FastBoot like I show in the picture attached with it.
I have yet to find an Odin flashable TWRP.
CZ Eddie said:
The TWRP doesn't use Odin. You have to use ADB/FastBoot like I show in the picture attached with it.
I have yet to find an Odin flashable TWRP.
Click to expand...
Click to collapse
After flashing the ROOTED STOCK ROM, I tried about 7 times to boot into recovery. It finally did!!! I then was able to do a wipe data and cache and I'm all set.
Thanks so much for helping me out. -jim
To get into recovery hold the power+volume up+ home key when you see the blue text at the top of the screen let go if the power button but still press the home + volume up
Sent from my SGH-I747 using Tapatalk 2
jerrycoffman45 said:
To get into recovery hold the power+volume up+ home key when you see the blue text at the top of the screen let go of the power button but still press the home + volume up
Click to expand...
Click to collapse
Why do you continue to hold the home + volume up? I release all three as soon as I see the blue text and it goes into Recovery just fine for me.
CZ Eddie said:
Why do you continue to hold the home + volume up? I release all three as soon as I see the blue text and it goes into Recovery just fine for me.
Click to expand...
Click to collapse
i dont know i have always done it that way well learned something new just tried it your way thanks
I have a Samsung Galaxy S3 SGH-I747 (AT&T) that I updated OTA to 4.1.1 a while back. I just decided to root the phone using Odin3 V3.04 and clockworkmod.tar. I tried using clockworkmod at first but couldn't get the phone to go into CWM recovery mode. It just went into stock recovery instead. Reading further, I was told that I need to flash fixboot.tar first, then clockworkmod.tar, then flash CWM_SuperUser_3.0.7.zip file in recovery mode. When I used odin to flash fixboot.tar and rebooted, it boots the Galaxy S3 logo, at&t chime, then goes black with Amber light. It will not boot fully. I then used Odin to flash clockworkmod.tar, rebooted and it also went to blackscreen.I was then able to go into recovery mode and flash the Superuser zip file and reboot but I'm still getting the black screen. What did the fixboot.tar file do to my phone?? Can I reverse this without flashing a whole new rom? I have search the forum for severalhours now with no luck. Any help would be great.
where did you get your initial information and tar? as well as the fixboot info and tar?
check out this rooting thread here on xda. the purpose is to flash cwm recovery onto your device. you then boot into the custom recovery you just installed and root from there. instructions are on the thread.
recovery mode is: vol up + home + power. release just the power button when your device vibrates
xBeerdroiDx said:
where did you get your initial information and tar? as well as the fixboot info and tar?
check out this rooting thread here on xda. the purpose is to flash cwm recovery onto your device. you then boot into the custom recovery you just installed and root from there. instructions are on the thread.
recovery mode is: vol up + home + power. release just the power button when your device vibrates
Click to expand...
Click to collapse
I got it from this link - http://rootgalaxys3iii.com/root-at-t-galaxy-s3/
I am aware of the process you mentioned, but it would not work. It just kept going into standard recovery mode instead of custom recovery so I could never root from there. Thats when I came across this link and thought I needed to flash fixboot.tar first as it states. It did work! I was able to flash clockworkmod.tar and then root the phone, but what good does that do now that my phone is hosed at the blackscreen...There were two sites that said to use this fixboot method. I should have known better...
I just read your thred. Looks like my problem was letting the phone reboot. Is there any way to reverse the fixboot.tar I used? Maybe there is a 4.1.1 boot.tar that can put things back as they were?
via the link i provided, in odin, were you unticking the "auto reboot" box?
i've used that thread method on several S3's with no problems. if you were getting a PASS message then it actually worked.
can you get into recovery now? if so, wipe data/factory reset and wipe cache. reboot.
xBeerdroiDx said:
via the link i provided, in odin, were you unticking the "auto reboot" box?
i've used that thread method on several S3's with no problems. if you were getting a PASS message then it actually worked.
can you get into recovery now? if so, wipe data/factory reset and wipe cache. reboot.
Click to expand...
Click to collapse
I used that method from another site and I was getting a pass. It looks like my issue was letting it reboot. When it didn't go into CWM recovery,I used the fixboot.tar and thats when my phone would not boot past the boot screen. I still have some unsaved material and don't want to wipe the phone. I can get into CWM recovery now. Will doing a data/factory reset wipe everything? If so, is that my only option at this point? I don't want to go to factory and lose everything unless I have to.
OpusxXx said:
I used that method from another site and I was getting a pass. It looks like my issue was letting it reboot. When it didn't go into CWM recovery,I used the fixboot.tar and thats when my phone would not boot past the boot screen. I still have some unsaved material and don't want to wipe the phone. I can get into CWM recovery now. Will doing a data/factory reset wipe everything? If so, is that my only option at this point? I don't want to go to factory and lose everything unless I have to.
Click to expand...
Click to collapse
Well, since I got no response, I did what you said and deleted everything. I still have the same problem. Phone boots to Samsung logo, does jingle and geos to blackscreen with blue light.
Back to my original question. I used the fixboot.tar and it jacked my phone where it only boots to blackscreen with blue light. Is there a fix for this???
Hi guys,
could anyone please help, I've been playing around quite a lot with rooting and flashing, but now I'm stuck with a problem I can't solve...
Device
Galaxy Tab S 8.4 WIFI (SM-T700 klimtwifi)
Starting point
Flashed CM12 , with CF root and TWRP
Everything ok, but had some trouble with wifi and root, so I wanted to flash a new rom.
Problem
Tried flashing another rom (can't remember if it was AROMA or BlissPop...), but the flashing got stuck.
Now I can only access Download-mode, not Recovery and normal boot gets stuck in the white Samsung-logo, I get past first screen and some other Samsung-animation.
What I've tried
Access to Recovery, not working (I have a stock-backup on internal SD)
Flashed stock image via Odin (T700XXU1ANL1_T700AUT1ANL1_HOME.tar.md5). Should be on right now, but no change in working.
Re-flash TWRP via Odin (tar-file)
Have I missed something? Any problem with going back and forth between Android 4 and 5?
F-B said:
Hi guys,
could anyone please help, I've been playing around quite a lot with rooting and flashing, but now I'm stuck with a problem I can't solve...
Device
Galaxy Tab S 8.4 WIFI (SM-T700 klimtwifi)
Starting point
Flashed CM12 , with CF root and TWRP
Everything ok, but had some trouble with wifi and root, so I wanted to flash a new rom.
Problem
Tried flashing another rom (can't remember if it was AROMA or BlissPop...), but the flashing got stuck.
Now I can only access Download-mode, not Recovery and normal boot gets stuck in the white Samsung-logo, I get past first screen and some other Samsung-animation.
What I've tried
Access to Recovery, not working (I have a stock-backup on internal SD)
Flashed stock image via Odin (T700XXU1ANL1_T700AUT1ANL1_HOME.tar.md5). Should be on right now, but no change in working.
Re-flash TWRP via Odin (tar-file)
Have I missed something? Any problem with going back and forth between Android 4 and 5?
Click to expand...
Click to collapse
After flashing the stock image, factory reset in recovery again.
But I can't get into recovery, even after flashing stock...
To elaborate, pressing vol up + power + home does not have any effect. Pressing vol down + home + power gives downloading mode as normal.
F-B said:
To elaborate, pressing vol up + power + home does not have any effect. Pressing vol down + home + power gives downloading mode as normal.
Click to expand...
Click to collapse
Sounds like one of the partitions is damaged, its strange because when you flash the stock firmware it relays all the partitions, just to verify you downloaded one of the big factory images from sammobile.com that's 1.6gb big, then flashed with Odin the extracted tar file...also you might not have a custom recovery installed if you have so vol up and home n power wouldn't work......
Maybe your way out of this is going the other way, flash a custom recovery through Odin, then get into that and use it to install ironrom which is like stock but cleaner.
F-B said:
To elaborate, pressing vol up + power + home does not have any effect. Pressing vol down + home + power gives downloading mode as normal.
Click to expand...
Click to collapse
Try pressing power +vol down and up together+home and then as soon as screen goes dark/black press power+vol up+home hopefully that will get you into recovery.
Have you edited to vold.fstab file
---------- Post added at 01:15 PM ---------- Previous post was at 01:07 PM ----------
If you have edited the vold.fstab file then try to flash a stock rom via odin with the pit file of your device.
F-B said:
But I can't get into recovery, even after flashing stock...
Click to expand...
Click to collapse
Just to elaborate when flashing stock through Odin it wipes your custom recovery and root...hence why you need to use auto root again through Odin.
Cheers guys for your inputs! I'll only get my hands on the tab this evening, so I'll test your solutions then and report back-
maxal said:
Try pressing power +vol down+home and then as soon as screen goes dark/black (just before you enter download mode) press power+vol up+home hopefully that will get you into recovery.
Click to expand...
Click to collapse
Thanks, have to try this!
pdolton2000 said:
Sounds like one of the partitions is damaged, its strange because when you flash the stock firmware it relays all the partitions, just to verify you downloaded one of the big factory images from sammobile.com that's 1.6gb big, then flashed with Odin the extracted tar file...also you might not have a custom recovery installed if you have so vol up and home n power wouldn't work......
Maybe your way out of this is going the other way, flash a custom recovery through Odin, then get into that and use it to install ironrom which is like stock but cleaner.
Click to expand...
Click to collapse
Yeah, flashed T700XXU1ANL1_T700AUT1ANL1_HOME.tar.md5 2,4gb
Tried flasing TWRP, no difference. Maybe here's the timing as well...
max86533 said:
Have you edited to vold.fstab file
---------- Post added at 01:15 PM ---------- Previous post was at 01:07 PM ----------
If you have edited the vold.fstab file then try to flash a stock rom via odin with the pit file of your device.
Click to expand...
Click to collapse
No clue about vold.fstab, so I seriously hope I haven't edited it
pdolton2000 said:
Just to elaborate when flashing stock through Odin it wipes your custom recovery and root...hence why you need to use auto root again through Odin.
Click to expand...
Click to collapse
Yeah, have to make sure I have done it in right order, Stock -> Root -> Custom Recovery... I've tried so many solutions that I'm starting to doubt myself.
Unfortunately, I find myself in the same situation, I do not know what to do.
Have you flash pit file via odin because maybe your device partitions corrupt during rooting.
F-B said:
To elaborate, pressing vol up + power + home does not have any effect. Pressing vol down + home + power gives downloading mode as normal.
Click to expand...
Click to collapse
F-B said:
Cheers guys for your inputs! I'll only get my hands on the tab this evening, so I'll test your solutions then and report back-
Thanks, have to try this!
Yeah, flashed T700XXU1ANL1_T700AUT1ANL1_HOME.tar.md5 2,4gb
Tried flasing TWRP, no difference. Maybe here's the timing as well...
No clue about vold.fstab, so I seriously hope I haven't edited it
Yeah, have to make sure I have done it in right order, Stock -> Root -> Custom Recovery... I've tried so many solutions that I'm starting to doubt myself.
Click to expand...
Click to collapse
Hi just to add I have just edited the instructions I gave you please read again.
F-B said:
Cheers guys for your inputs! I'll only get my hands on the tab this evening, so I'll test your solutions then and report back-
Thanks, have to try this!
Yeah, flashed T700XXU1ANL1_T700AUT1ANL1_HOME.tar.md5 2,4gb
Tried flasing TWRP, no difference. Maybe here's the timing as well...
No clue about vold.fstab, so I seriously hope I haven't edited it
Yeah, have to make sure I have done it in right order, Stock -> Root -> Custom Recovery... I've tried so many solutions that I'm starting to doubt myself.
Click to expand...
Click to collapse
Okay sounds like you've hit a dead end but don't panic your not the first to hit this point with t700.
Okay here's what I want you to do,
1. Open up device manager and completely remove your adb driver making sure to check the "also delete driver " box if shown
2. Download this http://developer.android.com/sdk/win-usb.html the latest Google adb drivers ..DL this ready actually.
3. Completely disable anti virus..remove if you have to, along with windows defender .
4. Restart
5. Download "i know it seems mad" the austrailian firmware http://www.sammobile.com/firmwares/download/43233/T700XXU1ANL1_T700XSA1AOA1_XSA/ and extract the file inside the archieve
6. Right click Odin and run as administrator to be safe.
7. Go for gold and try this...if it works your laughing and can change the firmware or ROM to any local area.
8. If...this doesn't work...restart one last time n try again, if still no then try using another laptop or PC if you can
Good luck keep me updated...I am trying to find you another solution too, got an idea with something called heimdall but not sure as never used it, supposed to be an alternative to Odin.
Hi All, finally had the time to sit down and test your solutions. As it happens, the first (easiest) thing I tried was the timing in pushing recovery boot, according to great help of Maxal. Worked on first attempt, booted into stock recovery, wiped everything and stock rom booted. I was prepared to do it all, so it was funny that a few well-timed presses of buttons solved it .
Now I'm rooted with TWRP and BlissPop again. Thanks everyone for great suggestions and assistance!
I also solved, it was enough to wait for the battery becomes exhausted, recharge the tablet and once off from entering recovery and do a factory reset.
The system is restarted.
maxal said:
Try pressing power +vol down and up together+home and then as soon as screen goes dark/black press power+vol up+home hopefully that will get you into recovery.
Click to expand...
Click to collapse
Man, you're genius! Thanks!