Database Develop

Problem installing OpenRecovery

Hi guys,
I'm having a problem installing OpenRecovery to my phone and hope that you will have a hint for me.
What I have:
Motorola Milestone (Firmware 2.2.1, Vodafone branding)
RSD Lite v5.0
Vulnerable SBF: vulnerable_recovery_only_RAMDLD90_78.sbf
Androidiani OpenRecovery 3.3
What I do:
Save OpenRecovery folder and update.zip file from Androidiani OpenRecovery to my SD Card
Boot Milestone holding Up on DPAD
Plugging USB Cable in and starting RSD Lite (Note that it shows my phone, but no IMEI/ESN/MEID)
I select the vulnerable SBF File and click "Start" (holding the Up Button on DPAD while doing it)
Once RSD Lite shows PASS as Result I unplug the USB Cable and switch off the milestone
I switch on the milestone holding the X-Key pressed.
In the triangle screen I press volume-up and camera.
I select apply sdcard:update.zip
Now the following is shown (yellow font):
Code:
E:Can't open /cache/recovery/command
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
So far I tried
Using vulnerable SBF files from different sources
Running RSD Lite as administrator
Can anyone tell me, what I'm doing wrong?
Thank you.

After some experimenting I solved the problem: Obviously the update.zip file got altered after putting the SD-Card in the phone (don't know how).
So what I did is to deleted the update.zip file and OpenRecovery folder from the SD-Card, flashed the vulnerable SBF, put the files mentioned again on the SD (after turning of the phone and inserting the SD into my PC) and booted into the triangle screen.
...and it works.
Thread can be closed.

Days ago i had this... lol..
Well, thx for the solution

Hi..
thank you for your solution..
but can u pls gave us the tools you used..?
* Motorola Milestone ( supported arabic language if you have)
* RSD Lite v5.0
* Vulnerable SBF: vulnerable_recovery_only_RAMDLD90_78.sbf
* Androidiani OpenRecovery 3.3
thank you so much

[Q] I9000 Kernal

Ok, steps taken so far include:
- Rooting device with Zerg through SuperOneClick
- Flashing Device with ClockwordMod Recovery
- Rebooting into Recovery Mode,
- Wipe Cache etc
- Install Update from SD
- Get to 25%, and get signature unable to be verified.
This happened with CM 10.1 20130429 Nightly, Xylon 20130412, And a few others which I have deleted the files from my computer so unable to remember names/versions.
I am unable to use Odin to flash the kernal, as Odin will only read .tar, and all downloads come out as .zip. Attempting to convert them to TAR fails as well.
Using Clockwork Mod Recovery isn't working either to reboot and install, as it has the same issue of unsigned files.
Device: GT-I9000T
Firmware: 2.3.3
Baseband: I9000TDVJV4
Kernel: 2.6.35.7-I9000TDVJV6-CL530973
[email protected] #2
Build No: GINGERBREAD.DVJV6
Any Help would be appreciated

Just an update, since I have now tried again. Actual Error Message and process is:
--Copying media files ...
Successfully copied media files.
# MANUAL MODE #
-- Applying Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/TEL/system/'.
successfully applied multi-CSC.
-- Install /sdcard ...
Finding update package...
Opening update package ...
Verifying Update package...
E: failed to verify whole-file signature
E:signature verification failed
Installation Aborted.

OK, managed to get it fixed by downloading Dark's recovery kit, I was then able to flash everything upto how I wanted it. So now running 4.2.2 on my GT-I9000T =D

Can you please explain what you're trying to do exactly?
Sent from my GT-I9000 using xda app-developers app

Binary Update fails SuperSU 2.4.6

Hello,
I am having a hard time getting SuperSu 2.46 installed. When I first install it, a dialog says "The SU binary needs to be updated. Continue?" I press Continue and choose the "Normal" mode. It fails. If I retry and select the TWRP/CWM mode, it will eventually fail with the error:
E: failed to verify whole-file signature
E: signature verification failed
I've attached as much info as I could from this article:
http://forum.xda-developers.com/apps/supersu/support-update-failures-t2907365
Model: RK3188 (China)
Android Version: 4.4.4
Kernel: 3.0.36+
Build: rk3188-eng 4.4.4 KTU84Q
After booting to TRWP mode, last_log is empty.
There was not a /tmp/recovery.log either.
I have the install log and also the list of various su commands but I do not see an area to upload files here.

Having same problem over here, its recomended that you download the supersu version you want into a zip file, then flash the zip into the system
Sent from my SCH-I545 using Tapatalk

I need help with OTA adb sideload update.

Hi, the other day I unlocked the bootloader of my Z3 Play, yesterday I got a notification for a new update, the January Security Patch or "OPWS28.70-56-8". I managed to get the update file looking for the URL in the logcat. When I downloaded this file I manually added ".zip" because it had no extension. And I followed all the steps in order to get this OTA using the stock Recovery.
I type "adb sideload ota.zip" and I get stuck because of an error, it suddenly stops in the first step at 47%, in the command prompt I get "Total xfer 1.01x" and on my device, on the Recovery menu it reads:
"Error applying update: 20 (ErrorCode::kDownloadStateInitializationError)
E: Error in /sideload/package.zip (Status 1)
E: Failed to open driver control: No such file or directory
Installation aborted"
I can use my Z3 without problems, is not bricked. But It would be nice if someone could tell me what I am doing wrong.
In any case, here it is the relevant info:
Model XT1929-6 (LATAM)
Software version: Blur_Version.28.231.6.beckham.ret
Carrier: attmx

Lewerosky said:
Hi, the other day I unlocked the bootloader of my Z3 Play, yesterday I got a notification for a new update, the January Security Patch or "OPWS28.70-56-8". I managed to get the update file looking for the URL in the logcat. When I downloaded this file I manually added ".zip" because it had no extension. And I followed all the steps in order to get this OTA using the stock Recovery.
I type "adb sideload ota.zip" and I get stuck because of an error, it suddenly stops in the first step at 47%, in the command prompt I get "Total xfer 1.01x" and on my device, on the Recovery menu it reads:
"Error applying update: 20 (ErrorCode::kDownloadStateInitializationError)
E: Error in /sideload/package.zip (Status 1)
E: Failed to open driver control: No such file or directory
Installation aborted"
I can use my Z3 without problems, is not bricked. But It would be nice if someone could tell me what I am doing wrong.
In any case, here it is the relevant info:
Model XT1929-6 (LATAM)
Software version: Blur_Version.28.231.6.beckham.ret
Carrier: attmx
Click to expand...
Click to collapse
i never got the updat notification so i manuelly flash the bootloader and everything to be honest if you want i can upload the folder with litterally everything you need including my homemade batch file to do all the work for you haha

hello
can you provide the update file zip?
Lewerosky said:
Hi, the other day I unlocked the bootloader of my Z3 Play, yesterday I got a notification for a new update, the January Security Patch or "OPWS28.70-56-8". I managed to get the update file looking for the URL in the logcat. When I downloaded this file I manually added ".zip" because it had no extension. And I followed all the steps in order to get this OTA using the stock Recovery.
I type "adb sideload ota.zip" and I get stuck because of an error, it suddenly stops in the first step at 47%, in the command prompt I get "Total xfer 1.01x" and on my device, on the Recovery menu it reads:
"Error applying update: 20 (ErrorCode::kDownloadStateInitializationError)
E: Error in /sideload/package.zip (Status 1)
E: Failed to open driver control: No such file or directory
Installation aborted"
I can use my Z3 without problems, is not bricked. But It would be nice if someone could tell me what I am doing wrong.
In any case, here it is the relevant info:
Model XT1929-6 (LATAM)
Software version: Blur_Version.28.231.6.beckham.ret
Carrier: attmx
Click to expand...
Click to collapse

Motorola XT1929-6 Your Phone Has loaded Diferent operating system. Help!
The phone was purchased at AT & T Mexico. When you start, your phone has been loaded with another system. please help. Software 9.0. ATTMX carrier
Model XT1929-6. Single sim, 64GB Storage 4GB Ram

Accidentally Disabled OEM Unlock on SM-N950N (w/ SM-N950F CSC), how to Recover Data?

Hey guys,
Here's the situation. I was in the process of completing the setup of my 768GB Note 8 (SM-N950N) with Dr.Ketan P12 custom ROM, and RZ Kernal (for DriveDroid support). Out of nowhere, my Note 8 camera just stopped working, and the Dr.Ketan ROM Tools and Tweaks Pro apps could no longer be opened. I began back-tracking my steps; tried reverting magisk back to v20.1, tried dirty flashing the ROM again, all to no avail. In the process of troubleshooting, figured it could be something I toggled under developer settings. Noticed that my OEM Unlock toggle was turned on, even though I recall seeing it turned off earlier during the configuration process (as explained by @dr.ketan here, scroll to Note for OEM Issue). Thinking it's ineffective, I turned it off and was prompted to reboot my device, just to get stuck at the boot screen
I came across the following forum post describing how to recover from the boot loop, without needing to delete any data, by flashing the latest available official firmware AP***.tar (removed the .md5 extension) file using Odin3:
https://forum.xda-developers.com/sprint-galaxy-s6/help/custom-binary-blocked-frp-lock-how-t3581010
The problem is, during the flashing of the Dr.Ketan P12 custom ROM, I chose to flash the SM-N950F OMC for SM-N950N, in order to use a Korean-Free CSC (more details on why explained here). So, even though I've attempted all of the following:
- flashed the current latest available official firmware AP***.tar file for SM-N950N,
- simultaneously flashed the current latest BL/CP/HOME_CSC***.tar.md5 and AP***.tar firmware files via Odin,
- flashed the latest TWRP***.tar custom recovery (failed probably due to OEM unlock being disabled),
- wiped cache via the stock recovery,
- tried booting via the "Lacking storage booting" option in the stock recover,
- tried booting to safe mode,
- tried using Smart Switch for PC, it (nor its Emergency Software Recovery) never detected my Note while stuck at the Samsung boot logo, nor did it detect it in Recovery mode,
- etc.​it still won't boot-up, and I think it's due to the CSC (UK Unbranded - BTU) not being available in the official firmware.
When I boot into recovery mode, I get the following message:
Code:
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
Support SINGL-SKU
File-Based OTA
Supported API: 3
E: unknown volume for path [/odm]
E: unknown volume for path [/vendor]
E: unknown volume for path [/odm]
E: unknown volume for path [/vendor]
# MANUAL MODE v1.0.0#
can't open directory '/system/omc/SUP/etc/sysconfig' . (No such file or directory)
can't open directory '/system/omc/SUP/etc/cid/sysconfig' . (No such file or directory)
can't open directory '/system/omc/SUP/etc/permissions' . (No such file or directory)
E:[libfs_mgr]is_dt_compatible(): firmware info was not valid : '/proc/device-tree/firmware/android/compatible' : No such file or directory
Would any of you folks have suggestions on how I could recover from this mess without needing to delete any data? Perhaps if there was a way I could add the UK Unbranded CSC to the official SM-N950N firmware and flash it via Odin, maybe that'll allow it boot? Please kindly advise, thanks in advance.

Bump

please i have the same proplem what to do
i dont know the meaning of bumb
please help

ah_1st said:
please i have the same proplem what to do
i dont know the meaning of bumb
please help
Click to expand...
Click to collapse
No luck on my end, lost months worth of data on my internal storage. Had to perform a factory reset on my Note 8 via Odin, reflash TWRP via Odin, then reflash my Custom ROM and tweaks. Lesson learned for real though