Seems I managed to have no OS, and only twrp on this old phone, which is good because I can actually do something with twrp. The thing is though, it seems I can't flash anything because it can't mount system or data. I can mount this to my computer, I just need advice on what to put on it/flash, because this never happened to me before.
atticusmas said:
Seems I managed to have no OS, and only twrp on this old phone, which is good because I can actually do something with twrp. The thing is though, it seems I can't flash anything because it can't mount system or data. I can mount this to my computer, I just need advice on what to put on it/flash, because this never happened to me before.
Click to expand...
Click to collapse
use this guide:http://forum.xda-developers.com/showthread.php?t=1238070
just in case the link to the firmware doesn't work, here's the stock Verizon Gingerbread build: http://d-h.st/AKs
skepticmisfit said:
use this guide:http://forum.xda-developers.com/showthread.php?t=1238070
just in case the link to the firmware doesn't work, here's the stock Verizon Gingerbread build: http://d-h.st/AKs
Click to expand...
Click to collapse
Thank you very much.
skepticmisfit said:
use this guide:http://forum.xda-developers.com/showthread.php?t=1238070
just in case the link to the firmware doesn't work, here's the stock Verizon Gingerbread build: http://d-h.st/AKs
Click to expand...
Click to collapse
Hi, I am running into a problem with ODIN. It seems when I follow the guide correctly, getting the drivers installed and the phone in download mode, when I start odin it says "<OSM> All threads completed. (succeed 0 / failed 0)". It seems nothing happened. It's just not recognizing the phone, or something. Any help is...helpful...
atticusmas said:
Hi, I am running into a problem with ODIN. It seems when I follow the guide correctly, getting the drivers installed and the phone in download mode, when I start odin it says "<OSM> All threads completed. (succeed 0 / failed 0)". It seems nothing happened. It's just not recognizing the phone, or something. Any help is...helpful...
Click to expand...
Click to collapse
Try different USB ports
If that didn't work, try a different USB cable
And if that didn't work, try a different computer
If you don't have any additional computers or they didn't work, put the USB cable in your cat and see if it works
If not... try your dog
do not attempt the last two items... you will anger your pets
skepticmisfit said:
Try different USB ports
If that didn't work, try a different USB cable
And if that didn't work, try a different computer
If you don't have any additional computers or they didn't work, put the USB cable in your cat and see if it works
If not... try your dog
do not attempt the last two items... you will anger your pets
Click to expand...
Click to collapse
Directions unclear, cyber pets taking over the world.
atticusmas said:
Directions unclear, cyber pets taking over the world.
Click to expand...
Click to collapse
need an eta on android 4.4 for the game boy color pls
Related
My usb port charges, but MOST DEFINITELY will not connect in any way to my pc...with all necessary drivers installed. My fiancee's connects just fine...so my usb is broken. Have tried cleaning it numerous times...etc. Does anyone know if it is possible to return to factory stock 2.2 or 2.1 with a flashable zip? I guess I'm also wondering if a nandroid flash will completely unroot me, also!? I found a file that says it'll take me to baseband T959UVJFD w/out root. Any help would be greatly appreciated!
Check The Bible.
Usually when this is an issue it's b/c of a rom or something, what did you flash? Was it a non-vibrant rom?
s15274n said:
Check The Bible.
Usually when this is an issue it's b/c of a rom or something, what did you flash? Was it a non-vibrant rom?
Click to expand...
Click to collapse
I've got this same problem. It's been like this for a couple days. I'd had Bionix-v1.3.1 on the for 4 or 5 days with no issues. All of a sudden, though, no computers I've tried will recognized the phone in mass storage mode. It still charges fine, though.
Edit: And I couldn't find anything in the Bible on USB connection issues. Maybe I missed it.
PsychoCemia said:
I've got this same problem. It's been like this for a couple days. I'd had Bionix-v1.3.1 on the for 4 or 5 days with no issues. All of a sudden, though, no computers I've tried will recognized the phone in mass storage mode. It still charges fine, though.
Edit: And I couldn't find anything in the Bible on USB connection issues. Maybe I missed it.
Click to expand...
Click to collapse
Same here! Was on Trigger 2.8 and my fiancee is on the same rom with no problems. I'm trying to nandroid but it won't show anything in the folder when I go to Backup and Restore and then Restore. WHAT THE HECK!?
jreed3786 said:
Same here! Was on Trigger 2.8 and my fiancee is on the same rom with no problems. I'm trying to nandroid but it won't show anything in the folder when I go to Backup and Restore and then Restore. WHAT THE HECK!?
Click to expand...
Click to collapse
I've tried mounting in linux, Windows XP, and a mac. None of them work in Mass Storage mode.
I went to Recovery and checked out the Restore option in Backup & Restore. I saw all my backups there, but I didn't try restoring b/c of Voodoo.
Anyone?
jreed3786 said:
My usb port charges, but MOST DEFINITELY will not connect in any way to my pc...with all necessary drivers installed. My fiancee's connects just fine...so my usb is broken. Have tried cleaning it numerous times...etc. Does anyone know if it is possible to return to factory stock 2.2 or 2.1 with a flashable zip? I guess I'm also wondering if a nandroid flash will completely unroot me, also!? I found a file that says it'll take me to baseband T959UVJFD w/out root. Any help would be greatly appreciated!
Click to expand...
Click to collapse
Went to my fiancee's laptop, installed the 64 bit samsung drivers, along with having ADB set up, and boom... was finally able to connect in Odin 1.7 to restore back to stock. Once that happened, I was able to connect on the same laptop to pull all files from the phone to make sure it was wiped out. You can also check partition in Odin. It's wierd, though, cuz my phone would not connect all of a sudden on a specific pc, while it worked just fine on another. And my old lady's worked on both! Same roms, too. WIERD!
jreed3786 said:
Went to my fiancee's laptop, installed the 64 bit samsung drivers, along with having ADB set up, and boom... was finally able to connect in Odin 1.7 to restore back to stock. Once that happened, I was able to connect on the same laptop to pull all files from the phone to make sure it was wiped out. You can also check partition in Odin. It's wierd, though, cuz my phone would not connect all of a sudden on a specific pc, while it worked just fine on another. And my old lady's worked on both! Same roms, too. WIERD!
Click to expand...
Click to collapse
Thanks for this. It does sound like my partitions might be a little funky. I'm reformatting my laptop, so I'll see if starting fresh on at least the computer side will help things along.
PsychoCemia said:
Thanks for this. It does sound like my partitions might be a little funky. I'm reformatting my laptop, so I'll see if starting fresh on at least the computer side will help things along.
Click to expand...
Click to collapse
You're welcome! I thought I was SCREWED!!! Good luck, man!
Currently I have a rooted Sensation.
I tried to install a theme using Rom Manager.
It said it installed successfully.
I reboot.
And when I boot up everything is weird. The drop shadow on all windows is green.
The Desktop isn't showing at all.
I can select applications from the locked menu. (Before I unlock) Like camera, mail etc.
Any thoughts on what might be wrong and how to fix?
Themes may require you to have a de-odexed rom. Is the rom you have odexed or de-odexed?
Either that, or you downloaded a bad file. Re-download and install again to see if it works.
Dave2582 said:
Themes may require you to have a de-odexed rom. Is the rom you have odexed or de-odexed?
Either that, or you downloaded a bad file. Re-download and install again to see if it works.
Click to expand...
Click to collapse
I don't know what odexed means.
I have tried to install it again.
And maybe I should mention that I installed it through bootloader? Recovery or what it is called.
I saw that you were able to install other themes simply using the apk file. But this one required you to install it through recovery.
Currently I am able to take photos and call people. There's no home screen.
When I try to view messages I get an error.
Is there any way I can like reset it to before I installed the theme? I was told to back it up before installing the theme, which I didn't do. Any other way to fix this?
Check out this thread. It will help you get back to a stock rom, since you never made a backup.
I would strongly advise to to backup up everything before you start messing around. That way you have a backup to fall back on in case something like this issue happens.
When I first started messing around with root and custom roms, I never did a nandroid, and the phone was bootlooping. So I had to start over from scratch.
Dave2582 said:
Check out this thread. It will help you get back to a stock rom, since you never made a backup.
I would strongly advise to to backup up everything before you start messing around. That way you have a backup to fall back on in case something like this issue happens.
When I first started messing around with root and custom roms, I never did a nandroid, and the phone was bootlooping. So I had to start over from scratch.
Click to expand...
Click to collapse
Tried Method 2 of debranding since it was the easiest one. Made no difference.
Trying Method 1 right now. Will report back with progress.
Just realized that I am not able to use Method 1 since it requires me to have USB Disk Drive mounted, which I can only do from recovery mode. And since I did not remove the image file it now constantly asks me if I want to update in HBOOT. So I can't really get past it.
If I update, it updates and reboots. If I click cancel it reboots.
What should I do?
Run a RUU. Which carrier are you coming from?
Dave2582 said:
Run a RUU. Which carrier are you coming from?
Click to expand...
Click to collapse
Did you not read my post?
I can not do anything in recovery mode, I.e not enable disk drive.
Just to clarify: There is no way of transferring ANY files from my PC to my phone that I am aware of at the moment.
You should take this into consideration before you come telling me to install stuff.
P1raten said:
Just to clarify: There is no way of transferring ANY files from my PC to my phone that I am aware of at the moment.
Click to expand...
Click to collapse
ever tried plugging your sdcard into your computer?
P1raten said:
You should take this into consideration before you come telling me to install stuff.
Click to expand...
Click to collapse
i smell a little attitude. you should take into consideration that this is not a customer support site. no one has to help you. so please be courteous, even if it means repeating what youve already said.
sweetnsour said:
ever tried plugging your sdcard into your computer?
i smell a little attitude. you should take into consideration that this is not a customer support site. no one has to help you. so please be courteous, even if it means repeating what youve already said.
Click to expand...
Click to collapse
I do not have an adapter.
P1raten said:
Did you not read my post?
I can not do anything in recovery mode, I.e not enable disk drive.
Click to expand...
Click to collapse
I said to run a RUU. It stands for Rom Utility Update. This is an executable program that you can run from the PC to your phone. It will take an image that was made specifically for your phone and flash over what you currently have, and once it's done and you power your phone on, it should look like you just took the phone out of the box. Download the RUU that matches your phone to the PC. Be sure that you pick the right one. Run the RUU on your PC. It will instruct you what to do as far as plugging your phone to the PC, when to turn it on/off, etc.
Once the program finishes, your phone should be reset, stocked, and back to normal.
Dave2582 said:
I said to run a RUU. It stands for Rom Utility Update. This is an executable program that you can run from the PC to your phone. It will take an image that was made specifically for your phone and flash over what you currently have, and once it's done and you power your phone on, it should look like you just took the phone out of the box. Download the RUU that matches your phone to the PC. Be sure that you pick the right one. Run the RUU on your PC. It will instruct you what to do as far as plugging your phone to the PC, when to turn it on/off, etc.
Once the program finishes, your phone should be reset, stocked, and back to normal.
Click to expand...
Click to collapse
How do I check which version is on my phone so I do not pick the wrong one.
P1raten said:
I do not have an adapter.
Click to expand...
Click to collapse
Buy one off EBay it only cost £2
Sent from my HTC Sensation
Ok, I was able to fix so that I can moun the USB Mass Storage device in Revolutionary CWM(In HBOOT). But the setup can not find my phone.
Any tips on how to deal with this? Is there maybe a way of installing a zip from the sdcard?
Okay, so I got my phone semi running like before.
And I plugged it into my computer and choose HTC Sync.
My phone was picked up by the computer.
So I tried starting the setup. And it worked!
Great success!
P1raten said:
Okay, so I got my phone semi running like before.
And I plugged it into my computer and choose HTC Sync.
My phone was picked up by the computer.
So I tried starting the setup. And it worked!
Great success!
Click to expand...
Click to collapse
I'm glad you got it working. Just have some patience if you run into problems.
Hi, can anyone help me with this issue ive been having? So, I odined back to stock, but I cant seem to transfer any files between the phone and the pc. When I plug in the usb cable and click on mount storage, nothing appears on my pc that says "Removable Disk." So, I go into Computer and when I click on the removable disks, the Computer window becomes unresponsive and freezes. Then I have to make it force close and unplug my phone in order to get my pc working again. Basically I have no way to transfer files. I tested it on froyo as well, (axura rom) and I get the same issue, and as well on cm7. Whats going on here???!?! It works fine on JB.... I did not test on ICS because of EU bug. Any help would be appreciated! :fingers-crossed:
New Problem: I cannot seem to flash any Froyo ROM whatsoever. When I do try, it says: E: Cannot open sdcard/***(rom)***.zip (bad)
Installation Aborted. I know that bad usually means its a bad download, but I dont think thats the case this time. I have tried many different 2.2 ROMs and none have worked, including the ones that I downloaded before and worked before. Also, for some Froyo ROMS it says a bunch of other stuff and then says: "Installation Aborted." I can flash GB ROMs fine.
Okay, so now when I click on "Removable Disk K" in "Computer" it takes a while and then says the disk cannot be accessed due to I/O error? What is that supposed to mean? How do I fix the problem? I never had this problem on android 4.1. And before when I odin back to stock, I also never had this problem.
Seems like a problem with your computer. Try uninstalling your current Android drivers, then install this driver: http://forum.xda-developers.com/showthread.php?t=961956
Make sure you use a good USB cable as well.
eksasol said:
Seems like a problem with your computer. Try uninstalling your current Android drivers, then install this driver: http://forum.xda-developers.com/showthread.php?t=961956
Make sure you use a good USB cable as well.
Click to expand...
Click to collapse
hmm. I dont think its an issue with the USB cable because it works on android 4.1 (and probably 4 as well). It may be a problem with the computer, but again, it worked with 4.1... Ill try the driver suggestion for now
eksasol said:
Seems like a problem with your computer. Try uninstalling your current Android drivers, then install this driver: http://forum.xda-developers.com/showthread.php?t=961956
Make sure you use a good USB cable as well.
Click to expand...
Click to collapse
Thanks for all the help! It works perfectly now! Looks like changing the Samsung drivers did the trick! But I wonder why the old drivers only worked for JB and not anything below... Anyway, thanks so much!
Uh oh. Looks like there is a new issue now. I cant seem to flash ANY froyo ROM. Whenever I try to, it says: E: Cannot open sdcard/***(rom)***.zip (bad) Installation Aborted. For some of the others, it says some other message and again, installation aborted. I dont think its a bad download since Ive tried old froyo roms from before and they did not work properly either.
Hobbesfed said:
Uh oh. Looks like there is a new issue now. I cant seem to flash ANY froyo ROM. Whenever I try to, it says: E: Cannot open sdcard/***(rom)***.zip (bad) Installation Aborted. For some of the others, it says some other message and again, installation aborted. I dont think its a bad download since Ive tried old froyo roms from before and they did not work properly either.
Click to expand...
Click to collapse
It's not an issue, those Froyo roms use older update script format that the new version of CWM is not compatible with. The only way to flash them is to Odin the phone back to Froyo and use CWM version 2 or 3.
eksasol said:
It's not an issue, those Froyo roms use older update script format that the new version of CWM is not compatible with. The only way to flash them is to Odin the phone back to Froyo and use CWM version 2 or 3.
Click to expand...
Click to collapse
yea, I tried that already though. I odined to Axura and tried flashing. (the fishmanmod version of axura) No luck. I also tried stock. No luck. And when I am on a freshly odined stock, I have to click reinstall packages twice in stock recovery so that cwm recovery pops up (the update.zip), and its already CWM 2.x.x (or something like that. I know it starts with a 2 though. Its the green recovery.)
I am currently stuck at the recovery screen on my Galaxy Player 4.0. I see plenty of help for people stuck at download screen. I wish I was that lucky. I can't get my computer drivers to recognize the device to use Odin. I have uninstalled and re-installed the Samsung drivers from a location on this sight. Yes I have held the down button and the power button, but it just stays at the Samsung screen. When I let go eventually it simply goes to the "Android system recovery <3e>" screen. None of the blue choices on the screen do anything. About mid-screen there is some yellow lettering including # MANUAL MODE #. Also a small android next to a white triangle with a yellow exclamation point. I am sorry to post a long and most likely ignored question, but I have searched for a long time trying to find help. Any help would be much appreciated.
what where you doing to get you to this point? If flashing ANY ICS the instructions will be different from other suggestions to follow.
have you tried removing the battery then hold power and volume down then while holding then insert the battery?
Am I the only person thinking its a soft brick? Dude try this... oneclickunbrick its a jar file and a charm... give me a day and I'll post a copy here
Sent from my YP-G70 using xda premium
button/battery
daniel644 said:
what where you doing to get you to this point? If flashing ANY ICS the instructions will be different from other suggestions to follow.
have you tried removing the battery then hold power and volume down then while holding then insert the battery?
Click to expand...
Click to collapse
Tried the battery with no luck.
I was trying to get into recovery with ROM Manager. Never got past the open box that turned into a triangle.
oneclick
Evoium said:
Am I the only person thinking its a soft brick? Dude try this... oneclickunbrick its a jar file and a charm... give me a day and I'll post a copy here
Sent from my YP-G70 using xda premium
Click to expand...
Click to collapse
oneclickunbrick failed
Is adb working, normally it should be working in recovery so if you have the sdk installed just go to platforms-tools and then type adb reboot download. This should work, if not, you could try a usb JIG.
adb
ti-pich said:
Is adb working, normally it should be working in recovery so if you have the sdk installed just go to platforms-tools and then type adb reboot download. This should work, if not, you could try a usb JIG.
Click to expand...
Click to collapse
I got "device not found". I guess I will go to the hardware store today and fab a jig. "fingers crossed"
Heimdall is the only place I can get the device recognized, so I have some hope. I get a fail on the pit file and I can't figure out the sector or the needed .dll. Although with the pit file error, I don't think the other two matter until I get that squared away. Thanks for your help. At least I have some guidance to try stuff.
Theodoric47 said:
I got "device not found". I guess I will go to the hardware store today and fab a jig. "fingers crossed"
Click to expand...
Click to collapse
The Galaxy Players are surprisingly robust, so yeah get the jig made and get into download mode. From download mode you should be golden. I've completely blown up my device twice to the point where the only fix was to flash the bootloader and pit then load up the rom(don't do any of this, I'm just explaining how sturdy the Galaxy Player is). Both times were fantastic learning experiences.
download mode
SGP4isokay said:
The Galaxy Players are surprisingly robust, so yeah get the jig made and get into download mode. From download mode you should be golden. I've completely blown up my device twice to the point where the only fix was to flash the bootloader and pit then load up the rom(don't do any of this, I'm just explaining how sturdy the Galaxy Player is). Both times were fantastic learning experiences.
Click to expand...
Click to collapse
OK, got the jig working and can get the device into download mode (whoot). Now I am having trouble getting it back to operational. I use the methods shown in this thread > http://forum.xda-developers.com/showthread.php?t=1531850< . Odin goes through its paces and gives me a pass. The device reboots but will not get past the white SAMSUNG screen. Do you know of a good walk through that will show me what I am doing wrong?
Theodoric47 said:
OK, got the jig working and can get the device into download mode (whoot).
Click to expand...
Click to collapse
Grats! The jig is simply invaluable and I know you probably don't enjoy your device not being functional right now but the fact that it still powers up means that it is recoverable. Getting to Download Mode is a huge win. Anyway, you never answered what it was that put your device into a broken state so it's hard to tell what's wrong. As an example of how I get assistance from the fine people of XDA here is the thread I made when I broke my device.
Were you trying out an ICS rom?
Did you attempt to convert to EXT4?
Were you loading a backup in CWM?
The more information you can give the smart people, the better. Me? I'm not a developer and I barely know anything about android...but they helped me recover my device so anyone can do it. Just give them some information to work with.
info
SGP4isokay said:
Grats! The jig is simply invaluable and I know you probably don't enjoy your device not being functional right now but the fact that it still powers up means that it is recoverable. Getting to Download Mode is a huge win. Anyway, you never answered what it was that put your device into a broken state so it's hard to tell what's wrong. As an example of how I get assistance from the fine people of XDA here is the thread I made when I broke my device.
Were you trying out an ICS rom?
Did you attempt to convert to EXT4?
Were you loading a backup in CWM?
The more information you can give the smart people, the better. Me? I'm not a developer and I barely know anything about android...but they helped me recover my device so anyone can do it. Just give them some information to work with.
Click to expand...
Click to collapse
I was trying to install the IcyFusion ROM when I ran into difficulty. If I was attempting to convert to EXT4, I sure did not know that I was trying to do that. And I was not trying restore a CWM backup. I had unlocked and rooted the device awhile back. I had the "yp-g1cwyxaa.tar" ROM from this thread >http://forum.xda-developers.com/showthread.php?t=1512331< running fine and was enjoying the player in all its rooted glory. But because I can never leave well enough alone, I wanted to try the "IcyFusion_v2.3_GIUEKI8" ROM. To be honest I am not sure what I did wrong in the process.
I see in the instructions that I specified that I have been trying to follow that there are instructions "Special instructions for people coming from CM7". Is this the route I need to take? I have rooted several devices including my Nook Tablet, Nexus 7 and my Galaxy Nexus phone with little or no trouble. This does not include the ugly incident with my TF300T that I did brick. At least Asus put in a new motherboard and she is back in operation. Ouch, that cost me. Like I said, I can never leave well enough alone.
I hope this info helps people help me. Thanks.
Update 1
I followed your link to your thread and guess what.
This is where I am now.
-- Copying media files...
E:failed to mount /dbdata (Invalid argument)
E:copy_dbdata_media:Can't mount /dbdata
your storage not prepared yet, please use UI menu for format and reboot actions
Meida files copy failed.
# MANUAL MODE #
-- Applying Multi-CSC...
Successfully applied multi-CSC.
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/recovery_kernel_log
E:copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
Looks familiar doesn't it.
I will read what you did and see if it helps, however the way I am going I will probably be back with more questions.
Update 2
Uh-Oh. That is the recovery file and procedure I tried and ended up where I am. I think it is obvious now that I am doing something very wrong.
info part 2
please ignore
info 3
please ignore
Theodoric47 said:
I was trying to install the IcyFusion ROM when I ran into difficulty. If I was attempting to convert to EXT4, I sure did not know that I was trying to do that. And I was not trying restore a CWM backup. I had unlocked and rooted the device awhile back. I had the "yp-g1cwyxaa.tar" ROM from this thread >http://forum.xda-developers.com/showthread.php?t=1512331< running fine and was enjoying the player in all its rooted glory. But because I can never leave well enough alone, I wanted to try the "IcyFusion_v2.3_GIUEKI8" ROM. To be honest I am not sure what I did wrong in the process.
I see in the instructions that I specified that I have been trying to follow that there are instructions "Special instructions for people coming from CM7". Is this the route I need to take? I have rooted several devices including my Nook Tablet, Nexus 7 and my Galaxy Nexus phone with little or no trouble. This does not include the ugly incident with my TF300T that I did brick. At least Asus put in a new motherboard and she is back in operation. Ouch, that cost me. Like I said, I can never leave well enough alone.
I hope this info helps people help me. Thanks.
Click to expand...
Click to collapse
Icy Fusion is a piece of cake and very stable. If something got jacked up during that it was probably a dicey USB connection(as weird as that sounds). I've loaded roms from my laptop and had them fail consistently on one USB port but not on others. Plug headphones into that port? It's fine. Moving on...
I tried EXT4 out and then I loaded up another rom and screwed my device. It sounds like that could be an issue here. The way I fixed it was to flash the bootloader and pit at the same time with repartition checked(in Odin). From there could load the kernel and then rom. Voila! Back to awesome. The only problem is that is you have a pretty good chance of doing irreparable damage(literally cannot come back from, "it's now a paper weight" damage).
You're not sure what you did, so...wait for smart people to show up. If you can remember anything more about the steps you took please add that so folks are better equipped to help you.
close but not quite
SGP4isokay said:
Icy Fusion is a piece of cake and very stable. If something got jacked up during that it was probably a dicey USB connection(as weird as that sounds). I've loaded roms from my laptop and had them fail consistently on one USB port but not on others. Plug headphones into that port? It's fine. Moving on...
I tried EXT4 out and then I loaded up another rom and screwed my device. It sounds like that could be an issue here. The way I fixed it was to flash the bootloader and pit at the same time with repartition checked(in Odin). From there could load the kernel and then rom. Voila! Back to awesome. The only problem is that is you have a pretty good chance of doing irreparable damage(literally cannot come back from, "it's now a paper weight" damage).
You're not sure what you did, so...wait for smart people to show up. If you can remember anything more about the steps you took please add that so folks are better equipped to help you.
Click to expand...
Click to collapse
I used Odin to install the bootloader and pit file successfully.>YP-G1CWYXAA_Bootloader< and >Samsung Galaxy Player 4.0 U.S. 8GB.pit<.
Then I used Odin and installed the kernel >STeVEs-3.0-USA< after it reboots to recovery, I clear the cache, clear the dalvic cache and factory reset. Then I flashed the >yp-g1cwxaa< ROM. She boots up and woohoo I see the Samsung splash screen for the first time in days. However it is now in a bootloop and keeps reloading the splash screen. I tried the same process with >IcyFusion_v2.3_G1UEKI8< and just got a solid Samsung logo. While I am happy to have made this much progress, I am obviously doing something wrong. Sorry if this is long but I was told that the more the info the more the possible help.
Thanks
Theodoric47 said:
I used Odin to install the bootloader and pit file successfully.>YP-G1CWYXAA_Bootloader< and >Samsung Galaxy Player 4.0 U.S. 8GB.pit<.
Then I used Odin and installed the kernel >STeVEs-3.0-USA< after it reboots to recovery, I clear the cache, clear the dalvic cache and factory reset. Then I flashed the >yp-g1cwxaa< ROM. She boots up and woohoo I see the Samsung splash screen for the first time in days. However it is now in a bootloop and keeps reloading the splash screen. I tried the same process with >IcyFusion_v2.3_G1UEKI8< and just got a solid Samsung logo. While I am happy to have made this much progress, I am obviously doing something wrong. Sorry if this is long but I was told that the more the info the more the possible help.
Thanks
Click to expand...
Click to collapse
I think you should use terrasilent kernel instead of steves kernel as this kernel cause bootloop. I think you got it but the problem was caused by steves kernel booting recovery. That's how I bricked my player the first time. Now I always use terrasilent as the only known issue is the data wipe when you mount something in recovery. So you should redo everything using terrasilent. Hope this help.
terrasilent
ti-pich said:
I think you should use terrasilent kernel instead of steves kernel as this kernel cause bootloop. I think you got it but the problem was caused by steves kernel booting recovery. That's how I bricked my player the first time. Now I always use terrasilent as the only known issue is the data wipe when you mount something in recovery. So you should redo everything using terrasilent. Hope this help.
Click to expand...
Click to collapse
Tried the new kernel and I have the same splash screen boot loop. I guess I will try a different bootloader next. Drat so close.
UPDATE
Woot! After a few tries with different pit files and kernels she is now running IcyFusion. I have my player back. Thank you everyone for your tips, links and threads. You helped me recover my device and taught my allot about it at the same time. I only wish I could return the favors, but I think it is obvious that I am a noob at this even after a year of tinkering.
i have the same exact issue, only i was coming from ics and got stuck trying to restore efs and all that. I managed to restore efs but no matter what i flash it leads me right back to the #manual mode#. Any help will be greatly appreciated
EFS
Ayoodannyx said:
i have the same exact issue, only i was coming from ics and got stuck trying to restore efs and all that. I managed to restore efs but no matter what i flash it leads me right back to the #manual mode#. Any help will be greatly appreciated
Click to expand...
Click to collapse
I have no experience with efs at all. I used Odin to restore my device, and I am not completely satisfied with that as it is. But at least it is working. I can try to tell you what I did, but as I said I doubt I can help you with efs.
Theodoric47 said:
I have no experience with efs at all. I used Odin to restore my device, and I am not completely satisfied with that as it is. But at least it is working. I can try to tell you what I did, but as I said I doubt I can help you with efs.
Click to expand...
Click to collapse
i believe i fixed my efs because it no longer gives me errors about efs, but whenever it starts up , it goes straight to manual mode and gets stuck there
Here's what happened:
-Had Eryigit GB-Installed PA w/ mevordel's kernel 4.0Rebooted recoveryStarted weird bootloop=would go back into recovery and act like its installing something, then reboot, ad infinitum
I tried reflashing Eryigits rom from odin,
then repartitioning. Somehow it was able to boot into Eryigit's ROM once, but the capacitative buttons didnt work and I couldnt reboot into anything except for download mode or a normal samsung logo bootloop.
I tried a few more things in Odin (not blindly, mind you) and still no go.. I can get it into recovery only if I flash a bootloader in Odin and auto-reboot it, otherwise it just goes back to the bootloop.
I believe I have the same problem as in this thread
I'm trying to adb into my device, but am having trouble detecting it. It'll connect in Odin fine, but not in adb, whether in download mode or just hanging at the samsung logo.
What can I do to fix this without adb working? I'm hoping for an odin fix for it, but through the mountains of threads I've been reading I don't believe there to be.
According to the thread above ^ it needs to be repartitioned manually... I read all the threads linked to and tried adb & heimdall but no luck after like 3+ weeks ):
Can anybody give me a better explanation of whats going on or throw me some troubleshooting advice?
<3 <3 <3
bmxer4130 said:
Here's what happened:
-Had Eryigit GB-Installed PA w/ mevordel's kernel 4.0Rebooted recoveryStarted weird bootloop=would go back into recovery and act like its installing something, then reboot, ad infinitum
I tried reflashing Eryigits rom from odin,
then repartitioning. Somehow it was able to boot into Eryigit's ROM once, but the capacitative buttons didnt work and I couldnt reboot into anything except for download mode or a normal samsung logo bootloop.
I tried a few more things in Odin (not blindly, mind you) and still no go.. I can get it into recovery only if I flash a bootloader in Odin and auto-reboot it, otherwise it just goes back to the bootloop.
I believe I have the same problem as in this thread
I'm trying to adb into my device, but am having trouble detecting it. It'll connect in Odin fine, but not in adb, whether in download mode or just hanging at the samsung logo.
What can I do to fix this without adb working? I'm hoping for an odin fix for it, but through the mountains of threads I've been reading I don't believe there to be.
According to the thread above ^ it needs to be repartitioned manually... I read all the threads linked to and tried adb & heimdall but no luck after like 3+ weeks ):
Can anybody give me a better explanation of whats going on or throw me some troubleshooting advice?
<3 <3 <3
Click to expand...
Click to collapse
If you are sure of what you state, solution is from post 39 at the following adress
http://forum.xda-developers.com/showthread.php?t=1676606&page=4
But check if you have a true "memory partitioning issue" best is said when wiping cache you get many advices about what is wrong (normaly in red letters!)
good luck and welcome to our club!
lolo9393 said:
If you are sure of what you state, solution is from post 39 at the following adress
http://forum.xda-developers.com/showthread.php?t=1676606&page=4
But check if you have a true "memory partitioning issue" best is said when wiping cache you get many advices about what is wrong (normaly in red letters!)
good luck and welcome to our club!
Click to expand...
Click to collapse
Hey thanks. I already read through all that stuff ^ and am not having much luck. Is there some way I can IM you or something? PM me if so. You seem very knowledgeable about this matter
bmxer4130 said:
Hey thanks. I already read through all that stuff ^ and am not having much luck. Is there some way I can IM you or something? PM me if so. You seem very knowledgeable about this matter
Click to expand...
Click to collapse
Normally we can solve this within a thread that can help any other getting the same issue.
i am still very involved because end 2011 I got in trouble (I was expecting to have much better performance by flashing a Gnote kernel !!!!) and stayed for months reading at XDA for a save. (also good english training then)
your Pb:
did you check by wiping if you are in this situation? You should get advice that (partition from n 14 and upper can't be read) if so follow the tracks from the relevant post and tell me what goes wrong with you.
I fixed it! you will do it the same!
PS:To enter Adb you should flash FIRST a kernel (with ODIN) rj14 for int'll version or entropy for US model
lolo9393 said:
Normally we can solve this within a thread that can help any other getting the same issue.
i am still very involved because end 2011 I got in trouble (I was expecting to have much better performance by flashing a Gnote kernel !!!!) and stayed for months reading at XDA for a save. (also good english training then)
your Pb:
did you check by wiping if you are in this situation? You should get advice that (partition from n 14 and upper can't be read) if so follow the tracks from the relevant post and tell me what goes wrong with you.
I fixed it! you will do it the same!
PS:To enter Adb you should flash FIRST a kernel (with ODIN) rj14 for int'll version or entropy for US model
Click to expand...
Click to collapse
Ok so I got into recovery with entropy's kernel and wiped everything,
When I try to mount usb storage it says:
E: Unable to write to ums lunfile (No such file or directory)
Click to expand...
Click to collapse
So yeah, its the internal memory.. now if i could just get adb shell to work right
okay now I'm just trying to adb shell into it from win7 x64 and fedora 18 linux with no luck. in win7 it shows up in adb devices, but i cant connect to it, right now im thinking its because of the java sdk and problems with the fact that its a 64 bit comp. in fedora adb devices says ???????????? offline usb:2-2...
bmxer4130 said:
okay now I'm just trying to adb shell into it from win7 x64 and fedora 18 linux with no luck. in win7 it shows up in adb devices, but i cant connect to it, right now im thinking its because of the java sdk and problems with the fact that its a 64 bit comp. in fedora adb devices says ???????????? offline usb:2-2...
Click to expand...
Click to collapse
So, you were able to flash entropy's kernel (said you have a US device?) Now you can go to recovery mode and enter adb call for;" adb devices" and your will and must show up. No need to mount anything. I 've never, under win7, tryied this. so no comment.
Would you mind to give me what is said after you do a single wipe because we have to be sure your problem is really a memory partition wreck.
lolo9393 said:
So, you were able to flash entropy's kernel (said you have a US device?) Now you can go to recovery mode and enter adb call for;" adb devices" and your will and must show up. No need to mount anything. I 've never, under win7, tryied this. so no comment.
Would you mind to give me what is said after you do a single wipe because we have to be sure your problem is really a memory partition wreck.
Click to expand...
Click to collapse
Ok, I was able to adb shell and rebuild the partition table, and it was indeed messed up, and I can mount usb storage, but I still can't get it to boot into any rom, and it refuses to boot into cwm recovery unless its just rebooted from odin. in recovery in the log it has an error about libc.so, idk if that has anything to do with it though. I'm beginning to think the problem may have to do with my usb cable. I accidentally switched the stock one with a Galaxy SII one, which should be fine, but maybe not.
bmxer4130 said:
Ok so I got into recovery with entropy's kernel and wiped everything,
When I try to mount usb storage it says:
So yeah, its the internal memory.. now if i could just get adb shell to work right
Click to expand...
Click to collapse
The "mount USB storage" option is for mounting the SD card on your computer. That error is because you don't have an external SD card inserted.
Mevordel said:
The "mount USB storage" option is for mounting the SD card on your computer. That error is because you don't have an external SD card inserted.
Click to expand...
Click to collapse
hehehe, I kinda realized that after posting. Derp.
But I think it may have to do with /data & maybe other folders/files being R/O (read only..) instead of R/W, as per this thread so I am now convinced I need the bootchain for the galaxy player, but this is just a sneaking suspicion, I need to do some more digging before making a fool of myself again
bmxer4130 said:
hehehe, I kinda realized that after posting. Derp.
But I think it may have to do with /data & maybe other folders/files being R/O (read only..) instead of R/W, as per this thread so I am now convinced I need the bootchain for the galaxy player, but this is just a sneaking suspicion, I need to do some more digging before making a fool of myself again
Click to expand...
Click to collapse
Ok you have all the needed stuff and now you are trained and skilled enough. You will succeed.
Why not you to try flashing Mevordel's GB Chip 1.5 rom that is in my view the best for your device, it is light simple and fast and no need for more for what we expect from this excellent but outdated product.
lolo9393 said:
Ok you have all the needed stuff and now you are trained and skilled enough. You will succeed.
Why not you to try flashing Mevordel's GB Chip 1.5 rom that is in my view the best for your device, it is light simple and fast and no need for more for what we expect from this excellent but outdated product.
Click to expand...
Click to collapse
Yes, I tried flashing it in cwm, along with eryigit (both with entropys kernel flashed over them) and PA venturi, but it refuses to boot properly. If it is the bootchain, how can I get a dump of a working one?
And I was able to dump a lot of stuff from [adb pull */*] and can access logs and dmesg, but havent inspected them fully. Is there an easy way to read the boot log and/or setup a custom log to run preboot? I figure that wouldnt be necessary since the linux kernel does a fine job of logging itself.
And yes I think I am skilled enough now, just was confused how to get to the adb shell, but I'm fairly well versed in linux, so the shell is relatively comfortable for me.
But if I'm able to figure it out I'm going to make a How To thread including what I've found and what you've found and posted to make it easier for nooblets in the future, maybe even make a simple shell script to repartition the US 8gb model.
I fixed it
how?
Jistropy said:
how?
Click to expand...
Click to collapse
Mainly luck hehe. But actually from the mentioned threads ^^^^^ and this nifty trick, but use caution as I have no clue how well this works for other devices, if it all. And a large part of the problem was that my battery was dead because it wasn't charging correctly when plugged into my computer; and it kept dying in Odin.
Do you have a similar problem?? I can probably help..