First up. I'm low on battery - some 40% on the optimistic side, so I'm going to avoid trying stuff on my own till someone helps.
It's a SOFT- brick, stuck at M logo :/ and looping restarts. All was well till I went ahead and tried 1% battery mod theming (on the stock odexed ROM - though I wiped cache ) :banghead:
The device is an Indian A 2 w/o 4G ?? Never saw the 4G option under network settings. Nor did the box advertise it. Could be wrong here.
Came with 2.3.6 Stock.
I've managed to pull up a link on the 2.3.5 Edison AT&T FXZ files.. but that's simply not the same phone as mine ( I think the radios differ.. could be wrong ) Also since I'm on 2.3.6 , I suppose I'll be required to edit some XML and overwrite some files?
I also have a 30 day replacement warranty with the online store I bought it from , and as seeing that I have NOT replaced the underlying OS as YET ( albeit a stupid 1% battery mod that didn't work out) , would it warrant an exchange ?
Side note : I DON'T have CWM on boot, but DO have a CWM backup of the stock ROM ( made one last night, though I don't see how it can help me now )
QUESTION :
* Is there any way my CWM backup can help if my phone boot loops ?
* Can an AT&T 4G radio goof up my Indian phone that makes no mention of it's HSDPA+ radio ANYWHERE ( other than the 21MBPs ?? ) .. Here's the link to the product page.
* I can always hope for the 30 day replacement warranty to do it's thing, but in my country, Moto service is sub par. Worth it ?
* Should I give moto-fastboot flash system system.img this a shot with the FXZ I'm downloading right now despite the 2.3.5 and 2.3.6 mismatch ?
This is my first android phone and despite reading up a bit on everything, I messed with a stock odexed ROM , so spare the noobness
The first thing you want to do is pull the battery. At your state, the only way to recover is to use (moto)fastboot or flash with RSD Lite.
I am not sure if the radios are the same. After reading the reviews it seems that it does, however I wouldn't take any chances. There are two things you can do:
1) Flash the fxz. By default the fxz will flash a lot of partitions including the radio, so you will have to edit the file "InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.xml" that is inside of the fxz to just flash the system.img
2) Use (moto)fastboot to flash the system.img. This is much easier so long as you know how. This is the first thing you should try. You can try "(moto)fastboot flash system.img" on its own but you might get an error about unable to write to /system. I recommend that you try these commands:
Code:
fastboot flash mbm allow-mbmloader-flashing-mbm.bin
fastboot reboot-bootloader
fastboot flash mbmloader mbmloader.bin
fastboot flash mbm mbm.bin
fastboot reboot-bootloader
fastboot -w
fastboot flash system system.img
Good luck!
Thanks a lot for the help. I contacted the store and they're giving me two options :
1.Replacement --- Well, it's out of stock, so this is shot.
2.Cash-back/ Credit ---- I could always wait on a new intruging phone. Though I doubt I could find something as cheap and powerful other than the sensation (know what you're thinking).
^ The whole process could take about 2 weeks to get me a new phone. Lame.
If you're absolutely sure about the flashing AT&T's FXZ files, I don't think I'll wait for that refund. Rather like this phone. I hope you've taken into consideration that :
* I'm on 2.3.6 stock odexed.
* I'm NOT from the States. Radios could differ.
* Once I do this and if it doesn't work , there's absolutely NO way that MOTO will take my phone back. Pretty sure the OS will look tampered with. Anyway , there's no service centre in my vicinity.
* If i flash the system image as you mentioned, isn't everything inter-linked in the OS package?? I mean, how can the AT&T modules work with any odd radio?
Thanks again!
Did you already try holding volume up + power when booting, then when you get to a screen with the android and an exclamation point inside a triangle pressing VOL UP + DOWN at same time to factory reset?
Sent from my MB865 using xda premium
0razor1 said:
Thanks a lot for the help. I contacted the store and they're giving me two options :
1.Replacement --- Well, it's out of stock, so this is shot.
2.Cash-back/ Credit ---- I could always wait on a new intruging phone. Though I doubt I could find something as cheap and powerful other than the sensation (know what you're thinking).
^ The whole process could take about 2 weeks to get me a new phone. Lame.
If you're absolutely sure about the flashing AT&T's FXZ files, I don't think I'll wait for that refund. Rather like this phone. I hope you've taken into consideration that :
* I'm on 2.3.6 stock odexed.
* I'm NOT from the States. Radios could differ.
* Once I do this and if it doesn't work , there's absolutely NO way that MOTO will take my phone back. Pretty sure the OS will look tampered with. Anyway , there's no service centre in my vicinity.
* If i flash the system image as you mentioned, isn't everything inter-linked in the OS package?? I mean, how can the AT&T modules work with any odd radio?
Thanks again!
Click to expand...
Click to collapse
Ok I am from India, I was in the same scenario you were in, the FXZ on this forum WILL NOT help, Indian ATRIX 2.
What I did, simply barged in MOTOROLA SERVICE CENTRE (Local to your city) and told them, i was doing a software upgrade (OTA) and the it hung, so I removed the battery and this issue started.
The person in the service center responded Quote: " That is what you should not be doing, when you do OTA update"
He then re flashed the whole phone to stock 2.3.6, as they would be having Indian FXZ and gave back my phone in 30 min.
I am now on Victory ROM and still enjoying flash MOD and ROMS, the lesson I learned is, do not flash any MOD unless it is working and confirmed from others ( provided you do it right way)
So go to service center, and your issue will be solved.
kisnerct said:
Did you already try holding volume up + power when booting, then when you get to a screen with the android and an exclamation point inside a triangle pressing VOL UP + DOWN at same time to factory reset?
Click to expand...
Click to collapse
Did that. Since I've flashed a battery update.zip to the ROM I don't see how it could have helped me ...
zeph_syk said:
Ok I am from India, I was in the same scenario you were in, the FXZ on this forum WILL NOT help, Indian ATRIX 2.
...............
..........He then re flashed the whole phone to stock 2.3.6, as they would be having Indian FXZ and gave back my phone in 30 min.
..............
..........I am now on Victory ROM and still enjoying flash MOD and ROMS, the lesson I learned is, do not flash any MOD unless it is working and confirmed from others ( provided you do it right way)
So go to service center, and your issue will be solved.
Click to expand...
Click to collapse
Well, I always knew I could do that. Have been messing around with moto and RSD from the L6/L7 days
There's no service center close to my place. That's the only problem. I wish there was one.
Questions :
* anyway they would give me the FXZ files ?? I could beg :/ If anything , I'd be doing a LOT of people favors
* You're using CWM on boot ? is it ? Cause I didn't and I suppose that was simply asking for it . Also, ROM manager flshes recovery for a LOT of Moto phones.. Could I get by, by using the Atrix 4G recovery or something similar. Whats the worst that could happen ? Soft brick or hard ?
0razor1 said:
First up. I'm low on battery - some 40% on the optimistic side, so I'm going to avoid trying stuff on my own till someone helps.
It's a SOFT- brick, stuck at M logo :/ and looping restarts. All was well till I went ahead and tried 1% battery mod theming (on the stock odexed ROM - though I wiped cache ) :banghead:
The device is an Indian A 2 w/o 4G ?? Never saw the 4G option under network settings. Nor did the box advertise it. Could be wrong here.
Came with 2.3.6 Stock.
I've managed to pull up a link on the 2.3.5 Edison AT&T FXZ files.. but that's simply not the same phone as mine ( I think the radios differ.. could be wrong ) Also since I'm on 2.3.6 , I suppose I'll be required to edit some XML and overwrite some files?
I also have a 30 day replacement warranty with the online store I bought it from , and as seeing that I have NOT replaced the underlying OS as YET ( albeit a stupid 1% battery mod that didn't work out) , would it warrant an exchange ?
Side note : I DON'T have CWM on boot, but DO have a CWM backup of the stock ROM ( made one last night, though I don't see how it can help me now )
QUESTION :
* Is there any way my CWM backup can help if my phone boot loops ?
* Can an AT&T 4G radio goof up my Indian phone that makes no mention of it's HSDPA+ radio ANYWHERE ( other than the 21MBPs ?? ) .. Here's the link to the product page.
* I can always hope for the 30 day replacement warranty to do it's thing, but in my country, Moto service is sub par. Worth it ?
* Should I give moto-fastboot flash system system.img this a shot with the FXZ I'm downloading right now despite the 2.3.5 and 2.3.6 mismatch ?
This is my first android phone and despite reading up a bit on everything, I messed with a stock odexed ROM , so spare the noobness
Click to expand...
Click to collapse
Dont worry, I am an Indian user, been in this situation. All I did was, took a chance. I flashed 2.3.5 Stock AT&T FXZ to my Indian Atrix 2 using the script given here on XDA and it came to life within few minutes. Hardware on Indian Atrix 2 and US device are exactly the same.
Just install AT&T FXZ, root it using 2.3.5 one click, then install bootstrap recovery and restore your previous backup and you will have exact working phone back in your hands, I did exactly the same and mine is up and running, no radio issues or anything at all.
The only stupid thing I did was, I took backup of Indian ROM after deleting some system files, which makes my phone's messaging app force close everytime I receive a message. Once you get yours up and running, would you be kind enough to upload your clean CWM Backup (or take a new one, after you fix it, if previous one has your personal stuff) and upload it to dropbox or some file sharing site?? It can help me fix my messaging issue too. And since Indian firmware is not restrictive like AT&T rom I beleive some Devs here can use it to make a fantastic overclocked rom, been looking for that since day one, all custom ones are AT&T based, so restrcitive.
Good luck....
---------- Post added at 10:02 PM ---------- Previous post was at 09:55 PM ----------
The one I used was from this thread http://forum.xda-developers.com/showthread.php?t=1539167
Its a script, you just need to connect your phone in fastboot mode (Vol Up+Vol Down pressed together and power on, select Fastboot from 4 options), and then click on bat file (Its name is something like return to stock.bat or something, dont remember exactly now). Then just wait for few around 8-10 minutes and it will do everything automatically and you will have your phone working in no time
Thanks for that info , but ..
http://forum.xda-developers.com/showpost.php?p=23469067&postcount=5
As you can see , well, the problem is flashing these files to a 2.3.6 device. :/
Anyway the store has offered a refund so I'm hopping on the bandwagon and biding out my time .
Here's what I plan to do :
See if I can somehow score a ONE S at a reasonable price else I'm just going to buy this phone again a month from now, at a more respectable street price. I'm judging ~ 21K and no more for this phone a month from now with the S advance et all releasing soon enough. 22.5K is simply too steep with ONLY ONE service center in my state :/ WTH :/
IN USD speak , that's ~ 400$ unlocked compared to the ~ 450 I bought one for a week back. I know that's cheap , but we pay in whole, no contracts for us, so the pinch is bad
This is what the service center rep had to say to me :
ASK MOTO FOR THE FXZ FILES :/ ( why they don't already have the boot files on an 8 month old phone is beyond me )
And MOTO customer support asked me to hard reset .. as if I didn't already try. They're asking me to goto the service center that hasn't and FXZ files :/
And the next cloese center is about ~ 80 Miles away and their registered phones are out of service :/ The next closest service center is about ~ 200 Miles away and I'm done hoping that they'd fare any better
Side : I plan to upload my CWM files ANYWAY after of course I change my Google account credentials But you'll have to wait a month for them as I'm far off from a connection that can upload ~ 900MB reliably. Plan to stick around this sub forum regardless of whether I buy the same phone or not as one of my friends has one and I'm the go-to techie around here :/
For all you out there, these CWM files are based around the MB not ME version of the files so it SHOULD* work on AT&T phones without all the AT&T crapware and should require NO hacks / tweaks to work the hotspot and other features
0razor1 said:
Did that. Since I've flashed a battery update.zip to the ROM I don't see how it could have helped me ...
Well, I always knew I could do that. Have been messing around with moto and RSD from the L6/L7 days
There's no service center close to my place. That's the only problem. I wish there was one.
Questions :
* anyway they would give me the FXZ files ?? I could beg :/ If anything , I'd be doing a LOT of people favors
* You're using CWM on boot ? is it ? Cause I didn't and I suppose that was simply asking for it . Also, ROM manager flshes recovery for a LOT of Moto phones.. Could I get by, by using the Atrix 4G recovery or something similar. Whats the worst that could happen ? Soft brick or hard ?
Click to expand...
Click to collapse
The service center do not have FXZ stored in there system, AFAIK they connect the phone to an application, this APP contacts the motorola server and recognize the build of this phone and then downloads the relative FXZ and flashes it! This is all done by the APP
I am really not sure if we can use the Atrix 4g recovery, but its unlikely we can do that.
Now i do have a copy of stock 2.3.6, but we cannot use the hotspot App and other system apps directly as they are not deodexed. Correct me if I am wrong please
Well , those guys simply said NO !! And they asked ME TO get MOTO to send them the FXZs .. as if .. :/
Do you mean to say that the app downloads a 500 MB compressed file EVERYTIME one flashes a phone ?? Very unproductive. :/
I just hope MOTO knows what they're doing dishing out service contracts to people who apparently don't know how things are meant to be.
Anyway ,I've recieved the refund email from flipkart and this phone's going back. Lets hope I pick up a better phone in a month , else its back to another A 2. Great phone, sub-standard service is all that's pulling it down.
And with the imminent launch of an S4 proccy in the rumored Atrix2 w/ a 720p screen, I think the future holds a lot more to offer than the A2's OMAP -- heck , I have problems decoding HP h264 vids --- B frames anyone ? I believe even the lowly adreno 220 and the Mali-400 can handle them with ease.
Furthermore, correct me if I'm wrong ,the A's processor claims to be dual channel capable, but with one channel available to each core, is that really what we're looking at ?
0razor1 said:
Well , those guys simply said NO !! And they asked ME TO get MOTO to send them the FXZs .. as if .. :/
Do you mean to say that the app downloads a 500 MB compressed file EVERYTIME one flashes a phone ?? Very unproductive. :/
I just hope MOTO knows what they're doing dishing out service contracts to people who apparently don't know how things are meant to be.
Anyway ,I've recieved the refund email from flipkart and this phone's going back. Lets hope I pick up a better phone in a month , else its back to another A 2. Great phone, sub-standard service is all that's pulling it down.
And with the imminent launch of an S4 proccy in the rumored Atrix2 w/ a 720p screen, I think the future holds a lot more to offer than the A2's OMAP -- heck , I have problems decoding HP h264 vids --- B frames anyone ? I believe even the lowly adreno 220 and the Mali-400 can handle them with ease.
Furthermore, correct me if I'm wrong ,the A's processor claims to be dual channel capable, but with one channel available to each core, is that really what we're looking at ?
Click to expand...
Click to collapse
You should complain about that service center. I flashed files as stated above and it worked.
I have been waiting someone to upload backup of Indian firmware but I am kind of fed up waiting for it to happen, so just now I went to service center and the guys there told me that they don't have stock firmware for it BUT then he spoke to someone in Chennai and I am told that they are going to receive stock firmware in an hour or two and he will flash it and let me know by 4pm today, so basically they do have stock FXZ, not every center may have it ready but its with them.
So I have left my phone there till evening, he said he will flash the stock firmware and if it doesn't work they will process a replacement for me and I will get a new phone. Simple as that. Motorola service centers are managed by Redington, if they are refusing to honour your service request you should complain to Moto as well as Redington. We need to let them know that they cant take us for granted after selling a phone.
And since you are going to get a refund anyway, why not try and flash the files I recommend? You have already bricked your phone, so even if it doesn't work you are still going to get a new phone. N I am sure when it works you will change your mind This is a fantastic phone as per my opinion. I would anyday stick with it.
---------- Post added at 12:43 PM ---------- Previous post was at 12:19 PM ----------
And all people who may need Indian Stock firmware stay tuned here, as soon as I get my phone back I am going to take a CWM Backup and upload it here, since I have 3G my upload speeds are not that good, so it will take at-least 2 days after I receive my phone, so that I can upload it here but I am definitely going to do it. AT&T users will benefit a lot from this. Just waiting desperately to get my phone back.
Sorry folks, Moto service is really bad. The guys at service center initially told me they will receive FXZ to flash, but seems like they didn't, they are processing my request for a replacement shame Moto, your service centers doesn't even have firmware to flash.. I am gonna complain to Moto as well as Radington. Its such a simple task for which they are giving me a replacement, if I have FXZ I can do it myself.
finally ordered a razr for 26.4k, a steal if u ask me. lets hope it pans out better than the A2..
Related
Disclaimer: I will not be held responsible for any damage to your phone, your PC or indeed your life from following this guide. The steps in this guide worked for me. If you have problems uninstall everything and start from Step 4 again. Doing this kind of thing could affect your warranty and all that so have a long hard think about it before you go ahead
US Owners - If you flash the UK firmware, you will lose 3g and wifi calling app etc... There are fixes for this problem that can be found on other Forums. A guide on how to restore this which has worked for others is HERE
##WARNING: be careful when flashing 2.51 firmware, firstly its patched so root isn't achievable by the usual methods, and isn't easy to downgrade back to other firmware - I suggest you search and read the various topics on it. My advice is to use 2.21 UK or 2.34 Deblur firmware##
This guide will show you how to debrand your Motorola Defy (Eg bought on T-Mobile UK and want generic UK firmware), or indeed restore the phone if you brick (Eg removing important apps that you shouldn’t have touched!!)
Props go to jutley (Modaco)for his debranding guide for the flipout, and dkspook (Modaco) for his information in other threads, and anyone else who thinks they may have contributed, oh yeah and my Mum.
##Disconnect phone from PC##
STEP 1 Download usb drivers here below
Motorola Drivers Here
STEP 2 Download the debranded Firmware here (To debrand to generic UK I used the one marked UK - choose the one for your country)
Choose Firmware Here
STEP 3 Download RSDLite - I used v4.9, I found earlier versions would not work. Get it here.
RSDLite 4.9 Here
STEP 4 Install the USB Drivers and the RSDLite program and reboot PC
STEP 5 Extract the firmware file you downloaded a while ago. Then copy the .sbf firmware file to c:\Program files\Motorola\RSDLite folder (installation directory for RDSLite). this should come out as JRDNEM_U3_2.21.0_SIGNED_UCAJRDNEMARAB1B80AA028.0R_USAJORDANRTGB_P026_A007_HWp3_S
rvice1FF.sbf for the UK one.
STEP 6 Start the RSDLite program now where it says filename press the select button and find the .sbf firmware file in c:\Program files\Motorola\RSDLite (it should default to this folder) and select the (sbf) file some details will appear on the right hand side.
STEP 7 We now need to boot the phone into the bootloader (as above make sure the phone is disconnected from USB – not sure if matters tho!). Hold the volume up and then power the phone on, after about 5 seconds release the buttons and the bootloader should display - it will show the version and a battery check. Now plug in the USB cable and it should install the drivers . Once the driver installation has finished you should see the phone appear at the bottom of the RSDLite program window under `port 1` - Once this is there you are ready to flash the firmware. NB: I had issues getting it to show a number of times. Uninstalling RSDLite/Drivers, rebooting PC, and then reinstalling these resolved this issue.
STEP 8 Press the start button on the RSDLite and just relax while your device gets flashed,debranded etc. you will see a progress status on the right hand side wait till it reaches 100% but please do not disconect it will reboot the phone automaticly and restart the phone.And just wait untill android comes up and fully running untill you disconnect it should read (PLEASE START PHONE MANUALY) on RSDLite when this shows it is safe to unplug.
Hopefully now you will have a debranded/unbricked phone.
One thing I noticed that was cool is that the data partition stayed intact for me when I debranded, meaning all my settings and installed app (providing you hadn’t moved stuff to /system) were still there after the process – cool! The only thing you will have to do is re-root the device.
Hope you find this useful and I look forward to a great community for the Defy!
Nice job! This worked perfectly. We now just need the tmo us FW. I'm kind of iffy about messing with my phone much more until I have a failsafe.
nitewalkergr said:
Nice job! This worked perfectly. We now just need the tmo us FW. I'm kind of iffy about messing with my phone much more until I have a failsafe.
Click to expand...
Click to collapse
Whats the benefit of the T-Mobile US Firmware - some kind of extra functionality? If we could get it, we could flash by this method and flash back if we didn't like it anyways I suppose.
In theory this method is a failsafe tho because if you mess any thing up you can get back to a different firmware. I must say I personally would like to get my hands on the original T-Mobile UK .sbf, just in case I wanted to put it back to its original state for returns/repair, so if anyone has found it (I haven't yet) please let me know.
If a tmo us user flashes with the uk FW they lose 3g.
A tmo us or just generic us fw would give us the clean sweep option while keeping our 3g.
Can I use the Uk Firm for a Vodafone Spain Defy??
Higgsy said:
Whats the benefit of the T-Mobile US Firmware - some kind of extra functionality? If we could get it, we could flash by this method and flash back if we didn't like it anyways I suppose.
In theory this method is a failsafe tho because if you mess any thing up you can get back to a different firmware. I must say I personally would like to get my hands on the original T-Mobile UK .sbf, just in case I wanted to put it back to its original state for returns/repair, so if anyone has found it (I haven't yet) please let me know.
Click to expand...
Click to collapse
Hi Higgsy, long time no see! Guess its cos you sold your Hero/G2 Touch so you have no need to visit htcdevscene, Its dead there now a days lol. I just got my Defy from T-Mobile UK. I here your after the T-Mobile UK Defy firmware? and I havent rooted or touched the firmware on mine at all, all i've done is charged it up and used as my day to day phone. If you know of a way to pull the firmware from the phone i will gladly upload it for you, if its even possible?
P.s. still got my Hero/G2 Touch not sure if i wanna sell the lil work horse yet lol, what are they selling for these days?
pedrogamo said:
Can I use the Uk Firm for a Vodafone Spain Defy??
Click to expand...
Click to collapse
Yes, I have a simfree defy, and this is my versión. Same version for France, UK, Spain, etc
Cesar Pipes said:
Yes, I have a simfree defy, and this is my versión. Same version for France, UK, Spain, etc
Click to expand...
Click to collapse
Thanks!! I did it. Now my Defy is debranded. Bye Vodafone!
dj_destruction said:
Hi Higgsy, long time no see! Guess its cos you sold your Hero/G2 Touch so you have no need to visit htcdevscene, Its dead there now a days lol. I just got my Defy from T-Mobile UK. I here your after the T-Mobile UK Defy firmware? and I havent rooted or touched the firmware on mine at all, all i've done is charged it up and used as my day to day phone. If you know of a way to pull the firmware from the phone i will gladly upload it for you, if its even possible?
P.s. still got my Hero/G2 Touch not sure if i wanna sell the lil work horse yet lol, what are they selling for these days?
Click to expand...
Click to collapse
Now then DJD!
Na we need the .sbf file for it but it no biggy at the moment. Get it rooted mate - easiest way is to download z4root from the market - works a treat and roots in like 10 secs lol.
Stopped going on htcdevscene for a number of reasons, firstly i could never get on the site and secondly i felt the way it was run was very inconsistent.
Just sold my Hero - they are going for between 80-120 on ebay the top end is for brand new boxed. I have just sold mine to a mobile recycle place for £103. This phone is different gravy to the hero for sure.
Anyway mate look forward to seeing you around again
Thanks for this guide Higgsy, very easy to follow even for a noob like me.
I have now said goodbye to Vodafone's crap a mere 20 minutes after opening the box with my shiny new DEFY in that was delivered today.
milesg said:
Thanks for this guide Higgsy, very easy to follow even for a noob like me.
I have now said goodbye to Vodafone's crap a mere 20 minutes after opening the box with my shiny new DEFY in that was delivered today.
Click to expand...
Click to collapse
No probs - Gone be the dirty network custom apps and splash screens!!
Done too. Thank you.
EDIT: Just reflashed and then calibrated the compass. Seems to be working now. Sorry for the unnecessary message.
Ok, having taken the phone out since I got rid of the Vodafone stuff, I've discovered that the GPS is no longer working. I've got GPS Test on it and it only sees one satellite where before it saw a load. I'm going to reload the firmware now, but does anyone have any ideas?
Higgsy what are the benefits of rooting and flashing the generic unbranded software apart from getting rid of the t-mobile rubbish?
tim440 said:
EDIT: Just reflashed and then calibrated the compass. Seems to be working now. Sorry for the unnecessary message.
Ok, having taken the phone out since I got rid of the Vodafone stuff, I've discovered that the GPS is no longer working. I've got GPS Test on it and it only sees one satellite where before it saw a load. I'm going to reload the firmware now, but does anyone have any ideas?
Click to expand...
Click to collapse
Hmm strange My GPS is fine, locks on in like 5 secs, maybe try rebooting with GPS switched on, if you haven't already done so.
DJD,
No real benefits apart from getting rid of any tmobile crap, there isn't much bloatware in the tmobile uk build anyways. I just like generic lol. And as for rooting - please tell me that question is joke surely as a seasoned veteran you know what that is geezer
I know rooting opens up a world of goodies but there arent any goodies for this phone yet in the way of ROMS, at least thats what i can gather so far lol. Can it be over clocked and JITenabled yet? after rooting it of course, sorry im being lazy n not google-ing lol.
Plus for my totally blonde moment if i flash the generic uk firmware would it still mean i could get the over the air 2.2 update when it is released by motorola before t-mobile release their bloatware version?
dj_destruction said:
I know rooting opens up a world of goodies but there arent any goodies for this phone yet in the way of ROMS, at least thats what i can gather so far lol. Can it be over clocked and JITenabled yet? after rooting it of course, sorry im being lazy n not google-ing lol.
Plus for my totally blonde moment if i flash the generic uk firmware would it still mean i could get the over the air 2.2 update when it is released by motorola before t-mobile release their bloatware version?
Click to expand...
Click to collapse
JIT can be enabled - its not stable imo - I tried it before, gonna have a better look at it.
i would expect you will be able to get the generic 2.2 update, to be fair, I think we will be flashing roms by that time anyways
Anyway stop being a ***** and get it rooted
OI lol,
Just downloaded z4root will put it on my memory card n get root tomorrow me thinks.
p.s z4root is no longer on the market, found the z4root.apk in a thread on here tho luckily lol.
Ok, now I do have a problem. I've flashed the non-branded rom and very happy with it, but my in-call speaker has failed this morning. This seems to be a common problem with the Defy and I suspect it needs replacing or repairing, but I need to put back the branded rom to have the phone in warranty, don't I? How do I even begin to go about that?
tim440 said:
Ok, now I do have a problem. I've flashed the non-branded rom and very happy with it, but my in-call speaker has failed this morning. This seems to be a common problem with the Defy and I suspect it needs replacing or repairing, but I need to put back the branded rom to have the phone in warranty, don't I? How do I even begin to go about that?
Click to expand...
Click to collapse
You can't unless you can find the vodafone .sbf sorry mate it was mentioned at the top of the post.
They probably wouldn't know anyway, just deny all knowledge if they say anything.
Hello everyone,
I just bought a Galaxy SII skyrocket from ATT few days ago. I did root and it went fine.
today I figured I'll try to load on it android 4.0 ICS and followed the guide from here (can't post links...)
After I shut it down I tried rebooting it but nothing happens.
I'm getting only black screen. nothing is on the display, nothing vibrates when I press the power, no responds at all from the phone.
I tried resetting after taking out battery but still can't get anything from the device.
I've being searching all day to fix it and saw the home made jig guides but as I understand it will not work if I have totally black screen.
I've tried One Click unbrick but it wont recognize the phone.
I've tried with Samsung's Kies but it wont read the phone either.
I've tried Heimdall Frontend and it won't recognize the device.
when I plug the USB cord to my windows machine I see the hardware found as "QHSUSB_DLOAD" but that's as far as I get now.
is there any remedy for this?
If i return it to ATT will they know it was rooted after they fix it? I just had it few days and already messed it up.
anyone have any ideas I can try please?
thanks for any help.
Well for one the android ics 4.0 leak is for the international gs2 so thats where you went wrong. The international sgs2 is different then the att ags2, and the skyrocket is completly different then tye sgs2. You CANNOT flash files from any other device on the skyrocket ( with the exception of the tmobile sgs2 ). . Take the battery out. Put it back in. Now while volume up volume down, and power plug in the usb cable to the phone and pc. See if it get into download mode. If not you bricked your new phone trying to flash software intended for a different device. Let this be a learning experience. Always read extensively, and never ever try to flash stuff you do not find here on xda in the skyrocket forum.
+1 silver03wrx
This is exactly what happened with my first Skyrocket .. however, I took the same release you found (the International leak for SGS2 ICS) and was in the mist of modifying it for the Skyrocket .. I had everything working (to my knowledge) .. but where I screwed up .. in my final zip (ready for flashing), I forgot one major component .. I left the original ICS boot.img in the zip !!! DUH !!!
So, I got the same result, bricked my phone totally .. no response at all, no screen, no vibration, no download .. nothing.
Now I was able to get another through AT&T's Warranty Repairs, so I am back up and running .. I have 14 days in which to return my bricked one (which I haven't yet) .. I ordered a USB JIG .. so I am waiting on that to arrive to see if the phone REALLY is BRICKED before shipping it to AT&T.
As you can see from my signature .. I have a I9020A Nexus S (AT&T) in which yesterday I installed ICS 4.0.3 successfully and everything is working great (with much modification and playing around) .. I have been playing with it all day .. and loving it. I WANT THIS ON MY SKYROCKET .. LOL
Thats awesome. I have not even playd with ics at all. But am looking forward to it on my skyrocket. Supposed to work better for multi core, and hardware acceleration
silver03wrx said:
Thats awesome. I have not even playd with ics at all. But am looking forward to it on my skyrocket. Supposed to work better for multi core, and hardware acceleration
Click to expand...
Click to collapse
Can't wait either .. will be sweet.
The Nexus S (although a good phone) was a challenge to get working with ICS since the OTA 4.0.3 that came out was for the TMO version not AT&T .. so the little playing around with the way I put it on the phone actually worked .. LOL
* Fastboot CWM recovery.img to Nexus
* Flashed TMO signed original image (Gingerbread 2.3.6) with CWM
* Rebooted to full access (of course, no signal being TMO)
* Fastboot CWM recovery.img to Nexus
* Flashed TMO ICS 4.0.3 with CWM
* Fastboot AT&T radio.img (UCK**) before first boot into ICS
Reboot the Nexus S .. ICS came up, signal there, data there, about phone shows 4.0.3 installed with AT&T Baseband .. it was beautiful.
Thanks guys for the reply.
Sure was an expensive lesson.
I used to have iphones before so I expected the galaxy to be stupid proof like that other fisher price toy. i guess with greater power comes greater responsibility.
I ordered the USB jig hope this will let me get into download mode but the more I read about it the more I doubt it will work i my situation.
anyone think there is a chance or am i wasting my time waiting for it?
Its always worth a try, and you will have it for futre use incase u run into a problem.
I'm completely new to the android experience, this is my first smartphone, ever. I recently purchased an unlocked myTouch 4G and from time to time I would plug my phone into it's charger and it would just cut off and reboot, and stay in this reboot cycle anywhere from 1 - 15mins.
I'm not sure what the issue could be, I don't have a warranty for the phone. I factory reset it using the software since i can't hard reset it from the bootloader. If I try to do that from the bootloader it will just take me through the rebooting cycle again. When I boot into the bootloader it's frozen for about 5 seconds and shows some error about a ZIP file on my SD card not being found (I'm assuming it's looking for an Android image).
This reboot cycle mostly happens when I'm dealing with plugging it in a charger, rarely it will do this when I power off the phone or reboot it from the software (the proper way). Unless I take the battery out, while the phone is off, I never pulled the battery while the phone is running.
What are some options available to me?
Go here
http://forum.xda-developers.com/showthread.php?t=1244018
and follow the instuctions. It will give you a link to the zip file the bootloader is looking for.
Sent from my HTC Glacier using XDA
dead links
Megaupload is dead, I can't use that post. I'm not even sure what the poster is informing people to do, looks like a downgrading. I'm not trying to downgrade, my phone is stock (as far as I know, it's running froyo 2.2.1).
Also I have no clue how to go into adb.
Here is Froyo http://www.4shared.com/zip/xa6viHf-/PD15IMG_221_.html
You won't be downgrading. Just download and flash the file. Its froyo.
jjbadd385 said:
Here is Froyo: 4shared.com/zip/xa6viHf-/PD15IMG_221_.html
Click to expand...
Click to collapse
^I'll try this.
Does anyone know a specific reason why this happens to the phone? is it the hardware or software/apps?
Also, is there a valid link to a Gingebread update from HTC/Tmobile? (valid please, megaupload doesn't exist anymore.)
Here is Gingerbread, although you may want to consider rooting and using a flashable Gingerbread Rom, unless you are trying to keep it Stock. http://www.4shared.com/zip/OrXR0864/PD15IMG_234_.html
Sent from my HTC Glacier using XDA Premium.
Scared
I'm still thinking about whether or not to flash these, I just did an OTA update and thought the issue was fixed until after a few reboots the issue started happening again.
I have questions I would like answered because I don't know what's going on:
Is this a hardware or software issue? Because if it's hardware I think I'll just send the phone back for a refund. If it's software then I'm sure I can just flash a completly different version of android and it'll go away (although not 100% sure)
I snooped around these forums and Google and failed to find a solid answer.
jjbadd385 are these links you're sending me ROMs from tmobile, stock android, or another source??
I don't want to cause any damage to the phone when I could just send it back and buy another, only reason I don't want to send it back just yet is beause if I can find a fix on these forums then id be happy.
Might be hardware just send it back and don't deal with non of this specially if u can still return it u might regret it later when u can no longer get a refund or exchange it for a different one just my .02$
Sent from my My Touch 4G using XDA
I have a very strange problem, and would require help. I had accidently flashed the Atnt ics version on my Asia (indian) version of atrix 2. These are the steps that i have followed.
Note: I appreciate Jimbridgman, for guiding me via pm to help me solve this.
1. Atrix 2 MB865 asia version. (non atnt) purchased and using in India.
2. Had SEARET rom ics.
3. After it came back from the service center (1 month and 7days, it was with them) everything was fine. But the camera app was not working. The moment i opened the camera app, screen flicked and stayed on the same screen. But the app was active as background app. Multitasking window showed it.
4. Thought of reflashing ics,hoping to fix the camera issue. But few months back, searched for official moto ics and never used it. Something as inline ics. So flashed without realising that it was atnt's ics. (using RSD)
5. Phone booted with atnt logo and i was dumbstruck. (i was aware that we should never flash international atrix 2 with atnt. (Hardware incompatibility.
6. Tried to reflash the SEARET rom but cdt.bin in step 7, failed every time. was using rsd lite 6.
7 tried other rom but same,
8 tried jim's script from ics ti gb. and got soft bricked.
9 was able to get fastboot and the screen to see "motorola dual core" (but it was stuck there).
10. Was reflashing atnt's ics again to atleast use the phone. But the battery just gave away it last breath at the climax.
Now cannot charge the battery and reflash. (will get an external charger and pump up some juice in the battery.
Now as i was being guided by Jim regarding the issue, im posting his reply
Jim : "Sorry to say but you are toast. If you have an international version, you can NOT flash the AT&T version, it will lock to the phone to AT&T harware ONLY, and if you try to flash any other versions it will brick.
If you can get the phone to boot and can get into it with adb you can wipe the CID partition and flash an international firmware, but if you are truly bricked and it will not power on, the only thing you can do is, buy an Atrix2 off of ebay or the like, that has a broken screen and replace the parts inside with the ones from the phone you buy that has a broken screen... That really is the ONLY way that I know of, sorry. "
Ebay doesn't have any broken international atrix 2 for sale. I reside in New Delhi, India. And would appreciate if any body can guide me get a new motherboard for my phone. Gaffar market (Indian will be aware of this market) just ignore a moto phone like a step son. And hardly anybody agrees to trouble shoot. And the person who was willing to reflash the ROM and just try to fix the phone quoted 2400/- (did not mention that he will change the motherboard or what.) even i was not aware of the motherboard replacement part (got to know from Jim)
Now can anyone try and help this poor soul :crying:
chayan18885 said:
I have a very strange problem, and would require help. I had accidently flashed the Atnt ics version on my Asia (indian) version of atrix 2. These are the steps that i have followed.
Note: I appreciate Jimbridgman, for guiding me via pm to help me solve this.
1. Atrix 2 MB865 asia version. (non atnt) purchased and using in India.
2. Had SEARET rom ics.
3. After it came back from the service center (1 month and 7days, it was with them) everything was fine. But the camera app was not working. The moment i opened the camera app, screen flicked and stayed on the same screen. But the app was active as background app. Multitasking window showed it.
4. Thought of reflashing ics,hoping to fix the camera issue. But few months back, searched for official moto ics and never used it. Something as inline ics. So flashed without realising that it was atnt's ics. (using RSD)
5. Phone booted with atnt logo and i was dumbstruck. (i was aware that we should never flash international atrix 2 with atnt. (Hardware incompatibility.
6. Tried to reflash the SEARET rom but cdt.bin in step 7, failed every time. was using rsd lite 6.
7 tried other rom but same,
8 tried jim's script from ics ti gb. and got soft bricked.
9 was able to get fastboot and the screen to see "motorola dual core" (but it was stuck there).
10. Was reflashing atnt's ics again to atleast use the phone. But the battery just gave away it last breath at the climax.
Now cannot charge the battery and reflash. (will get an external charger and pump up some juice in the battery.
Now as i was being guided by Jim regarding the issue, im posting his reply
Jim : "Sorry to say but you are toast. If you have an international version, you can NOT flash the AT&T version, it will lock to the phone to AT&T harware ONLY, and if you try to flash any other versions it will brick.
If you can get the phone to boot and can get into it with adb you can wipe the CID partition and flash an international firmware, but if you are truly bricked and it will not power on, the only thing you can do is, buy an Atrix2 off of ebay or the like, that has a broken screen and replace the parts inside with the ones from the phone you buy that has a broken screen... That really is the ONLY way that I know of, sorry. "
Ebay doesn't have any broken international atrix 2 for sale. I reside in New Delhi, India. And would appreciate if any body can guide me get a new motherboard for my phone. Gaffar market (Indian will be aware of this market) just ignore a moto phone like a step son. And hardly anybody agrees to trouble shoot. And the person who was willing to reflash the ROM and just try to fix the phone quoted 2400/- (did not mention that he will change the motherboard or what.) even i was not aware of the motherboard replacement part (got to know from Jim)
Now can anyone try and help this poor soul :crying:
Click to expand...
Click to collapse
well spending 2400 for atrix 2 is better than buying a new phone.if any one guarantees that he will repair your phone get it repaired for 2400.
Sent from my ME865 using xda premium
Of you're in warranty period, then give it to service station saying you just took an ICS OTA and now the phone wouldn't work! Or any better lie you could come up with
Even if it ain't in warranty, ask them how much it would cost to fix it. If it's lesser than 2k, then get it done by them.
- - - - - - - - - - - - - - - - - - - - - - - - - -
LIFE!
IT'S WHAT YOU MAKE OUT OF IT!
You could try using the fastboot commands to flash the SEARET ICS fxz. To do this you will need to get to get the moto-fastboot executable and the android SDK installed.
There is a thread in here I think it is in the General section, that explains how to flash the fxz with the fastboot commands. You will need to flash EVERY part of the SEARET firmware to be successfull and not skip any parts of it when using the fastboot commands.
I have seen others that were getting cdt.bin errors avoid it, by using the fastboot commands, but the only worry I would have is since it has the at&t firmware on it, if it will hard brick or not.
@shubham41230 well they cannot guarantee the fix and cannot be trusted to leave the phone for a day. but if nothing works. They will be the last resort.
@Lifehacker7 can a failed OTA update give the fastboot screen with ''flashing failed" message on top?
@jim the post you forwarded to help to charge the battery did not work. Or mayb i could not mix up the step efficiently to get the phone to charge. Cannot even try fastboot command (battery doesn't have charge) . Can you be kind enough to expalin why can it cause a hard brick if atnt Rom is there. And if gets hard bick. Will changing the motherboard revive it. Cause then i will first chk for availability of motherboard and try the commands (but after getting the damn battery charged). Else will reflash the atnt rom and try and use it. Atleast i will have my $ 400 phone and not a black expensive paper weight.
Regards to all helping and the advices...
Have the same problem as in the first post but my a2 is able to boot
I can flash ROMs with fastboot script.
Erased CID but still can't flash ROMs with RSD (cdt.bin error) and 4.1.2. leak3 Camera is unable to initialize.
Help please!
I posted this somewhere else, but I figured it was more appropriate to place it here.
After rooting and installing CWM using the method in the sticky at the top of the development section, (darkman's unnoficial CWM Recovery), My touchscreen no longer responds to finger input. The pen works fine, and is the only way I can navigate the tablet. Touch input doesn't work in CWM-touch either. I have tried: flashing a custom rom, flashing a stock rom through CWM, flashing stock firmware through Odin (both 4.0.4 and 4.1.2), resetting the triangle count, factory wipe/data reset, re-installing stock recovery, and changing various options in the settings. Nothing helped at all. I'm currently waiting for a reply on filing a warranty claim, but would really like not to have to send it in and wait for a new one. I've seen other people with similar issues, but most of them are either the s-pen doesn't work, or both s-pen and touch don't work. Does anyone have any idea of how to fix it, or is it definitely a hardware issue?
Thanks,
Reffu
Hi,
same issue here. Today the touchscreen stopped working suddenly after i flashed the Android Revolution HD 5.0 Rom yesterday. However, the S-Pen is still working fine. Installing other ROMs and the Stock ROM via Odin did not help. Issue allso appears in Touch-enabled-Recovery.
I see no reason, why this should be a hardware issue, although my N8000 came back from service a few days ago, where they also replaced the screen and digitizer.
Had anyone this issue before and was abled to resolve it?
Greets
I have the same problem on an n8013. Installed Revolution ROM HD version 5, rebooted and lost me touchscreen completely. Nothings worked. Flashed back to stock 4.1.2 but still no go.
Sent from my SCH-I535 using Tapatalk 2
to read this as a Note 10.1 newbie is not very encouraging. are there any similar facts between all of you like
which Note model do you have
how did you jaibreak (which method)
which rom did you have before
which rom do you have now
how did you flash a new rom
...
is there a way to find out whether the touchscreen is really "dead for touch"?
This is a bit scary - my Note 10.1 is arriving today, and I plan to root it at a minimum. I actually don't mind Touchwiz all that much on my Note 2 (which is running CleanROM ACE), so I think I might just root the 10.1 for now.
So restoring completely back to stock (via Odin) doesn't fix it? That is really odd that ROM-ing this thing might cause a hardware failure...
jiggyman said:
I have the same problem on an n8013. Installed Revolution ROM HD version 5, rebooted and lost me touchscreen completely. Nothings worked. Flashed back to stock 4.1.2 but still no go.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I would be tossing my cookies at this point ........ Did you also do a factory reset after flashing back to factory ROM?
kkretch said:
I would be tossing my cookies at this point ........ Did you also do a factory reset after flashing back to factory ROM?
Click to expand...
Click to collapse
Did anyone solve this, I'm having the same problem.
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
reffu said:
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
Click to expand...
Click to collapse
Just curious - did you just root, or did you root and install a ROM?
I am only rooted so far - haven't felt the need to ROM yet - partially due to worries about this happening. I bought a refurb from Best Buy and only get 90 days of warranty.
reffu said:
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
Click to expand...
Click to collapse
If they say you got a new one, you got one. They'll tell you otherwise if there's an issue over the phone.
But I wouldn't be afraid of ROMs, but to be more diligent and wise when it comes to choosing them. It's like choosing a poisonous mushroom versus an edible one to make stroganoff or stir fry. If you know what to avoid for the next time and follow the correct process to doing the root and flashing, there will not be an issues.
This is from someone who has soft-bricked my first tablet and learned how to unbrick my SIM-less Captivate and Note 10.1. It's how you apply the method and how much attention you practice not getting stuck into these situations is what matters. Especially since I bricked my tablet via experimentation and un-bricked it on the same day with ease.
It's not some big complex deal of rocket science or something only the mere geniuses can do, its how you perceive yourself and how you act. If you believe that you will suck and brick it to kingdom come , it will happen intentionally or subconsciously.
In this case, it was a freak accident where the file/s accessed and deleted the wrong files which allowed for capacitive touchscreen use, and it should be reported to x developers if you have not done so already.
I have rooted and used the Revolution HD rom, the Rom where you customize the colors of the bar/other things, and on the Captivate, the AOKP Collective. I further customized the latter with the Xperia launcher as it zips.
Did anyone find a repair for this besides replacement? My Note 2 is doing the same thing now.
Has anyone found a fix for the touch screen not working yet??
Anyone have any ideas?
Technicians input for touch problem
I am a technician and been repairing electronic devices for over 30 years and I would say the majority of repairs I have done were caused by people not happy with how their standard brand new device works and feel they need to make it better by modifying it in some way or other.
Now with smartphones if you didn't want the device as a standard rom and operating system why buy it ?
If you think the phone would be so much better with a modified rom then buy one working with a modded rom to start with as most of you put as much effort into modding as you did in your school work.
Anyone with half a brain that follows the instructions on the mod sites exactly as shown step by step will never have a problem, all those that do end up with paper weights or bricks didn't follow the instructions in numerical order.
Believe it or not even if after you have modded a rom and brought it back to standard they know it has been modded as they have a list of problems associated with repairs after roms have been modded so you are only fooling yourself they don't.
Same as the smoker that tells his Dr he has given up even though all the symptoms prove he really didn't.
So in my expert opinion if you play with modding and stuff it up why should you be eligible for a warranty claim ? The manufacturer has sold you or supplied a working item that you decided to f_ck around with and because of your stupidity expect some one else to pay for it.
I am not saying don't mod your phone with all the great roms out there but please to save yourself a lot of pain and cost some poor smuck trying to run a business in these economic times a lot of out of pocket from sending items back for replacement or warranty plus the time it takes to do all the paperwork and such, please please please read the instructions 300% or triple check you are doing everything exactly as the instructions say and you will be enjoying all the new benefits of that customised rom and laughing at all the noobs stuffing up their brand new device from not doing so.
I know this won't fix your problem but reread that last bit it was your problem as you are to clever to follow some one else's instructions
anyone have solution regarding this issue, mine have issue also, can anyone spare how to fix it without changing hardware?
---------- Post added at 06:47 AM ---------- Previous post was at 06:28 AM ----------
i hope anyone can solve my issue with touch not responding
WOW.. on TOPIC Flashing .pit might help ???
Gardum said:
I am a technician and been repairing electronic devices for over 30 years and I would say the majority of repairs I have done were caused by people not happy with how their standard brand new device works and feel they need to make it better by modifying it in some way or other.
Now with smartphones if you didn't want the device as a standard rom and operating system why buy it ?
If you think the phone would be so much better with a modified rom then buy one working with a modded rom to start with as most of you put as much effort into modding as you did in your school work.
Anyone with half a brain
Click to expand...
Click to collapse
------------------------------------------------------------------
WOW.. And you come to XDA For ? Most of the time The modded roms often fix manufacture issues and add features the manufacturer decided users do NOT Need ..Being your first post on xda . I do NOT think attacking users is the way to go. Also your post adds nothing to help the users..
ON TOPIC
Have any of you who have this issue try to do a full Wipe and flash pit file for your device.. Something is being left behind and not over written is most likely the Cause.. Also post this in the Rom developers forum So maybe he can look into it more as its his Creation..
Good Luck
erica_renee said:
------------------------------------------------------------------
WOW.. And you come to XDA For ? Most of the time The modded roms often fix manufacture issues and add features the manufacturer decided users do NOT Need ..Being your first post on xda . I do NOT think attacking users is the way to go. Also your post adds nothing to help the users..
ON TOPIC
Have any of you who have this issue try to do a full Wipe and flash pit file for your device.. Something is being left behind and not over written is most likely the Cause.. Also post this in the Rom developers forum So maybe he can look into it more as its his Creation..
Good Luck
Click to expand...
Click to collapse
thanks for reply can you give us a hint how to find pit files to flash it in Odin, pit files + official firmware tar.md5 right sir? my model is n8020 i will give it a try, thanks for reply sir
popohunters said:
thanks for reply can you give us a hint how to find pit files to flash it in Odin, pit files + official firmware tar.md5 right sir? my model is n8020 i will give it a try, thanks for reply sir
Click to expand...
Click to collapse
i Have seen them floating around random threads. There is a Thread in the General section with .pit files. Buy you MUST have the one for your Device..
Sorry i cant help I have 8013 device .
erica_renee said:
i Have seen them floating around random threads. There is a Thread in the General section with .pit files. Buy you MUST have the one for your Device..
Sorry i cant help I have 8013 device .
Click to expand...
Click to collapse
thanks sir, im done the flashing with pit files+ official firmware but touch screen is still missing, is there a modem file for touch screen maybe i missed it while its in downloading process before i brick the touch screen
any hope out there?????
confused and need help
i have a n8000 , base band version N8000XXCLL1, my touch screen stoped responding while playing a game , only Spen works , tried resetting , but no help, I'm a no-voice when it comes to programing and need a step by step guide >>>> many thanks in advance for all your help
reffu said:
I posted this somewhere else, but I figured it was more appropriate to place it here.
After rooting and installing CWM using the method in the sticky at the top of the development section, (darkman's unnoficial CWM Recovery), My touchscreen no longer responds to finger input. The pen works fine, and is the only way I can navigate the tablet. Touch input doesn't work in CWM-touch either. I have tried: flashing a custom rom, flashing a stock rom through CWM, flashing stock firmware through Odin (both 4.0.4 and 4.1.2), resetting the triangle count, factory wipe/data reset, re-installing stock recovery, and changing various options in the settings. Nothing helped at all. I'm currently waiting for a reply on filing a warranty claim, but would really like not to have to send it in and wait for a new one. I've seen other people with similar issues, but most of them are either the s-pen doesn't work, or both s-pen and touch don't work. Does anyone have any idea of how to fix it, or is it definitely a hardware issue?
I got the same problem after rooting my phone.... I used the following method and got ride of that Problem. ..
type this star code in in it Phone dialler *#2663#
Now you should see "TSP"
<update>
TAP on TSP ......it will take 5 seconds only....
......
NOW ENJOY ☺☺
Click to expand...
Click to collapse