Develop Bugs

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.

Bottom line steps to upgrade rooted 4.4 to 4.4.2?

Okay, I am in the same boat as many others here. I am running a rooted stock 4.4 with the Elemental 2.3 kernel, along with the two dalvik/bionic hacks and naturally xposed with all sorts of modules. My recovery is TWRP 2.6.1.0., and my device is a 2013 N7 wi-fi model. I think I used Wug's toolkit to root.
I have the OTA 4.4 > 4.4.2 .zip file. What is the easiest way to go about updating to this, and then getting back root and everything else? I have seen reports of people actually flashing the OTA using TWRP, but then some people have problems. Does a person have to force an unroot first, and then go through ADB sideloading from pc/console? Is there a way to flash this with either TWRP or one of the Phil/touch recovery setups?
I know that the kernel is untouched with this OTA, and that I will have to re-root and then re-install xposed. I also know that AppOps is broken with the 4.4.2 release, hopefully something they will sort out. Does it make sense to redo the two hacks for dalvik and bionic?
Anyone have a tried and tested way to update and get back to full root as easily as possible?

I'm in the same situation too, but would installing a custom Rom with 4.2.2 on not solve it if you were happy to flash custom?

..

BigPickle80 said:
I'm in the same situation too, but would installing a custom Rom with 4.2.2 on not solve it if you were happy to flash custom?
Click to expand...
Click to collapse
The beauty of the Nexus 7 is that you can stick with the stock rom and nowadays still get all the goodies you want with xposed and other tweaks that accomplish the same thing as most hotrod roms. I want HDMI out, which I have lost on other devices after going to a CM based build.

[Q] Update to 4.4.3

My Nexus 7 wifi has the 4.4.3 update that has been prompting me to update. I tried doing the update which fails.
I do have TWRP installed, MultiROM, and a customer kernel. I tried flashing a custom kernel which did not resolve the issue.
I currently swap between stock and CM depending on what I would like to play with.

pctechdroid said:
My Nexus 7 wifi has the 4.4.3 update that has been prompting me to update. I tried doing the update which fails.
I do have TWRP installed, MultiROM, and a customer kernel. I tried flashing a custom kernel which did not resolve the issue.
I currently swap between stock and CM depending on what I would like to play with.
Click to expand...
Click to collapse
I'd do a nandroid before doing anything.
It might help if you state what the exact contents of the error is, my guess is that you have changed something in /system (unexpected contents error), and flashing a custom kernel won't fix it, in fact you would want to flash a stock 4.4.2 system.img and stock 4.4.2 boot.img if you want to use the OTA method, else you can just skip using the OTA and try and flash a 4.4.3 system.img and 4.4.3 boot.img, either way make sure you clear dalvik and cache before booting up after the system flashes.

You cannot install official updates if your device is modified!
Since you mentioned that you are familiar with CM, why don't you update to the latest CM ROM?

mediumsteak said:
You cannot install official updates if your device is modified!
Since you mentioned that you are familiar with CM, why don't you update to the latest CM ROM?
Click to expand...
Click to collapse
I play with it every once in awhile but I don't know why I enjoy stock but I do. Maybe I will go back to CM.

New to rooted LG GPad-have questions

Hi folks. Long time rooter/rom user of phones and tablets. I have some questions for my V500
Since it is rooted, would this be the next step - http://forum.xda-developers.com/showthread.php?t=2641409
(Installing TWRP for a custom recovery)
Since I'm on 4.4.2 with a V50020d base, would I then focus on getting 4.4.2 base roms and flash them via that TWRP I installed?
This does seem like a really fun and snappy device. From what I can tell, it has an IR Blaster right? Are there any roms that don't work with the blaster (I see this sometimes in the Galaxy Tab roms for devices that have the IR blaster)

Once you root, the next step is installing TWRP so you can install roms.

I also have the V50020d UK version.
Stumproot which is available here worked fine for me, easiest root i have ever done. Just install apk and your done.
Installing and getting custom recovery to successfully flash a ROM is another story. I have managed to get TWRP flashed to the device and boots correctly. However it fails when i try to flash CM11 or any other ROM. After reading around I think I may have to downgrade the stock 4.4.2 to 4.2.2 in order to get TWRP to flash. I am not struggling to find the correct stock 4.2.2 kdz firmware for the v50020d device.
It's been a bit of a head scratcher! Let me know how you get on with yours.

Cracked it today. I've written a guide for all UK users who are stuck with V50020d, compiling all the info. http://forum.xda-developers.com/lg-g-pad-83/help/v50020d-uk-root-twrp-flash-stock-4-4-2-t2938914
Hope it helps

fresh87 said:
I also have the V50020d UK version.
Stumproot which is available here worked fine for me, easiest root i have ever done. Just install apk and your done.
Installing and getting custom recovery to successfully flash a ROM is another story. I have managed to get TWRP flashed to the device and boots correctly. However it fails when i try to flash CM11 or any other ROM. After reading around I think I may have to downgrade the stock 4.4.2 to 4.2.2 in order to get TWRP to flash. I am not struggling to find the correct stock 4.2.2 kdz firmware for the v50020d device.
It's been a bit of a head scratcher! Let me know how you get on with yours.
Click to expand...
Click to collapse
I did mine with towelroot. I'll be looking to flash a custom recovery soon. I wanted to pop in here first to double check before going ahead with a recovery and a rom.

I new to LG and have 2 of these for my boys.
I have a us and uk one, i assume these will need different ways of rooting and flashing twrp etc?
I rooted one with Kingoroot no issues, but damn, getting cwm to install is a mare.
Both mine are on 4.4.2.
Looked at so many tuts, they all change due to time and i had to give up as was draining me.
Any tips on how to get cwm installed fella.
Best wishes

I've just created a tutorial for first time custom recovery installation.
http://forum.xda-developers.com/lg-g-pad-83/orig-development/recovery-t2945917

Deltadroid said:
I've just created a tutorial for first time custom recovery installation.
http://forum.xda-developers.com/lg-g-pad-83/orig-development/recovery-t2945917
Click to expand...
Click to collapse
Thank you Delta. I will check it out ASAP.

Unable to update to new versions of TWRP & ViperOne Rom

Hi All,
Iv'e never posted here before, but I'm having issues updating to a newer version of TWRP and updating to the latest version of the ViperOne Rom.
I am currently using TWRP v2.8.7.0. I attempted to flash the latest version 3.0.2.0, but the recovery fails to load once I have flashed it. If i flash back to the older version the recovery works straight away.
The reason I am trying to install the newest TWRP is because newer ViperOne Roms don't seem to work when flashed. I am currently using ViperOneM9 V3.5.0. None of the later versions are working for me. Once I flash the newer Roms, the handset keeps booting back to the bootloader.
Does anyone have any idea why these problems are happening? I have no idea what to try next.
Thanks

JM92W said:
Hi All,
Iv'e never posted here before, but I'm having issues updating to a newer version of TWRP and updating to the latest version of the ViperOne Rom.
I am currently using TWRP v2.8.7.0. I attempted to flash the latest version 3.0.2.0, but the recovery fails to load once I have flashed it. If i flash back to the older version the recovery works straight away.
The reason I am trying to install the newest TWRP is because newer ViperOne Roms don't seem to work when flashed. I am currently using ViperOneM9 V3.5.0. None of the later versions are working for me. Once I flash the newer Roms, the handset keeps booting back to the bootloader.
Does anyone have any idea why these problems are happening? I have no idea what to try next.
Thanks
Click to expand...
Click to collapse
In one word, u must upgrade to a Marshmallow firmware, because latest versions are compatible only with Marshmallow (Android 6).
This is a good place to start reading:
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698

Fain11 said:
In one word, u must upgrade to a Marshmallow firmware, because latest versions are compatible only with Marshmallow (Android 6).
This is a good place to start reading:
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Click to expand...
Click to collapse
Thanks so much. I appreciate your help.