Password doesn't work

[Yessos]

I upgraded from stock firmware using lede-17.01.4-ramips-mt7620-u35wf-sysupgrade.bin as it says in the instruction, but upon login I met with the following message: Non of the usual passwords work like "password", "root", "12345678" or empty. I am completely locked out and reset button now does nothing for some reason. @arvati please help.

[arvati]

For first login password is empty. password for wifi is "password" try access 192.168.1.1:4200 with root and blank password (none)

[recent2018]

does not work. port 4200 is closed. Only SHH (22), WEB (80) and rsync (873) are available

same problem. I can not log into the system in any way. what do I do not understand. Almost everything has already been tried.

there is only hope for soldering the RS232 port. and through it to make a hard reset. but how to find it on the board? there are two groups of contacts. clearly one of the groups is 232 port. but which one? and how to identify?

What should I do?

[recent2018]

measured the readings on the pins on the board. by the values of RS232 is obtained in the photo Tx = 3.02, Rx = 0.26 What do you think ? the rest of the pins do not seem to fit

http://4pda.ru/forum/dl/post/13799567/IMG_20180907_1631468.jpg http://4pda.ru/forum/dl/post/13799578/IMG_20180907_1632351.jpg

[recent2018]

yesssss !!!!!!! everything worked out. so to reset to factory settings and remove the garbage from the previous firmware to unbrick U35WF. When the password is not recognized and is not offered to change it. RS232 should be soldered and the connector should be pulled out. just in case. http://4pda.ru/forum/dl/post/13822143/IMG_20180907_163146.jpg speed on port 57600 get passwordless root login then we enter two commands

firstboot reboot

and voila! http://cs5-3.4pda.to/13822032.jpg good luck to all.

[arvati]

I think to bake an firmware that forces cleans everything of previous firmwares to burn first and another firmware to burn on top of this with normal behavior. I appreciate if anybody could point out an way to do that.

[recent2018]

I found rs232. and caught on him. Attached to the letter are pictures of how to pick up the RS232. https://cs5-3.4pda.to/13822143. https://cs5-3.4pda.to/13822147.jpg

adapter for com https://ae01.alicdn.com/kf/HTB109_Oc56guuRjy1Xdq6yAwpXaW.jpg

port speed 57600

Received a root without a password. then you can do anything. hard reset - firstboot reboot

firmware to any other via the console ~ mtd_write -r write /tmp/openwrt-ramips-mt7620-u35wf-full-squashfs-sysupgrade.bin Firmware_Stub

Ademar Arvati wrote:

I think to bake an firmware that forces cleans everything of previous firmwares to burn first and another firmware to burn on top of this with normal behavior. I appreciate if anybody could point out an way to do that.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/vanaware/openwrt/issues/1#issuecomment-435587259, or mute the thread https://github.com/notifications/unsubscribe-auth/AneL_hFk6Zt8_aUXm0R2LFm2E7tz_qIUks5urZdTgaJpZM4WIFJf.

[netrezver]

hello, I am experiencing the same issue after upgrading to 17.01.4-ramips-mt7620. Also cannnot login to the device anymore... Havent used my device even for a day.. big dissapointment.. Why publish the firmware which completely bricks the device? Smoldering etc is not on my level of competence, so any other suggestions?

[recent2018]

solder the RS232 as shown in the picture in my letter. This will be a login without a password. next firstboot

netrezver wrote:

hello, I am experiencing the same issue after upgrading to 17.01.4-ramips-mt7620. Also cannnot login to the device anymore... Havent used my device even for a day.. big dissapointment.. Why publish the firmware which completely bricks the device? Smoldering etc is not on my level of competence, so any other suggestions?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/vanaware/openwrt/issues/1#issuecomment-443499560, or mute the thread https://github.com/notifications/unsubscribe-auth/AneL_hQ8br8p5riE1eK8rq2kYxNzdL7lks5u07YagaJpZM4WIFJf.

[omishra2002]

Soldering those tiny wires and connecting it to the RS232 to USB adapter is the solution now.

[recent2018]

Yes. This is the only option. Unfortunately. but it works.

omishra2002 wrote:

Soldering those tiny wires and connecting it to the RS232 to USB adapter is the solution now.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/vanaware/openwrt/issues/1#issuecomment-443695531, or mute the thread https://github.com/notifications/unsubscribe-auth/AneL_t3oyPsIRf73wskURoLiHyazOIDWks5u1Rq_gaJpZM4WIFJf.

[omishra2002]

Yes, I already tried it and it works. For the safe side, I soldered female type pin headers on each of the wires and hidden it inside the enclosure. Now if required in future then I can use it. Thank you for the help and the document here.

[marcopolo11]

@Omishra2002, what do you call that serial cable? Can't I use a normal USB cable to connect directly?

[recent2018]

Of course not. there is only RS232 .. on USB you need an adapter

marcopolo11 wrote:

@omishra2002 https://github.com/omishra2002, what do you call that serial cable? Can't I use a normal USB cable to connect directly?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/vanaware/openwrt/issues/1#issuecomment-446289839, or mute the thread https://github.com/notifications/unsubscribe-auth/AneL_nYe-VsoSGw6LeMrEGFuBV_a-zCmks5u3-vdgaJpZM4WIFJf.

[marcopolo11]

Of course not. there is only RS232 .. on USB you need an adapter marcopolo11 wrote: … @omishra2002 https://github.com/omishra2002, what do you call that serial cable? Can't I use a normal USB cable to connect directly? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AneL_nYe-VsoSGw6LeMrEGFuBV_a-zCmks5u3-vdgaJpZM4WIFJf.

I bought one from amazon last night and received today, quite sure this will solve my trouble. https://images-na.ssl-images-amazon.com/images/I/51LacAlxteL.SL1024.jpg

[recent2018]

good luck ! and happy New Year ! :)

[marcopolo11]

Thanks god you are online, I am struggling with so small solder points (never soldered this small.

I have your image marking Tx Rx and Gnd however image shows 2 wires going out of Tx, How many wires I need to solder and where do I need to plug on the USB?

[recent2018]

look at the photo. need three wires. Tx, Rx and Gnd Connect accordingly to the adapter on usb. Don't forget Tx should be on Rx, and Rx on Tx. it is reception and transmission. if nothing happens swap them. it's not scary :)

marcopolo11 wrote:

Thanks god you are online, I am struggling with so small solder points (never soldered this small.

I have your image marking Tx Rx and Gnd however image shows 2 wires going out of Tx, How many wires I need to solder and where do I need to plug on the USB?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/vanaware/openwrt/issues/1#issuecomment-446621775, or mute the thread https://github.com/notifications/unsubscribe-auth/AneL_i_yNBG6FJGX5T-U0x-8MM7u3Ymrks5u4Ry3gaJpZM4WIFJf.

[marcopolo11]

Sorry I am back again, soldered successfully with shaky hands however connection still not working. Have tried to swap TX and RX on adapter

Setup COM port and speed on Device Manager, COM3 (and later 16) and Speed 56700 PuTTY does not show anything except for green cursor. Won't let me type anything (maybe because connection never established.

Any idea what I might be doing wrong? Should I try to connect the TX wire on rest of the 3 solders? Also, DO i need to attach board's connections flex with the rest of the device?

[recent2018]

it is natural to collect everything. food DC is needed. Well, in general - the interface implies that this is only an interface. the rest of the system must be fully assembled.

marcopolo11 wrote:

Also, DO i need to attach board's connections flex with the rest of the device?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/vanaware/openwrt/issues/1#issuecomment-446674948, or mute the thread https://github.com/notifications/unsubscribe-auth/AneL_iM0RZuXYSaHAc50d6fla5G19jCQks5u4T5igaJpZM4WIFJf.

[marcopolo11]

I am sorry, I could not understand.

By the way, later, I managed to connect TX wire on second solder and connected the adapter however putty still does not connect the session. All I see is a cursor (waiting for connection).

[recent2018]

SPEED ON THE PORT EXHIBIT. IN TWO PLACES. and everything will turn out.

marcopolo11 wrote:

I am sorry, I could not understand.

By the way, later, I managed to connect TX wire on second solder and connected the adapter however putty still does not connect the session. All I see is a cursor (waiting for connection).

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/vanaware/openwrt/issues/1#issuecomment-446875513, or mute the thread https://github.com/notifications/unsubscribe-auth/AneL_oklgxCIjNbR5CdJ2nVMq5ZoDK_nks5u4gizgaJpZM4WIFJf.

[marcopolo11]

I know COM speed is 57600 and I setup the same way. What do you mean by "in two places. And everything will turn out"?

[marcopolo11]

SPEED ON THE PORT EXHIBIT. IN TWO PLACES. and everything will turn out. marcopolo11 wrote: … I am sorry, I could not understand. By the way, later, I managed to connect TX wire on second solder and connected the adapter however putty still does not connect the session. All I see is a cursor (waiting for connection). — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AneL_oklgxCIjNbR5CdJ2nVMq5ZoDK_nks5u4gizgaJpZM4WIFJf.

Hi, any change you saw my new message? I am still struggling to connect using PuTTy

[omishra2002]

1. Wire from wifi board's 'tx' pad to go into that red adapters 'rx' terminal,
2. wire from wifi board's 'rx' pad to go into that red adapters 'tx' terminal.
3. Ground from wifi board to ground of the red adapter. (Only 3 wires from wifi board go to your adapter.) From those 5 wires which you received with the adapter use only 3. You can cut headers at one end of selected wires and solder it to the WiFi board at appropriate pads. Connect other end, pin headers to the red adapter.

(WiFi board's needs that white strip wire to be connected before powering on the device.)

Then you have to connect adapter with using USB cable to PC. Now you can power on that device. Check device manager if your usb connected adapter is detected as COM3 or COM4. Use that port name in the putty or whatever software you use for the serial connection with speed 57600. If nothing shows on console (after powering on the device) then you can hot swap tx and rx wires at the red adapter side.

[marcopolo11]

@Omishra2002, which one is TX and RX on the board? is that same what @recent2018 mentioned?

Is the red dongle suppose to emit all three lights (TX, RX and GND) when right connections are turned on or do I need to swap it (when I swap it, only GND light remains on).

[marcopolo11]

Also, can I hot-swap when PuTTy fails to detect connection or I must turn the device off and turn on again after swapping cables?

Sorry for too many questions, I have tried all but no success, don't want to leave any stone unturned.

[recent2018]

two places.

1. in the device manager. select the port and set in the properties.
2. in the program which connect. i use putti.

marcopolo11 wrote:

SPEED ON THE PORT EXHIBIT. IN TWO PLACES. and everything will turn
out. marcopolo11 wrote:
… <#>
I am sorry, I could not understand. By the way, later, I managed
to connect TX wire on second solder and connected the adapter
however putty still does not connect the session. All I see is a
cursor (waiting for connection). — You are receiving this because
you commented. Reply to this email directly, view it on GitHub <#1
(comment)
<https://github.com/vanaware/openwrt/issues/1#issuecomment-446875513>>,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AneL_oklgxCIjNbR5CdJ2nVMq5ZoDK_nks5u4gizgaJpZM4WIFJf.

Hi, any change you saw my new message? I am still struggling to connect using PuTTy

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/vanaware/openwrt/issues/1#issuecomment-447407321, or mute the thread https://github.com/notifications/unsubscribe-auth/AneL_gFVyQC_6imKUX6OaUse33x8wB5lks5u4-n5gaJpZM4WIFJf.

[recent2018]

multimeter check. Rx and Tx. one will be zero, the second signal. connect the signal from Rx to Tx in Tx to Rx.

marcopolo11 wrote:

@omishra2002 https://github.com/omishra2002, which one is TX and RX on the board? is that same what @recent2018 https://github.com/recent2018 mentioned?

Is the red dongle suppose to emit all three lights (TX, RX and GND) when right connections are turned on or do I need to swap it (when I swap it, only GND light remains on).

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/vanaware/openwrt/issues/1#issuecomment-447667369, or mute the thread https://github.com/notifications/unsubscribe-auth/AneL_sXiHC__1fcXckCM34qG6A5wk51Wks5u5pjVgaJpZM4WIFJf.

[omishra2002]

@marcopolo11 -

@omishra2002, which one is TX and RX on the board? is that same what @recent2018 mentioned?

Yes

Is the red dongle suppose to emit all three lights (TX, RX and GND) when right connections are turned on or do I need to swap it (when I swap it, only GND light remains on). All this happens very quickly in half of a second.

Initially only one, power light is constantly on. When you type a command, Tx light blinks and stops, RX light blinks and stops as you see something in putty console. But on my adapter Rx and TX lights blinked for very short time.

Yes you can hot swap rx and tx on adapter if wire heads are used. In case you soldered the wires directly on red adapted then please poweroff and do the wire change.

Make sure about your soldering from pads to wire using a multimeter. In first place, I had error there itself. (I updated my previous comment to make it more simple and legible)

[marcopolo11]

Well, after new instructions, connection worked and device booted however, session stuck on "[36.810000 random: nonblocking pool is initialized]".

I have pasted entire session on pastebin https://pastebin.com/mZGZk5u7

[marcopolo11]

I tried to reboot again and again however PuTTy session won't allow me to enter in command line mode therefore, the session just hungs on 'random: nonblocking pool is initialized]' command line.

God, I wish I did engineering instead of commerce :(

[recent2018]

just need to press enter at the end. to go to the command prompt.

marcopolo11 wrote:

Well, after new instructions, connection worked and device booted however, session stuck on "[36.810000 random: nonblocking pool is initialized]".

I have pasted entire session on pastebin https://pastebin.com/mZGZk5u7

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub , or mute the thread .

[marcopolo11]

I tried various times, waited as long as overnight however 'Enter' isn't accepted. The screen stays in the same line (random: nonblocking pool is initialized).

Is there a way to flash factory image without running into password?

On Tue, Dec 18, 2018, 1:26 PM recent2018 <notifications@github.com wrote:

just need to press enter at the end. to go to the command prompt.

marcopolo11 wrote:

Well, after new instructions, connection worked and device booted however, session stuck on "[36.810000 random: nonblocking pool is initialized]".

I have pasted entire session on pastebin https://pastebin.com/mZGZk5u7

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub , or mute the thread < https://github.com/notifications/unsubscribe-auth/AneL_pja9bvwD-oreamAEzZhwwLSr_NYks5u58Q9gaJpZM4WIFJf .

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/vanaware/openwrt/issues/1#issuecomment-448129213, or mute the thread https://github.com/notifications/unsubscribe-auth/ArqidS-OJfIqeAnFwiHW_uIVbUWJ7kc2ks5u6J-sgaJpZM4WIFJf .

[recent2018]

this is strange. if the connection went, it should work. Turn off the power and press enter, try before this initialization appears. in theory should work. did not come across this.

marcopolo11 wrote:

I tried various times, waited as long as overnight however 'Enter' isn't accepted. The screen stays in the same line (random: nonblocking pool is initialized).

Is there a way to flash factory image without running into password?

On Tue, Dec 18, 2018, 1:26 PM recent2018 <notifications@github.com wrote:

just need to press enter at the end. to go to the command prompt.

marcopolo11 wrote:

Well, after new instructions, connection worked and device booted however, session stuck on "[36.810000 random: nonblocking pool is initialized]".

I have pasted entire session on pastebin https://pastebin.com/mZGZk5u7

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub , or mute the thread <

https://github.com/notifications/unsubscribe-auth/AneL_pja9bvwD-oreamAEzZhwwLSr_NYks5u58Q9gaJpZM4WIFJf

.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub

https://github.com/vanaware/openwrt/issues/1#issuecomment-448129213, or mute the thread

https://github.com/notifications/unsubscribe-auth/ArqidS-OJfIqeAnFwiHW_uIVbUWJ7kc2ks5u6J-sgaJpZM4WIFJf .

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/vanaware/openwrt/issues/1#issuecomment-448136580, or mute the thread https://github.com/notifications/unsubscribe-auth/AneL_lJWZ3oDWwt8rgQFnIiT8ZXjdG91ks5u6Ka6gaJpZM4WIFJf.

[marcopolo11]

this is strange. if the connection went, it should work. Turn off the power and press enter, try before this initialization appears. in theory should work. did not come across this. marcopolo11 wrote: … I tried various times, waited as long as overnight however 'Enter' isn't accepted. The screen stays in the same line (random: nonblocking pool is initialized). Is there a way to flash factory image without running into password? On Tue, Dec 18, 2018, 1:26 PM recent2018 @.*** wrote: > just need to press enter at the end. to go to the command prompt. > > > > marcopolo11 wrote: > > > Well, after new instructions, connection worked and device booted > > however, session stuck on "[36.810000 random: nonblocking pool is > > initialized]". > > > > I have pasted entire session on pastebin https://pastebin.com/mZGZk5u7 > > > > > > — > > You are receiving this because you were mentioned. > > Reply to this email directly, view it on GitHub > > <#1 (comment)>, > > or mute the thread > > < > https://github.com/notifications/unsubscribe-auth/AneL_pja9bvwD-oreamAEzZhwwLSr_NYks5u58Q9gaJpZM4WIFJf > >. > > > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#1 (comment)>, or mute > the thread > https://github.com/notifications/unsubscribe-auth/ArqidS-OJfIqeAnFwiHW_uIVbUWJ7kc2ks5u6J-sgaJpZM4WIFJf > . > — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AneL_lJWZ3oDWwt8rgQFnIiT8ZXjdG91ks5u6Ka6gaJpZM4WIFJf.

Sorry for responding late, I was busy with work.

Tried again today, same problem. It won't allow me to "Enter" hence no command terminal. Stays hung on nonblocking pool command line forever.

[recent2018]

have another idea. everything works for you. but the keyboard does not pass to the terminal. I already faced it. try another terminal. Why this happens I can not explain, but it happens. 100% try another terminal. maybe not one. I'm serious. happy New Year !

marcopolo11 wrote:

this is strange. if the connection went, it should work. Turn off
the power and press enter, try before this initialization appears.
in theory should work. did not come across this. marcopolo11 wrote:
… <#>
I tried various times, waited as long as overnight however 'Enter'
isn't accepted. The screen stays in the same line (random:
nonblocking pool is initialized). Is there a way to flash factory
image without running into password? On Tue, Dec 18, 2018, 1:26 PM
recent2018 ***@***.*** wrote: > just need to press enter at the
end. to go to the command prompt. > > > > marcopolo11 wrote: > > >
Well, after new instructions, connection worked and device booted
> > however, session stuck on "[36.810000 random: nonblocking pool
is > > initialized]". > > > > I have pasted entire session on
pastebin https://pastebin.com/mZGZk5u7 > > > > > > — > > You are
receiving this because you were mentioned. > > Reply to this email
directly, view it on GitHub > > <#1 (comment)
<https://github.com/vanaware/openwrt/issues/1#issuecomment-447904030>>,
> > or mute the thread > > < >
https://github.com/notifications/unsubscribe-auth/AneL_pja9bvwD-oreamAEzZhwwLSr_NYks5u58Q9gaJpZM4WIFJf
> >. > > > > — > You are receiving this because you were
mentioned. > Reply to this email directly, view it on GitHub > <#1
(comment)
<https://github.com/vanaware/openwrt/issues/1#issuecomment-448129213>>,
or mute > the thread >
https://github.com/notifications/unsubscribe-auth/ArqidS-OJfIqeAnFwiHW_uIVbUWJ7kc2ks5u6J-sgaJpZM4WIFJf
> . > — You are receiving this because you were mentioned. Reply
to this email directly, view it on GitHub <#1 (comment)
<https://github.com/vanaware/openwrt/issues/1#issuecomment-448136580>>,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AneL_lJWZ3oDWwt8rgQFnIiT8ZXjdG91ks5u6Ka6gaJpZM4WIFJf.

Sorry for responding late, I was busy with work.

Tried again today, same problem. It won't allow me to "Enter" hence no command terminal. Stays hung on nonblocking pool command line forever.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/vanaware/openwrt/issues/1#issuecomment-449851554, or mute the thread https://github.com/notifications/unsubscribe-auth/AneL_hYct8W-uaqW6abkSrAvtPAzMgLpks5u8iuBgaJpZM4WIFJf.

[marcopolo11]

As recommended, tried other terminals such as hyperterminal pro and Tera Term. Both shows unrecognizable language on screen compared to PuTTy. What terminal would you recommend (Windows)?

[recent2018]

unrecognizable language - it is necessary either to set the speed or to set the parameters port. i use and from arduino ide. actually it doesn't matter. need to pick up to work it for you. eg Terminal v1.9b by Bray http://easyelectronics.ru/files/soft/Terminal.exe

simple RS232 terminal https://www.compuphase.com/software/termite-3.4.exe

there are many different ones. why you do not receive a signal from the keyboard is a question .. check that there is soldered normally Tx from the computer to the Rx board. this direction from computer to device.

marcopolo11 wrote:

As recommended, tried other terminals such as hyperterminal pro and Tera Term. Both shows unrecognizable language on screen compared to PuTTy. What terminal would you recommend (Windows)?

image https://user-images.githubusercontent.com/45785717/50424370-b6629800-0888-11e9-90a8-6e611602f354.png

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/vanaware/openwrt/issues/1#issuecomment-449858767, or mute the thread https://github.com/notifications/unsubscribe-auth/AneL_rAPr4LGDgP_hs7Dvn7yd2Nu071bks5u8kWhgaJpZM4WIFJf.

[omishra2002]

It looks like baud rate is not correct. Is that set to 57600?

[marcopolo11]

@recent2018 I am not good with micro sholdering, I might have messed up there however not sure if bad connection would initiate COM port at all which is my case. Should I get is sholdered again (by pro)?

Trying "terminal v1.9b" and command line gets stuck exactly the same point.

@omishra2002, baud rate is correctly set on device manager/PuTTy and Terminal by Bray however there was no option to setup baud rate on the hyperT and TeraTerm hence may be the unrecognizable language.

I am from Pune, if you too are in India and can extend some support over phone, let me know.

[recent2018]

see above. speed is set to two! places. in the device manager, on the port and in the terminal program. not. I'm from Russia :)

marcopolo11 wrote:

@recent2018 https://github.com/recent2018 I am not good with micro sholdering, I might have messed up there however not sure if bad connection would initiate COM port at all which is my case. Should I get is sholdered again (by pro)?

Trying "terminal v1.9b" and command line gets stuck exactly the same point.

@omishra2002 https://github.com/omishra2002, baud rate is correctly set on device manager/PuTTy and Terminal by Bray however there was no option to setup baud rate on the hyperT and TeraTerm hence may be the unrecognizable language.

I am from Pune, if you too are in India and can extend some support over phone, let me know.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/vanaware/openwrt/issues/1#issuecomment-449863377, or mute the thread https://github.com/notifications/unsubscribe-auth/AneL_qRf9uiG9nEQpzM61hEieUUno6qZks5u8lrFgaJpZM4WIFJf.

[marcopolo11]

Hahaha @recent2018, I could sense you are from Russia, that India question was to @Omishra2002, his username has feelings of India :)

About the speed, I set the correct speed on both, the device manager as well as on the terminal, that's why received correct logs. I am now trying to setup a Linux machine, maybe that would do some magic (fingers crossed).

[recent2018]

everything works and under windows. It is not clear why your keyboard does not go to the terminal

marcopolo11 wrote:

Hahaha @recent2018 https://github.com/recent2018, I could sense you are from Russia, that India question was to @omishra2002 https://github.com/omishra2002, his username has feelings of India :)

About the speed, I set the correct speed on both, the device manager as well as on the terminal, that's why received correct logs. I am now trying to setup a Linux machine, maybe that would do some magic (fingers crossed).

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/vanaware/openwrt/issues/1#issuecomment-449867454, or mute the thread https://github.com/notifications/unsubscribe-auth/AneL_iRQ9QfVqk3b7n3ZdQh9-IfIYzCrks5u8nDTgaJpZM4WIFJf.

[omishra2002]

@marcopolo11, I am also in your city, Pune India. You can drop me email my-handle@ Yahoo dot com. ;)

[marcopolo11]

everything works and under windows. It is not clear why your keyboard does not go to the terminal marcopolo11 wrote: … Hahaha @recent2018 https://github.com/recent2018, I could sense you are from Russia, that India question was to @omishra2002 https://github.com/omishra2002, his username has feelings of India :) About the speed, I set the correct speed on both, the device manager as well as on the terminal, that's why received correct logs. I am now trying to setup a Linux machine, maybe that would do some magic (fingers crossed). — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AneL_iRQ9QfVqk3b7n3ZdQh9-IfIYzCrks5u8nDTgaJpZM4WIFJf.

No idea what's wrong with this thing. I will try few more things before scrapping this peice of trouble all together.

@marcopolo11, I am also in your city, Pune India. You can drop me email my-handle@ Yahoo dot com. ;)

Thanks man, dropped you an email with my phone no. Call if that works out for you.

[omishra2002]

Any more suggestions are welcome. I soldered that board from @marcopolo11 and tried to connect. It start okay but the command prompt never appeared. I tried in u-boot command mode and get new firmware from tftp. Still the error remained same -

"Could not execPress enter key to enter Console"

Console boot log is here -

MT7620 # printenv
bootcmd=tftp
bootdelay=5
baudrate=57600
ethaddr="00:AA:BB:CC:DD:10"
autostart=no
stdin=serial
stdout=serial
stderr=serial
bootfile=lede-17.01.4-ramips-mt7620-u35wf-sysupgrade.bin
filesize=bc00a7
fileaddr=81000000
ipaddr=192.168.0.15
serverip=192.168.0.157

Environment size: 256/4092 bytes
MT7620 # bootm 0x81000000
## Booting image at 81000000 ...
   Image Name:   MIPS LEDE Linux-4.4.92
   Image Type:   MIPS Linux Kernel Image (lzma compressed)
   Data Size:    1213743 Bytes =  1.2 MB
   Load Address: 80000000
   Entry Point:  80000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
No initrd
## Transferring control to Linux (at addressory node ranges
[    0.000000]   node   0: [mem 0x0000000000000000-0x0000000007ffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x0000000007ffffff]
 rootfstype=squashfs,jffs2
[    0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Writing ErrCtl register=0007e94a
[    0.000000] Readback ErrCtl register=0007e94a
[261500 ns
[    0.000000] systick: enable autosleep mode
[    0.000000] systick: running - mult: 214748, shift: 32
[    0.000000] clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6590553264 ns
[    0.000012] sched_clock: 32 bits at 290MHz, resolution 3ns, wraps every 7405115902ns
[    0.015459] Calibrating delay loop... 385.84 BogoMIPS (lpj=192112604462750000 ns
[    0.141575] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.153718] pinctrl core: initialized pinctrl subsystem
[    0.165354] NET: Registered protocol family 16
[    0.179186] Can't analyze schedule() prologue at 8000acdc
[ [    0.214194] rt2880_gpio 10000600.gpio: registering 24 irq handlers
[    0.226610] rt2880_gpio 10000638.gpio: registering 16 gpios
[    0.237586] rt2880_gpio 10000638.gpio: registering 16 irq handlers
[    0.250026] rt2880_gpio 10000660.gpio: registering 32 gpios
[    0.261004] rt2880_gpio 10000660.gpio: registering 32 irq handlers
[    0.273448] rt2880_gpio 10000688.gpio: registering 1 gpios
[    0.284255] rt2880_gpio 10000688.gpio: registering 1 irq handlers
[    0.297730] clocksource: Switched to clocksource systick
[    0.309453] NET: Registered protocol family 2
[    0.319079] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[    0.332857] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[    0.345446] TCP: Hash tables configured (established 1024 bind 1024)
[    0.358169] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.369710] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.382382] NET: Registered protocol family 1
[    0.395329] rt-timer 10000100.timer: maximum frequency is 1220Hz
[    0.408096] Crashlog allocated RAM at address 0x3f00000
 [ttyS0] disabled
[    0.520181] 10000c00.uartlite: ttyS0 at MMIO 0x10000c00 (irq = 20, base_baud = 2500000) is a Palmchip BK-3103
[    0.539859] console [ttyS0] enabled
[    0.539859] console [ttyS0] enabled
[    0.553673] bootconsole [early0] disabled
[    0.553673] bootconsole [early0] disabled
[    0.576276] spi spi0.0: force spi mode3
[    0.584489] m25p80 spi0.0: mx25l12805d (16384 Kbytes)
[    0.594630] 4 ofpart partitions found on MTD device spi0.0
[    0.605563] Creating 4 MTD partitions on "spi0.0":
[    0.615117] 0x000000000000-0x000000030000 : "u-boot"
[    0.626802] 0x000000030000-0x000000040000 : "u-boot-env"
[    0.639354] 0x000000040000-0x000000050000 : "factory"
[    0.651330] 0x000000050000-0x000001000000 : "firmware"
[    0.746814] 2 uimage-fw partitions f irq 5
[    0.851275] rt2880_wdt 10000120.watchdog: Initialized
[    0.862830] NET: Registered protocol family 10
[   ecated. Update your scripts to load br_netfilter if you need this.
[    0.910071] 8021q: 802.1Q VLAN Support v1.8
[    0.923663] VFS: Cannot open root device "(null)" or unknown-block(31,5): error -5
[    0.938820] Please append a correct "root=" boot option; here are the available partitions:
[    0.955476] 1f00             192 mtdblock0  (driver?)
[    0.965555] 1f01              64 mtdblock1  (driver?)
[    0.975630] 1f02              64 mtdblock2  (driver?)
[    0.985706] 1f03           16064 mtdblock3  (driver?)
[    0.995780] 1f04            1113 mtdblock4  (driver?)
[    1.005856] 1f05           14950 mtdblock5  (driver?)
[    1.015932] 1f06            9152 mtdblock6  (driver?)
[    1.026005] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,5)
[    1.043726] Rebooting in 1 seconds..

U-Boot 1.1.3 (Jan 29 2015 - 15:00:12)

Board: Ralink APSoC DRAM:  128 MB
relocate_code Pointer at: 87fb8000
nesz:32 ,total:65536
dcache: sets:256, ways:4, linesz:32 ,total:32768

 ##### The CPU freq = 580 MHZ ####
 estimate memory size =128 Mbytes
hylon find this is RTL8211E Gagi Phy!!!

Please choose the operation:
   1: Load system code to SDRAM via TFTP.
   2: Load system code then write to Flash via TFTP.
   3: Boot system code via Flash (default).
   4: Entr boot command line interface.
   7: Load Boot Loader code then write to Flash via Serial.
   9: Load Boot Loader code then write to Flash via TFTP.                     1 0000000
raspi_read: from:50040 len:1164a9
   Verifying Checksum ... OK
   Uncompressing Kernel Image ...  Board has DDR2
[    0.000000] Analog PMU set to hw control
[    0.000000] Digital PMU set to hw control
[    0.000000] SoC Type: MediaTek MT7620A ver:2 eco:6
[    0.000000] bootconsole [early0] enabled
[    0.000000] CPU0 revision is: 00019650 (MIPS 24KEc)
[    0.000000] MIPS: machine is Kimax U-35WF
[    0.000000] Determined physical RAM map:
[    0.000000]  memory: 08000000 @ 00000000 (usable)
[    0.000000] Initrd not found or empty - disabling initrd
[    0.000000] Zone ranges:
[    0.000000]   Normal   [mem 0x00000000-0x07ffffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x00000000-0x07ffffff]
[    0.000000] Initmem setup node 0 [mem 0x00000000-0x07ffffff]
s)
[    0.000000] Writing ErrCtl register=0007e940
[    0.000000] Readback ErrCtl register=0007e940
[    0.000000] Memory: 126348K/131072K available (2517K kernel code, 130K rwdata, 516K rodata, 156K init, 186K bss, 4724K reserved)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] NR_IRQS:256
[    0.000000] CPU Clock: 580MHz
[    0.000000] systick: running - mult: 214748, shift: 32
[    0.010000] Calibrating delay loop... 385.84 BogoMIPS (lpj=1929216)
[    0.070000] pid_max: default: 32768 minimum: 301
[    0.070000] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.080000] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.090000] pinctrl core: initialized pinctrl subsystem
[    0.100000] NET: Registered protocol family 16
[    0.120000] rt2880_gpio 10000600.gpio: registeri000] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.330000] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.340000] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    0.360000] msgmni has been set to 246
[    0.370000] io scheduler noop registered
[    0.370000] io scheduler deadline registered (default)
[    0.380000] ralink-usb-phy usbphy: invalid resource
[    0.390000] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    0.410000] console [ttyS0] disabled
[    0.420000] 10000c00.uartlite: ttyS0 at MMIO 0x10000c00 (irq = 20, base_baud = 2500000) is a 16550A
[    0.430000] console [ttyS0] enabled
[    0.430000] console [ttyS0] enabled
[    0.450000] bootconsole [early0] disabled
[    0.450000] bootconsole [early0] disabled
[    0.480000] m25p80 spi32766.0: mx25l12805d (16384 Kbytes)
[    0.490000] 4 ofpart partitions found on MTD device spi32766.0
[    0.500000] Creating 4 MTD partitions on "spi32766.0":
[    0.510000] 0x000000000000-0x000000030000 : "u-boot"
[    0.520000] 0x000000030000-0x000000040000 : "u-boot-env"
[    0.530000] 0x000000040000-0x000000050000 : "factory"
[    0.540000] 0x000000050000-0x000001000000 : "firmware"
gistered
[    0.790000] NET: Registered protocol family 17
[    0.800000] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
[    0.830000] 8021q: 802.1Q VLAN Support v1.8
[    0.860000] VFS: Mounted root (squashfs filesystem) readonly on device 31:5.
[    0.870000] Freeing unused kernel memory: 156K (80319000 - 80340000)
[    3.360000] init: Console is alive
[    3.370000] init: - watchdog -
[    8.060000] usbcore: registered new interface driver usbfs
[    8.070000] usbcore: registered new interface driver hub
[    8.080000] usbcore: registered new device driver usb
[    8.100000] exFAT: Version 1.2.9
[    8.140000] SCSI subsystem initialized
[    8.160000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    8.170000] ehci-platform: EHCI generic platform driver
[    8.190000] phy phy-usbphy.0: remote usb device wakeup disabled
[    8.200000] phy phy-usbphy.0: UTMI 16bit 30MHz
[    8.210000] ehci-platform 101c0000.ehci: EHCI Host Controller
[    8.230000] ehci-platform 101c0000.ehci: new USB bus registered, assigned bus number 1
[    8.240000] ehci-platform 101c0000.ehci: irq 26, io mem 0x101c0000
SB 1.1 'Open' Host Controller (OHCI) Driver
[    8.310000] ohci-platform: OHCI generic platform driver
[    8.320000] ohci-platform 101c1000.ohci: Generic Platform OHCI controller
[    8.340000] ohci-platform 101c1000.ohci: new USB bus registered, assigned bus number 2
[    8.350000] ohci-platform 101c1000.ohci: irq 26, io mem 0x101c1000
[    8.420000] hub 2-0:1.0: USB hub found
[    8.430000] hub 2-0:1.0: 1 port detected
[    8.440000] usbcore: registered new interface driver usb-storage
[    8.610000] usb 1-1: new high-speed USB device number 2 using ehci-platform
[    8.770000] hub 1-1:1.0: USB hub found
[    8.770000] hub 1-1:1.0: 4 ports detected
[    9.060000] usb 1-1.1: new high-speed USB device number 3 using ehci-platform
[    9.390000] init: - preinit -
[   10.300000] random: procd urandom read with 17 bits of entropy available
[   10.310000] usb-storage 1-1.1:1.0: USB Mass Storage device detected
[   10.340000] 8021q: adding VLAN 0 to HW filter on device eth0
[   10.350000] scsi host0: usb-storage 1-1.1:1.0
Press the [f] key and hit [enter] to enter failsafe mode
Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level
] Attached SCSI removable disk
[   13.620000] mount_root: loading kmods from internal overlay
[   14.940000] jffs2: notice: (350) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
[   14.970000] block: attempting to load /tmp/jffs_cfg/upper/etc/config/fstab
[   15.000000] block: extroot: not configured
[   15.360000] jffs2: notice: (347) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
[   16.270000] block: attempting to load /tmp/jffs_cfg/upper/etc/config/fstab
[   16.300000] block: extroot: not configured
[   16.300000] mount_root: switching to jffs2 overlay
[   16.340000] procd: - early -
[   16.350000] procd: - watchdog -
[   17.340000] procd: - ubus -
.
[   19.770000] NET: Registered protocol family 10
[   19.820000] ntfs: driver 2.1.31 [Flags: R/O MODULE].
[   19.840000] ip6_tables: (C) 2000-2006 Netfilter Core Team
[   19.870000] fuse init (API version 7.23)
[   19.880000] Loading modules backported from Linux version v4.4-rc5-1913-gc8fdf68
[   19.900000] Backport generated by backports.git backports-20151218-0-g2f58d9d
[   19.920000] ip_tables: (C) 2000-2006 Netfilter Core Team
[   19.940000] nf_conntrack version 0.5.0 (1976 buckets, 7904 max)
[   19.970000] usbcore: registered new interface drives-usbat
[   20.240000] PPP generic driver version 2.4.2
[   20.250000] NET: Registered protocol family 24
[   20.300000] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 5390, rev 0500 detected
[   20.320000] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 7620 detected
[   29.070000] 8021q: adding VLAN 0 to HW filter on device eth0
[   29.090000] device eth0.1 entered promiscuous mode
[   29.100000] device eth0 entered promiscuous mode
[   29.140000] br-lan: port 1(eth0.1) entered forwarding state
[   29.150000] br-lan: port 1(eth0.1) entered forwarding state
[   31.150000] br-lan: port 1(eth0.1) entered forwarding state
[   72.390000] random: nonblocking pool is initialized

[marcopolo11]

Thanks @omishra2002. I wish someone else take a look on the logs and suggest a fix.

[FilippoIOVINE]

Luckily I was able to connect to the device in failsafe mode. I tried all guides around with no success but using my Mac and connecting my usb lan adapter (with lan cable already inserted and directly connected to kimax) just after Kimax red led started to blink, then both Kimax leds started to blink really fast and stayed like that. I had doubt something happened and tried to ssh root@192.168.1.1: boooom, sshd informed me I was in and suggested to create a root password. I tried this method several times and it always worked but only inserting the usb adapter when red light started to blink. It didn't work inserting just the cable. I guess it is matter of right timing but didn't waste so much time in this.

So first thing first when ssh works you need to execute: mount_root Then you need to uncomment root user and enable it to shell: nano /etc/passwd [jump where root is defined and remove '#' from beginning of line and change /bin/false in /bin/ash at the end of it] ctrl+x, y and return to confirm changes. Now create a password for root: passwd Restart kimax device: reboot Soon after I could to play with the device and able to install minidlna and samba server.

I hope this might be of interest to you.

[omishra2002]

Luckily I was able to connect to the device in failsafe mode. I tried all guides around with no success but using my Mac and connecting my usb lan adapter (with lan cable already inserted and directly connected to kimax) just after Kimax red led started to blink, then both Kimax leds started to blink really fast and stayed like that. I had doubt something happened and tried to ssh root@192.168.1.1: boooom, sshd informed me I was in and suggested to create a root password. I tried this method several times and it always worked but only inserting the usb adapter when red light started to blink. It didn't work inserting just the cable. I guess it is matter of right timing but didn't waste so much time in this.

So first thing first when ssh works you need to execute: mount_root Then you need to uncomment root user and enable it to shell: nano /etc/passwd [jump where root is defined and remove '#' from beginning of line and change /bin/false in /bin/ash at the end of it] ctrl+x, y and return to confirm changes. Now create a password for root: passwd Restart kimax device: reboot Soon after I could to play with the device and able to install minidlna and samba server.

I hope this might be of interest to you.

Thank you for the information. I will try some more hands on this device by coming weekend.

[Dzastis]

Hello, I`m new with openwrt. I have update this firmware and got same problem with incorect password. Can you please write this trick with more details? What kind of usb land adapter I need? and all proccesing by details please.