Database Info

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.

bricked one x

So earlier i attempted to do the 2.2 root.
i managed to get as far as rooting, installing superuser and CWM
now, the problem is when i went to flash the rom, i tried to run the super wipe, but was getting errors about the sdcard not being able to be mounted. and the wipe was not performed/failed/aborted etc
i tried to run flash the rom still, it loaded, but still gave an error at the end and did not work.
reboot the phone, and i get the HTS quietly brilliant screen with red text that says"this build is for development purposes only...." and from here it does nothing but constantly reboot to this screen.
i am able to get to the bootloader screen, and fastboot works.
ive tried factory resetting the phone, as well as using the CWM recovery. i am unable to do any. as the CWM cannot write to e:\sd card
its not mounted, and i cannot mount it, when i try to reformat the sd card, it says it is unmounted.
mount usb storage was not working either, and said files were missing.
i read on other threads about needing the sd card reformatted, but the one x has an internal card.
please help
i feel like it can be fixed, but im really worried my phone is bricked
eta: i tried to revert to the stock ruu, but i think i should have read it more clearly.
so i guess i flashed the ruu that was NOT 2.2
now my CWM is gone, and i can only get onto the bootloader and fast boot
under fastboot devices my device's serial does show up
ETA: i reflashed with twrp, managed to wipe my sdcard, and am now able to mount.
from here my phone is still not able to boot up.
i can attempt to run the super wipe, but am still getting an error
"E:error in /sdcard"

chinaman_chong said:
So earlier i attempted to do the 2.2 root.
i managed to get as far as rooting, installing superuser and CWM
now, the problem is when i went to flash the rom, i tried to run the super wipe, but was getting errors about the sdcard not being able to be mounted. and the wipe was not performed/failed/aborted etc
i tried to run flash the rom still, it loaded, but still gave an error at the end and did not work.
reboot the phone, and i get the HTS quietly brilliant screen with red text that says"this build is for development purposes only...." and from here it does nothing but constantly reboot to this screen.
i am able to get to the bootloader screen, and fastboot works.
ive tried factory resetting the phone, as well as using the CWM recovery. i am unable to do any. as the CWM cannot write to e:\sd card
its not mounted, and i cannot mount it, when i try to reformat the sd card, it says it is unmounted.
mount usb storage was not working either, and said files were missing.
i read on other threads about needing the sd card reformatted, but the one x has an internal card.
please help
i feel like it can be fixed, but im really worried my phone is bricked
eta: i tried to revert to the stock ruu, but i think i should have read it more clearly.
so i guess i flashed the ruu that was NOT 2.2
now my CWM is gone, and i can only get onto the bootloader and fast boot
under fastboot devices my device's serial does show up
ETA: i reflashed with twrp, managed to wipe my sdcard, and am now able to mount.
from here my phone is still not able to boot up.
i can attempt to run the super wipe, but am still getting an error
"E:error in /sdcard"
Click to expand...
Click to collapse
Ruu back to stock 2.20
Edit.
If you can mount then connect to computer and try reinstalling boot image and the rom you were trying to install. Or adb
swagged out rooted jelly bean HOX

tae_254 said:
Ruu back to stock 2.20
Edit.
If you can mount then connect to computer and try reinstalling boot image and the rom you were trying to install. Or adb
swagged out rooted jelly bean HOX
Click to expand...
Click to collapse
so from mounting
im trying to install the Android Revolution HD 9.7.2 Ice Cream Sandwich
it allows me to choose settings, and such and start install.
after starting install, it goes through the files and such, but when it gets to /system/lib/ it just closes on itself, and goes back to twrp screen and recovery home. the rom never finishes installing. right now im gonna re-download the rom and see if that works.
if i cannot install the custom rom, how can i go back to stock exactly?
do i need to find the stock ruu?

fixed it.
turns out im stupid and was using a rom not compatible with this phone.
i flashed http://forum.xda-developers.com/showthread.php?t=1907324 so far, and it seems to be working
however, i prefer something closer to stock. can anyone suggest a rom?

hopefully you aren't using cwm anymore and flashed twrp for the evita.

chinaman_chong said:
fixed it.
turns out im stupid and was using a rom not compatible with this phone.
i flashed http://forum.xda-developers.com/showthread.php?t=1907324 so far, and it seems to be working
however, i prefer something closer to stock. can anyone suggest a rom?
Click to expand...
Click to collapse
I knew what you did the second I saw the words "Android Revolution", as that ROM does not exist for our phone.
Stick to the ROMs listed in our section of the forum (AT&T, Rogers HTC One X, Telstra One XL) in "Android Development" and "Original Android Devepment" here: http://forum.xda-developers.com/forumdisplay.php?f=1538
Or just use my handy index, which is an organized list of all our ROMs and mods:
http://forum.xda-developers.com/showthread.php?t=1671237
And apparently, you missed these:
http://forum.xda-developers.com/showthread.php?t=1813839
http://forum.xda-developers.com/showthread.php?t=1944712
http://forum.xda-developers.com/showthread.php?t=1952942

CleanROM on Viper XL
---------- Post added at 12:14 PM ---------- Previous post was at 12:13 PM ----------
chinaman_chong said:
however, i prefer something closer to stock. can anyone suggest a rom?
Click to expand...
Click to collapse
CleanROM or Viper XL

redpoint73 said:
I knew what you did the second I saw the words "Android Revolution", as that ROM does not exist for our phone.
Stick to the ROMs listed in our section of the forum (AT&T, Rogers HTC One X, Telstra One XL) in "Android Development" and "Original Android Devepment" here: http://forum.xda-developers.com/forumdisplay.php?f=1538
Or just use my handy index, which is an organized list of all our ROMs and mods:
http://forum.xda-developers.com/showthread.php?t=1671237
And apparently, you missed these:
http://forum.xda-developers.com/showthread.php?t=1813839
http://forum.xda-developers.com/showthread.php?t=1944712
http://forum.xda-developers.com/showthread.php?t=1952942
Click to expand...
Click to collapse
OMFG ..how did you get all these results, did you by any chance use that esoteric SEARCH functionality ?
Now all i have to do is read ?? Could you also pre-chew my food please ? :silly:

Crappyvate said:
OMFG ..how did you get all these results, did you by any chance use that esoteric SEARCH functionality ?
Now all i have to do is read ?? Could you also pre-chew my food please ? :silly:
Click to expand...
Click to collapse
I didn't even have to use the search function. 2 are near the top of General. The remaining has slipped past the first page, but its still pretty high up there.
People who flash a ROM for the international version are simply neglecting to do any basic reading and learning before flashing things willy-nilly, that's my point.

thanks for the help guys. i flashed viper xl yesterday night right after, loving it thus far. i was just so used to the sense keyboard already, and hated the cramped jb keyboard, and this rom has simple little tweaks
i did read, but i guess not thoroughly enough. in hindsight, i wasnt aware that the one x was different than the xl, its fairly easy to miss that the other roms are not compatible with this phone. and is completely different alltogether.
if i had known that, i wouldnt have flashed cwm, and would not have need to post a help thread. all "solutions" i attempted on my own were based off readings of the hox, rather than the evita, once again causing more problems. it was easily enough fixed once i figured that bit of information out.
i am a noob, but this phone is not my first time rooting, so with my prior knowledge i felt i was more than ready to tackle this rom flashing, im sure plenty of others will make the same mistake as i did.
the other phones ive rooted and flashed had their one model of phone only, so all the roms available were compatible.
im just glad my phone is not bricked, and i now have root access

chinaman_chong said:
So earlier i attempted to do the 2.2 root.
i managed to get as far as rooting, installing superuser and CWM
now, the problem is when i went to flash the rom, i tried to run the super wipe, but was getting errors about the sdcard not being able to be mounted. and the wipe was not performed/failed/aborted etc
i tried to run flash the rom still, it loaded, but still gave an error at the end and did not work.
reboot the phone, and i get the HTS quietly brilliant screen with red text that says"this build is for development purposes only...." and from here it does nothing but constantly reboot to this screen.
i am able to get to the bootloader screen, and fastboot works.
ive tried factory resetting the phone, as well as using the CWM recovery. i am unable to do any. as the CWM cannot write to e:\sd card
its not mounted, and i cannot mount it, when i try to reformat the sd card, it says it is unmounted.
mount usb storage was not working either, and said files were missing.
i read on other threads about needing the sd card reformatted, but the one x has an internal card.
please help
i feel like it can be fixed, but im really worried my phone is bricked
eta: i tried to revert to the stock ruu, but i think i should have read it more clearly.
so i guess i flashed the ruu that was NOT 2.2
now my CWM is gone, and i can only get onto the bootloader and fast boot
under fastboot devices my device's serial does show up
ETA: i reflashed with twrp, managed to wipe my sdcard, and am now able to mount.
from here my phone is still not able to boot up.
i can attempt to run the super wipe, but am still getting an error
"E:error in /sdcard"
Click to expand...
Click to collapse
Do not use CMW it causes lot of problems(not recommended for our device) . Use TWRP recovery instead
Sent from my HTC One XL using xda premium

redpoint73 said:
I knew what you did the second I saw the words "Android Revolution", as that ROM does not exist for our phone.
Click to expand...
Click to collapse
That and Superwipe. I remember that zip from other phones I used that rom on.
Sent from my HTC One XL

Dang you guys are slipping through the cracks in the bricks lol, excuse my pun. You are lucky. You're the only person I've seen that has flashed android revolution and not overwrite boot and having a beautiful brick lol.
Subscribe to the OneXL forums and stay here till you recognize your community!
Sent from my HTC One XL using xda app-developers app

can't brick from it after 2.20

DvineLord said:
can't brick from it after 2.20
Click to expand...
Click to collapse
Good thing eh
Sent from my HTC One XL using xda app-developers app

InflatedTitan said:
Dang you guys are slipping through the cracks in the bricks lol, excuse my pun. You are lucky. You're the only person I've seen that has flashed android revolution and not overwrite boot and having a beautiful brick lol.
Click to expand...
Click to collapse
From what others are saying, the newer hboot that came with 2.20 is write protected. Hboot can't be overwritten by flashing a ROM for the international One X. ROM just fails to flash, and you get a recoverable condition like this one, as opposed to hard bricks on the older hboot.

Yea, at least there's one good thing that came with the dreaded update
Sent from my HTC One XL using xda app-developers app

How do i ruu back to stock 2.20? I unlocked my device. Tried flashing the boot.img but after I couldnt mount my sdcard to flash the rest of the ROM. I can enter recovery and bootloader though. Really need some help

h1m said:
How do i ruu back to stock 2.20? I unlocked my device. Tried flashing the boot.img but after I couldnt mount my sdcard to flash the rest of the ROM. I can enter recovery and bootloader though. Really need some help
Click to expand...
Click to collapse
If you want to ruu grab the ruu file...lock your bootloader from within fastboot and run the ruu

omario8484 said:
If you want to ruu grab the ruu file...lock your bootloader from within fastboot and run the ruu
Click to expand...
Click to collapse
Where do i get the ruu file? I can't mount my sdcard

[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] Boot Looping - ANY custom rom

I have unlocked my TF700. I was able to root the stock rom with Kangaroot with no problem. I then tried to load a custom rom, and got stuck in boot loop. I was trying Stable CM10, then I went on to try 5 other nightlies in reverse (from current as of yesterday) order. All have the same problem. I have cleared Cache Partition and Davlik Cache multiple times. I can flash to the stock rom from ASUS site and get through boot with no problem. Each time I do that I need to re-flash CWM. I've since also tried Clean and LiquidSmooth. Nothing gets past boot animation. I've let all attempts sit there for at least 10-15 minutes just to be sure it wasn't just slow.
Any idea where to start in troubleshooting?
CWM Log shows:
Code:
ClockworkMod Recovery v6.0.2.7
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc.ueventd=running
init.svc.recovery=running
init.svc.mishelp=restarting
init.svc.adbd=running
service.adb.root=1
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
I:Can't format unknown volume: /external_sd
I:Can't partition non-vfat: datamedia
I tried without the microsd card in as well.

I'd make sure the latest 4.1 is installed.
Push TWRP thru ADB
Download A ROM zip to the external card
Boot to custom recovery
Then try installing a ROM from TWRP after backing up
Hope this might help you.

Thats OK said:
I'd make sure the latest 4.1 is installed.
Push TWRP thru ADB
Download A ROM zip to the external card
Boot to custom recovery
Then try installing a ROM from TWRP after backing up
Hope this might help you.
Click to expand...
Click to collapse
Well after trying CM10 Stable, 2 nightlies, Liquid Smooth, all through TWRP (which is way better than CWM in my book now), I was able to get past boot with CleanRom. Unfortunately it doesn't look like wifi works, nor bluetooth, or full screen resolution Maybe because the rom is meant for Nexus 10. Oddly it shows the liquidsmooth loader and options too.
[Edit] Wifi and bluetooth started working after another reboot. After that I was able to switch over to CM10 Nightly. Still no full resolution, but better than broken. Yay for TWRP.

You've installed Cleanrom for the Nexus 10 on your TF700? I'm surprised that it boots at all. Why don't you install the one for the Tf700?

I read this yesterday and felt dumb for not knowing what Kangaroot was. :S
@OP: you've taken an immense risk, and are darned lucky to get out of this with only a malfunctioning device and not a brick. Next time, read up a bit.
Sent from a comfortable chair from the outer ring of Purgatory. The red guy asked me to say 'hi'.

sbdags said:
You've installed Cleanrom for the Nexus 10 on your TF700? I'm surprised that it boots at all. Why don't you install the one for the Tf700?
Click to expand...
Click to collapse
I thought I was downloading the TF700 version. When it loaded, however, it said Nexus10. I've not been able to find one that is for the TF700 on Scott's site. I really like how it guides the user through install options, which more Roms had this. Helps us noobs.

ngMondo said:
I thought I was downloading the TF700 version. When it loaded, however, it said Nexus10. I've not been able to find one that is for the TF700 on Scott's site. I really like how it guides the user through install options, which more Roms had this. Helps us noobs.
Click to expand...
Click to collapse
OK, here is the correct Cleanrom for tf700 http://forum.xda-developers.com/showthread.php?t=2049274

MartyHulskemper said:
@OP: you've taken an immense risk, and are darned lucky to get out of this with only a malfunctioning device and not a brick. Next time, read up a bit.
Click to expand...
Click to collapse
So that I can avoid the risk later, what was it that I did wrong as you see? Or are you referring to the Nexus10 build of CleanRom? If so, its the only one I found, and the page I downloaded from said it was TF700.

Scott no longer makes or supports CleanROM for the TF700 (or Nexus 7 for that matter), I do He has removed it from his site.
I don't know how you did it but somehow you got confused and downloaded and flashed CleanROM for the Nexus 10.
You have now given me an idea, seeing as you guinea pigged it and it booted
SO an indirect thank you!!

Wow my friend,
You really did dodge a bullet there!
Looks like the Nexus drivers and framework must be close.
Interesting...

sbdags said:
Scott no longer makes or supports CleanROM for the TF700 (or Nexus 7 for that matter), I do He has removed it from his site.
I don't know how you did it but somehow you got confused and downloaded and flashed CleanROM for the Nexus 10.
You have now given me an idea, seeing as you guinea pigged it and it booted
SO an indirect thank you!!
Click to expand...
Click to collapse
So, oddly enough the "correct" version of CleanRom 3.2.2 doesn't boot, but the Nexus 10 one did. Tried wipe and everything right before and after, 3 times... no dice.

ngMondo said:
So, oddly enough the "correct" version of CleanRom 3.2.2 doesn't boot, but the Nexus 10 one did. Tried wipe and everything right before and after, 3 times... no dice.
Click to expand...
Click to collapse
Well I suspect you have also managed to flash the Google Nexus 10 bootloader or some part of a kernel. I have no idea how to help you, but what is certain is you currently can't use any roms designed for the TF700 .....

sbdags said:
Well I suspect you have also managed to flash the Google Nexus 10 bootloader or some part of a kernel. I have no idea how to help you, but what is certain is you currently can't use any roms designed for the TF700 .....
Click to expand...
Click to collapse
Well, I think I've redone bootloader and kernel multiple times by now. I was actually about to ask you if there was a specific kernel option I should choose in the CleanRom installer, but it looks like I'm up and running again. I tried the DeOdexed version about 4 times with no luck. The Odexed version worked the first time through. So far everything looks to be working (wifi, bluetooth, dock, sd, gapps, etc).

Buhohitr had mentioned in another thread that TWRP has an option to wipe the eMMC (internal card erase) without hurting the recovery partition.
Last resort however if the system is a mess.
If all is at least running a new version of CROMi I'd just sit tight.
I am kind of curious to see if you have any more problems with user incurred shutdown and reboots.

ngMondo said:
So that I can avoid the risk later, what was it that I did wrong as you see? Or are you referring to the Nexus10 build of CleanRom? If so, its the only one I found, and the page I downloaded from said it was TF700.
Click to expand...
Click to collapse
Yeah, I was referring to flashing the N10 build. You were lucky, my friend. The TF700 makes one expensive paperweight. My remark seems to have gotten your feathers ruffled a bit: I did not mean it that way. Sorry if I offended you in any way.
sbdags said:
You have now given me an idea, seeing as you guinea pigged it and it booted
SO an indirect thank you!!
Click to expand...
Click to collapse
Opportunism FTW!

[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.