Develop Bugs

sgh-t999v won't root

Hi,
I've an SGH-T999V, on stock 4.4.2 samsung touchwizz firmware. I'Ve try many things to root it, whit cf-auto-root, gehot exploit, and too whit cyanogen auto-installer, all the things works fine, in sense odin said all was passed. Same thing on the phone, example whit cf-auto-root i see the red android and the line said was in root process. Same thing whit gehot, saisd all is ok. Same thing whit cyanogen do congratulation was installed. When the phone reboot, ALWAYS on the stock firmware, same if i factory reset whit clockwork mod recovery that i've succesfully installed on the phone, too if i do a Know removal whit a tool found on the forum, alway on stock firmware. The phone wan't install any custom room, or rooting, but all the tools used said all was done fine.
Anyone else have idea of how to succefully install cyanogen? Thank very much!

Do you get a successful message when flashing cm with clockwork mod? Try twrp if you haven't

yes clockworkmod said success. I've tried to flash TWRP, odin said success,but when booting recovery, it like have never flash it, so stay whit the old recovery!

Unchecked auto reboot and flash again. When done, unplug and pull battery. Put it back in and boot recovery. When you flash SuperSU it'll stop this from happening.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

stuck on stock nb4 bootloader, unable to flash custom recovery

Trying to figure this out. Browsed forums for the last 24 hours, unable to come up with a way to figure it out. I was running Effortless rom, and older version that I can't remember, but it was on NF6 firmware. I wanted to play around with cm11 so I decided to flash back to stock NF6 then update to NF9 for the VOLTE update just to have it. So I triangled away, wiped then rooted and installed TWRP via ODIN, made a backup, everything went fine. Then I downloaded cm11 and gapps 4.4.4 and put them on my internal sd and went to flash in TWRP but cm11 was giving me errors. I figured it may have been TWRP so i decided to flash CWM but no go. It wouldn't stick. Tried again, no luck. Downloaded ROM Manager and this time I installed CWM through there. Tried rebooting in to recovery and ended up getting stuck in the "recovery booting" bootloop, so I flashed stock NF9(since I was on this firmware now) and tried installing CWM again, no luck. When I tried booting to recovery, it was stock NB4 recovery. I'm thinking that I'm stuck on an old bootloader and the recovery isn't NF9, which is the current stock recovery. I'm thinking that the reason why I'm unable to flash anything in TWRP/unable to install CWM at all is because of the stock recovery and possibly bootloader being NB4 for some reason while my baseband and build are both NF9. Any ideas/help would be appreciated. Thanks guys.

re: custom recovery
pyr0path said:
Trying to figure this out. Browsed forums for the last 24 hours, unable to come up with a way to figure it out. I was running Effortless rom, and older version that I can't remember, but it was on NF6 firmware. I wanted to play around with cm11 so I decided to flash back to stock NF6 then update to NF9 for the VOLTE update just to have it. So I triangled away, wiped then rooted and installed TWRP via ODIN, made a backup, everything went fine. Then I downloaded cm11 and gapps 4.4.4 and put them on my internal sd and went to flash in TWRP but cm11 was giving me errors. I figured it may have been TWRP so i decided to flash CWM but no go. It wouldn't stick. Tried again, no luck. Downloaded ROM Manager and this time I installed CWM through there. Tried rebooting in to recovery and ended up getting stuck in the "recovery booting" bootloop, so I flashed stock NF9(since I was on this firmware now) and tried installing CWM again, no luck. When I tried booting to recovery, it was stock NB4 recovery. I'm thinking that I'm stuck on an old bootloader and the recovery isn't NF9, which is the current stock recovery. I'm thinking that the reason why I'm unable to flash anything in TWRP/unable to install CWM at all is because of the stock recovery and possibly bootloader being NB4 for some reason while my baseband and build are both NF9. Any ideas/help would be appreciated. Thanks guys.
Click to expand...
Click to collapse
If I were you the first thing I would do is to ODIN flash TWRP recovery
and go from there.
Here is a direct download link for the latest odin flash twrp
custom recovery for the N900T Note 3:
https://app.box.com/AndroidShare
Once you get into twrp recovery do a complete wipe
which includes wipe data, system, cache, dalvik and
last but not least do a factory reset in twrp.
When that's done odin flash the official stock N900T NF9
firmware which can be found at http://SamMobile.com
After that's done you will need to odin flash cf-autoroot
and then odin flash twrp recovery again.
Here is the download link for cf-autoroot:
https://app.box.com/s/rgovggya5gkc51lc1uax
Then simply copy your favorite N900T zip file rom into
your internal sd and flash the N900T rom of your choice.
Be sure to do a full and complete wipe again before
flashing any custom roms.
Good luck!

Galaxy S4 SM-N910P Stuck in Bootloop After Trying to Root With Odin

aboot fused 4 binary 1
hi, i was trying to root my note 4 sm-n910p from sprint using odin, i check in debbuging mode and everything, tried to run the cf autoroot for my phone and it seemed like it was done correctly because the red android appeared and odin said passed. but after that red android appears and all of that it tries to reboot and it gets stuck on the sprint logo just after the samsung one comes up, i can still get into recovery and download modes, i tried hard reseting a couple of times but when i try to reboot it just gets stuck again and reboots and reboots, i tried downgrading to a previous firmware and when i use odin to do it says fail and on the phone the downloading mode says sw rev check fail : (aboot) fused 4 > binary 1, (1) emmc write fail: aboot plz help my baby has been like this for a day now and im desperate :c

If you were on the latest OTA OG5, you can't fully root with CFAutoRoot and you can't downgrade.
As long as you weren't on a bootloader OB7 or below, no harm in going back to Odin or KIES recovery to stock tar OG5.
Remember, if you're trying to root OG5, you need the exploited kernel. Look for freeza's thread in general section hello root 5.1.1
Odin recovery first, then flash the kernel.
This might get you started
http://forum.xda-developers.com/showthread.php?p=62241991
Sent from my SM-N910P using Tapatalk

I'm Also facing the same problem any solutions to this? I took the OTA update of 6.0 but it was restarting again and again so I wiped the system and tried to install the 5.0 AND GOT THIS emmc error

Grv0541 said:
I'm Also facing the same problem any solutions to this? I took the OTA update of 6.0 but it was restarting again and again so I wiped the system and tried to install the 5.0 AND GOT THIS emmc error
Click to expand...
Click to collapse
You've found a very old thread. If you saw the aboot with fuse error along with eMMC like above, you may be OK as long as you don't keep trying to flash anything less than OG5 with Odin.
If it's Lollipop you're after, try OK1 and the latest Lollipop ROM.
If early Lollipop 5.0 or KitKat, you'll need the kernel linked in above thread you quoted but don't use Odin for full stock tar downgrade. But you may need Odin for Lollipop bootloader firmware.
Do you have any TWRP backups for KitKat or 5.0? You could still use those if you downgrade bootloader to OG5 and use the OG5 kernel mentioned earlier.
What may have happened with Marshmallow rebooting was remnant of ItsOn left on internal memory. If that was the issue, you can likely run Marshmallow but you need to wipe internal memory to clean install Marshmallow.
One last thing (important that you review this before you begin) : do you recall what update you had before you wiped system and tried to flash 5.0? You may need to flash that same update (full stock tar) and go through the setup wizard and use same Google user and password to get past that factory reset protection. Sometimes it gets buggy when you try to flash a lower security bootloader in Odin and phone just doesn't seem to flash a different update until you do that or bypass the factory reset protection.
Sent from my SM-N920P using Tapatalk

First of all, thank you for replying I really need your help so here it is
1- I was on KitKat 4.4 when I started ( I'm having the complete backup in twrp 4.4 GB)
2- then I flashed 'N910PVPU1BOB7_N910PSPT1BOB7_N910PVPU1BOB7_HOME.tar" using Odin everything was working fine ( I'm also having the
backup except the system in twrp around 1.1 GB )
3- then I flashed 'Hybrid-x 5.1' that's where it first restarted faced boot loop flashed twrp everything was ok
4- then i decided to go back to 'step-2' i flashed again using Odin everything was Good then ROM download the update VIA OTA I don't know how i received but I did then I installed MM
install through OTA
5- On 'MM 6.0' it was restarting again and again but phone was working for around 20 min then I have to perform factory reset
6- I tried step-2 'N910PVPU1BOB7' And that's whee I got emmc error via Odin I tried again and again
7- Then I tried to restore backup of Lolipop and installed Emotion Rom but no networks everything was working fine else
8- And then I tried to flash 5.0 hybrid x but failed ad\nd stucked into boot loop
9- Then I downloaded 'N910PVPU4COG5 Sprint USA repair version' but failed miserably
10- then I downloaded 'N910PVPS4DQB3_N910PSPT4DQB3_N910PVPS4DQB3_HOME.tar.md5' and flashed it, I think it's MM but didn't work
11 - I read your reply stopped trying
Now before installing every Rom I performed clean installation wiped internal memory and everything except micro sd
and coming to your question I do have the backup of KitKat and 5.0 and I don't want MM I just want my phone back, and after reviewing I was on 4.4 kit kat before installing 5.0
"You may need to flash that same update (full stock tar) and go through the setup wizard and use same Google user and password to get past that factory reset protection. Sometimes it gets buggy when you try to flash a lower security bootloader in Odin and phone just doesn't seem to flash a different update until you do that or bypass the factory reset protection"
And i'm receiving that emmc error only on 5.0 & i'm also getting that 'Kernel is not seandroid enforcing set warranty bit: kernel' and keeps on boot looping but i don't think it's a problem isn't it
I don't know how to through Please guide you have everything and now i'm stucked on boot looo
and tell me how to use the Backup or kenrel
---------- Post added at 11:30 AM ---------- Previous post was at 11:04 AM ----------
samep said:
You've found a very old thread. If you saw the aboot with fuse error along with eMMC like above, you may be OK as long as you don't keep trying to flash anything less than OG5 with Odin.
If it's Lollipop you're after, try OK1 and the latest Lollipop ROM.
If early Lollipop 5.0 or KitKat, you'll need the kernel linked in above thread you quoted but don't use Odin for full stock tar downgrade. But you may need Odin for Lollipop bootloader firmware.
Do you have any TWRP backups for KitKat or 5.0? You could still use those if you downgrade bootloader to OG5 and use the OG5 kernel mentioned earlier.
What may have happened with Marshmallow rebooting was remnant of ItsOn left on internal memory. If that was the issue, you can likely run Marshmallow but you need to wipe internal memory to clean install Marshmallow.
One last thing (important that you review this before you begin) : do you recall what update you had before you wiped system and tried to flash 5.0? You may need to flash that same update (full stock tar) and go through the setup wizard and use same Google user and password to get past that factory reset protection. Sometimes it gets buggy when you try to flash a lower security bootloader in Odin and phone just doesn't seem to flash a different update until you do that or bypass the factory reset protection.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Please Have a Look

Grv0541 said:
First of all, thank you for replying I really need your help so here it is
1- I was on KitKat 4.4 when I started ( I'm having the complete backup in twrp 4.4 GB)
2- then I flashed 'N910PVPU1BOB7_N910PSPT1BOB7_N910PVPU1BOB7_HOME.tar" using Odin everything was working fine ( I'm also having the
backup except the system in twrp around 1.1 GB )
3- then I flashed 'Hybrid-x 5.1' that's where it first restarted faced boot loop flashed twrp everything was ok
4- then i decided to go back to 'step-2' i flashed again using Odin everything was Good then ROM download the update VIA OTA I don't know how i received but I did then I installed MM
install through OTA
5- On 'MM 6.0' it was restarting again and again but phone was working for around 20 min then I have to perform factory reset
6- I tried step-2 'N910PVPU1BOB7' And that's whee I got emmc error via Odin I tried again and again
7- Then I tried to restore backup of Lolipop and installed Emotion Rom but no networks everything was working fine else
8- And then I tried to flash 5.0 hybrid x but failed ad\nd stucked into boot loop
9- Then I downloaded 'N910PVPU4COG5 Sprint USA repair version' but failed miserably
10- then I downloaded 'N910PVPS4DQB3_N910PSPT4DQB3_N910PVPS4DQB3_HOME.tar.md5' and flashed it, I think it's MM but didn't work
11 - I read your reply stopped trying
Now before installing every Rom I performed clean installation wiped internal memory and everything except micro sd
and coming to your question I do have the backup of KitKat and 5.0 and I don't want MM I just want my phone back, and after reviewing I was on 4.4 kit kat before installing 5.0
"You may need to flash that same update (full stock tar) and go through the setup wizard and use same Google user and password to get past that factory reset protection. Sometimes it gets buggy when you try to flash a lower security bootloader in Odin and phone just doesn't seem to flash a different update until you do that or bypass the factory reset protection"
And i'm receiving that emmc error only on 5.0 & i'm also getting that 'Kernel is not seandroid enforcing set warranty bit: kernel' and keeps on boot looping but i don't think it's a problem isn't it
I don't know how to through Please guide you have everything and now i'm stucked on boot looo
and tell me how to use the Backup or kenrel
---------- Post added at 11:30 AM ---------- Previous post was at 11:04 AM ----------
Please Have a Look
Click to expand...
Click to collapse
Your modified stock TWRP backups older than OG5 will need the Lollipop bootloader and the kernel. Seems OG5 bootloader and OG5 Beastmode kernel is what you need.
Your TWRP backups cannot restore bootloader and they may not have the kernel you now need to get those to boot.
Emotion probably didn't work because you need the Lollipop bootloader for connectivity. Keep in mind that internal memory isn't compatible from CM to stock. Your wipes are warranted when crossing platforms like that. But clean installs are a good idea too.
So you at least need the Lollipop bootloader for CM. There's a thread by freeza in our development forum for baseband and bootloader. The ones labeled firmware are bootloaders. You need to Odin that as a tar in AP mode.
Modified stock is just a step or two more. The order of install isn't so important as long you flash kernel zip after restoring the TWRP backup for backups older than OG5. The bootloader can be installed first or last. But the bootloop is likely due to older kernels not working with the newer bootloader. Flash kernel prior to boot. You may also need to flash SuperSU zip again but try the kernel and attempt boot before trying to install SuperSU again. It may depend on the original SuperSU installed; I haven't done this but familiar with posts but recall and steps others may omit may be lacking but I think you can figure it out with the general idea.
But remember your bootloader cannot be downgraded to Android 5.0 or KitKat. That also means you cannot Odin 5.0 or KitKat stock tars.
The older stock backups (KitKat and Lollipop 5.0) should work with lollipop 5.1 bootloader and OG5 Beastmode kernel.
Since you had some success with Emotion ROM, it's possible you don't need to Odin Marshmallow for factory reset protection. I think the kernel for Emotion is fine but you need the OG5 bootloader for that backup to connect.
Sent from my SM-N920P using Tapatalk

samep said:
Your modified stock TWRP backups older than OG5 will need the Lollipop bootloader and the kernel. Seems OG5 bootloader and OG5 Beastmode kernel is what you need.
Your TWRP backups cannot restore bootloader and they may not have the kernel you now need to get those to boot.
Emotion probably didn't work because you need the Lollipop bootloader for connectivity. Keep in mind that internal memory isn't compatible from CM to stock. Your wipes are warranted when crossing platforms like that. But clean installs are a good idea too.
So you at least need the Lollipop bootloader for CM. There's a thread by freeza in our development forum for baseband and bootloader. The ones labeled firmware are bootloaders. You need to Odin that as a tar in AP mode.
Modified stock is just a step or two more. The order of install isn't so important as long you flash kernel zip after restoring the TWRP backup for backups older than OG5. The bootloader can be installed first or last. But the boot loop is likely due to older kernels not working with the newer bootloader. Flash kernel prior to boot. You may also need to flash SuperSU zip again but try the kernel and attempt boot before trying to install SuperSU again. It may depend on the original SuperSU installed; I haven't done this but familiar with posts but recall and steps others may omit may be lacking but I think you can figure it out with the general idea.
But remember your bootloader cannot be downgraded to Android 5.0 or KitKat. That also means you cannot Odin 5.0 or KitKat stock tars.
The older stock backups (KitKat and Lollipop 5.0) should work with lollipop 5.1 bootloader and OG5 Beastmode kernel.
Since you had some success with Emotion ROM, it's possible you don't need to Odin Marshmallow for factory reset protection. I think the kernel for Emotion is fine but you need the OG5 bootloader for that backup to connect.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
I Downloaded
1- OG5 Baseband by Freeza+0G5 Bootloader +Beatmode stock 1.0 and first flashed Kernel Failed! then I tried beastmode kernel r56 succeeded and then I flashed bootloader of OG5 after that Rom Emotion result= No boot at all
2- Then I wiped everything and Tried to install OG5 tar via Odin but again Boot loop
3- Tried Hybrid Rom but again Boot loop
4- And one more thing for the first time I flashed Emotion that was the last time phone booted after it's stucked on boot loop tried everything but I'm failing miserably
So tell me what should I do to Get a boot?
So tell me what to do I don't care whether I'm running MM or lollipop I just want my device back, Tell me the exact order if there Is any other like you said flash the kernel first and after bootloader, Help me

Grv0541 said:
I Downloaded
1- OG5 Baseband by Freeza+0G5 Bootloader +Beatmode stock 1.0 and first flashed Kernel Failed! then I tried beastmode kernel r56 succeeded and then I flashed bootloader of OG5 after that Rom Emotion result= No boot at all
2- Then I wiped everything and Tried to install OG5 tar via Odin but again Boot loop
3- Tried Hybrid Rom but again Boot loop
4- And one more thing for the first time I flashed Emotion that was the last time phone booted after it's stucked on boot loop tried everything but I'm failing miserably
So tell me what should I do to Get a boot?
So tell me what to do I don't care whether I'm running MM or lollipop I just want my device back, Tell me the exact order if there Is any other like you said flash the kernel first and after bootloader, Help me
Click to expand...
Click to collapse
Emotion is CM, right? I wouldn't think Beastmode would boot a CM ROM or backup.
Your TWRP backups don't boot with OG5 bootloader and flashing Beastmode kernel after restoring backup?
The bootloop issues may be data incompatibility. Are you wiping everything but ext sdcard before restoring backup? I think it should work by wiping, restore backup but flash Beastmode before attempting boot. If not, flash latest SuperSU zip from Chainfire. One of those steps should get a boot.
But maybe just a simple factory reset works?
If looking to get going with Odin, you need to flash full stock tar OG5 or higher. There's stock tars to download in the general thread for Sprint Note 4.
You may need to flash original tar that matches the last one you ran successfully before you tried to flash OB7. Or Samsung Smart Switch emergency recovery may do that too.
Weird that TWRP sometimes doesn't wipe after that fuse error. Some have found that stock recovery then factory reset or Philz touch recovery and factory reset may work better than TWRP.
I'd try Smart Switch first though. With Odin, you may need to flash full stock tar, factory reset in stock recovery and flash stock tar again, letting it auto reboot on second flash.
Sent from my SM-N920P using Tapatalk

how to install i317 UCU Stock Recovery without using CWM or TWRP

I am am trying to take my Samsung i317 AT&T Note 2 back to stock.
Installed 4.4.2 NJ1 stock rom using ODIN. Reset/ cleared and started phone and went to OTA upgrade the latest patch from AT&T to make it to NJ2. However, when the phone reboots, the Samsung Note II logo shows up and the screen does dark. When I try to enter recovery, it starts to reinstall the OTA patch all over again and says updated. Tried turning the phone back on and the same thing happens again.
I was able to get the phone to work by reflashing the NJ1 stock rom and installed the ZIP stock recovery file using CWM. However, I am trying to get back to the original stock configuration as possible without having CWM installed on the phone and was hoping I can install the stock recovery so that when I go to download mode, everything shows Samsung Official. Knox Warranty Void is at 1, so I guess there is nothing I can do to fix that at this point.
Would installing this be the simple fix by downloading 4.3 Param.bin and Tz.img
Another would be to install the stock recovery ZIP file using CWM as I have already successfully done and maybe someone can point me to find a way to uninstall the CWM afterwards. I've searched online to remove CWM but couldn't find the md5.tar file that would do that from ODIN.

Odin OH6 question

Hello everyone,
I previously had stock OH6 with root and TWRP. I decided to install Atrium v1.0 http://forum.xda-developers.com/tmobile-galaxy-s6-edge/development/please-post-till-t3171637 and the install requirements are that both Baseband and Bootloader need to be updated to OF8 to match the FW of the rom. I was able to install the rom without a problem. Now this is were I screwed up. I decided to do a fresh install again and in TWRP I wiped Dalvik Cache, system, data, cache and internal storage and also performed a factory reset. At the moment my phone is stuck at the boot screen "Samsung Galaxy S6 Edge" and I can't go into TWRP. I can only access Download mode. My question is can I Odin back to OH6 without bricking my phone or am I stuck with doing Odin to OF8 because of the previous baseband and bootloader upgrade?
Thanks in advance. I really appreciate it.

You can Odin oh6. Once on a higher version you can't Odin back to an older version as downgrade isn't allowed of the bootloader.

Thank you very much.