1

I was trying to setup the 7 inch touch screen with my raspberry pi. And admittedly, did one blunder after another :(

The information on the internet rare on setting this touchscreen up. So once I get mine working, the first thing I will do is write a tutorial for this.

The raspberry itself was running: Berryboot with an OS image of Raspbian Stretch.

The touch screen tutorial asked to add these settings to the config.txt. To do so, I added the following settings through here:

enter image description here

The settings I added were for the HDMI:

max_usb_current=1
hdmi_group=2
hdmi_mode=1
hdmi_mode=87
hdmi_cvt 800 480 60 6 0 0 0

I rebooted and the display was distorted a bit. So I installed git library as instructed in screen tutorial:

https://github.com/goodtft/LCD-show.git
chmod -R 755 LCD-show
cd LCD-show/

Ran the command for 7 inch screen:

sudo ./LCD7B-show

And from this moment, I can't get the screen back. I have tried attaching HDMI to tv, to touchscreen. No use. Can't even SSH in.

So to remedy it, I took the sd card out, edited the config.txt file myself and removed all the changes I made. Tried again, the screen did appear but berryboot was stuck on Colorful display it gives in the start.

At this point, I went all in and swapped the config.txt on the SDcard with the default berryboot config.txt file.

Now when I start, berryboot does start to the point where it asks settings for the first login: enter image description here

I do the settings and get to a linux shell with this written:

Emergency recovery shell activated
/bin/sh: can't access tty; job control turned off
/ #

Hope you guys are still with me till now :)

Now, is there any possibility I can my raspbian image back as it was?

UPDATE:

It is a chinese made 7 inch touchscreen compatible with Raspberry pi 3. The cd drive which came along with it contained the english manual on how to set it up. It also includes an image for the Raspbian-Jessie 2017-01-11 having settings already done for this display.

The last date modified of the files on the CD are August 2016 so I guess this display is not very ancient. It is the same thing as this one.

So the question still stands:

1) Can I somehow recover the data by manipulating the recovery shell? 2) Any guidance on how to set this display up?

UPDATE:

Found this excellent link about this touchscreen. Turns out the version I have is 3.0. So the steps of installing the Github library wasn't needed for my version. I just needed to set up the resolution.

  • We get a lot of posts about screens like this about various "compatible with" screens. Unfortunately, there are either too many of them and/or not enough people here who use them for most of those to be solved (it does sometimes happen though; if this works out for you please post an answer of your own). The usual advice is that the $40 you saved on not buying the official screen may be taken out of you in wasted hours, irresolvable glitches, and sometimes getting stuck with an out of date kernel due to binary only support modules. – goldilocks Sep 30 '17 at 19:41
1

The LCD7B-show script does this:

sudo cp -rf ./boot/config-7B-800x480.txt /boot/config.txt 
sudo cp ./usr/cmdline.txt /boot/
sudo cp ./usr/inittab /etc/
sudo cp -rf ./usr/99-fbturbo.conf-HDMI /usr/share/X11/xorg.conf.d/99-fbturbo.conf 
sudo reboot

Which is more than just changes to /boot/config.txt -- and note it overwrote that instead of appending whatever was necessary. Appending would override any previous duplicate directives in the file without erasing the rest of your configuration (it might be the other way around, i.e., later directives override, so they should have been appended). A point to take from that is whoever wrote this either didn't know (== did not bother to research) or did not care about doing things in a more responsible way.

Also note that /etc/inittab is atavistic and no longer used (unless you have not upgraded from Raspbian wheezy).

The major problem may have been the overwriting of /boot/cmdline.txt.

I was trying to setup the 7 inch touch screen with my raspberry pi.

By "the" do you mean the official one? If so I have no idea why you are using this "goodtft" github thing.

If it isn't that one and the instructions from the manufacturer/distributor were to use this, that's unfortunate -- caveat emptor. It may be that you simply cannot use the product (hopefully it can be returned). I suspect there are plenty of these kinds of things around that were released years ago and people are still selling off despite the fact no one has bothered keeping software support for them updated.

  • see update for details about the display – Mohsin Anees Sep 30 '17 at 18:30
  • And the original question is that is it possible to somehow recover the data through the recovery shell or not? – Mohsin Anees Sep 30 '17 at 18:31
  • 1
    And the original question is that is it possible to somehow recover the data through the recovery shell or not? - Dunno. If I had data I wanted I'd just plug the drive into something else and get it that way, then reinstall. Of course, if you kept regular backups you could use those, which is why people keep backups...there's no magic bullet solution for having not done so, or no one would bother. It's sort of like, "I have no insurance and my house burned down, what can I do?" -> Jump in your time machine, go back, and buy insurance of course! – goldilocks Sep 30 '17 at 19:44

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.