Related
So last night I installed the latest radio version and everything was running fine, that is until I did a cache and dalvik wipe this evening. Now my 4g stays in scanning even though I connected to it earlier. I tried reflashing the wimax radio but that didn't help any, suggestions?
My thoughts are I either fubared my wimax or it's down in my area, as I'm just in a test area. I'm really hoping it's not the former.
This is happening a lot and often. Happens to users who root and users who do not root - its an HTC bug. Try downgrading then upgrading again.
Should I downgrade just my radio, or my pri and nv too?
werxen said:
This is happening a lot and often. Happens to users who root and users who do not root - its an HTC bug. Try downgrading then upgrading again.
Click to expand...
Click to collapse
uhm no. the only reason it happens to root users is they corrupt their hwid or manage to delete their rsa keys.
@OP
Run:
adb shell
$ su
# grep RSA /dev/mtd/mtd0
If you see
----RSA PRIVATE KEY BEGIN------
----RSA PRIVATE KEY END -----
at the end than your rsa keys are intact, if you don't then you'll never see 4g on that phone again, unless you get it refurbished by htc themselves.
Thanks last chance, just curious could a simple cache and dalvik wipe delete my rsa keys?
so i did the adb command and got grep RSA /dev/mtd/mtd0
RSA-REQUEST
RSA-REPLY
RSA-REJECT
RSA-ACK
RSA-1024
RSA-REQUEST
RSA-REPLY
RSA-REJECT
RSA-ACK
RSA-1024
RSA
ReRSA
RSA requests
RSA replies
-----BEGIN RSA PRIVATE KEY-----
-----END RSA PRIVATE KEY-----
so my RSA keys are ok and my 4g should still work then?
yes it should. unless you messed with your hwid, in which case you can apparantly delete the xml file if its the wrong hwid and it will reset it to the right one, getting your 4g back.
here is a thread you can look at for the info:
http://forum.xda-developers.com/showthread.php?t=773547
Its also maybe the 4g signal in your area probably its weak. That happens to me when im at home it says i have 4g available but getting scanning sometimes connecting then disconnecting but I tried at my work and i get full bar, then I updated the latest radio/wimax/pri and ota 3.29, now gives me 1 bar or sometimes if i move somewhere 3 bars the most at my house no more scanning. Also my battery life improves 4hrs running still in 80% didn't install advance task kill or disable the background..
Sent from my PC36100 using XDA App
Wow... Not in front of a computer, but ran those command on Terminal Emulator and did not see the RSA start and end thing so my 4g is dead..
Strange thing was that it was working one day and it just went out while I was using the phone normally :/
th3b055 said:
Wow... Not in front of a computer, but ran those command on Terminal Emulator and did not see the RSA start and end thing so my 4g is dead..
Strange thing was that it was working one day and it just went out while I was using the phone normally :/
Click to expand...
Click to collapse
Yeah i had the same thing happen. I had rooted w/ unrevoked, installed fresh 3.0 and i forget which kernel but it had worked for 2 weeks, then suddenly stopped. Not sure if i deleted the keys when i tried 50 rom and radio reflashes, but I ended up having to exchange the phone yesterday. I'm a little hesitant to reroot for now.
scooter185 said:
So last night I installed the latest radio version and everything was running fine, that is until I did a cache and dalvik wipe this evening. Now my 4g stays in scanning even though I connected to it earlier. I tried reflashing the wimax radio but that didn't help any, suggestions?
My thoughts are I either fubared my wimax or it's down in my area, as I'm just in a test area. I'm really hoping it's not the former.
Click to expand...
Click to collapse
What method did you use and what files did you use to up date your radio
Sent from my PC36100 using XDA App
From my experience, either flashing radio/wimax updates **** up the 4g, or flashing cm6. Not sure which one it is, but my keys got deleted when doing one of those.
th3b055 said:
Wow... Not in front of a computer, but ran those command on Terminal Emulator and did not see the RSA start and end thing so my 4g is dead..
Strange thing was that it was working one day and it just went out while I was using the phone normally :/
Click to expand...
Click to collapse
Maybe Last-Chance can clarify this, but maybe you should try running those commands from a computer. When I run it from an adb shell on my computer I get:
grep RSA /dev/mtd/mtd0
RSA-REQUEST
RSA-REPLY
RSA-REJECT
RSA-ACK
RSA-1024
RSA-REQUEST
RSA-REPLY
RSA-REJECT
RSA-ACK
RSA-1024
RSA
ReRSA
RSA requests
RSA replies
-----BEGIN RSA PRIVATE KEY----
-----END RSA PRIVATE KEY-----
Which seems to suggest that my RSA keys are fine. But when I run the command from a terminal emulator on my phone I only get
<rsa>
</rsa>
Which output should I believe here? I have no idea
darkkterror said:
Maybe Last-Chance can clarify this, but maybe you should try running those commands from a computer. When I run it from an adb shell on my computer I get:
grep RSA /dev/mtd/mtd0
RSA-REQUEST
RSA-REPLY
RSA-REJECT
RSA-ACK
RSA-1024
RSA-REQUEST
RSA-REPLY
RSA-REJECT
RSA-ACK
RSA-1024
RSA
ReRSA
RSA requests
RSA replies
-----BEGIN RSA PRIVATE KEY----
-----END RSA PRIVATE KEY-----
Which seems to suggest that my RSA keys are fine. But when I run the command from a terminal emulator on my phone I only get
<rsa>
</rsa>
Which output should I believe here? I have no idea
Click to expand...
Click to collapse
Yeah just check on my PC and I don't have the
-----BEGIN RSA PRIVATE KEY----
-----END RSA PRIVATE KEY-----
Oh well though, getting a new phone then.. One question though, if I re-root and nandroid backup with RA Recovery v1.8.0 will it backup those keys and restore them if something goes wrong in the future?
darkkterror said:
Maybe Last-Chance can clarify this, but maybe you should try running those commands from a computer. When I run it from an adb shell on my computer I get:
grep RSA /dev/mtd/mtd0
RSA-REQUEST
RSA-REPLY
RSA-REJECT
RSA-ACK
RSA-1024
RSA-REQUEST
RSA-REPLY
RSA-REJECT
RSA-ACK
RSA-1024
RSA
ReRSA
RSA requests
RSA replies
-----BEGIN RSA PRIVATE KEY----
-----END RSA PRIVATE KEY-----
Which seems to suggest that my RSA keys are fine. But when I run the command from a terminal emulator on my phone I only get
<rsa>
</rsa>
Which output should I believe here? I have no idea
Click to expand...
Click to collapse
I'm not even sure if checking the RSA makes a difference or not. I had a similar issue two weeks ago and when I checked my RSA in terminal emulater, I had the same result <rsa> </rsa>. My phone would detect the 4g connection, but hang there while trying to connect to the network. Two days later my 4g started working again. I was also in a test area where the 4g isn't officially released yet. It might be worthwhile to call a Sprint CSR and find out if there is a trouble ticket for one of the towers in your area.
If you look in your nandroid folder on /sdcard....look in your backups and see if you have wimax.img. if you do....try to flash that....ANY WORKING BACKUP OF WIMAX.IMG WILL HAVE *YOUR* RSA KEYS IN IT.
thankfully it appears the tower in my area is down, my buddy at work just picked up an EVO yesterday, so it's totally stock and everything. When he cam in today i Had him check his 4G, and much like mine it was just scanning.
th3b055 said:
Yeah just check on my PC and I don't have the
-----BEGIN RSA PRIVATE KEY----
-----END RSA PRIVATE KEY-----
Oh well though, getting a new phone then.. One question though, if I re-root and nandroid backup with RA Recovery v1.8.0 will it backup those keys and restore them if something goes wrong in the future?
Click to expand...
Click to collapse
If you had a nandroid back up prior to the point of your rsa keys getting deleted, it *should* get them back. It might not, but it should.
As for terminal emulator, you can't run it there, cause you need to be in debug mode or something. Hence why you need adb.
Another thing to check is your MAC address. It should be same as the one printed on the label under your battery. As for saving your keys, get RA 1.8.0 recovery. If your keys are good save that wimax.img file someplace safe. For that matter save the whole nandroid of the ROM in a safe place. Lucky for me I got my replacement the evening that Froyo got root. So I saved the whole nandroid of my rooted stock ROM in several places.
About your 4G signals. Unless you are in a listed 4G market your signal is not guaranteed. In my area at least 4G was sporadic at best at first. Now that more towers are coming online (most cases it is just adding more equipment into an existing site) I am getting a better signal, or even signal at all. It is no easy feat getting a new tower in the air. I've done a couple, and they are lots of work especially a cell tower.
Might *fix* your Wimax "scanning" problem
scooter185 said:
So last night I installed the latest radio version and everything was running fine, that is until I did a cache and dalvik wipe this evening. Now my 4g stays in scanning even though I connected to it earlier. I tried reflashing the wimax radio but that didn't help any, suggestions?
My thoughts are I either fubared my wimax or it's down in my area, as I'm just in a test area. I'm really hoping it's not the former.
Click to expand...
Click to collapse
I've had this happen to me a couple of times, although a lot less so in the last month.
All I've had to do was:
1) turn off Wimax
2) delete /data/misc/wimax/[WIMAX-MAC-ADDRESS].tree.xml
Or, if it makes you feel better, rename the file.
3) turn on Wimax
This forces the wimax subsystem to re-generate the xml file, and in the process fixes my wimax "persistent scanning" problem pretty much every single time.
I got this tip somewhere else on xda a while ago.
I was finally able to obtain the PRL file for 60677. I have updated my site with the new changes in the file. Check my sig for the files.
No link to download it?
The analysis or PRL itself?
prl itself
Thanks, updaed my prl
Sent from my SPH-D700 using XDA App
digiblur said:
I was finally able to obtain the PRL file for 60677. I have updated my site with the new changes in the file. Check my sig for the files.
Click to expand...
Click to collapse
I really appreciate your work. Being a cell phone network junkie I think this is great to have.
I stay on top of updating my PRL but could you explain to me what exactly this info is telling us?
Example:
SID: 4183 - Sprint PCS - San Francisco Oakland San Jose CA - Priority: More - Roaming Ind:Native
1X Scan: PCS/50 PCS/25 PCS/200 PCS/100 PCS/75 PCS/350 PCS/925 PCS/325 PCS/375
EV Scan: Sprint - 0084:0AC0(Same) - PCS/25 PCS/50 PCS/150 PCS/475 PCS/550 PCS/625 PCS/650 PCS/375
Click to expand...
Click to collapse
digiblur said:
The analysis or PRL itself?
Click to expand...
Click to collapse
im looking for the prl itself to write in QPST
found it: attached
so what i do with this???
Ree$e said:
so what i do with this???
Click to expand...
Click to collapse
dont try to flash the zip i posted in CWM or anything.... you have to download qualcomm product support tools
extract the zip file i had to your desktop
turn usb debugging on your phone
adb shell getprop ril.MSL
write down the 6 digit number
disconnect usb cable
turn off usb debugging
type ##8778# in your dialer
make USB and UART modem instead of pda
plug phone into usb (it'll install drivers you might need to restart pc i forget)
open QPST, add port, uncheck the "show only" box click the usb port you plugged your phone into
on the top click start clients//service programming
click your phone and start
go to the roam tab
hit read from phone
enter your MSL 6-digit #
in the "enable perferred roaming" box click browse and point to the prl file you want
click write to phone, it will reboot, and your prl is updated
edit: forgot to mention after you're done enter ##8778# again and change usb back to pda (uart stays as modem)
You guys are aware that a 61677 PRL is up and out right?..
If not you can check it out in the Optimus V forum: http://forum.xda-developers.com/showthread.php?t=991668
Been doing major testing on both the 61 & the 60 version I see no difference as of yet..
However the code is different so something must be up with it..
61 is a modded one
does it add 3g roaming?
Can we use that one?
churro7 said:
61 is a modded one
does it add 3g roaming?
Click to expand...
Click to collapse
Sent from my Epic 4G using XDA Premium app
jeffyv2 said:
Can we use that one?
Sent from my Epic 4G using XDA Premium app
Click to expand...
Click to collapse
Don't, Virgin Mobile only uses Sprint Towers. No roaming is allowed on Virgin Mobile.
i updated to the 60677 and everything seems to work fine and i live in the dallas tx area so if anyone wants to update to 60677 and lives in the dallas area they can !!! good luck
I do everything correctly when starting perm root...then i get to terminal emulator and after I do "sh root.sh" I get tgis message:
/sdcard/root/wpx.ko failed (function not implemented)
Any ideas as to whats going on here? Ive never had it do this when rooting .
*edit* went into the store and got a new one, still doing the same error. So, any ideas what's up?
Sent from my HTC Glacier using XDA App
bballcat03 said:
I do everything correctly when starting perm root...then i get to terminal emulator and after I do "sh root.sh" I get tgis message:
/sdcard/root/wpx.ko failed (function not implemented)
Any ideas as to whats going on here? Ive never had it do this when rooting
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
From some on going research by the fine science team here at the XDA research facility it appears as if you may have a bad eMMC.
There are are two different rooting methods ./gfree and root.sh. It's becoming clear that if you have problems with the root.sh method, Which is a scripted out version of what you are trying to do, and if it doesn't work it's most likely your phone has faulty hardware that will not allow it to work properly. IF i were in your shoes i'd get ADB up and running (if you dont already) then look @ the "post your eMMC thread" to see if you have a bad one or not. If you have a good one use the ./gfree method. If you have a bad one i'd reconsider rooting your phone as the chances of bricking goes up alot.
I am only on my first day of having this phone, so if I have a bad one, I could just take it back to tmobile and get a new one for free.
If its good, can I do the gfree on my mac? Cause I dont have windows.
Sent from my HTC Glacier using XDA App
How do I do ADB for MAC?
The thread on here is for windows....
So I went to the T-Mobile store today and got a new one...so this is 2 MT4G's in 24 hours...brought it home...SAME THING
what are the odds off two bad emmc's??? Something's fishy here, wouldn't one think?
can you post the link of the guide your following .Also have u set up adb on mac
I am using "the unlockr's" method to temp root, and then followed by the perm root method...it's in the perm root method that this is happening obviously.
No, trying to get that figured out on how to do it on my mac right now
jeff7790 said:
can you post the link of the guide your following .Also have u set up adb on mac
Click to expand...
Click to collapse
http://esausilva.com/2010/10/02/how-to-set-up-adb-android-debug-bridge-in-mac-osx/
Have you tried visionary method for your phone. I know it doesn't work for everyone, but it worked perfectly for me. Saved me quite a few steps, too.
Did u CD/ sdcard first
Sent from my HTC Glacier using XDA App
Make sure that you have both
Code:
Run VISIONary.sh
and
Code:
Set /System to r/w
both check marked.
If those are checked it will not work
also make sure you have ADB debugging turned on
Options > application management > development > should be the top option.
rockstarar said:
Did u CD/ sdcard first
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
No...what is that?
Sent from my HTC Glacier using XDA App
neidlinger said:
Make sure that you have both
Code:
Run VISIONary.sh
and
Code:
Set /System to r/w
both check marked.
If those are checked it will not work
also make sure you have ADB debugging turned on
Options > application management > development > should be the top option.
Click to expand...
Click to collapse
I run visionary first in the temp root method and that works just fine. Installed screenshot it to verify I had root access
Sent from my HTC Glacier using XDA App
bballcat03 said:
I run visionary first in the temp root method and that works just fine. Installed screenshot it to verify I had root access
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
I understand your theory behind wanting to make sure you have root access. But unless you change the /system files to a read/write point it will not allow you to make changes to it. Which is required for the command to work. If it's not working there is a GOOD chance you may have a bad eMMC and i wouldn't advise rooting it.
neidlinger said:
I understand your theory behind wanting to make sure you have root access. But unless you change the /system files to a read/write point it will not allow you to make changes to it. Which is required for the command to work. If it's not working there is a GOOD chance you may have a bad eMMC and i wouldn't advise rooting it.
Click to expand...
Click to collapse
Would I really have a bad emmc on a 24 hour old phone? I thought they went bad when the phone got old?
Sent from my HTC Glacier using XDA App
bballcat03 said:
Would I really have a bad emmc on a 24 hour old phone? I thought they went bad when the phone got old?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Try this guide. I have the bad eemc too and it worked fine.
http://www.youtube.com/watch?v=XDFMR4UUdt0
That is the unlockr way... had the same issue
Sent from my HTC Glacier using XDA App
Okay so I ,about a month ago, lost my WiMax RSA keys by trying to flash a test ROM.
After many trials, and errors and many people helping me I Finally found a way to get mine back.
It is actually a very simple method. I was originally not going to share this method because it does not seem many people have lost their RSA keys until today I realized I was wrong.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++
First off what you will need!
-YOU NEED AN OLD CWM BACKUP FROM WHEN YOU HAD WIMAX KEYS
-You need TWRP recovery flashed
and you will need a TWRP backup with Wimax AFTER it was broke.
-You need to download Notepad++
-Now for a litttle info
CWM DOES backup the wimax keys. (commonly mistaken)
TWRP and CWM use the SAME kind of backups and code. except twrp just saves them in win format.
Although CWM backs your keys up they provide NO way to restore them (although twrp does)
So what do we need to do?
-Convert CWM backup along with md5 for TWRP.
PRIOR TO THIS MAKE A NANDROID BACKUP WITH TWRP AND MAKE SURE YOU SELECT TO BACKUP WIMAX (i know it seems pointless to make a bad wimax backup...just do it...if you ONLY want to backup wimax and nothing else thats fine.
Estimated Completion time? About 10 min
Difficulty: If you can read,type,and click a mouse button your fine.
++++++++++++++++++++++++++++++++++++++++++++++++
First. put BOTH Backups in seperate folders on your desktop.
Now download Notepad++
Now in the CWM backup folder you will see a Md5 file....open that up in notepad++.....You will see it has about 4 rows of md5 checks and a name by each one.
Find the "WiMax" labeled on and copy that string of characters.
Now in your TWRP folder with the backup you made open up (in notepad++) "wimax.eemc.win.md5" and delete the string of character (not the label!) and replace it with the ones you copied.
Now go back to your cwm backup and rename your backup to exactly what it says in your twrp folder for wimax and just change the extension to ".win" (my twrp wimax was called "wimax.emmc.win" but it might be different for you) now with the renamed file (with new extension" delete the one we made with twrp (only the win file NOT the md5) and copy the .win we just made from cwm and copy it to twrp backup folder.
Now in twrp restore your backup but ONLY have it restore wimax.
Glad you finally restored your wimax bro!
Sent from my PG06100 using XDA Premium App
Yay no longer locked. This was still locked from when I had all my threads closed. Glad Andy opened so quick. Thanks Andy!
I believe someone was looking for this
Sent from my PG86100 using Tapatalk 2
notsointeresting said:
Yay no longer locked. This was still locked from when I had all my threads closed. Glad Andy opened so quick. Thanks Andy!
I believe someone was looking for this
Sent from my PG86100 using Tapatalk 2
Click to expand...
Click to collapse
Saved my life and kept me from getting a samdung device
Thanks bro!
jesuscash said:
Saved my life and kept me from getting a samdung device
Thanks bro!
Click to expand...
Click to collapse
Glad it helped someone! :beer:
Sent from my PG86100 using Tapatalk 2
Thanks notso
wait.. how do you lose your wimax keys got me a bit lost on this one never head of this before
I know one way some people loose them is to flash a zip that isn't intended for our phone and didn't look at the updater-script to see that it wipes different partittions ment for another phone, which happen to be the partition the wimax keys are on. A.k.a the superwipe.zip that is floating around the web.
There is also other ways to loose the keys, sometimes recoveries don't play nice and will delete them. That is why many guides say the first thing to do after rooting is to backup everything including your wimax keys. I do believe the shiftrr.exe even has the option to back them up.
Sent from my PG06100 using Tapatalk 2
Yup I lost my wimax keys flashing a test 3.5 ROM for newtoroot (way before the one he released) guess the updater script wiped it.
My biggest complaint is that even though cwm backs wimax keys up. It provides no way to restore it. I just never understood lol
Sent from my PG86100 using Tapatalk 2
one_love_420 said:
I know one way some people loose them is to flash a zip that isn't intended for our phone and didn't look at the updater-script to see that it wipes different partittions ment for another phone, which happen to be the partition the wimax keys are on. A.k.a the superwipe.zip that is floating around the web.
There is also other ways to loose the keys, sometimes recoveries don't play nice and will delete them. That is why many guides say the first thing to do after rooting is to backup everything including your wimax keys. I do believe the shiftrr.exe even has the option to back them up.
Sent from my PG06100 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, I'm pretty sure I derped that partition when trying to port ICS AOSP roms
I remember this thread. It was classic.
VICODAN said:
I remember this thread. It was classic.
Click to expand...
Click to collapse
LOL Oh yea. All the nights on IRC
Sent from my PG86100 using Tapatalk 2
notsointeresting said:
LOL Oh yea. All the nights on IRC
Sent from my PG86100 using Tapatalk 2
Click to expand...
Click to collapse
You know the other day I was messing with WiMax on my laptop and I connected to Sprint and I thought about you and if I could export my Shift's WiMax key and get it on my laptop some how.
VICODAN said:
You know the other day I was messing with WiMax on my laptop and I connected to Sprint and I thought about you and if I could export my Shift's WiMax key and get it on my laptop some how.
Click to expand...
Click to collapse
LOL
I doubt it. Each key are specific to a device. I remember people doing some crazy **** like buying a used evo to replace the chip and THEN transfer the WiMax keys, or something like that. But that's before I wrote this or they made absolutely no backup anywhere.
Sent from my PG86100 using Tapatalk 2
What happened to the IRC channel anyway?
It's so void now.
Forcing me to come to the forum
nullstring2 said:
What happened to the IRC channel anyway?
It's so void now.
Forcing me to come to the forum
Click to expand...
Click to collapse
I stopped joining for a while, people got new phones, etc etc.
Ok everyone, I don't start new topics often but I've hit a brick wall on this one.
I've used terminal plenty of times before. But today I tried using it to flash a recovery image and when I entered terminal the line started like this
sh-3.2$
After I type SU which I also noticed I can't enter in lower case just upper. Terminal just won't let me. I then press enter and I get this
sh: SU: command not found
Refer to screen shots below.
Also, I know I have root. I've installed busy box, superuser is giving root access to apps and I can also write to system.
I'm on torxx venom rom 1.0.0.
Sent from my HTC myTouch 4g using xda premium
coupetastic-droid said:
Ok everyone, I don't start new topics often but I've hit a brick wall on this one.
I've used terminal plenty of times before. But today I tried using it to flash a recovery image and when I entered terminal the line started like this
sh-3.2$
After I type SU which I also noticed I can't enter in lower case just upper. Terminal just won't let me. I then press enter and I get this
sh: SU: command not found
Refer to screen shots below.
Also, I know I have root. I've installed busy box, superuser is giving root access to apps and I can also write to system.
I'm on torxx venom rom 1.0.0.
Sent from my HTC myTouch 4g using xda premium
Click to expand...
Click to collapse
Have you tried a different version of TE?
Yes I have. They all give me the same results.
Sent from my HTC myTouch 4g using xda premium
coupetastic-droid said:
Yes I have. They all give me the same results.
Sent from my HTC myTouch 4g using xda premium
Click to expand...
Click to collapse
Try a different keyboard. That caps business is your problem, I bet.
estallings15 said:
Try a different keyboard. That caps business is your problem, I bet.
Click to expand...
Click to collapse
That's what I thought at first. But then I remembered that terminal shell commands never started with sh-3.2$
Terminal always opened with just ($) and when I typed su and pressed enter, it would just grant permissions and the next line would just be a (#)
From there I was able to start the commands.
But I will try another keyboard just in case.
Sent from my HTC myTouch 4g using xda premium
The prompt doesn't matter - it's an easily changeable property.
Linux (and Android) is case-sensitive, SU isn't su.
That's it.
Thank you guys for the suggestion. It was the keyboard. I should've tried a different keyboard first. I just really didn't think the keyboard could had been the problem since I've used terminal on this rom with the stock keyboard before with no problems.
Some thing must be wrong so I'm just going to flash the rom fresh again.
Thanx again.
Sent from my HTC myTouch 4g using xda premium