Related
I installed paranoidandroid 3.96a today and I had some errors before I was able to install it so I ended up formatting the data and then clearing the caches.
I flashed PA. Then I flashed the latest google apps. Then I flashed PA again and rebooted. My phone loaded fine and I was able to install everything I want.
Then if I reboot my phone it get stuck on the splash screen and cannot load. If I go into TWRP 2.5.0.0 recovery it asks me for a password (I have not yet a password although I recently bought this phone used on swappa so I've contacted the seller to ask if he set a password). If I push cancel at the password screen then I can get into TWRP but if I go to wipe the dalvik cache it say sit "failed." The test printed to the console is:
Updating partition details...
E: Failed to wipe dalvik
Updating partition details...
I also cannot browse the internal memory of my phone. There is no folder named "android" or similar.
Any thoughts would be greatly appreciated. I'm going to try to update TWRP to the latest version. After that I'm out of ideas
Try the latest twrp like you said. Then you can also try cwm. Before you csn browse your file system in recovery, you have to mount system.
Id try another factory reset and reboot though. If thst doesnt help try another kernel. If youre still stuck, idin flash back to full stock with the root66 firmware, then start over clean from there.
Sent from my SGH-T999 using xda premium
how long do you let the phone sit after rebooting? I'm currently on the same rom and noticed it takes longer than usual to reboot the device. it's seems like it takes just as long to reboot the phone as it does to boot up the phone right after flashing the rom.
try letting the phone sit for 5-10 mins and see if it boots up. it's kind of ridiculous it takes that long to reboot a phone, but then again the rom is in alpha. I might try reflashing the rom to see if this still happens.
Just posted in the ROM thread to see if anyone else has the same issue.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Try the latest twrp like you said. Then you can also try cwm. Before you csn browse your file system in recovery, you have to mount system.
Id try another factory reset and reboot though. If thst doesnt help try another kernel. If youre still stuck, idin flash back to full stock with the root66 firmware, then start over clean from there.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I tried installing PA again and then upgrading TWRP to 2.6.0.0 but it still said that it had 2.5.0.0. Then I installed CM10.1 and used that to upgrade to TWRP 2.6.0.0 which worked. I then tried installing PA3.96a again with the same results.
I think that the problem is with TWRP not recognizing android 4.3 installs correctly because I have the same problem with CM10.2 that I had with PA3.96a.
I don't think the problem is that I'm not waiting long enough because after the first restart (i.e. I flash it and restart loading the ROM fine--then when I restart it for the first time it gets stuck). When I go into TWRP after it hangs the first thing it does is ask me for my password. I don't have a password. I think that something is happening to the system partition after install that makes TWRP unable to read it on this phone. Also it says that 0 MB have been used on my phone ram so I think the problem is with TWRP not being able to read the system partition in 4.3 correctly.
Has anyone gotten android 4.3 working on the t-mobile s3 yet?
Edit: And I can't restore from a nandroid backup (unless I put it on my SD card because the phone cannot read from the system partition).
Did you try mounting /system in recovery?
I would seriously consider Odin flashing stock root66 firmware before anything else at this point. Maybe something is corrupted in one of the underlying partitions.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Did you try mounting /system in recovery?
I would seriously consider Odin flashing stock root66 firmware before anything else at this point. Maybe something is corrupted in one of the underlying partitions.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Yes I did. If I mount it I still couldn't see /android or any other folders. I could also not clear the dalvik cache or do a factory reset.
Okay that's the consensus. I'll try restoring to stock sometime this weekend and see how that goes.
I just reverted back to stock using Odin. Reset the counter to be safe and then used odin to load a rooted stock. Then I installed goo manager and had it install TWRP 2.6.0.0.
Success! I can install and 4.3. Something must have been funky with the previous rooting job or something. Who knows. Thanks!
Right on! Good to hear you got it running good!
Sent from my SGH-T999 using xda premium
same thing
so i basically have the same thing but with mine i installed hyperdrive rom and flashing the stock rom like you said doesnt work and doesnt get rid of hyperdrive so it just has the hyperdrive boot screen and i cant get to my internal memory ect. like him please help i cant have ruined my phone by the way im a noob so please be specific and give me links thanks
Did you install stock with Odin?
I installed stock with Odin. I then installed a rooted stock and used that to reroot my phone by installing goo manager to install twrp 2.6.0.0.
Let me know if you want me to get the links for you. I got them on xda from googling
Edit: Found it. I used this http://forum.xda-developers.com/showthread.php?t=1900345.
Downloading the stock took about an hour so I would go ahead and just use odin to install the rooted stock. After you install your phone will reboot and then it will hang on a screen with Samsung on it (or at least it did for me). You then restart your phone and go into recovery and do a factory reset. Then install goo manager and reinstall the recovery by clicking on the options/settings button and selecting "Install OpenRecoveryScript." Then you can download whatever ROM you want to install. Reboot and go into recovery and you can install it.
Sent from my SGH-T999 using xda app-developers app
links please
bmdubs said:
Did you install stock with Odin?
I installed stock with Odin. I then installed a rooted stock and used that to reroot my phone by installing goo manager to install twrp 2.6.0.0.
Let me know if you want me to get the links for you. I got them on xda from googling
Edit: Found it. I used this http://forum.xda-developers.com/showthread.php?t=1900345.
Downloading the stock took about an hour so I would go ahead and just use odin to install the rooted stock. After you install your phone will reboot and then it will hang on a screen with Samsung on it (or at least it did for me). You then restart your phone and go into recovery and do a factory reset. Then install goo manager and reinstall the recovery by clicking on the options/settings button and selecting "Install OpenRecoveryScript." Then you can download whatever ROM you want to install. Reboot and go into recovery and you can install it.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
that would be awesome if you could i want to make sure i do the same downloads as you its so nice knowing im not the only one. im so screwed if i cant fix this
imfukked said:
that would be awesome if you could i want to make sure i do the same downloads as you its so nice knowing im not the only one. im so screwed if i cant fix this
Click to expand...
Click to collapse
Check your flash counter and if it's anything over 0 run Triangle Away to set it back to 0.
Then follow the directions in the stickied thread for directions on how to revert back to stock. I installed the latest t-mobile ROM from this thread http://forum.xda-developers.com/showthread.php?t=1771687
Just make sure you get the T-mobile versions
bmdubs said:
Check your flash counter and if it's anything over 0 run Triangle Away to set it back to 0.
Then follow the directions in the stickied thread for directions on how to revert back to stock. I installed the latest t-mobile ROM from this thread http://forum.xda-developers.com/showthread.php?t=1771687
Just make sure you get the T-mobile versions
Click to expand...
Click to collapse
Triangle Away only after you have stock kernel and stock recovery back on your phone. Otherwise it wont do you any good.
Odin flash the root66 firmware, triangle away, then full unroot from the supersu app.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Triangle Away only after you have stock kernel and stock recovery back on your phone. Otherwise it wont do you any good.
Odin flash the root66 firmware, triangle away, then full unroot from the supersu app.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
how do i check my triangle and triangle away it ohh and my odin doesnt have pda it has bl ap cp csc
imfukked said:
how do i check my triangle and triangle away it ohh and my odin doesnt have pda it has bl ap cp csc
Click to expand...
Click to collapse
Reboot your phone and instead of pushing volume up to put it into recovery mode push volume down to bring it into download mode. This is also what you use to revert to stock via odin.
IT WORKED
HOLY **** IT WORKED I HAVENT HAD MY PHONE FOR A WEEK I THOUGHT I WAS SOO SCREWED YOU SAVED MY ASS THANK YOU SOOOOOOO MUCH!!!!!!!:laugh::laugh::laugh::laugh:
My understanding is that it's actually kind for of hard to brick your phone from doing software modifications. It is possible but I think only if you really screw something up. Like powering down while installing a recovery or something.
Sent from my SGH-T999 using xda app-developers app
Unplugging in the midst of a firmware flash, and flashing the wrong models firmware are the easiest ways people hard brick.
If you can get download mode and recovery to boot it can be fixed most of the time.
Sent from my SGH-T999 using xda premium
Yeah what happened with me is I downloaded hyperdrive to my internal and this was my first time and I didn't install cwm or anything like that so I did the factory reset and cleared cashe but then I relized there's no way to clear your dalvik and or launch hyperdrive so I tryed booting my phone and it got stuck on the samsung logo everytime so I used odin to put cwm on my phone and I couldn't access my internal or clear dalvik so I used an external and used my old galaxy s2 to download hyperdrive on to the external and then launched it on my s3 and it installed great it let me choose everything but when I went to launch the phone it got stuck on the hyperdrive boot animation so I tryed like 10 stock roms none of them worked it wouldn't get rid of the hyperdrive boot animation iether so then I was sher the link you gave me wasn't going to work but unlike the other odin ones I did it took time instead of only taking half a second and it worked
Sent from my SGH-T999 using xda app-developers app
So my Nexus 7 still has not received the OTA update, and like a bunch of other, I decided to try to put it on myself. I tried both ways too - sideloading the zip and flashing the full factory image from google. Now I'm no newbie in this.. but for some odd reason, my Nexus 7 just wont boot past the Google logo in start up... any ideas? Ive been at it for the past couple days and still can't find anything on it
If you are not afraid to loose your data. Enter the recovery and do a factory reset.
BraddahBoi808 said:
So my Nexus 7 still has not received the OTA update, and like a bunch of other, I decided to try to put it on myself. I tried both ways too - sideloading the zip and flashing the full factory image from google. Now I'm no newbie in this.. but for some odd reason, my Nexus 7 just wont boot past the Google logo in start up... any ideas? Ive been at it for the past couple days and still can't find anything on it
Click to expand...
Click to collapse
There are always a small percentage of installations that won't work with a dirty flash (keeping your user data).
This could be because of the specific apps they have installed, flash memory corruption, etc.
That is why you should always backup before doing a system update.
The solution normally is to just wipe data/factory reset from recovery.
vbaros said:
If you are not afraid to loose your data. Enter the recovery and do a factory reset.
Click to expand...
Click to collapse
sfhub said:
There are always a small percentage of installations that won't work with a dirty flash (keeping your user data).
This could be because of the specific apps they have installed, flash memory corruption, etc.
That is why you should always backup before doing a system update.
The solution normally is to just wipe data/factory reset from recovery.
Click to expand...
Click to collapse
So wipe the data before flashing the factory image? Because I have tried booting into recovery AFTER doing the update to wipe data and it kept bootlooping still.
Sent from my Nexus 7 using xda app-developers app
BraddahBoi808 said:
So wipe the data before flashing the factory image? Because I have tried booting into recovery AFTER doing the update to wipe data and it kept bootlooping still.
Click to expand...
Click to collapse
Sorry, I didn't read your original post closely enough, if you are bootlooping at google, then it is a problem with /system and wiping won't help. If you were looping at the bouncing balls or X, then that is user data related so wiping usually fixes it.
If you are stuck at Google, something went wrong with your flash or your flash memory got corrupted.
I would try reflashing the factory image, making sure to do the -w wipe option (by default that is what flash-all.bat does)
Make sure to pay attention to any errors that might show up.
I had the same issue. You need to clear your data and cache after flashing the factory image. See my post here: http://forum.xda-developers.com/showpost.php?p=47472320&postcount=35
msk said:
I had the same issue. You need to clear your data and cache after flashing the factory image. See my post here: http://forum.xda-developers.com/showpost.php?p=47472320&postcount=35
Click to expand...
Click to collapse
It worked all fine until i wiped data and cache at the end of your process... After rebooting it still bootloops and is now hanging at the Google sign... At this point I have no idea what I'm doing wrong...
Bump.. Can someone help me?
Sent from my Nexus 7 using xda app-developers app
BraddahBoi808 said:
Bump.. Can someone help me?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
What method did you use to flash the factory images?
Sent from my Nexus 7
RMarkwald said:
What method did you use to flash the factory images?
Sent from my Nexus 7
Click to expand...
Click to collapse
Command prompt through android sdk. Didn't boot, stayed at Google screen. Then tried wugs toolkit and same thing, hung at Google boot screen...
Sent from my Nexus 7 using xda app-developers app
BraddahBoi808 said:
Command prompt through android sdk. Didn't boot, stayed at Google screen. Then tried wugs toolkit and same thing, hung at Google boot screen...
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
So you did all of the steps listed here? http://forum.xda-developers.com/showthread.php?t=2469508
Yes..
Sent from my Nexus 7 using xda app-developers app
Now sure if this means anything, but when i send the ota update zip through aideload, at the end it gives me
script succeeded: result was [/system]
Does that mean it worked or the system had something wrong??
Not sure on that one.
- Sent from my Galaxy S3
K this stupid thing must hate kit Kat or something cause no matter what ROM I try to flash that's kit kat it still don't boot. I'm tired of this already. Idk what else to do. I thought nexus devices were suppose to be the easiest ones to get updates... /end rant
Sent from my SCH-I545 using xda app-developers app
BraddahBoi808 said:
So my Nexus 7 still has not received the OTA update, and like a bunch of other, I decided to try to put it on myself. I tried both ways too - sideloading the zip and flashing the full factory image from google. Now I'm no newbie in this.. but for some odd reason, my Nexus 7 just wont boot past the Google logo in start up... any ideas? Ive been at it for the past couple days and still can't find anything on it
Click to expand...
Click to collapse
I would try this, if you can use TWRP to back up your data partition, then use Wugfresh's Rom toolkit to flash to stock KRT160, and then root, and install your recovery again.. Then.. restore just the data partiton.. That should bring your nexus to working order..
This will only work if you can move the TWRP folder off your device, use the TWRP folder via OTG to a Sdcard or thumb drive and then copy it back when your back at stock.. Sounds complicated, but its very simple.. That may work for you
Or if your brave enough, just flash Bootloader.img first, then System.img from Stock image.. That should be the simpler method..
Zaphodspeaks said:
I would try this, if you can use TWRP to back up your data partition, then use Wugfresh's Rom toolkit to flash to stock KRT160, and then root, and install your recovery again.. Then.. restore just the data partiton.. That should bring your nexus to working order..
This will only work if you can move the TWRP folder off your device, use the TWRP folder via OTG to a Sdcard or thumb drive and then copy it back when your back at stock.. Sounds complicated, but its very simple.. That may work for you
Or if your brave enough, just flash Bootloader.img first, then System.img from Stock image.. That should be the simpler method..
Click to expand...
Click to collapse
At the moment I dont really care about my data cause I dont have much on it. All i have are a couple songs and a movie, which is easily transferable because they are from my laptop. I just want this thing updated to kit kat. So, one more time, the methods I've tried using are:
Wug's toolkit to restore to KRT16O
ADB sideload to update manually using the OTA zip obtained from here
factory images obatined from google and flashed using the .bat in their zip
the link Mr. @RMarkwald posted
and through flashing stock KRT16O update from Scrosler's rom
So far, ALL methods will not allow my device to boot past the Google logo...
BraddahBoi808 said:
At the moment I dont really care about my data cause I dont have much on it. All i have are a couple songs and a movie, which is easily transferable because they are from my laptop. I just want this thing updated to kit kat. So, one more time, the methods I've tried using are:
Wug's toolkit to restore to KRT16O
ADB sideload to update manually using the OTA zip obtained from here
factory images obatined from google and flashed using the .bat in their zip
the link Mr. @RMarkwald posted
and through flashing stock KRT16O update from Scrosler's rom
So far, ALL methods will not allow my device to boot past the Google logo...
Click to expand...
Click to collapse
Then i would suggest possibly restoring your Nexus to 4.3 and see if you can atleast get it working again..
Im thinking your device maybe corrupted, but dont quote me on that.. Can you atleast boot into recovery?
I made a recovery of a Stock 4.4 from TWRP incase I needed it..
If you cant boot into recovery on the device, you can try booting into TWRP via Wugfresh's tookit.. and try and restore your Nexus that way
https://www.dropbox.com/s/mqczh3q59lydga9/2013-11-13--06-14-08 KRT16O.TWRP.zip Good luck..
Zaphodspeaks said:
Then i would suggest possibly restoring your Nexus to 4.3 and see if you can atleast get it working again..
Im thinking your device maybe corrupted, but dont quote me on that.. Can you atleast boot into recovery?
I made a recovery of a Stock 4.4 from TWRP incase I needed it..
If you cant boot into recovery on the device, you can try booting into TWRP via Wugfresh's tookit.. and try and restore your Nexus that way
https://www.dropbox.com/s/mqczh3q59lydga9/2013-11-13--06-14-08 KRT16O.TWRP.zip Good luck..
Click to expand...
Click to collapse
I can restore back to JSS15R 4.3 fine and the device works fine, no issues. It's just for some reason it doesnt like anything 4.4, which I find very odd. It still hasn't gotten to OTA update either. After updating to 4.4 and it hanging on the Google screen, it can boot into stock recovery fine. I have wiped data and cache in there too to see if that works but nothing. Thanks for all your quick help by the way. So the method your saying now.. Do I flash that from my stuck 4.4 or from rooted 4.3?
I would try that from 4.3....Dont use the stock recovery.. Flash it from TWRP..
So last night I decided to try to out the cyanmod installer . Everything seemed to go well phone booted. Now here's the strange part later on that night I tried a front face camera app the phone rebooted. I know this is a known issue. But my phone would not reboot after. Or even go into recovery mode. I tried reflashing the recovery via Odin. That did not work either. I feared my phone is bricked. I googled found a rooted version of MD 4 tar file. I attempted to flash this via Odin. All went well. Now the strange thing I still cannot flash recovery via Odin. I used to work fine before. Nothing haschanged on my computer. I fear maybe somehow I corrupted something. The only way I was able to flash recovery was via goo manager. Now the strange thing when I first tried to boot into recovery after goo manager. The phone flashed and said installing open recovery script. Then rebooted too system. i then tried to reboot into recovery.then the phone booted fine . My only issue is when I flashed the recovery via Odin it always set my day and time correctly for the recovery. And now after the goo manager method it's just way off
Sent from my SPH-L710 using Tapatalk
i should add when flashing recovery via odin it seems to work but i get recovery,reset and never a green pass up top now in the left hand box.i almost feel like i need to some how wipe all the phone chips. feel like the reinstall of md4 just overwrote and made it functional. but feel like maybe there is a under lying issue causing me from being able to odin flash recovery now.
Have you tried going to complete 100% stock and re-root? maybe going back to stock will help starting clean and making sure nothing goes wrong.
EverDeathly said:
Have you tried going to complete 100% stock and re-root? maybe going back to stock will help starting clean and making sure nothing goes wrong.
Click to expand...
Click to collapse
couldnt last night was on call for work. but i did flash 100 stock with root. so. idk im going to try 100 stock tonight with no root. then reroot the thing.
kaos420 said:
couldnt last night was on call for work. but i did flash 100 stock with root. so. idk im going to try 100 stock tonight with no root. then reroot the thing.
Click to expand...
Click to collapse
makes sense, it was only a suggestion since going back to stock did help solve some issues my device had.
EverDeathly said:
Have you tried going to complete 100% stock and re-root? maybe going back to stock will help starting clean and making sure nothing goes wrong.
Click to expand...
Click to collapse
I agree. I just suggested this in another post. Sometimes, as much as it sucks, it's best to go back to the beginning and start over. Try to remember your steps as you get your office back to the way you want it, and ifv these issues happen again, you'll know what is causing it. Might have been a corrupted file that you flashed, that's what I'd guess. And what recovery are you using? I'm on the latest CWM touch and my backups are always a wrong time, life 1970 Would love to get that fixed. Good luck!
Sent from my SPH-L710 using XDA Premium 4 mobile app
Hi all, hope you are doing well (I also hope that you can help me ).
I just recently got a replacement phone because my other one had a faulty speaker (crackling, etc.). The other one was rooted (via CF-AutoRoot) and had TWRP on it, and I made a complete nandroid backup of it onto my MicroSD card.
I rooted the new phone using CF-AutoRoot via Odin and installed TWRP on it as well (also via Odin). Then I swapped the SD card and SIM card and restored the complete backup to the new phone.
It took a while, but the phone booted up and I had two working clones, the only way to tell which was which was by changing the volume and hearing the crackling on the old one.
So the new phone worked all day (was able to make calls and everything, and the GUI that was customized with Wanam Xposed even looked good), however when I restarted it to put in my backup battery, I didn't have root for some reason. I tried and tried to get it back (reinstalled SuperSU, tried the TWRP method) to no avail.
I re-flashed CF-AutoRoot just to see, and the phone booted up but and for some reason SuperSU was gone (and I didn't have root). When I restarted, I got a boot loop and could not even get back into a recovery.
I got tired of this and wanted a fresh start, so I just flashed the stock ROM via ODIN and did a factory reset. However now if I try to boot, the Samsung logo will flash and just shut down, and I won't be able to get into the recovery no matter what. If I flash a recovery (CWM, TWRP or even stock), the recovery will work until I try to actually try to boot the phone. I've tried taking the battery out for a good 5 minutes and retrying (also tried swapping batteries), I've tried doing complete resets galore from all three recoveries mentioned with no success. Obviously Download mode still works so I know it's not completely bricked, but I am getting a little scared.
Any and all help is extremely appreciated as I would prefer not to have such an expensive paper-weight.
Thanks a bunch!
I would suggest going all the way back stock on stock firmware via Odin. Then re-root, TWRP, and re-download the rom of your choice. Dont restore the backup. Just start fresh.
I Think My S4 Is Insane
SICK MADE DEVELOPMENT
alloycowboy said:
I would suggest going all the way back stock on stock firmware via Odin
Click to expand...
Click to collapse
Thanks for the reply.
And okay, I tried that.
I flashed stock using the T-Mobile ROM I found here: galaxys4root_(dot)_com/galaxy-s4-stock-firmware/
This is the same ROM file I used to completely restore the phone I had to return, and that worked fine.
But it still won't boot up or go into recovery mode (just shows the Samsung logo for a split second before shutting down).
One thing I did do on the other phone was flash a kernel which had set-MUID to off so I could WiFi tether, but I thought flashing the stock ROM would revert that back as well. Do you think that's the reason it messed up so badly? I restored the backup from the other phone with a different kernel? Right after I restored the backup to the new phone and everything was working, I remember checking the kernel info in the About Phone section of the settings, and it was in fact the kernel I'd installed on the other phone.
TLDR: Tried flashing stock ROM to no avail. Download mode still works but can't enter recovery mode or boot.
Are you doing a factory reset after flashing stock firmware?
I Think My S4 Is Insane
SICK MADE DEVELOPMENT
I'd flash a stock rooted ROM. Get that root and recovery back. The konane tar file from the stickies, perhaps.
Sent from my SGH-M919 using xda app-developers app
alloycowboy said:
Are you doing a factory reset after flashing stock firmware?
Click to expand...
Click to collapse
Yeah, as soon as it finished installing I went into stock recovery and did a factory reset.
Karakoram2 said:
I'd flash a stock rooted ROM. Get that root and recovery back. The konane tar file from the stickies, perhaps.
Click to expand...
Click to collapse
Alright, I'll try that.
Is the konane tar an actual ROM? And what do you mean in the stickies?
Sorry, not very familiar with XDA forums.
Samsung GT-I9500 flashes n switches off!
BallisticallySimilar said:
Hi all, hope you are doing well (I also hope that you can help me ).
I just recently got a replacement phone because my other one had a faulty speaker (crackling, etc.). The other one was rooted (via CF-AutoRoot) and had TWRP on it, and I made a complete nandroid backup of it onto my MicroSD card.
I rooted the new phone using CF-AutoRoot via Odin and installed TWRP on it as well (also via Odin). Then I swapped the SD card and SIM card and restored the complete backup to the new phone.
It took a while, but the phone booted up and I had two working clones, the only way to tell which was which was by changing the volume and hearing the crackling on the old one.
So the new phone worked all day (was able to make calls and everything, and the GUI that was customized with Wanam Xposed even looked good), however when I restarted it to put in my backup battery, I didn't have root for some reason. I tried and tried to get it back (reinstalled SuperSU, tried the TWRP method) to no avail.
I re-flashed CF-AutoRoot just to see, and the phone booted up but and for some reason SuperSU was gone (and I didn't have root). When I restarted, I got a boot loop and could not even get back into a recovery.
I got tired of this and wanted a fresh start, so I just flashed the stock ROM via ODIN and did a factory reset. However now if I try to boot, the Samsung logo will flash and just shut down, and I won't be able to get into the recovery no matter what. If I flash a recovery (CWM, TWRP or even stock), the recovery will work until I try to actually try to boot the phone. I've tried taking the battery out for a good 5 minutes and retrying (also tried swapping batteries), I've tried doing complete resets galore from all three recoveries mentioned with no success. Obviously Download mode still works so I know it's not completely bricked, but I am getting a little scared.
Any and all help is extremely appreciated as I would prefer not to have such an expensive paper-weight.
Thanks a bunch!
Click to expand...
Click to collapse
The same thing has happened to me! Did you find any solustion for this?? Please help!! This was my first attempt and i have no idea wats going on!
Here are the stickies for our forum: http://forum.xda-developers.com/showthread.php?t=2419828
Sent from my SGH-M919 using XDA Premium 4 mobile app
What I did to unbrick my T-Mobile S4 (SGH-M919)
killerwolf2121 said:
The same thing has happened to me!
Did you find any solutions for this? Please help if you can; this was my first attempt and I have to idea what's going on.
Click to expand...
Click to collapse
Well, for the first problem, flashing the stock ROM did it for me. I followed this tutorial.
For the second issue of not booting up after displaying the Samsung logo; my battery just simply was too dead and didn't have enough juice to start. You have no idea how stupid I felt.
Let your phone charge from the wall cable for a good while before trying all this again; then see if that works. It did it for me. If it doesn't, I'm not sure what else to try.
After that (if it works), if you still want root, just flash CF-Auto-Root and then a custom recovery if you want (like ClockworkMod Recovery (click the little version link, not the "Download ROMs" button) or TWRP via GooManager) (I use TWRP)
All the best and let me know how it went!
Keep in mind that I did this on an SGH-M919 (T-Mobile S4) running Android 4.2.2, so if you don't have that, I have no idea if any of the above will work for you. Also I'm pretty sure if you do have 4.3, you will ruin your warranty forever due to the Knox restriction they added (if you haven't already).
Android_Monsters said:
Here are the stickies for our forum: http://forum.xda-developers.com/showthread.php?t=2419828
Click to expand...
Click to collapse
Thanks
BallisticallySimilar said:
Well, for the first problem, flashing the stock ROM did it for me. I followed this tutorial.
For the second issue of not booting up after displaying the Samsung logo; my battery just simply was too dead and didn't have enough juice to start. You have no idea how stupid I felt.
Let your phone charge from the wall cable for a good while before trying all this again; then see if that works. It did it for me. If it doesn't, I'm not sure what else to try.
After that (if it works), if you still want root, just flash CF-Auto-Root and then a custom recovery if you want (like ClockworkMod Recovery (click the little version link, not the "Download ROMs" button) or TWRP via GooManager) (I use TWRP)
All the best and let me know how it went!
Keep in mind that I did this on an SGH-M919 (T-Mobile S4) running Android 4.2.2, so if you don't have that, I have no idea if any of the above will work for you. Also I'm pretty sure if you do have 4.3, you will ruin your warranty forever due to the Knox restriction they added (if you haven't already).
Thanks
Click to expand...
Click to collapse
I am on 4.3 and yes, flashing the stock rom worked for me too! relief thanks a ton!
Having trouble unbricking M919 T-Mobile
Hi, I'm trying to unbrick my M919 through Odin. I have all the updated software, but I keep getting a fail message. Any help would be appreciated.
Alright guys, getting a little frustrated here. I'm trying to go from Carbon to OptimusDE ZVC, When I flash OptimusDE, everything boots up fine but there isn't data to start with. I go into settings to update PRL and as soon as it starts to update, the phone reboots. Try to connect to WiFi, the phone reboots. Also, Exchange Services crash immediately after boot up.
What I've tried - Re-flashing, wiping caches and then also doing a factory reset, flashing ZVC radio.
Nothing seems to be getting this working. Anyone know what I need to do to get things working here? Any help would be much appreciated. Thanks!
latrotoxin1986 said:
Alright guys, getting a little frustrated here. I'm trying to go from Carbon to OptimusDE ZVC, When I flash OptimusDE, everything boots up fine but there isn't data to start with. I go into settings to update PRL and as soon as it starts to update, the phone reboots. Try to connect to WiFi, the phone reboots. Also, Exchange Services crash immediately after boot up.
What I've tried - Re-flashing, wiping caches and then also doing a factory reset, flashing ZVC radio.
Nothing seems to be getting this working. Anyone know what I need to do to get things working here? Any help would be much appreciated. Thanks!
Click to expand...
Click to collapse
Try flashing the new Stocktimus ROM and see if the same thing happens. If it does, you may just have to re-root.
Sent from my Optimus G using Tapatalk
iamterence said:
Try flashing the new Stocktimus ROM and see if the same thing happens. If it does, you may just have to re-root.
Sent from my Optimus G using Tapatalk
Click to expand...
Click to collapse
I'm not sure how root would pertain to this issue. I'll give Stocktimus a try, but I tried engine's other stock ROM's a month or so back and had the exact same issue.
Weird. Did you try actually activating?
Sent from my Optimus G using Tapatalk
AFschizoid said:
Weird. Did you try actually activating?
Sent from my Optimus G using Tapatalk
Click to expand...
Click to collapse
The phone is activated, but trying to run the activation in settings causes reboot. Receives phone calls no problem. Just downloaded Stocktimus O and same thing. No data, crash on PRL update or Profile update, crash on WiFi activation. I really don't understand what's going on...
Yeah I've not had that issue and I've flashed back and forth from stock based to aosp and vice versa. Might be your efs got screwed up. Try lgnpst or LG flash tool (I prefer the latter because it takes it to an 'out of the box' state, activation required ) and try activating again
Sent from my Optimus G using Tapatalk
That has happened to me before going from an AOSP rom to one of the available stock roms. Don't remember which one.
But I remember flashing the TWRP recovery. I was on Philz Touch Clockworkmod.
And then performed all the required wipes and reset then flashed Stockimus-D and viola, no FC's. no reboots. No more problems.
If problems persist used TeenyBins via LGNPST
A couple other things to try also:
Make sure you're wiping /system also.
Sometimes CM/AOSP Roms can mess up your SD. You may need to wipe it also. Just make sure you back it up first. That's happened to me a few times.
Sent from my LG-LS970 using XDA Premium 4 mobile app
engine95 said:
A couple other things to try also:
Make sure you're wiping /system also.
Sometimes CM/AOSP Roms can mess up your SD. You may need to wipe it also. Just make sure you back it up first. That's happened to me a few times.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Lol, so funny story. I did LGNPST and got back to full stock. I had to use an oldddd ZVC .bin file, not a teenybin. Re-rooted, unlocked, put CWM 6.0.4.6 back on the phone and created a stock backup. I didn't mention before but I had long deleted my stock backups, so I didn't have a stock ROM on my phone at all to flash back to. Anyways, back on full stock, everything is working great, go into CWM, create a backup and flash Stocktimus O. It says it installed successfully, so I reboot...just the normal Sprint boot screen, everything is total stock. I'm wondering if perhaps, like a previous poster brought up, it's a CWM issue. I'll switch over to TWRP and give it a shot, report back later. I prefer CWM because I don't have any issues flashing AOSP ROM's whereas TWRP, on all versions I've tried, will fail with some ROM's while others work fine.
latrotoxin1986 said:
Lol, so funny story. I did LGNPST and got back to full stock. I had to use an oldddd ZVC .bin file, not a teenybin. Re-rooted, unlocked, put CWM 6.0.4.6 back on the phone and created a stock backup. I didn't mention before but I had long deleted my stock backups, so I didn't have a stock ROM on my phone at all to flash back to. Anyways, back on full stock, everything is working great, go into CWM, create a backup and flash Stocktimus O. It says it installed successfully, so I reboot...just the normal Sprint boot screen, everything is total stock. I'm wondering if perhaps, like a previous poster brought up, it's a CWM issue. I'll switch over to TWRP and give it a shot, report back later. I prefer CWM because I don't have any issues flashing AOSP ROM's whereas TWRP, on all versions I've tried, will fail with some ROM's while others work fine.
Click to expand...
Click to collapse
So LGNPST got everything working. But when you installed Stocktimus O you got stuck on the Sprint boot screen?
Did you give it about 4min to make sure it booted up?
It should work with both TWRP and CWM. I installed with both when I built them.
I know you've flashed before, but just in case, wipe /system, /data, /dalvic, and /cache.
If you don't want to do this next part, I'll see if it's something on my end:
If it doesn't install with TWRP, could you wipe your SD and try it again? I know it'd be a pain, but at least it would let me know if I need to fix the updater scripts.
Make sure your phone boots up. Then in recovery wipe "internal data" or SD and reboot. Your phone should still boot as long as you don't wipe /system.
If for some reason it won't boot, you may need to ADB sideload a rom, or LGNPST again.
Just trying to cover everything.
engine95 said:
So LGNPST got everything working. But when you installed Stocktimus O you got stuck on the Sprint boot screen?
Did you give it about 4min to make sure it booted up?
It should work with both TWRP and CWM. I installed with both when I built them.
I know you've flashed before, but just in case, wipe /system, /data, /dalvic, and /cache.
If you don't want to do this next part, I'll see if it's something on my end:
If it doesn't install with TWRP, could you wipe your SD and try it again? I know it'd be a pain, but at least it would let me know if I need to fix the updater scripts.
Make sure your phone boots up. Then in recovery wipe "internal data" or SD and reboot. Your phone should still boot as long as you don't wipe /system.
If for some reason it won't boot, you may need to ADB sideload a rom, or LGNPST again.
Just trying to cover everything.
Click to expand...
Click to collapse
It didn't get stuck, it just booted as though I hadn't flashed Stocktimus O even though it said it had successfully installed. Kinda weird...but it's definitely not on your end. I've done something, at some point, that has borked my ability to flash stock. I've thought about totally wiping SD....just LGNPST after that. I dunno.
TWRP didn't give me any different results. Same deal, just booted with the original Sprint screen, not your boot animation, nothing had changed...
latrotoxin1986 said:
It didn't get stuck, it just booted as though I hadn't flashed Stocktimus O even though it said it had successfully installed. Kinda weird...but it's definitely not on your end. I've done something, at some point, that has borked my ability to flash stock. I've thought about totally wiping SD....just LGNPST after that. I dunno.
TWRP didn't give me any different results. Same deal, just booted with the original Sprint screen, not your boot animation, nothing had changed...
Click to expand...
Click to collapse
It's gotta be on the SD. I don't know how, or where, no file explorer shows anything weird, but CM/AOSP ROM'S have got to be putting something on it for it not to flash. I've had issues more than once when I've had to wipe my SD to fix it.
We gotta got you going so you can get us some more Carbon, LS970 style.
engine95 said:
It's gotta be on the SD. I don't know how, or where, no file explorer shows anything weird, but CM/AOSP ROM'S have got to be putting something on it for it not to flash. I've had issues more than once when I've had to wipe my SD to fix it.
We gotta got you going so you can get us some more Carbon, LS970 style.
Click to expand...
Click to collapse
I'm TRYING to build it right now. Getting some really unusual errors. The last time I got one of them, I just restarted the build and it finished fine. This time though I'm getting Java Runtime Environment crashes though and something else...not sure what's up with that. Keep chipping away at it though
latrotoxin1986 said:
I'm TRYING to build it right now. Getting some really unusual errors. The last time I got one of them, I just restarted the build and it finished fine. This time though I'm getting Java Runtime Environment crashes though and something else...not sure what's up with that. Keep chipping away at it though
Click to expand...
Click to collapse
I had the reboot issue when it connected to data too when flashing back and forth from cm/aosp ROMs to stock. What resolves the issue for me is to use TWRP and go to advanced wrote and wipe everything EXCEPT internal. I used to have that issue all the time when using cwm recovery but philz recovery also seems to be ok when flashing back and forth hope this helps!
Sent from my LG-LS970 using XDA Premium 4 mobile app