hey guys, first post. had a weird issue after downloading RC2. i wasn't getting a clear signal anymore for some reason. this was a few days after a few newer updates, so i installed the best reviewed one. ended up getting bootlooped. tried reverting back to RC2 but kept getting an error. installation failed. so kept going back on the updates and wasn't able to install ANY of them. so i switched to slimbean.
now, i can't restore system data with titanium, because that causes me to go back to bootloop, which is understandable because cm10 and slimbean are different. i'm mainly looking for a solution to get cm10 back. i don't remember the EXACT code that it kept giving me, and i don't feel like bootlooping my phone by doing it all over again.. but essentially what i read was that it's what verifies that i'm installing it on the right phone (which i am.)
i just want cm10 back, but can't get it because of THAT code which pops up on every nightly. any ideas on what my issue is?
i'm moderately technical, so i won't ask to explain like i'm 5... but...maybe explain like i'm 10.
Ok try this real simple and should get you going. http://db.tt/Qt6NcH0a this is the baseband /firmware aio zip for md4. The new cm10 roms have a built in script checker to make sure your phone is updated to the latest bootloader. Just flash this in recovery boot up and your baseband should be md4 it also updated the bootloader. Then go back into recovery and flash your cm rom and gapps you should be golden.
Sent from the future via Xparent Green Tapatalk 2
You need to be on the newest MD4 firmware for the new builds to flash.
This goes for all new AOSP roms now, not just CM
edfunkycold said:
Ok try this real simple and should get you going. [had to delete the link] this is the baseband /firmware aio zip for md4. The new cm10 roms have a built in script checker to make sure your phone is updated to the latest bootloader. Just flash this in recovery boot up and your baseband should be md4 it also updated the bootloader. Then go back into recovery and flash your cm rom and gapps you should be golden.
Sent from the future via Xparent Green Tapatalk 2
Click to expand...
Click to collapse
thank you very much! will try now.
and an edit. didnt work. exact error is
assert failed: getprop(ro.bootloader") == "L710vpblj7" II getprop(ro.bootlaoder") == "L710vpbma6 ll getprop(ro.bootlaoder") == "L710vpbmb1" ll getprop(ro.bootlaoder") == "L710vpbmd4"
E:error in /external_sd/cm-10.1.0-rc4-d2spr.zip (status 7)
installation aborted
final edit. fixed it. didn't know to reboot into recovery after installing it! thanks! it worked.
nickgenova said:
thank you very much! will try now.
final edit. fixed it. didn't know to reboot into recovery after installing it! thanks! it worked.
Click to expand...
Click to collapse
Glad it worked! Enjoy:thumbup:
Sent from the future via Xparent Green Tapatalk 2
Related
So I'm stumped. I basically can't flash anything -- I got into recovery and try to flash something and I get status 7 errors with the message:
assert failed: getprop("ro.product.device") == "epic4gtouch" || getprop ("ro.build.product") =="epic4gtouch" || and so on and so forth with "SPH-D710" in the next block and "d710" in the final one.
As I understand it this is a build.prop error, but I've flashed back to complete stock, and verfied the correct build and device number in the build.prop on the device and I still can't flash anything. Is there a "hidden" build.prop somewhere that I don't know about that survives flashing back to stock
----NOW SOLVED----
For anyone else having this same issue, here's what I did to solve it:
* Install CWM from here. Then install a kernel that you know works, flashing via CWM. That's it! Now you should be able to go back to flashing roms again. No idea why it works, but it does -- I guess some imprint got left on my recovery.img or something.
If you are bone stock, that would mean you don't have a custom recovery which would allow you to flash unsigned files? I'm just trying to understand where you are at in order to help. Are you stock and if so gb or ics?
It sounds like a recovery issue or maybe a problem with the zip you are trying to flash.
TheSilverStig said:
If you are bone stock, that would mean you don't have a custom recovery which would allow you to flash unsigned files? I'm just trying to understand where you are at in order to help. Are you stock and if so gb or ics?
It sounds like a recovery issue or maybe a problem with the zip you are trying to flash.
Click to expand...
Click to collapse
I flash to stock and the AGAT's kernel. I'm trying to flash zips that I have successfully flashed before, and using this kernel, so I know there's nothing wrong with the zip or the kernel. I'm just really not sure where the issue is though if I've flashed back to complete stock.
Also to add, i can't run mobile Odin any more despite being able to run it a few days ago. Now it says my device is unsupported even though I'm using stock build.prop and i do have root
Sent from my SPH-D710BST using Tapatalk 2
I had this issue the other day when I tried to flash back to JB alpha 6 from a GB rom (forgot to get a GPS lock first). What fixed it for me was using caulkins format all and then flashing super galaxy 1.7. After that was done I was able to flash el26 kernel, go back to recovery and flash my JB rom.
Edit: ha ha ha I'm the idiot, didn't see you had already posted that you solved it.
Sent from my Transformer Prime TF201 using xda premium
Ok so it's been a while since I've done any new ROMs or anything, mainly did things on my GS2 but now going with the GS3 and have been for a little bit now. It's all rooted and everything fine, but I decided to finally install the CM10 ROM and am having a difficult time. I finally got it to install and boot up (had a slight issue with the boot loop which I got passed) but now my home screen says Sprint on the bottom. Maybe I downloaded the wrong CM10 zip? Or maybe they're all like this but I didn't think it was. On to the bigger problem, no mobile connection. I'm able to restore to my backed up status so that's what I'm going with for now but I'd really like to get this working. Any suggestions? Have I supplied enough info. Any help would be greatly appreciated, thanks to anyone that can give me some direction here.
You flashed the wrong zip.
for AT&T you need d2att http://get.cm/?device=d2att
If you need a different carrier then ATT try checking the CM10 thread http://forum.xda-developers.com/showthread.php?t=1778270
Randomacts said:
You flashed the wrong zip.
for AT&T you need d2att http://get.cm/?device=d2att
If you need a different carrier then ATT try checking the CM10 thread http://forum.xda-developers.com/showthread.php?t=1778270
Click to expand...
Click to collapse
Thank you for that! Will that solve the network problem too? Seems like something like that would solve my problem all together. Anything else I should know?
Imnice777 said:
Thank you for that! Will that solve the network problem too? Seems like something like that would solve my problem all together. Anything else I should know?
Click to expand...
Click to collapse
yeah it should if not go back to complete stock and try again.
If none of that works check in settings, about phone and make sure your imei number is still intact (not showing zeros).
Ok so my IMEI is still intact but that zip for AT&T didn't work, I got an error. I cleared cache and user data and chose it from my internal memory, not sure what the issue is except maybe my CWM is outdated? Wasn't sure if it'd be a problem but maybe that's it. Any other suggestions?
Sent from my SAMSUNG-SGH-I747 using xda premium
Might be an APN issue. Try adding the APN for your carrier and see if your data works. What error are you getting when you try to flash the at&t version?
jethro650 said:
Might be an APN issue. Try adding the APN for your carrier and see if your data works. What error are you getting when you try to flash the at&t version?
Click to expand...
Click to collapse
The error reads "asset failed: getprop("ro.product.device") == "d2att" l l getprop(("ro.build.product") == "d2att" E:error in /emmc/cm-10-20121024-NIGHTLY-d2att (1).zip (Status 7) Installation aborted."
Update your recovery.
Sent from my iPad 4
Update CWM recovery to latest version.
And you can get a newer version here. http://forum.xda-developers.com/showthread.php?p=28611956
Official ClockworkMod Recovery Images for AT&T
Ok so I figured it out and fixed it! All I had to do was update my CWM with ROM Manager like I thought I might have to do. I saw another thread with a similar issue, too so I guess this is somewhat common. Gotta update everything when it comes to this stuff. Thanks for all the responses though, I appreciate it.
Somehow I didn't see the replies telling me to update CWM before I.posted that I figured it out. Either way, I'm currently running it and all is awesome so far. If anyone has suggestions on specific things to do now?
Sent from my SAMSUNG-SGH-I747 using xda premium
please help
Hi there, i've been having issues trying to install cm10 since last week and it's been frustrating. After doing hours of search I found a thread that says I should reinstall cwm recovery. I've tried doing this with rom manager from google play but it didn't work. It says, make sure you have stable internet connection and that your sd card is installed and working. Now, do have to Odin again to flash the newest clockworkmod recovery. If not how do I do then cuz I keep getting aborted and every time have to restart system and set it up all over. by the way my phone is a galaxy s3 i747 android 4.0.4 rooted cwm 5.5.0.4. thanks
androidehca said:
Hi there, i've been having issues trying to install cm10 since last week and it's been frustrating. After doing hours of search I found a thread that says I should reinstall cwm recovery. I've tried doing this with rom manager from google play but it didn't work. It says, make sure you have stable internet connection and that your sd card is installed and working. Now, do have to Odin again to flash the newest clockworkmod recovery. If not how do I do then cuz I keep getting aborted and every time have to restart system and set it up all over. by the way my phone is a galaxy s3 i747 android 4.0.4 rooted cwm 5.5.0.4. thanks
Click to expand...
Click to collapse
Download this cwm 6.0.1.4 http://db.tt/te3vInsu , reboot into recovery and flash it, reboot recovery and flash cm10.
tonymtl said:
Download this cwm 6.0.1.4 http://db.tt/te3vInsu , reboot into recovery and flash it, reboot recovery and flash cm10.
Click to expand...
Click to collapse
that's not the problem, I already have the file. it's kind of my question, I keep getting aborted from the process of flashing. no errors, only aborted
androidehca said:
that's not the problem, I already have the file. it's kind of my question, I keep getting aborted from the process of flashing. no errors, only aborted
Click to expand...
Click to collapse
If that's the case I'd probably completely go back to stock and root with the updated CWM. Kind of a pain but might be your best bet. Updating for me was the solution. Try that and let me know how it goes.
Sent from my SAMSUNG-SGH-I747 using xda premium
I have rooted/flashed numerous phones and have only ever had issues with this phone. Anyways, enough with the intro...
history: had cm10 running fine but decided to try some ICS roms for better battery life / tethering with 4g still active.
-------
So I used odin 1.85, and have flashed StockCWM-EL26.tar.md5. This gets me CWM recovery 5.0.2.7, from here i tried to flash cm9 experimental build beta1 or something like that and it gives me a status 7.
I tried restoring a backup I had made previously but it failed saying mm blk9 or something like that. I believe these don't work because i had updated to the latest CWMR for the e4gt, but during flashing those custom ICS ROMS they flashed their own recovery
Odin appears to be the only thing that actually recognizes my phone. I can't get fastboot or adb to work in download mode. I believe fastboot should work. I mention this because the one click rooting methods sit waiting for me to plug in my phone.
I do have access to the SD card, so if i can get a ROM that CWMR 5.0.2.7 will flash i can put it on the card and try that. But again thats how i got to cm10 was from first installing this cm9 beta build.
Any ideas or useful info i left out that may help please let me know!
mohbandy said:
I have rooted/flashed numerous phones and have only ever had issues with this phone. Anyways, enough with the intro...
history: had cm10 running fine but decided to try some ICS roms for better battery life / tethering with 4g still active.
-------
So I used odin 1.85, and have flashed StockCWM-EL26.tar.md5. This gets me CWM recovery 5.0.2.7, from here i tried to flash cm9 experimental build beta1 or something like that and it gives me a status 7.
I tried restoring a backup I had made previously but it failed saying mm blk9 or something like that. I believe these don't work because i had updated to the latest CWMR for the e4gt, but during flashing those custom ICS ROMS they flashed their own recovery
Odin appears to be the only thing that actually recognizes my phone. I can't get fastboot or adb to work in download mode. I believe fastboot should work. I mention this because the one click rooting methods sit waiting for me to plug in my phone.
I do have access to the SD card, so if i can get a ROM that CWMR 5.0.2.7 will flash i can put it on the card and try that. But again thats how i got to cm10 was from first installing this cm9 beta build.
Any ideas or useful info i left out that may help please let me know!
Click to expand...
Click to collapse
I do not know much but it looks like the cm9 rom that you downloaded is a bad download, go back to Odin 1.85 and flash StockCWM-EL26.tar.md5. again and flash your cm10 rom or another rom to get back on track
Sent from my SPH-D710 using xda premium
jc.m said:
I do not know much but it looks like the cm9 rom that you downloaded is a bad download, go back to Odin 1.85 and flash StockCWM-EL26.tar.md5. again and flash your cm10 rom or another rom to get back on track
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I know I am trying to flash the proper cm10 rom (the one that worked before) because its the only cm10 rom on my SD card.
I'm pretty sure I followed this guide to make it all happen.
Is there a way i could flash the latest CWM recovery using ODIN? Then I would think this recovery would be able to restore my backups
Odin this:
http://shabbypenguin.com/k0/ecm/E4GT-EL29-directbootCWM-v3.tar.md5
goes in PDA slot in odin
calisro said:
Odin this:
http://shabbypenguin.com/k0/ecm/E4GT-EL29-directbootCWM-v3.tar.md5
goes in PDA slot in odin
Click to expand...
Click to collapse
Successfully used odin to flash this. I then tried using the cwm 5.0.2.7 recovery again to install cm9 and cm10, but both failed saying
Code:
assert failed: getprop("ro.product.device") == "d710" || getprop("ro.build.product") == "d710" || ..........
+several other options. I'm going to try another cm9 tonight unless anybody has another ROM suggestion *hint*hint*
I then tried to restore my backups, which said they couldn't find system/data. So then i tried advanced restore and selected boot which went fine, system gives my this:
Code:
E:format_volume: no MTD partition "/dev/block/mmcblk0p9"
Error while formatting /system!
mohbandy said:
Successfully used odin to flash this. I then tried using the cwm 5.0.2.7 recovery again to install cm9 and cm10, but both failed saying
Code:
assert failed: getprop("ro.product.device") == "d710" || getprop("ro.build.product") == "d710" || ..........
+several other options. I'm going to try another cm9 tonight unless anybody has another ROM suggestion *hint*hint*
I then tried to restore my backups, which said they couldn't find system/data. So then i tried advanced restore and selected boot which went fine, system gives my this:
Code:
E:format_volume: no MTD partition "/dev/block/mmcblk0p9"
Error while formatting /system!
Click to expand...
Click to collapse
You may also want to do a full restore look here http://www.sxtpdevelopers.com/showt...H-D710-FI27-(FI27-Modem-Kernel-ROM-Root-Stock
Sent from my SPH-D710 using xda premium
it lives!
I'm not sure where to give credit, but this is what secret sauce finally made things work..
a little bit of this
followed by using Odin v1.85, PDA loaded stock D710_CODE_SPH-D710.FI27_CL1127689_REV02_user_low_ship.tar.md5.7z from this link
So now that i at least have a booting device, i've been here before and can make my way to eventually restoring my backup.
thanks everyone!
mohbandy said:
I'm not sure where to give credit, but this is what secret sauce finally made things work..
a little bit of this
followed by using Odin v1.85, PDA loaded stock D710_CODE_SPH-D710.FI27_CL1127689_REV02_user_low_ship.tar.md5.7z from this link
So now that i at least have a booting device, i've been here before and can make my way to eventually restoring my backup.
thanks everyone!
Click to expand...
Click to collapse
Good to know that you are back on track
Sent from my SPH-D710 using xda premium
mohbandy said:
I'm not sure where to give credit, but this is what secret sauce finally made things work..
a little bit of this
followed by using Odin v1.85, PDA loaded stock D710_CODE_SPH-D710.FI27_CL1127689_REV02_user_low_ship.tar.md5.7z from this link
So now that i at least have a booting device, i've been here before and can make my way to eventually restoring my backup.
thanks everyone!
Click to expand...
Click to collapse
Credit goes to sfhub, who we hope will be back at some point!
For what its worth, now that I am back to where I originally started...
The CM10 I was flashing was putting CWM v6.0.1.7 (i believe) on my device. I made my backup using this and was able to restore to this after a failed boot of my CM10 downloaded ROM.
At this point, i then flashed the latest officially supported CWM version as reported from the cwm site. I then made another backup, this time using CWM v5.0.2.7 and now feel more comfortable/confident having the ability to re-flash this guy.
Hello,
I got this problem trying to install RC4 and RC5 as well, but now still getting it with the fresh CM10.1.0 update. I am running CWM 6.0.3.1 and tried updating CM but got the status 7 error due to the asserts. I checked md5 just to be sure and made sure I have proper d2att file for my phone. I went in and manually removed the 2 assert lines in the beginning of the updater-script file and zipped back up and tried to flash again but now I just get "installation aborted..." right after "installing update..." with no explanation or error at all.
I tried searching, got nothing, anybody seen this before?
Thanks,
J
madtorq said:
Hello,
I got this problem trying to install RC4 and RC5 as well, but now still getting it with the fresh CM10.1.0 update. I am running CWM 6.0.3.1 and tried updating CM but got the status 7 error due to the asserts. I checked md5 just to be sure and made sure I have proper d2att file for my phone. I went in and manually removed the 2 assert lines in the beginning of the updater-script file and zipped back up and tried to flash again but now I just get "installation aborted..." right after "installing update..." with no explanation or error at all.
I tried searching, got nothing, anybody seen this before?
Thanks,
J
Click to expand...
Click to collapse
Are you on a Canadian carrier?
Sent from my SGH-I747 using xda app-developers app
Nope, southern california ATT.
I edited using vim and did it cleanly, no chance of a carriage return or something stupid contributing to this.
Are you on the proper bootloader?
mrhaley30705 said:
Are you on the proper bootloader?
Click to expand...
Click to collapse
I have tried running the zip manually from recovery mode in CWM, tried installing it from Rom Manager where it reboots and automatically selects it and I have tried directly from the CM10 update button within the About Phone settings menu.
Is that what you are referring to?
No. Have you installed the jelly bean bootloader? If not, you will need to update them before cm, or any aosp based Rom, will install.
Also, you need the latest modem too.
mrhaley30705 said:
No. Have you installed the jelly bean bootloader? If not, you will need to update them before cm, or any aosp based Rom, will install.
Also, you need the latest modem too.
Click to expand...
Click to collapse
I do not follow, what is the jelly bean bootloader? I understood it to be an alternative to CWM? Why have I been able to flash every update for CM10 until this?
Link to this jelly bean bootloader update?
Bootloaders are not a type of recovery. Perhaps you should read through this:
http://forum.xda-developers.com/showthread.php?t=1903437
Then this:
http://forum.xda-developers.com/showthread.php?t=2292957
madtorq said:
Hello,
I got this problem trying to install RC4 and RC5 as well, but now still getting it with the fresh CM10.1.0 update. I am running CWM 6.0.3.1 and tried updating CM but got the status 7 error due to the asserts. I checked md5 just to be sure and made sure I have proper d2att file for my phone. I went in and manually removed the 2 assert lines in the beginning of the updater-script file and zipped back up and tried to flash again but now I just get "installation aborted..." right after "installing update..." with no explanation or error at all.
I tried searching, got nothing, anybody seen this before?
Thanks,
J
Click to expand...
Click to collapse
I have the same problem. Guess I'll never get 10.1, because it looks like you have to put a new bootloader on it, not sure why, and it risks a hard brick. It doesn't make any sense to require a new bootloader, seeing as I already have cyanogenmod 10, but the devs chose that for their reasons. I really want the camera in 4.2.
Well, if you've flashed any of the stock ROMS here, rooted or not rooted, you've flashed bootloaders.
well I guess I am confused. I am currently running cm-10.1-20130411-EXPERIMENTAL-d2att-M3.zip with the same bootloader I flashed with Odin back when I got the phone in september 2012. My roomate got the same phone except on sprint and we flashed his with the appropriate CM10.1 experimental release for the sprint phone. Since then we both have been updating via the built in CM updater and he has been able to go to the new stable CM 10.1.0 release today and has not flashed any new boot loader or anything, just updated CWM like I did.
So my question to you mrhaley30705, which no amount of searching or reading links has helped me thus far, is this something specific to the ATT version of the Galaxy S3? I do not understand what changed and why he can do it and I cannot.
More importantly, will flashing the newer boot loader you suggested require a wipe of everything? The only post actually referencing this for my phone is http://forum.xda-developers.com/showpost.php?p=41503727 and it is vague to say the least.
Your answers are much appreciated.
Here is the screen shot of what was posted on g+ by cm. I would say he is on the new bootloader. If you check the second link I posted above, there's a way to tell which bootloader you and your buddy have.
It doesn't wipe anything. You'll probably never notice the difference, with the exception of being able to run aosp based ROMS
thank you, that is informative, but still leaves me confused since I am running 4.2.2 (although the build is before that May release) and I am currently running I747UCLH9.
Checking my roomate's phone he is running XXXXXXLJ7 so either he started with a newer one or something. I guess that clears it up. Also, this thread was very helpful incase anybody searches and stumbles on my posts: http://forum.cyanogenmod.com/topic/73407-how-to-update-bootloader-and-do-i-need-to-do-this/
So I was feeling all confident, ready to install a new ROM, figuring based on my experience, I should have no issues. Went to flash a rom, and now I have a new problem...
So, problem is when ever I try to install a rom, installation is aborted by CW. The error is "assert failed: getprop ("ro.product.device") == "t0lte" // getprop ("ro.product.device") -- "t0ltexx // getprop("ro.product.device") -- "GT-N7105" // .... and then so on, many more times, listing different varients of my phone T889, I317, etc.
The steps I took were: boot to recovery, factory reset/data wipe, format sdcard (I had an issue the last time I flashed where the sdcard was still full of crap after data wipe), try to flash rom, experience error, stare at my phone for 5 minutes, then helplessly post on XDA.
I tried this with two different roms, AOKP and PAC-Man... really stuck here, I can't flash anything. Hope you guys can help!
Reflash through Odin or Samsung Kies, re-root and try again
Crimson Ghoul said:
Reflash through Odin or Samsung Kies, re-root and try again
Click to expand...
Click to collapse
Reflash stock you mean? I gotta go out, but I'll give that a shot as soon as I get back home. Have you heard of this problem before? Your advice sounds pretty solid, thanks.
Not the exact same problem, but similar. Odin/Kies always fixes it
Didn't work :/ ... now I'm back on stock ROM, rooted, but same errors. Here's my error page:
http://i.imgur.com/PQdAGwv.jpg
Hope you guys can help!
Err, okay, I know nobody likes to end a thread without a true solution, but I did some googling with the exact text of my errors, and one guy said he tried to install the rom through rom manager, so i tried to install a touchwiz rom through rom manager... and it worked.... and then froze half way through.... so i pulled the battery, hit the power button, it automatically went into recovery, and i was going to try the TW rom, but gave AOKP one more try for the hell of it..and... it worked. I don't know why. It just worked.
You need to update your recovery. TWRP 2.5 or whatever is the latest.
rangercaptain said:
You need to update your recovery. TWRP 2.5 or whatever is the latest.
Click to expand...
Click to collapse
+1 to this^^^^^^^^
Here's the link to the TWRP thread so you can take a look..
http://forum.xda-developers.com/showthread.php?p=33867032
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4 Beta