[Q] Trouble installing custom recovery after obtaining root - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

Hey guys, I've run into an issue while attempting to flash a custom rom to my i337. First off, I was successfully able to obtain root and have verified that I have su privileges. My issue is happening when I try to install any type of boot loader. I've tried the following methods to install a bootloader:
http://forum.xda-developers.com/showthread.php?t=2314494 (step 3- both methods)
http://forum.xda-developers.com/showthread.php?t=2297033
using odin to flash .img recoveries using this conversion method http://forum.xda-developers.com/showthread.php?t=2281287
Whenever I install any recovery and I try to boot into it, I boot into odin/download mode. After this happens I am unable to boot into the stock rom (or any rom for that matter) until I use this (http://forum.xda-developers.com/showthread.php?t=2360859) method to restore my current rom.
Additionally, I have been unable to perform a factory or soft restore since I've had this issue. I can't boot into recovery so I can't do a hard reset, but every time I attempt to restore within the android OS, I boot into odin mode....
It's become quite frustrating and I'm unsure of where to go next.
Additionally, additionally, I do believe that I have the MF3 update installed. I could be wrong, but I'm pretty confident I do.
I just got this phone a few weeks ago and I'm still learning the ropes here... so forgive me for my lack of knowledge on the subject
Thanks in advance for any input

If you have mf3 you can not flash roms or put on a custom recovery. In fact you'll lucky you haven't bricked your phone. Don't try any more until an exploit is found.
Edit, in the mean time, do some more reading and research. You need to know a lot more before you are ready to flash anything if the devs find away to put a custom recovery on.

I just don't understand why people that don't even have a basic concept of how their phone works would do something to it that could (and probably will) turn it into an expensive brick? Is it really to difficult to do a little reading first? It's forum rules, it's common sense, and it can save you a lot of time and trouble. I'm not trying to bust the OP's balls, but if you don't take a little time to be responsible for your own actions (searching and reading and reading some more), you get what you deserve. Being "new" is never an excuse, it's just more reason to do some reading. Everyone, don't touch your phone until you learn about what it is you are doing to it first!
Good luck to the OP, I hope you decide to read (at least) the pinned threads in the General section (and hopefully a lot more) before you do anything else to your phone.

Sad but true
Sent from my SAMSUNG-SGH-I337 using xda premium

Related

[Q] A sort of newbie query but...

Hi there,
I had been umming and arring about rooting and installing a new ROM one of my familys HTC Heroes for some time now and finally after reading lots of "How to's" on lots of different forums I decided to take the plunge and give it a go using the guide on here.
Both my wifes phone and my sons phone are sim unlocked Orange HTC Heros running 2.1-Update 1.
Rooting it was easy. One press of a button and I was there. Its pretty much worked OK and I have sucessfully made three backups of the wifes Hero.
My main query and this is the bit I have not really been able to find much info about despite spending a day trawling through the forums looking for similar queries is this:
Having flashed my recovery image file, the first time I reboot I can get into the recovery mode just fine. From here I can make a backup of the current ROM after which the Hero reboots and goes back into the OS as it should.
If I then shut it down and reboot using the HOME key + POWER option It does not go into the recovery mode. I get the screen with an image of the phone next to a red triangle with an exclamation mark in it.
Using the advice from various forums whilst searching for further advice / hints I have left the phone for up to half an hour but it stays on this screen. The only way to get it out of this screen it to pull the battery.
If I then boot up the phone and reflash the recovery image, I can then get into the recovery mode once again but for ONE BOOT ONLY.
I have tried AmonRA Revcovery v1.7.01. and also the Clockwork Recovery 2.5.0.7 images and both produce the same results. I have tried flashing the images via ROM Manager and also via Android Terminal Emulator
My question is this: Do I have to flash the recovery image EVERY time I want to open the recovery mode or is there something I have missed? At present I have held back from installing a new ROM in case I go past a point of no return where I brick the phone. Neither my wife or son would be too pleased despite my son wanting a better ROM on his.
Apologies for writing "War and Peace" but I wanted to make sure I had covered all I could and hope this is a) not a query already posted elswhere which I have missed b)posted in the right place. Apologies to any forum mods if its not.
Regards
Rhinestone.
hmm look on the unlokr.com or something like that. They use some simple passes and it's the way i did it. the on;y difference is that my phone wasn't blocked on a carrier...
1.there is a program that roots the hero's rom
2.after that i recommend installing clockwork recovery mode (it doesn't need signed zips)
3.if you don't feel safe doing this, i recommend to stop... I know that the 2.1 rom is boring but you can end up with a bricked phone after this...
The official 2.1 update has a script that reflashes the stock recovery every time the phone is shut down.
Hunt about for a modified 2.1 rom, all of them have had that script removed. I'm not a huge fan of sense now, but when I did use it, I found villainrom to be a good 2.1 sense rom.
TheReverend210 said:
The official 2.1 update has a script that reflashes the stock recovery every time the phone is shut down.
Hunt about for a modified 2.1 rom, all of them have had that script removed. I'm not a huge fan of sense now, but when I did use it, I found villainrom to be a good 2.1 sense rom.
Click to expand...
Click to collapse
This, just flash a custom ROM and it will stick.
Hello,
Problem might be with rooting, possible it has not been rooted completely or anything messed up. You can try this for rooting.
http://unrevoked.com/
If you are sure its rooted completely, then check out Superuser apps, if its there, and you are rooted, if not then download terminal emulator and type "su" command, if its doesnt display any error then its rooted.
Other then this,
problem might be with the recovery images you are flashing, download droid explorer its a window application, its has an option of flashing recovery with one click, simply choose recovery image & flash it, clockmod recovery or amonr any of this you can get in xda.

[Q] MF3 Need to Factory Reset & Root!

This is my first post on here, but I've used these forums before to root my S3 and at one time my current S4. My problem is with MF3... I used
this post [http://forum.xda-developers.com/showthread.php?t=2387577] to root my phone once, but since I couldn't install TWRP or CWM, I thought I could downgrade the software version with Odin. Well, I was wrong, and I unrooted my phone in the process... Upon trying the same technique I mentioned earlier, it now says "permission denied" upon entering the first prompt <<cd /mnt/extSdCard>>
AND, I can't use Odin to factory reset. Using posts such as this [http://www.youtube.com/watch?v=hZTTTk7vbVM] doesn't seem to work either. When putting my phone into download mode, I pull up Odin, and select the file in the link (the software file .tar I think), it says it fails shortly after starting.
Really, I need help with two things:
1. Obtaining root access
2. Resetting phone to factory settings
I might not have to do a factory reset, but I've noticed my wifi will NOT enable since I unrooted and this is a big concern for me. I know that all my troubles are because the bootloader is locked (and I'm messing with stuff I don't fully understand...), which is why I'd like help obtaining root again in the final hope that Safestrap [http://forum.xda-developers.com/showthread.php?t=2448925] is the answer I'm looking for so I can use my favorite ROM, LiquidSmooth!
PLEASE help me any way you can! I've tried to provide as much information as I can think of, but I'm new to this stuff, so bear with me. I have no real experience in rooting and whatnot, but so far, I've followed directions by users of this forum, so I have faith that there's a solution to this mayhem. Thanks for any help you can provide! =)
Your first mistake was not reading about what you can and can not do while on mf3. Your second was trying to put a recovery on. And your third was trying to use Odin to down grade your firmware.
I'm surprised your not having issues booting. The only way right now to get your phone back to normal is to see if best buy will flash the mf3 firmware for you
Edit, read this http://forum.xda-developers.com/showthread.php?p=45359306
jd1639 said:
Your first mistake was not reading about what you can and can not do while on mf3. Your second was trying to put a recovery on. And your third was trying to use Odin to down grade your firmware.
I'm surprised your not having issues booting. The only way right now to get your phone back to normal is to see if best buy will flash the mf3 firmware for you
Edit, read this http://forum.xda-developers.com/showthread.php?p=45359306
Click to expand...
Click to collapse
I guess you're trying to be helpful, but your condescending tone isn't helping. I READ everything, I just don't UNDERSTAND everything... The second paragraph actually provided some help, so thanks for that. I was just hoping for something I could do myself to re obtain root so that I can try the Safestrap method I provided in my original post. I will post a reply to the root method post and see if anyone can help me there, since that's my main issue is not being able to get root access back. I don't have any problems booting though, only when I boot into recovery mode do I get a loop in which I just have to get to the Samsung warning screen and select "cancel (reboot phone)". Thanks for reading this and providing some direction.
jeremythetree said:
I guess you're trying to be helpful, but your condescending tone isn't helping. I READ everything, I just don't UNDERSTAND everything... The second paragraph actually provided some help, so thanks for that. I was just hoping for something I could do myself to re obtain root so that I can try the Safestrap method I provided in my original post. I will post a reply to the root method post and see if anyone can help me there, since that's my main issue is not being able to get root access back. I don't have any problems booting though, only when I boot into recovery mode do I get a loop in which I just have to get to the Samsung warning screen and select "cancel (reboot phone)". Thanks for reading this and providing some direction.
Click to expand...
Click to collapse
No, your main issue is that you don't understand what you are reading and you shouldn't be doing anything to your phone until you do. Dozens of people just like you pass through this forum everyday with similar issues because they didn't read or take the time to understand what it was that they did read. Someone takes the time to tell them to read and learn and they don't listen or think they don't have to. Then, they screw their phones up and come back here crying for help. So it's not a condescending tone, it's people getting tired of the same crap. You admitted that you didn't understand everything you read so why would you do anything to your phone before you do understand it? Can you not see the problem?

[Q] Missing recovery on ZTE V5S/V5 Lux/N918ST

DISCLAIMER: Computer idiot. Forgive my stupidity.
Rooted my ZTE V5S using Kingoroot. Played about with apps on google store attempting to install custom recovery. Somehow, in the process, I seem to have lost even my stock recovery? When attempting to enter recovery, I now get this message:
No kernel (boot partition is bad). But it thankfully still boots the stock ROM. I have, however, lost the ability to do factory resets?
Question: is there any way that I can get the stock recovery back? Being able to install a custom recovery would be great, but I'll deal with some recovery...
PS. Any other reading materials to recommend besides http://forum.xda-developers.com/wiki/Main_Page? I guess I'm plain stupid since I don't seem to understand it too well. I'm hoping reading it bit by bit will eventually allow something to diffuse in, but alternative reading material is welcome (and yeah, I've searched google; I just can't tell which is fact and which is fiction).

Nexus 6P will not boot when boot loader is locked!

After using the megapixel rom. I tried flash back to stock with root tool kit.
During the process it told me I had to manual boot in recovery to a factory restore. That would not work so I ended up soft bricking my phone. I was able to side load twrp and the latest build and flash it (thank god). No when I do oem lock boot loader, my nexus 6p won't boot. As soon as I oem unlock, it will boot. Any ideas what could be cause that?
If you did not restore the recovery it probably throws a flag and says the configuration is invalid. You need to restore completely (recovery, boot, system, vendor, etc) through fastboot so that it is truly stock.
Cheers,
B.D.
This is a perfect time to remind folks that "locking" the bootloader is something that should be done with great care. There are dozens, if not hundreds of "my phone is bricked" threads centered around locking their bootloader without understanding the requirements and risks. If you don't have a reason to do it, leave it unlocked. If I need to do it, I flash 100% back to stock using a full factory image before locking.
Sent from my Nexus 6 using XDA-Developers Legacy app
BostonDan said:
If you did not restore the recovery it probably throws a flag and says the configuration is invalid. You need to restore completely (recovery, boot, system, vendor, etc) through fastboot so that it is truly stock.
Cheers,
B.D.
Click to expand...
Click to collapse
So you wouldn't recommend using the Nexus toolkit to flash factory? Can you give me the string in order that I would use to flash factory via fastboot? Fast boot is also hit or miss with the commands for me.
Blackfish77 said:
So you wouldn't recommend using the Nexus toolkit to flash factory? Can you give me the string in order that I would use to flash factory via fastboot? Fast boot is also hit or miss with the commands for me.
Click to expand...
Click to collapse
No offense intended, but this always irks me quite a bit.
Absolutely DO NOT use toolkits for anything at all, ever. They're not easier, they're not faster. It's just doing fastboot / adb with a UI that has buttons you can click instead of typing in fastboot.
This. This is the exact reason you shouldn't use toolkits. Especially if you don't know the manual way. It borks something up and now you need to wait possibly hours to get a working phone again when the solution would only take about 15 seconds to fix.
You need to fully familiarize yourself with this guide here;
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
ADB/Fastboot is absolutely not "hit or miss." If you have trouble with it then you need to make sure that your drivers are properly installed and you're entering commands correctly. Also make sure to ALWAYS keep your ADB & fastboot drivers up to date via the Android SDK. All of this is covered in the link above.
As far as your bootloader issue. You cannot return to a locked bootloader with anything other than 100% complete unadulterated stock factory images. No TWRP, no root, no Xposed, no Magisk, no build.prop edits etc., ...Nothing.
Use fastboot to flash your factory images you downloaded. You can use the flash all bat file or individually flash each separate. Again it's all covered in the link I posted above.
Also, what do you mean you couldn't wipe/reset from stock recovery? When you flash stock recovery and boot to it, you will see an Android on its back with an exclamation mark in a red triangle. You may or may not see text that reads "No Command". Either way, from that point hold down the power button and then press and release volume up. You will boot to stock recovery where you can wipe your data.
Not for nothing, but as mentioned above, people have hard bricked their 6P from locking bootloader's on combos besides stock. You got extremely lucky you didn't as well. Please take some time to read and fully understand what you're doing with your ~600$ device.
This is also, for the most part, pretty standard stuff as far as flashing / modding goes. At least since 2010 when I got into it. If you want to know the exact string of fastboot commands please read and use the guide I linked. It teaches you literally everything. There's nothing it doesn't cover and once you get used to it you will never use a toolkit again.
Hope I didn't come off rude, but basically since 2010 when I got into this across all my devices I try to help out in the Q+A sections. I've probably participated in hundreds and hundreds of "help, I used a toolkit and my phone is bricked and I have no idea how to fix it, I just wanted cool stuff on my phone" threads. They're absolutely 100% not worth the trouble and headaches from them. Especially if you have no idea what they're doing on the back end. Know Fastboot and ADB like the back of your hand and just prefer to use them? That's a different story, if something fails then you fix it yourself in 10 seconds. But for the love of God, please please please please please stop using toolkits if you don't know how to fix issues on your own. You will eventually hard brick. I've seen it happen dozens of times. Thread turns into a circlej*rk about whether toolkits are bad or not, OP hard bricks their phone and commits fraud, which is illegal by trying to RMA it. Just don't use them. It's simple enough without them. Why reinvent the wheel when it works just fine?
You should only lock bootloader when you are on stock factory image from nexus developers site. Either use flash_all script or flash everything manually. As others said keep away from toolkits.. You never know what can go wrong or what they re doing in background.
As I understand you restored TWRP and Megapixel rom and tried to lock the bootloader when you had that combination installed on your phone? That can not be done. You are either full stock (rom, kernel, recovery...) and locked bootloader or unlocked bootloader and any combo of kernel, rom, recovery that you want.
RoyJ said:
No offense intended, but this always irks me quite a bit.
Absolutely DO NOT use toolkits for anything at all, ever. They're not easier, they're not faster. It's just doing fastboot / adb with a UI that has buttons you can click instead of typing in fastboot.
This. This is the exact reason you shouldn't use toolkits. Especially if you don't know the manual way. It borks something up and now you need to wait possibly hours to get a working phone again when the solution would only take about 15 seconds to fix.
You need to fully familiarize yourself with this guide here;
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
ADB/Fastboot is absolutely not "hit or miss." If you have trouble with it then you need to make sure that your drivers are properly installed and you're entering commands correctly. Also make sure to ALWAYS keep your ADB & fastboot drivers up to date via the Android SDK. All of this is covered in the link above.
As far as your bootloader issue. You cannot return to a locked bootloader with anything other than 100% complete unadulterated stock factory images. No TWRP, no root, no Xposed, no Magisk, no build.prop edits etc., ...Nothing.
Use fastboot to flash your factory images you downloaded. You can use the flash all bat file or individually flash each separate. Again it's all covered in the link I posted above.
Also, what do you mean you couldn't wipe/reset from stock recovery? When you flash stock recovery and boot to it, you will see an Android on its back with an exclamation mark in a red triangle. You may or may not see text that reads "No Command". Either way, from that point hold down the power button and then press and release volume up. You will boot to stock recovery where you can wipe your data.
Not for nothing, but as mentioned above, people have hard bricked their 6P from locking bootloader's on combos besides stock. You got extremely lucky you didn't as well. Please take some time to read and fully understand what you're doing with your ~600$ device.
This is also, for the most part, pretty standard stuff as far as flashing / modding goes. At least since 2010 when I got into it. If you want to know the exact string of fastboot commands please read and use the guide I linked. It teaches you literally everything. There's nothing it doesn't cover and once you get used to it you will never use a toolkit again.
Hope I didn't come off rude, but basically since 2010 when I got into this across all my devices I try to help out in the Q+A sections. I've probably participated in hundreds and hundreds of "help, I used a toolkit and my phone is bricked and I have no idea how to fix it, I just wanted cool stuff on my phone" threads. They're absolutely 100% not worth the trouble and headaches from them. Especially if you have no idea what they're doing on the back end. Know Fastboot and ADB like the back of your hand and just prefer to use them? That's a different story, if something fails then you fix it yourself in 10 seconds. But for the love of God, please please please please please stop using toolkits if you don't know how to fix issues on your own. You will eventually hard brick. I've seen it happen dozens of times. Thread turns into a circlej*rk about whether toolkits are bad or not, OP hard bricks their phone and commits fraud, which is illegal by trying to RMA it. Just don't use them. It's simple enough without them. Why reinvent the wheel when it works just fine?
Click to expand...
Click to collapse
I ended up using fastboot to flash factory. I then re locked bootloader and everything booted without and issue. I was happy about that. I re rooted and everything is working great. :good:
I can say I learned a lot from this experience. Thanks to everyone for your advice. I am now comfortable using the fastboot method. Almost bricking my phone was scary but it taught me a lesson. Cheers everyone.

[FIX] Seandroid enforcing (NO ROM RE-FLASH)

In my case, I had installed the rom manager app, and tried to flash clockwork using it. I had thought rooting would be good enough, but I had forgotten to bypass the Verizon BS.
I had tried to boot to the recovery using the option in the app, which greeted me with that error, which will probably happen any time I try to boot into the device's stock recovery. I needed a quick solution, and managed to find it. If you just tried to manually enter recovery and it looped it, the results will likely be the same.
This doesn't look like it will work, and looks like pay bait, but it isn't. You can use the free trial to do the fix (which I have just wasted before I attempted to install my rom I wanted) and it will work without data loss. I didn't even lose root, which I would have using the popular method of re-flashing stock with ODIN.
Get this download, and follow the instructions. You will need a PC and you will need to have your phone hooked up to it and in download mode. It's quick and easy. The loading time seems long, but be patient as that could be a hard brick if you just unplug it (I'd give it at least 20min, but it took about 5 for me)
I don't know if it fixes the recovery, or really what it does, but it'll get you up and running in a pinch. Helped me, could help others with this issue.
https://www.fonepaw.com/bricked/recovery-is-not-seandroid-enforcing.html
Wrong forum this is not Verizon model forum .

Categories

Resources