hy everybody , i have been trying to install hyperdrive rom rl10 on mt at&t galaxy s3 i have follow every step ,fix, i even flash kt747 kernel and nothing i'm still stuck on boot it won't pass the first boot animation , i also flash xone kernel and still the same it will get stuck on first animation boot even after 7 minutes it wont do anything.:crying:
angeltouch 4g said:
hy everybody , i have been trying to install hyperdrive rom rl10 on mt at&t galaxy s3 i have follow every step ,fix, i even flash kt747 kernel and nothing i'm still stuck on boot it won't pass the first boot animation , i also flash xone kernel and still the same it will get stuck on first animation boot even after 7 minutes it wont do anything.:crying:
Click to expand...
Click to collapse
What model do you have? Carrier? What option did you first choose for a kernel?
You're like the 50th user in here this week with this issue on hyperdrive. It would appear the device type in the build.prop is being is being edited and there is a conflict during the boot process causing this soft brick. Anyone with more knowledge than this please chime in.
If you can still get back into recovery, your options are probably to restore a backup or flash another rom. In download mode you could flash stock stock rooted via odin. If your s3 is not recognized on your pc, there is a flashable stock firmware zip in the link in my signature. In post #2 at the bottom
xBeerdroiDx said:
What model do you have? Carrier? What option did you first choose for a kernel?
You're like the 50th user in here this week with this issue on hyperdrive. It would appear the device type in the build.prop is being is being edited and there is a conflict during the boot process causing this soft brick. Anyone with more knowledge than this please chime in.
If you can still get back into recovery, your options are probably to restore a backup or flash another rom. In download mode you could flash stock stock rooted via odin. If your s3 is not recognized on your pc, there is a flashable stock firmware zip in the link in my signature. In post #2 at the bottom
Click to expand...
Click to collapse
hi beerdroid i have at&t sgh-i747
i choose the ziggy kernel in aroma thats the only option for at&t , i did try with the verizon with the zeus kernel,deviant kernel, and stock kernel all with no luck , yea i seen a lots of users with the same problem , yes i can still pull out the battery and do the process again with a different kernel , i have try kt747 kernel ,xone kernel and devil's reject kernel all with no luck , phone will boot but it will get stock on first animation boot , and i have no clue when you say build.prop
angeltouch 4g said:
hi beerdroid i have at&t sgh-i747
i choose the ziggy kernel in aroma thats the only option for at&t , i did try with the verizon with the zeus kernel,deviant kernel, and stock kernel all with no luck , yea i seen a lots of users with the same problem , yes i can still pull out the battery and do the process again with a different kernel , i have try kt747 kernel ,xone kernel and devil's reject kernel all with no luck , phone will boot but it will get stock on first animation boot , and i have no clue when you say build.prop
Click to expand...
Click to collapse
i'm trying to do is installing the rls 9 and then update see if this help
So the very first time you flashed hyperdrive, you selected at&t and the ziggy kernel and it didn't work? I'm assuming you gave it plenty of time on the first boot up. Someone correct me if I'm wrong but hyperdrive is a verizon base, yes? If so, this might be the source of your problem, even though it is a "multi-carrier" rom. You can try wiping data, cache and dalvik in recovery then rebooting. Like i said, though, you will probably have to another route (restore backup or flash new rom). When you successfully boot up next, I would imagine your model is different in about phone
xBeerdroiDx said:
So the very first time you flashed hyperdrive, you selected at&t and the ziggy kernel and it didn't work? I'm assuming you gave it plenty of time on the first boot up. Someone correct me if I'm wrong but hyperdrive is a verizon base, yes? If so, this might be the source of your problem, even though it is a "multi-carrier" rom. You can try wiping data, cache and dalvik in recovery then rebooting. Like i said, though, you will probably have to another route (restore backup or flash new rom). When you successfully boot up next, I would imagine your model is different in about phone
Click to expand...
Click to collapse
i'm trying to do whay tou are saying but this aroma installer keeps freezing is driving me nuts
angeltouch 4g said:
i'm trying to do whay tou are saying but this aroma installer keeps freezing is driving me nuts
Click to expand...
Click to collapse
Are you using twrp or cwm for recovery? Twrp is recommended for aroma
xBeerdroiDx said:
Are you using twrp or cwm for recovery? Twrp is recommended for aroma
Click to expand...
Click to collapse
cwm
angeltouch 4g said:
cwm
Click to expand...
Click to collapse
If you're really wanting to get this particular rom going, changing to twrp might help. In my signature there is a link. Near the bottom of post #2 flashable recovery zips are mentioned. Download the twrp one and throw it on your phone. Boot into recovery and flash it. Reboot recovery. Wipe data, cache and try flashing the rom again.
xBeerdroiDx said:
If you're really wanting to get this particular rom going, changing to twrp might help. In my signature there is a link. Near the bottom of post #2 flashable recovery zips are mentioned. Download the twrp one and throw it on your phone. Boot into recovery and flash it. Reboot recovery. Wipe data, cache and try flashing the rom again.
Click to expand...
Click to collapse
ok i'll do that to see if helps thanks
hrsema and
angeltouch 4g said:
ok i'll do that to see if helps thanks
Click to expand...
Click to collapse
now i got the boot animation hyperdrive sbreen94 how much you think i have to wait it looks like is stock?
angeltouch 4g said:
now i got the boot animation hyperdrive sbreen94 how much you think i have to wait it looks like is stock?
Click to expand...
Click to collapse
It could take 10 or so minutes for the initial boot. If it takes a lot longer, you can try booting back onto recovery to wipe data and cache again. If this does not work, I would go another route
xBeerdroiDx said:
It could take 10 or so minutes for the initial boot. If it takes a lot longer, you can try booting back onto recovery to wipe data and cache again. If this does not work, I would go another route
Click to expand...
Click to collapse
ok , if not i'll try to flash some other kernels to see if it boots up , i f not i'll just give up on this rom and go back to synergy
When you're back up and running on a rom, go into settings > about phone and tell me what your device is listed as. You may have small issues down the road if your phone has been designated as an SCH-I535 or anything other than SGH-I747. That's an easy build.prop fix, though. Good luck
xBeerdroiDx said:
When you're back up and running on a rom, go into settings > about phone and tell me what your device is listed as. You may have small issues down the road if your phone has been designated as an SCH-I535 or anything other than SGH-I747. That's an easy build.prop fix, though. Good luck
Click to expand...
Click to collapse
ok i'll do that and let you know
model number samsung-sgh-i747
baseband number i747ucdlk3
angeltouch 4g said:
model number samsung-sgh-i747
baseband number i747ucdlk3
Click to expand...
Click to collapse
Good. Congrats. What rom did you end up on?
synergy thats were i was before trying to flash hyperdrive
The upside: now you can post in development threads
ok
Related
Hey there I know this might sound like a complete newbie question but I have honestly run out of ideas so posting here for some idea.
I have at this point decided my phone must be a lemon.
1. Day 1 received phone installed CM ran it for multiple days no problems.
2. After a few days of this wanted to try Wanams i9505 rom so wiped everything including data in recovery rebooted recovery and installed. First boot was fine setup was fine got it working but then after my first try to reboot it ot stuck at SAMSUNG GALAXY S4 second time it made it to the boot animation but crashed half way through it and reset.
3. Thinking my phone wasn't playing nice with the kernel in Wanam's rom (Adam I believe) I flashed his ROM then immediately flashed the stock m919 kernel after. Same results after first boot.
4. Then tried restoring my nandroid of complete stock. Same problem.
5. Wiped all (except SD) and restored nandroid of stock. Problem gone.
6. After my next backup of stock problem is back.
7. If I do a full odin to stock it works and reboots for days no problem.
I am using TWRP for TMO, have a m919v (Canadian Variant)
Any advice at all would be great, I could easily have overlooked something obvious. Thanks!
Should I not be wiping preload and EFS when doing a "full wipe" ?
No, if you are just flashing a rom from another carrier, which you are, wipe as usual, flash the rom, and before you boot use the tmo canadian kernel, it will boot.
TheAxman said:
No, if you are just flashing a rom from another carrier, which you are, wipe as usual, flash the rom, and before you boot use the tmo canadian kernel, it will boot.
Click to expand...
Click to collapse
Hey thanks for the response yes it does boot once, but after that it seems to not. I have even tried re-flashing the stock m919 kernel after flashing the target rom fails booting and that doesnt seem to fix it.
Idyar said:
Hey thanks for the response yes it does boot once, but after that it seems to not. I have even tried re-flashing the stock m919 kernel after flashing the target rom fails booting and that doesnt seem to fix it.
Click to expand...
Click to collapse
Where did you happen to find the kernel for your device?
TheAxman said:
Where did you happen to find the kernel for your device?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2262729
Idyar said:
http://forum.xda-developers.com/showthread.php?t=2262729
Click to expand...
Click to collapse
whoa, and that is for the 919v? Now I am really confused.
hmm, if thats the correct one, we have a problem. Let me ponder the moment. give me a few...maybe someone else could enlighten us...
is it just happening with this rom, does any of your backups restore ok?
TheAxman said:
whoa, and that is for the 919v? Now I am really confused.
hmm, if thats the correct one, we have a problem. Let me ponder the moment. give me a few...maybe someone else could enlighten us...
Click to expand...
Click to collapse
Good point they are not specifically for V variant but it is my understanding that they should be identical. I have the odin flash for it so what I will do is use that to be 100% sure thanks for the tip.
Idyar said:
Good point they are not specifically for V variant but it is my understanding that they should be identical. I have the odin flash for it so what I will do is use that to be 100% sure thanks for the tip.
Click to expand...
Click to collapse
You flashed Odin then made backup of stock right? And it still had an issue?
Seems like a recovery issue. Try CWM recovery instead
Sent from my SGH-M919 using Tapatalk 2
Yup cmw seems to have fixed all my problems thanks.
I'm not new to flashing ROMs, etc. But I'm completely confused on why when I installed the Wicked V4 ROM it works fine, but when i restart my phone it stays on the logo and I have to re flash the ROM again.
Any ideas?
nayte1993 said:
I'm not new to flashing ROMs, etc. But I'm completely confused on why when I installed the Wicked V4 ROM it works fine, but when i restart my phone it stays on the logo and I have to re flash the ROM again.
Any ideas?
Click to expand...
Click to collapse
Are you talking about the Galaxy S 4 logo or the boot animation? Either way, you should restore a nandroid backup (hopefully you made one before flashing Wickid V4).
The issue could be caused by not doing a proper wipe before flashing
C.Sweat said:
Are you talking about the Galaxy S 4 logo or the boot animation? Either way, you should restore a nandroid backup (hopefully you made one before flashing Wickid V4).
The issue could be caused by not doing a proper wipe before flashing
Click to expand...
Click to collapse
Could I return to stock using Odin? If so I'll try that when I'm able too.
nayte1993 said:
Could I return to stock using Odin? If so I'll try that when I'm able too.
Click to expand...
Click to collapse
Yeah you sure can. :good: Go here for instructions and stock firmware
nayte1993 said:
Could I return to stock using Odin? If so I'll try that when I'm able too.
Click to expand...
Click to collapse
try a factory reset/wipe first, before you go to stock again
Bob Hodges said:
try a factory reset/wipe first, before you go to stock again
Click to expand...
Click to collapse
Yeah I thought that would fix it too, but it doesn't. What I've had to do is reflash the ROM after clearing the cache and all of that, along with the factory reset and it works fine, the ROM will boot up and works great,but once I restart it just stays at the Galaxy S 4 logo and I have to do it all over again. I've also tried different recoveries because TWRP always wants a password when I boot into recovery and i'm not sure why.
(I've tried various ROMs and they all do this)
So I guess the only thing I can really do at this point would go ahead and use Odin to go to stock and try it all over again.
nayte1993 said:
Yeah I thought that would fix it too, but it doesn't. What I've had to do is reflash the ROM after clearing the cache and all of that, along with the factory reset and it works fine, the ROM will boot up and works great,but once I restart it just stays at the Galaxy S 4 logo and I have to do it all over again. I've also tried different recoveries because TWRP always wants a password when I boot into recovery and i'm not sure why.
(I've tried various ROMs and they all do this)
So I guess the only thing I can really do at this point would go ahead and use Odin to go to stock and try it all over again.
Click to expand...
Click to collapse
AFTER you flash stock rom, perform factory reset wipe, and you wont get stuck. flash recovery. and then flash custom rom and you should be fine
wrong kernels...period
TheAxman said:
wrong kernels...period
Click to expand...
Click to collapse
Yeah I'm coming from the Galaxy S 4G so I got some learning to do when it comes to this phone.
And yes that makes sense, obviously a Odin flash of stock should fix the problem?
Or could I just flash a correct Kernel and maybe that will fix the problem? I'm not quite sure.
I'm thinking Odin is the way to go at this point.
nayte1993 said:
Yeah I'm coming from the Galaxy S 4G so I got some learning to do when it comes to this phone.
And yes that makes sense, obviously a Odin flash of stock should fix the problem?
Or could I just flash a correct Kernel and maybe that will fix the problem? I'm not quite sure.
I'm thinking Odin is the way to go at this point.
Click to expand...
Click to collapse
I've had success with just flashing the right kernel (and clearing dalvik/cache)...but if you're not already set up within the ROM an Odin would make sure you've got a clean base to work with.
Toleraen said:
I've had success with just flashing the right kernel (and clearing dalvik/cache)...but if you're not already set up within the ROM an Odin would make sure you've got a clean base to work with.
Click to expand...
Click to collapse
Thanks so much for your input, now with the Wicked V4 ROM, what Kernel would be best to flash?
If you don't know that fine, I'm just curious. :good:
I haven't rebooted my phone yet, so it's working fine, and it's somewhat set up in term of my contacts, texts, and so on. I'd rather not do Odin if possible, but if I have to I will.
nayte1993 said:
Thanks so much for your input, now with the Wicked V4 ROM, what Kernel would be best to flash?
If you don't know that fine, I'm just curious. :good:
I haven't rebooted my phone yet, so it's working fine, and it's somewhat set up in term of my contacts, texts, and so on. I'd rather not do Odin if possible, but if I have to I will.
Click to expand...
Click to collapse
That's a matter of preference...just make sure to pull a TW kernel. Of course, the kernel built into Wicked should work just fine as well.
I've been a fan of ktoonsez's kernel (link in my sig). 7/7 got a little crashy on me, but 7/2 has been running smooth
Problem fixed, thanks everyone.
Few hours before this post I flashed a rooted version of android 4.3 from the thread by "Carlos_Manuel". However, following that the supersu was not working I flashed the supersu binaries over the ROM from TWRP. Since then, it is stuck in boot loop at the Google Logo. Tried flashing PA, Sourcery, CM but nothing seems to work. What should I do?
Flash the official Google image: http://forum.xda-developers.com/showthread.php?t=2376687
check dreams rom thread and see my post there
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Fix it by flashing factory images! do a full wipe, you can get imprtant stuff from your Nexus by using adb pull commands!
Users was blaming me when they screwed their Nexus with the root files!
I can successfully even flash old root files and no bootloops but ofc. root wont work if using those old root files.
OP, did you factory reset between ROM flashes?
beekay201 said:
OP, did you factory reset between ROM flashes?
Click to expand...
Click to collapse
pulling files then flashing 4.2.2 stock image to start fresh
NyPlaya513 said:
Ok, I am paranoid and want to be sure about this. I am in the same boat as the OP. I have a 32gb toro on twrp 2.5. I am under the impression that flashing the stock images will flash my sdcard partition and I want to pull some files if that is the case. Is there anyway to pull the files or am I stuck and need to start fresh.
Click to expand...
Click to collapse
You cant use the stock images they are for gsm not toro/cdma, have to use a custom zip only one is that light speed one in development right now I am waiting for muzzys but, full wipe, flash rom, gapps, supersu.
NeoMagus said:
You cant use the stock images they are for gsm not toro/cdma, have to use a custom zip only one is that light speed one in development right now I am waiting for muzzys but, full wipe, flash rom, gapps, supersu.
Click to expand...
Click to collapse
nvm pulling files
If you tried wiping just cache/dalvik after the flash I dont know there may be another way to get it to boot or not but yeah the factory image will start it over fresh and get you out of it
NeoMagus said:
If you tried wiping just cache/dalvik after the flash I dont know there may be another way to get it to boot or not but yeah the factory image will start it over fresh and get you out of it
Click to expand...
Click to collapse
nvm got the toolkit to pull files via adb for me on my parallels
agent47er said:
Few hours before this post I flashed a rooted version of android 4.3 from the thread by "Carlos_Manuel". However, following that the supersu was not working I flashed the supersu binaries over the ROM from TWRP. Since then, it is stuck in boot loop at the Google Logo. Tried flashing PA, Sourcery, CM but nothing seems to work. What should I do?
Click to expand...
Click to collapse
"just wipe data" in recovery after flashing, solve bootloop issue
dexviajiboy said:
"just wipe data" in recovery after flashing, solve bootloop issue
Click to expand...
Click to collapse
thanks for your help.. but I ended up flashing factory image of 4.3 which fixed the problem. Also I wnted to ask if you know of any 4.3 kernels that have implemented high performance audio mod. So far I have tried Faux and Hybrid but both dont have it.
agent47er said:
thanks for your help.. but I ended up flashing factory image of 4.3 which fixed the problem. Also I wnted to ask if you know of any 4.3 kernels that have implemented high performance audio mod. So far I have tried Faux and Hybrid but both dont have it.
Click to expand...
Click to collapse
i dont think there's any kernel for now, give it some time and you'll get one
Hi all. I just got a Verizon Htc One M7. I bought it used and it was already updated to 4.4.2 Kit kat and sense 5.5. I am new to rooting and unlocking and I am running into issues I am hoping someone can help me with. I successfully unlocked, rooted, and got S-off. A am trying to get a custom kernel on the phone so I can have tap to wake and swipe to wake. I installed TWRP recovery 2.7.0.0. Everything appears to be working I boot into bootloader mode and it say unlocked and s-off on top of the screen. I started recovery and it appears to be working fine. I created a backup and that works. So I tried 2 different kernels elementalx and elite lunar. Both appear to install fine but when I reboot the phone gets stuck in a boot loop on the HTC screen. I then have to go back into recovery and revert back to my saved backup. The phone will then boot up fine. Not sure if I'm doing something wrong or what. I am running the stock ROM. Any help will be greatly appreciated.
Forgive and help a noop!!!!
No one knows? I also just noticed that on the bootloader screen there is no numbers after OS. Which would appear to mean i have no OS. But the phone boots and operates just fine. Any suggestions? Thinking I should get it back to factory and start over and flash the NuSenseSIX rom. If anyone could please help me out here it would be greatly appreciated!!!! I attached a picture of what my bootloader screen looks like.
Reubster24 said:
No one knows? I also just noticed that on the bootloader screen there is no numbers after OS. Which would appear to mean i have no OS. But the phone boots and operates just fine. Any suggestions? Thinking I should get it back to factory and start over and flash the NuSenseSIX rom. If anyone could please help me out here it would be greatly appreciated!!!! I attached a picture of what my bootloader screen looks like.
Click to expand...
Click to collapse
it's the rom you are on, if you go back to stock build you will see the OS-build number correctly displayed. if you are on a custom rom, and its not built correctly, it will not display properly.
you dont need to worry about it. all the info in hboot is for diagnostic purpose and wont effect you in any way.
synisterwolf said:
it's the rom you are on, if you go back to stock build you will see the OS-build number correctly displayed. if you are on a custom rom, and its not built correctly, it will not display properly.
you dont need to worry about it. all the info in hboot is for diagnostic purpose and wont effect you in any way.
Click to expand...
Click to collapse
Ok I appreciate the response. I am still on the stock ROM. Just have it rooted, unlocked and s-off with twrp custom recovery installed. Any ideas as to why I'm not able to get it to boot after installing a custom kernel? Can I just try to flash the NuSenseSIX ROM in the phones current state or should I start over?
Reubster24 said:
Ok I appreciate the response. I am still on the stock ROM. Just have it rooted, unlocked and s-off with twrp custom recovery installed. Any ideas as to why I'm not able to get it to boot after installing a custom kernel? Can I just try to flash the NuSenseSIX ROM in the phones current state or should I start over?
Click to expand...
Click to collapse
if you would like to try NuSense i would make sure you have a good backup or do one before. you'll need to wipe system - data - cache - dalvik in twrp and then install the rom.
---------- Post added at 01:36 PM ---------- Previous post was at 01:29 PM ----------
After some discussion with fellow dev's, i think you havent flash the insecure boot.img that allows you to write to /system. this should stop the kernel bootlooping you.
ok, here we go.
Flash the attached zip in recovery.
wipe dalvik and cache (2x for good measure)
reboot the phone.
then try to flash a custom kernel and see if you boot loop. Let me know what happens. please have a working backup before trying any of this.
(credit to @buckmarble and @brymaster5000)
kernel source
synisterwolf said:
if you would like to try NuSense i would make sure you have a good backup or do one before. you'll need to wipe system - data - cache - dalvik in twrp and then install the rom.
---------- Post added at 01:36 PM ---------- Previous post was at 01:29 PM ----------
After some discussion with fellow dev's, i think you havent flash the insecure boot.img that allows you to write to /system. this should stop the kernel bootlooping you.
Click to expand...
Click to collapse
I have everything backed up google drive with titanium backup as well as backed up in TWRP. When I wipe it doesn't remove the TWRP backup right? I have not flashed any boot.img. I am new to this and don't really know what that is. How would I find the boot.img I need. I think I'll just move forward with the NuSense Rom. Can I just download the zip for the NuSense ROM then wipe and flash it using TWRP and I'm good to go or is there other stuff I need to do?
Reubster24 said:
I have everything backed up google drive with titanium backup as well as backed up in TWRP. When I wipe it doesn't remove the TWRP backup right? I have not flashed any boot.img. I am new to this and don't really know what that is. How would I find the boot.img I need. I think I'll just move forward with the NuSense Rom. Can I just download the zip for the NuSense ROM then wipe and flash it using TWRP and I'm good to go or is there other stuff I need to do?
Click to expand...
Click to collapse
the boot.img zip above will allow you to write to the /system part of the phone.
TWRP will not wipe your backup. that is stored in a location its not allowed to wipe unless you do a "factory reset"
flash the zip above first. let it boot then flash NuSense. I'm not to familiar with that rom so i cant for sure say it will have said insecure boot.img.
Ok I flashed that file and the phone boots up fine. But it has a weird N flashing at the top of the screen now. I'll try a kernel this evening and see what happens. Any idea what the N is? Attached a zipped video of what its doing.
Reubster24 said:
Ok I flashed that file and the phone boots up fine. But it has a weird N flashing at the top of the screen now. I'll try a kernel this evening and see what happens. Any idea what the N is? Attached a zipped video of what its doing.
Click to expand...
Click to collapse
That icon is for NFC. idk why its flashing but make sure its off if you dont use it.
its under settings.
synisterwolf said:
That icon is for NFC. idk why its flashing but make sure its off if you dont use it.
its under settings.
Click to expand...
Click to collapse
Ok. It is off in settings. Tried to turn it on and it won't let me. I'll flash a kernel later and see what happens and if it stops doing it. Is there another insecure boot.img I can try?
Reubster24 said:
Ok. It is off in settings. Tried to turn it on and it won't let me. I'll flash a kernel later and see what happens and if it stops doing it. Is there another insecure boot.img I can try?
Click to expand...
Click to collapse
only need to do it once. flash any kernel that is meant for your rom or switch roms. you should be good to go.
synisterwolf said:
only need to do it once. flash any kernel that is meant for your rom or switch roms. you should be good to go.
Click to expand...
Click to collapse
Awesome thanks for all your help. I think I'm gonna flash a Rom. Any suggestions? I would like something close to the stock Rom.
Thank you for all your help!! I successfully installed the NuSense Rom.
Reubster24 said:
Thank you for all your help!! I successfully installed the NuSense Rom.
Click to expand...
Click to collapse
congrats man, you can PM me if you have anymore questions or post in the Q/A thread and i will try to help
:highfive:
Hello everyone,
After a long fight to try and get this phone back to normal, everything seemed good,
except not really
I started on a buggy CM11 version. Sick of it, I downloaded a 4.4.4 stock rom. I had to disable firewall and defender, but I got Odin to flash my md5. I got through everything and it booted successfully. After signing in and all that jazz, I find out that my WiFi isn't working. After a few reboots, My 4G finally works and everything seems to be steady.
Then, after exploring the rest of the phone I find out that all my apps from last ROM are still there. I know that you are supposed to wipe before flashing, but I was told that Odin will take care of that. It obviously didn't.
After THAT, I try to boot into Recovery as the next sensible step is to try to wipe my data and cache. I turn the phone off and press (Vol up + Home + Pwr) and the first boot screen shows for a moment. It says in blue "RECOVERY BOOTING" in the corner. Right after, it disappears and in another second it does the same screen without the "RECOVERY BOOTING". And as presumed, it does a regular boot.
What did I miss? How can I wipe my phone from recovery? How can I fix my problem with Wifi?
Reflash in Odin.
Make sure you have the correct stock rom. If you flash the "md5" you may have flashed the wrong thing. The md5 is not tge firmware, that is just the code that verifies your firmware file is not corrupted.
If your old apps were still there, you flashed the wrong thing. There is no way to flash stock firmware in odin and not wipe the data partition.
You are correct then
Yeah, I flashed a tar.md5 in Odin. It gave me a new ROM but all my apps are there. After all that, I still can't go to recovery. I tried using the terminal and ROM Toolbox to go there, both didn't work. Can I just leave it as it is and find a way to recovery or is the only way to go to bootloader and flash a correct file to get to recovery?
Flash twrp and see if it will reboot into recovery, then factory reset and flash latest firmware with Odin right after. Odin will NOT wipe data. It has to be done manually
serio22 said:
Flash twrp and see if it will reboot into recovery, then factory reset and flash latest firmware with Odin right after. Odin will NOT wipe data. It has to be done manually
Click to expand...
Click to collapse
It depends on what you ate flashing.
If you are flashing a full stock factory image it will wipe user data. If you are just flashing a system partition it won't.
Essem G said:
Hello everyone,
After a long fight to try and get this phone back to normal, everything seemed good,
except not really
I started on a buggy CM11 version. Sick of it, I downloaded a 4.4.4 stock rom. I had to disable firewall and defender, but I got Odin to flash my md5. I got through everything and it booted successfully. After signing in and all that jazz, I find out that my WiFi isn't working. After a few reboots, My 4G finally works and everything seems to be steady.
Then, after exploring the rest of the phone I find out that all my apps from last ROM are still there. I know that you are supposed to wipe before flashing, but I was told that Odin will take care of that. It obviously didn't.
After THAT, I try to boot into Recovery as the next sensible step is to try to wipe my data and cache. I turn the phone off and press (Vol up + Home + Pwr) and the first boot screen shows for a moment. It says in blue "RECOVERY BOOTING" in the corner. Right after, it disappears and in another second it does the same screen without the "RECOVERY BOOTING". And as presumed, it does a regular boot.
What did I miss? How can I wipe my phone from recovery? How can I fix my problem with Wifi?
Click to expand...
Click to collapse
Fkash twrp and format system, data, cache and preload and install a deodexed stock os
g7755725 said:
Fkash twrp and format system, data, cache and preload and install a deodexed stock os
Click to expand...
Click to collapse
Also this. This gives you more control over the whole process
Skipjacks said:
Also this. This gives you more control over the whole process
Click to expand...
Click to collapse
How do I know whatever I download is deodexed? And I went to a page of ROMs someone gave me and I downloaded the NK2 version, which also gave me a tar.md5. If I want the correct thing to flash, what should I flash?
Essem G said:
How do I know whatever I download is deodexed? And I went to a page of ROMs someone gave me and I downloaded the NK2 version, which also gave me a tar.md5. If I want the correct thing to flash, what should I flash?
Click to expand...
Click to collapse
The first post of any customized stock rom will tell you if its deodexed. If it doesn't say it...its not.
@Essem G:
Any updates for us? I'm following this thread because I have similar problems with my WiFi not working after upgrading from 4.2.2.
Any luck getting TWRP flashed?
Also I believe that the stock firmwares do come as tar.md5's, as in the file: M919UVUFNK2_M919TMBFNK2_M919UVUFNK2_HOME.tar.md5 from ShinySide's stock firmware thread.
As for the WiFi issue, from the hours of reading I've done it looks like this problem occurs when you upgrade your firmware, but it no longer matches the bootloader. Such as bootloader (Baseband) showing MDL, but Build Number showing NH7, NK2, etc. What does your show?
This thread may be of use to you when you get back to a working ROM. Good luck!
@RavenMind1
Everyone has been saying different answers and i've put off fixing my device for a while. I'm just afraid i'll brick it forever and have another nightmare after this current one. So no, there has been no progress. I think i'm gonna try to flash Philz and format my system, then flash a deodexed rom. @g7755725 said that you can flash TWRP, but I usually use Philz. It appears to be that I have lost root access because no root features work and SuperSU won't recognize it. Will everything work or am I setting my self up for disaster?
Edit: Where can I find a deodexed rom? I desperately need one, thanks
Essem G said:
@RavenMind1
Everyone has been saying different answers and i've put off fixing my device for a while. I'm just afraid i'll brick it forever and have another nightmare after this current one. So no, there has been no progress. I think i'm gonna try to flash Philz and format my system, then flash a deodexed rom. @g7755725 said that you can flash TWRP, but I usually use Philz. It appears to be that I have lost root access because no root features work and SuperSU won't recognize it. Will everything work or am I setting my self up for disaster?
Edit: Where can I find a deodexed rom? I desperately need one, thanks
Click to expand...
Click to collapse
Look in the forums for deodexed rom theirs a bunch and untouched as well i had philz but it eoukdnt boot my s4 so i had to switch to twrp because it does better then any recovery
g7755725 said:
Look in the forums for deodexed rom theirs a bunch and untouched as well i had philz but it eoukdnt boot my s4 so i had to switch to twrp because it does better then any recovery
Click to expand...
Click to collapse
Thanks for the support so far, but has this problem occured before? do you think the steps i've listed will solve this? Im just trying to make sure that I know exactly what to do before I go in. Thanks
Essem G said:
Thanks for the support so far, but has this problem occured before? do you think the steps i've listed will solve this? Im just trying to make sure that I know exactly what to do before I go in. Thanks[/Q] it should
Click to expand...
Click to collapse
@g7755725 I downloaded a deodexed rom from the SkipJacks guy (different page than what you sent me) and it's a little under 9MB... how could this possibly be a ROM?
Essem G said:
@g7755725 I downloaded a deodexed rom from the SkipJacks guy (different page than what you sent me) and it's a little under 9MB... how could this possibly be a ROM?
Click to expand...
Click to collapse
Have you tried my gamerrom Ultimate 1 its basically stock touchwiz of if Official NK2 M919UVUFNK2 with stweaks and no bloatware here is the thread gru 1 is in.the botyom of the thread http://forum.xda-developers.com/galaxy-s4-tmobile/development/stock-os-gamerrom-ultimate-2-touchwiz-t3078467
Sounds cool but i would have been interested a few months ago. I'm trying to sell the phone so I need to get it back to stock. Appreciate all the help and I think it's cool that you make ROMs
Essem G said:
Sounds cool but i would have been interested a few months ago. I'm trying to sell the phone so I need to get it back to stock. Appreciate all the help and I think it's cool that you make ROMs
Click to expand...
Click to collapse
If you're trying to go back to complete stock then just Odin NK2 firmware. http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508 I used the NK2 from here about 2 days ago to go back to stock.