Soooo.... I rooted my Samsung Galaxy S4 (SCH-I545), then I decided to install a custom ROM since the default TouchWiz rom is slower than a turtle stuck in a pile of wax. I installed Safestrap 3.71 (TWRP v2.6.3.1) and by mistake flashed my stock rom. Now my phone won't boot into any ROM since that is corrupt, but it still boots into recovery (that's a good thing I suppose). I have tried a number of Safestrap compatible roms (omni, cm, beanstalk) but they either end up giving me a black screen or a very weird looking pixelated blue/cyan screen. I have to remove the battery to reboot my phone. I tried using adb to wipe the data aswell but nothing works beyond recovery.
I have to rely on adb to push and pull data to and from the phone.
I was hoping if anyone had any idea what I should try to do next?
Probably best just to restart by flashing the stock firmware back to it with Odin.
Make sure you don't try to downgrade the firmware vs what you have now, as that can create a lot more issues than you want to deal with.
Snake2k said:
Soooo.... I rooted my Samsung Galaxy S4 (SCH-I545), then I decided to install a custom ROM since the default TouchWiz rom is slower than a turtle stuck in a pile of wax. I installed Safestrap 3.71 (TWRP v2.6.3.1) and by mistake flashed my stock rom. Now my phone won't boot into any ROM since that is corrupt, but it still boots into recovery (that's a good thing I suppose). I have tried a number of Safestrap compatible roms (omni, cm, beanstalk) but they either end up giving me a black screen or a very weird looking pixelated blue/cyan screen. I have to remove the battery to reboot my phone. I tried using adb to wipe the data aswell but nothing works beyond recovery.
I have to rely on adb to push and pull data to and from the phone.
I was hoping if anyone had any idea what I should try to do next?
Click to expand...
Click to collapse
Have you cleared cache?
If you are not able to flash a custom rom, I would recommend you to flash a stock rom and begin from new. Also if you are on Android 4.4 you cannot use any recovery.
Sent from my GT-I9505 using XDA Premium 4 mobile app
es0tericcha0s said:
Probably best just to restart by flashing the stock firmware back to it with Odin.
Make sure you don't try to downgrade the firmware vs what you have now, as that can create a lot more issues than you want to deal with.
Click to expand...
Click to collapse
I'm just gonna give the Hyperdrive ROM a go, if that doesn't work, I'll definitely just go back to Stock I suppose and see what happens next. Thanks!
ikuni123 said:
Have you cleared cache?
If you are not able to flash a custom rom, I would recommend you to flash a stock rom and begin from new. Also if you are on Android 4.4 you cannot use any recovery.
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yep I cleared everything, weird problem lol. Its not 4.4 cus Verizon never released any for their S4s, but I'll definitely just head back to stock after I give Hyperdrive a chance Thanks!
Snake2k said:
I'm just gonna give the Hyperdrive ROM a go, if that doesn't work, I'll definitely just go back to Stock I suppose and see what happens next. Thanks!
Yep I cleared everything, weird problem lol. Its not 4.4 cus Verizon never released any for their S4s, but I'll definitely just head back to stock after I give Hyperdrive a chance Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2634408
According to that, only 13 is supported. I dunno if the that thread hasn't been updated or whatever, but something to consider.
Related
Anyone have an idea why every time I install an aosp rom it glitches at the Samsung boot screen then just goes black and I have to pull the battery? I've installed clean, jelly beans and jedi Rom without issue. Any help is appreciated.
Update your twrp then try again. Make sure your doing full wipes and flashing gapps
Sent from my SCH-I605 using Tapatalk 2
hopesrequiem said:
Update your twrp then try again. Make sure your doing full wipes and flashing gapps
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Just updated my TWRP to 2.4 and did what you suggested with the wiping and same problem.
The Samsung Galaxy screen glitches to half way off the screen, then goes off, then comes back on then the whole thing goes black and nothing.
I'm going to try another rom and see if it still does it as well.
dudeicles said:
Just updated my TWRP to 2.4 and did what you suggested with the wiping and same problem.
The Samsung Galaxy screen glitches to half way off the screen, then goes off, then comes back on then the whole thing goes black and nothing.
I'm going to try another rom and see if it still does it as well.
Click to expand...
Click to collapse
Even with another ROM it doesn't seem to want to work. It's really weird, because any Touchwiz ROM works fine, it only does it on AOSP roms..... I'm hoping someone knows what the fix for this is.
dudeicles said:
Even with another ROM it doesn't seem to want to work. It's really weird, because any Touchwiz ROM works fine, it only does it on AOSP roms..... I'm hoping someone knows what the fix for this is.
Click to expand...
Click to collapse
Odin to stock then re unlock and try this all again? I'm not sure what else you can try. I flip between aosp and tw almost daily
Sent from my SCH-I605 using Tapatalk 2
The Note 2 that couldn't...
Sent from my SCH-I605 using Tapatalk 2
1ManWolfePack said:
The Note 2 that couldn't...
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Heh I think I can I think I can...I was thinken are you trying to flash the file that the post links to because thats not the right one you need to get the note 2 lte one tolte..just a though I downloaded the wrong one first but caught it
http://changelog.bbqdroid.org/#t0lte/cm10.1/next
in my experience, you need to do a factory wipe again AFTER you install or you will get a bootloop.
I think CM10.1 mentions that in their install process.
Acery said:
in my experience, you need to do a factory wipe again AFTER you install or you will get a bootloop.
I think CM10.1 mentions that in their install process.
Click to expand...
Click to collapse
Yeah it can't hurt even if they don't say that
Sent from my SCH-I605 using Tapatalk 2
Acery said:
in my experience, you need to do a factory wipe again AFTER you install or you will get a bootloop.
I think CM10.1 mentions that in their install process.
Click to expand...
Click to collapse
Would it help in any way to change to CWM when flashing my AOSP roms?
dudeicles said:
Would it help in any way to change to CWM when flashing my AOSP roms?
Click to expand...
Click to collapse
I would try cwm, I had a gs3 that couodnt flash anything with cwm but could with twrp, my note was the opposite, cwm was awful on it.
Just ran into something very interesting . When I installed Rom Manager and flashed the CWM recovery, I rebooted and my boot screen did the exact same thing it was doing installing AOSP roms. It would seem my problem may just be CWM.
dudeicles said:
Just ran into something very interesting . When I installed Rom Manager and flashed the CWM recovery, I rebooted and my boot screen did the exact same thing it was doing installing AOSP roms. It would seem my problem may just be CWM.
Click to expand...
Click to collapse
I've heard too many issues with cwm to even try it. Twrp has been flawless for me so why switch? If it ain't broke, don't fix it.
Sent from my SCH-I605 using Tapatalk 2
Ok, so update - Odin'd back to stock and re-rooted using the Casual method. I have the most recent TWRP installed and when i install the AOSP rom it does the exact same thing. I'm thinking about videotaping what the boot animation does and maybe someone can look at it and see what the cause may possibly be.
If anyone has any other suggestions i'm all ears. Again, any rom based on STOCK works without issue (Clean Rom, Jelly Beans and Jedi), but only AOSP roms (And CWM) crash the phone at "Samsung Galaxy Note II" screen on startup.
Thanks for the suggestions so far, just weird it's not working. I may have the single note 2 to never run AOSP roms. LOL
so... oddly enough i still have trouble installing AOSP roms. the only AOSP rom i have been able to install so far is Paranoid Droid. I am slowly trying each one just to see which one i can force to work. Am I the only person who can't just flash whichever rom I want whenever?
Anyone with other ideas on this? I was frequently flashing back and forth between TW and AOSP. The other day I tried to flash AOSP again and get a failed message in TWRP. Already using latest version of TWRP. I then restore a backup of TW. Download again, verify md5, get failed message again. And yes, I wiped everything...same thing I do everytime. Now I have tried to DL and flash multiple different AOSP roms and I get failed everytime. Decided to try CWM recovery and that just aborts. I have NO problems flashing TW roms though
Follow the advice to Odin back to stock and start over. Otherwise, get a replacement and tell them it's acting weird and slow haha.
Sent from my SCH-I605 using xda app-developers app
Same here!!
spydersilk said:
Anyone with other ideas on this? I was frequently flashing back and forth between TW and AOSP. The other day I tried to flash AOSP again and get a failed message in TWRP. Already using latest version of TWRP. I then restore a backup of TW. Download again, verify md5, get failed message again. And yes, I wiped everything...same thing I do everytime. Now I have tried to DL and flash multiple different AOSP roms and I get failed everytime. Decided to try CWM recovery and that just aborts. I have NO problems flashing TW roms though
Click to expand...
Click to collapse
I currently have a Tmobile Note 2. And i recently ran into the same issue. I think it started after installing a certain paranoid andrroid rom, which wrote OS folders differently from what i am normally used to seeing. The folders were 0, legacy, and obb. I also notice that it changed my device id to an SGH-i317, which is an ATT Note 2. The rom was a port from an ATT rom of course, but if it was for ATT, it wouldn't work on my device right? I installed GOOmanager, and flashed the OPEN INSTALL SCRIPT. Which it flashed the ATT version. Everything still worked. I flashed back to stock, and updated OTA. Still nothing. I've also noticed that, if i can open the zip file on my pc, it will work on my phone. For some reason, The AOSP files read invalid. While the Touchwiz roms open like a regular zip file.
Any help is appreciated. Hope some of this info helps.
Just realized i posted in the Verizon section. But i think you and I are the only two people with this issue...lol
slinky42 said:
I think it started after installing a certain paranoid andrroid rom, which wrote OS folders differently from what i am normally used to seeing. The folders were 0, legacy, and obb.
Just realized i posted in the Verizon section. But i think you and I are the only two people with this issue...lol
Click to expand...
Click to collapse
This is standard on 4.2.2 ROMs. It is related to the multi-user implementation.
slinky42 said:
I currently have a Tmobile Note 2. And i recently ran into the same issue. I think it started after installing a certain paranoid andrroid rom, which wrote OS folders differently from what i am normally used to seeing. The folders were 0, legacy, and obb. I also notice that it changed my device id to an SGH-i317, which is an ATT Note 2. The rom was a port from an ATT rom of course, but if it was for ATT, it wouldn't work on my device right? I installed GOOmanager, and flashed the OPEN INSTALL SCRIPT. Which it flashed the ATT version. Everything still worked. I flashed back to stock, and updated OTA. Still nothing. I've also noticed that, if i can open the zip file on my pc, it will work on my phone. For some reason, The AOSP files read invalid. While the Touchwiz roms open like a regular zip file.
Any help is appreciated. Hope some of this info helps.
Just realized i posted in the Verizon section. But i think you and I are the only two people with this issue...lol
Click to expand...
Click to collapse
Did you ever get your phone to install the AOSP Roms? Mine worked when l just let the phone sit. Now it works fine all the time.
Sent from my SCH-I605 using xda app-developers app
Hey there,
Today I received an MHL-adapter for my Galaxy S3 and wanted to try it out. Since it didn't work in combination with Slim Bean I decided to flash another rom (more on the sammy side of things). Coming across a thread with a guy pointing out a so called Chameleon crossover rom, I decided to give it a go, downloaded and flashed it. I shat bricks as I saw that, in my euphoria to try the adapter, I flashed a rom that was meant to be for the Galaxy S2!
So I restarted into recovery and tried to perform a full wipe, which didn't work, because it wasn't able to load the partitions (data etc.) then I tried to flash on a recent backup of Slim Bean, which was only partly succsessfull, meaning, that it flashed but couldn't wipe because of the reason mentioned above.
Booting into system doesn't work either, I just get a bootloop.
Right now im not quite sure, which step to take. Shall i flash on a clean stock-image via Odin or maybe try out something like One-Click UnBrick?
All your help and suggestions are highly appreciated!
rockband said:
Hey there,
Today I received an MHL-adapter for my Galaxy S3 and wanted to try it out. Since it didn't work in combination with Slim Bean I decided to flash another rom (more on the sammy side of things). Coming across a thread with a guy pointing out a so called Chameleon crossover rom, I decided to give it a go, downloaded and flashed it. I shat bricks as I saw that, in my euphoria to try the adapter, I flashed a rom that was meant to be for the Galaxy S2!
So I restarted into recovery and tried to perform a full wipe, which didn't work, because it wasn't able to load the partitions (data etc.) then I tried to flash on a recent backup of Slim Bean, which was only partly succsessfull, meaning, that it flashed but couldn't wipe because of the reason mentioned above.
Booting into system doesn't work either, I just get a bootloop.
Right now im not quite sure, which step to take. Shall i flash on a clean stock-image via Odin or maybe try out something like One-Click UnBrick?
All your help and suggestions are highly appreciated!
Click to expand...
Click to collapse
Odion stock. If that fails you'll need to find and flash with a PIT
rootSU said:
Odion stock. If that fails you'll need to find and flash with a PIT
Click to expand...
Click to collapse
Thank you so much for the quick response, I'm going to check whether it works and report back after it's done! :good:
G'Luck
Problem solved, thanks rootSU!
So, if someone is following this thread, I just want to share with you guys what I did and how it turned out:
I flashed the original firmware, according to region etc. via Odin, the procedure was succsessfull and I rebooted.
At first I had a bootloop, so I went into the stock recovery and hit "wipe /data and /cache", which was succsessfull as well, meaning that the previous problem with not being able to mount the partitions was resolved. So I went ahead and rebooted again aaand it booted!
Everything is working fine as far as i can tell, no misfunctions, hot reboots or anything similar.
Thanks very much for the quick response rootSU, which prevented me from hyperventilating .
I've rooted, unlocked bootloader and flashed stuff on my former phones (Htc Wildfire, Galaxy S) and I've never done anything like that before and nothing like that ever happened to me. So to anyone reading this, I highly encourage you not to be as dumb as me and to doublecheck what rom you're flashing and not to flash while being overly exicted about anything .
Does your adapter now work?
Sent from my GT-I9300 using xda app-developers app
Never panic. Read lots and dont do anything you don't understand. That's my advice when you're in an S3 pickle
Sent from my GT-I9300 using Tapatalk 2
Very good advice
Sent from my GT-I9300 using xda app-developers app
Hey guys, I need help.
I consider myself fairly adept at handling rooted devices, but I have not been following development for the GS4 for the last several months and have been running the last release of Synergy before their hiatus.
I was going to try out something different. I always enjoyed Beanstown's Jelly 'Beans', and thought I would try Build 7.
Now I am stuck at the Samsug Galaxy Boot Logo and it never goes to the Custom Boot Screen.
WORSE...I managed to break my recovery...so it will not boot their either.
Only mode I can boot to is Download.
Maybe I am just blind but I searched and could not find any Odin flashable recoveries...does anyone have one? Is there a rooted MDK file out there that I can flash via Odin?
Someone please help
Did you do the proper wipes when flashing the new rom? There arent any odin flashable recoveries for the s4. I would probably use the no wipe mdk image to recover (wont lose any user data) since you have no custom recovery to flash something with. Youll have to start over but youll have a working phone at least.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Yes...I always wipe well when I am flashing. Almost every problem I have ever had going back to the Droid 1 was from a Dirty Wipe. I also tried searching for issues and warnings before moving forward...but did not find anything with my searches.
So just to be sure I have this right...start with this
http://forum.xda-developers.com/showthread.php?t=2301259&highlight=mdk
Then re-root as I did originally
http://forum.xda-developers.com/showthread.php?t=2290798
Then I can reflash CWM Recovery from Rom Manager? Will it automatically flash loki'd version?
Finally once there...can I just flash Beantown's Jelly Beans Build 7 or do I need to update the radios first? Can I use the just the MJ7 modem from the post below or do I need other parts updated too?
http://forum.xda-developers.com/showthread.php?t=2487298
Thanks all!
jbg25 said:
Yes...I always wipe well when I am flashing. Almost every problem I have ever had going back to the Droid 1 was from a Dirty Wipe. I also tried searching for issues and warnings before moving forward...but did not find anything with my searches.
So just to be sure I have this right...start with this
http://forum.xda-developers.com/showthread.php?t=2301259&highlight=mdk
Then re-root as I did originally
http://forum.xda-developers.com/showthread.php?t=2290798
Then I can reflash CWM Recovery from Rom Manager? Will it automatically flash loki'd version?
Finally once there...can I just flash Beantown's Jelly Beans Build 7 or do I need to update the radios first? Can I use the just the MJ7 modem from the post below or do I need other parts updated too?
http://forum.xda-developers.com/showthread.php?t=2487298
Thanks all!
Click to expand...
Click to collapse
Yeah looks like you got everything in order. Rom manager or rom toolbox will auto loki the recoveries. No need to update radios when flashing beans either. Itll already have the radios included unless your wanting to flash the mj7 radio seperately then I believe youll be ok doing that. I havent done alot of reading on the newest radios.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Back up and running with stock rooted MDK and CWM Recovery.
Now to try and flash a ROM.
jbg25 said:
Back up and running with stock rooted MDK and CWM Recovery.
Now to try and flash a ROM.
Click to expand...
Click to collapse
good deal just saw your pm was gonna say flash mdk odin but it looks like you found it
beanstown106 said:
good deal just saw your pm was gonna say flash mdk odin but it looks like you found it
Click to expand...
Click to collapse
Thanks for getting back to me! :good:
I am up and running...but with but not with 'Beans' Build 7 ... I have tried everything...and no matter what it stalls at the SGS4 Splash Screen and never progresses.
I thought maybe it was the new recovery I flashed ( CWM Touch Recovery 6.0.4.4) .... BUT I got Hyperdrive to install and boot. So maybe my SGS4 just doesn't like Beans...which sucks cause I ran that almost exclusively on my SGS3.
jbg25 said:
Thanks for getting back to me! :good:
I am up and running...but with but not with 'Beans' Build 7 ... I have tried everything...and no matter what it stalls at the SGS4 Splash Screen and never progresses.
I thought maybe it was the new recovery I flashed ( CWM Touch Recovery 6.0.4.4) .... BUT I got Hyperdrive to install and boot. So maybe my SGS4 just doesn't like Beans...which sucks cause I ran that almost exclusively on my SGS3.
Click to expand...
Click to collapse
Try TWRP 2.5.0.2.
Most of the devs use it.
Sent from my SCH-I545 using xda app-developers app
Mightycaptain said:
Try TWRP 2.5.0.2.
Most of the devs use it.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I downloaded and installed the latest TWRP 2.6.3.0 from DsLNeXuS's Recovery Tools App as Goo Manager is not finding a recovery for my device.
Still no good...nothing I do makes Beans Build 7 work ....
jbg25 said:
I downloaded and installed the latest TWRP 2.6.3.0 from DsLNeXuS's Recovery Tools App as Goo Manager is not finding a recovery for my device.
Still no good...nothing I do makes Beans Build 7 work ....
Click to expand...
Click to collapse
Go here. Get 2.5.0.2
http://techerrata.com/browse/twrp2/jfltevzw
Instructions
http://teamw.in/project/twrp2/181
At the bottom of the page.
Edit;
Or flash this in recovery
http://forum.xda-developers.com/showthread.php?p=45006486
I would reboot to recovery after flashing to make you got it on the right version.
Then make sure you can still boot back to your rom.
Then go back to recovery
Wipe
Factory reset.
Advanced
Check system, Data, davlik and cache
Wipe
Go back to main screen
Install
Fund your rom to flash.
Sent from my SCH-I545 using xda app-developers app
Me too. I tried the [ROM][TW4.3]STOCK-ROOTED-MJ7-AROMA-LOKI'd ROM with CWMR. Wiped Dalvik. Cache, Ractory Rest/Data. Seemed to install fine but then hung at "Custom". Fortunately I was able to a Nandroid Restore but not sure where this went wrong. Finally got TWRP to install after several failed GooManager attempts over the past month. May CWMR is the problem.
Hello I'm new here how is everyone?
Okay here is my issue:
I have a Verizon Galaxy S4 its on Android 4.3 with the build ending in mj7. It is rooted via the vroot method. So I've been looking around for a custom recovery so I could flash a ROM (preferably CM 11). I've came across a safestrap version that worked with my build (3.70). I downloaded the apk, installed it, installed the recovery and booted into recovery fine. I made my back up via the tool and also have a Samsung kies back up from before my root. So after I backed up my data I did my data wipe of the phone. The generic wipe my SD card and the data in it are good. Well long story short the phone turned off without installing a new ROM. Well phone powers on and stuck on Samsung logo with the open lock on it.
Was wondering can I..
A: Somehow force the safestrap to start via adb and restore my back up?
B: restore my back up through adb itself?
C: Use Odin to restore my stock firmware somehow even while rooted?
D: Sideload CM from adb?
E: I'm out of luck buy a new phone?
Thank you.
Fiftysilver said:
Hello I'm new here how is everyone?
Okay here is my issue:
I have a Verizon Galaxy S4 its on Android 4.3 with the build ending in mj7. It is rooted via the vroot method. So I've been looking around for a custom recovery so I could flash a ROM (preferably CM 11). I've came across a safestrap version that worked with my build (3.70). I downloaded the apk, installed it, installed the recovery and booted into recovery fine. I made my back up via the tool and also have a Samsung kies back up from before my root. So after I backed up my data I did my data wipe of the phone. The generic wipe my SD card and the data in it are good. Well long story short the phone turned off without installing a new ROM. Well phone powers on and stuck on Samsung logo with the open lock on it.
Was wondering can I..
A: Somehow force the safestrap to start via adb and restore my back up?
B: restore my back up through adb itself?
C: Use Odin to restore my stock firmware somehow even while rooted?
D: Sideload CM from adb?
E: I'm out of luck buy a new phone?
Thank you.
Click to expand...
Click to collapse
I beg all you new guys spend a couple hours reading some threads here...If I had a dollar every time some one posted about issues with trying roms NOT compatible with SafeStrap .
Again...no cm or asop base roms will work with safestrap...
Sent from my SCH-I545 using XDA Premium 4 mobile app
Fiftysilver said:
Hello I'm new here how is everyone?
Okay here is my issue:
I have a Verizon Galaxy S4 its on Android 4.3 with the build ending in mj7. It is rooted via the vroot method. So I've been looking around for a custom recovery so I could flash a ROM (preferably CM 11). I've came across a safestrap version that worked with my build (3.70). I downloaded the apk, installed it, installed the recovery and booted into recovery fine. I made my back up via the tool and also have a Samsung kies back up from before my root. So after I backed up my data I did my data wipe of the phone. The generic wipe my SD card and the data in it are good. Well long story short the phone turned off without installing a new ROM. Well phone powers on and stuck on Samsung logo with the open lock on it.
Was wondering can I..
A: Somehow force the safestrap to start via adb and restore my back up?
B: restore my back up through adb itself?
C: Use Odin to restore my stock firmware somehow even while rooted?
D: Sideload CM from adb?
E: I'm out of luck buy a new phone?
Thank you.
Click to expand...
Click to collapse
You should be able to use Odin to get back to stock MJ7. There are guides in the development section. Just so you know, you can't flash Cm 11 with Safestrap. As far as I know, the only ROM that works with MJ7 and Safestrap is Hyperdrive 11. Even if you're on an older base, you would only be able to flash TW based ROMs with Safestrap.
My suggestion, do A LOT of reading. There's tons of info on these boards.
Sent from my NCC 1701 Using Tapatalk 4
C; Google how to Odin back to stock.
Have you tried to boot the phone into recovery and restore your backup with SS? I never used SS but if you can make a backup I'm sure you can restore one as well
Sent from my SCH-I545 using Xparent Skyblue Tapatalk 2
I beg all you new guys spend a couple hours reading some threads here...If I had a dollar every time some one posted about issues with trying roms NOT compatible with SafeStrap .
Again...no cm or asop base roms will work with safestrap...
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You are correct and that is my mistake.
You should be able to use Odin to get back to stock MJ7. There are guides in the development section. Just so you know, you can't flash Cm 11 with Safestrap. As far as I know, the only ROM that works with MJ7 and Safestrap is Hyperdrive 11. Even if you're on an older base, you would only be able to flash TW based ROMs with Safestrap.
My suggestion, do A LOT of reading. There's tons of info on these boards.
Sent from my NCC 1701 Using Tapatalk 4
Click to expand...
Click to collapse
C; Google how to Odin back to stock.
Have you tried to boot the phone into recovery and restore your backup with SS? I never used SS but if you can make a backup I'm sure you can restore one as well
Sent from my SCH-I545 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
It worked. Didn't the first time but tried ODIN again with a stock mj7 ROM I found here.
I restored back to factory and implemented vroot once again, swapped out the Chinese (Korean?) superuser for our good old traditional one. I then re-installed safestrap apk and re-installed the recovery. I went in and found my back up I made earlier today and restored my phone back to how it exactly was before all this mess started.
Lesson learned I'll do my due-diligence next time and just keep my root till I can find a solid method to getting CM/Stock android on my Galaxy S4.
I'll try Hyperdrive 11
Thank you guys for all your help.;
Fiftysilver said:
I restored back to factory and implemented vroot once again
Click to expand...
Click to collapse
Why vroot? There is an open rooting technique - http://forum.xda-developers.com/showthread.php?t=2565758
Seems like you've got more reading to do.
***first of All I'm only making a new thread because I haven't found my specific issue anywhere else (even though its a common issue)***
SO...I need some help with my S4 ASAP!! I recently flashed a new rom (Hyperdrive 16.1 the link is: http://forum.xda-developers.com/showthread.php?t=2301724), Wiped Data/Factory Reset, Wiped cache and dalvik cache. I also did the format data where you had to type in "yes." I did it all in TWRP. Then after using my phone for a few hours I decided to reboot it. Now its stuck in the Samsung "Custom" screen with the lock (unlocked icon).
I cannot seem to be able to go into recovery mode as well. I'm not sure what build version my phone uses, and since I can't boot the phone i don't know what to do. What do you recommend I do? I was also using android 4.4.2....
Should I Odin back to factory and then re root?
This video seems to be very useful, and I want to follow it but what should i do if I don't know the build?
https://www.youtube.com/watch?v=GL8XwuRYoWU
Thanks for youre help XDA,
Dany
Danylevy12 said:
***first of All I'm only making a new thread because I haven't found my specific issue anywhere else (even though its a common issue)***
SO...I need some help with my S4 ASAP!! I recently flashed a new rom (Hyperdrive 16.1 the link is: http://forum.xda-developers.com/showthread.php?t=2301724), Wiped Data/Factory Reset, Wiped cache and dalvik cache. I also did the format data where you had to type in "yes." I did it all in TWRP. Then after using my phone for a few hours I decided to reboot it. Now its stuck in the Samsung "Custom" screen with the lock (unlocked icon).
I cannot seem to be able to go into recovery mode as well. I'm not sure what build version my phone uses, and since I can't boot the phone i don't know what to do. What do you recommend I do? I was also using android 4.4.2....
Should I Odin back to factory and then re root?
This video seems to be very useful, and I want to follow it but what should i do if I don't know the build?
https://www.youtube.com/watch?v=GL8XwuRYoWU
Thanks for youre help XDA,
Dany
Click to expand...
Click to collapse
Were you using SafeStrap or TWRP... that may help with what build you were on since your not sure and if you were MDK you don't want to Odin a different firmware and lock your phone up.
If you don't know.. What other ROMs have you flashed successfully before? Have you flashed custom kernels before?
Or did you have to flash kernel modules when flashing TW ROMs...
HD 16.1 needs to be on either MDK or a SafeStrap with 4.4.2 base so most likely you were on 4.3 base is my guess until you provide more info.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Were you using SafeStrap or TWRP... that may help with what build you were on since your not sure and if you were MDK you don't want to Odin a different firmware and lock your phone up.
If you don't know.. What other ROMs have you flashed successfully before? Have you flashed custom kernels before?
Or did you have to flash kernel modules when flashing TW ROMs...
HD 16.1 needs to be on either MDK or a SafeStrap with 4.4.2 base so most likely you were on 4.3 base is my guess until you provide more info.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
So Unfortunately i did a big mistake. I didn't realize I was still using MDK, and then I used Odin to upgrade to NC5
1. Can i Odin (full wipe) to MDK, or too late?
2. If not, should I considering doing this downgrade http://forum.xda-developers.com/showthread.php?t=2720163 ??
Danylevy12 said:
So Unfortunately i did a big mistake. I didn't realize I was still using MDK, and then I used Odin to upgrade to NC5
1. Can i Odin (full wipe) to MDK, or too late?
2. If not, should I considering doing this downgrade http://forum.xda-developers.com/showthread.php?t=2720163 ??
Click to expand...
Click to collapse
Yikes !! That's too bad. I won't make you feel any worse lol
It is to late now. You can't go back to MDK
I'd say look for Surge's method on here. I have an MDK phone and have never done those methods but most seem to like his method. Up to you though.
Sent from my SCH-I545 using Tapatalk
Here's an easier method to get root on NC5, http://forum.xda-developers.com/showthread.php?t=2769480. Well more like a better explained one.
Sent from my OtterX running SlimKat
Poor guy updated an MDK phone... No it's not the end of the world.. Just a cell phone.. But that just plain sux!
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Poor guy updated an MDK phone... No it's not the end of the world.. Just a cell phone.. But that just plain sux!
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
we see this happen as they dont really understand the rules of what can and can't be done with their phones. Unfortunate as we have a boatload of info in these forums that would them out,,,,,just need to take time to read first