restoring it to stock fabric way - Asus Eee Pad Transformer Prime

so i finally got my prime back on track beacuse of the boot loop CWM 5.2.0.4 if not mistaking but for some reason is still flicking youtube n some other stuff and i restore it with jermaine 9.4.2.15.zip (STOCK ROM UPDATED)..is there a way i can take CWM out and the rest of the things back like normal i am planning to send it back to ASUS to see what they are going to say or eather a new one or fix it ? any help or advice here thnx

At this point in time there is NO way to relock bootloader.
they will know and it will considered outside its warranty regardless of whether something you did (software wise) caused the problem (ie even if it is caused by faulty hardware, main reason im still using stock just rooted).

shreddintyres said:
At this point in time there is NO way to relock bootloader.
they will know and it will considered outside its warranty regardless of whether something you did (software wise) caused the problem (ie even if it is caused by faulty hardware, main reason im still using stock just rooted).
Click to expand...
Click to collapse
damn so this meanz i really busted now that flicking thing get me tired seeing it i changed ROM does the same now i dont know what to do i love tf201 but i really wanted to have it fresh

Related

Is it possible to damage phones with custom roms ?

The Reason i ask is either it is or i am the unluckiest person ever with a S2 lol
So far got the phone at xmas wasn't happy with the screen colours sent it off they said the main chip was faulty and had been replaced and a software upgrade etc...
Got it back and flashed a custom rom, well a few and noticed that i then had an issue where if someone called i had to put loudspeaker on in order to hear the other person...
Put phone back to stock and sent it off again...
Phone came back last week picked up monday used for a day all seemed fine, flashed a custom rom got another problem with the phone this time i have to put the loudspeaker on to hear other people they can hear me fine...
So its back to stock and back to vodafone tomorrow...
So can custom roms/kernels cause physical issue's with phones, never had an issue with my HTC Desire HD but i'm beginning to wonder if i should leave my next S2 stock, or have i just been unlucky ???
Would also add when going back to stock the screen colours seem much better than custom roms but the sounds issue's remain...
One word NO!
What rom are you flashing?
Checkrom, wickedrom, illusion Xt, not sure which if any has caused any issues could be I'm just unlucky
Definatly noticed issues with screen colours too which now in I'm back on stock have been sorted
Its all a bit weird
Sent from my GT-I9100 using xda premium
wakers said:
Checkrom, wickedrom, illusion Xt, not sure which if any has caused any issues could be I'm just unlucky
Definatly noticed issues with screen colours too which now in I'm back on stock have been sorted
Its all a bit weird
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Trust me if that was the case damaging my phone by flashing a rom then my phone would of been damaged goods by the first month i had it
Anyway just be careful how you flash a rom and it is always advised to do a full wipe before installing one
Um, actually, yes.
You run the (slight) risk of bricking your phone every single time you flash something to it. If you're the type of person who's paranoid about these things & can't handle the idea of possibly not getting warranty service if things go wrong, you shouldn't be messing with your phone in the first place.
Anyone who has an expectation (as opposed to a "hope") of warranty service after they stuff around with the phone is an idiot.
The SG2 is a hard phone to brick. Follow the general guidelines and you should be fine. I can't imagine flashing a rom can break this phone. Worst that can happen is you brick it. Either it works or it doesn't.
Yeah Im fully aware that you risk bricking the phone
I've been flashing roms to HTC,s for years always trouble free
I always read and full wipe between flashes
Sounds like I've been unlucky then 3rd time phone is going back and since Xmas 1day without a fault not a great introduction to Samsung for me...
Sent from my GT-I9100 using xda premium
In all my time reading SGS1 and 2 the only ones who have bricked their phone are the idiots (1) who refuse to read instructions . Even then 90% of them have been able to recover .
the SGS2 quota of 1 is getting higher day by day for some reason .
jje
Yeah 3 physical faults though in a month which is what got me thinking maybe installing the custom roms is causing an issue, but if others are installing with no issue's i've obviously just been unlucky
Hopefully this time i get it back its sorted...
wakers said:
Yeah 3 physical faults though in a month which is what got me thinking maybe installing the custom roms is causing an issue, but if others are installing with no issue's i've obviously just been unlucky
Hopefully this time i get it back its sorted...
Click to expand...
Click to collapse
~Don't accept a repair... DEMAND A NEW PHONE
Samsung doesnt change phones, only repairs.
GeorgeCm said:
Samsung doesnt change phones, only repairs.
Click to expand...
Click to collapse
Who said Samsung??? I meant Vodafone, and they do give new phones
About a stock I don't know, and on aosp try it
http://forum.xda-developers.com/showthread.php?t=1385862
Suarez7 said:
Trust me if that was the case damaging my phone by flashing a rom then my phone would of been damaged goods by the first month i had it
Anyway just be careful how you flash a rom and it is always advised to do a full wipe before installing one
Click to expand...
Click to collapse
Seconded..
It's possible to introduce some new bugs by flashing a custom ROM (that's the price of development, you uncover new weird stuff), but not to physically damage the phone. You'd have to fiddle with the battery or greatly increase the voltages to accomplish that.
If you experience hardware issues after flashing a ROM, it means that the hardware was faulty before, and flashing the ROM just uncovered it and made it obvious to you whereas it was hidden before.
But don't let it get you down. Apparently a lot of SGS2's are faulty when coming out of the factory and need to be replaced.
The first one I had didn't last the night, it 'overcooked' itself when I plugged it to the mains to get it recharged (I knew those phones could get pretty hot but damn ! a 100°C is too much for it, it didn't stand the strain and gave up)..
In fairness they suggested a new phone in Vodafone today so it's gone back with the the request of a new phone rather than repair so we'll see
Also if anyone is interested I obviously flashed a few custom roms and reset the counter to zero and installed original Vodafone software and have had no issues warranty wise
wakers said:
In fairness they suggested a new phone in Vodafone today so it's gone back with the the request of a new phone rather than repair so we'll see
Also if anyone is interested I obviously flashed a few custom roms and reset the counter to zero and installed original Vodafone software and have had no issues warranty wise
Click to expand...
Click to collapse
I seem to have been lucky with a Vodafone SGSII, I'd have insisted on a new phone from it's first problem, Vodafone have always been pretty good at replacing.
I am wondering however how did you manage to reset the flash counter ? Even with a USB Jig mine won't reset. It will go into download mode, but that's it. I presumed my six week old SGSII was a newer one a jig won't work on.
Before trying to reset the counter you should flash the old boot loader (pre-KI1) on, the new one cannot be reset safely with a jig. Works just fine after this
What Snakeforhire said i flashed the old bootloader reset the counter with the USB Jig then reflashed the new bootloader...
Updated through kies and sent back...

[Q] Issue with backlight

Hi all,
I am a proud owner of HTC Amaze, running BulletProof ROM with Faux Kernel v08.
The issue I am experiencing is most probably hardware issue, but I still hope it is not.
My backlight does not work at all. The phone works fine, and under heavy light you can see the actual screen, and can operate the phone as usual, but of course, otherwise, the phone is unusable, since you cannot see anything.
I've tried factory reset, restored to previous backup, charged it till full, left it without battery for few hours, nothing helped. Backlight is simply not there.
Soft buttons have the backlight, but not the screen.
There is a chance that it could be a battery issue (caused by phone), since it is my second battery, original one just died one day and refused to be charged. I got a new battery under warranty.
But even with a new battery it's been acting wierd. Random restarts after which the battery indicator would show red explanation mark. Had to take out the battery and reboot for it to work normal again.
It might be that my phone is defective and just kills batteries.
But in case of the backlight, the battery still charges normally (at least the indicators shows that it does).
Any idea what is going on with my phone? Had anyone experienced something similar? Could it be caused by software? Are there any hard reset options I can try?
And second question, if I will have to go to warranty, is there a way to relock the bootloader? And, I am sure I could find it, but if anyone has it handy, could you link me to a place where I can get the original WIND ROM and original Kernel?
What do you think are my chances of the warranty being granted?
Greg
Porcupine00 said:
Hi all,
I am a proud owner of HTC Amaze, running BulletProof ROM with Faux Kernel v08.
The issue I am experiencing is most probably hardware issue, but I still hope it is not.
My backlight does not work at all. The phone works fine, and under heavy light you can see the actual screen, and can operate the phone as usual, but of course, otherwise, the phone is unusable, since you cannot see anything.
I've tried factory reset, restored to previous backup, charged it till full, left it without battery for few hours, nothing helped. Backlight is simply not there.
Soft buttons have the backlight, but not the screen.
There is a chance that it could be a battery issue (caused by phone), since it is my second battery, original one just died one day and refused to be charged. I got a new battery under warranty.
But even with a new battery it's been acting wierd. Random restarts after which the battery indicator would show read explanation mark. Had to take out the battery and reboot for it to work normal again.
It might be that my phone is defective and just kills batteries.
But in case of the backlight, the battery still charges normally (at least the indicators shows that it does).
Any idea what is going on with my phone? Had anyone experienced something similar? Could it be caused by software? Are there any hard reset options I can try?
And second question, if I will have to go to warranty, is there a way to relock the bootloader? And, I am sure I could find it, but if anyone has it handy, could you link me to a place where I can get the original WIND ROM and original Kernel?
What do you think are my chances of the warranty being granted?
Greg
Click to expand...
Click to collapse
Well i am sorry to say i cant tell you whats wrong, but i can answer one of your questions. Yes, you can relock the bootloader, but it says "relocked". But if it is a hardware problem, being unlocked or relocked shouldnt matter, they should still warranty it for you.. if it is in fact a hardware issue that is..
Sent from my NRGized Amaze...
via xda premium
If you plan on sending in for warranty, there's no harm in using the ruu to go back to stock and seeing if in fact it is something with the software
mrmako777 said:
If you plan on sending in for warranty, there's no harm in using the ruu to go back to stock and seeing if in fact it is something with the software
Click to expand...
Click to collapse
I was just thinking the same thing. but he had mentioned he didnt kno where to get the original wind rom from. But ya, definately go back to stock and see what happens. If ur still having the problem, then i would bet its safe to say that is a problem with the phone not something you did.
As for the shipped Wind Mobile rom, you can find the RUU here:
http://forum.xda-developers.com/showthread.php?t=1335703
Rom||RUU|| Shipped Ruby ROM Collection
There is also a link in that thread to show you how to "relock" you bootloader.
Hope this helps. If you need help or run into any problems when trying to relock and go back to stock rom, just let me know man, ive had to do it on my phone too so ya, Good luck bro!
Sent from my NRGized Amaze...
via xda premium
Thanks all for the reply.
Well, finding WIND RUU wasn't a challenge at all . Thanks for the link anyways.
Never thought I would have to go back to that creature again.
I will give it a try. Also one of my work buddies has the same phone, so I'll swap batteries with him to eliminate another potential issue.
Even though we have the same phones and the same provider, he always jokes around by saying that I have a crappy phone (our old tradition, back from the time we had different phones). Well at last he might be correct
Porcupine00 said:
Thanks all for the reply.
Well, finding WIND RUU wasn't a challenge at all . Thanks for the link anyways.
Never thought I would have to go back to that creature again.
I will give it a try. Also one of my work buddies has the same phone, so I'll swap batteries with him to eliminate another potential issue.
Even though we have the same phones and the same provider, he always jokes around by saying that I have a crappy phone (our old tradition, back from the time we had different phones). Well at last he might be correct
Click to expand...
Click to collapse
Hah i was going to suggest that, but then i thought about it and if ur phone is for some reason frying batteries, then i figured u wouldnt want to try someone elses and then end up having to buy them a new battery lol
Sent from my NRGized Amaze...
via xda premium
aj_2423 said:
Hah i was going to suggest that, but then i thought about it and if ur phone is for some reason frying batteries, then i figured u wouldnt want to try someone elses and then end up having to buy them a new battery lol
Sent from my NRGized Amaze...
via xda premium
Click to expand...
Click to collapse
Well, it's not like it fries it instantaneously, it takes time and effort from my phone to do it
So if I'll insert it for few second to see if my backlight will come back, battery won't die, and I'll I know what's wrong with my phone, and that there is no point of me getting the third battery, since the same fate will be awaiting it.
In any case, if return to stock won't help, warranty is the only option, which is sad

[Q] Samsung Repair Ethics Question

My Galaxy Note (Bell) has a loose micro USB port. It can charge from the wall and is recognized by my pc however I need to prop it up on a slant in order for it to maintain pressure on the cable input, otherwise it will disconnect. It was caused by my dog knocking it off an end table while charging. It's a pain and Samsung has sent me a UPS slip to send it away.
The phone is rooted and this is my first experience with an Android. I've had a good time loading Da_G's kernel, figuring out adb, cwm, dagr8's Saurom and all the rest. However its time to send it back and I really don't know what Samsungs procedures are for a rooted phone. I've loaded the Bell kernel back to the phone but it's not the 100% solution I was looking for so I got frustrated and just went back to where I was already at with Saurom rc4 loaded up and titanium backup now doing it's thing.
Anyone with previous experiences send back a rooted phone for a hardware issue and know their policies?
Is there a step after flashing the bell kernel tar I'm missing?
Thanks
Jesso2k said:
My Galaxy Note (Bell) has a loose micro USB port. It can charge from the wall and is recognized by my pc however I need to prop it up on a slant in order for it to maintain pressure on the cable input, otherwise it will disconnect. It was caused by my dog knocking it off an end table while charging. It's a pain and Samsung has sent me a UPS slip to send it away.
The phone is rooted and this is my first experience with an Android. I've had a good time loading Da_G's kernel, figuring out adb, cwm, dagr8's Saurom and all the rest. However its time to send it back and I really don't know what Samsungs procedures are for a rooted phone. I've loaded the Bell kernel back to the phone but it's not the 100% solution I was looking for so I got frustrated and just went back to where I was already at with Saurom rc4 loaded up and titanium backup now doing it's thing.
Anyone with previous experiences send back a rooted phone for a hardware issue and know their policies?
Is there a step after flashing the bell kernel tar I'm missing?
Thanks
Click to expand...
Click to collapse
I had to send my Captivate to Samsung for repair. it was rooted and they fixed it without any issues.
Most manufacturers will fix hardware issues clearly not caused by rooting. Of course, no promises.
That's the reassurance I needed. I'll get on with it and send it away tomorrow. I'll report back in a very long 2 weeks...
Sent from my SGH-I717R using XDA
Jesso2k said:
My Galaxy Note (Bell) has a loose micro USB port. It can charge from the wall and is recognized by my pc however I need to prop it up on a slant in order for it to maintain pressure on the cable input, otherwise it will disconnect. It was caused by my dog knocking it off an end table while charging. It's a pain and Samsung has sent me a UPS slip to send it away.
The phone is rooted and this is my first experience with an Android. I've had a good time loading Da_G's kernel, figuring out adb, cwm, dagr8's Saurom and all the rest. However its time to send it back and I really don't know what Samsungs procedures are for a rooted phone. I've loaded the Bell kernel back to the phone but it's not the 100% solution I was looking for so I got frustrated and just went back to where I was already at with Saurom rc4 loaded up and titanium backup now doing it's thing.
Anyone with previous experiences send back a rooted phone for a hardware issue and know their policies?
Is there a step after flashing the bell kernel tar I'm missing?
Thanks
Click to expand...
Click to collapse
Best luck.... if you were in America you could just take it to an att store. Just be on a stockish rom and turn it in and they would not notice lol, get another device that day. Idk how things go up in Canada though.
Dont Do It!!!!
I dont know WHY there are people here sending the OP off....EVERYONE KNOWS that if you root it voids your warranty...it doesnt say "It voids your warranty except for hardware issues"
Why set yourself up to be disappointed when you can just revert it back to stock and not worry at all.....people always trying to catch a fool slipping....question is who will be the fool in this scenario????
BigBrotherMotown said:
I dont know WHY there are people here sending the OP off....EVERYONE KNOWS that if you root it voids your warranty...it doesnt say "It voids your warranty except for hardware issues"
Why set yourself up to be disappointed when you can just revert it back to stock and not worry at all.....people always trying to catch a fool slipping....question is who will be the fool in this scenario????
Click to expand...
Click to collapse
Well he should revert back to stock for sure but you can't roll back the counter. But as long as your stock they may not look at the counter and just fix the phone. It's been said before, there's no known case of Samsung voiding a warranty because of it.
Dont know how they do it up there but down here on AT&T we have a 30 day return/exchange policy I exercised yesterday in fact, plus a year warranty giving us refurbished phones if anything happens. I know you guys got it a little before us but I would check into this. Go back to stock there's a thread on how to do this in our development section and take it into your local providers store see what happens maybe you'll get lucky and they'll replace it on the spot. Say it was a hardware defect though.
BigBrotherMotown said:
I dont know WHY there are people here sending the OP off....EVERYONE KNOWS that if you root it voids your warranty...it doesnt say "It voids your warranty except for hardware issues"
Why set yourself up to be disappointed when you can just revert it back to stock and not worry at all.....people always trying to catch a fool slipping....question is who will be the fool in this scenario????
Click to expand...
Click to collapse
Because in everyone's experience they'll generally fix hardware problems even if you're rooted. Of course they have to, but they tend to. We all said there were no guarantees.
BigBrotherMotown said:
I dont know WHY there are people here sending the OP off....EVERYONE KNOWS that if you root it voids your warranty...it doesnt say "It voids your warranty except for hardware issues"
Why set yourself up to be disappointed when you can just revert it back to stock and not worry at all.....people always trying to catch a fool slipping....question is who will be the fool in this scenario????
Click to expand...
Click to collapse
It seems like one does not simply revert back to stock. Admittedly I'm new to this but all I can find in the development forum is the Bell kernel. The full bell system doesn't seem to be up, just the At&T. After a factory reset and old kernal I still have super user loaded and all of the bell bloatware gone. I'm sure with some due diligence I could have made a back up right after my original root but I didn't. Frustrated with the mess I created I just set the phone back up with Saurom the way I liked it.
alexige said:
Dont know how they do it up there but down here on AT&T we have a 30 day return/exchange policy I exercised yesterday in fact, plus a year warranty giving us refurbished phones if anything happens. I know you guys got it a little before us but I would check into this. Go back to stock there's a thread on how to do this in our development section and take it into your local providers store see what happens maybe you'll get lucky and they'll replace it on the spot. Say it was a hardware defect though.
Click to expand...
Click to collapse
It's only 14 days here. I've had it since launch on Feb 14th. Bell is synonymous for passing the buck off, contact them online and they tell you to call in, call them and they tell you go into a store, go to a store and they'll tell you to go to the original store of purchase or another another store with a repair tech on duty. Going directly through Samsung has been smooth thus far, I just hope if they have an issue they'll contact me before blowing whistles and charging my bill some erroneous fees.

[Q] Risk unlocking and flashing a rom?

Hello everyone, so im a bit confused. I have my galaxy s i9000 and i flashed thousands of rom without caring knowing its flexible to get it back again, heck i soft bricked it like 5 times . Now my question is should i risk voiding my warranty and bricking my pime for rooting/flashing a rom on it. So i want to take your opinions on is it worth it( like for the galaxy s I had to do it to remove the stupid lag) but i dont have any lag on the prime, so should i risk it all??
Stay Cool
I'd hope that you'd be able to answer that question for yourself.
If you are unable to list several shortcomings and limitations of it being stock, then why are you even thinking of risking it?
Myself, I bought a Nook Color 18 months ago with the full intention of rooting. I wasted no time in doing so. Of course those things are virtually unbrickable.
The Transformer Prime, OTOH, well... not so much. I haven't felt a pressing need to unlock and flash the ROM.
Do what you will, but unless you can quickly rattle off at least half-a-dozen limitations of its current config, it seems like it's a waste of time to fiddle with it.
So, I'm in similar situation. I had 3 android phones and all rooted, unlocked and with custom roms, but with Prime it's different, I'm more affraid of bricking it, because it's more expensive than all of these phones together.
But I'm seriously thinking about it, the main reason is now ROOT (and it can stay for half-a-dozen reasons) because I'm running JB.
And the most annoying thing now is the camera. I have green camera bug on my Prime. Does anyone know from own experience, that this can be fixed after unlocking?
And sorry for my English
Dekxster said:
And the most annoying thing now is the camera. I have green camera bug on my Prime. Does anyone know from own experience, that this can be fixed after unlocking?
And sorry for my English
Click to expand...
Click to collapse
Can't say from experience as I've never had a camera problem, but I've read numerous posts and the green camera is always hardware. You may be able to verify by squeezing lightly around the camera and seeing if it clears up temporarily.
Well i have some reasons to root it and i like to flash roms nd stuff mostly for fun, more like a hobby. but as you said this is like more precious and costs more especially after hearing bout asus' custom services that they wont be able to help if anything happens...
Well if u dont unlock bootloader thn there is no harm done.. It wont brick
Sent from my WT19i using xda app-developers app
vaibha said:
Well if u dont unlock bootloader thn there is no harm done.. It wont brick
Sent from my WT19i using xda app-developers app
Click to expand...
Click to collapse
Well then i cant do anything if i dont unlock it , Im on jb so unlocking it is the only way to access root etc. :/
Nope... Stay on ics rooted without unlocking bootloader..... Downgrade
Sent from my WT19i using xda app-developers app
vaibha said:
Nope... Stay on ics rooted without unlocking bootloader..... Downgrade
Sent from my WT19i using xda app-developers app
Click to expand...
Click to collapse
ohhh ok but i just love Jellybean and its smoothness (
nabil alami said:
Hello everyone, so im a bit confused. I have my galaxy s i9000 and i flashed thousands of rom without caring knowing its flexible to get it back again, heck i soft bricked it like 5 times . Now my question is should i risk voiding my warranty and bricking my pime for rooting/flashing a rom on it. So i want to take your opinions on is it worth it( like for the galaxy s I had to do it to remove the stupid lag) but i dont have any lag on the prime, so should i risk it all??
Stay Cool
Click to expand...
Click to collapse
I unlocked after letting my 1 year warranty expire. There aren't a ton of ROMs out there for the Prime atm, but it is worth it if you don't have a warranty to protect anyway.
The process of unlocking was painless for me. Downloaded the app, installed, it did its thing. I was on the newest JB OTA. No issues installing TWRP via fastboot.
nabil alami said:
Well i have some reasons to root it and i like to flash roms nd stuff mostly for fun, more like a hobby. but as you said this is like more precious and costs more especially after hearing bout asus' custom services that they wont be able to help if anything happens...
Click to expand...
Click to collapse
Thats exactly my problem. For example the green camera bug (tested and it is hardware fault, only strange thing is, it started just after JB update). Let's be honest, Prime is not perfect and you can have some hardware issues, when warranty is quite useful.
@vaibha: And do you know any way how to downgrade from JB?
Just flash gingerbred or ics... Easy...
Sent from my WT19i using xda app-developers app
Thanks for your detailed tutorial
I think there is no way (functional) for downgrading from JB to ICS. Or even gingerbread... on Prime?... :laugh: (I believe you just swapped GB and HC in your memory).
Of course I may be wrong, I hope I'm wrong. So you did you successfully downgrade? And if you did, how?
Dekxster said:
Thanks for your detailed tutorial
I think there is no way (functional) for downgrading from JB to ICS. Or even gingerbread... on Prime?... :laugh: (I believe you just swapped GB and HC in your memory).
Of course I may be wrong, I hope I'm wrong. So you did you successfully downgrade? And if you did, how?
Click to expand...
Click to collapse
Hahaha true, but im pretty sure you can downgrade the prime easily, manually download the software...to sd car...cont.
I thought so, but tried it and it doesn't work. There are 2 threads about it somewhere.
As it is written in another thread: "You cant revert back to the ICS bootloader once you have flashed the newer JB bootloader..."
Dekxster said:
I thought so, but tried it and it doesn't work. There are 2 threads about it somewhere.
As it is written in another thread: "You cant revert back to the ICS bootloader once you have flashed the newer JB bootloader..."
Click to expand...
Click to collapse
Unless you have your Nvflash backups.
Subsonic44 said:
Unless you have your Nvflash backups.
Click to expand...
Click to collapse
Dekxster, what subsonic says is right. You cannot downgrade to anything previous to jellybean if you haven't made nvflash backups while on ICS.
Also your green camera is 100 percent a hardware issue and if you haven't unlocked yet then return it for a free fix. If you are unlocked then you will normally have to pay but some people have got away with it. It all depends in what country you are in.
I figured this out, flumpster.
That is why I wrote, you can't downgrade, because I didn't make nvflash (I didn't post the rest of quotation, because I presumed, we don't have nvflash backup, if we are discussing about unlocking, which requires that) and that is why I wrote I don't want to unlock, because now I have hardware issue and they will fix it for free. I think I'll just wait one more year, when will my warranty expire, because who knows, what else might happen.
And are you guys using Hairy Bean? Is it good? Was it worth unlocking?
Because I don't know much about this rom, prefer CM on my phones.
Its worth unlocking if you are careful and dont mind risking hardware defect. A lot of people got a squaretrade or other 3rd party warranty. You can find a deal for $70 and get 2 years full protection...and then unlock without any risk what so ever.

RMA asus prime tf201,couple of questions ?

Hi all,
After a bit of deliberation, i've come to the conclusion that my prime is missing a few bits i would like to have, first and foremost, the camera is suffering from the green issue, 2nd the GPS is crap (to put it mildly) never locks although it does have a look.
Also there is a fair bit of stuttering and i am thinking that something a bit more sinister is wrong with the unit.
I've unlocked it, updated to JB and have got a custom rom running.
Now i know i can't relock it but do i need to unroot it? I mean these issues are hardware and nothing to do with me rooting it or unlocking it.
Has anyone else sent their's back and got it fixed and it's remained rooted? I send mine tomorrow, shall i bother to unroot or flash a stock rom ?
It's got Jelly beer at the moment.
Cheers.
PS: Any answers would be great as i don't have a lot of time.
rma
I just had the camera fixed rma for the second time and they reformatted the device installed jb and relocked my device.I cannot unlock it at all now and i am kinda pissed (i was running androwook 1.5)
horseless said:
I just had the camera fixed rma for the second time and they reformatted the device installed jb and relocked my device.I cannot unlock it at all now and i am kinda pissed (i was running androwook 1.5)
Click to expand...
Click to collapse
Did you give it to them with a custom ROM on it?
Sent from my GT-I9300 using xda premium

Categories

Resources