My g tablet has 2 dead pixels on it and while I still have a 2 week warrenty with office depot I want to return it and get another one. But I am running gingerbread and I need to get it back to stock. Everything is working fine except those pixels. So is there a way to use clockworkmod to install the stock rom? I know people use NVFLASH but is that necessary since my tablet is still responsive to everything. Thanks,
Here's the link to the instructions.
http://forum.xda-developers.com/showthread.php?t=861950
Another way is to flash using clockwork mod with the original roms. My notes below:
TnT 3316 recovery ROM, dated 12/19 and supplied by Viewsonic / TnT.
Link:
Alternate link: http://www.mediafire.com/?p9o52540baa5vfg
md5sum: 1333e22b6d802096d3c63757680777f0
TnT 3053 recovery ROM, dated 12/10 and supplied by Viewsonic / TnT.
Link:
Alternate link: http://www.mediafire.com/?qy92jzoz8upy8xa
md5sum: 7b800e409b5324f2c69e7ba6f84eab97
TnT 2967 recovery ROM, dated 11/22 and supplied by Viewsonic / TnT.
Link:
Alternate Link: http://www.mediafire.com/?99eb11cqhvrkkc7
md5sum: 43eb0358db25b492751b1b0a71568c51
These were grabbed fromover-the-air update. They are full recovery
images that wipes everything except the user data.
To use this with a vanilla recovery, you need to rename the file
to update.zip, copy it to the root of /sdcard, and also create a recovery
folder with a file called "command" (see the 1.00 release for that file).
When you run recovery, the command file will direct recovery to run
the update.zip to update the system. OR
YOU SHOULD BE ABLE TO SELECT THE ZIP WITH CWM RECOVERY MENU.
http://forum.tegratab.com/viewtopic.php?f=6&t=16
When you flashed it with a different firmware, you voided your warranty.
wasserkapf said:
When you flashed it with a different firmware, you voided your warranty.
Click to expand...
Click to collapse
You seriously think they can tell the difference at Office Depot ?! Even if he just took it without re-flashing it ?
supergroverthm said:
They are full recovery
images that wipes everything except the user data.
Click to expand...
Click to collapse
So that would remove even CWM ??!
aasoror said:
You seriously think they can tell the difference at Office Depot ?! Even if he just took it without re-flashing it?
Click to expand...
Click to collapse
It's the principle of it. You know going into it that flashing alternate firmware voids the warranty.
Doesn't anyone have any morals anymore?
wasserkapf said:
It's the principle of it. You know going into it that flashing alternate firmware voids the warranty.
Doesn't anyone have any morals anymore?
Click to expand...
Click to collapse
No. People open their devices and break them and return them. It wasn't their fault they broke the cable. People don't read instructions and soft brick their devices and return them. It wasnt their fault the firmware was horrible. I have ASUS Transformer on order. When it gets here I'm rooting it (and yes if I bork it I will buy another) and wiping XDA from my browser history. It may just be this device device but I don't believe I have ever seen so many people willing to purposely void their warranty and then expect the manufacturer to replace what they have screwed up. I think its goodintentions who keeps saying....."Buy an iPad2". Thats my recommendation from now on as well.
wasserkapf said:
It's the principle of it. You know going into it that flashing alternate firmware voids the warranty.
Doesn't anyone have any morals anymore?
Click to expand...
Click to collapse
What does morals have to do with this ?!?
Does your morals tell you he should suck up a defective display because he changed the software running on his device ?!?
And no, in principle flashing alternate firmwares doesn't void the warranty "UNLESS" you break your device doing so, if you consider running code on the hardware an alteration then installing any software from "gmarket" or "amazon app store" voids your warranty.
Warranty doesn't cover malfunctions caused by user alterations, how does dead pixels related to custom roms is beyond me.
I successfully restored it to the original rom and exchanged it. They never even opened the box. Just said here you go and have a nice day.
Related
I am looking for info for the Dev section library. Though there are a few comments made regarding flashing back to stock, none seem to offer a (up to date) return to store, stock phone method.
That having been said could sombody offer up a tutorial so I can post it.
Thank you.
Entropy's Thread entitled "[Heimdall][Odin][Stock][Root]UCKH7 Return/Unbrick to Stock (or Root)" is the closest you are going to find to a complete restore to stock.
http://forum.xda-developers.com/showthread.php?t=1286432
I believe this will work for a good majority of folks needing to get back to stock (provided they haven't completely hosed or done something crazy).
Basic steps:
1. Flash the package in the second link of the OP - *NEW* - Kernel + non-rooted system package using either Odin or Heimdall (user's choice - and extract or prepare files accordingly)
2. If the user has accidentally flashed a i9100 International ROM, then they may need to also reflash the stock ATT modem (also in the thread)
3. For good measure, after those items are flashed, probably best to do a factory reset (either via # code or in the UI)
As I mentioned, that should work for 95% of folks that need to go back to stock.
The other 5% are people that flashed a ROM that had new or alternate bootloaders. In this case, I am not aware of any Odin one-click package or bootloader pack available (yet) for the stock ROM, so this may been an issue. But someone may have some more updated information on that.
First settings> privacy> factory data reset.
Then boot into download mode and flash stock plus non root package from here
http://forum.xda-developers.com/showthread.php?t=1286432
With heimdall or Odin
And for anyone who has flashed a different modem you can get the stock modem from the above thread also.
and encase you need to repartition you will need a stock .pit file as well - though as of now as far as I know this is not needed for any reason - non of the roms or kernels in the dev section here in the att xda forums would cause any need for a repartition. Take care with .pit and repartitioning you could end up with a soft brick, a situation that can be recovered from but still not desirable
And if you have flashed anything containing the boot loaders you will need stock boot loaders too, but be very careful with boot loaders as a mistake with boot loaders can result in a hard brick
Sent from my SAMSUNG-SGH-I777 using XDA App
tomween1 said:
I am looking for info for the Dev section library. Though there are a few comments made regarding flashing back to stock, none seem to offer a (up to date) return to store, stock phone method.
That having been said could sombody offer up a tutorial so I can post it.
Thank you.
Click to expand...
Click to collapse
How to Prepare Your Phone to Return to the Store or for Warranty Replacement
There you go. A nice easy to read guide by creepy. Good work.
Sent from my SAMSUNG-SGH-I777 using XDA App
Great guide creepy.
To the OP - why do you believe my packages are not up to date? There is only one firmare revision available for our phone, and that's UCKH7. UCKJ2 is a leak - trying to return a phone with J2 will be a surefire sign to AT&T that you've been diddling around.
It is correct I don't include bootloaders in the package - this is intentional, flashing bootloaders is extremely dangerous. I have a bootloader dump buried within the thread, but I strongly encourage you NOT to try flashing those - again, very dangerous with a good chance of hardbricking.
Entropy512 said:
Great guide creepy.
To the OP - why do you believe my packages are not up to date? There is only one firmare revision available for our phone, and that's UCKH7. UCKJ2 is a leak - trying to return a phone with J2 will be a surefire sign to AT&T that you've been diddling around.
It is correct I don't include bootloaders in the package - this is intentional, flashing bootloaders is extremely dangerous. I have a bootloader dump buried within the thread, but I strongly encourage you NOT to try flashing those - again, very dangerous with a good chance of hardbricking.
Click to expand...
Click to collapse
Well I read through my post again. I thought my question was pretty straight forward, by the responses I received, but I can see where you could have misconstrued my request.
Your packages are all great and (with out a doubt) are the go-to steps. However for noobs, I wanted a more "spelled out" dictation of the steps.... Like the ones supplied by creepyncrawly!
Bro my apologies if I've offended you.... THIS WAS NOT MY INTENT!!!
I still have questions of superuser being in the apps, after all these steps. As I stated to you (PM). I really don't remember if this is installed by AT&T/Samsung out of the box. If not, how is it removed? I would assume, if one were to return a phone, this would be something AT&T wouldn't want to see (again assuming it wasn't stock).
Was the su app still there after flashing entropy's non root package? Are you sure you flashed the non root package and not the stock + root?
Sent from my SAMSUNG-SGH-I777 using XDA App
tomween1 said:
Well I read through my post again. I thought my question was pretty straight forward, by the responses I received, but I can see where you could have misconstrued my request.
Your packages are all great and (with out a doubt) are the go-to steps. However for noobs, I wanted a more "spelled out" dictation of the steps.... Like the ones supplied by creepyncrawly!
Bro my apologies if I've offended you.... THIS WAS NOT MY INTENT!!!
I still have questions of superuser being in the apps, after all these steps. As I stated to you (PM). I really don't remember if this is installed by AT&T/Samsung out of the box. If not, how is it removed? I would assume, if one were to return a phone, this would be something AT&T wouldn't want to see (again assuming it wasn't stock).
Click to expand...
Click to collapse
did you use the UNROOTED version of the package that he provided?
no, superuser is NOT provided by ATT, for obvious reasons.
dayv said:
Was the su app still there after flashing entropy's non root package? Are you sure you flashed the non root package and not the stock + root?
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
Well there's something interesting. I will retry. I had both on my computer and may have used the wrong one.
Hello,
I'm going to send my Galaxy S2 in for repairs but I need to un-root it first.
I'm searching for the official Vodafone Australia kernel DUKJ1
http://forum.xda-developers.com/showthread.php?t=1113928
The kernel is there but because multiupload is down I cannot download it. I have tried Check Fus downloader but it does not have DUKJ1. Is there any other way I can get the kernel?
Also do I even need to un-root it as I have used the usb jig to reset the binary counter?
Um, actually, Checkfus does have KJ1 for Voda AU. This is the most recent firmware available for Voda AU via Kies (I just checked this with my own copy of Checkfus).
Download the entire rom and extract the kernel zImage.
If you leave a rooted kernel on it & whomever repairs the phone notices this, there's a fair chance your warranty will be deemed to have been voided. Frankly, you might as well flash the entire KJ1 rom package from Checkfus (for all whomever repairs it knows, you probably updated OTA via Kies), then do a factory reset then double check to make sure there's no trace of any apps that required root left on the phone.
Then jig it again just to be doubly sure.
Then done. Send it in for warranty service.
MistahBungle said:
Um, actually, Checkfus does have KJ1 for Voda AU. This is the most recent firmware available for Voda AU via Kies (I just checked this with my own copy of Checkfus).
Download the entire rom and extract the kernel zImage.
If you leave a rooted kernel on it & whomever repairs the phone notices this, there's a fair chance your warranty will be deemed to have been voided. Frankly, you might as well flash the entire KJ1 rom package from Checkfus (for all whomever repairs it knows, you probably updated OTA via Kies), then do a factory reset then double check to make sure there's no trace of any apps that required root left on the phone.
Then jig it again just to be doubly sure.
Then done. Send it in for warranty service.
Click to expand...
Click to collapse
What version of Checkfus do you have as I can't find it. I select Android then GT-1900T but KJ1 is nowhere to be seen?
Thanks.
2.1. Android/I9100T/Australia (Vodafone). Tells you original firmware was KF2, then hit check firmware. Tells you KJ1 is latest released on 8/11/2011.
Are you sure you're using the PC version & not the phone app ?
Eye_Blake said:
What version of Checkfus do you have as I can't find it. I select Android then GT-1900T but KJ1 is nowhere to be seen?
Thanks.
Click to expand...
Click to collapse
I got it working, thanks alot.
To re jig it I flashed the old bootloader, should I re flash the new bootloader or leave the old one?
No worries
Unless you have a specific reason for flashing the new bootloader (I.E. something not working without it), leave it. The less you mess around with bootloaders the better.
Eye_Blake said:
I got it working, thanks alot.
To re jig it I flashed the old bootloader, should I re flash the new bootloader or leave the old one?
Click to expand...
Click to collapse
The reasons I planned on sending the phone in for repair/replacement were that is would turn on and off by itself sometimes, would open voice talk by itself almost constantly and would make the charging 'beep' noise when not plugged in.
Since unrooting none of these problems have happened again, should I still send it in for repair/replacement? Why would unrooting fix these problems?
Hard to say. Was the phone just rooted, or were you running a custom rom ? If the latter it may have been something in the rom causing the issues.
Up to you. Maybe run it for a week or two (or whatever) & see how it goes. You've unrooted it, you can jig it if you haven't already & send it in for warranty service whenever you like.
Obviously jigging it & going back to stock is never a guarantee of warranty service (given you've voided the warranty by rooting it in the first place), but most people who have done this have been fine so far as warranty service is concerned. I have seen a few exceptions over the past few months on here, but it's hard to say whether those people followed all the steps before sending it in or not.
That would be a good idea!
MistahBungle said:
Hard to say. Was the phone just rooted, or were you running a custom rom ? If the latter it may have been something in the rom causing the issues.
Up to you. Maybe run it for a week or two (or whatever) & see how it goes. You've unrooted it, you can jig it if you haven't already & send it in for warranty service whenever you like.
Obviously jigging it & going back to stock is never a guarantee of warranty service (given you've voided the warranty by rooting it in the first place), but most people who have done this have been fine so far as warranty service is concerned. I have seen a few exceptions over the past few months on here, but it's hard to say whether those people followed all the steps before sending it in or not.
Click to expand...
Click to collapse
It was just rooted. Yeah that's a good idea, I'll see if it plays up in the next week, thanks!
Do you think they will replace it or just repair it?
No idea. That's entirely up to them. But unlikely to replace outside the first few weeks unless the phone was unfixable if previous experiences on here are anything to go by.
Eye_Blake said:
It was just rooted. Yeah that's a good idea, I'll see if it plays up in the next week, thanks!
Do you think they will replace it or just repair it?
Click to expand...
Click to collapse
MistahBungle said:
Hard to say. Was the phone just rooted, or were you running a custom rom ? If the latter it may have been something in the rom causing the issues.
Up to you. Maybe run it for a week or two (or whatever) & see how it goes. You've unrooted it, you can jig it if you haven't already & send it in for warranty service whenever you like.
Obviously jigging it & going back to stock is never a guarantee of warranty service (given you've voided the warranty by rooting it in the first place), but most people who have done this have been fine so far as warranty service is concerned. I have seen a few exceptions over the past few months on here, but it's hard to say whether those people followed all the steps before sending it in or not.
Click to expand...
Click to collapse
Any proper guide to be done before send to repair?.. i've just sent my phone to service today. Battery temperature warning problem. Re-flash stock rom with stock kernel. Everything goes back like factory settings
Just the usual steps I.E. flash stock firmware, do a wipe/factory reset, use jig to reset the flash counter, double check that the reset worked & there are no traces of old apps on the phone which required root that could tip off whomever fixes the phone that you'd rooted it. Some say you should first (while the phone is still rooted) go into CWRecovery and format cache, data, system, & sd card. Then flash stock firmware and then use the jig. Depends on how paranoid you are I guess.
As I said to the previous poster, there are no guarantees of warranty service after you root or flash non-stock firmware on your phone (you shouldn't expect same), however if you follow these steps you should get warranty service. But there are always exceptions.
whose_ni said:
Any proper guide to be done before send to repair?.. i've just sent my phone to service today. Battery temperature warning problem. Re-flash stock rom with stock kernel. Everything goes back like factory settings
Click to expand...
Click to collapse
MistahBungle said:
Just the usual steps I.E. flash stock firmware, do a wipe/factory reset, use jig to reset the flash counter, double check that the reset worked & there are no traces of old apps on the phone which required root that could tip off whomever fixes the phone that you'd rooted it. Some say you should first (while the phone is still rooted) go into CWRecovery and format cache, data, system, & sd card. Then flash stock firmware and then use the jig. Depends on how paranoid you are I guess.
As I said to the previous poster, there are no guarantees of warranty service after you root or flash non-stock firmware on your phone (you shouldn't expect same), however if you follow these steps you should get warranty service. But there are always exceptions.
Click to expand...
Click to collapse
Lucky for me. My phone just back from service and they replace broken parts. ..i didn't jig to reset the counter..
Yep. You were lucky.
whose_ni said:
Lucky for me. My phone just back from service and they replace broken parts. ..i didn't jig to reset the counter..
Click to expand...
Click to collapse
I managed to break the Wifi on my tablet. I had root, accidentally replaced a file I shouldn't have, thought that wiping and flashing the .21 update would work...it didn't. It wouldn't flash because a system file had been modified.
Because I broke the wifi, I can't unlock. I basically am stuck waiting for .21 to be rooted.
Devs, are we close to root? I'm sure you're working on it and I applaud your efforts. Is this firmware super closed off? I'm not asking for an ETA, but maybe more of a status update. Just let me know there is hope
EDIT: I fixed it! I was able to pull an .apk of OTA Voodoo Rootkeep from a previous Titanium Backup file. I installed the app, and it restored root for me! Its possible that I was already still rooted, but without the ability to d/l apps I couldn't do anything about it. Anyway, I'm back with a rooted .21!
I think I had a similar issue....was using wifi tethered to phone...with modded wpa files....Couldn't OTA for .21......no computer/no router to get a wifi connection.
Went to Mickey D's for a free wifi connection....downloaded and installed .15 (for orig files) via SD card.
After that was finished, used OTA to download .21 ...if there are still issues, download it and manually install it via SD card.
Here's instructions to do it via SD card:
http://service.asus.com/TF201_fwupdate
Yeah I had to do that method when I first updated to .21. But then, after .21 I couldn't tether even though the chanelog said ad hoc wifi was supported. So I tried that method again, and broke it. Now I have no root and no wifi.
Waiting for someone to find root for .21 is killing me. lol
Any Devs want to chime in and give us an update on the .21 root process?
http://transformerprimeroot.com/tra...orkmod-recovery-5-8-2-0-on-transformer-prime/
use this. windows didnt work for me, drivers were messed up.
i used the mac method with no drivers required. (same with linux) and it worked flawlessly. pushed CWM using this, then flashed primeval .21 firmware.
stock .21 but with root.
requires unlock
Thanks, but I can't even unlock due to no data connection
I wonder if I could do it with an USB Ethernet dongle?
We definately need some tool to recover from such positions... NVflash or anything. This way its just too risky to temper with files if you're not unlocked imho. I remember about 3-4 cases where people got issues because of trying to improve stuff by editing files like build.prop etc.
Gogo devs, Asus, nVidia... Anyone, give us some tools to be safe
Definitely. I purchased a square trade warranty so that when I unlock I am still covered. However, why should I have to?
I sincerely hope a dev can get us root one .21 at least, and maybe some kind of unlock tool that doesn't report to Asus. And of course, NVFlash
the unlock is just an APK from asus? cant download that and put on SD?
malaeus said:
the unlock is just an APK from asus? cant download that and put on SD?
Click to expand...
Click to collapse
Its simple enough to install, but the app requires a connection with Asus' servers to record the Prime's serial number and then distribute a unique unlock key.
McLiarpants said:
Its simple enough to install, but the app requires a connection with Asus' servers to record the Prime's serial number and then distribute a unique unlock key.
Click to expand...
Click to collapse
Ah was not aware of such communication. Sorry :-(
Have you tried going online with a usb ethernet dongle?
I was going to look into this option, but I was able to fix my wifi!
I pulled Titanium Backup .apk files of my old apps and installed voodoo rootkeeper. it restored root (its possible I never actually lost root, just the ability to d/l apps like root explorer because of broken wifi)! I then loaded my backup of root explorer and copied the correct wpa_supplicant file.
I then immediately unlocked and flashed Virtuous Prime .21. I purchased a square trade warranty with accidental damage protection in case I have any problems with it.
It would be nice to know if I could do that for my unrooted Prime I accidentally upgraded to .21 before rooting. My other Prime is on .21 with root.
I'm sure it is because you had root before, but maybe it's worth a try.
McLiarpants said:
I purchased a square trade warranty with accidental damage protection in case I have any problems with it.
Click to expand...
Click to collapse
Has anyone confirmed that squaretrade considers unlocking and intentionally voiding your warranty "normal use"? I too am getting disheartened waitig for .21 root method. I would love to install custom rom and never have to worry about it again if squaretrade will cover a bricked device. However, I'm afraid if I void my warranty ASUS might decide not to honor the device with warranty issues such as gps dongles, etc.
casey225 said:
Has anyone confirmed that squaretrade considers unlocking and intentionally voiding your warranty "normal use"? I too am getting disheartened waitig for .21 root method. I would love to install custom rom and never have to worry about it again if squaretrade will cover a bricked device. However, I'm afraid if I void my warranty ASUS might decide not to honor the device with warranty issues such as gps dongles, etc.
Click to expand...
Click to collapse
What I've heard from other people is that the warranty says that they don't support intentional hardware or software modifications that would also void the manufacturer's warranty. Such as unlocking or opening the unit. However, if you have the accidental warranty and you drop it after being unlocked, they will fix it or replace it.
So if you have a problem with it after unlocking, it may need an "accident" to happen before you send it into ST.
clouds5 said:
We definately need some tool to recover from such positions... NVflash or anything. This way its just too risky to temper with files if you're not unlocked imho. I remember about 3-4 cases where people got issues because of trying to improve stuff by editing files like build.prop etc.
Gogo devs, Asus, nVidia... Anyone, give us some tools to be safe
Click to expand...
Click to collapse
there is a method to recover from this, grab the full update not the patch one from asus website, put it on a microsd card, and boot recovery
McLiarpants said:
So if you have a problem with it after unlocking, it may need an "accident" to happen before you send it into ST.
Click to expand...
Click to collapse
Understood I would still have to hope that Squaretrade doesn't determine the true problem, otherwise, would be SOL on all fronts. I will try to wait it out for now, but, I think I hear Virtuous Prime calling my name as I type this message.
casey225 said:
Understood I would still have to hope that Squaretrade doesn't determine the true problem, otherwise, would be SOL on all fronts. I will try to wait it out for now, but, I think I hear Virtuous Prime calling my name as I type this message.
Click to expand...
Click to collapse
I am running VP now, but I really like AOKP. The only reason I'm running VP is because Polaris isn't working on AOKP. I know it has some bugs, but I can't work with the lag between hitting a key and the letter showing on the screen in other office apps. I also haven't been willing to pay $15-$30 for an app to see how laggy it is.
lilstevie said:
there is a method to recover from this, grab the full update not the patch one from asus website, put it on a microsd card, and boot recovery
Click to expand...
Click to collapse
The update wont install if any of the system files are modified. It would be nice if it did, but it doesn't, unfortunately.
TB Pro restore with rooted .21 (NOT UNLOCKED)
So I had a thought and I am not sure that this will work. I have a TF101 that was rooted on 9.4.2.17 then upgraded to 9.4.2.21 (without any rootkeeper installed). Still have root but decided to install Voodoo RootKeeper just in case.
I have TB Pro installed and the Dev claims that you can restore to dissimilar hardware. My thought is to restore the APP+DATA+SYSTEM backup to my TF201 that is currently running 9.4.2.21 without root.
Any thoughts on this idea?
Niles
HI,
I used the search but could not find anything about this topic also I'm pretty sure there has to be someone who posted about this before.
I have some battery issue with my gen 8 101 and want to send it in for warranty. I'm pretty sure this has nothing to do with urukDroid which I'm using since I got the tablet a year ago. Anyway... I want to ask if there is a How-To for undoing all changes so Archos doesn't claim the warranty to be voided. I'm not sure if there is a way Archos might not recognise that I rooted and installed custom ROM but I'm pretty sure that this would be easier than to argue with them about if the custom ROM destroyed my battery or not...
thx 4 your help
Using:
UrukDroid 1.6 (installed on internal memory)
rooted with SDE from Archos + EasyInstall 1.5 from UrukDroid
http://code.google.com/p/urukdroid/wiki/Installation
If you installed the SDE your device is watermarked and you can't remove that.
But there are no known incidents where Archos has claimed that.
Thanks!
1. Since the Watermark is only in the software I think it shold be possible to remove it. It's not like the HTC unlocker where you have to give them your phones hardware id
2. As it is most likely to be very hard to remove the watermark I'll try and just flash stock ROM. I hope you're right and I won't be the first 'incident'.
No, it's not in software, they write it to an internal hardware component.
I'm pretty sure was long as you didn't brick it with SDE, Archos will accept it. I know someone here got the digitizer replaced and they used SDE.
Installing the SDE modifies something in the bootloader and the DRM keys are wiped (they probably do this to avoid key extraction and cloning via custom FW).
But, like they said, no one with a hardware issue came back telling they got their warranty service denied due to SDE installation.
Probably more a Cover Y A thing to avoid warranty replacement of bricked units.
There are no DRM Keys in the Gen8.
You might be talking aout Gen7
Thx again. But I now just have to ask: Do you recommend to wipe and install stock Rom? Or is it okay if I just leave UrukDroid installed? I can't find my Nandroid backup at the moment so it basically I wanted to:
1.enter recovery mode.
2.Try to follow this path and reformat my device.
3. Then do a fresh install of the firmware.
Is this the right way?
Sorry to ask those lame questions but I don't have much time at the moment for trying
As there is no nandroid, you can't have a backup, so yes that's the way to go.
Alright Archos send me a Mail today that they replace it and a new 101 G8 is on the way to me.
clickboombang said:
Alright Archos send me a Mail today that they replace it and a new 101 G8 is on the way to me.
Click to expand...
Click to collapse
That's great news for all of us and a clever move from Archos.
Sent from my LT18i using Tapatalk 2
chandoliasnikos said:
That's great news for all of us and a clever move from Archos.
Sent from my LT18i using Tapatalk 2
Click to expand...
Click to collapse
That's just what I was thinking
Hi,
i have a Thor LTE, rooted with TWRP and with a damaged SIM-Slot (i guess). No SIM-Card works. I reverted to stock rom (13.3.2.3.2) via TWRP Backup (yes, wlan switched off), and even the stock rom says "invalid sim".
So i guess, i'll file a warranty request.
my Questions:
how to remove twrp?
how to unroot?
unroot would be easy, just chosing "uninstall" un SuperSU. But how to remove TWRP?
sn123py said:
Hi,
i have a Thor LTE, rooted with TWRP and with a damaged SIM-Slot (i guess). No SIM-Card works. I reverted to stock rom (13.3.2.3.2) via TWRP Backup (yes, wlan switched off), and even the stock rom says "invalid sim".
So i guess, i'll file a warranty request.
my Questions:
how to remove twrp?
how to unroot?
unroot would be easy, just chosing "uninstall" un SuperSU. But how to remove TWRP?
Click to expand...
Click to collapse
Replacing twrp with a stand-alone stock recovery is risky; you might end up with an unbootable device which could impact your warranty claim. Upgrading with a standard Amazon .bin generally yields a non-functioning recovery which can usually be rectified by subsequently rerooting and using adb or flashify to flash a stock recovery. Lots of work and some risk. Check your device for a backup of the original recovery which I believe twrp creates when initially flashed. If found you could use adb/flashify to reapply which would be safer than using someone else's recovery which is probably from a WiFi only device.
Amazon typically issues a refurb for most warranty claims. Questionable if they even check the device coming back; there are many reports of rooted/bricked devices being replaced under warranty. Something to keep in mind if the other alternatives prove unattractive.
Davey126 said:
Replacing twrp with a stand-alone stock recovery is risky; you might end up with an unbootable device which could impact your warranty claim. Upgrading with a standard Amazon .bin generally yields a non-functioning recovery which can usually be rectified by subsequently rerooting and using adb or flashify to flash a stock recovery. Lots of work and some risk. Check your device for a backup of the original recovery which I believe twrp creates when initially flashed. If found you could use adb/flashify to reapply which would be safer than using someone else's recovery which is probably from a WiFi only device.
Amazon typically issues a refurb for most warranty claims. Questionable if they even check the device coming back; there are many reports of rooted/bricked devices being replaced under warranty. Something to keep in mind if the other alternatives prove unattractive.
Click to expand...
Click to collapse
Hey Davey126, thanks for the quick answer. Any Idea, where to find the pre-twrp-recovery-backup? If not, i'll simply keep the stock 13.3.2.3.2, keep twrp and remove root.
thanks again,
macfly.
sn123py said:
Hey Davey126, thanks for the quick answer. Any Idea, where to find the pre-twrp-recovery-backup? If not, i'll simply keep the stock 13.3.2.3.2, keep twrp and remove root.
thanks again,
macfly.
Click to expand...
Click to collapse
I renamed mine awhile back and do not recall the original. If present it will be located in the root of 'sdcard' in an appropriately named folder (eg: recovery.bak). Size should be around 8.5 MB.
Davey126 said:
I renamed mine awhile back and do not recall the original. If present it will be located in the root of 'sdcard' in an appropriately named folder (eg: recovery.bak). Size should be around 8.5 MB.
Click to expand...
Click to collapse
Thanks, did not found it. maybe i deleted it. So i simply factory-reset, wipe data and storage.
thanks for answers!
Hi,
just wanted to let you know, my replacement-kindle arrived, was on 13.3.1.0.
i unlocked Bootloader with cuber, root with towelroot, installed twrp and i'm back in business with cm11
thanks for your help sofar!