Develop Bugs

[Q] update of stock rom led to recovery failure

Hi,
I just got my Galaxy S III and decided to root it. I had done it before. I made a mistake and it wouldn't reboot, so, I had to put the stock rom on the device again. I found the stock rom, which was a 4.0.4 version and flashed it with no problem. But, then, the automatic update installed the 4.1.1 version. Here is when the problem starts: after installation, when I try to go into the recovery mode to clear the cache, the android is dead with a read triangle above it. I don't know what to do since I want to flash a custom rom.
Oh, a small detail that might be important. The stock rom is flashed using ODIN, but the reboot process is so lengthy, I have to remove the battery and then clear the cache before it fully reboots. At this stage (still 4.0.4) there is no problem with recovery mode and everything is fine. It is only after the update to 4.1.1 that the problem starts.
Your helps are much appreciated.:angel:

rezaasl2000 said:
Hi,
I just got my Galaxy S III and decided to root it. I had done it before. I made a mistake and it wouldn't reboot, so, I had to put the stock rom on the device again. I found the stock rom, which was a 4.0.4 version and flashed it with no problem. But, then, the automatic update installed the 4.1.1 version. Here is when the problem starts: after installation, when I try to go into the recovery mode to clear the cache, the android is dead with a read triangle above it. I don't know what to do since I want to flash a custom rom.
Oh, a small detail that might be important. The stock rom is flashed using ODIN, but the reboot process is so lengthy, I have to remove the battery and then clear the cache before it fully reboots. At this stage (still 4.0.4) there is no problem with recovery mode and everything is fine. It is only after the update to 4.1.1 that the problem starts.
Your helps are much appreciated.:angel:
Click to expand...
Click to collapse
So you can esily flash 4.0.4 with no hiccup but then you get the update (kies I assume) and it fails ?
Do you want to be rooted ?
if not just flash the stock 4.1.1 from Sammobile in Odin and update that way to avoid that Kies garbage

hednik said:
So you can esily flash 4.0.4 with no hiccup but then you get the update (kies I assume) and it fails ?
Do you want to be rooted ?
if not just flash the stock 4.1.1 from Sammobile in Odin and update that way to avoid that Kies garbage
Click to expand...
Click to collapse
Thanks for the reply. I do want to be rooted. Mine is an i747. Can you attach the link so I don't download the wrong one?

rezaasl2000 said:
Thanks for the reply. I do want to be rooted. Mine is an i747. Can you attach the link so I don't download the wrong one?
Click to expand...
Click to collapse
Find your carrier and flash one of these in Odin as they are pre-rooted.
http://forum.xda-developers.com/showthread.php?t=1739426

hednik said:
Find your carrier and flash one of these in Odin as they are pre-rooted.
http://forum.xda-developers.com/showthread.php?t=1739426
Click to expand...
Click to collapse
Thank you so much for the reply. After purchasing my g3 from AT&T, I used the same link you just sent me to flash the device. But it didn't work even though I changed the USB port. It installs SuperSU, but the recovery fails. I will try it one more time before and report back to you.
thanks again.

rezaasl2000 said:
Thank you so much for the reply. After purchasing my g3 from AT&T, I used the same link you just sent me to flash the device. But it didn't work even though I changed the USB port. It installs SuperSU, but the recovery fails. I will try it one more time before and report back to you.
thanks again.
Click to expand...
Click to collapse
It failed again (dead android with a red triangle above it). I have checked the ODIN version, whether the md5 file was downloaded correctly. I'm very frustrated.

rezaasl2000 said:
It failed again (dead android with a red triangle above it). I have checked the ODIN version, whether the md5 file was downloaded correctly. I'm very frustrated.
Click to expand...
Click to collapse
So you can't flash anything 4.1.1 or 4.1.2 ? That's odd that only 4.0.4 works. Does it fail with Kies too ?
What about just rooting using CF-auto root or casual and then flashing a rom ?

hednik said:
So you can't flash anything 4.1.1 or 4.1.2 ? That's odd that only 4.0.4 works. Does it fail with Kies too ?
What about just rooting using CF-auto root or casual and then flashing a rom ?
Click to expand...
Click to collapse
Okay, so, this method didn't work either. I went back to the link you sent me with the pre-rooted version and flashed it. Now, it has the same problem (dead android with red triangle), but RootChecker says that I'm rooted. I don't know what difference that makes.
Any thoughts?

rezaasl2000 said:
Okay, so, this method didn't work either. I went back to the link you sent me with the pre-rooted version and flashed it. Now, it has the same problem (dead android with red triangle), but RootChecker says that I'm rooted. I don't know what difference that makes.
Any thoughts?
Click to expand...
Click to collapse
So cf auto root worked but you can't flash ? You need to install a recovery. Can you flash a custom recovery in Odin or mobile Odin ?
Sent from my SGH-I747 using xda premium

hednik said:
So cf auto root worked but you can't flash ? You need to install a recovery. Can you flash a custom recovery in Odin or mobile Odin ?
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
So, I finally figured it out. I used the samsung galaxy s3 toolkit to install the stock firmware and then I updated it on the phone. Next, I went back to the toolkit and installed the most recent version of CWM on it and everything just worked beautifully. I have LiquidSmooth installed and it works just great.
thank you for the help hendik.
:good:

[Q] Odin flash failure !!!

*Upgraded to official 4.3
*Flashed modified stock MK2 by jovy23 http://forum.xda-developers.com/showthread.php?t=2545711
*Tried flashing stock 4.2.2 (MDL) via Odin( tried v1.85, 3.09,3.07, just to make sure Odin is not the reason of failure)
*Flashing fails(says Aunthentication failed )
Can anyone help me fix this..please..

re: odin flash
Shafayat said:
*Upgraded to official 4.3
*Flashed modified stock MK2 by jovy23 http://forum.xda-developers.com/showthread.php?t=2545711
*Tried flashing stock 4.2.2 (MDL) via Odin( tried v1.85, 3.09,3.07, just to make sure Odin is not the reason of failure)
*Flashing fails(says Aunthentication failed )
Can anyone help me fix this..please..
Click to expand...
Click to collapse
before you odin flash, go into recovery and do a "factory reset"
and then odin flash stock mdl and you should be good to go.
Good luck!

Are you flashing roms with Odin ? You should use TWRP or CWM to flash roms, not Odin.

dklue said:
Are you flashing roms with Odin ? You should use TWRP or CWM to flash roms, not Odin.
Click to expand...
Click to collapse
No, i tried flashing official MDL firmware , i flashed that modified MK2 by jovy23 via TWRP.

Misterjunky said:
before you odin flash, go into recovery and do a "factory reset"
and then odin flash stock mdl and you should be good to go.
Good luck!
Click to expand...
Click to collapse
tried that too..but no luck

Is the colored modem line showing up in odin, correct drivers installed, maybe bad download, check md5, are you clicking the phone button in odin ? Are you
going into download mode on phone, then connect cable ?

re: flashing roms
dklue said:
Are you flashing roms with Odin ? You should use TWRP or CWM to flash roms, not Odin.
Click to expand...
Click to collapse
Your post makes me laugh. LOL
Have a happy thanksgiving!

dklue said:
Is the colored modem line showing up in odin, correct drivers installed, maybe bad download, check md5, are you clicking the phone button in odin ? Are you
going into download mode on phone, then connect cable ?
Click to expand...
Click to collapse
yes...i even flashed twrp recovery after firmware flash failure.. "kernel is not seandroid enforcing, set warranty bit : kernel" shows up at every boot up on top of the screen.

Are you on the official 4.3? With the new bootloader? You can't Odin 4.2.2 once you have the new bootloader, only Odin mk2. If you are still on mdl bootloader you should be able to
Sent from my SGH-M919 using xda app-developers app

tylerholbrook said:
Are you on the official 4.3? With the new bootloader? You can't Odin 4.2.2 once you have the new bootloader, only Odin mk2. If you are still on mdl bootloader you should be able to
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
yes, i m on new bootloader...isnt there any way around ?

I flashed with Odin and i used the one before 1.85...was it 1.83? I'm not sure, but mine failed on 1.85. Try pervious ones and make sure it's in the right pda.
Sent from my SGH-M919 using Tapatalk

Well I guess that's the problem when people have problems and don't fully explain it, just trying to help, at this point he or she probably knows more
then me....... lol

Shafayat said:
yes, i m on new bootloader...isnt there any way around ?
Click to expand...
Click to collapse
At the moment no. And I have the slightest feeling that when you did that, you tripped your Knox flash counter by trying to Odin MDL firmware while on the newest. Now since you most likely tripped it, you won't be able to reset the counter because there is no way yet and that has permanently voided your warranty for now. Once you've updated via ota or kies or Odin to 4.3 you're stuck.
Sent from my GT-I9505G using XDA Premium 4 mobile app

Shafayat said:
*Upgraded to official 4.3
*Flashed modified stock MK2 by jovy23 http://forum.xda-developers.com/showthread.php?t=2545711
*Tried flashing stock 4.2.2 (MDL) via Odin( tried v1.85, 3.09,3.07, just to make sure Odin is not the reason of failure)
*Flashing fails(says Aunthentication failed )
Can anyone help me fix this..please..
Click to expand...
Click to collapse
Its because when you flash a fireware it communicates with the new boot loader to check if its the same version or newer.
If oyu pull the tars apart and retar just the system/data/and image files it might flash.

your help urgent please

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

[Q] Update Baseband - From M919Uvufnk2 To M919Uvufoh3

Hi,
Am on CM12.1, T-Mobile Galaxy S4 SGH-M919, Rooted, Android 5.1.1
How i can update the Baseband - From M919Uvufnk2 To M919Uvufoh3 using TWRP?

You can't. You have to use Odin.

HampTheToker said:
You can't. You have to use Odin.
Click to expand...
Click to collapse
Ok, i can use ODIN. But from where i can find the baseband for rooted custom ROM (CM) SGH-M919?

My method...Backup your current rom. Odin the oh3 stock release, odin cf root, odin twrp, backup the new stock rom, restore prior backup.
Sent from my SM-T320 using XDA Premium HD app

mgp53 said:
My method...Backup your current rom. Odin the oh3 stock release, odin cf root, odin twrp, backup the new stock rom, restore prior backup.
Sent from my SM-T320 using XDA Premium HD app
Click to expand...
Click to collapse
Hmmm...thats what i am actually thinking as of now....but looking for easy alternative like if we get the flashable zip or something of this baseband i can just flash it without taking backup of ROM and reinstall the ROM etc.....
But am looking for a site where i can download these basebands....

i take it you are trying to update the modem/baseband ihere you go. Must be done thru odin.
http://forum.xda-developers.com/galaxy-s4-tmobile/general/foh3-modem-bin-mdl-bootloader-t3191094
IMPORTANT: DO NOT CHANGE THE BOOTLOADER unless u KNOW EXACLY what you are doing...changing bootloader to the wrong bootloader will brick your device and some modem packages conatin bootloader. so make sure that you are getting a ODIN file that only contains the modems and no bootloader!
if you wish to properly update the bootlaoder and baseband properly ....just ODIN the OFFICIAL samsung release for your device and then re-root and reinstall recovery and then your rom.

XeoNoX said:
i take it you are trying to update the modem/baseband ihere you go. Must be done thru odin.
http://forum.xda-developers.com/galaxy-s4-tmobile/general/foh3-modem-bin-mdl-bootloader-t3191094
IMPORTANT: DO NOT CHANGE THE BOOTLOADER unless u KNOW EXACLY what you are doing...changing bootloader to the wrong bootloader will brick your device and some modem packages conatin bootloader. so make sure that you are getting a ODIN file that only contains the modems and no bootloader!
if you wish to properly update the bootlaoder and baseband properly ....just ODIN the OFFICIAL samsung release for your device and then re-root and reinstall recovery and then your rom.
Click to expand...
Click to collapse
Perfect....I will use this one....

And on S4 you don't even need to root before flashing TWRP and your ROM of choice. Just double flash the stock release with ODIN, let it boot up and make sure all is well, go into Camera to let it see if it needs a firmware update (happens automatically first time you run stock camera app), and when satisfied your phone is good, go into download mode, take TWRP + whatever else you want.

Flashing Stock ROM Question?

Hi guys.
I'm wondering, if I flash stock ROM to my note via Odin, do I need to re-root ?
And only recovery is back to stock one right?
Thanks!

Yes you will need to re-root. But it's really very easy. Just flash TWRP after stock ROM and then install SuperSU.zip.

Depending on the phone model and stock ROM version, you may be able to root by using cfautoroot and Odin.

d4rk_m4n said:
Hi guys.
I'm wondering, if I flash stock ROM to my note via Odin, do I need to re-root ?
And only recovery is back to stock one right?
Thanks!
Click to expand...
Click to collapse
there is another Solution to flash stock firmware ,and without PC !!
you can use FlashFire .apk
you can keep root access & inject SuperSu while flashing & manage recovery... and,.....
and the most important thing it is chainfire made

Can the stock rom be flashed with the TWRP, like an AOSP rom (img file) ?

Giuliano69 said:
Can the stock rom be flashed with the TWRP, like an AOSP rom (img file) ?
Click to expand...
Click to collapse
No. But you can use eclipse (flash via TWRP) if you want the feeling of stock ROM.

Sorry guys guys for late reply.
I was using Kingroot before but I cant run flux or cf lumen using with its root access.
I tried using the CF autoroot, flash using odin, its all good no error and "Passed".
After rebooted, I try to run the SU and get this error:
"there is no su binary installed and supersu cannot install it. this is a problem"
I then installed latest TWRP using odin and installed latest SU using recovery but the error still persist.
What should I do? Thanks!

xcorona said:
there is another Solution to flash stock firmware ,and without PC !!
you can use FlashFire .apk
you can keep root access & inject SuperSu while flashing & manage recovery... and,.....
and the most important thing it is chainfire made
Click to expand...
Click to collapse
I will keep this one in mind next time. Thanks!

audit13 said:
Depending on the phone model and stock ROM version, you may be able to root by using cfautoroot and Odin.
Click to expand...
Click to collapse
Its n7100 with 4.4.2
N7100XXUFNI4 - October 2014

I have always had success with cfautoroot.
Just double-check to make sure you used the correct version of cfautoroot, Odin 3.07, and the original Samsung USB cable.
Did you flash a stock ROM after kingroot failed? If not, this may be why cfautoroot didn't work.

audit13 said:
I have always had success with cfautoroot.
Just double-check to make sure you used the correct version of cfautoroot, Odin 3.07, and the original Samsung USB cable.
Did you flash a stock ROM after kingroot failed? If not, this may be why cfautoroot didn't work.
Click to expand...
Click to collapse
Do I need to use the Odin 3.07? Cant use the latest one?
Nope. I flash stock ROM and trying to find easy way to root. I tried Kingroot.
Now, I uninstall Kingroot and try to root like good ol day. but it didnt work.. :crying:

You don't have to just Odin 3.07 but that's what I always use.
Flash back to stock, then use cfautoroot.

audit13 said:
You don't have to just Odin 3.07 but that's what I always use.
Flash back to stock, then use cfautoroot.
Click to expand...
Click to collapse
Tried with 3.07. Same issues.
Em, I will stick with Kingroot if I need to flash back I guess.
Is there any other way?
I'm using this one tho:
CF-Auto-Root-t03g-t03gxx-gtn7100.tar.md5

You tried 3.07 to flash stock or cfautoroot? I meant use 3.07 to flash stock, then use 3.07 to flash cfautoroot.

audit13 said:
You tried 3.07 to flash stock or cfautoroot? I meant use 3.07 to flash stock, then use 3.07 to flash cfautoroot.
Click to expand...
Click to collapse
Ohh.. I just try to flash the cfautoroot with 3.07.

audit13 said:
You don't have to just Odin 3.07 but that's what I always use.
Flash back to stock, then use cfautoroot.
Click to expand...
Click to collapse
I reflash my note to stock and flash cfautoroot after. It worked perfectly fine now.
Kingroot was the real culprit.
Thanks!

That's great:good: