Hey guys i have read hundreds of posts and just want to know if i am missing anything before i count this as a total loss.
I was about to upgrade from Hairy Bean 3.5 to 4.2 I am rooted and unlocked.
First i have done many roms on many devices.
What i did was tried to get into clockwork, 2 times i shutdown and did the vol down and power and then hit vol up and it would say loading recovery kernel but never made it anywhere, so i held power down until it reboot into android, the i did the reboot into recovery from android and it did the same them, next i opened rom manager did the latest clockwork recovery and then rebooted into recovery from rom manager, it shut off and made it back to the Asus logo with the "the device is unlocked" in upper left corner and the Nvidi Tegra in lower right corner. Thats as far as i can get. i have tried the vol down and power again and nothing. it always gets back to that screen.
I can hold both power buttons and connect the usb and computer will see a APX and Unknown device in windows manager, but no drivers, i have tried the universal drivers but they dont work. i also download the asus stuff from asus and nothing helped either.
Any help would be great. Thanks to this great forum and great people as i have used it for years.
soloblazer said:
Hey guys i have read hundreds of posts and just want to know if i am missing anything before i count this as a total loss.
I was about to upgrade from Hairy Bean 3.5 to 4.2 I am rooted and unlocked.
First i have done many roms on many devices.
What i did was tried to get into clockwork, 2 times i shutdown and did the vol down and power and then hit vol up and it would say loading recovery kernel but never made it anywhere, so i held power down until it reboot into android, the i did the reboot into recovery from android and it did the same them, next i opened rom manager did the latest clockwork recovery and then rebooted into recovery from rom manager, it shut off and made it back to the Asus logo with the "the device is unlocked" in upper left corner and the Nvidi Tegra in lower right corner. Thats as far as i can get. i have tried the vol down and power again and nothing. it always gets back to that screen.
I can hold both power buttons and connect the usb and computer will see a APX and Unknown device in windows manager, but no drivers, i have tried the universal drivers but they dont work. i also download the asus stuff from asus and nothing helped either.
Any help would be great. Thanks to this great forum and great people as i have used it for years.
Click to expand...
Click to collapse
You have bricked your device.
You have installed an ics recovery onto the jellybean bootloader. There are warnings everywhere on xda saying not to use cwm on the prime.
If you cannot get back to the bootloader menu where the icons are or you cannot boot back into android it is game over I'm afraid.
flumpster said:
You have bricked your device.
You have installed an ics recovery onto the jellybean bootloader. There are warnings everywhere on xda saying not to use cwm on the prime.
If you cannot get back to the bootloader menu where the icons are or you cannot boot back into android it is game over I'm afraid.
Click to expand...
Click to collapse
So am i stuck? i didnt know it was a ICS recovery? i have used CW on the unit for almost a year and half, and never had a issue until today. Is there somewhere i can send the prime to, to get it fixed? or is it back to ASUS and pay them big bucks to fix it? Is there anything at all i could try before giving up on it?
thanks
soloblazer said:
So am i stuck? i didnt know it was a ICS recovery? i have used CW on the unit for almost a year and half, and never had a issue until today. Is there somewhere i can send the prime to, to get it fixed? or is it back to ASUS and pay them big bucks to fix it? Is there anything at all i could try before giving up on it?
thanks
Click to expand...
Click to collapse
You have not used cwm on that device since that nvidia logo has been bottom right. You updated the bootloader with a ROM at some point to jellybean and that is why you had no recovery there. You then tried putting cwm back on which was not for jellybean and you killed it sorry.
Only hope now Is Asus who could charge you up to 200 dollars to fix it.
Edit. there was a custom cwm at one point made by Wookie for his port of the tf300 ROM to the prime originally. This was never given out for long but the versions you say of hairybean in your first post never existed. We are only on 2.2 now and you are talking about 3.5 and 4.2.
flumpster said:
You have not used cwm on that device since that nvidia logo has been bottom right. You updated the bootloader with a ROM at some point to jellybean and that is why you had no recovery there. You then tried putting cwm back on which was not for jellybean and you killed it sorry.
Only hope now Is Asus who could charge you up to 200 dollars to fix it.
Edit. there was a custom cwm at one point made by Wookie for his port of the tf300 ROM to the prime originally. This was never given out for long but the versions you say of hairybean in your first post never existed. We are only on 2.2 now and you are talking about 3.5 and 4.2.
Click to expand...
Click to collapse
Sorry i was on 1.5 and was going to go to 2.11. Not sure were i got the other numbers. I guess i will try to send it back to ASUS and see what happens if there is nothing else to do.
So is it a software or hardware isssue? I am assuming is software issue and there is just not a way to reflash it?
thanks again for the help.
soloblazer said:
Sorry i was on 1.5 and was going to go to 2.11. Not sure were i got the other numbers. I guess i will try to send it back to ASUS and see what happens if there is nothing else to do.
So is it a software or hardware isssue? I am assuming is software issue and there is just not a way to reflash it?
thanks again for the help.
Click to expand...
Click to collapse
Most times Asus will try to replace the motherboard which is not needed.
If you be straight with them and tell them you messed up the recovery partition when flashing it and that there is nothing wrong with the hardware and could they please reflash it you might get lucky and have less of a bill.
flumpster said:
Most times Asus will try to replace the motherboard which is not needed.
If you be straight with them and tell them you messed up the recovery partition when flashing it and that there is nothing wrong with the hardware and could they please reflash it you might get lucky and have less of a bill.
Click to expand...
Click to collapse
Ok i will see what happens, so is it just a flash they have to do? I am assuming you need a special machine to flash it or is it done from a computer to flash it?
Update:
So i sent my prime back to Asus, after a week they said it was customer induced damaged and was not covered under warranty. They said it need to have the motherboard replaced at a cost of almost $300.
I told them what i did, as someone here told me to, and said i mess up the recovery partition and it just needed to be flashed and didnt need a new motherboard.
This is there response:
There are limitations to what we can do on the service side and the service dept does not have the capability to flash the unit so all we can offer is hardware replacement. Please advise.
Not sure what to do next, am i just out of luck? i can buy another one for less then $300?
Thanks for the help again.
buy a motherboard on eBay - $80 - $100, I just did, I replaced
I just did the same thing to mine; installed CMW on my TF201 latest stock JellyBean. Unlocked and rooted. Only had the thing for about a week. Can you tell me if the "mainboard" they are selling on ebay will work? Also did you find a tutorial to follow with replacing the board - if so where? Thanks - Bill
Yes does anyone know of, or have a video tutorial on how to take these apart and replace, i changed the digitize on my TF101, not a big deal.
Related
So I had previously rooted my SGSII, and decided to try installing CM7 on it. I used CWM Recovery and ran it off the SD card, and everything appeared to work fine. I think I had a bad/not fully functioning CWM or something, as it didn't list an option to backup anything (I'm guessing because I flashed the stock kernel after rooting?) Anyway, it will no longer boot. I can access download mode, but Odin fails everytime I try to flash anything back on there. When I try to boot my phone, I just get a "Firmware upgrade encountered an issue" error.
EDIT: I just tried again as I was writing this, after rebooting, reinstalling my drivers and rebooting my computer. I was able to get the Firmware to flash properly in Odin. Now I have my phone booting and getting stuck on the "Samsung Galaxy SII GT-I9100 splash screen... Doesn't seem to go any further than that though, unfortunately.
Any ideas what I can do? Is it possible that I need re-flash a bootloader or something ??
Any help would be supremely appreciated!
So I was just trying to re-install the Kernel, using the CF unsecured kernel, and it failed, but when I try to go into recovery mode, it looks as though it managed to install CWM Recovery. I have no idea what to do from here, and am sort of afraid to do anything for fear or bricking the phone completely...
I'm hoping someone out there knows how to fix this, I feel like such a tool
As long as you can get into download-mode, your phone isn't bricked.
If you switch from or to a TouchWiz-based ROM, you have to do a full-wipe in the recovery.
Sent from my GT-I9100 using XDA App
Go back to stock first via download mode via odin
Nah you're good. Similar thing happened to me at my first flashing attempt. Get your stock firmware from Intratech's thread, put the phone into download mode & flash the firmware via Odin.
Then maybe have another go at rooting the phone with the matching CFRoot kernel.
Porkchops said:
So I was just trying to re-install the Kernel, using the CF unsecured kernel, and it failed, but when I try to go into recovery mode, it looks as though it managed to install CWM Recovery. I have no idea what to do from here, and am sort of afraid to do anything for fear or bricking the phone completely...
I'm hoping someone out there knows how to fix this, I feel like such a tool
Click to expand...
Click to collapse
yes, if you can still go in download mode it's no so difficult..this "small brick" it's on of "Android things to do" once in your SGS2 life
Hi guys. I'm in a worst situation. As my phone after a failed ODIN downgrade from Android 2.3.6 to one stock kernel is completelly dead - it doesn't boot anymore - not even managed to put it back into download mode or revert to fact defaults (no keys, no lights not even battery charging displayed when pluged in) - tryed the USB jig also. Nothing worked.
The question is: Will Samsung manage to repair and how much will it cost - an average ammount offcourse. Because I guess it's out of the question to be considered a warranty issue. I guess it will be visible somebody have done smth to the ROM by a software approach....
This is the short story because I would bore you to discuss all the things I have been through - it was only my faoult out of stupidity
HELP!
I don't see why Samsung wouldn't fix it ? As to how much they'll charge you, I think you'll find that will vary from country to country (labour costs being variable, etc). No, I don't think you'll be able to have it repaired under warranty.
You might want to look at having it JTAG repaired by someone other than Samsung. This will possibly be cheaper than having Samsung repair it. Do a search on here/Google.
alexdonc said:
The question is: Will Samsung manage to repair and how much will it cost - an average ammount offcourse. Because I guess it's out of the question to be considered a warranty issue. I guess it will be visible somebody have done smth to the ROM by a software approach....
HELP!
Click to expand...
Click to collapse
Thank you very much. I have searched alot to actually understand - unfortunatelly for me it will cost... I saw on youtube a JTAG in action right now (cannot post the link yet). I understand now it is the only way. I'll keep you posted guys. Tomorrow I'll go to service.
I'm sorry it's going to cost Alex. A difficult thing to happen, I know
Here's a link for a JTAG repairer in the US who is also a member here, tho I see you've already found one. I'm sure doing it this way will be cheaper/probably faster than having Samsung do the repair as well.
alexdonc said:
Thank you very much. I have searched alot to actually understand - unfortunatelly for me it will cost... I saw on youtube a JTAG in action right now (cannot post the link yet). I understand now it is the only way. I'll keep you posted guys. Tomorrow I'll go to service.
Click to expand...
Click to collapse
Thax. Funny thing is that this is exactly the thing I found - the same mobiletechvideos in US Now I allready have an ideea of how much should cost that. Hopefully I'll find a local GSM repair shop with the posibilitty to unbrick it cheep - or at least not much than 50USD - in local currency ofcource.
I'm still thinking if it is possible to use an ATMEL copy process - like in the old times for EEPROMS - I have done that in the past. In theory it might work but I will never do it - alredy scared about what happened to my beloved droid.
Thx again Mistah and have a gr8 day and a wonderfull new 2012!
Yeah I've seen a report or two on here from people who have used his service & have been happy. Must admit I found his page when thought I'd bricked my phone after my first flash attempt messed up. Yeah you might be able to get it done cheaper somewhere local, and that will mean less time without the phone for you without the phone in mail from you to the US & back again.
Let us know how you get on, your experience will be a good guide for people in future who have the same problems as you.
No probs man, happy to give you the little help I did. You too Alex Hope you have a great year & you get your phone back & working soon
alexdonc said:
Thax. Funny thing is that this is exactly the thing I found - the same mobiletechvideos in US Now I allready have an ideea of how much should cost that. Hopefully I'll find a local GSM repair shop with the posibilitty to unbrick it cheep - or at least not much than 50USD - in local currency ofcource.
I'm still thinking if it is possible to use an ATMEL copy process - like in the old times for EEPROMS - I have done that in the past. In theory it might work but I will never do it - alredy scared about what happened to my beloved droid.
Thx again Mistah and have a gr8 day and a wonderfull new 2012!
Click to expand...
Click to collapse
Hello again. Solved right now. The service didn't charged me at all - I was kind of lucky after all. Unfortunately there are still some issues I have from the start. I'll keep on digging - software related.
Well i was flashing a few different roms to test and see which one i liked better and when i went to flash back to the stock rom, accidentally clicked on the wrong thing and it just hard bricked my sgp
It wont turn on at all. The charge logo doesn't even show up when you plug it in. I just need to know if there are any ways i can fix this.
happened to me too. the roms/file systems/procedures that are available for the 4.0 US are not infallible and can lead to a soft/hard brick.
the full restore appears to be faulty too, however it's quite possible that a working full restore might be available soon.
unfortunately, that leaves you with a well & truly dead device right now.
if you can get a warranty repair from samsung; well and good. I was able to return mine to the store and got it replaced - no questions.
to anyone else: wait for a working full restore.
I saw a video on youtube of a USB "jig" that plugs right into the player (or any samsung phone, I believe) that they claim will recover from hard bricks to download mode so you can reflash. Check around youtube or maybe here somewhere apparently its just a resistor connected to certain pins on the usb connector.
I just ordered a usb jig yesterday and when I get it ill tell you if it works. This is where i got it, its supposed to work for the galaxy player.
Its only $5.50 : usbjig (.) com Just take out the '(' and ')' in the link and it will take you to the website.
The same thing happened to me. What you need to do is instead of spending money on some device which is most likely a scam, you can just go into download recovery and flash from there. You said that you had been flashing roms before so you must have some experience with Odin or Heimdall. To get into download mode you need to power off your player, then hold the up-volume button while turning it on until a yellow triangle with a little android guy in it. Hook it up to Odin or Heimdall, by the way, I have no experience with Heimdall so I cannot really help you with that if thats what your using, and flash a different or a recovery rom to your device. May I suggest Klins Klassic R5 with SteveS custom kernel R3?
RexKyle said:
The same thing happened to me. What you need to do is instead of spending money on some device which is most likely a scam, you can just go into download recovery and flash from there.
Click to expand...
Click to collapse
First of all, the jigs that people have made or purchased have worked in countless situations and are well documented in this forum. Scam? I don't even know where to go with that. In my case both CWM and Recovery Mode were inaccessible without the jig. For less than $5 I was able to recover my device.
nelsona96 said:
It wont turn on at all. The charge logo doesn't even show up when you plug it in.
Click to expand...
Click to collapse
Try to get into download mode. If you can't get into download or recovery then picking up a jig isn't a bad idea. I was devastated when my Galaxy Player 4.0 seemed dead in the water but the jig got it to where I could connect it to my laptop and flash a recovery kernel, rom, and fortunately, a bootloader.
This is my experience
OP, do NOT copy what I did. What happened to my device does not look in any way similar to what happened to yours. I am linking my thread SOLELY to illustrate how much information I had to cough up to assist the fine folks of XDA to guide me towards a fix. XDA is awesome. Help them so that they can help you.
When i said hard bricked, i meant that you cant do anything with it. It wont boot into recovery or download mode. But i already ordered the jig, like i said ill post on here if it works or not.
Hi!
I just had the weirdest experience with my sgsii
I have been using the unofficial vsync patched cm10 rom for this modelfor the last month or so.
I have been updating at least one per week but this week I decided to give my phone a break and not flash it... i am actually really busy at job.
Suddenly tonight, the phone looked like when you have a SOD... so i just pulled the battery.
Now, it does not pass from the first logo stage, just prior to start booting.
I cannot access cwm recovery either, but download mode seems to work-
Now the odd thng is that i am attempting to flash somethng to get the phone working but it gets stuck in the step "NAND Write start!".... it goes no furter than that...
I have chosen the options auto reboot and f.reset time.
a pda file, phone and csc file from the eaked jb rom.....
The system I am attempting to flash from is a windows 7 pro 64 bit.... and odin is Odin3 v1.85...
Please, tell me i didnt get a brick and there is a way tofix it... :crying:
EDIT: Desperated, i tried to flash latest jb leak again, and chose the pit file that comes with it, which re-partitions the phone...
After 20 minutes not responding, i pulld the battery out... now i cannot even enter download mode....nothing....nada....
Sounds like you bricked it, good job.
Sent from my GT-I9100 using Forum Runner
GFXi0N said:
EDIT: Desperated, i tried to flash latest jb leak again, and chose the pit file that comes with it, which re-partitions the phone...
After 20 minutes not responding, i pulld the battery out... now i cannot even enter download mode....nothing....nada....
Click to expand...
Click to collapse
too bad never repartition unless you make your own pit file with heimdall .. if you would've wait a couple hours I just pmed you.
and for other people instead of flashing samsung's bricksquadroms you can flash CM9 resurrection edition. http://forum.xda-developers.com/showthread.php?t=1419102
Make a pit file with heimdall of your own device. Don't trust pitfile that comes with a rom.
I re-partitioned my device and i got like 3GB intern memory back.
There's probably a way to get your device alive. it isn't the mmc cap bug so. search some threads on xda about brickbugs etc of galaxy phones and you'll find people who hardbricked and unbricked their device.
Probably usb jig could get you into download mode i'm not sure though. Or else jtag. Ask some people over there they will know it
I will try to revive it with jig.... i must find the thingy though.,..... if not.. i will send it to the service but i'm not sure i'm on warranty....
Being not patient made me f*ck it up bad....
Any clue on how to recover a phone after re-partitioning.... i really don't know where to start...
EDIT: JIG does not switch it on either... why did i have to re-partition?!??!?!?!?!?!
That was a dumb move....... any more ideas?
If you cant enter recovery or download mode you have no choice but to JTAG repair or mobo replacement.
Hard brick.... on its way to service
Wish me luck..
Mobo replacement it is, this incident will at least teach you to be patient, I explained you my problem in PM, I waited for 1 week for USB jig to arrive from eBay then flashed stock ROM. I trust the f/w it came with the most.
Sent from my GT-I9100 using xda app-developers app
Sh4Dy said:
Mobo replacement it is, this incident will at least teach you to be patient, I explained you my problem in PM, I waited for 1 week for USB jig to arrive from eBay then flashed stock ROM. I trust the f/w it came with the most.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
USB JIG didn't work at all..... I have one and it was not able to boot the phone ....
Isn't this kind of brick fixable with Jtag?
Sent from my GT-I9100
Ok, before I repartitioned, making the problem worse, I was experiencing some kind of R/W problem..... there was something odd with the nand because I was able to boot in download mode, but not in recovery (CWM) mode....
Then, when I plugged the phone to the computer, Odin was able to recognize the phone.
I followed some thread around XDA to flash 4.1.2 leak from sammy and when I hit the "Start" button in Odin, it would not pass from the first stages, revealing that R/W or I/O problem.... the internal nand was, somehow broken.... it didn't read or write properly.... so, even If i could find a workaround, I would have lost some internal storage (some posts talk about around 3 Gb or something similar as lost space in these cases).... that is IF i had been able to fix it..... but then, that's what warranty is for..... so I gave it a last (dumb) try..... including the pit file, which attempted a format, which ended messing (i would say the f. word) everything up.
The good side is that unable to even boot, at least i lost the blue loading bar the vsync patched cm10 mod has in the first bootup screen.... which could have revealed to sammy that I was tempering with unofficial roms....
Lesson learned: Be patient people: But also, don't think this could not happen to you: The phone was perfectly working the last time I saw it... and I even was making some phone calls and browsing the internet.... I mean... it gave no prior symptoms or warnings... I t just died..... I guess I have to be glad I'm not one of those people whose phone gets caught up on fire on their pockets for malfunctioning.....
Now waiting for it to come back revived from samsung..... I have hope
hope it will be able to recover
Great: After losing the phone and past almost three months, samsung says the phone has been manipulated and the warranty is voided....
I wasn't able to flash back an original firmware prior to sending it to the tech service.....
What do you recommend me to do?
I guess paying for the repair would be quite expensive....
GFXi0N said:
Great: After losing the phone and past almost three months, samsung says the phone has been manipulated and the warranty is voided....
I wasn't able to flash back an original firmware prior to sending it to the tech service.....
What do you recommend me to do?
I guess paying for the repair would be quite expensive....
Click to expand...
Click to collapse
Well what is it you expect us to say, some secret magic word that will fix it for free?
The choice is pay for it to be fixed or dont.
So no magic word or secret passphrase so they will upgrade my device to a SGSIV for free?
Damn.....
I'm asking for advice, since I'm convinced the brick was not caused by flashing anything.....
Does anyone have any experience with this in the past to know more or less how expensive bill could I be facing for the repair?
GFXi0N said:
So no magic word or secret passphrase so they will upgrade my device to a SGSIV for free?
Damn.....
I'm asking for advice, since I'm convinced the brick was not caused by flashing anything.....
Does anyone have any experience with this in the past to know more or less how expensive bill could I be facing for the repair?
Click to expand...
Click to collapse
Dude, it WAS caused by flashing something.
Initially your device wasn't "bricked" and was likely a kernel issue and possibly a dirty usb data connection.
The point when it was bricked was when you tried flashing the pit file, had bad connection and you then pulling battery. This f**ked your nand chip up and only way to fix it is to replace motherboard.
You will need to either purchase a mobo replacement and replace it yourself or pay somebody to purchase/replace it for you. Probably looking at around £100.
When bricks happen, you really need to BRICK it before claiming warranty.
I've got a couple of guys here that own a PhD in bricking.
Brick is the new flash.
Sent from the little guy
Jig wasn't working
Flashing anyting.. even just a recovery wasn't working
FLashing official didnt work
Flashing CM didnt work either
Tested different cables and different ports
It was f*cked up already... anyway: 4 samsung devices owned: 3 gave problems of hardware..... that cannot be a coincidence...
Repartitioning erased my tracks, if anything... because the 3 key combo for recovery was working until then..... but either way they managed to access the memory somehow, I guess.....
GFXi0N said:
anyway: 4 samsung devices owned: 3 gave problems of hardware..... that cannot be a coincidence....
Click to expand...
Click to collapse
Maybe a PEBCAK?
GFXi0N said:
Jig wasn't working
Flashing anyting.. even just a recovery wasn't working
FLashing official didnt work
Flashing CM didnt work either
Tested different cables and different ports
It was f*cked up already... anyway: 4 samsung devices owned: 3 gave problems of hardware..... that cannot be a coincidence...
Repartitioning erased my tracks, if anything... because the 3 key combo for recovery was working until then..... but either way they managed to access the memory somehow, I guess.....
Click to expand...
Click to collapse
Don't blame the phone, blame the user.
Yeah, sure... anyway... thanks for the help... I hope some day you need it and someone will come not trying to mocking you..... anyway... this is the trend around here lately...
Happy trolling
Hey guys,
I have a galaxy s3 (I9300) and I've had it rooted for some time now. I started using CyanogenMod 10.2 nightlies a few months ago and they've mostly been fine. The odd issue comes up but I've been able to work it out. So, a few hours ago my phone just turned off of its own accord and started to bootloop, but on the "Samsung Galaxy S3 GT-19300" screen, not the CyanogenMod screen (to clarify, this screen comes up first then the cyanogenmod one usually). I've tried booting into recovery (CWM 6) but it just shows the CWM boot logo thing (that cog with the hat) and then loops back to the galaxy s3 page. I've also tried putting it in download mode, and it seems to stay on the warning page longer than it does anywhere else, but it wont let me actually put in it download mode from there.
I had a look around google and saw people have had the same problem, but everything I could find was when people had flashed a new rom/kernel etc. and something had gone wrong in the process. The weird thing about mine is that I haven't changed anything, even downloaded any new apps, for maybe a week, so it's not like something suddenly changed. I also wasn't using it when it started, it was just sitting on the table next to me.
Usually I can work these things out, but I'm stumped here. Any help would be really appreciated.
Thanks in advance!
danielbollom said:
Hey guys,
I have a galaxy s3 (I9300) and I've had it rooted for some time now. I started using CyanogenMod 10.2 nightlies a few months ago and they've mostly been fine. The odd issue comes up but I've been able to work it out. So, a few hours ago my phone just turned off of its own accord and started to bootloop, but on the "Samsung Galaxy S3 GT-19300" screen, not the CyanogenMod screen (to clarify, this screen comes up first then the cyanogenmod one usually). I've tried booting into recovery (CWM 6) but it just shows the CWM boot logo thing (that cog with the hat) and then loops back to the galaxy s3 page. I've also tried putting it in download mode, and it seems to stay on the warning page longer than it does anywhere else, but it wont let me actually put in it download mode from there.
I had a look around google and saw people have had the same problem, but everything I could find was when people had flashed a new rom/kernel etc. and something had gone wrong in the process. The weird thing about mine is that I haven't changed anything, even downloaded any new apps, for maybe a week, so it's not like something suddenly changed. I also wasn't using it when it started, it was just sitting on the table next to me.
Usually I can work these things out, but I'm stumped here. Any help would be really appreciated.
Thanks in advance!
Click to expand...
Click to collapse
can you at least enter download mode after a long time you said? if not, try pulling out the battery for 5 minutes or more and re-insert and enter download mode. i hope it's not sds! good luck
sriram231092 said:
can you at least enter download mode after a long time you said? if not, try pulling out the battery for 5 minutes or more and re-insert and enter download mode. i hope it's not sds! good luck
Click to expand...
Click to collapse
Nope, if I press the volume up button to go into it, it just goes back to the bootloop. I'll try the battery thing though, thanks!
Nope, it didnt work, I left it out for maybe half an hour and nothings changed :/ anyone else got any ideas?
SDS thread and BootLoop identical questions posted .
What does Product Code say in download mode .
But if you cannot get to download mode then you need a service centre repair .
looks like u are facing SDA but a bit diffrend than a normal SDS.. mine still can go into download mode with blank product name..
If product name is blank in download mode then you got sudden death, consider a phone as a brick. Nothing will help, including repartitioning.
You need to contact service centre.
I'll check it in a minute, but if it is bricked, will any service center actually help me seeing as it's rooted and all?
danielbollom said:
I'll check it in a minute, but if it is bricked, will any service center actually help me seeing as it's rooted and all?
Click to expand...
Click to collapse
AFAIK if it's sudden death then it's not possible to detect root and other modified things, or in other words - nobody has money to prove that you have been using unofficial firmware .
JustArchi said:
AFAIK if it's sudden death then it's not possible to detect root and other modified things, or in other words - nobody has money to prove that you have been using unofficial firmware .
Click to expand...
Click to collapse
Ahhhh, well that is handy then
In terms of a service centre, will samsung have a list of them somewhere so I can find one near me?
So I contacted samsung and they gave me the link to book into a service centre etc, but I just realised that when I try to go into recovery mode, the CWM recovery logo comes up before going back to bootloop. Is there any way to get rid of that so that my root is completely untraceable?
danielbollom said:
So I contacted samsung and they gave me the link to book into a service centre etc, but I just realised that when I try to go into recovery mode, the CWM recovery logo comes up before going back to bootloop. Is there any way to get rid of that so that my root is completely untraceable?
Click to expand...
Click to collapse
If you can't flash anything with Odin (stock software) then you're screwed. Eventually you can try to enter recovery and flash "eraser" of recovery, but this requires working recovery... So if you actually can enter recovery then you can also flash anything, which will literally delete everything.
In other case, no, no way. But if you're lucky enough you may break it just by leaving your phone on for some hours in bootloop, haha.
JustArchi said:
If you can't flash anything with Odin (stock software) then you're screwed. Eventually you can try to enter recovery and flash "eraser" of recovery, but this requires working recovery... So if you actually can enter recovery then you can also flash anything, which will literally delete everything.
In other case, no, no way. But if you're lucky enough you may break it just by leaving your phone on for some hours in bootloop, haha.
Click to expand...
Click to collapse
Is there any way to wipe it with magnets or anything? hahah I'm clutching at straws now, but otherwise I'm just left with an expensive paperweight so I'm trying to find anything I can
danielbollom said:
Is there any way to wipe it with magnets or anything? hahah I'm clutching at straws now, but otherwise I'm just left with an expensive paperweight so I'm trying to find anything I can
Click to expand...
Click to collapse
To be honest think twice before physically crashing your internal memory, as it may void your warranty at all.
I'd try flashing stock firmware through odin, if it doesn't work I'd try flashing anything through recovery. If both of these methods fail just leave your phone in bootloop and hope that it'll automatically destroy everything... :laugh:
Seriously though, you can either physically destroy internal memory or leave it in bootloop and hope for the best, eventually send them device in current status. Up to you, because you won't have a possibility to do anything else.
JustArchi said:
To be honest think twice before physically crashing your internal memory, as it may void your warranty at all.
I'd try flashing stock firmware through odin, if it doesn't work I'd try flashing anything through recovery. If both of these methods fail just leave your phone in bootloop and hope that it'll automatically destroy everything... :laugh:
Seriously though, you can either physically destroy internal memory or leave it in bootloop and hope for the best, eventually send them device in current status. Up to you, because you won't have a possibility to do anything else.
Click to expand...
Click to collapse
If I send it back to them as it is now it'll take them about 20 seconds I reckon before they see the CWM logo, realise its rooted and send it straight back, so I dont know what I'm gonna do hahah
OK so I might have screwed up my prime. I've done command line stuff and had custom ROMs on everything I own. But I am by no means an expert so please bear with me. I will explain my series of events to the best of my ability.
Starts off with a buggy ROM, i loaded it some time ago and have been dealing with it since. It was cm10 dated sometime in the middle of 2012. Did some searching and found that all the new ROMs were saying something about needing to nvflash to get blobs or something. No prob. Right?
Got everything prepared based off of these instructions:
androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
Downloaded recovery_tf201.img, fastboot, nvflash, and the drivers. The very first step went ok. It showed moving the .img and then flashing the file. When done the little blue bar went across the screen like it should have.
Here's were it all went bad. I ran the reboot command in fastboot, device rebooted, loaded android. I held power a sec and chose "reboot recovery". I can now get the device to do one of three things:
1. Asus splash screen showing device unlocked when powered normally. That's it.
2. Hold vol down gets asus screen with 4 lines: this device is unlocked, android cardhu-user bootloader 2.10 e, checking for ota recovery, and booting recovery kernal image. Stops there.
3. Volume up gets black screen apx mode
Also tried running battery dead. Still same thing.
Is there any hope for my prime?
Where did I go wrong? Was it by pressing "reboot recovery" from the os?
Arggg please help. Otherwise a guide to replace the main board would be great.
Anything else please ask.
Thanks all,
Nick
Username5.2 said:
OK so I might have screwed up my prime. I've done command line stuff and had custom ROMs on everything I own. But I am by no means an expert so please bear with me. I will explain my series of events to the best of my ability.
Starts off with a buggy ROM, i loaded it some time ago and have been dealing with it since. It was cm10 dated sometime in the middle of 2012. Did some searching and found that all the new ROMs were saying something about needing to nvflash to get blobs or something. No prob. Right?
Got everything prepared based off of these instructions:
androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
Downloaded recovery_tf201.img, fastboot, nvflash, and the drivers. The very first step went ok. It showed moving the .img and then flashing the file. When done the little blue bar went across the screen like it should have.
Here's were it all went bad. I ran the reboot command in fastboot, device rebooted, loaded android. I held power a sec and chose "reboot recovery". I can now get the device to do one of three things:
1. Asus splash screen showing device unlocked when powered normally. That's it.
2. Hold vol down gets asus screen with 4 lines: this device is unlocked, android cardhu-user bootloader 2.10 e, checking for ota recovery, and booting recovery kernal image. Stops there.
3. Volume up gets black screen apx mode
Also tried running battery dead. Still same thing.
Is there any hope for my prime?
Where did I go wrong? Was it by pressing "reboot recovery" from the os?
Arggg please help. Otherwise a guide to replace the main board would be great.
Anything else please ask.
Thanks all,
Nick
Click to expand...
Click to collapse
2. Hold vol down gets asus screen with 4 lines: this device is unlocked, android cardhu-user bootloader 2.10 e, checking for ota recovery, and booting recovery kernal image. Stops there.
Can you post a screen-shot of this ?
Thx Josh
See if this works.
Username5.2 said:
See if this works.
Click to expand...
Click to collapse
When on that screen does the PC see it as anything in device manager ?
So you do have your nvflash files backed up ?
Thx Josh
No it is not picked up by the PC at all.
And no I had just flashed the custom recovery with fastboot. Had not done anything else. Next step was to run wheelie. Didn't get that far.
Username5.2 said:
No it is not picked up by the PC at all.
And no I had just flashed the custom recovery with fastboot. Had not done anything else. Next step was to run wheelie. Didn't get that far.
Click to expand...
Click to collapse
Well, with no fastboot or adb an no nvflash a motherboard is the only way ...
Sorry for the crappy news ....
Thx Josh
lj50036 said:
Well, with no fastboot or adb an no nvflash a motherboard is the only way ...
Sorry for the crappy news ....
Thx Josh
Click to expand...
Click to collapse
Probably; but: screenshots show, that it is a tf101 (Eee Pad Transformer). I thought that I read in the forums some workaround, because it has no encrypted bootloader. Can be wrong, I'm no expert. Search!
edit:
Found it:
lilstevie said:
There is no concept of locked or unlocked in the tf101 bootloader, in the most general sense it is unlocked as it allows booting of unsigned kernels, and flashing of unsigned blobs.
the leaked key allows lower level communication (bootrom) with the device and can recover from bootloader errors.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=22408864&postcount=3
Josh, thanks. And no problem on the crappy news. I kinda figured this was the case.
OK well after searching eBay and forums, I'm going to just get another prime. $80 for the logic board or $100 for a whole working tablet. So I will let this one sit awaiting a fix or a cheap logic board.
In the mean time can someone tell me where I screwed up?
I hate stock ROMs, and the sound of an "unbrickable tablet" by flashing new recovery is appealing. For that I will be attempting to back up these nvflash files on my new prime but I don't want another expensive paperweight.
So 2 questions.
Where did it all go wrong?
Am I following the set of instructions you all would recommend? I did get the link from this forum.
Thanks again.
das chaos said:
Probably; but: screenshots show, that it is a tf101 (Eee Pad Transformer). I thought that I read in the forums some workaround, because it has no encrypted bootloader. Can be wrong, I'm no expert. Search!
Click to expand...
Click to collapse
It is def. A tf201. All that writing in the screenshot is new except "the device is unlocked" since I flashed the recovery image from the link.
das chaos said:
Probably; but: screenshots show, that it is a tf101 (Eee Pad Transformer). I thought that I read in the forums some workaround, because it has no encrypted bootloader. Can be wrong, I'm no expert. Search!
edit:
Found it:
http://forum.xda-developers.com/showpost.php?p=22408864&postcount=3
Click to expand...
Click to collapse
Its a really old bootloader, that is the way they use to look....
Thx Josh
Username5.2 said:
Josh, thanks. And no problem on the crappy news. I kinda figured this was the case.
OK well after searching eBay and forums, I'm going to just get another prime. $80 for the logic board or $100 for a whole working tablet. So I will let this one sit awaiting a fix or a cheap logic board.
In the mean time can someone tell me where I screwed up?
I hate stock ROMs, and the sound of an "unbrickable tablet" by flashing new recovery is appealing. For that I will be attempting to back up these nvflash files on my new prime but I don't want another expensive paperweight.
So 2 questions.
Where did it all go wrong?
Am I following the set of instructions you all would recommend? I did get the link from this forum.
Thanks again.
Click to expand...
Click to collapse
The bootloader is to old to flash that recovery, that is where you went wrong ....
Thx Josh
Username5.2 said:
OK so I might have screwed up my prime. I've done command line stuff and had custom ROMs on everything I own. But I am by no means an expert so please bear with me. I will explain my series of events to the best of my ability.
Starts off with a buggy ROM, i loaded it some time ago and have been dealing with it since. It was cm10 dated sometime in the middle of 2012. Did some searching and found that all the new ROMs were saying something about needing to nvflash to get blobs or something. No prob. Right?
Got everything prepared based off of these instructions:
androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
Downloaded recovery_tf201.img, fastboot, nvflash, and the drivers. The very first step went ok. It showed moving the .img and then flashing the file. When done the little blue bar went across the screen like it should have.
Here's were it all went bad. I ran the reboot command in fastboot, device rebooted, loaded android. I held power a sec and chose "reboot recovery". I can now get the device to do one of three things:
1. Asus splash screen showing device unlocked when powered normally. That's it.
2. Hold vol down gets asus screen with 4 lines: this device is unlocked, android cardhu-user bootloader 2.10 e, checking for ota recovery, and booting recovery kernal image. Stops there.
3. Volume up gets black screen apx mode
Also tried running battery dead. Still same thing.
Is there any hope for my prime?
Where did I go wrong? Was it by pressing "reboot recovery" from the os?
Arggg please help. Otherwise a guide to replace the main board would be great.
Anything else please ask.
Thanks all,
Nick
Click to expand...
Click to collapse
Username5.2 - We are sorry to hear about this issue you are having and we are more than happy to assist you. Please email us at [email protected] with your serial number and this post attached for assistance.
If you have any further questions, comments, or concerns please do not hesitate to let us know. We will be more than happy to assist you. Once again, thank you for choosing ASUS products and services.
Thank you,
-In Search of Incredible-
Technical Support Department
http://www.asus.com :: http://service.asus.com/
lj50036 said:
Its a really old bootloader, that is the way they use to look....
Thx Josh
The bootloader is to old to flash that recovery, that is where you went wrong ....
Thx Josh
Click to expand...
Click to collapse
Dang. I followed a link from this forum @
http://forum.xda-developers.com/showthread.php?t=1774352
That led me to this link I posted above:
androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
So that guide had me download an incorrect file? The files were downloaded right from that page. Check it out.
Username5.2 said:
Dang. I followed a link from this forum @
http://forum.xda-developers.com/showthread.php?t=1774352
That led me to this link I posted above:
androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
So that guide had me download an incorrect file? The files were downloaded right from that page. Check it out.
Click to expand...
Click to collapse
Your firmware version is 9.4.2.21 which is Android version 4.0.3 'ICE CREAM SANDWICH'
The guide is for 'JELLYBEAN' bootloaders....
That is why flashing said file was the wrong thing to do...
Sorry for the bad new... :crying:
Thx Josh