Jump to content

RK3318 device (Magicsee N5 Nova 4g/64g) with dead NAND

Lambert

By Lambert
in Rockchip CPU Boxes

 Share

Recommended Posts

Lambert

Lambert

Posted
Posted (edited)

Hi all!

Have RK3318 device (Magicsee N5 Nova 4g/64g) with dead NAND.

Need revive this trash any way.

Want to try this way but would be nice to be able watch console.

Guess this is what I need.

But I have no idea where is RX TX.

First PIN is GND (rihgt side).

Please help!

Thanx!

My_console_PIN.jpg

Edited by TRS-80
RK3318, not RK3188
  • Werner changed the title to RK3318 device (Magicsee N5 Nova 4g/64g) with dead NAND
Lambert

Lambert

Posted
  • Author
Posted (edited)
  On 11/28/2020 at 9:33 AM, hexdump said:

@Lambert or some moderator: i think what is ment here is rk3318 and not rk3188 - it might be good to adjust the title ...

Expand  

That's it! My fault. Thanx!

But I can't edit it no longer.

  On 11/27/2020 at 10:14 PM, jock said:

You may try this very work in progress build effort made by @fabiobassa, @hexdump and me.

 

Burn it on a sdcard and try, but your mileage may vary

Expand  

Thanx a lot for help!
I'll try yours image definitely soon! There is only one common card left.
Until I was waiting for an answer - did something: figured out RX & TX.
In order:
1. I burn bionic image (Armbian_20.07_Rk3328-tv_bionic_current_5.7.8.img) first. But SDcard even wasn't found I guess:

  Reveal hidden contents

2. Then I burn "trust.img" (by: "dd if=trust.img of=/dev/sdb seek=24576") and put "rk3318-t9.dtb"(from here) in the root of SDcard. I got "trust.img" from stock Android Firmware. The log has become much longer this time:

  Reveal hidden contents

what is more password does it required? "1234" mismatch.
---
How can I post more than one per day? It's too slow!

Edited by Lambert
addons
1
Werner

Werner

Posted
Posted
  On 11/28/2020 at 2:18 PM, Lambert said:

ow can I post more than one per day? It's too slow!

Expand  

Unfortunately needed to fight spam and other BS :(

You received a like. Restrictions should be lifted within 24h

Lambert

Lambert

Posted
  • Author
Posted
  On 11/27/2020 at 10:14 PM, jock said:

You may try this very work in progress build effort made by @fabiobassa, @hexdump and me.

 

Burn it on a sdcard and try, but your mileage may vary

Expand  

Hi again!

Sorry for long silence.

I try "Armbian_20.11.0-trunk_Rk3318-box_focal_dev_5.9.6_desktop", but it's no work!

Seems like this image has no BOOT partition: "ROOTFS" only. No ".dtb", no kernel...

Look yourself:

  Reveal hidden contents

 

BOOT not existing even in Linux-explorer.

Other results is:

Install LibreELEC-RK3328.arm-9.2.6-box.img : no wlan but extrenal dongle work OK. Wired - present and working properly.

Install Armbian_20.07...5.7.8_focal : no eth0, eth1: wired and wlan not present, not configuring.

Fight with it now....

jock

jock

Posted
Posted
  On 12/5/2020 at 8:25 PM, Lambert said:

Hi again!

Sorry for long silence.

I try "Armbian_20.11.0-trunk_Rk3318-box_focal_dev_5.9.6_desktop", but it's no work!

Seems like this image has no BOOT partition: "ROOTFS" only. No ".dtb", no kernel...

Look yourself:

  Reveal hidden contents

 

BOOT not existing even in Linux-explorer.

Other results is:

Install LibreELEC-RK3328.arm-9.2.6-box.img : no wlan but extrenal dongle work OK. Wired - present and working properly.

Install Armbian_20.07...5.7.8_focal : no eth0, eth1: wired and wlan not present, not configuring.

Fight with it now....

Expand  

It looks like that your assumption about broken NAND (that's an eMMC though) is wrong: your board is booting from eMMC.

You may try this other experimental multitool for rk3318: https://drive.google.com/file/d/1HbaB7glgDTYWrE4ieBkX6uK0sT223hCl/view?usp=sharing and follow the instructions you find here (installation for eMMC). You may want, in alternative, to get a shell and try to repair the existing android installation using fsck tools if you are experienced enough.

Again, this is very experimental, and your mileage may vary as well.

 

Lambert

Lambert

Posted
  • Author
Posted
  On 12/5/2020 at 9:19 PM, jock said:

It looks like that your assumption about broken NAND (that's an eMMC though) is wrong: your board is booting from eMMC.

Expand  

How I wish it be true but isn't. 

There is Android boot log with so many errors.

Pity I can do nothing with eMMC.

  On 12/5/2020 at 9:19 PM, jock said:

 

You may try this other experimental multitool for rk3318: https://drive.google.com/file/d/1HbaB7glgDTYWrE4ieBkX6uK0sT223hCl/view?usp=sharing and follow the instructions you find here (installation for eMMC). You may want, in alternative, to get a shell and try to repair the existing android installation using fsck tools if you are experienced enough.

Again, this is very experimental, and your mileage may vary as well.

Expand  

I try write/burn Multitool before:  still unsuccessful...

All "Android-trying" are crashed the booting.

jock

jock

Posted
Posted
  On 12/6/2020 at 1:30 PM, Lambert said:

How I wish it be true but isn't. 

There is Android boot log with so many errors.

Pity I can do nothing with eMMC.

Expand  

Can't see any log, teh webserver is anwering 403 Forbidden.

Anyway your eMMC is not dead. Maybe it is faulty, but since it boots it is not dead at all.

 

  On 12/6/2020 at 1:30 PM, Lambert said:

I try write/burn Multitool before:  still unsuccessful...

All "Android-trying" are crashed the booting.

Expand  

I don't think you could ever succeed because the multitool for rk3318 has never been made public yet.

Maybe you used that one for rk322x, but it does and will never work with 3318.

You need to download exactly that one I gave you the link above

Lambert

Lambert

Posted
  • Author
Posted
  On 12/6/2020 at 3:00 PM, jock said:

Can't see any log, teh webserver is anwering 403 Forbidden.

Anyway your eMMC is not dead. Maybe it is faulty, but since it boots it is not dead at all.

Expand  

1. Show me where I can put this log please.

2. eMMC not fully dead: I see two logos during Android boot trying .

  On 12/6/2020 at 3:00 PM, jock said:

You need to download exactly that one I gave you the link above

Expand  

3. I'll try definitely. But I'm not sure that I clearly understand those instructions. It may be complicated for me...

Thanx for Help!

Lambert

Lambert

Posted
  • Author
Posted

Need some help about instructions;

"Build or download your preferred Armbian image and a copy of the Multitool"

• I can't use Armbian on my box: it's started ok but I can't tune any ethernet connections there. Can I try other OS imge?

 

"Choose “Burn image to flash” from the menu, then select the destination device (usually mmcblk2) and the image to burn"

• What exactly type of memory is it talking about here? If it mean "eMMC" - it's useless: eMMC switched to R/O mode.  This is my second box with a similar malfunction.

 

BTW I guess more suitable for my case will be "Quick installation instructions to boot from SD Card". Is that true?

Next point to clear:

--------------------------------------------

Quick installation instructions to boot from SD Card:

• If you are already running Armbian from eMMC, skip to the next step. Instead if you are running the original firmware you need to first

   erase the internal eMMC; to do so download the Multitool, burn it on an SD Card, plug the SD Card and power the TV Box.

   Use “Backup flash” if you want to do a backup of the existing firmware, then choose “Erase flash” menu option.

• Build or download your preferred Armbian image;

• Uncompress and burn the Armbian image on the SD Card;

--------------------------------------------

Must I format SD before burn "preferred Armbian image" or burn it next on "Multitool"?

-----------------------

I attached that log here:

Android boot.txtFetching info...

jock

jock

Posted
Posted
  On 12/6/2020 at 9:34 PM, Lambert said:

Report.

Burn Multitool on SD, insert, turn Power On --> no result: boot Android from eMMC.

Expand  

Did you decompress the .xz archive first?

Use a good burner like balena.etcher or rufus if you are on windows

 

edit: also it may require a couple or more of power unplug/plug cycles to work. At least on my box it is so.

Lambert

Lambert

Posted
  • Author
Posted
  On 12/6/2020 at 9:46 PM, jock said:

Did you decompress the .xz archive first?

Use a good burner like balena.etcher or rufus if you are on windows

Expand  

I use Balena in both: under WINDOWS and UBUNTU - same result.

  On 12/6/2020 at 9:46 PM, jock said:

also it may require a couple or more of power unplug/plug cycles to work. At least on my box it is so.

Expand  

Ten times.

No boot from SD....

jock

jock

Posted
Posted
  On 12/6/2020 at 11:34 PM, Lambert said:

I use Balena in both: under WINDOWS and UBUNTU - same result.

Ten times.

No boot from SD....

Expand  

Odd.

I read the log in the post above and the line SdmmcInit=0 NOT PRESENT says that the sdcard is not detected at all.

Can't say anything more at the moment, you need to use the maskrom mode if you want to proceed further.

1
Lambert

Lambert

Posted
  • Author
Posted
  On 12/7/2020 at 9:43 AM, jock said:

I read the log in the post above and the line SdmmcInit=0 NOT PRESENT says that the sdcard is not detected at all.

Expand  

There was Android-boot-log from eMMC, ofcouse without SD.

I must to had to log the "MultiBoot" booting I guess...

Lambert

Lambert

Posted
  • Author
Posted
  On 12/6/2020 at 3:00 PM, jock said:

You need to download exactly that one I gave you the link above

Expand  

I was run Multitool at last!

It could only start this way:

1. Rufus+Multitool.img

2. dd if=trust.img of=/dev/sdb seek=24576
3. dd if=uboot.img of=/dev/sdb seek=16384

 

DateCamera1210164602.jpg

1
Lambert

Lambert

Posted
  • Author
Posted

eMMC not be able to be burned as I told before.

5 Burn image to flash proceed about 2sec long.

3 Erase flash was take with couple sec more.

eMMC must be forget.

 

jock

jock

Posted
Posted
  On 12/10/2020 at 3:59 PM, Lambert said:

I was run Multitool at last!

It could only start this way:

1. Rufus+Multitool.img

2. dd if=trust.img of=/dev/sdb seek=24576
3. dd if=uboot.img of=/dev/sdb seek=16384

 

Expand  

Glad to read that. Strange you had to write the trust.img and uboot.mg back onto the sdcard, they are already installed in the same position you burned again. Strange, I will check the scripts but thanks for reporting!

 

  On 12/10/2020 at 5:40 PM, Lambert said:

eMMC not be able to be burned as I told before.

5 Burn image to flash proceed about 2sec long.

3 Erase flash was take with couple sec more.

eMMC must be forget.

Expand  

Ok, an amount of sectors of the eMMC are gone. I suggest you to erase it and leave it alone.

Once the eMMC is erased, you may try to burn the armbian image I gave you on the sdcard, it should boot directly.

1
Lambert

Lambert

Posted
  • Author
Posted
  On 12/10/2020 at 9:44 PM, jock said:

Glad to read that. Strange you had to write the trust.img and uboot.mg back onto the sdcard, they are already installed in the same position you burned again. Strange, I will check the scripts but thanks for reporting!

Expand  

Did it because I burn correct for my device images maybe? They is 4096 kb lenght both. 

Yours?

2020-12-11_003337.jpg

Lambert

Lambert

Posted
  • Author
Posted
  On 12/10/2020 at 9:44 PM, jock said:

Once the eMMC is erased, you may try to burn the armbian image I gave you on the sdcard, it should boot directly.

Expand  

eMMC was not be erased. I checked it later - all files and folders are remains in their original locations. 

Pity inner memory is definately dead.

Once I tryed to burn your image, but I used balenaEtcher only.

Must I shell have try another burner in case maybe?

Thank You for your cares!

Lambert

Lambert

Posted
  • Author
Posted

Jock!

Your img not contain BOOT partition!

Where is .dtb placed  for example?

There are 3 partitions on SD: first and last are empty.

Middle partition has no label, looks like BOOTFS.

How it can boot?

Volume middle.jpg

Partitions.jpg

Lambert

Lambert

Posted
  • Author
Posted
  Reveal hidden contents

I understand where: in GPT

My MB support MBR only.

Sorry.

Need some upgrade!  :D

Lambert

Lambert

Posted
  • Author
Posted
  Reveal hidden contents

rk-kernel.dtb - this is device-tree from Android firmware.

It's not match for Linux.

I need try this:

rk3318-N5-NOVA.rarFetching info...

jock

jock

Posted
Posted

@Lambert

I'm afraid you are making some mess there.

The image I provided has the right content in the /boot directory, including the dtb, kernel and initramfs.

Everything is at the right place and the image boots fine on my box and others too.

If you see an empty /boot there is a problem or maybe you're looking at the wrong place.

Lambert

Lambert

Posted
  • Author
Posted
  On 12/11/2020 at 1:31 PM, jock said:

I'm afraid you are making some mess there.

Expand  

I've been attached log with many errors. Did You see it?

I find dtb in boot folder but i can't try my dtb: not owner.

Can I do enything else?

I feel useless...

jock

jock

Posted
Posted

From the last log you posted I see that the box is still booting from the eMMC.

Back to the multitool: if erase eMMC does not work, you may try to use option "Drop to Shell" and then execute: 

dd if=/dev/zero of=/dev/mmcblk2 bs=1M count=1 oflag=direct
exit

and hope it works. This command will remove the bootloader.

Reboot the board and you should not get the GPT partition table list anymore.

 

Maybe your eMMC is so faulty that it cannot be written in any manner.

If you can't write the eMMC, you cannot remove the bootloader and boot the Armbian image from sdcard.

 

Lambert

Lambert

Posted
  • Author
Posted
  On 12/11/2020 at 10:12 PM, jock said:

Back to the multitool: if erase eMMC does not work, you may try to use option "Drop to Shell" and then execute:

Expand  

Does Multitool support Terminal window?

  On 12/11/2020 at 10:12 PM, jock said:

Maybe your eMMC is so faulty that it cannot be written in any manner.

Expand  

Exactly!

  On 12/11/2020 at 10:12 PM, jock said:

If you can't write the eMMC, you cannot remove the bootloader and boot the Armbian image from sdcard.

Expand  

I don't think so...

Yesterday I took rk3318-box.dtb from your image, burn my trust.img and starting any Armbian_20.07...current_5.7.8 successfuly.

Definitely except yours(not rc) and LE.

 

Armbian-03.jpg

Armbian-05.jpg

Armbian-06.jpg

Armbian-08.jpg

firefly-dtb-1.txt

Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept