So,
I spent the last days trying to learn how to port a rom to a new device,
so I could manage to compile a rom, doesn't matter witch to xoom 2 ME.
I've been trying to make a /device folder and extract the /vendor, out of the one from AOSP rom for
the motorola spyder device ( droid RAZR), especially because they have similar hardware.
So I finally got a .zip rom, made out of the ICS vanila source code, so then I could use the same kernel it already has.
even though I'm pretty sure it won't work pretty well, maybe it won't even boot.
But then I tryed to flash it over the safestrap, and it didn't flash I got the following message:
asser failed: getprop("ro.product.device") == "fleming" || getprop("ro.build.product") == "fleming"
error in /sdcard/full_fleming.zip (status 7)
I also tryed to flash a kernel I compiled, and then the original kernel of it repacked,
the kernels flashed alright, but then when I restarted the phone, the kernel was still the original one,
so it didn't actually flashed.
Please if anyone can give some help I'd be really glad!
Maybe the safestrap is not able to flash a kernel or a rom, maybe it's blocked or maybe I have do something espcial to pack a .zip for a safestrap.
Please help me.
by the way, the safestrap is the 3.12 from hashcode
Related
So I was trying to get Wallet on my phone, complete mess, the phone went fubar, I can get the phone to work on stock 2.3.4 but can't update to 2.3.6 nor I can install any ROM, and yes, the phone is rooted.
If I try on updating to 2.3.6 I get >>>
assert failed: less_than_int(1303507835,getprop("ro.build.date.utc")
Status 7
If I try to install any Rom I get >>>
assert failed: getprop("ro.product.device") == "crespo" ll
getprop("ro.build.product") == "crespo"
And trying to restore will simply give me system.img not found.......
So if nothing works towards, then I will simply and rather prefer to do a clean install so it will wipe everything, but, is there a way to "Wipe" everything and reinstall?
And yes, I already tried the "Wipe data/factory reset", no good at all.
Upd: I can install kernels.....go figure.....
If this is a NS4G you can use OneClickStock
tylerwatt12 said:
If this is a NS4G you can use OneClickStock
Click to expand...
Click to collapse
Thx Mate but I have a i9023 (NS 3G+ if u can say), I was able to downgrade using the guide from TheUnlockr and it was a PITA since the file somehow is not really the best to work on the NS but I was able to update to 2.3.6.
And since now I'm updated and found a way to mess the phone even more it is time to try the Wallet again!!!
Hi all, I recently rooted my NS4G and flashed my rom to the Brainmaster's MIUI 10.14.11. It worked great for a while and then I started having issues with it so I tried to update it to the 10.28.11 version and it wouldn't let me. I was finally able to reflash to GRJ06D, but no other custom rom would work. I'm using CWM 5.0.2.0. ROM Manager won't work either after it gets into recovery. I get the error message...
assert failed: getprop("ro.product.device") == "crespo4g" || getprop("ro.build.product") == "crespo 4g"
E: Error in /sdcard/
(Status 7)
Even trying to do an OTA system update via Sprint freezes and gives me the Android error message (triangle with exclamation). I've tried many many times to reflash and no success.
What do I need to do?
This issue has been reported a few times and there are a few ways to fix it;
1) Make sure you downloaded the right ROM; ie, the ROMs from the Nexus 4G Development section
2) If you're installing ROMs through ROM Manager, don't. Reboot into recovery mode, do a full data, cache and dalvik wipe and then flash the ROM zip while still in the CWM recovery mode
3) Else; try a different version of CWM, make sure it's compatible with your device and then do step 2 again.
Good luck.
Greetz
I think you should flash CWM again then wipe data, cache, dalvik, boot, then flash rom again and report your findings back to us.
I had this issue last week.. You've probably tried to flash the incorrect ROM originally or something..
The only way I could fix it was to boot into download mode, and flash the PDA, phone and modem via Odin. You can get the firmware from samfirmware.com
Thanks for the responses, its funny because I flashed the 4.0.1.0 CWM, which was for the GSM version and then reflashed to 5.0.2.0 (NS4G) in order for the MIUI rom to work. It was after flashing that and running MIUI for a while that I started having issues so I reflashed a new 5.0.2.0 and its still the same.
I haven't been able to flash back to the CWM 3 that it originally came with because I lost my micro USB cable. I hope to get this fixed soon! Thanks again, will keep you guys posted.
I was previously running CM9 but flashed to 2.3.6, factory wiped and unrooted. Since then I have been unable to get the OTA even when force-checkin. Should I not expect it to work since it has been rooted before? I suppose it's not a huge deal but I would love to have OTA 4.1 when available.
I think 4.0.4 has been taken off the server, and as soon as 4.1 is available you will get it as well!
Sent from my Nexus S using Tapatalk 2
I don't understand why everyone is so obsessed with getting an OTA?
You most likely won't be one of the first to get it and as soon as its released someone on here is going to post a better, faster, rooted version anyway... which you'll then flash.
Why not just stick with CM9 instead and wait the day or so it takes for the custom ROM's to flow once OTA hits? Makes SOOOOO much more sense to me?
bryantee said:
I was previously running CM9 but flashed to 2.3.6, factory wiped and unrooted. Since then I have been unable to get the OTA even when force-checkin. Should I not expect it to work since it has been rooted before? I suppose it's not a huge deal but I would love to have OTA 4.1 when available.
Click to expand...
Click to collapse
Flash 4.0.4 factory image
https://developers.google.com/android/nexus/images
here you can find anything you want for 2.3.6 to 4.0.4 http://www.randomphantasmagoria.com/firmware/nexus-s/i9023/
You can check the DEV section which has several OTAs.
You can check the following two:
http://forum.xda-developers.com/showthread.php?t=1569509
http://forum.xda-developers.com/showthread.php?t=1751285
Forget all those links best thread so far
http://forum.xda-developers.com/showthread.php?t=1063664
Click and choose your model! Mine's i9023 btw
Ok so a bit of a follow up:
I unlocked, rooted, flashed recovery and when I go to install CM9 RC1 I'm getting Status 7.
assert failed: getprop("ro.product.device") == "crespo" || getprop("ro.build.product") == "crespo"
E:Error in /......
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
It seems like it thinks it is the wrong ROM for the device but I am positive it is correct as I've flash many crespo ROMs before. Any ideas?
EDIT: OK, so I just re-flashed CWM in ROM manager and it seemed to do the trick.
NYYFan325 said:
I don't understand why everyone is so obsessed with getting an OTA?
You most likely won't be one of the first to get it and as soon as its released someone on here is going to post a better, faster, rooted version anyway... which you'll then flash.
Why not just stick with CM9 instead and wait the day or so it takes for the custom ROM's to flow once OTA hits? Makes SOOOOO much more sense to me?
Click to expand...
Click to collapse
That's what I've been telling everyone. Mere minutes after the OTA is out we'll have something rooted/deodexed and whatnot. *shrugs*
bryantee said:
Ok so a bit of a follow up:
I unlocked, rooted, flashed recovery and when I go to install CM9 RC1 I'm getting Status 7.
It seems like it thinks it is the wrong ROM for the device but I am positive it is correct as I've flash many crespo ROMs before. Any ideas?
EDIT: OK, so I just re-flashed CWM in ROM manager and it seemed to do the trick.
Click to expand...
Click to collapse
OR, you could download the stock images and be done in 5 minutes with fastboot.
Finally bought a Nexus S so that I could run CM. I've activated the phone with sprint, and loaded a few other ROMs just fine (running JRO03R - Stock 4.1.1 currently). I've got a SPH-D720, and I've tried loading both the cm-10-20121024-NIGHTLY-crespo.img and cm-10-20121024-NIGHTLY-crespo4g.img using CWM 6.0.1.0.
The "crespo" one will load without problems, boot up, and no network (baseband unknown, phone number unknown, etc.). I Can't load the "crespo4g" img as it returns with an error in CWM status 7.
What am I doing wrong?
datag0d said:
Finally bought a Nexus S so that I could run CM. I've activated the phone with sprint, and loaded a few other ROMs just fine (running JRO03R - Stock 4.1.1 currently). I've got a SPH-D720, and I've tried loading both the cm-10-20121024-NIGHTLY-crespo.img and cm-10-20121024-NIGHTLY-crespo4g.img using CWM 6.0.1.0.
The "crespo" one will load without problems, boot up, and no network (baseband unknown, phone number unknown, etc.). I Can't load the "crespo4g" img as it returns with an error in CWM status 7.
What am I doing wrong?
Click to expand...
Click to collapse
Crespo4G represents the Sprint version of the Nexus S (Nexus S 4G). Crespo = All other variants of the Nexus S. Crespo and crespo4g are the identifying names Google gave the devices. So basically, Crespo4G roms aren't for your phone, only Crespo.
datag0d said:
Finally bought a Nexus S so that I could run CM. I've activated the phone with sprint, and loaded a few other ROMs just fine (running JRO03R - Stock 4.1.1 currently). I've got a SPH-D720, and I've tried loading both the cm-10-20121024-NIGHTLY-crespo.img and cm-10-20121024-NIGHTLY-crespo4g.img using CWM 6.0.1.0.
The "crespo" one will load without problems, boot up, and no network (baseband unknown, phone number unknown, etc.). I Can't load the "crespo4g" img as it returns with an error in CWM status 7.
What am I doing wrong?
Click to expand...
Click to collapse
If you activated the phone with sprint then you have crespo 4g which is d720 model if your not on sprint then you have crespo . The reason there's no data is because those img where for crespo so there's no radio to get signal . You should get the stock img for cresop 4g from Google AOSP site & install them
Sent from my Nexus 7 using xda premium
When i try to use Crespo4g, I get:
assert failed: getprop("ro.product.device") == "crespo4g" || getprop("ro.build.product") == "crespo4g"
E:Error in /sdcard/cm-10-20121028-NIGHTLY-crespo4g.zip
(status 7)
Installation aborted.
Again, Sprint phone, SPH-D720.
datag0d said:
When i try to use Crespo4g, I get:
assert failed: getprop("ro.product.device") == "crespo4g" || getprop("ro.build.product") == "crespo4g"
E:Error in /sdcard/cm-10-20121028-NIGHTLY-crespo4g.zip
(status 7)
Installation aborted.
Again, Sprint phone, SPH-D720.
Click to expand...
Click to collapse
Install a newer version of ClockworkMod recovery: http://forum.xda-developers.com/showthread.php?t=1782240
But I think it might be because your zip file is corrupt and you need to re-download it.
I'm already running 6.0.1.0....
I thought about the corruption thing, downloaded it multiple times on home desktop and school laptop, both sources don't work. Verified md5sum on downloaded file.
Try the version 5.8.0.2, it works for me: http://forum.xda-developers.com/showthread.php?t=1242947
Or try TWRP recovery instead, though I have no experience with it: http://forum.xda-developers.com/showthread.php?t=1196500
Otherwise I good luck. Then skip CM10 and go directly to SlimRoms.
Found out what I did wrong. Followed the wrong guide, downloaded the wrong CWM.
My device is a Nexus S 4G, and I followed the guide for the Nexus S, and used the download link in that guide.
Making sure everything you use that says crespo anywhere reads "crespo4g"
So make sure that the CWM that you download is for crespo4g. Crespo will work, but not for ROMS that check the device name before installing (such as cyanogen)
Thanks for the help.
Hi,
I need some help. Firstly I'm quite a noob so please go easy on me, have only flashed/rooted a couple of phones before this...both with pretty much no issues.
I flashed the CM 9.1 A while back to improve it, and decided I wanted to change it due to few bugs annoying me too much...such as the restarts, crazy battery life and most annoyingly of all calls only being able to be heard on loudspeaker! Buts can't seem to get any other rom to flash - tried 2 - samsation v6.0 kerneldev101 & MikTouch- 0.7-signed.
When trying to flash firstly 'samsation v6.0' i encountered an error code '"assert failed: getprop("ro.product.device") == "pyramid"
E:\Error in /storage/sdcard0/samsation v6.0.zip
(status 7)
Installation aborted.
and to try and overcome this I opened the updater script from rom zip and deleted the line 'assert(getprop("ro.product.device") == "pyramid" || getprop("ro.build.product") == "pyramid");'.....after reading in forums it could be this. After this line is deleted the flash attempt is 'opening update package...installing update...installation aborted'
I then tried MikTouch 0.7 and it came up with the 'status 7' error, so I deleted the first line of the updater script and now I am getting a 'status 4' error...even if I try to flash thru rom manager - CWM app.
Driving me crazy! Any help much appreciated.
even tried a different SD card to see if that makes a difference....and nope
installed new CWM - V6.0.4.6 after reading that may be the prob. no difference
To be honest it all P'd me off so much just went and bought myself the Moto G instead...but would still like to fix this one and get it even back to a stock like ROM so at least it functions properly but without all the bloatware.
Use TWRP instead of CWM. This should fix the issue.
Tried it thru the twrp app and it just launches into cwm recovery and does same status 4 error
Thanks for replying though!
Sent from my XT1032 using xda app-developers app
'Cwm-based recovery v6.0.4.6
--Installing: /storage/sdcard0/MikTouch-0.7-signed.zip
Finding update package...
Opening update package...
Installing update...
E:Error in /storage/sdcard0/MikTouch-0.7-signed. Zip
(Status 4)
Installation aborted
Sent from my XT1032 using xda app-developers app
I didn't mean the app found on Play Store. I meant the actual TWRP recovery.
You'll have to connect your phone to your PC, boot into bootloader, and flash the TWRP recovery, which will replace the existing CWM recovery.
Moto g looks like a great phone for the price, but I would want to fix my double shot too.
First off, the getprop errors you were getting were saying you were trying to flash a ROM for sensation on your doubleshot, not a good idea, don't delete getprop from updater-script no matter what the internet says, this is a good warning
Don't use an app for flashing, use recovery
But before you proceed any further I would suggest to boot into bootloader and write down every thing from that screen here, word for word
Then you will be sure to get the exact links and info, I wouldn't do anything until then, not to say @abe5 is having you bad info, he is correct, but I have a feeling there may be more info needed here
Sent from my Nexus 7 using XDA Premium 4 mobile app
Bootloader info
Hi,
OK thanks to both of you for your help! ...I guess I would rather check/be sure than do something worse to my phone.
Your right Moto G is great phone..I am pretty impressed so far...for the price. Only let down is the camera....I miss the doubleshot great camera...but you cant have it all....well not for £130
OK SO INTO BOOTLOADER..... (front screen reads as follows - hope this is what you mean?!)
***UNLOCKED***
DOUBLESHOT PVT SHIP S-OFF RL
HBOOT-1.45.0013
MICROP-0353
RADIO-11.16.3504.20_2
eMMC-boot
NOV 21 2011,20:20:47
FASTBOOT
VOL UP.... ETC ETC
.....
fickleama said:
Hi,
I need some help. Firstly I'm quite a noob so please go easy on me, have only flashed/rooted a couple of phones before this...both with pretty much no issues.
I flashed the CM 9.1 A while back to improve it, and decided I wanted to change it due to few bugs annoying me too much...such as the restarts, crazy battery life and most annoyingly of all calls only being able to be heard on loudspeaker! Buts can't seem to get any other rom to flash - tried 2 - samsation v6.0 kerneldev101 & MikTouch- 0.7-signed.
When trying to flash firstly 'samsation v6.0' i encountered an error code '"assert failed: getprop("ro.product.device") == "pyramid"
E:\Error in /storage/sdcard0/samsation v6.0.zip
(status 7)
Installation aborted.
and to try and overcome this I opened the updater script from rom zip and deleted the line 'assert(getprop("ro.product.device") == "pyramid" || getprop("ro.build.product") == "pyramid");'.....after reading in forums it could be this. After this line is deleted the flash attempt is 'opening update package...installing update...installation aborted'
I then tried MikTouch 0.7 and it came up with the 'status 7' error, so I deleted the first line of the updater script and now I am getting a 'status 4' error...even if I try to flash thru rom manager - CWM app.
Driving me crazy! Any help much appreciated.
even tried a different SD card to see if that makes a difference....and nope
installed new CWM - V6.0.4.6 after reading that may be the prob. no difference
To be honest it all P'd me off so much just went and bought myself the Moto G instead...but would still like to fix this one and get it even back to a stock like ROM so at least it functions properly but without all the bloatware.
Click to expand...
Click to collapse
Don't use CWM above 6.0.2.5 for flashing an older ROM. 6.0.4.6 is designed for KitKat and will fail older ROMs.
everything looks good on bootloader so the issue is with recovery or rom.zip
personally i think its the rom.zip, but I also recommend TWRP recovery
so i would download twrp (without dumblock) from HERE
and flash with fastboot, also do some erasing in fastboot for good mesure
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery nameofrecovery.img
the md5sum for recovery is listed next to download, be sure it matches use command line on linux or this for windows
but what i really think is the problem is the roms, bad download or whatever, the status 4 and status 7 are related to updater script, so either you playing with them messed them up or they were corrupt from the start
md5sum for MikTouch-0.7-signed.zip should be BAE9153946B02251621547DBFB537387
if not re download
now it is possible that the newer recoveries f\wont flash older roms, like Fuzi0719 said, but in theory they should and i have not had issues myself
but if need be weekends has posted older recoveries HERE be sure to thank him
flash with fastboot if you TWRP fails you
also when i see this --Installing: /storage/sdcard0/MikTouch-0.7-signed.zip
make me wonder, if i am correct the path on this phone is just /sdcard/MikTouch-0.7-signed.zip
but i cant recall as it has been months since i used my doubleshot, its just how i remember even the newer recoveries find sdcard path here
so maybe for good measure take everything important off sdcard and format to fat32
then put new rom on the root freshly formatted sdcard (not in any folders) before you flash
hope it all works out, if there is an issue let us know!
well I spent the whole evening mucking about with it and I have conquered it. Thanks guys for all the help...couldn't have done it without you!
After firstly having to switch to an older laptop as win 8.1 not compatible with htc drivers ...
I flashed TWRP and tried to flash new rom (miktouch 0.7) again through that, said failed. then tried to install the current ROM CM9.1 just out of interest which it also 'failed'
then considered the cwm comment about version, so flashed cwm 5.5.0.4. thru Hasoon 2000's ALL in 1 kit I still had. I then tried to reflash the current CM9.1 again, and it went through.....At the same time it occurred to me about me having 'messed' with the script files of MikTouch 0.7 ...maybe being the cause, so luckily, I had an original copy of the rom zip (kept justin kase lol) and then tried this method.
I now don't know if it was the script file or the cwm version number but hallelujah it WORKED. I honestly thought I was stuck on cm9.1 forever, I've spent so much time reading/trying to flash anything else!
Can't thank you all enough, whatever it was, I think I have overcome it now! phew.
:cyclops: :victory: