How to take screenshot in android system recovery ? - AT&T Samsung Galaxy S6

i dunno where i have to post this ....
Hello
Is it possible to take a screenshot in android system recovery ? NOT a custom recovery !
i can see here, in the first comment, he was able to capture / take a screenshot in "android system recovery" :
http://forum.xda-developers.com/showthread.php?t=2389595
that's not working with me on both CWM,stock recovery (android system recovery) :'(
i was able to take a screenshot in a custom recovery using the following tool
http://www.addictivetips.com/android/how-to-take-screenshots-in-recovery-aroma-on-android/
but its not working on "android system recovery" because it requires ADB to be enabled...
what can i do to take a screenshot under "android system recovery" ???
thanks a lot for any reply

Related

Reboot in recovery.

Hi. I have a stock based rom, deodexed. I cant' reboot in recovery with the shoutdown menù. I tried also with apps like rom manager, recovery boot does not works, every time goes in normal reboot. Anyone can give me some suggestions?
Although the power button + vol- button work as normal, but i want to set the "recovery reboot" in the menù, also reboot in fastboot and bootloader boot
I have cwm 6.0.4.5...
It happens to me too!
I have deodexed Stock ROM 4.1.2 and I wanted to add advanced power menu with 4 -Way Reboot: Reboot, Hot Boot, Bootloader and Recovery.
I have followed many guides and in particular this (here my post)
Now all reboots work, except Recovery Reboot:
when I select "Recovery" the phone restart normally!!
After several tests, I tried to use some scripts to reboot into Recovery!
First Script:
Code:
#!/system/bin/sh
echo "boot-recovery" | /system/bin/dd of=/dev/block/mmcblk0p5 bs=1 count=13
When I run this script, the phone reboot into Recovery only the first time and any option I selected, the phone always restarts in Recovery! Why?
Second Script:
Code:
#!/system/bin/sh
rm /cache/recovery/command ; echo 'boot-recovery' | dd of=/dev/block/mmcblk0p5 bs=1 count=13 ; reboot ;
When I run this script, the phone reboot into Recovery immediately!
Now I would like know how I can fix this Problem!
And those scripts serve to reboot the phone into recovery via Advanced Power Menu?
I tried everything and I do not know where I'm wrong!
Are you both running cwm? Could that be the issue?
Sent from my Nexus 5 using Tapatalk
Install "Xposed Framework" and "Advanced Power Menu" to get your wanted options...
Ben36 said:
Are you both running cwm? Could that be the issue?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I have tried many Recovery: TWRP 2.3.6.0, CWM 6.0.3.1 and 6.0.4.5, PhilZ Touch.
What do you suggest?
Fladder72 said:
Install "Xposed Framework" and "Advanced Power Menu" to get your wanted options...
Click to expand...
Click to collapse
I dont want "Xposed Framework", I want to fix my problem
glfsd said:
I have tried many Recovery: TWRP 2.3.6.0, CWM 6.0.3.1 and 6.0.4.5, PhilZ Touch.
What do you suggest?
I dont want "Xposed Framework", I want to fix my problem
Click to expand...
Click to collapse
Me too
paolotheking said:
Hi. I have a stock based rom, deodexed. I cant' reboot in recovery with the shoutdown menù. I tried also with apps like rom manager, recovery boot does not works, every time goes in normal reboot. Anyone can give me some suggestions?
Although the power button + vol- button work as normal, but i want to set the "recovery reboot" in the menù, also reboot in fastboot and bootloader boot
I have cwm 6.0.4.5...
Click to expand...
Click to collapse
You have to edit the frameworks to add the option, you'll need the android kitchen for that.
The fastboot reboot won't work, the fastboot boot option will work somewhat if you add "-c "androidboot.mode=normal"" as in fastboot boot [kernel.img] -c "androidboot.mode=normal"
It will have some problems but it'll work.
IcanhasLG said:
You have to edit the frameworks to add the option, you'll need the android kitchen for that.
The fastboot reboot won't work, the fastboot boot option will work somewhat if you add "-c "androidboot.mode=normal"" as in fastboot boot [kernel.img] -c "androidboot.mode=normal"
It will have some problems but it'll work.
Click to expand...
Click to collapse
I think he means that he isn't able to reboot to recovery with the option from the shutdown menu, not that there isn't one.
As he wrote he can't boot to recovery with ROM Manager either.
I had such problems back in the beginning of 4.3 development but and on stock too.
Maybe try to grab a log from boot if you tried to reboot to recovery.
Sent from my LG-P880 using XDA Premium 4 mobile app
Omario-242 said:
I think he means that he isn't able to reboot to recovery with the option from the shutdown menu, not that there isn't one.
As he wrote he can't boot to recovery with ROM Manager either.
I had such problems back in the beginning of 4.3 development but and on stock too.
Maybe try to grab a log from boot if you tried to reboot to recovery.
Sent from my LG-P880 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Rom Manager Free does not reboot in recovery, like other app, but Rom Manager Premium works...
Omario-242 said:
I think he means that he isn't able to reboot to recovery with the option from the shutdown menu, not that there isn't one.
Click to expand...
Click to collapse
exactly
Omario-242 said:
...Maybe try to grab a log from boot if you tried to reboot to recovery.
Click to expand...
Click to collapse
how to do it? I tried with adb
Code:
adb logcat > log.txt
or
Code:
adb logcat -v long > logcat.txt
but there are too much informations and I can not find the problem
I attach also "last_log" found in /cache/recovery/
..I do not know ..... but i think the problem is due to cwm
sorry for my poor english
glfsd said:
exactly
how to do it? I tried with adb
Code:
adb logcat > log.txt
or
Code:
adb logcat -v long > logcat.txt
but there are too much informations and I can not find the problem
I attach also "last_log" found in /cache/recovery/
..I do not know ..... but i think the problem is due to cwm
sorry for my poor english
Click to expand...
Click to collapse
maybe is a cwm problem, anyone can help us?

Everything urbane root easy how-tos and all the files you need in one place (11/26)

The purpose of this thread is to make the rooting process easier with all the files you need in one place to root and tutorials and a list of must have apps
You will be able to find everything you need in one spot.
I TAKE NO RESPONSIBILITY FOR ANYTHING YOU DO TO YOUR DEVICE.
* Please Leave Suggestions On What Else You Would Like To See Included In This Thread
Check back often as this will be a work in progress
Please vote yes or like so I can get a feel for how many people are interested in a thread like this so I can decide whether or not it's worth my time to continue it.
I've also provided two prerooted system images ( just be sure to follow steps 1 thru 12 and step 18 ( optional depending on the image )
Thanks Rob
__________________________________
Let's start by voiding your warranty lol by unlocking the bootloader ( Warning this will erase all data and factory reset your watch ). You will need an adb fastboot program of your choice installed on your computer. I prefer minimum ADB fastboot link in downloads section. Plus the proper drivers ( I will be providing links to them as well later)
Now what I like to do is create a folder on the desktop of my computer and name it urbane. Then download all the files and apps I will need and put the in the folder.
That way you can open that folder and have ADB open at the same time and you can just drag and drop the file your planning on pushing or flashing to your watch by placing it after the proper command. Which will be explained later.
1- On your Watch go to settings
2- Scroll down to about click on it
3- Find and click on build number 5 to 8 times
4- Swipe back and now go into developer options and enable USB debugging
5: Put watch in the charger and plug into computer wait for computer to recognize it and install the drivers
6- Now open terminal emulator (minimum ADB fastboot) on your computer and without the quotes and hitting enter after each command type in
"adb devices"
You should see your watch there
7- Now type
"adb reboot bootloader"
8- Wait for it to boot into fastboot mode then type
"fastboot oem unlock"
9- Follow instructions on device
device will factory reset & reboot
10- Wait for it to fully reboot then follow steps 1 thru 7 again and we can flash TWRP
This is where the drag and drop comes in. In the command line where you see (drop here) that's where you will grab the file/image from your urbane folder and drop it onto the terminal screen
11- Now that you're back into fastboot mode type in
"fastboot flash recovery (drop twrp image here)"
12- OK let's see TRWP so type in
"adb reboot recovery"
Alright now that we know we have TWRP
Do a backup and reboot
Now is a good time to install a file browser, if you haven't already done so and advanced settings. I prefer the file browser I listed in the downloads section as you can send and install apks and files from your phone to your watch.
Now we're going to pull that backup to our computer
Use the file browser on your watch to get the exact path to your backup location which will look something like this /scars/TWRP/BACKUPS/and a bunch of numbers and letters/
So type in
"adb pull /sdcard/TWRP/BACKUPS/*************/ (drop your urbane folder here)/"
Wait for it to finish will take a few minutes and reboot
13- Plug your watch back into computer and wait for computer to recognize it again. Now we can install super su
type in
"adb push (drop su zip here) /sdcard/
14- Reboot into recovery
" adb reboot recovery "
Now's the tricky part, using TWRP's tiny navigation go to install then install zip then to sdcard and find and click on the su zip and install. Reboot
15- Now let's install busybox ( Note if you are going to install skin's kernel you can skip this step and proceed to step 18 as his kernel had busybox built in ). With the watch plugged into your computer. ADB and your urbane folder open
Type in
"adb push ( drop busybox apk here) /sdcard/"
16- On your watch open the file browser and navigate to the busybox apk and click on it. It will install and do is thing, once installed go to your applications find and click on it. It will act weird then probably say it's stopped working but that's OK it's installed and working
17- Kernel time
Type in
"adb push ( drop kernel image here) /sdcard/"
"adb reboot recovery"
In recovery click install then click image then click boot image
And navigate to your sdcard and find skin's kernel click on it and swipe to install
18- Let's start by doing another backup, so assuming you've already backed up at least once already and have pulled the backups to your computer. You can if you haven't already done so delete the backups on your watch before you backup again
19- Next let's take some control over our new custom kernel by installing kernel auditor
Type in
"adb push (drop kernel auditor apk here) / data/local/tmp/"
"adb install -r ( drop kernel auditor apk here)"
Reboot and enjoy
*PLEASE HIT THANKS*
DOWNLOADS
IF YOU ARE NEW TO THIS PLEASE READ THE OP ENTIRELY BEFORE TRYING TO FLASH OR INSTALL ANYTHING.
I TAKE NO RESPONSIBILITY FOR ANYTHING YOU DO TO YOUR DEVICE
Stock images provided by @Skin1980 -
Recovery- https://www.androidfilehost.com/?fid=24269982086988347
Boot- https://www.androidfilehost.com/?fid=24269982086988339
System- https://www.androidfilehost.com/?fid=24269982086988934
__________________________________
Rooted system images
After flashing be sure to wipe caches dalvik/cache
Rooted system imaged 5.1.1 LCA44B (super su installed) - https://www.androidfilehost.com/?fid=24269982087001702
The following images have some unnecessary system apps and watch faces uninstalled to slim down the system and to make room on the system partition to change other apps to system apps . ( you can get back any of the uninstalled apks by flashing the stock image file rebooting then using file browser on your watch navigate to the apk you want back and send it to your phone then after flashing this image send the apk back to your watch and install it)
Rooted system imaged 5.1.1 LCA44B ( su, busybox and kernel auditor installed ) to be combined with stock kernel as skin's kernel has busybox preinstalled -
https://www.androidfilehost.com/?fid=24269982087004874
Rooted system image 5.1.1 LCA44B (su and kernel auditor installed ) for use with skin's kernel-
https://www.androidfilehost.com/?fid=24269982087005360
My personal kernel auditor settings with skin's kernel for best performance-
https://www.androidfilehost.com/?fid=24269982087005023
___________________________________
Stuff for root ( images, apks, zips )
@Skin1980 kernel-
Original thread- http://forum.xda-developers.com/wat...rnel-skin1980s-g-watch-urbane-kernel-t3210691
Direct download-
https://www.androidfilehost.com/?fid=24269982086999750
TWRP 2.8.7.0 -
Original source- https://dl.twrp.me/bass/#
Alternate download-
https://www.androidfilehost.com/?fid=24269982086988968
Wear Supersu zip - https://www.androidfilehost.com/?fid=24269982086990060
Kernel auditor ported by @bitstra from @Grarak work -
Original thread- http://forum.xda-developers.com/android-wear/development/app-kernel-audiutor-4-wear-t3126122
Direct download-
https://www.androidfilehost.com/?fid=24269982086989489
BusyBox on rails apk - https://www.androidfilehost.com/?fid=24269982086989488
Minimum ADB fastboot for windows - http://forum.xda-developers.com/showthread.php?t=2317790
Google ADB drivers can be found here-
http://developer.android.com/sdk/win-usb.html
__________________________________
OTHER USEFUL APPS:
File manager for android wear - https://play.google.com/store/apps/details?id=com.woiapp.filemanagerwear&hl=en
Advanced settings - https://play.google.com/store/apps/details?id=com.sssemil.advancedsettings&hl=en
Reset Wear Client-
Original thread- http://forum.xda-developers.com/and.../app-reset-wear-client-switch-phones-t3058962
Direct download- https://www.androidfilehost.com/?fid=24269982087005403
Wear internet browser- https://play.google.com/store/apps/details?id=com.appfour.wearbrowser&hl=en
VFP benchmark for android wear-
https://play.google.com/store/apps/details?id=jp.flatlib.flatlib3.vfpbenchw
____________________________________
Useful apks that can be sideloaded:
Greenify - https://www.androidfilehost.com/?fid=24269982086999820
/system/appmover
Used to convert user apps into system apps and vice versa ( USE CAUTION )
https://www.androidfilehost.com/?fid=24269982087004923
Other How-tos
Flashing images via fastboot
1- plug watch into computer and start ADB
2- Type in
"adb reboot bootloader"
"fastboot flash boot ( drop boot image here)"
"fastboot flash recovery ( drop recovery image here)"
"fastboot flash system ( drop system image here)"
__________________________________________
Returning to Stock
1- Download the stock images from the downloads section to your computer
2- Follow the above instructions for flashing images
3- Now on the watch click one of the arrows till you see recovery then click the circle (center button)
4- You will see a droid laying down with a red triangle
Swipe from the top left of the screen down to the bottom right
Now you're in recovery
Now you want to do a factory reset
I would just like to give a big thanks to those of you kind enough to hit the thanks button and that goes to a select few as I've had well over 100 downloads, 2100 views and only 21 thanks. I see it all over we really need to show the people that make this site great some appreciation
Awesome work! Keep it up!
Robshr said:
The beginnings of the downloads section is up.
Working on tutorials and links to threads
Also a prerooted (super su and busybox installed) latest version system image
Click to expand...
Click to collapse
So I only have to flash the prerooted system image and I'm fine to be rooted?
(TWRP for a backup at first of course..)
Sent from my HTC One M9 using XDA Free mobile app
meand0g1 said:
So I only have to flash the prerooted system image and I'm fine to be rooted?
(TWRP for a backup at first of course..)
Sent from my HTC One M9 using XDA Free mobile app
Click to expand...
Click to collapse
Yes that's what I'm hoping for. After you flash it you can test by typing
"adb shell"
"su"
And you should see something like this
[email protected]:/ #
If you do then super su is installed and you're rooted
meand0g1 said:
So I only have to flash the prerooted system image and I'm fine to be rooted?
(TWRP for a backup at first of course..)
Sent from my HTC One M9 using XDA Free mobile app
Click to expand...
Click to collapse
Just wondering if it all worked out for you?
Will test it when I own the watch..
Sent from my HTC One M9 using XDA Free mobile app
Doing all of this right now. Will report back when finished! Thanks man
---------- Post added at 06:35 PM ---------- Previous post was at 05:38 PM ----------
Okay so I unlocked bootloader, flashed twrp and rebooted into recovery. I can't backup anything because nothing is mounted. I've tried mounting though twrp with no luck whatsoever. So I tried erasing system and boot using fastboot to flash system image and skins kernel. But when I reboot the watch it boots straight into recovery....
anthonyg45157 said:
Doing all of this right now. Will report back when finished! Thanks man
---------- Post added at 06:35 PM ---------- Previous post was at 05:38 PM ----------
Okay so I unlocked bootloader, flashed twrp and rebooted into recovery. I can't backup anything because nothing is mounted. I've tried mounting though twrp with no luck whatsoever. So I tried erasing system and boot using fastboot to flash system image and skins kernel. But when I reboot the watch it boots straight into recovery....
Click to expand...
Click to collapse
Boot into fastboot and if you already have skin's kernel flashed try just flashing the system image and make sure you wipe the caches Dalvic/cache
Questions- did you flash su or did you use a prerooted image. I think su needs to be installed to do a back up
Robshr said:
Boot into fastboot and if you already have skin's kernel flashed try just flashing the system image and make sure you wipe the caches Dalvic/cache
Questions- did you flash su or did you use a prerooted image. I think su needs to be installed to do a back up
Click to expand...
Click to collapse
I'm using preroot image for skins kernel with kernel auditor . I've tried using
Fastboot flash system "drag and drop system.img" then
Fastboot flash boot "drag and drop skins boot.img"
Then reboot and it goes straight into recovery
The only way I could get data to show up in twrp was formatting data
anthonyg45157 said:
I'm using preroot image for skins kernel with kernel auditor . I've tried using
Fastboot flash system "drag and drop system.img" then
Fastboot flash boot "drag and drop skins boot.img"
Then reboot and it goes straight into recovery
The only way I could get data to show up in twrp was formatting data
Click to expand...
Click to collapse
I'm not sure what happened but somewhere along the line a step was missed or something was either flashed wrong or a corrupt download. I would say to stay over boot into recovery and do a factory data rest and start over
Robshr said:
Boot into fastboot and if you already have skin's kernel flashed try just flashing the system image and make sure you wipe the caches Dalvic/cache
Questions- did you flash su or did you use a prerooted image. I think su needs to be installed to do a back up
Click to expand...
Click to collapse
Robshr said:
I'm not sure what happened but somewhere along the line a step was missed or something was either flashed wrong or a corrupt download. I would say to stay over boot into recovery and do a factory data rest and start over
Click to expand...
Click to collapse
Gonna try download stock images and flash those to see if I can e en get this thing to boot, it doesn't even try it goes straight into recovery.
anthonyg45157 said:
Gonna try download stock images and flash those to see if I can e en get this thing to boot, it doesn't even try it goes straight into recovery.
Click to expand...
Click to collapse
That's strange because I just had to reset my watch back to stock and prerooted with my above post and everything went fine
Please keep me updated so if I have to I can make any necessary changes or help in anyway
Robshr said:
That's strange because I just had to reset my watch back to stock and prerooted with my above post and everything went fine
Please keep me updated so if I have to I can make any necessary changes or help in anyway
Click to expand...
Click to collapse
Was looking over the steps again from OP and it looks like step 10 is missing? Maybe that's something, I'm starting from the beginning
---------- Post added at 07:54 PM ---------- Previous post was at 07:16 PM ----------
Starting to lose hope, I've even tried erasing all data, booting into fastboot
Fastboot flash system (stock system.img)
Fastboot flash boot (stock kernel boot.img)
Whenever I reboot it goes straight into recovery , I've never even saw the android screen
anthonyg45157 said:
Was looking over the steps again from OP and it looks like step 10 is missing? Maybe that's something, I'm starting from the beginning
---------- Post added at 07:54 PM ---------- Previous post was at 07:16 PM ----------
Starting to lose hope, I've even tried erasing all data, booting into fastboot
Fastboot flash system (stock system.img)
Fastboot flash boot (stock kernel boot.img)
Whenever I reboot it goes straight into recovery , I've never even saw the android screen
Click to expand...
Click to collapse
The missing step ten was just a mistake
Fastboot flash only the stock recovery then try to boot into recovery and you should see an upside down android just swipe across the screen to get into stock recovery then fastboot stock image and follow the instruction to root again
Please message me with any other problems as to no clog up the thread
As I will post our findings later
Figured everything out for anyone following this thread. I ended up starting over after formatting data. I flashed everything stock, flashed modified system image and skin1980 boot image then booted rom, went back andf flashed twrp again and everything is working as expected. Not really sure what caused the issue,
Thanks to @Robshr for all of his help
I installed a different file manager on the watch just like you installed the kernel auditor. this file manager gives the message "sdcard inaccessible" when I try to open the sdcard. Do you think that this is doing this because it was installed in the tmp folder? Do you recommend paying for the paid app and I should have access to the sdcard?
Also I was unable to pull the backup from the watch, some error stating some file was not created because it wasn't found?
any ideas?
cubandanger05 said:
I installed a different file manager on the watch just like you installed the kernel auditor. this file manager gives the message "sdcard inaccessible" when I try to open the sdcard. Do you think that this is doing this because it was installed in the tmp folder? Do you recommend paying for the paid app and I should have access to the sdcard?
Also I was unable to pull the backup from the watch, some error stating some file was not created because it wasn't found?
any ideas?
Click to expand...
Click to collapse
As far as the file manager it depends on what one you are using does it state the the free version can't access the sdcard otherwise it should be able to read it
Not sure about the error message you're getting without seeing it
But it sounds like you didn't first copy the image to the sdcard and that's why it can't find it or didn't give it sufficient time to copy before you gave the pull command

RECOVERY - postrecoveryboot.sh - ERROR: 2

Google has no answer for me.
Every time I enter into the recovery and push the message button I get this ERROR: 2.
Everything works fine, its latest TWRP 3.0.2.
Could you tell me something about this error message 2?
What is 'postrecoveryboot.sh'?
How can I get this red message off / without error?
thanx in advance
How do I edit my boot script?
MichaBit said:
Google has no answer for me.
Every time I enter into the recovery and push the message button I get this ERROR: 2.
Everything works fine, its latest TWRP 3.0.2.
Could you tell me something about this error message 2?
What is 'postrecoveryboot.sh'?
How can I get this red message off / without error?
thanx in advance
Click to expand...
Click to collapse
Hi,
I have the same problem. Also on TWRP 3.0.2. and everything seems to work.
Can't find anything about this 'postrecoveryboot.sh' Error 2.
Did you find a solution in the meantime?
Thanks for any help in advance.
Arninho said:
Did you find a solution in the meantime?
Click to expand...
Click to collapse
No, unfortunately not.
If XDA has no solution, who else?
I have the same problem, this is inside the file
Code:
#!/sbin/sh
# Include device-specific vars
source /sbin/bootrec-device
# Turn the LED off
echo 0 > ${BOOTREC_LED_RED}
echo 0 > ${BOOTREC_LED_GREEN}
echo 0 > ${BOOTREC_LED_BLUE}
that error is because this file bootrec-device located at sbin folder always missing when reboot system or recovery
I have try many way
-flash stock rom with flashtool
-flash rom via recovery
-wipe via adb and fastboot
-chmod this file bootrec-device to read only
-remove this file postrecoveryboot.sh just come back after reboot recovery
all that way doesn't work
my Xperia unable to boot right know :crying:
maybe i'll try search what's file that create this??? postrecoveryboot.sh
where's boot script locate???
any help would be apreciated
InAMovies said:
my Xperia unable to boot right know :crying:
Click to expand...
Click to collapse
Thanks for that much information. :good:
A possible 'emergency solution' so that your device reboots again could be attached link.
What really surprised me, no one else has this ERROR: 2, and if not, why not?
http://www.flashtool.net/index.php
You can fix this 'postrecoveryboot.sh' Error 2 with a lower version twrp
I use twrp 2.8.7 which has been uploaded by someone from here androidfilehost.com/?fid=24052804347811669
flash with "fastboot flash boot boot.img" only if you UB, on LB try downgrade your twrp version
and then via file manager, just chmod the file bootrec-device located at sbin folder with read only access
my phone can only be booted only with rom existenz, and it was frequently rebooted and my battery status is unclear, sometimes 65% during the initial boot, and then only a 5% reboot afterwards
I have flash using flashtool with many based rom from 10.5.1.A, 10.6.1.A, 10.7.1.A latest, but it still does not make my phone work just to show sony screen flickered and died with the indicator is still red
all the problems occurred after I had this problem 'postrecoveryboot.sh' Error 2
I still do not know how to turn off the script, when I delete the file after reboot definitely go back there
hoping my phone can be normal again sometime
InAMovies said:
I still do not know how to turn off the script, when I delete the file after reboot definitely go back there
Click to expand...
Click to collapse
Could the cause for the error be a kind of provider branding?
So deeper implemented than the usual firmware.
My device was delivered via German Telekom.
[B]Solution![/B]
After installing Multirom v33 the error message is gone!
Dont ask why, both recoverys, the new one into the FOTA partition from attached link und the older, normal one 3.0.2.0 are error-free! :good:
https://forum.xda-developers.com/xperia-z/orig-development/mod-multirom-v33x-xperia-z-t3432385
I have installed the Modified recovery FOTA, before this error happen all working fine any custom rom working
but after this error, i can boot into recovery and install rom then reboot got bootloop, charger just show blip screen logo
just wanna try your idea with the Multirom v33 non modified
MichaBit said:
Google has no answer for me.
Every time I enter into the recovery and push the message button I get this ERROR: 2.
Everything works fine, its latest TWRP 3.0.2.
Could you tell me something about this error message 2?
What is 'postrecoveryboot.sh'?
How can I get this red message off / without error?
thanx in advance
Click to expand...
Click to collapse
Can You be so Kind to tell me how to flash in the correct way the latest version of TWRP with no error? Thank You very much!!
Ricky_Karmator said:
Can You be so Kind to tell me how to flash in the correct way the latest version of TWRP with no error? Thank You very much!!
Click to expand...
Click to collapse
Download latest recovery 'twrp-3.0.2-0-yuga.img' from link 1.
Put it to your Phone, turn of, push volume + and insert USB-cable for flashmode.
Blue LED-light appears.
Type -fastboot flash boot boot.img
-fastboot reboot
in ADB-connection CMD on your PC --> thats all.
Optional you can use the Tool in link 2.
*Flashing recovery successfully*
https://dl.twrp.me/yuga/
https://twrp.me/app/
MichaBit said:
Download latest recovery 'twrp-3.0.2-0-yuga.img' from link 1.
Put it to your Phone, turn of, push volume + and insert USB-cable for flashmode.
Blue LED-light appears.
Type -fastboot flash boot boot.img
-fastboot reboot
in ADB-connection CMD on your PC --> thats all.
Optional you can use the Tool in link 2.
*Flashing recovery successfully*
https://dl.twrp.me/yuga/
https://twrp.me/app/
Click to expand...
Click to collapse
I wa sure to copy the .img file in "platform-tools" folder in my PC and with cmd type "-fastboot flash boot boot.img" and not to have the file inside the internal memory of my Xperia Z. Obviously i think to rename "Twrp-3.0.blablabla" into boot.img
Ricky_Karmator said:
I wa sure to copy the .img file in "platform-tools" folder in my PC and with cmd type "-fastboot flash boot boot.img" and not to have the file inside the internal memory of my Xperia Z. Obviously i think to rename "Twrp-3.0.blablabla" into boot.img
Click to expand...
Click to collapse
Yes, very correct, copy and rename the file into 'boot.img' to your ADB-folder and flash it. :angel:
Finally with some free time i unlocked and flash the latest TWRP on my old Xperia Z. And yes i've got the same error "ERROR: 2". But everything works from backup to restore and flash Custom ROM. So i think we can nevermind about that
I have the same.
Sometimes my phone randomly reboot, and seems to be some app cause this reboots.
It was happend more and more often. And suddenly couple days ago my phone start to bootloop (just endlesly booting at xperia logo).
I have F5121 stock 8.0 Oreo and done all like in this manual https://forum.xda-developers.com/t/...els-latest-34-4-a-2-118-25-sept-2018.3594502/
So I was have rooted kenrnel twrp 3.2.3.0+DRM-Fix +magisk +FCS_1.3 +debloat script.
Almost 2 years of no problems and this surprise.
When I load to twrp and press menu button i see this:
Updating partition details...
...done
Unable to mount storage
So I was trying do backup of all partitions and after that I go in in wipe menu => advanced wipe => checkbox cache partition => fix patition
than I try to fix all patitions - it doesn't help.
So I do this:
wipe menu => advanced wipe => checkbox data partition => change to exFAT filesystem then => change back to EXT4 filesystem and restore data from backup. And do system/data partitions
and try to restore my backup - and it don't work.
EVEN my older backups don't works - I always become bootloop on xperia logo.
When I download twrp backup to PC and unpack cache.ext4.win\recovery I see file with name last_log.
Thats how last strings of file last_log look like:
~
ro.bootimage.build.date.utc=1533015130
ro.bootimage.build.fingerprint=Sony/omni_suzu/suzu:8.1.0/OPM4.171019.021.R1/4:eng/test-keys
ro.bootloader=s1
ro.debuggable=1
ro.property_service.version=2
init.svc.adbd=running
init.svc.ueventd=running
init.svc.recovery=running
init.svc.ldconfigtxt=stopped
init.svc.set_permissive=stopped
twrp.crash_counter=0
keyguard.no_require_sim=true
tombstoned.max_tombstone_count=50
Running boot script...
I:/sbin/postrecoveryboot.sh process ended with RC=0
Done.
I would like to hear some ideas why that may happen (Unable to mount storage). Coz i lost part of my data and don't wanna have the same experience again and again in future.

Mi 5X - Help me PLS!! im a noob trying my best and i got stucked....!!

NOTE: i cant add pictures as i get the error ::
""The following errors occurred with your submission:
To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!"""
Hi all,
I have Xiaomi Mi 5X with Chinese room and im trying to get a "normal" room like Android One.
Currently when i start device, i get the following sequence:
1. Mi loading screen - see ibb.co/d2wSkz
2. Android One loading screen - see ibb.co/cHoeyK
3. restart Mi loading screen - see ibb.co/d2wSkz
4. Recovery loading screen - see ibb.co/kmVWCe
5. Recovey options screen - see ibb.co/mtFgCe
If i started device holding Volume (-) and Power, loads Fastboot screen
Is visible on Mi loading screen, at bottom, "Unlocked" - i got this steps made as per en.miui.com/unlock/
The current stage was a result of following a tutorial, flashed "Mi5X_tiffany_AndroidOne_8.1.10_8.0" using XiaoMiTool.
Please ask me all needed to help me out on this nightmare, im big noob and dont know how to proceed!
-- how can i add the room into device storage to select in recovery options / install? --> is this a possible solution???
Thanks all for your time on this thread!
Best regards,
MeeeKieee
:
1. download `android-platform-tools` if you cannot run adb
2. falsh TWRP ,download trwp.img ,open `cmd` and run `fastboot flash recovery trwp.img`
3. reboot to trwp and flash room.zip
lslvxy said:
1. download `android-platform-tools` if you cannot run adb
2. falsh TWRP ,download trwp.img ,open `cmd` and run `fastboot flash recovery trwp.img`
3. reboot to trwp and flash room.zip
Click to expand...
Click to collapse
First of all, thanks for your time helping me on this nightmare.
As i told, im noob! so i will try to clarify all the steps you are giving me as much as possible.
you say:
1. download `android-platform-tools` if you cannot run adb
-- i have the platform-tools in C:\Users\USER\AppData\Local\Android\sdk\platform-tools, where i can see "adb" file and when i click it, very quickly shows up a new window that closes immediately after and nothing happens
my question:
-- i downloaded twrp at androidfilehost.com/?fid=817550096634791388
-- then i installed the downloaded twrp using XiaoMiTool
-- since then, as described before:
1. Mi loading screen
2. Android One loading screen
3. restart Mi loading screen
4. Recovery loading screen - TeamWin (see - ibb.co/kmVWCe)
5. Recovey options screen - TeamWin recovery project 3.1.1-0 (see - ibb.co/mtFgCe)
Soo, those this means that a i already got twrp flashed?
How can i flash room.zip using TeamWin recovery project 3.1.1-0, once that can´t add room into the device?
Could your please guide me through all the process?
Thanks again!
NOTE: i cant add pictures as i get the error ::
""The following errors occurred with your submission:
To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!"""
reboot to fastboot with v- and power
open u cmd tool and type `cd C:\Users\USER\AppData\Local\Android\sdk\platform-tools` to this folder
then type `fastboot flash recovery twrp.img `(u twrp file name)
reboot to twro with v+ and power
touch `Install` and choose ZIP file
just try and good luck
u c contact me at https://t.me/lslvxy

Twrp Testing for all versions of op7_pro

This thread is intended to get a fully working twrp for our new device sooner than later by more of us participating.
This is a testing thread so YES ANYTHING CAN GO WRONG. But most likely will not go wrong..
All test builds compiled by me are from @mauronofrio source code
https://github.com/mauronofrio/android_device_oneplus_guacamole_TWRP
This guide was copied and pasted from @mauronofrio Twrp thread.
Install guide:
Actually seems "fastboot boot twrp.img" is not working so we need to use another guide:
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Now you should check which slot are you using with this command "fastboot getvar current-slot"
5. Now you should change the slot in use with this command "fastboot --set-active=*" you should replace with the slot is not in use, for example if you are using slot a the command will be "fastboot --set-active=b"
6. Now you should flash the twrp in the boot partion using this command "fastboot flash boot twrp.img"
7. Now reboot the device with in recovery mode scrolling the menu with the volume button and selecting "Recovery Mode" with the power button
8. First thing go in reboot menu and restore the old active slot
9. Now you can flash the installer (Actually you can do it using sideload, start sideload server from twrp advanced menu and from pc use this command "adb sideload twrpinstaller.zip")
If you are already rooted, you can skip all and directly flash the installer like a magisk module. Always remember that after you flashed the installer you will be unrooted.
Tips:
If you alread have a twrp flashed you can only flash the new installer zip or the new installation method to update your TWRP (remember to flash again magisk or your system will not boot).
If you have some problems with backup, like 255 error or something similar please check this guide: https://forum.xda-developers.com/one...e-999-t3801632
For the Bacups use always "system_image" and "vendor_image" instead of "system" and "vendor".
I need the following logs in order to find issues.
start a terminal window and enter below commands to get the logs
When TWRP boots enter below commands in terminal:
Code:
adb shell "getprop" > getprop.txt
adb pull /tmp/recovery.log
adb shell "dmesg" > dmesg.log
adb logcat > logcat.txt
and post the files here.
Links will be in post #2
Links to test builds
Test-0.2 f2fs filesystem
Twrp.img https://www.androidfilehost.com/?fid=1395089523397969888
Twrp installer https://www.androidfilehost.com/?fid=1395089523397969887
Test-0. 3 ext4 filesystem
Twrp.img https://www.androidfilehost.com/?fid=1395089523397969903
Installer https://www.androidfilehost.com/?fid=1395089523397969902
Under 6. Should we be using "fastboot flash recovery xxx.xxx" or the one from the post?
I might be able to test evening today.
Sent from my GM1911 using Tapatalk
vickyjusme said:
Under 6. Should we be using "fastboot flash recovery xxx.xxx" or the one from the post?
I might be able to test evening today.
Sent from my GM1911 using Tapatalk
Click to expand...
Click to collapse
fastboot flash boot twrp-test.img
Tried this method, but TWRP does not load. Stuck on this (image attached)
Reboot sticks to this screen again. Cannot access fastboot from here, but I can see my device from adb devices. Help me?
https://imgur.com/1s6dejl
Edit: start by power on+volume down loads fastboot.. Phew...
vukis said:
Tried this method, but TWRP does not load. Stuck on this (image attached)
Reboot sticks to this screen again. Cannot access fastboot from here, but I can see my device from adb devices. Help me?
https://imgur.com/1s6dejl
Edit: start by power on+volume down loads fastboot.. Phew...
Click to expand...
Click to collapse
Where are the logs. Please don't test and not provide logs. But thanks for informing test 0.3 doesn't work.
Just wondering how long you waited.

Categories

Resources