Hi, after a security update my phone got stucked on bootloop and I'm trying to flash the stock ROM throw an SD card but I get this error :
( E3003: Can't install this package (Thu Jan 3 20:40:27 CEST 2019) over newer build (Thu Jan 2 19:59:28 UTC 2020)
so I tried to edit the update script to match the data and I tried to delete this whole line
(!less_than_int(1546519227, getprop("ro.build.date.utc"))) || abort("E3003: Can't install this package (Thu Jan 3 20:40:27 CST 2019) over newer build (" + getprop("ro.build.date") + ").");
but I get signature verification failed. and Ideas?
My phone isn't rooted and the bootloader isn't unlocked so idk if I'll ever get the phone again. thanks
Related
Hi.
I'm desperate, I'm fighting with simlock that showed up in my I9300 since yesterday. I have phone for one month, never knew that it has simlock. Everything started after upgrading MIUI. In /efs/nv.log:
Code:
Tue Aug 21 18:04:09 2012: cracking detected
Tue Aug 21 18:04:10 2012: NV backup has been rebuilt
Tue Aug 21 18:04:10 2012: NV restored
Tue Aug 21 18:06:08 2012: OFFSET_FOR_PRESET2 writing input
Tue Aug 21 18:06:08 2012: 2nd NV built
Tue Aug 21 18:06:08 2012: NV data back-uped
Tue Aug 21 18:06:13 2012: OFFSET_FOR_PRESET2 writing input
Tue Aug 21 18:06:13 2012: 2nd NV built
Tue Aug 21 18:06:14 2012: NV data back-uped
Tue Aug 21 18:06:20 2012: OFFSET_FOR_PRESET2 writing input
Tue Aug 21 18:06:20 2012: 2nd NV built
Tue Aug 21 18:06:21 2012: NV data back-uped
VooDoo app is no longer in GPlay, so I used this one to patch nv_data.bin, replaced file, echo'd md5 to nv_data.bin.md5 but it didn't help.
So I found that thread, but on position 00181460 I have FF not 00/01.
Lastly I found site that sells generated codes for unlocking. But even this unlocking code doesn't work. I've tried it on modified and original nv_data.bin
Two weird things:
- original nv_data.bin.md5 has diffent md5 than generated from original nv_data.bin
- when I dial *#SIMLOCK# instead of phone status I get error "not registered in network" like on every other phone number; tried it on MIUI and original Samsung ROM
Any ideas? Now I have smartphone without the "phone" and I'm out 20 Euro for unlock code.
I think the line
Code:
Tue Aug 21 18:04:09 2012: cracking detected
might be the clue.
Looks like an anti hacking mechanism has fired...
Z.
But what does it mean for me? I've look for "cracking detected" on forum, but nothing usefull came up.
Take a look at http://forum.xda-developers.com/showthread.php?t=1839200
"cracking detected" is mentioned there.. in post #92 for example.
Done it
I found stock firmware for my country [before I used Nordic 4.0.4 found on xda], flashed it from ODIN. Didn't want to start, but /data wipe from recovery helped. On that Polish firmware unlock code which I bought finally worked. CWM recovery to get back to MIUI 2.8.10, update to 2.8.17 and success, no simlock
20 Euro out, but at least now I have simlock free phone. Thread to close.
Hello guys!
I have problems with my updater-script!
This is my saved installer log from aroma
Code:
AROMA INSTALLER version 2.56
(c) 2012 by amarullz xda-developers
ROM Name : Sensai
ROM Version : 1.0.1
ROM Author : $tefanDroid
Device : Evo3d
Start at : Sat Apr 27 13:00:36 2013
line 1040 col 6: syntax error, unexpected ENDIF, expecting $end
1 parse errors
Installer Error (Status 6)
End at : Sat Apr 27 13:00:36 2013
Hello,
few days ago I flashed new ROM official from iOcean build 16.8.2014 4.4.2 KitKat. I have problem to root it. I tried almost every tutorial and ways to root it. I installed also SuperUS but still have problems to root and MTK Droid Root & Tools give me errors:
--- ERROR : file adbd not install !
--- ERROR :dev/radio/pttycmd1 inaccessible , should be Root Shell
--- ERROR ttycmd1 device NOT found!
CWM is installed. Created from read back rom.
And other thing is when i flashed this new ROM my IMEI disappeared and i can't get it back. MTK droid doesn't work also programs on iocean web page doesn't work.
Hardware : MT6592
Model : X7S
Build number : X7S 20140816-164613
Build date UTC : 20140816-084613
Android v : 4.4.2
Baseband v: MOLY.WR8.W1315.MD.WG.MP.V34.P2, 2014/04/09 18:07
Kernel v : 3.4.67 ([email protected]) (gcc version 4.7 (GCC) ) #1 SMP Sat Aug 16 16:42:32 CST 2014
JoellSVK said:
Hello,
few days ago I flashed new ROM official from iOcean build 16.8.2014 4.4.2 KitKat. I have problem to root it. I tried almost every tutorial and ways to root it. I installed also SuperUS but still have problems to root and MTK Droid Root & Tools give me errors:
--- ERROR : file adbd not install !
--- ERROR :dev/radio/pttycmd1 inaccessible , should be Root Shell
--- ERROR ttycmd1 device NOT found!
CWM is installed. Created from read back rom.
And other thing is when i flashed this new ROM my IMEI disappeared and i can't get it back. MTK droid doesn't work also programs on iocean web page doesn't work.
Hardware : MT6592
Model : X7S
Build number : X7S 20140816-164613
Build date UTC : 20140816-084613
Android v : 4.4.2
Baseband v: MOLY.WR8.W1315.MD.WG.MP.V34.P2, 2014/04/09 18:07
Kernel v : 3.4.67 ([email protected]) (gcc version 4.7 (GCC) ) #1 SMP Sat Aug 16 16:42:32 CST 2014
Click to expand...
Click to collapse
Hi,
Please verify first in Setting-->Security if exist a entry called Superuser. If exist activate it and it's ok.
I install the same official ROM and it's rooted.
Install from Play Store MobileUncle Tools and backup IMEI. After flashing new ROM reinstall MobileUncleTools ans restore IMEI.
Hi, i've juste received a Pulid F8 Android based 4.0.4 (China Clone). Basicaly everything works fine except i don't have Google Play Services on it and whenever i try to download it from Play Store, it says 'Not compatible with other using same ID'. Phone is rooted.
I've tried to reinstall GApps for ICS but it has 3e recovery and always gets error saying "Signature verification failed"
Below the info of the phone :
Hardware : MT6577
Model : PULID F8
Build number : PULID_F8_V105
Build date UTC : 20121007-082009
Android v : 4.0.4
Baseband v: MAUI.11AMD.W12.22.SP.V5, 2012/09/11 17:21
Kernel v : 3.0.13 ([email protected]) (gcc version 4.4.3 (GCC) ) #1 SMP Tue Oct 9 12:08:46 CST 2012
I wanted to know
1. how can I update the recovery.
2. Can i install latest GApps for ICS
3. Can i install custom roms on it
Anybody has an idea? I'm searching over internet for last weeks and no results.
Solution Found!!!
GaelSouris said:
Hi, i've juste received a Pulid F8 Android based 4.0.4 (China Clone). Basicaly everything works fine except i don't have Google Play Services on it and whenever i try to download it from Play Store, it says 'Not compatible with other using same ID'. Phone is rooted.
I've tried to reinstall GApps for ICS but it has 3e recovery and always gets error saying "Signature verification failed"
Below the info of the phone :
Hardware : MT6577
Model : PULID F8
Build number : PULID_F8_V105
Build date UTC : 20121007-082009
Android v : 4.0.4
Baseband v: MAUI.11AMD.W12.22.SP.V5, 2012/09/11 17:21
Kernel v : 3.0.13 ([email protected]) (gcc version 4.4.3 (GCC) ) #1 SMP Tue Oct 9 12:08:46 CST 2012
I wanted to know
1. how can I update the recovery.
2. Can i install latest GApps for ICS
3. Can i install custom roms on it
Anybody has an idea? I'm searching over internet for last weeks and no results.
Click to expand...
Click to collapse
Finally got the solution and wanted to post it here.
i've download GApps for ICS. Using X-Plore File manager, i simply put each file manually in System/App ..... etc etc
Rebooted it and got google services, playstore 5.0 and all.
*
Thanks to myself!!!! lol
But still couldn't get custom roms for it though. I'll post if i find something. Recovery is 3e. Stinks a lot.
I am confused about something that I think should be simple:
Monthly Android Security Updates
I apparently have to install these manually, since OTA updates fail supposedly because I run a rooted phone w/ custom bootloader/recovery.
Google has been making it a point to release security patches every month:
http://source.android.com/security/bulletin/index.html
March 2016's is here:
http://source.android.com/security/bulletin/2016-03-01.html
On that page they say:
"The Nexus firmware images have also been released to the Google Developer site.", with a link to:
https://developers.google.com/android/nexus/images
I download firmware for my Nexus5 Hammerhead MMB29K:
https://dl.google.com/dl/android/aosp/hammerhead-mmb29k-factory-1943f0f5.tgz
I unzip that file and list the contents:
Code:
Pvs-MacBook-Pro:hammerhead-mmb29k pv$ ls -la
total 1218408
[email protected] 8 pv staff 272 Nov 18 15:44 .
drwx------+ 28 pv staff 952 Mar 9 10:55 ..
[email protected] 1 pv staff 3195188 Nov 18 15:44 bootloader-hammerhead-hhz12k.img
[email protected] 1 pv staff 974 Nov 18 15:44 flash-all.bat
[email protected] 1 pv staff 845 Nov 18 15:44 flash-all.sh
[email protected] 1 pv staff 798 Nov 18 15:44 flash-base.sh
[email protected] 1 pv staff 574092301 Nov 18 15:44 image-hammerhead-mmb29k.zip
[email protected] 1 pv staff 46515712 Nov 18 15:44 radio-hammerhead-m8974a-2.0.50.2.28.img
Pvs-MacBook-Pro:hammerhead-mmb29k pv$
So, my question is:
Why does Google say that the March 2016 Security Updates Nexus devices are available for download, but the files themselves are dated November 2015?
This begs more questions:
Are the March 2016 Android Security Patch Levels really in the 6.0.1 November 2015 dated files?
If not, then why does Google say that I can get the March 2016 updates for my Nexus 5 from the firmware download page?
How do I non-OTA update my Nexus5 to the latest Security Patch?
Thanks!
Pv
Ping! Seriously, no one bites on this one?
I'll answer my own question: The answer is even lamer than I thought.
The download link that the monthly security bulletin(s) point you to is a download to the original [aka: "old"] system image.
As I pointed out, the March [now April] 2016 link for a recent Security Update for my Nexus 5 sends me to the download for the November Nexus 5 System Image.
I install that image, and soon after booting it prompts me to install the January 2016 Security Update.
Here is where it gets lame...
Soon after rebooting after the January 2016 SU it prompts me to install the February 2016 SU.
Soon after rebooting after the February 2016 SU it prompts me to install the March 2016 SU.
Soon after rebooting after the March 2016 SU it prompts me to install the April 2016 SU.
I'm seeing a [lame] pattern here.
How annoying!
Can't they just update the system image w/ the latest Security Update?
Or, provide me with a SU with all of the previous SUs?
I repeat: Lame!
Pv