Database Users

Stuck at boot screen

Hi.
It all happend when i wanted to replace the libwebcore.so file in the /system/lib.
So i did it. but its properly the wrong libwebore.
so i restarted the phone, but now, its stuck at the tattoo screen.
I can connect it to the computer. adb can see it. but i cant su neither mount which requires su.
It's the custom rom. i have no recovery image installed.
i CAN access fastboot AND recovery mode
I tried flashing a rom via HBoot by renaming the rom to CLICIMG.zip. but it doesnt work. phone says no image or wrong format.
Any suggestions?

Well, this really sucks
Now i cant even access adb. I pressed home+back key to reset the phone.
now its just stuck on the tattoo screen like just before but adb devices dont see anything.
Pleassee someone? i really need help on this one!
Hboot doesnt seem to help much. it cant detect anything. i had 3 files on the sdcard (all is amon_ra), just named differently: CLICDIAG.zip, CLICIMG.zip and CLICIMG.nbh
but it doesnt do anything :'(

Do you have a backup?
Have you tried to install recovery img via adb? If you can do this you can just do a backup of your current rom, try somehow to get your sd-card seen by the computer and copy the files of your old backup files to your new backup, asked to replace select yes.( I used a different phone to copy my backup files to the sd card when I couldn't get past startup screen.)
Good luck.

XabdullahX said:
Well, this really sucks
Now i cant even access adb. I pressed home+back key to reset the phone.
now its just stuck on the tattoo screen like just before but adb devices dont see anything.
Pleassee someone? i really need help on this one!
Hboot doesnt seem to help much. it cant detect anything. i had 3 files on the sdcard (all is amon_ra), just named differently: CLICDIAG.zip, CLICIMG.zip and CLICIMG.nbh
but it doesnt do anything :'(
Click to expand...
Click to collapse
Where you found these files?
To flash the rom from hboot you need the rom.zip file of your stock rom(renamed as CLICIMG.zip)

I have the same problem! stuck on "Tattoo" screen and boot again and again.
I have the goldcard with CLICIMG.zip and it loads on HBOOT and install all (boot,radio,recovery,etc.. ) but when it ends, returns to the same....
HELP PLEASEEE!!!

Do you have Amon_Ra or Clockworkmod recovery installed? If so you can try wiping the Dalvik cache and try rebooting. Most boot loops I had were resolved this way. Wiping data and cache totally might also help.
If you can access adb and device is rooted, you should be able to use "adb shell" command and have a rooted terminal with the "#" sign after running su. In that case you can also manually wipe Dalvik cache by deleting everything under /data/dalvik-cache/
$su
#cd /data/dalvik-cache
#rm *
#exit
$exit
Click to expand...
Click to collapse
Good luck!

tihe problem is that i can´t access to the phone by adb
i put "adb shell" and it says: "error: device not found"
the phone screen shows a phone and triangle with exclamation

[FIXED]Startup Pin not working

Yesterday my battery got to 0 and I didn't charge. Today when I plugged in my phone startup pin came up as usual since I have set it up. I typed the pin but it was not working! after several tries and reboots it finally said Your pin is correct but files are corrupt bla bla bla and I pressed the reset button hoping that the pin will be removed but it didn't. It booted into twrp and well it asks me for pin there too. The TWRP version is 3.0.2 and my phone is rooted. I have tried to wipe using adb through - adb shell recovery -wipe_data but no luck. I have also tried the wipe option on find my device but as I had guessed it didn't work.
Any suggestions?
EDIT- Found the fix myself-
Get minimal adb tools https://goo.gl/p3UdHg
open cmd as admin and type command-
Code:
cd C:\adb
Boot into fastboot mode on your phone and connect to pc via usb
back to the cmd window type the following commands-
Code:
fastboot devices
fastboot -w
after that is done you reboot your phone. It is quite possible that you will have bootloop so go boot into recovery and format all data and flash a new rom.

heres an update -
I deleted system partition and data partition and remade them with the exact same size and in the exact same sectors.

It's possible to flash without LCDscreen?

Hi. My normal screen just been destroyed, and it's not a big problem 'cause I normally use the EPD screen for everything, but I need it for flashing, backuping or restoring ROMs. Even for a factory reset I need the LCD screen for the first start configuration.
There is a way to do it just using the eInk screen? As long I know, adb can't do that. Maybe just fastboot with his partition-by-partition backup can do that, but don't know how to do it.
I am wrong with the impossibility for doing that with adb?
Thanks

Still in this quest...
I reafirm myself in the impossibility of flashing with adb (as I think for sideloading you need a custom recovery). I tried with "fastboot -w update xxxx.zip" with the full FOTA of android 6 RU version, and it came to me the error of missing android-info.txt and android-product.txt. I think about getting them from another ROM for yotaphone2, but prefer to ask you before.
The other option is to flash every single partition with fastboot, which is easy, but I have to manage how to do it with the format that my FOTA has.

eReader Fan said:
Hi.
Click to expand...
Click to collapse
I think you are looking for the most difficult ways and are unlikely to find them,It's easier to get a new screen.

Sure, but a lot more expensive.
It is a long quest since I started, but I think I almost did it!!!

It will be nice if you achieve it to post a tutorial
I got same problem, or just didn't thought about that till I restored the phone and realised what I did!!

It should be possible to make the phone usable.
Seeing recovery on the back screen will never be possible I think unless a skilled person puts tons of work into making that work, but you don't really need it.
I found that you can skip the initial setup by manipulating the /system/build.prop.
So if you can get an adb shell with the system partition mounted writable, then you can edit the file to skip the setup which should make it possible to immediately use the mirroring mode....
Getting an abd shell should be possible by first going into fastboot mode(using power+voldown) and then booting twrp recovery ( https://forum.xda-developers.com/yotaphone-one/development/twrp-3-0-2-0-yotaphone-2-t3494023)
Code:
fastboot boot twrpimg.img
Then wait a little until twrp is booted (just wait for a minute)
then open an adb shell:
Code:
adb shell
then mount the system in writable mode and add the setup skip line to the build prop:
Code:
mount -rw system
echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
and then reboot (still in adb shell):
Code:
reboot
I tested that you can go into twrp and mount the system writable but since I don't wanna reset my device, I cannot say for 100% sure that you will then be able to immediately use mirroring mode!
Also, for this to work, i think your bootloader needs to be unlocked. You can also do that using fastboot, but there is a next step which pops up on the normal screen, but it either just pressing power-button to confirm or pressing voldown of volup first and then pressing power to confirm you wanna unlock, so no touchscreen interaction needed. Beware that unlocking the bootloader erases userdata!
Lastly, you need to have fastboot and adb installed, go xda and google if you are not familiar enough with that.
Greets and good luck

tomgaga said:
It should be possible to make the phone usable.
Seeing recovery on the back screen will never be possible I think unless a skilled person puts tons of work into making that work, but you don't really need it.
I found that you can skip the initial setup by manipulating the /system/build.prop.
So if you can get an adb shell with the system partition mounted writable, then you can edit the file to skip the setup which should make it possible to immediately use the mirroring mode....
Getting an abd shell should be possible by first going into fastboot mode(using power+voldown) and then booting twrp recovery ( https://forum.xda-developers.com/yotaphone-one/development/twrp-3-0-2-0-yotaphone-2-t3494023)
Code:
fastboot boot twrpimg.img
Then wait a little until twrp is booted (just wait for a minute)
then open an adb shell:
Code:
adb shell
then mount the system in writable mode and add the setup skip line to the build prop:
Code:
mount -rw system
echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
and then reboot (still in adb shell):
Code:
reboot
I tested that you can go into twrp and mount the system writable but since I don't wanna reset my device, I cannot say for 100% sure that you will then be able to immediately use mirroring mode!
Also, for this to work, i think your bootloader needs to be unlocked. You can also do that using fastboot, but there is a next step which pops up on the normal screen, but it either just pressing power-button to confirm or pressing voldown of volup first and then pressing power to confirm you wanna unlock, so no touchscreen interaction needed. Beware that unlocking the bootloader erases userdata!
Lastly, you need to have fastboot and adb installed, go xda and google if you are not familiar enough with that.
Greets and good luck
Click to expand...
Click to collapse
I might try it... It looks a little difficult for me.
But what bothers me is the unskippable tutorial from the beginning that shows you how to use the 2 screens...
Anyways I can always use it for spare parts

TWRP not working anymore on Shield (2015) Version 7.2.1?

Hello everyone,
I've wasted my Christmas days to - unsuccessfully - re-root a Shield (16GB; 2015) after upgrading to Software 7.2.1. I need to use more than one USB mass storage device and to be able to copy from one to another, so I want to re-enable Stickmount.
The device was rooted before (which means the bootloader was already unlocked, too), and enabling USB debug, finding the device on my PC via "adb devices" was no problem, either. Issuing "adb reboot bootloader" went fine, too, the device could now be seen via "fastboot devices".
So, I flashed the TWRP image (I actually tried three different versions, 3.0.2, 3.1.1, and the most recent 3.2.3). All seemed to load fine (it spewed out two time values followed by OKAY, took about one second), but the reboot that follows only shows the NVIDIA logo forever without anything else happening (the longest I waited was 20 minutes) - according to the docs I could find (and had used before), TWRP should appear after about 15 seconds.
So, I'm stuck. I cannot get TWRP to start which prevents me from sideloading SuperSU, which means I can't use Stickmount.
Is there anything I did wrong? Is there any other way to get Stickmount installed onto my Shield? Any help is appreciated.
Cheers, Pit.

You'll need to wait until TWRP gets updated to get around the new android security measures. So keep checking TWRP website periodically to see when a new version is released.
You could have found this out if you went to Nvidia Shields Android TV forum and read some posts.

I was reading here, as well as at the nvidiashieldzone, where the tutorials are up, plus I was googling for the errors I was getting to no avail. Sorry for not finding every post on every forum on the internet, and thanks for giving the right pointer.
That means there is currently no way whatsoever to get the Shield rooted on 7.2.1., right?

Not just now, there's a guide to root 7.2 - using a developer image, and there's a chance of bricking - best to wait until TWRP is updated - also you don't need to root to use stickmount.
You only need to do something like this:
adb reboot bootloader
fastboot boot twrp-3.2.3-0-foster.img
#in twrp - mount/system - select storage - internal storage
adb shell
pm install -i "com.android.vending" -r /sdcard/Download/stickmount.apk
adb reboot
That way you can use your apk without being rooted - and your device will still be secure, and you can use widevine etc for netflix and other apps that check to see if your device is rooted.
Or you can just push the driver files stickmount uses like this:
adb reboot bootloader
fastboot boot twrp-3.2.3-0-foster.img
#in twrp - mount/system - select storage - internal storage
adb push hosts /system/etc/hosts (example file)
adb shell "chmod -R 644 /system/etc/hosts"
adb reboot

Thanks for the info - if I understand this correctly, I can install apks with root-like permissions using TWRP without rooting the whole device, right?
I will try that out once TWRP is working again.

[guide] Recover data from unencrypted S7 with broken screen

Hi,
I got help from ivan_meler and I couldn't find the steps here, so I thought I would post them for reference.
If you have an unencrypted S7 with a broken screen, you can get your data back from adb commands in a terminal (tested on my phone with TWRP, but I guess it should work with other recoveries)
The trick is to get it to boot in recovery mode, which is not easy if the phone is on (which it will most probably be, since you can't turn off the phone without the screen). To do that, press volume down + power for long enough to force a reboot, and, as soon as the phone reboots change to volume up + power + home.
That will get it in recovery.
After that, your phone should be recognized with $ adb devices as recovery instead of unauthorized. Then, $ adb shell mount will mount the filesystem in an adb shell, and you can browse the filesystem with $ adb pull /sdcard/.... to get your data back ! Most files will be in /sdcard/ or /data/
That said, encrypt your phones, and keep backups, that's a better way to go !