So I was running 2.1 Fusion and I installed Voodoo via OCLF and I then tried flashing over it without disabling voodooo. However, I am able to get into cwm and i flashed a voodoo-disable.zip i keep handy in there, no help.
My phone won't reboot, I've ODIN'd and I get an error saying "WIPE DATA FAILED" in big red letters, it shows the S bootup animation however it doesn't fully bootup. I can access Download mode and CWM recovery menus but I can't restore anything it just doesn't boot up... What should I do??? I NEED to use my phone!!!
Helpppppp!!!!11
Do you have adb installed?
Sent from my T-Mobile G2 using XDA App
shaynesaw said:
Do you have adb installed?
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
nooo i don't....
ANYBODY??? What would re-partition do if i set it on ODIN?
bobbbb said:
ANYBODY??? What would re-partition do if i set it on ODIN?
Click to expand...
Click to collapse
Yea repartition, use this odin image also. Worked good for me.
GTO777 said:
Yea repartition, use this odin image also. Worked good for me.
Click to expand...
Click to collapse
I checked Repartition with another odin image I found, it's the one i've always used and it always works, and it still doesn't boot... i have the bottom four buttons lighting up but that's it, nothing booots
I odind that image from your link but it takes me into recovery and there it says cannot verify whole-signature and i still can't reboot...
bobbbb said:
I odind that image from your link but it takes me into recovery and there it says cannot verify whole-signature and i still can't reboot...
Click to expand...
Click to collapse
well if you cant get it to work in ODIN, neither will Samsung most likely. Hope you have insurance IM KIDDING!
What ports is it?
itskohler said:
well if you cant get it to work in ODIN, neither will Samsung most likely. Hope you have insurance IM KIDDING!
What ports is it?
Click to expand...
Click to collapse
I'm not sure what you mean http://media.xda-developers.com/images/smilies/frown.gif but I'm coming from Fusion 2.1 on Galaxy S vibrant...
Whenever I try to odin with that 2.2 image it says cannot in stall update.zip (because i have taken out my sd card) HELP!!!! fmlllll
So i tried the odin 2.2 image with my sd card in and i checked re-partition and it goes to the recovery where it gives me this:
E: Can't mount /dev/block/mmcblk0p2
(Invalid argument)
E: copy_data_default_apk: Can't mount DBDATA:\\E: failed to open/mnt/internal_sd?update.zip
(No such file or directory)
E: signature verification failed
installation aborted
how i do fix my baby????
My p hone boots to the point where the colorful S appears but then it blinks a few seconds and goes black, and i can't turn the phone back on...
No one can save my ass
you can't turn it anymore? even when charging?
iynfynity said:
you can't turn it anymore? even when charging?
Click to expand...
Click to collapse
No... My phone can turn on, get into recovery and get into download mode, but whenever I odin it boots up the S animation then just goes to a black screen. I can't access cwm recovery because i don't have the update.zip, how can I push a ROM to my sd card using ADB, because that's what I think I'll have to do....
have you tried flashing froyo that doesnt brick?
as long there's ODIN and the never failing download mode, vibrant will always comeback from a brick.
bobbbb said:
No... My phone can turn on, get into recovery and get into download mode, but whenever I odin it boots up the S animation then just goes to a black screen. I can't access cwm recovery because i don't have the update.zip, how can I push a ROM to my sd card using ADB, because that's what I think I'll have to do....
Click to expand...
Click to collapse
as long as it's turning on you will be able to fix it. Try to download another stock .tar file then use a pit file. if not try Eugene's Froyo that doesn't brick that wipes everything.
xtone said:
have you tried flashing froyo that doesnt brick?
as long there's ODIN and the never failing download mode, vibrant will always comeback from a brick.
Click to expand...
Click to collapse
Im coming from a 2.1 build can i still dl the froyo that doesn't brick? Even if I don't have ADB, or the cwm or update.zip on my internal sd card?
Sell it to me...just kidding...try to download a 2.1 image file.,maybe that'll work.
Edit: search for the mirror file thread on the development section. Scroll down to the odin section and d/l the newest 2.1 leak img file. Try to flash that with odin. They have the latest update.zip over there that you can d/l.
bobbbb said:
Im coming from a 2.1 build can i still dl the froyo that doesn't brick? Even if I don't have ADB, or the cwm or update.zip on my internal sd card?
Click to expand...
Click to collapse
Sent from my GT-I9000 using XDA App
Related
hey guys. so im rooted and have put plenty of roms on my phone. i was using the miuiwiz 1.1 and wanted to switch to the new aosp miui. when trying to flash it it was saying need to mount sd card and did countdown from 20 and then kept repeating. tried nandroid and nothing would let it boot with out doing that again so im trying to odin back to stock. Maybe im dumb or maybe its just cause i havent done it yet but ive been trying to read directions from other threads and thought i figured it out but im just stuck at the samsung boot screen. will someone please help bc i cant get my phone on now and need it for work tmrw
kendall316 said:
hey guys. so im rooted and have put plenty of roms on my phone. i was using the miuiwiz 1.1 and wanted to switch to the new aosp miui. when trying to flash it it was saying need to mount sd card and did countdown from 20 and then kept repeating. tried nandroid and nothing would let it boot with out doing that again so im trying to odin back to stock. Maybe im dumb or maybe its just cause i havent done it yet but ive been trying to read directions from other threads and thought i figured it out but im just stuck at the samsung boot screen. will someone please help bc i cant get my phone on now and need it for work tmrw
Click to expand...
Click to collapse
Well, first odin "atlas.pit + dl09 or di01" then flash Recovery (preferably 3.x.x.x) > then go into recovery, wipe cache,dalvik,data. Flash CM7. Profit
xHoLyx said:
Well, first odin "atlas.pit + dl09 or di01" then flash Recovery (preferably 3.x.x.x) > then go into recovery, wipe cache,dalvik,data. Flash CM7. Profit
Click to expand...
Click to collapse
huh? sorry that wasnt english to me
kendall316 said:
huh? sorry that wasnt english to me
Click to expand...
Click to collapse
what is the "atlas.pit + dl09 or di01" and where do i get it
kendall316 said:
huh? sorry that wasnt english to me
Click to expand...
Click to collapse
open odin
go into download mode (plug the phon to usb then push volume down)
put This in PDA
and put This in PIT
Press Start.
When you are done Flash This in PDA
When you are done Reboot your phone and turn off the phone.
Go into recovery and wipe Dalvik/Cache/Data. Then flash CM7.
xHoLyx said:
open odin
go into download mode (plug the phon to usb then push volume down)
put This in PDA
and put This in PIT
Press Start.
When you are done Flash This in PDA
When you are done Reboot your phone and turn off the phone.
Go into recovery and wipe Dalvik/Cache/Data. Then flash CM7.
Click to expand...
Click to collapse
did all the above, and now everytime i press reboot now in recovery it just keeps rebooting into recovery and its saying it cant mount a bunch of stuff and when it boots it wont even show the samsung logo anymore
kendall316 said:
did all the above, and now everytime i press reboot now in recovery it just keeps rebooting into recovery and its saying it cant mount a bunch of stuff and when it boots it wont even show the samsung logo anymore
Click to expand...
Click to collapse
Follow the same steps you just did with ODIN with the DL09 file and the PIT file, but this time you also need to put a checkmark in the re-partition box under option all the way to the left of the start button. That box needed to be checked in order for the PIT file to fully do what it is supposed to do. Reboot after flashing the DL09 and Atlas 2.2 pit files in order to let the stock DL09 fully load with the repartitioning. Then you can power down phone, pull battery, flash the CWM file in ODIN, pull usb cord, put battery back in, boot directly to CWM by holding volume up, volume down, and power buttons, then wipe data/cache/dalvik cache and flash whatever ROM you wanted to go to, whether that is CM7 or MIUI.
landshark68 said:
Follow the same steps you just did with ODIN with the DL09 file and the PIT file, but this time you also need to put a checkmark in the re-partition box under option all the way to the left of the start button. That box needed to be checked in order for the PIT file to fully do what it is supposed to do. Reboot after flashing the DL09 and Atlas 2.2 pit files in order to let the stock DL09 fully load with the repartitioning. Then you can power down phone, pull battery, flash the CWM file in ODIN, pull usb cord, put battery back in, boot directly to CWM by holding volume up, volume down, and power buttons, then wipe data/cache/dalvik cache and flash whatever ROM you wanted to go to, whether that is CM7 or MIUI.
Click to expand...
Click to collapse
once i put the atlas file in pit, it automatically checked it
kendall316 said:
once i put the atlas file in pit, it automatically checked it
Click to expand...
Click to collapse
Ok, I've never seen that happen. I've always had to check the re-partition box myself. When you booted to recovery (CWM), what options did you have on the first screen you saw? Did you have an option of "install zip from sd card"?
kendall316 said:
once i put the atlas file in pit, it automatically checked it
Click to expand...
Click to collapse
and i just did the first part of the odin again with those 2 files and now my phone wont turn on
landshark68 said:
Ok, I've never seen that happen. I've always had to check the re-partition box myself. When you booted to recovery (CWM), what options did you have on the first screen you saw? Did you have an option of "install zip from sd card"?
Click to expand...
Click to collapse
yes i did, and i tried to run it but it said it couldnt run bc my cache wouldnt mount
kendall316 said:
and i just did the first part of the odin again with those 2 files and now my phone wont turn on
Click to expand...
Click to collapse
Try it again, but this time use this file in the PDA section:
http://adrynalyne.us/files/stuff/CI500_VZW_DL09_ECLAIR.tar.md5
Make sure battery is out the whole time
Use USB port in the back of the computer near the motherboard
when it finishes, put battery back in and power phone on.
when i first rooted it though i already had froyo. is that gonna make a difference?
kendall316 said:
when i first rooted it though i already had froyo. is that gonna make a difference?
Click to expand...
Click to collapse
No, this is just to do a deep, clean wipe back to a stock build. Getting back to Froyo from there is a piece of cake
okay, I have been on here several days trying to find a solution to this..., I know I am the one that borked it, now I am asking for help in understanding what I need to do to fix it... here is a list of things that I know happened...
A. I rooted the phone, added CWM, created a backup.
B. installed ROMManager
I had seen things on the MUINE ROM, saw it in the list for the vibrant so what the heck right?
C. installed the MUINE from the ROMManager app, rebooted, found that it could not "See" T-Mobile...
D. checked here on issues with the current version of MUINE ROM issues... didn't see anything, so I made sure that it was in USB debug mode, and tried to restore the backup I had made earlier... now comes the problem... , I think that when I tried unsuccessfully to do that with CWM, I tried ODIN, and the re-partition box was ticked... and wiped the internal SD and the update.zip etc, and put it into usb debugging off...
since then, I have tried the revert to stock and root thread, the update that does not brick etc... the AIO Vibrant toolbox tells me that USB Debugging is off, and here is the info on the recovery screen...
Android system recovery <2e>
-- Movi_check Start..!!
checksum confirmation need_checksum[1636849899]
MBR_Chksum in header : id
MBR checksum : 4206DE4BFAA052703D8107823C7EDDAF
MBR Checksum Error
Movinand ChecksumConfirmation Fail
--movi_checking done!...
# MANUAL MODE #
-- Appling Muti-CSC...
Installing Muti-CSC
any help is appreciated...
So you have successfully reverted it back to stock jfd? And you are trying to root and it is giving you those msgs on recovery screen? If yes use one click root then download Rom manager and download the recovery again.
Alex9090 said:
So you have successfully reverted it back to stock jfd? And you are trying to root and it is giving you those msgs on recovery screen? If yes use one click root then download Rom manager and download the recovery again.
Click to expand...
Click to collapse
I am just trying to boot... it goes through the vibrant splash, the galaxy s splash, the tmobile sound and pink splash, and then black... if you touch the capacitive keys, they light up and stay that way... other than that unresponsive... ODIN shows no errors when trying to flash it too... but when it tries to boot after, it comes up to that recovery... I have also from the <2e> recovery screen tried "reinstall packages" but to no avail...
Flash Eugene's froyo that doesn't brick then without rebooting immidietly flash jfd stock and you should be good. Check out this thread if you need links. http://forum.xda-developers.com/showthread.php?p=14960217
Sent from my Transformer TF101 using Tapatalk
Alex9090 said:
Flash Eugene's froyo that doesn't brick then without rebooting immidietly flash jfd stock and you should be good. Check out this thread if you need links. http://forum.xda-developers.com/showthread.php?p=14960217
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
okay, so, load Eugenes rom, and turn off auto reboot, then when Odin is done, reset to the JFD .pit and pda, and turn auto reboot back on for that one?
okay, got it... the load JFD after the no brick without rebooting is what did it, THANKS!!! it probably should be noted when doing this to turn off the partitioning in odin, and the auto reboot and once odin has completed, then remove battery and USB, then bring it into download mode without letting it power up into no brick first... that was the step I was missing, thank you so much for the quick response!!!
Seannon
My phone crashed this morning after running the daily OMFGB from the 31st for a few days. I tried to restart, it won't go past the Glitch Kernel screen. When I go into recovery, I am greeted with this message:
ClockwordMod Recovery v4.0.1.0
E: can't mount /cache/recovery/command
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
wiping data, did not help. reflashing the rom and kernel did not help. I still can't start the phone. What are the steps I need to take to fix this as I am currently not able to use my phone at all.
alemondemon said:
My phone crashed this morning after running the daily OMFGB from the 31st for a few days. I tried to restart, it won't go past the Glitch Kernel screen. When I go into recovery, I am greeted with this message:
ClockwordMod Recovery v4.0.1.0
E: can't mount /cache/recovery/command
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
wiping data, did not help. reflashing the rom and kernel did not help. I still can't start the phone. What are the steps I need to take to fix this as I am currently not able to use my phone at all.
Click to expand...
Click to collapse
Same thing happened to me yesterday..the only way I got my phone working again was to odin eb01 with the atlas 2.2..reboot fully...I then tried to go back to cm7 and got the same message and the only way I was about to fix it was to flash the com rom 2.0 obviously wipe everything before..let that boot and tried to flash cm7 with the recovery from com rom....still same message...i had to odin otb3.x.x.recovery... Download times infinity's recovery zip and flash that in otb recovery, then reboot recovery so I had ti's purple recovery...wipe everything and flash cm7...and success! I used the 7/17 build cause I didn't want nightly then rebooted from power button menu and flashed glitch and gapps.
Sent from my SCH-I500 using XDA App
Oh my goodness, sounds like something is really busted. Do you think it is OMFGB related? Yikes.
I have same thing, but I cant get the phone to show in download mode to odin anything
Same here. I'm now stuck in a boot loop. I can't even restore a backup.
Edit: Just tried to do a restore and the MD5 Sums don't match. I've had to do Odin reset three times today.
I think I might do Vodoo and try to restore that way. I will report back.
alemondemon said:
Oh my goodness, sounds like something is really busted. Do you think it is OMFGB related? Yikes.
Click to expand...
Click to collapse
No I don't think its omfgb related cause I've never ran that rom but I do think it has something to do with all the different recoveries we have floating around and so many different builds with different formats things are bound to get screwed up...my problem came from forgetting to wipe before flashing a different kernel and got me stuck in a boot loop.
Sent from my SCH-I500 using XDA App
I've had this problem ever since I got my Fascinate and tried to get CM7 on it. (2 days ago) I was always able to flash new builds just fine if I managed to get into the orange recovery and not the CM7 one. I believe the one I used was the one on ROM Manager.
This is kinda upsetting...
Hyphnx said:
Same here. I'm now stuck in a boot loop. I can't even restore a backup.
Click to expand...
Click to collapse
Its not the quickest but it should get you back...odin eb01 with the atlas 2.2pit...and reboot. Then odin recovery boot immediately to recovery via 3 finger salute...wipe everything and flash the rom you want...I've had good luck with cwm 3-30 fix all or otb 3x.x.x....if you want to go to cm7 odin the fixed recovery in jt's post and flash cm7 from that recovery....the sticky in the dev section...going from cm7/miui/gb to any other rom should give you some good info and instructions
Sent from my SCH-I500 using XDA App
efan450 said:
Its not the quickest but it should get you back...odin eb01 with the atlas 2.2pit...and reboot. Then odin recovery boot immediately to recovery via 3 finger salute...wipe everything and flash the rom you want...I've had good luck with cwm 3-30 fix all or otb 3x.x.x....if you want to go to cm7 odin the fixed recovery in jt's post and flash cm7 from that recovery....the sticky in the dev section...going from cm7/miui/gb to any other rom should give you some good info and instructions
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
We are having problems with the recovery he posted in his post.
Tried CWM-Recovery-All, turned my phone into muffed up phone. UGH!
Sorry for the double post. I've had to Odin 2 more times which makes it a total of 5 today. I used all the recoveries that are available. One at a time and they all end in the same way.
Hyphnx said:
Sorry for the double post. I've had to Odin 2 more times which makes it a total of 5 today. I used all the recoveries that are available. One at a time and they all end in the same way.
Click to expand...
Click to collapse
So what rom are you running now?
Sent from my SCH-I500 using XDA App
efan450 said:
Same thing happened to me yesterday..the only way I got my phone working again was to odin eb01 with the atlas 2.2..reboot fully...I then tried to go back to cm7 and got the same message and the only way I was about to fix it was to flash the com rom 2.0 obviously wipe everything before..let that boot and tried to flash cm7 with the recovery from com rom....still same message...i had to odin otb3.x.x.recovery... Download times infinity's recovery zip and flash that in otb recovery, then reboot recovery so I had ti's purple recovery...wipe everything and flash cm7...and success! I used the 7/17 build cause I didn't want nightly then rebooted from power button menu and flashed glitch and gapps.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
".i had to odin otb3.x.x.recovery... Download times infinity's recovery zip and flash that in otb recovery"
can you link to that? Is it the voodoo one form here:
http://forum.xda-developers.com/showthread.php?t=1046905
and which is the recovery zip that u flashed from otb recovery? can you link to them, i don't wanna screw this up any more than i already have.
alemondemon said:
".i had to odin otb3.x.x.recovery... Download times infinity's recovery zip and flash that in otb recovery"
can you link to that? Is it the voodoo one form here:
http://forum.xda-developers.com/showthread.php?t=1046905
and which is the recovery zip that u flashed from otb recovery? can you link to them, i don't wanna screw this up any more than i already have.
Click to expand...
Click to collapse
Yup...boot into the otb 3x.x.x recovery and flash the times infinity.zip and then select reboot recovery while in cwm and it should go from the otb one to the times infinity one...at that point wipe everything and flash cm7 build 7/17..not the nightly....once your on the mtd build you can flash the nightly if you wanted
From the power button menu
Sent from my SCH-I500 using XDA App
Edit: I suppose you could just odin times infinity's recovery...I just happened to have the zip on my sd handy so thats why I did it that way...it was that recovery that worked so you could odin it if you wanted it's in the link you posted try flashing it from ti's recovery..I just got there a little differently
Any suggestions if you cant get odin to recognize the phone? Ive tried three Win7 machines both x86 and x64 and three different cables...ALL of them say unknown device. Ive tried pointing to both the Sammy drivers and the nexus ones with no luck.
My phone was revived by simply doing the atlas odin method. I then flashed a fully rooted image...and from there on it's child's play. With that said, I can't get into download mode now, to odin things. What could be causing that? Not, very urgent, because at the moment the phone is running like it should
Thanks so much!
OK so I copied infinity times cwm red to phone and applied that. I still got message about cache. I ran the cwm4 from recovery and now Im back to square one again. I can try to install a ROM, but it boot loops everytime. Can my phone be revived w/o odin? Do I need an updated update.zip file?
humblewarfare said:
OK so I copied infinity times cwm red to phone and applied that. I still got message about cache. I ran the cwm4 from recovery and now Im back to square one again. I can try to install a ROM, but it boot loops everytime. Can my phone be revived w/o odin? Do I need an updated update.zip file?
Click to expand...
Click to collapse
unfortunately a boot loop normally requires odin...use the eb01 tar and the atlas 2.2pit and your phone will be back up and running
From there I would flash com rom and reboot then if you wanna take a stab at cm7...try and flash it with the com rom recovery...if it doesn't work you can just try odin'ing different recoveries as long as you don't let the phone boot fully you can simply pull the battery and try to odin a different recovery.try the one from com rom, the 3-30 fix all, ti's recovery, or jt's fixed recovery...I don't know where I got the file but I also have a recovery named fixed 3 x.x for cm7 but I came remember where I got it.it is important that you let eb01 sit for a few minutes after booting and also let com rom sit for a few minutes after flashing also...I just skipped all the setup stuff to get the main screen and then pulled the battery and started flashing
Sent from my SCH-I500 using XDA App
humblewarfare said:
Any suggestions if you cant get odin to recognize the phone? Ive tried three Win7 machines both x86 and x64 and three different cables...ALL of them say unknown device. Ive tried pointing to both the Sammy drivers and the nexus ones with no luck.
Click to expand...
Click to collapse
I'm running vista home edition...if it matters and I'm using odin v.1.7 try the samsung generic drivers also.but once I'm on cm7 my pc says it doesn't recognize my phone but if I put it in download mode and hook up odin recognizes it...so I'm not sure on that one
Sent from my SCH-I500 using XDA App
alemondemon said:
My phone was revived by simply doing the atlas odin method. I then flashed a fully rooted image...and from there on it's child's play. With that said, I can't get into download mode now, to odin things. What could be causing that? Not, very urgent, because at the moment the phone is running like it should
Thanks so much!
Click to expand...
Click to collapse
Try holding the down button while you plug into your wall charger then just move it to your pc...if that doesn't work...clean the contacts with rubbing alcohol...with the phone off.at worse case there is a jig you can manually force download mode...you can buy or make them
Sent from my SCH-I500 using XDA App
Hey guys, I'm basically screwed right now. I deleted many major applications from the /system/apps drawer. I am running Mac 10.5 on my laptop currently and I want to know how do I flash a working ClockworkMod.
I know, there are plenty of threads about this, but none gave me a REAL answer.
I'm on a Mac, So I can't ODIN in. It needs to be done on 2.2 Froyo.
Everytime I instal a CWM, It boots into Android Recovery and When I hit "reinstall packages", It doesnt do anything.
Please, tell me how to flash a working cwm recovery so I can flash another ROM stable for my Vibrant.
Try not to send me links, because I've seen them all. but If you think that link is the one, please show me.
Thanks In advace guys.
Did you do a backup before anything?
Sent from my PC36100 using XDA Premium App
Sadly no, Because I didnt have CWM installed.
Brazildiogo732 said:
Sadly no, Because I didnt have CWM installed.
Click to expand...
Click to collapse
Can you boot in to bootloader screen?
Truballa4real7 said:
Can you boot in to bootloader screen?
Click to expand...
Click to collapse
Yes I can
Brazildiogo732 said:
Yes I can
Click to expand...
Click to collapse
ok so you can just download the cwm recovery and put it on your sd card and power your phone off then hold volume down and power it should flash the file itself if you cant get to the phone at all other then bootloader try mounting your sd card with another phone or with a micro sd adapter moving the file to the sd and doing what i told you before. that should help..
u might fail signature verification just doing update.zip
i think it should go like :
install odin in windows
flash 2.1
install clockwork
flash whatever u want
cant you use the rom manager from the market to install any fooxx.zip?
Hi guys, I really hope u can help me, cause i admit i did my share of research and got no solution
My N8010 was using GNABO 6.5 and Boeffla Kernel. While using it the other morning, the tablet suddenly rebooted and got stuck on the Galaxy Note screen. It stays on it a few seconds then reboot to the same screen in a loop.
I can access the recovery menu (CWM 6.0.3.6 ) but my options there are pretty limited, cant wipe and cant install zip files. At the botton of the recovery i have the following logs:
Warning: no file_contexts
E: Can´t open /cache/recovery/log
E: Can´t open /cache/recovery/log
E: Can´t open /cache/recovery/last_log
E: Can´t open /cache/recovery/last_log
I read somewhere that the problem should be solved if i could install a new recovery through Fastboot. Problem is fastboot cant find my device when on bootloader (but i can find it through ADB).
Using ADB sideload to install new recovery or new ROM gave me error on CWM.
Please, save my Tabye.
_Gandour_ said:
Hi guys, I really hope u can help me, cause i admit i did my share of research and got no solution
My N8010 was using GNABO 6.5 and Boeffla Kernel. While using it the other morning, the tablet suddenly rebooted and got stuck on the Galaxy Note screen. It stays on it a few seconds then reboot to the same screen in a loop.
I can access the recovery menu (CWM 6.0.3.6 ) but my options there are pretty limited, cant wipe and cant install zip files. At the botton of the recovery i have the following logs:
Warning: no file_contexts
E: Can´t open /cache/recovery/log
E: Can´t open /cache/recovery/log
E: Can´t open /cache/recovery/last_log
E: Can´t open /cache/recovery/last_log
I read somewhere that the problem should be solved if i could install a new recovery through Fastboot. Problem is fastboot cant find my device when on bootloader (but i can find it through ADB).
Using ADB sideload to install new recovery or new ROM gave me error on CWM.
Please, save my Tabye.
Click to expand...
Click to collapse
Samsung devices don't support fastboot instead they have something called download mode, which you can entered powering off the device and then pressing Volume Down button + Power Button simultaneously, after a couple seconds you'll see a warning screen at the warning screen press Volume Up and the device will be in download mode. Then you can use Odin to flash a new recovery, I would recommend checking out this guide on how to flash a recovery with Odin, and this thread for a recovery you could flash for your device model. Let me know if you still have questions.
shimp208 said:
Samsung devices don't support fastboot instead they have something called download mode, which you can entered powering off the device and then pressing Volume Down button + Power Button simultaneously, after a couple seconds you'll see a warning screen at the warning screen press Volume Up and the device will be in download mode. Then you can use Odin to flash a new recovery, I would recommend checking out this guide on how to flash a recovery with Odin, and this thread for a recovery you could flash for your device model. Let me know if you still have questions.
Click to expand...
Click to collapse
Hey Shimp, thanks for the answer.
Unfortunately I tried to flash both TWRP and Philz Touch and, besides going everything ok with odin, the recovery did not change. It is still CWM 6.0.3.6
any other advice?
_Gandour_ said:
Hey Shimp, thanks for the answer.
Unfortunately I tried to flash both TWRP and Philz Touch and, besides going everything ok with odin, the recovery did not change. It is still CWM 6.0.3.6
any other advice?
Click to expand...
Click to collapse
Did you rename the recovery image to recovery.img before your .tar it and then flashed it via Odin?
shimp208 said:
Did you rename the recovery image to recovery.img before your .tar it and then flashed it via Odin?
Click to expand...
Click to collapse
m
I just downloaded a .tar and flashed it. isnt that right?
_Gandour_ said:
m
I just downloaded a .tar and flashed it. isnt that right?
Click to expand...
Click to collapse
Usually that will work however I have ran into times where I had to make sure the recovery image was named recovery.img and then tar'ed that recovery myself and then flashed it through Odin.
shimp208 said:
Usually that will work however I have ran into times where I had to make sure the recovery image was named recovery.img and then tar'ed that recovery myself and then flashed it through Odin.
Click to expand...
Click to collapse
Did that. No success either. Still same recovery.
_Gandour_ said:
Did that. No success either. Still same recovery.
Click to expand...
Click to collapse
Sounds like it is time to restock with the original firmware and Odin and start over.
es0tericcha0s said:
Sounds like it is time to restock with the original firmware and Odin and start over.
Click to expand...
Click to collapse
Already did that. Nothing happened.
_Gandour_ said:
Already did that. Nothing happened.
Click to expand...
Click to collapse
Another thing you could try is just flashing the stock recovery through Odin, and then flashing the new recovery you want over that in Odin.
shimp208 said:
Another thing you could try is just flashing the stock recovery through Odin, and then flashing the new recovery you want over that in Odin.
Click to expand...
Click to collapse
Well.. i can try that, how can i get the stock recovery? Couldnt find it.
_Gandour_ said:
Well.. i can try that, how can i get the stock recovery? Couldnt find it.
Click to expand...
Click to collapse
Did you use the correct firmware? Did it pass successfully in Odin? Did you perform a factory reset after using Odin to install the original firmware?
Stock recovery can be found here:
http://forum.xda-developers.com/showthread.php?t=2102677
es0tericcha0s said:
Did you use the correct firmware? Did it pass successfully in Odin? Did you perform a factory reset after using Odin to install the original firmware?
Stock recovery can be found here:
http://forum.xda-developers.com/showthread.php?t=2102677
Click to expand...
Click to collapse
Used correct firmware. It did pass successfully through odin. Factory reset seems broken.
I will try the stock recovery.
No success with stock recovery.
So... No way to fix at all?
_Gandour_ said:
So... No way to fix at all?
Click to expand...
Click to collapse
To clarify even after flashing the full stock firmware, then flashing another recovery your still stuck on the recovery you were trying to replace correct?
shimp208 said:
To clarify even after flashing the full stock firmware, then flashing another recovery your still stuck on the recovery you were trying to replace correct?
Click to expand...
Click to collapse
Correct
_Gandour_ said:
Correct
Click to expand...
Click to collapse
What settings are you using in Odin when flashing the stock firmware package?
shimp208 said:
What settings are you using in Odin when flashing the stock firmware package?
Click to expand...
Click to collapse
Put tar md5 file on AP/PDA, leave F Reset Time and Auto Reboot checked.
UPDATE:
I sent the tablet to a local technician and hes gonna charge me U$150 to make a repair on the board and restore the system. Does it make sense to you guys? Should i accept the service?