Related
So I've ran into a new issue. Just got my replacement phone from VZW, the trackball quit on my old one, and it came with 2.1 already installed. I didn't think much about it until I went to root the phone.
I've tried the first edition PB00IMG.zip and the more recent link from Ivan on XDA and with both files, when I boot the phone holding vol dn and end, I get the following error msg:
Main Version is older!
Update Fail!
Do you want to reboot device?
<Action> Yes
I've also tried the MR2 RUU downgrade method, but it failed too. Anyone have any ideas on how to root the phone?
boostlover said:
So I've ran into a new issue. Just got my replacement phone from VZW, the trackball quit on my old one, and it came with 2.1 already installed. I didn't think much about it until I went to root the phone.
I've tried the first edition PB00IMG.zip and the more recent link from Ivan on XDA and with both files, when I boot the phone holding vol dn and end, I get the following error msg:
Main Version is older!
Update Fail!
Do you want to reboot device?
<Action> Yes
I've also tried the MR2 RUU downgrade method, but it failed too. Anyone have any ideas on how to root the phone?
Click to expand...
Click to collapse
Sorry dude, you can't root. you now have the same problem as the people with the leak versions. The boot loader on your phone of higher than the one on the root rom.
Verizon has been sending some replacement phones that have the "wrong" HBOOT on them and users aren't able to root. Sounds like you got one too...
Was this shipped to you or an in-store exchange ? Seems to me that stores might have older, non-updated phones in stock, but I could be wrong.
It was shipped, go figure. So there's no way around it? :[
Not with that phone. Same problem people (who installed a leak) have been having for many, many weeks now...
Do you think its possible that since so many leakers have swapped their phones like scum bags that verizon is refurbing them and not flashing them back to stock?
Erris Bueller said:
Do you think its possible that since so many leakers have swapped their phones like scum bags that verizon is refurbing them and not flashing them back to stock?
Click to expand...
Click to collapse
If we can't get them back to stock bootloaders, no one can
hallstevenson said:
Verizon has been sending some replacement phones that have the "wrong" HBOOT on them and users aren't able to root. Sounds like you got one too...
Was this shipped to you or an in-store exchange ? Seems to me that stores might have older, non-updated phones in stock, but I could be wrong.
Click to expand...
Click to collapse
Its not "Wrong," HBoot 1.49 is just what Verizon is shipping all of their New Eris's with. Check the latest Verizon RUU that Conflipper released
Erris Bueller said:
Do you think its possible that since so many leakers have swapped their phones like scum bags that verizon is refurbing them and not flashing them back to stock?
Click to expand...
Click to collapse
EDIT: nevermind, I checked OP's post history. Sorry, bro. That sucks.
Spencer_Moore said:
If we can't get them back to stock bootloaders, no one can
Click to expand...
Click to collapse
spencer, technically, verizon and htc, and probably even google can return the phones back to whatever version they want, its just a matter of if they want to make the ROM and bootloader that will allow that.
And of course, they are not going to willingly do that for us, since that allows us to root the phone, which they dont want. they would rather have us keep the phones on an unrootable version.
That sucks dude. Strange enough my trackball on my eris is not working in one direction but I guess I'll just get use to it since I love root.
I loved having root too, looks like I'm up s***creek without a paddle though.
Damn that sucks man!!!!! Mine were shiped overnight from Texas and both had 1.5. Crap luck man. Just pray your trackball goes out again and it probably will.
Okay, so I've been using my Eris for months now with no problems. Development has gone fine aswell - rooted to 2.1, installed a ROM or two, and most recently got ahold of 2.2 for my enjoyment (KaosFroyo).
Well, actually, all I remember from the time was that my phone was at 11%, and I had locked it and put it down. Upon picking it up, I couldn't unlock it. But the other side of the screen, the one to switch it to silent, went about half way over and stopped. I posted the same problem in the KaosFroyo thread for help too, so.
I've tried doing restores with Clockwork with no luck. I'm just confused as to why it was so sudden. And if it's physical for some reason, I'm gonna' have trouble finding $90 for ****-surion to replace my phone.
Unfortunately, clockwork recovery can potentially mess up the Eris very badly. Idk why but it doesn't work well with this phone. Maybe try flashing a different recovery, wipe, and flash Rom again?
Sent from my Eris
settlethestorm said:
Unfortunately, clockwork recovery can potentially mess up the Eris very badly. Idk why but it doesn't work well with this phone. Maybe try flashing a different recovery, wipe, and flash Rom again?
Sent from my Eris
Click to expand...
Click to collapse
Gonna give it a go. Any suggestions as to a better recovery?
I'm afraid though I've lurked, I'm still learning.
V1215 said:
Gonna give it a go. Any suggestions as to a better recovery?
I'm afraid though I've lurked, I'm still learning.
Click to expand...
Click to collapse
Lol don't worry about it, I lurked for quite a while before I learned how to do the things I wanted. Do you have the app Rom manager on your phone?
Sent from my Eris
If you do (cause it puts clockwork on your phone) then you have the option to flash to an alternate recovery through the app. It's called amon ra 1.6.2 (numbers aren't exact lol) and requires no restart. If you don't have Rom manager, then search the Eris development subforum for the guide on how to safely flash from clockwork to amon ra. Hope this helps, if you have any questions feel free to pm me at anytime. I'm on a lot lol
Sent from my Eris
Well, I've used AR Recovery before, I just wasn't sure if there were any other/better ones. Obviously not Clockwork.
I successfully went back to AR Recovery using the guide I found on the forum.
Wiped data and dalvik.
Reflashed KaoFroyo v30.
Aaand... still no functionality on the left side. DAMN IT.
Any other suggestions? I mean, I could always go back to the stock 2.1 and take it back to VZW. Not that I really want to, but I can only assume it's hardware now.
Try reflashing a rom that hasn't caused you problems. If that doesn't work unroot and get a new phone. I don't know why you'd have to pay when it's a hardware issue that's the company's fault but whatever that's almost definitely the only thing you can do.
Hungry Man said:
Try reflashing a rom that hasn't caused you problems. If that doesn't work unroot and get a new phone. I don't know why you'd have to pay when it's a hardware issue that's the company's fault but whatever that's almost definitely the only thing you can do.
Click to expand...
Click to collapse
I tried flashing back to CELB 2.8, and still nothing. D:
Yeah, I agree. I've already gone back to stock 1.5, and am currently awaiting a trip to the Verizon store to return it. Hopefully they don't play it off as physical damage and make me pay for it. <.< Kind of unfortunate though - I was on a roll.
V1215 said:
I tried flashing back to CELB 2.8, and still nothing. D:
Yeah, I agree. I've already gone back to stock 1.5, and am currently awaiting a trip to the Verizon store to return it. Hopefully they don't play it off as physical damage and make me pay for it.
Click to expand...
Click to collapse
Hey guys... been checking around.. have a few quick questions. Just to give you an idea.. I've rooted and flashed my own Captivate, now my brother is looking for a new phone so we may get him an atrix.
1. How common is it to hardbrick the atrix? I know that on the captivate a hardbrick is an extremely rare happening, and you can almost always go back to stock via odin.
2. Is CM7 officially available? if so are the nightly releases fairly stable?
3. I know that flashing voids the warranty, and I wouldn't try to redeem a phone I ruined by overclocking or anything like that.. However, I prefer to have a way to completely remove anything I did to the phone. Is this possible?
1. Not very. Unless you try to downgrade from 4.5.91
2. I'm using cm7 now. No nightlies but 0 issues! VERY stable!
3. If you unlock bootloader its unlocked. No going back.
Sent from my MB860 using XDA App
Like joe said a hard brick is not very common, unless you don't follow directions. Cm7 is currently in beta for the atrix, but it is very very stable. No web top or finger scanner try though. Once you unlock the phone, during startup wroth the red M in thee upper left it will say unlocked. So nope, no way to undo it all.
Sent from my MB860 using XDA App
I'm going to agree with the the first two points earlier posters made, but as for relocking the bootloader, I think it can be done if you sbf(not recommended) back to the stock 3.4
Sent from my Unlocked Gingerblurred Atrix
Thanks guys, I know that on the Captivate if you go back to odin it returns it to stock.
I am hesitant to root something that can't be reverted.. not a good situation if something goes out.
I don't think he is too worried about the finger print scanner or webtop.
My friend wanted his Atrix rooted i took it home and did it under a hour, I had no experience with command prompts at the time
Sent from my VS910 4G using XDA App
There's an easy to follow guide if you only want root, not unlocked bootloader. Other than removing bloat its mildly pointless though
Sent from my MB860 using XDA App
krad54 said:
I'm going to agree with the the first two points earlier posters made, but as for relocking the bootloader, I think it can be done if you sbf(not recommended) back to the stock 3.4
Sent from my Unlocked Gingerblurred Atrix
Click to expand...
Click to collapse
I was under the impression that unlocking the bootloader cannot be undone, which is why the hardbrick occurs when flashing back to an earlier version after the GB OTA update.
I believe flashing a fruit cake should give you the stock Motorola bootlogo (no "Unlocked" at the top) image, but the bootloader will still be unlocked.
The biggest issue here is honestly this.
I don't want to get a phone with some sort of manufacturer defect, then not be able to claim the warranty because the phone was at some point in its life flashed. (Sometimes it takes a while for the defects to actually pop up..)
I don't believe in overclocking or anything like that.
If I softbrick a phone I can usually fix it on my own.
I just don't want say, the speaker to go out and it have nothing to do with what rom he is running..
And then for my brother to be out of a phone, just because the speaker went out.. despite it having nothing to do with the fact it was flashed..
As to the bootloader, yes you can flash earlier versions and the "unlocked" at the boot screen will disappear, however there will remain evidence that you had unlocked the bootloader before if they investigate it
That being said there's been quite a few people who have been able to get warrenty replacements and repairs sending back their phones after flashing back..I haven't heard of anyone who's phone has been investigated that deeply and rejected
That works.
I mean, I don't have any intention of overclocking or pushing the hardware out of spec or anything.
I figure as long as whatever goes wrong is reasonable and not related to doing something stupid with the device we will probably be ok.
You don't need to overclock that phone at all ... rooting it's simple as I posted before. There some bootloader blocking you from loading roms, can be taken off.
Sent from my VS910 4G using XDA App
While completely bricking the Atrix is hard to do, it's still possible if you don't carefully read all the instructions. I do miss the Captivate though, it's incredibly easy to flash and recover from any mistake. The CM7 beta build is very stable, I have been using it since the last update was release on the 13th of September and haven't experienced any big problems. If your brother is looking at the Atrix for the webtop or fingerprint scanning capabilities though, just know that the current CM7 build do not yet support them.
From what I've read so far, I haven't seen anyone trying to use their warranty have a problem with the unlocked bootloader. If you're going to buy it through AT&T, I'm pretty sure they're oblivious to it anyway. Last time I exchanged my phone at the repair center, they didn't even bother to see if it booted. They just took it and handed me another one on the spot.
I bought a Motorola Photon and unlocked the boot loader, rooted, Clockwork Mod Recovery'd, tried the whole Sprint phone unlocked for all carriers, then flashed CM9.
I tried to sbf back to stock and somehow (assuming I downloaded the wrong file along the way) I now have a Motorola Electrify that tries to run on U.S.Cellular.
I have subsequently downloaded all three stock sbf files on ShabbyPenguin's website and none of them will flash. (Super mega thanks to Shabby!)
I apologize if this is a duplicate thread. I've been searching all over this forum and the general interweb since roughly 9:00pm last night. Does anyone know a way I can force my phone to allow the flash that keeps failing on "re-enumeration"?
I come from mostly Samsung devices and RSD seems to be the closest thing to "download mode" but in download mode you can pretty much flash anything. Sorry this is long and rambling.
jonas916 said:
I bought a Motorola Photon and unlocked the boot loader, rooted, Clockwork Mod Recovery'd, tried the whole Sprint phone unlocked for all carriers, then flashed CM9.
I tried to sbf back to stock and somehow (assuming I downloaded the wrong file along the way) I now have a Motorola Electrify that tries to run on U.S.Cellular.
I have subsequently downloaded all three stock sbf files on ShabbyPenguin's website and none of them will flash. (Super mega thanks to Shabby!)
I apologize if this is a duplicate thread. I've been searching all over this forum and the general interweb since roughly 9:00pm last night. Does anyone know a way I can force my phone to allow the flash that keeps failing on "re-enumeration"?
I come from mostly Samsung devices and RSD seems to be the closest thing to "download mode" but in download mode you can pretty much flash anything. Sorry this is long and rambling.
Click to expand...
Click to collapse
Yikes... I think once people flash that Electrify SBF by mistake, they are screwed.
Well, crap.
Take it to nearest Sprint store ask someone there to reprogram it you tried to do a system update and the battery died in the middle of it and how your phone is now is the end result if you have insurance it will be free to program it and if it fails to program should get new/ refurbished one for free or at the worst what ever the replacement fee is worth a shot worked for me once I tried to flash an sbf and my damn battery drained completely. Took it to Sprint store said the above and received the above. Gl
Sent from my MB855 using xda premium
I don't have insurance.
If you dont have the insurance it will cost you $35 for a replacement phone. I bricked mine without insurance and had to cough up the $35 for a new one. They tried reflashing my phone for free though but it didnt fix issue, so they should reflash it for you no problem without charging
Do you think they'll do it even though its booting up as an electrify on U.S.Cellular?
jonas916 said:
Do you think they'll do it even though its booting up as an electrify on U.S.Cellular?
Click to expand...
Click to collapse
Honestly, it depends on who you see. As a Sprint employee who works at a S&R store, and into rooting myself, I'd have no problem with it (Upstate NY btw). But technically, since it's unlocked, its broken the warantee, and if you go to a store thats very by the books, it's gonna be iffy. If you can, go to a serice and repair store that IS NOT corporate, and likely they'll do it for you. If they ask if you rooted it, just say yes, and one of two things will happen. Either they'll say "sorry, we can't help you" and then you go to a different store, because trust me, that **** doesn't get noted or anything, or since the guy knows what rooting is, he's probably into it himself and will sympathise and get you a new one.
Sprint service and repair store turned me down. Looks like I'm just gonna keep at it. I figure I'll get it at some point. If anyone has any other suggestions, I'll give it a try.
jonas916 said:
Sprint service and repair store turned me down. Looks like I'm just gonna keep at it. I figure I'll get it at some point. If anyone has any other suggestions, I'll give it a try.
Click to expand...
Click to collapse
Does you phone say unlocked ?
Currently, it does not say unlocked. It also gives me an error message if I try to execute any fastboot commands aside from:
moto-fastboot -w
&
moto-fastboot reboot
Motorola is saying all I can do is send it in to them. I can get into RSD mode but nothing will successfully flash. I'm starting to think they might be right. I'm just so used to having Samsung phones. They're relatively easy in comparison. If anyone has any ideas, I'm open to suggestions.
Try # moto-fastboot -w and then rds unlock then #moto-fastboot erase recovery #moto-fastboot flash recovery recovery-cyan-photon3.img (cwm) and you should be good! *cross fingers*
Sent from my MB855 using xda premium
Yeah, that is not going to work either.
That electrify ROM is a PITA when placed on the Photon.
I was able to exchange mine at the local store, but I luck out in the fact that they LOVE me there.
My exchange didn't cost me a dime either. However by that time the phone wouldn't charge either, so it wasn't booting, so they couldn't see the unlocked or the US Cellular boot animation.
Plus the fact the the owner and one of the techs were running Photons really helped.
Good luck.
I have the same problem I think the only way to solve this is to actually unlock it and use a custom rom. OR wait for Sprint to release a 2.3.5 rom to flash since you have a 2.3.5 bootloader I basically have a useless phone now
radrian92 said:
Try # moto-fastboot -w and then rds unlock then #moto-fastboot erase recovery #moto-fastboot flash recovery recovery-cyan-photon3.img (cwm) and you should be good! *cross fingers*
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
Do I put the # in? I've never done that before.
Sent from my Nexus S 4G using Tapatalk
jonas916 said:
Do I put the # in? I've never done that before.
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
No without it
Sent from my MB855 using xda premium
Ok, I've tried that. Basically what I've found is that the 2.3.4 sbf for both the Photon 4G and the Electrify are unlockable, but the 2.3.5 which is available for the Electrify comes with a non unlockable bootloader. Somewhere along the line I must have accidentally flashed that and now I'm screwed. There is no way to downgrade without unlocking and no way to unlock that bootloader at this time. Sorry for the bad news to anyone else in this predicament. If anyone comes across a solution, please let me know.
jonas916 said:
Ok, I've tried that. Basically what I've found is that the 2.3.4 sbf for both the Photon 4G and the Electrify are unlockable, but the 2.3.5 which is available for the Electrify comes with a non unlockable bootloader. Somewhere along the line I must have accidentally flashed that and now I'm screwed. There is no way to downgrade without unlocking and no way to unlock that bootloader at this time. Sorry for the bad news to anyone else in this predicament. If anyone comes across a solution, please let me know.
Click to expand...
Click to collapse
try "frying" the phone phone/cpu so u can get it replaced without them seeing it unlocked ?
More or less that is what I did. By the time I brought my phone into the local store, it wouldn't even turn on.
Now when the tech put his charged battery into the phone, it showed whatever it did, but I was taken care of.
Verizon is sending out replacement phone and need to restore this to stock.
This also started prior to flashing the new ICS leak and after dling ~600mb's via wireless tether.
Not sure if something burned up.
Phone is stuck on 1X only. Tried everything and can't get 3g or reliable 4g.
It get's 4G but only a minute at a time.
I tried doing the various "Fix network bootloop 1x issue threads" but still a no go.
Phone doesn't take the CDMA only option under Mobile networks, it resets back to to lte/cdma.
It never drops to 3g.
I dled the RUU but it does not update nor recover.
Any ideas?
Thanks!
Flash the stock Rom from scrosler's website.
www.scottsroms.com
Droidel said:
Verizon is sending out replacement phone and need to restore this to stock.
This also started prior to flashing the new ICS leak and after dling ~600mb's via wireless tether.
Not sure if something burned up.
Phone is stuck on 1X only. Tried everything and can't get 3g or reliable 4g.
It get's 4G but only a minute at a time.
I tried doing the various "Fix network bootloop 1x issue threads" but still a no go.
Phone doesn't take the CDMA only option under Mobile networks, it resets back to to lte/cdma.
It never drops to 3g.
I dled the RUU but it does not update nor recover.
Any ideas?
Thanks!
Click to expand...
Click to collapse
First thing I'm thinking is you can't RUU back in your situation because the version number is higher than the old RUU. My suggestion is to ROM it, and then flash back to stock RUU, because most ROMs set the version number to 1.0.0.0, therefore all RUU's are a higher version number. Then when you go to flash it, it will recognize, read and flash.
On a side note form this, you're pretty much screwed if you're trying to go to stock from something ripped, since your bootloader will show relocked or tampered, or something other than 'locked' as it shows when completely stock out of the box. This is of course unless you never unlocked it, which means you cant change version numbers, which means you're screwed either way.
Verizon will be able to look at your bootloader and know that it isnt factory stock, so chances are, they are going to charge you for your phone. I'm just trying to be honest and upfront, since I'm kind of a realist when it comes to getting screwed by big corporations like Verizon.
Good luck getting it back to an older version though.
p.s. on the note of your signal issue... the back is on the phone, right? Did you check the contacts inside the cover?
poppajules said:
First thing I'm thinking is you can't RUU back in your situation because the version number is higher than the old RUU. My suggestion is to ROM it, and then flash back to stock RUU, because most ROMs set the version number to 1.0.0.0, therefore all RUU's are a higher version number. Then when you go to flash it, it will recognize, read and flash.
On a side note form this, you're pretty much screwed if you're trying to go to stock from something ripped, since your bootloader will show relocked or tampered, or something other than 'locked' as it shows when completely stock out of the box. This is of course unless you never unlocked it, which means you cant change version numbers, which means you're screwed either way.
Verizon will be able to look at your bootloader and know that it isnt factory stock, so chances are, they are going to charge you for your phone. I'm just trying to be honest and upfront, since I'm kind of a realist when it comes to getting screwed by big corporations like Verizon.
Good luck getting it back to an older version though.
p.s. on the note of your signal issue... the back is on the phone, right? Did you check the contacts inside the cover?
Click to expand...
Click to collapse
The contacts are fine. what if the phone bricked during a software update in hboot? Can they still see relocked and tampered?
Some say that vz doesnt care as long as it has no physical damage.
I don't know about Verizon not caring, but I highly doubt they would take back all of our rooted phones..
I doubt the phone bricked if it booted up. I would flash the ICS RUU and see if the radios fix your signal issue.
Like I said before, I am running Scott's CleamROM and it sets the software versions to 1.0.0.0, so any RUU will flash over it. This is your best bet.
If VZW doesn't care about the bootloader, then you're golden, but don't count on that.
If I may pry, why are you sending it back for the replacement? If it's because of the radios, then I really doubt they are going to just take the phone back, since you could have messed up software to cause the issue.
Just try flashing some stuff before you call it busted. I would go with the ICS leak, Scott's CleanROM, and then back to your old RUU if you want. There's also a patch you have to install to downgrade from CleanROM and ICS leak back to GB, so you might want to do research, also. If you need help finding stuff, just send me a PM.
p.s. Anyone can boot your phone to bootloader (unless of course your phone is in little tiny pieces all over the street), and see that the bootloader is unlocked, possibly tampered for the custom recovery installed, and even if you lock it again, it will say relocked, indicating to everyone that it has been unlocked at one point. 'Unlocked', 'Relocked', 'Tampered', and 'Security Warning' void certain parts of your warranty (in the words of HTC dev.com). The only thing that doesn't void it is if it reads 'Locked'. Period.
Some say that vz doesnt care as long as it has no physical damage.[/QUOTE] Dude I sent two Dinc2 back completed rooted with no problems. Most times the tech at big V. couldn't care less. Most don't wouldn't know what rooting is and the ones that do, more than likely are rooted themselves. The question is if they send it to HTC? And will it meet their requirment now that they have a record that you are rooted as I'm sure if you're had to go thru HTC to unlock. However in reading alot of cases noone have posted a problem with returning a rooted or relocked phone at lease none I've read about. Good luck tho as there's always that first time.
ghostt021 said:
Dude I sent two Dinc2 back completed rooted with no problems. Most times the tech at big V. couldn't care less. Most don't wouldn't know what rooting is and the ones that do, more than likely are rooted themselves. The question is if they send it to HTC? And will it meet their requirment now that they have a record that you are rooted as I'm sure if you're had to go thru HTC to unlock. However in reading alot of cases noone have posted a problem with returning a rooted or relocked phone at lease none I've read about. Good luck tho as there's always that first time.
Click to expand...
Click to collapse
Yeah, I've never tried to send a rooted phone back, personally, but I've never asked anyone at VZW about it. (I'm paranoid that SWAT will descend from the roof and take me down if they knew my phone was rooted)
Good luck dude, just box it up and ship it off then. 'F' 'em.
No go, reflashed ICS leak, the tamper and security warning are gone.
I don't understand why it's not letting me switch to CDMA only. It goes back to CDMA/LTE. Could a bad SIM card cause 3g issues?
I doubt the SIM card would cause 3G issues, but hey, anything is possible I guess. I would say that you wouldn't get ANY signal if the SIM card were bad. Do you have another SIM card phone to test with, perhaps? Just an idea...
Did you go to a ROM instead of just the leak? Hell, you might just have signal issues where you are.. Maybe?
Maybe the antenna did burn up.. never heard of it, but that's not saying it can't happen.
I think tracing your steps back is going to be the best at figuring out the issue. When you flashed the ICS leak, you relocked and flashed, right? no errors? the install went straight down the list with no skipping around? After the install, you went through full HTC/Verizon setup? Have you tried the phone in other locations, i.e. work, groceiry store, gas station, interstate, etc.? Even outside the house will give a different strength... Forgive these sugestions as 'elementary' or 'duh' type suggestions, but something just doesn't sound right.
Also, go to your network settings and try changing the network type from automatic to home only. See what happens.
poppajules said:
I doubt the SIM card would cause 3G issues, but hey, anything is possible I guess. I would say that you wouldn't get ANY signal if the SIM card were bad. Do you have another SIM card phone to test with, perhaps? Just an idea...
Did you go to a ROM instead of just the leak? Hell, you might just have signal issues where you are.. Maybe?
Maybe the antenna did burn up.. never heard of it, but that's not saying it can't happen.
I think tracing your steps back is going to be the best at figuring out the issue. When you flashed the ICS leak, you relocked and flashed, right? no errors? the install went straight down the list with no skipping around? After the install, you went through full HTC/Verizon setup? Have you tried the phone in other locations, i.e. work, groceiry store, gas station, interstate, etc.? Even outside the house will give a different strength... Forgive these sugestions as 'elementary' or 'duh' type suggestions, but something just doesn't sound right.
Also, go to your network settings and try changing the network type from automatic to home only. See what happens.
Click to expand...
Click to collapse
I noticed this happeneng a day prior to flashing the ICS leak. I was using wifi tether do download about 600mb's and notice a couple of hours later that it dropped to 1x. Restarted phone and it went to 4g. I usually switch to 3g to save battery, that's when i notice the problem.
The ics leak flash didn't show any errors.
I am trying to flash GB to this new firmware but i'm having a hard time flashing the PH98IMG RUU from scott's site. It reads and checks it but doesnt flash it.
RUU.exe errored out with "Unknown Error"
Droidel said:
I am trying to flash GB to this new firmware but i'm having a hard time flashing the PH98IMG RUU from scott's site. It reads and checks it but doesnt flash it.
RUU.exe errored out with "Unknown Error"
Click to expand...
Click to collapse
Make SURE you are pulling the PH98IMG for the stock RUU from the android police website, NOT Scott. He didn't post up the new leak. The RUU that Scott has will NOT flash over the old ICS stuff he's put out before.
Go here to get the leaked RUU.
In this process, relock your bootloader, flash the file from A.P.(TWICE, this is important), unlock your bootloader with your unlock token from htcdev, and THEN flash what scott has. It's a time consuming process. It's up to you though. The directions are out there on A.P., Scott's website, all over Scott's thread around the 400-page range for the 4.0.1 release... and my abbreviated directions here.
Grab one of the top three selections, not the pre-rooted version.
also, try going back and re-downloading your ROM file, maybe you got a bad download.
If you upgraded to ics, you can't ruu to gingerbread at all because of the older hboot. But you can flash a gb kernel then a Rom or nandroid+ scrosler sdcard fix
Sent from my ADR6425LVW using xda premium