Okay so I was running the AOKP milestone 4 build on my US wifi tab [CWM5.0.2.7] and accidentally let my tab battery drain completely. So when I let it charge for a bit and booted it up, to my surprise it froze upon bootup [the pink unicorn]. So I tried wiping data from CWM which did absolutely nothing. So I went and flashed the new CWM [5.5.0.4] which worked fine but it too wouldn't actually do anything. And so I just gave up and tried to return to stock (using ACSyndicate unroot) which started out fine but it got stuck at:
# Manual Mode #
--Updating application...
Copying 'XAB' apk.
Copying Common Apks.
it then reboots and tries again ad infinitum, whether or not its plugged in to my computer. I tried this three times with the same results, though fortunately I can still go into download mode. Any help is much appreciated.
Flash a stock firmware, then CWM, then install the ROM, happens I guess depends on which base firmware you originally were on. Less likely on 3.2, more likely on 3.1
Having same problem
I also soft-bricked and flashed a stock firmware P7510XABKMP_P7510UEKMP_HOME.tar.md5 . Now I'm stuck in the same loop of "# MANUAL MODE # etc. "
When I try to access recovery it just comes up with the #ManualMode# loop but fortunately I can still access ODIN (Download) mode. HELP?
Related
EDIT: As I've now gotten Odin to flash again, and my device still won't boot, I'm really starting to think Andromeda's recovery has wiped something vital that isn't restored with a "regular" stock ROM image. PIT? EFS? Partitioning? Something like that? Odin successfully flashes the whole image tar (which I've previously used successfully), and the boot splash now correctly changes to the default Samsung one without triangle, but still the phone won't boot (as described in msg #3). So I'm now wondering if there's any way to a more aggressive restore (whence the topic title change)? Or am I barking up the wrong tree here?
----------
Hi
Okay, so I was testing out different kernels with Paranoid Android. I had the Dorimanx kernel installed at first, but had some volume issues, so I shifted to the Dream kernel, wouldn't boot. Then then the Andromeda kernel, and it still wouldn't boot, so I thought I might try doing a factory wipe in Andromeda's recovery. It then froze, and after about 20 minutes I gave up waiting for it and reset the device.
I then tried using the recovery to reinstall the Dorimanx kernel that worked, but it would fail, too. Just hang. After some attempts, also at just mounting the storage via USB, everything would fail, a couple of times with a message about emmc not mounting IIRC.
I then got a response on PA's forum about which kernel was suggested, and the answer was the stock kernel, so I thought I'd just use Odin to flash a CF kernel.
I think I had to do two attempts, or maybe just one, but it succeeded in installing the kernel, and the device rebooted. Except it didn't really. I can't get a "regular" boot screen (the one with the triangle), and so I can't get into recovery. Also, when the charger is plugged in, instead of showing first the grey battery icon with the spinner in it (which I seem to remember would spin before) and the going to the battery with green, it just show the grey icon with a spinner that doesn't spin. It never goes to the green battery screen.
I could (and can) still get to download mode, so I thought I'd do a back to stock routine. I downloaded a full stock ROM and tried to flash it with Odin. It would then freeze at the setup connection step. I tried a different image, same result. I tried reflashing the CF kernel (which worked just minutes before with Odin), again with the same result. I tried different USB ports and cables (even though I just used Odin successfully before), rebooting, unplugging at the frozen step and plugging back in, but to no avail. Odin won't flash any .tar.md5 anymore AFAICT. At least not with the regular no-frills one-click approach.
I'm fearing a hardbrick here. Except I still have access to download mode, and Odin sees the device. Could the recovery in Andromeda have destroyed the partition table perhaps? Or overwritten something it wasn't supposed to?
Is there a different approach to recovery that I could try out? Or does any one of you have any tips I might try out? Anything would be most welcome and appreciated
Thank you,
Daniel
PS: Oh, I just tried starting it up after it's been without battery and unplugged overnight and all day. I tried starting it into recovery mode, and now I have a different screen altogether: It says, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. Well, that sounds tempting! Except - I've never used Kies on this device in the first place, and Kies does not having any clue what I've been doing with this thing... Would it be safe to try out? I'm hesitant...
Daniel Smedegaard Buus said:
Hi
Okay, so I was testing out different kernels with Paranoid Android. I had the Dorimanx kernel installed at first, but had some volume issues, so I shifted to the Dream kernel, wouldn't boot. Then then the Andromeda kernel, and it still wouldn't boot, so I thought I might try doing a factory wipe in Andromeda's recovery. It then froze, and after about 20 minutes I gave up waiting for it and reset the device.
I then tried using the recovery to reinstall the Dorimanx kernel that worked, but it would fail, too. Just hang. After some attempts, also at just mounting the storage via USB, everything would fail, a couple of times with a message about emmc not mounting IIRC.
I then got a response on PA's forum about which kernel was suggested, and the answer was the stock kernel, so I thought I'd just use Odin to flash a CF kernel.
I think I had to do two attempts, or maybe just one, but it succeeded in installing the kernel, and the device rebooted. Except it didn't really. I can't get a "regular" boot screen (the one with the triangle), and so I can't get into recovery. Also, when the charger is plugged in, instead of showing first the grey battery icon with the spinner in it (which I seem to remember would spin before) and the going to the battery with green, it just show the grey icon with a spinner that doesn't spin. It never goes to the green battery screen.
I could (and can) still get to download mode, so I thought I'd do a back to stock routine. I downloaded a full stock ROM and tried to flash it with Odin. It would then freeze at the setup connection step. I tried a different image, same result. I tried reflashing the CF kernel (which worked just minutes before with Odin), again with the same result. I tried different USB ports and cables (even though I just used Odin successfully before), rebooting, unplugging at the frozen step and plugging back in, but to no avail. Odin won't flash any .tar.md5 anymore AFAICT. At least not with the regular no-frills one-click approach.
I'm fearing a hardbrick here. Except I still have access to download mode, and Odin sees the device. Could the recovery in Andromeda have destroyed the partition table perhaps? Or overwritten something it wasn't supposed to?
Is there a different approach to recovery that I could try out? Or does any one of you have any tips I might try out? Anything would be most welcome and appreciated
Thank you,
Daniel
PS: Oh, I just tried starting it up after it's been without battery and unplugged overnight and all day. I tried starting it into recovery mode, and now I have a different screen altogether: It says, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. Well, that sounds tempting! Except - I've never used Kies on this device in the first place, and Kies does not having any clue what I've been doing with this thing... Would it be safe to try out? I'm hesitant...
Click to expand...
Click to collapse
the reason for Dream and Andromeda not booting ur phone is that, if ur paranoid rom version was latest, then it comes with the new JB mali drivers for which only Dori v7.4 and siyah v5.0 are compatible
since u have already messed up too much with ur phone, u can try the 'KIES' option as the last resort to restore it back, since odin flash is not wrk'ng for u
Okay, so I tried installing Kies and connecting it. A variety of connection attempts, but it just won't connect to the device.
But, I'm making some progress! I've found that when I can get the phone to boot into the "Firmware upgrade encountered an issue." screen, I can get Odin to flash the stock Gingerbread image (still won't in download mode). And I then get a reboot with the regular Samsung boot splash (no yellow triangle) - except it never gets past it. After about a minute, it'll go black and then boot back up to the same splash screen and the same problem.
This is the exact same image I've used previously to revert the device to stock. So I was kinda hoping to see a normal clean. But unfortunately no donut. It reminds me of a computer I once bricked by screwing with its BIOS - it never got beyond POST and so I couldn't reflash it.
Is there something like a BIOS in this thing that could've gotten damaged in some way? And if so, is there any way to use Odin or another tool to fix that?
Cheers,
Daniel
Tried flashing a couple of matching CF kernels. I now get the green battery after the grey one, but still no boot.
All turned out the be the Shun Andromeda kernel re-introducing the hard brick bug. If you have the same issue, see my reply here for links to where you can get the custom PIT trick up and running.
Hello
I have been using my int Gs3 for sometime and decided to root and explore the mods and custom fw world. I have started with getting to root access and after that install CWM.
Then I try to install nightly cyanogenmod 10. It didnt work and boot back to normal GS3 Touchwiz interface. After that I tried the GooManager and when the phone is restarted it went to bootloop. I removed the battery and put it back. The problem started there.
The phone does not boot to any OS, I only can see the galaxy s3 9300 black splash screen and awatis there. I can go into download mode, but when I go into recovery mode, I can see the Android robot, and it dies The screen is too fast but what I can see it cannot mount EFS, System and any folder.
So I have tried several different methods
- Tried to flash with original rom, different roms, CWM and what I can find suitable for international model. But everytime I got stucked in Nand Write part. In some of them, the flash started and stucked in installing some parts(passes the cache and hidden and stuck after that)
- Tried with bricked phone roms, different PIT files and Bootloader Vralec methods.
- When I am trying these, I have tried with 3 different PC's with/without KIES and Samsung drivers installed. When I plug the phone in Download mode, the PC recognizes it as Generic device.
- I manage to flash the CWM but when it restarts it does not go any further than the first splash screen, but in Odin, some time later it turns to pass. Funny, when the phone is on Galasy S3 black splash screen, the pc recognizes the phone and starts to install the driver.
So, here is an interesting flashing story of mine. I really would appreciate your valuable comments and suggestions.
Thanks in advance.
cugami said:
Hello
I have been using my int Gs3 for sometime and decided to root and explore the mods and custom fw world. I have started with getting to root access and after that install CWM.
Then I try to install nightly cyanogenmod 10. It didnt work and boot back to normal GS3 Touchwiz interface. After that I tried the GooManager and when the phone is restarted it went to bootloop. I removed the battery and put it back. The problem started there.
The phone does not boot to any OS, I only can see the galaxy s3 9300 black splash screen and awatis there. I can go into download mode, but when I go into recovery mode, I can see the Android robot, and it dies The screen is too fast but what I can see it cannot mount EFS, System and any folder.
So I have tried several different methods
- Tried to flash with original rom, different roms, CWM and what I can find suitable for international model. But everytime I got stucked in Nand Write part. In some of them, the flash started and stucked in installing some parts(passes the cache and hidden and stuck after that)
- Tried with bricked phone roms, different PIT files and Bootloader Vralec methods.
- When I am trying these, I have tried with 3 different PC's with/without KIES and Samsung drivers installed. When I plug the phone in Download mode, the PC recognizes it as Generic device.
- I manage to flash the CWM but when it restarts it does not go any further than the first splash screen, but in Odin, some time later it turns to pass. Funny, when the phone is on Galasy S3 black splash screen, the pc recognizes the phone and starts to install the driver.
So, here is an interesting flashing story of mine. I really would appreciate your valuable comments and suggestions.
Thanks in advance.
Click to expand...
Click to collapse
GO here : http://forum.xda-developers.com/showthread.php?t=1993044
Hi all,
I think I broke my Galaxy S (I9000). I hope you can help me somehow. Here is the history of things I already did/tried
- my phone was working and had cyanogenmod 9.1 installed
- I wanted to give my phone a little speedup and wiped the cache and dalvik cache partition (did this before and it worked before)
- after this, phone was in a boot loop (even the battery loading animation rebooted over and over)
- the download mode still worked, but no recovery menu appeared!
- as given on cyanogenmod homepage in the install guide I flashed ClockworkMod Recovery using heimdall
- after that, recovery worked again
- I copied the cm9.1 zipfile on my phone to flash it, wiped the whole phone (factory reset), but flashing fails at some asserts (even though I disabled asserts) that seem to check that the target device really is a Galaxy S (I9000) (unfortunatly, I do not have a screenshot and cannot provide one now)
- I also had a ClockworkMod backup I tried to recover, but it fails at restoring /system (unfortunatly, I do not have a screenshot and cannot provide one now)
- so I thought, maybe I can use a regular firmware and flash it with Odin3 (1.87) to make things working at least a little
- started odin, selected firmware and started, but Odin3 got hung at some early point, so I closed Odin after ~10 minutes (see screenshot odin.jpg)
- when I now start my phone, only two symbols appear which kind of signal a problem with a connection to a (PC-)host which I have never seen before (see screenshot startscreen.jpg)
I tried a lot, but now I am out of ideas. Can you help?
Robert
missing attachments
Missed the attachments. Here they are.
Robert
Turn off phone, remove usb cable from pc if it's connected, remove battery, wait around 10 seconds, while battery is still not in the phone press the button combination for download mode. While u still holding the button combination for download mode, force reinsert the battery. Now phone should go into download mode automatically. Connect cable to pc and phone and flash stock Rom via Odin. Good luck
Worked! Great! Phone is back in download mode. Unfortunatly my work pc does not detect the Samsung composite device so I have to wait until I am back home. I hope Odin is working then. As given, it did not when I last tried.
Can you tell me what kind of mode this is, when those two symbols appear?
Robert
It's not any mode, it just an indication that earlier download mode flashing via Odin failed or interrupted by user.
U probably need to kill Kies process via Windows task manager before flashing with Odin because it's known to interrupt Odin, make it hung at setup connection.
Hi,
brought my phone into download mode again and this time odin flashed succesful. However, Kies was never installed on this computer so I have no idea why it worked now.
After flashing the phone rebooted, but stated several errors. They are similar to those which appear on reflashing with the cm91 zip via recovery mode ( "unable to mount ... (file exists)" ). I have made a screenshot and attached it. You have an idea how to help?
I have tried both the 512 and the 803 pit file, same results.
Thanks,
Robert
Tried to re reboot after those errors, but the S-Animation of the stock rom during boot never ended.
Robert
I took another stock firmware, JVI, which contains also a CSC and PDA image. Flashing worked, phone booted, Works!
I will see how to come back to my cm91, but a great step forward .
Thanks,
Robert
Made it back to cm91 . Thank you for your support.
Here are the steps ...
- applied I9000XWJVI.zip with 512 pit and repartition (2.3.3 based german stock firmware)
- applied I9000XWJW6_I9000DBTJW2_DBT (2.3.6 based german stock firmware)
- applied cf-root-xx_oxa_jw4-v4.4-cwm3rfs.zip as this clockworkmod recovery is able to disable verifications before appling a zip
- applied cm91 zipfile
- restored my backup
Robert
This is the problem I am having with my Samsung Galaxy Note 3 (SM-N900P). This problem just popped up out of the blue on a stock ROM a few days ago and nothing I have tried has gotten close to fixing the issue
Description:
a) The boot sequence repeats in a loop with no more sound. The phone would reboot at the Sprint splash screen
What I've done so far:
a) Pulled the battery and depleted the capacitors
b) Installed TWRP and did a complete wipe
c) Tried installing a custom ROM to see if the issue persisted. ROMs failed to install as /system was being sketchy (at times it was reporting 0MB for partition and then an actual value after repair). When I managed to get a ROM to install still stuck in the boot loop
d) Used Odin to do a full restore to a stock NC5 ROM. The phone got up to initial configuration page and then rebooted, now only gets to the Samsung splash screen before rebooting
Items that I can get into:
Recovery mode
Download mode
I have a 30 second video of it rebooting but cannot post it currently due to the forum rules
Question:
Is this issue fixable or is it a sign of internal memory failure?
Try an older version of TWRP, i.e. 2.8.5.0
Or, try a different recovery.
I'm not sure that it will work, but it's worth a try.
Good luck!
Are you doing it this way?
http://forum.xda-developers.com/showthread.php?t=3069667
rbeavers said:
Are you doing it this way?
http://forum.xda-developers.com/showthread.php?t=3069667
Click to expand...
Click to collapse
I didn't notice that but I just installed TWRP 2.8.0.0 through Odin (like a few minutes ago). Phone actually managed to get to the stock recovery image config screen and was working as long as the cable was still attached to the computer.
As soon as I removed the cable it went straight back to the boot loop
SubRyan said:
I didn't notice that but I just installed TWRP 2.8.0.0 through Odin (like a few minutes ago). Phone actually managed to get to the stock recovery image config screen and was working as long as the cable was still attached to the computer.
As soon as I removed the cable it went straight back to the boot loop
Click to expand...
Click to collapse
Here is what you need to do. First pull battery, reinstall. If you can boot into twrp recovery, fine wipe everything i.e. caches, system, data, etc. If you are on a stock recovery do a factory reset. Pull battery, reinstall and boot into download mode.
NOW let's go to work. First use odin to flash stock NC5 tar. Chances are it will bootloop, STOP !!!! don't panic. Just reflash with odin again. The second time it should take. Remember that your device is setting up for first time use. This will take 3-5 minutes, sitting at the Samsung logo. Since didn't list the most important thing which is what OS you where on where the device Borked, or what you where doing with the device when it Borked. I'm going to assume it was on 4.4.4 and you tried to downgrade to 4.4.2 NC5. In which case a bootloop on the first bootup after a downgrade is normal, you have to flash twice to reset the bootloader. For more info click on rom flashing basics in my signature. Enjoy !!!
Problem solved. I started getting suspicious when the phone would boot up with the charging cable attached to the computer today
The issue was an aftermarket Mugen Power battery that developed a fault. Put the stock battery back in and problem resolved
Thanks for the help guys
I know this is a known issue, but the thing is that most solutions i have found regard looking into the phone's settings.
The thing is I can't even boot my phone any more. The moment I get the Galaxy SIII GTI9300 logo the phone simply freezes there forever.
It's been like hours like this. I even tried removing the battery for half an hour and put it back. It just won't boot any more.
I didn't install a custom ROm after rooting, the phone was freshly rooted and didn't got to that step yet.
I rooted the device by using the toolkit http://forum.xda-developers.com/gal...msung-galaxy-s3-unified-toolkit-v8-0-t1703488
which surprisingly worked pretty fast and I was able to confirm that my phoen was rooted by installing a root-only app (Root Uninstaller)
then i got a message asking me to update the SU binary and when i accepted the update the phoen restarted never to boot again.
I didn't even get the chance to get the ClockworkMod yet.
Now I don't even have ClockworkMod's menu at the beginning, i have nothing. only the classic boot mode that allows me to download software via Odin (which always fails no matter what package I try)
please help me, i have no other device than that right now....
Download-Mode
Hello and good morning,
have you tried to boot into download mode ?
It's the same like s3
Take the battery out for a few seconds . put it back in and boot into download mode again and it should work