I was trying to use busybox to install allshar (dlna.apk/odex) back to system/app/ and it reboots, goes through boot animation, keys light up and then a black screen.
It is recognized in ADB, but when I type reboot recovery--operation not permitted
or when I typed su I get---- su + stopped signal
Type su again and I get [2] Segmentation fault
[1] Segmentation fault
I'm not Bricked right? Otherwise it wouldnt be able to be recognized by ADB and boot up?
Related
Well I need help. Last week when verizon was having probelms with service my friend thought that it was his phone. He got to messing with **** and now he cant load any roms. Im hoping someone can help. When he boots into recovery mood he no longer has the option to flash zip from sd. Also Nand backup is now missing so he can not backup to a restore point. the only options he has is flash update reboot wipe cache and factory reset. I have heard of people losing root but with that would you even be able to boot by pressing power and the volume up key... he wont leave me alone about fixing his problem so any info someone could shed on the situation I would really appreciate... Thanks
leech2082 said:
Well I need help. Last week when verizon was having probelms with service my friend thought that it was his phone. He got to messing with **** and now he cant load any roms. Im hoping someone can help. When he boots into recovery mood he no longer has the option to flash zip from sd. Also Nand backup is now missing so he can not backup to a restore point. the only options he has is flash update reboot wipe cache and factory reset. I have heard of people losing root but with that would you even be able to boot by pressing power and the volume up key... he wont leave me alone about fixing his problem so any info someone could shed on the situation I would really appreciate... Thanks
Click to expand...
Click to collapse
Just redo Amons recovery. That should fix it.
Follow these steps: (Also found in Sticky section)
III: Flashing a Custom Recovery
Flashing a custom recovery will make your life easier when flashing ROMs in the future.
1. Download this file: Recovery.zip
2. Extract file contents to your \tools\ directory of your Android SDK.
3. Open up a command prompt and go to your tools directory, and execute these commands:
* adb shell mount -o rw,remount /dev/block/mtdblock3 /system
* adb push recovery.img /sdcard
* adb push flash_image /system/bin
* adb shell chmod 755 /system/bin/flash_image
* adb shell flash_image recovery /sdcard/recovery.img
4. Success! You now have a recovery partition installed on your phone. You can access it by running "adb shell reboot recovery" or by powering off your phone, holding "Volume Up + Power On"
Once you do this...power down... then volume up + end = recovery..
The behavior of the recovery boot that you are describing is an HTC recovery; it is not Amon_RA. Amon_RA didn't change, it got replaced.
That strongly suggests that "your friend" re-flashed an HTC ROM onto the phone, probably using a HBOOT method (using a "PB00IMG.ZIP" file).
droidkevlar said:
Just redo Amons recovery. That should fix it.
Click to expand...
Click to collapse
droidkevlar assumes here that what got flashed was the HTC Root PB00IMG.ZIP file.
For the sake of "your friend who won't leave you alone", I hope droidkevlar is correct; otherwise your friend has joined the leak club.
Good luck,
bftb0
vash8806 said:
* adb shell mount -o rw,remount /dev/block/mtdblock3 /system
* adb push recovery.img /sdcard
* adb push flash_image /system/bin
* adb shell chmod 755 /system/bin/flash_image
* adb shell flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
or you could do it from the PC with a single command. Put the phone into FASTBOOT mode (power on phone holding down both Send+End/Power), and then
Code:
fastboot flash recovery recovery-RA-eris-v1.6.2.img
The md5sum of Amon_RA v1.6.2 for the Eris is e3932991f097993602af3c7a4b61a4f8
You can check to see if fastboot is communicating with the phone by using the command "fastboot devices". (Note that if running fastboot from Linux, fastboot needs to be run as root to access the USB device).
bftb0
hi,
one of our members in and-roid.ir is facing a strange problem... his phone is s-off and recovery v.3 was flashed.
he was installing a rom and suddenly there was an error in the installation... he tried to enter recovery and restore a back up but when trying to enter recovery from bootloader instead of entering recovery mode it will enter fastboot mode...
he flashed recovery again but no luck...
suddenly when usb was plugged he entered recovery mode... he tried again with usb unplugged and couldn't enter recovery mode...
so after entering recovery mode with usb plugged memory card won't mount... he tried to manually mount it and still no luck...
any ideas what's the problem?and how to trouble shoot it?
any clues at all?
Reflash the misc partition. (you can see how to do this in the root HBOOT 1.00 thread) Or you can boot into recovery...
Go to fastboot
put the custom-recovery.img in your android-sdk/tools folder
fastboot boot (drag and drop recovery.img into cmd or terminal) press enter
so i have to do following commands? correct?
Code:
adb shell
su
...you should have root privileges now (showing #). Next thing is backing up misc partition and replacing it with one from hack4legend-v5.zip. Extract this zip somewhere and fire another command promt there. Now you should upload flash_image binary and misc1-2.img:
Code:
adb push flash_image /data/local/
adb push misc1-2.img /data/local/
...switch back to 1st command prompt and change permission of flash_image_binary:
Code:
chmod 755 /data/local/flash_image
...and backup your current misc partition:
Code:
cat /dev/mtd/mtd0 > /sdcard/misc_backup.img
Now flash misc1-2.img:
Code:
/data/local/flash_image misc /data/local/misc1-2.img
exit
Click to expand...
Click to collapse
I believe so yes
How do I format SYSTEM partition from adb on ideaPad K1 ?
adb shell
and
wipe system
does not work becuase I lack permissions
ClockwordMod installed and replaced k1recovery and I cannot boot into it. I cannot also start CWM, fastboot doesn't work.
When I am in adb and issue:
sdb shell
# recovery
I receive:
[1] Segmentation fault recovery
I need to get to recovery or remove CWM. Any tips will be appreciated.
Are you able to boot to the main screen at all? If so, you should be able to soft reboot (hold power button down), then select "reboot to recovery" from the menu to get to CWM.
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
Hello guys,
Unfortunately I broke my 1+5's screen recently. I can barely see things on the bottom half of the screen and the touchscreen is not responding correctly so I can't unlock my phone anymore (cuz password is needed :good.
I would like to ship it back to 1+ factory so they can repair the screen but they will factory reset my device, this is why I'm requiring your help : I want to get some files which are inside my phone, but I don't know how to do it. I tried some things :
I have access to adb recovery but I'm unable to get su working : adb shell can't mount anything and ls shows nothing in data sdcard and so on.
I have access to adb unauthorized (unlock screen) and I tried to push adbkey.pub into /data/misc/adb/adb_keys with no success, still unauthorized.
In these 2 states adb pull /sdcard does nothing.
Any ideas ?
any solution?
gosuleaf said:
Hello guys,
Unfortunately I broke my 1+5's screen recently. I can barely see things on the bottom half of the screen and the touchscreen is not responding correctly so I can't unlock my phone anymore (cuz password is needed :good.
I would like to ship it back to 1+ factory so they can repair the screen but they will factory reset my device, this is why I'm requiring your help : I want to get some files which are inside my phone, but I don't know how to do it. I tried some things :
I have access to adb recovery but I'm unable to get su working : adb shell can't mount anything and ls shows nothing in data sdcard and so on.
I have access to adb unauthorized (unlock screen) and I tried to push adbkey.pub into /data/misc/adb/adb_keys with no success, still unauthorized.
In these 2 states adb pull /sdcard does nothing.
Any ideas ?
Click to expand...
Click to collapse
did you send it ?did they make factory reset to your phone?did you find any solution?
custom recovery ...
custom recovery have adb enabled, so boot twrp (it will ask for your password to decrypt data if their is encrypted, unfortunately : if so, I don't know sorry).
Nothing2Do.eu said:
custom recovery have adb enabled, so boot twrp (it will ask for your password to decrypt data if their is encrypted, unfortunately : if so, I don't know sorry).
Click to expand...
Click to collapse
You can decrypt the /data partition via adb, without using the touch screen.
The command you need is there:
https://forum.xda-developers.com/showthread.php?t=2484380
You can then adb pull /data/media to get your data.