When I got this note 2, it didn't have the ota to lock the bootloader. I after a year or so on the Alliance 26 rom I had some issues and wanted to upgrade to the newest one. I tried to install it and it didn't take and was stuck in bootloop.
So I used the same files in odin to flash the phone back to stock and start it again.
I was finally able to get it rooted but no recover will install. I am having a hell of a time and I don't understand what I have done wrong. Even casual wont work.
Well when I try to install recovery like twrp the install fails and on boot it says software not supported my Verizon , take to your local vzw store for repair.
Knox has even been tripped as well and it seems like the bootloader is locked. How is that possible? Don't know how, i flash with odin a stock rom as I did when I got the phone rooted and installed a recovery and than a rom. No issues what's so ever.
Now it seems everything I try it either says software not supported by vzw or bad firmware update or boot loops. I have downloaded so many files from all of these recovery threads I'm lost .
Never had the ota update, once I got the phone I flashed it to mj9 per beanstown on the original alliance rom and ran that room ever since.
I think I have tried every how to in this forum. Can someone chime in and tell me what I am doing wrong?
Sent from my SCH-I605 using Tapatalk 2
Phone info..
Sent from my SCH-I605 using Tapatalk 2
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.
Here is what happened, i downloaded the OTA from AT&T, unrooted my phone and installed the update. It went all the way through, rebooted and that's where it stops. As soon as the AT&T welcome screen comes up the phone just freezes. When i plug it to my PC the phone is not recognized. Kies says it can't connect to the device. I'm able to get into download mode and odin seems to find the phone. But in download mode there is no option to reboot or anything. It only says "custom" on all options.
Can anybody help?
Factory reset usually solves most boot hangups. It will wipe your internal sd if you have stock recovery though.
i can't find any option to do a factory reset. I flashed Philz touch with odin, it said it passed. Tried a factory reset but it still freezes at the AT&T homescreen.
Any other way to do a factory reset?
Why'd you re-root BEFORE installing the update? Is there a particular reason? From what I've read on here, towelroot will easily root it afterwards.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
keithfrombm said:
Why'd you re-root BEFORE installing the update? Is there a particular reason? From what I've read on here, towelroot will easily root it afterwards.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Click to expand...
Click to collapse
I took root off the phone since most of the time root stops OTA updates. Then i downloaded and installed the update. I had plans to root it again after the update.
Hello there. I also attempted the 4.4.2 OTA from stock 4.3, and now I'm having this exact same issue. The device had TWRP recovery installed, so I re-installed the stock recovery. It was also rooted and a few system files were edited (lock sounds, hosts file), I reverted all the changes, did a full unroot via SuperSU and proceeded with the OTA. It seemed successful until it tried to boot.. it now freezes on the AT&T logo, as the OP mentioned. I installed TWRP recovery again via Odin so I could back up all the data from the phone and do a factory reset. Unfortunately, this did not fix the freezing. I've attempted reverting back to the latest official Odin .tar (4.1.1), which I've now learned is not possible since the 4.3 update and its locked bootloader. It would seem that the only thing that would do the trick now would be an Odin-flashable 4.4.2 tar. For now, I've installed CyanogenMod as a temporary solution.
I dunno if it has been tested yet but this is a TWRP/CWM flashable zip which also preserves root.
http://forum.xda-developers.com/showpost.php?p=53539462&postcount=5
It didnt work. I am currently uploading two more attempts now and will post the links in that thread as soon as they are ready.
this worked for me
Hi All, Just wanted to share a solution that worked for me. I was in the same boat. OTA update locked phone on ATT screen. Used steps 2 and 6 from link below and now have 4.4.2 running on my phone. Happy flashing.
http://forum.xda-developers.com/showthread.php?p=53574211
I got my Note 2 about 6 days ago and was on firmware 4.3 I noticed that the battery was draining very fast so I looked around online and found
4.3 had this problem so I updated the firmware to 4.2.2.After a day or so I got fed up with touchwiz and said screw it im going to root my
phone.so I started getting the note 2 ready to root this went fine I was able to boot up my phone with twrp. So then I made a backup through twrp
just in case I screwed up my phone. I then Flashed CM11 to the phone but it failed so I tried wiping the caches and it failed again. I then try
Booting it up but it is stuck on the Samsung logo. So I turn it off and said no big deal I got the backup I can flash so I try to flash that but it fails to
but after this I notice my Knox security is void.so im wondering is the Knox security causing the problem. Because after I did this I did some
Research and It said that It would void my warranty and it had an efuse? What exactly does this Knox voided warranty mean does it mean my
Is useless can or can I still flash roms to it ? And If so how would I go about doing this because im all out off ideas.
Flash this using Odin to get the phone back. http://forum.xda-developers.com/showthread.php?p=53353625
Then use philz 6.07.09 and not twrp. That's where the problem started.
Thanks
jrebo said:
Flash this using Odin to get the phone back. http://forum.xda-developers.com/showthread.php?p=53353625
Then use philz 6.07.09 and not twrp. That's where the problem started.
Click to expand...
Click to collapse
Thanks so much my phone is now running stock touchwiz 4.4.2 but I would like to know if you have any suggestions for roms?
ace362 said:
Thanks so much my phone is now running stock touchwiz 4.4.2 but I would like to know if you have any suggestions for roms?
Click to expand...
Click to collapse
It's really personal preference so you have to flash everything that's out there to see which one you like. I'm a flash a holic so I tend to flash anything new and will change between touchwiz and non-tw ROMs based on my mood that day. Enjoy!
bootloader?
Just one more thing I read somewhere that the Verizon note 2 was the only note 2 with a locked boot loader .If this is not true could you tell me how to unlocked it because I feel like I looked everywhere.
I've been rooting phones for a few years now (my evo and my Note 2.) I had my note 2 rooted for about a year and while having performance issues with Sprint (hate sprint) I flashed back to stock and updated everything, including the firmware. Ugh, I updated the firmware to the new knox firmware. Not knowing I was up a creek, I reflashed my phone with the tools I already had and had already used and triggered knox and cant get a recovery to stick. As far as I can tell the phone is still stock with knox tripped and I cant get any farther. I've spent a few hours reading now and I cant seem to find a way to either reverse knox or root the phone with knox tripped. I tried the cf auto root in the origional development section and couldn't figure it out.
Anybody got any advice, or a link to a thread started post knox so it talks about how to deal with it?
koker93 said:
I've been rooting phones for a few years now (my evo and my Note 2.) I had my note 2 rooted for about a year and while having performance issues with Sprint (hate sprint) I flashed back to stock and updated everything, including the firmware. Ugh, I updated the firmware to the new knox firmware. Not knowing I was up a creek, I reflashed my phone with the tools I already had and had already used and triggered knox and cant get a recovery to stick. As far as I can tell the phone is still stock with knox tripped and I cant get any farther. I've spent a few hours reading now and I cant seem to find a way to either reverse knox or root the phone with knox tripped. I tried the cf auto root in the origional development section and couldn't figure it out.
Anybody got any advice, or a link to a thread started post knox so it talks about how to deal with it?
Click to expand...
Click to collapse
You shouldn't be up a creek. What recovery did you flash? Try the latest Philz for note2. Unchecked auto-reboot in Odin before flashing it, and when it's done pull the battery then put the battery back in and do the power button/home button/volume up to get into recovery...
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
g_money said:
You shouldn't be up a creek. What recovery did you flash? Try the latest Philz for note2. Unchecked auto-reboot in Odin before flashing it, and when it's done pull the battery then put the battery back in and do the power button/home button/volume up to get into recovery...
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
I've been using the unified android toolkit. It seemed to work flawlessly before knox. Now it just stalls. Odin installs the custom recovery, the phone reboots, and goes into the stock android recovery. So I unchecked the auto reboot option, flashed CWM, and while looking nervously at the do not power down device screen, pulled the battery. It booted into CWM fine, flashed Paranoid Android and gapps fine, and rebooted into the new ROM just fine.
Not really sure why I was having problems, or why the pull the battery step is necessary, but it seems to have worked. I did not flash any SU files. Is that necessary?
I would download 1 of the root checker apps, or just install an app that requires root.
Usually (though I can verify not always. Lol) you have to reboot directly into download mode to finish the install of the custom recovery. If you let your phone reboot, stock recovery will over-write the custom recovery that you're trying to install...
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
I ran a root checker and it says I do not have root access. But the phone is running paranoid...so what am I missing here? I thought I needed root access to install the recovery and install a ROM. Seems I do not. Should I care about the lack of root access? Because all I really wanted was to replace the ROM, and that seems to have worked.
koker93 said:
I ran a root checker and it says I do not have root access. But the phone is running paranoid...so what am I missing here? I thought I needed root access to install the recovery and install a ROM. Seems I do not. Should I care about the lack of root access? Because all I really wanted was to replace the ROM, and that seems to have worked.
Click to expand...
Click to collapse
PA Roms work funny with root access on my device also. Just download and flash the latest SuperSU zip. If you already have it installed wipe the data first.
Sent from my SPH-L900 using XDA Free mobile app
Hi everyone I hope this is not a repetition of some old thread (I tried but couldn't find though).
I was using my note 2 (T889) on stock 4.3 which i previously flashed via odine. A couple of days ago i came by this good looking kitkat based rom ( eZKAT v2.0 ) and went on to try it. the rom flashed flawlessly and after flashing my modem i got the signals as well but the wifi was not working. tried using dr. ketans wifi patch but didnt get the wifi to working. Anyhow, I decided to go back to 4.3 via odine. The odine flashing completed successfully but i got stuck on T-mobiles boot screen for hours.
Is there anything called "you cant go back to 4.3 from 4.4.2"? If yes, then whats the way around? I really need to go back to the stock.
Thanks.
zetrixNoob said:
Hi everyone I hope this is not a repetition of some old thread (I tried but couldn't find though).
I was using my note 2 (T889) on stock 4.3 which i previously flashed via odine. A couple of days ago i came by this good looking kitkat based rom ( eZKAT v2.0 ) and went on to try it. the rom flashed flawlessly and after flashing my modem i got the signals as well but the wifi was not working. tried using dr. ketans wifi patch but didnt get the wifi to working. Anyhow, I decided to go back to 4.3 via odine. The odine flashing completed successfully but i got stuck on T-mobiles boot screen for hours.
Is there anything called "you cant go back to 4.3 from 4.4.2"? If yes, then whats the way around? I really need to go back to the stock.
Thanks.
Click to expand...
Click to collapse
I had this problem on my Note also. Downgrading versions of Android requires a data wipe. You will need to reflash your 4.4 ROM then backup your data if you want. Save your backup to your computer then install the 4.3 image.
Sent from my Nexus 7
EverDawn4 said:
I had this problem on my Note also. Downgrading versions of Android requires a data wipe. You will need to reflash your 4.4 ROM then backup your data if you want. Save your backup to your computer then install the 4.3 image.
Sent from my Nexus 7
Click to expand...
Click to collapse
I already tried that but still the booting stuck on the t-mobile logo. I read somewhere that locked bootloader don't let you downgrade to previous version. Is this true?
In that case. Try finding a 4.3 rom that's close to stock.
Sent from my Nexus 7
The locked bootloader is always in stock firmwares i.e 4.3 for the Note 2 but not in custom roms meaning u can even install Lollipop custom on it & downgrade smoothly, i have done that many times. The problem is 4.3 stock firmware has locked bootloader hence downgrading still keeps u in 4.3 bootloader even if u remove all the KNOX files.
Stuck trying to downgrade from custom 5.1.1 to stock 4.3
Hi, i have a problem like this, upgrade to a custom 5.1.1 and then sell the phone, the new owner wants to have it stock, i try to downgrade to 4.3 but i cant, in odin i set the phone to flash it but seems like it doesn`t recognize the phone and i dont know why, so, i decided to try in recovery mode installing from the sd card but the sistem abort, so, i don`t know what to do, i`ll appreciates any help, sorry for my english, i do my best. (i have root access before upgrated to 5.1.1).