Hi all, I'm having issues with an HTC One Developer Edition phone. It initially had Sense on it. I rooted it, installed TWRP 2.6.3.0, and flashed the 4.2.2 GE ROM onto my phone. I have since sold my phone, but the current owner is having some serious issues with it after the 4.3 GE update downloaded onto her phone. I don't remember flashing any new radios on the phone. I did flash a Bulletproof kernel, but seeing as how the kernel is wiped whenever you flash a new ROM, I don't think that's the issue here.
She is currently unable to flash ANY ROM through TWRP [2.6.3.3] or CWM [6.0.3.1]. She has tried to redownload the files a number of times and ensured that the MD5 checks up, so missing bits are not the issue. She's tried flashing through fastboot as well to no avail, ensuring to clean /data, /system, /cache, and /davlik each time she attempts a new flash. The ONLY ROM that flashes successfully on the phone is the 4.2.2 GE ROM.
It sounds like a very weird issue to me and I honestly have no idea how else to troubleshoot this as we've tried all of the common techniques. Would appreciate any input or help towards resolving this as her phone is now in a very unstable state.
The error line in recovery says:
Code:
No MD5 assert failed: getprop("ro.product.device") || getprop("ro.build.product") == "m7"
Related
ive tried everything to get my tablet back to stock. as of now i am on overcome ROM. ive followed every guide i could fiund to get back to stock and nothing works. wheni try to flash anything i get 2 errors.
when i try to flash the hc-3.1_ota-full_sam_tab_10.1.zip i get this error:
assert failed: getprop("ro.bootloader") == "P7100BUKB7"
E:Error in sdcard/hc-3.1_ota-full_sam_tab_10.1.zip
(Status 7)
Installation aborted.
when i try to flash anything else, i get this error:
assert failed: getprop("ro.bootloader") == "P7100BUKB7" || assert failed: getprop("ro.bootloader") == "P7100BUKB8"
any help on this is greatly appreciated. i mean any help. thank you.
so, i tried again this morning and have still got the same results. has ANYONE else had this issue? or something simular? i am at my end. this is what ive tried so far:
flash the stock
flash another rom
factory reset
flash restock from overcome
nothing is working. someone has to have some information on this.
thanks!!
SOLVED!!!
this is what i did to get back to stock after getting the errors above.
first thing, i re-rooted my tab.
once re-rooted, i flashed the hc-3.1_ota-full_sam_tab_10.1.zip
then i did used ODIN to flash the stockrecovery file. (everything you need is ont the files for dummies zip
on the tab re-booted, it was stuck in a bootloop.
so i got back into recovery and did a factory/data reset/wipe.
tab rebooted and everything is working fine. back on stock.
android version 3.1
kernel 2.6.36.3
[email protected]#1
build number
hmj37.uekf3 p7510uekf3
hope this helps anyone having the same problem.
Which method to re-root did you use? I have the same issue.
EDIT: Nevermind! Got it! Thanks
jcporter80 said:
Which method to re-root did you use? I have the same issue.
EDIT: Nevermind! Got it! Thanks
Click to expand...
Click to collapse
Ack! Which method did you use to re-root? I'm getting the same error. I'm trying to root by flashing the root zip file in CWM. It flashes fine, but then I still get the same error. Is there another way to do it?
The problem seems to be the CWM version. I was on 5.x that came with one of the ROMs. So I used ODIN to flash the older CWM 4.0.0.4. Then I was able to flash the stock hc-3.1_ota-full_sam_tab_10.1.zip file.
I have an Optimus T, P509, with the latest stock firmware 2.2.2. I want to flash it to mik_os's CM7, version 6.5.8.
1) I rooted the machine using Gingerbreak.
2) I used the ROM Manager to install CWM.
3) I put cyanogen_thunderg-ota-eng.mik-6.5.8.zip onto my SD card and verified the md5sum.
4) I booted into CWM, which reports v5.0.2.7.
5) I did a wipe data/factory reset.
6) I proceeded to "install zip from sdcard" and selected the file.
7) This is the error that I see:
Code:
assert failed: getprop("ro.product.device") == "thunderg" || getprop("ro.build.product") == "thunderg" || getprop("ro.product.board") == "thunderg"
E:Error in /sdcard/cyanogen_thunderg-ota-eng.mik-6.5.8.zip (Status 7)
Installation aborted.
So I proceeded to search for this error message, and I came across the following suggestions in various threads:
* Toggle image verification and script assert
* Update to CWM v5 (I'm already using 5.0.2.7)
* Format /system
I've tried all of these suggestions, and I still get the exact same error...
Dont verify md5sum / signature or anything. Just wipe everything and flash!!
As I indicated in my OP, I did wipe everything. And I did try turning off signature verification. As for the md5sum check, that was something that I manually did when I copied the file to the card, before I even booted into recovery mode, so verify that the file was not corrupt.
In any case, when I created this thread, I was not aware that there was an "official" CM7 build for the Optimus (it wasn't mentioned in the FAQ, and I'm new to all this...),but after I found that there is an official CM7.2 stable build, I tried flashing that zip instead, and it went ahead without a hitch. So I guess there was something wrong with the mik_os CM7? But i checked the hashes again, and there wasn't any corruption. Oh well, all's well that ends well...
Maybe it was because your on new baseband?
Virusbetax said:
Maybe it was because your on new baseband?
Click to expand...
Click to collapse
No, I'm on the old baseband; a new baseband was never released for the Optimus T, and as I understand it, the new baseband does not support the AWS frequencies that T-Mobile uses, so I mustn't upgrade to the new baseband anyway (I had to apply the baseband fix to allow CM7.2 to use the old baseband).
Actually I've been using v20g baseband on tmobile for almost a year now and it does work perfectly with tmobile... I'm also in NY and 3g, mms, text, all work. Even signal is better
Try updating baseband with lgmdp, I used tht and it worked flawlessly :thumbup: tht should solve problems cuz of new baseband
Sent from my LG-P500 using xda premium
Originally the phone failed to install the 4.1.2 update. It failed with an error such as "assert failed: motorola.motoflash("/tmp/lte.img")". Looked like everything was succeeding in flashing except the radio. That being said, I used fastboot to flash the 4.1.2 update to the phone. This was all and dandy, but 4g didn't work and wifi was a little bit spotty. Figuring I had nothing to lose, I flashed Cyanogen, but still had no 4g. I extracted the update_radio.zip from the radio.img file, and that fails to install in either stock recovery or in twrp. I believe that if I can get this file to flash then it'll fix it in both OSes, but I've hit a wall and ran out of options. Anybody else have any advice?
DarthRogue said:
Originally the phone failed to install the 4.1.2 update. It failed with an error such as "assert failed: motorola.motoflash("/tmp/lte.img")". Looked like everything was succeeding in flashing except the radio. That being said, I used fastboot to flash the 4.1.2 update to the phone. This was all and dandy, but 4g didn't work and wifi was a little bit spotty. Figuring I had nothing to lose, I flashed Cyanogen, but still had no 4g. I extracted the update_radio.zip from the radio.img file, and that fails to install in either stock recovery or in twrp. I believe that if I can get this file to flash then it'll fix it in both OSes, but I've hit a wall and ran out of options. Anybody else have any advice?
Click to expand...
Click to collapse
What type of jelly bean update are you using? What is your phone model? XT910 or XT912?
XT912, the verizon version. If I'm not mistaken, the other one does not have 4g. After the OTA failed, I flashed 9.8.2O-72_VZW-16 Blur_Version.98.72.16.XT912.Verizon.en.US via fastboot.
Found a log file. This looks like the juicy part.
updating LTE...
Reading input Flash Image
Registering bp flash device
Registering lte flash device
Rebooting LTE in Flash Mode
Searching for flash devices
Unable to find flash devices
Retrying flash
Searching for flash devices
Unable to find flash devices
Retrying flash
Searching for flash devices
Unable to find flash devices
Retrying flash
script aborted: assert failed: motorola.motoflash("/tmp/lte.img")
assert failed: motorola.motoflash("/tmp/lte.img")
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
EDIT:
Searched for a portion of the error. Found a thread I hadn't seen before. Looks like I'm going to talk to my good buddies at verizon.
droidrzr.com/index.php/topic/9739-no-4g-cant-upgrade-to-ics-assert-failed-motorolamotoflashtmplteimg/page__k__bb2fe024f8a71424996db6d9af08c1fc__settingNewSkin__38
I tried to install
|ROM||AROMA|| Padawan JB V2 || PIE || Per App DPI ||4.1.2| 5|31 on my i717 using both CWM and TWRM and both give me the same error after flashing the ROM. It says encryption failure, and tells me to format all my data and try to encrypt it again. I don't have any encryption on my phone, and I did a full wipe of the device prior and after flashing the ROM. I then flash a stock AT&T rom using Odin which worked fine, but then when I reflashed the ROM using both CWM V5.5 and the latest TWRM I still get the same error. I read about how it can be caused by the OS unable to read those paritions, but I followed the directions and it doesn't seem like anyone else is having issues. Can anyone point me in the right direction? Not sure if it matters but I was upgrading off of CM v10
Scarpa_sd said:
I tried to install
|ROM||AROMA|| Padawan JB V2 || PIE || Per App DPI ||4.1.2| 5|31 on my i717 using both CWM and TWRM and both give me the same error after flashing the ROM. It says encryption failure, and tells me to format all my data and try to encrypt it again. I don't have any encryption on my phone, and I did a full wipe of the device prior and after flashing the ROM. I then flash a stock AT&T rom using Odin which worked fine, but then when I reflashed the ROM using both CWM V5.5 and the latest TWRM I still get the same error. I read about how it can be caused by the OS unable to read those paritions, but I followed the directions and it doesn't seem like anyone else is having issues. Can anyone point me in the right direction? Not sure if it matters but I was upgrading off of CM v10
Click to expand...
Click to collapse
If you reflashed the stock rom and put custom recovery did you check for root. I had same issue with a different rom so I went back to my stock backup and downloaded the rom and flashed again. But with Padawan Twrp will try to fix superuser but the Dev says don't let it.
Hope this helps. If all else fails PM the Dev he is always willing to help
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Scarpa_sd said:
I tried to install
|ROM||AROMA|| Padawan JB V2 || PIE || Per App DPI ||4.1.2| 5|31 on my i717 using both CWM and TWRM and both give me the same error after flashing the ROM. It says encryption failure, and tells me to format all my data and try to encrypt it again. I don't have any encryption on my phone, and I did a full wipe of the device prior and after flashing the ROM. I then flash a stock AT&T rom using Odin which worked fine, but then when I reflashed the ROM using both CWM V5.5 and the latest TWRM I still get the same error. I read about how it can be caused by the OS unable to read those paritions, but I followed the directions and it doesn't seem like anyone else is having issues. Can anyone point me in the right direction? Not sure if it matters but I was upgrading off of CM v10
Click to expand...
Click to collapse
FIXED
It had something to do with the SD card. I had a 32 gig card installed, this time I moved the rom to the internal memory and reflashed and it worked perfect. The external card cannot be in the phone. Odd thing is it happend with the official 4.1 release I flashed using Odin as well. Hopefully this will save some poor soul many hours of frustration.
Hello,
I searched in many threads as I could and although I learned that mediatek phones were virtually "unbrikable", I'm afraid it keeps getting worse and won't do more without your expertise.
So a few days ago I was wiping my phone to install another rom and besides wiping data and cache, I also made the huge mistake of wiping SYSTEM... My phone now just boots into recovery and nothing else.
I have an Efox Smart e4, equals to no.1 s6 and hdc galaxy s4 according to other posts here. MTK 6589, 1gb internal, 1,84gb internal sd.
The first custom rom that i installed was Essefour no.1 s6 by iceman and also the touch recovery. The rom performed great but I wanted to solve the issue that the phone kept switching between sd external and internal randomly. Also, I wanted to merge the internal memory with the internal sd so I was gonna try another rom. With this problem, was even trying the stock rom but to no avail.
When I try to install the Smart e4 factory rom for cwm and I get status 7.
E:Resource type (image) failed to load
Installing /sdcard/SMART-E4_V1.0_V01_2013-10-29_CWM.zip
Checking for MD5 file
Skipping MD5 check: no MD5 file found.
... Writing boot...
assert failed: write_raw_image("/tmp/boot.img", "boot")
Error in /sdcard/SMART-E4_V1.0_V01_2013-10-29_CWM.zip
(Status 7)
Click to expand...
Click to collapse
Other roms it just fails.
Right now, my computer windows 8.1 x64 can't identify correctly my phone, only access the sd. So can't do any adb push. In download mode it identifies as lenovo composite interface?? and cdc serial, the last I can't install. In other modes, I get gt-9500 but with the yellow triangle.
I would really really appreciate any help, thanks!
Might try to just edit the updater-script and remove the asserts.
Reference this for more info: http://forum.xda-developers.com/showthread.php?t=2522762
But I think your issue is that since you wiped the system, there's no /tmp folder to store the boot.img. However, if the last rom and this rom can use the same kernel (boot.img) then removing the assert for the boot.img install might do it since wiping the system does not affect the kernel.
What happened to the other rom you know is working somewhat? Can you just reflash that?
Otherwise, you'll just have to find the official way to flash with the scatter file and all that.
I searched for that updater and there are no lines for assert on the stock rom. Also inside the main zip, there are zips for system, boot, recovery and logo...
I'm trying to install the stock rom to play it safe since it was the same that came with the phone. The previous rom I talked about, I deleted it and now the phone isn't recognized on the computer..
Since I don't know if they have the same kernels, is it safe to try and reinstall the custom rom?
As of using scatter and such, maybe I need other pc to get the drivers running again.
Will let you know
I got it!!
The zip from the stock rom wouldn't let me install the kernel (boot). Managed to install only the rom, and as you said the kernel wasn't the same.
Eventually I reinstalled the custom rom and afterwards flashed a completely different rom via spflash tools since it connected successfully to my computer this time.
As I'm already restoring apps and data, I think everything is working properly.
Once more, thank you very much