Austrie
Android Expert
The MT is so crappy in Stock form(Because Of Them), that we deserve to get a replacement even though we voided the replacement.
-
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!)
- Thread starter BSydz
- Start date
-
- Tags
- motorola triumph
agentc13
Daleks Über Alles
Too bad that isn't how it works.
Well I backed up all the hidden partitions to a usb drive, now my thumb drive thinks it is a GSM Triumph 
!
But I still think there might be more hidden partitions. Cause I unplugged the devices and then plugged them back in and the /dev path swapped but I ran the command the same and it started making my phone the usb drive
. So, either it didn't wipe the folder with my esn and stuff before I yanked the plug or it is on another hidden partition.
Then I ran SUT and retored the phone. SUT asked me if the phone was a drive or not, a few times, and said it had to format the drives to get it back. Man those guys with the GSM x6 variants and an nb0 are a lucky bunch. I'm half tempted to format the whole disk and see if SUT will reload it.
! But I still think there might be more hidden partitions. Cause I unplugged the devices and then plugged them back in and the /dev path swapped but I ran the command the same and it started making my phone the usb drive
. So, either it didn't wipe the folder with my esn and stuff before I yanked the plug or it is on another hidden partition.Then I ran SUT and retored the phone. SUT asked me if the phone was a drive or not, a few times, and said it had to format the drives to get it back. Man those guys with the GSM x6 variants and an nb0 are a lucky bunch. I'm half tempted to format the whole disk and see if SUT will reload it.
tusing
Android Enthusiast
Well, my power button seemed to not have worked, or maybe the processor went bad (couldn't even get past charging screen, download mode wasn't possible). Since I got this from a brick and mortar store, VM told me to contact the store instead. Store told me to contact Motorola. I would have removed all traces of my screwing with the phone if I could, but given the state the phone was in, it seemed impossible.
Well, I'll see what comes of this. If they send it back because of voided warranty, I'll ask around here for help. If that doesn't work, I'll argue with VM.... And if that doesn't work, I'll give up and move on to T-Mobile, but I doubt it will ever come to that. Thanks for all the advice! I do prefer not breaking the phone on purpose to get it replaced though. As much as I dislike Motorola, doing something like that makes me feel cheap and devoid of morals- put yourself in Motorola shoes. Would you want customers to break phones just because they think you can afford to give away new ones?
On-topic, though: if you are able to flash a ROM, try logcatting what happens when you open up the camera app. Maybe the logcat output cold be useful?
Well, I'll see what comes of this. If they send it back because of voided warranty, I'll ask around here for help. If that doesn't work, I'll argue with VM.... And if that doesn't work, I'll give up and move on to T-Mobile, but I doubt it will ever come to that. Thanks for all the advice! I do prefer not breaking the phone on purpose to get it replaced though. As much as I dislike Motorola, doing something like that makes me feel cheap and devoid of morals- put yourself in Motorola shoes. Would you want customers to break phones just because they think you can afford to give away new ones?
On-topic, though: if you are able to flash a ROM, try logcatting what happens when you open up the camera app. Maybe the logcat output cold be useful?
Austrie
Android Expert
If they didn't do such a poor job on the phone, then we wouldn't need to root, and we wouldn't need the replacement in the first place. Just think of it as if we didn't root then they took our 340 dollars for nothing, and i count that as
. They deserve revenge for the people who wasted their money on the lies they sold us...
Back on topic: So do ROMs from Ideos X6 with touchscreen driver that don't work for us, work for you?
agentc13
Daleks Über Alles
Lying and deceiving to cover up your own mistakes and to get a replacement when you did something to break the warranty isn't revenge, it's fraudulent. I'm not talking about rooting to get rid of issues from the stock ROM, flashing a nb0 from another phone or overclocking and frying your processor are not VMs or Motorola's fault. That sort of thing is purposely taking a risk and you deserve losing whatever you paid if you do it. It is completely different than rooting to get rid of alog files that eat up your internal memory or getting a replacement because the charging port doesn't work.
), and lets stop derailing this thread.
tusing
Android Enthusiast
When you flash a (ICS?) ROM with a working camera, try using logcat to see what happens when you open the camera app. I think this would really help the guys over in the CM9 development thread- maybe we aren't too far from a working camera.
Odds are, if you were able to flash the Gingerbread version of a ROM for a phone, you should also be able to flash the ICS version.
Odds are, if you were able to flash the Gingerbread version of a ROM for a phone, you should also be able to flash the ICS version.
Every x6 rom I have flashed, mostly stock, works like a charm, some are more responsive but none are as bad as my Intercept. LOL.
Hey, guys. There are so many custom roms for all the different phones, at different sites, that it is hard to keep up. If you want me to flash a rom or get logcats, point me to the thread and let me know what filters if any, that you want.
Now that I have almost every file off this phone I have been focusing on sorting through everything, So the phone is just sitting idle, ready to be flashed by request.
I'm doing this for the devs, and to get a hands on with the android operating system and devices. I know a lot of the devs and modders don't get in to the source code side, so I figured they would be more comfortable with picking apart and editing files from the nandroid backups.
Austrie
Android Expert
Tell me if the touchscreen work in this ROM [rom] miui v4 ics (updated - better one!!!) - xda-developers
marc12868
Android Expert
There isn't an FB0 ICS rom that has a working camera though.
I started with a fresh flash of Mi410 - GingerBread_FB0-318D-0-5012-A03 for both update_miuiv4_fb0_2.2.17-revised and update_miuiv4_fb0_2.2.17-redo. Also, I used the cwm-recovery-fb0-v2 , but I usually use recovery-cwm-5.0.2.6-triumph for most of this stuff.
So, I installed both, and right off the bat no, but the soft keys worked. On page two there is update-kernel-fixtouchscreen and that fixed it. There was no camera, HDMI, and haptic feedback didn't work but when I connected to wifi, it vibrated when I typed the pass code. The usb mounted very quickly, couldn't see anything else I could test that you don't have working.
Anything else you need?
Chairshot215
Android Expert
Probably depends on your level of shady. VM just wants to get a phone in your hands as quickly as possible because without a contract there is no guarantee that if you purchase a new phone they will continue to receive your monthly payment. Motorola on the other hand has already made all the money they can when you purchased the phone. Either way part of my job is to test returned Pidion PDA's and most companies will not put in the time testing for stupid user issues and will most likely hard reset the device and re-flash the most updated firmware before even looking the device over so as long as you don
tusing
Android Enthusiast
Link to the latest prl please? What happens?
So, what kinda goodies you got for me? I think it did change the partitions, cause looking through the stock logs it says No such file or directory, Not granting permission, Error in initializing QCRIL CM, GW SIM(sec): Not ready --> Not ready, CDMA SIM(sec): Not ready --> Not ready, and a few others. Also, at the beginning of the radio log it says, RIL <--- CM_PH_EVENT_PRL_INIT(69670), but further in it says, RIL_REQUEST_CDMA_PRL_VERSION 8888.
Any ideas how to open the Unknown Partitions, File -sL says "DATA", so I'm thinking RAW maybe? Any suggestions on possible programs that might gain access? Check out the screenshot.
I am assuming you mean to try that PRL on the MIUI rom, right? I have 60686 that Mobsterergunz posted, but have only tried it with the stock rom.
After searching for PRL 21085, I found this at xda "No and these prls you're describing have no 3G data roaming. Also are no differences between 21086 and 60686. We've already checked"
Attachments
What is weird is:
1. Disk utilty sees all the partitions, but only reads 7 of the 16.
2. Gparted sees the usb as unallocated.
3. fdisk shows all of the partitions but the unknown results are different than disk utility.
Take a look at the attachment I posted above, and let me know what you think
1. Disk utilty sees all the partitions, but only reads 7 of the 16.
2. Gparted sees the usb as unallocated.
3. fdisk shows all of the partitions but the unknown results are different than disk utility.
Take a look at the attachment I posted above, and let me know what you think
RussianBear
Lurker
agentc13
Daleks Über Alles
It looks to be from a Cherry Magnum phone.
RussianBear
Lurker
i see. do triumph users have access to similar hex and mbn files for their phones?
marc12868
Android Expert
nope. unless someone could somehow create an .nbo file...
I need somebody to hook their phone up in bootloader/download mode to a linux box and run the file manager as root to see the original partition names. Using Nautilus it says 34MB Filesystem but as root it says 3ce0a72a-54db-4aa6-995b-a414e87238af.
Just want to see what the regular partitions are named, other than mobile, cache, caivs, and userdata. Don't know if this changes with each device or not but, mine are :
16efd6ae-bd14-47a5-bdcf-0b67c9ed80e9
306b94c1-4e3a-43b4-a9a2-5457c99a933d
3ce0a72a-54db-4aa6-995b-a414e87238af
Most of the files on the partitions can be put in a .7z as root, but one I had to tar.7z. I would like to be able to get us a full partition backup without the meid changing, but I believe that data is stored in one of the "unknown" partitions.
Just want to see what the regular partitions are named, other than mobile, cache, caivs, and userdata. Don't know if this changes with each device or not but, mine are :
16efd6ae-bd14-47a5-bdcf-0b67c9ed80e9
306b94c1-4e3a-43b4-a9a2-5457c99a933d
3ce0a72a-54db-4aa6-995b-a414e87238af
Most of the files on the partitions can be put in a .7z as root, but one I had to tar.7z. I would like to be able to get us a full partition backup without the meid changing, but I believe that data is stored in one of the "unknown" partitions.
ok, when ubuntu mounts partitions that it does not know the filesystems name it will mount them using the blkid, this is what you are seeing them mounted as. if you use the command line and run sudo blkid it will print out the blkid of all known block devices(drives, partitions) as well as list what device they goto. if you look at my thread you will see the 2 different layouts, CM7/CM9 remove the partition labels but the partitions still remain for the same uses.