Related
OK i have done some searching and this sounds like a good one. http://forum.xda-developers.com/showthread.php?t=461524
Then i want to make shure i can get it back to the original rom i have right now so in case it breaks. this it? http://forum.xda-developers.com/showthread.php?t=427507&highlight=dump
Then do you guys know if in this rom it already has gps unlocked or do i have to do the bored thing? http://forum.ppcgeeks.com/showthread.php?t=49933
Then this is my first time doing this. is there anything else i am missing?
First, have you unlocked your phone? This is a must!!
Second, you do have to follow the steps from bored to unlock the GPS.
Third, check out bored's ROMs and kitchens on this forum. Updated today!!
Also, you can revert back to the original ROM and re-lock your phone if neccasary. So no worries. Also, for better signal strength you can also try a new radio (sticky on ppcgeeks). May not help but if you have weak service now, these could give you more bars and extend your battery life.
OH, and if your still on the stock ROM....WOW. You are about to LOVE your phone!! Its like a different phone with a custom ROM, SOOOO much faster
stanglifemike said:
OH, and if your still on the stock ROM....WOW. You are about to LOVE your phone!! Its like a different phone with a custom ROM, SOOOO much faster
Click to expand...
Click to collapse
AMEN!!!!!!
stanglifemike said:
OH, and if your still on the stock ROM....WOW. You are about to LOVE your phone!! Its like a different phone with a custom ROM, SOOOO much faster
Click to expand...
Click to collapse
ya i dont have a rom installed yet and i want a guide on how to install.
So first i have to unlock. Can it be relocked for warrenty.
Then i have to install the rom i have above. Can i install it back to the original rom on my touch pro. and if so how?
then i have to do the bored thing. Can i make so gvps is locked again?
I want to be able to have a new rom but i also want to be able to return it to normal for warrenty.
ReaperBoy said:
ya i dont have a rom installed yet and i want a guide on how to install.
So first i have to unlock. Can it be relocked for warrenty.
Then i have to install the rom i have above. Can i install it back to the original rom on my touch pro. and if so how?
then i have to do the bored thing. Can i make so gvps is locked again?
I want to be able to have a new rom but i also want to be able to return it to normal for warrenty.
Click to expand...
Click to collapse
I am not too familiar with XDA myself but PPCGeeks I would say is a better resource for your Verizon TP. I will post a few links that answer every one of your questions but you'll have to do a little reading yourself......
Unlocking and Relocking for Warranty Repair
Guide To Flashing
lllbored GPS Fix (very easy to do and includes the cab to revert if necessary)
Thread About RELOCKING for Warranty
In my Opinion these are all very easy things to accomplish as long as you made sure you READ the instructions throughly before attempting. Good Luck!
If i have a data connection will that get charged like double when i reastivate my phone? and were and how would i get my rom back to stock?
ReaperBoy said:
If i have a data connection will that get charged like double when i reastivate my phone? and were and how would i get my rom back to stock?
Click to expand...
Click to collapse
Stock CDMA ROMS
Not sure why you would think your Data plan would double???? I havent had any issues with my data plan changing except when buying a new device and they "assume" you want the Enterprise plan. As long as you made sure Verizon set you up on the $29.99 plan in the first place then it shouldnt change to my knowledge....... DONT CALL VERIZON AND TELL THEM THAT YOU UNLOCKED/FLASHED YOUR PHONE , lol.
Your data plan will be fine. Just dont do a lot of tethering if your plan isnt unlimited. Data usage will be the same as before though
GrandMasterB said:
Stock CDMA ROMS
Not sure why you would think your Data plan would double???? I havent had any issues with my data plan changing except when buying a new device and they "assume" you want the Enterprise plan. As long as you made sure Verizon set you up on the $29.99 plan in the first place then it shouldnt change to my knowledge....... DONT CALL VERIZON AND TELL THEM THAT YOU UNLOCKED/FLASHED YOUR PHONE , lol.
Click to expand...
Click to collapse
Lol no i am not that stupid! and all i see for verizon is the leaked rom? i dont knwo if i want to use this.
ok unlocking seems very easy. But now the flashing WOW. I wish there was a video tut for this because this seems pretty easy to screw %$#@ up. Could some one possibly make one?
ReaperBoy said:
Lol no i am not that stupid! and all i see for verizon is the leaked rom? i dont knwo if i want to use this.
Click to expand...
Click to collapse
Little history about that , bout 6 months ago I was helping someone in the CrackBerry forums flash a leaked beta on their Curve , they got confused , called Verizon for help flashing and of course were told that they had Violated customer agreements and the device warranty and how they were going to burn in hell for sinning against Verizon. This person then comes back to the forums furious at everybody that had been trying to help because WE had "voided" their warranty. Just wanted to make sure you werent going to do the same and be mad at me
That ROM is the leaked SHIP Rom that comes on the Verizon TP. Double check your Settings/System/Device Information if your not sure. Like I said in the post I linked above ,I have unlocked , flashed (MANY TIMES) and relocked and flashed the Verizon leaked rom so I could send it back and had NO issues whatsoever.
EDIT : Flashing a new rom is just as easy as unlocking was. Which ROM have you chosen for your first one??
GrandMasterB said:
Little history about that , bout 6 months ago I was helping someone in the CrackBerry forums flash a leaked beta on their Curve , they got confused , called Verizon for help flashing and of course were told that they had Violated customer agreements and the device warranty and how they were going to burn in hell for sinning against Verizon. This person then comes back to the forums furious at everybody that had been trying to help because WE had "voided" their warranty. Just wanted to make sure you werent going to do the same and be mad at me
That ROM is the leaked SHIP Rom that comes on the Verizon TP. Double check your Settings/System/Device Information if your not sure. Like I said in the post I linked above ,I have unlocked , flashed (MANY TIMES) and relocked and flashed the Verizon leaked rom so I could send it back and had NO issues whatsoever.
EDIT : Flashing a new rom is just as easy as unlocking was. Which ROM have you chosen for your first one??
Click to expand...
Click to collapse
all right and then when i am unlocking you get the screen on your computer with a picture of the touch pro and it has you accept the agreements. i have not done this yet but what does that do because it does not seem like that is the unlocker.
Damn this seems harder then putting custom firmware on a psp wich i did with ease.
ReaperBoy said:
all right and then when i am unlocking you get the screen on your computer with a picture of the touch pro and it has you accept the agreements. i have not done this yet but what does that do because it does not seem like that is the unlocker.
Damn this seems harder then putting custom firmware on a psp wich i did with ease.
Click to expand...
Click to collapse
I have had 3 different PSP's and never dared flashed the firmware on one , lol , but this is EASY. All you have to do is litterally follow the onscreen instructions.
GrandMasterB said:
I have had 3 different PSP's and never dared flashed the firmware on one , lol , but this is EASY. All you have to do is litterally follow the onscreen instructions.
Click to expand...
Click to collapse
ok that part seems really easy. but the flashing part? http://forum.ppcgeeks.com/showthread.php?t=43266
I am looking at this one and it has alot of words and i was reading and i dont get when you put the rom in.
this is were i get lost
3.then in the newly created RUU directory add the rom of your choice - (copy the RUU_Signed.nbh to desktop\RUU)
4.Place phone in bootloader mode (power button while holding volume down button)
5.open the ROMUpdateUtility.exe
6.follow the RUU on screen instructions from there
Oh and i just for fun did the power and down volume key and i went to the 3 color thing and it says security unlocked and i dont think i unlocked it yet......
ReaperBoy said:
ok that part seems really easy. but the flashing part? http://forum.ppcgeeks.com/showthread.php?t=43266
I am looking at this one and it has alot of words and i was reading and i dont get when you put the rom in.
this is were i get lost
3.then in the newly created RUU directory add the rom of your choice - (copy the RUU_Signed.nbh to desktop\RUU)
4.Place phone in bootloader mode (power button while holding volume down button)
5.open the ROMUpdateUtility.exe
6.follow the RUU on screen instructions from there
Oh and i just for fun did the power and down volume key and i went to the 3 color thing and it says security unlocked and i dont think i unlocked it yet......
Click to expand...
Click to collapse
and i have been reading and i think i take the ruu thing in my roms folder and put it into the RUU folder on my desktop?
ReaperBoy said:
and i have been reading and i think i take the ruu thing in my roms folder and put it into the RUU folder on my desktop?
Click to expand...
Click to collapse
That is dependant on which ROM you choose......... which rom did you choose?
Most roms are alot easier than that now.
EDIT** If it says .35 cmonex in bootloader then it IS unlocked. Nothing against XDA but for your CDMA Touch Pro you reallly need to be over at PPCGeeks for this. That Crossler post you linked to hasnt been updated for 3 months now. Crosslers Kitchen on PPCGeeks was updated yesterday , just a thought
I guess I'll say what I did to end up here, first:
A few months back, I bought an unlocked HTC Hero (A626) from eBay. This evening, I decided it'd be a good idea to root the thing and install a nice 2.1 ROM.
2 hours later, I find myself with a locked phone. Or, at least, that's what it seems to be. My SIM is definitely *in* the phone, and it's quite adamant that it doesn't have one.
I *was* following the instructions at theunlockr.com about "rooting the hero in one click" - I downloaded the RUU downgrade for "unbranded European users" (though my phone is now in Canada... it *is* an unbranded European phone).
After some mess with drivers and HTC Sync, I finally got the 1.76 RUU to work (I was on 2.73 before)... until I ended up with error code 140; something about a device error.
Now, from my browsing, I'm fairly certain that I could get around this by making a Goldcard and retrying the downgrade and continuing with the root/upgrade.
What I want to know is: will this fix my phone? (making a goldcard, rooting and continuing with a custom rom, that is) Right now it's on radio 6.35.06.18, but I don't believe that changed since the RUU failed. The RUU seems to have locked the phone, and nothing else; every other piece of my data is still intact. If not, is there any way that I can make it work again?
Thanks very much; any help is appreciated
i seem to remember the 140 error when trying to apply the RUU. making a goldcard got me past it.
strange..from other ppl post on phone sim unlocking, rooting shouldnt affect the sim lock at all
krisrm said:
I guess I'll say what I did to end up here, first:
A few months back, I bought an unlocked HTC Hero (A626) from eBay. This evening, I decided it'd be a good idea to root the thing and install a nice 2.1 ROM.
2 hours later, I find myself with a locked phone. Or, at least, that's what it seems to be. My SIM is definitely *in* the phone, and it's quite adamant that it doesn't have one.
I *was* following the instructions at theunlockr.com about "rooting the hero in one click" - I downloaded the RUU downgrade for "unbranded European users" (though my phone is now in Canada... it *is* an unbranded European phone).
After some mess with drivers and HTC Sync, I finally got the 1.76 RUU to work (I was on 2.73 before)... until I ended up with error code 140; something about a device error.
Now, from my browsing, I'm fairly certain that I could get around this by making a Goldcard and retrying the downgrade and continuing with the root/upgrade.
What I want to know is: will this fix my phone? (making a goldcard, rooting and continuing with a custom rom, that is) Right now it's on radio 6.35.06.18, but I don't believe that changed since the RUU failed. The RUU seems to have locked the phone, and nothing else; every other piece of my data is still intact. If not, is there any way that I can make it work again?
Thanks very much; any help is appreciated
Click to expand...
Click to collapse
I dont see the sim lock being the cause of no network since you started messeing about with it as the sim lock is held on a totally different part of the phone so any ru update wouldnt effect that or the networks would be nackered, have you tried putting thte recovery image on http://android.modaco.com/content/htc-hero-hero-modaco-com/291486/06-jan-installing-the-patched-recovery-image-on-your-device/ and flashing one using that?
This is not a sim-lock issue. sounds like a goldcard is needed, as this is the bootloader lock you are experiencing...
Ok, well, I suppose I'll try the goldcard, then - one more question; once I make the goldcard, can I ever use the SD card normally afterwards? I don't know if I want to use my 8GB Class 6 if it's unusable as storage, after this :/ .
(Also, apologies to the mods for posting in the Development forums - 'tis what happens when one is low on sleep and stressed by phone problems )
EDIT: Ok - from some reading, it sounds like it's best for me to go looking for the 2GB card that came with the phone, as it will "just be a goldcard after this". If anyone wants to confirm this, that would be excellent. Thanks for all the help, by the way
Ok - I decided I'd try out Flashrec instead (I guess I wasn't on 2.73....7, rather 5, which apparently has the exploit needed to make flashrec work), and I flashed Cyanogen's recovery image successfully - I can boot into recovery mode and I get the familiar screen .
I just want to be very clear about this: can I now flash a custom ROM (preferably without bricking my phone )? (I was thinking Villain 4 Beta2, but if anyone else has a better suggestion... I'm looking for a 2.1 ROM with Sense). I'm not really sure I want to flash the "improved" recovery-RA-HERO right now, as I cannot su (I think this is an issue with me not having it on the phone, as I get "permission denied" errors when I try to run it). Would it be a wise idea to flash a custom ROM with su *first*, and then maybe update my recovery image?
Thanks
All right, sorry about that - disregard my above post; I went ahead with the update. I'm now running Villain4beta2 (2.1 is so nice ). However, I still have the "No Sim card in phone" issue, even though I most certainly *do* have a SIM card in the phone. Does anyone have any idea what's happened? Even better, does anyone know how I can fix this? I'd get it unlocked again, but as some of you mentioned, it doesn't really make sense that a ROM update would sim-lock the phone... Also, I have no idea which carrier it would have been locked to (it shouldn't have been locked to a carrier, really... it's a stock white international phone), so wouldn't that make unlocking rather difficult/impossible?
...and disregard *that* post as well. Turns out the Hero is *really* picky with the SIM tray. It has to be locked entirely; you can use your fingernails and swipe to the left if it doesn't work. Anyway, it had nothing to do with SIM locks and everything to do with me being incompetent at putting in the SIM . So, consider this problem SOLVED.
If it is incapable of detecting any inserted sim I imagine that will make unlocking impossible, since aiui to unlock you need to have a sim inserted belonging to a carrier other than the one it is locked to, in order for the phone to prompt you for an unlock code.
Was the sim recognised & working previously? I know you've just rooted it, but I'd be inclined to try flashing with a stock RUU, if you haven't already. Just pick an old one so you can root it afterwards without the hassle of a gold card.
If it doesn't work with a stock ROM I'd suspect a hardware problem, but it is strange if it was working prior to you starting to update flash. There's no way at any stage you attempted to flash a CDMA Hero rom to your GSM Hero (which I assume it is as you said it was European)? It doesn't seem likely, but worth double checking I guess.
Lol. I've done that before. Didn't think to suggest it as I never imagined anyone else could be as incompetent as me Glad you got it sorted.
Heheh, I do believe you've met your match . Thanks, everything is working beautifully now
krisrm said:
...and disregard *that* post as well. Turns out the Hero is *really* picky with the SIM tray. It has to be locked entirely; you can use your fingernails and swipe to the left if it doesn't work. Anyway, it had nothing to do with SIM locks and everything to do with me being incompetent at putting in the SIM . So, consider this problem SOLVED.
Click to expand...
Click to collapse
haha you clown, well at least now you have the rec image and you can flash away till your hearts content!!
Hello everyone. I have a problem with my Motorola Atrix and I am hoping someone might be able to help me.
I got it as a late Christmas present so its still practically new. I tried doing an OTA update from 2.2 to 2.3 and the battery died whilst the update was taking place. I replaced that battery with my spare battery which was fully charged, but now it won't load. When trying to load on startup, it gets stuck at the dual core logo and gives an error message if I press the volume button. The message says something like "Starting RSD protocol support". I am gutted...
I have been searching feverishly through the forums for some help, and I have come across some information with regards to the types of bricks, ie hard/soft, but I am not sure which it is in my case. There is alot of information available, but I can't find any with my problem. I am not opposed to trying to fix the problem myself as I have some experience in messing around with software, though that was back in the days of p2k-tools some 10 years back, but I would appreciate a nudge in the right direction and some advice maybe since I am almost clueless about Android software. Any help would be greatly appreciated.
Additional info:
The phone is completely factory default software wise, so is not rooted or running any form of custom firmware. UK carrier - Tmobile.
I think you have two options. If it's still under a warranty, take it back to the store and ask them to repair it. Or if you don't care about a warranty, you can follow this post http://forum.xda-developers.com/showthread.php?t=1136261 to unlock your phone and install a custom ROM. But if you decide to unlock you phone, before trying anything, read the post completely. I'm saying again, read the post completely before doing anything.
I myself unlock the Atrix and using a custom ROM and I have a pretty good battery life compared with a stock ROM.
Thank you for your response. I will look into the warranty idea and see how that goes. I hope there is not a long wait period which is my biggest reservation about this option since I need my phone.
In so far as installing the custom ROM and unlocking it, is there maybe another way that would allow me to continue to use stock firmware and OTA updates? I have been reading through some threads where they say once there is a custom firmware, running an OTA update could brick the phone. I also really just prefer to keep the phone original. If this can't be done, then I will have to give the warranty thing a serious go before I consider the alternative.
shottah said:
Thank you for your response. I will look into the warranty idea and see how that goes. I hope there is not a long wait period which is my biggest reservation about this option since I need my phone.
In so far as installing the custom ROM and unlocking it, is there maybe another way that would allow me to continue to use stock firmware and OTA updates? I have been reading through some threads where they say once there is a custom firmware, running an OTA update could brick the phone. I also really just prefer to keep the phone original. If this can't be done, then I will have to give the warranty thing a serious go before I consider the alternative.
Click to expand...
Click to collapse
Go here > http://www.motorola.com/Support/US-EN/Android_Products/ATRIX-4G_Software_Update_Page. Another alternative is to flash 2.3.4 stock via RSDLite, but if the update went through on your phone you could brick. Hopefully one of these will work for you! Other option is to unlock the bootloader.
If you have a full battery why not download the T-Mobile software and write it back to the phone via rsd.
Sent from my MB860 using Tapatalk
CaelanT said:
Another alternative is to flash 2.3.4 stock via RSDLite, but if the update went through on your phone you could brick. Hopefully one of these will work for you! Other option is to unlock the bootloader.
Click to expand...
Click to collapse
Thanks for the suggestion. How can I tell if the update went through? Can I access this information in the phone's current state?
lonegunman said:
If you have a full battery why not download the T-Mobile software and write it back to the phone via rsd.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
By now the battery is just short of full, but it should be enough to get through the flash. Where would I get the T-mobile software? I have checked their site and the latest android update they have is 2.1 on the site. I have also looked at the Motorola website, but their means of update is via an update program called Motorola Software Update.
Sorry if I appear a bit dense, its just from what I'm seeing is that I may only have one chance to do this and get it right, else its bye bye Atrix. I am still waiting on a response from Motorola with regards to my query about the warranty. If I can get it sorted myself, I will definitely prefer that as opposed to having to wait on them to diagnose etc.
Have a look for the ATRIX super firmware thread on here and see if the T-Mobile software is in it, it may be the old software but it's worth a try as you can send the phone in to be fixed or just take it to a T-Mobile store and let them deal with it for you.
Sent from my MZ604 using xda premium
CaelanT said:
Another alternative is to flash 2.3.4 stock via RSDLite, but if the update went through on your phone you could brick. Hopefully one of these will work for you! Other option is to unlock the bootloader.
Click to expand...
Click to collapse
If I implemented the automated update via the link you provided, could that circumvent the potential bricking you described, provided the program can access the phone? By the way, the link you gave was software for an AT&T mobile, while mine is T-Mobile UK. Will this make a difference?
shottah said:
If I implemented the automated update via the link you provided, could that circumvent the potential bricking you described, provided the program can access the phone? By the way, the link you gave was software for an AT&T mobile, while mine is T-Mobile UK. Will this make a difference?
Click to expand...
Click to collapse
Ah, you're on an international Atrix? AT&T update won't work for you then.
Sorry, I missed that at bottom of the OP.
If you get stuck and are in london pm me and I will see if I can help.
Sent from my MB860 using xda premium
CaelanT said:
Ah, you're on an international Atrix? AT&T update won't work for you then.
Sorry, I missed that at bottom of the OP.
Click to expand...
Click to collapse
No problem, I appreciate whatever help I can get.
lonegunman said:
If you get stuck and are in london pm me and I will see if I can help.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Thanks for the offer pal. Wish I was in the London area to get the help but, I'm in Stoke.
Ok, i have no idea if this will work but hay the phone is knacked so why not give it a go, it's under warranty so you can send it back if it don't work go http://forum.xda-developers.com/showthread.php?t=1125944 find the orange full and t-mobile service files, download them and write them to your phone via rsd, it's kinda hard to say what one first, its a shame that the t-mobile one is not a full one as that would be perfect, the battery should still charge so leave it on over night, also if can try and make a motorola service cable, that will put power to your so no need to worry about a battery, have a look on here as to how to make it.........ok forget all that if you check out post 276 on the link above it has download for the GB rom t-mobile uk which is what you need to wirte via rsd.
Even if you don't pay you're carrier for warranty Motorola gives you a year warranty on the phone and that's the sane with almost all carriers I sent my unlocked atrix in for screen issues and they still fixed it and same with my hd2 and ipod touch
Any update on this?
Sent from my MB860 using Tapatalk
lonegunman said:
Any update on this?
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Sorry pal, been busy with classes so no time to update the thread. Basically, I tried to update via Motorola software, but it seems it cant access the phone to begin the update process. I tried to do download the OEM ROM of 2.3.4 from the ATRIX superthread, as this seems the safest option to me, bit it seems its on a host that no longer allows downloads. I tried to request a mirror, but I don't seem to have the authority to post in that thread. If you or anyone can make the request for it to be reuploaded to another mirror, I would be most great full.
Post 276 of Atrix Formwares Superthread
ROM:
Original Gingerbread SBF for ATRIX MB860 T-Mobile UK
Android 2.3.4 ---- Blur_Version.45.31.2.MB860.T-Mobile.en.GB
filename:
1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31.2-release-keys-signed-T-Mobile-GB.sbf.gz
Did you try this?
http://forum.xda-developers.com/showpost.php?p=19908591&postcount=276
shottah said:
Sorry pal, been busy with classes so no time to update the thread. Basically, I tried to update via Motorola software, but it seems it cant access the phone to begin the update process. I tried to do download the OEM ROM of 2.3.4 from the ATRIX superthread, as this seems the safest option to me, bit it seems its on a host that no longer allows downloads. I tried to request a mirror, but I don't seem to have the authority to post in that thread. If you or anyone can make the request for it to be reuploaded to another mirror, I would be most great full.
Post 276 of Atrix Formwares Superthread
ROM:
Original Gingerbread SBF for ATRIX MB860 T-Mobile UK
Android 2.3.4 ---- Blur_Version.45.31.2.MB860.T-Mobile.en.GB
filename:
1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31.2-release-keys-signed-T-Mobile-GB.sbf.gz
Click to expand...
Click to collapse
When you say that the updated doesn't start because the Motorola software can't access the phone, is your phone recognized when you plug it into your computer?
dratsablive said:
When you say that the updated doesn't start because the Motorola software can't access the phone, is your phone recognized when you plug it into your computer?
Click to expand...
Click to collapse
The laptop recognizes the phone since I can hear USB noises when plugged and unplugged. When I try to run the software, it tries to connect and then I get the message:
"Motorola Software Update is unable to identify your device at this time. Please try again."
zigbee_chitti said:
Did you try this?
Click to expand...
Click to collapse
Yes I did try the link, but sharing is disabled on that host so I cant download it. That is exactly what I need from what I understand, but I don't have enough access to request a mirror, even though I have more than 10 posts for some reason.
Ok, well it seem over the whole megaupload thing any of the file sharing sites are playing it safe, you need to find someone who has the t-mobile file already and can send it to you, i have the orange one but not sure if it will brick your phone or not.
lonegunman said:
Ok, well it seem over the whole megaupload thing any of the file sharing sites are playing it safe, you need to find someone who has the t-mobile file already and can send it to you, i have the orange one but not sure if it will brick your phone or not.
Click to expand...
Click to collapse
The OP of that file would have access to his files on the host, its only 3rd parties who can't download his files from uploaded to his account. If he/some one else who has it can upload it to another site, it would be fine. He should still have access to his files on his account with the host though, so if anyone is feeling kind to make the request on my behalf, I would appreciate it very much since I am being prevented from posting in that section myself. Thnaks.
Please go here now: http://forum.xda-developers.com/showthread.php?t=1653777
Mods should unsticky mine and sticky that instead.
Go to the above link if your a victim of virgin mobile firmware.
since the other thread got shut down before i got a response, i will repost now.
I flashed the original fix that was posted a few days ago and it worked great until today. I got my first radio interface error since the pri downgrade. Does this mean if i want to fix my issues completely i should go through these new downgrade instructions? I don't really care about a banner (or even roaming at the moment), since i am assuming an official sprint firmware update will come very soon. The only thing that i need right now to work is my texting. Any suggestions on doing the bare minimum to hold me over till the official firmware is released?
hockey4life0099 said:
since the other thread got shut down before i got a response, i will repost now.
I flashed the original fix that was posted a few days ago and it worked great until today. I got my first radio interface error since the pri downgrade. Does this mean if i want to fix my issues completely i should go through these new downgrade instructions? I don't really care about a banner (or even roaming at the moment), since i am assuming an official sprint firmware update will come very soon. The only thing that i need right now to work is my texting. Any suggestions on doing the bare minimum to hold me over till the official firmware is released?
Click to expand...
Click to collapse
So you have no data at all? I'd try a ##data# reset first.
hockey4life0099 said:
since the other thread got shut down before i got a response, i will repost now.
I flashed the original fix that was posted a few days ago and it worked great until today. I got my first radio interface error since the pri downgrade. Does this mean if i want to fix my issues completely i should go through these new downgrade instructions? I don't really care about a banner (or even roaming at the moment), since i am assuming an official sprint firmware update will come very soon. The only thing that i need right now to work is my texting. Any suggestions on doing the bare minimum to hold me over till the official firmware is released?
Click to expand...
Click to collapse
Never assume. Just because VM has a different firmware, that doesn't mean that Sprint 3d's will too. We do not fully know what the differences are between the 2 devices.
Thus the reason for this and other fix threads. I would suggest trying this fix, and see if it helps, and hope that there is a firmware fix in the future.
I will tell you how I restored my data. I first downloaded the following stock rom.
Stock 2.08.651.2 With HTC/Sprint Spyware Removed
http://forum.xda-developers.com/showthread.php?t=1285975
After flashing to the stock rooted rom above I then went into my dialer and typed in ##my MSL number# (Example: ##000000#) To get your MSL number simply download MSL reader from the market. I then clicked on edit and then edited my MDN with all zeros and MSID with all zeros. I pressed the menu button and then pressed reset. After the phone rebooted the phone activation screen came up when I unlocked the phone and it was able to automatically activate it and I got 3G data.
jlechner said:
So you have no data at all? I'd try a ##data# reset first.
Click to expand...
Click to collapse
no, i have data ussually. I have found though every once in a while my sms messages will not send (with a radio interface error). When this happens, my phone will show a signal, but calls, sms, and data will not work until i do a profile or a prl update. then my phone will work normally again until it decides it wants to crap out yet again.
hockey4life0099 said:
no, i have data ussually. I have found though every once in a while my sms messages will not send (with a radio interface error). When this happens, my phone will show a signal, but calls, sms, and data will not work until i do a profile or a prl update. then my phone will work normally again until it decides it wants to crap out yet again.
Click to expand...
Click to collapse
This is the issue some are having. I would say it's because of the VM firmware we flashed. Did you try the PRI version downgrade that takes you back to 003 even though it shows 005? or does yours still say 004?
hockey4life0099 said:
no, i have data ussually. I have found though every once in a while my sms messages will not send (with a radio interface error). When this happens, my phone will show a signal, but calls, sms, and data will not work until i do a profile or a prl update. then my phone will work normally again until it decides it wants to crap out yet again.
Click to expand...
Click to collapse
Hockey, I have not seen this issue yet on my rom, PM me if you want to try mine, and let me know if you see any difference. I wonder if some of the SMS issues have to do with the ICS rom itself. BTW do not post my ROM anywhere as I do not release my stuff public, just want to help out a fellow hardcore flasher.
Cheers
jlechner said:
This is the issue some are having. I would say it's because of the VM firmware we flashed. Did you try the PRI version downgrade that takes you back to 003 even though it shows 005? or does yours still say 004?
Click to expand...
Click to collapse
i flashed chads first firmware downgrade. My phone now shows that my PRI is 1.53_145. This worked for like 3 days, but here i am again with the same issue
Freeza or Unknownforce, I have a guy getting a replacement phone tomorrow. He wants to help. I figured we could have him pull the partitions, please advise.
hockey4life0099 said:
i flashed chads first firmware downgrade. My phone now shows that my PRI is 1.53_145. This worked for like 3 days, but here i am again with the same issue
Click to expand...
Click to collapse
Touch base with Mikey.
hockey4life0099 said:
i flashed chads first firmware downgrade. My phone now shows that my PRI is 1.53_145. This worked for like 3 days, but here i am again with the same issue
Click to expand...
Click to collapse
Oh perhaps you need to be on PRI version 1.42_003? I never ran into issues on chad's downgrad PRI either though.
This thread can't be deleted. This has good info we need up.
I know it says Chad in it, but should we just take the name out?
Well, if we did, then we won't give credit where it's due.
Anyways,
Is there any general thought on the rough percentage of people this works 100% for?
Mikee4fun said:
Oh perhaps you need to be on PRI version 1.42_003? I never ran into issues on chad's downgrad PRI either though.
Click to expand...
Click to collapse
is there a way to get to 1.42_003?
Thank god there's another one of these!
Ok so I got back from sprint again and the were totally in awe and had no idea whatsoever was wrong with my phone They ordered me a new one and it'll be here on like tuesday or wednesday and i'll see if I can get it not activated already.
Btw the sprint people are totally dumb.... They were talking to a couple and saying yeah, the more storage a phone has the faster it'll be! He said that 32gb phones out performed 16gb phones.... I was like wtf man... Also he was trying to sell them the galaxy s 2's and was telling them that they're new phones. Wtf sprint salesman, wtf...
hockey4life0099 said:
is there a way to get to 1.42_003?
Click to expand...
Click to collapse
The 005 mod is actually 003, from my understanding.
Sent from my Sprint/Virgin Mobile hybrid.
jlechner said:
Freeza or Unknownforce, I have a guy getting a replacement phone tomorrow. He wants to help. I figured we could have him pull the partitions, please advise.
Click to expand...
Click to collapse
Thanks, but I think we have everything we need at this point. I'm writing code right now for the patching part of the process. Not that I have everything that I need just yet, but at least getting that part out of the way for when I do have the correct information.
I've located everything that I have to change in my own partition to fix it (All the differences) next I'm going to compare these offsets with those of the partitions that freeza gives me and see if they line up the same... there's going to be some major coding needed for this, because it did manipulate some of the "flow" I think in the way it lists out certain information in the file, like rom name, and phone number and stuff...
I'm not the fastest coder, but I have basically all I need at this point for my own device... I just want to verify that it's similar code on others' devices as well before I get too far ahead of myself here and have to backtrack. I'm actually going to re-code the downgrade tool to make it part of that, probably rename it to a "multitool" of some kind and simply put it into the already stickied thread, and have closeone update his cd with it so that people can do this with ease.
The best part of this all is that the bricking process isn't going to be a stupid timing thing like it is when downgrading... a single command can brick an already S-OFF phone the way we need it. So no confusing timing issues with this one! Just a nice easy set of instructions. Phew.
Short and sweet basic steps right now:
1.) Nand Backup
2.) Brick
3.) Run "multitool" Plug unplug, yadda yadda.
4.) Boot phone back up to 1.40 S-ON
5.) Run 1.13 RUU
6.) Revolutionary S-OFF
7.) Flash 2.17 Firmware
8.) Flash recovery
9.) Restore Backup
10.) Drink Beer
More details to follow.
hockey4life0099 said:
is there a way to get to 1.42_003?
Click to expand...
Click to collapse
Yes, you need to go through the adb push process stated in the OP. I can assist you if you want through team viewer if you don't want to tackle it.
Unknownforce said:
Thanks, but I think we have everything we need at this point. I'm writing code right now for the patching part of the process. Not that I have everything that I need just yet, but at least getting that part out of the way for when I do have the correct information.
I've located everything that I have to change in my own partition to fix it (All the differences) next I'm going to compare these offsets with those of the partitions that freeza gives me and see if they line up the same... there's going to be some major coding needed for this, because it did manipulate some of the "flow" I think in the way it lists out certain information in the file, like rom name, and phone number and stuff...
I'm not the fastest coder, but I have basically all I need at this point for my own device... I just want to verify that it's similar code on others' devices as well before I get too far ahead of myself here and have to backtrack. I'm actually going to re-code the downgrade tool to make it part of that, probably rename it to a "multitool" of some kind and simply put it into the already stickied thread, and have closeone update his cd with it so that people can do this with ease.
The best part of this all is that the bricking process isn't going to be a stupid timing thing like it is when downgrading... a single command can brick an already S-OFF phone the way we need it. So no confusing timing issues with this one! Just a nice easy set of instructions. Phew.
Short and sweet basic steps right now:
1.) Nand Backup
2.) Brick
3.) Run "multitool" Plug unplug, yadda yadda.
4.) Boot phone back up to 1.40 S-ON
5.) Run 1.13 RUU
6.) Revolutionary S-OFF
7.) Flash 2.17 Firmware
8.) Flash recovery
9.) Restore Backup
10.) Drink Beer
More details to follow.
Click to expand...
Click to collapse
Cool thanks!
Sent from my Sprint/Virgin Mobile hybrid.
Hiya folks, bit of a problem. I never bothered to root or unlock my DNA (it's been getting the job done nicely with a few non-root customizations, and I have other gadgets to tinker away with). This morning I accepted the OTA update from Verizon, and now it's bricked - stuck on the HTC splash screen.
I did a soft reset, cleared the cache partition, and performed a hard reset - no dice. Called Verizon and HTC, no help - I can pretty much do a repair/replacement if I'm still under warranty. I'd really rather avoid going down that path, as I think I'm barely over the warranty (though I can hopefully get them to honor it if I'm within 30 days).
Is there any way I can still flash this back to an older stock, having never unlocked it? I can only get the thing into fastboot mode, and all of the instructions I've found are for when the phone's been bricked after rooting. adb can't seem to talk to it at all, probably because it's in fastboot. Is it safe to attempt using an RUU or some sort of image to flash it using the fastboot utility?
Since it's already bricked, I went ahead and made a go at it using an older RUU, but it quick before even trying, claiming I needed the correct version of the utility. It's possible I did it wrong, though.
Any help would be much obliged! This is what I get for not rooting/learning how to do this stuff earlier...
EDIT: Before this newest update, my phone had the most up-to-date stock ROM. It was fully charged when it performed the OTA.
jaawerth said:
Hiya folks, bit of a problem. I never bothered to root or unlock my DNA (it's been getting the job done nicely with a few non-root customizations, and I have other gadgets to tinker away with). This morning I accepted the OTA update from Verizon, and now it's bricked - stuck on the HTC splash screen.
I did a soft reset, cleared the cache partition, and performed a hard reset - no dice. Called Verizon and HTC, no help - I can pretty much do a repair/replacement if I'm still under warranty. I'd really rather avoid going down that path, as I think I'm barely over the warranty (though I can hopefully get them to honor it if I'm within 30 days).
Is there any way I can still flash this back to an older stock, having never unlocked it? I can only get the thing into fastboot mode, and all of the instructions I've found are for when the phone's been bricked after rooting. adb can't seem to talk to it at all, probably because it's in fastboot. Is it safe to attempt using an RUU or some sort of image to flash it using the fastboot utility?
Since it's already bricked, I went ahead and made a go at it using an older RUU, but it quick before even trying, claiming I needed the correct version of the utility. It's possible I did it wrong, though.
Any help would be much obliged! This is what I get for not rooting/learning how to do this stuff earlier...
EDIT: Before this newest update, my phone had the most up-to-date stock ROM. It was fully charged when it performed the OTA.
Click to expand...
Click to collapse
Exact same thing happened to me last evening...except I'm rooted with S-off.
grimmkt said:
Exact same thing happened to me last evening...except I'm rooted with S-off.
Click to expand...
Click to collapse
Try flashing the latest RUU ZIP in fastboot. someone had a similar issue.
http://forum.xda-developers.com/showpost.php?p=48301738&postcount=6
The actual thread is here: http://forum.xda-developers.com/showthread.php?t=2558885
ryclegman said:
Try flashing the latest RUU ZIP in fastboot. someone had a similar issue.
http://forum.xda-developers.com/showpost.php?p=48301738&postcount=6
The actual thread is here: http://forum.xda-developers.com/showthread.php?t=2558885
Click to expand...
Click to collapse
Aha! Much obliged. I searched for the right RUU and couldn't find it, and completely missed that thread - I was using the wrong search terms. Downloading now - I'll update tonight once I know if it works. Then I'm modifying the crap out of this thing!
jaawerth said:
Aha! Much obliged. I searched for the right RUU and couldn't find it, and completely missed that thread - I was using the wrong search terms. Downloading now - I'll update tonight once I know if it works. Then I'm modifying the crap out of this thing!
Click to expand...
Click to collapse
Sounds good! let us know!:good:
ryclegman said:
Try flashing the latest RUU ZIP in fastboot. someone had a similar issue.
http://forum.xda-developers.com/showpost.php?p=48301738&postcount=6
The actual thread is here: http://forum.xda-developers.com/showthread.php?t=2558885
Click to expand...
Click to collapse
I can't get the phone to connect in fastboot. I keep getting a "driver failed to load" type error when I plug in the USB...the device is never visible.
Worked like a charm! The download took awhile, but once I had it downloaded it was easy.
For others searching for this issue:
Once you have the RUU, just install Android Development tools (specifically fastboot) and enter
>fastboot oem rebootRUU
>fastboot flash install IMAGEFILE.ZIP
Terminal/command prompt on the computer side told me it was finished but the phone was stuck at the very end of the progress bar. I waited a while few minutes, and when it didn't move I risked doing a
>fastboot reboot
and we were good to go.
Arise, thread!
So! My phone never bricked again, but a few weeks after I performed the RUU with the image linked earlier in this thread, I started to see the problem that early DNA's started to have with it randomly giving a "no SIM card" error. I'd had this issue when I first got the DNA, but at the time I just went through the normal phone replacement process to resolve it. Imagine my surprise when it came back after flashing! It's now reached the point where I will lose calls because of it, and will often have to reboot/toggle airplane mode to get data back, so I finally got annoyed enough to post.
Presumably this problem is because the image I flashed from is the original DNA image with the drivers that cause that SIM issue. So my question is: if I s-off, root, and install a custom ROM, will that take care of it? Or is this particular issue so deep on the driver level that I need to find a more recent RUU?
I also have not yet tried a new SIM - because of the timing of the problem, I'm slow to believe that it's related to the SIM card, but I suppose it isn't impossible.
jaawerth said:
Arise, thread!
So! My phone never bricked again, but a few weeks after I performed the RUU with the image linked earlier in this thread, I started to see the problem that early DNA's started to have with it randomly giving a "no SIM card" error. I'd had this issue when I first got the DNA, but at the time I just went through the normal phone replacement process to resolve it. Imagine my surprise when it came back after flashing! It's now reached the point where I will lose calls because of it, and will often have to reboot/toggle airplane mode to get data back, so I finally got annoyed enough to post.
Presumably this problem is because the image I flashed from is the original DNA image with the drivers that cause that SIM issue. So my question is: if I s-off, root, and install a custom ROM, will that take care of it? Or is this particular issue so deep on the driver level that I need to find a more recent RUU?
I also have not yet tried a new SIM - because of the timing of the problem, I'm slow to believe that it's related to the SIM card, but I suppose it isn't impossible.
Click to expand...
Click to collapse
The only way I have seen this permanently resolved is to get a new Sim tray from HTC. I got one and my brother did too and I never get Sim card errors like I used to. Just go to their website contact their support and ask for one and they send it out for free no questions asked.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Jaggar345 said:
The only way I have seen this permanently resolved is to get a new Sim tray from HTC. I got one and my brother did too and I never get Sim card errors like I used to. Just go to their website contact their support and ask for one and they send it out for free no questions asked.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks, may as well give it a try. What's odd is that this problem hadn't happened at all with this sim tray until after I flashed, which really makes it sound like a software issue. Still, worth a shot!
jaawerth said:
Thanks, may as well give it a try. What's odd is that this problem hadn't happened at all with this sim tray until after I flashed, which really makes it sound like a software issue. Still, worth a shot!
Click to expand...
Click to collapse
It's a known hardware issue in the DNA. When they give you a new Sim tray it's thicker and it holds the Sim card in place better resulting with no more errors.
Sent from my HTC6435LVW using XDA Premium 4 mobile app