Related
So, disclaimer. I'm an idiot today. Don't mind me.
So today I decided to go to jt's CM7 from ComRom 2.1 (non gingerbread)
Backed up everything, made a nandroid, wiped everything installed cwm 3.x.
Went and started to flash CM7. That didn't exactly like me too much as it went into a 45min long bootloop saying that it failed. No big deal. Nows the fun part. Rewiped everything, started to reinstall the ComRom. That didnt like me either, it says that it cannot mount Cache/recovery/log etc. So I thought. Okay, well I can always ODIN!
Ideas folks?
Thanks in advance.
Sorry about the bump/post, forgot to edit this one instead.
OK! Ignore above, used odin so now im on stock eb01 but still when i use odin to flash cwm 3.0.2.8x it still says it cannot open or mount cache/recovery/log and recovery/last_log.
At this point, I just want to get it so I can nandroid back to where i was on comrom.
Ideas?
What I did, ODIN the atlas2.2 and ebo1 Froyo package, boots up to stock fine no problem.
Attempted to flash CWM 3.0 in ODIN. flashes fine.
3 finger salute. doesnt boot, have to hold it for about a second then cwm just pops up saying it cant mount recovery.
Then I re ODINd eb01, deleted all voodoo, cwm, update.zip etc from sdcard.
re tried to flash cwm 3.0
same thing.
Completely lost haha
New ; odin's dl09, OTA'd up to current. What steps should I take next given my issues with CWM?
By deleting the file named clockworkmod on your sd card, you most likely deleted all of your nandroid backups. unless you backed up you sd card to your computer, im pretty sure they are gone. Im sorry. As far as the rest of your problems... I know a stock kernal will overwrite clockworkmod every reboot.
schu9120 said:
By deleting the file named clockworkmod on your sd card, you most likely deleted all of your nandroid backups. unless you backed up you sd card to your computer, im pretty sure they are gone. Im sorry. As far as the rest of your problems... I know a stock kernal will overwrite clockworkmod every reboot.
Click to expand...
Click to collapse
I did back up everything, made sure of that haha. So I should try reflashing a kernal? or would that have been included in the ODIN package/ OTA updates I did?
Thanks
tkirane said:
I did back up everything, made sure of that haha. So I should try reflashing a kernal? or would that have been included in the ODIN package/ OTA updates I did?
Thanks
Click to expand...
Click to collapse
there may have been a kernel in the ota updates, the problem us you need a non stock kernel..stock ones over write recovery in every boot
My suggestion....
odin eb01 with the atlas 2.2pit and repartition checked.
Fully boot after eb01 flash
Odin cwr 3-30-all and immediately three finger boot into cwr....wipe everything
Flash cm7 build 7/4 completely reboot
Use the power menu to access recovery...this time it will be cwr 4.x.x.x flash the
Cm7 build your want with no wiping, thats what works for me
Sent from my SCH-I500 using XDA App
efan450 said:
there may have been a kernel in the ota updates, the problem us you need a non stock kernel..stock ones over write recovery in every boot
My suggestion....
odin eb01 with the atlas 2.2pit and repartition checked.
Fully boot after eb01 flash
Odin cwr 3-30-all and immediately three finger boot into cwr....wipe everything
Flash cm7 build 7/4 completely reboot
Use the power menu to access recovery...this time it will be cwr 4.x.x.x flash the
Cm7 build your want with no wiping, thats what works for me
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I believe I attempted that last night at home, I will definitely try again after I am out of work. Would you happen to have a link to download of cwr 3-30-all?
Also, would I be correct in the assumption that same steps would apply to ComRom installation.
Also too, I am currently on the ED04 non-rooted stock OTA. Do same rooting methods that I used way back on dl09 still apply?
Sorry for the multiple idiotic questions, just much different this time around do to the inability for CWM (either 2.5 or 3.0) to be able to locate/mount the cache/recovery/log.
Would that have to do with Root? thats my main concern is getting into CWM for it to say it cannot mount. After this point I have it reboot system and it does not boot up again. It boots into CWM immediately. So it is unable to bot back into the actual phone mode. So then I reflash dl09 or eb01 in ODIN and start over.
tkirane said:
I believe I attempted that last night at home, I will definitely try again after I am out of work. Would you happen to have a link to download of cwr 3-30-all?
Also, would I be correct in the assumption that same steps would apply to ComRom installation.
Also too, I am currently on the ED04 non-rooted stock OTA. Do same rooting methods that I used way back on dl09 still apply?
Sorry for the multiple idiotic questions, just much different this time around do to the inability for CWM (either 2.5 or 3.0) to be able to locate/mount the cache/recovery/log.
Would that have to do with Root? thats my main concern is getting into CWM for it to say it cannot mount. After this point I have it reboot system and it does not boot up again. It boots into CWM immediately. So it is unable to bot back into the actual phone mode. So then I reflash dl09 or eb01 in ODIN and start over.
Click to expand...
Click to collapse
rooting has no effect on wheather or not recovery (cwm) sticks, its the stock kernel that is overwriting it as soon as you boot. com rom 2.0 comes with a kernel in the flash so if you do this exactly you'll be on comrom rooted with recovery
The steps for going to com rom would be the same this method may be overkill but it should get you cleared up....you said you odin'd ebo1 and the atlas pit before in your previous post,so im going to assume you know how to properly get into download mode and what do, and not do in odin, so down load cwr 3-30-fix all here, and save it on your pc in your odin folder
http://forum.xda-developers.com/attachment.php?attachmentid=556634&d=1301538947
download com rom (ukb) 2.0 either from your phone or from your pc, connect your usb cord and move it to the root of your sd card.(ie.not in a folder)
pull the battery,and odin the ebo1 tar with the atlas 2.2 with repartition checked, when its done insert batt and boot fully.
when done pull batt, odin cwr 3-30-fix all, when done insert batt and right away hold volume up, down, and power and continue to hold until your see the red cwr screen.
wipe data(factory reset)/wipe cache/go to advanced and wipe dalvik
go to install zip from sd, and find the comrom ukb zip and select install...when its done select reboot and done...at this point your phone will look like its not doing anything and its important to be patient you will hear the voodoo lady talking to you and this is good, when your phone fully boots hit the power button and select recovery and at the recovery screen go to backup and restore and select nandroid backup and run it, when its done reboot and enjoy
if you want to go to ukb 2.1 just download the patch, boot into recovery and flash, no wipe needed.
as a side note the 3-30 file you odined will not be your recovery after this is complete because comrom comes with its own recovery, after you get on to this rom the recovery that came with it will be the one you see.
i used these same steps to go to cm7 but i have only had success by, odin cwr 3-30 fix all, wipe everything and then install build date 7/4 and reboot completely, and power menu to recovery and flash the 7/13 build.
efan450 said:
rooting has no effect on wheather or not recovery (cwm) sticks, its the stock kernel that is overwriting it as soon as you boot. com rom 2.0 comes with a kernel in the flash so if you do this exactly you'll be on comrom rooted with recovery
The steps for going to com rom would be the same this method may be overkill but it should get you cleared up....you said you odin'd ebo1 and the atlas pit before in your previous post,so im going to assume you know how to properly get into download mode and what do, and not do in odin, so down load cwr 3-30-fix all here, and save it on your pc in your odin folder
http://forum.xda-developers.com/attachment.php?attachmentid=556634&d=1301538947
download com rom (ukb) 2.0 either from your phone or from your pc, connect your usb cord and move it to the root of your sd card.(ie.not in a folder)
pull the battery,and odin the ebo1 tar with the atlas 2.2 with repartition checked, when its done insert batt and boot fully.
when done pull batt, odin cwr 3-30-fix all, when done insert batt and right away hold volume up, down, and power and continue to hold until your see the red cwr screen.
wipe data(factory reset)/wipe cache/go to advanced and wipe dalvik
go to install zip from sd, and find the comrom ukb zip and select install...when its done select reboot and done...at this point your phone will look like its not doing anything and its important to be patient you will hear the voodoo lady talking to you and this is good, when your phone fully boots hit the power button and select recovery and at the recovery screen go to backup and restore and select nandroid backup and run it, when its done reboot and enjoy
if you want to go to ukb 2.1 just download the patch, boot into recovery and flash, no wipe needed.
as a side note the 3-30 file you odined will not be your recovery after this is complete because comrom comes with its own recovery, after you get on to this rom the recovery that came with it will be the one you see.
i used these same steps to go to cm7 but i have only had success by, odin cwr 3-30 fix all, wipe everything and then install build date 7/4 and reboot completely, and power menu to recovery and flash the 7/13 build.
Click to expand...
Click to collapse
I definitely know my way around odin and recovery haha thank you very much for the help. I'll try it out once I am out of work and let you know how it goes. I was doing just that only with cwr 3.0 not the fix all. so hopefully that does the trick. Hopefully I wont be seeing and mount cache errors.
So I did use the recovery-all last night to no avail, still says that it cannot mount certain items.
I have to three finger salute it, then let go after a while for it to boot to CWM, then it cannot mount cache:recovery/command and recovery/log and dev/block/st111
Also when trying to wipe data it cannot mount datadata
Then I do reboot system now and it reboots to CWM with same errors.
EDIT : Found an ODIN for EC01 ComRom 2.0
Going to try that out and see what happens.
I'm an idiot. I realized I kept ODIN'ing pit with CWM, aka, BAD idea. All fixed and running.
Thanks everyone!
tkirane said:
I'm an idiot. I realized I kept ODIN'ing pit with CWM, aka, BAD idea. All fixed and running.
Thanks everyone!
Click to expand...
Click to collapse
Lol glad to hear your up and running...I've had my share of idiotic moments and lucky our phones are pretty brick proof...and now we can add to the list that using a pit file and trying to odin cwr while it won't allow your phone to work..... you can still recover even from this with out perma-bricking!
Sent from my SCH-I500 using XDA App
Ok so today i finally figured out how to root my Samsung Galaxy S Fascinate 3g+(Telus and now as I'm going through trying to install custom roms i see that it only uses 3e and not CWR
Is there any solution to my problem and yes I have been looking around the forums for a almost 3 hours and now have become mildly enraged seeing no support for my phone
well, I have been going through alot of the same stuff with my Telus fascinate too.I don't think im capable of writing a full guide, but I can tell you the basics about how I got to CM7 with a working stable kernel.
First Odin back to stock 2.2
A. Download Odin (attached) and the Telus JL3 stock files http://www.megaupload.com/?d=C3DQ1LZF
B. Open Odin, and put the files in the appropriate boxes
s1_odin_20100512.pit in "PIT"
T959TLJL3-REV03-ALL-low-CL763100.tar.md5 in "PDA"
T959TLJL3_FROYO_Phone-CL763100.tar in "PHONE"
SGH-T959D-CSC-TLSJL3.tar.md5 in "CSC"
C. Boot into download mode by turning phone off, then holding "Volume Down" while connecting the phone to the computer
D. The first "ID:COM" box should turn yellow and show a numerical COM port
E. Click "Start" and wait for it to finish and reboot, and unplug the phone after the yellow box turns green and says "PASS"
next
http://www.megaupload.com/?d=GJCCIU4N
Odin this file using the "pda" part of odin. Let your phone boot up and go through the voodoo lagfix. Once your booted up, it might be a good time too root your phone again.
also this might not be needed, but if you get no service once your on your custom rom.this can help.
So while still on stock, download an app called "nitrality" perform an efs backup. Then copy the "insanity" folder from your phone to somewhere safe.
ok, now that your rooted and have a cwm recovery, reboot into recovery and flash the custom kernel zip found here
http://forum.xda-developers.com/showpost.php?p=18268484&postcount=3865
CM7_SGS_20111009_NEO_17-voodoo-col_BLN.zip is what I use
pull battery and reboot into recovery once more. From there flash your rom, CM7 in my case.
http://cm-nightlies.appspot.com/?device=galaxysmtd
After installing the rom, again reflash the platypus kernel, and your all good to go.
If you have no service, then put that "insanity" folder on your phone, install nitrality and perform the efs restore.
Sorry for the all over the place guide.
fromthestars said:
well, I have been going through alot of the same stuff with my Telus fascinate too.I don't think im capable of writing a full guide, but I can tell you the basics about how I got to CM7 with a working stable kernel.
First Odin back to stock 2.2
A. Download Odin (attached) and the Telus JL3 stock files http://www.megaupload.com/?d=C3DQ1LZF
B. Open Odin, and put the files in the appropriate boxes
s1_odin_20100512.pit in "PIT"
T959TLJL3-REV03-ALL-low-CL763100.tar.md5 in "PDA"
T959TLJL3_FROYO_Phone-CL763100.tar in "PHONE"
SGH-T959D-CSC-TLSJL3.tar.md5 in "CSC"
C. Boot into download mode by turning phone off, then holding "Volume Down" while connecting the phone to the computer
D. The first "ID:COM" box should turn yellow and show a numerical COM port
E. Click "Start" and wait for it to finish and reboot, and unplug the phone after the yellow box turns green and says "PASS"
next
http://www.megaupload.com/?d=GJCCIU4N
Odin this file using the "pda" part of odin. Let your phone boot up and go through the voodoo lagfix. Once your booted up, it might be a good time too root your phone again.
also this might not be needed, but if you get no service once your on your custom rom.this can help.
So while still on stock, download an app called "nitrality" perform an efs backup. Then copy the "insanity" folder from your phone to somewhere safe.
ok, now that your rooted and have a cwm recovery, reboot into recovery and flash the custom kernel zip found here
http://forum.xda-developers.com/showpost.php?p=18268484&postcount=3865
CM7_SGS_20111009_NEO_17-voodoo-col_BLN.zip is what I use
pull battery and reboot into recovery once more. From there flash your rom, CM7 in my case.
http://cm-nightlies.appspot.com/?device=galaxysmtd
After installing the rom, again reflash the platypus kernel, and your all good to go.
If you have no service, then put that "insanity" folder on your phone, install nitrality and perform the efs restore.
Sorry for the all over the place guide.
Click to expand...
Click to collapse
EDIT: so at the http://cm-nightlies.appspot.com/?device=galaxysmtd what did you mean my CM7 in your case
EDIT2: Ok so now that platypus is installed my phone is now looping from the SGH screen to Platypus and then for about a second it shows recovery mode
I used the stable RC of cm7. galaxysmtd
I apologize for the boot looping, im not overly technical. Just, those are the steps that got me up and running. Maybe try the other Kernel on that thread?
No its alright. I fixed to looping by flashing the stock froyo. Now i just need to figure out how to not have this happen again
fromthestars said:
I used the stable RC of cm7. galaxysmtd
I apologize for the boot looping, im not overly technical. Just, those are the steps that got me up and running. Maybe try the other Kernel on that thread?
Click to expand...
Click to collapse
which one do i click?
EDIT:Nevermind got everything working Thanks
Okay, as the thread title states and as I had searched for a Samsung Vibrant related thread about this issue I haven't found any. My issue as stands is when I try to perform a Factory Data Reset on my Samsung Vibrant t959VUVKD1, 2.2.1 Froyo, it only comes up with this set of words on the recovery screen.
-- Wiping data...
Formatting DATA:...
Data wipe failed.
Formatting CACHE:...
Formatting DBDATA:...
Db data wipe Failed.
-- Appling Multi-CSC...
Installing Multi-CSC
Install default apk;files, please wait
E: Can't mount /dev/block/mmcblk0p2
(No such file or directory)
E:copy_data_default_apk:Can't mount DATA:
your storage not prepared yet, please use UI menu for format and reboot actions.
Click to expand...
Click to collapse
So, as one can see this is evidence of my attempt at rooting and using Clockworkmod Recovery.
What I used was SuperOneClick 2.2 and successfully rooted my phone but then I decided to unroot after finding out ClockworkMod Recovery wasn't able to create a backup on my phone, also, I used a 3e_recovery_installer batch file I found somewhere which managed to unlock my Android system recovery so I could get into Clockworkmod Recovery but ever since I unrooted and uninstalled Clockworkmod Recovery it won't allow me to perform a factory data reset. I was able to do it TWICE after unrooting my phone but now I can't perform the factory data reset and I do not understand why.
Have you tried to odin back to stock or use the toolbox?
http://forum.xda-developers.com/showthread.php?t=954509
Never used Odin or Toolbox before because I've never found a concrete tutorial on how to correctly flash/root my vibrant. I would like to flash but I just don't feel safe about it even though I had downloaded a supposedly stock rom of the UKVD1 rom for Vibrant.
nomadrider123 said:
Have you tried to odin back to stock or use the toolbox?
http://forum.xda-developers.com/showthread.php?t=954509
Click to expand...
Click to collapse
Erm, I used the Toolbox to use "Flash to Stock" and when Odin opened up I selected Pit.pit and it showed a yellow to green color on the first box and my phone turns off then nothing happens. What does this mean?
1. When odin opens select pit
2.click the Pit.pit file after screen change and click open
3.You should be returned to odin main.
4. click pda
5.click pda file and click open.
6.you are returned to main odin.
7.set phone down, click start and do not unplugg
8 let it run till pass, and auto reboot
Sugartibbs said:
1. When odin opens select pit
2.click the Pit.pit file after screen change and click open
3.You should be returned to odin main.
4. click pda
5.click pda file and click open.
6.you are returned to main odin.
7.set phone down, click start and do not unplugg
8 let it run till pass, and auto reboot
Click to expand...
Click to collapse
I did all that just now but now I'm stuck on a looping charging screen or a looping Samsung Vibrant screen. However, this isn't the same as the original T-Mobile screen and even so how do I get past the looping screen?
1. pull the battery
2. insert the battery
3.hold down volumeup/ volumedown buttons
4. insert the usb cable, you should enter download.
5 reset toolbox and select flash to stock, odin should appear,
My experience.
When you are facing boot loop, it's very hard to get in to download mode.
I tried button trick for download mode, but I failed.
So I used adb and tried to reboot into download mode by command.
I repeated it until I could get into the mode.
Anyway, download Toolbox and once u get into the mode,
try to go back to stock. That 'll fix everything.
I also know that the logo changed after I flashed back to stock.
I faced I9000 logo which wasn't before.
FYI: + the version will be eclair, and I couldn't get the official update.
Anyway good luck.
---------- Post added at 03:09 AM ---------- Previous post was at 03:02 AM ----------
If you never get into download mode.. Try to use JIG.
Another way is to disassembly your phone and do something.
I suggest you buy a JIG.
Problem is, I can easily get into Download mode by:
1. Remove USB Cable
2. Pull battery and re-insert
3. Plug in USB cable
4. Hold Volume - and +
And it's in Download mode
But I want to get the original Smasung Vibrant 2.2.1 UVKD1 Rom back on but it appears the provided files aren't it?
Btw, what is a Pit and and PDA file supposed to be, I'm a complete noob at this point.
The pit and pda files in aio toolbox are the stock rom the vibrant is shipped with, if you want anythig else on it you have to download it and flash it through odin, rom manager, or cwm.
Sugartibbs said:
The pit and pda files in aio toolbox are the stock rom the vibrant is shipped with, if you want anythig else on it you have to download it and flash it through odin, rom manager, or cwm.
Click to expand...
Click to collapse
I see. But now when the phone starts up it shows a buncha dots in consecutive order to the Samsung Vibrant screen after I flashed to stock using the pit and pda files and it just loops continuously until I pull the battery. Is there anything that can be done to get past the looping?
Does the pitcure look like a phone....!....computer? If so then you are softbricked and just get back in download mode and re-Odin, but make sure that when you Odin, you DO NOT have the repartition checked. Probably what happened.
If it is not the above, can you get into recovery? Can you now do a factory reset? Wipe cache, dalvik and reset usually clears the bootloop problem.
Woodrube said:
Does the pitcure look like a phone....!....computer? If so then you are softbricked and just get back in download mode and re-Odin, but make sure that when you Odin, you DO NOT have the repartition checked. Probably what happened.
If it is not the above, can you get into recovery? Can you now do a factory reset? Wipe cache, dalvik and reset usually clears the bootloop problem.
Click to expand...
Click to collapse
Unfortunately I can't get into recovery. I also Odin'd with the given Pit.pit and PDA.tar files with Repartition unchecked but that didn't change anything.
I cant figure how you could be in a bootloop coming out of odin. Is the AIO you downloaded for vibrant. I think theres one for fascinate and captivate.
Sugartibbs said:
I cant figure how you could be in a bootloop coming out of odin. Is the AIO you downloaded for vibrant. I think theres one for fascinate and captivate.
Click to expand...
Click to collapse
I used the AIO Toolbar for Vibrant as provided by the link by the person earlier. The loop just continues forever and ever until I remove the battery.
The three button method of entering recovery hasnt worked?
You mean hold Power and Vol + and -?
No, it doesn't work.
i am hesitant to advise anything, the fact that factory reset didnt work, and recovery has been removed is troubling. when i get a fail message when flashing to stock ive used eugenes froyo that does not brick. If all else fails you might google it and read the op. Its a pda file used by odin.
What I find strange is that download mode works perfectly fine but nothing else.
what I find strange is coming out of odin and looping, you should come out in recovery with an error message. a cannot mount data or bdata. storage not ready. Removing recovery may have removed more than was expected. check the op on eugenes froyo you have to get back to stock.
So my vibrant won't boot up. I've tried odining it back to stock, and no matter what I do, it will almost get to the galaxy S screen (freezes as it is forming the S). Download mode and recovery mode both work.
Pull the battery, boot into recovery and wipe factory reset, wipe cache, and advanced->wipe Dalvik. The reboot. Will take longer b/c it has to rebuild Dalvik but it should work out fine. I had the same thing happen the two nights ago coming off ICS.
Don't forger you won't have CWM and it isn't in the market for 2.1 anymore. You can download it from my signature. Put Update.zip in internal and hit reinstall packages twice (that is if you want flash or restore).
Are you able to "Reinstall Packages" from recovery or does that fail?
Did you check re-partition when converting to stock?
You may have corrupted your internal SD
Sk3tchy said:
Are you able to "Reinstall Packages" from recovery or does that fail?
Did you check re-partition when converting to stock?
You may have corrupted your internal SD
Click to expand...
Click to collapse
The reinstall packages fails. It says: "can't open /sdcard/update.zip" (no such file or directory).
Woodrube said:
Pull the battery, boot into recovery and wipe factory reset, wipe cache, and advanced->wipe Dalvik. The reboot. Will take longer b/c it has to rebuild Dalvik but it should work out fine. I had the same thing happen the two nights ago coming off ICS.
Don't forger you won't have CWM and it isn't in the market for 2.1 anymore. You can download it from my signature. Put Update.zip in internal and hit reinstall packages twice (that is if you want flash or restore).
Click to expand...
Click to collapse
I don't have the option of wiping the Dalvik in recovery. I think its because it went back to the default "Android system recovery <2e>"
I tried wiping everything, but when it boots, it goes to the vibrant screen, then to the tmobile screen (the boot sound works), but then, the screen turns black and it goes back to the vibrant screen again (and it just keeps looping).
Maybe try ka7 or kb5 instead of jfd? Investigate /mnt/efs and the copies in /sdcard/backup? Don't know much about eds, might be worth a look. Reflash SBL for good measure?
cashmundy said:
Maybe try ka7 or kb5 instead of jfd? Investigate /mnt/efs and the copies in /sdcard/backup? Don't know much about eds, might be worth a look. Reflash SBL for good measure?
Click to expand...
Click to collapse
So I flashed ka7, and it gets past the S logo now, but then it turns black and now it says "Kernel Panic" upload mode:
RST_STAT=0x4
PMIC_IRQ1=0x0
PMIC_IRQ2=0x0
PMIC_IRQ3=0x0
PMIC_IRQ4=0x0
PMIC_STATUS1=0x40
PMIC_STATUS2=0x2C
Go to the dev section and download the Toolbox. It is stickied. It has drivers, Odin and the Pit/Tar files to get you back to stock. Get back into download mode and re-run Odin with those files.
Don't forget that you don't have to see the DL mode on your screen as long as the COM box is yellow in Odin.
Also check out this thread.
Woodrube said:
Go to the dev section and download the Toolbox. It is stickied. It has drivers, Odin and the Pit/Tar files to get you back to stock. Get back into download mode and re-run Odin with those files.
Don't forget that you don't have to see the DL mode on your screen as long as the COM box is yellow in Odin.
Also check out this thread.
Click to expand...
Click to collapse
I tried using the toolbox and reflashing the stock rom, but it just gets to the t-mobile "stick together" screen, then screen turn black, then it goes to the battery charging screen.
If you're doing Odin right, with a good rom and pit file, and still have trouble, I guess you could flash the SBL. I had a rom flash (via zipfile) do something unknown which made it nearly impossible to get into download mode. Once I did, I flashed the SBL and I was fine. No idea what happened. I even had a nandroid backup, not a restore, hose my phone once. When the other Phone Gods turn against you, Odin is your friend.
cashmundy said:
If you're doing Odin right, with a good rom and pit file, and still have trouble, I guess you could flash the SBL. I had a rom flash (via zipfile) do something unknown which made it nearly impossible to get into download mode. Once I did, I flashed the SBL and I was fine. No idea what happened. I even had a nandroid backup, not a restore, hose my phone once. When the other Phone Gods turn against you, Odin is your friend.
Click to expand...
Click to collapse
But I can get into download mode. And which sbl should I flash?
Probably the closest-to-stock Froyo SBL you can find.
I'm using a GB SBL from this thread, and he has Froyo also:
http://forum.xda-developers.com/showthread.php?t=1117990
I got stuck in this loop a few months back flashing back to stock from CM7 when Odin froze.
I could get to Download Mode and Stock recovery but had the same error when attempting to "Reinstall Packages" from recovery. The internal SD partition had corrupted.
I flashed Eugene_2E_JK2_Froyo with Odin, which fixed the Internal SD.
If you follow the write up on unbricking when you have the little triangle and phone error on your screen it will get you out of this one.
Your bootloaders are not the issue here. 2e Recovery isn't seeing the Internal SD Card and that it what is causing the hangup on boot.
Yeah, probably just flashing a decent kernel would fix you up, but unless you can find an Odin kernel file, you need to do the whole rom.
BTW, with Linux, you can use
tar -tf <rom file> if you want to see what's in a rom.
You can download the Odin flashable Overstock Kernel which contains the red recovery and flash it. That would give you the ability to format the internal SD and then Mount it to your PC through recovery and copy a Rom over to flash.
Otherwise the Unbrickable Froyo I mentioned before will also work.
The only thing you can do when stuck in a boot-loop, if the previous suggestions don't work, is to just reflash it. You can flash back to stock easily using Heimdall One-Click. http://forum.xda-developers.com/showthread.php?t=1278683
We're missing some info here. What ROM were you using before you flashed back to stock? Did you use a pit file in addition to the pda file in ODIN?
If you were using an ICS (android 4.0.x), flashing back to stock and didn't use a stock pit in addition to stock pda, it would definetly be giving you problems. ICS uses a different partition scheme then does stock (which is on android 2.1). The pit file tells odin how to partition your phone.If you're flashing from Froyo, then this should not be relevant as it uses same partition scheme as stock.
Hey. i have looked in similar threads and i still cant find out how to fix it.
I just got a warranty phone and just updated it to ICS and followed the rooting steps for here http://forum.xda-developers.com/showthread.php?t=1483113
After using the pda.tar provided I Flashed the phone with odin 1.85 and on reboot the samsung galaxy I717 screen comes up the goes straight to the Samsung screen skipping the rogers logo and the start up clip.
then i found this thread http://forum.xda-developers.com/showthread.php?t=1840416 and i got the Rogers stock kernel-only odin pda tar. and flashed the phone again and on start up the telus logo comes up and just sits at that screen.
what do i need to do to get back to stock ics and re root?
Bakon420 said:
Hey. i have looked in similar threads and i still cant find out how to fix it.
I just got a warranty phone and just updated it to ICS and followed the rooting steps for here http://forum.xda-developers.com/showthread.php?t=1483113
After using the pda.tar provided I Flashed the phone with odin 1.85 and on reboot the samsung galaxy I717 screen comes up the goes straight to the Samsung screen skipping the rogers logo and the start up clip.
then i found this thread http://forum.xda-developers.com/showthread.php?t=1840416 and i got the Rogers stock kernel-only odin pda tar. and flashed the phone again and on start up the telus logo comes up and just sits at that screen.
what do i need to do to get back to stock ics and re root?
Click to expand...
Click to collapse
Here is the thread with all the tools required to get back to stock ics and rooting, http://forum.xda-developers.com/showthread.php?t=1740367
bigjoe2675 said:
Here is the thread with all the tools required to get back to stock ics and rooting, http://forum.xda-developers.com/showthread.php?t=1740367
Click to expand...
Click to collapse
wow pure life saver. thanks
Ok so I got the phone back to GB and the updated to ICS.
flashed with ClockworkMod Based Touch Recovery - 04/14/12
installed Superuser-i717-ICS-signed.zip.
then flashed flash_counter_reset_rogers.zip
so now im
custom binary download: NO
Current Binary: samsung offical
working perfect
Well done everyone! Bigjoe's Super Everything thread saved the day. . .again!
rangercaptain said:
Well done everyone! Bigjoe's Super Everything thread saved the day. . .again!
Click to expand...
Click to collapse
It's like the gnote Bible ....LOL
It really is amazing. Big thanks to big Joe!!
Bookmark worthy
gregsarg said:
It's like the gnote Bible ....LOL
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Might be a good name change The GNote Super bible Thread, GSbT, I'll use little b don't want to upset others.
But glad the gnote page helped, it's a thread of all the great work being done around our great community, not my work.
bigjoe2675 said:
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Might be a good name change The GNote Super bible Thread, GSbT, I'll use little b don't want to upset others.
But glad the gnote page helped, it's a thread of all the great work being done around our great community, not my work.
Click to expand...
Click to collapse
:laugh:
yeh....may be hold off on that one....LOL
I have a similar problem but cannot NOT fix it
Bakon420 said:
Ok so I got the phone back to GB and the updated to ICS.
flashed with ClockworkMod Based Touch Recovery - 04/14/12
installed Superuser-i717-ICS-signed.zip.
then flashed flash_counter_reset_rogers.zip
so now im
custom binary download: NO
Current Binary: samsung offical
working perfect
Click to expand...
Click to collapse
Out of the many "stuck on samsung screen", Bakon420's post is mostly resembled of my problem. My Note is stuck at the "Samsung" screen. My hope is that someone can help me find the right thread and right way to fix it. I have read and continue reading. But the fear of keep bricking my Note to point of no return has prompted me to plead for help.
I have a Telus Galaxy Note SGH-i717, out of the box it came with Android 2.3.6. I updated it to Android 4.0.4 using the "update" feature in the "settings" of the phone.
I began rooting it using this method: http://rootgalaxynote.com/galaxy-no...y-note-sgh-i717-icsgingerbreadeasiest-method/. After the method, I verifed that I had "superuser" app. When I used "root checker" app, it declared my Note was not rooted.
So again, I rooted it using another method at http://androidcritics.com/how-to-ro...7-on-android-2-3-6-gingerbread-and-4-0-4-ics/ . This method gave me the "stuck at "Samsung" screen.
On to xda-developers forum, I followed the threads and tried doing this: [STOCK ODIN] [AT&T, TELUS, Bell, Rogers] In case of brick...(http://forum.xda-developers.com/showthread.php?t=1506330). After using odin and Telus stock, Note was stuck at the "Telus" screen.
So I went on to this thread:
[ROOT] [AT&T, TELUS, Bell, Rogers] Pre-Rooted Kernel (flash via Odin) http://forum.xda-developers.com/showthread.php?t=1504218 and tried odin with the provided "pda.tar". Now it's back to "samsung" screen.
I have also tried this method: http://forum.xda-developers.com/showpost.php?p=28725010&postcount=10. Kies won't recognize it and won't do Tools>firmware upgrade and initialize.
All that happened within the 5 hours time frame last night. I feel exhausted. If you have the same problem and have resolved it, please point me a way. Thank you.
My Gosh man !!
Train wreck !!!
Sorry, I am willing to help you...as are the rest of the note family here...but you need to stop blindly flashing to the device...
It's so junked up with binary code, that it can't even crap...(rant off)
Okay Brother....
Do you have a recovery ??? As in CWM ??
If so...boot to the recovery, and wipe data, dalvik,....hell, basically everything 3 times.....(If not...then Odin push the recovery image to the device, so we can clean the garbage out of the system partition, and the boot partition)
You need a recovery to clean this phone up, then wipe all caches, data, battery stats...
Then, pull the battery....do not attempt to reboot, or you'll be stuck again...
Put the battery back in, then boot to download mode, and push the Odin .tar back to the device (the rom from the brick thread)
then reboot...
It may still give force closes etc.....thats because it still has junk in the system partition. but now we can boot into recovery and wipe again..
then on the second boot, you should be pretty clean..
those are the steps I'd use my friend...and no, i'm not pissed at you...it's just been a long azz day, and i know how you feel...g
gregsarg said:
My Gosh man !!
Train wreck !!!
Sorry, I am willing to help you...as are the rest of the note family here...but you need to stop blindly flashing to the device...
It's so junked up with binary code, that it can't even crap...(rant off)
Okay Brother....
Do you have a recovery ??? As in CWM ??
If so...boot to the recovery, and wipe data, dalvik,....hell, basically everything 3 times.....(If not...then Odin push the recovery image to the device, so we can clean the garbage out of the system partition, and the boot partition)
You need a recovery to clean this phone up, then wipe all caches, data, battery stats...
Then, pull the battery....do not attempt to reboot, or you'll be stuck again...
Put the battery back in, then boot to download mode, and push the Odin .tar back to the device (the rom from the brick thread)
then reboot...
It may still give force closes etc.....thats because it still has junk in the system partition. but now we can boot into recovery and wipe again..
then on the second boot, you should be pretty clean..
those are the steps I'd use my friend...and no, i'm not pissed at you...it's just been a long azz day, and i know how you feel...g
Click to expand...
Click to collapse
Okay. I will do it as I type this. First, boot in to recovery as in pressing vol. up and down and power, then let go power when it vibrates, but keep on pressing vol. up/down. It shows a 4g/lte Telus screen for about 2 secs. Now on to Android system recovery <3e>.
Now, using volume up/down to move highlight. Options are: reboot system now, apply update from external storage, wipe data/factory reset, wipe cache partition, and lastly apply update from cache. I don't see "dalvik" as an option. So, I'll do wipe data/factory reset, and wipe cache partition in that order 3 times. Okay, 3 times wipes. Now pull the battery...
Battery back in, boot to download mode. Screen says "ODIN MODE". product name SGH-i717D, custom binary download: YES (6 counts). Current binary: custom. Now load odin3 v1.85 on my computer, load up the "TELUS stock kernel-only odin pda tar" from the brick thread. Now plug in my usb cable to the phone and the computer. Only check boxes are "auto reboot", and "PDA". ID:COM box shows "0:COM6" in yellow color. Now , click start. ODIN Message:
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Now the phone is rebooting and stuck at the "samsung" screen. The computer says "found new hardware Samsung Mobile MTP Device". Kies is loading automatically but not recognize any thing connected. Now booting to recovery to wipe data/factory reset and wipe cache again.
Now pull the battery out... back to recovery mode and reboot system now. It's still stuck in the samsung screen. !!! I feel like an idiot and maybe I am one and I don't know what else to do!
There is every indication that the kernel image you are using is not correct somehow...
And after reviewing the thread link you posted ....the affected user was able to repair the device by loading a rooted stock ICS build from flappjaxxx.
And since his roms contain the kernel image ....you can eliminate the need for a kernel by simply flashing his ICS rom.
But in order to do this ...you need the CLOCKWORKMOD recovery pushed to your device ....
And you currently have the stock 3e recovery. (Will not work)
So you need to push the CWM recovery to your device ....then flash the ICS build using your new recovery ....not Odin.
The only need for Odin at this point is to push the new recovery ...
Lets get that far ....and worry about the modem later...
Note : your device may contain a recovery script that forces the device to revert from a custom recovery, back to the 3e recovery.
Not all devices do.....
But if you do ....it's fixable ....and the fix can be found by a general search....but lets try the recovery push, and rom flash first using these steps ...
On PC .....
Download the Odin CWM recovery from the super thread......the .tar image for Odin
Then download the ICS rooted rom from Flappjaxxx ....the .zip file
Then move the downloaded rom to the download folder of your phones SD card.
Next :
Push the CWM recovery to your device using Odin.
If the device hangs at the samsung screen (it will ) don't pull battery...simply hold volume up and down, then power..
The device will start to vibrate every 2-4 seconds.....and after 3 vibration cycles ..release the power button but continue to hold the volume buttons.
The device will boot your new CWM recovery...
Then navigate to the "wipe data,factory reset " option and wipe the data.....then do the same for the cache and dalvik cache.
Then choose "install zip from SD card "...and flash the rom you placed to the device from the PC ..
Once the flash completely finishes .....reboot
If all went well ....you'll have ICS running ....
Let me know ..g
gregsarg said:
There is every indication that the kernel image you are using is not correct somehow...
And after reviewing the thread link you posted ....the affected user was able to repair the device by loading a rooted stock ICS build from flappjaxxx.
And since his roms contain the kernel image ....you can eliminate the need for a kernel by simply flashing his ICS rom.
But in order to do this ...you need the CLOCKWORKMOD recovery pushed to your device ....
And you currently have the stock 3e recovery. (Will not work)
So you need to push the CWM recovery to your device ....then flash the ICS build using your new recovery ....not Odin.
The only need for Odin at this point is to push the new recovery ...
Lets get that far ....and worry about the modem later...
Note : your device may contain a recovery script that forces the device to revert from a custom recovery, back to the 3e recovery.
Not all devices do.....
But if you do ....it's fixable ....and the fix can be found by a general search....but lets try the recovery push, and rom flash first using these steps ...
On PC .....
Download the Odin CWM recovery from the super thread......the .tar image for Odin
Then download the ICS rooted rom from Flappjaxxx ....the .zip file
Then move the downloaded rom to the download folder of your phones SD card.
Next :
Push the CWM recovery to your device using Odin.
If the device hangs at the samsung screen (it will ) don't pull battery...simply hold volume up and down, then power..
The device will start to vibrate every 2-4 seconds.....and after 3 vibration cycles ..release the power button but continue to hold the volume buttons.
The device will boot your new CWM recovery...
Then navigate to the "wipe data,factory reset " option and wipe the data.....then do the same for the cache and dalvik cache.
Then choose "install zip from SD card "...and flash the rom you placed to the device from the PC ..
Once the flash completely finishes .....reboot
If all went well ....you'll have ICS running ....
Let me know ..g
Click to expand...
Click to collapse
Thank you for your post. I will confirm the correct downloads and methods before actually trying them out. I am quite nervous because of previous failures. If this confirmation step seems overkill and rediculous to you, it is only because I am an idiot.
gregsarg said:
Download the Odin CWM recovery from the super thread......the .tar image for Odin
Click to expand...
Click to collapse
means go to this thread: http://forum.xda-developers.com/showthread.php?t=1584576, download Odin from here: http://thinkleet.de/cwm/cwm-touch-i717-120414.tar.md5.
gregsarg said:
Push the CWM recovery to your device using Odin.
Click to expand...
Click to collapse
means using Odin3 1.85 adready on my PC to load cwm-touch-i717-120414.tar.md5 and flash it on my Note i717D. Is it correct?
gregsarg said:
Then download the ICS rooted rom from Flappjaxxx ....the .zip file
Click to expand...
Click to collapse
means , download this: i717-ICS-UCLE2: Credit and Thank you flappjaxxx. It is on the top and flle name implies it is the lastest version. Also this rom is the one to be moved to my SD card "download" folder. Is it correct?
Thank you. I have downloaded the files and await your confirmation.
Update: Sept. 26
I searched and found a thread that referred to CWM Recovery here: http://forum.xda-developers.com/showthread.php?t=1775263. The file in the mentioned thread is the same as the file you have indicated. So I downloaded it and pushed it to the phone, using Odin. Now I have booted in "CWM-based Touch Recovery v5.5.0.5". Run "wipe data/factory reset 3 times, wipe cache partition 3 times, and get in advanced to wipe Dalvik cache 3 times. Reboot recovery to go back to CWM Recovery main screen. Select "install zip from sdcard". Select "i717-ICS-UCLE2" from the sdcard. It took a few minutes and displayed "Flashing UCLE2 modem", then "Reboot Now", and lastly "Install from sdcard complete.", then return to the "Apply update from .zip file on SD card" screen of the CWM Recovery. Now reboot. There is no selection to reboot from this screen, so I just remove the battery, put it back in and restart the phone using the power button the normal way. The phone restarted with a screen "Samsung Galaxy Note, SGH-i717D", then onto the infamous white-on-blue "SAMSUNG" on the black background screen and stayed there.
Look like there is another problem somewhere else, caused by my second root attempt. For now, I will just sit tight to prevent further damage to the phone. Any thoughts that may explain and/or fix the problem is much appreciated.
Similar problem
Bakon420 said:
wow pure life saver. thanks
Click to expand...
Click to collapse
Hey good day I am currently having the same problem as you. I used odim and the pda file provided by link http://forum.xda-developers.com/showthread.php?t=1504218 however when phone restarts the screen is stuck on samsung. I would love to know what you did to fix this problem.
Thanks in advance
Take a look at the last post in that thread. That is a gingerbread kernel. I'm going to assume you're on ics. You'll have to install an ics kernel in recovery. Just make sure it's the correct kernel for your device and build. Just search and read. Also make sure to check the date on the thread. This thread was from August and the kernel thread you are referring to is from over a year ago. Good luck