I tried doing my first rom install, everything went well, but when ii nstalled the new rom it didn't recognize my sim, and when i tried to fix it, it turned my phone off and keeps saying in top right corner "only official binaries are to be flashed" and i can't do anything using odin, everything fails. an help?
Related
Hi,
I had my G2 rooted ages ago and was using custom ROMS right up until yesterday. I'm due to get a Desire HD in the post today so was resetting phone to give my girlfriend and thought it easier if she had the Stock ROM.
So I put that back on using the official updater, back to 1.5... However I can't update it to Eclair. Whenever it downloads the update and tries to install it I get a black screen with a phone and a triangle with an exclamation mark
I've most definitely updated with the OTA before... could it be because it was once rooted?
Try going to your country's HTC homepage and download the official 2.1 RUU from there.
If it isn't there, maybe you can find it here http://www.shipped-roms.com/shipped/Hero/
That is where I found my Hong Kong ruu.
Then, also install HTC Sync to make sure your computer will recognize your phone.
Then run the RUU with your phone connected to your computer via USB.
I recently did this and it worked perfectly.
Good luck.
http://www.htc.com/uk/supportdownloadlist.aspx?p_id=283&act=sd&cat=all
I can't seem to find the 2.1 files... There's an option for HTC Sync 2 if you've already got Eclair...
I have found Stock 2.1 ROM on here which could be of use but now I can't seem to install the recovery image so I can install them...
Well I have managed to root it once again as nothing else seemed to work... I then tried to use ROM Manager to install a Custom Recovery like I did before but all I get once it has flashed is the exclamation mark...
I recall last time I used this I ended up using an alternative one it offers at the bottom (RA 1.7?) but this hasn't improved the situation either...
Any thoughts?
I have the AT&T SGS2. I had installed a few custom software a few months ago, but then I installed a stock 2.3.4 for the AT&T phone. The custom binary count is 1 on the recovery screen.
To upgrade to the official ICS from AT&T, I installed the latest KIES. It successfully detects the firmware update for the device. KIES starts installing and everything goes fine until almost very end. At 91%, installation fails giving the error message something like "Unexpected error. Firmware upgrade encountered an issue. please select recovery mode in kies & try again". I tried several times and same thing happens again. I also tried downloading the stock ICS and install it via ODIN, but same thing happened. It failed at the very end.
What could be happening here? Any advice? Can it be anything to do with the custom binary count? Thanks in advance...
Not sure what might be intefering with kies or Odin. Where did you get the tar that you flashed that failed?
You might try again, with the UCLE5 Stock ICS plus Root tar from the Development forum.
Hello everyone.
I am having a big issue installing custom ROMs nowadays. Previously it was no deal, but now, whatever ROM I get, it is stuck att the Edify crap in the beginning of installation. Tried using the Amend (or whatever) to Edify on the update script in com -> android or something like that. It does everything fine, but rezipped the archive after saving and tried to flash it. This time I got some message from the tool and it ended with an "Update complete" message. Started the phone. NO change.
So I tried opening just the zip of the rom and yet again, seemed to do some stuff. Transfer to my SD card and everything goes well on installation. Getting the regular "Update complete" message. Restart phone, no change.
Thats how far I got, tried flashing the recovery thinking the recovery obviously might be outdated. No luck, at all.
Might add that the reason I want to use a custom ROM is since the one im using now (Mokee Epic) does not support USB. My computer doesn't recognize it. This way I can get it to work in Sony Ericsson PC Companion and reinstall the stock ROM.
So, im sorry for a big read, but I am in a very bad mood now.
EDIT: Might add that I tried out FeraVolt's ROM which installed fine. The problem was that when I started it and entered my PIN, the screen would go black. I guess this is a result of me NOT flashing with their custom FeraKernel. But when I tried to flash the kernel with FeraVolt's GB 5.3 kernel released earlier this month, It gave me the Edify error.
Sincerily,
Earlier today i flashed a stock rom, locked my bootloader, and flashed the stock AT&T recovery in an attempt to recieve the 4.2.2 update. As i was checking for the update, a 13.8 mb update was downloaded, however when it tried to install, a red exclamation point came up. So i restarted and tried it again and no luck. So then i decided to run the RUU and start fresh and try again. However this time, the update is not being recieved. Any ideas or hints that you guys have?
Dash_Skeezy said:
Earlier today i flashed a stock rom, locked my bootloader, and flashed the stock AT&T recovery in an attempt to recieve the 4.2.2 update. As i was checking for the update, a 13.8 mb update was downloaded, however when it tried to install, a red exclamation point came up. So i restarted and tried it again and no luck. So then i decided to run the RUU and start fresh and try again. However this time, the update is not being recieved. Any ideas or hints that you guys have?
Click to expand...
Click to collapse
Try to uncheck the automatic time in settings and put the tine 24 hour ahead. And try to get the update. Some claim it works this way.
Sent from my HTC One X+ using Tapatalk
Same for me
Having exactly the same problem. Made an account because i could not find an answer anywhere else. Just tried the time strategy and it did not work.
I do have the downloaded update file. Is there a way to install it through ADB and pushing, as can be done with nexus devices?
Thanks
So it has been a VERY, VERY, long time since I attempted to root a device. I admit, that I completely forgot most of what I knew from back in the day rooting like the Motorola OG Droid. Here's the deal. I tried rooting a USC XT1526 and I had no idea what I was doing. I followed the steps through and managed to install TWRP and SU. So I assume I got full root. Well The issue started after I got an UPDATE AVAILABLE message and tried to go through with the OTA Update. When it got to the point of installing the OTA Update, my device turned off like normal but instead of updating, it booted into TWRP recovery. It didn't update at all and when I booted my phone normally, it kept trying to update so my phone turn off (loop) every time it tried to install the update. I did a factory reset and it stopped rebooting. I later tried to flash back to fully stock but I believe I might have downloaded the wrong file because I now have a device with no WiFi. Can someone please help me.