Ever since I flashed my first ICS rom, I have not been able to connect to WiMax 4G. It just redirects to Clear's website telling me to sign up with them.
So my thinking is that my WiMax keys were deleted/overwritten/corrupted.
So my question is this, using CWM recovery, how do I restore my WiMax partition? I see no option to restore it, when I revert back to a previous backup I see all the other stages (system, recovery, boot, etc) being restored but never WiMax.
I do have a nandroid backup from prior to installing any ICS rom... Just can't do anything with it as of now.
Any help would be greatly appreciated.
Try doing dialer code ##3282# then go to edit mode and enter ur keys in the 1st part of the NAI under WiMAX but write everything down first before u change anything on the menu just in case
Sent from my PG86100 using xda premium
kickyoace said:
Try doing dialer code ##3282# then go to edit mode and enter ur keys in the 1st part of the NAI under WiMAX but write everything down first before u change anything on the menu just in case
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Already did that (kind of) I reverted back to the last GB nandroid I had, took screenshots of all my wimax info in epst, went back to ICS and all settings were the same.
Now I think that was a failed test anyway. Like I said CWM goes through all the things it is restoring, but wimax is never mentioned... ever. And there is no wimax option in "Advanced Restore" either.
There is a wimax-blahblahblah.img in each of my nandroid backup folders though... can I restore it via adb? Pull the wimax*.img from the sdcard and "adb flash wimax ./wimax.img" or something like that?
I am convinced I have the tools to fix this, just not the knowledge yet lol.
More info (trying to fix via fastboot...)
Ok, so I pulled the CWM backup of my wimax partition...
Code:
adb pull /mnt/sdcard/clockworkmod/backup/2012-05-06.23.15.11/wimax.SERIALNUMBER.img ~/wimax.orig.img
Which yeilded:
4017 KB/s (12583424 bytes in 3.058s)
At this point I am thinking "Woot! going as planned!"...
Ok, so fastboot time...
Code:
adb reboot bootloader
Ok, "FASTBOOT USB" displayed, awesome.
Code:
fastboot flash wimax /home/ranthony/Desktop/wimax.orig.img
sending 'wimax' (12288 KB)...
OKAY [ 2.770s]
writing 'wimax'...
FAILED (remote: image update error)
finished. total time: 2.780s
Failed
I can't be the only one in this boat... Anyone offer a fix?
What hboot are u on cuz dl the eng hboot so u can use that command successfully
Sent from my PG86100 using xda premium
netstat_EVO said:
More info (trying to fix via fastboot...)
Ok, so I pulled the CWM backup of my wimax partition...
Code:
adb pull /mnt/sdcard/clockworkmod/backup/2012-05-06.23.15.11/wimax.SERIALNUMBER.img ~/wimax.orig.img
Which yeilded:
4017 KB/s (12583424 bytes in 3.058s)
At this point I am thinking "Woot! going as planned!"...
Ok, so fastboot time...
Code:
adb reboot bootloader
Ok, "FASTBOOT USB" displayed, awesome.
Code:
fastboot flash wimax /home/ranthony/Desktop/wimax.orig.img
sending 'wimax' (12288 KB)...
OKAY [ 2.770s]
writing 'wimax'...
FAILED (remote: image update error)
finished. total time: 2.780s
Failed
I can't be the only one in this boat... Anyone offer a fix?
Click to expand...
Click to collapse
try flashing this image....
kickyoace said:
What hboot are u on cuz dl the eng hboot so u can use that command successfully
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
On hboot 1.40
This really won't work without the eng hboot?
wloftus said:
try flashing this image....
Click to expand...
Click to collapse
Going to hold off for now. Really want to just restore the original from mine. Thanks though.
kickyoace said:
Try doing dialer code ##3282# then go to edit mode and enter ur keys in the 1st part of the NAI under WiMAX but write everything down first before u change anything on the menu just in case
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Also, the NAI is your 4G MAC address (minus all the :'s) @sprintpcs.com, not a key.
In any case, I am officially lost...
I checked the md5 sum between my wimax backup prior to the problem and compared to the md5 sum of a more recent backup... same. Problem is not related to anything in it
netstat_EVO said:
Ever since I flashed my first ICS rom, I have not been able to connect to WiMax 4G. It just redirects to Clear's website telling me to sign up with them.
So my thinking is that my WiMax keys were deleted/overwritten/corrupted.
So my question is this, using CWM recovery, how do I restore my WiMax partition? I see no option to restore it, when I revert back to a previous backup I see all the other stages (system, recovery, boot, etc) being restored but never WiMax.
I do have a nandroid backup from prior to installing any ICS rom... Just can't do anything with it as of now.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
What are you talking about? There is no 4G on ICS roms. That's your problem.
raptoro07 said:
What are you talking about? There is no 4G on ICS roms. That's your problem.
Click to expand...
Click to collapse
Huh?
I am sending this on 4g Wimax using MeanROM ICS.
Sent from my ICS 3VO with Tapatalk 2
coal686 said:
Huh?
I am sending this on 4g Wimax using MeanROM ICS.
Sent from my ICS 3VO with Tapatalk 2
Click to expand...
Click to collapse
Sorry, your right. In sense 3.6 leaks. I'm on sense 4.0 and that's what I was thinking about. Sorry. :banghead:
Sent from my PG86100 using xda app-developers app
raptoro07 said:
Sorry, your right. In sense 3.6 leaks. I'm on sense 4.0 and that's what I was thinking about. Sorry. :banghead:
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Yeah, I can't wait until the devs get 3d and 4G on sense 4.0.
Sent from my ICS 3VO with Tapatalk 2
MAY, I repeat MAY have found a solution.
I went back into epst, and for some reason my realm was "sprintpcs.com " with a trailing space. I took this out, committed changes, and it rebooted. I went back into epst and the trailing space didn't come back... Hopefully with android being a linux based os where even something as simple as a letter being in the wrong case can screw things up, the fix may be just that simple. Will update when I get a chance to waste gas and drive out to a 4G coverage area again...
Solved.
Damn trailing space ... can't even see it unless you try to edit the realm setting.
But, I got my 4th G back!
netstat_EVO said:
Solved.
Damn trailing space ... can't even see it unless you try to edit the realm setting.
But, I got my 4th G back!
Click to expand...
Click to collapse
Glad you got it. It's funny how a space is nothing to us, but makes a big difference to a computer.
Sent from my ICS 3VO with Tapatalk 2
Yep that shows how dumb comps really are unless there super computers then they are amazingly smart
Sent from my PG86100 using xda premium
So screwed
Need help.. I lost my nandroid backup on the HDD so I am getting an SSD. I flashed a ROM and lost wifi and 4g. now I cant get gplay to work..
I have no wimax.img to modify or the knowledge to change it using a HEX editor. Can I use someone's .img?
I need help.
retsehc said:
Need help.. I lost my nandroid backup on the HDD so I am getting an SSD. I flashed a ROM and lost wifi and 4g. now I cant get gplay to work..
I have no wimax.img to modify or the knowledge to change it using a HEX editor. Can I use someone's .img?
I need help.
Click to expand...
Click to collapse
Read this thead. You can't use WiMax keys from another phone and shouldn't even been asking for them.
ramjet73
ramjet73 said:
Read this thead. You can't use WiMax keys from another phone and shouldn't even been asking for them.
ramjet73
Click to expand...
Click to collapse
ramjet.. I have read several threads now that it can be done with a donor wimax.img and hex editing to enter the MAC address of my phone. I just need the wimax.img
Anyone want to be a donor?
Related
This tool will allow reading and directly writing the main version in Htc's misc partition to allow flashing if your main version is higher than the hboot/fastboot zip you are trying to flash or for the purpose of software downgrading on most HTC devices.
Pre-reqs:
Device must be an emmc based HTC & you must have root.
This should work on all emmc based HTC devices G2 to current such as rezound. This tool has been tested on Incredible 2 and on Rezound.
Useage is :
misctool <option> <value to write>
r: read main version from misc partition. No <value to write> needed
w: write new value to main version in misc partition & read back new value
ex. misctool w 1.00.000.0
Setting a value of 1.00.000.0 will allow all hboot zips to pass version checking.
If you are testing to see if it works on another htc run "misctool r" and if the version read back is correct the write will work also.
This can be used in userspace & recovery.
Example of use in updater-script:
run_program("/tmp/misctool", "w", "1.00.000.0");
I will eventually have this included into my RA Revamped recovery lineup as time permits.
If you find this useful consider donating to my development device fund (I'm hoping one day to join the Rezound club) as I was considering releasing this in a paid for apk but changed my mind and decided to GPL source it.
Static pre-compiled binary & gpl source is attached.
Looks good bud!
So just flash the zip in recovery?
Sent from my ADR6425LVW using XDA App
Flash this in recovery and your main version gets set to a generic 1.00.000.0
This will allow any PH98IMG.zip or the newest RUU to run on your phone. I recommend flashing this before you flash a ROM that autoboots to install a PH98IMG.zip or before loading a PH98IMG.zip manually.
How to use: Just flash it in recovery as if it were a rom. Main Version Older issue will be solved.
con247 said:
No. I can make a flashable zip. Hold tight.
Click to expand...
Click to collapse
Sweetness!!!!!
Edit: U guys are awesome. You just helped a lot of people
Sent from my ADR6425LVW using XDA App
Doddzilla said:
Sweetness!!!!!
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
It is up
10char
This is a super tool I've been using fast boot to keep from running into problems with main version. May still but this is an unfortunately necessary tool. If we had s-off this wouldn't be a issue. But thanks again for this
sent from ics land
it can be dropped in rom scripts to fix the main version. This can be used to avoid future mainversion problems.
Has anyone tried it yet? Think I'm bout to take the leap tired of this damn mainver issue
Sent from my ADR6425LVW using XDA App
Doddzilla said:
Has anyone tried it yet? Think I'm bout to take the leap tired of this damn mainver issue
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
Umm of course. Think something would be just thrown together and not tested?
drellisdee said:
Umm of course. Think something would be just thrown together and not tested?
Click to expand...
Click to collapse
No not really. Sorry to doubt.
Edit: flashed Cons zip in recovery worked like a charm. Checked mainver through fastbboot
Sent from my ADR6425LVW using XDA App
con247 said:
No. I can make a flashable zip. Hold tight.
edit: attached. Flash this in recovery and your main version gets set to a generic 1.00.000.0
Click to expand...
Click to collapse
How much to sticky this? I forsee many other updates/leaks* etc that will end up causing mainver issues. Stick this at top. Sadly I wont get to see Con go off anymore in threads about fixing mainver
Anyway, Big THANKS to drellisdee and con247!
ih8mydroid said:
Sadly I wont get to see Con go off anymore in threads about fixing mainver
Anyway, Big THANKS to drellisdee and con247!
Click to expand...
Click to collapse
No seriously if someone has f'ing problems now I will be even more pissed lol.
LOL! It's soooo gonna happen, too.
:banghead: :beer: .
drellisdee said:
This tool will allow reading and directly writing the main version in Htc's misc partition to allow flashing if your main version is higher than the hboot/fastboot zip you are trying to flash or for the purpose of software downgrading on most HTC devices.
Click to expand...
Click to collapse
This is awesome! Thanks man!
i have never had a mainver problem yet but this will make sure i dont
yojoe600 said:
i have never had a mainver problem yet but this will make sure i dont
Click to expand...
Click to collapse
I was thinking the same thing. I never had a problem but now I can accept the OTA and not have to worry about causing the mainver issue. #baller
Um... Not sure what I did but I just flashed this and restored a GB backup with the GB kernel and now the phone won't recognize my SIM. I have no service. Could this be related or not.
Did you put your battery cover back on?
con247 said:
Did you put your battery cover back on?
Click to expand...
Click to collapse
I had it on but still nothing. Just took out the sim and cleaned it and all is good now. Sorry about that. The sim might have slipped out or something earlier when I was fighting with it trying to get out my sd card.
Love the tool. Finally I don't have to go in and manually change the android-info.txt file on every kernel.
As you guys know, we can't flash boot images directly from Recovery. This makes restoring nandroid backups more difficult.
Well, not anymore. This flashable allows you to restore the boot image from a nandroid backup directly from recovery. For those of you who are experts, this duplicates the functionality of "fastboot boot recovery.img" in a self-contained zip.
To Use:
1) Flash the attached zip file
2) Press Volume UP when prompted at HBOOT
3) Reboot the Device (it will probably ask you to press power to do so)
NOTE: If the device doesn't reboot on its own, reboot "normally" not into recovery. It will take you to recovery automatically. If you go into recovery via the HBOOT menus, you still won't be allowed to restore boot images.
4) Restore your nandroid and with its boot image. It will flash this time
5) Done.
How it works:
1. Dumps your recovery image
2. Zips it into a viable PH98IMG.zip and drops it on your SD card
3. Downgrades your main version
4. Reboots to HBOOT so you can flash it
5. You then boot into unprotected recovery.
Haha I had an issues yesterday that this would have fixed. You do amazing work con, keep it up! We appreciate it!!!!!
Sent from my Ice Cream covered Rezound
Why are there not 1000 thanks for this??? This is awesome!
Great stuff. Thanks
DbZ Gokuu said:
Haha I had an issues yesterday that this would have fixed. You do amazing work con, keep it up! We appreciate it!!!!!
Sent from my Ice Cream covered Rezound
Click to expand...
Click to collapse
WasabiWa83 said:
Why are there not 1000 thanks for this??? This is awesome!
Click to expand...
Click to collapse
NilsP said:
Great stuff. Thanks
Click to expand...
Click to collapse
I am glad you guys like it. Not sure how much use it will get, but atleast it is out there.
con247 said:
I am glad you guys like it. Not sure how much use it will get, but atleast it is out there.
Click to expand...
Click to collapse
Worked perfectly ! wow, nice job just like using my OG droid now with backups I had quit making them since I always had to remember what kernel for the rom etc.. tried the endeavor leak and afterwards flashed my backup without a hitch
mjh68 said:
Worked perfectly ! wow, nice job just like using my OG droid now with backups I had quit making them since I always had to remember what kernel for the rom etc.. tried the endeavor leak and afterwards flashed my backup without a hitch
Click to expand...
Click to collapse
Good to get a confirmation that it works.
So we use this any time we restore a nand correct?
yep. It just allows Recovery to flash the boot image, but it is temporary.
Curious. Could this be used on a fresh install as well?
sent from ics land
pwned3 said:
Curious. Could this be used on a fresh install as well?
sent from ics land
Click to expand...
Click to collapse
Yeah but it offers no benefit or extra ease. The way we install custom roms right now is the ideal way.
con247 thank you so much for this. I fastboot flash everything from the computer. But two guys that I help out on gtalk on a regular basis had a bunch of trouble with the PH98 process, but aren't able to use fastboot on their computers while at work.
Both guys have been using this rom very heavily going back and fourth between ICS and gingerbread, and both have confirmed this is very easy for noobs compared to the fear they have of ADB, fastboot.exe, and the cmd line.
Thanks again. You are an incredible asset to the Rezound and Android community.
Nice work
Sent from my ADR6425LVW using xda premium
con247 said:
I am glad you guys like it. Not sure how much use it will get, but atleast it is out there.
Click to expand...
Click to collapse
No more renamed PH98IMG files on my sd card! Good work, sir
Sent from my Ice Cream covered Rezound
I used this quite a bit the other night , after I ran the RUU before I found out restoring old backups was a bad idea LOL. Still worked flawlessly though , so this tool has been invaluable to me ! I started making backups again
I can't restore any backups. I'm using the latest amonra. It just says oops check recovery log. I tried doing it regular and with this but they both failed and I had to use the ruu to recover each time. I don't understand what the problem is.
Sent from my HTC Vigor
Andro X said:
I can't restore any backups. I'm using the latest amonra. It just says oops check recovery log. I tried doing it regular and with this but they both failed and I had to use the ruu to recover each time. I don't understand what the problem is.
Sent from my HTC Vigor
Click to expand...
Click to collapse
well give me the recovery log please. Do you have an external SD card?
con247 said:
well give me the recovery log please. Do you have an external SD card?
Click to expand...
Click to collapse
It might be related to using the Amon Ra 3.14 and trying to backup android secure. Dres, just released a fix because the Devblock location changed so it borked making or restoring backups that contained android secure. Sorry , if this wasn't helpful , but I realized my backups worked because I never backup android secure. Just figure it might save you a lot of debugging when its probably on the recovery this time not the app.
mjh68 said:
It might be related to using the Amon Ra 3.14 and trying to backup android secure. Dres, just released a fix because the Devblock location changed so it borked making or restoring backups that contained android secure. Sorry , if this wasn't helpful , but I realized my backups worked because I never backup android secure. Just figure it might save you a lot of debugging when its probably on the recovery this time not the app.
Click to expand...
Click to collapse
You could have also gotten a bad download. This script shouldn't be affected by the new firmware.
Thanks guys but I figured it out. I left a space when renaming the folder containing my backup. So once took out the space I was able to restore.
Sent from my HTC Vigor
ok,
So like an idiot, i began the S-OFF process without reverting my SuperCID. I cannot get past step 8, and i am having errors flashing my RUU.
Right now i cannot get past the bootloader. If i try to fastboot reboot, it takes me back to the bootloader. If i try a reboot, it takes me back to the bootloader.
Is there something that i can flash to get me back and running? I have tried numerous things, and i really need my phone back tonight. Grandfather is in the hospital, and i have no way to contact anyone except through facebook / email.
does anyone have some ideas, or know what i need to do? I honestly dont care about root or s-off, i can do that later. Right now i just need a bootable phone.
help!
squeezyb said:
ok,
So like an idiot, i began the S-OFF process without reverting my SuperCID. I cannot get past step 8, and i am having errors flashing my RUU.
Right now i cannot get past the bootloader. If i try to fastboot reboot, it takes me back to the bootloader. If i try a reboot, it takes me back to the bootloader.
Is there something that i can flash to get me back and running? I have tried numerous things, and i really need my phone back tonight. Grandfather is in the hospital, and i have no way to contact anyone except through facebook / email.
does anyone have some ideas, or know what i need to do? I honestly dont care about root or s-off, i can do that later. Right now i just need a bootable phone.
help!
Click to expand...
Click to collapse
Did you relock the boot loader?
Sent from my DROID RAZR using Tapatalk 2
yes i did
squeezyb said:
yes i did
Click to expand...
Click to collapse
More info would help like what errors you are getting
Sent from my DROID RAZR using Tapatalk 2
adb wont even find my device, so i am not getting any errors. is there a working RUU i can rename to PJ53IMG, and flash that through the bootloader?
http://forum.xda-developers.com/showthread.php?p=28723878
Sent from my DROID RAZR using Tapatalk 2
right, i tried this and had no success. the bootloader went through the process, and began to load the file, but did not finish the process. Could i possibly have tried flashing the wrong one?
i know this is something simple that i can flash, but it is not working
squeezyb said:
right, i tried this and had no success. the bootloader went through the process, and began to load the file, but did not finish the process. Could i possibly have tried flashing the wrong one?
Click to expand...
Click to collapse
Either should work but try the other
Sent from my DROID RAZR using Tapatalk 2
i tried using the one from unlimited.io, renaming it to PJ53IMG, but it would not flash... in theory that would do the trick right?
i am trying to download the file again, we'll see if that works. possibly corrupted on my end
squeezyb said:
i tried using the one from unlimited.io, renaming it to PJ53IMG, but it would not flash... in theory that would do the trick right?
i am trying to download the file again, we'll see if that works. possibly corrupt
Click to expand...
Click to collapse
Probably not. Use the one provided in Andy's thread. ADB is probably not working because debugging has been turned off.
Have you tried the recovery? Check to see if that works. If not try to fastboot a recovery. The command is "Fastboot flash recovery". Try with TWRP. If that takes then try to flash a ROM with that.
blazingwolf said:
Probably not. Use the one provided in Andy's thread. ADB is probably not working because debugging has been turned off.
Click to expand...
Click to collapse
the link in andy's thread is busted, or i would. unless i am wrong.. have you tried it?
On my side ill say do what the ther said, if you still have supercid you can unlock device and flash recovery and flash a working rom if you want it booteable
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
squeezyb said:
the link in andy's thread is busted, or i would. unless i am wrong.. have you tried it?
Click to expand...
Click to collapse
Yep. Working just fine for me.
Anyways, try the recovery route. I think it is your best bet.
blazingwolf said:
Yep. Working just fine for me.
Anyways, try the recovery route. I think it is your best bet.
Click to expand...
Click to collapse
OK FALSE ALARM!
I am back in business.
the first time tried flashing the RUU it did not work. i redownloaded, tried again, and it works fine.
Thank you everyone for dealing with my noob behavior.
<3 you all
squeezyb said:
OK FALSE ALARM!
I am back in business.
the first time tried flashing the RUU it did not work. i redownloaded, tried again, and it works fine.
Thank you everyone for dealing with my noob behavior.
<3 you all
Click to expand...
Click to collapse
Great to hear.
squeezyb said:
OK FALSE ALARM!
I am back in business.
the first time tried flashing the RUU it did not work. i redownloaded, tried again, and it works fine.
Thank you everyone for dealing with my noob behavior.
<3 you all
Click to expand...
Click to collapse
Everyone panics a little bit when the screen goes black
Sent from my DROID RAZR using Tapatalk 2
jamminjon82 said:
Everyone panics a little bit when the screen goes black
Sent from my DROID RAZR using Tapatalk 2
Click to expand...
Click to collapse
No truer words are spoken
jamminjon82 said:
Everyone panics a little bit when the screen goes black
Sent from my DROID RAZR using Tapatalk 2
Click to expand...
Click to collapse
Yep. And somehow time stands still for an eternity until something happens to let you know its alive.
I'll ask here first I achieved s off bit it destroyed my sd well to cut it short I flashed the ruu.zip I'm now s off with a locked bootloader no superuser or root and no recovery how do I install a recovery?
Sent from my ADR6410LVW using xda app-developers app
prairiedogn said:
I'll ask here first I achieved s off bit it destroyed my sd well to cut it short I flashed the ruu.zip I'm now s off with a locked bootloader no superuser or root and no recovery how do I install a recovery?
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
look here: http://forum.xda-developers.com/showthread.php?t=1435228
I think i might have got to comfortable with my phone and possibly screwed something up in the process.
I recently have been Installing and Removing various ROMS on my phone so I can find one I am happy with and stick to as a DAILY.
I recently deleted from the SD Card all the folders in it besides DCIM, MUSIC, and my own Media. I figured its just an SD Card even if I removed it the phone should still operate. But I haven't touched anything Internally on the phone itself. Just always making CLEAN installs before installing ROMS under Amon Ra WIPE ALL. Which it skips my SD.
So for some reason now I have no Mobile Network on my phone it says its Disconnected. It also shows Full bars but with a TRIANGLE
over it now. I want to go back to regular data. I have a Nandroid Backup of my HTC Rezounds FACTORY ICS Build. While it help if I reverted to that? and started over with the ROM I like?
Have you tried long pressing on Mobile Network in settings and seeing if you it shows LTE/CDMA?
It does, and it is selected.
Take a look at this.
I found a way to take it off of ROAMING. In system select I switched the CDMA ROAMING MODE from Automatic B (I think it was) to Home.
I have a feeling it has something to do with a rom I installed last night. MIUI it might have change some options in the phone internal system
to thinking its not in the US. Im running stock ICS HTC at the moment from my NAN backup of Amon Ra. But at the moment its showing FULL SIGNAL BARS
& then seconds later no Signal Bars with an X over it. The verizon wireless rep told me that I was connecting to their SERVERS. I can also make calls but only under Automatic B settings in Roaming.
Im not sure what to do at this point. I wish there was someway I could reset the phone SIGNAL OR DATA OR CONNECTION SETTINGS or radio or something. o DEFAULT. I even reset back to my NANDROID Backup and WIPED all before I did that and I was still having the same problem. It doesnt make sense to me unless its a TOWER near by that is Out of order.
Sent from my ADR6425LVW
Im stumped
I would appreciate anyone that can help shed some light on this.
ChuckZv2 said:
I would appreciate anyone that can help shed some light on this.
Click to expand...
Click to collapse
You always have the option of flashing a RUU and with that putting your phone back to bone stock.
Sent from my ADR6425LVW using xda premium
i would say start from scratch, flash the global ruu twice, pull the. zip followed by a factory reset. thats what I would do, if I was in your shoes.
Sent from my ADR6425LVW using Tapatalk 2
Or reflash your ROM. If you can do a dirty flash you can just flash over it and I think you won't lose your set up. That should restore any necessary folders/files if that's the issue.
Oh! What about this... Format it in recovery or via your phone in settings. Since there's that option it should put whatever is needed on there.
If you can't tell, I'm just brainstorming here... I don't know what the files and folders are but seems to me formatting it from within the phone should work or why would you be able to do it?
EDIT: I just reread your post where you posted the pic. I guess you probably have more issues than just the ext sd. Probably best to RUU it and get back to stock and start from scratch. Then you know it's all good and clean.
Thanks
LOBBS said:
You always have the option of flashing a RUU and with that putting your phone back to bone stock.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
mike7728 said:
i would say start from scratch, flash the global ruu twice, pull the. zip followed by a factory reset. thats what I would do, if I was in your shoes.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Where can I find the right GLOBAL RUU for my phone?
So I flash the RUU twice one after another. Delete the zip? and Boot and do a factory reset?
I would appreciate any links you can forward me to for the Global RUU!
:victory:Thanks in advanced.
It used to be here:
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
But I just read today that all those mirrors are taken down.
Check the Developer section in the Vigor Shipped RUU thread.
Here's the link from that thread:
http://www.androidfiles.org/ruu/?dir=Vigor
You don't need to factory reset after running the RUU, it puts it all back to factory stock anyway. Relock before you run it:
fastboot oem lock
And after it's done you'll need to unlock again and flash a recovery, root, then flash custom rom.
feralicious said:
Or reflash your ROM. If you can do a dirty flash you can just flash over it and I think you won't lose your set up. That should restore any necessary folders/files if that's the issue.
Oh! What about this... Format it in recovery or via your phone in settings. Since there's that option it should put whatever is needed on there.
If you can't tell, I'm just brainstorming here... I don't know what the files and folders are but seems to me formatting it from within the phone should work or why would you be able to do it?
Click to expand...
Click to collapse
The funny thing is I have a COMPLETE Nandroid Backup of my phone even before I ever flashed my first ROM! (Before this even happened)
I went into Amon Ra and did a CLEAN WIPE. I wiped everything in the internal storage it was completely blank (I check it under My Computer)
I then restored my Nandroid Backup of my STOCK ICS from Verizon and HTC and Im still getting the same error.
"I found a way to take it off of ROAMING. In system select I switched the CDMA ROAMING MODE from Automatic B (I think it was) to Home.
at the moment its showing FULL SIGNAL BARS & then seconds later no Signal Bars with an X over it. The verizon wireless rep told me that I was connecting to their SERVERS."
ChuckZv2 said:
The funny thing is I have a COMPLETE Nandroid Backup of my phone even before I ever flashed my first ROM! (Before this even happened)
I went into Amon Ra and did a CLEAN WIPE. I wiped everything in the internal storage it was completely blank (I check it under My Computer)
I then restored my Nandroid Backup of my STOCK ICS from Verizon and HTC and Im still getting the same error.
"I found a way to take it off of ROAMING. In system select I switched the CDMA ROAMING MODE from Automatic B (I think it was) to Home.
at the moment its showing FULL SIGNAL BARS & then seconds later no Signal Bars with an X over it. The verizon wireless rep told me that I was connecting to their SERVERS."
Click to expand...
Click to collapse
Are you S-On or Off? If S-On, your nandroid may have missed a file that is necessary that can only be replaced by flashing a RUU. Just throwing ideas against the wall.
If I remember correctly, a nandroid from S-On can't touch the kernel and coming from MIUI there may be files that are missing or modified.
In that case, you may be able to pull the stock boot.IMG from the RUU you were on and push that to restore the files.
Sent from my ADR6425LVW using xda premium
LOBBS said:
Are you S-On or Off? If S-On, your nandroid may have missed a file that is necessary that can only be replaced by flashing a RUU. Just throwing ideas against the wall.
If I remember correctly, a nandroid from S-On can't touch the kernel and coming from MIUI there may be files that are missing or modified.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
I am S-On. Its so weird I cant wrap my head around it.
Another funny thing is I've before restored my Nandroid backup when I needed it with a ROM I had that was Unstable and it was working like it should I was back to normal.
Im thinking it has something to do with their towers in my area. But I called a friend that has Verizon as well and he seems to be handling alright.
I just dont get it. Im going to try that RUU flash and see if that works after I eat dinner and possibly relock my phone.
LOBBS said:
Are you S-On or Off? If S-On, your nandroid may have missed a file that is necessary that can only be replaced by flashing a RUU. Just throwing ideas against the wall.
If I remember correctly, a nandroid from S-On can't touch the kernel and coming from MIUI there may be files that are missing or modified.
In that case, you may be able to pull the stock boot.IMG from the RUU you were on and push that to restore the files.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Yes I ADB the Nandroids Boot.img too lol!
ChuckZv2 said:
Yes I ADB the Nandroids Boot.img too lol!
Click to expand...
Click to collapse
Free-flow thinking there. Lol. It's looks like a RUU is going to be your best bet.
Sent from my ADR6425LVW using xda premium
feralicious said:
It used to be here:
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
But I just read today that all those mirrors are taken down.
Check the Developer section in the Vigor Shipped RUU thread.
Here's the link from that thread:
http://www.androidfiles.org/ruu/?dir=Vigor
You don't need to factory reset after running the RUU, it puts it all back to factory stock anyway. Relock before you run it:
fastboot oem lock
And after it's done you'll need to unlock again and flash a recovery, root, then flash custom rom.
Click to expand...
Click to collapse
The android police website did have the RUU files but they are .zip only to flash in recovery they where PH98IMG.zip files.
So im not sure what to do.
hey
Im trying to run the RUU .exe files but the arent executing. I double click the .exe files but nothing happens. I locked my phone so now I dont have access to the bootloader =( I feel like throwing this thing in a river:crying: at this point.
ChuckZv2 said:
Im trying to run the RUU .exe files but the arent executing. I double click the .exe files but nothing happens. I locked my phone so now I dont have access to the bootloader =( I feel like throwing this thing in a river:crying: at this point.
Click to expand...
Click to collapse
Quoted the wrong post this is for the zip files.
You should only have to shorten the name to PH98IMG. All the RUUs I've seen are some longer name (usually the name of the site hosting them_PH98IMG.)
Then just place it on the root of your external SD and boot into Hboot.
Sent from my ADR6425LVW using xda premium
Are you still working on this?
You should be able to RUU from a zip file. Just make sure it's named PH98IMG.zip, put it on your card and then boot into hboot. It should find that file and run it. Let it run through a few times, do its thing and it should reboot when it's done.
I came back here cuz I just ran across this post from another thread:
GordoGuapo said:
<snip>
Could it be because I don't have an SDcard? My phone doesn't read SDcards anymore, so I'm using only the internal storage.
Thanks again!
Click to expand...
Click to collapse
So that guy is using his phone normally without the external card. What happens if you boot up with the external card out of the phone?
I think it has something to do with the hardware on my phone that started not functioning. I did try going into recovery wiping the whole phone wiping my sd card and then placing the zip file in my sd card. I then booted into H boot and from ADB locked my phone rebooted and then it started to read the zip file and reinstalled to factory reset. I let it reinstall the files let it do its thing it restarted a couple of times reinstalled everything needed went back into the lock screen and was still having the same issue till now. But it's okay because I called Verizon Wireless spoke with him on the phone and I still have my extended warranty on the phone and they concluded that it was a hardware issue so I got to replace my phone for free lol
***
Although the problem wasnt solved I still appreciate everyone's help on the matter.
Sent from my ADR6425LVW using xda app-developers app
Go to phone dialer and put *#*#3646#*#* then go to phone information. Look for a drop down menu and make sure its on CDMA/LTE Only (or anything really with CDMA and LTE in it, that specific one may not show up on your list depending on what ruu your on.) That changes the specifics of how the radio operates incoming connections. Set your data settings back to HOME and turn off roaming. Lemme know if that works.
Sent from my Rezound using Tapatalk 2
as the title says.. my droid dna has a triangle above the signal strength.. says I am roaming.. I flashed cm10.2 but it wouldnt boot up so I wiped it and then installed viper rom on it.. still there. any suggestions.. please..thanks
Is it overlaying the signal bars or above the bars, like the data indicator in AOSP?
Sent from my CarbonROM 4.3'd HTC DNA
jlinn75 said:
as the title says.. my droid dna has a triangle above the signal strength.. says I am roaming.. I flashed cm10.2 but it wouldnt boot up so I wiped it and then installed viper rom on it.. still there. any suggestions.. please..thanks
Click to expand...
Click to collapse
I had to reset mine to stock, relock it and return it on warranty, apparently there is a known issue with the sim card slot or tray or something. On my third now, debating whether to unlock and try again. No matter what I flashed on it, RUU, stock roms, anything, I couldn't get it back working right. Always had the roaming. New sim card didn't work either.
So your gonna have to do some work to get it back to stock and proper relocked, and then request a new phone from verizon.
I'm screwed I bought it from a friend
Sent from my Nexus 7 using Tapatalk 4
jlinn75 said:
I'm screwed I bought it from a friend
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
This happen to me also. Luckily I had an upgrade available.
So reverting back to stock and then getting a new sim won't work.?
Sent from my Nexus 7 using Tapatalk 4
Harvey Dent said:
This happen to me also. Luckily I had an upgrade available.
Click to expand...
Click to collapse
what phone did you end up getting?
jlinn75 said:
what phone did you end up getting?
Click to expand...
Click to collapse
I ended up getting the S4. Wanted the One but figured I would give the S4 a go.
I just ****ing got this phone and having the same exact issue.. Got it off swappa so now looks like I'm ****ed
Sent from my Nexus 7 using xda premium
I to have the triangle
Are their any current threads on how to ruu back to stock?
I also have the triangle and was told flashing back to stock would fix it I guess we'll see lol
The thing is I get the triangle but I got it back today by messing around with the sim card.. IMO this seems like an issue with the sim slot.. If u go back to stock let me know how that goes.. As of now I have 3g but no 4g and honestly I haven't had 4g on this phone since I got it 3 days ago
Edit... Just replaced my sim .. Good to go now make sure u try that b4 giving up
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Kevin3328 said:
The thing is I get the triangle but I got it back today by messing around with the sim card.. IMO this seems like an issue with the sim slot.. If u go back to stock let me know how that goes.. As of now I have 3g but no 4g and honestly I haven't had 4g on this phone since I got it 3 days ago
Edit... Just replaced my sim .. Good to go now make sure u try that b4 giving up
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've tried replacing my sim with no luck. Is there a step by step guide to return to s-on with the moonshine method?
Ruu back to stock, I had the same issue and had to do this to get it working again. You do NOT need to go back to s-on to run the ruu, but you do need to be running the stock hboot, so if you are on eng hboot make sure you flash back. .torrented has links in his signature for the ruu and the hboot
Sent from my DNA using Tapatalk 2
jamiethemorris said:
Ruu back to stock, I had the same issue and had to do this to get it working again. You do NOT need to go back to s-on to run the ruu, but you do need to be running the stock hboot, so if you are on eng hboot make sure you flash back. .torrented has links in his signature for the ruu and the hboot
Sent from my DNA using Tapatalk 2
Click to expand...
Click to collapse
I did that and it did not work I had to warranty replace it
Nothing will fix it sorry guys
Sent from my HTC6435LVW using xda app-developers app
How exactly is this an issue? Seems more like a cosmetic thing. Plus, your carrier could be renting towers from another carrier causing the phone to think it is roaming while it actually is not.
Sent from my GT-I9300 using xda app-developers app
eyegor said:
How exactly is this an issue? Seems more like a cosmetic thing. Plus, your carrier could be renting towers from another carrier causing the phone to think it is roaming while it actually is not.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
I don't think this has anything to do with renting towers. The same thing happened to me while I was flashing the GPE rom for the DNA. I spent two days trying to revert back to s-on and stock out of the box. Finally figured out how to do it. Next I took the ota and the triangle disappeared and showed 4G LTE.
It means your are stuck in roaming. You'll have to adb install stock hboot. Run the RUU. Let it boot. Once that's installed, you'll have to go into hboot and do a factory reset. After that, get the two OTA's. Then install custom recovery and your back in business. I've done it three times that I remember, maybe more, with success. If the first time factory reset don't work, so it again. Promise it will work. You don't have to lock or relock...
Sent from my HTC6435LVW using Tapatalk 4
planedoc said:
It means your are stuck in roaming. You'll have to adb install stock hboot. Run the RUU. Let it boot. Once that's installed, you'll have to go into hboot and do a factory reset. After that, get the two OTA's. Then install custom recovery and your back in business. I've done it three times that I remember, maybe more, with success. If the first time factory reset don't work, so it again. Promise it will work. You don't have to lock or relock...
I have the 'triangle' problem on a moonshine s-off DNA, but ADB doesn't recognize the phone, I only get "list of devices attached" and blank. It will connect in fastboot, but I've tried 3 computers, multiple usb ports, installing and updating drivers, etc. The device shows up in windows attached by usb and I can drag and drop files- any ideas? I am NOT a programmer by the way, so have been trying to rely on step by steps. Is there a way to fix it without adb? I guess even if I have to go back to box stock that will be better than no phone!
Also, the other things I've read do say you have to lock the bootloader in order to flash the stock hboot and run the RUU.
Thanks in advance-
Click to expand...
Click to collapse
Try these drivers for adb
https://db.tt/GMMd9IFX
Sent from my HTC6435LVW using Tapatalk 4
planedoc said:
Try these drivers for adb
Sent from my HTC6435LVW using Tapatalk 4
Click to expand...
Click to collapse
Planedoc, thanks for that, nogo however...when I tried to manually install those I got a Windows (7) error message saying "The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64 based systems."
I did try to install Koush's universal drivers as well via the exe he provided, and it still didn't recognize the phone in ADB, and then every time I plug the phone in it tries to install it's own drivers again, currently the DNA is showing up in device manager with device name: HTC6435LVW, Device type ortable devices, Location: Port_#0004.Hub_#0005, and driver files \Windows\system32\DRIVERS\WinUSB.sys and \Windows\system32\DRIVERS\WUDFRd.sys
Maybe I'll try my wifes macbook tonight and see if it shows up there.