Database Info

[REQ] Reboot into custom recovery (bootmenu)

Hi, i am MIUI Spain ROM coocker from http://miuis.es and i want to know how to ( which commands) reboot directly into custom recovery in miui or cm7 with bootmenu, i want to know it to implement it in our OTA updater( which reboots into stock recovery by default).
thanks.

I think you should ask Epsylon3, he's working on this stuff.
Sent from my MB525 using XDA App

bihariel said:
Hi, i am MIUI Spain ROM coocker from http://miuis.es and i want to know how to ( which commands) reboot directly into custom recovery in miui or cm7 with bootmenu, i want to know it to implement it in our OTA updater( which reboots into stock recovery by default).
thanks.
Click to expand...
Click to collapse
i think you just have to play a bit with "/system/bootmenu/config/default_bootmode.conf"
maybe it's possible to create a new folder for cwm init
all sources are available to see

Yeah i think it must be possible. Obviously it is possible to auto boot the boot menu every time so just need something to automatically load the CWM after this...

ephumuris said:
Yeah i think it must be possible. Obviously it is possible to auto boot the boot menu every time so just need something to automatically load the CWM after this...
Click to expand...
Click to collapse
that´s the point, but how to load automaticlly the cwm.

The first Nandroid for Defy was possible through any special restart-commands(I don't know which).
Maybe the developer can change the bootmenu so it checks for this so you don't have to change the bootmode.

v0.9.5 have now this feature...
need to write "recovery" in bootmenu/config/bootmode.conf
will be in next nightly
manually selected bootmode (in bootmenu) will stay in default_bootmode.conf (for next reboot)

Epsylon3 said:
v0.9.4 have now this feature...
need to write "recovery" in bootmenu/config/default_bootmode.conf
will be in next nightly
hmm no... will make a new 0.9.5 which use a new file "bootmode.conf" to keep old selected bootmode in default_bootmode.conf
Click to expand...
Click to collapse
Thanks man, i wait for it. just to clarify , i use an ota updater and i want it to flash automaticlly the patches.

available in cm7-110708-1933-NIGHTLY-Jordan.zip and newer builds
need to write "recovery" in bootmenu/config/bootmode.conf
NOT in default_bootmode.conf

Epsylon3 said:
available in cm7-110708-1933-NIGHTLY-Jordan.zip and newer builds
need to write "recovery" in bootmenu/config/bootmode.conf
NOT in default_bootmode.conf
Click to expand...
Click to collapse
ok thanks, but i tried to port it to miui, and not boots, after the blue led it reboots.

keep your 2nd-init binary, this file is dependent of the kernel version
in nightly builds i make a backup of it since i dont upgrade kernel.... unlike miui which force kernel "downgrade" to 343-11

Epsylon3 said:
keep your 2nd-init binary, this file is dependent of the kernel version
in nightly builds i make a backup of it since i dont upgrade kernel.... unlike miui which force kernel "downgrade" to 343-11
Click to expand...
Click to collapse
well i managed to port it and got my updater work but when it goes flashing.
the recovery log says this:
Starting recovery on Fri Jul 8 20:44:27 2011
can't open /dev/tty0: No such device or address
framebuffer: fd 4 (480 x 854)
ClockworkMod Recovery v4.0.0.7
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot emmc /dev/block/mmcblk1p15 (null)
2 /cache ext3 /dev/block/mmcblk1p24 (null)
3 /data ext3 /dev/block/mmcblk1p25 (null)
4 /system ext3 /dev/block/mmcblk1p21 (null)
5 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
6 /sd-ext /dev/block/mmcblk0 /dev/block/mmcblk0p2 (null)
I:Completed outputting fstab.
Irocessing arguments.
I:Got arguments from /cache/recovery/command
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery_stable" "--update_package=/sdcard/download/signed_Swype-ultima-version.zip" "boot-recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=0
ro.factorytest=0
ro.usb_mode=normal
ro.bootmode=reboot
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=0x0000
ro.hardware=jordan_umts
ro.revision=0
Finding update package...
I:Update location: /sdcard/download/signed_Swype-ultima-version.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:verify_file returned 1
E:signature verification failed
Installation aborted.
Click to expand...
Click to collapse
but the zip is signed, so what happens, why it says signature failed, when the zip is signed?

signatures (md5) are in META INF folder

Epsylon3 said:
signatures (md5) are in META INF folder
Click to expand...
Click to collapse
yes i know and the zip is signed and has three files in that folder:
CERT.RSA
CERT.SF
MANIFEST.MF

i dunno, never tried that . . check with google apps zip file...

Epsylon3 said:
i dunno, never tried that . . check with google apps zip file...
Click to expand...
Click to collapse
also ggaps not working.
the problem is E:signature verification failed
how can i disable the verificacion signature on config files?

hmm maybe sdcard is not automatically mounted in this case...
try to check with adb feature in advanced menu...

Epsylon3 said:
hmm maybe sdcard is not automatically mounted in this case...
try to check with adb feature in advanced menu...
Click to expand...
Click to collapse
thanks, but what i want is to get the updater to flash automaticlly, without entering in bootmenu.

bihariel said:
thanks, but what i want is to get the updater to flash automaticlly, without entering in bootmenu.
Click to expand...
Click to collapse
yes i know .... and so you cant check ? This feature was implemented yesterday in bootmenu... I cant test all the features... (of recovery this time)

Epsylon3 said:
yes i know .... and so you cant check ? This feature was implemented yesterday in bootmenu... I cant test all the features... (of recovery this time)
Click to expand...
Click to collapse
check what?
what i want is like in rommanager, you chose aplly patch and the phone reboots automaticlly to recovery ( thanks to your bootmenu 0.9.4 i can do it now) but it fails on flashing the signed zip, it gives signature check fail.

Trouble going from CM10.0 to CM10.1.3

So, after waiting about a year for the next stable CM version I decided to update my HOS from CM10.0 to CM10.1.3.
Now the first thing I did was find information about how to do it and I found out the built in updater was not going to work. I did a full backup and tried anyway in case all I needed was to flash boot.img but after downloading the update the phone just reboots and nothing changes.
The next step was to manually flash the boot.img myself and then install the .zip, so I did it and after flashing the img the phone gets stuck in a bootloop (the circular screen). I immediately rebooted into TWRP and attempted to install CM10.1.3.zip, but the phone does not allow me to. Here's the log it gives me:
I:Attempt to load settings from settings file...
I:Version number saved to '/cache/recovery/.version'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Switching packages (TWRP)
I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
I:Set page: 'flash_zip'
Installing '/sdcard/cm-10.1.3-ville.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Warning: No file_contexts
script aborted: assert failed: getprop("ro.bootloader") == "2.15.4444" ||
getprop("ro.bootloader") == "2.15.0000" ||
getprop("ro.bootloader") == "2.13.0000"
assert failed: getprop("ro.bootloader") == "2.15.4444" || getprop("ro.bootloader") == "2.15.0000" || getprop("ro.bootloader") == "2.13.0000"
E:Error in /sdcard/cm-10.1.3-ville.zip
(Status 7)
Error flashing zip '/sdcard/cm-10.1.3-ville.zip'
Updating partition details...
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Set page: 'flash_done'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'settings'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'settings'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:Copying file /tmp/rec
Click to expand...
Click to collapse
I can flash the 10.0 boot.img back without any problems, and I can also install the CM10.0.zip stable without any problems, so the phone is not in a state of emergency, but this is really bugging me out. Can anyone help me get through this?

You need to update your firmware.
See where it fails? It is checking your hboot and wants it to be 2.15.
So the easy way is to run latest RUU.exe to update to Jellybean, or flash a new hboot.

tivofool said:
You need to update your firmware.
See where it fails? It is checking your hboot and wants it to be 2.15.
So the easy way is to run latest RUU.exe to update to Jellybean, or flash a new hboot.
Click to expand...
Click to collapse
After investigating for a bit I found this thread:
http://androidforums.com/one-s-all-things-root/691874-guide-how-run-ruu-your-htc-one-s.html
It says after using the RUU.exe the phone will be back to stock, both the ROM and recovery. So if I go through with it I'll have to repeat the root process/recovery/rom flash again right? And after that, will I be able to put all the backed up data back into the phone without losing anything? (I'll flash 10.0 again and then do the upgrade, not sure if a 10.0 backup is compatible with 10.1.3)

Rodrows said:
After investigating for a bit I found this thread:
http://androidforums.com/one-s-all-things-root/691874-guide-how-run-ruu-your-htc-one-s.html
It says after using the RUU.exe the phone will be back to stock, both the ROM and recovery. So if I go through with it I'll have to repeat the root process/recovery/rom flash again right? And after that, will I be able to put all the backed up data back into the phone without losing anything? (I'll flash 10.0 again and then do the upgrade, not sure if a 10.0 backup is compatible with 10.1.3)
Click to expand...
Click to collapse
Yep, you will have to lock bootloader (I assume you are S-on)
fastboot oem lock
run the ruu, then unlock, custom recovery, flash rom, fastboot flash boot boot.img.
You will need to save photos, media, wallpapers, ringtones to your pc and put them back after the process. You will lose things like text messages.
I always download apps from the play store rather than trying to restore them. (less problems)

tivofool said:
Yep, you will have to lock bootloader (I assume you are S-on)
fastboot oem lock
run the ruu, then unlock, custom recovery, flash rom, fastboot flash boot boot.img.
You will need to save photos, media, wallpapers, ringtones to your pc and put them back after the process. You will lose things like text messages.
I always download apps from the play store rather than trying to restore them. (less problems)
Click to expand...
Click to collapse
So even though I did a full backup with TWRP if I restore it nothing is saved? Then what is the point

Rodrows said:
So even though I did a full backup with TWRP if I restore it nothing is saved? Then what is the point
Click to expand...
Click to collapse
yes, you are right, if you are going to stay on CM 10.0 you can use the backup. But what is the point of upgrading your firmware?
So basically you are going to be flashing a different ROM by going with the new CM. Restoring your TWRP backup will put you back to CM 10.0. (with new firmware)
The point of a backup is to restore to a time that you wanted before changes were made.

tivofool said:
yes, you are right, if you are going to stay on CM 10.0 you can use the backup. But what is the point of upgrading your firmware?
So basically you are going to be flashing a different ROM by going with the new CM. Restoring your TWRP backup will put you back to CM 10.0. (with new firmware)
The point of a backup is to restore to a time that you wanted before changes were made.
Click to expand...
Click to collapse
I read that people on 10.0 who flash boot.img and then do the update keep their settings/data, and I was talking about doing the RUU/unlock/recovery/CM10.0 to have the exact same thing as before (except for the hboot) and then updating to 10.1.3
Now I'm doubting if the keep settings/data part is true

Rodrows said:
I read that people on 10.0 who flash boot.img and then do the update keep their settings/data, and I was talking about doing the RUU/unlock/recovery/CM10.0 to have the exact same thing as before (except for the hboot) and then updating to 10.1.3
Now I'm doubting if the keep settings/data part is true
Click to expand...
Click to collapse
That sounds reasonable, but if you have problems with apps or bugs, the first thing people will ask is if you dirty flashed or did a full wipe before the install.

tivofool said:
That sounds reasonable, but if you have problems with apps or bugs, the first thing people will ask is if you dirty flashed or did a full wipe before the install.
Click to expand...
Click to collapse
I'll keep that in mind if there are problems. Besides, if something goes wrong I can always go back to 10.0
Thanks for all the help! :highfive:

I don't understand what happened.
I downloaded the RUU for my phone based on the getvar all commands, installed it, re-unlocked the phone, re-installed TWRP, re-rooted the phone, and after an hour I'm still where I started: hboot is not 2.15 so 10.1.3 does not install.
I can still install CM10.0 and restore the backup as expected, but I'm puzzled. I don't know what is wrong with this.
Can't I just get a 2.15 hboot file/zip from somewhere and flash it via fastboot? unless it doesn't work like that, then I guess I'll have to stay on 10.0.

What is your CID? Sounds like we reed to find a newer RUU
Sent from my HTC One S using Tapatalk now Free

tivofool said:
What is your CID? Sounds like we reed to find a newer RUU
Sent from my HTC One S using Tapatalk now Free
Click to expand...
Click to collapse
I don't know about that CID thing but the file I downloaded from http://www.androidruu.com/?developer=Ville was this one:
RUU_Ville_U_ICS_40_S_Vodafone_UK_2.38.161.6_Radio_1.08es.50.02.21_10.09c.50.04L_release_280400_signed.exe
It matched the getvar info perfectly, and since I'm S-On that's the only one I can use

Rodrows said:
I don't know about that CID thing but the file I downloaded from http://www.androidruu.com/?developer=Ville was this one:
RUU_Ville_U_ICS_40_S_Vodafone_UK_2.38.161.6_Radio_1.08es.50.02.21_10.09c.50.04L_release_280400_signed.exe
It matched the getvar info perfectly, and since I'm S-On that's the only one I can use
Click to expand...
Click to collapse
Yep, that would be the RUU that your phone came with when you brought it home from the store, but that is Ice Cream Sandwich version of android.
Now we need someone who knows RUUs and can tell you if Vodafone has a Jelly Bean RUU.
Or now could be a good time to S-Off your phone, then you can run whatever RUU you want.

tivofool said:
Yep, that would be the RUU that your phone came with when you brought it home from the store, but that is Ice Cream Sandwich version of android.
Now we need someone who knows RUUs and can tell you if Vodafone has a Jelly Bean RUU.
Or now could be a good time to S-Off your phone, then you can run whatever RUU you want.
Click to expand...
Click to collapse
Time to S-Off it is

Problem Flashing newer ROMs

I apologize if this has been answered before, I've been searching the better part of the afternoon/evening and haven't been able to find anything that is exactly what I'm seeing.
I have been running Jellybeans ROM for months, but recently it has been giving me fits, so I thought I'd try out one of the newer 4.4 ROMs. I have not done the 4.3 OTA update, so I figured it would be pretty easy. Here's the issue. I can install the 4.3 stock ROM without the firmware, or the Jellybeans ROM, I assume any 4.1.2 ROM. If I attempt to install any of the 4.4 ROMs, the installation aborts immediately with the following error:
Code:
Can't partition non mmcblk device: /devices/platform/msm_sdcc.3/mmc_host/mmc1
Specifically, I've tried BeanStalk and the unofficial CM11. I'm using CWM v6.0.4.6. Any ideas what I'm missing? Thanks for any help you can give.

I'm using twrp so not sure if the cwm you're using is up to date. Recovery not being the latest will give people errors and you'll be unable to flash. I updated my recovery through jrummys Rom installer app
Sent from my SCH-I535 using Tapatalk

Yeah just update your recovery.
Sent from my SCH-I535 using xda app-developers app

Thanks for the responses. That is the latest CWM for the Verizon S3, but just to be sure, I installed TWRP. I am still unable to flash the ROMs. The TWRP log shows the following:
Code:
Error flashing zip '/external_sd/BeanStalk-4.4.225-20140123-d2vzw.zip'
Updating partition details...
I:Data backup size is 0MB, size: 12335MB, used: 1672MB, free: 10497MB, in data/media: 1672MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Set page: 'flash_done'

sully51 said:
Thanks for the responses. That is the latest CWM for the Verizon S3, but just to be sure, I installed TWRP. I am still unable to flash the ROMs. The TWRP log shows the following:
Code:
Error flashing zip '/external_sd/BeanStalk-4.4.225-20140123-d2vzw.zip'
Updating partition details...
I:Data backup size is 0MB, size: 12335MB, used: 1672MB, free: 10497MB, in data/media: 1672MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Set page: 'flash_done'
Click to expand...
Click to collapse
Tough one.
Sounds drastic, but try to Odin back to stock and reroot. I don't even think using a pit file would fix this one.
If it's still throwing an error, then repartitioning might fix the error.
Sent from my SCH-I535 using Tapatalk 2

HTC Butterfly X920d Lollipop 5.0.2 HELP!

Hi,
First, my english is not so good.
I have got a Htc Butterfly X920d smartphone.
Android 4.3, Htc Sense 5.5
Kernel: 3.4.10 g4a55757
Radio: 3A.32.306.04_10.21.1060.16D
Build:3.15.707.4 CL293608
HTC SDK Api: 5.65
Rooted, HBOOT 1.55,S-ON
Installed TWRP v2.3, busybox, su
Yesterday, i deleted the cache/Dalvik cache/data/format data and found a workable version. (I think) --> Butterfly_Sense7.0_L5.0.2_Soul30.0.
Use adb sideload with cmd and i see the install screen (next next.. etc), wipe cache/dalvik cache/data ..
BUT...
Twrp error---> E: Unable to mount /data
E: unable to mount internal storage. :crying:
.... Always restarts and I can see the HTC logo. :crying: :crying: :crying:
I read some threads in xda and other websites, youtube videos but i no lucky.
Help me please!!!!!!

Manage to get the 'S' 'OFF'. With security turned 'ON' it would hinder the installation. There would be guides to go about this.
GUIDE TO DISABLE SECURITY: http://forum.xda-developers.com/showthread.php?t=2683500
Confirmation: http://forum.xda-developers.com/showthread.php?t=2526327
--
Aidroos

AIDROOS said:
Manage to get the 'S' 'OFF'. With security turned 'ON' it would hinder the installation. There would be guides to go about this.
GUIDE TO DISABLE SECURITY: http://forum.xda-developers.com/showthread.php?t=2683500
Confirmation: http://forum.xda-developers.com/showthread.php?t=2526327
--
Aidroos
Click to expand...
Click to collapse
Aidroos thanks your reply.
Hm, my phone Butterfly X920d , not butterfly S.
I tried Rumrunner, but it did not work. ( Rumrunner say ' adb not connected, but connected... and debugging mod disabled)
Hm, i found firewater file and How-to-do guide, but not work, becouse i can not update this file.
TWRP Errors:
E:unable to mount '/data'
E:unable to recreate /data/media folder
updating partition details...
E:unable to mount /data
E:Failed to wipe dalvik
updating partition details...
E:unable to mount storage
Linux kernel updates help? (i have got Boa kernel)
-- android_LP5.0.2_kernel_htc_dlxub1 --
Link:GithuB
I were downloaded VMware 11 , install ubuntu 15.04 , linaro toolchain 4.9 but not compile the kernel ...
What do you think? - Anybody help me? i am really noob.
JB 4.3 or LP 5.0.2?

Twrp (error=255 on restore)

Hello,
I NEED SOME HELP
I made a backup of my phone using TWRP. When I try to restore from the backup I created, I get a "E:extractTarFork() process ended with ERROR=255" error message when it tries to restore the data.
Anyone know the fix for this?
Code:
I:Restore filename is: data.ext4.win
I:Restore file system is: 'ext4'.
Wiping Data...
Wiping data without wiping /data/share ...
I:Unable to unlink '/data/bugreports'
I:Unable to unlink '/data/skin'
I:Unable to unlink '/data/light'
I:Unable to unlink '/data/.hwplace'
I:Unable to unlink '/data/bflag'
I:Unable to unlink '/data/su.img'
I:Unable to unlink '/data/stock_boot_e0f9860555e8bb7e5681625b1e4fbf547191ac19.img.gz'
Done.
Restoring Data...
I:Multiple archives
I:First tar file '/sdcard/TWRP/BACKUPS/P6Q7N14A11007468/2016-04-25--14-39-12/data.ext4.win000' not encrypted
I:Extracting uncompressed tar
prefix:
==> tar_extract_all(TAR *t, "")
E:Unable to extract tar archive '/sdcard/TWRP/BACKUPS/P6Q7N14A11007468/2016-04-25--14-39-12/data.ext4.win000'
I:Error extracting '/sdcard/TWRP/BACKUPS/P6Q7N14A11007468/2016-04-25--14-39-12/data.ext4.win000' in thread ID 0
E:Error extracting split archive.
E:extractTarFork() process ended with ERROR=255
I:Set page: 'action_complete'

Are you using TWRP 2.7.8.0 and android 6??? It happened to me too.
Update to TWRP Recovery 3.0.2-0 Mate7 Android 6.0 (http://forum.xda-developers.com/mat...overy-twrp-2-8-7-0-mate7-android-5-1-t3156779)...
I am not sure (i did not try) if backups made with 2.7.8.0 can be restored with 3.0.2-0 without errors, but I can assure that 3.0.2-0 backups works perfectly...
Ciao.

leonardus_magnus said:
Are you using TWRP 2.7.8.0 and android 6??? It happened to me too.
Update to TWRP Recovery 3.0.2-0 Mate7 Android 6.0 (http://forum.xda-developers.com/mat...overy-twrp-2-8-7-0-mate7-android-5-1-t3156779)...
I am not sure (i did not try) if backups made with 2.7.8.0 can be restored with 3.0.2-0 without errors, but I can assure that 3.0.2-0 backups works perfectly...
Ciao.
Click to expand...
Click to collapse
Well...
I have TWRP Recovery 2.8.7.0 and had made a backup of my phone on Android 5.1.1 before updating to Android 6.0. So, the backup that I'm trying to restore is Android but my phone is now on Android.
The reason I want to restore is to get a hold of a certain app and data from it.