Would appreciate any help…
Tab 8.9 wifi only UK model running rooted stock HC. Flashed US stock ICS without problem and everything working. However, could not root as recovery mode was not allowing me to flash a zip from the sd card (‘E: unknown volume for path /sdcard’ error).
Attempted to flash back to stock HC (yes it was the right file!). Tablet now freezes at ‘Samsung Tab 8.9’ splash screen. Cannot boot into recovery at all. Can boot into download but Odin gets only so far before freezing (at hidden.img.md5)
I’ve seen the threads here and in the 10.1 forums which suggest draining the battery completely and doing some clever stuff with various drivers (nvflash). Is this my route forwards or is there another answer?
Did you try re-flashing stock recovery?
Sent from my DROID RAZR using XDA Premium HD app
...and the solution is:
1. in download mode flash ics stock until Odin freezes
2. disconnect and reboot to recovery if possible. Then reboot from there if recovery mode comes up
3. Reboot to download and try to flash ics stock again from Odin
Repeat
Each time I did this Odin made a bit more progress until finally it finished and I had ics back
Absolutely no idea why this worked!
Related
I was recently using Stunner ICS but decided I wanted to go back to stock and start over. I downloaded the stock N7000XXKJ4_N7000OXXKJ4 firmware and installed it through odin. I did not receive any errors on the phone or on my PC. But now it seems like my phone is stuck in a boot loop. It just keeps showing the samsung boot animation over and over. I used the download jig to get into download mode and tried redoing the firmware twice already with no luck. One thing I did notice is that the jig is no longer resetting the binary counter. Does anyone have any other ideas or is my phone possibly bricked?
This is supposed to be in Q& A section... Anyways... Did you try wipe?
Sent from my GT-N7000 using xda premium
What worked for me having the same problem recently is go to Recovery mode (Volume up + home + power) and you'll see this funny kinda recovery, not at all CWM Do a data wipe/factory reset and then reboot.
Same thing happened with me yesterday, wipe in recovery fixed the problem
priyanv said:
This is supposed to be in Q& A section... Anyways... Did you try wipe?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I'm sorry. Mods please move to appropirate section.
Thank you guys. I was beginning to freak out. I was trying to do the recovery menu but couldn't get it to work. I thought the recovery menu was also hosed but I had the wrong buttons. All is good now! thank you so much!
First thing you need to do if you want to get back GB, flash abyss 3.9 redpill kernel.
After that flash GB rom.
So later you can flash whatever kernel you want
Sent from my GT-N7000 using xda premium
Hanging at Samsung logo; can't boot into recovery; am I bricked???
Hi guys...
I've been semi bricked for about 18 hours now. And it's starting to look like it's a full-brick.
I had the latest Gingerbread ROCKET ROM on my Samsung Galaxy Note GT-N7000, with the latest Franco kernel in place.
I thought I'd give the ICS version of ROCKET ROM a go. Flashed Abyss4.2 kernel without any hassles. Used 'advanced' to boot into recovery. Did my various wipes. Flashed the ICS Rocket Rom zip. And got caught up in the recurring boot-up, mostly upgrade, run, reboot cycle that's been described in many places.
Didn't panic.
Booted into recovery again, and flashed the ICS Rocket Rom again.
But this time, it wouldn't go past the SAMSUNG logo.
Still, I could boot into recovery.
Which I did.
And I tried to restore my Gingerbread build from Nandroid.
Tried it. But it hung on the Samsung logo again.
With one key difference... Now, no matter how much I try, I can't boot into recovery.
I *CAN* boot into 'download' mode. So I've used PC Odin to try and inject a rooted Gingerbread rom into the phone.
The instructions tell me to wait for the phone to reboot twice. Sadly, it tries its first reboot, and doesn't get past the Samsung logo. And that's where it hangs. No recovery mode either.
What shall I do??? Oh, woe is me. Etcetera.
--------------------------------------------------------
UPDATE
--------------------------------------------------------
I found a version of Abyss 4.2 kernel in tar format. I flashed it via PC ODIN, and I now seem to have a phone that can boot again.
Not much more to report at the moment, cos the battery is on about 3%, so I'm charging it now before delving further. Will give more feedback once the battery's up and running again.
Here's a link to the Abyss file: http://forum.xda-developers.com/attachment.php?attachmentid=1072122&d=1337500067
I tried all of this, was on stock ICS 4.0.3 and had it rooted.
I tried to restore a backup which was sadly on GB and then the restore of /data failed
I then tried to flash paranoid custom rom and it was successful but the phone never went any further than SAMSUNG GALAXY NOTE GT-N7000 logo
I then Flashed a direct rootable stock rom via PC odin and all was well but the phone would never go any further than the logo before mentioned
I tried flashing AbyssNote kernel via pc odin but the CWM recovery menu kept on rebooting hence leaving me with not particular choice to select
Tried wiping data, cache mem, dalvik cache but no use and now i am on stock recovery menu. please help me out
i have this Samsung i9220 china i try to flash upgrade the firmware with Odin3 v1.85 . i got stock phone can't power non recover modem non booting logo , does anyone have any ideas ?
Hi there.
I am trying to install 4.1.1 Rom, and I've got this problem, no matters which rom I choose. Here are the steps I follow:
1.- Install Official 2.3.6 firmware with Odin
2.- Install Clockworkmod with Odin
3.- Go into Recovery Mode and follow the install instructions from the ROM (wipe data..., install from sd card)
4.- And here it goes. I got "Samsung Galaxy Logo - ROM Logo - Installation init" again and again. The installation shows log messages that I don't have enough time to read (something about E unknown, or can't mount. I've tried flashing with dbdata.rfs.tar, but with no luck)
Any help? Thanks in advance.
Reflash you have to flash twice and also I recommend flashing on top is cm not GB as it seems to stop imei issues
Sent from my Awesome I9000 running Slim Bean
Keep pressed the Recovery Combo until you see the Samsung Galaxy S first screen. It will force to enter Recovery mode.
Then wipe again and reflash
Instead of directly installing clockwork mod, install the cf-root kernel instead, which gives you root and CWM. That's what I normally do anyway.
He/ She doesn't need too there flashing straight to another ROM don't need root
Sent from my Awesome I9000 running Slim Bean
Thank you all for the replies.
I'll try them tonight and I'll let you know if it works out
It does that to me everytime I want to upgrade frome Gb to ICS or ICS to JB
I pull out the battery to stop the bootloop, then put it back in and get in recovery mode with three-buttons combo, then flash again the rom, it shouldnt bootloop again.
I started with last solution (remove battery and flash rom again) and it has worked out! The thing is that after removing the battery and flashing it again, "another" recovery mod is loaded and then it all goes perfect. So, thanks all for the help!
Yes as it changes the partition table and needs a different recovery to handle it properly
Sent from my Awesome I9000 running Slim Bean
I unrooted my Galaxy Note N7000 via ODIN using a UK firmware (Car warehouse) one
I did all the things which was posted in the method but when it get suceeded my phone reboot and does not load up, the samsung logo keeps blinking and nothing happens. I tried going in Recovery mode too but it keep "Downloading do not turn off the target" and don't go anywhere beyond that.
Please help what i have done wrong here?
Its not recovery mode,i guess you entered download mode
Flash the firmware again
Sent from my GT-N7000 using xda premium
Ok. If you are coming from a JB rom you will need to reset. To do that safely, you will need to flash a safe kernel first. Download philz kernel zip version for the rom you just installed on the phone. Place it on ext sd and boot into recovery by using vol up + home + power.
Flash the kernel using aply update.
Now reboot into recovery and do a factory reset. Once done do a reboot and your phone will boot. But it will be rooted again. You can flash the rom again to completely unroot. This time phone will boot normally without the above steps
Dear friends,
Little background. I was on CM10 stable, but decided to I update to CM10.1 M1, After the update, had no market, however, so I tried to downgrade to CM10 stable and it bricked. So .. back to stock it is! Now I am having trouble getting out of stock. I am not new to flashing, but I never had this kind of a persistent problem.
The short summary of what I get no matter what I try is: Every kernel that is not the stock Eclair kernel has boot-animation messed up (random lines of color on screen), and I cannot enter recovery - I sometimes can boot sometimes cannot.
Steps I have taken
I went back to stock Eclair rom + non-root kernel (LINK).
I rooted (LINK)
But when I tried to update kernel to allow CWM, it bricked my phone. So back to stock, again!
I tried this a few times. Now, the latest attempt, I tried the stock 2.3.5 rom + rooted, CWM kernel (LINK... I get the phone running, but I cannot get into recovery, and no utility that has "reboot to recovery" has managed to get me into recovery.
The plea
All I want is CWM, so I can install what I want. Without it, I am stuck with Odin one-click and Odin flashable packages (Heimdall does not want to work right for me - the drivers are messed up - and trying to fix those brkeas my Odin drivers).
I have no data on the phone at the moment, I can reinstall everything if need be .. but I am out of ideas besides keep trying different roms and kernels until something gives me CWM and I am free again.
I have AT&T GB bootloaders.
thanks for any help, I will try to provide any additional info I can.
dozyaustin said:
Dear friends,
Little background. I was on CM10 stable, but decided to I update to CM10.1 M1, After the update, had no market, however, so I tried to downgrade to CM10 stable and it bricked. So .. back to stock it is! Now I am having trouble getting out of stock. I am not new to flashing, but I never had this kind of a persistent problem.
The short summary of what I get no matter what I try is: Every kernel that is not the stock Eclair kernel has boot-animation messed up (random lines of color on screen), and I cannot enter recovery - I sometimes can boot sometimes cannot.
Steps I have taken
I went back to stock Eclair rom + non-root kernel (LINK).
I rooted (LINK)
But when I tried to update kernel to allow CWM, it bricked my phone. So back to stock, again!
I tried this a few times. Now, the latest attempt, I tried the stock 2.3.5 rom + rooted, CWM kernel (LINK... I get the phone running, but I cannot get into recovery, and no utility that has "reboot to recovery" has managed to get me into recovery.
The plea
All I want is CWM, so I can install what I want. Without it, I am stuck with Odin one-click and Odin flashable packages (Heimdall does not want to work right for me - the drivers are messed up - and trying to fix those brkeas my Odin drivers).
I have no data on the phone at the moment, I can reinstall everything if need be .. but I am out of ideas besides keep trying different roms and kernels until something gives me CWM and I am free again.
I have AT&T GB bootloaders.
thanks for any help, I will try to provide any additional info I can.
Click to expand...
Click to collapse
Messed up screen = wrong bootloaders. Flash Odin KK4 with bootloaders
From there, follow this link.
Finally, you can get back up on CM10.1 - Btw, you had no market cause you didn't flash their Gapps.
UPDATE .. ugh that took a while:
1) From the master list LINK, wet back to 2.1, I897UCJF6
2) From the same thread installed I897UCKF1 with bootloaders
3) rooted: LINK (I know -not XDA)
4) removed the 3e recovery lock (LINK) - this did not seem to work, but I did do it.
5) installed Speedmod kernel from here LINK - this did not boot, but it did install CWM
6) installed CM10.0 Stable from SD cadr - twice
7) installed gapps
8) just did my first boot to CM10.
This is both a record for myself for later, and for anyone else that may find this useful.
BWolf56 said:
Messed up screen = wrong bootloaders. Flash Odin KK4 with bootloaders
From there, follow this link.
Finally, you can get back up on CM10.1 - Btw, you had no market cause you didn't flash their Gapps.
Click to expand...
Click to collapse
Ooooh. I learn something new every day! Thanks.
Sent from my SGH-I897 using xda app-developers app
Hi!
Today i wanted to update my firmware just because Samsung Kies asked me if i wanted to. I couldn't have been more wrong when i chose to update.
The update froze at 3% and after a lot of time i unplugged the phone and ended up with a brick instead of a phone.
If i try to turn it on, i get a black screen with a "phone--!--pc" picture. I can enter Download Mode by pressing VolumeDown + HomeButton + PowerButton and i get an android logo with ''Downloading... Do not turn off target'' written under it.
My phone was never rooted, nor updated ( it remained with its out-of-the-factory OS and everything ).
For the past 6 hours i've been trying to use Odin v4.43 along with AriesVE.ops (the one from the well-known WORKED2 archive) to try and get recovery-clockwork to work.
So my questions are:
Given the fact that my phone was not rooted, how can i get my GT-I9001 to work again? Is this even possible?
Can i first root it in its condition, then flash a custom rom like cyanogenmod? Or do i need to install a stock rom and then try a custom one?
What other options do i have?
Everything i've tried so far with Odin froze while downloading and i have no other solution to this problem. Please help!
zerkylo said:
Hi!
Today i wanted to update my firmware just because Samsung Kies asked me if i wanted to. I couldn't have been more wrong when i chose to update.
The update froze at 3% and after a lot of time i unplugged the phone and ended up with a brick instead of a phone.
If i try to turn it on, i get a black screen with a "phone--!--pc" picture. I can enter Download Mode by pressing VolumeDown + HomeButton + PowerButton and i get an android logo with ''Downloading... Do not turn off target'' written under it.
My phone was never rooted, nor updated ( it remained with its out-of-the-factory OS and everything ).
For the past 6 hours i've been trying to use Odin v4.43 along with AriesVE.ops (the one from the well-known WORKED2 archive) to try and get recovery-clockwork to work.
So my questions are:
Given the fact that my phone was not rooted, how can i get my GT-I9001 to work again? Is this even possible?
Can i first root it in its condition, then flash a custom rom like cyanogenmod? Or do i need to install a stock rom and then try a custom one?
What other options do i have?
Everything i've tried so far with Odin froze while downloading and i have no other solution to this problem. Please help!
Click to expand...
Click to collapse
Yes it is possible as long as your device boots into Download mode.
No you can't root it in its current condition.
You need to download a stock firmware, flash it using Odin or Heimdall (recommended), then root it and finally install a custom ROM if you want.
kalpetros said:
Yes it is possible as long as your device boots into Download mode.
No you can't root it in its current condition.
You need to download a stock firmware, flash it using Odin or Heimdall (recommended), then root it and finally install a custom ROM if you want.
Click to expand...
Click to collapse
Thank you for answering!
I fixed the issue. Tried different usb port along with a different version of CWM (5.5.0.4) which I installed with Odin v4.43. CWM 5.5.0.4 caused a bootloop, but i used it only to install CWM 6.0.4.9 from external_sd, so the bootloop problem was gone. Then flashed CyanogenMod 11 and now works like a charm !
I attached an archive with CWM 5.5.0.4, AriesVE.ops and Odin v4.43, so that anyone having my problem can solve it the way i did. But keep in mind that this version of CWM *may* cause a bootloop, so prior to installing it, you should have a working version of CWM on your external_sd. Use CWM 5.5.0.4 to install the better version of CWM from your external_sd. Also, whatever you do is at your own risk!