Hello there,
Well, to preface what has led me into the situation that I am in right now, I had installed SS in the hope of creating a virtual ram disk and installing a custom rom within it. Where I messed up is that, despite me having the virtual rom created, I flashed a ROM zip over the stock android rom and not on the virtual rom slot, thus locking me out of my phone. I had done a standard factory wipe before installing the new rom and (unless I am incorrect) have wiped out the usb debugging functionality I had previously enabled as a result. When starting my phone, I am still able to access the custom recovery that SS has installed (I545 Safestrap 3.75 (TWRP v2.7.10)). However, from there I attempt to boot the phone into system, I get an error notice to the effect of "There is software Verizon doesn't supprot please take this to your nearest Verizon store, etc, etc." With a notice at the top saying kernel failed - and at that point if I attempt to start the phone by pulling out battery and restarting, it negates the option to log into SS/TWRP recovery and leads me to that verizon incompatibility screen all over again.
This is where it get interesting though
(I would use link functionality to post a Heimdall screenshot but I couldn't remember my old xda account info and it prohibits users w/ less than 10 posts from posthing links)
If I attempt to reflash the MDK kernel through Heimdall, despite it saying that it failed in the log, my phone reboots and it once again brings me to the SS splash screen at the ability and I able to get back into the SS/TWRP recovery yet again. Very weird.
I have been primarily following instructions from this site: droidview's "how-to-install-latest-official-firmware-on-samsung-galaxy-s4-all-models" (which you can find easily via those terms in google without me posting link)
I have been using the original .pit file that I have pulled from my own phone from heimdall myself (before I locked myself out of stock rom compeltely) but do have a PIT file copy from the website where I have been referencing before.
I have yet to try to flash a zip file of a 4.4.2 verizon ROM via the SS/TWRP recovery because I don't have any SD card readers in my computer and had previously put the custom firmware I had wished to install on my sd card via mounting my phones SD card through the stock ROM to my pc before I messed up overwriting it. The functionality for SS mounting sd card via the recovery itself seems to be broken so that isn't an option. However, I could borrow a phone from someone else and mount my SD card through their phone and access it from my PC that way.
All attempts of reflashing via ODIN on my windows partition have failed as well. ODIN recognizes my device but, following the instuctions from the instructions I referenced earlier, have resulted in it displaying a "FAIL" message almost immediately.
Thanks for taking the time to read this much and I'd appreciate any help I can get.
Related
***************SOLVED*******************
Hey, hoping some android gurus can help me out here.
I had the latest version of Obsydian on my phone and have not had any issues. Yesterday, my battery on the phone died, and when it started up again I was getting forcecloses all over the place. Tried reinstalling the rom and go errors, tried a different rom and got errors. So I ODINed the Voodoo RFS fix, followed by stock+Voodoo-Froyo-T959-UVJL5.tar , and didn't get anywhere.
I thought there might have been something wrong with the data on the phone so i tried clearing and formatting everything through Clockwork recovery. Then I tried the partition SD Card through clockwork recovery. I assumed it was the EXT-SD it was formatting so i chose 128mb ext, 32 swap, and left the rest for fat32. However, I'm starting to think it might have been the internal SD card.
I tried ODINing back to stock stock using this guide: http://androidspin.com/2010/08/09/h...droidSPIN+|+Your+No.1+source+for+Android+news.)
I get the phone in ODIN and it flashes, no errors in ODIN, but when the phone leaves download mode and goes to installation it gives a few errors:
Code:
MBR Checksum Error
Movinand Checksum Confirmation Fail
Then it continues installing, and I get another error:
Code:
Wiping data
Formatting Data
[B]Data Wipe Fail[/B]
Formatting Cache
It still acts like it completely finishes the installation, reboots, I get the Tmobile boot and then Galaxy S, and then I get a black screen with all 4 of the lights/buttons on the bottom of the screen on. It can sit like this for 30 minutes, it doesn't do anything.
I still have access to download mode, and I still have access to recovery, however it's no longer ClockworkMod recovery, it's the stock recovery, and it seems to only work for a few moments before going to a triangle with an exclamation point and the android logo.
Any ideas on what I can do to make this phone functional again, or acceptable for a warranty return?
I appreciate any help.
Welcome to the club
Check out my post http://http://forum.xda-developers.com/showthread.php?t=887837
Post #3 it might help if it does let me know so we know for sure if it works
Yes welcome to the club!!! glad you could join us!
Anyways here is what I have learned/done, my only working rom currently is the eugene froyo, can use the phone and data BUT cant download anything or install anything. You can adb push apks into the rom though. Heres the link for it
Use Odin, pit=512, pda=eugene..tar Run this to get semi working rom
http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=3
Once here I have access to my Sd card, this is where I placed the clockwork recovery on as an "update.zip" Link to this is posted below
http://forum.xda-developers.com/showthread.php?t=734164
Boot into recovery, note this will take you to stock recovery. REINSTALL update, may have to do this twice but itll get you to the Clockwork recovery....
After this I tried to install two different roms and both times I get some sort of data error, and installation aborted....hopefully this will help a few people
Yeah a bit more google searching for "vibrant mbr checksum" brought me to the same conclusion, that I needed to ODIN the eugene's froyo - it's flashing right now. Will see where that gets me.
It's my belief that using the SD partition in CWM is what caused the MBR issues and the Data Wipe Fail, as others said they messed with a partition in either CWM or something else prior to this happening
And that's a no go. It just reboots back into the stock recovery every time after odining it, with some new errors.
update media. please wait.
E:Can't mount /dev/block/mmcblk0p1
(Invalid argument)
E:copu_dbdata_meda:Can't mount SDCARD:
your storage not prepared yet. please use UI menu for format and reboot actions.
copy default media content failed.
Click to expand...
Click to collapse
I take it back - i did the wrong one apparently.
Had to use the files located on the link you sent, inside of the Eugene_2E_JK2_Froyo.zip file. Apparently there are a few different download files on the first post of that link. This one took longer than all the others I'd tried ODINing, about 5-6 minutes, compared to 2-3 for the others. I had also updated my Odin3 to v1.7, from the v1.3 I was using before.
When it booted up, it gave me an issue with my external SD card, said it was formatted incorrectly, so i formatted it from the phone - it says I have 13gb memory and 1.86 on the ext-SD.
Was able to download and install ROM manager from the market. Attempting to install Nero v3 now.
*** SOLVED ***
I've succesfully installed a rom other than Eugene's froyo, and did not receive any installation errors! Got Nero V3 up and running, very happy.
Note that the MBR checksum error still appeared but did not affect installation at all. Thanks everyone for their help - hopefully this helps the others.
My old one started getting the sim card error.Still under warranty so...new phone in hand. (Refurb) I rooted using Odin 3v1.85 installed SuperUser and ClockworkModRecovery. All moves along fine. Now I try to install ROM zips (tried three) and they all abort quickly. It starts opening and checking and aborts saying error with zip file. I have downloaded three different ROMs and redid it from different sites too...same thing. What am I doing wrong?
Did you update your recovery after rooting? I recommend twrp which can be found in the original development section.
"Update my recovery" Hmmmm....since I am unsure what you mean...I guess not. TOG recommended TWRP over CWM too. I'll go take a look see. By "original dev section" I assume you mean the other subforum?
Quick explanation of updating my recovery?
Thanks for your valuable time. Here, have a coffee...U)
EDIT:
OK, I went, found and downloaded the latest TWRP2.zp for Odin install, since I'm most familiar with that method. So, am I right in these steps?
1. Re-root w Odin using .tar file from the TWRP.zip using the PDA button.
2.Update?
3. Reboot into recovery (does twrp use the same method as cwm?)
3.Install ROM zip of choice...rejoice?
That's way too complicated broseph...
You still have cwm right?
Just Go back to the twrp thread, download the recovery flashable zip.
Put it on your sdcard and flash it in cwm like a Rom.
Once that's done reboot recovery and you'll now have twrp
Button combos are built into the boatloaders, changing recovery has no effect on them whatsoever.
OK
Thanks again all....I did all of the above and finally got the ROM to load, then Gapps, and the rest of the drill. I never could access my back-up that I stored on my ext SD card and the card is not showing in any file explorers (although it shows in storage, under settings ?).
AT least I have a functioning phone...yay.
Sd card is named as /emmc and several other names.
I mistakenly flashed it to force Google Play store onto it as it was failing to work through other methods. Now all I get when it boots up is the welcome Google screen you get when you turn on an Android tablet for the first time. I can enter the Kindle settings and use wifi but I can't get to the launcher screen. I have tried to put the Fire into Amazon recovery mode using the volume down and power but it just turns on and off. Safestrap appears as disabled on the stock slot and can't see the stock rom I have put into the internal storage. Even though it isn't bricked there seems to be no way to flash a rom back and regain full control. I think the Gapps flash corrupted the firmware. In the settings I still see my firmware 4.5.2. I tried factory restoring it, wiping everything using Safestrap, but nothing works.
loughrey101 said:
I mistakenly flashed it to force Google Play store onto it as it was failing to work through other methods. Now all I get when it boots up is the welcome Google screen you get when you turn on an Android tablet for the first time. I can enter the Kindle settings and use wifi but I can't get to the launcher screen. I have tried to put the Fire into Amazon recovery mode using the volume down and power but it just turns on and off. Safestrap appears as disabled on the stock slot and can't see the stock rom I have put into the internal storage. Even though it isn't bricked there seems to be no way to flash a rom back and regain full control. I think the Gapps flash corrupted the firmware. In the settings I still see my firmware 4.5.2. I tried factory restoring it, wiping everything using Safestrap, but nothing works.
Click to expand...
Click to collapse
Responded here (double post).
You were fortunate attempts to access the native Amazon recovery menu failed as resetting from there will immediately brick the device with no possibility of recovery when Safestrap is installed. See link above for other suggestions. You need to do most of the repair work from within Safestrap recovery.
Further thoughts:
- flashing GApps over FireOS 4.5.2 is untested and likely led to your current situation (where did you read that was an option?)
- do not reset or wipe anything unless advised to do so by an experienced contributor as it will only make the situation worse and likely eliminate any hope of recovery
- if you never attempted to flash a custom rom (Nexus or CM11) then there is no image file to work from in Safestrap greatly limiting recovery options
- with WiFi functional and access to Kindle Settings you may be able to enable USB debugging (please try)
- if sucessful you may be able to transfer a rom image to your device via tether and then flash with Safestrap; please ask which files are suitable if you get that far
Download Safestrap-compatible stock image
Copy file onto tablet
Boot into Safestrap, flash the aforementioned file
Remember to disable OTA updates
EncryptedCurse said:
Download Safestrap-compatible stock image
Copy file onto tablet
Boot into Safestrap, flash the aforementioned file
Remember to disable OTA updates
Click to expand...
Click to collapse
Yes - this would be the most expeditious route of you can gain sufficient control when booting FireOS to 'see' the device when tethered. Ideally it will show up in Windows and you can simply copy the file to 'internal storage'. Failing that you will need to enable USB debug (as mentioned in an earlier post) and then use adb to push the file onto your device.
If you are successful in getting an image file on your device don't delete it even if things work out ok! With Safestrap you should always keep an flashable rom on your device for recovery purposes. The FireOS rom weighs in around 800 MB. If space is a concern the Nexus v4 and CM11 roms are somewhat smaller, <300 MB. Even if you never plan to run these roms they can be used for emergency recovery.
Hi,
I have a samsung S3 and I want to update it to lollipop or above as my nexus 5 has started randomly rebooting and I need a phone to use whilst I sort a replacement.
I have been following this guide: wccftech.com/install-aosp-android-5-1-1-lollipop-on-galaxy-s3/ as I'm a bit of a noob when it comes to this custom rom business.
I have rooted the device and installed clockworkmod recovery v6.0.1.2. and copied over the rom and the gapps file to my phone.
I then booted into recovery mode and made a backup of the current setup.
I then did the factory reset and the cache wipe(s) and installed the new zip for lollipop and then the gapps.
This is where I received an error "E: Error in /sdcard/0/0/0/Download/gapps-lp-20150314.zip (status 7) installation aborted".
I figured that I should restore to my backup now but when I press it, the app says that files can't be found.
I can see that the files that I backed up do exist but they appear to have been dumped inside a new directory called /0/0/0 (I think this has got three levels because I've tried this a few times).
Now I can't boot into an OS to get any other roms on the phone and I can't edit the files on there (I googled and saw a possible fix for the gapp status 7) and I can't get clockworkmod to recognise an external SD card so I can copy over a new rom or file to try (I have googled and it's suggested the FAT32 is the format for this phone and my size of SD card (16GB)).
Can anyone offer me some advice on how to get out of this situation?
Thanks
Sounds like you're at a place where you should start exploring using your computer instead of a recovery in order to fix your system.
I recommend using the PC software Odin and installing a stock ROM of your device. (Or perhaps using fastboot)
There's plenty of guides on how to use Odin both here on XDA and on the rest of the internet if you just look around a bit
EDIT: This link contains a (possible) fix for your problem.
http://forum.xda-developers.com/showthread.php?t=2522762
Don't use cwm as it is an outdated recovery. Use twrp instead.
Sgt.Mindfudge said:
Sounds like you're at a place where you should start exploring using your computer instead of a recovery in order to fix your system.
I recommend using the PC software Odin and installing a stock ROM of your device. (Or perhaps using fastboot)
There's plenty of guides on how to use Odin both here on XDA and on the rest of the internet if you just look around a bit
EDIT: This link contains a (possible) fix for your problem.
http://forum.xda-developers.com/showthread.php?t=2522762
Click to expand...
Click to collapse
I had a look at the link you suggested and it's one of the suggestions that had come up whilst I was googling for a fix. Unfortunately, I don't have any way to get the updated script onto the phone as the phone isn't picked up by my pc whilst it's in this state, and I can't get the recovery tool to recognise the sd card so I can't put it on there either.
I'll take a look at the stock rom or fastboot option and see if I can get back into the phone. Maybe then I can apply the fix in the suggested post.
Thanks
audit13 said:
Don't use cwm as it is an outdated recovery. Use twrp instead.
Click to expand...
Click to collapse
I'll see if I can install twrp through odin.
Thanks for your help
If the phone works in download mode, try to flash a stock rom too.
Update - fixed
Hi all, just wanted to let you know that I fixed the device with the combined advice from here:
I installed TWRP after holding the volume down + power + home buttons and then pressing volume up when the message appears (I can't remember what this mode is called). I then flashed the device with the TWRP image.
After this I rebooted into the TWRP recovery mode (Volume up + home + power and then release power button when the samsung logo appears).
At this point, the device appeared on my windows machine so I could upload a new image to the internal memory.
I decided to copy on CM13 and GApps.
I then wiped the cache, system, data, and davik cache using TWRP, then I installed CM13 and GApps.
After a reboot the device came back up as a new install.
Hopefully that information may be useful to somebody.
Thanks for all your help
Hi all
I hope that I am posting in the correct place
I need help with my Galaxy S3 SGH-T999
Recently the phone died on me, it was stock rom and with the updates through some of the apps, the phone stopped working correctly. I don't use the phone for making calls, etc, but need it for pictures and a few other apps. The phone is from T-mobile.
I tried to reset the phone and that worked until all the updates were back on and then back to the same problem.
So I decided to put on a custom rom on the phone.
I have tried the following roms:
cm-14.1-20161225-NIGHTLY-d2tmo
I9300XXUGNB6_I9300OJVGNB3_I9300XXUGNA8_HOME
RevolutionaryS5-V3
Slim-d2tmo-6.0.1.alpha.0.1-UNOFFICIAL-20160516-1346
I first installed CWM recovery and then transferred the roms over to the external sd car (also the internal card), went to boot manager (vol up) and installed the files.
It looked like the installation worked but when selecting reboot, the phone would not come back on.
I then loaded up Kies and reset the phone back to factory defaults and only then does the phone load back up after reboot.
Every time I try the custom rom - I run into the same problem
At first I thought the phone was bricked and found info about the jtag and then found something about using an SD card with the following image installed on it - tmobile-T999_4.3_debrick
With the SD card in the phone I can boot to either menus and also able to get the phone to boot to the slim-d2tmo rom. But when I pull the SD card, the phone won't boot. Nothing, no power, nada
I am not sure what I did wrong, followed the direction on the site and thought I did it correctly.
Not sure if I deleted some file, or partition needed or what. I would greatly appreciate some help with this.
Also I would like a custom rom that is stable and fast. I don't need all the bells and whistles but one thing I would like and that is for the camera to be able to take pictures using voice. I know the stock rom allows for this. Not essential but preferred.
Please help with detailed instructions.
Thanks in advance.
It,s amazing
Please elaborate. What's amazing.
Boot into download mode and confirm the model # of the phone. I see you tried to flash I9300XXUGNB6_I9300OJVGNB3_I9300XXUGNA8_HOME which not for the the T999, it's for the gt-i9300.
I want to flash Ressurection Remix on my Samsung Galaxy S3.
I tried flashing twrp recovery through Odin 3.07, but, it didnt work. I even tried Odin 3.85.
The Android System Recovery 3e, simply refuses to budge.
Please advice.
Rraayy8 said:
I want to flash Ressurection Remix on my Samsung Galaxy S3.
I tried flashing twrp recovery through Odin 3.07, but, it didnt work. I even tried Odin 3.85.
The Android System Recovery 3e, simply refuses to budge.
Please advice.
Click to expand...
Click to collapse
OPen Odin, uncheck everything except f reset time. Flash TWRP. When you see the word "reset" in the status window, remove the USB cable from the phone, remove the battery, replace the battery, boot directly into recovery.