I have the Cool Pumpkin 3188 KLD1 (best I can tell). I have it rooted, and it's been running alright since about this time last year. I've updated to MCU 2.67, which worked fine. The Firmware is currently June 30, 2015. I cannot get any of the newer Malaysk firmware to load now. It always says "not support" and fails. I can reload the firmware it already has just fine. But any other firmware, it keeps saying it's not supported and aborts. I've tried numerous different to no avail.
It sees the update.img file just fine. As soon as I pop the card in, it detects it and initiates the update. It reboots into recovery, begins the update, and stops saying it is not supported firmware. I have tried numerous different versions. It will only let me install the Update.img for the firmware I already have, which obviously worked fine (rk3188-eng4.4.4 30062015 19:58:59)
Any suggestions?
Related
Hi,
I really, really hope someone can help me with this: I have an unbranded europeans GSm hero on the Dutch Telfort network. I was really looking forward to the official 2.1 update, but I can't even install the preparing OTA-update (including the YouTube update). I'd be really grateful if someone can help me out!!!!!!
Firmware: 1.5
Build: 2.73.405.5 146733 CL#61267 release-keys
Software: 1.0.0.A62888
My computer: Windows 7 (64), HTC Sync and drivers installed
OTA update
About two weeks ago I received the preliminary update notification on my phone (4.6mb or somehting like that). I downloaded it and in the next window I chose to install it. The phone rebooted, but remained stuck in de HERO screen forever. I removed the battery, rebooted it, changed the date, received the OTA again, but same thing happened. Apparently, the update cannot install.
I figured it might have something to do with my current build not allowing the update, so I tried installing the original RUU from HTC. But that didnt work either: it kept saying "waiting for bootloader..." and eventually gave some USB-error message (error 171). So it seems it cannot connect to my phone. Other RUU's don't work either. Downgrading therefore seems impossible too.
Recovery image
It appeared to me that perhaps my recovery image is broken as I once unsuccessfully tried to root my Hero (Tell me, is this related? i really dont know). I used the flashrec method back then, but it didnt seem to work. Afterwards, other flashing attempts using Flashrec or abd via the terminal didnt work either.
Flashrec gave "backup failed: remote not allow" or "backup failed: image invalid" or somehting like that.Adb says "device not found" or "remote failed" or "somethign similar" Somehow I have the idea the recovery image is corrupted, but the flashrec requires you to back it up before writing the new image. As it wont backup, it doesnt allow to install the new image.
I asked HTC for help, but they were of no avail: they advised me to do a factory reset. That worked, but the problem remains and the OTA update still won't install. I e-mailed them again, but they are not very guick at replying.
Does anyone have an idea how to solve this and has anyone had similar problems? I'd really like to know. To be able to install the official 2.1 would be great, a stable custom 2.1/2.2 rom would be fine too.
Please be very clear in any steps you might describe cause some of the walkthroughs are not really clear to me.
I am even willing to give the person who is able to help me a voucher for some webshop, cause I'm getting really annoyed with my phone now.
There you go http://forum.xda-developers.com/showthread.php?t=647353
I eventually got it to work: I used a computer with winXP instead of my Windows 7 (64bit), which at least helped me install to wipe the phone, install a working RUU and eventually, the OTA update worked.
That was months ago... now I'm trying the 2.2 Sense port for my Hero and it seems to be giving less problems than the official update LOL
So i bought a used Verizon S4 yesterday and it works fine. Last night it said it had an update, so i accepted before i went to sleep and this morning it said "software update unsuccessful"
Today i tried again to update, i downloaded the update, it verified the download, update available, tap to install, install now, it booted, said installing system update and then "error" about 5 seconds later and thats as far as it gets before it restarts the phone and says "software update unsuccessful"
The phone is not rooted (i used root checker) and is currently on I545VRUAMDK
Any ideas or suggestions to remedy this issue?
Plug it into your PC and let it update thru the Verizon app. Just realize once you take the update you will not be able to root your phone.
that worked, thanks!
Hi All,
I'm really not sure how to go about with this so hopefully I can get some help here. I have a Note 4 (N910T) model which was never able to do OTA update from it's 5.1.1 state. It'd download the patch and upon reboot, it'd say installation fail.
Eventually I went into the rabbit hole and used Odin to try to update the phone to 6.0.1. No luck either as it'd just get stuck on aboot. I rebooted the phone and tried to use Smartswtich from samsung and hoped that it'd update using that. Not only does it not work and stuck in the "Odin Mode (fast track)" screen, it eventually tell me that I need to go through recovery to get it back.
I didn't know what to do at that point, so I've decided to try my luck again with Odin. This time, the patch went through successfully with my surprise. However upon reboot after the patch is installed, it gave me an error "DRK not found" error. I simply reboot the phone and all seems to be working. On 6.0.1, no lagging issue, no wireless/mobile network issue, nothing.
However, I do want to know if I still have an error of DRK not found, and would like to patch that hole before any problem occurs. Can any one help? I haven't rooted the phone yet.
bump, any help would be welcomed. Thanks!! :crying:
Is it still giving that error upon every reboot or it was only on the first reboot? If you aren't having other issues and your IMEI / service / etc is fine, then nothing to worry about.
You also kept mentioning "patch". This is not common usage. What file did you flash via Odin?
Thanks for the reply!! this is what i downloaded to update the firmware using Odin:
rootmygalaxy.net/download-install-n910tuvu2epe3-marshmallow-t-mobile-note-4 (http at front)
the IMEI seems fine, and it doesn't show the error upon reboot except the first time. However the phone seems to freeze quite often now for no reason at all. Not sure how to troubleshoot that one.
es0tericcha0s said:
Is it still giving that error upon every reboot or it was only on the first reboot? If you aren't having other issues and your IMEI / service / etc is fine, then nothing to worry about.
You also kept mentioning "patch". This is not common usage. What file did you flash via Odin?
Click to expand...
Click to collapse
oc9653 said:
Thanks for the reply!! this is what i downloaded to update the firmware using Odin:
rootmygalaxy.net/download-install-n910tuvu2epe3-marshmallow-t-mobile-note-4 (http at front)
the IMEI seems fine, and it doesn't show the error upon reboot except the first time. However the phone seems to freeze quite often now for no reason at all. Not sure how to troubleshoot that one.
Click to expand...
Click to collapse
Did you install the 1st link there from the Download button or the 2nd one for the n910t3 file located @ androidfile?
I actually used another firmware today and so far it seems to not lag AS much.. but still freezes with no apparent reason:
http://forum.xda-developers.com/note-4-tmobile/development/roms-10-29-2014-t2922618
The one that I downloaded was N910TUVS2EPG2_N910TTMB2EPG2_TMB = v6.0.1 = Build date Thu, 07 Jul 2016 13:33:23 +0000 = NEWEST UPLOADED FIRMWARE
The reason I flash again is because I tried to root my device using CF_auto root, which upon reboot, caused an error of "Kernel is not Seandroid enforcing" on boot menu.
Oh and the DRK error comes back everytime after i flash the firmware, but it only appears once, and no more on subsequent reboots. My IMEI looks fine but my S/N upon typing *#60# is (none)
bump .. phone is rebooting more and more, and it's freezing more often now... help please!!
Hi!
I received J8110 from Sony as a service exchange unit (they could not repair my other model). It came originally with Android 9 1317-9334_55.0.A.2.205 GLOBAL-A1. I have not unlocked it.
It never got any OTA update for this over 2 years old firmware, so I decided to flash it myself using flashtool. As I could not find exactly matching 1317-9334 on XperiCheck, I used 1318-3803 Android 10 "Internal Service Exchange Unit 55.1.A.9.127-R1B" firmware. It did flash correctly, and almost everything works - except both Netflix and HBO Max reboot the phone whenever I try to play any video. Moreover, the phone reboots itself randomly once a few hours, and I must say it is really irritating issue.
The last entries in Android logcat just before reboot look like this:
Code:
03-07 10:18:41.251 886 17948 D WVCdm : [license.cpp(355):PrepareKeyRequest] PrepareKeyRequest: nonce=3174971344
03-07 10:18:41.313 886 6842 I WVCdm : [cdm_engine.cpp(191):CloseSession] CdmEngine::CloseSession: sid10
I suspect it might be somehow related to Widevine keys. But the DRM info app shows everything is OK and L1 support is enabled (as in the attached screenshot).
I tried to flash also other firmware images - everything available for J8110 in XperiCheck (including 55.2.A.4.332), but the phone won't boot - "Your device is corrupt. It can't be trusted and will not boot.". I even tried flashing J8170, but that eneded up even worse, in recovery: "cannot load Android system". This 55.1.A.9.127-R1B (that reboots my phone on Netflix) is the only firmware I was able to boot.
My first question: is there any way to downgrade to this original, obsolete but working Android 9 1317-9334_55.0.A.2.205 GLOBAL-A1? I can't find it in XperiFirm.
And, of course - if you could point me on how to install the more recent Android versions that work I would be very grateful. I would prefer to leave the phone locked as I suspect some DRM issues with unlocking, but if that is the only way and it is confirmed working I can try it as well.
Service menu *#*#7378423#*#* "software info" of original and updated firmware attached.
Thanks for any help!
I forgot to mention that of course I tried clearing data and cache for Netflix app, as well as uninstalling and re-installing updates (can't fully uninstall the app as it was included in the firmware). I could fully reinstall HBO though, but fresh install did not help with the issue at all.
Did you tried the Firmware with version 205 on XperiFirm?
There is one called SA or ZA.
Get things into your PC and use newflasher by @munjeni. It will work if there is nothing wrong with hardware.
Thanks for the response.
I have tried the newflasher as well, but the results are exactly the same as for flashtool - "Your device is corrupt..." (or recovery error, depending on firmware). I don't think this is an issue with flashing itself, I did not notice any error in logs.
Yes, I have tried this 205 "Customized ZA" also - it does not boot, stops in recovery "Can't load Android system". I did not try to factory reset the data yet, as I really would prefer to keep my user data intact.
I have tried every single firmware available in XperiCheck for J8110, and only this 1318-3803 boots for me - but reboots my phone every hour or so and this is really annoying.
I have also asked XperiCheck maintainer to add my 1317-9334, but no response so far.
Plz provide the frimware that is working in your mobile i am facing the same problem my device stuck on sony logo i will be thankful to you brother
Hi, I own a samsung galaxy A31F, I rooted it back in April of 2021 and decided to not update till android 12 comes out. I downloaded the firmware from samfrew and everything went perfectly until I opened the phone and found out that my IMEI is "unknown".
Both of them are, I have tried every method to restore them.
Including re flashing android again with root or without it. Nothing seems to work I tried apps.
I tried to use Xposed.
IMEI flashing software for PC.
Nothing seems to work and I would really appreciate it if someone decides to help.
Thanks.