Hi all, I bought a new TF700 two days ago. I proceeded to successfully unlock, root, flash Cromi-x. After some teething problems got it working beautifully. Unfortunately my girlfriend noticed what looks like a big smear of some type of adhesive inside the glass. Kind of looks like something has wiped the back of glass or the panel itself, and has dried but with residue. Anyway its only visible when the screen is off or on a black background but I contacted Asus anyway and they immediately advised me to get it replaced at place of purchase.
I realise they don't normally allow this but they've given me the Return Authorisation number and the store has shipped the replacement device to my nearest store for collection. SO, do I just go ahead and swap it or do you think it will come back to bite me later on? Even if they do come back later and say they found it was unlocked, Ill have already unlocked + flashed the replacement so I figure whats the worst that can happen?
It seems the rumored 'database update' back to Asus when unlocking isnt accurate as I got through no problems and they checked serial number etc.
Any thoughts?
Great Minds Think Alike!
rogannzb said:
Hi all, I bought a new TF700 two days ago. I proceeded to successfully unlock, root, flash Cromi-x. After some teething problems got it working beautifully. Unfortunately my girlfriend noticed what looks like a big smear of some type of adhesive inside the glass. Kind of looks like something has wiped the back of glass or the panel itself, and has dried but with residue. Anyway its only visible when the screen is off or on a black background but I contacted Asus anyway and they immediately advised me to get it replaced at place of purchase.
I realise they don't normally allow this but they've given me the Return Authorisation number and the store has shipped the replacement device to my nearest store for collection. SO, do I just go ahead and swap it or do you think it will come back to bite me later on? Even if they do come back later and say they found it was unlocked, Ill have already unlocked + flashed the replacement so I figure whats the worst that can happen?
It seems the rumored 'database update' back to Asus when unlocking isnt accurate as I got through no problems and they checked serial number etc.
Any thoughts?
Click to expand...
Click to collapse
A fellow immediate modder...I like it
For me, you've already answered your own question. Once you've got your new tablet, what do you care? Even if they do notice that your original tablet was rooted, what are they going to do, force you to give the new one back....threaten to sue you if you don't? Not likely. You've got to remember that it's all about money for these guys, so once you've got your new tablet, even if they do spot your rooted original, it's going to cost them more to try to get the new one back from you than it would for them to just repair & re-sell the original.
I think that once you've got your new one, start enjoying it
Ok so Im taking it back tomorrow for replacement. But before I do...
For my reference can anyone explain to me how to flash this back to the stock Rom? I downloaded from Asus website, rebooted into TWRP and tried to install the stock software, which failed.
Also I'd like to know if I should be 'removing TWRP somehow? I know I cant reverse the unlock process but can I revert everything else back to factory configuration?
When one reboots via power and holding volume down, you get the menu with RCK, Android and Wipe Data - what are the definitions of RCK and Android? From what I gather one boots recovery and the other the installed ROM?
Finally - when one does a Restart from within Cromi and there are options for Bootloader and Recovery - what is the difference between these two options? Do they achieve the same things as the point above (ie reboot to recovery versus the installed rom?)
Thanks, sorry for the noob questions.
Unzip the zip from Asus first and you will see an update zip inside. Flash this from twrp and it will reset you back to stock.
rogannzb said:
Ok so Im taking it back tomorrow for replacement. But before I do...
For my reference can anyone explain to me how to flash this back to the stock Rom? I downloaded from Asus website, rebooted into TWRP and tried to install the stock software, which failed.
Also I'd like to know if I should be 'removing TWRP somehow? I know I cant reverse the unlock process but can I revert everything else back to factory configuration?
When one reboots via power and holding volume down, you get the menu with RCK, Android and Wipe Data - what are the definitions of RCK and Android? From what I gather one boots recovery and the other the installed ROM?
Finally - when one does a Restart from within Cromi and there are options for Bootloader and Recovery - what is the difference between these two options? Do they achieve the same things as the point above (ie reboot to recovery versus the installed rom?)
Thanks, sorry for the noob questions.
Click to expand...
Click to collapse
If you flash the stock firmware it will replace TWRP with the stock recovery.
If you bot with Power + Volume down you boot into the bootloader menu. Your correct on RCK and Android.
It is not recommended to use Wipe Data fro the bootloader if you have a custom recovery installed, btw. If you want to wipe do it fro TWRP.
The Restart options are just a more convenient way to boot into the bootloader or recovery .
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Thanks to you both for the replies.
@ sbdags - Its funny I actually noticed the zip within the zip and after it failed the first time removed the zip out on its own. I astill got the same error message. To be clear, I was using the install option from within TWRP and selecting this file on my external sd card. Im re-downloading it now to test this again.
rogannzb said:
Thanks to you both for the replies.
@ sbdags - Its funny I actually noticed the zip within the zip and after it failed the first time removed the zip out on its own. I astill got the same error message. To be clear, I was using the install option from within TWRP and selecting this file on my external sd card. Im re-downloading it now to test this again.
Click to expand...
Click to collapse
I've done it lots of times and it works fine for me.
Related
I have had my TF for a week or so, and have had no issues whatsover. I have am rooted, running a custom kernel.
All of the sudden I am having the TF reboot at random places, and now it is freezing even in CWM recovery. I wiped everything and went back to stock and still having the problem (on 3.1). Anyone else with this issue, and does it sound like hardware at this point? I think I may return it today, but I am nervous since the screen on this one is perfect.. don't want to get one with light bleed like my last.
Thanks guys.
yes. A quick search will show you the multitudes of threads regarding this issue.
skydirt said:
yes. A quick search will show you the multitudes of threads regarding this issue.
Click to expand...
Click to collapse
Yeah.. I get that.. I have been on XDA for 4 years.
I understand the freezes and reboots happen and are happening and other people are having them happen, however per my subject line I was looking for people who are having it happen while they are in their recovery mode. I have had the tab freeze after booting into recovery, as well as during a restore and backup. I wasn't having any issues for an entire week and without any kernal or rom mods this just started. (SPECIFICALLY IN RECOVERY MODE AS WELL AS NORMAL MODE)
If it freezes + reboots in recovery, see if a Ramdump file is placed in the root of your /sdcard/ folder. If so, paste it up here so we can look at it.
sassafras
sassafras_ said:
If it freezes + reboots in recovery, see if a Ramdump file is placed in the root of your /sdcard/ folder. If so, paste it up here so we can look at it.
sassafras
Click to expand...
Click to collapse
I actually have a bunch of those files. I attached them here. Oddly, today I am trying to dup the issue after the tablet has sat on but unused, it is working fine. I went into CWM, moved around the menus and waited for it to freeze but it didn't. I restored my backup and am currently testing different things to repeat the freezes. I know there was an issue so if possible I would love to be able to find out what it was/is, and make sure it will or won't happen again so I can get a replacement if needed while I can.
I post if I have the issue again..
EDIT: yup rebooted 3 times again after barely using the tablet. Also completely locked up on one boot before I even put in my pass pattern.
I then went into recovery mode, moved around the menu system and it froze again in CWM.
superevilllama said:
I actually have a bunch of those files. I attached them here. Oddly, today I am trying to dup the issue after the tablet has sat on but unused, it is working fine. I went into CWM, moved around the menus and waited for it to freeze but it didn't. I restored my backup and am currently testing different things to repeat the freezes. I know there was an issue so if possible I would love to be able to find out what it was/is, and make sure it will or won't happen again so I can get a replacement if needed while I can.
I post if I have the issue again..
EDIT: yup rebooted 3 times again after barely using the tablet. Also completely locked up on one boot before I even put in my pass pattern.
I then went into recovery mode, moved around the menu system and it froze again in CWM.
Click to expand...
Click to collapse
Hey there superevilllama, glad to see you back on XDA. Question, are you running custom firmware, ie. custom kernel, ROM, etc? If so, I would suggest downloading the stock firmware from ASUS and flashing back completely to stock and see if that alleviates any issues. If this continues to happen on a completely stock system, you might have faulty hardware.
It was the kernel...
Alright guys.. It was the kernel. I wiped and reset to stock, thinking I had already went back to stock kernel but apparently flashed the same kernel instead of stock.
I checked Clemsyn's kernel thread and # 17 of his had other people getting lockups and reboots too, OC or not. Gave me a scare because I did a bunch of things at one time.. updated kernel, got a new keyboard dock, updated setcpu.
I kept freezing all over the place and rebooting, OC or not. Thought I restored back to stock kernel but I didn't. Thought it was wierd as I had no issues before. Back to 16 of Clemsyn's kernel and all is well, both when not overclocked and OC to 1.5ghz.
I appreciate your help guys. Glad to know my TF is still in good shape. Good thing because the replacement I got had bbaaadd light leakage. Now I can just take it back.
Yes, it was the kernel.
More importantly, it looks like it was the clock speed.
sassafras
It is wierd that it froze in recovery mode tho. I thought recovery had its own kernel, I didn't think it used whatever kernel I had flashed. Eh either way I am glad it is working.
Hi folks, it seems that I may use some help right now. Searched around, but so far no luck is found. My rooted TF700 runs with the latest firmware and not unlocked (stock). Today she went nowhere but showing the ASUS logo and circling dots.
First, as usual, I tried to have a cold boot. Still, she didn't go further. Then I decided to wait patiently, and I think one hour is a reason to try helping her out of there. Next step, as some of you may already had in mind: RCK. Picked it up, the green robot showed up, but only few seconds before it went to sleep accompanied by that... yes, that red triangle.
Not so long afterwards, I downloaded the firmware ZIP file from ASUS's website. Extracted it once, renamed it the "usual" way, put the file at a MicroSD root and got the TF700 installing it. Installation was complete, the robot wasn't shown sleeping, and then it rebooted. At this moment I took the MicroSD from the slot so it doesn't interrupt the process.
But then what? Still the same old eight dots making the runabout form under ASUS logo. Tried cold boot once again, no luck. Then, I borrowed my children's A100 to type this help request.
I have no idea what to do. Still have the warranty valid but I want to try another thing before sending it out. It might be due to the new firmware (25 I think, I'm not memorizing firmware numbers) but it seems that I'm the only one suffering it so far. The last thing I remembered was the TF700 went sudden reboot when I click the bluetooth icon to activate it, while I'm trying to connect to a portable speaker.
I never flash any custom ROMs, it has been always the stock. Random reboots, yes, I think I'm not the only one. But now I'm getting suspicious since this happens one day after the last firmware update. The looping at boot screen.
In case anyone has suggestions or thoughts, please kindly share that here. Thanks in advance.
Sent from my A100 using XDA Premium HD app
Maybe your data partition is corrupted. Did you try "wipe data" in the bootloader menu?
_that said:
Maybe your data partition is corrupted. Did you try "wipe data" in the bootloader menu?
Click to expand...
Click to collapse
Hi, thanks. Doesn't install a fresh firmware do further? I mean, it also removes the data, right? Or am I wrong here?
Sent from my A100 using XDA Premium HD app
suroboyo said:
Hi, thanks. Doesn't install a fresh firmware do further? I mean, it also removes the data, right? Or am I wrong here?
Click to expand...
Click to collapse
"Wipe data" deletes your data, right. I never did it myself, so I can't say what exactly will be deleted. Installing a firmware only replaces the firmware, not your data.
Alternatively you can try if you can connect via adb shell while the boot screen dots are spinning.
_that said:
"Wipe data" deletes your data, right. I never did it myself, so I can't say what exactly will be deleted. Installing a firmware only replaces the firmware, not your data.
Alternatively you can try if you can connect via adb shell while the boot screen dots are spinning.
Click to expand...
Click to collapse
Wipe data is factory reset. If you reset your device from setting-> factory reset, it will boot into "wipe data" mode and wipe all your apps, bring everything back to factory default. At this point if you don't have a backup, I see you only have one option which is wipe data.
OK guys, thanks a lot. If you read my footer now, you know I already have access to my TF700.
I did it as you suggested, chose "Wipe Data" after several times failing with firmware recovery. Losing data in SD is not a very big deal since I always keep my "real data" in an external MicroSD, anticipating such things exactly like I just "suffered". I also backed up my most of apps and their data to the MicroSD using Titanium Backup, so it's very close to the previous state... only snappier.
So I wiped the data and got into the stock of everything, without root. Then I rolled back to ICS firmware (30), rooted it using Debugfs, installed OTA Rootkeeper, protected a copy of the root access, updated the firmware, restored root, installed TB, restore all apps and data. Then it's the matter of replacing some widgets and little "here-and-there" settings. No more than two hours overall, could be way less if the number of apps are smaller.
What was really missing is just a few downloads and some "not really important" winter photos. Movies and maps kept in the internal storage, well, I have the backup. I wouldn't say this was caused by the new firmware, but somehow I feel like I should have a suspicion at it.
Thanks again!
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
I had previously rooted, unlocked and put a custom bootloader on my S3. I was enjoying Beans 10, but wanted to try Slimbeans. I got the initial .zip of Slimbeans installed, but the AIO .zip kept failing, so I had a useless device. Interestingly, I could not boot to recovery. My computer wasn't recognizing my stock Verizon ROMs. I was able to eventually download root66 and Odin that onto my phone, but when it starts up, it gets stuck at the Verizon 4G/LTE screen and never gets passed it. I have pulled the battery and turned the phone on several times, but get the same result. I thought I'd try another Odin attempt, but when I hold down the vol. down/power/home keys and then select the vol. up, I very briefly see the android guy and then then phone reboots. Please help, I'm stuck!
Well, I downloaded a different stock ROM and got that installed. In the meantime, I had to use my iPhone 4 as a backup. When I contacted Verizon to switch me back to the S3, it shows me as roaming. The tech was no help. Anyone with an idea?
Check network settings. Make sure you are on SIM and not NV
Sent from my SCH-I535 using Tapatalk 2
Thanks for the reply. GrainOSand, I had missed this.
I got the stock ROM flashed and thought I was good. The tech's were no help, but told me I needed a new SIM card. I went to my local Verizon store, got the card, the guy there tried to get my S3 going again, but couldn't.
Now, it acts like it is in a loop. It starts the Startup Wizard and very soon I just get the circle spinning and it tries to call the network. I Odin'd the ROM again with the same effect. I have a new phone that is supposed to be here tomorrow, but my Flash counter is at 1. Anyone know how I can get this thing working enough to use Triangle Away?
So, am I asking retarded questions, or is there really no answer?
At the wizard, try tapping all four corners clockwise, starting at the upper left to bypass the activation screen.
lvgdgts said:
Thanks for the reply. GrainOSand, I had missed this.
I got the stock ROM flashed and thought I was good. The tech's were no help, but told me I needed a new SIM card. I went to my local Verizon store, got the card, the guy there tried to get my S3 going again, but couldn't.
Now, it acts like it is in a loop. It starts the Startup Wizard and very soon I just get the circle spinning and it tries to call the network. I Odin'd the ROM again with the same effect. I have a new phone that is supposed to be here tomorrow, but my Flash counter is at 1. Anyone know how I can get this thing working enough to use Triangle Away?
Click to expand...
Click to collapse
You need to root the phone then install and run triangle away to get rid of the flash count http://forum.xda-developers.com/showthread.php?t=1494114 then odin back to stock
Also Im pretty sure you can simply odin to either the F2 or G1 ICS builds then type this in the dialer to fix the roaming issue as long as your imei is still intact.... *2767*3855#
No need to have the phone replaced, easily fixable
Roninrc51 said:
At the wizard, try tapping all four corners clockwise, starting at the upper left to bypass the activation screen.
Click to expand...
Click to collapse
That sounded interesting, but didn't work.
x714x said:
You need to root the phone then install and run triangle away to get rid of the flash count http://forum.xda-developers.com/showthread.php?t=1494114 then odin back to stock
Also Im pretty sure you can simply odin to either the F2 or G1 ICS builds then type this in the dialer to fix the roaming issue as long as your imei is still intact.... *2767*3855#
No need to have the phone replaced, easily fixable
Click to expand...
Click to collapse
I'll give this a go at home tonight.
Hi Everyone, I was wondering if I could get a little help -
I've had my S3 for a little over a month, rooted, stock kernel, cm 10.1. The other day the display suddenly went haywire, shifted green, and is now completely fubar (all black except for a little flickering strip up at the top).
Verizon sent me a replacement and I have to send the old one back, but I need to find a way to reset the flash counter and flash un-rooted stock rom before doing so...without a working screen.
The phone seems to work fine (pc recognizes it as well), I just can't see the damn thing and so can't install Traingle Away or any other apps that would help me.
Could anyone help me figure out a way to clear the flash counter and restore this thing to stock so I can send it back? I have 5 days and am getting kinda desperate...thank you in advance!
UPDATE: Lucky me, the screen turned on again after a day without functioning. It was green and had extremely low resolution, but it was enough to see what I was doing to unroot/return to stock. I wonder if this problem could have been caused by CM 10.1? I'm asking because touchwiz is the ugliest, clunkiest interface since the abacus and I want to root/flash the new phone right away...but I'm not sure if the gpu instability (I'm guessing that's what it was) was related to me flashing a custom rom and new firmware...any thoughts?
...Could I take the motherboard out of the broken phone, put it into the replacement, perform the necessary steps to return it to factory stock, and then put the motherboard back? I hope there's a less intimidating option...
id be shocked if they investigated it further after the device screen wont turn on as you describe.
especially if its not just ablack screen and it still sorta functions.
ddurandSGS3 said:
id be shocked if they investigated it further after the device screen wont turn on as you describe.
especially if its not just ablack screen and it still sorta functions.
Click to expand...
Click to collapse
But won't it become an issue when they replace whatever's defective with the screen/gpu and see that it boots to CM when they try to refurbish it?
If your computer recognizes it and your phone is indeed functional. Try to get into download mode on your phone and flash a stock unrooted image. That should do the trick!
Sent from my Galaxy S3
TheKucho said:
If your computer recognizes it and your phone is indeed functional. Try to get into download mode on your phone and flash a stock unrooted image. That should do the trick!
Sent from my Galaxy S3
Click to expand...
Click to collapse
Can I do that through ODIN? I've always used clockwork for flashing roms, and I can't see the screen even in recovery. Also, would that reset the flash count?
Still kind of a noob at this, so sorry if any of the questions seem obvious. Thanks again for all your feedback
Exactly what thekucho said.
I had this exact problem, my screen took a crap while I was rooted and I needed to get back to stock before I sent it back. I was able to get it into download mode and Odin back to stock. I didn't even bother with resetting the flash counter and I haven't heard anything about it.
Boot into download mode (vol down + home + power), Odin back to stock, and you're good!
Sent from my SCH-I535 using Tapatalk 4 Beta
I just threw mine in a microwave for 4 seconds... :silly:
Hey all, before I start I'd like to apologise for making the post here but I don't know what you guys would classify the state of my phone as, "bricked, soft-bricked, hard-bricked", I have no clue! As a result I have no idea what threads to start looking in so I've come here to make this, sorry again!
I'm here looking for help because I think I've completely destroyed my Moto G and really really would like to fix it.
Basically, I had been running an old version of CyanogenMod for months and was not able to update due to the fact my bootloader was not updated. After finally updating it through a tool on XDA, I installed the newest version of CyanogenMod onto the phone and it was all going well, except for the fact all of my Google apps were crashing and making it impossible to use.
Now, I'm not sure why, but without taking any precautionary measures or looking into it at all or what I needed to do, I then decided to try and flash a Paranoid Android rom onto the phone, which installed fine. I load the phone up and something comes up with a passcode saying I need to unlock it to use the phone. I put in some random things and eventually get it, but it says my data is corrupted and therefore I need to reset to factory settings and there's a button there to do it. I think "why not" and click.
So now, the phone did something weird and basically went into a bootloop of the PA logo, so I restarted the phone and went to the bootloader thing. When doing "Normal Startup" it loads the phone with the PA logo like before, comes up with a brief "Android is Upgrading" screen before showing me the passcode screen for half a second, before repeating this, thus having a bootloop. Every so often, I can put my code in and press the reset button again, but it does the same thing.
On the other hand, if I try to access my ClockworkMod recovery system, the screen repeatedly flashes with the CWM background of the Android Alien guy, as if to say it keeps trying to start but it cannot.
TLDR: I cannot access my phone through a normal powerup or through my recovery, have I screwed it completely?
I'd hugely appreciate any help here guys because I'm stressing like I never have before here, thanks!
EDIT: it is the X0123 version!
Spaciouz said:
TLDR: I cannot access my phone through a normal powerup or through my recovery, have I screwed it completely?
I'd hugely appreciate any help here guys because I'm stressing like I never have before here, thanks!
EDIT: it is the X0123 version!
Click to expand...
Click to collapse
Just a few questions before I start suggesting a full flash to stock.
Did you have any SIM passwords, boot passwords, CWM passwords before flashing?
Also In CWM does it flash before any options are selected and did you dirty flash the new ROM over the old ROM?
Anyway, your phone is not hardbricked as it can get to recovery so thats good news.
I would suggest flashing your phone back to factory stock using the tools here on XDA (http://forum.xda-developers.com/showthread.php?t=2542219). That should hopefully resolve most of the issues and then if you feel like it you can start flashing custom ROMs again.