Related
So I rooted my phone and installed the latest CWM recovery but every time I try to install any custom rom I get a status 7 error and it says something along the line of asserts failed ro.product.drvice == d2att. I've tried using TWRP, I've unrooted and installed stock, nothing seems to work. Last week I was running Jellybam fine for about 2 days, got stuck in bootloop, tried numerous ways to fix it, ended up returning to stock but now I cannot flash anything. Help me please
The status 7 error happens when the ROM ur about to flash, checks to see if the model of ur phone is compatible with said ROM. Its a good thing(safety mechanism) but can be a pain at the same time. What version of cwm are u using? Download the latest cwm recovery thru the ROM manager app and that can sometimes fix the issue. What ROM are you trying to install?
Sent from my SAMSUNG-SGH-I337 using xda premium
I think 6.0.2.3? not 100% sure though.. and I need to be rooted in order for rom manager to work... I tried using it but it kept saying the flash failed.. I'm using the root recovery. I've tried flashing CM 10.1 and RC5 as well as the latest and 3 before that Jellybam Roms
shewantsmyduck said:
I think 6.0.2.3? not 100% sure though.. and I need to be rooted in order for rom manager to work... I tried using it but it kept saying the flash failed.. I'm using the root recovery. I've tried flashing CM 10.1 and RC5 as well as the latest and 3 before that Jellybam Roms
Click to expand...
Click to collapse
Latest cwm is at 6.0.3.1
I think you're getting a little confused.
You need to be rooted to have any custom recovery installed, so right off the bat you are rooted. You shouldn't flash anything with rom manager, it can cause serious harm to your phone. Tom manager is best for just updating your recovery.
There are two main reasons for a status7 error, out of date recovery or an out of date bootloader.
Update your recovery to 6.0.3.1 and he to flash it again, if it comes back you'll need to update your bootloader a two second search in these threads will provide you with a large handful of threads where people had identical issues as you
Sent from my SGH-I747 using xda app-developers app
Checked my bootloader and it says i747UCDLK3 and I think that's the latest... I'll root and install latest CWM through rom manager once I get home
And one question though... I tried using TWRP 2.5 (the latest) and I still got the status 7 error...?
shewantsmyduck said:
So I rooted my phone and installed the latest CWM recovery but every time I try to install any custom rom I get a status 7 error and it says something along the line of asserts failed ro.product.drvice == d2att. I've tried using TWRP, I've unrooted and installed stock, nothing seems to work. Last week I was running Jellybam fine for about 2 days, got stuck in bootloop, tried numerous ways to fix it, ended up returning to stock but now I cannot flash anything. Help me please
Click to expand...
Click to collapse
Can you flash any stock modded rom's ? You state you went back to stock but what method did you use to go back to stock ?
Why oh why were you using jellybam...
My cousin has it on his Verizon GS3 and it works perfectly fine so I thought I'd give it a shot. To go back to stock I followed some unroot and return to stock I found online.. not sure of the link. It basically consisted of flashing it in Odin and returned it back to stock 4.0.4 which I then updated to 4.1.1 using att ota. I'm not sure if it was a a modded stock rom or not. And I really don't feel like going back through that mess again only to flash it and get stuck in another boot loop I want to be pretty positive that it will work :/
shewantsmyduck said:
My cousin has it on his Verizon GS3 and it works perfectly fine so I thought I'd give it a shot. To go back to stock I followed some unroot and return to stock I found online.. not sure of the link. It basically consisted of flashing it in Odin and returned it back to stock 4.0.4 which I then updated to 4.1.1 using att ota. I'm not sure if it was a a modded stock rom or not. And I really don't feel like going back through that mess again only to flash it and get stuck in another boot loop I want to be pretty positive that it will work :/
Click to expand...
Click to collapse
The ODIN flash to stock 4.0.4 probably installed the old ics bootloaders, and the ota update to 4.1.1 may not have included the new jb bootloaders.
Ok so what is the newest bootloader? I downloaded the root checker that allows you to see your bootloader version and it's on i747UCDLK3.
shewantsmyduck said:
Ok so what is the newest bootloader? I downloaded the root checker that allows you to see your bootloader version and it's on i747UCDLK3.
Click to expand...
Click to collapse
That's the right one
Sent from my SGH-I747 using xda premium
So what should I do now then :s
You're trying to flash the wrong rom for your device, or you're not using the right recovery for your device. What Galaxy S3 model do you have? On which carrier are you and where did you buy the phone?
I have an AT&T i747 that I got at an AT&T store. The Rom is correct as I've downloaded it numerous times and I've tried the latest TWRP recovery and still received the error.
I'm going to try and flash a factory image tomorrow from the development section and root afterwards. As Michael3214 pointed out in a pm, the issue may be that my phones id has changed, hopefully a factory image will fix that.
Hello, I recently just updated my Rogers SGH-i317M to 4.3, which then downloaded a system update which put it at 4.4. I was running Jedi X20, which is based on 4.1.2, when I first tried updating, I flashed the "4.3param_tz" file in odin, and was left with an error screen saying I need to recover using Kies, so I downloaded the official release, flashed via odin, and thats how I got to where I am now. I want to try the "Ditto Note 3" rom, "Sky Note Air 4.3", "Mean Bean" and "Beanstalk". My main question is, can I just start flashing these roms like I was before on 4.1.2, or do I need to use the specific kernel listed on their page? Before you needed a specific kernel to run a touchwiz rom or an aosp rom, so is it still the same? Or can I use my stock 4.4 kernel and try both aosp and tw roms now? If so could you point out the kernels I would need? And educate me on anything else I should know about before flashing 4.3 and 4.4 roms, (I'm not worried about warranty), this would be greatly appreciated. Thanks for your time in reading this and helping me out, much appreciated!!
Regardless of where u are, I'd Odin to Rogers stock KK 4.4.2. Then Odin Twrp recovery, boot into twrp recovery and flash SU v.1.99. Finally choose your rom and flash away. This way you are on the lastest KK 4.4.2 Bootloader and KK Modem/Baseband.
just_visiting said:
Regardless of where u are, I'd Odin to Rogers stock KK 4.4.2. Then Odin Twrp recovery, boot into twrp recovery and flash SU v.1.99. Finally choose your rom and flash away. This way you are on the lastest KK 4.4.2 Bootloader and KK Modem/Baseband.
Click to expand...
Click to collapse
I did all that except flash SU 1.99, so I tried flashing SKynote Air and it didnt work, upon restarting my phone it said no os is available. So I tried restoring from the backup I made of the official 4.4.2 Samsung rom in twrp, didn't work. Tried Odin, didn't work. Then I tried flashing the Skynote rom again and it worked. So I'm afraid of flashing any other roms now.
Hello all. I just received a galaxy s3 from my sister in law running 4.4.2. I am aware I can't downgrade the complete firmware using Odin. The phone it's rooted. My question is what can I do with this thing as far as playing with roms and what not? Can I only install 4.4.2 based roms? Can I even unroot? I have been rooting and installing roms for years now but never have a phone felt more unfriendly before this. Thanks in advance.
Is the phone running stock 4.4.2?
You can install a custom recovery to the phone, copy some custom ROMs to an external SD card, and try out a bunch of ROMs.
Yeah its stock 4.4.2 rooted with clockwork mod recovery. Do the roms have to be 4.4 or 4.4.2 based? Tried cyanogenmod 4.3 and failed. I pretty much would like to flash via odin to go back to stock unrooted but 4.4.2 was over the air. Got 4.3 via sammobile but that fails. Kies won't show my device for firmware recovery. Shows it as normal to sync.
What error did you get when trying to flash CM10.2? Is your CWM up to date?
I would have assumed that CM10.2 would be comaptible with your KK bootloader and modem.
Do not make anymore attempts to flash 4.3 via Odin. This could result in a bricked phone because a KK modem on a 4.3 bootloader cannot be fixed using any method available on XDA.
Yeah I'm aware of the boot loader and modem downgrade issue. Tried odin once and just left it as is.
Is your CWM up to date? What error did you get when trying to flash CM10.2?
I don't remember the error. According to Rom manager, my recovery is up to date
What version is the cwm? I prefer to manually flash a custom recovery instead of relying on ROM manager.
Cwm 6.0.4.7. I've always used rom manager except for my galaxy nexus. Flashed with windows terminal and fastboot.
Since CWM is up to date, try flashing the most recent CM11.
Older cm roms, and any older roms should run fine on NE4. Some may not flash though, such as cm10. This is because the updater script doesn't include NE4 as it wasn't out when the rom was built. If you edit the script to make it flash, any of the available roms should run just fine.
As it stands though, the easiest thing would be to do as audit13 suggested and flash cm11. That and most other recent roms should flash just fine w/o any extra work.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
well, after downloading the most recent cm11 nightly and gapps, rebooted into recovery and wiped. when trying to flash cm11, sd card not mounting. couldn't mount, restored a backup only to be greeted to a display that would not go to sleep and a fury of app and processes stopping pop ups. settings-accounts-backup and reset-factory data reset-etc did nothing but ask for a password. did it through recovery to a perfectly working phone with baseband version: unknown, IMEI: unknown, IMEISV: unknown. flashed the NE4 modem Doc posted in another forum, no dice. same message from cm as before. this time i remember. it was a bunch of basebands not including NE4.
And getprop ro.bootloader says NE4. first said unknown but maybe i typed it wrong.
Got it all back running. tried the S3Rx NE4 aroma zip that would end with installation aborted. found enewman17's post on updating using a stock-rooted 4.4.2 zip after flashing Doc's modem zip. all is well! So thank you DocHoliday77, and thank you enewman17!
Glad you got it working!
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Hi, I'm having issues flashing roms which aren't based off of 4.1.2 firmware. I am rooted on 4.1.2 JB and have flashed a few of the 4.1.2 roms on my tmobile s3 t999, when I attempt anything else it fails with "error 7" for example cm10 and 11 or 4.3/4.4. Please Help? Thanks.
1. Make sure you're on latest version of recovery.
2. You may need to ODIN to a newer version/bootloader.
ShernDog said:
1. Make sure you're on latest version of recovery.
2. You may need to ODIN to a newer version/bootloader.
Click to expand...
Click to collapse
I tried flashing over the bootloader update found here. http://forum.xda-developers.com/showthread.php?t=2282603
and am receiving a "status 7" error once again. I restored a backup which contained no mods, downloaded rootkeeper and booted into cwm tried flashing the updated zip, it returned a status 7 error. I'm not sure how to proceed. I am currently using 4.1.2 axis with trinity kernel. I cant seem to flash anything whatsoever aside from roms based off 4.1.2. Can someone help me step-by-step?
thanks
Update recovery
thanks guys. Success!!!
hello im tring to flash roms for my s3 t999 when going to the process of root I install cwm and then I was installing Update-SUperuser.zip but it failed it says (bad) installation aboarded but the wiered thing is ive done this in the past its not only the superuser cause I have root it but when I tried installing any rom for the t999 4.3 it stopeds in the same error. Em I missing something??
neutech15 said:
hello im tring to flash roms for my s3 t999 when going to the process of root I install cwm and then I was installing Update-SUperuser.zip but it failed it says (bad) installation aboarded but the wiered thing is ive done this in the past its not only the superuser cause I have root it but when I tried installing any rom for the t999 4.3 it stopeds in the same error. Em I missing something??
Click to expand...
Click to collapse
Are you on the latest version of CWM? If not update to latest versions of CWM.
what would be the latest for s3 4.3 I tried CWM_6.0.4.7 but it didn't work it stays in a black screen
ok I used a couple of them even the one im running now its cwm 6.4.7 same error it doent take anyroms at all none. its rooted so I have no clue what else to try any ideas?
Being rooted won't make a difference. Download and flash latest cwm or twrp if it still doesn't work. Check their site for the most up to date recovery version
on the cwm website the version is 6.0.4.5 and I have CWM_6.0.4.7 so its not the recovery its gotta be be something else
neutech15 said:
on the cwm website the version is 6.0.4.5 and I have CWM_6.0.4.7 so its not the recovery its gotta be be something else
Click to expand...
Click to collapse
Try different methods to download the rom. Could be bad downloads. If it still doesn't work, use twrp