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
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.
I am not new to rooting and flashing rom however, I switched from my rooted GS3 running CM11 to the Note 2. I flashed the stock firmware (root66) and made the mistake of running the OTA 4.1.2 update which caused my note to be soft bricked. The phone boots to the samsung logo and freezes there. I flashed several stock firmware using odin that pass but when my phone reboots it freezes at the samsung logo. I can not access recovery mode, only downloading mode. I know its a way to fix this I'm just not sure how. Any suggestions?
MaddenMS6 said:
I am not new to rooting and flashing rom however, I switched from my rooted GS3 running CM11 to the Note 2. I flashed the stock firmware (root66) and made the mistake of running the OTA 4.1.2 update which caused my note to be soft bricked. The phone boots to the samsung logo and freezes there. I flashed several stock firmware using odin that pass but when my phone reboots it freezes at the samsung logo. I can not access recovery mode, only downloading mode. I know its a way to fix this I'm just not sure how. Any suggestions?
Click to expand...
Click to collapse
Easy peasy, flash philz v5.00.5 (not the latest) through odin then u should be able to access recovery, from recovery flash a custom ROM so u can get unstuck, then when everything is fine, flash a stock rom from sammobile and hopefully it should work.
With Regards,
Overdub
Smack the thanks if I helped.
Sent from my GT-N7100 using Tapatalk
So, I'm not a complete noob to flashing roms/rooting devices. I flashed cm 11 to my s3, and decided I wanted to go back to stock via Odin. For some reason when I tried to turn on my device it was still showing the cm 11 splash screen and wouldn't proceed any further. It isn't technically bricked. I guess this would be classified as a boot loop to the nth degree. I tired to boot in recovery mode and wipe the cache partition and all user data to the same cm 11 robot taunting me. When I tried the process (flashing stock vi Odin) again to possibly fix whatever might have been a miss, I got the error message on the download screen "secure check fail: sb12." On the download mode screen it also says I am running the official system rom. I don't know what steps I need to take from here to get my phone to actually boot via the stock rom. Has anybody else had this issue or similar? Any help in resolving this would be greatly appreciated.
Is your phone a i747? If you are you running a stock 4.3 bootloader on your i747, you can't use Odin to flash back to stock unless the ROM was specifically designed to be flashed in Odin.
What is shown on the screen in download mode?
audit13 said:
Is your phone a i747? If you are you running a stock 4.3 bootloader on your i747, you can't use Odin to flash back to stock unless the ROM was specifically designed to be flashed in Odin.
What is shown on the screen in download mode?
Click to expand...
Click to collapse
I was under the impression the rom I was attempting to flash was indeed intended for Odin. It is the SGH-I747.
The download screen states,
Product Name: SGH-I747
Custom Binary: Custom
System Status: Official
Qualcom Secure Boot: Enable
Warranty Bit: 1
Bootloader AP SWERV: 2
Here is an added bit of fun, in the midst of the process I accidentally checked "Nand erase all," in Odin at one point.
Based on the information provided, your phone is running a stock ATT 4.3 bootloader. The CM11 splash screen is still showing up because the flash did not actually happen. You're lucky your phone was not bricked in the process of using Odin. I recommend not using Odin to flash a ROM that tries to alter the bootloader.
I recommend flashing a custom recovery such as Philz Touch in Odin and flashing a different KK ROM such as Valudis.
If you want to get back to stock, try this: http://forum.xda-developers.com/showthread.php?t=2658486
audit13 said:
Based on the information provided, your phone is running a stock ATT 4.3 bootloader. The CM11 splash screen is still showing up because the flash did not actually happen. You're lucky your phone was not bricked in the process of using Odin. I recommend not using Odin to flash a ROM that tries to alter the bootloader.
I recommend flashing a custom recovery such as Philz Touch in Odin and flashing a different KK ROM such as Valudis.
If you want to get back to stock, try this: http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
My next question would be how can I move the zip files I download to the internal storage of my phone to flash them through Philz Touch?
Have you tried using kies?
http://forum.xda-developers.com/showthread.php?t=2088809
sjthuss said:
Have you tried using kies?
http://forum.xda-developers.com/showthread.php?t=2088809
Click to expand...
Click to collapse
I did. It said the the device couldn't be updated, or something to that effect.
Kies will not work without a stock recovery or a rooted phone from my experience.
I would be surprised if kies can restore your phone as ATT never released a full 4.3 stock ROM. ATT only made 4.3 available via an OTA update.
audit13 said:
Kies will not work without a stock recovery or a rooted phone from my experience.
I would be surprised if kies can restore your phone as ATT never released a full 4.3 stock ROM. ATT only made 4.3 available via an OTA update.
Click to expand...
Click to collapse
I don't know about AT&T, but I'm on Telus in Canada and I used kies to revert back to stock 4.3 with CWM recovery and phone rooted, and it worked no problem.
audit13 said:
Based on the information provided, your phone is running a stock ATT 4.3 bootloader. The CM11 splash screen is still showing up because the flash did not actually happen. You're lucky your phone was not bricked in the process of using Odin. I recommend not using Odin to flash a ROM that tries to alter the bootloader.
I recommend flashing a custom recovery such as Philz Touch in Odin and flashing a different KK ROM such as Valudis.
If you want to get back to stock, try this: http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
So, I know there is a "thanks," button but I feel like that would be a little too informal for how much I appreciate your help! I downloaded ADB to move the rom (I went with AOKP because it was the first one that worked) to my phone, flashed it using TWRP and...BAM! We are back in business. Thanks for the direction, I thought I had a nice, new, shiny brick on my hands for about two days.
sjthuss said:
I don't know about AT&T, but I'm on Telus in Canada and I used kies to revert back to stock 4.3 with CWM recovery and phone rooted, and it worked no problem.
Click to expand...
Click to collapse
Canadian carriers use the i747m while att users get the i747.
The Canadian carriers did release a full 4.3 ROM unlike att who did not.
Hello,
I messed up my Note 8 and recently was able to reinstall 4.1.2 stock, I tried connecting to Kies and it doesn't work. I wanted to update to the newest software then root. Since that wasn't working I rooted via Odin then attempted to flash twrp so I could flash a custom rom. Root works but the custom recovery doesn't stick... I tried unticking reboot in odin and the system still reboots into standard recovery.
I tried using the toolkit and its stuck on waiting on debug even though debug is clicked.
Can anyone help me install a custom recovery via odin or another way?
If you have the at&t sgh-i467 version - there is not a custom recovery for it because it has a locked bootlader.
Additionally, the newest 4.4.2 ota update has not been rooted as of yet - so if you must have root, don't install the ota.
The original mf1 rom is rootable, but again there is no customers recovery due to the locked bootloader.
This only applies to the at&t in version...
use Odin
Need help?
Hi everyone, I just upgraded to the SGS4(M919) from the LG G Stylo.
I haven't been a part of an active development community in awhile, coming from the Stylo where there was 0 development for my variant(No Unlock for Bootloader). I haven't developed anything nor really done anything with samsungs since the SDX-Days when the Captivate was popular.
So my question is where the heck do I start?
Model: M919
OS: 4.4.2
BB: M919UVUFNB4
The in Call screen really bothers me and my husband got a s5(the only one they had) that's 1000 time better ascetically.
TIA, Kristi
Also I see that some have bootloader lock. I have a m919 but it is NOT T-mobile My phone is a unbranded factory unlocked. I bought I brand new from aarons
The m919 does not have a locked bootloader.
To confirm the exact model #, boot the phone into download mode.
If it is an sgh-m919. I would run OTA updates until the phone is running a stock 4.4.4 ROM. This will ensure the modem and bootloader are up to date.
Next, I would flash TWRP via Odin. Once TWRP is up and running, select a custom ROM and use TWRP to flash a custom ROM of your choice.
audit13 said:
The m919 does not have a locked bootloader.
TO confirm the exact model #, boot the phone into download mode.
If it is an sgh-m919. I would run OTA updates until the phone is running a stock 4.4.4 ROM. This will ensure the modem and bootloader are up to date.
Next, I wuld flash TWRP via Odin. Once TWRP is up and running, select a custom ROM and use TWRP to flash a custom ROM of your choice.
Click to expand...
Click to collapse
Thank you for the help.
Download mode, sticker, and settings confirms SGH-M919 however it says at 4.4.2 is the latest version
I believe 4.4.4 is the latest: http://www.sammobile.com/firmwares/database/SGH-M919/
audit13 said:
I believe 4.4.4 is the latest: http://www.sammobile.com/firmwares/database/SGH-M919/
Click to expand...
Click to collapse
Will download that and install TWRP. Thanks for the help.
No problem. We're here to help and learn from each other. Let us know how it goes.
audit13 said:
No problem. We're here to help and learn from each other. Let us know how it goes.
Click to expand...
Click to collapse
Are there any recovery images/boot image with sgs5 off line charging screen? I have cm13 and cwm touch recovery but when I flashed cwm charging animation looks like something from a palm pilot from 2002
What is the model # for the s5? I would not recommend using CWM as it has not been updated for a long time. Try TWRP. I believe the charging animation is based on the ROM.
What happened with flashing the s4?
audit13 said:
What is the model # for the s5? I would not recommend using CWM as it has not been updated for a long time. Try TWRP. I believe the charging animation is based on the ROM.
What happened with flashing the s4?
Click to expand...
Click to collapse
I did flash the s4. I have cm13 my husband has the s5(g900m) and his power off charging screen is pretty.
You could try flashing an s5 or Note 4 port to your phone.
audit13 said:
The m919 does not have a locked bootloader.
To confirm the exact model #, boot the phone into download mode.
If it is an sgh-m919. I would run OTA updates until the phone is running a stock 4.4.4 ROM. This will ensure the modem and bootloader are up to date.
Next, I would flash TWRP via Odin. Once TWRP is up and running, select a custom ROM and use TWRP to flash a custom ROM of your choice.
Click to expand...
Click to collapse
Question, is Odin the only way to install TWRP?
I have some down time at work
Odin is not the only way to flash twrp but I find it to be the easiest and most efficient way.
I think other methods require a rooted phone with and some sort of rom manager app.