Database Info

About to flash first rom, Backups?

SO I sat up last night and got S OFF, installed recovery 5.something....made a back up of rom, used titanium to create apps back up.
I have copied the titaniumbackup folder to my computer.
I have copied clockworkmod folder to my computer.
I have exported my contacts to sd card...then to my computer
Is that all I need to back up, I am a little worried I have missed something important.
Fast responses welcome. I am sitting waiting to flash my first rom...
Also planning supercid before rom though...

You are totally set to flash in my opinion. When you make a backup with Clockworkmod Recovery or any other custom recovery you have a exact copy of the ROM and all your apps and personal settings. So you are actually triple ready I would say lol.

Okay cool, it's just that the sddir looked different after clockwork went in, files were in different order, so had to make sure the only places to back up were the folders themselves.

8thsiner said:
Okay cool, it's just that the sddir looked different after clockwork went in, files were in different order, so had to make sure the only places to back up were the folders themselves.
Click to expand...
Click to collapse
I would make sure you are s-off'ed and CID as well follow the instructions fully and presto you will have a new phone with ics running on it.
let us know how it goes.
regards
rich

S off is done, cid is done, rooting is all done, everything is backed up.
But I have been seriously distracted today playing with and setting up go launcher and numerous other go customization-al software.
Right at this minute I am waiting for for my new splash screen to load up...using the mysplash 1112.3 script
Though I am getting this error coming up,
"daemon not running starting it now on port 5037"
I got something similar when getting cid with adb...is this normal?
And this splash conversion is taking forever...Never mind, no one actually said you have to manually reboot into fast boot mode...grr...new splash screen flashed with success
I think I will wait until tomorrow to re-back up my customized look and then go for the rom again...

Although it's a good move *just in case* you should know that flashing a ROM will never wipe your sd card. So putting the backups on the computer shouldn't be necessary! In less something goes SERIOUSLY wrong there should never be a circumstance where your sd card will get wiped. Good luck, play safe, have fun ;D
Sent from my HTC Pyramid using XDA

If you s off your good look for my post and get ruu and don't worry till you get some rims going and find one or two u like not sure if anyone backs up stock Rom
Sent from my HTC Sensation 4G using xda premium

sorry to hijack your thread but i have everything like you s-off,root,cwm supercid aswell just scared to brick alot lol how did your first flash turned out ?
Sent from my HTC-Z710a using xda premium

On my first flash (EVER) I have about 2 percent battery left and stupidly flashed anyways, and ended up soft bricked and returned to HTC for a fix. Be sure you have at least 70 percent battery, (not really necessary to have quite this much but precaution) and if you know what you are doing, which I assume you do since you've gotten this far, all should go well. Good luck
Sent from my HTC Pyramid using XDA

yeah, umm.. you can also flash ROMS while charging the phone... assuming of course, you're at home, staring at your phone/PC and flashing roms...that way you won't have to worry about bricking your phone...
...jus sayin

I haven't gotten around to it yet, honestly I am still unsure as to how, and yes I have checked quite a few threads for basic details, I am a Noob despite thoughts to the contrary, but I am a fussy one at that, I must have read the s off guide over a dozen times like...
Maybe I just missed details on how to actually flash but...yeah, will let you know anyway.

Quakeworld said:
yeah, umm.. you can also flash ROMS while charging the phone... assuming of course, you're at home, staring at your phone/PC and flashing roms...that way you won't have to worry about bricking your phone...
...jus sayin
Click to expand...
Click to collapse
yeah I know...
Sent from my Sensation using XDA

HTC Thunderbolt Issues - Stuck at HTC Logo... Recovery not working, etc...

here is my issue.
2 weeks ago, i rooted my phone. all was well. flashed CWM Recovery 5.0.2.1 for my Thunderbolt. I made a backup just before i rooted so that in case ANYTHING went wrong, it would unroot me and fix any problems. So, here i am, backing up apps with Titanium Backup, and it backed up fine. The next thing i did was start to uninstall HTC Bloatware... I knew which ones were the ones i could remove, plus even if i removed the wrong one, i could just restore using my image backup. After removal, the phone instantly ran better. i had over 65% free memory space... This was all well and good, until i rebooted the phone. the instant i rebooted my phone, i was getting the flashing HTC Quietly Brilliant screen. i had done NOTHING to it to cause this. It would alternate from HTC splash to Thunderbolt animation.
So, knowing what was wrong, (UI not loading) i went to recover my image from CWM. that went fine. but things just got worse. After a successful recovery (according to CWM) i rebooted, but to my surprise, now its worse. its stuck at the HTC boot logo. ALL MANNER OF ROMS DO NOT WORK!!! recoveries, new OS, anything, all the same result. AT LEAST with the thunderstick full blown ROM, i can get back to the looping splash screen, but not any further. i DONT KNOW what is wrong but i am hoping one of you mad phone geniuses out there can get my phone working. i tried getting s-off with revolutionary, but it failed because the phone has to be booted up for it to work, and is something i obviously cant do at this point... relocking the phone made things worse too because i unlocked using the HTCdev method.
This is not a boot loop, as it doesnt loop. it just sits there. i have tried every available resource on this, and other sites. i must have read over 1,000 posts in the past week to try and gather what the devil happened to my phone... If its any help, i did accidently delete the settings storage APK file, but a restore should have fixed that. i want to lock up the phone to send it in for repair but i cant gain s-off to flash a new radio with the phone in its current state. i know how to do all if these things but the phone wont let me.

Reformat the sd card to fat32 and flash an RUU file to put you back to stock.
Sent from my ADR6400L using xda premium

Does your computer recognize your device?
Sent from my ADR6400L using xda app-developers app

i am nearly pulling my hair out...
smtom said:
Reformat the sd card to fat32 and flash an RUU file to put you back to stock.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
any RUU downloads that would have been available on multiupload.com are disabled and redirects to to "the internet vs., holywood". besides, as i said, any attempt to flash any rom no matter what it is fails. Well, technically it FLASHES ok, but doesnt actually work. as far as i know, the phone has 2 bootloaders in any given android phone. There is the primary HTC Bootloader (Hboot) and a secondary ROM UI Bootloader. (Android Boot) i think what has happened is that this part has become corrupted and i wanted to know how to access this and reformat that. supposedly you cant because its partitioned, and formatting the partitions would fix my issue. problem is that i have done all of this. to answer the second reply, yes, i can get the phone to be recognized in any mode as long as its fastboot, or recovery. Fastboot.exe works, and adb recognizes it in recovery as being IN recovery mode. unfortunately, with my device still locked, i cannot flash a new bootloader, which might solve my problem. this is not like any issue currently on XDA so far as i read, so this is why i created a new thread.
I am sure the Moderators will agree that my problem seems to be unique. After reading what seems to be hundreds of forums, i cannot solve the issue. While technically i am a newbie here, i am no stranger to modding phones. i have been at it for over 4 years now. THIS problem is absolutely a first for me. At least before i could restore using CWM, but even that failed. i checked my MD5 Sum for CWM backup and it checked out.
If someone can provide me a link to an ORIGINAL, unmodded, RUU that shipped with the phone, (PRE OTA 2012) that ISNT that stupid file-factory corrupted crap, i would be extremely indebted to that person. last time i used File-factory, it took THREE hours and the download was corrupted according to CWM. it refused to flash the phone even though Chrome said it completely downloaded (Error: Bad - Installation Aborted). There was no MD5 SUM to compare with so thats also another problem. i absolutely need that info to properly flash the phone. All the other ROMS i downloaded like TSGB and Lightning Rom technically flashed fine after a full wipe, but refused to go past their own "Open Mobile" splash screen.
So you see, i am at a loss with this phone, as all i did was reboot after rooting it, and nothing i did could have possibly caused this kind of failure...

cyberkeeper1 said:
any RUU downloads that would have been available on multiupload.com are disabled and redirects to to "the internet vs., holywood". besides, as i said, any attempt to flash any rom no matter what it is fails. Well, technically it FLASHES ok, but doesnt actually work. as far as i know, the phone has 2 bootloaders in any given android phone. There is the primary HTC Bootloader (Hboot) and a secondary ROM UI Bootloader. (Android Boot) i think what has happened is that this part has become corrupted and i wanted to know how to access this and reformat that. supposedly you cant because its partitioned, and formatting the partitions would fix my issue. problem is that i have done all of this. to answer the second reply, yes, i can get the phone to be recognized in any mode as long as its fastboot, or recovery. Fastboot.exe works, and adb recognizes it in recovery as being IN recovery mode. unfortunately, with my device still locked, i cannot flash a new bootloader, which might solve my problem. this is not like any issue currently on XDA so far as i read, so this is why i created a new thread.
I am sure the Moderators will agree that my problem seems to be unique. After reading what seems to be hundreds of forums, i cannot solve the issue. While technically i am a newbie here, i am no stranger to modding phones. i have been at it for over 4 years now. THIS problem is absolutely a first for me. At least before i could restore using CWM, but even that failed. i checked my MD5 Sum for CWM backup and it checked out.
If someone can provide me a link to an ORIGINAL, unmodded, RUU that shipped with the phone, (PRE OTA 2012) that ISNT that stupid file-factory corrupted crap, i would be extremely indebted to that person. last time i used File-factory, it took THREE hours and the download was corrupted according to CWM. it refused to flash the phone even though Chrome said it completely downloaded (Error: Bad - Installation Aborted). There was no MD5 SUM to compare with so thats also another problem. i absolutely need that info to properly flash the phone. All the other ROMS i downloaded like TSGB and Lightning Rom technically flashed fine after a full wipe, but refused to go past their own "Open Mobile" splash screen.
So you see, i am at a loss with this phone, as all i did was reboot after rooting it, and nothing i did could have possibly caused this kind of failure...
Click to expand...
Click to collapse
https://dl.dropbox.com/u/61129367/Stock-ROM.zip
013CBDD3A9B28BC894631008FA2148E2

will this really work??!? lol
trter10 said:
https://dl.dropbox.com/u/61129367/Stock-ROM.zip
013CBDD3A9B28BC894631008FA2148E2
Click to expand...
Click to collapse
If this works, i will be forever grateful. and something that mere Custom ROMS wont do, is repair any boot issues and lock up my phone again right? i hope at least it fixes the issue.

new problem... i think...
cyberkeeper1 said:
If this works, i will be forever grateful. and something that mere Custom ROMS wont do, is repair any boot issues and lock up my phone again right? i hope at least it fixes the issue.
Click to expand...
Click to collapse
ok. so the download finished fine so far as i know, but now CWM says ITS bad too. i will try again but i cant seem to flash any stock rom no matter if its OTA or pre-OTA from CWM. is there a way to flash a rom from the PC via adb or something?

Ohh! They're not flashed through CWM. They're flashed through hboot. Just rename it to PG05IMG.zip and put on SD card and boot to hboot it will ask you to flash
Sent from my ADR6400L using Tapatalk 2

i will try that. previous hboot flashes always fail. it reads the archive, but never goes to "checking zip". it loads, checks, and then parses. i was successful with my evo shift earlier today, but that thing is ancient compared to my thunderbolt. With the Shift, i was able to gain root AND s-off with an old bootloader and i dont even need a new one.
i wanted to do the same with my bootloader in case another disaster hits because then i can flash whatever RUU i want with s-off. i will make sure the MD5 SUM matches before flashing. i forgot to do that anyhow.

Hboot flash failed. went through the motions of scanning it and it scanned the whole thing and then did nothing. it returned me to Boot Choices. Like Fastboot, recovery, etc... i tried twice. are you absolutely certain that is the shipping firmware that formats the entire phone, and not just updates it? i cant send it to verizon even though they know it was illegal to lock up my phone... Anyhow, i realy need this thing working and i have racked my brain enough to damage it already... lol. if it fails again i will try to redownload it. So far it loads and does NOT ask me to start the update. could be a version issue because it does not complain about anything else.

Have you tried following the instructions in the return to stock thread in the android development section stickies? This may help you.
Sent from my ADR6400L using xda app-developers app

lemew said:
Have you tried following the instructions in the return to stock thread in the android development section stickies? This may help you.
Sent from my ADR6400L using xda app-developers app
Click to expand...
Click to collapse
yes i have. i cannot do what it asks because it requires my phone to be functional to flash it using hboot. i need a signed copy of an older RUU. hboot doesnt do anything with it. its a valid copy, and i can see all the images and contents in windows and linux, but all i can get hboot to do is read it, then it doesnt ask me to update. i dont know what to do now.

I believe there is a ruu image without hoot download there.
Sent from my ADR6400L using xda app-developers app
---------- Post added at 06:39 PM ---------- Previous post was at 06:34 PM ----------
Try http://shipped-roms.com/index.php?category=android&model=Mecha
Sent from my ADR6400L using xda app-developers app

ok well i will literally try ALL of the signed images. i will see if hboot will update it.

If your hboot is flashed with revolutionary I believe you have to unlock it before anything thing else can be flashed over that. Hboot or emmc could be corrupted as well.
Sent from my ADR6400L using xda app-developers app

How i fixed my tbolt stuck at the white HTC screen
I had this exact same problem literally yesterday (stuck at HTC screen) with some different cwm symptoms. I'm guessing my cwm was corrupted because the phone would reboot after about 30 seconds being in cwm, preventing me from flashing any roms. oh, and my backup image was corrupted as well. awesome. Flashing other CWMs did not fix the CWM problem.
Your problem sounds similar in the fact the CWM won't flash properly. You're trying to fix it by trying to flash a rom in HBOOT that isn't configured to be flashed that way. for example, i put the skyraider rom (named properly) in the root folder and tried to flash with HBOOT. it scanned and parsed but didn't give me the option to flash.
What I did was go here and grab a stock like image:
androidforums.com/thunderbolt-all-things-root/418539-thunderbolt-root-unroot-thread.html
(won't let me make a link, i'm too new)
Go to the "Putting current stock firmware and s-on back onto the phone" section.
Download file 1 and flash it using HBOOT. I had to pull my sd card to get the file on there since cwm was crashing. Only flash that rom and nothing else. It flashed for me; if it doesn't flash for you then maybe your HBOOT is corrupted, and if so i don't know if you can fix it.
Once that flashes, reboot the phone and it should return to some level of functionality. You'll have S-off but no recovery or root tools installed. I ran revolutionary at this point, which recognized i already had S-off...then it offered to load CWM. This i did. in the meantime i deleted the unrooted image and put the image of the rom i wanted on the sd card. i then booted into recovery(it won't flash in HBOOT) and loaded that rom (skyraider zeus). That worked fine and the cwm didn't crash out.
I hope this works for you. I was getting ready to fire back up my OG droid before i did this.

mpcapps said:
I had this exact same problem literally yesterday (stuck at HTC screen) with some different cwm symptoms. I'm guessing my cwm was corrupted because the phone would reboot after about 30 seconds being in cwm, preventing me from flashing any roms. oh, and my backup image was corrupted as well. awesome. Flashing other CWMs did not fix the CWM problem.
Your problem sounds similar in the fact the CWM won't flash properly. You're trying to fix it by trying to flash a rom in HBOOT that isn't configured to be flashed that way. for example, i put the skyraider rom (named properly) in the root folder and tried to flash with HBOOT. it scanned and parsed but didn't give me the option to flash.
What I did was go here and grab a stock like image:
androidforums.com/thunderbolt-all-things-root/418539-thunderbolt-root-unroot-thread.html
(won't let me make a link, i'm too new)
Go to the "Putting current stock firmware and s-on back onto the phone" section.
Download file 1 and flash it using HBOOT. I had to pull my sd card to get the file on there since cwm was crashing. Only flash that rom and nothing else. It flashed for me; if it doesn't flash for you then maybe your HBOOT is corrupted, and if so i don't know if you can fix it.
Once that flashes, reboot the phone and it should return to some level of functionality. You'll have S-off but no recovery or root tools installed. I ran revolutionary at this point, which recognized i already had S-off...then it offered to load CWM. This i did. in the meantime i deleted the unrooted image and put the image of the rom i wanted on the sd card. i then booted into recovery(it won't flash in HBOOT) and loaded that rom (skyraider zeus). That worked fine and the cwm didn't crash out.
I hope this works for you. I was getting ready to fire back up my OG droid before i did this.
Click to expand...
Click to collapse
I have read that post you provided probably 100 times its not working for me. flashing a custom rom actually got me past the HTC white screen and into a splash screen loop (Open Mobile). Also, I havent even been able to use the REV tool because my phone is not recognized by it without it being fully functional. you have to be fully booted up for the REV tool to use adb and start the process. thats why i need a signed copy of an older ROM with hboot flashing capability so i can fully restore my phone. i am 100% sure its a corruption issue, but i am out of clues as to how to actually get it to flash over while being s-on. with the evo shift it worked perfectly. it only took me 20 minutes to root, s-off and flash a custom rom. this phone has been a thorn in my side ever since i accepted that STUPID FOTA... i regret not knowing before hand what that OTA was and what it prevented. Now i know, too little / too late.
without s-off, i cant unlock hboot to flash it, and the fastboot mw whatever command failed also because its locked tight.

lemew said:
If your hboot is flashed with revolutionary I believe you have to unlock it before anything thing else can be flashed over that. Hboot or emmc could be corrupted as well.
Sent from my ADR6400L using xda app-developers app
Click to expand...
Click to collapse
thats what i thought. is there a way to change out that eMMC, or remove it to format it manually? i mean based on the description, its technically external which implies removable.

Yes you can format emmc I do not know if this will solve your problem. You wipe abd format through adb but need to see if it is being mounted first.
Sent from my ADR6400L using xda app-developers app

lemew said:
Yes you can format emmc I do not know if this will solve your problem. You wipe abd format through adb but need to see if it is being mounted first.
Sent from my ADR6400L using xda app-developers app
Click to expand...
Click to collapse
too bad i cannot repartition it to allow for more RAM instead of app space. i dont care about app space because i have a 32gb card... lol. i just want that phone to be faster than what it is currently once i finally get it running.

[Q] Stuck on SGSIII Bootscreen

Before you post, "BLAKDSKF READ OTHER FORUMS BLUSDFLU!!!!!!!111!!!", please, PLEASE, read the whole post. I am not illiterate or a fool. I've spent the last few days researching similar posts, both on xda and other sites, and as far as I've found, this is the only post of this kind on the Verizon SGSIII forums, though there are some that are somewhat similar in the other SGSIII forums (though I think the root of the problem is different). If you can prove me wrong, please redirect.
The Long Story:
ok. SO. I was trying to root my SGSIII, unlock the bootloader, and install CM10. Simple enough, right? Not so. I got through the rooting tutorial at Link 1 relatively smoothly. For the record, I did the composite root and bootloader combo, and I installed CWM Touch Recovery, as per the guide. I also restored the Jellybean Bootchain. I think it was at this point I downloaded Titanium Backup (because forethought is not my forte) and backed up all my apps. I also made a backup with CWM Recovery, but there were errors. I forget the reason, but it aborted backup. I then tried to make a backup onto my external sd card, and some other errors popped up. Mainly that it couldn't find /android.secure (something along those lines) or /sd-ext (might have been something else. I'm going off memory) and skipped them. It still made the backup, so my illiterate, foolish self decided to roll with it and go ahead.
I then went ahead to Link 2, and with it being 2 AM, I stupidly decided to screw trying to figure out how to use Heimdall 1.4rc1 and continue to use ODIN for flashing. After all what's the difference, I thought. One flashing program is the same as another. I flashed the first two files. Well, in truth, I'm not sure if I flashed the first file. Since I just made a single folder for all the SGSIII Verizon flashing stuff, I had two files with similar names at the time. One from Link 1 and one from Link 2. The only difference was one was a boot chain, the other was a boot loader. Also, one ended with .md5 while the other ended with .tar. Sadly I tiredly picked one and flashed it. I think it was the .md5 one, but I'm not sure. Around this point, my micro sd card reader broke, so I decided to just use my other phone (Motorola Photon 4g running Joker's CM9) as a reader of sorts. I swapped them, used my phone to put the zip from Link 2 on it, and swapped them back. I say this because I'm not sure if that is what broke my md5sums or not (more on that in a sec).
Well, surprise, surprise, my phone got stuck on the animated, colorful "4G LTE" boot screen, except it was fully black, though the noise was playing. I think to myself, "No biggie. I'll just restore my previous backup," so I go back to restore it when I get the error 'md5sum mismatch'. I look up the problem, and after extensive, 3AM research (read: clicked the first link on google and blindly followed), I went with one guys advice, which was to create a blank nandroid.md5 file to force the restore. I figured, "Hey. This is pretty risky. I think I'll just restore the bootloader instead of the whole restore." Or at least that's what was going through my head as I went through with restoring the whole backup. Lo and behold, /system was corrupted, I assume, and it aborted restoring it. I reboot my phone only to find out that my phone gets stuck on the SGSIII boot logo. This is where I am now. I would go through with flashing a stock rom onto it to undo everything I've done, but ODIN won't recognize my phone anymore. I can still get into Download and Recovery Mode. All my backups are useless at the moment.
In Short:
I tried to root, unlock the bootloader, and flash CM10 on it
I messed up and ended up restoring a broken backup, md5sums be screwed.
Now ODIN won't recognize my phone and it's stuck at the SGSIII boot screen.
Is there any way to fix this or at least return it back to stock so I can start again?
If there's any other information you need, just ask. I'd be happy to give it. :laugh: This is my first post on these forums, so I'm not sure what information is standard. If you have any idea of what it might be, please drop a comment or something rather than just leaving. I'd like to know that people are actually reading this post.
And on an unrelated note, every time I try to flash with Heimdall, I get an error about there not being a certain .dll file, even though I downloaded the package from Link 2. Am I doing something wrong?
EDIT: I've already tried factory resetting and wiping the cache/dalvik cache. Most of my info is backed up anyway.
Links:
Link 1: http://forum.xda-developers.com/showthread.php?t=2046439
Link 2: http://wiki.cyanogenmod.org/w/Install_CM_for_d2vzw

What happens when you plug your phone into your PC? Have you tried deleting the drivers then reinstalling them either from Samsung or from the Kies program? You really have to try to mess up this phone and it seems like you definitely tried very hard in this regard.
Edit: Idk anything about Heimdall, I use Odin only so I can't help you there.

SlimSnoopOS said:
What happens when you plug your phone into your PC? Have you tried deleting the drivers then reinstalling them either from Samsung or from the Kies program? You really have to try to mess up this phone and it seems like you definitely tried very hard in this regard.
Edit: Idk anything about Heimdall, I use Odin only so I can't help you there.
Click to expand...
Click to collapse
I hadn't noticed before, but my phone doesn't even show a charge screen when plugged in, but that might just be the settings on the phone pre-root. I'm not sure because I left the phone on to see if it was just a time thing. The phone died and I have to recharge it.
After goofing around with the phone while on the charger for a while, I can get a charge screen to show up for a second. The standard "battery with a loading circle" type symbol for this type of error.
I just reinstalled the drivers. I'll let the phone charge for about 10 minutes or so, then test the phone.

dudeman9199 said:
I hadn't noticed before, but my phone doesn't even show a charge screen when plugged in, but that might just be the settings on the phone pre-root. I'm not sure because I left the phone on to see if it was just a time thing. The phone died and I have to recharge it.
After goofing around with the phone while on the charger for a while, I can get a charge screen to show up for a second. The standard "battery with a loading circle" type symbol for this type of error.
I just reinstalled the drivers. I'll let the phone charge for about 10 minutes or so, then test the phone.
Click to expand...
Click to collapse
Well if it died you should leave it on the charger longer than ten minutes if it is charging. If Odin recognizes it, your first step would be to try flashing a stock image.

SlimSnoopOS said:
Well if it died you should leave it on the charger longer than ten minutes if it is charging. If Odin recognizes it, your first step would be to try flashing a stock image.
Click to expand...
Click to collapse
Thanks. It would seem that it now recognizes the phone, from what I can tell. As soon as I get a stock rom, I'll flash it and post an update.

dudeman9199 said:
Thanks. It would seem that it now recognizes the phone, from what I can tell. As soon as I get a stock rom, I'll flash it and post an update.
Click to expand...
Click to collapse
Great! Use Droidstyle's guide or MrRobinson's thread for the proper images. Should be a good starting point.
Sent from my SCH-I535 using xda app-developers app

I just wanted to add that THIS is how you do a first post or any help needed post! Great details and is obvious you researchedyour problem as well.
The errors in cwm are actually normal. I think the corrupt backups are unrelated.
Sent from my SCH-I605 (AKA NOTE 2)

SlimSnoopOS said:
Great! Use Droidstyle's guide or MrRobinson's thread for the proper images. Should be a good starting point.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I've finally booted up into the setup wizard. I guess from here on I can re-root, unlock the bootloader, and *hopefully* get a working backup and eventually flash CM10.
I guess this means Problem Solved? Again, Thanks.
kintwofan said:
I just wanted to add that THIS is how you do a first post or any help needed post! Great details and is obvious you researchedyour problem as well.
The errors in cwm are actually normal. I think the corrupt backups are unrelated.
Sent from my SCH-I605 (AKA NOTE 2)
Click to expand...
Click to collapse
Thanks. I'm just gonna assume that the problems stemmed from swapping the sd card and leave it at that.

dudeman9199 said:
Thanks. I've finally booted up into the setup wizard. I guess from here on I can re-root, unlock the bootloader, and *hopefully* get a working backup and eventually flash CM10.
I guess this means Problem Solved? Again, Thanks.
Thanks. I'm just gonna assume that the problems stemmed from swapping the sd card and leave it at that.
Click to expand...
Click to collapse
Perfect! Which thread did you end up using btw?
Sent from my SCH-I535 using xda app-developers app

SlimSnoopOS said:
Perfect! Which thread did you end up using btw?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I used droidstyle's thread for getting the stock rom.

[Q] Where to Access Hasoon2000 S-Off Tool?

I've spent hours searching for how to S-Off my device. I've been running CM 9 and then 10, but it seems like my problem with 10.1 is S-on.
Most searches come to someone recommending Hasoon2000s S-Off tool, and linking to the original thread at: http://forum.xda-developers.com/showthread.php?t=1696373&highlight=s+off
The problem is that the link in that original thread to download the S-Off Tool is no longer there. I've looked through Hasoon2000s other downloads, and while there is the all-in-one toolkit 2.0, there doesn't seem to be a way to do S-Off in that kit.
I'll probably settle for JuopunutBear's solution, but since everywhere I go people are swearing by Hasoon2000s, (and I used the all-in-one toolkit with great success), does anyone have any new direction to track down a downloadable version of the S-Off tool, or a way to access it, or is JuopunutBear's all that is left for some reason? I haven't found any posts saying why Hasoon2000's has been pulled?
Thanks!

If I were you I would stay away from toolkits altogether. Not because they are bad, only because you learn absolutely nothing from using them and usually come bomb the threads when **** hits the fan.
The wire trick is a fun little task to handle though so everything should be okay that way.
Sent from my Nexus 4 using Tapatalk 2

Toolkit
ArachnydZ28 said:
I've spent hours searching for how to S-Off my device. I've been running CM 9 and then 10, but it seems like my problem with 10.1 is S-on.
Most searches come to someone recommending Hasoon2000s S-Off tool, and linking to the original thread at: http://forum.xda-developers.com/showthread.php?t=1696373&highlight=s+off
The problem is that the link in that original thread to download the S-Off Tool is no longer there. I've looked through Hasoon2000s other downloads, and while there is the all-in-one toolkit 2.0, there doesn't seem to be a way to do S-Off in that kit.
I'll probably settle for JuopunutBear's solution, but since everywhere I go people are swearing by Hasoon2000s, (and I used the all-in-one toolkit with great success), does anyone have any new direction to track down a downloadable version of the S-Off tool, or a way to access it, or is JuopunutBear's all that is left for some reason? I haven't found any posts saying why Hasoon2000's has been pulled?
Thanks!
Click to expand...
Click to collapse
His toolkit is still there, just browse around a bit... or go here... http://d-h.st/users/hasoon2000/?fld_id=2818#files

acwest said:
His toolkit is still there, just browse around a bit... or go here...
Click to expand...
Click to collapse
Thanks for your help I appreciate it- That was the same place linked to above.
Thats his toolkit 2.0 which I used to unlock my phone, but it doesn't give the phone S-Off (or atleast I couldnt find a way to do it in the toolkit)
His S-Off toolkit can't be found anymore on the otherhand, and I've searched in depth. I've been trying for at least 6-8 hours to get S-Off. Now I have a semi-bricked phone. Every path I go down is a dead end and its driving me nuts!
I was going to try the wire trick, but it requires stock rom. I had backed up the stock rom but it won't load. I downloaded 2 PD15IMG.zip files but neither of them will load, recovery says "Bad" when I try to run the .zip files. Did a little research. I think I need to do it via fastboot for the PD15IMG.zip files. Trying to figure that out now. Warnings seem pretty dire about trying to do it on a non-stock rom
This is getting above my head but I'm working my best to figure it out. Worst comes to worse I'll just have to order a new phone! I hate to be the novice that ends up being a PITA, as I've dealt with them plenty on the car forums I'm active on. I'd like to apologize up front for being "that guy".

Whats your situation now, do you have a recovery? What does it all say on your bootloader screen? Write that all down here
Sent from my Nexus 7 using xda premium

demkantor said:
Whats your situation now, do you have a recovery? What does it all say on your bootloader screen? Write that all down here
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
unlocked
Doubleshot PVT Ship S-On RL
Hboot- 1.45.0013
Microp-0353
eMMC-Boot
Nov 21 2011, 20:20:47
I do have recovery and hboot. Stock backup won't load though even though the file is there in recovery.
Thanks!

And what if you were to try and flash another rom, like miktouch, through recovery?
Sent from my MyTouch 4G Slide using xda premium

demkantor said:
And what if you were to try and flash another rom, like miktouch, through recovery?
Sent from my MyTouch 4G Slide using xda premium
Click to expand...
Click to collapse
I was able to reflash a version of CM10 I was using for a while and that works, but I can't find a stock one that will work. I've tried multiple, and they all give me "bad" error and don't finish the install.
I was going to try a different version of CM10, 10.1, or go to a stable release of 9. If none of those worked, I'd be happier with stock. None of the ones I've tried will work, but I'm assuming thats because I'm S-On, but since I can't find hasoon2000s S-Off tool everyone was raving about, and the wire trick requires stock ROM based on what the directions say, I find myself in a pickle.
The CM10 version I have can't do some basic things I need for work- like sync with my bluetooth in the car or not randomly freeze up during the day without me knowing it sending all my calls to voicemail. I tried versions of the others that other people are using (like silverL's 10.1 and the CM-listed stable CM9) and neither would load.
Do I have a different issue? AKA are other people with S-On able to load those Roms? I can try miktouch too.
---
Also trying to load via fastboot and I'm getting this error:
"Whoops: didn't find expected signature
read_central_directory_entry_failed
error: failed to access zipdata in [Whole bunch of non-english characters taking up a few lines]"
----
Update: Just to clarify, when I try to install a stock rom it gives me "Can't open [filename] (bad)
However, when I try to install the CM's, it installs fine and says "Install from sdcard complete" they just won't load when I restart my phone, except for the original version of CM10. (for example, in all the 10.1s I've tried I get "Unfortunately, the process com.android.phone has stopped" but the intro page will load. I figured that came down to an S-On issue when I tried to troubleshoot.

Any rom that is based off stock (like miktouch) should work to do the wire trick. I would check md5sums of the roms that won't flash to make sure they aren't corrupt at all. Also some say the latest twrp (and maybe other recoveries) won't flash some roms, so may need to change that as well
Sent from my MyTouch 4G Slide using xda premium

demkantor said:
Any rom that is based off stock (like miktouch) should work to do the wire trick. I would check md5sums of the roms that won't flash to make sure they aren't corrupt at all. Also some say the latest twrp (and maybe other recoveries) won't flash some roms, so may need to change that as well
Sent from my MyTouch 4G Slide using xda premium
Click to expand...
Click to collapse
Great, thanks!
I'll give miktouch a shot to see if I can use it for the wire trick. I'll let you know if it works.

ArachnydZ28 said:
Great, thanks!
I'll give miktouch a shot to see if I can use it for the wire trick. I'll let you know if it works.
Click to expand...
Click to collapse
negative.
miktouch would go through the install process, and end at the Tmobile mytouch 4g slide screen forever. I know on one install it took a long time to "load" the first time so I left it on this screen for about 15 minutes to no avail. Let me know if there is any chance of it taking longer than that. Reinstalls were the same story.
I got CM9.1 to install by installing it twice on top of itself (not sure why that fixes it) but it was a tiny bit buggy.
Is there any chance this could be bootloader related or recovery related? I can try to reload those too. grrr...

Its possible but if your bootloader can boot up one ROM it should be able to boot another. For this phone the only reason I have seen to change bootloaders is to unlock all the fastboot options. Flashing a new bootloader would reformat your partitions which may be the cause of your issue. Make sure you do a full wipe from recovery or fastboot -w or use a superwipe script, hell I tend to do all three between flashes but I'm kinda ocd when it comes to this, I hate debugging issues caused by residual effect from old data left after a dirty flash
But it may be worth it to flash a new recovery, not sure what you are using now but sometimes one will work when another doesn't, this would probably be my next step
Sent from my Nexus 7 using xda premium

demkantor said:
Its possible but if your bootloader can boot up one ROM it should be able to boot another. For this phone the only reason I have seen to change bootloaders is to unlock all the fastboot options. Flashing a new bootloader would reformat your partitions which may be the cause of your issue. Make sure you do a full wipe from recovery or fastboot -w or use a superwipe script, hell I tend to do all three between flashes but I'm kinda ocd when it comes to this, I hate debugging issues caused by residual effect from old data left after a dirty flash
But it may be worth it to flash a new recovery, not sure what you are using now but sometimes one will work when another doesn't, this would probably be my next step
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I'm running CWM 5.5.0.4
I'll try to reload it or another version (I'm seeing some issues people have with 5504)
Thanks!

ArachnydZ28 said:
I'm running CWM 5.5.0.4
I'll try to reload it or another version (I'm seeing some issues people have with 5504)
Thanks!
Click to expand...
Click to collapse
You should try CWM 5.0.2.7. Also, since you are S-On you should extract the boot.img from Miktouch and flash it from fastboot, separately from the ROM. Since you have been on an ICS/Jellybean rom, I have to believe your original boot.img was replaced at some point. This is the only way to get back the Gingerbread boot.img. I am not savvy enough to know if this file is the bootloader or the kernel, but this process should get you back to stock-enough to do the wire trick.
Sent from my SGH-T699 using xda app-developers app

It's the kernel.....the boot.img file, I mean. The bootloader is that mostly white screen you see with "Hboot" at the top that will have "S-On" or "S-Off" after the word Radio. Good response.:good:

ArachnydZ28 said:
Thanks for your help I appreciate it- That was the same place linked to above.
Thats his toolkit 2.0 which I used to unlock my phone, but it doesn't give the phone S-Off (or atleast I couldnt find a way to do it in the toolkit)
His S-Off toolkit can't be found anymore on the otherhand, and I've searched in depth. I've been trying for at least 6-8 hours to get S-Off. Now I have a semi-bricked phone. Every path I go down is a dead end and its driving me nuts!
I was going to try the wire trick, but it requires stock rom. I had backed up the stock rom but it won't load. I downloaded 2 PD15IMG.zip files but neither of them will load, recovery says "Bad" when I try to run the .zip files. Did a little research. I think I need to do it via fastboot for the PD15IMG.zip files. Trying to figure that out now. Warnings seem pretty dire about trying to do it on a non-stock rom
This is getting above my head but I'm working my best to figure it out. Worst comes to worse I'll just have to order a new phone! I hate to be the novice that ends up being a PITA, as I've dealt with them plenty on the car forums I'm active on. I'd like to apologize up front for being "that guy".
Click to expand...
Click to collapse
Load the pd15img.zip on your sd card and boot to your bootloader. It should detect the file on your card and ask if you want to flash it. Just follow the directiins it gives you
Edit: actually should be pd59img not 15
Sent from my SGH-T889 using Tapatalk 2

[Q] Unauthorized software message ONLY when booting into recovery

This is my first post ever here so I'm sorry if I'm breaking some rule (read the forum rules so I don't think I am) or if it's in the wrong subforum (although this does seem like a help & troubleshooting topic to me).
A little backstory is probably necessary.
I rooted my s3 (latest OTA update) via CASUAL (thread: http://forum.xda-developers.com/showthread.php?t=2332825) and it seemed like it worked for the most part, although it didn't boot into twrp like it should have and instead booted into normal recovery. I just assumed that it was because something went wrong with the recovery installation so I just thought "ok whatever."
Root access was there, and I assumed the bootloader was unlocked since I read several places that when it's unlocked, the initial samsung boot logo appears for about a second as opposed to several seconds when it's locked. So I just assumed all i needed was to reinstall a custom recovery and I was golden.
Installed ROM Manager, flashed CWM through the app, and rebooted the phone, and as it was booting into recovery I was greeted with the infamous "NO CUSTOM SOFTWARE ALLOWED PLEASE ALERT PAPA VERIZON IMMEDIATELY" warning.
I was about to flash back to stock through odin (which i regretted since I've had bad experiences in the past using it) when I figured out I could get the device to boot normally by clicking cancel in the download mode confirmation window. I guess it kept trying to reboot to recovery after every unsuccessful boot, which made it seem like it was softbricked to me.
Phone is operating normally now, and it should after another reboot as long as it doesn't try to go into recovery again (though I'm kind of afraid to even do that).
Is there any way without Odin I can fix my recovery and/or bootloader? I'm not sure what the problem is here and I don't think this sort of thing is a common searchable issue. Google/XDA search didn't bring up anything that sounded like someone had 100% the same problem I do.
Also on a semi-related note, does EZ-Unlock still work with this latest OTA? And if my bootloader is potentially unlocked already, would unlocking it again through EZ-Unlock break something?

Sleix said:
This is my first post ever here so I'm sorry if I'm breaking some rule (read the forum rules so I don't think I am) or if it's in the wrong subforum (although this does seem like a help & troubleshooting topic to me).
A little backstory is probably necessary.
I rooted my s3 (latest OTA update) via CASUAL (thread: http://forum.xda-developers.com/showthread.php?t=2332825) and it seemed like it worked for the most part, although it didn't boot into twrp like it should have and instead booted into normal recovery. I just assumed that it was because something went wrong with the recovery installation so I just thought "ok whatever."
Root access was there, and I assumed the bootloader was unlocked since I read several places that when it's unlocked, the initial samsung boot logo appears for about a second as opposed to several seconds when it's locked. So I just assumed all i needed was to reinstall a custom recovery and I was golden.
Installed ROM Manager, flashed CWM through the app, and rebooted the phone, and as it was booting into recovery I was greeted with the infamous "NO CUSTOM SOFTWARE ALLOWED PLEASE ALERT PAPA VERIZON IMMEDIATELY" warning.
I was about to flash back to stock through odin (which i regretted since I've had bad experiences in the past using it) when I figured out I could get the device to boot normally by clicking cancel in the download mode confirmation window, rebooting the phone normally. I guess it kept trying to reboot to recovery after every unsuccessful boot, which made it seem like it was softbricked to me.
Phone is operating normally now, and it should after another reboot as long as it doesn't try to go into recovery again (though I'm kind of afraid to even do that).
Is there any way without Odin I can fix my recovery and/or bootloader? I'm not sure what the problem is here and I don't think this sort of thing is a common searchable issue. Google/XDA search didn't bring up anything that sounded like someone had 100% the same problem I do.
Also on a semi-related note, does EZ-Unlock still work with this latest OTA? And if my bootloader is potentially unlocked already, would unlocking it again through EZ-Unlock break something?
Click to expand...
Click to collapse
That is really weird...
I was reading it and was going to suggest easy unlock v1.2,you will not break anything using that app.
If that still doesn't work, try to flash TWRP through goo manager and see if it somehow fixes your recovery issue.
It sounds to me that your Bootloader is unlocked though... But give it a shot.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
That is really weird...
I was reading it and was going to suggest easy unlock v1.2,you will not break anything using that app.
If that still doesn't work, try to flash TWRP through goo manager and see if it somehow fixes your recovery issue.
It sounds to me that your Bootloader is unlocked though... But give it a shot.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the quick response.
That was going to be what I tried first, that's why I asked about it.
I'll wait for a little more input before trying it though if it's really that weird of an issue.

Sleix said:
Thanks for the quick response.
That was going to be what I tried first, that's why I asked about it.
I'll wait for a little more input before trying it though if it's really that weird of an issue.
Click to expand...
Click to collapse
It's just strange that you only get that message with recovery mode, it normally will not do that.
At the very worst, an odin back to stock is pretty easy. Just follow the same process, but use ez recovery instead of rom manager. It was made specifically for our phone, and never gives me any issues when installing recoveries.
I still think if you use ez unlock it'll probably fix the issue completely. Let me know if you figure it out. Good luck.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
It's just strange that you only get that message with recovery mode, it normally will not do that.
At the very worst, an odin back to stock is pretty easy. Just follow the same process, but use ez recovery instead of rom manager. It was made specifically for our phone, and never gives me any issues when installing recoveries.
I still think if you use ez unlock it'll probably fix the issue completely. Let me know if you figure it out. Good luck.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks. Used ez unlock to unlock the bootloader. It was previously labeled as "Unknown".
Downloading ez recovery right now. Do you think I need to reinstall my recovery just to make sure?

Sleix said:
Thanks. Used ez unlock to unlock the bootloader. It was previously labeled as "Unknown".
Downloading ez recovery right now. Do you think I need to reinstall my recovery just to make sure?
Click to expand...
Click to collapse
No, but it wouldn't hurt.
Use 1.2 of ez unlock, versions 1.3 and 1.4 will give an unknown message. There have also been lots of reports saying that version 1.4 did not unlock their bootloader.
These are the most recent recoveries, download and flash in the ez recovery app if you need to.
http://forum.xda-developers.com/showthread.php?t=2096735
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
No, but it wouldn't hurt.
Use 1.2, versions 1.3 and 1.4 will give an unknown message. There have also been lots of reports saying that version 1.4 did not unlock their bootloader.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Reflashed CMW (I used the version provided by ez recovery, please let me know if that's a problem) just in case and it worked like a charm. Thanks!
Also I did use version 1.2. I actually had it sitting on my phone's home screen before I made this thread.
It still showed up as "Unknown". Maybe that indicated the problem?
Regardless, this problem seems to have been fixed. Now it's time to do some research on verizon s3 roms.
Also another semi-unrelated note, it seems I tripped a flash counter somewhere along the line.
Is Triangle Away one of those apps that is just "open and press a button"? I've been kind of wary of using it since it has that huge warning in app's description.

Sleix said:
Reflashed CMW (I used the version provided by ez recovery, please let me know if that's a problem) just in case and it worked like a charm. Thanks!
Also I did use version 1.2. I actually had it sitting on my phone's home screen before I made this thread.
It still showed up as "Unknown". Maybe that indicated the problem?
Regardless, this problem seems to have been fixed. Now it's time to do some research on verizon s3 roms.
Also another semi-unrelated note, it seems I tripped a flash counter somewhere along the line.
Is Triangle Away one of those apps that is just "open and press a button"? I've been kind of wary of using it since it has that huge warning in app's description.
Click to expand...
Click to collapse
Glad to hear it's working! Strange issue but looks like you ironed it out.
Triangle away is the app you would use. You tripped it using the rooting method injecting your recovery through odin, it's a big warning because it messes with your boot partition. If it fails and borks your boot partition, then you'd have to jtag your phone to fix it.
I personally wouldn't use it unless I was turning in my phone for service or replacement. But the app has great reviews and not many reports of bricks.
Before flashing anything, use a newer recovery image. The one provided by ez recovery is from last year, the newer versions are better written to prevent possible errors that come up with jellybean.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
Glad to hear it's working! Strange issue but looks like you ironed it out.
Triangle away is the app you would use. You tripped it using the rooting method injecting your recovery through odin, it's a big warning because it messes with your boot partition. If it fails and borks your boot partition, then you'd have to jtag your phone to fix it.
I personally wouldn't use it unless I was turning in my phone for service or replacement. But the app has great reviews and not many reports of bricks.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I'll keep that in mind, thanks again!
Any roms you'd recommend?

Sleix said:
I'll keep that in mind, thanks again!
Any roms you'd recommend?
Click to expand...
Click to collapse
Read through the op's and decide based on what you're looking for.
Mostly stock, very stable:
Clean rom, bonestock, darthstalker x1.
More modified stocks, more buggy but can run very well:
Hyperdrive, axis, goodness, moar
AOSP isn't my cup of tea, but they are fast and lag free.
Make sure you update your recovery image first, I edited my last post but think you missed it.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
Read through the op's and decide based on what you're looking for.
Mostly stock, very stable:
Clean rom, bonestock, darthstalker x1.
More modified stocks, more buggy but can run very well:
Hyperdrive, axis, goodness, moar
AOSP isn't my cup of tea, but they are fast and lag free.
Make sure you update your recovery image first, I edited my last post but think you missed it.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Will do. Thanks for pointing that edit out.