Hey Guys,
I'm having some problems with my screen and have made a quick video to make the problem clear.
http://www.youtube.com/watch?v=6sR3JSElIvM&feature=youtube_gdata
As you can see, it's unresponsive in a horizontal section about 2cm wide near the bottom of the screen - it's almost exactly where the unlock slider resides.
I'm running CM7 weekly 11-15 with the standard CM7 kernel, 01.100.00R radio.
I've tried Aura, CM7 bat2f or whatever, as well as another radio, and the OC kernel, all with the same exact problem, so I don't think it's any of that.
I've tried factory reset, and also formatted the data, system and cache in romracers recovery.
I haven't dropped it or got water damage, it just started happening about 2 weeks ago. The phone is still usable (although annoying), but I wouldn't be able to sell it like this.
Any idea's on what the problem could be, and how I could fix it?
NOTE: I thought I fixed it after 1 of the formats, but when I re-installed apps the problem started again (could have been an ICS theme app for ADW EX), and I haven't been able to replicate it, even without installing any apps.
All suggestions and help is really appreciated
This could help: http://forum.xda-developers.com/showthread.php?t=1131649
Do you remember accidentally partitioning (in cwm) the internal storage? The above will fix it in that case. Good luck
Thanks for the tip, but unfortunately it didn't work.
I tried deep cache erase too with no luck either.
Can anyone point me to a list of commands on how to totally wipe my phone (like full on format in fastboot). I want to try totally wiping everything, data, system, cache, boot maybe, and see if that helps. However I can't find the commands for it.
Thanks heaps!
dbergen said:
Thanks for the tip, but unfortunately it didn't work.
I tried deep cache erase too with no luck either.
Can anyone point me to a list of commands on how to totally wipe my phone (like full on format in fastboot). I want to try totally wiping everything, data, system, cache, boot maybe, and see if that helps. However I can't find the commands for it.
Thanks heaps!
Click to expand...
Click to collapse
Bummer..
Here are the commands mate:
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot
Perfect! That's a tremendous help to me! I have searched for about 30 mins and couldn't find anything like that.
I will try soon (hanging out with the girlfriend at the moment)
Since that erases the boot, do I need to install a rom before I reboot? Don't wanna brick this thing
Why don't you install the latest fruitcake & start new? Do the above, install the fruitcake, reboot to cwm, clear dalvik & cache, reboot & let the system build up cache for 10-15 minutes.
AHHH! I've done all that now and I'm on the HKTW build of fruitcake... yet the same problem persists.
Have I exhausted all my options? Do you think it's just a screen problem that will need repair under warranty?
dbergen said:
AHHH! I've done all that now and I'm on the HKTW build of fruitcake... yet the same problem persists.
Have I exhausted all my options? Do you think it's just a screen problem that will need repair under warranty?
Click to expand...
Click to collapse
Hm. It certainly sounds like a defect then. Unless someone else has a more educated guess..
Damn it! Looks like I might have to flash it back to stock then.
I was hoping it wouldn't come to this since I had it sent over from the US, so I'll have to post it back for the warranty claim (I'm in Australia), which will be expensive and time consuming I'm sure
Thanks for trying Vangelis
dbergen said:
Damn it! Looks like I might have to flash it back to stock then.
I was hoping it wouldn't come to this since I had it sent over from the US, so I'll have to post it back for the warranty claim (I'm in Australia), which will be expensive and time consuming I'm sure
Thanks for trying Vangelis
Click to expand...
Click to collapse
Then again, if someone can verify it's the screen you could order it off eBay & swap it yourself. It's allegedly very easy.
I've seen a couple of posts about defect screens though; check in the pds thread, I think its a girl called "filmusicat" or so that had a screen issue. Check her profile & see if there isn't any thread she's started about the defect screen she had..
Same issue, got my replacement on wednesday
Sent from my CM860
Oh really Robby! Was it a warranty repair?
I just heard back from Motorola and they advised me to turn it off, then on again, lol
I might try and get it done under warranty, but if they deem it to be misuse then I'll have to pay their repair fee's which I assume will be around $200 (girlfriend had Steak screen repaired for $280).
Otherwise I can just grab a screen on ebay for $70 and do it myself.
Any recommendations?
Grab a cold Fosters before swapping it..? ;-)
Lol, thanks for that mate.
I think I'll take the warranty route. I've found quite a few others with similar problems who got a warranty replacement. One theory is that that glass is squashed down and touching the digitizer.
Now I just need to get rid of the 'unlocked' text on the boot up so they don't void my warranty :S Hopefully it's not too difficult to do
dbergen said:
Lol, thanks for that mate.
I think I'll take the warranty route. I've found quite a few others with similar problems who got a warranty replacement. One theory is that that glass is squashed down and touching the digitizer.
Now I just need to get rid of the 'unlocked' text on the boot up so they don't void my warranty :S Hopefully it's not too difficult to do
Click to expand...
Click to collapse
theres probably a guide or 2 to help you out with that, check the dev section
I actually fried a portion of my screen (the vertical area is now unresponsive) by overheating my CPU on Faux's 1.45 kernel (hold it, dev avengers... I am not blaming Faux). I have to play acrobatics with my screen orientation just to type simple sentences. Really sucks with apps that don't support rotation. There are certain letter-values my blank tiles will never again hold in Scrabble Free.
Oh that sucks dude. It's possible that mine was caused by a similar problem, but I was just running the stock CM kernel at 1ghz, however I did occasionally feel it getting pretty hot.
Couldn't you downgrade yours to stock and then take it in for a warranty replacement?
I pretty much hate my phone at the moment because texting is near impossible
Related
So I changed a few things in the build.prop-file to get incompatible apps work on my TF 201 but then I somehow restarted it and now it won't boot anymore. Well it shows up the Asus logo and so one but then the screen just stays black (but still illuminated).
I already wiped the data and tried the recovery mode (with the Volume-down/up-button) but they didnt work, it still doesnt boot.
So any ideas which could help me? Im thankful for every help I can get
Maybe let the battery run out. There is also the reset button in the pinhole next to the SD card slot.
Why do people keep taking such risks. There has been a few threads already of some trying to do the same thing and bricking their device. Where these apps so great n important to now have possibly bricked your device? Instead of editing build. Props you could've used another device with same screen size resolution. For example a gameloft game, modern combat 3. Won't work on Prime because it says its incompatible. That is b.s. Prime just wasn't added to support list yet. So I used an Acer500 , same screen size resolution, version and it worked perfectly. A simple wrkaround without risking editing the app and causing a possible bootloop or brick.
Hope you get it up n running soon. Maybe letting the battery completely die and charging back up may clear whatever you did. I won't risk anything till atleast bootloader unlocked n we have recovery also. GOOD LUCK.
I already let the battery run out twice but it doesnt help, when I plug it in again, it just boots normally till the part where the screen stays black.
And the reset button under the sd card slot just reboots the device normally.
try to return it from wherever you bought it they will never even know what happened to it
fliger5 said:
So I changed a few things in the build.prop-file to get incompatible apps work on my TF 201 but then I somehow restarted it and now it won't boot anymore. Well it shows up the Asus logo and so one but then the screen just stays black (but still illuminated).
I already wiped the data and tried the recovery mode (with the Volume-down/up-button) but they didnt work, it still doesnt boot.
So any ideas which could help me? Im thankful for every help I can get
Click to expand...
Click to collapse
I have the same problem with being stuck in bootloop. I've done the pinhole reset, as well as the power+volume reset... nothing works. I've let the battery drain.. nothing.
I just got off the phone with Asus customer support. They told me to return the tablet. Guess where I'm going today? Best Buy and returning it.
And yes, I'll probably get another Prime. They are just so Beautiful!
tylermaciaszek said:
try to return it from wherever you bought it they will never even know what happened to it
Click to expand...
Click to collapse
You sure about that? I bought it from Amazon btw. But I read that some people got the same problem by just applying an official firmware update, so I guess it's really possible that they will never find out what really happened .
but I think there's no other possibility but returning it. :/
I'll give you $50 for it. J/K.... Good luck getting it running.
I don't quite understand how some people can make changes with out us being able to use Clockwork recovery yet. I would return it, they will probably give you a replacement.
Wait til Feb. Asus will prolly release a restore tool along with the bootloader unlock. Like the ruu for htc phones.
Sent from my Transformer Prime TF201 using xda premium
fliger5 said:
You sure about that? I bought it from Amazon btw. But I read that some people got the same problem by just applying an official firmware update, so I guess it's really possible that they will never find out what really happened .
but I think there's no other possibility but returning it. :/
Click to expand...
Click to collapse
Yes. I just did it today. Got the new one on order.
!
Yes. I just did it today. Got the new one on order.
!
Click to expand...
Click to collapse
And did you have to say anything how it happened? If yes, what did you tell them?
fliger5 said:
And did you have to say anything how it happened? If yes, what did you tell them?
Click to expand...
Click to collapse
Nope. Didn't have to tell them anything. It wouldn't leave the bootloader screen. So I did both types of factory resets. They only way thy find out that I rooted it is when it gets back to Asus, they are somehow to get a computer to recognize it (mine won't), and look at the root files therein.
I had no problem returning mine!
Hope that helps!
Did you at least make a backup of the build.prop? I think the system will make one automatically I am just not sure how to go about getting it. I would guess if you can get into it with adb you could pull the backup rename it and push it to the /system. I don't know the commands but I am guessing someone who has posted stuff in the development section does, maybe that would work. Also, I am not sure there is a way to clear the cache/dalvik cache. Maybe through adb somehow which might have to be done as well.
I just don't know enough about adb and the commands to get it done.
Problem is, adb doesnt work because the device isnt recognized. It always says "No device found" or anything like that. Well I'll send it back to Amazon but I think they will send it then to Asus, so there's a chance that they will find it out, right?
Hi!
I have two problems with the screen on my prime!
1. The first problem was when I pressed the button of my recent applications one part of the screen flashes (I think this is a bug because I read for people have same problem)!???
2. Second Problem is that the screen on my prime after a few seconds (10-15) remember what he looked like a screen (homepage) and when I open an application in some areas can be seen in the background of the icon from the homepage, weather,...the same problem is when i have open another app. It is a bug or ... ?? Do you have some problem?
Do you have that force 2d gpu setting on in developers options? If so, cut it off. Then try a reset. Stick a paper clip in the little hole right underneaths the memorybcard slot. See if that helps.
For your second issue not sure what you mean? You mean a screen burn in? Like some t.v.s. get I'd you leave it on a same image for too long. So when you go to another channel you still see image from before kind of. That's what it sound like you describing. Just try a reset n see if it clears it.
demandarin said:
Do you have that force 2d gpu setting on in developers options? If so, cut it off. Then try a reset. Stick a paper clip in the little hole right underneaths the memorybcard slot. See if that helps.
For your second issue not sure what you mean? You mean a screen burn in? Like some t.v.s. get I'd you leave it on a same image for too long. So when you go to another channel you still see image from before kind of. That's what it sound like you describing. Just try a reset n see if it clears it.
Click to expand...
Click to collapse
No, i have 2d gpu off.Where I need to put paper clip, Do you mean little hole underneath memory sdcard slot?( it is factory reset my prime)? Second problem I try the screenshot but can not see! My screen remember that is a picture on it was, I open kaspersky and transparency on the screen I see pictures of homescreen or any other thing that was open before! and now i found two dead pixel =(
Yes, insert paperclip into the hole underneath memory card slot. Press it enough till you hear or feel it click. Then your prime will reset. I know what you saying now about the screen. You have ghosting or screen burn in it seems. Hopefully the reset will get rid of it.
Do I lose my stuff,apps,root on my prime when i reset my prime(hard reset)??? Yes do you have this problem (second problem)?? How to resolve this problem???
Sent from my Transformer Prime TF201
Don't worry, they're removing having a screen from the specs for the Prime.
I reset my prime, but i still have this problem with recent apps and second problem!
No I don't have none of the issues you describe. Don't mind the troll tactics..lol. you might have to send in for RMA if you got screen burn in or ghosting. It happens with these type displays and on bigscreen t.v.s. there are some apps in android market you can try to fix it. Don't remember the names. Just search market for screen fix LR whatever. Good luck.
---------- Post added at 11:52 AM ---------- Previous post was at 11:49 AM ----------
Reset won't erase your apps. Its more like a reboot button. Last resort is to try a factory reset. That's in settings. Backup n reset. It may just be a bad bug or glitch. You will more than likely lose your apps n data. You can always redownload if needed. That's not as important as trying to fix the issue. If nothing works, you have warranty. Just send in for a RMA
This is no big problem for me..First problem is bug 100% because when i have few recent app. i not have this problem.but im for second problem concerned! I'm afraid if I take the device guarantees they do even more damage because they are there at my poor services. Do I get a new prime? Sry for bad english!
Pegaz-7 said:
This is no big problem for me..First problem is bug 100% because when i have few recent app. i not have this problem.but im for second problem concerned! I'm afraid if I take the device guarantees they do even more damage because they are there at my poor services. Do I get a new prime? Sry for bad english!
Click to expand...
Click to collapse
Don't feed into the supposed " bad service" some describe. Don't be afraid to send it in. If they can't fix the issue then they will give you a new one. You have warranty. Use it. Just make sure to unroot your device before you send it in.
demandarin said:
Don't feed into the supposed " bad service" some describe. Don't be afraid to send it in. If they can't fix the issue then they will give you a new one. You have warranty. Use it. Just make sure to unroot your device before you send it in.
Click to expand...
Click to collapse
Yes ofc first UNROOT than send to warranty!
Tomorrow I will call them and see...I have a very bad experience with warranty because always do more damage than it was!
Oh OK. I see where you coming from then. Chances are if its a screen problem, they will replace the screen or give you a new tablet. Good luck
One last thing you can try is doing a hard rest from recovery mode. Turn prime off then press volume down and power at same time. It'll bring you to recvoery mode. Wipe all data n cache from there. Then do reset from there. Then reboot tablet. Worth s shot before you send it in. If its a bug or something, this might clear it. In recovery u use volume down to scroll thru options. Volume up confirms option u want to use.
I have that same issue with the recent apps button. It seems like a software issue that could be resolved in future OTA updates.
If you do feel like sending it in for a RMA, unroot it if it's rooted and do a factory reset of it before you send it. Call me paranoid but I'm not letting that thing leave my hands to go to a mystery factory somewhere with any of my personal data on it. I did this with my Captivate. If you need backups of all your apps you can use the Asus app or root the thing and use Titanium Backup and save the backups to your computer.
dannb said:
I have that same issue with the recent apps button. It seems like a software issue that could be resolved in future OTA updates.
If you do feel like sending it in for a RMA, unroot it if it's rooted and do a factory reset of it before you send it. Call me paranoid but I'm not letting that thing leave my hands to go to a mystery factory somewhere with any of my personal data on it. I did this with my Captivate. If you need backups of all your apps you can use the Asus app or root the thing and use Titanium Backup and save the backups to your computer.
Click to expand...
Click to collapse
When I buy prime it was be on honeycomb>then on ICS .11>ICS .14>ICS .15 and update no remove this bug.And this bug is not that some stupid bug, It is really a big problem! I am a little disappointed with prime!
demandarin said:
Oh OK. I see where you coming from then. Chances are if its a screen problem, they will replace the screen or give you a new tablet. Good luck
One last thing you can try is doing a hard rest from recovery mode. Turn prime off then press volume down and power at same time. It'll bring you to recvoery mode. Wipe all data n cache from there. Then do reset from there. Then reboot tablet. Worth s shot before you send it in. If its a bug or something, this might clear it. In recovery u use volume down to scroll thru options. Volume up confirms option u want to use.
Click to expand...
Click to collapse
Thanks for all!
So, I've been jumping back and forth between Atrix CM9 and CM7 roms and running the .36p radio. Yesterday on CM9, i started getting a large amounts of random reboots and finally got things settled by doing a factory reset in CWM and flashing a clean cm9 rom. However, whenever I turned on wifi, the phone would crash and reboot to the Dual Core logo. I tried flashing another CM9 rom and it didn't crash, but the wifi radio would never seem to pick up any AP's (i'm at home).
I've gone as far as changing to the .37p radio and going back to cm7 to no avail... I'm a bit worried I might have "fried" the wifi radio on the phone.
Did you do a full wipe? Use fastboot to wipe properly before flashing any ROM. Plenty of threads with instructions.
Sent from my MB860 using xda premium
Looking at the fast boot command, I'm not sure how that does anything different then the clockwork mod wipe... but I will give it a shot.
Sent from my NookColor using xda premium
Sorry, but your wifi/bluetooth card is dead. My Atrix got the exact same symptoms a few days ago. Both WiFi and bluetooth are on the same chip. When the system tries to reference them, it fails to locate the hardware and crashes/reboots.
In fact, in researching this topic, I found dozens of threads about this. We should make a sticky about it at this point. Best Buy was kind enough to take back my phone (unlocked bootloader, rooted, cwm, custom fonts, startup, etc.) if I restored it all to stock. If you want Motorola/AT&T/the store you purchased it at to not void your warranty, you should flash the 2.3.6 SBF. Just be cautious and read all about it. But that is the only way that Motorola will service a modded phone
xandr115 said:
Looking at the fast boot command, I'm not sure how that does anything different then the clockwork mod wipe... but I will give it a shot.
Sent from my NookColor using xda premium
Click to expand...
Click to collapse
Nothing like the same. Clockwork wipe only does data and cache. You erase boot, system, preinstall, cache, user, webtop, etc., via fastboot. I've posted the procedure probably more than 20 times before.
Sent from my MB860 using xda premium
Yeah unfortunately even after a fastboot wipe, the phone's bluetooth and wifi were gone. I was also over the year warranty. Luckily, I picked up a barely used one on Craigslist and restored my backup to it. Now i've got an expensive battery charger (and spare phone should i need it).
If there were any tips you'd have on restoring to a new phone? I've restored my phone a lot and worked on a lot of android phones (I work at a repair shop), but I've never restored data/settings from one phone to another. Of course its the same model, but I can only imagine the issues that could arise out of such an operation
Thanks!
I just made sure I did a fastboot full wipe of the new phone, then placed my clockworkmod directory on the internal (external should be ok too) storage and did a restore. After the restore, I re-flashed the latest version of the rom I was running on top of it with Google apps and it booted fine. Afterwards, I made sure to do a permissions repair and reboot.
Yeah, it seems like a lot of people are having this problem. Like me for example :[
So far there is no solution that I'm aware of, after trying practically everything I could think of and find on the internet... I'm pretty sure it's hardware related. I bet the phone just isn't very high quality. How much did it cost again? $600? + all of the dumb accessories for it. Normally when you see a pattern of failures you would call it a design flaw, but apparently when it comes to expensive electronics they call it out of warranty.
xandr115 said:
So, I've been jumping back and forth between Atrix CM9 and CM7 roms and running the .36p radio. Yesterday on CM9, i started getting a large amounts of random reboots and finally got things settled by doing a factory reset in CWM and flashing a clean cm9 rom. However, whenever I turned on wifi, the phone would crash and reboot to the Dual Core logo. I tried flashing another CM9 rom and it didn't crash, but the wifi radio would never seem to pick up any AP's (i'm at home).
I've gone as far as changing to the .37p radio and going back to cm7 to no avail... I'm a bit worried I might have "fried" the wifi radio on the phone.
Click to expand...
Click to collapse
did your wifi
For anyone interested, here is a supposed solution to the problem:
http://www.youtube.com/watch?v=SYz_RiuFVRk
It will require you to open the phone up, and solder the "wifi battery" into place. I'm not sure what the hell that thing is, but that guy in the video called it a battery. Voids warranty etc. Good luck.
cafe. said:
For anyone interested, here is a supposed solution to the problem:
http://www.youtube.com/watch?v=SYz_RiuFVRk
It will require you to open the phone up, and solder the "wifi battery" into place. I'm not sure what the hell that thing is, but that guy in the video called it a battery. Voids warranty etc. Good luck.
Click to expand...
Click to collapse
I'd give it a try, if I could understand what exactly he does. It looks like he just pries it up with a screwdriver and then pushes it back down.
Meursau|t said:
I'd give it a try, if I could understand what exactly he does. It looks like he just pries it up with a screwdriver and then pushes it back down.
Click to expand...
Click to collapse
If I ha some solder I might try it
Sent from my NookColor using xda premium
Okay, guys. I'm new to this forum (I own the ATRIX since yesterday, so...). I had the HTC Desire, Desire HD and EVO 3D before and never had such problems with them (instead, I used to have other issues such as crappy sound, ghost touching etc.).
Flashed Neutrino GT+ ROM, set the max CPU freq to 1 GHz, instead of 1.45 - I don't feel like I need that extra power (at least not yet, anyway). Flashed the Superuser 3.0.7 pack, flashed several Addons, also set the NitroCharger.sh script on boot... I think I pretty much did everything that mattered.
Oh, I flashed the ROM from the internal sdcard (emmc). I don't get why it's reccomended not to flash from the external sdcard, anyways, but... oh well...
-----
The best way to describe the problem(s) I am experiencing is through this movie I've made. I filmed it with a Nokia 6233, so it's not really high definition, but hey, at least it's 480p, not QVGA . Oh well, you can figure, I suppose / hope.
Okay, the problem is the touch panel is acting weird. When I'm browsing through the app drawer, and I slide my finger across and then stop or do something like that, the app that the finger was on is being launched (like I released my finger = touch ended, registered, whatever).
Also, the left and right sides of the screen seem to be less responsive (you can clearly see that in Multitouch Visualiser), especially as you get closer to the edges. Not ALL THE TIMES, though, but roughly 95%, the problem occurs and... well... the touch goes crazy.
----------------------------------------------------
Can anyone confirm that this is happening to them, and not only to me? Perhaps use Multitouch Visualiser yourself and see if you get the same results?!
VIDEO HERE
Formhault said:
Okay, guys. I'm new to this forum (I own the ATRIX since yesterday, so...). I had the HTC Desire, Desire HD and EVO 3D before and never had such problems with them (instead, I used to have other issues such as crappy sound, ghost touching etc.).
Flashed Neutrino GT+ ROM, set the max CPU freq to 1 GHz, instead of 1.45 - I don't feel like I need that extra power (at least not yet, anyway). Flashed the Superuser 3.0.7 pack, flashed several Addons, also set the NitroCharger.sh script on boot... I think I pretty much did everything that mattered.
Oh, I flashed the ROM from the internal sdcard (emmc). I don't get why it's reccomended not to flash from the external sdcard, anyways, but... oh well...
-----
The best way to describe the problem(s) I am experiencing is through this movie I've made. I filmed it with a Nokia 6233, so it's not really high definition, but hey, at least it's 480p, not QVGA . Oh well, you can figure, I suppose / hope.
Okay, the problem is the touch panel is acting weird. When I'm browsing through the app drawer, and I slide my finger across and then stop or do something like that, the app that the finger was on is being launched (like I released my finger = touch ended, registered, whatever).
Also, the left and right sides of the screen seem to be less responsive (you can clearly see that in Multitouch Visualiser), especially as you get closer to the edges. Not ALL THE TIMES, though, but roughly 95%, the problem occurs and... well... the touch goes crazy.
----------------------------------------------------
Can anyone confirm that this is happening to them, and not only to me? Perhaps use Multitouch Visualiser yourself and see if you get the same results?!
Click to expand...
Click to collapse
The app drawer thing is the manner in which you stop it, to stop the app drawer from scrolling, just give a quick very light tap, it also helps to try and tap between two of the apps, if you're using your right hand try to tap between the 3rd and 4th columns, this way you don't tap any icons. To be honest, I never really have any problems at all. Can you give me DETAILED information on how you flashed the ROM? It could be cause by a mistake in the flashing process.
Erebus671 said:
The app drawer thing is the manner in which you stop it, to stop the app drawer from scrolling, just give a quick very light tap, it also helps to try and tap between two of the apps, if you're using your right hand try to tap between the 3rd and 4th columns, this way you don't tap any icons. To be honest, I never really have any problems at all. Can you give me DETAILED information on how you flashed the ROM? It could be cause by a mistake in the flashing process.
Click to expand...
Click to collapse
I forgot to put the video link in the first topic (I edited it, it is there now).
I put Neutrino GT+ .zip in the emmc (along with all other flashables, actually). I still don't get why it is reccomended to flash from the internal memory instead of an external sdcard. Speaking of internal memory, is it an internal SD card (just like HTC devices with WP7) or NAND?!
Wiped everything in recovery (using the latest RomRacer's CWM). Then, I flashed Neutrino V2.6 GT+.zip, then Lite Gapps, then Deskclock addon, then Languages addon, then Live Wallpapers addon, then Sync addon, then Theme Chooser addon, then TTS addon, then VPN addon. Then rebooted the phone.
The red M logo appeared, and a few seconds after that, it seemed like the phone turned off and turned itself on again (M logo appeared second time, then the boot animation showed up and the ROM booted). I remember that was happening back when I was using CM7 on my old Desire and I was flashing the Gapps right after the ROM. If I were to flash MIUI and then the DarkTremor script (for A2SD), without rebooting in between, the boot splash would appear three times .
Formhault said:
I forgot to put the video link in the first topic (I edited it, it is there now).
I put Neutrino GT+ .zip in the emmc (along with all other flashables, actually). I still don't get why it is reccomended to flash from the internal memory instead of an external sdcard. Speaking of internal memory, is it an internal SD card (just like HTC devices with WP7) or NAND?!
Wiped everything in recovery (using the latest RomRacer's CWM). Then, I flashed Neutrino V2.6 GT+.zip, then Lite Gapps, then Deskclock addon, then Languages addon, then Live Wallpapers addon, then Sync addon, then Theme Chooser addon, then TTS addon, then VPN addon. Then rebooted the phone.
The red M logo appeared, and a few seconds after that, it seemed like the phone turned off and turned itself on again (M logo appeared second time, then the boot animation showed up and the ROM booted). I remember that was happening back when I was using CM7 on my old Desire and I was flashing the Gapps right after the ROM. If I were to flash MIUI and then the DarkTremor script (for A2SD), without rebooting in between, the boot splash would appear three times .
Click to expand...
Click to collapse
Okay, I'm not exactly sure about what the "Internal SD Card" is, but it is not an actual SD card, I do know that.
Are you at all familiar with fastboot? I would assume so, but I would like to know before I go any further.
Yeah, the double boot before the boot animation is normal.
Erebus671 said:
Okay, I'm not exactly sure about what the "Internal SD Card" is, but it is not an actual SD card, I do know that.
Are you at all familiar with fastboot? I would assume so, but I would like to know before I go any further.
Yeah, the double boot before the boot animation is normal.
Click to expand...
Click to collapse
I was assuming it is a SD card, so... Okay, so it is internal memory, so NAND .
I am familiar with fastboot, of course. That's how I was flashing recoveries, radios etc. on the HTC devices : fastboot flash recovery <file.img> etc...
I saw that for Motorola the fastboot commands are a bit different, and this system being somewhat different than it is on HTC devices, I am a bit afraid
Formhault said:
I was assuming it is a SD card, so... Okay, so it is internal memory, so NAND .
I am familiar with fastboot, of course. That's how I was flashing recoveries, radios etc. on the HTC devices : fastboot flash recovery <file.img> etc...
I saw that for Motorola the fastboot commands are a bit different, and this system being somewhat different than it is on HTC devices, I am a bit afraid
Click to expand...
Click to collapse
lol, okay, I'll give you a thanks for that one.
TBH, I don't use the "moto fastboot" commands, you can just use the general fastboot commands, so try this out..
Do a clean install, using fastboot wipe everything:
Code:
fastboot -w
fastboot erase system
fastboot erase preinstall
fastboot erase boot
fastboot reboot (make sure you're pressing the VOL Down button when you press enter)
reboot into recover and erase the Dalvik cache, once all that is done, flash the ROM as usual and see how it goes... Sometimes all you need is a clean install.
That's how most of my problems get fixed.
OK, I am no longer sure if it's a digitizer malfunction.
What I would do is wipe the screen completely clean with a wet PC cloth or something.
Also, try installing a different launcher (Go Launcher, ADW) and check if it does the same thing.
Usually, when the digitizer dies, the symptoms are - digitizer registers random touches without you touching it.
xploited said:
OK, I am no longer sure if it's a digitizer malfunction.
What I would do is wipe the screen completely clean with a wet PC cloth or something.
Also, try installing a different launcher (Go Launcher, ADW) and check if it does the same thing.
Usually, when the digitizer dies, the symptoms are - digitizer registers random touches without you touching it.
Click to expand...
Click to collapse
That sounds like my problem... but to hell with motorola, I'll buy my own digitizer, damned fools sent me a sim locked phone to replace a sim unlocked phone when I am under a carrier that does not have the equipment to support locking the phones to its network...
Erebus671 said:
TBH, I don't use the "moto fastboot" commands, you can just use the general fastboot commands, so try this out..
Do a clean install, using fastboot wipe everything:
Code:
fastboot -w
fastboot erase system
fastboot erase preinstall
fastboot erase boot
fastboot reboot (make sure you're pressing the VOL Down button when you press enter)
reboot into recover and erase the Dalvik cache, once all that is done, flash the ROM as usual and see how it goes... Sometimes all you need is a clean install.
That's how most of my problems get fixed.
Click to expand...
Click to collapse
No fastboot erase data and etc.? Just those? Mmmmkay . Should I do this when the battery is ABSOLUTELY FULL?! Cause yesterday I flashed when the phone was @ ~20%, and today, when the battery reached 15%, it dropped to 4% as I blinked, rofl (fully charged it earlier today).
Erebus671 said:
lol, okay, I'll give you a thanks for that one.
Click to expand...
Click to collapse
read my signature, carefully (I'll edit it to match the current state... soon... some day...)
"I've had the Wildfire, Desire & Desire HD before, so I know flies are not eatable "
God damn it, this post is a fail. Head on to the second page, rofl.
xploited said:
OK, I am no longer sure if it's a digitizer malfunction.
What I would do is wipe the screen completely clean with a wet PC cloth or something.
Also, try installing a different launcher (Go Launcher, ADW) and check if it does the same thing.
Usually, when the digitizer dies, the symptoms are - digitizer registers random touches without you touching it.
Click to expand...
Click to collapse
Erebus671 said:
That sounds like my problem... but to hell with motorola, I'll buy my own digitizer, damned fools sent me a sim locked phone to replace a sim unlocked phone when I am under a carrier that does not have the equipment to support locking the phones to its network...
Click to expand...
Click to collapse
Guys, have you tried Multitouch Visualiser?
I mean seriously... Clean your screen (like I did) with a cloth (not NASA-ultrasmooth-bacteria-remover) and then try it in that program... like I did... see if you get the same outcome...
Formhault said:
No fastboot erase data and etc.? Just those? Mmmmkay . Should I do this when the battery is ABSOLUTELY FULL?! Cause yesterday I flashed when the phone was @ ~20%, and today, when the battery reached 15%, it dropped to 4% as I blinked, rofl (fully charged it earlier today).
read my signature, carefully (I'll edit it to match the current state... soon... some day...)
Click to expand...
Click to collapse
nope.. fastboot -w takes care of that.
The battery thing is simple, once it is fully charged calibrate the battery with a battery calibration app. It's that simple.
I'm not sure what I'm supposed to be reading, the device history? or the thanks message?
---------- Post added at 05:48 AM ---------- Previous post was at 05:46 AM ----------
Formhault said:
Guys, have you tried Multitouch Visualiser?
I mean seriously... Clean your screen (like I did) with a cloth (not NASA-ultrasmooth-bacteria-remover) and then try it in that program... like I did... see if you get the same outcome...
Click to expand...
Click to collapse
I have actually and I've gotten up to 8 fingers on there with fairly accurate precision...
Edit: You'll have to elaborate on the non-eatable flies thing, understand I do not... (I didn't see you point that out until after I posted this)
Erebus671 said:
nope.. fastboot -w takes care of that.
The battery thing is simple, once it is fully charged calibrate the battery with a battery calibration app. It's that simple.
Click to expand...
Click to collapse
I thought the thing with the battery calibration was sorted already (it is a placebo?). Anyway, I'll do that (placebo DOES have effect, rofl).
Erebus671 said:
I'm not sure what I'm supposed to be reading, the device history? or the thanks message?
Click to expand...
Click to collapse
I edited the original post. Oh well, what I meant is... I'm not REALLY a newbie. Not THAT much of a newbie
Erebus671 said:
I have actually and I've gotten up to 8 fingers on there with fairly accurate precision...
Click to expand...
Click to collapse
I can only get FIVE touch points :/
Also, it seems that 5 is the maximum, lol. So how the heck did you get 8 touch points, and even working PERFECTLY :/ https://www.google.ro/search?sourceid=chrome&ie=UTF-8&q=motorola+atrix+multi+touch
-----
WHY WON'T posts merge?! -.-
Formhault said:
I thought the thing with the battery calibration was sorted already (it is a placebo?). Anyway, I'll do that (placebo DOES have effect, rofl).
I edited the original post. Oh well, what I meant is... I'm not REALLY a newbie. Not THAT much of a newbie
Click to expand...
Click to collapse
Uh, no, you're right, the battery life problem was solve, but there is no real solution to the battery calibration issue, that is cause by battery stats remaining over multiple flashes. At least that's how I comprehend it from what I have read in the past. I calibrate my battery on every flash, never once had the problem.
And I edited mine as well, and believe it or not I AM a newbie. I simply seem to not be a newbie (well not a total newbie at least) because I actually follow the first rule of XDA, unlike a lot of the people who have a million questions... Present company excluded... Basically what I just said is, I READ BEFORE I POST. Once again, I will note that I am excluding the present company when I state this.
---------- Post added at 05:58 AM ---------- Previous post was at 05:55 AM ----------
Formhault said:
I can only get FIVE touch points :/
Also, it seems that 5 is the maximum, lol. https://www.google.ro/search?sourceid=chrome&ie=UTF-8&q=motorola+atrix+multi+touch
-----
WHY WON'T posts merge?! -.-
Click to expand...
Click to collapse
hmm, I'll have to test again... I'll let you know what I get.
Edit: Okay, you got me, 5 it is. I seem to have forgotten and over guestimated. XD
Okay... I say again : should I flash ONLY when the battery is full? I know it wasn't much of a problem on HTCs... The difference was I had to make a few battery cycles afterwards so the battery percentage is displayed right.
Formhault said:
Okay... I say again : should I flash ONLY when the battery is full? I know it wasn't much of a problem on HTCs... The difference was I had to make a few battery cycles afterwards so the battery percentage is displayed right.
Click to expand...
Click to collapse
It's not all that important to be fully charged... I do it between 25-30% when I really have to...
Off topic... Is it safe to remove the stock messenger app? Or am I being a newbie?
Erebus671 said:
It's not all that important to be fully charged... I do it between 25-30% when I really have to...
Click to expand...
Click to collapse
As I thought .
I was thinking, somewhat, since the Motorola system is a bit different, it may require a battery closer to full... I had the Motorola V360 before and... oh well, if you know what I'm talking about, nuff said
Formhault said:
As I thought .
I was thinking, somewhat, since the Motorola system is a bit different, it may require a battery closer to full... I had the Motorola V360 before and... oh well, if you know what I'm talking about, nuff said
Click to expand...
Click to collapse
Lol, I know what you're talking about... Horrible customer service aside, I am a tried and true moto fan.
Erebus671 said:
Off topic... Is it safe to remove the stock messenger app? Or am I being a newbie?
Click to expand...
Click to collapse
I remember this part from the time I was using CM7 on my Desire. God, at that time, I thought CM7 is the ONLY ROM, lol.
Some people were saying that you need to remove/replace some libraries & some other additional files in order to be able to fully replace the stock Messaging app. I ended up just adding Handcent SMS and using the option from within its Settings menu to disable the stock Messaging app notification.
Of course, I no longer use Handcent. I was, almost a year ago. Now I'll just wait for MIUI to be fully working on the ATRIX then...
Hello!
Bought a 9100 ( Ihave also a 9100, just for reserve) on bay for 45€,with a little broken frontglass, it is possible to go into download mode also recovery, I have also flashed with all possible rom ( 3 part + repart with pit) all the possible stuff......
RESULT NOTHING!
It does not accept the power button in recovery mode, and it restarts whole the time, as would the power button be non stop on...
PLEASE HELP!
Bin job unless you want to replace the motherboard.
Edit - Or...Perhaps replace home/power buttons first. There might well be a lot more things wrong with it hardware-wise than would appear to be the case.
MistahBungle said:
Bin job unless you want to replace the motherboard.
Edit - Or...Perhaps replace home/power buttons first. There might well be a lot more things wrong with it hardware-wise than would appear to be the case.
Click to expand...
Click to collapse
"Bin job unless you want to replace the motherboard."
What do you mean with this? Bin job = Trash? :cyclops:
Flashing with odin and all the other stuff worked, but it tries to go in the os and break it up....
That's it. You seemed to get a successful Odin flash, yet it's still bootlooping. Which could mean any one (or maybe even a combination) of:-
1) NAND corruption (which would mean a motherboard replacement)
2) If you're lucky, replacing the power & home buttons might enable you to do a factory reset in recovery
3) I've had another thought in the 25 minutes since my last post - perhaps try to do a factory reset through ADB ? This may/may not be possible. How ? Lots of tutorials on here/Google search on how to use ADB. You're facing a lot of reading/research if you want to try this.
Or, it could be other stuff wrong hardware-wise which you don't know about at this point causing the problems, and none of the above may be possible. You're only going to if you try them. So....In order of cost to you, try 3 first, then 2, then you can decide whether 1 is going to be worth it. It might cost you what you paid for the phone again to source a 2nd hand motherboard (or more), plus labour if you're not confident enough to swap the board out yourself & have to pay someone to do it.
MistahBungle said:
That's it. You seemed to get a successful Odin flash, yet it's still bootlooping. Which could mean any one (or maybe even a combination) of:-
1) NAND corruption (which would mean a motherboard replacement)
2) If you're lucky, replacing the power & home buttons might enable you to do a factory reset in recovery
3) I've had another thought in the 25 minutes since my last post - perhaps try to do a factory reset through ADB ? This may/may not be possible. How ? Lots of tutorials on here/Google search on how to use ADB. You're facing a lot of reading/research if you want to try this.
Or, it could be other stuff wrong hardware-wise which you don't know about at this point causing the problems, and none of the above may be possible. You're only going to if you try them. So....In order of cost to you, try 3 first, then 2, then you can decide whether 1 is going to be worth it. It might cost you what you paid for the phone again to source a 2nd hand motherboard (or more), plus labour if you're not confident enough to swap the board out yourself & have to pay someone to do it.
Click to expand...
Click to collapse
Well factory reset is not the problem, when im in the cwm recovery ( I flashed dorimanx 9.43 where a touch is in) i resetted all.
Reset, flash 3 part , not working, flashed 10 different rom with odin and directly in cwm.
I know I bought a *hit, I was blended of the screen logo, I thought it just stuck while the guy have done something wrong...
In that case you're stuck with 2, then 1.
MistahBungle said:
In that case you're stuck with 2, then 1.
Click to expand...
Click to collapse
well i love to play with stuff that I bought wrong.... lets see..
cheers
Keep us informed how you go in this thread
Just sell the phone on immediately.Maybe some mug will think(like you did) it works/can be resurrected.
-------------------------------------------
maybe your an iphone expert
------------------------------------------
theunderling said:
Just sell the phone on immediately.Maybe some mug will think(like you did) it works/can be resurrected.
-------------------------------------------
maybe your an iphone expert
------------------------------------------
Click to expand...
Click to collapse
nah thats not so fine, when I know there is a hardware problem, it will bring bad karma , well display is ok, so what I have seen may has the powerbutton a shorty, so we will see.
I dont think NAND, because formating and wiping and flashing in CWM worked, good. hey there is battery reserve too
BTW: iphone expert, Ive got a dead iphone 4 ( not mine) crawling around, searching a lot for a logicboard for this inhumane part
sh0ne said:
well i love to play with stuff that I bought wrong.... lets see..
cheers
Click to expand...
Click to collapse
I dont know what 3 part firmware Mistahbungle meant(maybe from Phistachio),but I read a thread yesterday from king_below_the_lord.Maybe try that as youve nothing to lose.
http://forum.xda-developers.com/showthread.php?p=35719424
As for selling the phone,all you say is "doesnt boot properly".Then let someone think they can fix it.You are doing nothing wrong,as the phone doesnt boot properly.
I could buy phones every day of the week,but I dont because of ones like yours,and I suspect loads of them have water damage.
-------------------------------------------
maybe your an iphone expert
------------------------------------------
sh0ne said:
Hello!
Bought a 9100 ( Ihave also a 9100, just for reserve) on bay for 45€,with a little broken frontglass, it is possible to go into download mode also recovery, I have also flashed with all possible rom ( 3 part + repart with pit) all the possible stuff......
RESULT NOTHING!
It does not accept the power button in recovery mode, and it restarts whole the time, as would the power button be non stop on...
PLEASE HELP!
Click to expand...
Click to collapse
It really looks like i say this to everyone, but before replacing your hardware and looking at "extreme caution" posts, have you tried nuking your phone? Search hawkerpaul s nuke and try it.
Edit: Just saw that you cannot press power button on recovery. Well then, try everything you can but i think your best bet would be selling it again, if you even buy buttons you will be losing more money, maybe you can open it and try repairing the button or find a workaround like pressing it manually tho.
well bought a s2 for 20€ with a defect screen ( good mainborad , FULL of data like pics.... ) resambeld all, not so dificult, sove samsung for that, and it works like a charm, and my wife (hardcore whatsapp & viber user) is happy too , installed infecteds cm 10.1 v2 , yesterday I saw it brings with my old 2000mAh Battery ( samsung original) 4h! of display! amazing!
Thanks for all guys!