First, thank you to the mods for putting my last post in the right place (and now I know where the right place is).
Anyhoo, my previous problem was a hardware issue that I've had repaired.
Now, this is no longer critical since I bought a replacement phone (Xperia Z if anyone cares) that is happily rooted and running CM. However, I'd still like the S4 rooted with CM and ready to go in an emergency.
The downside of the repair was that the shop I took it too re-flashed it back to stock (I wasn't happy, but hell, it gives me something to do, practically risk free now). Having soft bricked the I9505 three times, I've brought it back to life. However, I'd like to get twrp on there (Honestly, CWM is stepping backwards rather than forwards IMHO, dumbing down to the lowest common denominator). I have the flash files, and for good measure, I have a stock G4 recovery.
Now my problem,. whilst the phone will boot normally without an issue (I said I brought it back from dead), I can't boot to any recovery, either from the phone itself with HW keys, or via adb. It simply sits there at the Samsung logo pretending to boot. This is with both TWRP and stock, so I'm stumped.
I get the Samsung logo, with the little blue too tiny to read text top left, and there it stays. Normal reboot works just peachy with both. Not rooted as best as I can tell (though it should be). i.e. In developer options, none of the root stuff (enhanced reboot, root options etc.) are missing.
So, whilst not critical (it will still be a handy backup phone), any ideas?
you wouldn't have any advanced reboot options unless they were in the rom, and you can't have TWRP without root. maybe the phone shop left you with nothing as a recovery because they forgot ???
In Odin, uncheck everything except f.reset time, flash the tar version of TWRP in Odin, when you see the word "reset" in the status window, remove USB cable from the phone, remove battery, wait 5 seconds, replace battery, use buttons to get into recovery.
Getting into recovery.
*Press the three button combo of vol.up+home+power button
*As soon as Samsung appears relase the combo and in a jiffy press only the volume up+home button.
Hurray! :')
In order:
I've reflashed TWRP, stock, and CWM - all the successful, but same result
No Odin,. Linux user exclusively - so Heimdall
Three button combo starts recovery reboot (the giveaway is the too small to read blue text top left), but there it hangs. Using abd results in the same.
It simply hangs on booting recovery, whichever recovery, but will boot normally without a problem. Tried with and without SIM/SDCard/both/neither.
Probably worth adding, I'm not new to rooting (done it with my last 7 phones, including the one I'm currently using (Xperia Z)), and the S4 was rooted with CM13 before the shop got their hands on it.
After flashing twrp, are you letting the phone auto reboot from Odin?
How many times. Linux user - no Odin (that's Windows) - Heimdall, and it's not just TWRP, it's stock, TWRP and CWM
Personally, recommend trying to flash with Odin. I use Mac OSX myself.
I only have two options for Odin, either via a VM or using wine, and neither lets it detect the phone in download mode.
However, heimdall has always worked well (previously on this phone) so I'm not convinced that's the problem.
Don't know why, but it's finally worked.
How do I mark solved?
Related
A message popped up from Samsung to install an update (I had been pressing cancel for the past week on this update). It says click OK to reboot and apply update (something along those lines) so I do. Now I am stuck with a tablet that won't boot. If I hold the power button it says "Samsung Galaxy 10.1" after about 12 seconds, but then it goes away and back to darkness. Nothing else. Holding power and volume up does nothing.
Someone know what is going on and have any idea how to resolve?
The best way is to restore any backup you have from cwm recovery. Else grab a stock firmware and flash it with ODIN or if zip than CWM recovery. For luck, try clearing cache and data in recovery, first!Perhaps it may work saving you all fuss of flashing a firmware.
I cannot even boot that far too get into recovery. And I just noticed that although I can't boot, the backlight is on (on a solid black screen).... wtf
You can't hold volume down and power button to enter recovery?
Nope. I plugged into my computer and for some reason with the USB connectd it let me enter recovery. Flashed a backup and rebooted, but now I have no wifi... im confused.
it occured once to me when i tried to overclock, it never worked except when installing a new rom... Try to root the device and then install a new rom
OK, was a helluva night messing with ROM and kernel installs... I have yet to go back to completely stock (that's next up tonight, unfortunately), but I installed Starburst ROM and the Wifi still didn't work so I then installed pershoot's kernel and now when I boot the screen is extremely distorted kind of like this: http://t1.gstatic.com/images?q=tbn:ANd9GcTsKa5IoQxnesGdUjykWDDggoQZ38yZ2VXSgPAQ09NOCnETzl9-
As a side note, when I say the wifi is not working, it still shows all networks and allows me to connect just like normal. However when connected no apps can access the network...
Can someone point me to a thread on how to revert EVERYTHING back to stock so I can start fresh? TIA!!
http://forum.xda-developers.com/showthread.php?t=1171089
Should have all the files you need. From where you are now I would flash the stock OTA 3.1 or TW then flash the stock recovery and do a factory reset from that recovery. That should get rid of the garbled screen.
Thanks buddy. On my way to grab the files now
I heard the update was pulled as it sometimes rewrites the bootloader improperly. You might need to send it in, unfortunately.
Please see Update 5 at/near the top of:
http://forum.xda-developers.com/showthread.php?t=2176452
Basically, a bad USB cable was making fastboot operations flakey, and by the time I discovered it, the recovery program was wrecked. Everything else seems to work fine. The Nexus is running 4.2.2, and I have toolkit 4.3.5, running on win7x64.
I've tried reflashing various recovery programs, including the stock one. No error flashing is reported (with the now-good cable), but going into recovery mode fails, showing the android image with a red triangle and exclamation point in it.
[Edit: To be clear, I have NO recovery menu at all - when I select recovery in the bootloader, I get the regular boot "X" in the middle of the screen, then it is replaced with the android lying on its back with the alert notice above it]
The bootloader appears successfully unlocked, and in fact the entire unlock/root process was fine, once the cable was replaced. That is, no errors were reported, everything seems to be ok, but I can't use the recovery option. Note that the unlock wiped all data, so it was as clean as possible.
Should I completely reflash 4.2.2? Will that even matter?
Is there anything else I can try? I'm not keen to try sideloading 4.2.2, but will, if there are instructions some place.
If this is no go, I'm going to have to try restoring everything to the basic original state and asking for a replacement from Amazon. I don't know how that will go, and this was to be a gift due in about a week, that I was setting up for the recipient. I've spent literally 8 hours on this today, before realizing the flakeyness was due to the USB cable being bad. Any help is very appreciated.
stickplayer said:
Please see Update 5 at/near the top of:
http://forum.xda-developers.com/showthread.php?t=2176452
Basically, a bad USB cable was making fastboot operations flakey, and by the time I discovered it, the recovery program was wrecked. Everything else seems to work fine. The Nexus is running 4.2.2, and I have toolkit 4.3.5, running on win7x64.
I've tried reflashing various recovery programs, including the stock one. No error flashing is reported (with the now-good cable), but going into recovery mode fails, showing the android image with a red triangle and exclamation point in it.
[Edit: To be clear, I have NO recovery menu at all - when I select recovery in the bootloader, I get the regular boot "X" in the middle of the screen, then it is replaced with the android lying on its back with the alert notice above it]
The bootloader appears successfully unlocked, and in fact the entire unlock/root process was fine, once the cable was replaced. That is, no errors were reported, everything seems to be ok, but I can't use the recovery option. Note that the unlock wiped all data, so it was as clean as possible.
Should I completely reflash 4.2.2? Will that even matter?
Is there anything else I can try? I'm not keen to try sideloading 4.2.2, but will, if there are instructions some place.
If this is no go, I'm going to have to try restoring everything to the basic original state and asking for a replacement from Amazon. I don't know how that will go, and this was to be a gift due in about a week, that I was setting up for the recipient. I've spent literally 8 hours on this today, before realizing the flakeyness was due to the USB cable being bad. Any help is very appreciated.
Click to expand...
Click to collapse
So you've tried using fastboot to flash a custom recovery image? The command fastboot is a part of the Android SDK.
fastboot flash recovery <name of recovery .img>
There's plenty of stickies and information in this forum, which I won't re-hash here.
The stock recovery WILL show the android with the red triangle. To get into recovery from there, I believe you need to hold the up volume key. Other recoveries shouldn't do this though. Perhaps you should try using ROM Manager or Goomanager to flash a recovery from within android.
It took several attempts - flashing stock, then cwm, from the toolkit, before cwm finally "took". It's all working now.
I seem to be another victim of this issue. I was attempting to update my recovery (TWRP 2.6 installed) on my Verizon S4 via TWRP's app. It failed, so I figured I might try it from recovery. I attempted to boot into recovery, but it is stuck at the Samsung "custom" screen and the blue "RECOVERY BOOTING......" text is in the top left corner. I can leave the device alone for several minutes and it never goes into recovery. It does get very hot though, and occasionally it will reboot on its own. If I hook it up to my PC and then put in the battery, it will vibrate as if it is going to boot, then it vibrates again in 3 seconds and does this endlessly with nothing coming up on the screen. Without being able to get into recovery or have my desktop recognize the device, I'm not sure what to do. Any ideas before I chuck this brick?
Are you able to get into download mode (volume down, home button, power)? If you're able to, the device is not bricked and, using Odin, you can update TWRP to 2.8.4.
I've found that the app isn't working all that well. For the last few updates I've had to use Odin to update TWRP.
Strephon Alkhalikoi said:
Are you able to get into download mode (volume down, home button, power)? If you're able to, the device is not bricked and, using Odin, you can update TWRP to 2.8.4.
I've found that the app isn't working all that well. For the last few updates I've had to use Odin to update TWRP.
Click to expand...
Click to collapse
Ah ha, you are correct. I actually tried a variation of this (I think with volume up?) but it just attempted to go into recovery again. At the download screen I just told the phone to boot into the OS and all seems well. I'll look into updating TWRP via Odin and see if I have any joy, but at least I have a working phone again. Thanks for the help.:good:
When you update, do NOT try to use TWRP 2.8.5.0. It's bugged on the S4. Use 2.8.4.0 instead.
Thanks, good advice!
Looks like my recovery is toast. Doing some research, I never used Odin as my phone had the old MDK baseband. Sites tell me not to use Odin, so I followed the instructions on TWRP's site using Terminal Emulator and 2.8.4.0: http://teamw.in/project/twrp2/181 Everything seemed to go well, so I attempted to reboot into recovery, but now I get some warning/error about unauthorized software, turn off your phone and take it to Verizon, etc.
Sounds like I need to try again, but I'm not sure what my options are now.
I didn't even see you had a Verizon S4 until you mentioned it. Verizon encrypts the bootloader as a matter of course, and thus installing TWRP is not possible. You should however be able to restore the official firmware with Odin, and from there, follow the root guides at http://forum.xda-developers.com/galaxy-s4-verizon to get yourself back up and running.
mine get to the point where i select volume up, i see the android bot and message do not turn off target, and it shuts down. what do i do?
Hello All -
My wife got a new S7 Edge, so I thought I would update from my N2 to her N3.
I originally rooted it before the bootloader got locked down, flashed a stock modified KK 4.4.2 ROM, and prevented further OTAs.
I can't recall if I installed a custom recovery, so i tried it and in the upper left hand corner it says Recovery Booting..., it fails to enter recovery mode and then rebooted normally.
So I installed Safestrap, booted into recovery, and backed up the Stock ROM slot. I then did a Factory Wipe and Advanced Wipe the system partition as per the instruction to install Jasmine ROM.
I choose then chose reboot into Recovery again so that I could use the SD Card to install Jasmine. Unfortunately, I'm stuck in a bootloop where it says Recovery Booting... and never gets back into Safestrap.
I've tried holding down the Power Button, Volume Up or Down, and Home and I can't get into recovery or download mode.
I also tried using a USB Cable plugged into my PC and the button combo thing, but no luck.
Any ideas guys?
Thank you in advance!
Pull the phone battery.
Wait 5 or more seconds.
Reinsert battery.
Start phone with Vol-Down + Home + Power. (as if you wanted to use Odin Download mode)
When the "do you really want to do this?" dialog pops up, select cancel.
This will boot to the normal OS (and also clear the boot communication block so that the next time you reboot it doesn't try to boot the recovery again)
For some reason this sequence won't work if you omit the battery pull. (Don't leave it plugged in to USB or a charger, either)
It works this way with MJ7 firmware; since this is a bootloader behavior, it is possible that it won't work the same way with later firmwares. Simple enough to try and find out though.
good luck
Good news!
I was about to select download mode finally, but only after I removed the SIM card!!
I odin'd 4.3 stock, towel-rooted, safestrapped, and installed Jasmine.
Thanks again all!
Happy, happy, happy! Since I got it to work, thought I'd share.
~ caveat emptor, not responsible if this doesn't work for you ~
First off, I followed this very helpful post from DeeXii:
https://forum.xda-developers.com/note-4-tmobile/general/recovery-n910t-t3-marshmallow-pe3-guide-t3406870
I had flashed the N910TUVS2EPK2 stock from Odin after screwing up my phone doing other crap. In any case, after doing that, I obviously wanted root again! Note that this wasn't immediate - I flashed to this a couple months ago, so have been fully setup with gmail, and other account settings. So, the above link gave the best overall, simple step-through, with handy download links. It worked, and even better didn't lose any of my settings. (but, no guarantees, make sure you've backed up!)
Additional details that would be helpful:
- make sure you run Odin as Administrator.
- Odin: click the button next to AP, and then go select the twrp archive you downloaded
- Power off phone, hold boot into download mode (power, home, volume down at same time). click volume up when it says so.
- connect to Odin. you need to see the square just below ID:COM turn blue.
- Click Start to flash the twrp.
- IMPORTANT: after it flashes, the phone will auto-restart. *Quickly* pull out battery before it boots, otherwise it will put back stock recovery on you. (this happened to me - I had waited until it had fully booted, then powered down, then brought it up in recovery mode, and it wasn't twrp! - so remember, pull out battery right after it cycles after flashing)
- Put battery back in, and then boot into recovery by holding power-home-volume up simultaneously. If you end up seeing the nice pretty twrp squares, then this worked. It is interesting that there is also a message here stating that the kernel may very well write back the custom recovery. So, can't say if this will be permanent or not, but at least you can now flash the supersu. (subsequent reboot into recovery still seems to have twrp, so groovy!)
- (presuming you had already put the supersu on the sd card or internal memory - I used the systemless supersu), click install, select it and flash.
- just for kicks (not sure if this was needed or not), after flashing I saw an option to wipe cache/dalchik, so I did that too.
- rebooted (it took awhile, had to 'optimize' all the apps, etc.) - and I'm rooted!
If anyone has been trouble with specifically the N910TUVS2EPK2 build, then I hope this helps.
Thanks man, had the same issue. I figured it might be something to do with booting int OS. Sure enough with 6.0.1 EPK2 rom you MUST load into boot recovery right after flashing TWRP as you stated.
Something went wrong with my OTA update of EPK2 and it started to bootloop( 2 vibrates upon restart and then random amount of bootloops, and then random, soon-coming freeze upon loading in OS and continuing boot-looping) sometime after the update. I erased most of the old stuff via TWRP reinstalled EPK2 bootloader separately and then flashed EPK2 rom and it seems to be OK so far (knock on wood). We'll see hopefully it's not hardware issues like many people were reporting with bootlooping.
Can't you just uncheck the Odin option to reboot instead of the frantic battery pull?
Just wondering, as I'm going to do this later- thanks!
Steven.RN
Followup: Yep. Slip over to the options tab in Odin and uncheck "auto reboot". After Odin flashes TWRP, (the bar is all the way across the download screen, and the Odin Log says "succcess") go ahead, disconnect the phone from USB. Do your battery pull, replace battery. Close up the phone, then hit Volume up, home, and power at the same time- Bang! TWRP screen.
Further note: first time I did this flash, it didn't work, it just stopped in it's tracks. Then I realized I had to enable "developer mode" by clicking on the build number in the "About phone" sections in settings 5 times, going into Developer mode (the new option will present itself in the menu on settings), then: enable OEM unlock and USB debugging. Odin will flash TWRP just fine after that. (Duh on me!)
planetjeff said:
Happy, happy, happy! Since I got it to work, thought I'd share.
~ caveat emptor, not responsible if this doesn't work for you ~
First off, I followed this very helpful post from DeeXii:
https://forum.xda-developers.com/note-4-tmobile/general/recovery-n910t-t3-marshmallow-pe3-guide-t3406870
I had flashed the N910TUVS2EPK2 stock from Odin after screwing up my phone doing other crap. In any case, after doing that, I obviously wanted root again! Note that this wasn't immediate - I flashed to this a couple months ago, so have been fully setup with gmail, and other account settings. So, the above link gave the best overall, simple step-through, with handy download links. It worked, and even better didn't lose any of my settings. (but, no guarantees, make sure you've backed up!)
Additional details that would be helpful:
- make sure you run Odin as Administrator.
- Odin: click the button next to AP, and then go select the twrp archive you downloaded
- Power off phone, hold boot into download mode (power, home, volume down at same time). click volume up when it says so.
- connect to Odin. you need to see the square just below ID:COM turn blue.
- Click Start to flash the twrp.
- IMPORTANT: after it flashes, the phone will auto-restart. *Quickly* pull out battery before it boots, otherwise it will put back stock recovery on you. (this happened to me - I had waited until it had fully booted, then powered down, then brought it up in recovery mode, and it wasn't twrp! - so remember, pull out battery right after it cycles after flashing)
- Put battery back in, and then boot into recovery by holding power-home-volume up simultaneously. If you end up seeing the nice pretty twrp squares, then this worked. It is interesting that there is also a message here stating that the kernel may very well write back the custom recovery. So, can't say if this will be permanent or not, but at least you can now flash the supersu. (subsequent reboot into recovery still seems to have twrp, so groovy!)
- (presuming you had already put the supersu on the sd card or internal memory - I used the systemless supersu), click install, select it and flash.
- just for kicks (not sure if this was needed or not), after flashing I saw an option to wipe cache/dalchik, so I did that too.
- rebooted (it took awhile, had to 'optimize' all the apps, etc.) - and I'm rooted!
If anyone has been trouble with specifically the N910TUVS2EPK2 build, then I hope this helps.
Click to expand...
Click to collapse
thanks for the info, might give it a shot tonight. you have a link to the software update so i can load it with odin?
Thanks for the post. Where can I find the stock N910TUVS2EPK2 ROM?
Charlie Rock said:
Thanks for the post. Where can I find the stock N910TUVS2EPK2 ROM?
Click to expand...
Click to collapse
sammobile.com
Sent from my SM-N910T using Tapatalk