Hi Guys,
I’m stuck somewhere in the middle of root access. I was having problems with weak phone signal so I was advised to change the kernel.
I followed the procedure correctly but this led to the phone running hot, rebooting itself from time to time and occasional freezing.
So I want to start a fresh, backup some of my data files (can’t use titanium as it’s asking for root access) and then flash the saber kernel and probably also a new rom.
In Superuser the root access is green so I presume this is okay however there are no apps in the approved list… When I go to root checker or any other app requiring root they just whir and do nothing.
ROM manager tries to flash custom recovery but it just gets stuck at 100% flashing until I touch the screen
Holding up+home+power just keeps re-booting the phone without going into custom recovery and I can’t use mobile odin as it gets stuck checking root access!
I’ve been flashing roms for many years so I’ve no idea what’s going on here! Any help would be greatly appreciated,
Cheers,
Andy
Related
Hi all,
I'm new to trying to root the E4GT and I've gotten in a bit of a jam. I don't think I'm completely borked because I can still easily get the phone into download mode or Clockwork recovery, but I'm stuck on what to do next and I want to proceed carefully so I don't accidentally turn this into a hard brick.
Because I'm on Linux, not Windows, after reading up on rooting the E4GT I installed heimdall. It's not the most intuitive program in the world but I eventually worked out rooting it using "heimdall flash --kernel ~/path/to/zImage" where the "zImage" in question belonged to Zedomax v3 as linked from epic4gtouchroot.com. That seemed to work brilliantly as I was able to boot into what appeared to be a reset phone, now with a generic Android boot animation rather than the default Sprint advert, and I had the Superuser app.
From there, I decided to try Strongsteve's Odex blue and I booted into Clockwork. Without even thinking about it I wiped the factory data and cache partition, and then started looking into what I needed to do, only to learn that my external SD was going to be inaccessible from here so I had the .zip file in the wrong place. I proceeded to reboot my phone to set things right but I was shocked when the phone simply appeared to turn off after the (new, rooted) boot animation played. The phone then becomes unresponsive until the battery is pulled, at which point it becomes responsive again.
Because it boots the Samsung logo (with the yellow warning triangle) and part of the boot animation, I have plenty of time to get it into download mode or Clockwork, but I don't know what my next move is. I guess (based on a bad experience with trying to root a Kindle Fire) that this is still recoverable, though. Should I just flash a stock/stock rooted ROM? Reflashing the Zedomax kernel doesn't seem to work like it did before. Has anyone encountered this? Does anyone have a link to a recovery method that should be reliable in this situation? Thanks in advance and please remember LINUX -- i.e., no Odin.
[[ PS - I pretty much described the whole process above, but in case anyone was wondering, let me explicitly state I do not have a working nandroid backup. I only got Clockwork after rooting successfully, and I didn't think wipe data/cache was potentially a brick! :\ ]]
UPDATE: Solved! I was able to successfully flash the zImage from the stock rooted kernel here. Phone is working (and rooted) once again!
Hi all
I unlocked and rooted my Galaxy Nexus (Verizon) phone months ago and recently have struck a very weird prob. I had been swapping ROMs for a while, when recently the phone bricked on a ROM switch and would not go past the loading part of any rom I tried. I used RootKit to flash it back to the manf. Rom and that seems to have worked. The problem is though that my phone can not update (to manufacturer jellybean update, It starts but then hits red triangle android) or even flash clockwork recovery image. Every time i try any Recovery installer it just freezes up and says the app is not responding. Additionally though I have rooted and unlocked the phone and have superuser app, root checker tells me my phone is not rooted.
Please help
Thank You
1) stop using toolkits. you have no idea what it is doing, and sounds like it didnt really root your phone
2) return your phone to stock with this: http://forum.xda-developers.com/showthread.php?t=1626895
3) root your phone with this: http://forum.xda-developers.com/showthread.php?t=1529058
Hey guys, I'm new to XDA, so I hope I'm not being a noob . Just today I rooted my note 2 (international version) with Odin. After that I did the following: installed adaway, installed triangle away (and reset my counter), installed rom toolbox lite and through that changed the system font, after it asked me to reboot to finalize it and my phone hasn't turned on since. I had rebooted multiple times between rooting and changing the font, so I don't think the problem in with triangle away or adaway (but I can't be sure). My phone is just stuck on the pulsing samsung logo. What I have tried so far: redoing the root process through odin, taking out battery and restarting, trying to reset through the recovery menu and wiping cache.
Is it possible that my phone is in brick? Any suggestion? I'm hoping the fact that I can access the recovery menu is a good sign!
Any help would be greatly appreciated,
Thanks so much!
It's not bricked since you can still get to recovery and download modes!
I tried looking around on the net a little and there are some reports of bootloops after using Rom Toolbox to change the font, so that might be the problem here.
I would just re-stock and re-root with Odin and not use Rom Toolbox to change the font.
Ok guys I am pretty sure I fubar'd my tablet.
I am stuck in a recovery loop. When I start the tablet it just goes back into recovery. Which if I still had TWRP I think I could still do something, but I flashed cyanogen recovery trying to flash cm13 since I cold not get anything else to work. I cannot boot into download/firmware update screen. The screen just flickers a little and goes dark.
A little background:
Started when tablet forced install of 5.0 update and I was in a recovery loop. I flashed 410 test build, rooted, flashed twrp, installed stock rooted ROM. Everything was fine. Then tablet did it again, this time I just flashed rooted ROM and factory reset. Even took the steps to fix the white lines and storage issues. Was working fine. Got home a few days ago and I was in a recovery loop again. But now I don't have the bootloader screen/download mode/firmware update screen (whatever you want to call it) so last night i tried to download cm13, Gapps and cyanogen recovery with no avail.
I can access adb on my PC while in recovery, but when I try to access ADB shell I get unauthorized something or other. Because I cannot authorize USB debugging, because ROM won't boot. I tried to flash stock rooted ROM from cyanogen recovery and it says not signed or something like that.
Does anyone have any ideas? I really think I have screwed the pooch here.
sent from a device using an app
title
if you have a stock recovery image flashing it is easy, i had a LOT of troubles with my v410 and still am working with it. i have mine rooted, just with TWRP though, i cant use xposed framework, which negates why i rooted this in the first place. anyway, through much grit and determination flash your stock image after wiping what needs to be wiped and doing all other necessary things. Then, you must download kingo root, supersu, superuser. flashify would help with the flashing i hear, but it has troubles with the v410. kingo root was an apk i managed to find buried under a million viruses on the 34th page of google..or something. rooted mine in one click, from stock to reboot to twrp root.. many glitches.
I need help myself, deleted my "Phone" system app, causing me to lose connectivity with my data plan. cant seem to restore it, and flashify nor twrp has been able to flash a custom recovery, or a backup, im at a loss.
Help? We seek the same thing.
Ok but how do I flash the stock recovery image. I can't use fastboot. ADB says I am unauthorized.
sent from a device using an app
Anyone have any other ideas?
I am at a complete loss. I am by no means a developer, but I do know my way around. I really think I have FUBAR'd this one.
Kind of stinks, I give up. Anyone want a bricked v410?
Sent from my Galaxy Tab 2 using Tapatalk
Hi, so i got someone to root my phone to enable a safetynet pass on an app with Magisk
Suddenly now as soon as the screen turns off via sleep or lock it myself, I will boot into TWRP recovery.
This is becoming a huge problem for me now so im trying to find a solution asap.
Do i unroot my phone and just reset it all to norm? If so how do i go about doing this step-by-step as im not too entirely familiar with root which is why i got someone else to do it.
Re-flash the stock recovery. Even I was facing this kind of issue after rooting. I wasn't able to get my Mix 2 booted after installing TWRP for rooting. However, I got it solved by re-flashing stock recovery.
I was long time ago, but I think it should work for your as well. In you want to root your Mix 2, instead of flashing TWRP, boot it right away, flash magisk to get root access & reboot, you should not get any such bootloop issue whatsoever.