Develop Bugs

[Q] TWRP 2.6.3.1 Asks for password

I woke up this morning to my phone perpetually rebooting.
I was running a nightly of CM 11.
Now when I try to go into Recovery I get a screen that asks for a password. I have no idea what that password is as I did not set one. I tried wiping data to no avail. I tried flashing a new recovery via Odin this did not work (Odin said successful but the screen on the phone never showed the transfer of the file). No matter what wipe method I use in recovery it just says fail, doesn't work at all and hangs or will say it can't mount. I have searched and searched and tried and tried and I'm stuck. I even tried ADB that didn't work either. Please help!

Try flashing Philz Touch (based on CWM) over TWRP via Odin. I have always had good luck with CWM and Philz.
Download the tar version: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att

audit13 said:
Try flashing Philz Touch (based on CWM) over TWRP via Odin. I have always had good luck with CWM and Philz.
Download the tar version: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att
Click to expand...
Click to collapse
I tried this already. I cannot flash ANYTHING via ODIN. Odin states that the process completed but the bar on the phone on the download screen never shows up to show that it has accepted a file.

therecker said:
I tried this already. I cannot flash ANYTHING via ODIN. Odin states that the process completed but the bar on the phone on the download screen never shows up to show that it has accepted a file.
Click to expand...
Click to collapse
Did you unchecked F . reset and unchecked auto reboot when you flashed recovery in Odin? After you flash the file you have to pull the battery then replace it and boot to recovery do not allow the phone to boot to OS or you have to flash again as your recovery will only stick if you pull the battery and boot to recovery after flashing it. After you get into it the first time all will be well with the world again you can flash your heart out.
I had twrp ask me for a password once I hit the back arrow key and told it to mount my external SD card then flashed my rom, bootloader, kernel and modem then rebooted no problem.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

theramsey3 said:
Did you unchecked F . reset and unchecked auto reboot when you flashed recovery in Odin? After you flash the file you have to pull the battery then replace it and boot to recovery do not allow the phone to boot to OS or you have to flash again as your recovery will only stick if you pull the battery and boot to recovery after flashing it. After you get into it the first time all will be well with the world again you can flash your heart out.
I had twrp ask me for a password once I hit the back arrow key and told it to mount my external SD card then flashed my rom, bootloader, kernel and modem then rebooted no problem.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
This did not work. When I use ODIN all that is happening is that ODIN says it has succeeded but the little progress bar that usually shows up on the phone when you are in download mode never comes up. I did try this method though and it didn't work.
I restarted the phone in ODIN mode then opened ODIN then connected the USB cable then unchecked the two boxes you mentioned then flashed a new non TWRP recovery then waited for ODIN to say successful then the phone never showed the progress bar so I waited 2 mins until I pulled the battery then I restarted phone directly to recovery and still have the password prompt. Even after hitting cancel I cannot interact with recovery because every option I choose just says fail. I cannot even mount external sd card.

What phone do you have? What was the most recent stock ROM on your phone? Maybe you can flash a stock ROM.

There is a copy of the stock Samsung 3e recovery (which we can't use to flash zips with) I'm curious if maybe it can overwrite what you have going on? On the password screen I wasn't hitting cancel I was simply hitting the back arrow key. I will see if I have a copy of the stock recovery, just maybe you can flash it then flash another recovery after that so you can fix your phone.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

I have Samsung Galaxy S 3 At&T (d2att) SGH-I747 whichever one of those you want. The most recent stock rom on the phone was when I bought it brand new a few months after it came out. I tried installing a stock rom. I tried this using ODIN and it failed. The issue here is that TWRP somehow encrypted the entire file system so NOTHING at all in recovery works. When I use ODIN mode it never shows on my phone that it is accepting a transfer from the computer. When I tried the stock rom via ODIN method it actually failed in ODIN instead of telling me it succeeded and then just not work. It failed at the point when it says Firmware Update Start...aboot.mbn...NAND Write Start!...Complete(Write) operation failed. I am up for any suggestions but I need them to be detailed instructions because I have tried so many things I need to know what exact steps to follow.

I believe the aboot file is a bootloader. Did you ever have a stock 4.3 ROM on the phone? If you did, it probably has the stock 4.3 AT&T bootloader which cannot be downgraded without bricking the phone which means you cannot flash a ROM with an older bootloader via Odin.

audit13 said:
I believe the aboot file is a bootloader. Did you ever have a stock 4.3 ROM on the phone? If you did, it probably has the stock 4.3 AT&T bootloader which cannot be downgraded without bricking the phone which means you cannot flash a ROM with an older bootloader via Odin.
Click to expand...
Click to collapse
To my knowledge I never had a stock 4.3 ROM on the phone. The only stock ROM to touch this phone was the one that came on it. So be specific what are you actually suggesting in this post that I do?

therecker said:
To my knowledge I never had a stock 4.3 ROM on the phone. The only stock ROM to touch this phone was the one that came on it. So be specific what are you actually suggesting in this post that I do?
Click to expand...
Click to collapse
I am surprised that the aboot file was giving you a problem because the bootloader can be downgraded as long as it is not a 4.3 bootloader.
Do you recall exactly which ROM was on the phone when you got it? Where did you get the stock ROM?

audit13 said:
I am surprised that the aboot file was giving you a problem because the bootloader can be downgraded as long as it is not a 4.3 bootloader.
Do you recall exactly which ROM was on the phone when you got it? Where did you get the stock ROM?
Click to expand...
Click to collapse
It was a CM11 Nightly ROM from the very beginning of February. And before that it was a CM10.2 Stable ROM.

Which stock ROM was on your phone before you loaded a custom ROM?

audit13 said:
Which stock ROM was on your phone before you loaded a custom ROM?
Click to expand...
Click to collapse
I have no idea. It was when I first got the phone in November of 2012.

Sounds like your phone may be running a 4.3 bootloader which means your bootloader is locked and cannot be downgraded. This may explain why you are getting errors when trying to flash Odin. There is no stock AT&T 4.3 ROM that can be flashed via Odin.

[Q] "Kernel is not seandroid enforcing" :(

I have PayPal for which I will use to donate an amount to the person(s) who can help me.
I just recently got a new GS4 becuase of an insurance replacement. I looked at the specs before I flashed TWRP. After failing to install 4.2.2 ROMS, I finally found a 4.3 mk2 stock ROM to install. I have the phone working. But TWRP is not installed. My phone tests positive for ROOT with Rootchecker
Currently I'm getting this message everytime I boot "Kernel is not seandroid enforcing"
I have multiple 4.4.2 and 4.3 ROMs I like to use on my SD card, I'd like to continue from a TWRP backup i've made using that recovery.
Here are my current specs:
Model
SGH-M919
Android Version
4.3
Baseband
M919UVUEMK2
Kernel Version
[email protected] #1
Build Number
JSS15J.M919UVUEMK2
SELinux status
Permissive
Secure boot status
Type: Samsung

The replacement phone was probably already on the MK2 bootloader and modem when you received it. Which means you had Knox pre-installed and tripped it when you rooted the phone. The "kernel is not seandroid enforcing" error message does not affect the functioning of your phone in any way. It's just a part of the Knox bootloader. You can continue to re-install TWRP recovery and flash any ROM you want. Your phone will function as normal. Just don't try reverting to the 4.2.2 MDL baseband/modem because it won't work. There's currently no way to revert to 4.2.2 MDL if you're on MK2 or higher. If you want to get rid of the message just flash the stock kernel in a recovery.
Try to be careful with your replacement phone now since you tripped Knox. It might be harder to get a replacement depending on how T-Mobile is.
No donations are needed for these kinds of things.

Ok Im flashing Infamous 4.4.2 Version 3.7 after ODIN flashing TWRP 2.6.3.1
The only reason I'm flashing that ROM is because no backups are not showing theirselvesin the Restore option, what would cause that?
Is TWRP 2.5.0.2 better?
Did I miss a step? All my actions were using odin to flash the twrp recover, and then flash another ROM, or restoring a Previous Back. Should I have flashed a rooted bootloader, or rooted firmware or anything besides those two?

nopotential said:
Ok Im flashing Infamous 4.4.2 Version 3.7 after ODIN flashing TWRP 2.6.3.1
The only reason I'm flashing that ROM is because no backups are not showing theirselvesin the Restore option, what would cause that?
Is TWRP 2.5.0.2 better?
Click to expand...
Click to collapse
The backups could either be stored on the internal or external SD card. Try switching between both and see if they appear. They'll be in the TWRP folder on the root of either the internal/external storage.
I've had no problems with the latest TWRP v2.7.0.1. If you have problems then use v2.5.0.2.
If you have connection problems after installing Infamous 4.4.2, you might need to Odin the newest KitKat NB4 modem found here.
Download the file and flash MODEM.bin via Odin under the phone slot.
Personally, since you already tripped Knox, you should just Odin flash the complete NB4 KitKit stock ROM which will give you the newest modem without having to mess with anything else or do various flashing of things. Everything for flashing NB4 KitKit can be found here. Download the full 4.4 firmware from here.

brian117 said:
The backups could either be stored on the internal or external SD card. Try switching between both and see if they appear. They'll be in the TWRP folder on the root of either the internal/external storage.
I've had no problems with the latest TWRP v2.7.0.1. If you have problems then use v2.5.0.2.
If you have connection problems after installing Infamous 4.4.2, you might need to Odin the newest KitKat NB4 modem found here.
Download the file and flash MODEM.bin via Odin under the phone slot.
Personally, since you already tripped Knox, you should just Odin flash the complete NB4 KitKit stock ROM which will give you the newest modem without having to mess with anything else or do various flashing of things. Everything for flashing NB4 KitKit can be found here. Download the full 4.4 firmware from here.
Click to expand...
Click to collapse
I want to use a custom ROM because of the features. Should I still flash the latest firmware, the KitKat NB4?

nopotential said:
I want to use a custom ROM because of the features. Should I still flash the latest firmware, the KitKat NB4?
Click to expand...
Click to collapse
You will still be able to flash the custom ROM after you Odin flash the KitKat NB4 firmware. The steps are as followed:
1. Open Odin v3.07.
2. UNcheck the boxes that say auto reboot and f. reset time.
3. Power off your phone and enter Download Mode by holding down the Vol DOWN + Home + Power buttons at the same time. Hit Vol UP after the warning message comes up.
4. Connect your phone to your PC and wait for it to appear in the COM: box in Odin.
5. Click the PDA tab and select the "M919UVUFNB4_HOME.tar.md5" file that you extracted from http://www.cheatersedge.org/android/m919/M919UVUFNB4_M919TMBFNB4_TMB_FENNY_FIXED.zip.
6. Wait for it to run an MD5 check. The program will freeze and unfreeze when it's done.
7. Click start and let Odin flash the ROM.
8. When it says PASS, unplug the phone and long press the power button until the phone turns off and reboots on its own. Leave it alone for about 2 minutes and then power it off.
9. Reboot back into Download Mode and then flash the CF-Autoroot found here.
10. Flash that via the PDA slot in Odin, reboot, and you should now be rooted. You can then continue to do everything else such as install TWRP and flash Infamous 4.4.2.

brian117 said:
You will still be able to flash the custom ROM after you Odin flash the KitKat NB4 firmware. The steps are as followed:
1. Open Odin v3.07.
2. UNcheck the boxes that say auto reboot and f. reset time.
3. Power off your phone and enter Download Mode by holding down the Vol DOWN + Home + Power buttons at the same time. Hit Vol UP after the warning message comes up.
4. Connect your phone to your PC and wait for it to appear in the COM: box in Odin.
5. Click the PDA tab and select the "M919UVUFNB4_HOME.tar.md5" file that you extracted from http://www.cheatersedge.org/android/m919/M919UVUFNB4_M919TMBFNB4_TMB_FENNY_FIXED.zip.
6. Wait for it to run an MD5 check. The program will freeze and unfreeze when it's done.
7. Click start and let Odin flash the ROM.
8. When it says PASS, unplug the phone and long press the power button until the phone turns off and reboots on its own. Leave it alone for about 2 minutes and then power it off.
9. Reboot back into Download Mode and then flash the CF-Chain's Autoroot found here.
10. Flash that via the PDA slot in Odin, reboot, and you should now be rooted. You can then continue to do everything else such as install TWRP and flash Infamous 4.4.2.
Click to expand...
Click to collapse
Thanks for the step by step. I'm following it now. The NB4_HOME.tar.md5 is taking a long time to flash with ODIN. But I will follow it closely, if everything looks good I'll send out a donation, I appreciate your help.

nopotential said:
Thanks for the step by step. I'm following it now. The NB4_HOME.tar.md5 is taking a long time to flash with ODIN. But I will follow it closely, if everything looks good I'll send out a donation, I appreciate your help.
Click to expand...
Click to collapse
Like I said donations are not needed. It does take a while for it to flash through Odin so that's normal.

It was boot looping, went into optimizing apps to something about media database multiple times. I went into the stock recovery and cleared cache and factory reset. It's trying to boot now.

nopotential said:
It was boot looping, went into optimizing apps to something about media database multiple times. I went into the stock recovery and cleared cache and factory reset. It's trying to boot now.
Click to expand...
Click to collapse
My Wifi is unable to be turned on in this stock rom. I'm going to flash TWRP and then Infamous

nopotential said:
It was boot looping, went into optimizing apps to something about media database multiple times. I went into the stock recovery and cleared cache and factory reset. It's trying to boot now.
Click to expand...
Click to collapse
Yes that will happen. You just boot into recovery and factory reset and it will boot. Let me know if that works.
nopotential said:
My Wifi is unable to be turned on in this stock rom. I'm going to flash TWRP and then Infamous
Click to expand...
Click to collapse
If you continue to have WiFi problems, flash this via recovery.

brian117 said:
Yes that will happen. You just boot into recovery and factory reset and it will boot. Let me know if that works.
If you continue to have WiFi problems, flash this via recovery.
Click to expand...
Click to collapse
It looks like everything is looking good by following your list. Thank you.

nopotential said:
It looks like everything is looking good by following your list. Thank you.
Click to expand...
Click to collapse
Awesome! Good to hear man. Enjoy KitKat and the newest modem. The new modem has gave a significant reception boost for a lot of people. Hope it's the same for you. And please check your PM.

-Deleted-

[Q] CWM Help

Hey guys, I flashed a Custom Rom, Slimkat. Via CWM, but I wanted to come back from Slimkat to my official rom. I came back successfully to my official Rom, then I like a mod and wanted to flash it, all done. But when I try to go into Recovery mode it opens stock recovery only! But I didn't gave up, I flashed the CWM again via Odin as before. But it opens stock recovery only! Please help me guys. Thanks in advance.

shanwarsi said:
Hey guys, I flashed a Custom Rom, Slimkat. Via CWM, but I wanted to come back from Slimkat to my official rom. I came back successfully to my official Rom, then I like a mod and wanted to flash it, all done. But when I try to go into Recovery mode it opens stock recovery only! But I didn't gave up, I flashed the CWM again via Odin as before. But it opens stock recovery only! Please help me guys. Thanks in advance.
Click to expand...
Click to collapse
In my case, when I install CWM recovery using odin, it installs sucessfully, but when my phone reboots after the download, and then I try going to the recovery, I still get the official Stock recovery.

Same
saudkhan75 said:
In my case, when I install CWM recovery using odin, it installs sucessfully, but when my phone reboots after the download, and then I try going to the recovery, I still get the official Stock recovery.
Click to expand...
Click to collapse
Same problem I got

shanwarsi said:
Same problem I got
Click to expand...
Click to collapse
Not only you, many other users like us got the same problem.
When we install CWM using Odin with Auto-Reboot turned on, it says pass and reboots the phone. But when we go to the recovery mode, the Stock recovery is still present there.
Secondly, when we try installing CWM using Odin with Auto-Reboot unchecked, the phone freezes on the downloading screen after downloading it, so we have to remove the battery, put it back inside, and go to the recovery. At that time we can see CWM recovery, but when we reboots system and then later when we have to come back to recovery more, the stock recovery pops up again.
This kind of problems are being faced by many Samsung Galaxy Grand duos GT-19082 users.
It would be really appreciated if someone knows the solution and could help us.
Thanks!

[Q] Sprint Galaxy S3 will not complete boot process

I've searched around for this specific problem and haven't found anything that will help me. I have the SPH-L710 model through Sprint that was previously running Android 4.4.2. That version killed the battery, so I attempted to root and install a custom ROM. I have rooted before, so superSU was already on the phone. I opted to follow the rooting directions from galaxys3root.com, which uses ClockworkMod Recovery v5.5.0.4. I did that and installed superSU again via a .zip file. When I rebooted the phone, superSU kept stopping. After some frustration, I found that there was an updated superSU v2.01 that I installed via CWM. Being an idiot, I figured I would just go right ahead and trying to install the custom ROM without checking anything. I then attempted to install the Carbon ROM 4.4.4 from galaxys3root.com without first making a backup of my existing version (again, idiot). There was some sort of error, and after that point, I was unable to boot up the phone...it would display the Samsung GS3 screen and then do a continuous bootloop.
I tried finding stock ROMS, but they usually have to be loaded from the SD card rather than through ODIN, and they so far haven't been working. I have downloaded more than one that claimed to be an MD5, but they turned out not to be. My wife has the exact same phone so I thought maybe if I use CWM to save a backup of hers to my SD card, perhaps I could restore that and boot up my phone. I got a bit farther this time and boot up made it through the Samsung GS3 and various Sprint 4g screens before getting stuck on the last Samsung screen.
If I can get the phone to boot up again, I've since learned that once you update superSU, you can have it disable knox, thereby allowing me to root, and thereby allowing me to install a custom ROM, but at this point I just need to get the phone to boot up so I can use it again.
Summary:
Attempted to root using CWM v5.5.0.4
Did not properly disable Knox first and had an error loading custom ROM
Phone stuck in bootloop
Did not back up phone first but have a backup of my wife's exact same model
Used that backup and it gets stuck on very last Samsung screen
Any and all help is appreciated.
Matt

huntley said:
Summary:
Attempted to root using CWM v5.5.0.4
Did not properly disable Knox first and had an error loading custom ROM
Phone stuck in bootloop
Did not back up phone first but have a backup of my wife's exact same model
Used that backup and it gets stuck on very last Samsung screen
Any and all help is appreciated.
Matt
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2738533 <-----Odin stock ND8 rom use Desktop Odin
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/philz_touch_6.48.4-d2lte.tar.md5/ <------flash this recovery through Odin as well it gives you the option to root the stock ND8 rom under Philz settings choose option re-root(SuperSU)

6th_Hokage said:
http://forum.xda-developers.com/showthread.php?t=2738533 <-----Odin stock ND8 rom use Desktop Odin
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/philz_touch_6.48.4-d2lte.tar.md5/ <------flash this recovery through Odin as well it gives you the option to root the stock ND8 rom under Philz settings choose option re-root(SuperSU)
Click to expand...
Click to collapse
Thank you. That image worked perfectly, and the recovery is a newer version than I was trying to use earlier.

huntley said:
Thank you. That image worked perfectly, and the recovery is a newer version than I was trying to use earlier.
Click to expand...
Click to collapse
i know lol but its the best one for stock ND8 honestly

stuck in recovery mode

I have a Samsung galaxy tab 3 light it also has TWRP recovery.
After installing this app: play.google.com/store/apps/details?id=phongit.quickreboot&hl=en
and using it to boot into recovery, I am now stuck recovery boot loop,I can however still get into download mode.
I also do not have a customer rom or custom kernel installed.
I tried using backups that I have, wiping cash,and even entering strings of code in terminal that I found on forums that said it would work, and none of it seems to work.
I do not care about keeping any data that's on there I just want to get out of the loop.
P.s please keep in mind that I am extremely new to android, as well as this form.

neo6060 said:
I have a Samsung galaxy tab 3 light it also has TWRP recovery.
After installing this app: play.google.com/store/apps/details?id=phongit.quickreboot&hl=en
and using it to boot into recovery, I am now stuck recovery boot loop,I can however still get into download mode.
I also do not have a customer rom or custom kernel installed.
I tried using backups that I have, wiping cash,and even entering strings of code in terminal that I found on forums that said it would work, and none of it seems to work.
I do not care about keeping any data that's on there I just want to get out of the loop.
P.s please keep in mind that I am extremely new to android, as well as this form.
Click to expand...
Click to collapse
The onlyest way is flash STOCK with Odin.
If you want root, flash PhilzTouch with Odin, after flash Boot directly with Power ,Volume+ and Home button into Recovery and flash The SuperSu.ZIP V1.94
After that install The supersu.APP from playstore and update The supersu.
This way was working by me.

bierma32 said:
The onlyest way is flash STOCK with Odin.
If you want root, flash PhilzTouch with Odin, after flash Boot directly with Power ,Volume+ and Home button into Recovery and flash The SuperSu.ZIP V1.94
After that install The supersu.APP from playstore and update The supersu.
This way was working by me.
Click to expand...
Click to collapse
I've tried several ROMs and still no dice.
Any other ideas.

Ive experienced this before and flashing stock thru odin is the only way out, and dont use quickreboot again heard theres a bug with the kernel

LoVeRice said:
Ive experienced this before and flashing stock thru odin is the only way out, and dont use quickreboot again heard theres a bug with the kernel
Click to expand...
Click to collapse
any ideas where I can find the stock rom.

neo6060 said:
any ideas where I can find the stock rom.
Click to expand...
Click to collapse
You could go to sammobile
h__p://www.sammobile.com/firmwares/
and search by your device type

neo6060 said:
any ideas where I can find the stock rom.
Click to expand...
Click to collapse
That is what i have writen, flash Stock with Odin.