Related
Hi all,
I'm hoping I'm posting this in the right place and with the right format.
I have a rooted T-Mobile Samsung Galaxy S2 device, and after trying to install Villainrom 3.0.0 (VillainROM-3.0.0-signed.zip) through the Clockworkmod recovery console, it is completely bricked. Installation said it finished successfully, I then chose 'Reboot' through the CWR console, and the device went dead.
It won't turn on, or boot into recovery or download modes. I removed the battery and SIM for 10 minutes, and same results. When connecting the device to the computer, I hear the "Device failed to connect" sound. If I try to press the power button, I hear the "device connected" sound followed immediately by the "device failed to connect" sound. The fact that it is responding at all to the USB cable being connected, is the only hope I have left that I can do something about it. Odin does not show it connected though (I saw in another thread that someone was able to use it despite the device not turning on).
I would appreciate any advice before I try ordering a USB jig and / or visiting a support center and hoping they somehow replace it within warranty by making another story.
Next time you should really be careful when installing ROMs................. Make sure they are supported by your phone............... That's all the advice I can give.
Your only options now is to try a USB jig or sending it to a support center so...
Yup, you need to make sure the ROM you want is supported.. other than our dev section, everything else you will find is for the i9100.
Completely different phone.
I think your only options are jig or warranty
Sent from my SGH-T989 using XDA App
Yeah - this happens when you flash a ROM for a totally different device.
You could try flashing a T989 kernel and see if that helps - but the International SGS2 has a Exynos processor - yours is a Snapdragon - along with some other differences.
You can also try using ODIN to flash a stock tar and ROM back - it's not really bricked - but you'll need to do some reading to hopefully avoid such disastrous results again
I had a previous generic Galaxy S2 and installed roms without a problem. How come the T-mobile is a completely different device? aside from some carrier bloatware, it's basically the same hardware, no? at least everything I read led me to believe that.
How could I use ODIN when the device doesn't respond to any kind of button combo and doesn't go into download or recovery modes? is there a way to force ODIN to recognize a bricked device?
erangalp said:
I had a previous generic Galaxy S2 and installed roms without a problem. How come the T-mobile is a completely different device? aside from some carrier bloatware, it's basically the same hardware, no? at least everything I read led me to believe that.
Click to expand...
Click to collapse
The answer to your question is common knowledge and in fact has already been answered in this thread even. Le sigh.
Sent from my SGH-T989 using XDA App
TJBunch1228 said:
The answer to your question is common knowledge and in fact has already been answered in this thread even. Le sigh.
Click to expand...
Click to collapse
I appreciate everyone trying to help, but this is not very helpful. Obviously it wasn't common knowledge for me, otherwise this wouldn't have happened - and I did read up a lot about this. And where in this thread does it answer about the difference in hardware?
Please bear in mind that I'm not an android developer, so what seem like common knowledge to you about internal difference in devices is not that obvious.
How many times in these forums does it say don't flash if you don't know what you are doing. If you don't know what you are doing ask questions. Maybe bricking your phone will teach you a lesson.
are you able to go into Download mode with a USB Jig?
(you can always make your own if you can add up enough spare resistor to amount 301k)
if you can then you can try flashing the stock Odin ROMs
erangalp said:
Hi all,
I'm hoping I'm posting this in the right place and with the right format.
I have a rooted T-Mobile Samsung Galaxy S2 device, and after trying to install Villainrom 3.0.0 (VillainROM-3.0.0-signed.zip) through the Clockworkmod recovery console, it is completely bricked. Installation said it finished successfully, I then chose 'Reboot' through the CWR console, and the device went dead.
It won't turn on, or boot into recovery or download modes. I removed the battery and SIM for 10 minutes, and same results. When connecting the device to the computer, I hear the "Device failed to connect" sound. If I try to press the power button, I hear the "device connected" sound followed immediately by the "device failed to connect" sound. The fact that it is responding at all to the USB cable being connected, is the only hope I have left that I can do something about it. Odin does not show it connected though (I saw in another thread that someone was able to use it despite the device not turning on).
I would appreciate any advice before I try ordering a USB jig and / or visiting a support center and hoping they somehow replace it within warranty by making another story.
Click to expand...
Click to collapse
erangalp said:
I had a previous generic Galaxy S2 and installed roms without a problem. How come the T-mobile is a completely different device? aside from some carrier bloatware, it's basically the same hardware, no? at least everything I read led me to believe that.
How could I use ODIN when the device doesn't respond to any kind of button combo and doesn't go into download or recovery modes? is there a way to force ODIN to recognize a bricked device?
Click to expand...
Click to collapse
Hmm - well let's see... a simple Google search to compare the phones would tell you that it's definitely not the same device. A little more reading might be in order though...
1. different screen sizes
2. different SoC (system-on-chip, i.e. processor)
3. different basebands/radios
4. etc.
All of those combine to a different device.
Now as relating to ODIN - I honestly don't see why you couldn't get into ODIN. A jig might help but I doubt it.
erangalp said:
I had a previous generic Galaxy S2 and installed roms without a problem. How come the T-mobile is a completely different device? aside from some carrier bloatware, it's basically the same hardware, no? at least everything I read led me to believe that.
How could I use ODIN when the device doesn't respond to any kind of button combo and doesn't go into download or recovery modes? is there a way to force ODIN to recognize a bricked device?
Click to expand...
Click to collapse
With very little research....
Galaxy S2 (International) - i9100
Dual-core 1.2GHz ARM Cortex-A9 processor, Mali-400MP GPU, Exynos chipset
T-Mobile/Telus Galaxy S2 - T989/D
1.5 GHz Scorpion dual-core processor, Adreno 220 GPU, Qualcomm APQ8060 Snapdragon chipset
This difference in specification should be the FIRST thing keeping you away from flashing a i9100 ROM on a T989...
erangalp said:
I appreciate everyone trying to help, but this is not very helpful. Obviously it wasn't common knowledge for me, otherwise this wouldn't have happened - and I did read up a lot about this. And where in this thread does it answer about the difference in hardware?
Please bear in mind that I'm not an android developer, so what seem like common knowledge to you about internal difference in devices is not that obvious.
Click to expand...
Click to collapse
Well - how about this answer given above which does in fact provide the answer for you:
jerdog said:
You could try flashing a T989 kernel and see if that helps - but the International SGS2 has a Exynos processor - yours is a Snapdragon - along with some other differences.
Click to expand...
Click to collapse
How can you know what you don't know? I have previously rooted my galaxy S2 and installed various ROMs without a problem. I now have this new T-mobile device since I switched carriers. I could I know that what worked for my previous Galaxy S2 won't work for this one? why should I "be taught a lesson"?
I would really appreciate if someone could give me a helpful answer - I can't use ODIN to flash since I can't boot up the device in any mode. Is there any way to make ODIN recognize a bricked device? the computer does make the USB connected sound for a sec there. Please guys, anything helpful instead of telling me how "should've known", because really, if I could I would. Nobody here ever had a faulty ROM installation?
erangalp said:
I appreciate everyone trying to help, but this is not very helpful. Obviously it wasn't common knowledge for me, otherwise this wouldn't have happened - and I did read up a lot about this. And where in this thread does it answer about the difference in hardware?
Please bear in mind that I'm not an android developer, so what seem like common knowledge to you about internal difference in devices is not that obvious.
Click to expand...
Click to collapse
Jerdog covered the differences in hardware for you. In fact it was exactly above your post explaining that you were unaware of the differences in hardware. 95% of us here are not devs... All you gotta do is read. There are dozens of threads already from folks who have already made your mistake. Read read read. And if you think you've read enough, read more. The difference in processor is one of the most commonly known and discussed things about this phone. Good luck with your phone.
Edit: regarding an actual solution, just try to do a warranty exchange. Play dumb.
Sent from my SGH-T989 using XDA App
This thread happens 30 times a day, very annoying. People will never learn
Sent from my SGH-T989 using xda premium
TJBunch1228 said:
Edit: regarding an actual solution, just try to do a warranty exchange. Play dumb.
Click to expand...
Click to collapse
Thanks, will do that.
Sorry guys, it was an honest mistake. I didn't bother googling it, because I assumed it was the same hardware. Obviously, a sorry mistake, but we're all human. Thanks again to all who tried to help, sorry if annoyed anyone with my problem (and I did search the forum before posting, none of the other threads offered any solutions to my case).
Cheers
If you just assumes it was the same, that basically means you are.clueless and don't even know anything about the phone, in other words, you should not be flashing if you don't know what you are doing
Sent from my SGH-T989 using xda premium
Yup, it's unfortunate - people try to flash VR onto their device, then find it's not compatible...
If there's something I can do to the zip to prevent it flashing on these devices, I will gladly do it, but since they bear the SGS2 name, the standard check for "galaxys2" likely won't help us...
If you try the jig, it SHOULD in theory work, if the hardware is fine. But I have no experience of this, it's a case of stabbing blind in the dark
erangalp said:
Thanks, will do that.
Sorry guys, it was an honest mistake. I didn't bother googling it, because I assumed it was the same hardware. Obviously, a sorry mistake, but we're all human. Thanks again to all who tried to help, sorry if annoyed anyone with my problem (and I did search the forum before posting, none of the other threads offered any solutions to my case).
Cheers
Click to expand...
Click to collapse
Hey - we all make mistakes - and you own up to it - that's a good thing.
I wouldn't personally recommend taking it back for a warranty exchange and playing dumb. If you can go without your device for a few days go on eBay and get a jig. Try that and then flash with ODIN back to stock. It's better than driving up the overall costs for others (trickle-down) for something you did yourself.
My $0.02.
Is there anyone who has made any headway in their research on cracking or unlocking the bootloader? My short research confirms that it is using a 256-bit encryption algorithm, but I've not identified the algorithm used, nor do I think it would matter, as I really have no intention of doing a cryptanalysis on something that strong and I doubt anyone else would, either. Out of curiousity, though: anyone know offhand?
I'm curious to know what methods you guys are attempting to employ and what, if any, other research has already been done. I'd like to help, where I can.
**** if i knew more about it id take a crack at it but unfortunately i lack the skills required. Guess its time to learn huh.
grayn0de said:
Is there anyone who has made any headway in their research on cracking or unlocking the bootloader? My short research confirms that it is using a 256-bit encryption algorithm, but I've not identified the algorithm used, nor do I think it would matter, as I really have no intention of doing a cryptanalysis on something that strong and I doubt anyone else would, either. Out of curiousity, though: anyone know offhand?
I'm curious to know what methods you guys are attempting to employ and what, if any, other research has already been done. I'd like to help, where I can.
Click to expand...
Click to collapse
Vache and I worked on it yesterday for about 6 hours. We didn't get it cracked yet but we are making progress. Don't bother with trying to get your SBK (secure boot key) because A: you won't be able to crack the encryption & B: we have a "secret" way to extract it from the tablet (shhhhh!) (and no, we won't share it just yet, sorry )
timbrendelaz said:
Vache and I worked on it yesterday for about 6 hours. We didn't get it cracked yet but we are making progress. Don't bother with trying to get your SBK (secure boot key) because A: you won't be able to crack the encryption & B: we have a "secret" way to extract it from the tablet (shhhhh!) (and no, we won't share it just yet, sorry )
Click to expand...
Click to collapse
Ahh. Yes, it looks like I noticed vache's call for test in the ROOTED thread a bit late, sent him a PM a couple hours ago.
If you guys need another "Linux guy" or a fresh set of eyes, feel free to PM me. I'll keep poking about the system on my own, in the mean time, as well. Good luck on the research!
This is great news!
This is awesome. Keep up the good work.
Sent from my PG86100 using Tapatalk
timbrendelaz said:
Vache and I worked on it yesterday for about 6 hours. We didn't get it cracked yet but we are making progress. Don't bother with trying to get your SBK (secure boot key) because A: you won't be able to crack the encryption & B: we have a "secret" way to extract it from the tablet (shhhhh!) (and no, we won't share it just yet, sorry )
Click to expand...
Click to collapse
reallllyy appreciate the times you guys are putting into this.
I'm curious how the bootloader is different from the acer iconia a500? If it is not, couldn't we use the same technique from there?
will this thing never gonna get unlocked?
i think i should just sell that piece of ****
TheUndertaker21 said:
will this thing never gonna get unlocked?
i think i should just sell that piece of ....
Click to expand...
Click to collapse
Go for it, the Developers of the XDA community don't owe you anything and if this is how you are going to help (by complaining) then you are better off selling this wonderful device. Patience is a key thing with this device, just like the atrix its just a matter of time.
Lightsword1942 said:
I'm curious how the bootloader is different from the acer iconia a500? If it is not, couldn't we use the same technique from there?
Click to expand...
Click to collapse
Yes, different bootloader, due to both having different versions of hc. The A100 is newer, has newer programming, and leaves us with a different place to start. I myself have tried putting every single script of my A100 into an emulator on my PC to attempt to "reverse engineer" the bootloader to try to decrypt it, but that was unsuccessful for many reasons.
ummmmm............ could you repeat that?
Rather new to androids but I would consider myself a Linux guru. I just picked up an A100 on an open box sale and I would like to get involved in cracking the bootloader on this device. I am a professional low level developer and I have contributed to the development of several major open source projects including Gentoo and Fedora.
I also own a new Samsung Nexus S. Whose working on this now? Is there anything you need help with?
vamman said:
I also own a new Samsung Nexus S. Whose working on this now? Is there anything you need help with?
Click to expand...
Click to collapse
Our biggest challenge with this device is the 256bit encrypted bootloader from hell.. if you know a cryptologist, or some one at acer, that would help a ton
Sent from my MB860 using XDA App
Sent from my MB860 using XDA App
I tried not cracking the bootloader but loading a second init. This proved beyond my skills. I am more a infrastructure and SQL guy then developer.
I would love to have this thing cracked open but I must say with a few tweeks this is a fast stable tablet. I do not know what I would want changed other then the native bluetooth PAN menu.
I just received my a100 from best buy, order placed on black friday.
I would love to see the bootloader cracked.
Keep up the good work guys.
Sent from my MB855 using Tapatalk
I for one would love to see some development on the a100! If there is anything I can do to help just let me know. Im not a dev but I have been tinkering since ms-dos in 1982, and I am very eager to see some development on this tablet, especially usb host mode. good luck!!
painter_ said:
I tried not cracking the bootloader but loading a second init. This proved beyond my skills. I am more a infrastructure and SQL guy then developer.
I would love to have this thing cracked open but I must say with a few tweeks this is a fast stable tablet. I do not know what I would want changed other then the native bluetooth PAN menu.
Click to expand...
Click to collapse
That's the route Im going as well, so far I've compiled 2nd-init and it runs, but it crashes right after initalizing the memory and reboots the tablet (I dont think I have the correct memory address of init for the hook to work properly so it reboots the device). I've also tried log's kexec hack and I dont think it works. Asks for a kernel to load, which I dont have but, I dont think our current kernel supports kexec, so a module would have to be compiled for it. Im no kernel developer (I understand how they work, and how to mod an existing one, but building onne from scratch not so much). With kexec, it requires a special kernel the starts up where your current kernel resides in memory, so it would be harder to get working than 2nd-init.
cracking the encryption
I am not sure what type of file this is but I am fairly experienced with cracking and have access to a small render farm with plenty of gpu power and john the ripper installed. I could give it a go at cracking the password. let me know if I can help.
burn.phreak said:
I am not sure what type of file this is but I am fairly experienced with cracking and have access to a small render farm with plenty of gpu power and john the ripper installed. I could give it a go at cracking the password. let me know if I can help.
Click to expand...
Click to collapse
You can't really brute force this kind of thing, we need to use some sort of exploit, would take millions of years or something like that.
Lightsword1942 said:
You can't really brute force this kind of thing, we need to use some sort of exploit, would take millions of years or something like that.
Click to expand...
Click to collapse
I have brute forced a lot before its worth a shot, I wouldn't say its our best shot but it's worth a look and gives me something to occupy my time.
Hi,
i was considering buy an A100 but was surprised to see very little or no development for this tablet. Any particular reasons for it?
Sent from my GT-I9001 using XDA App
@sahilkhurana:
The particular reason is that Android 4.0 is supposed to be available on the A100 "early" in the New Year.
jschall said:
@sahilkhurana:
The particular reason is that Android 4.0 is supposed to be available on the A100 "early" in the New Year.
Click to expand...
Click to collapse
I really do hope deving kicks off after ICS. If not i will sell this tab despite being such an amazing specd tab at fantastic price and buy a kindle fire.
jay_993 said:
I really do hope deving kicks off after ICS. If not i will sell this tab despite being such an amazing specd tab at fantastic price and buy a kindle fire.
Click to expand...
Click to collapse
I don't think I could use a kindle fire, it doesn't have a volume rocker, Bluetooth, GPS, or a sdcard slot. I agree this needs more development, but until you we either have a super intelligent person crack the boot-loader, or acer unlocks it for us, we won't get any development going on this. After that gets open, its cake and bacon. (lawl)
It's not ICS preventing dev support... Its the locked and encrypted bootloader. It has been mentioned in several other thread topics that in order for anything "major" to be done to this device that the bootloader has to be unlocked.
With an unlocked bootloader you'll get alot more doors open, such as:
- Rom Manager
- The possibility of porting CM7 and when it comes out CM9
- Custom Kernels
- Over Clocking
- Custom Roms
The dev community can do custom roms (by way of DD'ing a system.img file), but its not the same and can be messy (definitely not something an average person would want to do.)
Some of the more talented "hacker" type devs that have good decryption skills could break the encryption on the bootloader or find a loop hole in it, but so far no one has managed to break it. It's not something every one or dev can do and takes a skilled hacker or someone with the right connections at Acer.
Until this happens this device will be just like the Atrix you won't see much done with it but if it does manage to get unlocked you'll see a flood of roms and things for it.
Thats what i thought as well. Well might sell this tab off soon then cuz i get too many force closes.
Oh and one more thing, you can't use the bootloader hack that was released for the A500. They are two separate devices and while similar the A500 bootloader doesn't have the same 256 bit encryption key.
If you are experiencing too many FC's then you may need to do a hard reset or if you have it rooted try fixing permissions in rom manager (rom manager still works for permissions, but nothing else since it can't load itself into the bootloader). I use this device every day for development work and have no problems, every once in a while the browser will FC, but it's usually because I've done something stupid. Games will FC because of our device's resolution too (all 10" tablets usually run games at 1280x800 our 7" runs at 1028x600)
Like for instance if i log onto xda and click on a link not only will it force close but also delete data as well. Annoying that
I have to agree on slow development but on the other hand i'm so glad I was able to root it quickly as soon as i opened it. Also to add I havent experience FC on normal operation. But I have encountered some when I try to install apps that werent made for the a100. Just as crossix metioned probably cause of resolution conflict.
Thanks a lot for the replies. Its such a shame that Acer has locked bootloader for this device.
Sent from my GT-I9001 using XDA App
why would you buy a crippled WiFi TV
jay_993 said:
I really do hope deving kicks off after ICS. If not i will sell this tab despite being such an amazing specd tab at fantastic price and buy a kindle fire.
Click to expand...
Click to collapse
maby you have not noticed all the things fire dose not have IE: SD card,hdmi,non over custom ROM,and more than i have time to type
I will say this though to be able to charge over USB is nice
Hi everybody,
I bought a Note 2 in october 2012. I installed the ROM HD Revolution. Until now there was no problem.
Few days ago, my screen has swiched off and there was lot of reds pixels everywere on the screen.
The phone of course was rooted and the garantly not applicable.
So in the samsung shop, i explain that the phone was rooted... The techniciens has puted a new screen thinking that the problem was coming from a screen hardware. This new screen has well worked during 20 mn, after that, same trouble, the screen was killed....
My phone was sent to another tehcniciens ( more specialists and i think, working directly with samsung) in france, who can works on the motherboard. But just before to sent it, the technical personnal has succefuly replace the rom Revolution by another official ROM by Odin. (In order to keep my garantly.....wonderful techniciens)
Today the phone was return to me, with just a new screen. The third screen after mine who was killed in first.
No motherboard trouble, no graphic chipset trouble was fixed, only the HD Revolution ROM who is apparently , and i 'am sure now, has killed the screen
I'am not able to explain why and how, I am not found on the web or another forum the same trouble.
Somebody know what's happened?
thanks
You might want to contact the developer, but I doubt the rom was the issue.
Sent from my SAMSUNG-SGH-I317 using xda premium
silentecho13 said:
You might want to contact the developer, but I doubt the rom was the issue.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
I'am sure, very sure that the problem on the screen is due to the ROM Revolution, otherwise explain me why the third screen has no trouble after changing only the ROM with the lastest samsung ROM?
The official technicians do try to convince you that a custom ROM is the cause of your problem. Not making a judgement on whether this was what happened in your case, but just my personal opinion.
I am in India, where anyway Sammy tries to avoid taking responsibility however possible. One of my friend had sds on his s3, and the guys from Samsung tried to refuse him warranty on the basis that they believed he had a custom firmware. They were adamant on this even on his pointing out that thousands had had this even on the stock ROM, and thus could not be in any way related to flashing a custom firmware. Only when he threatened them with legal action (as they couldn't prove it was flashed anyway) did they finally took it in for repairs.
My advice is, check out the devs thread for the ROM, if its a genuine problem then it is sure to be mentioned by someone there.
Sent from my GT-N7100.
Those who help noobs go to heaven. True story.
SacGuru said:
The official technicians do try to convince you that a custom ROM is the cause of your problem. Not making a judgement on whether this was what happened in your case, but just my personal opinion.
I am in India, where anyway Sammy tries to avoid taking responsibility however possible. One of my friend had sds on his s3, and the guys from Samsung tried to refuse him warranty on the basis that they believed he had a custom firmware. They were adamant on this even on his pointing out that thousands had had this even on the stock ROM, and thus could not be in any way related to flashing a custom firmware. Only when he threatened them with legal action (as they couldn't prove it was flashed anyway) did they finally took it in for repairs.
My advice is, check out the devs thread for the ROM, if its a genuine problem then it is sure to be mentioned by someone there.
Sent from my GT-N7100.
Those who help noobs go to heaven. True story.
Click to expand...
Click to collapse
I understand but, the first technicians i saw works for samsung, it's not samsung technicians, and these technicians has tried to change my ROM revolution in order to preserve my warrantly. Unfortunatly we have decided together that in first my phone will not send to Paris at Samsung.
The local technicians has received a new screen, and it was impossible for them to change the rom, anyway they has changed my screen by the new, after 20 mn the new screen has crashed...
We decided to send unfortuntly the phone to paris because we has think that the trouble was the motherbord or the graphic chipset. I was very afraid concerning my warrantly. But the local technicians has success just before to send the phone to change the revolution rom to a samsung in order to keep my warrantly. Otherwise the technicians of Paris..
At paris they has changed for the third time just the screen, anything else , and the note 2 is working perfectly....
I have the report by paper of all investigations makes... I am not a lie.. I cannot saw another reason of this trouble....
aquasirius said:
I understand but, the first technicians i saw works for samsung, it's not samsung technicians, and these technicians has tried to change my ROM revolution in order to preserve my warrantly. Unfortunatly we have decided together that in first my phone will not send to Paris at Samsung.
The local technicians has received a new screen, and it was impossible for them to change the rom, anyway they has changed my screen by the new, after 20 mn the new screen has crashed...
We decided to send unfortuntly the phone to paris because we has think that the trouble was the motherbord or the graphic chipset. I was very afraid concerning my warrantly. But the local technicians has success just before to send the phone to change the revolution rom to a samsung in order to keep my warrantly. Otherwise the technicians of Paris..
At paris they has changed for the third time just the screen, anything else , and the note 2 is working perfectly....
I have the report by paper of all investigations makes... I am not a lie.. I cannot saw another reason of this trouble....
Click to expand...
Click to collapse
I suggest you verify on the forum thread and contact the dev. I highly doubt its the rom. I imagine for what you say to be possibly its not rom related but kernel and would require some sort of color adjustment hack of sorts, even then I highly doubt it as more users would have experienced the same. As for your proof from samsung means nothing. I've sent devices and computers out to warranty and the document says one thing but when I take it apart I see things where changed that do not reflect what the work order says. Not saying its the case just saying take it with a grain of salt.
I can't seem to find the rom your talking about.
prbassplayer said:
I suggest you verify on the forum thread and contact the dev. I highly doubt its the rom. I imagine for what you say to be possibly its not rom related but kernel and would require some sort of color adjustment hack of sorts, even then I highly doubt it as more users would have experienced the same. As for your proof from samsung means nothing. I've sent devices and computers out to warranty and the document says one thing but when I take it apart I see things where changed that do not reflect what the work order says. Not saying its the case just saying take it with a grain of salt.
I can't seem to find the rom your talking about.
Click to expand...
Click to collapse
It was the REVOLUTION HD Rom.
You think that the Samsung technicians when they changed the screen after the other first technicians has not been honnest?
It's incredible, i don't believe in this idea... I cannot see the interest... But if you are talking about the kernel maybe it yes...
It's a crazy story...
HD Revolution....? wait.. isnt it for a international version of Note 2?
No wonder why your phone is acting up. Flashing almost non compatible ROM on your device doesnt give you rights to discredit Dev.
I believe he is talking about this rom that is not in the att section.
http://forum.xda-developers.com/showthread.php?t=1925402
OP, when flashing did you happen to flash anything else such as that gpu rendering thing they have on that page? Also, any extreme overclocking or anything?
Sent from the Bacon Pope's Galaxy Note 2
Well then if that is the rom there is your problem. Your lucky Note II in general share the same SoC else you would have hard bricked. I suggest you do your research correctly before saying something broke your device. In the end its your responsability to know what you are flashing and even if said rom/kernel/mod does break your device its your fault, you flashed it not the developer. Its a risk we all take when modifying our devices.
cwhitney24 said:
I believe he is talking about this rom that is not in the att section.
http://forum.xda-developers.com/showthread.php?t=1925402
OP, when flashing did you happen to flash anything else such as that gpu rendering thing they have on that page? Also, any extreme overclocking or anything?
Sent from the Bacon Pope's Galaxy Note 2
Click to expand...
Click to collapse
I use the recovery mode after have put the zip's ROM on my SD card.
And i never use the o/c
I 'am sure that the trouble has been caused by the Kernel or the ROM... I don't remember what was the kernel... i thinking...
prbassplayer said:
Well then if that is the rom there is your problem. Your lucky Note II in general share the same SoC else you would have hard bricked. I suggest you do your research correctly before saying something broke your device. In the end its your responsability to know what you are flashing and even if said rom/kernel/mod does break your device its your fault, you flashed it not the developer. Its a risk we all take when modifying our devices.
Click to expand...
Click to collapse
I know that, but on the french forum we are several with this ROM, i'am looking for the same trouble in France: nothing...
I'am wondering what's happened and i 'am not here to cry but to exlpain you this trouble and i 'am trying to have an elaborate conversation in order to find the origin, I find it normal beetween enthusiast....
aquasirius said:
I know that, but on the french forum we are several with this ROM, i'am looking for the same trouble in France: nothing...
I'am wondering what's happened and i 'am not here to cry but to exlpain you this trouble and i 'am trying to have an elaborate conversation in order to find the origin, I find it normal beetween enthusiast....
Click to expand...
Click to collapse
Well you are disproving yourself. If no other LTE variant on that rom has had similar problems then its not the rom/kernel/mod. It was a fluke of bad hardware with lazy techs (don't want to generalize its easier to blame it on an external source than actually debugging). Second your arguments are null in the end becaus:
mike1986. said:
No mate, LTE version is not supported.
Click to expand...
Click to collapse
That includes I7105, I317[M] and T889[V]. It might work, but probably not 100% and the developer simply offers no support for it.
aquasirius said:
I understand but, the first technicians i saw works for samsung, it's not samsung technicians, and these technicians has tried to change my ROM revolution in order to preserve my warrantly. Unfortunatly we have decided together that in first my phone will not send to Paris at Samsung.
The local technicians has received a new screen, and it was impossible for them to change the rom, anyway they has changed my screen by the new, after 20 mn the new screen has crashed...
We decided to send unfortuntly the phone to paris because we has think that the trouble was the motherbord or the graphic chipset. I was very afraid concerning my warrantly. But the local technicians has success just before to send the phone to change the revolution rom to a samsung in order to keep my warrantly. Otherwise the technicians of Paris..
At paris they has changed for the third time just the screen, anything else , and the note 2 is working perfectly....
I have the report by paper of all investigations makes... I am not a lie.. I cannot saw another reason of this trouble....
Click to expand...
Click to collapse
Relax man, I did not think you were lying, neither did I accuse you of it, I merely asked you to, and personally believe,that the developers on this forum (who are people like you and me) are anyday more trustworthy than repair men who are from samsung or freelancers (read people bent on profiting from me screwing up my cellphone). Thus I asked you to visit the developers thread and look for comments about the issues you were facing, that is what I would've done.
Apparently you flashed a ROM which was not meant for your particular model. Whether that is true or not, I am sorry for all the trouble you had to go through with the engineers and all. I hope your note 2 functions great from now on.
Je vous présente mes meilleurs vœux pour l'année 2013
Sent from my GT-N7100.
Those who help noobs go to heaven. True story.
prbassplayer said:
Well you are disproving yourself. If no other LTE variant on that rom has had similar problems then its not the rom/kernel/mod. It was a fluke of bad hardware with lazy techs (don't want to generalize its easier to blame it on an external source than actually debugging). Second your arguments are null in the end becaus:
That includes I7105, I317[M] and T889[V]. It might work, but probably not 100% and the developer simply offers no support for it.
Click to expand...
Click to collapse
It was the REVOLUTION HD 4, installed in november, not the 8 or the 9
I used the ROM perfectly adapted for my note 2
Now my note is working without problem with the last samsung rom with 4.1.2 android version.
Nothing has been changed into my phone (hardware etc...) just a new ROM...
And never else was happened on my phone before the trouble.
aquasirius said:
It was the REVOLUTION HD 4, installed in november, not the 8 or the 9
I used the ROM perfectly adapted for my note 2
Now my note is working without problem with the last samsung rom with 4.1.2 android version.
Nothing has been changed into my phone (hardware etc...) just a new ROM...
And never else was happened on my phone before the trouble.
Click to expand...
Click to collapse
Man you said your on a 3rd screen so don't say hardware hasn't changed. This is not counting for anything that changed when you shipped out. In the end it doesn't matter if it was a November rom, or January rom its based on the N7100 firmware not N7105 therefor although it might work probably won't work 100%. You are so caught up that it has to be the rom that you are ignoring key points in your argument. It is more likely to be a hardware problem than software. I'm not saying it wasn't the rom/kernel combination because its possible, who knows, however its a rom based on Sammy firmware that isn't made for your device. Plain and simple.
Cheers
prbassplayer said:
Man you said your on a 3rd screen so don't say hardware hasn't changed. This is not counting for anything that changed when you shipped out. In the end it doesn't matter if it was a November rom, or January rom its based on the N7100 firmware not N7105 therefor although it might work probably won't work 100%. You are so caught up that it has to be the rom that you are ignoring key points in your argument. It is more likely to be a hardware problem than software. I'm not saying it wasn't the rom/kernel combination because its possible, who knows, however its a rom based on Sammy firmware that isn't made for your device. Plain and simple.
Cheers
Click to expand...
Click to collapse
I mean hardware (motherboard, chipset,....etc) of course screens are hardware.
And I have 7100 and the ROM I used was for the 7100.
The ROM has broken something on my phone, i don't know what, maybe my english is too bad and i'am not able to do understand my story with the corrects words
I'am not a noob to choose the wrong ROM for my note 2...
we thought that the problem has came from a voltage problem beetween the screen and the GPU or the chipset...
Without any else action from me (no o/c, no brutality) i cannot see anything else....
I think several people have made good points though who knows, it's also possible some part of your os got corrupted and it killed the screens. I've seen a lot of wierd stuff happen with computers over the years. I repair phones, desktops and laptops myself and I continue to see new problems. Some of it I figure out, some I never do.
Another explanation that occurs to me - a transitory short that fried the screens. Did you drop or jar the phone? Spill fluid? Have high or extremes of temp or humidity ? **** happens. Intermitant problems are the absolute worst to track down. If it is something lurking in the hardware and they didn't fix it completely, it may say hello to you again! Problem devices often stay problem devices even after a number of "final" repairs that work for a while. That's why if something like that happened to me, I'd be happier with a replacement device.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Dumbo53 said:
I think several people have made good points though who knows, it's also possible some part of your os got corrupted and it killed the screens. I've seen a lot of wierd stuff happen with computers over the years. I repair phones, desktops and laptops myself and I continue to see new problems. Some of it I figure out, some I never do.
Another explanation that occurs to me - a transitory short that fried the screens. Did you drop or jar the phone? Spill fluid? Have high or extremes of temp or humidity ? **** happens. Intermitant problems are the absolute worst to track down. If it is something lurking in the hardware and they didn't fix it completely, it may say hello to you again! Problem devices often stay problem devices even after a number of "final" repairs that work for a while. That's why if something like that happened to me, I'd be happier with a replacement device.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
Maybe you right, and the phone has been exposed every time in good condition, and never droped or jared. I will see with the time if it was a another hardware problem.
I think actually the association ROM/kernel has revealed an intrinseq hardware problem on my phone and maybe later even with a samsung rom the problem should be appear again....
aquasirius said:
I mean hardware (motherboard, chipset,....etc) of course screens are hardware.
And I have 7100 and the ROM I used was for the 7100.
The ROM has broken something on my phone, i don't know what, maybe my english is too bad and i'am not able to do understand my story with the corrects words
I'am not a noob to choose the wrong ROM for my note 2...
we thought that the problem has came from a voltage problem beetween the screen and the GPU or the chipset...
Without any else action from me (no o/c, no brutality) i cannot see anything else....
Click to expand...
Click to collapse
Wait.....Your Note 2 is an N7100? Then why did you come to an i317 forum to complain about a ROM somehow breaking your screen?
If you really think you have a legitimate concern that a ROM may have damaged your phone in some way, contact the developer. Maybe it has happened before. Maybe the developer can make changes to prevent it from happening to others. What you probably shouldn't do is to make claims that a ROM damaged your phone on a forum for a different model of phone.
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...