Database Info

[HOW TO] Debranding /Installing different/recovering bricked firmware on your Defy

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.

[Q] Samsung Galaxy Gio (S5660M, not S5660)

Hello,
I have bought a North American (Canadian, to be exact) Galaxy Gio (S5660M, with an additional "M" from the European model).
There are lots of tutorials about S5660 rooting and unlocking, but none for S5660M. There has been some reports that flashing S5660 firmware on S5660M to root and unlock made their phones unusable (randomly changing screen brightness, etc).
I tried searching on google and XDA, but could not find any relating to S5660M.
Is it too early to see any rooting/unlocking on S5660M?
Thank you very much!

Hello,
After some reading on here to compare unlock methods, I decided to take the leap into the unknown. I used the one published in this thread. (EDIT: Check out this one instead, perfectly safe.) (It turns out that the Gravity Smart, Galaxy Q, 551, 550, Mini, Ace, Fit, and Gio are siblings in a few respects. They all share Qualcomm 7x27 family SoCs.)
One deviation from the above linked thread is that SuperOneClick does not work on the 2.3.4 MUGK3 firmware. Updated versions of SuperOneClick do work with the firmware. Worst case scenario the program won't finish gracefully, but you'll have a root shell and you can work from there.
I've uploaded my modified superuser zip that'll work with the 5660M. Install through recovery mode. Removed - the superuser files within were long obsolete. Get the current ones through proper channels.
I wouldn't risk flashing the ROMs posted here until we can get a complete backup ROM, either from samfirmware.com (they don't have one yet) or through efforts here. I'll be starting another thread here for that purpose. Backup made a long time ago and SamMobile has had an official Odin image for some time as well.
There's been some issues reported with the 5660M, ranging from odd screen brightness behavior to bricking. (Many ROMs initially posted for the 5660, left "as is" also flash both the kernel and radio: not good.)
Goodbye,
Darkshado

Thank you for the reply! I have successfully rooted & unlocked using the modified zip. I am not sure if it was your's (I have done it prior to looking at your reply... ), but it worked!
thank you!
Darkshado said:
Hello,
After some reading on here to compare unlock methods, I decided to take the leap into the unknown. I used the one published in this thread. (It turns out that the Mini, Ace and Gio are siblings in a few respects.) Make extra sure to follow the steps intelligently, especially the bit right after you get your code.
One deviation from the above linked thread is that SuperOneClick does not work on the 2.3.4 MUGK3 firmware.
I've uploaded my modified superuser zip that'll work with the 5660M. Install through recovery mode.
I wouldn't risk flashing the ROMs posted here until we can get a complete backup ROM, either from samfirmware.com (they don't have one yet) or through efforts here. I'll be starting another thread here for that purpose.
There's been some issues reported with the 5660M, ranging from odd screen brightness behavior to bricking. (The ROMs posted for the 5660, left "as is" also flash both the kernel and radio: not good.)
Goodbye,
Darkshado
Click to expand...
Click to collapse

could you tell me how I could unlock my phone too.

New tonight
Just picked up a GIO here tonight.
BTW Future Shop in Canada has these on for $80 right now.
I think this is a great deal, for a very responsive 2.3 android phone.
OK,
So S5660m - is the version in canada it would seem.. I think there are going to be quite a lot of owners because of the pricing.
We should use this thread or another to setup a difinitive list of what works.
1. How to root the phone.
2. Unlocks that work - I have heard some methods brick Ms very easy. What is the best unlock method specific to the M
3. What ROMs can we use? do we need to have our own set of modified roms because of the modem portion?
4. Overclocking.. I have heard these can clock up to 1100 and run awsome!!
This is my wish list.
James

Hello James. Welcome to XDA.
Whoa there early thread starter! Use the search engine before even thinking of starting another thread. We don't have a dedicated Gio forum at the moment so things are scattered all over. Advanced search is handy as it outputs threads instead of posts.
Biker1bob said:
1. How to root the phone.
Click to expand...
Click to collapse
Same as a lot of other phones, apply a zip file through CWM. You could also flash an already rooted ROM with Odin.
2. Unlocks that work - I have heard some methods brick Ms very easy. What is the best unlock method specific to the M
Click to expand...
Click to collapse
The bml5 method is safe. I noticed I had left a link to the older and unsafe stl5 method in my post above and removed it.
And keep your unlock code accessible somewhere on the phone. This phone is known to relock itself to Bell in some specific scenarios.
3. What ROMs can we use? do we need to have our own set of modified roms because of the modem portion
Click to expand...
Click to collapse
Yes, and no. If you only flash system.rfs, and maybe boot.img, it should work based on what others have reported.
I've cooked up a ROM for the 5660M that's called ArpegGioMod if you want to have a look.
Another point to consider if you want to run your phone in French: the Eurasian ROMs may or may not have that locale, and will likely have an AZERTY keyboard instead of a QWERTY one.
Do not flash radio (AMSS) or the other bootloaders from the Euro 5660. The former will make you lose all cellphone connection, the latter is unnecessary and increases your chances of bricking.
4. Overclocking.. I have heard these can clock up to 1100 and run awsome!!
Click to expand...
Click to collapse
Where'd you get that? The only kernel mods I've seen so far for any Gio are all ramdisk modifications that left the stock kernel untouched.

Just to clairify darkshadow, by "bml5 method" you mean this ?
0) brand new locked GT-S5660M phone frome the store
1A) root the device using this zip
http://forum.xda-developers.com/showpost.php?p=16962635&postcount=2
simplest method :
1.1 To begin, download the zip file from the link above and copy it to the root of your SD card.
1.2 Power the phone off.
1.3 Boot into recovery mode by holding the middle button and pressing the power button.
1.4 Once in recovery mode, select update from sdcard and choose the update.zip that you copied to your SD card.
1.5 Let the file flash and once done, reboot your phone.
OR
1B Follow EDIT2, for temp rooting on same URL below
2. Follow exact instructions as per here:
http://forum.xda-developers.com/showpost.php?p=17148825&postcount=334
(with the slight modification for HEX code to search specified here http://forum.xda-developers.com/showpost.php?p=17311381&postcount=358 )
Question: Does it matter if there is a SIM card in the phone when following these instructions ?
Any thoughts about "Network Lock Control Key" ?? ( ... would appear that this shows up as a separate issue for some users some time after unlocking see:
http://forum.xda-developers.com/showthread.php?t=992564 )
THANK YOU so much for confirming I got this right....I just want to make sure I am not missing anything, and these instructions are really safe as far as you know before attempting anything.

Darkshado said:
Hello James. Welcome to XDA.
Whoa there early thread starter! Use the search engine before even thinking of starting another thread. We don't have a dedicated Gio forum at the moment so things are scattered all over. Advanced search is handy as it outputs threads instead of posts.
Same as a lot of other phones, apply a zip file through CWM. You could also flash an already rooted ROM with Odin.
The bml5 method is safe. I noticed I had left a link to the older and unsafe stl5 method in my post above and removed it.
And keep your unlock code accessible somewhere on the phone. This phone is known to relock itself to Bell in some specific scenarios.
Yes, and no. If you only flash system.rfs, and maybe boot.img, it should work based on what others have reported.
I've cooked up a ROM for the 5660M that's called ArpegGioMod if you want to have a look.
Another point to consider if you want to run your phone in French: the Eurasian ROMs may or may not have that locale, and will likely have an AZERTY keyboard instead of a QWERTY one.
Do not flash radio (AMSS) or the other bootloaders from the Euro 5660. The former will make you lose all cellphone connection, the latter is unnecessary and increases your chances of bricking.
Where'd you get that? The only kernel mods I've seen so far for any Gio are all ramdisk modifications that left the stock kernel untouched.
Click to expand...
Click to collapse
so i'm pretty new here... i have a gio n my usb port is messed up.. i wiped tha phone the other day n the network lock came back on.. so seeing that i can't use any usb what should i do?
thanks in advance
IMEI: Mod Edit: IMEI # Removed...not a great idea to post them on a public forum

Let me start with things you shouldn't do:
-Resurrect two year old, stale, threads.
-Post your IMEI for everyone to see.
Exactly *how* is your USB port messed up? Just not talking to the computer or not working at all?
Are you rooted? If not, get that sorted out by using one of the exploits that worked on Gingerbread. You'll have to do it manually, no SuperOneClick for you. (Although the binaries included might come in handy.)
It is possible to do the commands to get bml5 via a terminal emulator app, and then transfer that file over wi-fi. (Samba, WebDAV, FTP, Dropbox, etc...)
I'm not sure anymore if this is possible in GB, look into using ADB over wi-fi instead of USB. I've sold my Gio months ago, and all of my current devices run 4.1+.

[Q] So, I'm an idiot (Baseband help needed, I think)

So my friend (lives in Canada) has an Optimus One one a plan with Koodo. I walked her through installing CyanogenMod 7.1 or whatever the latest was. You know, unlock bootloader, root phone, and get Clockwork Mod to do all the hard work. I... may have skipped over the backing up part. See, I thought you know, her phone got wiped on bootloader anyway, so why backup? Yeah, idiot
So now she can't make calls, send text messages or anything. So I can only assume it's a baseband issue. But, that's where I'm stuck. After reading, some people suggest mik's mod, or something, others give a download to a backup for an Indian ROM. One flow chart suggested installing the baseband from this thread http://forum.xda-developers.com/showthread.php?t=1149530 which looks useful. Except... which one do I use? And will it work on Canadian company Koodo? Will the Indian ROM work with Canadian Basebands?
Please, help would be so greatly appreciated

Garethp said:
So my friend (lives in Canada) has an Optimus One one a plan with Koodo. I walked her through installing CyanogenMod 7.1 or whatever the latest was. You know, unlock bootloader, root phone, and get Clockwork Mod to do all the hard work. I... may have skipped over the backing up part. See, I thought you know, her phone got wiped on bootloader anyway, so why backup? Yeah, idiot
So now she can't make calls, send text messages or anything. So I can only assume it's a baseband issue. But, that's where I'm stuck. After reading, some people suggest mik's mod, or something, others give a download to a backup for an Indian ROM. One flow chart suggested installing the baseband from this thread http://forum.xda-developers.com/showthread.php?t=1149530 which looks useful. Except... which one do I use? And will it work on Canadian company Koodo? Will the Indian ROM work with Canadian Basebands?
Please, help would be so greatly appreciated
Click to expand...
Click to collapse
Hey man, so basically you were right, it's a baseband issue.
Flash version 20g/i/h whatever, I don't remember what letter but it doesn't matter.
Just follow the guide to the letter and it will work fine
Cheers mate!

Garethp said:
So my friend (lives in Canada) has an Optimus One one a plan with Koodo. I walked her through installing CyanogenMod 7.1 or whatever the latest was. You know, unlock bootloader, root phone, and get Clockwork Mod to do all the hard work. I... may have skipped over the backing up part. See, I thought you know, her phone got wiped on bootloader anyway, so why backup? Yeah, idiot
So now she can't make calls, send text messages or anything. So I can only assume it's a baseband issue. But, that's where I'm stuck. After reading, some people suggest mik's mod, or something, others give a download to a backup for an Indian ROM. One flow chart suggested installing the baseband from this thread http://forum.xda-developers.com/showthread.php?t=1149530 which looks useful. Except... which one do I use? And will it work on Canadian company Koodo? Will the Indian ROM work with Canadian Basebands?
Please, help would be so greatly appreciated
Click to expand...
Click to collapse
You're on the right track, use the file attached to that post titled "P500-v20G-baseband.7z" (use 7-Zip/WinRAR/etc to extract).
Make sure you follow the instructions EXACTLY. Do NOT unplug your phone until it tells you it's completely done, and don't delete the backup it makes! I got lucky the first time I flashed, I thought it had lost communication and had unplugged my phone, but luckily it hadn't started the wipe yet and I was able to recover it.

Don't worry, you're doing the right thing. Remember to follow every single step (double check twice), and DO NOT UNPLUG THE USB, until it tells you to, as they have said above. Also to add, I have a Canadian Koodo O1, and I'm 200% that you won't have any problems whatsoever installing anything on this forum, whether it's an Indian based ROM, Chinese based, etc. Have fun modding!

Touchscreen not working after root, but S-Pen works fine

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

GT-N8000 downgrade and no update.

I've been using Gnabo v_7 version for quite a long time, and a very simple and beautiful day when I woke up my Samsung GT-N8000 was stuck on bootscreen. I wasn't able to do much so I got this "Brazil stock rom" that I found in a website, and it flashed all right, except for the detail that there is something at the screen that I haven't got a bloody clue how to remove. hahaha
And still, whenever I try to install another room, I got stuck at bootlogo and so on. I'm kinda lost here, mind a little help?
I traveled around the forum but well, I'm a little dumb so I couldn't find any proper information about, how to solve this. I would like to know if there is a way to remove this thing from the main screen, and post here the image for you guys to see it please.
I tried to post the image here to make it easier understanding, but since I got this login recently I can't =\
Thanks

Install custom recovery (if you haven't already. If you already have it installed, make sure to update to latest version), root device, wipe everything and flash custom ROM.

DroidTwe4kz said:
Install custom recovery (if you haven't already. If you already have it installed, make sure to update to latest version), root device, wipe everything and flash custom ROM.
Click to expand...
Click to collapse
So far I've tried the rom = N8000XXUDNE4 [still bootloop], then another 4.1 android version of other German rom XXALGA and nothing. Downloaded 3 Brazilian versions, and nothing. [I am from Brazil]. The only one that worked flashing using Odin was one called "KIES_HOME_N8000UBALGA_N8000ZTOALG3_N8000UBLG5.tar". And still, not recognizing my cellphone chip, and with some big watermark at the middle of the screen showing some information about the ROM and the version is 4.0. Even though this one worked fine, I was able to root and when I tried to flash another room, BANG! Bootloop again! =\
I was looking at the forum topics and I read some about ADB or something like that can fix this and "break" this bootloop making the device work normally again with the roms. But i haven't got a clue how to use it. Please help me! =\

vitortakeda said:
So far I've tried the rom = N8000XXUDNE4 [still bootloop], then another 4.1 android version of other German rom XXALGA and nothing. Downloaded 3 Brazilian versions, and nothing. [I am from Brazil]. The only one that worked flashing using Odin was one called "KIES_HOME_N8000UBALGA_N8000ZTOALG3_N8000UBLG5.tar". And still, not recognizing my cellphone chip, and with some big watermark at the middle of the screen showing some information about the ROM and the version is 4.0. Even though this one worked fine, I was able to root and when I tried to flash another room, BANG! Bootloop again! =\
I was looking at the forum topics and I read some about ADB or something like that can fix this and "break" this bootloop making the device work normally again with the roms. But i haven't got a clue how to use it. Please help me! =\
Click to expand...
Click to collapse
You can use ADB to push/pull files to Android. I don't know if you can use it to fix bootloop. With it, you can also reboot to recovery and sideload zip

DroidTwe4kz said:
You can use ADB to push/pull files to Android. I don't know if you can use it to fix bootloop. With it, you can also reboot to recovery and sideload zip
Click to expand...
Click to collapse
Well, after 2 days of research and paying attention on things here, I found out that my problem is "/EFS error". Meaning to use ADB to recover or fix it? But I don't know how to use this. I've downloaded 3GB of it but I was lost about using, and uninstalled. Is is there any short or better version and some good tutorial about using to retrieve my EFS so I can install another roms? I'm using original stock rom now, Brazilian android 4.0 and that's the only only the device is working fine but of course missing things as my cellphone card and the yellow message at the top of the screen. Please guide me through ADB.
P.s Is there a way to create /efs or something like so the device work properly? Cause I've deleted when I installed some rom, and I have no backup here. =\
Thanks!

vitortakeda said:
Well, after 2 days of research and paying attention on things here, I found out that my problem is "/EFS error". Meaning to use ADB to recover or fix it? But I don't know how to use this. I've downloaded 3GB of it but I was lost about using, and uninstalled. Is is there any short or better version and some good tutorial about using to retrieve my EFS so I can install another roms? I'm using original stock rom now, Brazilian android 4.0 and that's the only only the device is working fine but of course missing things as my cellphone card and the yellow message at the top of the screen. Please guide me through ADB.
P.s Is there a way to create /efs or something like so the device work properly? Cause I've deleted when I installed some rom, and I have no backup here. =\
Thanks!
Click to expand...
Click to collapse
Here is tutorial about how to install ADB and Fastboot drivers and use them. Unfortunately, I don't know how to use it to restore efs. Sorry.