Database Users

Easiest 4G Wimax Fix [Possibly]

I'd been having problems with 4G being stuck in scanning mode after 1.47 ROM updates and almost lost all hope when no solutions seemed to work.
UNTIL!!!!!!
1. Flash your 1.47 based ROM of choice.
2. Make sure 4G is turned off and boot into recovery and install latest Radio (http://forum.xda-developers.com/showthread.php?t=715485) and update profile then update PRL.
3. Make sure 4G is turned off and boot into Recovery and install latest Wimax Radio (http://forum.xda-developers.com/showthread.php?t=715485) and update profile then update PRL.
4. DELETE TREE.XML FILE IN THE FOLLOWING DIRECTORY: /data/misc/wimax/
How you delete this file is totally up to you. I personally deleted using adb shell, but Root Explorer from the Market should work as well.
5. Reboot & Turn on 4G
At this point the tree.xml file will be automatically generated and hopefully you will have full functioning 4G.
Good luck!

I will second this!
After i updated to Fresh's newest this morning I ran into this is as well. I used root explorer to delete the tree file and voila, functioning 4g goodness.

Worked for me as well! I'm glad it's this easy! Although, I just used ADB instead of Root Explorer, but they both work the same.

I thought the easiest way was to use Whitslacks start over method?

can someone post the adb commands for us cheap (don't want to spend the $ on root explorer) n00b's?

tx_jaycee said:
can someone post the adb commands for us cheap (don't want to spend the $ on root explorer) n00b's?
Click to expand...
Click to collapse
adb shell [enter]
cd /data/misc/wimax/ [enter]
rm name_of_your_tree_file.xml [enter]
[enter] = hit the enter key on your keyboard

tx_jaycee said:
can someone post the adb commands for us cheap (don't want to spend the $ on root explorer) n00b's?
Click to expand...
Click to collapse
here you go:
To figure out what your mac address is/file name is called:
Code:
adb shell
ls /data/misc/wimax
this will list all the files and folders in the wimax folder. look for the one ending with .tree.xml
Then to remove the file (assuming you're still in shell-denoted by the # sign):
Code:
rm data/misc/wimax/############.tree.xml

I wish someone could find a fix for the less common problem of 4g dropping and not reconnecting:
http://forum.xda-developers.com/showthread.php?p=7206162&posted=1#post7206162

Thanks initial. I'll have to wait till I head into town tomorrow. No 4G in the burbs yet.

If you say 4G works, can you say if you can connect, leave the 4G area for a little while, re-enter the 4G area, and have the phone re-connect 4G without getting stuck on "Scanning" or "Obtaining IP?"

I did the whitslack method flash DC 3.2.3 everything works great only problem I'm having is everytime I leave 4g area I have to reboot for 4g to work this goes for wifi wont start unless reboot Bluetooth wont conect unless reboot. Can someone please confirm if this is only on rooted roms or both stock and rooted.
Sent from my PC36100 using Tapatalk

initial said:
here you go:
To figure out what your mac address is/file name is called:
Code:
adb shell
ls /data/misc/wimax
this will list all the files and folders in the wimax folder. look for the one ending with .tree.xml
Then to remove the file (assuming you're still in shell-denoted by the # sign):
Code:
rm data/misc/wimax/############.tree.xml
Click to expand...
Click to collapse
If you want to delete the tree you can just use a wildcard without listing the directory first:
Code:
adb shell
rm data/misc/wimax/*.tree.xml

Good call, this is even easier. no need to list the directory anymore.

ewilson said:
I did the whitslack method flash DC 3.2.3 everything works great only problem I'm having is everytime I leave 4g area I have to reboot for 4g to work this goes for wifi wont start unless reboot Bluetooth wont conect unless reboot. Can someone please confirm if this is only on rooted roms or both stock and rooted.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
I don't think you're alone:
http://forum.xda-developers.com/showthread.php?t=717307

Holy ****ing ****. I've tried everything, and this actually worked? I ****ing love you. Kudos, man.

Posted here: http://forum.xda-developers.com/showthread.php?t=717307&page=3
swatspyder said:
I need someone to confirm, but I believe I found a FIX!!!
Requirements:
Your MSL code (See Here: http://forum.xda-developers.com/showthread.php?t=697487)
Instructions:
Turn OFF your 4G radio if it is turned on!
1) Click on phone and dial ##DATA# (##3282#)
2) Click on "Edit Mode"
3) Type in your MSL code (see above if you don't have it yet)
4) Click on the menu entry "WiMAX"
5) Scroll down the list and click on "WiMAX_Scan_Retry(s)"
6) Enter the number 15 and click "OK" (This equals 15 seconds instead of 300 seconds)
7) Scroll down the list and click on "WiMAX_Entry_Delay(s)"
8) Enter the number 0 and click "OK" (This equals 0 seconds instead of 300 seconds)
9) Press the "Menu" key and click on "Commit Modifications"
10) Grab a cup of coffee, get a bite to eat, or sit back and wait for your EVO to restart
Testing:
1) Go to your phone's settings and click on "Wireless & networks"
2) Scroll down and click on 4G settings
3) Click on 4G to turn it on and wait for the status to change to "Connected to Sprint"
4) Without touching any of the menu items, cover the top half of your phone with your hands until the status changes to "Scanning..."
5) Uncover the top of the phone and count the seconds until it says "Connecting to Sprint"
6) Realize that you no longer have to cycle the 4G radio to reconnect
Result:
After modifying my EVO and my girlfriend's EVO and inputting these changes, the phone will reconnect to the 4G tower in as little as 20 seconds!
Yes, 20 seconds, the most I have seen so far is 30 seconds after dropping the connection. This is a HUGE improvement over the 5+ minutes to reconnect (300+ seconds).
Click to expand...
Click to collapse

mrkmrk said:
Holy ****ing ****. I've tried everything, and this actually worked? I ****ing love you. Kudos, man.
Click to expand...
Click to collapse
Ditto.
I tried to skip a step because I was lazy and didn't work. Started from the begining and IT WORKED.

Just to clear things up, this will not fix any bad MAC addresses.
This is just a soft fix to get roms working (given that your MAC has not been corrupted)

Neotelos_com said:
Just to clear things up, this will not fix any bad MAC addresses.
This is just a soft fix to get roms working (given that your MAC has not been corrupted)
Click to expand...
Click to collapse
How do I fix the corrupted mac address? I think that may be what my problem is.
Edit: Nevermind, this fixed the problem; I have a weak signal in my house and it's still as bad as before the original wimax radio.

I have tried the method of the original poster and still have no luck. I rooted my phone after the OTA update using the simple root method. Prior to root my 4G was working.
I then installed BakedSnack 9.6 and since then 4G just sits on scanning. I have installed the latest radio/wimax roms multiple times and done everything else to no luck.
Can someone with a now working wimax post their output from logcat when they enable it. There is a thread in Q&A here: http://forum.xda-developers.com/showthread.php?t=725773 that explains the issue some of us are seeing.
For me and others with issues Logcat showing the error: E/Wimax ( 274): <DCP> Bad return status 0xffffffff
To capture a logcat connect do the following in adb:
Code:
adb shell
logcat > \sdcard\logcat.txt
immediately start wimax and leave it until it connects
You can now hit CTRL+C to kill logcat
The output of the logcat will be written to a text file called logcat.txt on the root of your sdcard instead of just scrolling by on your screen.
If someone here could do this it would be much appreciated and might help those of us still having issues.

Went to Sprint about RSA keys

So I lost my RSA keys a while back but had no idea because there was no 4g in the bay area at the time. well a week or two ago, I realized that yes, I had lost my RSA keys. now, I took my evo into a sprint store and asked em about it. I don't think any of them knew wth an rsa key was but they did tell me pretty much that they can't troubleshoot 4g yet because it "is still in beta".
I did not ask if they could recover them but I had been hoping they could give me a new evo (lol wishful thinking). I don't want to report my phone as stolen and pay $100 for a new one (I do have insurance) and sell my old one.. which couldn't be used on a network.
So what are my best options? any ideas?

Hold still until 4g launch and go back in..you might get a new phone.. I read some members in here got their evo replace.
Sent from my PC36100 using XDA App

tkhan02 said:
Hold still until 4g launch and go back in..you might get a new phone.. I read some members in here got their evo replace.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
2nd that
I had problems with mine connecting to 4g, wasn't broken, just couldn't connect properly. They wouldn't help me at first, after Sprint officially announced 4g around me, they got it taken care of. I think it is just that they have not trained techs on 4g if they aren't in a 4g market, just my guess.

We can use our RSA key on our EVO's. please tell me how so I can stop carrying around this stop key.

gmelchert said:
So I lost my RSA keys a while back but had no idea because there was no 4g in the bay area at the time. well a week or two ago, I realized that yes, I had lost my RSA keys. now, I took my evo into a sprint store and asked em about it. I don't think any of them knew wth an rsa key was but they did tell me pretty much that they can't troubleshoot 4g yet because it "is still in beta".
I did not ask if they could recover them but I had been hoping they could give me a new evo (lol wishful thinking). I don't want to report my phone as stolen and pay $100 for a new one (I do have insurance) and sell my old one.. which couldn't be used on a network.
So what are my best options? any ideas?
Click to expand...
Click to collapse
Question how can one tell if his/her Evo have a lost or missing RSA key?
I use to get 4g connection here in Martinez and now when trying to connect to sprint it immediately disconnected or never connect.
In terminal under wimax_mtd everything pass with no error. I'm thinking I might have got lucky a few weeks ago while sprint was testing it, who knows maybe now they cut it off.

I don't remember what the exact commands are but if you havent flashed anything new since it worked you should be good. im pretty sure it was the wimax radio.
anyways, I just used my insurance and ordered a new evo. I sold my old one for $200 as it can't be used on sprint anymore.
And yes I do know for a fact that my RSA keys are gone. I recovered my mac, and all that junk. Anyways.. can't wait for my new evo tomorrow

Possible help
I too thought I lost my RSA keys irretrievably from constant flashing/updating of ROMs/kernels (4G stuck on scanning). I tried to restore via ROM Manager to an earlier ROM which had successfully connected to 4G (WIFI tethering and everything) with no luck.
I then restored a NANDROID backup I had made and all was well.
I have read on net that a NANDROID b/u is a lower-level backup than backup afforded by ROM Manager, i.e., it backs up your RSA keys.
If you happen to have a NANDROID b/u, try restoring that first to see if it rectifies 4G problems.

jrotert said:
I too thought I lost my RSA keys irretrievably from constant flashing/updating of ROMs/kernels (4G stuck on scanning). I tried to restore via ROM Manager to an earlier ROM which had successfully connected to 4G (WIFI tethering and everything) with no luck.
I then restored a NANDROID backup I had made and all was well.
I have read on net that a NANDROID b/u is a lower-level backup than backup afforded by ROM Manager, i.e., it backs up your RSA keys.
If you happen to have a NANDROID b/u, try restoring that first to see if it rectifies 4G problems.
Click to expand...
Click to collapse
For that, you have to have amon ra 1.80 i think. And ive had 1.71 or something this whole time. Good luck to other people though!
Sent from my PC36100 using XDA App

So have you decided how you're going to root your new phone?
I got mine replaced about 3 weeks ago and have been in no hurry to root at the possible risk of losing my 4g keys again.
TBH, between launcher pro plus and a few others plain stock hasn't been all that bad, but I do plan to root again as soon as I can be sure I won't jeopardize my fogees.

nebenezer said:
So have you decided how you're going to root your new phone?
I got mine replaced about 3 weeks ago and have been in no hurry to root at the possible risk of losing my 4g keys again.
TBH, between launcher pro plus and a few others plain stock hasn't been all that bad, but I do plan to root again as soon as I can be sure I won't jeopardize my fogees.
Click to expand...
Click to collapse
I cant live without root lol. Yeah i will, i just wont flash any new wimax image of any sorts
Sent from my PC36100 using XDA App

theoner1 said:
Question how can one tell if his/her Evo have a lost or missing RSA key?
Click to expand...
Click to collapse
cat /dev/mtd/mtd0 | grep RSA
returned output show appear as this:
# cat /dev/mtd/mtd0 | busybox grep RSA
cat mtd0 | busybox grep RSA
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-----
#
the important lines are BEGIN RSA PRIVATE KEY and END RSA PRIVATE KEY.
If you have those two lines, your keys are still likely to be intact.
If those two lines are missing, your keys are likely missing.
/dev/mtd/mtd0 is where the wimax image is stored.

I was one of the lucky ones to be burned by Unrevoked with their bogus patch release. I waited patiently for 4g to launch in Boston. Once that occurred I walked into the sprint store after restoring my phone to default using this guide:
http://forum.xda-developers.com/showthread.php?t=780141
The hardest thing was getting the PRI up to date from 1.34. Doing ##3282# was the one that worked for me.
Make sure you get your MSL using the app from the Market.
I walked in and played dumb. I sat for about 2 hours and walked out with a new phone. It might be best for you to drop it off and come back when it's ready.

joeykrim said:
cat /dev/mtd/mtd0 | grep RSA
returned output show appear as this:
# cat /dev/mtd/mtd0 | busybox grep RSA
cat mtd0 | busybox grep RSA
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-----
#
the important lines are BEGIN RSA PRIVATE KEY and END RSA PRIVATE KEY.
If you have those two lines, your keys are still likely to be intact.
If those two lines are missing, your keys are likely missing.
/dev/mtd/mtd0 is where the wimax image is stored.
Click to expand...
Click to collapse
Hi, thanks so much for the help. Here what's mine say after that command.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I guess my key are okay then and probably sprint was just doing a test run that week my Evo had pick up. Oh well it was fun when i had 4g that week.
Thanks again for all the help you've provided in this community.

how
joeykrim said:
cat /dev/mtd/mtd0 | grep RSA
returned output show appear as this:
# cat /dev/mtd/mtd0 | busybox grep RSA
cat mtd0 | busybox grep RSA
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-----
#
the important lines are BEGIN RSA PRIVATE KEY and END RSA PRIVATE KEY.
If you have those two lines, your keys are still likely to be intact.
If those two lines are missing, your keys are likely missing.
/dev/mtd/mtd0 is where the wimax image is stored.
Click to expand...
Click to collapse
how do you do this i tried and no can do
update
i got it but no
-----BEGIN RSA PRIVATE KEY-----
-----END RSA PRIVATE KEY-----

Mine doesn't seem to have the "BEGIN RSA PRIVATE KEY"... on top of which, the clockworkmod recovery has some how messed thigns up (can't use the phone)...
RSA-REQUEST
RSA-REPLY
RSA-REJECT
RSA-ACK
RSA-REQUEST
RSA-REPLY
RSA-REJECT
RSA-ACK
RSA-1024
RSA
ReRSA
RSA requests
RSA replies
-----END RSA PRIVATE KEY-----

Im going to try to loose my rsa keys so i can get a new evo lol but I did scratch of the paint off my evo so they might not wanted who any one
Sent from my PC36100 using Tapatalk

How to type a "|" on the android keyboard
I cant figure out how to type a | on the android keyboard.
I am trying to check my RSA keys and cant seem to figure it out
cat /dev/mtd/mtd0 | grep RSA
Any help?
[EDIT] figured it out!

gmelchert said:
I don't remember what the exact commands are but if you havent flashed anything new since it worked you should be good. im pretty sure it was the wimax radio.
anyways, I just used my insurance and ordered a new evo. I sold my old one for $200 as it can't be used on sprint anymore.
And yes I do know for a fact that my RSA keys are gone. I recovered my mac, and all that junk. Anyways.. can't wait for my new evo tomorrow
Click to expand...
Click to collapse
So you sold your evo, called insurance and said what?

I followed with this Tutorial CM ROM and got my RSA Key safe in my SD Card
I never used unrevoked methods, toast rooting method + Amon_RA to the end

# cat /dev/mtd/mtd0 | busybox grep RSA
cat mtd0 | busybox grep RSA
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-----
-----BEGIN RSA PRIVATE KEY-----
-----END RSA PRIVATE KEY-----
#
2times in a row it says
-----BEGIN RSA PRIVATE KEY-----
-----END RSA PRIVATE KEY-----
how do i alter this extra entry and could this be the reason my 4g is fubar'd?
Little help? i know this is an old thread but any in sight would be great

Fix(maybe)for USB error 43/non working mass storage

If this thread has already been done or if this is old news please delete or move to the sfn section(stupid f******* n00b).
Anyway
bhfd64 over at fascinateforums.com helped me out with this one. So far I have had 2 phones give me this error on 3 different occasions. The first was returned before trying this(but with all other possible ways to fix it tried). The second phone had this happen twice. Once after flashing the quick media scan hack and once randomly. Tried the phone on a few different computers and got error code 43 or USB device not recognized/can not install drivers. I had all proper drivers installed.
You must be rooted for this to work. Do not use the quotations in the command script.
Download terminal emulator from the market
Enter command "su" to give super user permissions
Enter command "default_media"
Your phone will restart after the DM command. Once your phone reboots let the media scanner do it's thing, make sure USB debugging is on, and try connecting your phone to your computer. Your computer should now recognize your phone.
This has worked on two phones getting this error and I am just curious to see if it works on others having this problem. If it doesn't work for you I am sorry to get your hopes up with this thread.
Alpha Tappa Lambda

That command simply disables the fast_media scanner. It wouldn't do anything at all if you didn't have that installed.
Sent from my SCH-I500 using XDA App

fascinateforums! ftl!

Lol this is funny.
It would have no effect on usb mass storage. It would only remove the .nomedia file from system/media.
I agree there is a bug, but that is not the fix.
Sent from my SCH-I500 using XDA App

I didn't tell him that would fix his connection error. He said he started having problems after flashing the media hack, I simply told him how to undo it.

^^^ Agree with the above responses. More likely it was the reboot while the phone had USB debugging enabled that did the trick, or just the reboot by itself.

Yep reboot would do it, usually. Sometimes rebooting the computer
Sent from my SCH-I500 using XDA App

As in most threads the exchange of information got pretty confusing. Bh was respectful, polite and did a great job trying to understand the situation. He is an asset to the forum. The FF is a friendly place that will not ridicule or mock the inexperienced.
Either way...it is good that bob found a solution of sorts.

The second time I got the error 43/device not recognized error I did not have the quick media scan hack flashed.
Tried my fascinate on 3 different computers like before and a few other things and it would not connect. After re entering the default_media command my USB connected and worked fine.
So is what I did really not doing anything and this is just some huge coincidence?
Also bhd never said this would be a fix for this...he simply gave me the command to remove the fast media scan hack. He never told me this would fix a non working USB.
As stated in the first line of this thread...me=n00b. I was just excited because this has been a problem I have had with 2 phones on 3 different occasions and this has worked twice now. I saw a lot of posts about people here having this same problem so I figured I would post this here to see if it works for anyone else as it did for me.

Fix for those who cant get the generated beta key to work for revolutionary root!!!!

If you can not get the generated beta key to work for the 2.3.3 revolutionary root, and it keep saying invalid beta key???
The fix is you must generate the key from the same revolutionary zip file you downloaded can not be used from different one and copy and past it from the beta key box, just hilight and copy then open the revolutionary.exe and put your mouse pointer at the top of the cmd box not in it, then right click scroll to edit then paste.
Remember 99.9% of invalid beta key response is because it has to be regenerated from a fresh revolutionary download and from the same one so , if all fails delete all your revolutionary downloads and start of and do the copy and paste.

I don't see how its a 'fix,' since that's how its supposed to be done from the beginning. I think most people are getting errors because the missed a value, or didn't get the letter case correct, because it IS case sensitive.

I have only downloaded the revolutionary tool once. I generate a beta key from the website for each phone s/n. I have rooted 6 GB EVO's w/o downloading a new .zip
v3 and v4 use different beta keys so you need to make sure your revolutionary tool is v4
Sent from my EVO 4G

Please help!!!!!
1. Should the serial number in the terminal box match the serial number on the phone?
2. I have tried all methods of the beat key and its still saying invalid key. SOo my question is, is there another way to get a beta key?
3. Is there any other way besides revolutionary to root the evo 4g?
If you guys can please answer these questions i would highly appreciate it.

Should the serial number in the terminal box match the serial number on the phone?
Yes
2. I have tried all methods of the beat key and its still saying invalid key. SOo my question is, is there another way to get a beta key?
Are you going to the website to generate the beta key? Someone above noted to copy the serial number from the command prompt. That saves yourself from typos.
3. Is there any other way besides revolutionary to root the evo 4g?
No
If you guys can please answer these questions i would highly appreciate it.
Sent from my PC36100

I can say that I tried my key a total of six times and got the invalid key response every time until I copied and pasted on the seventh.
I knew beforehand that it was case sensitive because this was the second Evo I rooted. My brother (his phone) and I both checked the characters every time and they matched every time. The first four times I tried from one download, the last two I downloaded separate files.
My theory is that for some unknown reason (im not smart at this stuff) when you first get an invalid key, it might continue to be invalid until you do the copy / paste.
Not sure if thats possible, but thats my guess.

He is right this is not a fix but actually how it is supposed to be done. Also I have used the same zip on multiple phones so that is a false statement. Now if all drivers are loaded up properly you will see your serial number in the cmd window. If that number is different than the one on the back of the phone you may have bigger problems but I would go with the one seen in the cmd box
Enter you info properly and the beta key that is produced can be copied and then as stated in the revolutionary thread- right click on the task bar of the cmd and click paste to enter your beta information. Much safer than writing it down and hoping you entered it correctly
One other things- If you have an older Evo with an older HBoot then you can try Unrevoked root method if not then yes you have to keep trying Revolutionary
If anyone needs help with this task PM me.

I never had any problems with the beta key it worked the first time .
Sent from my PC36100 using Tapatalk

pfcland said:
I never had any problems with the beta key it worked the first time .
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Most don't but a few do seem to have issues

hey, new to this but this seemed to work for me.. i verified (several times) on my phone, and everything on there said that my hboot version was 2.15.. (I even verified by powering down, holding the power/volume down button), and revolutionary still did not work.. but i noticed on the revolutionary exe. it said my phone had the 2.16, so i tried a different beta key with the 2.16 hboot option and now it seems to be working.. not sure if this helps.... worked for me..

help new phone i done this b4 no problem now it wont work
put in new sn got new key and wont go in ugh

I am having a slightly different problem, and I think its probably user error. I downloaded revolutionary-0.4prep4.zip and unzipped it into a new folder on my desktop. I tried running the 'revoluationary' application (double clicked it), i get a cmd box that flashes and disappears and that's it. What am i doing wrong or missing? Running windows7 64, dl'd the windows version. my phone is on and connected via usb.
Thanx

Try right clicking and running as administrator.. Did you also install the drivers, and is HTC sync installed

I did try running as admin. And I thought I had installed the drivers. I do have HTC Sync installed, too. I'll double check the drivers, though.
---------- Post added at 12:59 PM ---------- Previous post was at 12:53 PM ----------
tammerlane said:
I did try running as admin. And I thought I had installed the drivers. I do have HTC Sync installed, too. I'll double check the drivers, though.
Click to expand...
Click to collapse
Ok, I reinstalled HTC Sync and drivers just to be sure, ran revolutionary as admin, and it still flashes onscreen and disappears. I've even tried a different USB port, for whatever that was worth. My phone itself it is set to charge only, does that make a difference?

DO NOT HAVE SYNC IMSTALLED! You need to remove it and any other HTC thing installed when you installed sync.
SYNC causes issues with revolutionary.
You should download the drivers from the wiki which can be gotten to by the revolutionary site. They are all you need.
Sent from my PC36100 using XDA App

ack, that was it. thank you for pointing me in the right direction. problem solved!

tammerlane said:
ack, that was it. thank you for pointing me in the right direction. problem solved!
Click to expand...
Click to collapse
You guys have got to stop improvising and follow directions to the letter....It works believe me I have done quite a few phones already. Use the right drivers and it will work out for you... Good luck...

Ok people getting an invaled beta key. I mad the mistake of downloading the file and using the s/n from the back of the phone under the battery. That is not the sn you need. After you download the file and run it under admin it will ask you for the beta key. The serial number you need is the number right before the space provided for the beta key. In other words the serial number you need is in the comand prompt not on the phone.

Mine won't even get past the waiting for device, I'm using the same method that I used on my wifes EVO and mine before I took it in for a screen replacement. Only difference is I'm no longer using my laptop. I'm using a desktop now and it ain't working.
Sent from my PC36100 using XDA App

Thanks a lot, you helped me fix my problem

How to access my Nook Glowlight 3 without registration?

Hello everyone,
Could you show me how to access my Nook Glowlight 3 without registration ?
Current firmware: 50.0.117
Thank you!

Well, I usually bypass the registration by popping the thing open, hooking up a 3.3V UART interface and getting a root console.
I've never really looked into if there were secret hand signals to bypass the registration.
So I looked at the disassembled code to see what was there.
All the OOBE (Out-of-box-experience) stuff is in /system/priv-app/bnereader.apk
The welcome screen is com.nook.app.oobe.o.WelcomeIntroActivity
This calls com.nook.viewutils.KeyHeldHelper to see if a particular button is held down
and also com.nook.viewutils.MultiClickListener to see if you tap three times.
I held the button and tapped three times and I got com.nook.app.util.DiagnosticActivity (as in the screen grab).
(You can also get here if you had a shell with)
Code:
# am start -n bn.ereader/com.nook.app.util.DiagnosticActivity
The problem? The key you have to hold down while tapping is the volume up key.
What? You don't have a volume up key?
The way I held down the volume key was with a USB keyboard, but that can only be done when you're rooted.
You could also pipe raw events to the input system if you were rooted.
I'm certainly interested in someone contradicting me, but this seems like a dead end.

Ok, I'm going to contradict myself.
As I said, the Welcome Intro screen needs the volume up key and a triple tap.
There is also the com.nook.app.oobe.RegisterUserLogin screen
This can be bypassed by holding the Lower Left and the Upper Right and giving a triple tap.
Obviously, this would only work on the Glow3 which has buttons.
Unfortunately, the Glow2 has the exact same code.
I can't seem to get this one to work on an (already rooted) Glow3.
If you have a Glow3 try the LL/UR/triple tap.
Yes, this should work on the Glow3 if you are at a page with email/password/etc.
I can't get there because I'm intercepted by the WiFi page.

It's not working
Hello
I have Nook Glowlight 3, I tried the LL/UR/triple tap many times on login screen. but it don't work
Thank you!
Renate NST said:
Ok, I'm going to contradict myself.
As I said, the Welcome Intro screen needs the volume up key and a triple tap.
There is also the com.nook.app.oobe.RegisterUserLogin screen
This can be bypassed by holding the Lower Left and the Upper Right and giving a triple tap.
Obviously, this would only work on the Glow3 which has buttons.
Unfortunately, the Glow2 has the exact same code.
I can't seem to get this one to work on an (already rooted) Glow3.
If you have a Glow3 try the LL/UR/triple tap.
Yes, this should work on the Glow3 if you are at a page with email/password/etc.
I can't get there because I'm intercepted by the WiFi page.
Click to expand...
Click to collapse

dnt83 said:
I tried the LL/UR/triple tap many times on login screen. but it don't work
Click to expand...
Click to collapse
You know, there are more secret touches and broken code all over.
I found another one, but I can't seem to get this to work either.
It's on this screen. There are four touch spots.
The bottom two when pressed and held should show a version number at the top center of the screen.
The top two, in some pattern (that I'm still looking at) should respond with the Easter Egg which gets you to the Diagnostic.
I'm working on it, but you can try too.
Ok, the top two spots, tap: L-R-L-R-L-R-L-R-L-R and you'll get to the Easter Egg.

Renate NST said:
You know, there are more secret touches and broken code all over.
I found another one, but I can't seem to get this to work either.
It's on this screen. There are four touch spots.
The bottom two when pressed and held should show a version number at the top center of the screen.
The top two, in some pattern (that I'm still looking at) should respond with the Easter Egg which gets you to the Diagnostic.
I'm working on it, but you can try too.
Click to expand...
Click to collapse
Thank you very much for your support
The bottom two it showed version.
I tried the top two it no work

dnt83 said:
I tried the top two it no work
Click to expand...
Click to collapse
Ok, the top two spots, tap: L-R-L-R-L-R-L-R-L-R and you'll get to the Easter Egg.

Renate NST said:
Ok, the top two spots, tap: L-R-L-R-L-R-L-R-L-R and you'll get to the Easter Egg.
Click to expand...
Click to collapse
Yes, it worked
Thank you very much!

Renate NST said:
Ok, the top two spots, tap: L-R-L-R-L-R-L-R-L-R and you'll get to the Easter Egg.
Click to expand...
Click to collapse
Hello
Could you show me next step to root it?
Thank you!

Renate NST said:
Ok, the top two spots, tap: L-R-L-R-L-R-L-R-L-R and you'll get to the Easter Egg.
Click to expand...
Click to collapse
Hello
I rooted and can work in adb shell, could you show me how to skip oobe?
Thank you!

dnt83 said:
how to skip oobe?
Click to expand...
Click to collapse
You need to install a launcher so that you have something "Home" to run.
Also:
Code:
# pm disable com.nook.partner/.oobe.WelcomeScreenActivity

Renate NST said:
You need to install a launcher so that you have something "Home" to run.
Also:
Code:
# pm disable com.nook.partner/.oobe.WelcomeScreenActivity
Click to expand...
Click to collapse
Yes, Thank you
I already installed custom firmware
Thank you very much for your support!

And if anybody is wondering, this works on all 5.0 Nooks, Glow2, Glow3, Glow4

Hi, I just picked up a new Nook Glowlight Plus (the 2019 7.8" model) and am trying to get started using it without the compulsory registration. My understanding from the start of this thread is that I should be able to root it, install an alternate launcher, disable the oobe.WelcomeScreenActivity, and I'm off to the races.
I have gotten as far being able to see the device with adb and connect to it, but I can't root it. adb seems to be working as normal (e.g., I can "adb shell" in as I would expect) but any attempts to push files with "adb push" fail. After attempting adb push, the device disconnects from adb and can no longer be seen until I physically unplug and re-plug it. Interestingly, adb push of a directory _does_ create the directory structure on the Nook -- just not any of the actual files...
Any help debugging this is appreciated...
A log of what I'm seeing is here:
https pastebin.com / ti4qB6Xr
(Sorry, I can't post direct links yet, and didn't want to spam the thread with a wall of text...)
Thanks!
---------- Post added at 02:58 AM ---------- Previous post was at 02:52 AM ----------
I should also mention that if I start to go through the on-device Welcome screen (choose timezone, choose wifi network and enter password), before actually getting to the login screen, I'm prompted to allow it to download a firmware update. I did not allow the update, in case a) the update changes something that would make rooting or installing a new launcher more difficult, and b) I don't want to miss the opportunity to note the download link and fetch an extra copy of the update in case it's useful later.
But if the download link is already known to the community, and if the update is unlikely to change anything that rooting/launchers depend on, I would also try letting it download, and then going to the login screen and trying the lower-left+upper-right+triple-tap bypass mentioned earlier in the thread.
Please let me know if I should try this.
Thanks.

So "adb push" is still not working, but I was able to root the device with shell chicanery. I tarred/gzipped the exploit payload, base64 encoded it, and used a shell loop to transfer it a line at a time:
Code:
c=1
cat nookrooter.tgz | base64 -e | while read line
do
echo "$c" >&2 ; c=$(expr $c + 1)
echo "$line" | adb shell 'busybox head -1 | busybox tee -a /data/local/tmp/nookrooter.tgz.b64 > /dev/null'
done
At ~64k base64-encoded lines, it took a bit over an hour to transfer. After base64-decoding, checking the md5 on both sides, and untarring in the right spot, it rooted just fine:
Code:
frappe/home/chris/nook/root-glp/rootGLP-3-13998# adb shell id -u
uid=0(root) gid=0(root)
That said, I'd still love to get some guidance on this device from folks who are familiar with it. Any idea why adb push might consistently fail? Is my basic understanding of how this whole process works is correct? Does it matters if I allow the device to complete the OTA firmware update before going farther?
My intent for the device is to use it as a standalone e-reader. I don't want to ever connect it to a network, nor to run any apps on it other than an e-reader. Public domain e-book content will be converted to EPUB (or, occassionally, CBZ or PDF) with Calibre (specifically the ebook-convert CLI) and copied via USB. I don't need to use "shelves" or whatever the Nook paradigm is for organization, nor will I "manage" the device with Calibre; "management" as such will be strictly copying individual files into a flat directory structure from the shell. I'm not too fussy about fonts, and don't need (or want) much more than the ability to click on a book and page-up/page-down through its contents.
I'm an experienced C/Unix developer, but have never used Android before.
Any help and pointers are much appreciated.
Thanks!

CrisCraigMorgan said:
But if the download link is already known to the community...
Click to expand...
Click to collapse
Yes, the manifest of the updates is discussed here: https://forum.xda-developers.com/nook-touch/general/software-updates-wifi-t4136097
CrisCraigMorgan said:
So "adb push" is still not working...
Click to expand...
Click to collapse
Strange. Why didn't you try adb install on the apk?
Maybe the adb on your host is broken. Try this.
adb push something
Did it fail?
adb devices, is it "gone"?
lsusb, really?
adb kill-server
adb devices, is it "back"?

Renate NST said:
Yes, the manifest of the updates is discussed here: https://forum.xda-developers.com/nook-touch/general/software-updates-wifi-t4136097
Click to expand...
Click to collapse
Thanks!
Renate NST said:
Strange. Why didn't you try adb install on the apk?
Click to expand...
Click to collapse
I'll try installing some apk that way. But in the case of the root payload, there are other files in addition to the one APK.
Renate NST said:
Maybe the adb on your host is broken. Try this.
adb push something
Did it fail?
Click to expand...
Click to collapse
Yup, I tried experimenting with other files, smaller files, individual files rather than directories -- all files failed (though, as noted, directories were created in the case of trying to push a local source directory).
Renate NST said:
adb devices, is it "gone"?
lsusb, really?
adb kill-server
adb devices, is it "back"?
Click to expand...
Click to collapse
I can run some more experiments later. The pastebin log above shows what I saw: immediately after any attempt to use "adb push", "adb devices" showed no devices. I didn't check usbconfig (FreeBSD here, not Linux, but that shouldn't matter), but there were no kernel messages about the device detaching (until I physically pulled the USB cable), so I suspect that the device would still have shown as attached.
Thanks!

So having rooted my Nook, I went ahead and installed the l2.apk launcher posted here https://forum.xda-developers.com/nook-touch/general/normal-launcher-nook-t3966911; disabled com.nook.partner/.oobe.WelcomeScreenActivity; renamed the bootanimation file; and rebooted.
When the device rebooted, it just displayed a message that said, "Unfortunately, com.nook.partner has stopped" and nothing else. Re-enabling com.nook.partner/.oobe.WelcomeScreenActivity restored it to its original boot-up behaviour.
So I think I must be missing something basic about the boot process, or rooting generally.
Should it be sufficient to just have another launcher installed? Do I have to do something particular to invoke it during the boot process?
Should I install TWRP? Alternate firmware, as described here: https://forum.xda-developers.com/nook-touch/general/gp-g3-gp7-8-twrp-alternative-firmware-t4074347 ?
Another question I have is about keeping root access across reboots. I can unpack the exploit in rootGLP-3.zip (from https://forum.xda-developers.com/nook-touch/general/how-to-root-set-nook-glowlight-3-t3802331) and run it to gain root; but when I reboot the device, I lose root again until I re-run the exploit. I tried setting /system/bin/busybox suid root, but then "busybox su" returns "unknown user root" -- I'm guessing because it's calling getpwuid(), but there's no /etc/passwd so the call fails. Could I just create /etc/passwd to define root? I also tried copying the "su" binary in the exploit dir into /system/chris/bin/ and setting it suid root, but this also fails (with no output). I could just write the three-line version of su that calls
Code:
setuid(0); exec("/system/bin/sh")
, but I have no idea how to compile code for this thing. Anything I'm missing here?
Thanks.

I played around a bit more with adb push. Still consistently failing, but restarting the local adb server does at least re-establish connectivity without unplugging/re-plugging the device. Definitely sounds like a problem with my local adb install rather than the device. Considering that I have a(n admittedly super-janky) method to transfer files, I don't feel a strong need to debug it right now.
Code:
frappe/home/chris/nook-13599# usbconfig | grep 1.6
ugen1.6: <BarnesAndNoble BNRV700> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA)
frappe/home/chris/nook-13600# adb devices -l
List of devices attached
MY_SERIAL_NUMBER device usb:1:6 transport_id:19
frappe/home/chris/nook-13601# adb push ReLaunchX_2.1.5-app-debug.apk /data/local/tmp/
adb: error: failed to copy 'ReLaunchX_2.1.5-app-debug.apk' to '/data/local/tmp/ReLaunchX_2.1.5-app-debug.apk': couldn't read from device
ReLaunchX_2.1.5-app-debug.apk: 0 files...ped. 7.6 MB/s (131056 bytes in 0.016s)
frappe/home/chris/nook-13602# usbconfig | grep 1.6
ugen1.6: <BarnesAndNoble BNRV700> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA)
frappe/home/chris/nook-13603# adb devices -l
List of devices attached
frappe/home/chris/nook-13604# adb kill-server
frappe/home/chris/nook-13605# adb devices -l
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
MY_SERIAL_NUMBER device usb:1:6 transport_id:1
frappe/home/chris/nook-13606# adb shell
[email protected]_6sl:/ # id
uid=0(root) gid=0(root)
[email protected]_6sl:/ # ^D

CrisCraigMorgan said:
Anything I'm missing here?
Click to expand...
Click to collapse
There's all sorts of "rooting" stuff here, but I just prefer a simple replacement of adbd in the ramdisk with one that doesn't switch to user "shell".
I don't want/need/like the chainfire stuff hanging around.
Sorry, I've lost track of where everything here is as I've never used any exploit method.
As for your launcher stuff, did you check logcat to see if there is any obvious reason why partner.apk is dying?
Code:
adb logcat
Have you tried:
Code:
adb shell am start -n com.android.launcher/com.android.launcher2.Launcher
Was the Launcher even installed correctly?
Code:
adb shell pm list packages -f launcher