OK, so I've got a Samsung Tab 7 (GT-P1000T). Running firmware 2.2, kernel 2.6. I'm trying to upgrade to CyanogenMod, looks like the closest I'll be able to get to ICS for the Tab as it's not supported. I've used Doomlord's zergrush root to get the device rooted, but now I'm having issues with CM.
I'm trying to use the p1 builds as they appear to be the correct one for this device. I've tried CM10 nightly and CM9 official to no success. At first there is an assert error because it's only looking for P1000, so I've tried changing the assert to look for P1000T and also just deleting the assert line. In both instances it reports that it is installing the update and then aborting the update with no indications as to why.
I'm hoping someone has had some experience with this or can point me in the right direction. I'm not having any luck with google. (Also, sorry if I've posted in the wrong part of the forum).
Related
XDA team,
Great thanks for all the work you are doing.
Until now there was no need to add a post because everything was working just fine.
I have a problem flashing a custom rom on my Galaxy Nexus. I used the root toolkit tu root the GN and that worked just fine.
When i trying to install custom firmware some of them installs without problems but other customs give an error (status 7) when trying to install it from recovery mode.
I have found multiple threats for this issue but i just not seem to find the right solution. I did everything by the book and i think it should work just fine but it doesn't.
Hope someone can help me with this isseu.
thnx in advance.
Status 7 errors are when you try to flash a rom that is not for your device. Only ever flash stuff that is specifically for your device. Flashing a rom is unlikely to do any harm but if you tried to flash a bootloader or radio from another device you are very likely to get in trouble.
If you have a GSM Galaxy Nexus get your roms from here and if you have a CDMA Galaxy Nexus get the then from here
I recently rooted and flashed my Samsung Galaxy S3 SCH-S960L (TracFone Variation, Sprint Based) with CyanogenMod 10.2-20131102-SNAPSHOT-M1-d2mtr which is for the MetroPCS version of CyanogenMod. Along with it saying MetroPCS, I also had an issue where the landscape orientation would be inverted which is quite a nuisance. Over on CyanogenMod's website someone suggested flashing the Sprint ClockworkMod (Which I was already using but for MetroPCS) and flashing the Sprint version of CyanogenMod. Now, upon flashing the ROM I get the error of
Code:
ClockworkMod Recovery v6.0.4.3
/storage/sdcard1: Checking
/storage/sdcard1: Mounted
--Installing" /storage/sdcard1/cm-10.1.3-d2spr.zip
Finding update package...
Opening update package...
Installing update...
assert failed: get prop("ro.bootloader") == "L710VPBLJ7" || get prop("ro.bootloader")
(Log is not directly copied, some symbols may be inaccurate)
From there is just continues with similar lines of error.
Can anyone provide a fix to using my phone? I have to use the MetroPCS/Sprint versions of CWM and CM since the TracFone version of the Galaxy S3 has little support. At the moment my device is a brick and I would really like to use CyanogenMod but without that orientation issue and it saying "MetroPCS"
Any support is appreciated.
With best regards,
SirBenjamin
SirBenjamin said:
I recently rooted and flashed my Samsung Galaxy S3 SCH-S960L (TracFone Variation, Sprint Based) with CyanogenMod 10.2-20131102-SNAPSHOT-M1-d2mtr which is for the MetroPCS version of CyanogenMod. Along with it saying MetroPCS, I also had an issue where the landscape orientation would be inverted which is quite a nuisance. Over on CyanogenMod's website someone suggested flashing the Sprint ClockworkMod (Which I was already using but for MetroPCS) and flashing the Sprint version of CyanogenMod. Now, upon flashing the ROM I get the error of
Code:
ClockworkMod Recovery v6.0.4.3
/storage/sdcard1: Checking
/storage/sdcard1: Mounted
--Installing" /storage/sdcard1/cm-10.1.3-d2spr.zip
Finding update package...
Opening update package...
Installing update...
assert failed: get prop("ro.bootloader") == "L710VPBLJ7" || get prop("ro.bootloader")
(Log is not directly copied, some symbols may be inaccurate)
From there is just continues with similar lines of error.
Can anyone provide a fix to using my phone? I have to use the MetroPCS/Sprint versions of CWM and CM since the TracFone version of the Galaxy S3 has little support. At the moment my device is a brick and I would really like to use CyanogenMod but without that orientation issue and it saying "MetroPCS"
Any support is appreciated.
With best regards,
SirBenjamin
Click to expand...
Click to collapse
http://review.cyanogenmod.org/#/c/54652/ got it merged in, come tomorrow just flash the latest d2spr nightly and it should flash in d2spr recovery for you.
it works
shabbypenguin said:
http://review.cyanogenmod.org/#/c/54652/ got it merged in, come tomorrow just flash the latest d2spr nightly and it should flash in d2spr recovery for you.
Click to expand...
Click to collapse
I got it to work(this is bilyan from IRC) missed CM on my s3
wickedclown691 said:
I got it to work(this is bilyan from IRC) missed CM on my s3
Click to expand...
Click to collapse
glad to hear it
APN
make sure you back up your apn. After I installed d2spr I couldnt connect with data. I had to restore APN settings.
Convinced my friend to let me root and ROM his 2.3.6 Tmobile S II. Disaster ensued and with both CWM and TWRP, long story short, i couldn't flash any roms or do anything. Tried CM 10 and CM 11 [for Hercules/T989] on both CWM and TWRP several times and kept getting errors [error 7, error 0 on CWM], and product assert errors on TWRP. Now he's back on stock 2.3.6 with his GPlay market error 492ing and I promised I'd look into it and get him running on 4.0/4.1+. Anyone know why it keeps failing and going wrong? Even my Galaxy Tab 10.1 was easier to root and that could be a nightmare sometimes and I even softbricked it several times.
Best to use Odin to flash the latest 4.1.2 firmware. Make sure everything is working, then proceed from there. There's upgrading guides around... And you may need to use Google to find the firmware, as most links here are dead. Sammobile. Com may have it too. ?
This is actually one of the easiest phones to root, and most Samsung smartphones in general. I bought this phone for myself and my mom, and got my dad a Galaxy S2 Skyrocket (which is pretty much the exact same specs as this phone).
For all three phones, I had to use ODIN. Reverting to stock is painless--just make sure to follow the ODIN guide carefully. From stock, it's easy enough to flash a custom recovery (via ODIN).
Hi.
Yesterday i tried to use my old S3 i747 which i hadn't used for a long time, and it didn't see any sim card ("no sim card installed").
Before i put the device on the shell about 6 months ago, it had worked ok and saw exactly the same sim card. On that moment it had Jelly Bean installed on it.
I decided to install custom ROM, and have just installed custom ROM [5.0] CM12 D2att Alpha Builds [12/25] and updated my bootloader and modem to NE4.
It still couldn't see any sim card, so i am wondering - is it software or mechanical problem? Is there any possible way to check this?
P.s. I am noob in flashing ROMS, but as i figured out, because of my upgrading to NE4, the only ROMs i can install on my device are CM12 (also tried Cyanide L build). I tried to install 10.2.1 and it failed with "Error 7". So there is no way for me (at least which is known to me) to check any other ROMs.
Try flashing the latest CM11 but for the d2lte. Status 7 errors can be caused by using an outdated recovery.
Been wanting to play around with Marshmallow and saw that we can finally get it on the S3. Followed everything to a T in the OP. Using TRWP, [i am now,] running L710VPUDNJ2 Touchwiz on my S3 on it now since I was rocking CM11 on some out of date firmware version (MD4 I think) and yet it just fails. Do you guys have any ideas? Do I need to flash CM12.1 first for some reason?
Here's a link for reference: http://forum.xda-developers.com/gal...rom-d2spr-cyanogenmod-13-0-t3248561?nocache=1
I also would be posting these questions on the thread itself but I guess I don't have enough posts to do so.
Edit: I figured out my problem, I ended up having to install CM12.1 and then go to CM13. Which I find strange since I've never had something like that happen before but I wanted to put that note out there.