Hey guys.
So I recently went back to stock using the KDZ method. Once on stock, I took a couple of OTAs to get to 4.4.2. Now I want to root, so I picked up ioroot25 and tried it out.
The problem is that when I go through the process in ioroot, the phone reboots to go into recovery and all that happens is I get a screen with the little android icon knocked over, and ioroot says device not found.
Anybody have any ideas that might help? It'd be much appreciated. Thanks!
Anybody have any idea? It's really frustrating.
Related
EDIT: okay I found the stock rom, but my problem persists, so I'll just state the issue im having and hopefully someone who knows what theyre doing can tell me where I screwed up lol.
So, I had my Sprint S4 on MDC, was rooted with CF auto root, and had TWRP recovery.. I let my little brother play with my new phone, and he saw the lil update notification in the tray, so he updated to MF9 for me... That didnt go as planned.
After the update, my phone rebooted, and went all the way to the sprint logo, and stuck there. for about an hour. My device got reeaaallly hot so i popped the battery out, since power buttons werent responding. Put the battery back in, and same problem. SO, I got the stock rom, and booted it with Odin. It booted to recovery, then rebooted and stuck on the Samsung Galaxy S4 splash screen. I did the stock rom again, did the same thing. Now im stuck on the samsung splash screen and I have no idea what to do
dannyblunts said:
EDIT: okay I found the stock rom, but my problem persists, so I'll just state the issue im having and hopefully someone who knows what theyre doing can tell me where I screwed up lol.
So, I had my Sprint S4 on MDC, was rooted with CF auto root, and had TWRP recovery.. I let my little brother play with my new phone, and he saw the lil update notification in the tray, so he updated to MF9 for me... That didnt go as planned.
After the update, my phone rebooted, and went all the way to the sprint logo, and stuck there. for about an hour. My device got reeaaallly hot so i popped the battery out, since power buttons werent responding. Put the battery back in, and same problem. SO, I got the stock rom, and booted it with Odin. It booted to recovery, then rebooted and stuck on the Samsung Galaxy S4 splash screen. I did the stock rom again, did the same thing. Now im stuck on the samsung splash screen and I have no idea what to do
Click to expand...
Click to collapse
Go to recovery, do a factory reset, reboot.
Bt I doubt he was able to update you to MF9 since you were in MDC I believe he updated you to MDL.
Edit: here a stock tar of MF9 if you need it. http://forum.xda-developers.com/showthread.php?t=2375523
Sent from my SPH-L720 using xda app-developers app
I'm not sure that will work but it's worth a try. You might have to just use PC Odin and do a full flash then reroot it and get it to where you want it.
Long story short (I can go into more detail if needed):
Had a stock rooted rom with a zv8 radio/modem on sprint. I successfully flashed the Optimus 2.2 rom with the new ZVA (Sprint Spark) modem and everything was fine and dandy and working perfectly for a few hours. Then i was a dummy and restored apps from my previous roms using mybackup and one of those apps was the xposed installer with a few different modules.
Phone froze, rebooted and would no longer attatch to a network. No signal, just a red x. No radios work, not even wifi or bluetooth. If the screen goes blank the phone will freeze and bootcycle. Or if it is on for more then a minute, it will freeze and turn off and get stuck in a bootloop.
Recovery worked. I tried everything. Flashing other roms, with the appropriate radios of course, and restoring my backup with the appropriate radio. Nothing works, and ive had the same issue with each and every rom and radio.
I finally whipped out lgflashtool and returned to stock unrooted to no avail. Same issue, except now my touchscreen is not responsive, which means no adb to reroot and the pc doesn't recognize the phone while booted. Now im aware of a method using Ubuntu to get a custom recovery on these when all else fails, but is it worth my time if there is no fixing my issue?
Also, how much can you do with the lgflashtool? Can i flash different radios or root using it?
Worst case scenario i will take my phone to sprint and get a warranty replacement. The only issue with that is, while the rootchecker in download mode shows "unrooted" , the boot animation on the stock .tot image is an lg one, not the Sprint logo one and i feel like the service person would catch on. Any idea on how to change that as well?
Thanks in advance guys! Im kind of freaking out that im running out of options.
Bump
dantheman9703 said:
Long story short (I can go into more detail if needed):
Had a stock rooted rom with a zv8 radio/modem on sprint. I successfully flashed the Optimus 2.2 rom with the new ZVA (Sprint Spark) modem and everything was fine and dandy and working perfectly for a few hours. Then i was a dummy and restored apps from my previous roms using mybackup and one of those apps was the xposed installer with a few different modules.
Phone froze, rebooted and would no longer attatch to a network. No signal, just a red x. No radios work, not even wifi or bluetooth. If the screen goes blank the phone will freeze and bootcycle. Or if it is on for more then a minute, it will freeze and turn off and get stuck in a bootloop.
Recovery worked. I tried everything. Flashing other roms, with the appropriate radios of course, and restoring my backup with the appropriate radio. Nothing works, and ive had the same issue with each and every rom and radio.
I finally whipped out lgflashtool and returned to stock unrooted to no avail. Same issue, except now my touchscreen is not responsive, which means no adb to reroot and the pc doesn't recognize the phone while booted. Now im aware of a method using Ubuntu to get a custom recovery on these when all else fails, but is it worth my time if there is no fixing my issue?
Also, how much can you do with the lgflashtool? Can i flash different radios or root using it?
Worst case scenario i will take my phone to sprint and get a warranty replacement. The only issue with that is, while the rootchecker in download mode shows "unrooted" , the boot animation on the stock .tot image is an lg one, not the Sprint logo one and i feel like the service person would catch on. Any idea on how to change that as well?
Thanks in advance guys! Im kind of freaking out that im running out of options.
Click to expand...
Click to collapse
try to flash kdz via flash tools
gembo said:
try to flash kdz via flash tools
Click to expand...
Click to collapse
I've done this. But I found one from a new source and I'll try it again. Would I need to flash the radio again? Thank Thank you for the help.
Hello folks,
I have a S4 that I rooted back when it first came out. I'm on 4.2.2, I337UCUAMDL and want to update to hopefully stock 4.4 but with root and the ability to change to a custom rom later on. What's my best course of action?
Is there a stock rom that's basically pre-rooted and without Knox, or should I OTA to 4.4.2 and use Towelroot and Safestrap? I'll preface this a tad by saying that I currently can't seem to load CWM Recovery via ROM Manager. SU keeps force closing and I think regular recovery boots instead. I would assume there's a way to load it manually, like ODIN or something, but I'll cross that bridge when I get to it.
Thanks for your time and sorry if someone has asked this before! I couldn't find anything with some quick searches.
EDIT - I actually got CASUAL to fully process (kept hanging before) and got TWRP installed. So I guess my only question now is what ROM to load?
Hello Folks,
Looks like I borked my Note 3 tonight. Was attempting to install a new ROM and things didn't go well at all.
Phone was last running BajaROM 4.4.2 with Safestrap as a virtual recovery.
After a failed install of a new ROM from SS, I tried restoring from the backup file I just made tonight before upgrading the OS. Failed. Then, from SS, I wiped the phone and attempted to install the old AllianceROM, and it too, failed. When I went to reboot phone to see what would happen it simply loops the custom Note 3 screen, then blue text Recovery appears in the upper left hand corner, then repeat. Can't boot into recovery, and now, can't get back to Safestrap. All I got is Download mode when I pull the battery and hold Power/Volume Down/Home when I reinsert battery.
I'm following the guide at this link currently, http://forum.xda-developers.com/showthread.php?t=2483380, but have to wait over an hour for the stock Android firmware to download from one of the few hosting servers that still have one of them loaded.
In the meantime, is there anything else anyone recommends? This is my primary device so I'm kinda screwed till I can get it back up again. Any additional info would be appreciated.
Thanks.
For anyone reading who might be in a similar predicament, the soft-brick fix at the link above got me up and running again. Got the Note 3 running on stock OF1/5.0, rooted, and am now looking into unlocking bootloader so I can properly upgrade to 6.0.
A little disappointed no one bothered to respond in what could've turned into a bad situation, but the site itself did bail me out so no big complaints. Thanks to all the devs for their hard work.
Hi,
I have a rooted nexus 6p, all was well until it decided to reboot and boot-loop when I opened my music app. I get as far as the white Google logo then the phone restarts and I'm back to the normal warning then Google logo then reboot.
I have managed to get into the recovery screen (with the android laying down) but when i choose recovery mode the phone just starts boot-looping again.
I am wondering if I have somehow managed to hard brick it?
I have tried to flash the latest OS onto my phone but it said no signature.
I did managed to wipe the device also.
Thanks for any help.
Are you on Nougat or still on MM? Since you're rooted, it means you didn't receive an OTA. Did you flash it yourself, originally?
istperson said:
Are you on Nougat or still on MM? Since you're rooted, it means you didn't receive an OTA. Did you flash it yourself, originally?
Click to expand...
Click to collapse
When my phone started playing up I was still on MM 6.0.1, I tried to flash N after the boot-looping started.
Thanks