I accidently deleted my back-up and now I'm left with TWRP 2.2 and everytime I try to install a tom it fails halfway through. So I looked and most say ignore and wipe Dalvik cache, so I do. Reboot, then it just boots to TWRP.
Kindle Fire Utility will not detect my Fire either.
I'm at a loss, please help.. :\
In twrp go to mount and then mount the drive. Then download a rom from the development section and transfer it to your kindle. Then flash the rom.
---------- Post added at 11:21 PM ---------- Previous post was at 11:21 PM ----------
veeman said:
In twrp go to mount and then mount the drive. Then download a rom from the development section and transfer it to your kindle. Then flash the rom.
Click to expand...
Click to collapse
Do a factory reset again and then flash.
veeman said:
In twrp go to mount and then mount the drive. Then download a rom from the development section and transfer it to your kindle. Then flash the rom.
---------- Post added at 11:21 PM ---------- Previous post was at 11:21 PM ----------
Do a factory reset again and then flash.
Click to expand...
Click to collapse
I followed your instructions explicitly and they were to no avail, as they relinquished the same results in my latter post.
I've been inactive here over the last month, but from what I've seen the over last couple of days, it seems there's a new version of TWRP (2.2.0? am I seeing this correctly?) that is causing problems. Try an earlier version.
soupmagnet said:
I've been inactive here over the last month, but from what I've seen the over last couple of days, it seems there's a new version of TWRP (2.2.0? am I seeing this correctly?) that is causing problems. Try an earlier version.
Click to expand...
Click to collapse
I had first tried 2.0 then updated to 2.2.
Thanks
Then I would say, since you know you can restore from a backup, try requesting one (minus personal data of course) from someone and see if you can restore from it.
It's very strange some of the things going on lately. I'd hate to think Amazon's hardware has something to do with it, although, I wouldn't put it past them.
soupmagnet said:
Then I would say, since you know you can restore from a backup, try requesting one (minus personal data of course) from someone and see if you can restore from it.
It's very strange some of the things going on lately. I'd hate to think Amazon's hardware has something to do with it, although, I wouldn't put it past them.
Click to expand...
Click to collapse
Any idea where I'd look for a back-up?
The idea has merit, I just googled it and nothing came up.
maybe you'd volunteer to send me a back up?
Thanks
JerzyLW said:
Any idea where I'd look for a back-up?
The idea has merit, I just googled it and nothing came up.
maybe you'd volunteer to send me a back up?
Thanks
Click to expand...
Click to collapse
Lemme see what I can do...
---------- Post added at 12:17 AM ---------- Previous post was at 12:12 AM ----------
Gimme time to flash something create a backup and upload it stick around It won't be posted for long...
Thepooch said:
Lemme see what I can do...
Click to expand...
Click to collapse
It is much appreciated! :highfive:
Check your pm
---------- Post added at 12:52 AM ---------- Previous post was at 12:44 AM ----------
I was thinking more direct upload but since your not here that's kinda difficult lol yea restoring a borrowed backup is probably your best bet once you have a working system replacing twrp would probably be a good idea I have a simple solution for that that really doesn't require much just placing a folder on your SD card and using file browser to run a script... but I really can tell you whether this will remedy your problem if it still exists it could be more than meets the eye..
Maybe your just doing it wrong.
1. Factory reset
2. Wipe cache
3. Wipe dalvik
4. Wipe system
5. Flash rom zip (in zip form)
6. Flash gapps zip (in zip form)
7. Reboot then system if prompted....
If your doing all this and it fails make sure you have zip signature verification and md5 verification unchecked, still failing sounds like a twrp problem..
Also twrp should be throwing you some errors would be nice to know what they are?
Thepooch said:
Check your pm
---------- Post added at 12:52 AM ---------- Previous post was at 12:44 AM ----------
I was thinking more direct upload but since your not here that's kinda difficult lol yea restoring a borrowed backup is probably your best bet once you have a working system replacing twrp would probably be a good idea I have a simple solution for that that really doesn't require much just placing a folder on your SD card and using file browser to run a script... but I really can tell you whether this will remedy your problem if it still exists it could be more than meets the eye..
Click to expand...
Click to collapse
The restore was successful. I am now stuck in a boot loop with TWRP.
And I still cannot get KFU to recognize my Fire either.
JerzyLW said:
The restore was successful. I am now stuck in a boot loop with TWRP.
And I still cannot get KFU to recognize my Fire either.
Click to expand...
Click to collapse
Install a newer version of TWRP (2.1.1 or greater). Reboot to system does not work properly in earlier versions. Otherwise, use "adb shell idme bootmode 4000" to set the bootmode to normal manually. If you are unfamiliar with adb/fastboot, read this guide...
http://forum.xda-developers.com/showthread.php?t=1552547
The third post has explanations of adb/fastboot commands and how to use them, but the entire guide will probably be useful to you.
kinfauns said:
Install a newer version of TWRP (2.1.1 or greater). Reboot to system does not work properly in earlier versions. Otherwise, use "adb shell idme bootmode 4000" to set the bootmode to normal manually. If you are unfamiliar with adb/fastboot, read this guide...
http://forum.xda-developers.com/showthread.php?t=1552547
The third post has explanations of adb/fastboot commands and how to use them, but the entire guide will probably be useful to you.
Click to expand...
Click to collapse
Thanks I'll take a look.
JerzyLW said:
Thanks I'll take a look.
Click to expand...
Click to collapse
No matter what I do, I cannot get my computer to recognize my Kindle. In device manager it says it is there with a yellow triangle, so I click update it doesn't work, I check my Android SDK downloader and it says I have the drivers downloaded so I manually searched for them in the extras folder in the sdk folder, still no go. I get an error. I am now at ends I have no idea what to do, and it is very aggravating to say the least.
Thanks for your help guys!
Instead of letting it boot by itself manually select normal boot in the boot menu if that doesn't work rewipe restore the backup again this time skip the dalvik and cache wipe after the restore...
My computer can't find my kindle fire and it's mounted on twrp
make sure there are no checks in the boxes of system and data then hit the big button that says mount..... the only things that should have checks in them are sdcard and cache...
Thepooch said:
make sure there are no checks in the boxes of system and data then hit the big button that says mount..... the only things that should have checks in them are sdcard and cache...
Click to expand...
Click to collapse
Yes they are but the computer wont find it. Do you know how to get the computer to find the kindle via adb?
if you cant mount your sdcard there is more at play than meets the eye look at this thread http://forum.xda-developers.com/showthread.php?t=1877567
Related
Hi!
I will have to send my Kindle back since it has a hardware issue. What is the smoothest way to reset it completely i.e including removing TWRP2 and the custom bootloader.
I found a quite outdated thread in which it seemed like you could just flash the original Kindle image, will that work? Also, I do have a NAND-backup, if I restore the device to this backup will it also restore the bootloader and remove TWRP?
Thanks in advance!
Massy
Masssy said:
Hi!
I will have to send my Kindle back since it has a hardware issue. What is the smoothest way to reset it completely i.e including removing TWRP2 and the custom bootloader.
I found a quite outdated thread in which it seemed like you could just flash the original Kindle image, will that work? Also, I do have a NAND-backup, if I restore the device to this backup will it also restore the bootloader and remove TWRP?
Thanks in advance!
Massy
Click to expand...
Click to collapse
If you flash the stock ROM it will reset everything including TWRP and root..
fiddlefaddle said:
If you flash the stock ROM it will reset everything including TWRP and root..
Click to expand...
Click to collapse
Worked perfectly, had a hard time finding the stock software though. While looked for it I did I find a thread that discussed the matter further. As it turns out you could get it from Amazons site, duh
Masssy said:
Worked perfectly, had a hard time finding the stock software though. While looked for it I did I find a thread that discussed the matter further. As it turns out you could get it from Amazons site, duh
Click to expand...
Click to collapse
Can you share the steps as what you did?
wintablet said:
Can you share the steps as what you did?
Click to expand...
Click to collapse
Download the stock software from amazon.com and http://www.amazon.com/gp/help/customer/display.html/ref=hp_k6_updatesi?nodeId=200790620
And wipe everything in TWRP then flash like any other rom...
fiddlefaddle said:
Download the stock software from amazon.com and http://www.amazon.com/gp/help/customer/display.html/ref=hp_k6_updatesi?nodeId=200790620
And wipe everything in TWRP then flash like any other rom...
Click to expand...
Click to collapse
The downloaded file is a bin file. After downloading I copied that to root of SD card (Just like any other ROM), however TWRP won't see that file when I boot KF in Recovery.
You have to rename the .bin to .zip before moving it to your sdcard
just be careful with how you wipe. I wiped too much once and ended up having to get a factory cable to fix my kindle.
soupmagnet said:
You have to rename the .bin to .zip before moving it to your sdcard
Click to expand...
Click to collapse
You are right I forgot about that... thanks lol
---------- Post added at 02:36 PM ---------- Previous post was at 02:34 PM ----------
chris_m128 said:
just be careful with how you wipe. I wiped too much once and ended up having to get a factory cable to fix my kindle.
Click to expand...
Click to collapse
Correct... factory reset,cashe,dalvik.. that's it DO NOT WIPE SDCARD OR SYSTEM.
First day I got the phone I rooted and installed clockwork mod. I downloaded and installed cm9 but now I can't flash any other roms. Every time I try and flash a new one it boots to log screen then stays on a blank black screen. Any help would be appreciated as i would like to try something else out. Also I followed the flashing instructions of each rom and even tried formatting system with no luck.
just to check, you have to format data as well as cache and dalvik when switching amongst roms. not assuming you didn't, just checking.
---------- Post added at 04:26 PM ---------- Previous post was at 04:16 PM ----------
another thought would be to try to flash via recovery, if you haven't tried that.
scott0 said:
just to check, you have to format data as well as cache and dalvik when switching amongst roms. not assuming you didn't, just checking.
---------- Post added at 04:26 PM ---------- Previous post was at 04:16 PM ----------
another thought would be to try to flash via recovery, if you haven't tried that.
Click to expand...
Click to collapse
Thanks for your reply. I have tried flashing in recovery, and just to make sure I was doing everything ok I wiped cache, wiped davlik cache and formatted the system and it still boots to lg screen, then goes to a blank black screen (but the screen is still on) and stops there. The only rom I can get to flash is CM9.
lendmeyoureers said:
Thanks for your reply. I have tried flashing in recovery, and just to make sure I was doing everything ok I wiped cache, wiped davlik cache and formatted the system and it still boots to lg screen, then goes to a blank black screen (but the screen is still on) and stops there. The only rom I can get to flash is CM9.
Click to expand...
Click to collapse
What ROMs are you attempting to flash that aren't working? Did you try to re-download them to see if the original download was corrupted?
drumist said:
What ROMs are you attempting to flash that aren't working? Did you try to re-download them to see if the original download was corrupted?
Click to expand...
Click to collapse
I have tried the kernelpan1c one and domination HD multiple times through multiple downloads.
lendmeyoureers said:
I have tried the kernelpan1c one and domination HD multiple times through multiple downloads.
Click to expand...
Click to collapse
ahh yes, i bricked my phone several months ago this very way, it looks to me like you will have to do machz' unbrick.
scott0 said:
ahh yes, i bricked my phone several months ago this very way, it looks to me like you will have to do machz' unbrick.
Click to expand...
Click to collapse
But the phone isn't bricked. I can boot and even install CM9 but no other ROM. I have tried the unbrick (post 29) but I get stuck at the lg install tool when I plug my phone in it says failed to download
lendmeyoureers said:
But the phone isn't bricked. I can boot and even install CM9 but no other ROM. I have tried the unbrick (post 29) but I get stuck at the lg install tool when I plug my phone in it says failed to download
Click to expand...
Click to collapse
i didn't say your's was bricked, i said i bricked mine doing what you did.
my point was going towards the topic of the thread, you want to fix your phone to be able to flash other ROMs and i'm figuring you will need to follow the unbricking guide to get your phone to a point to do that, even if it's not bricked, by definition.
i'm not sure what post 29 is, but i've done machz's unbricking 2x succesfully, it's the 1st post in his thread.
either way, i know how frustrating it can be, i hope you get it all sorted out.
lendmeyoureers said:
I have tried the kernelpan1c one and domination HD multiple times through multiple downloads.
Click to expand...
Click to collapse
The reason you're having the problem is because the Kernelpan1c ROM does not include a boot image. I'm guessing the Domination HD ROM didn't either, although it seems like the thread for that ROM was deleted so I can't verify that. The ROMs require that you still have the default LG Gingerbread boot image on your device for either of them to work.
Meanwhile CM9 includes a custom boot image, which is necessary since it's ICS.
Do you have a Nandroid backup from when your phone had stock LG Gingerbread installed? If so, what you should do is first restore the Nandroid backup (which will also revert your boot image), then install Kernelpan1c or DominationHD ROM.
If you don't have a nandroid backup, let me know.
---------- Post added at 10:38 AM ---------- Previous post was at 10:34 AM ----------
scott0 said:
my point was going towards the topic of the thread, you want to fix your phone to be able to flash other ROMs and i'm figuring you will need to follow the unbricking guide to get your phone to a point to do that, even if it's not bricked, by definition.
Click to expand...
Click to collapse
Unbricking is overkill. He can boot into CM9 which would give him root access already, so really all he would need to do is go into terminal emulator and push the correct boot image to his device (unless he already has a Nandroid backup, which is easier and less prone to accidentally bricking the device).
drumist said:
The reason you're having the problem is because the Kernelpan1c ROM does not include a boot image. I'm guessing the Domination HD ROM didn't either, although it seems like the thread for that ROM was deleted so I can't verify that. The ROMs require that you still have the default LG Gingerbread boot image on your device for either of them to work.
Meanwhile CM9 includes a custom boot image, which is necessary since it's ICS.
Do you have a Nandroid backup from when your phone had stock LG Gingerbread installed? If so, what you should do is first restore the Nandroid backup (which will also revert your boot image), then install Kernelpan1c or DominationHD ROM.
If you don't have a nandroid backup, let me know.
---------- Post added at 10:38 AM ---------- Previous post was at 10:34 AM ----------
Unbricking is overkill. He can boot into CM9 which would give him root access already, so really all he would need to do is go into terminal emulator and push the correct boot image to his device (unless he already has a Nandroid backup, which is easier and less prone to accidentally bricking the device).
Click to expand...
Click to collapse
this is good advices. but i never was able to sort out how to use terminal emulator, ugh. i kept trying to run commands from within the phone that were ....hekk can't recall exactly. it was frustrating.
but the best advice i think is the nandroid b/u of the original ROM. although nothing necc. wrong with doing a debrick, only takes <30 minutes, as long as the debricking Gods are all in a good mood at that particular moment.
If you get hono's GB rom, then flash HONO's GB kernel, you should be able to boot into GB no problem
drumist said:
The reason you're having the problem is because the Kernelpan1c ROM does not include a boot image. I'm guessing the Domination HD ROM didn't either, although it seems like the thread for that ROM was deleted so I can't verify that. The ROMs require that you still have the default LG Gingerbread boot image on your device for either of them to work.
Meanwhile CM9 includes a custom boot image, which is necessary since it's ICS.
Do you have a Nandroid backup from when your phone had stock LG Gingerbread installed? If so, what you should do is first restore the Nandroid backup (which will also revert your boot image), then install Kernelpan1c or DominationHD ROM.
If you don't have a nandroid backup, let me know.
---------- Post added at 10:38 AM ---------- Previous post was at 10:34 AM ----------
Unbricking is overkill. He can boot into CM9 which would give him root access already, so really all he would need to do is go into terminal emulator and push the correct boot image to his device (unless he already has a Nandroid backup, which is easier and less prone to accidentally bricking the device).
Click to expand...
Click to collapse
Thanks everyone for the replies. I don't have a backup of the original GB ROM, so I'm assuming the boot img is my issue. Someone mentioned flashing a boot image through CM9. Is there a specific instruction list for this? I can go forward with the unbricking procedure if you guys think its easier.
lendmeyoureers said:
Thanks everyone for the replies. I don't have a backup of the original GB ROM, so I'm assuming the boot img is my issue. Someone mentioned flashing a boot image through CM9. Is there a specific instruction list for this? I can go forward with the unbricking procedure if you guys think its easier.
Click to expand...
Click to collapse
Go to the unbricking guide thread and download the boot.img file and place it on your SD card. You don't need any other file.
Next from CM9, open terminal emulator (may have to install it) and type:
Code:
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
Be extra careful that you type this exactly! It's a zero, not an 'o', following 'mmcblk', and it must all be lowercase.
Next turn the device off. If it won't turn off, just pull the battery. Don't try to boot back into CM9 because the phone won't boot up properly at this point in time.
Next use volume down + power to get into CWM again. From there, do factory reset/wipe data and install the ROM you want like normal. It should boot up fine now.
(If it doesn't, you can reflash CM9.)
drumist said:
Go to the unbricking guide thread and download the boot.img file and place it on your SD card. You don't need any other file.
Next from CM9, open terminal emulator (may have to install it) and type:
Code:
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
Be extra careful that you type this exactly! It's a zero, not an 'o', following 'mmcblk', and it must all be lowercase.
Next turn the device off. If it won't turn off, just pull the battery. Don't try to boot back into CM9 because the phone won't boot up properly at this point in time.
Next use volume down + power to get into CWM again. From there, do factory reset/wipe data and install the ROM you want like normal. It should boot up fine now.
(If it doesn't, you can reflash CM9.)
Click to expand...
Click to collapse
THIS WORKED! Thanks so much! Now if there were only more then 1 ROM whose download links worked...
hah, yeah, that command reminded me of what i was doing wrong, i was mistakenly trying to run shell commands from the emulator.
lendmeyoureers said:
THIS WORKED! Thanks so much! Now if there were only more then 1 ROM whose download links worked...
Click to expand...
Click to collapse
Awesome. Now make a Nandroid backup BEFORE you install another ROM, so you have an easier way to revert to your current boot image. That way you can install CM9 again later if you want without worrying about going through this again if you want to install something else.
The last thing I remember doing is going to flash a new ROM.
I went into recovery then pushed "factory reset" in CWM.
Ever since then I have not been able to mount /data or /cache so I cannot restore a backup or flash a new ROM. I've tried a lot of different things, NOW I cannot even get a Recovery to start up. (flashed and deleted different versions of different Recoveries (TWRP and CWM).
Was wondering what other solutions there might be.
Right now I am currently using an older booloader with the yellow triangle. Any help is appreciated. Thank you so much!
Well start by putting twrp back on if at all possible go to mount and make sure there are no checks in the boxes of data in system and try to flash another rom or do a restore if you still have issues something far worse has gone wrong post back when and if you can get to that point
---------- Post added at 08:45 PM ---------- Previous post was at 08:41 PM ----------
Also read the first post then maybe through this thread and make sure this is not your case http://forum.xda-developers.com/showthread.php?t=1651413
I'm having an issue with the latest liquidsmooth ROM. I updated my kernel, cleared my cache and my dalvik. This is a dirty flash. But I'm stuck at the Liquidsmooth loading animation. It has sat here for a good 10 minutes so far. Is this normal for the first time? I had this issue before so I just flashed back to my old rom and it was fine after that.
Anyone please? I can't use my phone and have no back ups or another rom to flash to. And my computer wont install the drivers in order to push a rom onto my phone..
What did you dirty flash from? Dirty flashes are generally a bad idea, unless you are flashing from an update for a rom. But even then, you need to make sure the OP says its ok to dirty flash because the nature of some update can require a full wipe
Sent from my PG06100
---------- Post added at 11:41 PM ---------- Previous post was at 11:40 PM ----------
And you dont need the drivers to get a rom on your phone. Just mount the sdcard through recovery and it should show as a usb mass storage device
Sent from my PG06100
CNexus said:
What did you dirty flash from? Dirty flashes are generally a bad idea, unless you are flashing from an update for a rom. But even then, you need to make sure the OP says its ok to dirty flash because the nature of some update can require a full wipe
Sent from my PG06100
---------- Post added at 11:41 PM ---------- Previous post was at 11:40 PM ----------
And you dont need the drivers to get a rom on your phone. Just mount the sdcard through recovery and it should show as a usb mass storage device
Sent from my PG06100
Click to expand...
Click to collapse
I did a dirty flash from JellyBomb. And it wont allow me to mount the sdcard, I choose it and it just stays at "mount sdcard". I have mounted the extsdcard but when I plug my phone into my computer, it makes 3 beeps and doesn't display anything. Also, I appreciate all the help.
Edit: After doing a wipe installing liquidsmooth works now I have lost eveyrthing though
Theminatar said:
I did a dirty flash from JellyBomb. And it wont allow me to mount the sdcard, I choose it and it just stays at "mount sdcard". I have mounted the extsdcard but when I plug my phone into my computer, it makes 3 beeps and doesn't display anything. Also, I appreciate all the help.
Edit: After doing a wipe installing liquidsmooth works now I have lost eveyrthing though
Click to expand...
Click to collapse
You shouldve made a nandroid, then you couldve done advanced restore > data only....
Sent from my PG06100
So I was looking at vines when my rom (newest liquidsmooth) froze and hard booted. It got stuck at kernel splash screen (newest att kt747). Rebooted into recovery (Twrp 2.6.0.0) and it's asking for a password. I have never set a password and I can't see/install anything. Just empty folders.
Naturesretard said:
So I was looking at vines when my rom (newest liquidsmooth) froze and hard booted. It got stuck at kernel splash screen (newest att kt747). Rebooted into recovery (Twrp 2.6.0.0) and it's asking for a password. I have never set a password and I can't see/install anything. Just empty folders.
Click to expand...
Click to collapse
I cannot wipe any partitions or perform any actions. My phone also refuses to boot.
No download mode?
Sent from my SGH-T999 using Tapatalk
Try this If TWRP is asking for a password and not booting do this: Re odin recovery twrp 2.4.4.0, wipe ALL data, odin twrp 2.6.1.0 back on to the device, reboot recovery, re-wipe data, flash desired COMPATIBLE rom.
---------- Post added at 05:39 AM ---------- Previous post was at 05:24 AM ----------
ssingh0247 said:
Try this If TWRP is asking for a password and not booting do this: Re odin recovery twrp 2.4.4.0, wipe ALL data, odin twrp 2.6.1.0 back on to the device, reboot recovery, re-wipe data, flash desired COMPATIBLE rom.
Click to expand...
Click to collapse
22
ssingh0247 said:
Try this If TWRP is asking for a password and not booting do this: Re odin recovery twrp 2.4.4.0, wipe ALL data, odin twrp 2.6.1.0 back on to the device, reboot recovery, re-wipe data, flash desired COMPATIBLE rom.
---------- Post added at 05:39 AM ---------- Previous post was at 05:24 AM ----------
22
Click to expand...
Click to collapse
I am in the exact same situation, from the random reboot, non-booting phone, and password in TWRP on my d2vzw. I'll try the above and let you know what I come up with.
On a different note, if I take my SD card out and reinstall it, TWRP 2.6.1.0 reads it. I will try putting a ROM and GAPPS package on it, reflashing from the SD and using GOOManager to fix my recovery. This might be a viable option B.
Hopefully one of these will do the trick.
scubamike said:
I am in the exact same situation, from the random reboot, non-booting phone, and password in TWRP on my d2vzw. I'll try the above and let you know what I come up with.
On a different note, if I take my SD card out and reinstall it, TWRP 2.6.1.0 reads it. I will try putting a ROM and GAPPS package on it, reflashing from the SD and using GOOManager to fix my recovery. This might be a viable option B.
Hopefully one of these will do the trick.
Click to expand...
Click to collapse
To all besieged by the TWRP 2.6.x.x problems, it has a bug in reading or even mounting internal SD Partition. That may cause this or other issues for you. Strongly suggest reverting to 2.5.0.0
scubamike said:
I am in the exact same situation, from the random reboot, non-booting phone, and password in TWRP on my d2vzw. I'll try the above and let you know what I come up with.
On a different note, if I take my SD card out and reinstall it, TWRP 2.6.1.0 reads it. I will try putting a ROM and GAPPS package on it, reflashing from the SD and using GOOManager to fix my recovery. This might be a viable option B.
Hopefully one of these will do the trick.
Click to expand...
Click to collapse
try that and let me know how it goes. and a word of advice don't flash ROM's to often because you can brick your phone and don't flash random kernals like i did so now my phone is hard bricked meaning it wont do anything but i bought a jig so it should work again
No go so far...
I've tried reflashing the PacMan Rom, which started this whole problem, from the ext-SD. It will not get past the Samsung boot screen. I tried reflashing an older, AOKP ROM with the same result.
I Odined back to TWRP 2.4.4.0, but I could not wipe any data because I still can't mount anything other than the ext-SD. I went all the way to 2.6.3.0 without success. So far, I've settled on TWRP 2.5.0.0.
I've also tried restoring an old nandroid that I had on the SD card, but it failed at "Wiping Data". At this point, I'm planning on Odin back to stock and see where that leaves me. I'd really like to access some of the data on the internal storage, but I will settle for a phone that makes calls for now. My factory image is almost downloaded. I may get to it tonight.
Again, I'll keep you posted.
---------- Post added at 02:49 AM ---------- Previous post was at 02:43 AM ----------
I also tried flashing the newest version of CWM recovery, but it couldn't mount the internal storage either.
Has my internal data actually been physically changed to an unreadable format, or is the way it is being read from recovery(s).
Where did the encryption come from? I've flashed literally over 100 roms between my GNex and my S3 with zero issues. This is baffling.
Lastly, if I Odin back to 4.1.2, will my data be decrypted by the ROM, or could I do more harm than good?
---------- Post added at 03:21 AM ---------- Previous post was at 02:49 AM ----------
Odined back to VRBMB1. Rebooted. Wouldn't boot. I booted into stock recovery and did a factory reset. I was finally able to boot into stock Samsung software.
I don't know how many of you are praying people, but this was an answer to my prayers!
Thread cleaned
Either help the OP or do not post
Disrespect of other members will not be tolerated
Also please refrain from disrespecting developers and ROMs
Thank you for your cooperation
Friendly Neighborhood Moderator
Sorry. Been away. Managed to fix my own problem. Let me explain:
Crashed while watching video in ROM. Rebooted into recovery to clean cache and dalvik just to see if it would fix. Asked for password.
Odined 2.5 and same problem. The only way to fix was flash my t999l back to stock. Weird as hell... but I'm running better on stockorama.
Sent from my SGH-T999 using xda app-developers app