I Mean I've read I've tried it's all second nature to me flashing twrp isn't hard ...Done it a million times but I just took the 4.2.2 ota and rooted with cf auto root which gets a boot loop I learned the hard way unless u use the cf auto for 9005 international .
I can't get twrp to boot into recovery with volume up home and power
let alone don't even know if it installed at all every time I try to install it with Odin It flashes but I get boot loop I tried with flashify boot loop tried with goo manager Boot loop
Tried version 2.6.3.9 tried 2.6.3.8
What's the trick here with twrp and 4.2.2 ota .Doesn't work and Bootloop issues when manually booting into twrp
Sea android enforcing boot loop
Nothing more nothing less
I even had to reroot with cf auto just to get out the loop
Sent from my SM-N900T using xda app-developers app
edit 4.4.2 Not 4.2.2
I Meant to say 4.4.2 ota
Twrp doesn't install or maybe it is it says installed with Odin and flashify but it boot loops when trying to boot into it manually stuck on sea android enforcing ?
Are we boot loader locked with this ota or what am I doing wrong
Twrp site states all versions above 2.6.3.0 are working with 4.4.2
lojak29 said:
I Meant to say 4.4.2 ota
Twrp doesn't install or maybe it is it says installed with Odin and flashify but it boot loops when trying to boot into it manually stuck on sea android enforcing ?
Are we boot loader locked with this ota or what am I doing wrong
Twrp site states all versions above 2.6.3.0 are working with 4.4.2
Click to expand...
Click to collapse
I don't believe all twrp versions work with 4.4.2. Big Biff just made a beta version yesterday for the KitKat update. Flash with Odin and it should be all good. Here is his post:
For you guys who have updated to the Tmobile 4.4 Kitkat update and bootloader: http://techerrata.com/bigbiff/hltetmo-recovery.img.tar
It is sort of a twrp2.7 beta until the official builds get released but only for 4.4. I will be building for 4.3 bootloaders this weekend. Don't pay attention to the version number in TWRP, just please let me know if it works.
Just compiled with n900t kk source from samsung and compiled dtb. Please test adb shell too.
Well I tested it myself. adb shell works, twrp backup works, restore works. version says 2.6.3.2 if anyone cares, but consider it TWRP 2.7 beta.
Sent from my SM-N900T using Tapatalk
If this is a question then it should be in Q&A and not in general. Have you searched for your issue? Read here: http://forum.xda-developers.com/showthread.php?p=50841774
Sent from my SM-N9005 using Tapatalk
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.
today i rooted, flashed the most recent version of twrp on a stock n7100.
I did all this via Skipsoft unified android toolkit and intended to flash DItto note 4 on the n7100.
Ive done this before since i own another Note2 with Cyanogenmod X currently installed, coming from DN3.
on that phone i have current version of twrp and bootloader OD4.
I flashed the new OD4 bootloader on this newly rooted phone but i have been stuck at the samsung screen since then.
ODIN completed the flash successfully with no errors so i do not understand why i am experiencing this problem.
I have a TWRP backup though.
Can anyone help me sort this out.
THe device still boots into download mode but not into recovery.
Thanks
santet said:
today i rooted, flashed the most recent version of twrp on a stock n7100.
I did all this via Skipsoft unified android toolkit and intended to flash DItto note 4 on the n7100.
Ive done this before since i own another Note2 with Cyanogenmod X currently installed, coming from DN3.
on that phone i have current version of twrp and bootloader OD4.
I flashed the new OD4 bootloader on this newly rooted phone but i have been stuck at the samsung screen since then.
ODIN completed the flash successfully with no errors so i do not understand why i am experiencing this problem.
I have a TWRP backup though.
Can anyone help me sort this out.
THe device still boots into download mode but not into recovery.
Thanks
Click to expand...
Click to collapse
flash Philz recovery and see what happens
Will a full stock reflash fix this.
I need an urgent fix.
Please
Sent from my GT-N7100 using XDA Free mobile app
i've samsung note 4 sm-n910p
was working fine ,tried to install firmware but got bricked
i've tried downloading many firmwares all fail
need someone to send the right firmware for my device
attached the error i get
thanks
And here we go again...... What version software was installed before trying to update? Were you rooted?
zjor2000 said:
i've samsung note 4 sm-n910p
was working fine ,tried to install firmware but got bricked
i've tried downloading many firmwares all fail
thanks
Click to expand...
Click to collapse
Try Flashing CF Auto Root through Odin and reboot your phone and report back please.
w7excursion said:
And here we go again...... What version software was installed before trying to update? Were you rooted?
Click to expand...
Click to collapse
Lol, ikr....
done so ,,but nothing keeps restarting ,,,,loop
it needs a new firmware .. OS
zjor2000 said:
done so ,,but nothing keeps restarting ,,,,loop
it needs a new firmware .. OS
Click to expand...
Click to collapse
Were you on the OG5 OTA and tried to root your phone?
rooted thru odin
now i can't get to OS ,just show samsung sign and loops
Flash whatever firmware u was on in odin
zjor2000 said:
rooted thru odin
now i can't get to OS ,just show samsung sign and loops
Click to expand...
Click to collapse
In Odin, Flash the TWRP recovery
Download notarized,cm12 or sacs and put it on your SD card, and reboot to recovery and install your choice of Rom downloaded.
Reboot and relax.
tried to do thru sd card ,but i get :
dm-verity verification failed
can i just go back to 5.1 lollipop with an official stock rom via odin ?
zjor2000 said:
can i just go back to 5.1 lollipop with an official stock rom via odin ?
Click to expand...
Click to collapse
There is no official rom
any firmware can get me back to lollipop with odin !!!
zjor2000 said:
any firmware can get me back to lollipop with odin !!!
Click to expand...
Click to collapse
Here's what I understand as far as recovering with Odin by build:
All these builds NIE, NK2 (KitKat) and first Lollipop (OB7) were downgradeable; you were free to flash in Odin within these builds. Or KIES but not downgrade.
OE1 didn't have a tar, it also locked out the older ones but was compatible with OF5 to flash Odin or KIES to upgrade. Can only go back to OE1 with nandroid backup from OF5. OE1 introduced reactivation lock to prevent flashing over user locked phone as well as preventing the downgrade to escape the feature. Seems dine could recover from a bit loop by flashing CF Auto Root in Odin.
OF5 was released with a supporting tar eventually but it's the same story as OE1. But I'm not sure if CF Auto Root worked to recover boot when looped.
OG5 locks it further. If you don't have a nandroid, recovering from boot loop options may include flashing CWM recovery or a compatible flash that takes you away from OG5 almost entirely. Sacs, Notarized, and CM12 are reportedly working. Reportedly, can't go back to OF5 with Odin and not sure about nandroid, maybe not.
Depending on certain exceptions unclear, Odin and KIES have been reported to work together, flashing stock OB7 ROM, parts of stock tar with Odin with a flash result that won't boot but connecting KIES in recovery and using the emergency recovery method. If KIES doesn't see your phone on recovery, you may try this fix on your Windows PC:
http://forum.xda-developers.com/showpost.php?p=34864154&postcount=14
I'll add this too: flashing L Speed Mod may fix adb with ADB Insecure in booted mode; ADB Insecure wouldn't be needed in recovery anyway so it works without it. I can report this does work for me with the above MTP fix on OB7.
Sent from my SM-N910P using Tapatalk
samep said:
Here's what I understand as far as recovering with Odin by build:
All these builds NIE, NK2 (KitKat) and first Lollipop (OB7) were downgradeable; you were free to flash in Odin within these builds. Or KIES but not downgrade.
OE1 didn't have a tar, it also locked out the older ones but was compatible with OF5 to flash Odin or KIES to upgrade. Can only go back to OE1 with nandroid backup from OF5. OE1 introduced reactivation lock to prevent flashing over user locked phone as well as preventing the downgrade to escape the feature. Seems dine could recover from a bit loop by flashing CF Auto Root in Odin.
OF5 was released with a supporting tar eventually but it's the same story as OE1. But I'm not sure if CF Auto Root worked to recover boot when looped.
OF5 locks it further. If you don't have a nandroid, recovering from boot loop options may include flashing CWM recovery or a compatible flash that takes you away from OG5 almost entirely. Sacs, Notarized, and CM12 are reportedly working. Reportedly, can't go back to OF5 with Odin and not sure about nandroid, maybe not.
Depending on certain exceptions unclear, Odin and KIES have been reported to work together, flashing parts of stock tar with Odin and connecting KIES using the emergency recovery method. If KIES doesn't see your phone on recovery, you may try this fix on your Windows PC:
http://forum.xda-developers.com/showpost.php?p=34864154&postcount=14
I'll add this too: flashing L Speed Mod may fix adb with ADB Insecure in booted mode; ADB Insecure wouldn't be needed in recovery anyway so it works without it. I can report this does work for me with the above MTP fix on OB7.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Was i incorrect in my method of getting him back on his feet? I should suggest CWM instead of TWRP? Now im confused.
The last thing i want to do is tell someone the wrong procedure, only causing more frustration. I thought i read 'Twrp, Install and Viola!' from many users in the other thread.
xxSTARBUCKSxx said:
Was i incorrect in my method of getting him back on his feet? I should suggest CWM instead of TWRP? Now im confused.
The last thing i want to do is tell someone the wrong procedure, only causing more frustration. I thought i read 'Twrp, Install and Viola!' from many users in the other thread.
Click to expand...
Click to collapse
I think your suggestion is consistent with what we're learning as you gave it. It seems to be evolving with trial and error. The CWM suggestion came from a single experience shared.
http://forum.xda-developers.com/showthread.php?p=62196189
The OP was asking for another solution and it wasn't clear where he started from to correctly recovery so tried to answer including all the options for each build. I added some things that may help depending on his situation.
Sent from my SM-N910P using Tapatalk
i managed to find the right fW ,,,if anyone has same problem u can do it your self
https://1fichier.com/dir/IOjXgJUa
and download this file : N910PVPU3BOF5_SPT3BOF5_SPR_Sprint_USA_5.0.1.zip
I'm using a Verizon Note 4 (retail) with a emmc 15 bootloader is unlocked but when i flash flash chainfire SU, USE KINGroot or attempt cf autoroot in TWRP 3.0.2 5.0.1 OR 5.1.1 stock ROM OR flash stock ROM with aboot removed and Recovery removed IF im lucky enough to get one of the above exploits to work, each time I try to flash root phone reboots and says unfortunately messages has stopped working... wtf
What ROM are you flashing? And what is your bootloader and baseband?
SU has been nagging me to update for a couple of weeks so I finally did it. Now my phone gets stuck at the Verizon logo.
rooted s-off
stock lollipop 5.0.1
TWRP 3.0.0.0
I've updated SU a few times in the past without any problems. Can anyone tell me what version I can try to downgrade to? I don't even remember what it was on before or what version the new update was. Should TWRP be updated to another version? Need to get my phone working ASAP.
Thanks
Got it sorted out. Flashed SuperSU v2.79 and it's booting again. SuperSU v2.82 must not be compatible with TWRP 3.0.0.0. Not sure if the latest TWRP is compatible with stock 5.0.1 or not and I don't feel like finding out. :/