Database Info

Not really sure is it 32a or 32b.

The whole problem is i have 32a rom. I'm using it since i got the phone from Orange [Poland]. 1. It's htc branded. 2. It has 32a hboot. 3. and thats the problem it have got 196 rom total it says in any program.... So which is it 32b and i'm just using wrong roms or 32b?

criskrzysiu said:
The whole problem is i have 32a rom. I'm using it since i got the phone from Orange [Poland]. 1. It's htc branded. 2. It has 32a hboot. 3. and thats the problem it have got 196 rom total it says in any program.... So which is it 32b and i'm just using wrong roms or 32b?
Click to expand...
Click to collapse
Boot your phone into fastboot mode:
1. Power phone off
2. Hold Back key and power phone on

it says 32a but is it normal that i have 196 ram?

criskrzysiu said:
it says 32a but is it normal that i have 196 ram?
Click to expand...
Click to collapse
yes, you have 32A. the rest of memory is reserved.

criskrzysiu said:
it says 32a but is it normal that i have 196 ram?
Click to expand...
Click to collapse
yes its normal. the other memory you cant see since is reserved for the Operating system

lol i think if it says "32a" you have a 32a device...come on man. common sense....

[ROOT] Think-tank

So, I'm starting this thread to start trying to put a root method together.
I've started work on a unsecure boot image using the at&t boot.img from 1.68
(going to try and get a 'INSECURE BOOT AND ROOT' going for our devices that paulobrien already has going for teg3 models)
I'd like a confirmation that the at&t 1.68 ruu does indeed work 100% without issue on the rogers devices. As there's no Rogers RUU, I'm taking a big leap with semi-bricking a pretty expensive device that I bought outright and would like to minimize risk (I still am willing to take the risk)
Also, any other information/help/idea's from other dev's or users alike would also be appreciated.
Let's get this ball rolling without waiting for the at&t release...
Edit: Has anyone attempted to compare the partition table to the one already somewhat put together for the Tegra 3 One X ?
PS: I'm going over information regarding the regular one x, and comparing them to the extracted items from the 1.68 evita ruu (so I can get a sense of the makeup of our devices) ... I might have to make us a partition table comparison similar to mike1986's

from my understanding and research... the Rogers and AT&T are identical minus the HIGHEND bloadware

Even the CID is the same?!
Wow that's good news for AT&T people, they can flash the Rogers RUU to gain more features
For rooting... Possible to unlock with htcdev?
Then we only need a custom recovery to push busy box and whatever to get root

ytwytw said:
Even the CID is the same?!
Wow that's good news for AT&T people, they can flash the Rogers RUU to gain more features
For rooting... Possible to unlock with htcdev?
Then we only need a custom recovery to push busy box and whatever to get root
Click to expand...
Click to collapse
I haven't done it myself yet, but some misguided users did unlock their bootloader and flashed the CWM for the Tegra edition of the One X. So I'd assume we're good on that front. I was going to start trying to compile CWM for our device on the weekend, but life got in the way.

I've unlocked my bootloader through HTCDev. I also believe the CID are the same but please don't quote me on that. I spent hours trying to correct my device so everything is a blur.
I believe that outside the carrier bloatware that the Rogers and AT&T devices are completely identical. I've killed just about every piece of Sense software too and my device is running flawlessly. On a side note, I'm quite impressed at how polished this is and that Sense isn't the beast it was on previous devices. Re-enabled a lot of features and I quite enjoy them.

LNKNPRKFN said:
from my understanding and research... the Rogers and AT&T are identical minus the HIGHEND bloadware
Click to expand...
Click to collapse
The same was the case between the Telus DHD and the Inspire 4G... But one was the PD9814000, while the other was a PD9812000 (ordered respectively). I wouldn't doubt the same. The original DHD was PD9810000 (DHD 9191), and there was also a PD9815000 as well floating around in the asian market (I think Korea) and was simply another variant of the TelusDHD/Inspire (9192).
If someone were to hop into an at&t store and check their display model, what it says on the back under the FCC logo .. or better yet install terminal on it and run /sbin/grep and get the androidboot.mid value to accurately get the CID, would be best.
Sent from my HTC One X using xda premium

craig0r said:
I haven't done it myself yet, but some misguided users did unlock their bootloader and flashed the CWM for the Tegra edition of the One X. So I'd assume we're good on that front. I was going to start trying to compile CWM for our device on the weekend, but life got in the way.
Click to expand...
Click to collapse
Well, if our recovery sits in the same partition as the teg3 device, then we might actually have a chance.
Sent from my HTC One X using XDA premium

Also, here's a link to a 1.68 mirror I put up. More reliable that the one's currently available.
http://d-h.st/hoA
Will upload more as I get them (clicking my user name will get the full listing of items I have available; 'ER3BUS' is NOT for the One X if anyone's wondering)
Sent from my HTC One X using XDA Premium

JSLEnterprises said:
The same was the case between the Telus DHD and the Inspire 4G... But one was the PD9814000, while the other was a PD9812000 (ordered respectively). I wouldn't doubt the same. The original DHD was PD9810000 (DHD 9191), and there was also a PD9815000 as well floating around in the asian market (I think Korea) and was simply another variant of the TelusDHD/Inspire (9192).
If someone were to hop into an at&t store and check their display model, what it says on the back under the FCC logo .. or better yet install terminal on it and run /sbin/grep and get the androidboot.mid value to accurately get the CID, would be best.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
On the Rogers unit, it's NM8PJ83100.
I believe some AT&T customers here said they had the same number on their pre-orders.

JSLEnterprises said:
Well, if our recovery sits in the same partition as the teg3 device, then we might actually have a chance.
Sent from my HTC One X using XDA premium
Click to expand...
Click to collapse
(This may be a dumb question.)
Even if it's not on the same partition, does that really matter when we can just "fastboot flash recovery cwm.img?" Of course we'd have to find the partition locations, but I think fastboot should be enough to get us off to a start. Maybe I'm wrong. I've never had the chance to work on rooting a device, but with this one being so new, I'm hoping I get a chance to help out.

craig0r said:
(This may be a dumb question.)
Even if it's not on the same partition, does that really matter when we can just "fastboot flash recovery cwm.img?" Of course we'd have to find the partition locations, but I think fastboot should be enough to get us off to a start. Maybe I'm wrong. I've never had the chance to work on rooting a device, but with this one being so new, I'm hoping I get a chance to help out.
Click to expand...
Click to collapse
Compiling a proper working cwm 'port' (if you will), kinda requires adaptation of code to correspond to the device's partition table... values need to change for commands for it to work properly and not cause your device to brick (you wouldnt want to flash the recovery to mmcblk0p05 if the recovery isnt in that partition)
(think back to the sd partition issue with cwmrecovery early last year which repartitioned some device's emmc instead of the sd)
I personally havent dabled in kernel / recovery compiling... so I'm only going off the amount of knowledge that I know; I could be wrong however.

I'm an AT&T rep, and I have a One X on hand. I can't take it home with me, but here's some info that you guys have been needing. Let me know what else you guys need me to find out/dump.
CID is CWS_001
{
"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"
}

danielsaenz said:
I'm an AT&T rep, and I have a One X on hand. I can't take it home with me, but here's some info that you guys have been needing. Let me know what else you guys need me to find out/dump.
CID is CWS_001
[ two images]
Click to expand...
Click to collapse
Thanks.
I also have a modelid confirmation that the 1.68 is indeed the same as the 'release' firmware, and that our devices are identical.
I'll be attempting a down n dirty 'boot n root' tonight.

k4p741nkrunch said:
Also, I think the only holdup is finding and verifying the partitions then you just sign up to HTCdev, get the unlock.bin file and fastboot flash the modded cwm.
Click to expand...
Click to collapse
I'd rather fastboot flash a modded boot image (since thats easy to change) rather than flash an untested recovery, espeically since I'm the one changing the default prop values, and permissions in init.rc the boot.img. lol.
Edit: The boot image i'll be modifying is the 1.68 boot image.
k4p741nkrunch said:
Root access shouldn't be necessary to cat the init file and list the partitions right?
Click to expand...
Click to collapse
no, you dont need root for that.

danielsaenz said:
What is the command to get the partition table?
Is it done on the phone, fastboot, or adb?
Let me know and I will find that out for you.
Click to expand...
Click to collapse
dev: size erasesize name
mmcblk0p23: 000ffa00 00000200 "misc"
mmcblk0p22: 00fffe00 00000200 "recovery"
mmcblk0p21: 01000000 00000200 "boot"
mmcblk0p33: 67fffc00 00000200 "system"
mmcblk0p30: 00140200 00000200 "local"
mmcblk0p34: 0ffffe00 00000200 "cache"
mmcblk0p35: 97fffe00 00000200 "userdata"
mmcblk0p26: 01400000 00000200 "devlog"
mmcblk0p28: 00040000 00000200 "pdata"
mmcblk0p36: 27be00000 00000200 "fat"
mmcblk0p31: 00010000 00000200 "extra"
mmcblk0p17: 02d00000 00000200 "radio"
mmcblk0p18: 00a00000 00000200 "adsp"
mmcblk0p16: 00100000 00000200 "dsps"
mmcblk0p19: 00500000 00000200 "wcnss"
mmcblk0p20: 007ffa00 00000200 "radio_config"
mmcblk0p24: 00400000 00000200 "modem_st1"
mmcblk0p25: 00400000 00000200 "modem_st2"
---
Using ADB - adb shell cat /proc/emmc
dsixda's kitchen auto root did not work for the stock ROM, it results in bootloop. Also, my other bootimg decompilation tools aren't working either. I know what to do, just not how to get it to boot on my phone. logcat doesn't pick anything up, either. If anyone has any ideas on how to get the boot.img decompiled/recompiled, feel free to send it my way.

So, I think Paul may have beaten me to it.
But I'm still going to test my edits later tonight anyways. heh

RMatt1992 said:
dev: size erasesize name
mmcblk0p22: 00fffe00 00000200 "recovery"
Click to expand...
Click to collapse
Just make's you wonder what's actually sitting in our 5th partition (the recovery location of the endeavor)
RMatt1992 said:
dsixda's kitchen auto root did not work for the stock ROM, it results in bootloop. Also, my other bootimg decompilation tools aren't working either. I know what to do, just not how to get it to boot on my phone. logcat doesn't pick anything up, either. If anyone has any ideas on how to get the boot.img decompiled/recompiled, feel free to send it my way.
Click to expand...
Click to collapse
dsixda's kitchen is really only for gingerbread devices.
I use that kitchen... just to 'cook' the final release into a signed zip.

FYI, Rogers CID = ROGER001, so they are different unfortunately.

RMatt1992 said:
FYI, Rogers CID = ROGER001, so they are different unfortunately.
Click to expand...
Click to collapse
doesnt matter...
ro.aa.modelid=PJ831000 <- key value (this is what usually denotes hardware variance... usually the third last '0' becomes a different number)
same as the at&t one x.
the maincid and cidlist values mean nothing other than software branding.

JSLEnterprises said:
doesnt matter...
ro.aa.modelid=PJ831000 <- key value (this is what usually denotes hardware variance... usually the third last '0' becomes a different number)
same as the at&t one x.
the maincid and cidlist values mean nothing other than software branding.
Click to expand...
Click to collapse
Cheers, I thought the CID was important for something.

[Q] Firmware Images from RUUs and OTAs

Does anybody know what the tz.img and rpm.img are for? (Or point me to where this is explained.)
From the looks of it, tz has to do with encryption and security,
and rpm has to do with clocks, voltages (power management).
Those of us with older hboots who don't take RUUs or OTAs but manually flash radios will fall behind on those. Since that typically involves radio (cellular/gps/..?), wcnss (wifi) and adsp (audio processing and routing?).
I don't think I'm too interested in updating tz.img, in case it causes more restrictions, much like updating hboot,
but I wonder whether updating rpm.img could be beneficial, or at some point even necessary for compatibility.
(rpm goes in mmcblk0p10, tz goes in mmcblk0p11)
Thanks,
-Jobo
Edit: Ok, so I flashed the rpm.img from the 2.31 OTA, and I can hereby report that
* it takes (I extracted it again after a reboot and it was the new one) and
* it does not brick the device, nothing seems broken.

touch of jobo said:
Does anybody know what the tz.img and rpm.img are for? (Or point me to where this is explained.)
From the looks of it, tz has to do with encryption and security,
and rpm has to do with clocks, voltages (power management).
Those of us with older hboots who don't take RUUs or OTAs but manually flash radios will fall behind on those. Since that typically involves radio (cellular/gps/..?), wcnss (wifi) and adsp (audio processing and routing?).
I don't think I'm too interested in updating tz.img, in case it causes more restrictions, much like updating hboot,
but I wonder whether updating rpm.img could be beneficial, or at some point even necessary for compatibility.
(rpm goes in mmcblk0p10, tz goes in mmcblk0p11)
Thanks,
-Jobo
Edit: Ok, so I flashed the rpm.img from the 2.31 OTA, and I can hereby report that
* it takes (I extracted it again after a reboot and it was the new one) and
* it does not brick the device, nothing seems broken.
Click to expand...
Click to collapse
do you notice any differences whatsoever? How do you know it properly flashed?
-Sent from my HTC One S.-

chrikenn said:
do you notice any differences whatsoever? How do you know it properly flashed?
Click to expand...
Click to collapse
I know it flashed, because after a reboot I extracted the partition again from the device. What I got out was the same as what I put in, not the same as what was in there before. (So at least hboot-1.06 lets you do this.)
I don't notice any difference. Everything just works like it did. Keep in mind that this is nothing exotic. Everyone who took the OTA now has this same image in place, but they're now on hboot-1.14.0002.

touch of jobo said:
I know it flashed, because after a reboot I extracted the partition again from the device. What I got out was the same as what I put in, not the same as what was in there before. (So at least hboot-1.06 lets you do this.)
I don't notice any difference. Everything just works like it did. Keep in mind that this is nothing exotic. Everyone who took the OTA now has this same image in place, but they're now on hboot-1.14.0002.
Click to expand...
Click to collapse
I'm also on hboot 1.06 and resisting ruus. What command did you use to flash? Fastboot flash rpm rpm.img?
-Sent from my HTC One S.-

chrikenn said:
What command did you use to flash?
Click to expand...
Click to collapse
dd in an adb shell in recovery, same as with radio images.

touch of jobo said:
dd in an adb shell in recovery, same as with radio images.
Click to expand...
Click to collapse
hmm that's beyond my expertise. Notice any differences at all yet?
-Sent from my HTC One S.-

What is going on!!
I have a T-MO one s came from a S2 t-989. WHY are flashing new radios so complicated with this new phone!! they need to make thread specifically for the tmo variant...
Will someone nice please help me out... I read that the 2.21 radio is the best at the moment and that is the one I want
Currently I have HBOOT 1.09, radio 0.16.31501S.16_2 and says tampered and unlocked
I already have ViperOneS on my phone and it works good but the signal is poor goes from G, to 3G, and under one circumstance it said 4g...
I live in Texas and when it was stock I had 4G ALL the time...
Used the all in one kit to flash TWRP and was lucky enough to get the rom on there
The reason I am posting here is because it wont let me in the dev section

Partition brick.! Please help.!!! SOLVED

So yesterday i decided to flash CWM touch on my phone manually. I decided to do it through the phone on terminal emulator,
i wrote:
su
dd if=/sdcard/recovery.img of=/sdcard/dev/block/mmscsomething/13
note i used 13, cause i saw it on a thread. I think that's the problem.
IT said something like not enough memry. but it did it anyway.
I tried restoring. Odin back to stock... flashing new ROMs. but NOTHING WORKS. PLEASE help me. it does turn on but it's supper laggy. i tried resetting, wiping cache & dalvik.. but nothing works.. I do recall never being able to wipe my dalvik... is that a problem.?? Help!

i think my case is special. I've NEVER heard of this. Maybe i discovered a new kind of brick. Semi-brick? I have no idea what to do. Is there a way to revert the dd if=\ command? or a way to COMPLETLY wipe my phone. I mean COMPLETELY factory. NOthing but stock.

I think i might move to a windows phone. Where's there's slim chances of me F*cking up BIG TIME. D;

I'm gonna try to 'fix' my recovery with ROM manager to flash it for me.
I hate it that now the recoveries come out as .img format. >=[

I know have CWM but still same problem. WTF.??
GOnna wipe.

Nothing.! OMG i'm gonna cry.... ;(
WTF happened, I swear.!!!

I think i know my problem... since i think i put the wrong number... it sort of bricked my phone. Can i recover from this at all.???

My problem is partition brick. Any help?

unicorndust98 said:
My problem is partition brick. Any help?
Click to expand...
Click to collapse
Woah! Come down lol
Sent from my SGH-T769 using xda premium

im_awesome_right? said:
Woah! Come down lol
Sent from my SGH-T769 using xda premium
Click to expand...
Click to collapse
Lol. But i'm really freaked out. This may be unfixable for me.

I am COMPLETELY UNABLE to fix this.
I even tried to re-partition in Odin while returning to stock, with just the pit, and while flashing CWM.
& I can't even afford a new phone.
Well, back my old one.
Thanks Blaze community. It's been great here, but due to my ignorance I've fried my partitions and am unable to fix it.
If anyone is interested in a defective, faulty Blaze... Hmu.
( I mean software-ish defective. My phone is in brand new cond. 9/10 definetly)

unicorndust98 said:
I am COMPLETELY UNABLE to fix this.
I even tried to re-partition in Odin while returning to stock, with just the pit, and while flashing CWM.
& I can't even afford a new phone.
Well, back my old one.
Thanks Blaze community. It's been great here, but due to my ignorance I've fried my partitions and am unable to fix it.
If anyone is interested in a defective, faulty Blaze... Hmu.
( I mean software-ish defective. My phone is in brand new cond. 9/10 definetly)
Click to expand...
Click to collapse
If you're really selling the phone let me know how much I might be able to use it as a dev phone
----------------------------------------------
If helped don't be afraid to hit the thanks button it doesn't bite lol

Dude, leaving the phone seems a bit extreme. If you just fubar'd one partition, it'll be fairly easy to fix it. Partition 13 is the misc firmware partition. If it was the EFS partition, I'd worry, but it isn't. It's got fairly static stuff in it. I'm not volunteering (because I have like 0 time right now), but I'm sure someone here will be able to help you:
figure out if you actually screwed the partition
get a new copy of the partition installed if there really is a problem
I'm sure you could probably also solve this problem by flashing a fully stock firmware. Either way, going crazy over a matter of a few hours is no way to solve your problem over a perfectly good phone.
Instead of going crazy, ask the questions that will help you figure out what partition 13 should look like. If you have a phone to fall back to, well... fall back to it for the moment. Fix your phone, move forward.

Well, I already tried Odin to stock like 4 times,but the problem persists. Although, you are a GREAT motivation. Thanks, dude.

Okay, so I'm gonna try doing a FULL Odin to stock with ALL the files there. Only problem is that I don't know where to get the: CSC, BOOTLOADER, or PHONE files. I saw here that it worked. Can someone show me where to get them?
EDIT: I'm downloading one from SamMobile. Hope this works.

Oh my F GOD. It worked.! I fixed it.! YAY.!!! Thank you SO much dr4stic.. Thanks a TON.!! saved me hundreds.
If anyone somwhoe manages to mess up their partitions too. but still can get to download mode, All i did was download my firmware from sammobile.. (its the ICS one). Flash it along with the pit (don't know if it was necessary to include it but i did and ALSO ticked repartition). And I am now good.!

I did this now I'm screwed......
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p6 bs=4096
nothing no response hard brick......Anyone help?

theprogram1 said:
I did this now I'm screwed......
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p6 bs=4096
nothing no response hard brick......Anyone help?
Click to expand...
Click to collapse
Bro.. I TOLD you pay the $2, better than paying that *100+
I did NOT understand any of that before i did it, nor do i now..
But i was lucky enough to not screw up the CORE partition..

theprogram1 said:
I did this now I'm screwed......
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p6 bs=4096
nothing no response hard brick......Anyone help?
Click to expand...
Click to collapse
if you can't get the phone back into download mode, you're pretty much screwed.
Do you guys know what these partitions mean?
mmcblk0p22: 00fffc00 00000200 "recovery"
mmcblk0p8: 01000000 00000200 "boot"
mmcblk0p24: 5ffffc00 00000200 "system"
mmcblk0p26: 13fffe00 00000200 "cache"
mmcblk0p25: 9ffffe00 00000200 "userdata"
I don't know what partition 6 or 13 are, but you guys need to stop shooting from the hip. The guides for other phones DO NOT NECESSARILY APPLY to this phone.
You will hose your device.

dr4stic said:
if you can't get the phone back into download mode, you're pretty much screwed.
Do you guys know what these partitions mean?
mmcblk0p22: 00fffc00 00000200 "recovery"
mmcblk0p8: 01000000 00000200 "boot"
mmcblk0p24: 5ffffc00 00000200 "system"
mmcblk0p26: 13fffe00 00000200 "cache"
mmcblk0p25: 9ffffe00 00000200 "userdata"
I don't know what partition 6 or 13 are, but you guys need to stop shooting from the hip. The guides for other phones DO NOT NECESSARILY APPLY to this phone.
You will hose your device.
Click to expand...
Click to collapse
Yeah, I agree with 3rd paragraph. Lol
Sent from my YP-G70 using xda app-developers app

[Q] Stuck @ factory splash screen - w/ S-OFF [formerly 'Stuck in Bootloop"]

Ok so please forgive me I originally posted under the "Stuck in Bootloop" post but it was confusing people as i was not the OP.
Anyhow I have S-OFF (via revolutionary io) & hboot-1.45.0013 and for some reason the phone locks up when trying to flash any non gingerbread rom. I tried changing recoveries, and using older ICS (as opposed to JB roms) and have the same issue. Im currently running MikTouch 0.7 but want to go to JellyBean - i dont know if there was something in particular about this Hboot im using but came across a post about
"JuopunutBear S-OFF" and was thinking of giving this a shot somehow even though im already S-OFF.
I dont know if something in the past got flashed incorrectly... however my gingerbread miktouch 0.7 seems to works great with a fresh install (as opposed to a clockwork nandroid restore) as a sanity check... but when going upward to newer android versions things get messed up quick and i get stuck at splash screen.
Does anyone have any suggestions? I was reading how the splash screen is located at a particular location, but perhaps somehow in my device it got moved or God knows what , im just trying to figure out whats going on and how to move forward.

Splash screen did not move to a new partition, if it did it wouldn't show at all (and probably have a brick on your hands)
Can't attest to your particulars as I've never had rev s-off but I do highly recommend j-bear s-off as its true radio s-off rather than simply a patched hboot (can explain more of this if you'd like)
So if I were in your shoes....
First try flashing a known stable ROM that is 4.x (you did)
Not working, so now after the flash try flashing kernel extracted from the ROM you flashed (yeah for s-on folks but its not like its a hard test)
Try different recoveries (worth a shot)
Nothing works? Than do the wire trick and get true radio s-off
Now ROM again ... Still doesn't work? Then well go from there but for now... Above stuff
Sent from my Nexus 7 using Tapatalk 2

demkantor said:
Splash screen did not move to a new partition, if it did it wouldn't show at all (and probably have a brick on your hands)
Can't attest to your particulars as I've never had rev s-off but I do highly recommend j-bear s-off as its true radio s-off rather than simply a patched hboot (can explain more of this if you'd like)
So if I were in your shoes....
First try flashing a known stable ROM that is 4.x (you did)
Not working, so now after the flash try flashing kernel extracted from the ROM you flashed (yeah for s-on folks but its not like its a hard test)
Try different recoveries (worth a shot)
Nothing works? Than do the wire trick and get true radio s-off
Now ROM again ... Still doesn't work? Then well go from there but for now... Above stuff
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Looks like im off to the wire trick as ive already tried all of the above - from the fastboot s-on flash method of boot image to changing recoveries
As for the wire trick I read one needs the original rom for the phone for it to work - which i will need to dig up
But yeah seems as if i covered everything else - ill go to the unlimited.io site and read up some more but thanks for the suggestions.

You can use miktouch or any stock based ROM instead, don't need official stock
Sent from my Nexus 4 using XDA Premium 4 mobile app

Update:
I tried Juopunutbear and no dice.. the tool was smart enough to see that i already had S-OFF. So im trying to decide how i can go back to stock RUU and S-on and rerun my device through thier tool.
I was originally S-OFF via revolutionary, i might try contacting them to see if they have any thoughts. But the good people at unlimited.io think that the reason i might not be able to flash anyting above gingerbread might be due to a Hboot version mismatch thats incompatible with the ROM.
What Hboots are others using? Is there a standard or "unchained" Hboot i can flash to get me going -- this is just totally bizarre.
I tried flashing the following: with a FULL WIPE between installation attempts (formatting : cache, data, system, sdext, & dalvik)
JellyBean DS v1.7
JellyBean DS v1.4
JellyBean DS v1.3
JellyKang 2.1
JellyKang 2.0
LiquidSmooth 2.4
GimmeABreak 2.0
PACMan v23.0
I just get stuck at the splash screen... I am rooted and S-OFF which makes this very strange...
my default scenario: currently Miktouch 0.7 (gingerbread)
*** UNLOCKED ***
doubleshot PVT SHIP S-OFF RL
Hboot-1.45.0013
radio-11.16.3504.20_2
eMMC-boot
nov 21, 2011
what gives...??? has anyone else had a simillar exerience? where and how can i find info on stock rom RUU and going back to S-ON....
this is very troubling
I tried re-running the device through revolutionary.io tool again and it says that "HBOOT 1.45.0013 is not supported at this time" which makes me think that some OTA update (or something else) has corrupted my hboot and make it incompatible with roms above gingerbread -- is there a way to flash a known good Hboot ?

There are always guides in the stickies if you look ©
http://forum.xda-developers.com/showthread.php?p=17384037
Be sure to thank weekends for hosting needed files and bluex for writing such elaborate guides on the doubleshot
Sent from my Nexus 4 using XDA Premium 4 mobile app

Ok im about ready to give up here :
I return to stock 1.63 OTA image, try to go S-ON (failed) - all i managed to do was lock the bootloader
so again I unlocked bootloader ,returned to stock 1.63 OTA image, fastbooted flash TWRP , did full wipe w/ TWRP, fastbooted flash the JellyBeanDS_v1.4 boot.img file , went back into TWRP and installed the full JellyBeanDS_v1.4.zip rom -- and ended back where i started - stuck at factory splash screen for 20 min now and counting.....
HOWEVER this time i found something interesting... after about 30 minutes when I was about to yank the battery and accidentally hit the volume button which made a beep noise (that was unfamiliar in tone) .... granted im still staring at the hideous default splash screen but it does appear that something is going on in the background as when vol+ repeatedly pressed the beep gets louder, and when vol- pressed it beeps quieter... so it seems that something is running - I also see that if i plug it in to a usb cable it appears to be charging now (which wasn't happening before) but why all i see is the splash screen is the question... any ideas?
i cant connect via fastboot or adb to get any additional info... however i was able to manipulate the power button and the optical pad and after fiddling with it seemed based on the haptic response and various other noises i seemed to be in some sort of menu (although i cant see it) but if i select first option and drag the pad to the right - and press the pad... it appears to power-off my device... so def looks like there is some intelligence there but i just get the stupid splash screen all the time.
Can someone please do me a HUGE favor - can someone please shoot me a link to a - "just recently flashed" (i.e) bare JellyBeanDS_v1.4 or (even better JellyBeanDS_v1.7 ) perhaps in a TWRP (or even a CWM) backup? I just want to see if there is something wrong with my phone - if the nandroid/TWRP backup still doesn't work - i will know for sure that my device is jacked and will see if i can acquire another doubleshot somewhere - this is just ridiculous...
:
i'll setup a dropbox account for the backup if someone can assist me in my quest...

I'll have a chance this weekend if someone else doesn't, haven't had a chance to use my doubleshot in a few months so this will give a reason.
Sent from my Nexus 4 using XDA Premium 4 mobile app

I did not have any luck getting past 1.4. I flashed it over tbalden's P21 and it worked ok. (But did not backup) I've tried the newer ones and may get as far as the cyan sign in screen, screen won't respond and keeps rebooting. So I just go back to P21. Looking forward to using the newer versions and hope you get yours up and running.
Sent from my MyTouch 4G Slide using Tapatalk

daswerk said:
I did not have any luck getting past 1.4. I flashed it over tbalden's P21 and it worked ok. (But did not backup) I've tried the newer ones and may get as far as the cyan sign in screen, screen won't respond and keeps rebooting. So I just go back to P21. Looking forward to using the newer versions and hope you get yours up and running.
Sent from my MyTouch 4G Slide using Tapatalk
Click to expand...
Click to collapse
Ill try starting over with 1.3- but was thinking after some reading - isn't the splash screen mapped to a particular block of memory....
(FROM : http://forum.xda-developers.com/showthread.php?p=17384037)
doubleshot Partitions
Known:
- mmcblk1p2 - "sd-ext"
- mmcblk1p1 - "sdcard"
- mmcblk1 - Link to sdcard/non eMMC block listing.
- mmcblk0p31 - "misc" ( ? same as 16? )
- mmcblk0p29 - "pdata"
- mmcblk0p27 - "devlog"
- mmcblk0p26 - "modem_st2"
- mmcblk0p25 - "modem_st1"
- mmcblk0p24 - "cache"
- mmcblk0p23 - "userdata"
- mmcblk0p22 - "system"
- mmcblk0p21 - "recovery"
- mmcblk0p20 - "boot"
- mmcblk0p19 - "adsp"
- mmcblk0p18 - "radio_config"
- mmcblk0p17 - "radio"
- mmcblk0p16 - "misc" ( ? same as 31? )
- mmcblk0p14 - "splash1" <==================== ??
- mmcblk0p12 - "bootloader" hboot
- mmcblk0p11 - ( TZ ? Trust_Zone ? )
- mmcblk0p10 - ( RPM ? )
- mmcblk0p9 - ( SBL3 ? )
- mmcblk0p8 - ( SBL2 Backup ? )
- mmcblk0p7 - ( SBL1 Backup ? )
- mmcblk0p2 - ( SBL2 ? )
- mmcblk0p1 - ( SBL1 ? )
- mmcblk0 - link to eMMC/ eMMC block listing
Click to expand...
Click to collapse
Now thinking back to my x86 Assembly class - what if the last address of location (or some other part) of the splash block/partition ( mmcblk0p14 ) was truncated...
So what if the code at the end of the splash block in my device is missing a "JMP" as in when the code runs... which is why the splash-screen stays up on screen because the cpu somehow misses this instruction and doesn't know to how to get to the address where the regular video driver section of the code is located (or something like that).
Perhaps some of the code is missing from my " mmcblk0p14 " block section...
would it be possible for someone to send me a flashable splash screen zip of the mmcblk0p14 - "splash1" partition only - to test this theory.... ?
Ill try going back to JB DS 1.3 just in case.. but if i had a fastboot flashable image of the mmcblk0p14 - "splash1" partition - that would be great mini experiment.

http://forum.xda-developers.com/showthread.php?t=2381279
You can flash in recovery or extract images and use fastboot
But the splash partition only holds the image the bootloader controls the booting process so I really don't think it will help
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
http://forum.xda-developers.com/showthread.php?t=2381279
You can flash in recovery or extract images and use fastboot
But the splash partition only holds the image the bootloader controls the booting process so I really don't think it will help
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ill definitely try this with a new image - it cant hurt... and might be my only shot as i also see the same behavior on flashing other roms (tried several last night after wiping, startng from stock OTA, rewiping and flash zip but all of them give me the splash screen problem.

UPDATE
well wish i had better news but think there is a problem with the device itself . So as per my previous posts I tried re-flashing the default splash as well as other splash screens to see if my theory back in post #10 proved out . I was able to change the flash image and re-try a few roms after wiping my device, but same deal... after flashing all i see is the splash screen.
So I wanted to do a quick test and tried instal RUU then flash recovery & full wipe followed by flashing the official CM9 build - and sadly i cant even get that ( the official CM9) running - i do hear noises just like in some of the other roms i flash and i do hear activity if i fiddle with all the buttons and such but all i see is the splash screen......
Im probably going to either see if i can get another used mts4g or upgrade to samsung note3... really love the slide though... would be willing to pay to have someone get it working.....
can someone please send me a few just installed ROM backups preferably as TWRP (or CWM) backups for my MTS4G (Doubleshot) -- via dropbox it would be good to establish that my hw is indeed bad before investing in a new device --- if folks can upload a backup of :
1) Official CM9 for doubleshot (to prove my hw ok)
2) a droid 4.3 release like JellyBeanDS_v1.3+ or JellyKang-doubleshot_v2.1
3) a droid 4.2 release like CM10.1 Liquid.v2.4 or CM10.1-PACman.v23.0.0-JB.4.2.2
if folks can do this that would be great... also if you cant see my dropbox account info below PM me...
USE THE DROPBOX WEB-PORTAL TO UPLOAD FILES
dropbox "[email protected]"
psswd "steve_77"

Well you don't have to pay me as you got me intrigued, if you cover shipping all see what I can do
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
Well you don't have to pay me as you got me intrigued, if you cover shipping all see what I can do
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Just might take you up on that offer PM me the details... address etc.. - im just at wits end here!