Develop Bugs

[Q] Rooted Now what??

Hello group,
I just finished rooting my samsung galaxy s3 sgh1747m using the odin method.. I have all the titanium backups except media. I have 2 surperuser prgs installed and also Rom Manager.
I just reset my counter using triangleaway.290 on a custom rom.. I am running also clockwork mod recovery 5..5. .0 4
my question is...
How do get the latest Jelly Bean Updates on to my phone.. with modified status..
(i am using jb 4.1.1 right now)
baseband i747mvldlk4
Also how do i get the latest recovery clockwork recovery file
any help would be apprieciated//
HolydiverWpg

do not double post.
you are currently ON the latest stock firmware for your device. are you wanting to install a custom ROM to get a newer (4.2.2) release?
you can use Rom Manager to update your recovery. once thats done, if you havent done so yet, boot into recovery and make a nandroid (backup). you may need it down the road.

yes!
Yes I want to know how i can update my 4.1.1 once the newer Jelly Bean 4.2.2 update is available.
i have made a nandroid back and i also made a titantiam backup..
is there a newer version of CWM for my phone??rom manager says no.
xBeerdroiDx said:
do not double post.
you are currently ON the latest stock firmware for your device. are you wanting to install a custom ROM to get a newer (4.2.2) release?
you can use Rom Manager to update your recovery. once thats done, if you havent done so yet, boot into recovery and make a nandroid (backup). you may need it down the road.
Click to expand...
Click to collapse

The 4.2.2 custom roms are located in the Original Android Development section. There is no 4.2.2 update from samsung. Look them over and read up on the flashing process. The link in my signature has some good information.

Galaxy S3 bootloops after flashing any custom rom

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.

[Q] Beginner - Help!! Error Status 7

I just rooted my AT&T Galaxy S3
Specs:
Model number: SAMSUNG-SGH-I747
Android Verson: 4.3
I am trying to install the AOKP Rom for my device. I have it all downloaded and know how to install it but I keep getting Status error 7. What is happening? I read a little online and it says this error is for whenever you have the incorrect ROM version? Please help!!

Install the latest cwm onto your phone and flash from recovery mode.

audit13 said:
Install the latest cwm onto your phone and flash from recovery mode.
Click to expand...
Click to collapse
How do I do that?

Check page 3 in the Android development section.

BammS2 said:
Check page 3 in the Android development section.
Click to expand...
Click to collapse
That doesnt help at all /:

Originally Posted by BammS2
Check page 3 in the Android development section.
Click to expand...
Click to collapse
That doesnt help at all /:
Click to expand...
Click to collapse
If you already have a custom recovery CWM then just find the most up to date version of it. You obviously installed once already. Also are you referring to stock 4.3?
Sent from my Awesome Phone using xda app-developers app

Also getting Status 7 error
I had TWRP installed (whatever ver comes with toolbox app)
Read reply, and installed latest version of CWM Touch from: http://forum.xda-developers.com/showthread.php?t=2152769
Still getting Status 7 on two different ROMs.
Now, I had been on 4.1.1, rooted and flashed a custom ROM no problem
Had some problems with my TMO service (I have another thread in this forum) and ended up doing an ODIN flash back to stock (4.0.4)
Which I have now sitting at stock, rooted. Is it possible that I'm getting the status 7 because both of the ROM's I'm attempting to flash are 4.4.2 and that is too big of a leap from 4.0.4? I'm going to grab a 4.1.x rom now to see if any different, but wanted to share history and that I was getting same error

The easiest way for me to get 4.4.2 onto an s3 was this:
1) copy a custom rom to your sd card (internal or external)
2) use Odin to flash back to any stock rom for your phone;
3) use Odin to install the latest version of Philz Touch Recovery from here (get the tar version and flash in PDA): http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att;
4) update to the most recent non-4.3 bootloader: http://forum.xda-developers.com/showthread.php?t=2321310
5) do a full wipe in recovery;
6) flash a custom 4.4.2-based ROM from recovery.

dannymac77 said:
I had TWRP installed (whatever ver comes with toolbox app)
Read reply, and installed latest version of CWM Touch from: http://forum.xda-developers.com/showthread.php?t=2152769
Still getting Status 7 on two different ROMs.
Now, I had been on 4.1.1, rooted and flashed a custom ROM no problem
Had some problems with my TMO service (I have another thread in this forum) and ended up doing an ODIN flash back to stock (4.0.4)
Which I have now sitting at stock, rooted. Is it possible that I'm getting the status 7 because both of the ROM's I'm attempting to flash are 4.4.2 and that is too big of a leap from 4.0.4? I'm going to grab a 4.1.x rom now to see if any different, but wanted to share history and that I was getting same error
Click to expand...
Click to collapse
Your main problem is that you need an updated bootloader. Please read up on this as it has been covered in great and very extensive detail throughout these forums. One bootloader will cause you to no longer to be capable of using ODIN to flash back to any stock based ROM without bricking your phone so you need to be careful.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Read more and you will see that cwm recovery is highly recommended for flashing 4.4.2 roms. Some roms dont flash good with twrp.

[Q]Need clarification for rooted rogers note 2, android 4.4

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.

Sgh-i747 4.4.2

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