Related
OK.. so here is my story. i got my phone about a month ago. rooted it. worked great. last week my phone froze so i had to pull the battery, ive dont that before, but this time when i tuned it on it took me thru setup wizard. my apps were gone and i have 0 bytes. every time i turn it off and turn it back on i have to go through the set up wizard. i looked online for ways to go back to stock, but they require i download an app. but i cant because i have 0 bytes. please i just want this thing unrooted and back to normal. PLEASE HELP
Theres a thread in the development section that addresses this issue. Search 0.00. Fyi imo voodoo is not worth the drama, stock file system roms ftw, kk?
Sent from my SCH-I500 using XDA App
i cant get it to work i downloaded odin but am having problems with it
Odin will not fix your problem, rooting is not your problem. Look in the development section on this forum and run the voodoo uninstaller(automatic) boot into stock android recovery 2e, and wipe data/cache after you run voodoo uninstaller.
Sent from my SCH-I500 using XDA App
but what is voodoo??
i never installed voodoo
and in odin... icant locate the pda file or i just dont have it. when i find a link to install it brings up a blank page
This may be a dumb suggestion, but is it possible your SD card is loose in its socket?
I really don't understand this phone. I've been on a quest of 2 weeks to be rooted and on official status, finally i gave up everything because i was not able to have both. Finally i flashed factory rom through odin, formated a couple of time the phone, and i got back official status. I much rather gave up a few rooting benefits then OTAs, at least until they fix the phone's problems.
Well, this morning, i wake up, and that DAMN custom status is back....WHY????????? I'm not rooted, i'm 100% stock, i checked with rootchecker and my phone doesnt have root....then why does that damn status keep coming back??? There is obviously something else that triggers it......man i'm so deperate! Please help!
polish_pat said:
I really don't understand this phone. I've been on a quest of 2 weeks to be rooted and on official status, finally i gave up everything because i was not able to have both. Finally i flashed factory rom through odin, formated a couple of time the phone, and i got back official status. I much rather gave up a few rooting benefits then OTAs, at least until they fix the phone's problems.
Well, this morning, i wake up, and that DAMN custom status is back....WHY????????? I'm not rooted, i'm 100% stock, i checked with rootchecker and my phone doesnt have root....then why does that damn status keep coming back??? There is obviously something else that triggers it......man i'm so deperate! Please help!
Click to expand...
Click to collapse
It's really not as big of a deal as you are making it. The way I see it you have 2 choices.
1. Exchange the phone for another (that might do the same thing)
2. Ignore it.
Just like every other Galaxy phone out there (you remember the skyrockets, right?) not all of them react the same way. Some get custom, some do not. Others switch back and forth.
I've noticed you have made many posts about this same thing. If someone hasn't provided a concrete answer that has worked for you by now it just doesn't exist yet. No matter how frustrated you are over it, making new posts about it are not going to change anything.
Its up to you if you keep wanting to post about it (I'm not complaining about it), I just don't think it's going to get you any more information at this point than what already has been said. Maybe I am wrong and someone will tell you exactly what to do to make it "official", but I haven't seen anything yet.
Good luck and try not to let it get to you so much.
euhhh no, they are not about the same thing, one was about retaining officiel while rooted, and now that i've given up on that, i still have a custom status, the reson why i dont report there is becuase poeple have seen the thread and will not go back, so in order to attract new poster i create a new thread. And no, i dont want to ignore anything because i want OTAs. If you have a problem with that, dont answer
You need to re-root (motochopper method) and then using a file browser such as "root explorer" go to:
/System/Xbin
Once you have navigated to the above path, delete these two files:
"su" and " busybox"
Once you've deleted the two files, uninstall SuperSU and reboot your phone twice.
You'll notice that after the second reboot the "custom" will revert back to "official"
Sent from my SGH-I337M using Tapatalk 2
peoples_flip said:
You need to re-root (motochopper method) and then using a file browser such as "root explorer" go to:
/System/Xbin
Once you have navigated to the above path, delete these two files:
"su" and " busybox"
Once you've deleted the two files, uninstall SuperSU and reboot your phone twice.
You'll notice that after the second reboot the "custom" will revert back to "official"
Sent from my SGH-I337M using Tapatalk 2
Click to expand...
Click to collapse
correct me if i'm wrong but these 2 files, should not even exist if you install a firmware thru odin and format the phone a few times...
I went through what you have, I completed a full stock restore via Odin and these two files I mentioned were still there. Use a file explorer and go to the path I suggested and you'll see them there
Sent from my SGH-I337M using Tapatalk 2
polish_pat said:
correct me if i'm wrong but these 2 files, should not even exist if you install a firmware thru odin and format the phone a few times...
Click to expand...
Click to collapse
I don't believe the current Odin contains a pit...or whatever it is that formats the phone...
So all Odin is going to do is reinstall everything...so replace missing or corrupted files - it will not delete your new files
Formating from the phone itself won't delete everything...its just going to delete your apps, app data, and cache
Therefore doing multiple factory resets and odins likely will not remove all traces of root...someone correct me if I'm wrong but that's what I believe is the case...
Sent from my HTC PH39100 using Tapatalk 2
Is there a reason why it showing custom is a bad thing?
Sent from my SAMSUNG-SGH-I337 using xda premium
XGhozt said:
Is there a reason why it showing custom is a bad thing?
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
AT&T software update push or download will not work for your phone if it is showing custom. People like to be getting these stock updates as soon as they are published by the provider, not when some good heart packages a new ROM using them.
polish_pat said:
correct me if i'm wrong but these 2 files, should not even exist if you install a firmware thru odin and format the phone a few times...
Click to expand...
Click to collapse
Good info here, I did this procedure as you described, and yes, official is showing, but you can NOT delete su, it will unroot. I just renamed the 2 files, and root was gone. renamed su back, re-installed su superuser, and reboot, root is back with official status.
Thanks.
TheAxman said:
Good info here, I did this procedure as you described, and yes, official is showing, but you can NOT delete su, it will unroot. I just renamed the 2 files, and root was gone. renamed su back, re-installed su superuser, and reboot, root is back with official status.
Click to expand...
Click to collapse
I tried this procedure and still have custom after 2 reboots. I renamed su and busybox then verified root was gone. Then renamed su back. I guess the part I was confused at was reinstall super user. Do I uninstall then re-install from play store?
Thank you.
EDIT: Followed my thought of uninstalling and re-installing through play store and still get custom.
CAG-man said:
I tried this procedure and still have custom after 2 reboots. I renamed su and busybox then verified root was gone. Then renamed su back. I guess the part I was confused at was reinstall super user. Do I uninstall then re-install from play store?
Thank you.
EDIT: Followed my thought of uninstalling and re-installing through play store and still get custom.
Click to expand...
Click to collapse
Same here
CAG-man said:
I tried this procedure and still have custom after 2 reboots. I renamed su and busybox then verified root was gone. Then renamed su back. I guess the part I was confused at was reinstall super user. Do I uninstall then re-install from play store?
Thank you.
EDIT: Followed my thought of uninstalling and re-installing through play store and still get custom.
Click to expand...
Click to collapse
Correct. the one from the playstore updates the binaries. then uninstall.
---------- Post added at 07:11 PM ---------- Previous post was at 07:10 PM ----------
XGhozt said:
Is there a reason why it showing custom is a bad thing?
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
Good answer, why does it matter if it says custom? whats the big deal here. If you are wanting the update, why not just wait until a dev does what they need to do to it, and flash it later. I updated 1 time in a year on my GS3, and never did it again. When a new rom is developed, it usually is a base from the update...so....
Had a posting. Could not delete
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Did some digging in the forums and I am rooted with OFFICIAL.
This is how to do it. Taken from this thread.
http://forum.xda-developers.com/showthread.php?t=2252248&page=42
Mr. Q said:
Well, you do not have to install the ZIP, but instead, do the following:
- Install SuperSU from the market
- Grant SuperSU root access
- When asked to update su-binary, please do
- Remove SuperUser from your device
- Reboot (I read two reboots are needed to make the icon disappear again.)
Click to expand...
Click to collapse
My process completely.
Remove Busybox from system/xbin (or your busybox backup)
Install SuperSU by Chainfire from playstore.
Open SuperSU and Grant SU root
Update the binary
Say yes to try to remove other root apps. This will remove superuser.
reboot
reboot
On second reboot you will notice the Galaxy S4 logo returns and Official Status has returned.
If it has not returned then some other issue is causing the custom status.
CAG-man said:
Did some digging in the forums and I am rooted with OFFICIAL.
This is how to do it. Taken from this thread.
http://forum.xda-developers.com/showthread.php?t=2252248&page=42
My process completely.
Remove Busybox from system/xbin (or your busybox backup)
Install SuperSU by Chainfire from playstore.
Open SuperSU and Grant SU root
Update the binary
Say yes to try to remove other root apps. This will remove superuser.
reboot
reboot
On second reboot you will notice the Galaxy S4 logo returns and Official Status has returned.
If it has not returned then some other issue is causing the custom status.
Click to expand...
Click to collapse
I was able to get official and root, the problem is it comes back after 2-3 days, please report back on sturday and tell me if its still official, also this logo you are talking about, i never see it because im in canada and my bootloader is unlocked already
EDIT: Ok, so once i was rooted and installed SuperSU and got superuser out, i deleted busybox, i then rebooted ONCE and got official just like that. I also took out SD card because i know this screwed me up last time. I'm happy because i'm rooted and official, but i'm not convinced this will last very long because it has never lasted more than 2 days. I will report back in a few days. Thanks Cagman, you've been very helpful and what you told me to do did the best results for me, i just hope they last
so far so good!!!:fingers-crossed:
polish_pat said:
so far so good!!!:fingers-crossed:
Click to expand...
Click to collapse
Try rebooting a few more times.
For about a week i was getting the custom status every 2nd or 3rd reboot, and then eventually it just went away...
joeybear23 said:
Try rebooting a few more times.
For about a week i was getting the custom status every 2nd or 3rd reboot, and then eventually it just went away...
Click to expand...
Click to collapse
Hahaha, i did it!! earlier this afternoon i sort of challenged my phone by rebooting it constantly, ive rebboted probbaly 20-30 times and its still official, i guess deleting busybox sealed the deal!!
Polish_pat I am glad I was able to help. You are welcome. Congratulations.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Rooting my Galaxy S4 has been one of the biggest pains in my rear ever and now I'm bricked and need a bit of help.
Normally, when I want to root a phone, I come here, to XDA, and follow a nice well written up-to-date thread on how to do it and it works. For the S4 however, I can't find any such threads that are not either old, out-of-date, or they use so many abbreviations for things I have no clue what they are talking about.
I started out with a totally stock Samsung Galaxy S4, was a VPUAMDL.
I used ODIN to push TWRP tarball. I then used TWRP to install the CWM SuperSU zip file.
I noticed when it started up that I had no root, I had the SuperSU program however, it nor another program I got on the marketplace, could confirm root.
Bit of looking I found this: galaxys4root (DOT) com/galaxy-s4-root/sprint-vpuamdl-firmware-update-root-fix/
(sorry, can't post full links yet)
Which basically informed me that VPUAMDL needs a new kernel to remove the SetUID restrictions.
I downloaded that file, and put it on my SD card. Booted into TWRP and installed. now my phone is bricked. gets to the "Samsung Galaxy S4" startup splash screen on black background
I am looking for a kernel that will work, either the stock kernel or not.
I am also looking for a good tut on rooting the S4, as all the tuts I have used have been utter wasted time.
I have ODIN, and can boot TWRP, ODIN mode, etc on my phone.
have no clue where to go from here and Im afraid to start trying to download random files and get everything mixed and confused.
Thanks for any help at all.
CF Auto Root
http://forum.xda-developers.com/showthread.php?t=2291827
Sent from my SPH-L720 using xda app-developers app
FanOfSkynyrd said:
CF Auto Root
http://forum.xda-developers.com/showthread.php?t=2291827
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
I followed that page, pushed it, installed fine, 100% no errors.
still bricked at GS4 startup splashscreen.
It did finish successfully and I saw the screen with the red android.
It removed TWRP and replaced it with the stock recovery as it should have.
I am actually surprised myself that it is still bricked at the GS4 splash.
Odin stock everything. See if it boots. Then try to root after that.
Stealyourface said:
Odin stock everything. See if it boots. Then try to root after that.
Click to expand...
Click to collapse
I am failing to find stock everything to push.
I think I stated that, not sure... hmm
none the less. I do not have a stock kernel or recovery on hand. I can not find one either as there seem to be a plethora of kernels and threads and pages all for different files and downloads. Sifting through trying to find something is becoming harsh. Thus this thread.
You are not bricked if your phone can turn on and go to download mode or recovery.
Sent from my Sprint Galaxy S4 using Tapatalk 2
GiantJay said:
You are not bricked if your phone can turn on and go to download mode or recovery.
Sent from my Sprint Galaxy S4 using Tapatalk 2
Click to expand...
Click to collapse
Well then its whatever you want to call it when it wont boot the operating system and is totally un-usable as a phone or mobile device.
I would go HERE
That is the thread for stock MDL stuff.
Download and flash the kernel and full wipe rom for MDL.
Then upgrade to MF9.
+2 ^^^^ to what he said :edit:
Nice tut on rooting the s4 thanks to mudavo here http://forum.xda-developers.com/sho...to Full Stock [MF9] w/ Root & Custom Recovery
There is also a video tutorial stickied in android devolpment
Sent from myself SPH-L720 using xda app-developers
Thanks guys, going to try some of the stuff from there. Hope i get it going. Need mah phone back! lol
Wooo, those links where just what I needed. Thanks a lot.
Got my phone back on and now I have a stock file in case I muck things up again.
Just make a nand back up and restore when something bad happens ive mucked up alot and it has always saved me
Sent from my SPH-L720 using xda app-developers app while smoking
Hi,
On MF3.
I'm rooted. I have clock work recovery installed.
I can download the update succeffuly however when the phone reboots the install begins, gets as far as 25% then fails. Phone reboots back to 4.2.2 with a message that says the install was interrupted.
Have tried twice with the same result.
Anyone else experiencing this?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
ckalantzis said:
Hi,
On MF3.
I'm rooted. I have clock work recovery installed.
I can download the update succeffuly however when the phone reboots the install begins, gets as far as 25% then fails. Phone reboots back to 4.2.2 with a message that says the install was interrupted.
Have tried twice with the same result.
Anyone else experiencing this?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
If I were you I would go back and read a little information about mf3 and what kind of recovery can be used. It sounds to me like you might be very confused. In order to correctly keep from bricking your phone you may want to read up on things. Good luck.
ckalantzis said:
Hi,
On MF3.
I'm rooted. I have clock work recovery installed.
I can download the update succeffuly however when the phone reboots the install begins, gets as far as 25% then fails. Phone reboots back to 4.2.2 with a message that says the install was interrupted.
Have tried twice with the same result.
Anyone else experiencing this?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Since you are rooted, take a look in the /cache/recovery directory. Read the log file. It will tell you where things messed up.
For example, I had forgotten that I did something with csc and had replaced the feature.xml file. Luckily, I had a back up of the original file. I renamed it, fixed is file permissions to rw-r--r--, advanced my clock one day, and then was able to install MJ9.
Good luck, and remember you won't have root anymore when you install this (for the time being)
Yrs,
dkephart
Sent from my SAMSUNG-SGH-I337 using Tapatalk
ckalantzis said:
Hi,
On MF3.
I'm rooted. I have clock work recovery installed.
I can download the update succeffuly however when the phone reboots the install begins, gets as far as 25% then fails. Phone reboots back to 4.2.2 with a message that says the install was interrupted.
Have tried twice with the same result.
Anyone else experiencing this?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
I had the same problem. The only way I was finally able to upgrade to 4.3 was to use Odin to revert to stock (unrooted) 4.2.2 MF3 using the files on this thread: http://forum.xda-developers.com/showthread.php?t=2502003 Once I did that I ran the OTA update to 4.3 and it worked without any problems
To able to keep your root and upgrade from 4.2.2 to 4.3 you have to change your param file back to the stock. Thats all the information that I have so far so... not completely sure. But I think that is what you're supposed to do.
Because you have a custom param file, when you try to upgrade to 4.3 it's telling you there is an issue with your phone.
I may be wrong.
Is there a copy of the correct feature.xml? Im having the same issue
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
According to the log its stopping when it can't find the chat on apk. I did remove it using titanium.
Will restore it try again andbipdate the thread. Thanks for pointing out the correct log file to look at.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
I checked again and found my backup feature.xml. Typed this from mj9.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
ckalantzis said:
Hi,
On MF3.
I'm rooted. I have clock work recovery installed.
I can download the update succeffuly however when the phone reboots the install begins, gets as far as 25% then fails. Phone reboots back to 4.2.2 with a message that says the install was interrupted.
Have tried twice with the same result.
Anyone else experiencing this?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
I had the same problem happen to me on Wednesday night and last night. Today I used Odin to go back to stock MF3, however, then I couldn't get the OTA update. It kept saying my firmware was up to date each of the three times I restored it.
Now I'm finally on MJ9 after copying "update-mf3-mj9.zip" to my SD card, going into recovery mode, and updating from external SD card. Now I can use my Galaxy Gear!
Cause I want to sound like a noob.
How did you install CWM on what reads to me a MF3 S4.
Those on MF3 have been using Safestrap cause CWM hasn't been possible.
Sent from my ATT S4 MF3 using Tapatalk
jball said:
Cause I want to sound like a noob.
How did you install CWM on what reads to me a MF3 S4.
Those on MF3 have been using Safestrap cause CWM hasn't been possible.
Sent from my ATT S4 MF3 using Tapatalk
Click to expand...
Click to collapse
I was excited when I rooted the phone, then installed ROM manager premium. It allowed me to install the recovery. You can even boot into the recovery from ROM Manager.
However since the S4 is locked down tight, you can do any thing from there. So i can't flash anything. It even gives me a message saying as much.
However it is partially installed I can boot into it at will.
I will post a video of it. So that you all have an idea of what im talking about.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Don't waste your time with a video,its your stock recovery.your not the first to have done this.lets jump ahead a bit and just install Safestrap.whats Safestrap you might ask?search for it and READ please sir.
Sent from my ATT S4 MF3 using Tapatalk
jball said:
Don't waste your time with a video,its your stock recovery.your not the first to have done this.lets jump ahead a bit and just install Safestrap.whats Safestrap you might ask?search for it and READ please sir.
Sent from my ATT S4 MF3 using Tapatalk
Click to expand...
Click to collapse
While I was preparing to record it, I did notice that you are correct. Although Rom Manager goes through the motions of flashing the recovery, when you attempt to boot into the Recovery, you are faced with an Error, and default back into Android Recovery.
Although I know all about Safestrap...I think we've all missed the point. The OP was meant to get help about why the 4.3 OTA was failing 25% into the install.
I've got what I needed by being pointed to the location of the install log.....and while reading through it, I noticed that the install is failing because I removed the Chat On APK. I will install from backup and move forward.
Thank you all who provided the necessary guidance to solve the original problem.
Thank you as well to those who helped clear up the whole Clockwork vs Android recovery part. Although a minor part of the original post, it's good that we don't spread misinformation.
Cheers
ckalantzis said:
While I was preparing to record it, I did notice that you are correct. Although Rom Manager goes through the motions of flashing the recovery, when you attempt to boot into the Recovery, you are faced with an Error, and default back into Android Recovery.
Although I know all about Safestrap...I think we've all missed the point. The OP was meant to get help about why the 4.3 OTA was failing 25% into the install.
I've got what I needed by being pointed to the location of the install log.....and while reading through it, I noticed that the install is failing because I removed the Chat On APK. I will install from backup and move forward.
Thank you all who provided the necessary guidance to solve the original problem.
Thank you as well to those who helped clear up the whole Clockwork vs Android recovery part. Although a minor part of the original post, it's good that we don't spread misinformation.
Cheers
Click to expand...
Click to collapse
You handled this all very well.
ITNV said:
I had the same problem. The only way I was finally able to upgrade to 4.3 was to use Odin to revert to stock (unrooted) 4.2.2 MF3 using the files on this thread: http://forum.xda-developers.com/showthread.php?t=2502003 Once I did that I ran the OTA update to 4.3 and it worked without any problems
Click to expand...
Click to collapse
Did you use all files? I mean, I've been trying the same for the past couple of days, and I even asked in that thread if I could use just the PDA file, nobody replied so I went ahead and did it, it removed the root and I kept all my files and settings (That was the idea) but just after that I can't connect anymore to Kies ( I could without issues, I did a full backup moments before) and trying to do the sideload it always gives me the Error 7, I even tried the full SD card update,it erased everything and guess what, when it rebooted for my surprise I was still at 4.2.2 MF3, so it just did the Wipe Data and then rebooted, so I lost almost 6 hours getting everything back as it was and then, I had the Damaged SD card error so I also lost all my pictures and videos withoout back up.
So, as you can see half a day later I'm still at the same point I was this morning and with a huge loss, so, please, Did you use all the files? If you did, doing this erase everything also?
Thanks in adavance.
erasat said:
So, as you can see half a day later I'm still at the same point I was this morning and with a huge loss, so, please, Did you use all the files? If you did, doing this erase everything also?
Thanks in adavance.
Click to expand...
Click to collapse
Yes. I used all the files. The result was a completely stock unrooted 4.2.2 so, yes, it reset the phone and erased everything that I had on there. (It left my external SD card intact but I would still advise removing it if there is anything on there you don't want to lose.)
ITNV said:
Yes. I used all the files. The result was a completely stock unrooted 4.2.2 so, yes, it reset the phone and erased everything that I had on there. (It left my external SD card intact but I would still advise removing it if there is anything on there you don't want to lose.)
Click to expand...
Click to collapse
Yep, that was the reason why I just used the PDA I didn't want to lose my data, and then I did it anyways, my mistake was not doing the Odin Restore just after I realized that it erased everything and I was still at 4.2.2, that's was the perfect time to do it, but now, after I finally put everything back as it was, I simply don't see myself by my own choice, doing all this again.
Thanks.
erasat said:
Did you use all files? I mean, I've been trying the same for the past couple of days, and I even asked in that thread if I could use just the PDA file, nobody replied so I went a head and did it, it removed the root and I kept all my files and settings (That was the idea) but just after that I can't connect anymore to Kies ( I could without issues, I did a full backup moments before) and trying to do the sideload it always gives me the Error 7, I even tried the full SD card update,it erased everything and guess what, when it rebooted for my surprise I was still at 4.2.2 MF3, so it just did the Wipe Data and then rebooted, so I lost almost 6 hours getting everything back as it was and then, I had the Damaged SD card error so I also lost all my pictures and videos withoout back up.
So, as you can see half a day later I'm still at the same point I was this morning and with a huge loss, so, please, Did you use all the files? If you did, doing this erase everything also?
Thanks in adavance.
Click to expand...
Click to collapse
It was mentioned several times in that thread exactly what files to use and how to use them. There were also several pictures provided that showed EXACTLY what the ODIN screen should look like before the flash.
scott14719 said:
It was mentioned several times in that thread exactly what files to use and how to use them. There were also several pictures provided that showed EXACTLY what the ODIN screen should look like before the flash.
Click to expand...
Click to collapse
In the thread, there are tons of instances where it explains where to use each file and even pictures, I know because I read every single post, but none of them explains if I could use just the PDA one if I wanted to keep my settings while unrooting the phone, that's why I asked about it, because nobody replied to my question I decided to be the guinea pig, and yes, it works, you keep your settings, and I was glad, but as you can see, what I wanted to accomplish didn't work after all. Without all the files it doesn't fix the issue that causes the error 7 when doing the sideload.
help with mf3 to mj9
Having the same issue and formatted card with backup image.
Update got to 23 % and failed
now phone refuses to flash in odin.....and im missing factory apps preventing me from doing anything to get it back to stock
anyone have a stock restore image I could use in kies?
Would that work properly?
I've tried asking this in the q&a section on the main thread but I think I'm being ignored because I'm asking a question about the at&t version inside a Verizon thread. Idk. But I've tried installing hyperdrive rls15 and I follow the instructions on the main page for at&t and I get to where I need to reboot and wait 10 mins. Well it just stays on the splash screen. I've tried repeating the install 4 time's now amd the same results. I found a tooic saying fix permissions but it fails. I'm sorry if this has been asked already. I have looked through several different threads but I may have overlooked it. My phone baseband is I337UCUAMDL im on 4.2.2 and have twrp v2.5.0.2 as my recovery. I've also verified the md5. any suggestions?
I hate to double post but if anyone has any ideas as to why this is happening I'm going to try and redownload and try loki patch I don't know if it's needed but I will try.
motel6man said:
I hate to double post but if anyone has any ideas as to why this is happening I'm going to try and redownload and try loki patch I don't know if it's needed but I will try.
Click to expand...
Click to collapse
Same problem here,
I'm going to try and install a kernel through TWRP. I've tried a fresh root / loki install, same issue.
For me, I remember having to install an AT&T compatibility pack.zip file on previous Hyperdrive releases, like RLS 10.
I tried to install RLS15 and at the very end of install, it says this:
Flashing Kernel
file_getprop: failed to stat"/tmp/aroma/kernel.prop": No such file or
directory
However, for some reason, after trying to install this new release, I was not able to restore data in TWRP from a backup of RLS 10. I was able to restore to a non-rooted backup (i don't know how), and it appears that I am not rooted anymore, and I don't think I have superuser anymore. So, I'm not exactly sure where to start.
Glad to see I'm not the only one this is happening to. Please let me know if you figure it out. I noticed the same thing but thought I seen someone else say that it was nothing.
so i redownloaded all files and nothing. tried loki patch and nothing. tried kt kernel because i seen another post with someone saying it was the only one that worked for them and nothing. im still stuck on splash screen. please if anyone knows how to fix this please let me know im desperate now. i really want to try this rom so any help would be greatly appreciated. thanks
Same here =/
Flashing a kernel before ROM didn't do anything.
I'm starting to think that we don't have Super User installed anymore, I tried re-installing some BackUps (rooted backups)
and TWRP said something like, you don't have SuperUser instyalled, want to install it? *Slide to Install* Phone quickly reboots (not showing any proof of Super User being installed in TWRP emulator) and still no effect.
When I get some time ill look into how to install SuperUser, which I thought was already put on when we root.
Have you tried installing any other ROMS with success?
Are you still on MDL? I am, and im starting to think i need to just go ahead and do the update from AT&T, and then switching over to Safestrap recovery, but i hope i can find another solution before doing all that.
Sent from my SAMSUNG-SGH-I337 using xda premium
d9vabder said:
Same here =/
Flashing a kernel before ROM didn't do anything.
I'm starting to think that we don't have Super User installed anymore, I tried re-installing some BackUps (rooted backups)
and TWRP said something like, you don't have SuperUser instyalled, want to install it? *Slide to Install* Phone quickly reboots (not showing any proof of Super User being installed in TWRP emulator) and still no effect.
When I get some time ill look into how to install SuperUser, which I thought was already put on when we root.
Have you tried installing any other ROMS with success?
Click to expand...
Click to collapse
I haven't tried any other roms yet. I haven't really seen any that I liked.
d9vabder said:
Are you still on MDL? I am, and im starting to think i need to just go ahead and do the update from AT&T, and then switching over to Safestrap recovery, but i hope i can find another solution before doing all that.
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
I'm still on mdl. I'm going to keep looking around for a solution. Please let us know if you found a way to fix it.
Also heres a screen shot of my info
motel6man said:
I've tried asking this in the q&a section on the main thread but I think I'm being ignored because I'm asking a question about the at&t version inside a Verizon thread. Idk. But I've tried installing hyperdrive rls15 and I follow the instructions on the main page for at&t and I get to where I need to reboot and wait 10 mins. Well it just stays on the splash screen. I've tried repeating the install 4 time's now amd the same results. I found a tooic saying fix permissions but it fails. I'm sorry if this has been asked already. I have looked through several different threads but I may have overlooked it. My phone baseband is I337UCUAMDL im on 4.2.2 and have twrp v2.5.0.2 as my recovery. I've also verified the md5. any suggestions?
Click to expand...
Click to collapse
Are you using Safe strap?
I was having the same problem after like 4 tries i figured out that every time I would download this it would go into the internal memory when it should have gone into the xd. I had to move folders manually. After that everything has been working correctly.
Do you know what folders have to be moved and where?
Sent from my SAMSUNG-SGH-I337 using xda premium
d9vabder said:
Do you know what folders have to be moved and where?
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
I created a new one on the xd card named it roms so I won't forget.
All I did was go to Mounts in TWRP recovery and mounted my microSD card and this fixed the problem.
Sent from my SAMSUNG-SGH-I337 using xda premium
d9vabder said:
All I did was go to Mounts in TWRP recovery and mounted my microSD card and this fixed the problem.
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
cool im going to go try it in a few mins thanks
i tried mounting both internal and external and still nothing can you go through the steps you did from start to finish maybe im missing something
Okay, so the first thing i did was mount my microSD(external sd) then a full wipe. Even though i was mounted to my sd card, i still had to navigate to my internal memory to select the zips i wanted to flash. I first installed an older release of Hyperdrive Rom, and during installation, i selected Full Wipe option again. i also added my AT&T compatibility pack.zip to be flashed right after the ROM. Also, i dont know if this affected anything, but i tried installing the T-Mobile compatibility pack on a previous attempt. I read somewhere where some1 did this and it worked for them, but it didnt work for me until i did another install of RLS15 and the ATT pack.
Hope this can help you
Sent from my SAMSUNG-SGH-I337 using xda premium