Hey everybody,
I have a really strange situtation with my Motorola Milestone RTEU.
One day I wanted to flash G.O.T. 2.2.1 but I had an in-active start button. I searched thru the Internet and I found a solution to flash it. Changed the name of the file hmmm updated RSD Lite updated the drivers I ran in administrator the RSD Lite, I tried it in XP mode and I did almost everything what I found.
My problem is, that I started the flash and it went thru normally my phone is rebooted but when I checked the build number it was the same SHOLS U2 which one was before. I tried to do on another laptop, actually that is a netbook with Windows 7 starter. I didn't have to change anything, just ran RSD Lite with the original GOT sbf. My phone rebooted but still I see that the build number is the same old SHOLS U2.
What should I do? I can't access Open Recovery to flash any updates and I tried to flash vulnerable recovery...same issue...like I didn't do anything. Any tips?
2.1
And the funny thing is, I could flash 2.1 even without changing it's name and I didn't have to force flash that. After that I flashed GOT 2.2.1 and the build name changed to SHOLS again. I can't get GOT back. Just wondering why...
Related
Yesterday I saw the news that JPO is starting to spread, along with a new Kies version. So I downloaded the new Kies and installed it. Hooked up my SGS, at that time running official JM1 patch (obtained through Kies a few months ago), and hit the update button.
Kies then showed that the JPO update was supposedly available to me.
Unfortunately, during flashing, something went wrong and I ended up with an incomplete update (the screen went solid-color pale green at one point and nothing more happened after that). Repeated atempts of Recovery after that, as well as Odin ended in similar failure. It looks like I can't run updates from this computer.
I then installed Kies on a different computer and hooked up the SGS there, in Download Mode, and tried to flash JPO (downloaded from the Dev forum here) using Odin. That worked partially - on restart, I only got Recovery mode with an error message, claiming that format of the internal memory failed.
So I downloaded official JM1 and flashed that, and it works.
Now I reconnected to Kies and tried to look for the JPO update on that other computer, but I now get this message:
PDA:JM1 / PHONE:JG6 / CSC:JG7
This device's version cannot be updated.
I'd really like to get me some Froyo now - what files will I need to do this through Odin, reliably?
Froyo probably hasn't started rollout for many carriers yet. And I'm not sure exactly which carriers have begun rollout So I can't help.
did u have lagfix installed ???
Hello everybody.
I am having serious trouble with my phone and I was hoping some of you might be able to help me out.
I just bought my SGS 3 days ago. It came with android 2.1.1 eclair installed.
I had read that that version was not the best ( the first thing I saw when I opened the phone actually was an error screen, and the lag was horrible) so when I got home I decided to try and upgrade it using the official software for it (Kies).
Unfortunately Kies would simply disconnect my phone when I told it to upgrade, after which it would ask me to upgrade again >.>
So I decided to use Odin to flash one of the newer 2.2.1 versions.
I flashed a 'JS3' version with a repartition to 803 pit , but it crashed after rebooting with the dbdata error (which as I learned later was caused by not flashing a full firmware).
I flashed JPU after which worked great. It was fast and responsive.
However my phone kept crashing. Whether on standby, using apps, or just trying to dial a number, it would freeze, start vibrating, and sometime reset, other times just stay frozen until I force shut down it from the power button.
I flashed JS5 afterwards, with full cache clearing, factory reset etc. Still crashed.
Then I tried flashing Darky's 9.2 Ressurection. Loved it but I couldn't even set up my google account because it crashed constantly.
Then I went back to what I believe is the current official version for my location and carrier (Vodafone Romania), JP9 .
After flashing it didn't crash, but after a while (one night), it started crashing like crazy, even wound up with weird gray lines and a freeze in the morning.
I was hoping someone here might know what is wrong with it. I already sent it back to be serviced but I am thinking maybe I broke it somehow and would like to know how so I don't do it again.
The phone is network locked, which I later learned is usually a bad thing for flashing, unfortunately I didn't know about that when I started.
well first of you want to remove the network lock so try these:
http://forum.xda-developers.com/showthread.php?t=761045
http://forum.xda-developers.com/showthread.php?t=913681
next step is to register on www.samfirmware.com (its free) and here is where you will get all the latest official firmwares from samsung..
what you want to do is download (XWJS5) with all 3 files and PIT and flash that through odin with RE-PARTITION..
Before you do that, put your phone into recovery mode (volume up + Home button + Power button ) and do a factory reset / wipe cache ect...
so when you have done that and flashed the new firmware. let me know what the outcome is..
another thing.. ALWAYS MAKE SURE KIES IS CLOSED.... EVEN IN THE ICON TRAY... AND MAKE SURE DRIVERS ARE UP TO DATE.
other than that you shouldn't have any problems
hi, thanks for the advice.
I already did most of that however. I did a factory reset numerous times, and I also did a full repartition flash more than once, to no avail.
I am waiting to get it back from warranty service now but I am wondering what went wrong.
Was it broken when I bought it or did I damage it somehow by trying to flash it while network locked ?
flashing with network lock wouldnt make everything force close. the worst thing that could happen when flashing with network lock is not picking up a signal and possible IMEI corruption.
i think you may have just flashed the wrong ROM, it happens to us all, but the more you do it the more experienced you become and you soon learn methods to restore things..
dont worry too much it will be fine when it comes back from samsung, just be sure to read up properly if you have any doubts.. or ask a question first you will get a reply quicker than you can Unbrick your phone..
My phone seems to hate the 803 pit file. Lots of force closes when I used it. Try using 512, see if that works any better.
Hey guys I been having a huge problem with my Samsung Galaxy S 1900M its currently locked with Bell/Virgin Canada. I bought it off of some 2nd hand company. The phone was sold as is saying that it was unable to connect to the computer, (computer does not recognize it at ALL). I bought the phone amusing it was a ROM load problem. It came to me rooted and in almost perfect condition so I was quite happy with my purchase considering I paid $180 USD ($170 CAD). I tried connecting to the computer using the USB that came with the phone, and as stated it does not recognize it at all on ANY Windows/Linux base PCs. I also have another Samsung USB cable that I know works, I tired that as well...no success.
So I am assuming who ever loaded a ROM did not know what they were doing.So I have been searching all over the internet/google, XDA forums and Q&A and everyone point to loading a new kernal....BUT here is where it gets weird. Who ever had this phone previous did not flash a new kernal when updating and put the 3e recovery on the phone, WHICH MEANS I cannot flash any new: Kernals, OR ROMS using the CWM, which btw I am pretty sure isn't working properly because it goes into the base recovery mode with limited options, ex. reboot, sdcard update.zip, wipe cashe, format sdcard...nothing else.
Which brings us back to the original problem, I can not connect to the PC for ODIN to work its magic on the kernal....Please help....
Here is the current load,
Firmware Version: 2.2
Baseband: 19000UGJK4
Kernal Version: 2.6.32.9 shout.leeSEP-09 #1 ( I have never heard of this?)
Build: FROYO.UGJK4
may be a issue with drivers dont quote me though, i had to update drivers after flashing and updateing my galaxy s, as i had simular issue with odin, by not reconize, do you mean windows wont even detect the phone added, or is it connect and nothing? does the phone charge when connected to the pc ?
The phone does charge, but even with the Samsun Keis app, and having the proper Sumsung drivers it still wont even detect the phone. I even went to Device Manager and searched for new hardware/device. I also tried putting it into download mode, and connecting Odin. Windows still wont even detect it. I think its a problem with the kernal....for both issues...
Fixed the problem, hope this helps for others.
Just following up on this as I figured out what to do on my own in case anyone else has this issue.
It was quite simple actually, the kernal was faulty, and so was the ROM that was loaded just as I anticipated
1st:The person that previously owned the phone loaded FROYO custom build that was taken from a leaked version prior to the official release and had no USB support, therefore being unable to connect to the computer.
2nd: The kernal was a custom build and had a 3e recovery built into it and was not able to load any un-verified files(unofficial ROMS, firmwares, updates etc.), therefore I was not able to load a new ROM to fix the first problem, stated above, and visa versa.
I found a program on the market place called "kernal manager", I downloaded the PRO version by searching Google on the computer for the .apk file, I then copied the .apk file onto my external 2 GB SD card and ran the .apk file through the phone. I then opened "kernal manger pro" and opened the menu button, then hit search for kernals. A list of different models of phones came up, I browsed down to my handset maodel (Samsung Galaxy s 19000), press on it, and got a list of kernals. I took each top rated and downloaded kernal listed, did a little research on the internet and found one of them to be suitable. I then went back to the phone chose that kernal through "kernal manager", it asked me to flash then reboot, I hit yes, it then begun the process, and when finished reboot on its own. I then reboot into recovery again after the kernal had loaded and the first reboot and found that the new kernal had succsefully been flashed. I then was able to go about as I please. I uploaded a cm7.zip file to the external sd card, put it in the phone, boot to recovery browsed to the file, and ran it having complete success.
I am now happily running Cyanogen 7. Hope this helps anyone that needs it. Any questions just ask
I started having issues with the MIUI rom and wanted to get a different ROM. The devices menu shows for the captivate device that there is no driver. I have tried to let windows find a driver but it cannot find one and I tried installing one manually but still has the same error. My only idea is that the device name changed so it cannot find a driver. Can someone tell me what their machine says the device name is for your samsung captivate? Or if I am wrong can anyone help me out?
MIUI version: MIUI-109160
Kernal: [email protected]#1
Thank you
Have you tried a Heimdall one-click (like the one in my signature)? That should detect your phone as part of the installation process, and let you flash back to stock (with CWM) as well.
Edit: okay I got it to work. Thanks I am now back to the default. If i have any more issues I will come back. Thank you
Yeah even tho it got back to the stock it can't read the sim card now. suggestions?
Hello,
I have a stock Bell HTC Raider, locked, unrooted, basically never touched, all original software and state. It is updated to latest OTA software.
I'm trying to wipe it and reinstall the stock rom because it is starting to act funny and I want to start from scratch.
I am trying to flash the version 3.5 bell RUU, and it will see that I have version 3.38 on phone, and RUU is same version 3.38, and when I click "next" it will go to screen which says "sending" and it will just hang there. The "sending" progress bar just keep incrementing continuously but nothing else happens. the phone is on the white HTC logo.
I gave up after 2 hours of this. Tried several times. Phone info is not wiped, same old ROM is still on it with my apps and everything.
I also tried to put the PH39.zip file for rogers on the card (can't find one for bell) and it gives me a "wrong CID, flash fail" error.
I'm running windows 7, I am admin on the PC, I also ran the RUU as administrator.
I installed latest HTC Synch, and I can open the phone as a USB drive and copy data to it, but I don't see it in HTC synch.
HTC synch does automatically launch when I plug phone in, so it sees something, but when I go to the "home" tab it says that no device is connected. I did select "htc synch" as the connection method on phone. USB debug mode is on.
Any ideas of what could be wrong?
Is there any working link for the PH39 zip file for bell?
each umaxces
Update:
in the mean time I bit the bullet and unlocked the bootloader (still S-ON), put WCX recovery on and flashed the cyanogenmod 11 *kitkat) rom.
That had the low call volume problem, so I flashed Holic's 1.3 ROM (back to ICS) which so far works perfectly.
So I am in fact able to flash other roms in recovery but I can't get back to stock using the Bell RUU.
If I ever want to return to stock, what do I do?
tudorvictor said:
Update:
in the mean time I bit the bullet and unlocked the bootloader (still S-ON), put WCX recovery on and flashed the cyanogenmod 11 *kitkat) rom.
That had the low call volume problem, so I flashed Holic's 1.3 ROM (back to ICS) which so far works perfectly.
So I am in fact able to flash other roms in recovery but I can't get back to stock using the Bell RUU.
If I ever want to return to stock, what do I do?
Click to expand...
Click to collapse
Might want to check out http://forum.xda-developers.com/showthread.php?t=2013122 which explains:
How to run the RUU
1: Make sure your bootloader is re-locked and by using the fastboot oem lock code
2: Plug in your device and make sure you have the drivers installed ( or HTC Sync )
3: Run the RUU specific to your carrier and wait for it to load ( could take up to 20 min depending on your PC )
4: A box should popup on your screen and a progress bar will be shown ( wait )
5: Once it's done loading follow the steps to return to stock.
6: You are now unrooted
Been years since I did that. KitKat low volume? Are you running the latest nightly? http://www.chronic-buildbox.com/nightly/holiday/ Best rom I've tried and I've tried em all. (Can't wait to see what pacman can add to what Albinoman is doing an awesome job with)
I managed to return to stock using the RUU without problems.
I didn't do anything different this time, it's just that I wasn't trying to flash the stock ROM while already on the stock ROM.
Maybe that doesn't work?
you can close this thread now. thanks.