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
Related
Hi everyone,
Just a word of advice: Rooting + Flashing ROMs for the Desire may og may not brick your devices. As you can see in this thread http://android.modaco.com/content-p...-usb-connectivity-etc-and-root-a2sd/page/540/ we are quite a few with bricked devices - and no way to un-brick them so far.
Nobody yet knows what might have caused this - maybe Apps 2 SD.
I would advice for everyone to wait flashing any further until this issue is clarified!!!
Thanks for the heads up. Not been flashing much as of late but was planning to try out a different ROM. Does this problem affect all customised ROMs or just certain newer builds?
Mastoid said:
Thanks for the heads up. Not been flashing much as of late but was planning to try out a different ROM. Does this problem affect all customised ROMs or just certain newer builds?
Click to expand...
Click to collapse
It is about as random as can be is the best way to decsribe it! Some people flash many times and have no bother, others flash once and the phone is bricked
It so far doesn't seem to be exclusive to any particular rom, people speculate it may be A2SD, but others think it's the actual rooting process. To be honest, no one actually knows why it's happening and how to fix it. All that is certain is that more and more people are posting with the issue.
It could be any ROM.
Sent from my HTC Desire using Tapatalk
socktug said:
It is about as random as can be is the best way to decsribe it! Some people flash many times and have no bother, others flash once and the phone is bricked
Click to expand...
Click to collapse
I take it you have a bricked phone then? I hope this gets resolved soon especially for those who might have turned their phone into nothing more than a paper weight.
It so far doesn't seem to be exclusive to any particular rom, people speculate it may be A2SD, but others think it's the actual rooting process. To be honest, no one actually knows why it's happening and how to fix it. All that is certain is that more and more people are posting with the issue.
Click to expand...
Click to collapse
Since many people have reported this issue, is there not some kind of pattern emerging? Hopefully we can isolate the problem to something in particular, as you stated, whether it be caused by the rooting process, Apps2SD, or a USB driver issue.
For those who are experiencing this, might be an idea to post computer specs, what ROM they attempted to install, and other associated things so we can narrow down the problem.
I've flashed loads so far and have no issues - finally got a ROM I like at the mo so will leave it for now...probably
My guess its the recovery, its not installed to the phone and its very sensitive for connection: do not move phone or cable during flash.
It happens that I flash several time in a day, I have MCR r3 A2SD+ now and I never had such a problem...
The problem is APPS2SD related.
DocRambone said:
My guess its the recovery, its not installed to the phone and its very sensitive for connection: do not move phone or cable during flash.
Click to expand...
Click to collapse
I don't mean do break up the good mood in this thread. But if you have a problem/issue with this, please follow the thread on MoDaCo - any kind of input is welcome in this debate
BTW: If any moderator reads this: Can we make this sticky until problem is solved?
Could this be most of the issue happened to be with people with .80 bootloader??
kuailan said:
Could this be most of the issue happened to be with people with .80 bootloader??
Click to expand...
Click to collapse
This problem has nothing to do with the 0.80 bootloader. It's all to do with APPS2SD, that was discovered weeks ago on MoDaCo.
abc27 said:
This problem has nothing to do with the 0.80 bootloader. It's all to do with APPS2SD, that was discovered weeks ago on MoDaCo.
Click to expand...
Click to collapse
There are people on modaco who have bricked their phones, and were not using A2SD.
I managed to brick mine by knocking it during the flashing process. I did not use A2SD.
socktug said:
I managed to brick mine by knocking it during the flashing process. I did not use A2SD.
Click to expand...
Click to collapse
I think DocRambone is onto something here... he stated a few posts back that he thinks it may be down to the sensitivity of the connection/cable while the phone is in recovery mode during flash, and you mentioned that you bricked your phone while knocking it while flashing in recovery?
From my experience, whenever I attempted to flash Desire cutoms ROMs, I did not move the USB cable at all and it worked fine. Had the phone placed on the desk and kept it stationary while flashing. I have not had any problems with Apps2SD or USB driver issues either.
I did mine from the laptop and the phone on the sette beside me. lol. I initially thought I'd knocked it and the battery came out, but I'm fairly sure now that the battery wasn't the problem, it fits too tight to come out with a simple knock of the hand.
Anyway, all I can say is if you brick it, and can unroot it, and bought it at the carphonewarehouse, you will be fine! They took it back and gave me a new one, no questions asked. I'm not going near a root process untill there is a fix now
Afaik there are two possible solutions for the issue
1. someone needs to security unlock the spl, so that we are able to use all fastboot commands
2. In the modaco thread someone found some helpfull kernel commands
so, if anyone either is experienced in spl modifications or capable of programming c for the kernel commands, pleade send me a pm
millen said:
I don't mean do break up the good mood in this thread. But if you have a problem/issue with this, please follow the thread on MoDaCo - any kind of input is welcome in this debate
BTW: If any moderator reads this: Can we make this sticky until problem is solved?
Click to expand...
Click to collapse
I have read the last few pages of the MoDaCo thread but still I am not clear about the issue.
Is it there are some unknown factors causing the root process to brick the USB? But still you can flash stock RUU in fastboot?
you can flash back to stock cause fastboot is still working and so you can flash the signed stock roms (thoose with release keys or the testrom with testkeys) but due to the fact that adb is nomore working you can't enter the custom recovery to flash cooked roms
millen said:
I don't mean do break up the good mood in this thread. But if you have a problem/issue with this, please follow the thread on MoDaCo - any kind of input is welcome in this debate
BTW: If any moderator reads this: Can we make this sticky until problem is solved?
Click to expand...
Click to collapse
Just send a message to one of the mods, he sure will make that post sticky
--edit---
man, theese guys are fast, now it's sticky
Easy and apparently safer method of rooting?
Not sure if anyone's seen this on modaco but using the tiny core linux has worked well for me, with 3 flashes from a stock HTC ROM and currently running eViL De-SiRe after trying paul's initial boot then the Cyanogen Port.
May flash again tonight with the Kernel release the ROMs will get better and better.
P500VPBMB3 Sprint 4.1.2 Firmware
For some unusual reason there is little to no development for the SPH-P500 and absolutely ZERO official firmware available for the Sprint model. This means, if you soft brick the tablet trying to install something you should not have, you have no easy way of getting back to the stock firmware. In addition, getting to the 4.1.2 version of the firmware is a royal pain due to the massive amount of "PATCH CHECKS" and assert checks built in to the OTA update. This means any deodexed system or a number of other reasons will be rejected if you try the OTA update while on non-official or approved firmware. So, for your convenience, I have compiled a simple ODIN-Flashable TAR file which will jet you up to speed installing the latest official Sprint 4.1.2 firmware.
Details:
P500VPBMB3 Stock w/ MB3 Modem
Package Includes: BOOT, RECOVERY, SYSTEM, MODEM AND CACHE ZONES
Download:
P500VPBMB3 Sprint 4.1.2 Firmware
Password on the archive is: www.mobiletechvideos.com
How To Flash:
BACKUP YOUR FILES AND DATA BEFORE FLASHING...ALWAYS. First extract this file using WinRAR or a program capable of extracting a RAR package as the package inside it is the TAR file you need. This was done to save time on the download. Once extracted, using ODIN, select PDA and choose this file. Now place your tablet in DOWNLOAD MODE by having it powered off, then power on by holding POWER and VOLUME DOWN until you see the on-screen text come up. Release the buttons and press VOLUME UP to enter DOWNLOAD MODE. Now click START on ODIN. Once completed (takes around 10 minutes), it is advised to enter RECOVERY MODE and perform a FACTORY DATA RESET for the best bug free experience since I don't know what ROM you are flashing from.
Did this help you out? Great, I'm glad it did! Click that THANKS button next to my name if you have the time. Please note, if you find yourself in a hard/soft brick situation of any type on any advice, give me a shout via PM or email through the contact page on our site. We also offer repairs on a number of other issues.
27 downloads and nothing? I'd love some feedback so others can be confident in the firmware.
It´s a disease from all P31XX and P51XX useres don´t hitting the thanks button and don´t giveing feedback... maybe they don´t want any support.... (?)...
i don´t have a P51XX - i can´t give other feddback then this... sorry....
Haha it seems that way! Well thanks for your response. Nice to hear from somebody about this. For some reason the Tab 2 10.1 forum members seem to be dead but want development anyhow without any input!
There are a lot of people here in a german forum there is mostly nobody ...
i hope you get some feedback! if not: there is not problem first things that will reported are problems
Haha, how true! No news is good news right?
problem and feedback if it works...
Hi. I am pretty new here (although I have been a member for a while, I have not really been active). I do have a Sprint Samsung Galaxy tab 2 10.1 inch display model P500VPBMB3. Perhaps I can try out what you are talking about if it helps me with my problem below and then I will be more than happy to give you feedback.
PROBLEM
I never really rooted a device before but I am at a loss here since the current version of Android that I have on my device is 4.1.2 . It's working OK but I run out of space very often since I only have 16GB of main memory. I would love to upgrade to 4.2.x so that I have the option of storing apps on the external SD card. I am not clear exactly what you are giving us here on your thread. If you can explain it to me and especially if it does what I am outlining above I would want done, I would love to give it a shot and then give you some feedback.
Either way thank you for helping is Sprint tablet people whether or not what you have above will help me.
Thanks
shmusie said:
Hi. I am pretty new here (although I have been a member for a while, I have not really been active). I do have a Sprint Samsung Galaxy tab 2 10.1 inch display model P500VPBMB3. Perhaps I can try out what you are talking about if it helps me with my problem below and then I will be more than happy to give you feedback.
PROBLEM
I never really rooted a device before but I am at a loss here since the current version of Android that I have on my device is 4.1.2 . It's working OK but I run out of space very often since I only have 16GB of main memory. I would love to upgrade to 4.2.x so that I have the option of storing apps on the external SD card. I am not clear exactly what you are giving us here on your thread. If you can explain it to me and especially if it does what I am outlining above I would want done, I would love to give it a shot and then give you some feedback.
Either way thank you for helping is Sprint tablet people whether or not what you have above will help me.
Thanks
Click to expand...
Click to collapse
You will actually want to look into custom recovery combined with a custom ROM to enable this type of option. What I have provided here is a stock firmware (stock operating system). This is actually already what you have installed on the device.
connexion2005 said:
You will actually want to look into custom recovery combined with a custom ROM to enable this type of option. What I have provided here is a stock firmware (stock operating system). This is actually already what you have installed on the device.
Click to expand...
Click to collapse
Thank you very much for your prompt reply. You seem to be a helpful sort of person. I am sorry to be so dense but I have no idea what those things are. Is there a place where I can, sort of begin from scratch to learn all about these things or can you please fully explain what I need to do here?
I get that yo said that what you are offering is what I already have. What I don't understand is what exactly what to look for. I do know that if I install the wrong thing, I can brick my device. What I don't know if how to find what I am looking for. I already tried it in the search box-that's how I got to your thread.
This is honestly a very tough section as the P500 is a rare unit that has little to no development. You are in the right sub-forum but finding any mods for your unit may not be possible at this time unfortunately.
Thank you, thank you, thank you!!!!! You can root with Kingo root and make modifications with xposed. I just have been so busy with work.
I will flash this when I have time. Now I can be more risky with flashing because I can now go back to stock ROM.
Sent from my SM-N900P using Tapatalk
Android-Andi said:
It´s a disease from all P31XX and P51XX useres don´t hitting the thanks button and don´t giveing feedback... maybe they don´t want any support.... (?)...
i don´t have a P51XX - i can´t give other feddback then this... sorry....
Click to expand...
Click to collapse
Hello, I know its been almost a year, but I tried to flash this ROM and get stuck after the tab reboots with the message "POWER RESET or UNKNOWN UPLOAD MODE", is there anything I can do to restore the tab (I did not do any backup).
Thanks a bunch
Do you have the Sprint model? If so, try re-downloading it and flashing again. Afterwards, perform a factory data reset.
connexion2005 said:
Do you have the Sprint model? If so, try re-downloading it and flashing again. Afterwards, perform a factory data reset.
Click to expand...
Click to collapse
The tab comes from China but in the options i've seen SPH-P500 so I supposed it was a model made for Sprint.
I did flash again and reset factory but nothing changed.
meresis said:
The tab comes from China but in the options i've seen SPH-P500 so I supposed it was a model made for Sprint.
I did flash again and reset factory but nothing changed.
Click to expand...
Click to collapse
That is definitely unusual though the fact it came from China. This likely is NOT the right firmware for your model. The back of the unit should have the model number. See what it says...
connexion2005 said:
That is definitely unusual though the fact it came from China. This likely is NOT the right firmware for your model. The back of the unit should have the model number. See what it says...
Click to expand...
Click to collapse
Indeed the back says P5110 ... Chinese devices ... Thanks a lot ! :good:
P500
Wow!! I made a mistake!! I bought this tab to have some fun rooting and installing custom roms. I should have checked the forums first to see if there was any support. Thanks for what you've provided here. I'm going to at least try to root and install xposed.
I have a sprint gtab2 10.1 that's out of contract, so i'm willing to start working on things if needed.
if we no longer need to use the Sprint data can we flash a SPH-P5100 rom for wifi only ?
resurrecting an old thread. Need to find the original firmware for sph-p500. This appears to be it, but I can't find or get the password to the .rar file. I can't find the firmware anywhere else after a TON of google searches. any help appreciated in either getting the password to the .rar file, or a different place to download the firmware.
Howdy
Not sure where to start asking for help. Here is where I'm at :
Twrp (2.8.6?) works great... Too good
Used it to create a complete Nandroid of my original (jb) system.. I backed up everything I could see.
Installed a blisspop rom that also worked.
Decided to return to the original system .
In twrp did factory reset, advanced wipe of dalvic cache, data, and system each time.
Did restore with md5 check. 6 md5's all good, no failures
Restore from Nandroid file on ext micro sd. Everything successful. No fails reported anywhere.
Reboot. System tries to start but returns to twrp instead of booting to system. Have done this 3 times with same results.
My stock was something like UEUCOI1.
I hate to have to start over but will if that's the best I can do. If so I don't know where to proceed from here. Where to locate a stock room
Any suggestions are much appreciated,
Best regards,
Dr Dan
Jonathan Kang said:
Ok, I have seen what you have done. You installed and did too many things at once on TWRP! If you do that you will get a bootloop or a soft-brick which is very common. If I ever got stuck I just downloaded Samsung Smart Switch for Windows.
1st: Turn off your tablet/phone.
2nd: Press More then Emergency software recovery and initialization.
3rd: Press Device initialization.
4th: Take off your cover of your tablet/phone and see the sticker for the Model Number and the Serial Number and type it in.
5th: Sit back and wait for 10 - 120 minutes and it should be done!
(Not all steps have been written down in this post. You'll see it in the Smart Switch app for Windows.)
That should do it!
Hope I helped,
Jonathan
Click to expand...
Click to collapse
Thank you very much Jonathan. Your words are more comforting than you know and much appreciated. It'll be late today before I've time to test this out but I'll get back with you either way.
Best regards,
Dr Dan :victory:
drdan123 said:
Thank you very much Jonathan. Your words are more comforting than you know and much appreciated. It'll be late today before I've time to test this out but I'll get back with you either way.
Best regards,
Dr Dan :victory:
Click to expand...
Click to collapse
Hi Jonathan,
I got the back cover off and found something that I suspect is the serial number. It is SNR32CB01G4SN. Does that seem right to you? Inside the back cover (plastic) is KIGDSW1102 504B. Regardless it never asks for a serial number.
Your instructions call for a model number. I could not find one inside the back cover. The smart switch PC app is calling for a model name. There is no place for a serial number. The app will not accept GT-N8013 in the name space nor will it accept Samsung Galaxy Note 10.1.
I don't know what other info I can give it. What do you recommend?
Thanks for helping me get started,
Dr Dan
drdan123 said:
Hi Jonathan,
I got the back cover off and found something that I suspect is the serial number. It is SNR32CB01G4SN. Does that seem right to you? Inside the back cover (plastic) is KIGDSW1102 504B. Regardless it never asks for a serial number.
Your instructions call for a model number. I could not find one inside the back cover. The smart switch PC app is calling for a model name. There is no place for a serial number. The app will not accept GT-N8013 in the name space nor will it accept Samsung Galaxy Note 10.1.
I don't know what other info I can give it. What do you recommend?
Thanks for helping me get started,
Dr Dan
Click to expand...
Click to collapse
Update :
After experimenting and pushing a bunch of buttons I was able to get it to accept the model name as GT-N8013 and the serial number as written above except that I omitted the first 2 letters (SN). The search then reported...
"'GT-N8013' does not support initializing. Please contact our service center."
Looks like I'm still up the proverbial Creek. Stuck in TWRP never never land.
Thanks for trying ,
Dr Dan
Update. Upon reading about smart switch it says it is only good for devices with android 4.3 or higher. This tablet in its last update was 4.1.2. The last rom I had (Blisspop) was 5.1.1 but I doubt samsung would accept that as valid software.
Conclusion, smart switch is a dead end. I'm hoping to make either gnoba or hyperdrive rom work but am having a hard time getting the files needed. Also cannot make Sammobile site work so I cannot get the original firmware to flash.
I'll keep swinging as long as I can.
drdan123 said:
Update :
After experimenting and pushing a bunch of buttons I was able to get it to accept the model name as GT-N8013 and the serial number as written above except that I omitted the first 2 letters (SN). The search then reported...
"'GT-N8013' does not support initializing. Please contact our service center."
Looks like I'm still up the proverbial Creek. Stuck in TWRP never never land.
Thanks for trying ,
Dr Dan
Update. Upon reading about smart switch it says it is only good for devices with android 4.3 or higher. This tablet in its last update was 4.1.2. The last rom I had (Blisspop) was 5.1.1 but I doubt samsung would accept that as valid software.
Conclusion, smart switch is a dead end. I'm hoping to make either gnoba or hyperdrive rom work but am having a hard time getting the files needed. Also cannot make Sammobile site work so I cannot get the original firmware to flash.
I'll keep swinging as long as I can.
Click to expand...
Click to collapse
I actually starting to think that twrp is just not the right recovery for Note 10.1. When I was trying to flash the original software it happened to me too. It just has a bug or insufficiency to install system on some roms. Here is what I did:
-Installed gnabo rom for a system base. I STRONGLY SUGGEST THAT YOU FLASH THE SAME BASED ROM WITH THE ROM YOU WANT TO FLASH.
-Wipe everything EXCEPT system.
-Flash the rom you want. In my case it was the stock rom.
Well, not a proper, solid solution but if it's working, who cares?
Hi furkey,
I also saw the gnabo room. I got 6 files...
Gnabo room v8
N801x+v6. Zip
Update-supersu-v1. 99.zip
Gt-n8013-kk-WiFi -fix .zip
Stock-gt-n8000-leaked-kk-boot.img-cwr-installer.zip (really a convoluted name?)
V8-final-fix.zip
I was unable to get the kernal. Each attempt sent me to the playstore to install Mega drive. I have it already installed and am fully subscribed but...
I wrote Mikyno (the creator of gnabo) asking for help but never heard back.
The morass of gnabo files is bewildering. I don't know what I need and don't need and how or with what tools to load them.
I'm pretty sure I need the kernal as I understand it the kernal is the interface between hardware and software. Without it and without some guidance or support from the creator I gave up.
Then I spent a couple of days trying to locate a 4.1,2 stock firmware (ready to give up on roms altogether) . There were several published but all links have expired and the posters do not respond. Sammobile requires a puzzle be solved to register. I spent several hours trying to make my tablet move a puzzle piece. No success.
Finally I gave up and reloaded the blisspop I'd installed to start this journey. It is a bit flakey at times but it's all I have. I cannot go forward and cannot go backward.
Any directions you can send my way are much appreciated.
Dr Dan
Hello,
I too am experiencing this. I really can't throw this device away. I have even tried a stock rom from high on android. Downloaded and used odin to flash to no avail. I hope anyone will have an answer or another stock rom or anything!
Thank you!
Tony
Hi badteddy,
Perhaps we can work this out together. I'd like to try out the stock rom you have. I went to the site but was unable to search very well at all and could not find any stock roms. Can you send me a download link to it? I assume it is for the UEUCOI1 build. I think anything close should work. I also assume your tablet is the GT-N8013 Wifi only version.
Have you loaded the blisspop rom and twrp both? I have both working as advertised with a minor improvement.
Looking forward to hearing from you ,
Dan
drdan123 said:
Hi badteddy,
Perhaps we can work this out together. I'd like to try out the stock rom you have. I went to the site but was unable to search very well at all and could not find any stock roms. Can you send me a download link to it? I assume it is for the UEUCOI1 build. I think anything close should work. I also assume your tablet is the GT-N8013 Wifi only version.
Have you loaded the blisspop rom and twrp both? I have both working as advertised with a minor improvement.
Looking forward to hearing from you ,
Dan
Click to expand...
Click to collapse
Dr. Dan!
of course! here's the link:
http://rootgalaxynote.com/galaxy-note-10-1-2/how-to-unrootunbrick-galaxy-note-10-1-factory-firmware/
the link to download the rom is here:
http://stockroms.net/file/GalaxyNote10.1/N8013/N8013UEALI3_N8013XARALI3_XAR.zip
i have not tried the blisspop rom. I believe I was using the latest twrp.
Just do what I said in the first place. It worked out for me and I have a strong feeling that it will work out for you too (well, hopefully). You can use just the main rom file, not thinking others are required too. Or you can simply flash the tab s sensation rom instead of gnabo rom. It can be found in this page: http://forum.xda-developers.com/galaxy-note-10-1/development/gnabo-rom-x-tab-s-feature-t3164779. Notify me if you succeed or not.
And do not forget to mention me otherwise I may not notice that you have wroten to me.
badteddy said:
Dr. Dan!
of course! here's the link:
http://rootgalaxynote.com/galaxy-note-10-1-2/how-to-unrootunbrick-galaxy-note-10-1-factory-firmware/
the link to download the rom is here:
http://stockroms.net/file/GalaxyNote10.1/N8013/N8013UEALI3_N8013XARALI3_XAR.zip
i have not tried the blisspop rom. I believe I was using the latest twrp.
Click to expand...
Click to collapse
Hi Tony,
Thanks much for the links. That site has always given me grief. When I select download it simply takes me back to the same page to select download again etc. This time your 2nd link worked! Great day. I got the file, unzipped it, removed the ". Md5" extension and ran the md5 Checker. It failed. I hope you checked yours before installing it. Is there any other place I can get that file. Upon returning to the same page to dl the file again I got stuck back in the old circle I have always found myself in.
On anther note; I think furkey is stepping in to help. He wants us to try the gnabo rom. It looks good but there are 7 files needed. I don't know if furkey was referring to you or to me in his last post. I'll ask and see. I think he can easily clear the air on what is needed to load gnabo.
I also am using the latest twrp (2.8.6 I think).
I'll get back when I learn more.
Dr Dan
furkey said:
Just do what I said in the first place. It worked out for me and I have a strong feeling that it will work out for you too (well, hopefully). You can use just the main rom file, not thinking others are required too. Or you can simply flash the tab s sensation rom instead of gnabo rom. It can be found in this page: http://forum.xda-developers.com/galaxy-note-10-1/development/gnabo-rom-x-tab-s-feature-t3164779. Notify me if you succeed or not.
And do not forget to mention me otherwise I may not notice that you have wroten to me.
Click to expand...
Click to collapse
Hi furkey,
Thanks much for stepping in. I'm assuming you mean me instead of (possibly in addition to) badteddy.
I'd never heard of the tab s rom. It looks really good. The gnabo scares me a little. My concern is you likely have flashed more support software than I. What works for you may well crash mine.
The tab s rom was given without an md5 so I can only hope I got a good download.
Once I've rebuilt my courage I'll give it a go and report back to you (and badteddy) with results.
Best regards,
Dr Dan
I don't recall a stylus on the tab s. Does this rom support the active stylus? Do you know if there is an addon that will include support of not? I'll also ask the creator but I've yet to hear back from any rom maker save the sweet lady that made the blisspop rom.... Needy blonde.
drdan123 said:
Hi furkey,
Thanks much for stepping in. I'm assuming you mean me instead of (possibly in addition to) badteddy.
I'd never heard of the tab s rom. It looks really good. The gnabo scares me a little. My concern is you likely have flashed more support software than I. What works for you may well crash mine.
The tab s rom was given without an md5 so I can only hope I got a good download.
Once I've rebuilt my courage I'll give it a go and report back to you (and badteddy) with results.
Best regards,
Dr Dan
I don't recall a stylus on the tab s. Does this rom support the active stylus? Do you know if there is an addon that will include support of not? I'll also ask the creator but I've yet to hear back from any rom maker save the sweet lady that made the blisspop rom.... Needy blonde.
Click to expand...
Click to collapse
It's not a Tab S rom. It's a Note 10.1 rom with Tab S features in it like new touchwiz, file explorer and etc. Your s-pen will work on this rom.
drdan123 said:
Hi badteddy,
Perhaps we can work this out together. I'd like to try out the stock rom you have. I went to the site but was unable to search very well at all and could not find any stock roms. Can you send me a download link to it? I assume it is for the UEUCOI1 build. I think anything close should work. I also assume your tablet is the GT-N8013 Wifi only version.
Have you loaded the blisspop rom and twrp both? I have both working as advertised with a minor improvement.
Looking forward to hearing from you ,
Dan
Click to expand...
Click to collapse
OK. I tried out the Tab S Sensation Rom. It is outstanding. Here is a link that shows what I did,
http://forum.xda-developers.com/showpost.php?p=67440486&postcount=342
Furkey recommended it and he was spot on!
I was never able to dl the link you gave but I did find the file and checksum on a different mirror. I finally got it but have no use for it as the tab s room works better than the stock.
Enjoy,
Dr Dan
furkey said:
It's not a Tab S rom. It's a Note 10.1 rom with Tab S features in it like new touchwiz, file explorer and etc. Your s-pen will work on this rom.
Click to expand...
Click to collapse
You are the greatest. That rom is everything you said it would be. Wish I'd found it 2 years ago.
Best regards,
Dr Dan
drdan123 said:
You are the greatest. That rom is everything you said it would be. Wish I'd found it 2 years ago.
Best regards,
Dr Dan
Click to expand...
Click to collapse
You're welcome mate. I am glad that worked out for you
drdan123 said:
Update :
After experimenting and pushing a bunch of buttons I was able to get it to accept the model name as GT-N8013 and the serial number as written above except that I omitted the first 2 letters (SN). The search then reported...
"'GT-N8013' does not support initializing. Please contact our service center."
Looks like I'm still up the proverbial Creek. Stuck in TWRP never never land.
Thanks for trying ,
Dr Dan
Update. Upon reading about smart switch it says it is only good for devices with android 4.3 or higher. This tablet in its last update was 4.1.2. The last rom I had (Blisspop) was 5.1.1 but I doubt samsung would accept that as valid software.
Conclusion, smart switch is a dead end. I'm hoping to make either gnoba or hyperdrive rom work but am having a hard time getting the files needed. Also cannot make Sammobile site work so I cannot get the original firmware to flash.
I'll keep swinging as long as I can.
Click to expand...
Click to collapse
Hello, drdan123,
I am Jonathan Kang, and I'm using my secondary account.
So try to use Samsung Kies because it probably supports older devices. Smart Switch is for the newer devices. I hope I helped!
My question current is really about better understanding something in this whole Root and Linux learning adventure I think I am totally confused about.
Basically if no custom ROM exist or your device is not listed on the supported list of devices in any recovery program....
OR as in my case you want desperately to get the thing back running on it's true stock what do you do?
Your rooted, but stuck.
So my main question is:
What is the best way to bring a device back to stock if there is no stock ROMs available and factory reset will not work?
On any device in this situation. Mostly I am hoping to have it explained in a way I can really finalize this confusing hole in my logic.
Like can a recovery program find it if it is still on the device somewhere and if not, why not?
Thanks in advance.
Additional backstory if helpful.
I have a Wacom Cintiq Hybrid running Android 4.1 that is ( now ) rooted..
This is a very bad thing. The Real Stock ROM has palm rejection and all the drivers to make it work as a tool. So stock is the ideal but it is clearly not stock as my device supposedly came in the
box running 4.2 and with software and drivers to make it work properly with the pen. This has nothing. No software and the smallest amount of apps possible. Worse this is no custom ROM its on ( I think) as it would be the worst one ever and it was not rooted on arrival. I have no idea what happened before I got it. I may have made the mistake of rooting it really as I found out to my dismay there is no ROM support. So back to square one. I bought it ( very cheap for one of these ) "stuck and unable to go to the play store" and I did not realize until I got it, on a version of Android it was not meant for. Wacom is totally and woefully unhelpful in every way. They seem to want to quietly put this device behind them at the expense literally of their customers.
I have discussed this problem in another thread if more details on all this specific to this device are of interest.
Duende101 said:
My question current is really about better understanding something in this whole Root and Linux learning adventure I think I am totally confused about.
Basically if no custom ROM exist or your device is not listed on the supported list of devices in any recovery program....
OR as in my case you want desperately to get the thing back running on it's true stock what do you do?
Your rooted, but stuck.
So my main question is:
What is the best way to bring a device back to stock if there is no stock ROMs available and factory reset will not work?
On any device in this situation. Mostly I am hoping to have it explained in a way I can really finalize this confusing hole in my logic.
Like can a recovery program find it if it is still on the device somewhere and if not, why not?
Thanks in advance.
Additional backstory if helpful.
I have a Wacom Cintiq Hybrid running Android 4.1 that is ( now ) rooted..
This is a very bad thing. The Real Stock ROM has palm rejection and all the drivers to make it work as a tool. So stock is the ideal but it is clearly not stock as my device supposedly came in the
box running 4.2 and with software and drivers to make it work properly with the pen. This has nothing. No software and the smallest amount of apps possible. Worse this is no custom ROM its on ( I think) as it would be the worst one ever and it was not rooted on arrival. I have no idea what happened before I got it. I may have made the mistake of rooting it really as I found out to my dismay there is no ROM support. So back to square one. I bought it ( very cheap for one of these ) "stuck and unable to go to the play store" and I did not realize until I got it, on a version of Android it was not meant for. Wacom is totally and woefully unhelpful in every way. They seem to want to quietly put this device behind them at the expense literally of their customers.
I have discussed this problem in another thread if more details on all this specific to this device are of interest.
Click to expand...
Click to collapse
Hello & welcome to xda-assist,
If you rooted the device you changed the system /kernel in the process, if root is all you done you should be able to unroot by using the unroot option in your root management application, if you did further changes like deleting system apps and so on it gets more complex, the best and easiest way to get back to the original state would be a copy of the latest firmware.. If it doesn't exist you're somewhat out of luck, please refer to this link for further help & information..
http://forum.xda-developers.com/android/help
Sam Nakamura said:
Hello & welcome to xda-assist,
If you rooted the device you changed the system /kernel in the process, if root is all you done you should be able to unroot by using the unroot option in your root management application, if you did further changes like deleting system apps and so on it gets more complex, the best and easiest way to get back to the original state would be a copy of the latest firmware.. If it doesn't exist you're somewhat out of luck, please refer to this link for further help & information..
http://forum.xda-developers.com/android/help
Click to expand...
Click to collapse
Thanks for the reply. So no way to get the extract the original firmware? I don't wish to un-root. The device was set to a very sad state of affairs when I got it, unrooted, with something very unlike the stock firmware and factory date reset not helping at all. Persistently locked into a lower version of Android than it was not meant for and not running the drivers or software it would seem I need to make it function properly that came with the device.
Basically it lead to my curiosity of how one goes about extracting or mining the data that is stored somewhere on the device if all I did was root. Which is all I did.
It should still be there. Basically how do I get to it?
The link takes me back to the forums for help, however I found no help there after much searching before I asked here but thanks
Duende101 said:
Thanks for the reply. So no way to get the extract the original firmware? I don't wish to un-root. The device was set to a very sad state of affairs when I got it, unrooted, with something very unlike the stock firmware and factory date reset not helping at all. Persistently locked into a lower version of Android than it was not meant for and not running the drivers or software it would seem I need to make it function properly that came with the device.
Basically it lead to my curiosity of how one goes about extracting or mining the data that is stored somewhere on the device if all I did was root. Which is all I did.
It should still be there. Basically how do I get to it?
The link takes me back to the forums for help, however I found no help there after much searching before I asked here but thanks
Click to expand...
Click to collapse
The intended of xda-assist is to direct you to the most suitable board of xda, we do not solve issues for you or do technical support, please be patient, it often takes time for exotic devices / questions to be seen by someone who can give hints and answers..
Edit: but it's not that the original firmware is stored somewhere on the device by default where you can grab it and reinstall it..
Sent from my OnePlus 2 using XDA Labs
Sam Nakamura said:
The intended of xda-assist is to direct you to the most suitable board of xda, we do not solve issues for you or do technical support, please be patient, it often takes time for exotic devices / questions to be seen by someone who can give hints and answers..
Edit: but it's not that the original firmware is stored somewhere on the device by default where you can grab it and reinstall it..
Sent from my OnePlus 2 using XDA Labs
Click to expand...
Click to collapse
Totally cool. It's a tough question.
The OG firmware thing is the toughest part to understand. Just wanted to make sure I was clear in my explanation and question.
Ok, so there was a thread on here for this issue, but it has been dead for 5 years so I hope it's ok I open this new thread.
I have been given a Samsung Tab 2 GT-P5110 by a colleague of mine. At some point in time he managed to corrupt the firmware to get the black screen of death 'firmware has encountered a problem.......'. This will not have been from flashing ROMs or attempting to root the device (he's an elderly guy, who recently asked me for help resetting his Google passwords, so rooting is well beyond his expertise). I first thought this won't be an issue, I'll hook it up to Odin, flash a recovery, stick it in download mode and then flash a new ROM...... However this failed, Odin confirming the process was unsuccessful. I understand this may be because the corruption is seated deeper than just the level of flashing a new ROM and have read flashing a new kernel may go deep enough to make progress, however, I have only ever used Odin for flashing ROMs so this is all new to me.
I would be very appreciative if someone was able to point me in the right direction, I have found some kernels to download which I think would be compatible, but I'm a little foggy on the steps I should take. Alternatively, someone may know another route to go down, I am also not afraid to open this little guy up and do some DIY surgery if needs be, after all I didn't buy the thing so I have nothing to lose.
Any suggestions would be great and if you want some more info please feel free to ask.
Thanks in advance.
elboobio said:
Ok, so there was a thread on here for this issue, but it has been dead for 5 years so I hope it's ok I open this new thread.
I have been given a Samsung Tab 2 GT-P5110 by a colleague of mine. At some point in time he managed to corrupt the firmware to get the black screen of death 'firmware has encountered a problem.......'. This will not have been from flashing ROMs or attempting to root the device (he's an elderly guy, who recently asked me for help resetting his Google passwords, so rooting is well beyond his expertise). I first thought this won't be an issue, I'll hook it up to Odin, flash a recovery, stick it in download mode and then flash a new ROM...... However this failed, Odin confirming the process was unsuccessful. I understand this may be because the corruption is seated deeper than just the level of flashing a new ROM and have read flashing a new kernel may go deep enough to make progress, however, I have only ever used Odin for flashing ROMs so this is all new to me.
I would be very appreciative if someone was able to point me in the right direction, I have found some kernels to download which I think would be compatible, but I'm a little foggy on the steps I should take. Alternatively, someone may know another route to go down, I am also not afraid to open this little guy up and do some DIY surgery if needs be, after all I didn't buy the thing so I have nothing to lose.
Any suggestions would be great and if you want some more info please feel free to ask.
Thanks in advance.
Click to expand...
Click to collapse
flash a custom recovery, and install this, https://builds.unlegacy-android.org/aosp-4.4/espresso/ua_espresso-4.4.4-20171105172717.zip
Thanks for the reply. I have attempted to flash a recovery, however every one I've tried fails and tells me 'NAND write failed'. I tried the TWRP recovery and philztouch. You don't have a link to a recovery you think might work? I'm pretty sure I've been using recoveries that should work, but you never know.