Related
I've been flashing different roms for awhile, and decided to go from OpenEclair to one of the "new" ones that requires the new SPL and radio. Went fine. No problem. Used the new rom for about a week, but really got screwed by a massive bug I found in it today, so I wanted to go back to my OE nandroid backup.
I went to reflash to my original SPL. It was a ZIP, so I treated it like a ROM and used AmonRa's recovery to flash it. Said it went fine. Rebooted, expecting to get back into fastboot and flash my radio.
I can't get into fastboot. All it does is show Rogers then HTC Magic in a boot loop. ADB devices shows nothing, fastboot devices shows nothing. Back and Power doesn't work. Home back and power doesn't work. Vol down doesn't work.
Am I as bricked as I think I am?
Yes, it sounds bricked. The proper method to go from 6.x --> 3.x radios and matching SPL is to use fastboot. You have to flash radio and SPLs in matching pairs, you can only use the update.zip format for SPL when it already matches your radio (ie. 1.33.2005 ---> 1.33.2010 w/ the 3.22.20.17 radio).
I believe you should normally flash radios first as well. If you don't get it fixed id like to buy it, need parts. Anyways, most the time when you can't get into fastboot or anything else, it is bricked. Best bet is to get warranty if you still have it. Unfortunately the new phones won't be rootable yet
its best to follow guides when downgrading/upgrading spl/radio (cursordroids for example) when not knowing completely what your doing.. sorry my friend.. sounds like your phone is now a boat anchor
i flashed a 1.33.2010 SPL with a 3.?? radio and now all i get is the logo screen no fast boot, i can enter debug mode (action button) but nothing else sounds like its bricked, but hey its been fun
to be honest i was in this situation last week after leaving my phone off for a hour fastboot was working
oh this is sounding more promising, see what happens when i get home, i see there have been a few people about that have been in the same situation and got out of it so fingers crossed
unfortunantly none of the above worked, wow after 10 years of flashing **** i finally killed something !!.... mind you i still have to make up the serial cable this weekend and see if i can fix it like that
Oh well, you guys should know better ... radio/spl/recovery upgrade/downgrade is a child play, if you do it with fastboot and in the correct order (radio - spl - recovery).
I just hope you can get your Magic back to life.
yeah i was a little distracted at the time, never mind, im going to boot into the radio bootloader and see if i can fix it this weekend, fingers crossed
ruimoura said:
Oh well, you guys should know better ... radio/spl/recovery upgrade/downgrade is a child play, if you do it with fastboot and in the correct order (radio - spl - recovery).
I just hope you can get your Magic back to life.
Click to expand...
Click to collapse
i have flashed not in that order and never bricked and also i have flash different things like radios in different orders and no brick
Just a (long) update on trying to get the phone repaired...
First thanks to bcrook, KAwAtA and digitaljeff for the prompt replies at confirming my screw up.
Ruimoura, why even post? Nothing helpful, and not even commiserating. "Oh well, you guys should know better ...". I hope someone is there when you make a mistake to rub it in.
Anyway...
This was a Rogers Magic used in the states on AT&T.
Heres what happened if anyone is interested:
I searched the forums and tried every trick I could find, including the gold card method; no luck. To be honest, I'm not sure I did the gold card right, but I tried my best. I even looked into the jtag idea, but it seems like more work then its worth to me, and no one seems to have been successful with it yet.
I then called HTC to find out what a repair would cost. HTC said they don't have that phone in their parts list and can't service it because it is a Rogers phone and they don't work with Rogers. They told me I would have to call Rogers for service.
Called Rogers and explained the situation (carefully; blaming the 911 update ). Rogers lectured me on how dare I take their phone off their network, and that they have no interest in helping me at all and "contacting HTC is easy. Whats wrong with you?". I explained that I contacted HTC and they said to contact Rogers. They said (after some fighting) call this number and then gave me the same number HTC has on their website.
Called HTC again and explained the situation. After checking their parts database, the person I was talking to this time confirmed what the person I previously talked to said. HTC doesn't service the Rogers Magic but he felt, like I, that was kinda crazy and called the repair location directly to confirm. After a bit of time on hold, he came back and said that Rogers phones are serviced through a place called FutureTel in canada, and gave me their contact number.
I called FutureTel and it was a very short conversation. "What store are you calling from?" I Explained I wasn't calling from a store and why I was calling. "We only work with Rogers directly. We won't support you." and they hung up.
I have to say, both times I called HTC the people I talked to were incredibly polite and honestly seemed like they wanted to help. Rogers and FutureTel seemed like they truly resented having to pick up the phone. Maybe its a cultural thing I'm not aware of, but it honestly seemed, from the first word, that they hated talking to me.
So, as near as I can tell, you can't even pay someone to fix a Rogers HTC Magic.
At this point I'm back suffering on my old WinMo phone and desperately hoping that the rumored March 23 release date for the Verizon Nexus One is legitimate since T-Mobile isn't really an option.
hey guys im new to the scene and trying to figure as much stuff out on my own as i can, usually i do a good job and don't need to ask for help. but i do when i have to, so the problem i am having is with a sony xperia play .
its my brothers phone and i was thinking about getting one but i want to "root" it and see whats what with it but i am trying to do so without unlocking the bootloader just incase anything goes wrong with it later so it remains under warranty. im coming from the iphone jail-breaking scene so this is a little different. but i want to give it a go. so i'm trying to root it i checked out this post
http://forum.xda-developers.com/showthread.php?t=1044765&page=1
i realize at the top of the post it says not all devices are supported because of new FW's does the FW i am on fall in this category?
i tried it with the 1.2.apk and the 1.1
im not sure why it is not working.
but i have a feeling its got something to do with the FW the phone has come with
its running 2.3.3
build number 3.0..1.A.0.145
model number r800i
kernal version 2.6.32.9-perf
i formatted the SD card before anything then after i installed gingerbreak to the phone itself. (also tried it without formatting it, i installed gingerbreak and tried to run it then and it didnt work so i rebooted formatted SD card and tried again and still nothing)
made sure the phone was set to be in USB debugging mode.
gingerbreak opens and has the options there but when i tap "root device" it just says "running exploit" ect on screen and nothing changes. on the post it says usually about 10 minutes but i read through it and one person said it worked for theirs but it took an hour and a half, but another said it took 3-5 minutes.
so i do not know what i am doing wrong. but i have a feeling its the FW it has come with out of the box but i have not been able to find out any information about it as of yet.
i have found another post saying to flash it with a UK generic FW 2.3.2 .184
but im guessing i cannot downgrade to a FW that was not on the phone from packaging. although i may be wrong but that is usually the norm with this kind of thing.
any help in getting me in the right direction is greatly appreciated, and i hope to be able to help others in the future. yes it doesn't seem like i am of much help right now seeing as i can't even get it rooted yet. but i tend to pick up on things very fast. today i am having trouble getting in to it. but soon enough i will get there thank you to anyone who read this i know it is a little long but i wanted to make sure i gave as much information as possible to make sure i haven't left out something critical if i have left out anything let me know and once again thank you for taking the time to read this post and reply (if you did reply =] )
BUMP -- ?
anyone available who can help me out at all
i know im new to the forum/site but please don't let that stop any of you. if that is stopping you
ive done as much searching as i can and i keep drawing up blanks.
On my skyrocket from AT&T I was having an issue with the battery indicator getting stuck at 100%.
I updated the phone to the latest OTA update, no root or anything on this phone, all completely stock.
After update phone info is as follows:
Model Number: SAMSUNG-SGH-I727
Android Version: 2.3.6
Baseband Version: I727UCLA3
Kernel Version: 2.6.35.11
Build Number: GINGERBREAD.UCLA3
After I did the update the battery indicator has not come back (awesome right?, not so fast.)
Now I have an issue with call quality, my best attempt at describing it is like the ear piece sounds blown out, it kind of has a vibrate when people talk, Its not just one persons phone either, its any call I get/place.
I'm not sure if I should try a factory reset, revert back to 2.3.5?, Go to AT&T for a new one.
If anyone has had this issue and knows how to fix it please post. I apologize ahead of time if this is already posted somewhere, I looked for a few hours on google and couldn't find it anywhere. Also even if you don't know how to fix it, could you please post if your having the same issue so I know I'm not alone and have some ammo if I do have to go to AT&T.
Visit AT&T Store
Of course I'm 4 days outside my 30 day trial period so I would have to get a replacement mailed to me if I can't get it to work.
Lady I spoke with there was very nice (as always) but didn't have any idea what to do (as always) and advised I try and factory reset it. What the hell, mine as well.
Also got her to tell me that if I root and custom rom it and it still dosn't work I can still RMA it. So she went against what all their documentation says so now I can do what I want
Figure ill factory reset first, if that dosn't work I'll ODIN it back to the original 2.3.5 if possible.
Ill keep updating this thread though incase anyone else has a similar issue.
albeemichael said:
Of course I'm 4 days outside my 30 day trial period so I would have to get a replacement mailed to me if I can't get it to work.
Lady I spoke with there was very nice (as always) but didn't have any idea what to do (as always) and advised I try and factory reset it. What the hell, mine as well.
Also got her to tell me that if I root and custom rom it and it still dosn't work I can still RMA it. So she went against what all their documentation says so now I can do what I want
Figure ill factory reset first, if that dosn't work I'll ODIN it back to the original 2.3.5 if possible.
Ill keep updating this thread though incase anyone else has a similar issue.
Click to expand...
Click to collapse
Haha, just because she said that doesn't mean anything. Read the contract, that trumps what some lady says. Anyways, you can flash back to stock and warranty it, so it doesn't matter what anyone says
Absolutely Right
xcrazydx said:
Haha, just because she said that doesn't mean anything. Read the contract, that trumps what some lady says. Anyways, you can flash back to stock and warranty it, so it doesn't matter what anyone says
Click to expand...
Click to collapse
As the title says you absolutely correct. Lady probably didn't have a clue lol.
I called their warranty support line and am going to drive to their wallingford exchange place.
I was talking with my father before I called and figured if I went in and said get a manager, and told him/her if I don't have a new phone in my hand in 10 minutes, your losing a customer in 10 minutes, I bet I would get my phone
Regardless I'm getting a replacement, I did try the factory reset, didn't work. Also tried downgrading the device to 2.3.5 stock, and this also did not work.
Think its hardware, the static is only on the ear piece. Speaker phone, head phones, and bluetooth do not have the issue so I think its a odd coincidence
To anyone that may have been checking on this, it seems I got a rare case, there was actually a hardware problem on my device. Just a coincidence that I noticed it right after an update, I took it to the Customer Service place AT&T has in Wallingford, CT and the lady tried to re-flash the phone (what she said was standard procedure, she HAS to with every issue.) This didn't work so she gave me a new one.
All in all, only bad part of the experience was that it happened at all. New phone is working great.
Glad tohear that you got this taken care of.
Sent from my SAMSUNG-SGH-I727 using xda premium
Hi all. My new phone was going greatish. It was a little laggy, so thought I would root it and remove some of the preinstalled junk. All went fine no problem.
I removed some of the vodafone (UK) stuff, and all was well. Some time later though, I get a message:
"Unfortunately, the process com.android.phone has stopped"
And now my phone won't find the network and message pops up every couple of seconds. I tried a factory reset, but I suspect this made it worse as I have now lost my backups from Titanium app. The phone is basically unusable as it is due to constant error message and no network.
I have tried to access the recovery menu, but i get an empty robot with "no command".
I have seen some mention of CIDs on other forums but haven't got a clue how to go about fixing it or even where to start.
Any help would be greatly appreciated as obviously the phone is absolutely brand new, and I'm very very upset about the whole thing! Not to mention the fact that I feel like an idiot!
Anyway, thanks in advance.
You deleted something that was not suppose to be deleted. Don't the stock tot file on this forum and follow the steps to Flash back to factory
http://forum.xda-developers.com/g-flex2/general/guide-lg-g-flex-2-stock-firmware-to-t3037593 follow the video and you should be up in running in no time . make sure this link support your version not sure which g flex2 Version you have.
Still no tot files available for the LG G Flex 2 (any variant). Sorry got to wait for some to become available.
Thanks for the input. I figured it would be something like that. Any idea when the files might be available? I don't mind being a guinea pig at this stage. My phone is LG H955 on Vodafone UK.
I am going to try and play dumb in Vodafone shop today and see if they'll replace it there and then (doubtful).
I suppose my other alternative is to return it to LG for Firmware Flash. Anyone know if this is possible and potential cost?
Strangely, I'm not so bothered about (temporarily) destroying my brand new phone too much, it's my sudden lack of connectivity that hurts the most.
Thanks guys
Further update; I have spoken to LG tech support / repair department, and I told them the phone had been rooted etc. (I didn't leave any identifying details!) They informed me that as the phone was now out of warranty, I should speak to their service partner SBE.
After calling SBE, they informed me that LG or their partner have no obligation to fix rooted phones, so apparently they just won't do it, even though I'm certain they could, which kind of sucks, as I was obviously willing to pay.
So it looks like I'm waiting for the TOT files. I hope they come along soon!
Lesson well and truly learned!
djjag1 said:
Further update; I have spoken to LG tech support / repair department, and I told them the phone had been rooted etc. (I didn't leave any identifying details!) They informed me that as the phone was now out of warranty, I should speak to their service partner SBE.
After calling SBE, they informed me that LG or their partner have no obligation to fix rooted phones, so apparently they just won't do it, even though I'm certain they could, which kind of sucks, as I was obviously willing to pay.
So it looks like I'm waiting for the TOT files. I hope they come along soon!
Lesson well and truly learned!
Click to expand...
Click to collapse
Stay positive. Hopefully those tot files come soon. I on the other hand what to experiment with my phone but need a tot file just in case I mess anything up.
If it's just your dialer that's acting up, have you tried a third party dialer to make phone calls?
djjag1 said:
Further update; I have spoken to LG tech support / repair department, and I told them the phone had been rooted etc. (I didn't leave any identifying details!) They informed me that as the phone was now out of warranty, I should speak to their service partner SBE.
After calling SBE, they informed me that LG or their partner have no obligation to fix rooted phones, so apparently they just won't do it, even though I'm certain they could, which kind of sucks, as I was obviously willing to pay.
So it looks like I'm waiting for the TOT files. I hope they come along soon!
Lesson well and truly learned!
Click to expand...
Click to collapse
Lets see if we can work on this.
Is it working ok, just not picking up the network?
How long exactly have you had it?
If you put what you all deleted meaning what folders they were in i could make a copy of that folder or apps you deleted and upload them on dropbox for you that might help get you going worth a shot
Be better if someone had the same variant as you i have the Sprint model.
Thanks again for input. I have hopefully managed to sort this with my provider. I was just within the 14 day cancellation period, so I have arranged for a brand new handset. I know its a little bit naughty but if the phone wasnt so laggy to begin with, I would never have rooted it.
I'm guessing it makes no difference to them as the phone will go back to lg for wipe and reflash as a matter of course once returned.
Thanks folks, I will remain on this forum and hopefully not do anything quite so stupid again!
Unfortunately this is my last day with this device . Great phone but i was wrong the 810 processor is dangerously hot to the point it felt like my pockets were on fire. This my second g flex2 and I'm moving on to something more reliable. Love this phone but this heat issue i can't risk. After 14 days i would be stuck with this phone and i can't take the risk of hoping of getting a device that function fine bye everyone.
:victory::victory::victory:
Today, I've gotten myself in a similar pickle after applying noob root.. Data OK but no phonecalls and no txts. When I tried to make a call, the thing said the phone is not activated. Sprint tech supp was of course no help, so after some digging I found this: ##72786#
Factory reset, keep the data (and all apps).
That solved it.
I guess I'm old enough to know that being lazy doesn't pay.
Stank0 said:
Today, I've gotten myself in a similar pickle after applying noob root.. Data OK but no phonecalls and no txts. When I tried to make a call, the thing said the phone is not activated. Sprint tech supp was of course no help, so after some digging I found this: ##72786#
Factory reset, keep the data (and all apps).
That solved it.
I guess I'm old enough to know that being lazy doesn't pay.
Click to expand...
Click to collapse
so you had root, and while doing this factory reset you were able to go back to full stock unrooted rom? if so, were you able to install updates? i too have a sprint version and i was rooted and tried installing an update but failed, i then unrooted my phone tried the update again and still got an error. im just wondering if this method would actually help people who have the same problem as i do.
gothikzoul said:
so you had root, and while doing this factory reset you were able to go back to full stock unrooted rom? if so, were you able to install updates? i too have a sprint version and i was rooted and tried installing an update but failed, i then unrooted my phone tried the update again and still got an error. im just wondering if this method would actually help people who have the same problem as i do.
Click to expand...
Click to collapse
Unfortunately, that wasn't the case.
I tried every possible way to install this damn update. Rooted, unrooted, factory reset 4 times, tried to install from the system update in settings, from recovery (which is, at least for me, very tricky to get into) all efforts errored out.
I posted a link to the update.zip in other thread.
So then I gave up and used this noob root which killed voice calls and text.
This code I posted says it does a factory reset but is resetting something else than other factory resets because almost all my settings, passwords and all apps remained intact.. Then I used the original root method and everything works like it's supposed to.
I guess we'll have to wait until someone finally starts developing for our phone.
So after a few days I just received a notification for the update for the third time. Any suggestions as to how I should proceed? I've tried it while being rooted and failed, also tried it the second time after unrooting and failed too. Also, what is the default location where the update is downloaded to, so I can back it up.
So far nothing has worked. The update should be in the cache folder. There is also a link to download the update that someone posted in another thread here about the update.
FYI - I forced the update through recovery over root and bricked my phone. Like all the way bricked. I can get to recovery and download mode, but no fastboot even. Luckily I was within my 14 days and there is no way to tell it is rooted... because it doesn't even get that far, so I got a replacement. My sincere advice would be to wait to root until we have custom recovery and stock firmware available, and if you have root now, wait to update until a dev can release a "root safe" version.
I'm not an expert but I'm not new either. I got the original Evo on launch day and have done all kinds of dumb stuff to every phone since. This is the first time I haven't been able to recover it.
austontatious said:
FYI - I forced the update through recovery over root and bricked my phone. Like all the way bricked. I can get to recovery and download mode, but no fastboot even. Luckily I was within my 14 days and there is no way to tell it is rooted... because it doesn't even get that far, so I got a replacement. My sincere advice would be to wait to root until we have custom recovery and stock firmware available, and if you have root now, wait to update until a dev can release a "root safe" version.
I'm not an expert but I'm not new either. I got the original Evo on launch day and have done all kinds of dumb stuff to every phone since. This is the first time I haven't been able to recover it.
Click to expand...
Click to collapse
=( *hug. That sucks man, thankfully you were able to get it replaced. *pfew I dodged a bullet there. I was actually thinking about doing the same thing getting home from work. Yeah its best we don't mess with the phone any longer those that have root at the moment. Until custom recovery and stock rom is out like he says.
Wow. How did you manage to "force" the update through recovery? I tried it through recovery but it would error out. (Error 7)
I will tell you, as a cautionary tale.
The error when you flash from recovery references a specific file that is incompatible with the update. I used root explorer to investigate further and found that the root script had overwritten a system file. The original was saved as "original" so I deleted the file causing the error and renamed the original one. After that, the update went through and I thought I was golden... Only now nothing else works.
Hey,
I traded a bunch of old laptop parts and got this phone in exchange: an HTC One S. I think some call it a Ville. Nice looking phone.
Anyways, when I made the trade, I didn't notice that there was no icon in the status bar to show it was receiving any kind of cell signal. Really bright and sunny day washed the screen out. Jumped in my car, where it was a little darker, and discovered that the phone had a custom ROM (Or is it RUU?) installed. No biggie. Actually, it ran really smooth and kinda looked cool. It was a Cyanogenmod Mod, called Dark Jelly S edition. My thought was that I could use it as a backup phone, so I went to a local place to get an unlock to use on my network (it was, supposedly, on Fido. I'm on Koodo).
So, I tried to get the IMEI # off of it. No dice. Tried *#06# and I got a blank line. Went into settings, and settings crashed. When I got to the place I get my unlocking done, the guy at the desk knew that if you took off the back cover, there it was! Buddy got my code, but when I put my sim in, nothing. No way to enter the code.
Now, I'm no phone expert, but I knew something was terribly wrong. I have played around a little with smart phones, and even rooted one (well, partially at least), but I did some research, mostly here, and found that this appears to be a rather troublesome phone to mod. to make matters worse, I found out how to get into the bootloader and I fear I have done more harm than good. Not sure what I did, but then the SD card (which, of course, there really isn't one) became unmounted.
What I need, is a step by step process on what I can do, if anything, to make this phone work again. Now I know there are already threads like this on here, but they assume that the people they are helping have dev backgrounds. I do not. I get lost in all the jargon. I follow for a bit and then I get ROM and RUU all mixed up and have no idea what facepalm is or why you want S-off. It needs to be in plain english, or at least as plain a language as the terminology permits. I'm sure I'm not the only one on the planet suffering a similar fate and wondering what the heck to do.
Here is what I know:
Model - PJ40110
Kernel version - 3.0.71-gdde6c1e-dirty
[email protected] #1
Wed May 1 00:22:12 CEST 2013
CPU - ARMv& Processor rev 4 (v71)
Android version - 4.1.2
CyanogenMod version - 10-20130430-UNOFFICIAL-ville
Build version - Dark-Jelly-S-Edition -(Build-31)
Build date - Mi 1.Mai00:19:13 CEST 2013
Build # - cm_ville-userdebug 4.1.2 JZO54K eng.
xxmrhyde.20130501.001850 test-keys
Having been rooted and modded, I can access a lot, provided that doesn't happen to be one of the areas that crashes. If you need more info, tell me where to look and exactly what to look for. I'm really that much of a noob. All I really want is for it to work, whether that means taking it back to stock or another mod that actually works. Please help!
Hi, thank you for using XDA Assist. The purpose of XDA Assist is to point you in the right direction. I'm going to give you some links which hopefully will solve your problem. You're going to have to do the homework. Not having an IMEI is going to be your biggest problem but the first thing to do is get the device back to stock.
Start here, http://forum.xda-developers.com/showthread.php?t=1630459 and here, http://www.xda-developers.com/all-i...-mytouch-4g-slide-amaze-4g-rezound-and-vivid/
If you have further questions ask in here, http://forum.xda-developers.com/htc-one-s/help
Thread closed.