Database Info

[ROM-DEV] 04/16/10 | Back from the dead | Coming soon

Geek For Me is proud to announce:
Toast's Secret Sauce
From the developers who brought Eclair (Android 2.x) to the CDMA Hero
I'm confused about this post/rom
A lot of new HeroC users out there don't even remember a 2.1 before damage got the leaked RUUs. I actually ported it to the Hero way back in November of 2009 from a copy that had been ported to the GSM Hero. Myself, toast, and a couple of others then spent MONTHS getting everything working. We started with basically nothing at all and ended up with a near fully functioning rom, through the use of real dev work. Check the older posts at http://geekfor.me/android21/ for info on the previous work. I also went ahead and made this post using the old thread so that maybe people can get some history on it.
Can you tell me more about this?
I'll be staying tight lipped for the moment but what I will say is that this is marked as a dev rom for a reason. It is not going to be a 100% functioning rom and is made more as a proof of concept, and for fun. It is not meant as a daily rom for most users.
When will this be released?
Coming soon to a phone near you. We're still working on hammering out some bugs, and adding some features.
And a little teaser (benchmarks) :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I wanna try it but am scared haha still nothing works hopefully will get it before sprint does

magicalan said:
I wanna try it but am scared haha still nothing works hopefully will get it before sprint does
Click to expand...
Click to collapse
Just make a nandroid backup and you'll be fine. lol. This doesn't modify anything that could possibly brick your phone. But yea... it's pretty to look at but doesn't do anything just yet. I can probably get wifi working and such but I don't know what my chances are of making it work on Sprint. I don't know if it even ties in to our radio.img at all and if it's compatible with 2.1.

Many thanks!
I will be flashing this momentarily but wanted to ask you generally what is involved in "porting" a ROM from GSM to CDMA. My naive understanding is that 1.6 and up are GSM/CDMA capable.
And I must admit (with a developer background in many flavors of *nix, particularly the open source varieties of Linux and BSD) I'm not sure I understand why Android is so device specific. Is it the device drivers for individual hardware, the radio? Chip/CPU architecture?
Thank again for the work, I'll let you know what happens!

Hey Flipz.
have you tried to load the modules from the 1.5 rom. ie the radio and all other pertinent modules for the cdma radoi

Tried it can't get past the boot screen. Waited for a crazy long time. You didn't say to do a Nandroid backup in your post, What should I do now? Just kidding, you know it's going to seriously be asked in a couple of posts though.

from the sceen shots i can most likely tell what the major issue is.(i.e. 2.6.27) lol... but hell yeah man!!! thanx fixin to flash now.

If you wait a seriously long time and it won't boot then you likely didn't do a wipe before you flashed the update. It will fail horribly and just keep looping on the startup screen.
I haven't done a single thing yet to try and get anything working other than getting it booting. I wanted to post it up here ASAP.

ah I didn't see to do a wipe, if I wipe the nandroid on the sdcard stays right? I assume it does but I'm going to copy to the copter to be safe. Thanks.

thezero4 said:
ah I didn't see to do a wipe, if I wipe the nandroid on the sdcard stays right? I assume it does but I'm going to copy to the copter to be safe. Thanks.
Click to expand...
Click to collapse
Yup. The wipe pretty much just clears from info from /data/. But having multiple backups is always a good thing!

ok man great... it boots. it takes a minute but it boots. ur right nothing works. maybe bluetooth but all i did was scan for devices. it scanned. but i dont got a bt device. anyhow im gonna charge my phone a bit an try to debug some issues. phone is dead so i gotta wait a few. but thanx again man... good work

oh yeah it booted after a wipe, I feel dumb, it's kind of cool to play arround. the two things I really wanted to see from the 2.1 where the pinch to zoom home screen trick that will zoom out and show all 7 homescreens at once. And the Landscape home screen. Oh well it's really cool to check it out on a CDMA device now after all the GSM brothers have been having fun.

well the phone works. still says no service though... hmmm weird

toastcfh said:
well the phone works. still says no service though... hmmm weird
Click to expand...
Click to collapse
you shouldn't have service, read the first post

well i do... atleast phione service. no data(ie. i can send and recieve calles

so you can make calls and send texts?

no text. the app fails. but yes i can send and recieve calls

if u cant then try plugging in the usb and adb shell. thats all i did. i was doing that then my wife called and surprised the hell out of me

Does sense UI now work with the accelerometer, per rumors and leaks) or is that not the case yet?

idk... i tried using teeter and the ball wouldnt move.... i think the accel is broken... bluetooth works i paired up with my wifes eris

[Q] How to repair a bricked Xoom

Bricked my xoom with wrong imagefile when rooting it.
I would like to know which part, if possible, to replace to get some life in my xoom. I'm stuck at the Motorola logo screen with "Starting RSD 3 mode" or nothing. Can't connect to it with RSD-Lite, ADB or fastboot. I cant connect to it from any of my computers. I have a Linux 32-bit and a win7 64-bit.
So,this is my question.
Can I replace something in the tab to get access to it? Something that comes "preloaded" with the software that I need to communicate with the device using ADB or fastboot? I think, if it's possible to do that, I can flash new imagefiles found in this forum to it.
To tear it down I found this guide:
http://www.ifixit.com/Teardown/Motorola-Xoom-Teardown/4989/1
What do you think? Is it possible? And, if so, where can I find that piece of hardware? Motorola company spareparts? Thats the hardest I think.

I have the exact error as you do! How do we unbrick this error???

I think it's impossible without sending it in for replacement or repair. It would be nice if someone who repairs it tell me what they did when they repaired it. If it's a hardware replacement or some kind of "forced" flash of new software. I hope they have some software tools that we in the community doesn't have. If so, it shouldn't be so expensive.
My problem is that I bought it from a person who bought it from Best Buy in New York. I don't have any warranty because I'm not the one who bought it and here in Sweden they won't repair it because they don't have a service-agreement with Motorola yet. So I have to do it myself or throw it away.

Contact your nearest Motorola office directly, they didn't ask for any paperwork to replace mine.

http://forum.xda-developers.com/showthread.php?t=1035202&highlight=omnia1994
read this thread slowly.. start from pg 2. good luck dude

poisike said:
Contact your nearest Motorola office directly, they didn't ask for any paperwork to replace mine.
Click to expand...
Click to collapse
you are lucky

rachelleroy said:
you are lucky
Click to expand...
Click to collapse
Really lucky, I managed to get a Xoom with a problem that no one has seen or heard about

I had same problem. Try power, vol- and vol+ all at same time. When it comes back on do power and vol -. that should put you back to fast boot. It worked for me anyway.

omnia1994 said:
http://forum.xda-developers.com/showthread.php?t=1035202&highlight=omnia1994
read this thread slowly.. start from pg 2. good luck dude
Click to expand...
Click to collapse
Yes I did a fast "read-thru" of this thread. My problem is different. I can not reboot into fastboot mode. Only RSD 3 mode, and RSD-Lite can't see it. I tried to flash the 3g sbf file just to see if I could restore the fastboot mode and check if RSD-Lite could do anything at all. Nothing happened. That's why I want to learn a little about hardware and replacement of hardware "things". I think that's the only way for me to fix it.
I'm thankful that you are trying to help but all threads are about fixing things with fastboot and fastboot is DEAD on my xoom.
I am searching for a way to restore fastboot.

I feel STRESSED OUT after bricking my Xoom. I bought my Xoom with a $200 off rebate, which is $400 total from costco. PLEASE, someone help us with the RSD mode 3 error!!!!!!

Same problem
Hi jai134,
Just wondering if you had any joy with hardware replacement or some other solution? I think my problem is exactly the same as yours. It's RSD mode 3 or nothing! Windows and Linux can't see the device, and no combination of button presses seems to do anything.
The guys at #xoom on freenode very kindly spent a couple of hours trying to help me out last night but to no avail... it turns out I flashed a zip instead of a boot.img using fastboot.

Dockheas23 said:
Hi jai134,
Just wondering if you had any joy with hardware replacement or some other solution? I think my problem is exactly the same as yours. It's RSD mode 3 or nothing! Windows and Linux can't see the device, and no combination of button presses seems to do anything.
The guys at #xoom on freenode very kindly spent a couple of hours trying to help me out last night but to no avail... it turns out I flashed a zip instead of a boot.img using fastboot.
Click to expand...
Click to collapse
Read through this thread. You might be able to solve your problem with a "factory " cable > http://forum.xda-developers.com/showthread.php?t=1121650
Sent from my Xoom using XDA Premium App

Thanks. That sounds like what I'm looking for... I refuse to believe this one can't be salvaged!
I'll give it a try, and will let you know how it goes.

Hooray!
It worked! My Xoom is unbricked. I made a scary looking factory cable which allowed me to flash with fastboot. My experience was exactly the same as post 41 in the following thread:
http://forum.xda-developers.com/showthread.php?t=1121650&page=5
Here's one end of the cable. The other end is just a regular type A USB plug.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I soldered some staples to the cable and attached them to a micro-usb male breakout board I got on Amazon (see post 43 of the thread linked above). I'd advise covering the connections and staples with electrical tape. I didn't have any handy and consciously decided to take the risk, but any contact between the staples could have fried the USB ports on the Xoom and/or the computer. I'll be taping this up and keeping it on standby in case it's needed again!
Thanks very much for your help cam30era, and also the guys on IRC at freenode, especially Kas and Solarnz.

I just walked someone through this error yesterday, after about 2 hours we recovered his xoom. Don't forget to stop by the xoom irc channel on freenode, you would be surprised the stuff we recovery from in there.

bwcorvus said:
I just walked someone through this error yesterday, after about 2 hours we recovered his xoom. Don't forget to stop by the xoom irc channel on freenode, you would be surprised the stuff we recovery from in there.
Click to expand...
Click to collapse
Why not write up the procedures and put up a download for a pdf?

[Q] Not Complaning, just curious: 1 touch root?

Maybe it's just me, but it seems like the Evo Shift doesn't have it as easy as a lot of other phones. I have NEVER had succesful root (temp or perm) on this phone using a "One Touch" solution like Visionary+, Ginger Break, or z4 Root.
Can anyone explain why that is? What did they do SO differently on this phone, that makes us the ones that have to jump through all of the hoops?
NuAngel

Because you didn't code it.

Or vicodan, he's on gingerbread and didnt bother to read that none of them work or that you need to be in airplane mode on froyo for z4 and visionary to work.

Does this mean there are now 1 touch root apps that WORK for the Shift?! I've been away fro a few weeks...

stormchaser404 said:
Does this mean there are now 1 touch root apps that WORK for the Shift?! I've been away fro a few weeks...
Click to expand...
Click to collapse
No, it means you should READ.

Actually, I'd say neither of you two bothered to read. As he said, he's mainly just curious what makes the Shift different than other, more easily rooted phones. Stop being dicks.
I myself don't have a good answer to the question but I'm tired of seeing so many people harrassed just for asking questions. If you don't want to answer the question, then say nothing.

VICODAN said:
No, it means you should READ.
Click to expand...
Click to collapse
Wow dude, nice attitude. Might wanna lay off the pills, one of the first signs of opiate addiction is aggression.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

jesusice said:
Actually, I'd say neither of you two bothered to read. As he said, he's mainly just curious what makes the Shift different than other, more easily rooted phones. Stop being dicks.
I myself don't have a good answer to the question but I'm tired of seeing so many people harrassed just for asking questions. If you don't want to answer the question, then say nothing.
Click to expand...
Click to collapse
I'm glad we don't have one touch root. I used it on the droid and felt stupid for using it.
Not trying to be a ****, people need to develop a tougher skin.

Yeah. I don't know why people jumped to conclusions about me. I AM, in fact, on Gingerbread NOW - but even back on FroYo, it never worked for me. I got my phone from Best Buy 3 days before you could buy it at Sprint, I've had a SHIFT since the MINUTE I could have a Shift.
I know you need to be in airplane mode, etc, etc, etc... but I've NEVER achieved even a temp root - it just sat there and saying it was trying, and that it might take a few minutes, for 45+ minutes, once, until I power cycle the phone.
And even the gingerbread "perm root" guide says to temp root with Visonary or z4 first. I've never been able to do that. Was just wondering if anyone knew why?

NuAngel said:
Yeah. I don't know why people jumped to conclusions about me. I AM, in fact, on Gingerbread NOW - but even back on FroYo, it never worked for me. I got my phone from Best Buy 3 days before you could buy it at Sprint, I've had a SHIFT since the MINUTE I could have a Shift.
I know you need to be in airplane mode, etc, etc, etc... but I've NEVER achieved even a temp root - it just sat there and saying it was trying, and that it might take a few minutes, for 45+ minutes, once, until I power cycle the phone.
And even the gingerbread "perm root" guide says to temp root with Visonary or z4 first. I've never been able to do that. Was just wondering if anyone knew why?
Click to expand...
Click to collapse
I don't know anything about an airplane mode trick, read the wiki and the stickies in the general forum for root instructions.

VICODAN said:
I don't know anything about an airplane mode trick, read the wiki and the stickies in the general forum for root instructions.
Click to expand...
Click to collapse
Scratches head and wonders how you even got root seems how one of the instructions to perm root your phone was to put it into airplane mode after you checked the hboot and before temp rooting a second time and then perm rooting, but
Sent from a MikSupremed Shift

strapped365 said:
Scratches head and wonders how you even got root seems how one of the instructions to perm root your phone was to put it into airplane mode after you checked the hboot and before temp rooting a second time and then perm rooting, but
Sent from a MikSupremed Shift
Click to expand...
Click to collapse
Ahh. It's been so long. I rooted back in April or May with the help of some people in the irc channel.

NuAngel said:
Maybe it's just me, but it seems like the Evo Shift doesn't have it as easy as a lot of other phones. I have NEVER had succesful root (temp or perm) on this phone using a "One Touch" solution like Visionary+, Ginger Break, or z4 Root.
Can anyone explain why that is? What did they do SO differently on this phone, that makes us the ones that have to jump through all of the hoops?
NuAngel
Click to expand...
Click to collapse
to try to answer your question lol.
Its basically a pain in the ass. Im right there with you.
my reasoning is its because that companys lock their low-end devices the same way for each device because they don't care to much about them and those low-end phones are the main selling point of the company their locked the sameway they therefore have a very easy known,developed method to rooting and nand unlocking
For high-end POPULAR (key word in CAPS) devices tend to have all the attention and developer focus on them so they get more worked in, focused methods to provide an easier user expierence.
The shift is niether popular or low-end so we don't get much focus from devs (compared to others) and we do have a high end device so HTC took the time to lock our phone up good
I went through the same thing
My BEST advice (which many know is not very good)
Is first (yes put in airplane mode)
Run the temp root and perm root with VISONary i have always had problems with z4
Now run the temp root, if it fails to work and doesnt reboot thats fine
now reboot manually
and try it again
and keep rebooting and trying
I eventually got it to take lol
Disclaimer: The Sentences stated in this post were the sole opinions of the poster and do not reflect actual facts, or any others ideas,thoughts or concerns. Translation: Don't flame me!

Good answer.
Sent from my PC36100 using Tapatalk

[Q] Power Brick: killed two HTC One X's in two weeks?

I managed to permanently brick 2 ATT HOX in as many weeks. My bad. When i say brick, i don't think i mean recoverable. I effectively killed the phone's ability to power up, period. Hoping someone here can prove me wrong. (Ex: maybe by jumping a combination of the 5 metal dots on the back of the HTC One X will force it to try reinitializing?)
Symptom: phone will not power on. Holding down the power button for 10 minutes results in the same (dead?) black screen, with no signs of any backlight, power light, nothing.
Before brick: Full battery (93%), was working fine as ATT ICS 4.0, before i tampered with it. Was on version 2.20.(520 or 502) before i killed it. Came stock, which i didn't like, so i chose juicy-looking ICJ v3.4 rom, with plans to add gApps, su. Trying to remember steps to recreate:
tried rooting phone using promising one click root, but got a bunch of permission denied, adb out of date errors. Killed existing adb processes, HTC uploader, etc -- but to no avail. So i gave up after a few tries
bootloader was locked, so i figured to unlock it and flash a rom afterwards. Tried HTC Dev but failed on "unauthorized" error.
used x factor root to successfully unlock bootloader while also changing CID to all 1's. At this point, i think i created the "tampered" mark in bootloader. Oh well.
flashed awesome Team Win Recovery Project twrp v2.3.1 to success
in twrp: fixed permissions, cleared cache, dalvik cache, system... and finally made the infamous (dumb) mistake of flashing external storage and losing the ZIPs i had already placed on the sdcard. Now had no way to install a new OS; and had already deleted my existing OS.
tried to use ADB push to place the zips back on sdcard.... but failed on "unable to mount sdcard" error.
used awesome tutorial by xsmagical to rebuild corrupt partitions, to be able to adb push to a mounted sdcard again
once sdcard was mounted again, pushed ICJ, gapps, and su 0.98 to sdcard
in twrp, installed ICJ successfully from zip. I should be golden at this point, right???
nope. reboot system... to never wake ever again. Never see a boot screen to ever witness ICJ.
press power for 30 seconds.... nothing, Try for 5 minutes... nothing. 10 minutes.... nothing. USB cable connected, disconnected.... power cord connected, disconnected..... nothing.
waited a full week for the power to die -- in case all the phone needed was time to shut down completely. then charged for a full night, tried again in the morning.... nothing.
tucked tail between legs, took bricked phone to ATT device support center, made best innocent-face "dunno what happened", got replacement.
repeat, like an idiot
If i could change anything, i certainly wouldn't use all those tasty (possibly unnecessary) options in twrp to clear the system/caches prior to flashing a new rom.
So, I have another HTC One X to take back to the ATT device support center. They will surely look at me funny the 2nd time around. (The first time we decided to say the power button was stuck. LOL) At least they can't even power the unit to ever see the "TAMPERED" mark in at the top of the bootloader.
If i get another HOX from them, I will surely deviate from the steps above. Hopefully someone reading this thread can figure out a way i can avoid making that shameful visit to claim a 2nd replacement device in as many as 3 days. Any ideas? Did i miss something? Could the phone be on, but unable to turn on the display?
Otherwise... any suggestions to flash ICJ but avoid a 3rd brick are also welcomed.

phi11yphan said:
Was on version 2.20.(520 or 502) before i killed it. Came stock, which i didn't like, so i chose juicy-looking ICJ v3.4 rom, with plans to add gApps, su. Trying to remember steps to recreate:
[*]nope. reboot system... to never wake ever again. Never see a boot screen to ever witness ICJ.
Click to expand...
Click to collapse
Oh dear Lord, another one.
http://forum.xda-developers.com/showthread.php?t=1974101
You'd best work up a good excuse for the AT&T rep.

one
phi11yphan said:
I managed to permanently brick 2 ATT HOX in as many weeks. My bad. When i say brick, i don't think i mean recoverable. I effectively killed the phone's ability to power up, period. Hoping someone here can prove me wrong. (Ex: maybe by jumping a combination of the 5 metal dots on the back of the HTC One X will force it to try reinitializing?)
Symptom: phone will not power on. Holding down the power button for 10 minutes results in the same (dead?) black screen, with no signs of any backlight, power light, nothing.
Before brick: Full battery (93%), was working fine as ATT ICS 4.0, before i tampered with it. Was on version 2.20.(520 or 502) before i killed it. Came stock, which i didn't like, so i chose juicy-looking ICJ v3.4 rom, with plans to add gApps, su. Trying to remember steps to recreate:
tried rooting phone using promising one click root, but got a bunch of permission denied, adb out of date errors. Killed existing adb processes, HTC uploader, etc -- but to no avail. So i gave up after a few tries
bootloader was locked, so i figured to unlock it and flash a rom afterwards. Tried HTC Dev but failed on "unauthorized" error.
used x factor root to successfully unlock bootloader while also changing CID to all 1's. At this point, i think i created the "tampered" mark in bootloader. Oh well.
flashed awesome Team Win Recovery Project twrp v2.3.1 to success
in twrp: fixed permissions, cleared cache, dalvik cache, system... and finally made the infamous (dumb) mistake of flashing external storage and losing the ZIPs i had already placed on the sdcard. Now had no way to install a new OS; and had already deleted my existing OS.
tried to use ADB push to place the zips back on sdcard.... but failed on "unable to mount sdcard" error.
used awesome tutorial by xsmagical to rebuild corrupt partitions, to be able to adb push to a mounted sdcard again
once sdcard was mounted again, pushed ICJ, gapps, and su 0.98 to sdcard
in twrp, installed ICJ successfully from zip. I should be golden at this point, right???
nope. reboot system... to never wake ever again. Never see a boot screen to ever witness ICJ.
press power for 30 seconds.... nothing, Try for 5 minutes... nothing. 10 minutes.... nothing. USB cable connected, disconnected.... power cord connected, disconnected..... nothing.
waited a full week for the power to die -- in case all the phone needed was time to shut down completely. then charged for a full night, tried again in the morning.... nothing.
tucked tail between legs, took bricked phone to ATT device support center, made best innocent-face "dunno what happened", got replacement.
repeat, like an idiot
If i could change anything, i certainly wouldn't use all those tasty (possibly unnecessary) options in twrp to clear the system/caches prior to flashing a new rom.
So, I have another HTC One X to take back to the ATT device support center. They will surely look at me funny the 2nd time around. (The first time we decided to say the power button was stuck. LOL) At least they can't even power the unit to ever see the "TAMPERED" mark in at the top of the bootloader.
If i get another HOX from them, I will surely deviate from the steps above. Hopefully someone reading this thread can figure out a way i can avoid making that shameful visit to claim a 2nd replacement device in as many as 3 days. Any ideas? Did i miss something? Could the phone be on, but unable to turn on the display?
Otherwise... any suggestions to flash ICJ but avoid a 3rd brick are also welcomed.
Click to expand...
Click to collapse
Is this a real thread? If I'm not correct their is a PSA about not flashing ice cold jelly on your HTC one x. I don't even think the Rom is on any of the android threads of HTC one xl.ICJ IS A INTERNATIONAL ROM MEANING IT WILL NOT WORK WITH A NON INTERNATIONAL ONE X. Flash viper xl on these forums in android dev forums of this section. READ before FLASHING ANY ROMS TO MAKE SURE THE ROM IS COMPATIBLE WITH YOUR PHONE. STAY IN THESE FORUMS.

phi11yphan said:
Otherwise... any suggestions to flash ICJ but avoid a 3rd brick are also welcomed.
Click to expand...
Click to collapse
Buy an International One X :good:

Here's the thing I don't get. You're clearly an experienced modder, who is capable of researching and reading and finding solutions on your own. You've been in and out of the AT&T One XL forums repeatedly based on all those links. Surely you noticed at some point that there are two different One X forums, and that ICJ came from the other forum, while all your solutions came from this one.
Yet you not only bricked your phone once with ICJ, but you came back with a new one and did it again.
You sir win the prize for most amazing One XL brick, and that is saying something, believe me. :good:

iElvis said:
Oh dear Lord, another one.
http://forum.xda-developers.com/showthread.php?t=1974101
You'd best work up a good excuse for the AT&T rep.
Click to expand...
Click to collapse
Thanks for the clear explanation!!! Makes perfect sense now. Excuses for the rep I got, no problem. But sadly, I didn't read the PSA, which would've prevented this headache.
My bad for failing to research that ROM incompatibility. I must not have seen the warning in the ROM thread for my phone. Maybe a warning for idiots like me at the top of the ROM thread, since we're all in the HOX section?

WhatTheAndroid? said:
one
Is this a real thread? If I'm not correct their is a PSA about not flashing ice cold jelly on your HTC one x. I don't even think the Rom is on any of the android threads of HTC one xl.ICJ IS A INTERNATIONAL ROM MEANING IT WILL NOT WORK WITH A NON INTERNATIONAL ONE X. Flash viper xl on these forums in android dev forums of this section. READ before FLASHING ANY ROMS TO MAKE SURE THE ROM IS COMPATIBLE WITH YOUR PHONE. STAY IN THESE FORUMS.
Click to expand...
Click to collapse
Doh! Man. Thanks again.
Will try CM10... if i can get myself another HOX. LOL

No. There are 2 different sections. You went to a different one, probably from google, to get that rom.

I personally think the PSA should be at the top of forum website, like a flashing banner. Less hard bricks in QA thread.

WhatTheAndroid? said:
I personally think the PSA should be at the top of forum website, like a flashing banner. Less hard bricks in QA thread.
Click to expand...
Click to collapse
There are clear warnings are in the development section stickies for both forums. But there's only so much you can do if people won't read them. XDA assumes a certain level of caution and that new phone owners will go to the trouble of researching the basics of their handset before diving into rooting and romming.

"Insanity: doing the same thing over and over again and expecting different results"
- Albert Einstein
Why in the world would you try the same thing that bricked the first phone, without taking a few minutes research as to what went wrong?
Sent from my HTC One XL using xda app-developers app

Bom Bom Bom... Another one bites the dust
Sent from my One X using Tapatalk 2

InflatedTitan said:
Bom Bom Bom... Another one bites the dust
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=rY0WxgSXdEE

iElvis said:
You sir win the prize for most amazing One XL brick, and that is saying something, believe me. :good:
Click to expand...
Click to collapse
LOL
lets just say i wasn't at my best multitasking these past few weeks i'll try to slow down and smell the... pine trees?

Two phones... Gone.... Seriously kid, I for one refuse to believe you're an sort of modder/hacker. You apparently can't read from the many warning threads around here... If you bricked from an ICJ on the first one, why do it a second time? Its like grabbing a hot piece of metal. You're first reaction would be to instantly drop it, the next would be to never touch something that is hot... :shakehead:
Sent from my One X using xda app-developers app

Myrder said:
Two phones... Gone.... Seriously kid, I for one refuse to believe you're an sort of modder/hacker. You apparently can't read from the many warning threads around here... If you bricked from an ICJ on the first one, why do it a second time? Its like grabbing a hot piece of metal. You're first reaction would be to instantly drop it, the next would be to never touch something that is hot... :shakehead:
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
No it's like stabbing yourself with a knife in the chest going to the hospital them telling you youre lucky you have survived going home doing the exact same thing expecting nothing to be wrong with you than doing some research once finally in deathbed

omario8484 said:
No it's like stabbing yourself with a knife in the chest going to the hospital them telling you youre lucky you have survived going home doing the exact same thing expecting nothing to be wrong with you than doing some research once finally in deathbed
Click to expand...
Click to collapse
yeah yeah...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

anyone remember this

phi11yphan said:
yeah yeah...
Click to expand...
Click to collapse
That pic is hilarious
Sent from my One X using Tapatalk 2

Well, now that we've thoroughly roasted you, in the spirit of actually answering the question: your only real option to get the phone back up and running (aside from major surgery, like replacing the main board) is here, and requires access to a Linux machine, and not that easy. So . . . uh, good luck.
phi11yphan said:
Hopefully someone reading this thread can figure out a way i can avoid making that shameful visit to claim a 2nd replacement device in as many as 3 days.
Click to expand...
Click to collapse
Its easy to avoid. Just don't do it. Claiming a warranty replacement for your own negligent actions is a scumbag move. Some will say you are just "sticking it to the man". But in reality, you are just screwing the rest of us, since this is the main reason HTC is locking down their bootloaders to begin with.
Take responsibility for your actions and buy a replacement phone; or contact HTC directly, tell them what you did, and ask them how much it will cost to repair it, like this guy: http://forum.xda-developers.com/showpost.php?p=34703109&postcount=195
A lesson that hits your wallet is an easy one to remember.

Oneplus One. EMMC Possibly Corrupted but not sure, need help unbricking.

If anybody can add me on skype or steam or any other IM platform, that would be fantastic, just PM me if you could, with your user for anything.
I have all the possible QPST tools needed to interface with my device, and it still has some life left in it, for example it is still able to interface via usb through qualcomm's 9008 qdloader drivers.
I have tried endlessly to unbrick this device using various tools and methods, but they all come up with that same error relating to Sahara, firehose, or programmer. I can't seem to get MiFlash to do anything, since I know basically nothing about how it works, just that I followed some guys tutorial on flashing to the Opo, but it doesn't seem to work. All the QPST tools say it can't communicate with the
flash programmer.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Am I screwed except for JTAG? I really, desperately need help, and this seems to be the only place to get actual help from devs who actually understand what is happening in terms of partitions, etc. (Xda won't help me since I'm a new user and I've tried posting multiple times and got basically no response.)

Help!
Wax that no one can help us?

Have you tried this guide?
It works for me, unbricked my OPO twice.

soralz said:
Have you tried this guide?
It works for me, unbricked my OPO twice.
Click to expand...
Click to collapse
If friend as you can see, all these tools have already been used.!

soralz said:
Have you tried this guide?
It works for me, unbricked my OPO twice.
Click to expand...
Click to collapse
What works for you and the majority of other people sadly doesn't work for me, or people with my issue.
No tool this specific case exists yet to fix this.
It's as simple as that. I need a developer, I need a programmer. That is all I need. And I've been on the hunt for months.

PikuChan said:
What works for you and the majority of other people sadly doesn't work for me, or people with my issue.
No tool this specific case exists yet to fix this.
It's as simple as that. I need a developer, I need a programmer. That is all I need. And I've been on the hunt for months.
Click to expand...
Click to collapse
Hmm, probably incorrect driver? What OS environment are you in to flash the OPO anyway?

soralz said:
Hmm, probably incorrect driver? What OS environment are you in to flash the OPO anyway?
Click to expand...
Click to collapse
Linux, Windows 7, Windows XP, Windows 8 and 8.1 separately, (seriously), you name it. I've tried everything. I mean that to its fullest If the tools in my post weren't enough, I've also tried a billion others, whether they relate to the OPO or not.
Again, people with this issue need a developer, the device doesn't go into 9006 Loader mode when tools like ToolStudio try to flash things to it, aka locked bootloader (I think). This has nothing to do with drivers. I'm not looking for a one click solution, one doesn't exist. I'll do almost anything to fix this.

If you got sahara error unplug your phone and try again with holding VolUp and plug it back in. This is to force it into 9008 mode again.

tropenfrucht said:
If you got sahara error unplug your phone and try again with holding VolUp and plug it back in. This is to force it into 9008 mode again.
Click to expand...
Click to collapse
All this has been done, and nothing appears to be a more serious problem than that.

krizzhellsing said:
All this has been done, and nothing appears to be a more serious problem than that.
Click to expand...
Click to collapse
Indeed. I just need custom linux code to mess with the partitions. I had a friend try wiping EVERYTHING in Twrp terminal, all the partition data, nothing remained. And the ColorOs tool (Msm8974 Downloader) still managed to rebuild the partitions, etc. If there's any way I can nuke the OPO's current partition data through something like a linux perl script, I'd probably be set to restore it through the regular tools.

Here's what happens when I try to flash anything with qdloader's perl script in Linux.

Good Luck.!
I see it very difficult to repair, better choose to buy the motherboard on eBay for $ 100, I wish you luck hopefully you can fix.

Same issue here. Tried everything and every suggestion out there. Still stuck on 'Sahara' issue. I also tried with the QFIL software but met with the same dead end. The idea of wiping the entire partition tables in Linux may work, if only we can get the 'how'. I'm just stumped why this one is having this issue; the first one I unbricked went smoothly, no issues and worked perfect afterwards. I wish I can get my head around this quickly; it's giving me sleepless nights.

stuck at same step
me too tried all possibilities and stuck at same step; spent sleepless nights to fix it and still hunting for solution

How did you bricked your oneplus one?downgrade to kitkat?
Sent from my A0001 using XDA Free mobile app

OPO dead unexpectedly
assassin0408 said:
How did you bricked your oneplus one?downgrade to kitkat?
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
My Phone dead unexpectedly , @ night after charged to 80% unplugged and slept; @ morning no display, no reaction on any action. but experienced hot at front camera

Sounds like hardware failure for it to just stop. You could've had an unexpected surge charging, and the some part of the motherboard failed. I agree with earlier post, it might be time to replace it. Sucks, but it happens and I've seen it happen from time to time when I worked 3 years in wireless (VZW and ATT) in college. None of our tools would bring them back and we had software to do exactly what you're asking/looking for. It would wipe the phone to the point of literally being a brick, then reload everything back onto it. It would take hours sometimes and most failed. They eventually started hiring people just to do that all day, and we'd ship them off to a local store that had people doing it all day in the back offices.
Sent from my A0001 using XDA Free mobile app

nikeman513 said:
Sounds like hardware failure for it to just stop. You could've had an unexpected surge charging, and the some part of the motherboard failed. I agree with earlier post, it might be time to replace it. Sucks, but it happens and I've seen it happen from time to time when I worked 3 years in wireless (VZW and ATT) in college. None of our tools would bring them back and we had software to do exactly what you're asking/looking for. It would wipe the phone to the point of literally being a brick, then reload everything back onto it. It would take hours sometimes and most failed. They eventually started hiring people just to do that all day, and we'd ship them off to a local store that had people doing it all day in the back offices.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Ok thanks seems like its time to buy new phone

Same problem
Hi I have the same problem, I tried with windows 7, 8, 10, XP, but does not solve the hard brick, is nothing msiimage.mbn because someone knows this problem?:crying:

OnePlus One gone X came in
laxlucky said:
Ok thanks seems like its time to buy new phone
Click to expand...
Click to collapse
Bought new phone OnePlus X.