Related
Am I missing something on this new WP7 ROM that's been leaked.
All this trouble trying to get the ROM working on a HD2, hasn't Tom Codon already shown a WP7 on HD2 and said it's running? If that the case then why isn't he sharing how he managed to do it without this Jtag thing.
Or has he now been proven a liar?
Logicalstep
Well, as far as I remember he did it using that JTAG thing and somewhere in the new thread it was mentioned that he used a different (older) ROM as a basis, so drivers, etc. might be different.
The reason for needing JTAG is, that until it flashes correctly we most likely will brick the device several times - using JTAG means we don't have to be a new HD2 for every attempt (which is indeed more cost effective).
If Tom managed to do it then or not is still to be seen.
How can somebody still think that it wasn`t fake? Tom is not active even on his forum /htcpedia/...
i know there isnt a root for the evo with 2.3 yet but im just curious why not
If you think you can do it..by all means...it takes a lot of work to find a root. Ways that use to work get fixed by companies...basically it boils down to detective work which cannot have a time table and takes a incredible amount of patience and brainpower..along with luck. Basically it boils down to finding a exploit...a way to somehow get foot in door...then once that is done...exploring the exploit for options to elevate privileges to get temp or permanent root. How they do this takes time..and a lot of tinkering. And once the root method is out...companies fix it and the game starts all over again.
ok cus i was just wondering if htc blocked it for some reason
Companies do block it..but mostly for security reasons..the same exploits used for rooting also can be used for malware and some nasty other type of software...spyware and so on.
ok thanks i was under the assumption that thats the best part of android, to you know mess with it and mold it and hack it .....thats why android is suppose to be better then apple as well as different....oh well we cant have everything
thanks for clearing it up though
as its been said, this stuff takes time, and luck, and sometimes not even that works,,
i believe they have made some progress, monitor the irc channel yourself during nights and you can see some chatter about it, but it looks like its not quite ready and/or stable as of yet, though i hear the hboot problem has already been beaten...
we shall see, just be patient and try to not make the mods work more by asking this questions in a separate thread, you could have very well asked this in one of the other ones talking about this
deanventure said:
ok thanks i was under the assumption that thats the best part of android, to you know mess with it and mold it and hack it .....thats why android is suppose to be better then apple as well as different....oh well we cant have everything
thanks for clearing it up though
Click to expand...
Click to collapse
I wouldn't call it a part of Android since every non-Nexus/dev Android phones required the exploitation of the software for root to be possible.
Sent from my Nexus S 4G using Tapatalk
Actually I think its all non samsung phones. But of course I could be totally wrong.
deanventure said:
ok thanks i was under the assumption that thats the best part of android, to you know mess with it and mold it and hack it .....thats why android is suppose to be better then apple as well as different....oh well we cant have everything
thanks for clearing it up though
Click to expand...
Click to collapse
Android itself is open, but any phone that the carriers and manufacturers have control over generally gets locked down. The Nexus phones are the notable exception, and are intended for use by developers and tinkerers. In particular, the bootloader is locked down to prevent you from tinkering. However, there's been a big push to get manufacturers to release their phones in way where the bootloader can easily be unlocked. Many have stated they will move in this direction, but it's a recent development. I'm also still not fully convinced the carriers won't try and succeed in blocking it, but getting the manufacturers to commit to it is a great start.
Until then, we have to rely on an exploit, which for almost all versions of almost all phones, they've been able to do. But it isn't necessarily easy. You still have FAR more customization and tinkering opportunities on Android even without an unlocked bootloader, but once you have that, yes, you can tinker with Android in ways you couldn't even imagine with Apple.
I don't see how this is legal. We're paying on average $300-$500 for phones, that are mini-computers. I can pay that for a laptop and get a mobile usb stick for it on the same carrier, and I have many options of Operation Systems to put on said laptop, even though it's an HP, or a Dell, or a Chinese Knockoff.
Same with Sony and XboX, such Bullcrap!
Would it be any way possible to get android (froyo) on the kin two? Its a really nice phone, not to mention that it doesn't require a data plan from verizon . I dont care that wifi is needed for internet access just that android on this thing would make it amazing. I am pretty decent at computers and stuff so if I know how to root it I may be able to develop my own software for it based on another package....
That is a wonderful idea and I would like to help you procced. The problems are we dont know how to boot the KIN into recovery. If we can figure this out were home free. Feel free to ask and Ill do anything to help.
controol shift r b i think its on the forums somewhere
Thats to reset to the origonal KIN software not a recovery mode.
How about APX Mode?
WEM97 said:
Thats to reset to the origonal KIN software not a recovery mode.
Click to expand...
Click to collapse
How about APX mode does that help?
Why would someone want android on it? i highly doubt its processor could handle it.
DustinWolf said:
Why would someone want android on it? i highly doubt its processor could handle it.
Click to expand...
Click to collapse
According to Wikipedia the Kin has a Freescale i. MX31L processor ARM Core nVidia Tegra APX 2600, which is dated now,but if it were to be hacked it could most likely run Froyo and/or Gingerbread (maybe). And according to documentation found on Android website, the Kin fits the profile for Gingerbread.
I have some thumb rule, never update to the newest firmware, and reed the comments. Also at home I have a router, that the manufacture update the firmware from time to time, but I used to run one firmware before the last one. It just an example, but since all the Lollipop, people complain, so why bother? Can't you wait for a while, till Google resolve all the issues? Do you consider Kitkat was perfect then? Or does Lollipop runs perfect on Nexus 6 & 9? I'm starting to think, it intentionally, like iOS 7 on iCrap 4, on iOS 6 it was fine, just think of it, maybe Google do it intentionally, to make us buy a new device? Or they just do a bad optimization job for older devices, and put all effort toward new devices? Any thoughts? I know we all nexus user, are a free beta testers, but if running latest firmware, means it brick out devices, it's hard to thrust Google like that, so I think it's better to stay on Kitkat till better times.
Sent from my hammerhead using Tapatalk
The people who's tablets work fine (the vast majority I'd guess) don't complain. You only here from the people who have problems.
I've been on lollipop since the preview and it's been great. I'll be flashing 5.1.1 the second it's out. Kitkat is dead to me, and very ugly looking back. It certainly was not perfect.
If my device gets the brick people are talking about it would suck but I really, really doubt it has anything to do with the firmware. Some hardware failure most likely. No reason to stay on an old release.
5.0.2 was horrible. While I disregard majority of users complaining of battery life, some of them weren't spewing nonsense.
5.1 is an improvement. I'm one of the guys who do not post every complaint or dissatisfaction I encounter with the Nexus 7. I know what the problem is, I know where to ask for help to pinpoint the cause, now it's my turn to make a decision, stay on Lollipop? or revert to KitKat? Or remove the cause, in other words the app itself.
Back to the OP, there is no risk updating to 5.x. Your device won't magically break. If you like to play it safe, maybe it's better for you to wait for user feedback and ignore the OTA.
OTA you say...
All I hear ate 2 things "Memory leak" & "Bad battery life", be it Nexus 4, 5 or 7, all after the "Lollipop", ...mostly the "Memory leak thing, that told to be solved after each update
Is it safer to flash from ADB? or the "dead" devices dyed in both ways? be it ADB on clean device, after reset, or just OTA? I personally, never thrust OTA updates, I wish there was an easy way, to make a full backup, like a "Norton Ghost" for PC's, I know it can be done with ADB, the question is, if there's any difference, between flashing "with wipe" or without? or maybe the "dead" devices was : 1. rooted, 2. bootloader unlocked, 3. encrypted, or something else? I mean, Google do test all new FW on real devices? don't they?
I wouldn't take an ota myself. Not because of "the brick," I think thats a hardware problem, I feel it's a cleaner update with fastboot and if something fails I'll know what.
And you can (and should) make full nandroid backups in a custom recovery (cwm, twrp etc.).
But to the poster aboves comment it just goes to show you people are having different experiences. 5.0.2 was fantastic for me, great battery life, best it's ever been actually (still as good on 5.1 ~8 hours screen time over two days.)
The memory leak was/is a problem. Oh no I had to reboot once a week. Huge headache. On 5.1 I'm at 270 hours uptime and system ram's at 479. It is creeping up slooowly but better than 5.0.2
I guess it depends what you do with the tablet and especially what apps you have installed. I use my **** pretty heavily though so I don't know why I'v had no problems.
donisan969 said:
OTA you say...
All I hear ate 2 things "Memory leak" & "Bad battery life", be it Nexus 4, 5 or 7, all after the "Lollipop", ...mostly the "Memory leak thing, that told to be solved after each update
Is it safer to flash from ADB? or the "dead" devices dyed in both ways? be it ADB on clean device, after reset, or just OTA? I personally, never thrust OTA updates, I wish there was an easy way, to make a full backup, like a "Norton Ghost" for PC's, I know it can be done with ADB, the question is, if there's any difference, between flashing "with wipe" or without? or maybe the "dead" devices was : 1. rooted, 2. bootloader unlocked, 3. encrypted, or something else? I mean, Google do test all new FW on real devices? don't they?
Click to expand...
Click to collapse
Hard bricks have been reported from both OTA and ADB updates, but very seldom from users of custom ROMs... Most likely cause is eMMC failure due to faulty hardware, though the issue is present on nexus 4 and 5 as well... Possibly faulty bootloader software too.
^Bootloader faults could be possible.. that has pretty low level access. I don't know low enough to corrupt the chip. I don't know. Asus/google probably does but guaranteed you'll never hear a word from them.
I hope it's not something like the infamous s2 brickbug. Then you're just playing russian roulette. Maybe entropy can help lol.
What emmc chips are the 4 and 5 using? I'll have to look.
I'm not sure this is true but if you use Greenify I think the memory is kept in check better, although it requires root. I still see the occasional launcher redraw but not nearly as bad as it was in 5.0. I was on 5.0.2 for several weeks and wouldn't have updated if I hadn't read about the hardware failures.
Well if you don't update your tab, than you don't need a Nexus, buy some cheap chinese tabs for 70-100$, almost all of them are on kitkat, most of them vanila android, no updates, and they all work fine.
This is Nexus.It's a developers tab, for testig, trying, people who like the freshest system on their device, who like clean android....if something's not working, there's always an image of the old system or a bunch of ROMs to test and use...
I know, I myself for now test windows 10 on work PC, and a server 10 preview, but computers and tablets are different things, because you not have that much control for both. All I say, is, that I see same threads for any nexus device, I had a Galaxy nexus before, so I know. About s2, there was a rumor about some other Samsung devices back than.
Sent from my iPhone 4 using Tapatalk
donisan969 said:
I know, I myself for now test windows 10 on work PC, and a server 10 preview, but computers and tablets are different things, because you not have that much control for both. All I say, is, that I see same threads for any nexus device, I had a Galaxy nexus before, so I know. About s2, there was a rumor about some other Samsung devices back than.
Sent from my iPhone 4 using Tapatalk
Click to expand...
Click to collapse
Device OEM is irrelevant in that regard, the quality of internal components is really the crux of understanding hardware failure IMO. of the major android OEMs, all of them have in the past put forth devices that were predisposed to early hardware failure, mostly due to choices of components used during the manufacturing process. Hardware revisions on individual devices of the same model is also a valid form of comparison.
This is a followup to an earlier post in another area and I've been advised I'd be better served to ask it over here in this area of the forum subset...
(Warning: Antique Phone Issues) - Moto Droid Turbo 2 Firmware update(Nougat 7.0)
I have perused the forums here and there seems to be some answers, but I am a noob, so I am trying to clarify some stuff for my own knowledge. I am NOT a developer and know an insignificant amount of info on phone rooting, bootloading, etc. This...
forum.xda-developers.com
I followed the basic steps provided and my PC doesn't see the phone connected to it, even after I've done the steps and uploaded the Motorola drivers, LMSA, etc on the PC. I am just dumb(again) and really don't know wtf I'm doing with this software/phone so before I brick it, I wondered if anyone would be interested in updating the software in my phone for a nominal fee? Common sense tells me that those that do this regularly can probably do this in a matter of a few minutes. If you are local(Indpls, IN), I can bring it to you, but I really don't want to spend a lot of money dicking around with an old phone. I hate to throw away this good(but old) phone, but Is there any interest in something like this? I am really fighting my common sense here and probably should just be getting rid of it and moving on. Thoughts?
88_pacifica said:
This is a followup to an earlier post in another area and I've been advised I'd be better served to ask it over here in this area of the forum subset...
(Warning: Antique Phone Issues) - Moto Droid Turbo 2 Firmware update(Nougat 7.0)
I have perused the forums here and there seems to be some answers, but I am a noob, so I am trying to clarify some stuff for my own knowledge. I am NOT a developer and know an insignificant amount of info on phone rooting, bootloading, etc. This...
forum.xda-developers.com
I followed the basic steps provided and my PC doesn't see the phone connected to it, even after I've done the steps and uploaded the Motorola drivers, LMSA, etc on the PC. I am just dumb(again) and really don't know wtf I'm doing with this software/phone so before I brick it, I wondered if anyone would be interested in updating the software in my phone for a nominal fee? Common sense tells me that those that do this regularly can probably do this in a matter of a few minutes. If you are local(Indpls, IN), I can bring it to you, but I really don't want to spend a lot of money dicking around with an old phone. I hate to throw away this good(but old) phone, but Is there any interest in something like this? I am really fighting my common sense here and probably should just be getting rid of it and moving on. Thoughts?
Click to expand...
Click to collapse
Windows 10?
might work easier if the Phone is in fastboot mode first.
sd_shadow said:
Windows 10?
might work easier if the Phone is in fastboot mode first.
Click to expand...
Click to collapse
Sorry, I forgot to udpate on the OS. It's old Windows 7(trying to keep it simple) and I tried to do the fastboot mode mode and it didn't seem to see it even after that. The phone doesnt acknowledge that it is in fast boot mode though when it turns on(does it normally say something?) after doing it. I am positive I'm an idiot and doing it wrong.
I am also wondering if there is possibly something wrong with the motherboard because the phone doesn't advise it is on a 'quick charger'(OEM Motorola cable and power supply) when I plug it in. It seems to charge just fine though. Weird...
88_pacifica said:
Sorry, I forgot to udpate on the OS. It's old Windows 7(trying to keep it simple) and I tried to do the fastboot mode mode and it didn't seem to see it even after that. The phone doesnt acknowledge that it is in fast boot mode though when it turns on(does it normally say something?) after doing it. I am positive I'm an idiot and doing it wrong.
I am also wondering if there is possibly something wrong with the motherboard because the phone doesn't advise it is on a 'quick charger'(OEM Motorola cable and power supply) when I plug it in. It seems to charge just fine though. Weird...
Click to expand...
Click to collapse
Is this a Verizon-branded device?
Yes, I did follow the Verizon specific instructions too.
88_pacifica said:
Yes, I did follow the Verizon specific instructions too.
Click to expand...
Click to collapse
So you are using this? http://www.motorola.com/VerizonSoftwareUpdateWin
Correct...
88_pacifica said:
Correct...
Click to expand...
Click to collapse
Try the regular LSMA version
Sorry if you have Windows 7 you might as well use
RSD Lite
Will do. Thank you...
DId you try these drivers?
Where can I download the USB drivers for my device?| Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.Where can I download the USB drivers for my device?
mobilesupport.lenovo.com
I am sure that you are a guru at this type of thing(obviously) and could build your own phone with all the knowledge you've gained, but I've been fooling with this phone most of the day and am getting nowhere. I am to the point that I would either dump it or send it to you and let you do your magic. Would you want to piddle around with it? I am just too computer illiterate to make this work apparently.
Don't feel like you have to do this or give any more advice. I'm about tapped out now on jacking with this thing and just have to know my limits. I can fix any car(or truck) as I am a former ASE mechanic, but this damm phone has me beat...