Related
I know this topic is kind of frowned on, but bear with me, I'm doing it for legitimate purposes.
I just picked up a used sprint CDMA hero for use on my Carolina West plan. I rooted the new hero, put it in diag mode so that I could manipulate it with CDMA workshop 3.5 and Qxdm. My wife has a Carolina West Hero, so I was able to pull the PRL off of it and load it to my Sprint Hero. I also copied all of her NAM and EVDO settings to my phone and set my MSL/SPC to match Carolina West's, while giving it my phone #.
At this point, the phone's pretty much provisioned for Carolina West. So, I take it to one of their retail stores and they refuse to add the ESN to their database although its common practice with other carriers like Verizon.
I already have a data package for WAP browsing on my current phone, so I thought I'd try to change the ESN/MEID on the hero just to see if I could get it to work. Not hurting or defrauding anybody.
As I stated earlier, I used my licensed copy of CDMA workshop to change all of the EVDO, NAM, MSL, etc. However, it fails every time I try to change the ESN or MEID. I also read up on QXDA. As with CDMA workshop, I can read/change Nam stuff etc. but when I go to the Memory Viewer, all of the information on the screen is greyed out and the only address I can access is 0x00400000. And, since it returns all 0's for everything, I don't think it is actually reading the phone's memory.
Without discussing any legal implications, can someone please share ideas with me as to why CDMA Workshop and QXDA can't access the phone's memory even though they are supposed to be able to?
Thanks a million guys, I've learned more here so far than every other phone forum put together.
Only thing I can think of is restarting computer / phone...
I wouldn't be posting anything about this stuff on this site, I'm sure if you googled meid and hero you'd find a site that is a bit more accepting of this stuff.
I had already thought of that. I restarted the computer and both phones several times. For a "control group" I also tried to see if I could read the memory on the other Hero. Neither will allow it (in either CDMA workshop or QXDM).
Do you think flashing to an earlier software revision would do me any good? The sprint one is at 1.56.651.2 and pri 1.70_003. The other one is running something newer and proprietary (much like what I've read about Cellsouth, Bluegrass, Appalachian, Alaska, etc.).
Actually, this is the most accepting forum I've found so far. Thats why I chose this forum to ask. This is where I found most of my research on ESN/Meid.
If you have any suggestions of somewhere else to look/ask please post...or shoot me a PM.
I also did alot of reading at Howard Forums, Mobile Files, CDMA gurus, etc. but the information on the subject was really more clear and coherent here.
This forum is just more accepting because a mod hasn't come across your post yet. There are too many sections and most of the sections do not have individual mods for that section only. So it is a bit harder to police.
Anyway... you can try searching google for "esn repair" rather then "change esn". Unfortunately we can't help you any further. I only know the basics and not the details of the programs since I never had a reason to do that. There might be 1 or 2 people on these forums who could truly help you.
However, no one can post anything more because it would mean a ban and this thread deleted. Even though you have a good reason to do so, changing your esn is illegal and almost any forum out there will strictly get rid of posts that talk about it because they don't want to be shut down.
Its not like this is one of the thousands of posts out there asking "how do I change my esn". That information is fairly readily available.
Instead, if you read my post you'll see that I'm asking for some troubleshooting help to try to determine why my device isn't functioning properly and a spitballing of ideas as to how I can get it to work (ie...possibly rolling back to a previous software revision). I just filled in the backstory, because I felt it was pertinent information (showing that I can make writes to all areas of the device with various programs) just not the ESN/MEID.
Though, some would frown on what I'm trying to accomplish, I haven't asked for any illegal information...just troubleshooting help to figure out why my device isn't behaving properly. I don't know of any forum that would delete a post and ban somebody for asking for troubleshooting help, thats why the forum is here.
Muleguy said:
Though, some would frown on what I'm trying to accomplish, I haven't asked for any illegal information...just troubleshooting help to figure out why my device isn't behaving properly. I don't know of any forum that would delete a post and ban somebody for asking for troubleshooting help, thats why the forum is here.
Click to expand...
Click to collapse
I know where you are coming from. All I was trying to say is that many forums will error on the side of caution and get rid of these threads.
I am not sure if there was a bunch of forums that got shut down that has brought the fear of god into the forum operators or what. I know forums get shut down all the time for warez(not just android) but I am not sure why they are so fearful about the ESN issue.
I think it is because a shutdown notice can be sent to the hosting site and the hosting site will blindly comply without looking into the issue. So the owner/operators of the forum have no say in the matter and can't argue their case.
Are you using a laptop? I had that problem, so used a desktop. Then after that it worked with the laptop. It is pretty simple thing to do.
-------------------------------------
Sent via the XDA Tapatalk App
Good idea aven. That is one of the things though that struck my mind late last night, although for a different reason. I was originally trying on a laptop running Win 7 Pro. Sometimes Win 7's a bastard about running programs designed for legacy communications. So, I installed the programs onto my desktop which is still on Win XP pro. Well, at least I was able to try QPST and QXDM on the desktop. My CDMA workshop license is tied to the laptop.
Anyway, I got the same errors on the desktop that I did the laptop.
And back to the idea I had about going back to a earlier software version, then attempting it...that didn't work too swimmingly either. In trying to research what earlier stock versions there were, I found that some Heroes came out with 1.29 and some with 1.56. Once a phone is at 1.56, it can never go back to 1.29. I don't know the history of this phone, if it came out with 1.29 or not, but either way its at 1.56 now. Either way, I reinstalled the stock 1.56 RUU which unrooted the phone. I haven't had time to root it again yet. But, with the stock 1.56 on, I still got the same errors when messing with the ESN/MEID.
I posted on another forum in the post that details this method asking if it can be confirmed that they are in fact changeable in 1.56. I also found some information about people using MTTY to log communications during this process. That is what I plan to do next.
Can anyone here confirm that they've seen it done on a Hero at 1.59?
Are you using the HTC usb data cord or a regular one? Could be worth looking into
Have you set up your ports in QPST Configuration? That solved my problems I think.
-------------------------------------
Sent via the XDA Tapatalk App
Are you using the HTC usb data cord or a regular one? Could be worth looking into
Click to expand...
Click to collapse
Yep...using the data cable that came new in the box with my wife's Hero.
Have you set up your ports in QPST Configuration? That solved my problems I think.
Click to expand...
Click to collapse
Yes, while using QXDM, QPST is configured properly. I can use it to write to NAM, EVDO, etc., just not ESN/MEID. If the port isn't connected in the QPST configuration, QXDM won't even behave like a phone is there.
In CDMA workshop, the program itself grabs the com port. I've forgotten before and left QPST server running while opening CDMA workshop. When that happens, QPST has the port locked so that other programs (apart from QXDM) can't access it. At that point I have to shut down QPST server before I can connect the port in CDMA workshop.
Actually, I ran into the same problem when I tried what I mentioned earlier. I tried to connect the port in MTTY to log the communications. But then, I wasn't able to use CDMA Workshop or QXDM because MTTY had the port locked.
Were you ever able to find a solution? Stuck here as well.
Lets just say programs like DFS and CDMA Workshop have come light years since this thread was started.
I need to find the new versions then. I was one of the first to do it after the 2.1 update that I could find. Now I'm wondering if I could do it to a newer HTC phone
Sent from my HERO200 using XDA App
Hi i have searched the forum but not found, i think my web browser is messing me around as every time i try and search it gives me an error.
Basically I'm selling my tab, so to avoid problems in the future i want to put it back to stock. It was originally a UK unlocked tab with no network touching it.
Can someone either explain what i need to do, or forward me to the correct post?
Thanks for your help
Just reset your Tab to stock in settings and erase contents of SD card.
Have you ever thought that maybe someone out there prefers to buy a modified Tab? Consider the fact that for some, it's not easy to replace the FW/ROM.. If you're lucky, you might even get a few extra for the custom ROM.
Do you have a cdma or gsm tab? Procedure is a bit different.
Where is the firmware stored (ie chip)
Inside the Chromecast? My thinking maybe off but is it possible to have the unit boot and load the firmware we want if the firmware is manually written to memory? I have not found much information on the JTAG port, but I see it also has 16gig TSOP as well with a 4 or 8 gig DDR memory. I assume the DDR is used for a buffer for the CPU and the memory in the CPU is for storing the bootloader . so hoping the TSOP is where the firmware is stored. If we were able to write the firmware there would we be able to achieve our needed root, or would the current firmware on the chip be useful for finding an exploit to root?
Would think unless we are changing the bootloader when we root the unit now at low serial numbers I would think it would be the same as is writing a ROM to a phone and using a factory bootloader.
Correct me if I am all messed up here please.
1080xt root 12.15.15
rekids said:
Where is the firmware stored (ie chip)
Inside the Chromecast? My thinking maybe off but is it possible to have the unit boot and load the firmware we want if the firmware is manually written to memory? I have not found much information on the JTAG port, but I see it also has 16gig TSOP as well with a 4 or 8 gig DDR memory. I assume the DDR is used for a buffer for the CPU and the memory in the CPU is for storing the bootloader . so hoping the TSOP is where the firmware is stored. If we were able to write the firmware there would we be able to achieve our needed root, or would the current firmware on the chip be useful for finding an exploit to root?
Would think unless we are changing the bootloader when we root the unit now at low serial numbers I would think it would be the same as is writing a ROM to a phone and using a factory bootloader.
Correct me if I am all messed up here please.
1080xt root 12.15.15
Click to expand...
Click to collapse
That pretty much what FlashCast did until Google plugged the hole that would let you hijack the boot process....
I don't know how diligently some have been looking but since Google plugged that hole there seems to be no way into the CCast anyone can find.
rekids said:
Where is the firmware stored (ie chip)
Inside the Chromecast? My thinking maybe off but is it possible to have the unit boot and load the firmware we want if the firmware is manually written to memory? I have not found much information on the JTAG port, but I see it also has 16gig TSOP as well with a 4 or 8 gig DDR memory.
Click to expand...
Click to collapse
It was written elsewhere that the gtvhacker team found the JTAG pins are disabled at the hardware level.
There was also mention that there may be a device-specific encryption, but no confirmation on that. Someone with an eeprom programmer and soldering station who can swap chips would have to confirm.
That I have (chip programmer and soldering station) just have not decided if it was stored on the 48 pin TSOP as that is the easiest to gain access to. This one of couple of things I would need to know or at least have a good idea about before tearing my noon rooted unit apart for.
IF ... The firmware is stored there and I had an image of the Eureka firmware that needs to be on the TSOP then tearing it apart is worth the test. I don't see the software being encrypted to the device since JTAG has been disabled seams like a lot of work and keys needed for a simple device and low cost but I could be wrong. The other thing I would need to do is go through the data sheet on the TSOP to see if it has a write once area or a locked portion that would require a key from CPU to allow writing, but kinda doubt that.
So if some one has info on the actual image preferably a .bin image of eureka in the correct data location would be great.
My thought is if it is that simple then ISP maybe possible for the average tinker with a simple chip programmer or even make it possible for some one to program on a larger scale for a small fee of like $5 or $10 instead of $100 on EBay or finding the last few with old software out there.
1080xt root 12.15.15
I like this thread hopefully it will be cracked open...just like the ps3 was miraculously despite many theories that it was impossible to hack even after sony plugged the holes again and again
Sent from my Nexus 5 using Tapatalk
Just a small update. Removed the TSOP and went to read it using factory default settings and found the first 141 bocks are invalid and the rest of the chip was blank "FF". Changed the settings to not skip over the 141 blocks and got a 2 gig data file. Not sure if this a good thing yet need to sort through to see if any of the data is intact valid. My Chromecast is using current firmware. The TSOP does hold 16gigs of data. Only data seen so far is up to data block 3F3C000 then blank from that point on.
Could really use another TSOP from another Chromecast even a dead one for comparison.
1080xt root 12.15.15
Not sure, but maybe @Team-Eureka has a dead CCast they can donate/lend to your effort...
Need some help from some one who knows a few things about the Chromecast.
What I able to do right now is read and write what ever is stored on the 16 gig TSOP that is in the Chromecast. As far as I can see this is where the firmware should be stored.
The idea is to write the firmware that is desired to the TSOP and have the Chromecast boot that software instead.
Problem ... The data that is recovered from my Chromecast that is up to date has about 200-500 MB of data towards the beginning of the blocks and a few more MB just before the end of the blocks. The total .bin file is about 2.2 gigs. When viewing the contents of the .bin there is no readable text (example "Google , version, build" and so forth) and there is usually at least something in text format when viewed in WinHex of other devices that I have read and written to in the past.
What I don't know is where exactly is the TSOP the firmware begins or ends, location of checksum (s) and an image of Eureka firmware as it is written on the TSOP.
Possible solution is a TSOP that has had the firmware already loaded or an image of that TSOP or possibly even the rootable firmware image.
Any help is great. I have been on the IRC channel of Eureka and Gtvhacker and asked there but had no response.
The programmer I have is an older Dataman 48pro (newer version is more efficient and does multiple chips at once) it is very reliable and takes about 20 minutes for a complete read of the 16 gig TSOP. The chip does need to be removed and placed in the adapter to read since ICP is not spotted by the TSOP and from my research the JTAG or UART has been disabled I suspect with in the processor.
Any one with info or even idea would be great.
Thanks
Rekids
Team Eureka hangs out in #team-eureka though they've been busy lately... Wish I knew more but hardware is my weakness.
bhiga said:
Team Eureka hangs out in #team-eureka though they've been busy lately... Wish I knew more but hardware is my weakness.
Click to expand...
Click to collapse
we are here, we are just quiet NAND dump was sent his way.
Thank you and yes understand being busy, I work 40+ them got stuff I do at home with 4 kids and the wife not to mention I do a few things out of town each week.
I did get a full NAND image just got to compare with the read I got and see if there online with each other as to location and type of code in case it is different after it passes through the CPU.
Will keep you posted, as to findings.
1080xt root 12.15.15
Just in case of anyone is following this,
I did get the bootloader downgraded to a TOtable version written on the NAND. Down side is was not able to get the NAND remounted well enough for a boot without some liquid flux I had lost around the house some where so ordered some more. It is definably possible to change all the data in the NAND with a programmer but the NAND has to be removed from the PCB and then remounted. But have to wait for supplies to show up and then a day I can play around with this project again.
The Chromecast I am working with is one with the serial number of 3B and it has updated to the the most recent firmware.
Any how will post when I have it boots again
1080xt root 12.15.15
rekids said:
Just in case of anyone is following this,
I did get the bootloader downgraded to a TOtable version written on the NAND. Down side is was not able to get the NAND remounted well enough for a boot without some liquid flux I had lost around the house some where so ordered some more. It is definably possible to change all the data in the NAND with a programmer but the NAND has to be removed from the PCB and then remounted. But have to wait for supplies to show up and then a day I can play around with this project again.
The Chromecast I am working with is one with the serial number of 3B and it has updated to the the most recent firmware.
Any how will post when I have it boots again
1080xt root 12.15.15
Click to expand...
Click to collapse
Wow, great work [emoji3][emoji106]
Although, this is a method what only few users might use, I'm glad to see someone doing this kind of stuff.
Eagerly waiting to hear if you manage to pull it together and eventually root your device [emoji2]
Sent from my Nexus 4
Can't wait to hear your upcoming updates either. Good work
Sent from my Nexus 5 using Tapatalk
rekids said:
Just in case of anyone is following this,
I did get the bootloader downgraded to a TOtable version written on the NAND. Down side is was not able to get the NAND remounted well enough for a boot without some liquid flux I had lost around the house some where so ordered some more. It is definably possible to change all the data in the NAND with a programmer but the NAND has to be removed from the PCB and then remounted. But have to wait for supplies to show up and then a day I can play around with this project again.
The Chromecast I am working with is one with the serial number of 3B and it has updated to the the most recent firmware.
Any how will post when I have it boots again
1080xt root 12.15.15
Click to expand...
Click to collapse
lots of us are following.
this is great news.
but yes only for advanced users. but once it is perfected a clip could probally be made like the ps3/360 nand clips
Just to be sure every one is aware all thanks goes to those who really deserve it Gtvhackers for the original and only exploit that we have, and every one at Team Eureka, and above all else a very helpful and encouraging person who has helped with the vital info that was needed and willing to spend time helping me out and not knowing a thing about me (just a noob)
Thanks ddggttff3, for the help so much.
1080xt
Could this be used to flash the tsop without desoldering?
http://www.ic2005.com/shop/product.php?productid=137&cat=0&featured=Y
I've been out of the modding scene for years and haven't kept up.
Sent from my Nexus 4 using Tapatalk
Looks like more a way to connect while mounted then a way to program. The NAND requires a particular set instructions to do anything really. The way I understand what needs to happen to program and write are a couple of things,
1 connection to the right pins (obtain with the item you mentioned our to place in a adapter with individual connections for each pin)
2 uninterrupted communication (may have issue with resistors, caps, CPU and any other items on board connected to NAND)
3 instruction set for communication to the NAND to have it do what you want.
I have not come across anything as of yet suggesting in In circuit programming is possible out side of the use of the UART or JTAG. And since as far as I can find the correct set of UART pins are not connected and the JTAG is either disabled or not connected makes in circuit programming not possible as of right now.
A data sheet on the 88DE3005 has not been found by me as of now. Marvell seams to keep that info unavailable to us.
A map out of the armada mini would be great and a pin out of the board connections would help to see if that would be possible in the future.
1080xt 4.4
So got my stuff to remount the NAND with the changed bootloader to the exploitable one and .. no boot. Not sure what exactly went wrong got a sneaky feeling it may have died during the attempt to remount before I got my stuff with a big fat solding iron. Gonna go get another and try again.
It is definitely easier to remount when you use liquid flux and not just trying to hit each leg with solding iron.
Any news? Have we found a hardware method of rooting?
I've been doing research and experimenting for the past few days, with only 6 hours of sleep in the last 48 hours. Long story short, I had a Droid TURBO on Verizon, loved it, the best phone I've ever had hands down. A month or so into having my Turbo, my family switched to Sprint, rendering my Turbo completely useless as a phone Skip a few more months ahead to 11/15 when I broke my Samsung S6. I was looking for an excuse to figure out how to do this, I'd done a few hours of research, but never really had a reason to attempt what I have been. My goal is to allow my droid turbo to call/text with my sprint number and plan. My first idea was to simply open up some bands, maybe change some APN settings, BOY was I in for a trip. I'm currently running the 5.1 OTA of Lollipop on my Turbo, which means I have a locked bootloader, however I've gotten as far as getting temporary root access on 5.1 OTA (SU3TL-39). I wasn't sure how temporary root worked at first so of course, I was trying to get "XPOSED" working with this temporary root, then I could modify the phones information and trick Sprint into thinking that my Droid Turbo, is actually my old phone. I attempted to change the IMEI swap the two different IMEI's however it was soon after that, that I found out that my temporary root doesn't actually save after a boot, or even in-between roots. Kingroot seems to have to keep re-rooting itself in order to keep it's temporary root alive. Anyways, I've been up all night, and I've got to get to Uni. I'd like to see what other ideas you all might have. At this point I've gotten invested in attempting to find my own method to rooting, or flashing a modified firmware of some type. I'd really like some guidance in these fields even if my Turbo will never work with Sprint. I appreciate those of you who read the post entirely.
EDIT: I've gotten many different theories, but the only way I see myself doing this is by somehow downgrading and starting from complete scratch, maybe even rebuilding the OS just to miss the security update? (All of these things are probably impossible, but I'd really like to think that we can figure something out together instead of letting the TURBO die.)
EDIT 2: ****, I really need to leave, but I had one last idea as I walked out the door, I'm sure it's out of the question, but maybe there's some way to physically modify the TURBO, or even modify the IMEI that the SIM card is looking for in the first place, but all just theories, will come back later with more ideas!
Tabrune said:
I've been doing research and experimenting for the past few days, with only 6 hours of sleep in the last 48 hours. Long story short, I had a Droid TURBO on Verizon, loved it, the best phone I've ever had hands down. A month or so into having my Turbo, my family switched to Sprint, rendering my Turbo completely useless as a phone Skip a few more months ahead to 11/15 when I broke my Samsung S6. I was looking for an excuse to figure out how to do this, I'd done a few hours of research, but never really had a reason to attempt what I have been. My goal is to allow my droid turbo to call/text with my sprint number and plan. My first idea was to simply open up some bands, maybe change some APN settings, BOY was I in for a trip. I'm currently running the 5.1 OTA of Lollipop on my Turbo, which means I have a locked bootloader, however I've gotten as far as getting temporary root access on 5.1 OTA (SU3TL-39). I wasn't sure how temporary root worked at first so of course, I was trying to get "XPOSED" working with this temporary root, then I could modify the phones information and trick Sprint into thinking that my Droid Turbo, is actually my old phone. I attempted to change the IMEI swap the two different IMEI's however it was soon after that, that I found out that my temporary root doesn't actually save after a boot, or even in-between roots. Kingroot seems to have to keep re-rooting itself in order to keep it's temporary root alive. Anyways, I've been up all night, and I've got to get to Uni. I'd like to see what other ideas you all might have. At this point I've gotten invested in attempting to find my own method to rooting, or flashing a modified firmware of some type. I'd really like some guidance in these fields even if my Turbo will never work with Sprint. I appreciate those of you who read the post entirely.
EDIT: I've gotten many different theories, but the only way I see myself doing this is by somehow downgrading and starting from complete scratch, maybe even rebuilding the OS just to miss the security update? (All of these things are probably impossible, but I'd really like to think that we can figure something out together instead of letting the TURBO die.)
EDIT 2: ****, I really need to leave, but I had one last idea as I walked out the door, I'm sure it's out of the question, but maybe there's some way to physically modify the TURBO, or even modify the IMEI that the SIM card is looking for in the first place, but all just theories, will come back later with more ideas!
Click to expand...
Click to collapse
There are two problems that you're up against:
1. The /system partition is write protected. Even with temp root (or permanent root, for that matter), /system cannot be modified. To use anything via the xposed framework, the framework must be installed, which requires writing to /system, which is impossible. The only way around this is the moforoot exploit, which allows flashing of pre-modified /system images, eliminating the need to modify /system while the phone is running. However, this does not work on the 5.1 bootloader, which you have.
2. As you correctly state, the bootloader is locked. That means no downgrading and no flashing of modified firmwares using official flashing methods (fastboot, mfastboot) or non-mofo unofficial methods (TWRP, FlashFire).
This thread discusses hardware modifications. It's way above my head, so I'm not sure how useful it is: http://forum.xda-developers.com/droid-turbo/development/rd-turbo-jtag-emmc-direct-hardware-t3162558.
Hope this is at least moderately helpful.
I suppose there's no way to disguise an exploit within some of the core system files? Since all of these files are signature checked, but how exactly does signature checking work with the Lollipop, I doubt that it would be easy to trick, but maybe some reverse engineering of it? Trick it into thinking that everything is okay even though an exploit is riding alongside a system file.
Tabrune said:
I suppose there's no way to disguise an exploit within some of the core system files? Since all of these files are signature checked, but how exactly does signature checking work with the Lollipop, I doubt that it would be easy to trick, but maybe some reverse engineering of it? Trick it into thinking that everything is okay even though an exploit is riding alongside a system file.
Click to expand...
Click to collapse
Even if that were possible, it would not help you, since that would require being able to write a file to where the core system files are stored (/system). As for how signature checking works, I think it is enforced by whatever is stored on the /boot partition, but I'm not sure about that. A locked bootloader will not allow flashing modified images to /boot, and there are no known ways to bypass this.
When I get home, I'm going to do some experimenting on attempting to strip down and down grade to KK. I know that it most likely won't work, but I will gain some knowledge about it at least.
TheSt33v said:
Even if that were possible, it would not help you, since that would require being able to write a file to where the core system files are stored (/system). As for how signature checking works, I think it is enforced by whatever is stored on the /boot partition, but I'm not sure about that. A locked bootloader will not allow flashing modified images to /boot, and there are no known ways to bypass this.
Click to expand...
Click to collapse
Yep, the boot partition is what would have to be bypassed or unlocked in order to be able to write to system. That is where all the sig checks are locked in, right in the boot partition.
Well, we had a BL Unlock coming to us in a few days, maybe a week or two. With that, you can flash what you need to attempt to use with sprint possibly, depending on the bands the Turbo has
I've gotten the phone to work to an extent, I'm hoping if the BL unlock happens that it will open up lots of opportunity.
i have a google g1 development phone (NOT a T-Mobile google g1 but a phone from prior to that release) and I am not a developer. my phone is progressively losing functionality as i can't load new versions of applications presumably since it is a development phone and licensed applications won't download. i don't need the development capability but would like to restore functionality, like youtube access etc., and also other licensed, purchasable applications.
i am probably in the wrong forum (not being a developer) but it is hard to find anywhere to ask this question and get direction to 'where to go' ... so my apologies, if that is the case.
Nope, this is indeed the proper forum and place to ask
A couple of questions though, is there an android version you want? The newest official update would be 1.6 doughnut but there are custom ROMs that may be better for you and even 2.3 gingerbread runs fairly well on this phone (and has more app choices)
Also to know the best way to change the software we need to know current firmware, can you boot to bootloader and write down all on that screen? (Power on while holding camera button)
response to demkantor
thanks for responding!
if it is possible for me to update the android system, that is great and i don't know too much about the systems to specify my needs in terms of system capabilities. as a user, i am not sophisticated and my main mission was to stop my phone from its progressive decline due to, i think, its inability to update the applications that were initially installed on it [i bought it 'new and in the box', not knowing it was a developer's system].
the parameters that i can access directly from settings ('About Phone') are as follows;
Model number
Android Dev Phone 1
Firmware version
1.1
Baseband version
62.33.20.08H_1.22.12.29
Kernel version 2.6.25-01843-gfea26b0
[email protected] #6
Build number
dream_devphone-userdebug 1.1 UNLOCKED
121975 test-keys
IMEI
351676030141180
IMSI
00
OK, I would suggest a custom ROM which would allow you access to more apps and actually be more stable in many ways then current one
There are multiple methods to do so but in order to allow you to skip a lot of the steps (which I believe you can being a dev phone) I need you to tell me all on the bootloader screen
bootloader screen
demkantor said:
OK, I would suggest a custom ROM which would allow you access to more apps and actually be more stable in many ways then current one
There are multiple methods to do so but in order to allow you to skip a lot of the steps (which I believe you can being a dev phone) I need you to tell me all on the bootloader screen
Click to expand...
Click to collapse
DREA100 PVT 32B
HBOOT-0.95.3000
CPLD-4
RADIO-1.22.12.29
Oct 20 2008
Serial0
Looks like tapatalk didn't let me respond.....
So basically you do have options to do oneclick root apps but in order to use the latest-stable custom ROMs you will need to update firmware anyway
So I would suggest going through the same steps as someone without dev phone
http://forum.xda-developers.com/showthread.php?t=1668524
See these old threads and we have walked people through this many times, but of course if you need a hand let me know where you get stuck
Best of luck!
demkantor said:
Looks like tapatalk didn't let me respond.....
So basically you do have options to do oneclick root apps but in order to use the latest-stable custom ROMs you will need to update firmware anyway
So I would suggest going through the same steps as someone without dev phone
http://forum.xda-developers.com/showthread.php?t=1668524
See these old threads and we have walked people through this many times, but of course if you need a hand let me know where you get stuck
Best of luck!
Click to expand...
Click to collapse
many thanks, ... have browsed those threads and see that i need to do some studying to get a view of the structure of these systems and understand the terminology. i guess the CyanogenMod website is the place to do that?
I notice the link that others used to for their pre-education is no longer viable;
http://wiki.cyanogenmod.com/wiki/HTC_Dream:_Rooting
and there is no HTC Dream listed on the cyanogenmod supported devices.
also, i do not have a dataplan on my service (Rogers), should i be looking for someone to loan me their sim? (i guess i should hold my questions until i have done some homework).
thanks for getting me launched into this!
No problem! It is possible to do things differently than what's laid out in those threads, but I would be most confident using the ol tried and true methods
I've played around with a countless number of these phones for many years and this method always works without hitch so its the way to go IMO
Even if it feels complicated it really isn't much but there can be a learning curve if you are new to this kind of stuff
But to answer your question it is easiest if you can use a sim (this is an unlocked dev phone so any gsm with data plan) but it is not needed as you can bypass the start screen
And I have all files needed on my server as well as other places so if you can't find the right ones let me know and I'll link you
Best of luck!
demkantor said:
No problem! It is possible to do things differently than what's laid out in those threads, but I would be most confident using the ol tried and true methods
I've played around with a countless number of these phones for many years and this method always works without hitch so its the way to go IMO
Even if it feels complicated it really isn't much but there can be a learning curve if you are new to this kind of stuff
But to answer your question it is easiest if you can use a sim (this is an unlocked dev phone so any gsm with data plan) but it is not needed as you can bypass the start screen
And I have all files needed on my server as well as other places so if you can't find the right ones let me know and I'll link you
Best of luck!
Click to expand...
Click to collapse
rgr, thks! when i think i know what to do, i'll post my plan here for critique prior to implementing it.
emeeliano said:
rgr, thks! when i think i know what to do, i'll post my plan here for critique prior to implementing it.
Click to expand...
Click to collapse
Read through this for a good idea on the whole process
http://forum.xda-developers.com/showthread.php?t=2189589