Hi,
I think flashing a ROM has been the biggest mistake I could make. I guess I just got greedy for a lil more performance that I decided to take the risk .Anyway, lots of things have gone wrong ever since.
To cut the story short, how can I reset my tablet to the way I got it? Locked bootloader, no cwm...how? I have restored via Nandroid, and did a factory reset...but still I can find traces of nothrills A700 ROM on my system. I wan't to get rid of all this.
Thanks!
PS: My device now shows up as "Acer A510 (registered November, 2012)" on Google Play. Previously, it showed up as "Acer A510 Tegra 3".
Please, don't start this conversation in multiple threads because people aren't answering your problems fast enough. You want to get back to stock because of problems (that have nothing to do with your flashing, but still) and people are already trying to help you with that in other threads.
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.
Hey guys, been a long time lurker here and just encountered my first issue, so made an account to hopefully get some advice.
I received the note 10.1 8010 (UK) as a gift for Christmas. I was disappointed to see it was running 4.0, when devices like the Nexus 7 are already on 4.2. And Germany had the 4.1 update for over a month. Samsung as always refuse to give a solid answer.
I followed a guide to install the German 4.1.1 update. I first installed the German version of ICS via Odin. I then applied the update.zip from here:
HTML:
d-h.st/lLB
Prior to this, I rooted the device, but I believe the above process removed the root anyway.
After my device rebooted, the S Pen isn't working at all. It recognises when I take the pen out, but I cannot use it. It doesn't do a thing. I've read about 1,000 forum threads and cannot find an answer, as to how I can get it working again.
I tried deleting cache and user data, then reapplying the update.zip to no avail.
When I boot up in to recovery mode, it does come up with a message about CSC and then the little drop falls over and I have the usual options.
Any idea what I need to do, to get my S Pen working again? Or what I've done wrong?
Many thanks
This is how I rooted the device.
HTML:
rootgalaxynote.com/galaxy-note-10-1-root/how-to-root-galaxy-note-10-1-easiest-methodcwmmethod-2/
I have a feeling this is the "root" of the issue. I'm not sure how to remove it.
I know previously I wasn't able to change my CSC via CSC switcher, but I am now.
So I guess installing the German ICS and then update.zip, hasn't completely undone whatever rooting it above did.
Removed the custom recovery and the pen started working again. At this point I was back on ICS, trying to see whether JB was the issue.
Now update.zip will not apply, despite the fact I'm on the German ICS stock. I get an error status 7 in package.zip.
This is the worst experience I've ever had, with any device in my life.
If this wasn't a present I'd have smashed it in to tiny pieces. I will never buy a non Nexus device ever again.
I know this may seem trivial, but when I'm running 4.2 on all other devices, I don't want to be stuck on 4.0 with my brand new tablet.
Samsung have really put me off ever buying their devices in the future.
Tehkseven said:
Removed the custom recovery and the pen started working again. At this point I was back on ICS, trying to see whether JB was the issue.
Now update.zip will not apply, despite the fact I'm on the German ICS stock. I get an error status 7 in package.zip.
This is the worst experience I've ever had, with any device in my life.
If this wasn't a present I'd have smashed it in to tiny pieces. I will never buy a non Nexus device ever again.
I know this may seem trivial, but when I'm running 4.2 on all other devices, I don't want to be stuck on 4.0 with my brand new tablet.
Samsung have really put me off ever buying their devices in the future.
Click to expand...
Click to collapse
This a pretty bummer situation. Sorry you're dealing with it.
I find this interesting, as I followed the exact same procedure to root as you. I haven't experienced any pen issues though.
Could it be the 4.1 you flashed?
This is one of my fears too, so I really hope this can be solved.
I finally managed it.
I downloaded a different German ICS from a different guide and this time it worked no problems.
The one that worked, had a file name: N8010XXALI3_N8010OXAALI3_DBT
Update.zip worked first time after I installed the above ICS.
Hope that helps.
Alright, so before I say anything, I have not visited this site nor have I conducted any business with roms, TWRP, etc in the past year let's say. I used to be an avid visitor, flashing a bunch of roms, but was tired of the amounts of bugs and problems that I found. So I restored my back to stock on my G2 from TWRP. Been using it for about 1 year now, just so I didn't have to deal with problems... until now.
So a few days ago I saw an update in my notifications, but for the love of God I cannot remember what it said. All I know was that it needed to update something about the phone, not for example an app. Today I decided just to update it, and suddenly the phone rebooted into TWRP. I thought that was weird so I rebooted it again, and back into TWRP I was. I tried restoring some old backups to see if they would maybe boot into it, but once again it keeps bringing me to TWRP. Now I am stuck in a position where I am unable to use my phone and am not sure what to do next. I haven't visited these forums in a while either so Im not sure where to post this xD.
Honestly if someone can suggest something or help me in any way, it is appreciated. If there is anything I can do to help, just say the word.
I am using the Canadian Variant of the LG G2, from wind. I believe it is a D801 but not an actual D801, as I remember being told to only flash D803 roms as it was basically a D803. Not sure if that helps. Im planning on getting a new phone so I just need this one to hang on a little bit longer.
Thread closed / Duplicate
Hi, really in the need for help, sorry if i get any concepts wrong but I've abandoned this kind of tech knowledge years ago.
XT1032, never rooted or anything, only installed OTA updates.
About a month ago it bricked (permanently stuck at Motorola loading screen). Tried to do a factory boot but CWM shows a dead android with a ! symbol on top of it. Too lazy to study and fix it myself i got it to a technician to fix it.
Everything got back to normal but it has been starting to slug just like before it brick'd.
Been thinking that rooting and installing a custom ROM could fix it? Thing is, I'm afraid to do it with CWM in such state.
Any ideas or tutorials to redirect me? Tried to google but only got specific cases of such issue with CWM for other phones
up?
last up
Hello people of XDA!
I know that this thread may be repetitive, but I unfortunately didn't find any help in all threads regarding GSII's NAND r/w problem.
So in short, I will explain what happened to this device
I bought this GSII brand new as my 1st flagship device, and I am kind of sentimentally connected to it, if not I would've thrown it in trash a long time ago.
So here is the thing
I had stock firmware on this device (4.1.2 JB) , and after some time decided to flash CM 11 on it when it came out, and had it on my phone for 4-5 weeks but I instantly noticed that my device was overheating with that ROM so I decided to get back on stock firmware, unfortunately thing is that i flashed android 4.0.3 ICS (Movistar Mexico) then my device got bricked (I had a really bad knowledge back then about roms and things that I SHOULD and SHOULDN'Tdo), anyway I tried fixing the mess I made by flashing my original android 4.1.2 JB rom (Telenor Serbia) hoping that will solve my bricked device, but unsuccessfully. Then I tried flashing again standardly for maybe 4-5 times with no success and decided to explore more functions that odin provides, so I checked NAND erase all last time I flashed and I guess made a huge mistake, but still I couldn't boot my device, I tried hard resetting it (I lost my power button while replacing the screen of my phone, so I couldn't boot into recovery to check if device is soft bricked or really hard bricked, but download mode works just fine). Still I tried, I flashed custom kernels hoping they would fix this brick but nothing happened, I would really like to get this thing working again, I had no success at finding a good mainboard to replace the old one, and doing it in official repair shops and non-official ones costs more than the phone itself. Sorry for asking the same old question I guess but I would be really thankful if I could get this working again!