Related
Note: I may not use terms correctly, I have spent the past hour reading threads similar to mine in order to (hopefully) use the correct terms to describe my predicament.
I was using TriForce ROM 3.0 and I wanted to mix things up a bit because it was too much like the stock ROM. I found Negalite S4 and tried my hand at that, with devastating consequences. I booted my phone into TWRP did a wipe and then proceeded to install the Negalite S4.zip onto my phone. It got stuck in a boot loop. After a good 30~ minutes of it continuously rebooting I turned it off and booted back into TWRP. However, now that my phone was wiped, it is not a recognized device by my computer any longer. Since I wiped the phone clean the .zip is no longer on my phone either. So, all I have now is a phone that can boot into recovery (TWRP); which is a soft-brick (correct me if I'm wrong).
I have read other threads and the xda community informs the user to use KIES or ODIN (I have used ODIN once before). However, try as hard as I can to understand their directions... I don't know what to do with ODIN.
My computer does not recognize my device at all. It will only boot into recovery otherwise it's stuck in an infinite boot loop. I am really scared that I have ruined such a valuable phone and so I am not thinking clearly - which is only adding to my "noobishness."
Can anyone please help me out in a way that I can understand? All help is much appreciated!
_retro said:
Note: I may not use terms correctly, I have spent the past hour reading threads similar to mine in order to (hopefully) use the correct terms to describe my predicament.
I was using TriForce ROM 3.0 and I wanted to mix things up a bit because it was too much like the stock ROM. I found Negalite S4 and tried my hand at that, with devastating consequences. I booted my phone into TWRP did a wipe and then proceeded to install the Negalite S4.zip onto my phone. It got stuck in a boot loop. After a good 30~ minutes of it continuously rebooting I turned it off and booted back into TWRP. However, now that my phone was wiped, it is not a recognized device by my computer any longer. Since I wiped the phone clean the .zip is no longer on my phone either. So, all I have now is a phone that can boot into recovery (TWRP); which is a soft-brick (correct me if I'm wrong).
I have read other threads and the xda community informs the user to use KIES or ODIN (I have used ODIN once before). However, try as hard as I can to understand their directions... I don't know what to do with ODIN.
My computer does not recognize my device at all. It will only boot into recovery otherwise it's stuck in an infinite boot loop. I am really scared that I have ruined such a valuable phone and so I am not thinking clearly - which is only adding to my "noobishness."
Can anyone please help me out in a way that I can understand? All help is much appreciated!
Click to expand...
Click to collapse
Okay, download and install Samsung drivers from the Internet if your phone isn't installing them on its own. Download MDL stock. Open ODIN. Put your phone in download mode. ODIN should see your phone. Flash stock MDL. Use goo manager to install TWRP again after your booted on stock MDL. Or use ODIN to do it. Redownload the custom ROM you want and then flash in TWRP. Also wiping the phones dalvik, cache system ect shouldn't have erased your SD card in the first place. You mist have accidentally checked the wipe SD card in advanced wipe options. You never need to do that. So next time also have a nandroid backup on your external SD. I keep one on internal as well in case external card goes bad cause sometimes that happens. And never select that wipe SD card option. Unless of course you really do want to wipe your SD card. Don't do that and keep a full backup of your last working ROM and you'll not have this problem again.
3ncrypt3d said:
Okay, download and install Samsung drivers from the Internet if your phone isn't installing them on its own. Download MDL stock. Open ODIN. Put your phone in download mode. ODIN should see your phone. Flash stock MDL. Use goo manager to install TWRP again after your booted on stock MDL. Or use ODIN to do it. Redownload the custom ROM you want and then flash in TWRP. Also wiping the phones dalvik, cache system ect shouldn't have erased your SD card in the first place. You mist have accidentally checked the wipe SD card in advanced wipe options. You never need to do that. So next time also have a nandroid backup on your external SD. I keep one on internal as well in case external card goes bad cause sometimes that happens. And never select that wipe SD card option. Unless of course you really do want to wipe your SD card. Don't do that and keep a full backup of your last working ROM and you'll not have this problem again.
Click to expand...
Click to collapse
Thank-you for the detailed response, I'll get started now! I did wipe the SD card, you're right. I'm so glad that you posted, thanks again.
If I need help I'll edit this post (no bumping within 24 hours). I'm hoping I have enough smarts to knock this out though. Again, thank you so much.
EDIT: Excuse my ignorance. I'm not sure what MDL stock is, I figured it was the default ROM - I have a nandroid of that. However, even after re-installing the samsung drivers, rebooting both my phone and computer - nothing happens. I don't know how to proceed from here. I can imagine I'm becoming a pain and do apologize.
_retro said:
Thank-you for the detailed response, I'll get started now! I did wipe the SD card, you're right. I'm so glad that you posted, thanks again.
If I need help I'll edit this post (no bumping within 24 hours). I'm hoping I have enough smarts to knock this out though. Again, thank you so much.
EDIT: Excuse my ignorance. I'm not sure what MDL stock is, I figured it was the default ROM - I have a nandroid of that. However, even after re-installing the samsung drivers, rebooting both my phone and computer - nothing happens. I don't know how to proceed from here. I can imagine I'm becoming a pain and do apologize.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2375523
The link above is the tar file for stock MF9. If you just use the link for the from the first post you just need to download the first file (not the kernel). Once downloaded you need to extraxt that zip and you will get a .tar.md5 file from it. Later open odin and make sure only auto reboot is checked. Click on the PDA slot and find the .tar.md5 file you downloaded click on it. Next put your phone into download mode and connect it to your computer. Wait for it to install drivers and you will see a yellow box with "com:[some number]" once you see that click start and from there let it do its thing and whoola you have your phone back to MF9 stock. Good luck!
Sent from my SPH-L720
ROMANTiC KiD said:
http://forum.xda-developers.com/showthread.php?t=2375523
The link above is the tar file for stock MF9. If you just use the link for the from the first post you just need to download the first file (not the kernel). Once downloaded you need to extraxt that zip and you will get a .tar.md5 file from it. Later open odin and make sure only auto reboot is checked. Click on the PDA slot and find the .tar.md5 file you downloaded click on it. Next put your phone into download mode and connect it to your computer. Wait for it to install drivers and you will see a yellow box with "com:[some number]" once you see that click start and from there let it do its thing and whoola you have your phone back to MF9 stock. Good luck!
Sent from my SPH-L720
Click to expand...
Click to collapse
Well, you did it! That post is solid, I understood every-bit! My phone (most likely) is downloading the firmware now. I don't know how long it will take to get off the "Downloading... Do not turn off target !!" screen, but I'll edit this post after letting it sit over night! Thank you both so much.
_retro said:
Well, you did it! That post is solid, I understood every-bit! My phone (most likely) is downloading the firmware now. I don't know how long it will take to get off the "Downloading... Do not turn off target !!" screen, but I'll edit this post after letting it sit over night! Thank you both so much.
Click to expand...
Click to collapse
Your welcome glad to help again, should take less than 10 mins. If its more than that just reboot your computer and repeat the steps from opening odin and finding your file. Another GS4 saved ;D
Sent from my SPH-L720
ROMANTiC KiD said:
Your welcome glad to help again, should take less than 10 mins. If its more than that just reboot your computer and repeat the steps from opening odin and finding your file. Another GS4 saved ;D
Sent from my SPH-L720
Click to expand...
Click to collapse
You were right, it was quite snappy. I cannot believe I was so panicked over this! My babies safe ... for now.
So how did Twrp wipe nor SD card? When by boot into recovery and immediately click on Wipe, it'll wipe everything Necessary except the internal and external memory. Did you click the option to choose what you want to wipe? Happens more than ya may think, cause I've done it myself lol. Good to hear it's back up, I still get freaked out by those occurrences
Sent from my SPH-L720 using Tapatalk 2
reverepats said:
So how did Twrp wipe nor SD card? When by boot into recovery and immediately click on Wipe, it'll wipe everything Necessary except the internal and external memory. Did you click the option to choose what you want to wipe? Happens more than ya may think, cause I've done it myself lol. Good to hear it's back up, I still get freaked out by those occurrences
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
It wasn't human error through TWRP, it was an error while flashing Negalite. It asks if you want to wipe everything, data, or nothing at all. Silly me thought let's wipe EVERYTHING! Heheh
3ncrypt3d said:
Okay, download and install Samsung drivers from the Internet if your phone isn't installing them on its own. Download MDL stock. Open ODIN. Put your phone in download mode. ODIN should see your phone. Flash stock MDL. Use goo manager to install TWRP again after your booted on stock MDL. Or use ODIN to do it. Redownload the custom ROM you want and then flash in TWRP. Also wiping the phones dalvik, cache system ect shouldn't have erased your SD card in the first place. You mist have accidentally checked the wipe SD card in advanced wipe options. You never need to do that. So next time also have a nandroid backup on your external SD. I keep one on internal as well in case external card goes bad cause sometimes that happens. And never select that wipe SD card option. Unless of course you really do want to wipe your SD card. Don't do that and keep a full backup of your last working ROM and you'll not have this problem again.
Click to expand...
Click to collapse
ODIN IS NOT RECOGNISING MY PHONE ...WHAT TO DO????:crying::crying::crying:
Ridddeathmetal said:
ODIN IS NOT RECOGNISING MY PHONE ...WHAT TO DO????:crying::crying::crying:
Click to expand...
Click to collapse
Reinstall drivers, use different USB ports, used different USB cables?
Sent from my SPH-L720 using xda app-developers app
romantic kid said:
reinstall drivers, use different usb ports, used different usb cables?
Sent from my sph-l720 using xda app-developers app
Click to expand...
Click to collapse
tried 4 ports...in different pc also but same result used 3 cables...but none recognising it.....drivers have been downloaded and reinstalled
Hi guys,
I tried to update my Nexus 4 to 4.4 when Google pushed the update out for it yesterday, I forgot I had unlocked the phone (I don't have any custom ROMs on it, just SuperSU.)
Every time I try and power it on, the loading screen is endless, although I can hold power and volume down to enter recovery mode, nothing seems to be working.
I am a bit of a novice so any help or suggestions would be really appreciated!
Thanks.
The first few pages of the forum is littered with posts like this, i was in the same situation.
What i did was download the 4.3 rom from google, and flash /boot and /system onto the phone. I suspect the 4.4 rom would also work.
This got the phone booting without harming (most of) my data, but much of the UI was mangled and didnt work properly. I tried to backup my images over USB but it didnt work, you might have a better result. I also wanted to backup my SMS but they had all vanished.
I rebooted the phone to recovery (TWRP) and used adb to backup the sdcard (adb pull /sdcard sdcard) then did a full flash using the 4.4 rom downloaded from google and that got it working again. Then i reflashed the latest version of TWRP recovery and SuperSU.
Hope that helps.
That's really helpful, thanks! Is there ANY chance of a step-by-step? I'm a complete 'noob' probably a mistake to root in the first place :crying:
If you're busy don't worry, just don't want to **** things up more than I have haha.
Thanks, appreciate it.
GeorgeAmodio said:
That's really helpful, thanks! Is there ANY chance of a step-by-step? I'm a complete 'noob' probably a mistake to root in the first place :crying:
If you're busy don't worry, just don't want to **** things up more than I have haha.
Thanks, appreciate it.
Click to expand...
Click to collapse
Look here http://forum.xda-developers.com/showthread.php?t=2010312 for flashing a factory image guide.
gee2012 said:
Look here http://forum.xda-developers.com/showthread.php?t=2010312 for flashing a factory image guide.
Click to expand...
Click to collapse
Got stuck in google screen, tried to flash factory images but my pc won't detect the phone anymore. Any advice?
Edit: Solved.
arffrhn said:
Got stuck in google screen, tried to flash factory images but my pc won't detect the phone anymore. Any advice?
Edit: Solved.
Click to expand...
Click to collapse
Cheers guys, a lot more helpful than the bloke from Google. Will try it in the morning!
This will surely help
If somebody is facing boot loop after kitkat update on nexus 4 and no data backup can try to go to safe mode and backup their data. To goto safe mode on boot screen just keep pressing up and down volume button for some time phone will get into safe mode and can be backed up.
Hi,
It also happened to me, dont know if it is related to having ROOT or not, but i had to manually flash factory image (4.4) and it worked. I flashed everything except userimage.img but on first boot it took like 15 minutes to reboot and then all my personal data (photo, music...) was gone....
So just be cautious before upgrading!
Hi,
It also happened to me, dont know if it is related to having ROOT or not, but i had to manually flash factory image (4.4) and it worked. I flashed everything except userimage.img but on first boot it took like 15 minutes to reboot and then all my personal data (photo, music...) was gone....
So just be cautious before upgrading!
gee2012 said:
Look here http://forum.xda-developers.com/showthread.php?t=2010312 for flashing a factory image guide.
Click to expand...
Click to collapse
Yeah that is pretty much what I did to fix mine except that I did not flash the userdata (step 10 in chapter D) so that I would't loose my data.
arffrhn said:
Got stuck in google screen, tried to flash factory images but my pc won't detect the phone anymore. Any advice?
Edit: Solved.
Click to expand...
Click to collapse
What did you end up doing for your PC to detect your phone?
iamj00 said:
What did you end up doing for your PC to detect your phone?
Click to expand...
Click to collapse
I had sideloaded a rom in recovery so that it will replace the lost system.img on my phone. Then, it booted up and I flashed back factory images the usual way. Everything is running smoothly again.
arffrhn said:
I had sideloaded a rom in recovery so that it will replace the lost system.img on my phone. Then, it booted up and I flashed back factory images the usual way. Everything is running smoothly again.
Click to expand...
Click to collapse
I don't know what any of that means or how to do it...
iamj00 said:
I don't know what any of that means or how to do it...
Click to expand...
Click to collapse
This is sideload guide. And the is the rom I used to sideload before: Purity. After I had successfully booted into the system. I flashed 4.4 factory images using this awesome noob friendly guide for a clean kitkat update.
arffrhn said:
I had sideloaded a rom in recovery so that it will replace the lost system.img on my phone. Then, it booted up and I flashed back factory images the usual way. Everything is running smoothly again.
Click to expand...
Click to collapse
iamj00 said:
What did you end up doing for your PC to detect your phone?
Click to expand...
Click to collapse
Installing the driver. Refer to this thread http://forum.xda-developers.com/showthread.php?t=1992345
Boot to bootloader and connect to your PC, usually Windows will find the driver automatically
Okay, so I feel like I've looked everywhere and tried everything for this problem with my Nexus 7. The closest thing I found was this:
(Google: Nexus 7 2012 rebooting reverts back to previous state)(I can't post outside links as I am a new member)
and there was no followup reply, and the thread was closed.
Here's my problem (I want to be very detailed in case I missed something):
I've had Cyanogenmod 11 on my Nexus 7 for a long time (I think I started with M1 release). I recently installed the M7 release after previous nightly and it was working so smooth that I had finally decided there was no need to install nighties anymore. Everything was going fine until the night after when I noticed it kept rebooting, so I reverted it back to the nightly I had before (June 11th?) because I assumed it was probably something bad with the update. Except it did the same thing, rebooting after a couple minutes, which is weird because it never did that with this nightly. There was never enough time to download the nightlies before it reboots so I tried downloading them on my laptop and then just transferring them to my nexus via usb. I put it in the cmupdate folder so that I could quickly go to settings and press install (as it can see the update from there). It rebooted to install, but it went into cwm with what appears that nothing happened, and I usually never see cwm when updating this way. So I figured, while I'm here, I could just "install zip" and find that zip I just transferred and install, right? Nope. The zip mysteriously vanished, yet the other two updates were still there (M7 and the previous nightly). So I just rebooted just to try the process again, maybe the file transfer didn't work. Same thing happened. So I went to cwm and tried wiping cache, nothing. Wiped dalvik cache, nothing. So I went and did it, wiped data/factory reset, that did NOTHING, as in I rebooted and everything was still there.
So I got to the point where I just wanted to see if I could just revert back to stock so I have a place to start from, maybe contemplate on just staying there for a while where there shouldn't be problems. So I got that all set up with fastboot, got the latest 4.4.3 image, unarchived until I could get to the flashall.bat I ran that and it was successful. Okay now I can just boot into that, right? Suddenly I see the cyanogenmod boot graphic. What happened? Even all of my apps are still there. Still freezing and rebooting.
I tried reverting to stock manually by erasing then formating everything that I can, flashed bootloader (grouper 4.23), flashed zip, locked bootloader, unlocked bootloader (trying to erase as much as I can). This did nothing, still cyanogenmod. I tried a third time while rebooting to bootloader with each step. Nothing. I tried doing a factory reset within cyanogenmod, but when I press the "erase everything" button it doesn't lead anywhere, so I could never get that to start the process. I also tried doing the erasing and formatting from cwm (which isn't being overwritten, as it seems, by all the attempts at flashing stock?), nothing.
I was curious. I uninstalled Netflix because it was right there in my dock. Then I rebooted myself. When it came back up, Netflix was still there. I tried various things, also going back to locking the bootloader and rebooting the bootloader, it still said it was unlocked. So I came to the conclusion that literally nothing was being written or committed to the sdcard no matter what I do.
I did some more research and found that article up top. So I tried uninstalling some apps because it said it may have something to do with a third-party app misbehaving (seems a bit extreme, I'll do it anyways), but there's never enough time to erase everything before it reboots. It also said to try to get it into safemode. I think I might have gotten there once but it still rebooted (which makes me think that it didn't get to safemode), the rest of the times it wouldn't even get to the lockscreen.
What I'm currently attempting is to see if I can get it into safemode, or I'm trying to uninstall or stop/clear data for every single app with an intentional reboot each time.
Anyone got any idea what's going on? Is it maybe a bad sector, or worse, bad sdcard?
Gonna bump this. Still no luck on my part.
Anyone have any idea?
Perhaps somehow something got triggered to prevent anything being written to the sdcard? (Kinda like the lock switch on actual sdcards?) Is everything I've been doing going straight to memory since everything reverts back after a reboot? That's the only explanation I can think of.
Perhaps there's more I could try. I'm only moderately knowledgeable with things like fastboot and roms, so maybe someone with more experience might have more insight. Please, chime in.
Thanks in advance,
JM
Same problem here....
Flash factory image
USBhost said:
Flash factory image
Click to expand...
Click to collapse
Although you flash the factory image, the previously ROM boots again, that is precisely the problem.
Amd64bits said:
Although you flash the factory image, the previously ROM boots again, that is precisely the problem.
Click to expand...
Click to collapse
O ok
Amd64bits said:
Same problem here....
Click to expand...
Click to collapse
Curious, how did you get to the point where it boots the previous rom? Same as me or something else? Are you using cyanogenmod? I want to try and rule out some possibilities.
I'm at the same point since last time. Trying to nuke the hell out of cyanogenmod but it won't go away!
This just outright baffles me!
Try this out format /system /cache /data with twrp to f2fs
If it doesn't boot then cheers you got out if the loop
Then adb sideload an f2fs ROM and kernel them flash
USBhost said:
Try this out format /system /cache /data with twrp to f2fs
If it doesn't boot then cheers you got out if the loop
Then adb sideload an f2fs ROM and kernel them flash
Click to expand...
Click to collapse
I have clockworkmod recovery v6.0.4.3 probably from installing cyanogenmod, however formating any of those partitions does literally nothing. I'm not sure what file system it formats it to, but the process seemed too quick for a full format.
I cannot flash a different recovery because... well... it doesn't remember me flashing a recovery (even when nothing "fails" when flashing). So I'm stuck with whatever is already on my internal storage. Nothing is writing to the sdcard, and nothing is being deleted.
violoncellemuse said:
I have clockworkmod recovery v6.0.4.3 probably from installing cyanogenmod, however formating any of those partitions does literally nothing. I'm not sure what file system it formats it to, but the process seemed too quick for a full format.
I cannot flash a different recovery because... well... it doesn't remember me flashing a recovery (even when nothing "fails" when flashing). So I'm stuck with whatever is already on my internal storage. Nothing is writing to the sdcard, and nothing is being deleted.
Click to expand...
Click to collapse
Boot twrp temporary from the bootloader
USBhost said:
Boot twrp temporary from the bootloader
Click to expand...
Click to collapse
I'm unfamiliar with this, how do I boot temporarily?
violoncellemuse said:
I'm unfamiliar with this, how do I boot temporarily?
Click to expand...
Click to collapse
1 set getting on computer
Okay, so I was able to boot twrp and change the partitions to f2fs. No dice. Still cyanogenmod.
violoncellemuse said:
Okay, so I was able to boot twrp and change the partitions to f2fs. No dice. Still cyanogenmod.
Click to expand...
Click to collapse
then you did boot twrp temporary
USBhost said:
then you did boot twrp temporary
Click to expand...
Click to collapse
I did. I didn't know that was possible until now.
But still, changing the file system or formating anything doesn't do anything after I reboot. I even checked after I changed the file system to f2fs in twrp to see the "current file system" when changing the partitions again, but it says it's ext4 still.
I tried repairing system, which processed quickly. However, trying to repair cache and data led to an error. Perhaps this might mean something? or is this normal?
violoncellemuse said:
I did. I didn't know that was possible until now.
But still, changing the file system or formating anything doesn't do anything after I reboot. I even checked after I changed the file system to f2fs in twrp to see the "current file system" when changing the partitions again, but it says it's ext4 still.
I tried repairing system, which processed quickly. However, trying to repair cache and data led to an error. Perhaps this might mean something? or is this normal?
Click to expand...
Click to collapse
thats not normal
ok i know why its a new cyanogenmod feature
no matter what you do cyanogenmod is now unkillable lol
this is such a strage problem
USBhost said:
thats not normal
ok i know why its a new cyanogenmod feature
no matter what you do cyanogenmod is now unkillable lol
this is such a strage problem
Click to expand...
Click to collapse
Do you have any more info? Perhaps my sdcard is "softlocked" or something.
violoncellemuse said:
Do you have any more info? Perhaps my sdcard is "softlocked" or something.
Click to expand...
Click to collapse
i have been noticing CWMR is the root of all the problems
i dont sorry but your not the only one i think there are 3+ people that have this same problem
formating should have fixed it
USBhost said:
i have been noticing CWMR is the root of all the problems
i dont sorry but your not the only one i think there are 3+ people that have this same problem
formating should have fixed it
Click to expand...
Click to collapse
I do thank you for trying to help me out.
I found a thread with someone with the same problem I'd like to direct people towards: http://forum.xda-developers.com/showthread.php?t=2800064
violoncellemuse said:
Curious, how did you get to the point where it boots the previous rom? Same as me or something else? Are you using cyanogenmod? I want to try and rule out some possibilities.
I'm at the same point since last time. Trying to nuke the hell out of cyanogenmod but it won't go away!
This just outright baffles me!
Click to expand...
Click to collapse
Well, I have Paranaoid Android 4.4.4, not Cyanogen, and everything seemed ok until I installed Cloudmagic (and maybe Busybox?) that poped up a Play Store error (I don't remember which one), and suddenly all the problems began. It started to reboots, rebooted so many times that I decided to flash another ROM... but this wasn't possible.
My recovery is TWRP, so we can discard Cyanogen, ParanoidAndroid, CMW and TWRP as guilty, I think.
USBhost said:
Try this out format /system /cache /data with twrp to f2fs
If it doesn't boot then cheers you got out if the loop
Then adb sideload an f2fs ROM and kernel them flash
Click to expand...
Click to collapse
Tried that, nothing happened, still with Paranoid Android.
violoncellemuse said:
I did. I didn't know that was possible until now.
But still, changing the file system or formating anything doesn't do anything after I reboot. I even checked after I changed the file system to f2fs in twrp to see the "current file system" when changing the partitions again, but it says it's ext4 still.
I tried repairing system, which processed quickly. However, trying to repair cache and data led to an error. Perhaps this might mean something? or is this normal?
Click to expand...
Click to collapse
Same here.
Hey everyone, I have a really frustrating problem, I am currently able to boot into TWRP via hardware method and ADB can see my device as well. However I have tried to install a stock system image through TWRP and I have also tried to install another TWRP backup that a user had posted in the Q&A forum. At one time I was able to successfully boot into the system but my device said encryption unsuccessful. After wiping the system partition and trying to install these images through TWRP I am still unable to boot into the system. Whenever I install them my phone will reboot into TWRP. I am at a loss as to what to do. If anyone has any ideas or suggestions I would appreciate it.
crazyc78 said:
Hey everyone, I have a really frustrating problem, I am currently able to boot into TWRP via hardware method and ADB can see my device as well. However I have tried to install a stock system image through TWRP and I have also tried to install another TWRP backup that a user had posted in the Q&A forum. At one time I was able to successfully boot into the system but my device said encryption unsuccessful. After wiping the system partition and trying to install these images through TWRP I am still unable to boot into the system. Whenever I install them my phone will reboot into TWRP. I am at a loss as to what to do. If anyone has any ideas or suggestions I would appreciate it.
Click to expand...
Click to collapse
I saw your other post in the other thread, but couldn't reply for some reason.. did you wipe the internal storage before restore?
Yes I did wipe the internal storage, I actually wiped everything the first time I tried to get everything in order and that was my original problem by wiping the system. I didn't realize that wiping internal storage would cause issues but that could have been one of the culprits. I think what finally solved my issue is I installed a deodexed rom and then powered down my device instead of rebooting and it booted up the rom. I had to flash SuperSU from a zip because for some reason the one that was preinstalled with that rom didn't install properly. So I installed the SuperSU zip and I am now officially rooted. Lesson learned DON'T WIPE SYSTEM OR INTERNAL STORAGE lol. I should have known better I have been rooting for awhile now, I just wasn't paying attention it happens to the best of us sometimes. Thanks for your help.
crazyc78 said:
Yes I did wipe the internal storage, I actually wiped everything the first time I tried to get everything in order and that was my original problem by wiping the system. I didn't realize that wiping internal storage would cause issues but that could have been one of the culprits. I think what finally solved my issue is I installed a deodexed rom and then powered down my device instead of rebooting and it booted up the rom. I had to flash SuperSU from a zip because for some reason the one that was preinstalled with that rom didn't install properly. So I installed the SuperSU zip and I am now officially rooted. Lesson learned DON'T WIPE SYSTEM OR INTERNAL STORAGE lol. I should have known better I have been rooting for awhile now, I just wasn't paying attention it happens to the best of us sometimes. Thanks for your help.
Click to expand...
Click to collapse
I've been rooting for a while myself but messed up I'm stuck in twrp and don't know how to get it the phone back on! your help would be glady appreciated .
ricosuave88 said:
I've been rooting for a while myself but messed up I'm stuck in twrp and don't know how to get it the phone back on! your help would be glady appreciated .
Click to expand...
Click to collapse
I used the deodexed ROM that is in the development forum. If I can upload it here I will if not just download it put it on your SD card and flash it. It may take a couple tries though I would suggest powering down your phone instead of rebooting it. Then turn it on and it should boot into the new rom. It's basically the same stock rom that our phone comes with. You may have to flash Chainfires SUPERSU zip that's in one of the threads. These steps should get you up and running again. Also if you can see your internal storage you're not encrypted. Hopefully that works for you. Let me know how it goes.
I wasnt able to upload the file from my phone. Just download it from here.
http://forum.xda-developers.com/v20/development/h918-stock-deodex-debloat-t3499423/page5
crazyc78 said:
I wasnt able to upload the file from my phone. Just download it from here.
http://forum.xda-developers.com/v20/development/h918-stock-deodex-debloat-t3499423/page5
Click to expand...
Click to collapse
Thanks for responding back. Man I'm still stuck in twrp I'm losing all hope at this point been at all day and can't figure out what Im doing wrong . I know you was stuck in the same situation did flashing that twrp back up help you out?
ricosuave88 said:
Thanks for responding back. Man I'm still stuck in twrp I'm losing all hope at this point been at all day and can't figure out what Im doing wrong . I know you was stuck in the same situation did flashing that twrp back up help you out?
Click to expand...
Click to collapse
Flashing the rom helped me out. It's a system image file. It's basically the stock rom for our device just deodexed. What exactly happened what did you wipe after your phone booted into
TWRP? If you still have TWRP you're not bricked. If you can flash that image from the thread I copied above then you should be good. You may have to flash SUPERSU to get root back. Also after you flash make sure you're not encrypted if you can see your internal storage partition then you're not encrypted.
crazyc78 said:
Flashing the rom helped me out. It's a system image file. It's basically the stock rom for our device just deodexed. What exactly happened what did you wipe after your phone booted into
TWRP? If you still have TWRP you're not bricked. If you can flash that image from the thread I copied above then you should be good. You may have to flash SUPERSU to get root back. Also after you flash make sure you're not encrypted if you can see your internal storage partition then you're not encrypted.
Click to expand...
Click to collapse
when I flashed the rom from your link above it just booted me into twrp again . I don't know what exactly I'm suppose to wipe. I can see internal storage tho so I guess that's a good sign but what's not good is that I can't use my phone :/ I've been rooting for years and can't seem to figure this one out.
ricosuave88 said:
when I flashed the rom from your link above it just booted me into twrp again . I don't know what exactly I'm suppose to wipe. I can see internal storage tho so I guess that's a good sign but what's not good is that I can't use my phone :/ I've been rooting for years and can't seem to figure this one out.
Click to expand...
Click to collapse
When you flashed the rom did you power the phone down and then try to boot into the rom? That's what I did and it worked for me. So don't select reboot into system, I'm not sure why it doesn't work that way. I had to power my device down and then boot into the room. Also if you can see your internal partition in TWRP then you should be good and encryption is not enabled. I know how frustrating this is. Just keep trying eventually that rom should stick.
crazyc78 said:
When you flashed the rom did you power the phone down and then try to boot into the rom? That's what I did and it worked for me. So don't select reboot into system, I'm not sure why it doesn't work that way. I had to power my device down and then boot into the room. Also if you can see your internal partition in TWRP then you should be good and encryption is not enabled. I know how frustrating this is. Just keep trying eventually that rom should stick.
Click to expand...
Click to collapse
Man, I have tried everything as well and I can't seem to get pass TWRP. Has anyone found a way around this problem? I have been looking around for an answer for 2 days and nothing has worked so far, any help will be greatly appriciated.
Thank you
kaiser10 said:
Man, I have tried everything as well and I can't seem to get pass TWRP. Has anyone found a way around this problem? I have been looking around for an answer for 2 days and nothing has worked so far, any help will be greatly appriciated.
Thank you
Click to expand...
Click to collapse
There a stock rom that I posted a link to a few posts back when I trying to help someone else. Download it put it on your SD card and install it. You don't need to wipe anything it will format things for you. After it installs don't reboot, power down the device and then turn it back on it should boot into the rom. That's what worked for me. I believe there was another way then what I just described it's in the same thread that I linked a few posts back. Good luck!!
crazyc78 said:
There a stock rom that I posted a link to a few posts back when I trying to help someone else. Download it put it on your SD card and install it. You don't need to wipe anything it will format things for you. After it installs don't reboot, power down the device and then turn it back on it should boot into the rom. That's what worked for me. I believe there was another way then what I just described it's in the same thread that I linked a few posts back. Good luck!!
Click to expand...
Click to collapse
Thanks for the help brother. However, it did not work for me. I flash the stock system, boot, turn device off and turn back on but I am still stock on TWRP. I will continue reading and hopefully I will find the answer soon.
thank you,:crying:
kaiser10 said:
Thanks for the help brother. However, it did not work for me. I flash the stock system, boot, turn device off and turn back on but I am still stock on TWRP. I will continue reading and hopefully I will find the answer soon.
thank you,:crying:
Click to expand...
Click to collapse
Np don't give up, I almost lost hope and then it worked for me.
Like I said there was another method that was discussed that worked for someone else. Try this thread, I know someone had the same issue that you and I had and they finally got it working.
http://forum.xda-developers.com/v20/development/h918-stock-deodex-debloat-t3499423
I'm here to the rescue! Follow this to the T! It worked for me! Let me know. http://forum.xda-developers.com/showthread.php?p=69685809
Sent by using the battery of my LG V20
im on the same boat as you. I am stuck in TWRP
tried all the methods i found so far and still stuck in twrp. i would greatly appreciate if someone can get me out of this bootloop!
hslayer said:
tried all the methods i found so far and still stuck in twrp. i would greatly appreciate if someone can get me out of this bootloop!
Click to expand...
Click to collapse
Same. Though I am on US996. Not sure what I did, was exploring some behind the scenes stuff using 'hidden codes' but didn't change any values as I didn't know what they meant in most cases. I rebooted my phone and it went straight to TWRP (3.0.2-1) and it will not boot past TWRP. Occasionally after I've flashed something, it will boot into TWRP and the screen will be unresponsive to touch so I have to pull the battery, but then it will be fine again.
I was in your position not to long ago, I'm currently working on getting a .kdz recovery file for the H918. My progress will continue on it later when finals are over.
netgar post 134
Restore H918 to 100% Stock (!!REQUIRES TWRP!!)
!!! I apologize if this is the wrong thread to ask for help and kindly request that a moderator move it, because I don't know where it's supposed to go and my brain is in panic mode right now, thank you. !!!
So, here goes:
DEVICE INFO: SM-J510FN, TWRP, stock ROM, encrypted data partition
ISSUE: Phone does not boot. Powering it on makes it boot to recovery. Selecting "Reboot to system" from inside the recovery, also boots back to recovery. Cannot mount data partition as it is encrypted (but it doesn't at least ask for PIN or anything, just cannot select /data in mount).
HOW IT HAPPENED:
1. I encrypted the phone while it still wasn't rooted.
2. I flashed TWRP (via Odin) and SuperSU (via TWRP)
3. Phone booted to system normally, everything OK. Root access, all good.
4. Reboot to TWRP, flashed some blacked out Google Apps (Team Blackout .zip files). I got no error message, just "cannot mount data" at some points.
5. I selected "wipe cache and dalvik cache"
6. Reboot to system
Reboot to system doesn't work. It boots back into TWRP!
Now I don't know if the flashing of the .zip apps or if the wiping bricked the phone as I don't have that deep of an understanding of how it works. If you can enlighten me , I'd really appreciate it.
FEAR: That the phone is bricked forever and that I won't be able to format the data partition as I cannot even mount it and TWRP needs it mounted in order to wipe it (as far as I know). In short, phone ruined forever because of my stupidity.
HOPE: That someone will tell me a way to re-flash the stock firmware or any ROM so that I get the phone to boot up normally.
I really really need help ASAP because this phone does not even belong to me. My employer gave it to me as a gift, provided I use it for work. That's the reason it's encrypted, he wanted it encrypted in case it gets stolen. Now you're probably thinking "why would you root a company phone??" Well it's not a company phone, it is my main phone, my daily driver. It was given to me by my employer, who said I can do whatever I want with it, as long as it remains functional (at work I use it simply for phone calls, WhatsApp, Skype, mail etc)
I assume that I won't sleep much tonight, will try everything to get the phone to boot. But first I'm going to wait for any piece of advice!
Thank you in advance for any feedback...
Can you get into download mode?
If so, you should flash your stock firmware.
Yes if you boot into download mode you can flash stock rom and all will be good
capsLock1337 said:
Can you get into download mode?
If so, you should flash your stock firmware.
Click to expand...
Click to collapse
pando504 said:
Yes if you boot into download mode you can flash stock rom and all will be good
Click to expand...
Click to collapse
Hello, thanks for the replies.
Yes, download mode works. I will download the stock firmware and flash it via Odin then, yes?
But what happens with the encryption then? Will it remain in place and I will just have to enter my pin to boot as usual?
Can you please explain to me why it does not boot now..? As far as I understand, the boot partition couldn't have been damaged. Aka, stock ROM still in place, only difference is it's rooted.
bi11ie said:
Hello, thanks for the replies.
Yes, download mode works. I will download the stock firmware and flash it via Odin then, yes?
But what happens with the encryption then? Will it remain in place and I will just have to enter my pin to boot as usual?
Can you please explain to me why it does not boot now..? As far as I understand, the boot partition couldn't have been damaged. Aka, stock ROM still in place, only difference is it's rooted.
Click to expand...
Click to collapse
Not sure bout the encryption, if you lose it, you can set it up again.
Something went wrong when you tried to flash the blacked out google apps, I honestly don't have a clue.
Good luck
capsLock1337 said:
Not sure bout the encryption, if you lose it, you can set it up again.
Something went wrong when you tried to flash the blacked out google apps, I honestly don't have a clue.
Good luck
Click to expand...
Click to collapse
Haha I really don't care about the encryption at all! I'm just afraid it is going to interfere somehow but hopefully not.
I'm waiting for the stock firmware to get downloaded from sammobile. I know, I know, I should have done that first before anything else, but I was in such a hurry and I thought "OK, this is routine by now, nothing can go wrong", somehow completely forgetting about the encryption. Oops. In any case, I will post the results here later and will be VERY VERY prepared and organized in the future :'(
bi11ie said:
Haha I really don't care about the encryption at all! I'm just afraid it is going to interfere somehow but hopefully not.
I'm waiting for the stock firmware to get downloaded from sammobile. I know, I know, I should have done that first before anything else, but I was in such a hurry and I thought "OK, this is routine by now, nothing can go wrong", somehow completely forgetting about the encryption. Oops. In any case, I will post the results here later and will be VERY VERY prepared and organized in the future :'(
Click to expand...
Click to collapse
How did it go?
capsLock1337 said:
How did it go?
Click to expand...
Click to collapse
I'm flashing right now Let's see if it boots...
*fingers crossed*
Case solved
bi11ie said:
I'm flashing right now Let's see if it boots...
*fingers crossed*
Click to expand...
Click to collapse
Ahh turns out I almost freaked out for nothing! All good! So, for documentation purposes:
1. I flashed stock firmware through Odin
2. Boot up started normally ("firmware update") - got asked for encryption pin!
3. Decryption took a long time, system booted normally - ALL DATA INTACT
4. No root and No recovery (not even stock recovery)
5. I flashed TWRP through Odin and SuperSU.zip
6. Phone booted normally, TWRP there, SuperSU app there.
The only change is that the bloatware I removed is back
I'm so glad it was nothing after all! I was honestly SO scared that I bricked it ^^;
Thanks and sorry!
bi11ie said:
Ahh turns out I almost freaked out for nothing! All good! So, for documentation purposes:
1. I flashed stock firmware through Odin
2. Boot up started normally ("firmware update") - got asked for encryption pin!
3. Decryption took a long time, system booted normally - ALL DATA INTACT
4. No root and No recovery (not even stock recovery)
5. I flashed TWRP through Odin and SuperSU.zip
6. Phone booted normally, TWRP there, SuperSU app there.
The only change is that the bloatware I removed is back
I'm so glad it was nothing after all! I was honestly SO scared that I bricked it ^^;
Thanks and sorry!
Click to expand...
Click to collapse
No need to apoligize, we all do stupid mistakes sometimes
Glad that it worked!