• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root The Triumph Experiment Thread (CAUTION!)

So I went back to the Sharp SH8188U rom to see why I couldn't get recovery to work and found a bunch of CDMA settings in the settings menu.
 
So this is the Sharp SH8188U 2.3.5 Triumph nandroid backup. This one is interesting cause it is 2.3.5 and it has kernel 2.6.35.7 . Plus it has cdma stuff built in, there are tons of cdma options inside the menus that I posted pics of earlier. And it shows my meid and says searching for service instead of no sim. Everything works except phone/data.

Again, DO NOT flash this nandoid backup it is intended for development purposes only!

Sharp SH8188U 2.3.5 Triumph Bare Nandroid (no phone).zip

I had to run tj_styles recovery found here http://download.andro-id.net/index.php?dir=FIH-FB0/&file=FB0-0-416B-CWM5-recovery.img It was the only recovery I could get to work with the sharp rom.
 
Can you run edowar's latest ICS rom and check if the headset button ie the button with earphones to play/pause music , etc works with that ROM? Also check if the light sensor works with that rom.

And thanks so much for your efforts.
 
Goofee691 said:
I'm wondering, in any of these rom's does the fm radio work?
Click to expand...

All of these roms come with the fm radio. It has a power button in the app to turn on radio, and it seems to, cause then it will change stations and record fuzz. I searched last night for my hands free headset but all I have are regular headphones and everybody says it needs an antenna. So don't take this as it does work but it seems kinda functional. If I can get my hands on a headset I'll try again.
 
tgpraveen said:
Can you run edowar's latest ICS rom and check if the headset button ie the button with earphones to play/pause music , etc works with that ROM? Also check if the light sensor works with that rom.

And thanks so much for your efforts.
Click to expand...


I went to the Alpha AOSP page but he took down alpha 5 and I don't have a 4shared account to download the alpha 4, so if you guys can link me to a mirror I will get right on it cause I am on the sharp rom now, so I am prepped for the alpha. Getting my coffee in me and getting ready to tear through this stuff again today.
 
Been talking with tj_style at andro-id and he said my baseband is different than his, and wanted me to change the amss.mbn, but when I do, it blue screens after the boot logo shows for a second. I know the Magnum nb0 changed some stuff, I need to figure out how to open up the nb0 to see what it actually changed. If anybody has any ideas feel free to post them.
 
Ok, just so you guys know, here is some background. I have 3 computers set up in my man cave/office, an eight core beast and a quad core beast that are dual boot win 7 x64 and ubuntu 11.10 x64, and an old xp machine. If you have specific instructions for a specific OS I can just turn my chair to the next machine.:D I work from home, so I have all day and then some to mess with this stuff. I've been trying to get more into the depths of android but Linux is fairly new to me, I don't understand all the switches and what they do yet. But my brain is like a sponge, and I can usually fix anything. I want to get into compiling some roms but I know I have alot to learn. I think this Sharp 2.3.5 rom may be the key for us to get a solid gingerbread rom as it has the cdma built in.
 
BSydz said:
I want to get into compiling some roms but I know I have alot to learn.
Click to expand...

I have some decent write up at

Build CM7

http://androidforums.com/triumph-al...uide-setting-up-your-android-environment.html - CM9

The difference between the two is one is for CM7 and one is for CM9. The write up for CM7 is to be used with a local linux account. CM9 is designed to use with the sudo "root" account. Basically since mantera has changed his build to not use adb I should rewrite it. However adb is a very handy tool to pull files and such from a running version of android and also troubleshoot issues with adb logcat. The problem is I found it much easier to configure adb for sudo account than local account. I didn't spend a lot of time on it hence the lazy man way.

Anyways that's a good place to get started. It will also help to know programming in Java and also C. Good luck :)
 
Well I was thinking about how to undo the problem "GSM Triumph" when you flash a a variant's nb0 file. I was wondering if stock recovery can make backups, because you would need a triumph's nb0 not just a ROM zip to fix this problem; and stock recovery uses nb0 format. Even though stock recovery doesn't make backups, I would assume you would need a triumph nb0 to fix this problem...

Edit: I think a firmware update from motorola/vm would work since the update would be a nb0 file...
LOL!!!! Firmware Update From Motorola/VM. LMAO, You're a$$ is gonna be stuck as a GSM Triumph for a WHIIIIIIIIIIIIIILE. LOL!!!!!!
 
Well I think one way to undo the GSM part may be to before switching to a GSM phone make a backup of the phone in linux using dd and the phones download mode, as I learned this actually backs up the PRL MSN MDN and all the other CDMA stuff actually allowing you to clone the phone. you can see more on that in my thread.

http://androidforums.com/triumph-all-things-root/480439-accidental-meid-change.html

I would think as long as you can get to a download mode it would be possible to do this
 
Ok, so I am neck deep in this Magnum nb0, and setting up my dev station. Here is a list of files in the nb0,
FB0-318D-0-5019-A03.mlf
FB0-0-2380-MPRG7x30.hex
FB0-0-2380-NPRG7x30.hex
FB0-0-2380-partition.mbn
FB0-0-2380-partition.bin
FB0-0-2380-loadpt.cmm
FB0-0-2380-dbl.mbn
FB0-0-2380-osbl.mbn
FB0-0-2380-amss.mbn
FB0-0-2390-emmcboot.mbn
FB0-0-2380-adsp.mbn
FB0-0-2390-5017-boot.img
FB0-0-318D-5017-system.img.ext3
FB0-0-2390-0001-recovery.img
FB0-5019-008-splash.img
FB0G-0-3010-5019-hidden.img.ext3
FB0-0-2390-ftm.img
FB0-5019-008-NV_cust.mbn
FB0-5019-008-cda.img.ext3
FB0_5019_NV.xml
FB0_5019_sim_perso.xml
NvDefinition.xml
FB0-318D-0-5019-A03.md5

If anybody has any ideas about where to look for the changes it may have made or wants to check out the files let me know. I'm just sifting through things and comparing the other nb0's right now.
 
I know, some of you might think I'm just a n00b, but I have been building and fixing PCs for over ten years. I didn't even get a computer til 2000, pentium 66 my boss was throwing out, and I am completely self taught from that point. I've just recently got in to C++ this past year, as I now work from home and can spend countless hours reading, and learning new stuff. But, learning new languages is a pain in the rear. :confused:

I enjoy coming to this forum and messing with my phones, there is some great information here. And, some great devs! That is why I started this thread. I don't care about the phone and getting it working, that would be cool if I could. I just want to get these guys that work so hard to make our phones better, some files to use and try to contribute what I can.


I'm trying to get access to the radio folder through Ubuntu right now, gonna try ddrescue to get the files off to see if I can edit them. Thanks Goofee691.
 
Well if we fix the problem, then it will make it easier to experiment on; to see if we can make our phone better.

Edit: These files are ones I know are radio files...
FB0-5019-008-NV_cust.mbn
FB0-5019-008-cda.img.ext3
FB0_5019_NV.xml
FB0_5019_sim_perso.xml
NvDefinition.xml
Click to expand...
 
Well, I bricked my phone :P
Won't turn on, only turns on for 2 seconds to charge, after that, power button doesn't work... lol.

Sent it in to Motorola today. I'll see if they'll repair it or just give it back without fixing (because I "tampered" with it). If they do the latter, I'll just get a GNex and move onto T-Mobile :)

Though I would recommend caution on random ROM flashing. Doesn't seem like the best way to learn about a phone (unless you have a few hundred bucks to mess with). If I remember, from the IRC conversations with Isaac when Gingerbread was still in development for the Triumph (nostalgia!) that the Triumph has a different partition map than most phones with ROMs, and if you screw that up, well... you're screwed.

Though, you're the ROM developer here, and I'm sure you know what you're doing, and I probably don't know what I'm saying.
 
tusing said:
Well, I bricked my phone :P
Won't turn on, only turns on for 2 seconds to charge, after that, power button doesn't work... lol.

Sent it in to Motorola today. I'll see if they'll repair it or just give it back without fixing (because I "tampered" with it). If they do the latter, I'll just get a GNex and move onto T-Mobile :)

Though I would recommend caution on random ROM flashing. Doesn't seem like the best way to learn about a phone (unless you have a few hundred bucks to mess with). If I remember, from the IRC conversations with Isaac when Gingerbread was still in development for the Triumph (nostalgia!) that the Triumph has a different partition map than most phones with ROMs, and if you screw that up, well... you're screwed.

Though, you're the ROM developer here, and I'm sure you know what you're doing, and I probably don't know what I'm saying.
Click to expand...

How did you brick it? I have had this phone NOT work in so many ways flashing these roms, it is ridiculous. So many times I couldn't get it in to download mode or recovery and all I had to do was remove the battery for a little bit longer than I did to begin with. But, there is always a way to get it back up and running. I know you sent it back but, if you get it back the same as you sent it, you can try the Mobile partition files through download mode. The two stock ones I found in this forum didn't work for me, but many people have said they work, there are just 2 versions 038 and 039. And, I can confirm the process because the one I made after I jacked the phone does work for me.

P.S. If you were talking about me being a developer, I'm just a junior member, on my way to halfway understanding what I am doing. :)
 
tusing said:
Well, I bricked my phone :P
Won't turn on, only turns on for 2 seconds to charge, after that, power button doesn't work... lol.

Sent it in to Motorola today. I'll see if they'll repair it or just give it back without fixing (because I "tampered" with it). If they do the latter, I'll just get a GNex and move onto T-Mobile :)

Though I would recommend caution on random ROM flashing. Doesn't seem like the best way to learn about a phone (unless you have a few hundred bucks to mess with). If I remember, from the IRC conversations with Isaac when Gingerbread was still in development for the Triumph (nostalgia!) that the Triumph has a different partition map than most phones with ROMs, and if you screw that up, well... you're screwed.

Though, you're the ROM developer here, and I'm sure you know what you're doing, and I probably don't know what I'm saying.
Click to expand...

why'd you send it to Motorola instead of seeing if VM would send you a new one? You coulda told them what happened and they might've sent you a new one. Or did you ask VM if they would?
 
tusing said:
Well, I bricked my phone :P
Won't turn on, only turns on for 2 seconds to charge, after that, power button doesn't work... lol.

Sent it in to Motorola today. I'll see if they'll repair it or just give it back without fixing (because I "tampered" with it). If they do the latter, I'll just get a GNex and move onto T-Mobile :)
Click to expand...
1. You could've told us what happened, we could've tried help you.
2. You could've smashed the phone, or drown it in water, and return it to VM and defiantly get a new one in a week.
3. You could've smashed the phone, or drown it in water, and return it to Motorola and defiantly get a new one in two weeks.
~~~
I perfer 1 & 3, since VM is too nice when it comes to replacing phones(and they have very generous phone plans) and it would be wrong to scam them; and Motorola could spare a couple of phones(they're richer than VM, Motorola have been horrible to they're customers, and it's their fault the MT is so crappy).
 
Austrie said:
1. You could've told us what happened, we could've tried help you.
2. You could've smashed the phone, or drown it in water, and return it to VM and defiantly get a new one in a week.
3. You could've smashed the phone, or drown it in water, and return it to Motorola and defiantly get a new one in two weeks.
~~~
I perfer 1 & 3, since VM is too nice when it comes to replacing phones(and they have very generous phone plans) and it would be wrong to scam them; and Motorola could spare a couple of phones(they're richer than VM, Motorola have been horrible to they're customers, and it's their fault the MT is so crappy).
Click to expand...

That made me laugh. If I recall correctly, the Triumph was released in July 2011. So, almost any Triumph out there should still be under warranty, except maybe reburbs, right?

I was thinking about writing a letter to Motorola that demanded a stock .nb0 because they put no fail safe in place to make sure that new updates were for the correct phone version. Maybe it would work. :)
 
Even if you're under warranty, VM can charge a minor fee like other companies; and they even when you're not under warranty, they replace your phone most of the time.
 
BSydz said:
That made me laugh. If I recall correctly, the Triumph was released in July 2011. So, almost any Triumph out there should still be under warranty, except maybe reburbs, right?

I was thinking about writing a letter to Motorola that demanded a stock .nb0 because they put no fail safe in place to make sure that new updates were for the correct phone version. Maybe it would work. :)
Click to expand...

No not almost every phone... EVERY single one is still under warranty unless you have voided it by taking it apart or something. Even refurbs. I don't think that writing a letter would really do much, but I guess it can't hurt to try.
 
But rooting/flashing will void your warranty. If you flash a nb0 from some other device you can't expect them to replace it.
 
You must log in or register to reply here.
Back
Top Bottom