I want to use guaranty for my tablet so What should I do to turn my rooted device to official state.
Full story:
Touch screen stopped working and I can work only with pen. I searched web and tried some solutions such as factory reset, but didn't help.
So i think it's a hardware issue and I want to turn it in for repair. But the problem is I've rooted my device with odin(probably with custom Rom) and my binary counters shows 2.
Please guide me how to roll back to official state
P.S. If anyone can help to solve the touch screen issue, I prefer to have my device rooted.
Download and run Triangle |Away from the Play store .
Run TA
Boot to download mode flash stock rom for your phone reboot factory reset.
ardalan_o said:
I want to use guaranty for my tablet so What should I do to turn my rooted device to official state.
Full story:
Touch screen stopped working and I can work only with pen. I searched web and tried some solutions such as factory reset, but didn't help.
So i think it's a hardware issue and I want to turn it in for repair. But the problem is I've rooted my device with odin(probably with custom Rom) and my binary counters shows 2.
Please guide me how to roll back to official state
P.S. If anyone can help to solve the touch screen issue, I prefer to have my device rooted.
Click to expand...
Click to collapse
Post # 2 covers the restore but I have seen many posters with pen issue just like yours and it appears that you could have caused the problem somewhere in your Rooting and or the installation of the custom ROM.
Do a search there are lots of people with the same condition and I believe it is rooting and or user MOD's related.
Good luck.
.
Tanx JJegan, It worked smoothly:victory:.
But still I have the touch screen issue kkretch .
Now I am realy convinced that it is hardware. but thank you for the tip man.
Related
i have a samsung captivate i897.
i bought it sim free and unlocked from the states but i'm in the UK.
i recieved it already rooted running cyanogen mod and miui and have had it for 8 months. its worked perfectly the whole time.
until the past month i'd say its been radomly forcing closs on nearly everything.
i havent installed any new software or roms or anything or even dl any new apps so i cant figure out what would be causing the problem.
i tried checking for updateds on the muiu and it runs android 2.3.7
i'm not a tech person at all so i spoke to one of the tech guys at my local phone shop and he said i should try a factory reset.
so i guess i'm asking a few questions here:
1) does anyone have any idea what might be up with my phone?
2) can someone elplain to me the easiest/safest way to fix it?
please bear it mind i am a total noob at this tech stuff. i'll try to understand and cooperate as much as i can with those so kind to help me, but i'd really appreciate if people would help/point me in the right direction instead of giving me a short blunt answer which assumes i know all this tech stuff then locking my thread.
If it's already rooted & running a custom ROM, then you probably already have a custom recovery installed (probably clockworkmod). 1st thing would be to boot into recovery & do a backup. Then, you can try flashing any ROMs you want / factory reset / whatever, and restore your backup if you don't like the results.
-- Sent from my TouchPad using Communities
how do i know if i have clockwork mod installed (i've never seen it before, but then again if its on the boot menu where i've not been before)
for booting into recovery i just long press the power button (at least it works like this on my phone) > reboot > recovery > ok
then what should happen after i press "ok" ?
also just to state (if it helps) the options i get for rebooting are: normal, hot boot, bootloader & recovery.
i dont really feel confident to be flashing roms (mainly because i dont really know how/which are stable etc) on the other hand i do need to fix it. guess i'd like to try the factory reset first though..... under the assumption its slightly easier.
i thought factory reset would restore the phone back to stock settings? but the guy in the phone shop said it wouldnt? (not sure how reliable he is ;] )
found this thread here which seems kinda similar
http://forum.xda-developers.com/showthread.php?t=1264177&page=3
have tried uninstalling some apps to see if it helps.
the thing is with the problem is seems to occur randomly. the phone will work like perfect again for a few days then boom starts forcing close yet again.
only time will tell.
New to this site but have done days of searches for my problem. Since JB update my bluetooth is not working and I have also found out Airplane mode is messed up also. Both will have slight responses for a short time after booting , then nothing. I down graded back to ICS and I get some functionality and have actually paired a device but does not work correctly. Asus wants the tablet sent back , but it sure seems to me as it is Op system causing all of this. It was working fine before. I am new to messing around with android , So one question is since I down graded to ICS 4.0 does the actual device firmware downgrade completely also ? I see that Bluetooth Version lowered and other versions lowered , but could something else not get back to that version , some type of Bios type settings? ( I was told no Bios in android ,but is there something like it ? )
So does anyone have the same problems , any answers or thoughts ?
Is there a way to erase everything completely and go back to the exact files software , kernals etc. as when in the box it came in.
Sure seems to act like a software driver type problems.
What are the "Source Code" that are offered on the Asus Site ? Can those used to be used to Factory fresh the device ?
I do not want to void any warrenty , but before I send back I want to see if it is Hardware or software.
Thanks
wadea2 said:
What are the "Source Code" that are offered on the Asus Site ? Can those used to be used to Factory fresh the device ?
Click to expand...
Click to collapse
Source code is only useful for software developers. To restore your device as close to factory state as possible, install the full firmware package of your desired version, as you already did when downgrading, and wipe data.
Things not restored by this method:
- device-dependent settings (e.g. serial number, sensor calibration data)
- DRM key
- Partition table
These usually cannot be changed by the user and therefore do not need to be restored anyway.
My main concern is the kernal, I feel that this may be the cause of my problems , if indeed the hardware does not have a problem. So when I restored to ICS , Did the kernal complete revert to factory also ? I understand now that the Kernal is the ( Bios) of Android , takes comands from software and tells hardware what to do . ( Right ? )
I am finding that the "Factory Reset " from from "Setting" does not truely reset all settings ( I set a Sound Setting before Reset , and the same setting was "on" after the reset ), therefore a "Firmware" reset back to ICS may leave the reason my bluetooth and airplane is not working.
So is there a way to use the "blob" with-out rooting or causing a warrenty issue ?
The kernel is part of the full firmware, so it is flashed when you install the firmware. It is the core of the operating system and also contains all the hardware drivers. The PC BIOS would be more comparable to the tablet's bootloader, as it only initializes the hardware and loads the kernel.
Your problem description is completely worthless. If you expect help, state exactly what you did, which error messages appear, and describe in detail what does not work and what you expected.
I thought i expalined better. I will try again. I used my bluetooth on my tablet connected to my phone and sent photos to tablet from phone. All was fine, Did not try and use bluetooth again untill a week later ( 3 days after OTA JB update ) now the bluetooth does not work and I see that Airplane mode is not working correctly either.
Since this happened right after the JB Update , It made since to me it is an update problem. I was wanting to go back to the exact state before update to see if errors were gone. I have re installed ICS and had better response from bluetooth , was able to pair a device but after pairing would not work ( headphones , sound stayed on tablet ) .
With these findings it would lead me to beleave two things , the "Firware install of ICS " left traces of the newer Kernal , that caused the problem or the Tablet hardware is the problem.
does that make more since to you ? Sorry about the first Question. I have let the tablet do the OTA back to JB and still in the same situation. I have an RMA set up , but I just like to know for sure the cause before sending back.
Thanks for you time.
wadea2 said:
now the bluetooth does not work and I see that Airplane mode is not working correctly either.
Click to expand...
Click to collapse
I'm giving up.
Ok, Well thanks for trying ? I do not have any other info. to tell you then my last reply , that is all that I can explain , What is wrong what I did and what I was trying to figure out by process of elimination.
In an attempt to deal with massive instability I was able to upgrade from Samsung Stock to SlimKat 4.4.4r1. The instability problems remain but now I can't install apps. I have tried to flash to Carbon ROM but that doesn't take.
Curiously, all of the indications are that the apps and ROMs are installing but they in fact they actually don't.
The device doesn't even stay on long enough for me to alter a Setting, it trips over in a matter of seconds and reboots. Each time, I get the error message “Unfortunately, The process android.process.media has stopped”.
Could this be the Brick Bug manifesting itself? Perhaps if I repair the PIT that would fix it? Luckily I can access TWRP 2.7.0.0 recovery, I have tried to upgrade to TWRP 2.8.0.0 but that has failed also.
Any suggestions would be welcome
Hi, I would like to thank all those who took the time to read my description. Clearly it has you flummoxed too.:laugh:
In the meantime, I tried flashing Stock ROM but no joy and then I tried repairing the PIT, no joy there also.
My options now are either to ask Samsung to take a look or else wait for a functioning Tab with a broken screen to come along. My Tab is in superb condition and it would be a shame to let it go without at least making another attempt at rescue.
hi, in the past I had a huawei y511 and because I had this problem I've changed my phone now, but I want to fix it. plz help me.
Previously I could root my phone easily using framaroot 1.8, and I tried to root my phone to do some things then after things got ok, I unrooted it and this was done several times, but the latest time I wanted to root, it didn't allow me and I installed framaroot 1.9 and rooted successfully. but the problem started from here, after a couple of days, constant force closes came and without any they started force closing, clicking ok and the next one was there! sometimes restarting could fix my problem but in some situations restarting the phone was not the solution and I was made to enter recovery mode to full wipe, then everything could get ok again! firstly I thought the problem is from updated gaps, so I tried keeping them outdated to see if it was relating to this, but no nothing changed, although no apps was updated, these errors came again! I even flashed my phone (but I hadn't unlocked it's bootloader) to the stock rom to see if it could fix but NO, even in this rom problem existed and already exists! I googled a lot but couldn't find any working solution so i ask my question here! I do not know that may either unlocking bootloader or just installing a custom rom fix my problem?!?!?! plz help me this is really annoying!
HUAWEI Y511-U30, BB118
PLZ PLZ PLZ SOMEONE HELP!
I have an HTC One M9 (Sprint) software version 2.11.651.19 (OPJA2) with Android v5.1
Within the last couple months I unlocked the devices bootloader, and rooted it. Last night I left the phone under my laptop and I'm thinking it got way way way too hot, somehow the thing is still alive, however when I went to turn it on in the morning, I had no wifi or cellular capabilities. At first I assumed this was a hardware issue, however I then unrooted the device on a whim, and this fixed it (Until I turned it off again, to my dismay).
I'm thinking somehow my phone overheated (Which explains why my battery life won't go over 47%) and somehow my flash memory must have been corrupted because I can no longer boot into recovery mode, which is my serious catch 22. Since I figure this is some issue related to my firmware, which I would LIKE to reflash (This is my goal here). To my dismay, in order to flash a stock RUU or firmware to the device, you must have your bootloader relocked. However in order to relock your bootloader you must have root, and like an idiot I unrooted it. I can't reinstall SuperSU through my TWRP recovery because my phone refuses to boot into recovery mode. I attempted to re-flash TWRP to the device through download mode, the flashing is completed successfully, however I still cannot boot into my recovery. To break it down simply:
-Want to reflash stock firmware
-Must have root to reflash stock firmware/RUU
-Don't have root because I uninstalled it
-Can't re-root because my recovery is corrupted
-Can't re-flash TWRP (Already tried and it's not working)
-Can't re-root because I can't flash TWRP
-Can't reflash stock firmware because I can't disable it with root
Regardless of this I attempted to use adb and echo to relock the bootloader however instead of getting # I get $, so I'm not really able to do this either. Is there ANY way I can repair my recovery, has anyone ever run into an issue like this before? Or am I just completely screwed, hahaha.
Do you think I might be able to reflash Android V5.1 to try and fix the corruption and then maybe that would allow me to get into recovery mode so I can flash Super SU so I can at least factory reset my device with TWRP, or possible reload stock firmware and factory reset from there?
Thanks guys for any help you can provide.
*EDIT
If anyone wants to provide any advice great, but for now I'm going to try using HTC Sync Manager to load Marshmallow (v6.0) onto the HTC and see if this may allow me to actually get into recovery mode. Downloading the file from here: *nevermind can't post links yet, under 10 posts, you can find it on HTC's website* (This is for the HTC One M9, Sprint) in case anyone else EVER has to run into this awful issue, lol.
Moderators please feel free to update the thread to SOLVED status, I was able to update my phone to marshmallow to resolve the issue. This time around I WILL be backing up my phone, probably not going to root it this time around either, I have like 3 other phones so I'll just root them instead, lol. If you would like the download link I am happy to provide it VIA PM so you can update my OP with the link for the full fix. My phone is able to get wifi and texts now without an issue, unfortunately all my data is wiped but honestly I don't really care!!
Thanks everyone!
Good job on solving your issue.
If you have further questions or want to help out others, you can do so here
http://forum.xda-developers.com/sprint-one-m9/help
http://forum.xda-developers.com/sprint-one-m9
Thread closed