Some how I have screwed up my partitions. I was able to Odin to stock lollipop and I can get into download and recovery. However I cannot flash anything at all at this point. In TWRP when I try to flash a custom ROM, Kernel or even the lastest TWRP version, all that happens is recovery restarts. This all started when I tried to flash SlimLP ROM. It flashed fine but would only bootloop when I tried to start phone. So I wiped everything and reflashed lollipop AllianceROM. The phone started okay but I got some error message about the UID. I noticed right away that ALL my text messages which should have been wiped were intact. The phone was running really, really slow and I had continual issues installing apps from the Playstore and TiBu. I decided to try another ROM and again wiped everything, flashed and rebooted. Again text messages were intact. I believe it's my system and/or data partition that is messed up but I am not sure. I'm not knowledgable about any of this so I really need some help here.
Factory reset in TWRP a few times and power down. Pull the battery, reinstall and Odin stock OB7 again. Watch the auto boot, it should go into stock recovery noted only by a android with wavy antennas and small progress bar that may not even fill before booting the ROM.
If you don't see that, factory reset, power down and try again. Make sure stock is OK before trying another flash. Also, use internal memory to flash from. Almost sounds like your sdcard is encrypted?
BTW, I don't know of any available PIT file for our phone. I thought it may be included in the stock tar but who knows for sure? One thing I learned a while back on the older phones going from CM to stock, flash twice to correct the partitions. Maybe it still works? -different recoveries; flash, reboot recovery, flash again. Those ROMs included recovery.
Before going to Alliance, factory reset.
From the sound of things you don't need a pit file to repartition your phone. Don't attempt to mess with that. I would do what was suggested above. Just make sure you do the "factory reset" several times then wipe data several times. also go into advanced wipe and wipe everything EXCEPT your external micro-sd card several times as well. then odin flash the stock BOB7 rom tar. That should do it.
tx_dbs_tx said:
From the sound of things you don't need a pit file to repartition your phone. Don't attempt to mess with that. I would do what was suggested above. Just make sure you do the "factory reset" several times then wipe data several times. also go into advanced wipe and wipe everything EXCEPT your external micro-sd card several times as well. then odin flash the stock BOB7 rom tar. That should do it.
Click to expand...
Click to collapse
samep said:
Factory reset in TWRP a few times and power down. Pull the battery, reinstall and Odin stock OB7 again. Watch the auto boot, it should go into stock recovery noted only by a android with wavy antennas and small progress bar that may not even fill before booting the ROM.
If you don't see that, factory reset, power down and try again. Make sure stock is OK before trying another flash. Also, use internal memory to flash from. Almost sounds like your sdcard is encrypted?
BTW, I don't know of any available PIT file for our phone. I thought it may be included in the stock tar but who knows for sure? One thing I learned a while back on the older phones going from CM to stock, flash twice to correct the partitions. Maybe it still works? -different recoveries; flash, reboot recovery, flash again. Those ROMs included recovery.
Before going to Alliance, factory reset.
Click to expand...
Click to collapse
Thank you both. I did just what you guys suggested and it worked out! Thank you again!
Related
Hi
I was flashing back to Stock from task650 to fix my gps. Well something blew up and when the phone reboots the screen goes black but I hear the AT&T start-up tune. Essentially I can't get to enable USB debugging to reflash. I can get to download or recovery, but there are no files to recover<?> and busybox never got installed.
What do I do now?
Do you have the stock recovery now? If so, try going in there and resetting to defaults. That helps sometimes.
Otherwise, you may need to Odin back to stock if you still want to go stock.
CZ Eddie said:
Do you have the stock recovery now? If so, try going in there and resetting to defaults. That helps sometimes.
Otherwise, you may need to Odin back to stock if you still want to go stock.
Click to expand...
Click to collapse
Yes I have stock recovery. Odin is of no use because it hangs waiting for the USB debug to respond. And i can't turn it on because the screen is black and I can't navigate
Do you have a micro sd card? If so, throw a rom on there. If you want to go back to stock, there' a flashable stock zip at the bottom of post #2 in the link in my signature. Under the emergency toolkit section. Flash that, turn on use debugging, do your gps fix and continue on with the task release
xBeerdroiDx said:
Do you have a micro sd card? If so, throw a rom on there. If you want to go back to stock, there' a flashable stock zip at the bottom of post #2 in the link in my signature. Under the emergency toolkit section. Flash that, turn on use debugging, do your gps fix and continue on with the task release
Click to expand...
Click to collapse
Thanks. I created an emergency tool kit on an SD, I wiped data, wiped cache and Davlik and formated system. Flashed the stock rom. When I rebooted it now hung at the Samsung Galaxy S III screen.
How do I get out of this mess?
Try wiping data and cache again in recovery
xBeerdroiDx said:
Try wiping data and cache again in recovery
Click to expand...
Click to collapse
I've wiped data and cache several times, and format/system. I've even tried to flash CWM 6.0.3.1 and I get a status 7 error. Nothing is taking.I get signature failures.
I re downloaded all the files figuring they were corrupted. Nothing doing. I need some real help, because this is beyond my abilities to figure out.,
Now I've got a red triangle showing up in recovery.
BertMor said:
I've wiped data and cache several times, and format/system. I've even tried to flash CWM 6.0.3.1 and I get a status 7 error. Nothing is taking.I get signature failures.
I re downloaded all the files figuring they were corrupted. Nothing doing. I need some real help, because this is beyond my abilities to figure out.,
Now I've got a red triangle showing up in recovery.
Click to expand...
Click to collapse
i dont know why some of these things are not working correctly for you. you're seeing the red triangle because you have stock recovery now from the stock firmware zip. you cannot flash anything in stock recovery nor can you format /system. what happens when you boot up after a factory reset and cache wipe?
a couple of your options include either using odin to flash the stock firmware back onto your device or to use odin to flash a custom recovery back and make a move from there.
xBeerdroiDx said:
i dont know why some of these things are not working correctly for you. you're seeing the red triangle because you have stock recovery now from the stock firmware zip. you cannot flash anything in stock recovery nor can you format /system. what happens when you boot up after a factory reset and cache wipe?
a couple of your options include either using odin to flash the stock firmware back onto your device or to use odin to flash a custom recovery back and make a move from there.
Click to expand...
Click to collapse
When it rains it pours. Now I can't get into recovery. I get the empty battery graphic cycling on and off, and its very warm to the touch. I think the battery is not charging.
I tried using Odin and flashed a stock rom but I kept getting verification errors and status 7 errors. Things just are not taking. I fear I've got a hard brick and I don't know what to do to fix it.
I appreciate your help
aaaaand let the questions roll:
you got verification errors in odin? and after flashing the firmware, i'm assuming you then flashed cwm and that's where you were getting the status 7 errors?
at what point did it all go off? i need to know what order you did all of these things.
can you still get into download mode?
xBeerdroiDx said:
aaaaand let the questions roll:
you got verification errors in odin? and after flashing the firmware, i'm assuming you then flashed cwm and that's where you were getting the status 7 errors?
at what point did it all go off? i need to know what order you did all of these things.
can you still get into download mode?
Click to expand...
Click to collapse
No, it won't go into download. I initially flashed stock rom, but I don't think I wiped anything. That was probably the big mistake. I used something called Samsung S3 QCom tool kit to do an initial flash. It never failed me before. And I also flashed a CWM.
I followed your advice and made a emergency SD kit and flashed from there. I did a clean flash several times. Things just never worked and I kept getting those error messages. Then it just got more difficult to get into download. Now it just flashes a drained battery
it might indeed be drained. leave it plugged in for a while and report back.
you were getting the error/status 7 messages after you flashed cwm back on it likely because the cwm wasnt up-to-date.
what was the last thing you tried before it stopped working altogether?
It gets really hot if I leave it plugged in. But it seems like I can get into recovery again. The last thing I flashed was CMW 6.0.3.1. But what is on it now is CMW 5.5.0.4
actually, what you're saying is the last thing you flashed was cwm 5.5.0.4, just via odin not cwm.
if the phone was in my hands, i would:
flash the cwm 6.0.3.1 zip, select advanced and reboot recovery. now you will be in the updated cwm recovery.
perform a full wipe: wipe data, cache, dalvik, format /system, format /data
flash rom and gapps. if you're going to stick with tasks, use the 4/23 release. i'm on that with no feature or stability issues.
wipe data, wipe cache, reboot.
give it a few minutes to boot up.
BertMor said:
No, it won't go into download. I initially flashed stock rom, but I don't think I wiped anything. That was probably the big mistake. I used something called Samsung S3 QCom tool kit to do an initial flash. It never failed me before. And I also flashed a CWM.
I followed your advice and made a emergency SD kit and flashed from there. I did a clean flash several times. Things just never worked and I kept getting those error messages. Then it just got more difficult to get into download. Now it just flashes a drained battery
Click to expand...
Click to collapse
xBeerdroiDx said:
actually, what you're saying is the last thing you flashed was cwm 5.5.0.4, just via odin not cwm.
if the phone was in my hands, i would:
flash the cwm 6.0.3.1 zip, select advanced and reboot recovery. now you will be in the updated cwm recovery.
perform a full wipe: wipe data, cache, dalvik, format /system, format /data
flash rom and gapps. if you're going to stick with tasks, use the 4/23 release. i'm on that with no feature or stability issues.
wipe data, wipe cache, reboot.
give it a few minutes to boot up.
Click to expand...
Click to collapse
Nope. When I try to flash CWM 6.0.3.1 I get an assert failed error. I came across this fix, I wonder if it is safe to try http://mobotechie.com/tips-tricks/how-to-fix-android-custom-rom-status-7-installation-abort-assert-failed-error-in-recovery-easily-ultimate-guide
BertMor said:
Nope. When I try to flash CWM 6.0.3.1 I get an assert failed error. I came across this fix, I wonder if it is safe to try http://mobotechie.com/tips-tricks/how-to-fix-android-custom-rom-status-7-installation-abort-assert-failed-error-in-recovery-easily-ultimate-guide
Click to expand...
Click to collapse
Well I think I managed it!. First I tried to install an update d/l'ed from Dropbox and that did nothing. Then I flashed an old .tar that was a rooted stock and it rebooted!
I tried editing the updater-script but I couldn't getit to save the changes properly.
Well I will now re flash the RM and CWM and hope for the best
Thanks for all your help, greatly appreciated
I had decided to upgrade my cm10 to the latest version so I went into twrp recovery backup it up wiped data, system, cache, dalvik cache, then I installed the rom and gapps and whiped cach and dalvik. Now im rebooting and im stuck in the first cm10 bootscreen with the samung galaxy s3 text an the cm10 alien dude. I tried restoring my twrp backup and it failed.
What do i do with formatting data? I tried installing older cm10 rom version I got on my phone and none worked and for some reason i cant see my sd card when i mount it through twrp
Help!
re: bootloop
genardas said:
I had decided to upgrade my cm10 to the latest version so I went into twrp recovery backup it up wiped data, system, cache, dalvik cache, then I installed the rom and gapps and whiped cach and dalvik. Now im rebooting and im stuck in the first cm10 bootscreen with the samung galaxy s3 text an the cm10 alien dude. I tried restoring my twrp backup and it failed.
What do i do with formatting data? I tried installing older cm10 rom version I got on my phone and none worked and for some reason i cant see my sd card when i mount it through twrp
Help!
Click to expand...
Click to collapse
Have you tried this? - It should work every time.
Here is the step by step guide:
After you have followed these instructions your phone will be in the same condition
as it was the day you have purchased it except with the benifit of being rooted.
Download the stock-rooted T999 firmware: http://www.androidfilehost.com/?fid=9390169635556426451
After downloading it make a folder on your desktop and unzip the file
using Winzip or 7zip so the .TAR file is in the new folder you just made.
Here is a link for ODIN which is required for flashing the stock rooted firmware (a windows app) http://d-h.st/Q14
Download and extract Odin into the same folder you made containing the TAR file.
Download the Odin Flash firmware for T999 Tmobile then copy it to the same folder as Odin
Run Odin by double clicking the Odin.exe within the same folder as the TAR file you extracted
Turn off your phone and boot into DOWNLOAD MODE (Volume Down + Home + Power Hold until phone powers up, then release and press Volume Up to enter Download Mode)
Once in Download Mode, connect the USB/Charger cable to the phone and plug into the USB port on your computer.
You should now see a COM** port listed toward the top-left of Odin (under ID:COM)
Click on the PDA button in the middle-right area of Odin.
Browse to and select the Firmware you downloaded (TAR file)
Make sure Auto-Reboot and F. Reset Time are the only options checked and that PDA is the only other thing checked.
TRIPLE CHECK your settings and that you have selected the correct firmware for your model phone and are using the correct options.
If you are using a laptop, make absolutely sure you are plugged in, or if on battery, that it is charged enough and will not go into sleep mode during flash.
Click Start to begin the flash. This will take a while, so be patient!
Once complete, in the top-left box in Odin, it will say PASS and the phone should have automatically rebooted.
You may unplug the phone and close Odin if you wish.
Wait at least 5-10 minutes for the system to boot the first time and then build its cache!
(It may seem to hang during boot, this is normal and you must be patient!!!)
Good Luck!
Sometimes it can take a while to get past that screen the first time you turn it on with a new ROM (like, 5+ minutes) - how long did you wait ?
Wow. What a crazy 24 hrs. My S3 kicked out a couple hiccups yesterday. Gave me a gapps error and then one other I don't remember. I decided to just reboot to restore everything. Phone would not boot past boot screen. Crazy. I could get into recovery. Tried to restore from backup. Nope. Stuck at boot screen. Odin back to stock w/root. Nope. Odin back to stock. Nope. Ended up Odin to stock. Boot into recovery. *Wipe data and factory reset 3 times*. It then completed a boot. FINALLY!!! OMG. Such a bizarre fluke. I am back on rooted Wicked 9.1 thanks to a backup. I searched various forums and threads on here. I tried the above procedure. (It was actually the first thing I did and what I used as a guide.) It wasn't until I did the Odin, boot into recovery and wipe data 3 times that my phone would completely boot up fully.
radar9 said:
Wow. What a crazy 24 hrs. My S3 kicked out a couple hiccups yesterday. Gave me a gapps error and then one other I don't remember. I decided to just reboot to restore everything. Phone would not boot past boot screen. Crazy. I could get into recovery. Tried to restore from backup. Nope. Stuck at boot screen. Odin back to stock w/root. Nope. Odin back to stock. Nope. Ended up Odin to stock. Boot into recovery. *Wipe data and factory reset 3 times*. It then completed a boot. FINALLY!!! OMG. Such a bizarre fluke. I am back on rooted Wicked 9.1 thanks to a backup. I searched various forums and threads on here. I tried the above procedure. (It was actually the first thing I did and what I used as a guide.) It wasn't until I did the Odin, boot into recovery and wipe data 3 times that my phone would completely boot up fully.
Click to expand...
Click to collapse
Could have saved yourself hours by doing a factory reset.
Yeah guys I restored it thorugh odin and then went into the stock recovery like an idiot and being used to the twrp recovery clicked wipe data/factory reset thinking it would reset the rom and I lost everything. Well really only lost music buts its k. Now im back on stock but I might have to root again DDD
genardas said:
Yeah guys I restored it thorugh odin and then went into the stock recovery like an idiot and being used to the twrp recovery clicked wipe data/factory reset thinking it would reset the rom and I lost everything. Well really only lost music buts its k. Now im back on stock but I might have to root again DDD
Click to expand...
Click to collapse
Next time you should keep stock rom and kernel on your sdcard so that if anything goes wrong you could flash that, usually it might fix the bootloop. When installing a JB rom, be sure that you have a kernel that is compatible with JB. If not, you could enter a bootloop. Also, BACKUP EFS.
I've got the intergalactic ROM installed on my S3 and I've had it for a while. I want to change ROMs but every time I flash a new one it flashes fine but when the phone boots up it tells me the setup wizard failed and a bunch of other stuff stopped working. any ideas on what it could be?
I'm using CWM.
Also if I just wanted to wipe everything on my phone and go back to stock so that I can re root it and try flashing roms then how would I do that?
You probably just need to factory reset. If you wanted to go back to stock rooted, flash the root66 firmware via odin then boot recovery and factory reset. Note that factory reset from stock recovery will wipe internal sd. From cwm/twrp it will leave internal sd alone unless you "format data".
Sent from my SM-N900T using Tapatalk
Hello all,
My S3 currently has TWRP 2.7.0.1 recovery and CM11 installed. It was also previously encrypted.
Recently the gapps on my S3 have completely stopped working. New accounts cannot be added and the programs immediately crash upon starting. Deleting the app-data for these has had no effect.
While I can decrypt the phone for regular use, I cannot do the same in recovery to reinstall gapps. Consequentially, it appears that the best option would be to wipe out everything to get rid of the encryption. Unfortunately, it seems that you cannot flash a new ROM over an encrypted partition via recovery. I have reached the conclusion that Odin should be used to reformat everything.
Is this a correct understanding? And how would I go about doing this safely?
First, backup everything you can. Then try a factory reset. If this doesnt help, choose format data from recovery. (Formatting /data will wipe the internal sd card).
If all else fails, then go for the odin flash. From what I have seen though the factory reset or format should be sufficient.
Be very careful using Odin of you have a 4.3 or newer bootloader. You don't want to flash an incorrect modern or bootloader which can brick your phone.
Very true, always be careful of this. I dont usually mention it for Odin flashes though because Odin will recognize the versions and will refuse to flash. Its usually flashing via recovery that is the most dangerous in my experience. (But I have seen odin flashes go bad too, its kind of rare, but always be careful with what youre doing.)
Ok I have T999L 16GB.
Phone working fine. Did hard reset because they hadn't been used in a while and wanted to start fresh.
After reboot, phone stuck in "T-Mobile 4G LTE" bootloop forever. Tried again, same thing.
Did Odin flash of latest ROM for that device (per what I could find?)
T999LUVUBOH1_T999LTMBBOH1_T999LUVUBOH1_HOME.tar
same thing, no result. Downloaded the PIT file for that phone, did another odin flash of the ROM above, but checked "re-partition" and pointed to the PIT file. Successful flashing, device rebooted. Same thing endless bootloop.
Not really sure what to do now, any ideas?
@DocHoliday77 possibly as one of the resident experts 'round these parts...
Immediately after flashing and before the first boot, get into recovery and perform a full wipe.
audit13 said:
Immediately after flashing and before the first boot, get into recovery and perform a full wipe.
Click to expand...
Click to collapse
worth a try, will report back.
edit: @audit13 - Worked like a boss, did the odin with repartition PIT file, but deselected auto-restart, went into recovery after flashed and wiped factory reset plus cache, rebooted, and BAM, got into the set up screen.
Thanks for your help.
Glad it worked for you. A factory wipe is sometimes required to make the data and cache partition available to the newly flashed rom. Even wiping via twrp or cwm may not be enough at times.
audit13 said:
Glad it worked for you. A factory wipe is sometimes required to make the data and cache partition available to the newly flashed rom. Even wiping via twrp or cwm may not be enough at times.
Click to expand...
Click to collapse
Yeah sure seems to be that way, glad that's all it was. I know the PIT mapping with the ROM must have helped too, but flashing in stock recovery after that cleared it up for writing to the new partitions like you said.
Coming from a Nexus 6 this was pretty annoying, I am used to using fastboot to do everything, I don't see a Samsung device in my future.
Same thing can happen with a nexus 4 and nexus 5 in that I still have to perform a full wipe in stock recovery if the phone was running a custom rom. Don't have a nexus 6 or 6p to play with
Samsung phones don't have a fastboot mode. The closest thing would be their download mode.