brickbug question - Samsung Galaxy Tab Plus

i just got my tap 7 plus a couple of weeks ago and have been reading through the forums about this bub. all i have done is root the tap and do not plan on putting ics on it till it is released in the states as an ota update.
if i get the ota update am i safe from this bug or is it a case of the tab not liking ics.
i bought me tab off ebay and it is refurbished unit. i tried to register it with samesung and they said that i couldnt since it was refurbished so i dont want to screw it up.
so bottom line---is the bug only triggered by flashing the ics update from austria or is it any ics update including the official ics from samsung for the usa

Please, do NOT start another brickbug topics, again!

air001 said:
Please, do NOT start another brickbug topics, again!
Click to expand...
Click to collapse
i just want to know if the ota ics update is safe. if i had wanted a smartass answer for my question i would have asked my wife!!!!!

There are 2 more topics about this question.
http://forum.xda-developers.com/showthread.php?t=1818638
http://forum.xda-developers.com/showthread.php?t=1828367
Why did you start the 3rd?

Closed, as mentioned above, there are multiple threads on this already.
Its always better to use an existing, relevant thread rather than opening a new one.
The "main" brickbug is that if you have a eMMC chip with insane firmware and the kernel has emmc cap erase enabled then wiping (or flashing) from CWM or stock recovery can cause a hardbrick.
It seems there is another brick effecting the galaxy tab plus related to the stock recovery, best bet is to check out the threads linked above
Use the brickbug test apps to see if when samsung refurbished it they replaced the motherboard for one with a sane eMMC chip

Related

Reset back to factory

I use to follow XDA very regularly when I had my HTC Hero a year ago, and then followed another forum (can't remember the name) when I had my Samsung Moment. I remember both of those phones had the ability to use a RUU in case the worse happened. I believe the Samsung didn't use a RUU file, but it was similar in function. Anyhow, I was just wondering since I just got my Samsung Galaxy S 4g and would like to start rooting again, is there a way to revert back to factory in case I decide I no longer want to root or if the worse case scenario happens (boot loop, no boot, ...etc)? Having these factory firmware files made bricking a phone much less likely. Correct me if I am wrong. Thanks in advance!
you posted this in the wrong forum. this goes into the general section.
to answer your question, you can always use odin to restore everything should you soft brick. check out the bible below for should you brick (noobs guide to odin) and for information in general:
http://forum.xda-developers.com/showthread.php?t=1117554
and also user danstheman7's site, as well:
http://cyclopscomputers.com/gs4g
to go back to stock, you can check out krylons stock+root rom. you can unroot using superoneclickroot.
mar122999 said:
I use to follow XDA very regularly when I had my HTC Hero a year ago, and then followed another forum (can't remember the name) when I had my Samsung Moment. I remember both of those phones had the ability to use a RUU in case the worse happened. I believe the Samsung didn't use a RUU file, but it was similar in function. Anyhow, I was just wondering since I just got my Samsung Galaxy S 4g and would like to start rooting again, is there a way to revert back to factory in case I decide I no longer want to root or if the worse case scenario happens (boot loop, no boot, ...etc)? Having these factory firmware files made bricking a phone much less likely. Correct me if I am wrong. Thanks in advance!
Click to expand...
Click to collapse
you used to follow XDA? and yet you post on the wrong forum?? and start reading!!!!! mod please close this thread.. the answers to these question are in the forum. they just need to read more.
Thread closed.

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

[ROM][ODIN] P500VPBMB3 Sprint 4.1.2 Firmware

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.

[Q] Need help to update Samsung Galaxy S III I9300

Hello folks,
i am new here, i have a problem with one of my friends mobile Samsung Galaxy S III I9300 Android v4.0.4 (Ice Cream Sandwich), it so happened he dropped the mobile from his hand and from that moment, the device fails to load properly.
I tried to go to Recovery mode, by pressing Power key+DownVol key+Home key. The next screen was all fuzzy, it didn't show anything.
So i tried Power key+UpVol key(this time)+Home key, it showed a warning page, please see images to be more clear.
On continuing with the process, it went to Download mode.
I am little familiar with that process, since it is trying to update the device OS to a newer version of Android.
I did a little research and found out there was Android 4.4.4 Kit Kat available.
I can proceed to download that, but i want to know few things and i.e.,
The device is not Rooted.
CWR is not installed.
Whether it is safe to proceed with the update of Android Ice Cream Sandwich to Android Kit Kat.
I also found Galaxy S III can be updated to 4.3 (Jelly Bean), but i want your opinion which would be suitable for this device.
Thanks.
I do not want to brick my friends device, since i am getting paid to do this stuff. Hence i am requesting any kind of expert advice.
Thank you.
P.S: Any suggestion is welcommed and waiting for any reply impatiencly. Also if the moderator thinks this post must be in some other part of the forum, please do so. :fingers-crossed:
Hello again, i did a little research and found out this site, where it mentions in detail how to install ClockworkMod Recovery 6.0.4.7 on Galaxy S3 GT-I9300
http://trueandroid.com/install-clockworkmod-recovery-6-0-4-7-on-galaxy-s3-gt-i9300-how-to/
I did as mentioned in the tutorial and while opening the Odin, and checking the AP button, and selecting the non touch version of ClockworkMod Recovery 6.0.4.7 ; i am getting this error. Please see the snapshot.
It also say, PIT partition not found, does anyone know how to figure out this problem.
Or
Is it a hardware issue, do i need to change the motherboard or give it to technician to fix it.
First off: Have you tried posting it under the correct category on this forum? its under galaxy core... you have a galaxy S 3
Second, you can update if it stock... custom recoveries and roms do void warranty. That is, if the kitkat is for his phone it is no problem. upgrading wrong rom to your phone will mess with it yes. Boot loops and stuff.
Then again, if it droped I would rather have sent it in for repairs if it was still under the warranty .
canisalbus said:
First off: Have you tried posting it under the correct category on this forum? its under galaxy core... you have a galaxy S 3
Second, you can update if it stock... custom recoveries and roms do void warranty. That is, if the kitkat is for his phone it is no problem. upgrading wrong rom to your phone will mess with it yes. Boot loops and stuff.
Then again, if it droped I would rather have sent it in for repairs if it was still under the warranty .
Click to expand...
Click to collapse
I find it quite difficult to find my way in this forum, just newbie here.
But thank you for your concern. My friend has taken the mobile , he thinks its better to repair it by technician.
Enough of head-ache for a device that can't be repaired through updating, the mobile was trashed. Couldn't be salvaged through
updating.
desktopuser said:
I find it quite difficult to find my way in this forum, just newbie here.
But thank you for your concern. My friend has taken the mobile , he thinks its better to repair it by technician.
Enough of head-ache for a device that can't be repaired through updating, the mobile was trashed. Couldn't be salvaged through
updating.
Click to expand...
Click to collapse
I understand.
On top of the page there are 2 places you can enter stuff, one says "type to find device" and the other for searching all the forums. Writing i9300 - and clicking on the line - will get you the I 9300 forums
desktopuser said:
Hello again, i did a little research and found out this site, where it mentions in detail how to install ClockworkMod Recovery 6.0.4.7 on Galaxy S3 GT-I9300
http://trueandroid.com/install-clockworkmod-recovery-6-0-4-7-on-galaxy-s3-gt-i9300-how-to/
I did as mentioned in the tutorial and while opening the Odin, and checking the AP button, and selecting the non touch version of ClockworkMod Recovery 6.0.4.7 ; i am getting this error. Please see the snapshot.
It also say, PIT partition not found, does anyone know how to figure out this problem.
Or
Is it a hardware issue, do i need to change the motherboard or give it to technician to fix it.
Click to expand...
Click to collapse
Bro you should have unchecked the re partition option
Susan Dahal said:
Bro you should have unchecked the re partition option
Click to expand...
Click to collapse
OOPS! I did not even see that one

[Completed] Can Clockwork or another recovery program find and backup your truly stock ROM?

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.

Categories

Resources