Tried to encrypt, now stuck on boot screen! - Galaxy Tab S Q&A, Help & Troubleshooting

Ok, so... This is a Galaxy S, 10.5". The T800. I'm running Resurrection OS: the Luis build or whatever. The one with the dog. I attempted to encrypt this thing with the built-in tool. From Settings. I tried and probably failed. I checked on my tablet a few hours later and found it stuck on the boot screen: spinny colors, all that. It never reached the end.
I rebooted into TWRP, and that worked fine. I checked to see if I could access the file manager, and I could. I could peer into various directories on the Data partition and see the files there. So I figure that's a good sign. I figured, I'll wipe the cache and the dalvik cache. That's good for what ails ya. No help. I found some recommendation about using TWRP to repair the data partition, so I tried that. No difference. I tried to boot into Safe Mood, but the key code didn't seem to make any difference either. No good.
So, any suggestions? There wasn't anything essential on there that couldn't reasonably be gotten back. I know I could just wipe... everything and start anew, but it would be a pain in the neck, pardon my French. I'd have to download and reinstall everything. If there's a quick way to get this thing back to normal without that hassle, I'd appreciate it.

If it failed,i fear your app data,information,etc might not work normal y any more?Just get to twrp,plug your usb and get your file,etc back.

Would it help if I provided a logcat?
https://filebin.net/zx61szgrgur7l7n3
Even if I have to just wipe and start over, I want to know what the heck was going on!

FailSafeNow said:
Would it help if I provided a logcat?
https://filebin.net/zx61szgrgur7l7n3
Even if I have to just wipe and start over, I want to know what the heck was going on!
Click to expand...
Click to collapse
Sorry i'm not a developer,just ask the rom builder himself https://forum.xda-developers.com/ga...om-resurrection-remix-n-sm-t800-wifi-t3606243 if i correct?

Related

Seem to have soft bricked my SGH-i747

I'd like to start by apologizing for what is probably the 9,000th "help, I've bricked my phone!" thread. I did some searching, and while I found many, I wasn't able to find one that both dealt with my specific issue, and did so assuming a level of newbishness appropriate for me.
Months ago, I rooted my AT&T Galaxy SIII, and installed CM10. It's been all candy and rainbows since. This morning, I somewhat foolishly decided to update from a nightly I installed in October/November, to the January 7 CM 10.1 nightly, using the built-in updater I had previously used to switch to a nightly.
It worked...sort of. I guess I should have cleared my cache or something ahead of time, because almost all of my GAPPS stopped working. Woops! Figuring that I should probably stop dicking around with my phone until I learned a bit more, I just went back and told the phone to switch back to the nightly I from October/November that I was previously using.
It didn't work. My phone now reaches the CM boot animation and just...sits there. And sits there. And sits there. To complicate the issue, I cannot get the phone to boot into recovery mode (although admittedly, I'm too thick to know what I'm meant to do once I'm there anyway). I CAN get the phone into download mode, but not being sure what I should do there, I thought it best to consult you all on what to do next.
I'm happy to give any additional information needed, and I hope it goes without saying that I am extremely thankful for any help you all can offer.
Try to get it back into recovery by taking the battery out, putting it back in and then holding volume up, home, and power. If you are sure you can't get it into Recovery, but know for sure you can get it into Download, go into Download and flash stock and go from there. These aren't bricks. These are just whoops. Lol.
If you can reach download mode, you'll be okay. What you want to do is use Odin to flash a rooted stock image; from there, you should be able to get back to a point where you can re-install a custom recovery of your choice and try flashing your favourite ROM again.
For the record, it's always a good idea to clear data/cache when changing ROMs, or changing between major revisions of a ROM (such as CM10 -> CM10.1) to avoid this sort of problem.
Actually, you should always wipe cache and dalvik when flashing the update. If it is a major update like 4.1.2 to 4.2.1, then you should wipe cache, wipe dalvik, Factory Reset, Format System then flash your ROM.
Move important files to SD using twrp file manager. Put rom on SD with gapps. Format internal, wipe caches, format system, factory reset, load ROM, load gapps. Reboot.
Sent from a Horny Pink Pony
smelenchuk said:
If you can reach download mode, you'll be okay. What you want to do is use Odin to flash a rooted stock image; from there, you should be able to get back to a point where you can re-install a custom recovery of your choice and try flashing your favourite ROM again.
For the record, it's always a good idea to clear data/cache when changing ROMs, or changing between major revisions of a ROM (such as CM10 -> CM10.1) to avoid this sort of problem.
Click to expand...
Click to collapse
I did this, being careful to follow all the instructions provided. Odin seemed to think everything worked, and after about 10 minutes, it rebooted the phone.
However, it still gets stuck. Now, since CM is no longer installed, it just sits at the SAMSUNG logo forever.
It still boots into download mode, and will now boot into recovery as well. Any suggestions?
naporeon said:
It still boots into download mode, and will now boot into recovery as well. Any suggestions?
Click to expand...
Click to collapse
Boot to recovery and clear data and cache.
smelenchuk said:
Boot to recovery and clear data and cache.
Click to expand...
Click to collapse
Worked like a charm, thanks! Can't believe after all that trouble, I didn't think to do that myself. >.<

[Q] Boot Loop

I just entered the world of a rooted phone, all exciting and new. I used triangle away, and everything is well. I even turned off the debugging mode as i thought i was all done with things rooting and didn't need it.
The next day I realize there is update for supersu, so i accept, if gives me two choices in the update, i choose one, and now my phone is the in GTN7100 loop non stop. Seems of the two options, I choose wrongly. I can put it into download mode. I think I can put it into recovery mode too.
I used this method to boot.
galaxy-note2.wonderhowto.com/how-to/root-your-samsung-galaxy-note-2-using-odin-for-windows-so-easy-your-grandma-can-do-it-0146884
I did perform some basic backups with kies and i believe an app called my backup, so in the worst case, I believe i can recover everything if had to do some kind of reset that would erase all the data. (I am hoping to avoid that, as the recovery may be a learning process if any challenges with it)
its with 4.1.2 and I am not sure if any other details I should provide. so i feel proud i got this far, sad the supersu update made some kind of corruption. i know you guys may be extremely busy and i thank you so much in advance.
Try getting into recovery (CMW or Philz touch) and re-flash a ROM?
thank you bunglebp
bunglebp said:
Try getting into recovery (CMW or Philz touch) and re-flash a ROM?
Click to expand...
Click to collapse
Thank you so much for your reply bunglebp.
I believe I had the CMW when i rooted. Reflashing the ROM won't lose the data, or will? This is new territory for me, so I am going step be step.
Volume up - home - power, i think i understand this far. I just don't want to make any mistakes and follow to a T to bring the phone back up with least work at it if possible.
Macguyer2000 said:
Thank you so much for your reply bunglebp.
I believe I had the CMW when i rooted. Reflashing the ROM won't lose the data, or will? This is new territory for me, so I am going step be step.
Volume up - home - power, i think i understand this far. I just don't want to make any mistakes and follow to a T to bring the phone back up with least work at it if possible.
Click to expand...
Click to collapse
Yes your description of how to get into recovery is correct. But your description of your situation is light on details, hard to get a clear picture, but I feel your pain!
If you have a ROM sitting on your phone that you can reflash in recovery, do it. You won't lose any media on your internal memory e.g. pictured, movies. All your app settings will remain if you don't wipe anything in recovery prior to flashing - but in your situation I suggest a full wipe & reset to (hopefully) clear out any problems.
As for upgrading SU, I'm wondering what you mean by two options? Let us know how you get on. Also feel free to PM me if you're truly stuck, I've been there myself and received help that saved me untold stress.
tweeny80 said:
Yes your description of how to get into recovery is correct. But your description of your situation is light on details, hard to get a clear picture, but I feel your pain!
If you have a ROM sitting on your phone that you can reflash in recovery, do it. You won't lose any media on your internal memory e.g. pictured, movies. All your app settings will remain if you don't wipe anything in recovery prior to flashing - but in your situation I suggest a full wipe & reset to (hopefully) clear out any problems.
As for upgrading SU, I'm wondering what you mean by two options? Let us know how you get on. Also feel free to PM me if you're truly stuck, I've been there myself and received help that saved me untold stress.
Click to expand...
Click to collapse
When I was welcomed to update supersu, it had a left choice (normal) and a right side choice cwm/twrp (not sure the spelling) I choose the right.
I really want to first thank you so so much.
Which options within the recovery should i choose?
When I did try to repeat the original root process, I got a PIT message that just stayed and did not change. I was on slow machine, but I think it was because the debug usb was off or as i was starting to hear, the partition might be changed in the rooting process? Not sure how that would relate. likely because the debug was off
The pain and fear that broke the phone is really intense. Plus, I use it all the time, before this happened. what information do you need?
Macguyer2000 said:
When I was welcomed to update supersu, it had a left choice (normal) and a right side choice cwm/twrp (not sure the spelling) I choose the right.
I really want to first thank you so so much.
Which options within the recovery should i choose?
When I did try to repeat the original root process, I got a PIT message that just stayed and did not change. I was on slow machine, but I think it was because the debug usb was off or as i was starting to hear, the partition might be changed in the rooting process? Not sure how that would relate. likely because the debug was off
The pain and fear that broke the phone is really intense. Plus, I use it all the time, before this happened. what information do you need?
Click to expand...
Click to collapse
My assumptions are you were successfully rooted, I'm unsure if you are on stock ROM or custom ROM, you updated SU and ended up in bootloop. You are able to get into recovery - do you have a ROM already sitting on your phone, that you can flash/install? If yes, do that. But first, in recovery look for options named factory reset, do that. You suggested you have CWM recovery - there is option to wipe cache, then under advanced option, is wipe dalvik cache, do those. I hope I adequately described the menu structure, my phone is not with me right now to check.
Really, we just want to get you back into a functioning ROM, and stop the bootloops. As for updating SU, I assume you tried updating from recovery? If so, stick to the Play Store updates only.
Again lemme know how you get on, and confirm my assumptions so I can help further if needed.
tweeny80 said:
My assumptions are you were successfully rooted, I'm unsure if you are on stock ROM or custom ROM, you updated SU and ended up in bootloop. You are able to get into recovery - do you have a ROM already sitting on your phone, that you can flash/install? If yes, do that. But first, in recovery look for options named factory reset, do that. You suggested you have CWM recovery - there is option to wipe cache, then under advanced option, is wipe dalvik cache, do those. I hope I adequately described the menu structure, my phone is not with me right now to check.
Really, we just want to get you back into a functioning ROM, and stop the bootloops. As for updating SU, I assume you tried updating from recovery? If so, stick to the Play Store updates only.
Again lemme know how you get on, and confirm my assumptions so I can help further if needed.
Click to expand...
Click to collapse
[If you don't already have it, download and install the Samsung USB Drivers. Now, download and unzip the GalaxyNote2Root.zip file. Open the ODIN program by double-clicking the odin3 v1.85.exe application file.] from the website i followed. with this catchy title:
How to Root Your Samsung Galaxy Note 2 Using ODIN for Windows (So Easy Your Grandma Can Do It)
and it rooted with no problem...just that boot loop the next day when updating supersu...and using the google only site is a good idea.
I am having trouble to get the recovery mode on. I can go into download mode easily, but to go into recovery appears to be a trickier issue. I just can't get it. Can you guide me on this....
Simply reflash rom and reroot again.
Flashing stock rom won't erase data. So if after flashing rom device boot up normally, tour data will be there intact, incase it doesn't boot normally after flashing rom then you may need to wipe it.
Sent from my GT-N7100 using xda premium
Macguyer2000 said:
I just entered the world of a rooted phone, all exciting and new. I used triangle away, and everything is well. I even turned off the debugging mode as i thought i was all done with things rooting and didn't need it.
The next day I realize there is update for supersu, so i accept, if gives me two choices in the update, i choose one, and now my phone is the in GTN7100 loop non stop. Seems of the two options, I choose wrongly. I can put it into download mode. I think I can put it into recovery mode too.
I used this method to boot.
galaxy-note2.wonderhowto.com/how-to/root-your-samsung-galaxy-note-2-using-odin-for-windows-so-easy-your-grandma-can-do-it-0146884
I did perform some basic backups with kies and i believe an app called my backup, so in the worst case, I believe i can recover everything if had to do some kind of reset that would erase all the data. (I am hoping to avoid that, as the recovery may be a learning process if any challenges with it)
its with 4.1.2 and I am not sure if any other details I should provide. so i feel proud i got this far, sad the supersu update made some kind of corruption. i know you guys may be extremely busy and i thank you so much in advance.
Click to expand...
Click to collapse
Just to let you know I have used both sources of available update for super su.
And have never had any problems, I highly doubt your boot loop is anything todo with the su update. The guus on here at xda are superb and will have you back up and running no problem.
GT N7105 with XDA Premium......that is all......
bearusa said:
Just to let you know I have used both sources of available update for super su.
And have never had any problems, I highly doubt your boot loop is anything todo with the su update. The guus on here at xda are superb and will have you back up and running no problem.
GT N7105 with XDA Premium......that is all......
Click to expand...
Click to collapse
thank you for the positive thinking. but I think I have a serious problem here.
I can not get into recovery, as much as i try.
Before all this happened, i unticked usb debug.
I can however get into download mode.
I really feel that i have critically wounded my phone.
Macguyer2000 said:
thank you for the positive thinking. but I think I have a serious problem here.
I can not get into recovery, as much as i try.
Before all this happened, i unticked usb debug.
I can however get into download mode.
I really feel that i have critically wounded my phone.
Click to expand...
Click to collapse
Enter download mode and reflash the recovery using odin. Unticking debug should not put your phone into bootloop neither. . You have to make sure your flashing the correct recovery or rom for your phone model. Depending if you have n7100 or n7105..
GT N7105 with XDA Premium......that is all......
bearusa said:
Enter download mode and reflash the recovery using odin. Unticking debug should not put your phone into bootloop neither. . You have to make sure your flashing the correct recovery or rom for your phone model. Depending if you have n7100 or n7105..
GT N7105 with XDA Premium......that is all......
Click to expand...
Click to collapse
OK, let me make sure I understand correctly..I can put some of my fears/worries to rest.
Let me restate
My situation is a bootloop.
My usb debugging is off. (the day after the rooting, I didn't think I needed it on anymore, as I completed the root)
Later that day, just moment before the loop happened, I was updating SuperSu. (something the phone didn't like)
I found: I can go into download mode. I can not go into recovery mode.
(a phone with a bootloop, usb debugging is off, and download mode is accessible)
So:
(When rooting, I opened Odin, I selected the PDA option, choose the proper file, and pressed start. Yellow changed to Green and we were done)
So Now, I open Odin, select the PDA option, choose the correct file for my phone (GT N7100) from likely the samsung website, I see the Yellow, hit start, yellow turns to green, and we're ok?
That simple thing I said 24 hr ago, still you are here.
It has nothing to do with usb debugging.
If you keep it enable /disable, it won't make any difference in flashing.
Sent from my GT-N7100 using xda premium
Phone is OK now!
dr.ketan said:
That simple thing I said 24 hr ago, still you are here.
It has nothing to do with usb debugging.
If you keep it enable /disable, it won't make any difference in flashing.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
I want to say thank you to everyone. I flashed recovery and it told of bad install. I rebooted and everything is FINE!
Thank you so much!

[Q] Rooted 4.3 OTA soft-bricked, wouldn't load any apps

So basically I did this:
http://forum.xda-developers.com/showthread.php?t=2538991
But unfortunately, I hadn't realized that the mobile hotspot was sealed up in that update. So I looked it up, and saw that someone had recommended this:
http://forum.xda-developers.com/showthread.php?p=48326067
So I went into TWRP and installed it. But that didn't work. When I booted back up EVERY app was crashing immediately except the stock Samsung apps (Messaging, Email, etc.). I tried to reverse it with the original framework-res.apk but when I did, the phone would get stuck at the AT&T logo (which was silent). I went back and forth a few times (when I applied that tethering mod, the phone would boot; when I tried to reverse it, it wouldn't), then did a factory reset in TWRP. After that, the phone booted, but the Setup Wizard would crash. So I did a Nandroid restore in TWRP and now the phone hangs at the AT&T logo no matter what I do.
My question is, what can I do now? I have a replacement device coming through warranty just in case, but it would be much better to just fix this one. However, I want to be certain and not HARD brick the phone...
I have never been able to restore a stock 4.3 nandroid without everything crashing. I have always had to go back into recovery and wipe data/factory reset and wipe cache and dalvik cache then reboot and go through the whole setup process again. If that doesn't work you could try installing the stock debloat ROM from this thread. That's what I am running and it works great. http://forum.xda-developers.com/showthread.php?t=2540998
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Iantuition said:
So basically I did this:
http://forum.xda-developers.com/showthread.php?t=2538991
But unfortunately, I hadn't realized that the mobile hotspot was sealed up in that update. So I looked it up, and saw that someone had recommended this:
http://forum.xda-developers.com/showthread.php?p=48326067
So I went into TWRP and installed it. But that didn't work. When I booted back up EVERY app was crashing immediately except the stock Samsung apps (Messaging, Email, etc.). I tried to reverse it with the original framework-res.apk but when I did, the phone would get stuck at the AT&T logo (which was silent). I went back and forth a few times (when I applied that tethering mod, the phone would boot; when I tried to reverse it, it wouldn't), then did a factory reset in TWRP. After that, the phone booted, but the Setup Wizard would crash. So I did a Nandroid restore in TWRP and now the phone hangs at the AT&T logo no matter what I do.
My question is, what can I do now? I have a replacement device coming through warranty just in case, but it would be much better to just fix this one. However, I want to be certain and not HARD brick the phone...
Click to expand...
Click to collapse
if you can get back to twrp , clear everything then flash the official correct file that yu want then see if that works...restore your apps/data after a clean refresh for your phone
remember panicking and being paranoid with flashing/rooting is not a a good idea, always rethink what you did wrong, let the phone cool down, research know what you re doing then fix it
dont rush, cuz rushing leads to bricks (learned from experience from day 1 with root)
bellifritz said:
I have never been able to restore a stock 4.3 nandroid without everything crashing. I have always had to go back into recovery and wipe data/factory reset and wipe cache and dalvik cache then reboot and go through the whole setup process again. If that doesn't work you could try installing the stock debloat ROM from this thread. That's what I am running and it works great. http://forum.xda-developers.com/showthread.php?t=2540998
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
How'd you do that? Just the regular factory reset? Cause the setup wizard wouldn't even run after that.
winosxbuntu said:
if you can get back to twrp , clear everything then flash the official correct file that yu want then see if that works...restore your apps/data after a clean refresh for your phone
remember panicking and being paranoid with flashing/rooting is not a a good idea, always rethink what you did wrong, let the phone cool down, research know what you re doing then fix it
dont rush, cuz rushing leads to bricks (learned from experience from day 1 with root)
Click to expand...
Click to collapse
Okay. Which official file though? and should I clear the system and boot partitions too?
Iantuition said:
How'd you do that? Just the regular factory reset? Cause the setup wizard wouldn't even run after that.
Okay. Which official file though? and should I clear the system and boot partitions too?
Click to expand...
Click to collapse
try this two links, everything on flashing 4.3 stock/rooting and fix http://forum.xda-developers.com/showthread.php?t=2540998
http://forum.xda-developers.com/showpost.php?p=46804338
either one will work
AND dont clear everything just cache/dalvik/format system/ factory reset BUT follow the instructions given for that rom to avoid any problems
winosxbuntu said:
try this two links, everything on flashing 4.3 stock/rooting and fix http://forum.xda-developers.com/showthread.php?t=2540998
http://forum.xda-developers.com/showpost.php?p=46804338
either one will work
AND dont clear everything just cache/dalvik/format system/ factory reset BUT follow the instructions given for that rom to avoid any problems
Click to expand...
Click to collapse
Okay so I just leave boot alone. Let us pray, LOL. And sorry if I've sounded like a supernoob but I'm trying to be REALLY careful.
Iantuition said:
How'd you do that? Just the regular factory reset? Cause the setup wizard wouldn't even run after that.
Hit the power button to make the screen go to sleep. Hit the power button again to wake it up. Nothing should be crashing while you are on the lock screen so just hold the power button until the power menu appears and select power off. Once it powers off hold the volume up, home button and power button until you see the blue words in the upper left corner of the screen I believe it says loading recovery. Release the power button but continue holding the other 2 buttons until recovery loads. Now wipe data, cache and under advanced wipe dalvik cache. Reboot and everything should quit crashing but you will have to setup your account and apps again. That is the only way that I can get stock touchwiz 4.3 nandroids to work.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Iantuition said:
Okay so I just leave boot alone. Let us pray, LOL. And sorry if I've sounded like a supernoob but I'm trying to be REALLY careful.
Click to expand...
Click to collapse
it will work, i agree with what bell said. unless its hard bricked then no worries just keep calm and fix the damn phone

I screwed up xD

So, this is my first Samsung device, longtime HTC user. I was cocky and thought I could go ahead and delete system apps that I thought were safe to delete. Apparently, I was sorely mistaken.
I am now caught in a bootloop. Luckily for me, I can get into the system and do a few things before it reboots. I was unable to fing factory images for the s6 edge, so, I have another idea, but I need someone's help.
I was thinking if someone could make a backup using titanium backup of all their system apps and share it with me, I would attempt to run the restore option in TiBu to remedy the issue. If anyone could do this, or has a better idea, let me know. Thanks in advance, and I apologize for needing something so trivial (smh).
if you can get into the settings menu and do a factory reset, that would fix it..
also, try calling t mobile, and ask tech support how you can boot into recovery, and there should also be a factory reset choice in there..
wase4711 said:
if you can get into the settings menu and do a factory reset, that would fix it..
also, try calling t mobile, and ask tech support how you can boot into recovery, and there should also be a factory reset choice in there..
Click to expand...
Click to collapse
I've done that, the phone simply reboots itself. When I try to boot into recovery, I don't get that distorted green/white screen everyone else does, it flashes real quick then goes dark, nothing more. I've tried the vol- 4 times, power, vol- 7 times power, wait, power combo as well, it does not factory reset my device.
I would still call t mobile and ask them how to actually boot into recovery.
There has to be a way to do it; I would turn the phone off completely, then boot into recovery using the method t mobile suggests..
EDIT: read this http://www.androidexplained.com/galaxy-s6-recovery-mode/
wase4711 said:
I would still call t mobile and ask them how to actually boot into recovery.
There has to be a way to do it; I would turn the phone off completely, then boot into recovery using the method t mobile suggests..
EDIT: read this http://www.androidexplained.com/galaxy-s6-recovery-mode/
Click to expand...
Click to collapse
I really appreciate your help in trying to get me into recovery, but I have tried everything. I've done the release after the buttons stop blinking, don't release until you see blue text (which I never do, there is never blue text at the top of my screen). I also work for T-Mobile, I have access to the files customer care would read you if you called in. I am at work right now lol.
Honestly, all I need is a zipped titanium backup of system apps (just the app, no data) that I can get onto the phone and try and restore.
I don't mean to sound rude, but this isn't my first rodeo. I've been attempting to get a logcat to identify which error is causing the device to crash so I can ask for just that one app (I can't get the log though, always hangs on waiting for device, even though I can execute other adb commands). All I need is that TiBu copy.
Edit: Wow, I finally got it to factory reset. I'm not sure why it didn't work before. I tried the same thing countless times with no success, but I finally got it.
Again, I apologize if I sounded rude earlier. I really didn't mean to be.
not rude at all bro, as you know, there are so many different levels of "knowledge" here, that I try to use the lowest common denominator when helping folks out, but you obviously know what you are doing!
Glad to hear you got to factory reset menu; that should fix you right back up!:good:
I was in the same boat as you. Rooted, removed system apps, got back to Recovery Screen, but a Factory Restore did not bring back the apps that were removed. Tried Kies, but it would not work last night. As of this afternoon, Kies will now work. Just did it a few minutes ago.
Use the "Firmware Upgrade and Initialization" option. You'll need the Model Name and Serial Number, both of which can be found on the Box, or in the Settings menu if you can get there.

I am unable to make any ROM, TWRP stick.

I have FB factory, flashed ROM's and nothing is sticking. Might be corrupt storage. I was wondering if there is a more thorough way to wipe/flash the phone so I can make a ROM/OS stick?
Have you tried a factory image with the -w as in wipe everything?
Sent from my Pixel XL using Tapatalk
Soooperstar said:
Have you tried a factory image with the -w as in wipe everything?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Yes, I have done all of the typical things and I am having very, very bad luck. Out of the box, thinking is critical.
Fixed!
Scottay5150 said:
I have FB factory, flashed ROM's and nothing is sticking. Might be corrupt storage. I was wondering if there is a more thorough way to wipe/flash the phone so I can make a ROM/OS stick?
Click to expand...
Click to collapse
Fastboot format system, fastboot erase userdata, fastboot format cache. There was a guide somewhere someone had about clean flashing. I had an issue once but after totally wiping and a clean install of stock, I haven't had any issues since. Use the flash-all.exe to flash, idk if you flash your images separately, but flashing the zip as a whole through fastboot yielded better results for me. Also being sure that my adb.exe files were up to par. Also be sure to wipe both slots, as it might be slot b giving you problems. Google search should find you the right fastboot commands, I've forgot them off the top of my head. Of course if you're going to wipe you would need to back everything you need up.
Bryanx86 said:
Fastboot format system, fastboot erase userdata, fastboot format cache. There was a guide somewhere someone had about clean flashing. I had an issue once but after totally wiping and a clean install of stock, I haven't had any issues since. Use the flash-all.exe to flash, idk if you flash your images separately, but flashing the zip as a whole through fastboot yielded better results for me. Also being sure that my adb.exe files were up to par. Also be sure to wipe both slots, as it might be slot b giving you problems. Google search should find you the right fastboot commands, I've forgot them off the top of my head. Of course if you're going to wipe you would need to back everything you need up.
Click to expand...
Click to collapse
Yes, my SDK is up to date, from Google site. Interesting about flash-all.exe.
Fastboot format system
fastboot erase userdata
fastboot format cache
These were the commands you have used?
Anyone have beta how to wipe both a and b??
Does anyone want to link me to clean flashing?
Scottay5150 said:
Yes, my SDK is up to date, from Google site. Interesting about flash-all.exe.
Fastboot format system
fastboot erase userdata
fastboot format cache
These were the commands you have used?
Anyone have beta how to wipe both a and b??
Does anyone want to link me to clean flashing?
Click to expand...
Click to collapse
You need to go back to square one.. Asking questions like this lead me to believe you have absolutely no idea what you are doing and you need to leave things alone before further damaging your device...
stebomurkn420 said:
You need to go back to square one.. Asking questions like this lead me to believe you have absolutely no idea what you are doing and you need to leave things alone before further damaging your device...
Click to expand...
Click to collapse
OK folks. I want to apologize for my flooding of the forums attempting to repair my situation last week. Yes, I have been flashing for a long time without real complications. I haven't been on my ADHD meds for a while and that did not help me with the drama last week. Unfortunately my world like most of you is in my phone, I was panicked. Sorry about that.
Needless to say I needed other eyes on what I was doing for perspective sake. I went to my PC tech, luckily had personal flashing experiences with Android, Pixel even. We worked on it for about 6 hours in total. He couldn't get RR to work.
The issue was this after following the OP instructions. Once in the system I couldn't get the WiFi to connect with the phone, not being able to download whatever the phone was looking for. Google play services kept FC'ing. Google TTS kept FC'ing as well. I don't know if there is a fix or a forthcoming fix for this abnormal issue. I deleted data from the apps that were FC'ing and other Google that might be related. PS: not a RR issue I had this same issue with Benzo)
Unfortunately, we didn't save anything from the old RR setup because I couldn't be without a phone for another day. Any constructive thoughts would be welcomed.
I shall attempt to reinstall RR at some point to see if it works, or to get data to help the devs understand what might have happened or might had happened.
I am back on stock, not loving it that is for sure.
Scottay5150 said:
OK folks. I want to apologize for my flooding of the forums attempting to repair my situation last week. Yes, I have been flashing for a long time without real complications. I haven't been on my ADHD meds for a while and that did not help me with the drama last week. Unfortunately my world like most of you is in my phone, I was panicked. Sorry about that.
Needless to say I needed other eyes on what I was doing for perspective sake. I went to my PC tech, luckily had personal flashing experiences with Android, Pixel even. We worked on it for about 6 hours in total. He couldn't get RR to work.
The issue was this after following the OP instructions. Once in the system I couldn't get the WiFi to connect with the phone, not being able to download whatever the phone was looking for. Google play services kept FC'ing. Google TTS kept FC'ing as well. I don't know if there is a fix or a forthcoming fix for this abnormal issue. I deleted data from the apps that were FC'ing and other Google that might be related. PS: not a RR issue I had this same issue with Benzo)
Unfortunately, we didn't save anything from the old RR setup because I couldn't be without a phone for another day. Any constructive thoughts would be welcomed.
I shall attempt to reinstall RR at some point to see if it works, or to get data to help the devs understand what might have happened or might had happened.
I am back on stock, not loving it that is for sure.
Click to expand...
Click to collapse
Sounds to me like you used the wrong GApps. Or maybe used the wrong TWRP, or tried installing TWRP when you should have just booted it. Something like that.
borxnx said:
Sounds to me like you used the wrong GApps. Or maybe used the wrong TWRP, or tried installing TWRP when you should have just booted it. Something like that.
Click to expand...
Click to collapse
I wish I could say the wrong GAPPS, the version from the OP was used (others had issues as well), TWRP 3.2.0 again from the OP was installed per instructions. They were not. Not letting system boot up might have been the bigger issue. I shall never know.

Categories

Resources