Hello! This is my first time rooting a phone.
I was following the official Magisk guide, successfully unlocked the bootloader and used the Magisk mobile app to patch the AP tar file (I checked the Recovery mode checkbox since it was showing no ramdisk). I am sure I downloaded the right firmware. Everything went great. Then I pulled the patched AP tar, opened Odin, selected the BL, CP, CSC and the patched AP and hit start. After that my phone rebooted and the first time setup showed up. I thought everything was great, until I realized that the touchscreen is not working. The Volume keys and the Power button work, but I can't use the touchscreen. I tried holding the Power key so it restarts but seems like that doesn't work while in the Setup. I held down the volume keys (which made a TalkBack popup appear which I can't remove) and a lot of key combinations in hope something would happen, but nothing. The phone is currently at about 80% battery, if that matters. I'll be leaving it unplugged for now.
EDIT!: Managed to setup the phone by rebooting normally. Though, the Magisk app showed N/A for Installed, so I read the guide again, and since the phone shows no ramdisk I held the recovery key sequence and when the splash screen appeared I stopped holding the buttons, and it successfully booted! But the touch still DOES NOT WORK!
Thanks for anybody who helps, since it's my first time doing this, and also the first time I'm posting here.
Just for your information, the phone automatically shut down so I powered it back on again in hope that this time the touchscreen works but still nothing.
Related
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?
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
Hi all,
I have a weird problem with my Galaxy S4 (i9505) as follows:
-The screen was broken, then replaced the screen and worked for fine so I upgraded the phone to the offered 5.0.1 OS.
-It worked fine for two days, and then suddenly turned off, and kept stuck on Samsung Logo.
-It only could go to Download mode, but never to Recovery mode.
-If connected to the wall charger, it keeps vibrating and displaying the battery symbol alternatively for ever.
-I tried every all the tricks I could find on the forums such as
----Using a new battery
----Writing the official firmware 4.4.2, 5.0.1, recovery firmwares (4 files AP, BL, CS, CCS), all completed successfully.
----Tried PIT files (disparately reset NAND).
-It kept showing "Memory Booting ..." message either when starting normally or with Recovery mode.
-Installed TWRP (latest) and then it showed "RECOVERY BOOTING ...", "RECOVERY IS NOT SEANDROID ENFORCING", " Set Warranty Bit : recovery".
-Lastly installed official firmware 4.4.2 and again showing "MEMORY BOOTING ...".
Your help is tremendously appreciated.
Also, I've noticed that I can go to the download mode only by pressing (Power + Vol Down) buttons, without the need to press the Home button, does that mean that the Home button is already pressed all the time (could be a faulty screen?).
I have an s4 sgh-i337m that will also go into download modem by only pressing volume down and power. The phone does function properly and I can get into recovery without any issues.
audit13 said:
I have an s4 sgh-i337m that will also go into download modem by only pressing volume down and power. The phone does function properly and I can get into recovery without any issues.
Click to expand...
Click to collapse
Thanks audit13, now the possible home button issue has been eleminated.
Any other suggestions?
Have tried flashing the stock rom with Odin 3.07 as a single tar file in the pda slot and performing a factory reset before letting the phone both for the first time?
When booting to recovery, are you letting go of the power button after the phone starts to boot?
Yep, I did all possible firmwares 5.0.1, and 4.4.2 either in one file or in 4 files, also I've tried every possible combination but didn't let me into Recovery mode.
Sounds like there may be something wrong with the phone's internal memory.
Only thing I can suggest is getting the phone flashed via jtag.
audit13 said:
Sounds like there may be something wrong with the phone's internal memory.
Only thing I can suggest is getting the phone flashed via jtag.
Click to expand...
Click to collapse
Happy to do anything in this stage, any guidelines about this jtag (never used before)?.
Thanks a lot
You'll have to take it to a cell repair shop to flash it.
I attempted to root my Galaxy Tab A 10.1 WI-FI (SM-T580), and something went wrong.
I'm very new to the android scene, and was trying to use odin to install twrp.
The install passed, and my tablet rebooted, but I didn't press up, home, and power in time, and it started the regular boot process.
I powered it off, and tried to boot with the power up, home, and power button combination, but when it booted, the tablet went to a screen with hundreds of little horizontal streaks.
I am still able to boot into the power, home, volume down combination (where you can install a custom os), but I have no idea what to do from here.
could someone please walk me through what I have to do to get my tablet back to a working state?
I'd prefer to have root access if possible, but as of right now my only concern is not owning an expensive brick.
I attempted to follow Tech Alpha's video, which was posted at the beginning of this year (February 17, 2018), and it didn't work.
I tried to use Odin3_v3.12.7 to install twrp-3.1.1-0-gtaxlwifi.img.tar to my device. and that's where the problem started.
Thanks in advance for any help with this problem.
edit:
I fixed the problem, as it turns out, all I needed to do was search for an updated version of TWRP, and it worked fine.
So I updated my rooted 6t to Android 10 using Magisk, and everything went as expected prior to rebooting. I hit uninstall and restored images via Magisk, downloaded and installed the Android 10 update package to the inactive slot, downloaded the TWRP A/B partition module then finally installed Magisk to the inactive slot as well. Finally, from there I rebooted and it seemed to boot normally, hung a bit longer on the animation than normal but no more than 30 second or so.. it then skipped the lock screen and went straight to my wallpaper (the same one i has set, not default) BUT the system doesn't start. No icons. Can't pull up the app drawer, can't pull down the notification menu. No notification bar... Nothing.
The only thing I can do is restart the phone by holding PWR button but that just brings me right back to the same deal. I tried fastboot>TWRP recovery and was able to determine that all the system data is in fact present anyway but rebooting from TWRP also lead to the same situation.
I'm asking for advice BC the last time I messed around without knowing fully what I was doing, I hard bricked it. I'm using Blu_Spark TWRP if that makes any difference at all...
It's possible that I just need to wait longer, I read a number of reports of pixel users needing to wait hours after OTA updates but they were stock on the boot logo/animation. I'm beyond that point, only it skips the lock screen, goes straight to my wallpaper and that's it. I can't do anything at all from there.
PLEASE HELP?
Thanks!
QNE
Use MSM tool.
Download MSM tool. Unzip it on PC desktop. ConnectUSB typC cable to PC. Shutdown your OnePlus 6. Open msm download too. Click start. Press volume up and dn key simultaneously(don't touch power button). Now connect cable to phone. Progress bar of MSM download too will be active. Let it completed. Phone will boot to os. Now upgrade to Android 10. That's it.
I ended up factory resetting prior to your response, but thanks just the same. Fortunately, I didn't lose root which was my main concern anyway so no harm done. Thanks again!