I was having a bunch of problems the other day and I had to re-ODIN the phone like.. 4 times and now its just randomly rebooting itself.. Should I ODIN AGAIN? I'm using the 1.6 factory.. and I'm afraid I'm going to have to keep just re loading it over and over..
View 2 Replies
I did a search on this topic and didn't find anything specific to the BH2. Has anyone else experienced this? I got the phone yesterday and the phone has already crashed twice. It's almost as if the phone has died, but I can't turn it on or anything. I have to remove the battery and then turn it on. This can't be normal. Should I head back and get a different one?
View 12 Replies View RelatedMy replaced Samsung is rebooting, sometimes 2 times a day, it will just be sitting there, I look over and it's on the samsung boot screen! WTF! Anyone else having these issues? I just had my other one replaced due to a cracked screen, only have had this about 1-2 weeks at this point.
View 6 Replies View RelatedWill putting the Behold 2 stock that BH_man is working on fix the phones problems such as random apps opening and horrible battery life?
View 7 Replies View RelatedI have never flashed a phone before. I followed instructions for ODIN. I installed the ADB drivers as indicated. (I had them installed on my windows 7 laptop previously for use with PDA net.) I shut down my phone then enter recovery mode. I then plug my phone into the computer and it never shows up as connected. I have tried this on my new IBM Thinkpad R500 (windows 7 32 bit) and on an older IBM laptop running Windows XP. I have used these same computers and phone connection before when I added MP3's to the phone.
When I let the phone boot up normally, both computers then recognize it and I can transfer files and such. I have uninstalled and reinstalled the ADB drivers multiple times, when the phone boots up normally I can use PDANet just fine so I doubt it is the connection. Is there something special I need to change in the phone settings before I shut it down and enter recovery mode? It seems like the phone isn't loading something as it boots into recovery mode. That it loads when I let it boot normally.
I encountered "zero memory" issue if I flash custom ROM over another with "onepackage" and factory reset doesn't help. Now I found a fix of this issue, and this should be done if you want to flash custom ROM over another.
Download and flash BH-MAN Warheads ROM http://www.4shared.com/file/nFe93F45/BH_MAN_WarHeads.html
Make sure you put in the components correctly. After md5 check has completed, you can flash and take a little break. Once you're in the standby screen on the phone, you can turn it off and reset the Odin and select the ROM and .ops file along with the ROM.
what would happen if i flashed the galaxy kernel on my behold 2? or any other kernel for that matter... i am sort of new to this but i know alot of things too. so is this possible?
View 3 Replies View RelatedI decided to split this off to a new thread, and hope some coders will join in and start compiling a kernel. We could then merge this with the galaxy asop effort.
Here's a bit more technical information.
Galaxy
The galaxy flash files are just yaffs images and a zimage (and of course AMSS) all tarred up. The tar format needs to be oldgnu for odin to accept it.
There's no protection at all. Thats because the glaxy is released completly security unlocked (simlocks are different, not the same thing). You can flash any image you like.
AMSS - arm ELF binary for baseband
kernel - zimage
system - standard yaffs image
recovery - standard recovery format
tar - oldgnu style standard tar file
The Galaxy also has a mtd device driver which means you can read/write its partitions with dd.
/dev/mtd
Behold 2
The behold has the same image format, yaffs, zimage and AMSS. See below for specific differences per image:
AMSS - arm ELF binary for baseband
The behold 2 also contains a partitions file. This is most likely for the AMSS, and allows the layout of the baseband to change. I'm not sure if the galaxy supports the same, but probably does.
Its safe to say you should NOT try to flash an AMSS from galaxy to the behold or vice versa.
Since the radios have the same functionality, and we don't know how to recompile and AMSS, you should never flash any new AMSS with a custom rom. Only flash AMSS with official updates.
> kernel - zimage
Just like the Galaxy this is a standard zimage. There's nothing special about it and you can modify it however you want. BUT in order for it to flash the tar file needs a special header (see tar below)
Since we can change the kernel, upgrades to newer OS versions is now possible.
> System - standard yaffs image
It appears the system image format on the behold2 is DIFFERENT to that on the galaxy. If you flash a galaxy system file onto the behold 2 you will most likely end up with a brick.
I suspect the behold 2 file has the flash address embedded inside it. Flashing the galaxy system file writes to a bad address killing the bootloader. When i say BRICK i really mean BRICK. No life in the phone at all, it wont even charge. so DONT DO IT!
In order to write a custom system to the behold 2, we will need to untar or unyaffs the modified system from the sdcard on first boot. This can easily be accomodated in the init.rc of you're modified zimage.
> Recovery - standard recovery format (protected?)
The recovery image format seems to be the same - standard android format with a ramdisk, kernel etc. However flashing it using odin doesnt work. There is some sort of protection which is preventing the image being flashed. I havnt looked thoroughly at this and someone really should. I suspect either it is signed (unlikely since the other images dont seem to be protected), or there is a write address embedded in the file, like the system file.
It would be nice to be able to flash a custom recovery, or even boot from a ramdisk, but I think this wont be simple.
> tar - oldgnu style standard tar file (with header)
Both the galaxy and behold2 have a header at the top of tar. The galaxy will flash regardless of if this header is intact or not. The behold 2 however MUST have this header intact for it to flash anything.
It seems this header contains the size, and write address of the zimage. Its possible the addresses of other images like the recovery are embedded in this too. We should look more closely at this header, especially between firmware versions to see what changes. In the mean time to replace the zimage, just hexedit your new image over the existing 'kernel' file in the tar. Remember you need to keep the size the same, so pad with zero's or just leave the remainder of the old kernel in the extra space.
Progress?
The sources that samsung provided are missing patches. This means you can't compile the behold kernel simply.
Also because the partitions are different, and the memory layout is different (compare msm/board-init files) a standard galaxy kernel will not boot.
Making the changes to get it to boot are not that dificult. It would be nice if someone who actually has a behold 2 and linux knowledge could have a look at this. It takes far to long for me to do this remotly, and frankly I just dont have that much time.
All you need to do is:
- compile the galaxy kernel (test your environment)
- replace board-init in the galaxy source with that from behold2 sources
- turn on linux console
Now boot and check if the galaxy kernel is able to see device's for each partition on the behold. If not you'll need to copy the disk/flash driver from the behold 2 sources.
Once you are able to get that far, you can merge the changes into the i7500 asop project and add a kernel switch for the behold 2. Now all galaxy 2.x progress will be directly transferable to the behold2.
You will need to make a change to the init.rc to mount the drives and unyaffs the modified system.img the first time it boots. Again a simple change.
Forgot to mention HOW to flash a kernel.
1) Take the stock behold 2 PDA tar file.
2) Use jzip (must be jzip on windows, winzip etc wont work) to remove ALL files except the kernel.
3) Extract the kernel file for reference (leave it in the tar too)
3) Download HexWorkshop or similar Hex utility.
4) Use Hex Workshop compare function to compare 'kernel' and the tar. It will highlight the kernel in the tar file
5) Open new kernel in Hexworkshop. Select all and Copy
6) Highlight the same number of bytes in the tar file and paste over the original kernel
7) Flash with Odin (JUST this tar) as PDA, and of course selecting the behold ops file.
First of all, salute to BH_MAN for offering so much joy to BHII users.
My questions is how to back up my apps. Everytime I flash a new ROM, all my installed apps and settings are wiped away. If there a way to back them up and restore them after flashing?
Since updating to 2.1 I have been experiencing random reboots - recently 3 in the space of a few hours. I think I have traced the culprit. The reboots seem to have stopped since uninstalling Newsrob. A quick Google on random reboots Newsrob reveals reports of similar problems on HTC sense phones which the author believes to be due to bug in sense. Just reporting it here to prevent others tearing their hair out as I was and blaming 2.1 for being buggy.
View 1 Replies View RelatedI have a Hero that will randomly restart itself.
Maybe once a week, maybe daily, maybe not for two weeks.
No correlation between Apps that I can see, and the service provider (Inland Cellular) hasn't heard of this problem yet.
Has anyone else seen this on a Hero?
I get about 4+ a day almost always when its just sitting on my desk, and usually not being charged.
I live in an area with only 1 bar reception from anywhere between -94 to -100.
I'm curious to see how many of you out there are experiencing the same problem.
Received the Incredible today. When I was setting it up the phone it rebooted a couple of times that seemed random to me, but I thought maybe that was part of the setup process. After using for several hours the phone continues to reboot randomly. As an example: I was waiting on a video to load form youtube and the screen went blank and went into reboot. Once I pressed the power key to bring the phone back from sleep mode and it went to what looked like an OS screen with three or four choices to reboot or shutdown the phone. As a side note, the battery was fully charged before I went through setup. Not sure what's going on here.
View 49 Replies View RelatedAnyone else have their phone doing random reboots? I've had two in the last two days, both while the phone is out, not touching anything, on my desk...
View 24 Replies View RelatedI know it's an app, but can't figure out which one. Phone has been acting a little funny since I started running juice defender, I hate to say it, but JD might have to go. Anyone been able to trace this to an app?
View 7 Replies View RelatedNow "Flashing Take5 For Complete Morons". Here's what I wrote after succeeding with Take5:You do NOT need root access to flash Take5 or 1.6 stock. Odin does it all. So here's some more detail about how I finally got it done (thanks to everyone helping):
1. Download http://www.junefabrics.com/bin2/SamsungUsbBehold.zip and unzip the files, then run the "Setup.exe" file. Your phone does NOT need to be connected to the computer to install this driver.
2. Download Odin at http://www.4shared.com/file/nFe93F45/BH_MAN_WarHeads.html. This file includes other files but you need ONLY the "Odin Multi Downloader v4.03.exe" file (there may be another download location for it). So unzip this folder and put Odin somewhere on your PC so it's handy. Don't need to open it yet, though.
3. Download Take5 from http://www.4shared.com/file/h6HvytYX/BH_MAN_Take5.html. Unzip this folder that contains two files: "Behold2_partition.ops" and "BH_MAN_Take5.tar.md5".
4. Open "Odin Multi Downloader v4.03.exe" and then:
a. Click the "OPS" button and select the "Behold2_partition.ops" file
b. Click the "PDA" button and select the "BH_MAN_Take5.tar.md5" file (you may get a message saying "Image Image Type" but you can ignore it)
5. While your phone is still not connected to the computer, turn the phone off. Then you need to get into DOWNLOAD MODE. To do this, hold down (in order, and you KEEP HOLDING THEM) Volume Down, Center D-Pad Button (the round one), and then End Call. Remember: KEEP HOLDING THEM ALL DOWN THE ENTIRE TIME. The phone will turn on, and should say that it's in Download Mode (psz clarified this). It will take several seconds. Don't let go of any of the three buttons until you see "download mode".
6. Now that the phone is in download mode, connect it to the computer's USB port. When I did this, Windows asked me if I wanted to install drivers, so I said yes and let it do it's thing.
7. In the Message box in the bottom-left corner of Odin, it will say something about your phone being connected. Now you click the Start button in Odin. Wait maybe a few minutes and your phone will reboot and turn on with Take5 running.
8. Unplug phone from USB and enjoy.
Tonight I showed my wife, who has a Droid Eris like me, that the icon in her notification panel was telling her there were updates available for some of her apps. Turns out she hasn't updated any of them so she updated them all at once. Her phone starts lagging quite a bit and reboots itself spontaneously... just goes to a black screen and then restarts and boots back up. Once I realized what was happening I canceled the updates that hadn't yet downloaded and started Taskiller to get rid of all the programs running. Now her phone won't stop rebooting every 5 minutes or so. I did a hard reset by taking the battery out for a minute... does anyone have any suggestions? Her phone's been fine until tonight.
View 16 Replies View RelatedI'm having a very frustrating problem with my phone. I've been noticing a large number of random reboots lately. It primarily happens while I'm listing to music through my bluetooth headphones or my car stereo (connected via bluetooth). When the phone restarts it can't start the bluetooth and I get a force close of a system process. I have to pull the battery and cold boot it to get bluetooth back. Bad hardware?
View 1 Replies View RelatedMy Cliq will just reboot at random times. It started doing this after the OTA update. It won't be a full reboot, either. It'll stop at the T-Mobile "Stick Together" screen, which requires me to do a battery pull. I was hoping battery pulls were a thing of the past for me after giving up BB's.
View 6 Replies View RelatedI am getting frustrated with all the re-boots on my Droid. They don't seem to be related to any running service, unless it is a background service. 98% of the time the phone reboots, it is "asleep" in my pocket. I will hear the notification chime, pull the phone out, and see the droid eye. suxxor, booted again! This happens about twice a day now. Before the 2.1 OTA it was about once a day. When the phone was new, it was about once every other day. Phone was rooted, but not rom'ed before OTA. I have not re-rooted after OTA. I have not wiped (ever), but am about ready to try. Recently added Helix as my home, but had the re-boots before helix.
View 9 Replies View RelatedI have the 2.1 VillainROM and every now and again it will reboot or fc qpps. How to stop this or should try a different ROM?
View 6 Replies View RelatedIdk what else i can do. i started out on rooted 2.1. At first it was complete fine up until a few weeks ago. Once it started i decided to flash a barebones rooted 2.2 ROM over and i figured it would get rid of the issue. That didn't help it either. So i moved to a more well known ROM thinking maybe it will fix it so i flashed over skyraider 3.3 with sense and its still doing it. This happens like 3 times a day and sometimes it will get caught in a boot loop where it restarts before its even completely loaded. So i have to pull the battery for like 10 min. What else can i do? its soooo annoying
View 2 Replies View Relatedmy Lenovo A1 tablet has been really acting up lately due to a failed flash of the newest version of Cyanogenmod 7. After the failed flash, I flashed the ramdisk needed for my device which is called, "stock-at-ramdisk-2643.zip" then i restored the backup as the directions said. Now my wireless either says, "error" or it doesn't scan for networks nearby. Also I'm getting random reboots pretty much ever 1-2 minutes. I'm pretty sure i ran through the instructions correctly.
View 1 Replies View RelatedSo I've had my Behold 2 for about 2 months now, and I've tried several different ROMs, but all of them have this same problem, apps always disappear after a reboot. Things such as google maps, navigation, places, springpad, dropbox, astrid tasks, handcent sms, even the android market sometimes is completely gone, not even in the apps list from settings. It only shows a white box with the green android, and when opened, it just says app not installed. If I reboot/pull battery some of the apps mix n' match for which ones to appear and not. After one reboot, dropbox will be gone, while on another springpad will be gone but dropbox is back.
So it's never the same. I'm currently using BHMAN's latest take5 ROM, and I've tried 1.6 no twiz, microhaxo's OTA 1.6 tweaked as well as bearsfan's all having similar results. Now when I first flashed a custom ROM, I used the unlockr's guide, and followed the rooting instructions there. Could it be that the rooted ROMs are interfering somehow with the already rooted phone? Is it possible to unroot the phone and flash back to stock 1.5 or 1.6? Then I would try flashing to one the latest ROMs.
I got droid x in launch. I have had three reboots and one freeze. Is this okay shoukd I worry. Or is this okay and fine.
View 10 Replies View RelatedI get random reboots occasionally. I do not think it is app related because it happens when my phone is in standby, I.E. in my pocket on table or even in Multimedia dock? Any suggestions anyone? One thing I think is suspect is Awakestay because It did not completely uninstall from my phone. Maybe it iscausing some kind of conflict. It was working fine and stopped working so I uninstalled when I went to reinstall it shows up as an installed app but it is not in my widget list and I do not have option to uninstall from market or app list.
View 2 Replies View RelatedI've noticed lately that my Droid has been rebooting without cause, most recently just now. Can anyone suggest a way to find the cause, or know of any especially-buggy apps?
View 18 Replies View RelatedMy X has already been randomly rebooting at least 3 times since yesterday last one froze the phone and i had to do a battery pull anyone else been expericeing any of this just asking cause i might got a lemon and need to exchange it
View 11 Replies View RelatedI was wondering if the droid 2 had random rebooting issues.
View 17 Replies View RelatedIs anyone else having this issue where the phone or just sense (is it still even sense?) reboots? I get this and the word "FRESH" pops up while I get the loading wheel and all of my widgets have to re-load.
It takes less than a minute (if it's just the interface and doesn't boot to the HTC screen...), but it's happened a couple of times now when I got an incoming call - and I can't answer the phone. Anyone else getting this?