Related
Hi all,
I have looked for a similar post, I found out that many people experienced something like that trying unlocking their phones, but I haven't found out any solution.
Here is my situation:
I have tried to unlock my s5830 (orange spain carrier), I have used a method which it seems to be dangerous for the phone, but of course I have found out it was dangerous after I have already tried it
Anyway after I discovered the unlock number contained in the perso.txt file in the efs folder, my phone restarted without service once and after that it went in a bootloop mode, it goes on a download mode, but there is no way to get back recovery mode or a normal boot.
I flashed the s5830 several times with many firmware, but no one worked, and the phone is still stuck in an infinite loop, in which I am not even able to see the samsung logo coming out at the very beginning.
I know many phones got bricked in this way, I wanted to know if anybody has been able to recover the phone or if anybody know any possible solution.
And if not, do you know if the warranty is covering this problem? I just got the phone a couple months ago; i have unlocked other devices before, but this is the first time I have experienced a problem so I am quite new about warranty as well. Please HELP ME
Merry Christmas guys!!!
Thanks in advance
sfrat said:
Hi all,
I have looked for a similar post, I found out that many people experienced something like that trying unlocking their phones, but I haven't found out any solution.
Here is my situation:
I have tried to unlock my s5830 (orange spain carrier), I have used a method which it seems to be dangerous for the phone, but of course I have found out it was dangerous after I have already tried it
Anyway after I discovered the unlock number contained in the perso.txt file in the efs folder, my phone restarted without service once and after that it went in a bootloop mode, it goes on a download mode, but there is no way to get back recovery mode or a normal boot.
I flashed the s5830 several times with many firmware, but no one worked, and the phone is still stuck in an infinite loop, in which I am not even able to see the samsung logo coming out at the very beginning.
I know many phones got bricked in this way, I wanted to know if anybody has been able to recover the phone or if anybody know any possible solution.
And if not, do you know if the warranty is covering this problem? I just got the phone a couple months ago; i have unlocked other devices before, but this is the first time I have experienced a problem so I am quite new about warranty as well. Please HELP ME
Merry Christmas guys!!!
Thanks in advance
Click to expand...
Click to collapse
if you can get into download mode im guessing there is some hope for you.
go here: http://droidangel.blogspot.com/2011/05/samsung-galaxy-ace-s5830-original-stock.html
look for: S5830XXKP9
and make sure you have odin 4.38 and flash with that.
try to install cwm and install a customrom
Sent from my GT-S5830 using xda premium
sfrat said:
Hi all,
I have looked for a similar post, I found out that many people experienced something like that trying unlocking their phones, but I haven't found out any solution.
Here is my situation:
I have tried to unlock my s5830 (orange spain carrier), I have used a method which it seems to be dangerous for the phone, but of course I have found out it was dangerous after I have already tried it
Anyway after I discovered the unlock number contained in the perso.txt file in the efs folder, my phone restarted without service once and after that it went in a bootloop mode, it goes on a download mode, but there is no way to get back recovery mode or a normal boot.
I flashed the s5830 several times with many firmware, but no one worked, and the phone is still stuck in an infinite loop, in which I am not even able to see the samsung logo coming out at the very beginning.
I know many phones got bricked in this way, I wanted to know if anybody has been able to recover the phone or if anybody know any possible solution.
And if not, do you know if the warranty is covering this problem? I just got the phone a couple months ago; i have unlocked other devices before, but this is the first time I have experienced a problem so I am quite new about warranty as well. Please HELP ME
Merry Christmas guys!!!
Thanks in advance
Click to expand...
Click to collapse
with the cellphone off, put out ur baterry for a minute, then maintain ur finger into the volume down button and the power button tell a friend or if u can alone insert the batery while quickly pressing volume down and power button to get into download mode, and flash.
Hehehe,bootloop is horrible,you just have to get in download mode & flash with 2.3.4 firmware with Odin,just that steps and you save your SGA.
I got bootloop many times and Odin saved me.
Sent from my SGA
robinandroid said:
try to install cwm and install a customrom
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
he cant go back in recovery mod............
If you can go to recovery mode than you can just wipe the data and cache. This saved me many times. Otherwise on what ever OS you may be , just create new user name after removing samsung android drivers. Login from new user name and than re install drivers again and now flash your phone from firmware which was installed on your phone before you bricked it. This helped me a few times.
dr_vishal said:
If you can go to recovery mode than you can just wipe the data and cache. This saved me many times. Otherwise on what ever OS you may be , just create new user name after removing samsung android drivers. Login from new user name and than re install drivers again and now flash your phone from firmware which was installed on your phone before you bricked it. This helped me a few times.
Click to expand...
Click to collapse
hey guys thanks for the answers, but unfortunately i am not able to reach the recovery mode, my phone just reach the download mode.....i will try with the xxkp9, even if i have already tried it...I guess i have tried at least 15 firmwares without any success
Helping to make your Christmas Merry
It seems that you've already received a lot of help for unbricking your device. So I'll try to help out in unlocking your phone after you finished unbricking it.
This is the method I personally used on my locked Ace:
http://forum.xda-developers.com/showthread.php?t=1335548
It's perfectly safe. 100%.
King Kaze said:
if you can get into download mode im guessing there is some hope for you.
look for: S5830XXKP9
and make sure you have odin 4.38 and flash with that.
Click to expand...
Click to collapse
I have tried the XXKP9 again, it is not working, as usual Odin ends to load the firmware and then it goes back in the endless loop mode....there is no chance to get it back?
franzks said:
It seems that you've already received a lot of help for unbricking your device. So I'll try to help out in unlocking your phone after you finished unbricking it.
This is the method I personally used on my locked Ace:
http://forum.xda-developers.com/showthread.php?t=1335548
It's perfectly safe. 100%.
Click to expand...
Click to collapse
thank you very much I will follow your advice...IF I will be able to get my phone back which seems impossible =(
@dr_vishal
Thank you first of all, I have tried to uninstall and reinstall the android device driver, but it doesn't seems to be the problem, Odin ends with a "PASS" at the end, I guess there still is comunication in the between the two devices...
Hopefully it will be a Merry Christmas =)
It's not impossible. I'm relatively new here but I have noticed quite a few "bricked" threads already. Most of them (if not all) have been able to fix their device. I haven't seen a single person permanently brick their device, so I would guess that your chances of fixing it are really high. Just be patient and keep describing your situation and more experienced help will certainly arrive. I'd really like to help out but I have no idea how to fix it as I have not experienced bricking my phone yet.
Anyway, if the method for unlocking I suggested works for you kindly press the Thanks Button. Merry Christmas!
franzks said:
It's not impossible. I'm relatively new here but I have noticed quite a few "bricked" threads already. Most of them (if not all) have been able to fix their device. I haven't seen a single person permanently brick their device, so I would guess that your chances of fixing it are really high. Just be patient and keep describing your situation and more experienced help will certainly arrive. I'd really like to help out but I have no idea how to fix it as I have not experienced bricking my phone yet.
Anyway, if the method for unlocking I suggested works for you kindly press the Thanks Button. Merry Christmas!
Click to expand...
Click to collapse
Thank you franzks!
I promise I will try your method and I am positive it will works, but I need to get my phone back...so I will add few new information I have found out talking to a friend of mine which has my same device and the same carrier as well.
The version built-in is:
GINGERBREAD.BVKQ9
S5830BVKQB
[email protected]#1
Any suggestion about the firmware I am suppose to flash in?
I am actually passing through all the version contained in the address droidangel you gave me...at the moment no one is working...I will keep trying...
sfrat said:
Thank you franzks!
I promise I will try your method and I am positive it will works, but I need to get my phone back...so I will add few new information I have found out talking to a friend of mine which has my same device and the same carrier as well.
The version built-in is:
GINGERBREAD.BVKQ9
S5830BVKQB
[email protected]#1
Any suggestion about the firmware I am suppose to flash in?
I am actually passing through all the version contained in the address droidangel you gave me...at the moment no one is working...I will keep trying...
Click to expand...
Click to collapse
Guys,
I am out of ideas, I have tried each single firmware I have seen around internet, no one is working, any tip or advice or suggestion?
I messed up with the efs, and I guess that's all, the phone is gone....now it needs a JTAG or whatever is its name....
maybe to get the warranty still valid I should broke totally the phone over charging it....??
sfrat said:
Guys,
I am out of ideas, I have tried each single firmware I have seen around internet, no one is working, any tip or advice or suggestion?
I messed up with the efs, and I guess that's all, the phone is gone....now it needs a JTAG or whatever is its name....
maybe to get the warranty still valid I should broke totally the phone over charging it....??
Click to expand...
Click to collapse
Did you try that?
http://forum.xda-developers.com/showthread.php?t=1153310
just a thought
a lot of people have talked about reflashing it and all but have you managed to get into the recovery mode at all once you have reinstalled the rom with odin? if you can get to that you just need to hit factory reset, wipe cache and wipe dalvik and normaly after that it will work fine... so far ive been stuck in soft brink 3 times and each time doing the wipes from the recovery mode has worked...
Pinting said:
Did you try that?
http://forum.xda-developers.com/showthread.php?t=1153310
Click to expand...
Click to collapse
I've tried to use the oneclick, but it seems it doesn't recognize the phone, since, i guess, it's made for a galaxy s.
The others are not my case, since I am able to get download mode, and all these are made to can get it back.
Anyway I found out a post in which the people were talking about the s5500, which apparentely is similiar to my device, and the owners of that model experienced a similar problem doing the same process....anyway in that post the people needed to use a Jtag, which is the only way to get it back....so I though it could be the same solution for my problem...but I don't know anybody with Jtag, so the only way is contacting the service center.
thanks anyway, when I will be back at home after Christmas I will try to find the ticket and I will probably try to get it back in warranty, since is preatty new...
@torchwolfery
I am not able to reach recovery mode, there is no way to get it back, even flashing the phone with different firmwares, all I got is download mode, and apparently that is completely pointless...since the only change in the phone behavior is that if i install a certain firmwares it doesn't even have the back-light working when it is stuck in bootloop.
Warranty is your only hope (as it was mine once and it worked).
I didn't think it was possible to brick these phones. There I have tried so much to try and brick it but I have not been able to as it still always goes into 'download' mode. The only advice I can give you is double check that you are using the correct version of Odin which is v4.38 and that you use cooper v1.0 as your OPS. If dont mind me asking, but exactly what did you do or do you remember the steps you took to brick it? What buttons are you using for 'recovery' mode.
Also please clarify if Odin is going in a loop or does the phone come on and then keeps rebooting? If it is the phone that keeps rebooting, then wiping cache and data partition should do the trick. This can be done by going into recovery mode (which I am aware you cannot get into) or if you can manage to get into the dialler quick enough before the reboot, by dialling *7267*3855# and that should format the relevant partitions (data and cahce) and bring it back to factory settings. Without further info, I cannot really tell exactly what the situation is.
The fact that you are getting 'download' mode, I dont think that it is bricked because it will still allow you to write the relevant directory/files to the relevant blocks. Either way, would be interested to know.
Hello people, thanks for reading and trying to help in advance hehe
ok here it goes ....
i bought a galaxy tab 10.1v "Australian Vodafone Version" a while back, and since me and other users that own this pices of **** didn't get updates and stuff i decided to "unlock+Root+rom". I did that successfully after following guieds:
unlock :http://forum.xda-developers.com/showthread.php?t=1064793
root+room: http://forum.xda-developers.com/showthread.php?t=1079781
Everything wsa fine and i had the super user and everything, but in the second guide it says it is recomended or something like that to download ROM Manager from the market which i did, and i started the app and and did a backup. My Tab rebooted to a blank screen , i waited for a while but with no luck so i turned off and tried to go to DW mode or recovery mood so i can at least connecte it to odin3 and do something. When press V- + Power theres no DW nor recovery mode all i see is one smmall line on the left top corner that says "Booting Recovery Kernal Image#"
When i plug the usb into my computer nothing happenes no sound , no new device installing no nothin. but since i have been reading alot regarding this issue, i read something about APX mode and NVflash here and many other websites but i followed this guide :
http://forum.xda-developers.com/showthread.php?t=1130574
i got my tab connected but i couldn't do NVflash because whenever i do
"--sync" or "nvflash --bl bootloader.bin --go"
i get this :
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
some say that that means the device is locked eventho i pretty sure it not because i had the lock logo. anyway ...
just to answer every possible question in advnce and give more info :
*its a 10.1v "Vodafone Australia Version"
*was working fine after root/rom
*stoped working after using the app "ROM Manager" (i think its not compactible)
* the device on somekinda boot loop, the screen would turn on and off "blank screen with nothing in it no sound also"
* pressing Volum down + Pwer will taking me to a blank screen with one little line that says "Booting Recovery Kernal Image#"
*when i plug the usb to the computer nothing hapenes
* in APX mod is working but i cannot do anytning since the NVflash won't work.
* I followed everything step by step
Does that mean my device is useless ? is there anyway to get it back to life ?
Thank you and sorry for the spilling mistakes as im using a F'ed up keyboard
one more thing i did :
I let the battery drain overnight and pluged charged it again hopeing that will help, the battery logo won't even show up, just a blank screen
thanks
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums & Read the Forum Rules
Moving to Q&A
lufc said:
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums & Read the Forum Rules
Moving to Q&A
Click to expand...
Click to collapse
ops sorry about that, my bad
Hi Barry. Welcome to XDA. One quick suggestion: If you want to get help in an enthusiasts forum, don't call the object of everyone's affections a "pices [sic] of ****."
We all understand the stress of having non-responsive electronics; but you'll catch more flies with honey...
***edit. Wrote some stuff for you only to realize that you're on a 10.1v. Not sure how I missed that in your title (and thus, I suppose I can't comment on whether or not it really is a POS!). Until just now I never realized how different your tab is from the regular 10.1 (guides are much more difficult to follow!) Anyways, I found these threads that might be useful to you:
http://forum.xda-developers.com/showthread.php?t=1083517
and
http://forum.xda-developers.com/showthread.php?t=1232664
Good luck!
slack04 said:
Hi Barry. Welcome to XDA. One quick suggestion: If you want to get help in an enthusiasts forum, don't call the object of everyone's affections a "pices [sic] of ****."
We all understand the stress of having non-responsive electronics; but you'll catch more flies with honey...
***edit. Wrote some stuff for you only to realize that you're on a 10.1v. Not sure how I missed that in your title (and thus, I suppose I can't comment on whether or not it really is a POS!). Until just now I never realized how different your tab is from the regular 10.1 (guides are much more difficult to follow!) Anyways, I found these threads that might be useful to you:
http://forum.xda-developers.com/showthread.php?t=1083517
and
http://forum.xda-developers.com/showthread.php?t=1232664
Good luck!
Click to expand...
Click to collapse
i apologize for that, but i was referring to my tab only ... anyways
thanks for your reply and for the links you gave me .. but still the biggest problem is i'm unable to connect my tab to odin, and downloading mode and recovery mode are not even there .. theyre all gone, only APX mode is working and even with that, NVflash won't work and i would give me this error
"Nvflash started
rcm version 0X4
Command send failed (usb write failed)"
if i could connect to odin i could actually do something, or even NVflash i could run bootloader and it would install image files and all.
i'm not sure if i can do anything with APX other than NVflash .. or if i could somehow bypass Nvflash error ..
i just have a feeling that my tab won't make it
Just an idea... did you try to do the work with another pc?
For example a fresh XP 32bit install on another pc.
This "usb write error" seems strange.
Max
gfreeman86 said:
Just an idea... did you try to do the work with another pc?
For example a fresh XP 32bit install on another pc.
This "usb write error" seems strange.
Max
Click to expand...
Click to collapse
Thanks for replying. .. Yes i tried with anither pc. . I have read in this forum and others that this error means that the tablet is somehow locked even tho it wasnt before i root/rom it
Its like not writable, ill install a freah xp pro and givr it another try since i tried only win win 7
Did you try to drain completely the battery and then charge?
http://forum.xda-developers.com/showpost.php?p=19519586&postcount=15
seems it worked for someone
gfreeman86 said:
Did you try to drain completely the battery and then charge?
http://forum.xda-developers.com/showpost.php?p=19519586&postcount=15
seems it worked for someone
Click to expand...
Click to collapse
Yes i did as i metioned in my post, didnt help
When i charged it after i drained the battery, the screen light will turn on but no battery logo or anything.. The only thing that would show up on the screen is when i try to enter downloading mod/recovery mod by pressing power+volume is a little line on the top right corner which says : " booting recovery image# "
thank you for your reply, what do you guys recommend since i can access APX mod, will i be able to do anthing other than nvflash in APX mod?
Since you are getting a usb write error as well as no charge indicator, is it possible that your USB cable is bad?
sgip2000 said:
Since you are getting a usb write error as well as no charge indicator, is it possible that your USB cable is bad?
Click to expand...
Click to collapse
thanks for your reply
when i charge, the tablet does charge but no Battery logo, i can tell its charging because the screen lights will go on.
what i have tried so far :
* installed APX but when i try to nvflash it says something like writing failed
* tried both windows XP and windows 7
* drained the battery twice for 2 days
* changed USB cable
* tried to connect it to different versions on odin but computer only recognise the device in APX mode
* device still showing ( booting recovery kernel image#) when a try to access DW mod.
it all started when i used a backup program after rooting it, i don't get .. is its a backup it shouldn't delete everything (the system) and brick the tablet...
whats Kernel ? << noob
any new ideas guys ? is there any other programs/methods out there ?
anyone have the same problem ?
thanks
-Bazza
When it says booting recovery kernel image, did you try to just wait for about 15 to 20 minutes to find out if it boots again, or try logcat command?
djden said:
When it says booting recovery kernel image, did you try to just wait for about 15 to 20 minutes to find out if it boots again, or try logcat command?
Click to expand...
Click to collapse
yes, i left it like that till the next morning
** update **
Today i disassembled my tab after i read somewhere in this forum that i might get it back if i take the battery out or unplug the screen cables. Some claim that the touch screen could cause the tab to go into a boot loop; however that didn't work
i decided anyway to buy a new tab either Asus Transformer or Galaxy 8.9, even tho I'm kinda worried that this thing could happen to my new tab when i try to root it and install roms. I don't want to spend that much money until i figure out the problem, so i'm making this tablet "A testing Device" i'm gonna test every possible way to revive it for me and and others. I'll do my best with your help guys to solve this so we can provide help for others.
There was a Guide here in this forum about JTAGing that tablet along with a software that some company use to unbrick devices but i cold not find it, my cousin owns a hardware store and i could use everything i need .. i just need someone to guide me.
Thanks
Sounds like a cool project, sorry it cost so much.
zBarry, You should try this while you can, It sounds simple as it is but it worked for both my tablets that had the 0x4 aka locked bootloader. Sorry if you had already "Lego" lized your tablet into pieces but this may help. :]
http://forum.xda-developers.com/showthread.php?t=1478361
bumb!
im still looking with no luck ... please help ?
can i do anything with linux ?
zBarry said:
bumb!
im still looking with no luck ... please help ?
can i do anything with linux ?
Click to expand...
Click to collapse
As far as I know linux won't help, what % is your tablet charge at? Since you've opened it already why not just de-attach the battery and reattach it back and try to power it directly into fastboot. Normally draining is the same as stopping the flow of current into the tablet. Unlike phones where you can pop out the battery you can't do it to the tab unless you've opened it.
Can you please let me know what steps have you tried so far? Would be nice to know in detailed So I can help you out at best.
Misledz said:
As far as I know linux won't help, what % is your tablet charge at? Since you've opened it already why not just de-attach the battery and reattach it back and try to power it directly into fastboot. Normally draining is the same as stopping the flow of current into the tablet. Unlike phones where you can pop out the battery you can't do it to the tab unless you've opened it.
Can you please let me know what steps have you tried so far? Would be nice to know in detailed So I can help you out at best.
Click to expand...
Click to collapse
i think i have third every possible way out there... and the steps that i did to revive the device your way was :
i taped the power button and left it for like 2 days, then i plugged it to the computer in APX mode to check if its drained or not, but i think it was charging off the computer. So i repeated the first step and left it for 3 days, then plugged it into the socket. after couple of mins the screen turned on, but no logo or anything, just black screen (same issue). i decided to disassemble the device to take the battery out which i did and yet same result. i had hope so i re-did the battery drain thing and left it for a week and when i plugged it i pressed pwr+ vlo + and something.
my tab turns on, but just a black screen it won't that up, and power + volume up will show me a kernel message.
thanks so much, i aprreciate your trying to help any other way you think i should try ?
What sort of kernel message do you get? As far as I know maybe perhaps the contact's arent touching properly? Seems to me you did everything right but when it turns on you don't get the charging icon.
The good part is the display works and atleast you can boot up *Somehow* the bad part is you can't get it into Fastboot mode.
As far as I know the tablet is supposed to light up but have you checked if you get the offline charge icon (That green battery that sits in the middle of the screen and charges?) once you get it to drain/disconnect you should leave it to charge via wall socket for about 5-10secs for that icon to pop up. If you get that icon atleast then you know you are getting somewhere
I wish I had the tablet in hand so I could see what's going on. The whole oceans away solution makes it hard to guess what's happening
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.
Well i got this tablet wanted to intall cynagon mod for that i need twrp i installed twrp transfered it to my tablet went into recovery and flashed twrp after it rebooted into TWRP the screen was all fuzzy then the menue came up i could'nt touch anything so i pressed the power buttom it said swipe to unlock but i couldnt touch anything so i held the power off button for 30sec it turn off i turn it back on and it was the exect same thing can someone help me please what do i do ? is it bricked?
viperasap said:
Well i got this tablet wanted to intall cynagon mod for that i need twrp i installed twrp transfered it to my tablet went into recovery and flashed twrp after it rebooted into TWRP the screen was all fuzzy then the menue came up i could'nt touch anything so i pressed the power buttom it said swipe to unlock but i couldnt touch anything so i held the power off button for 30sec it turn off i turn it back on and it was the exect same thing can someone help me please what do i do ? is it bricked?
Click to expand...
Click to collapse
Hi,
I was just wondering: Have you rooted your device and have you installed twrp for your specific device? (I know, sounds like a dumb question, but you'll be suprised how many people install wrong versions). Because if you have rooted your device properly, and you installed twrp (one for your device), then you should be just fine. But I'm afraid that you haven't, and that therefore the screen is all fuzzy. And also, is the screen fuzzy in the twrp menu, or when you are on (e.g) the homescreen? If the second option doesn't apply, then you are not bricked. Please answer and give as much information as possible on what you did, then I might be able to help you. (btw, it's very unlikely that you are hard-bricked and that your device won't be able to be repaired)
(and a happy new year )
pep18 said:
Hi,
I was just wondering: Have you rooted your device and have you installed twrp for your specific device? (I know, sounds like a dumb question, but you'll be suprised how many people install wrong versions). Because if you have rooted your device properly, and you installed twrp (one for your device), then you should be just fine. But I'm afraid that you haven't, and that therefore the screen is all fuzzy. And also, is the screen fuzzy in the twrp menu, or when you are on (e.g) the homescreen? If the second option doesn't apply, then you are not bricked. Please answer and give as much information as possible on what you did, then I might be able to help you. (btw, it's very unlikely that you are hard-bricked and that your device won't be able to be repaired)
(and a happy new year )
Click to expand...
Click to collapse
Yes i root my device before i installed twrp , when i boot my tablet twrp boots up the screens goes alll blurry / fuzzy with colors then it becomes normal recovery menue i installed twrp touch so i should be able to touch the setting but i can't i press the power button and a fuzze Unlock with ''Slide to unlock'' comes up but i can't slide to unlock it.. Oh yeah and it is upside down so i have to turn my tablet upside ..
I think[I know] i installed the wrong version of twrp which does not work for my device, Is there any way i could get rid of this recovery or factory reset?
What kind of tablet do you have? Does the bootloader support fastboot? If so you should be able to flash the proper recovery. If not does adb work when in recovery? You may be able to change it here. Also your OEM may have a download mode to flash firmware, this may be another option.
Sent from my Nexus 4 using XDA Premium 4 mobile app
I have a Allwinner A31 table to be precise ubonton u705a
I have tried adb but it just says [waiting for device] so I guess ADB does not work.
I don't know anything about bootloaders it had an option of fastbooting in the power menus if that means anything sorry for my lack of description Sent from my R800i using xda app-developers app
viperasap said:
Yes i root my device before i installed twrp , when i boot my tablet twrp boots up the screens goes alll blurry / fuzzy with colors then it becomes normal recovery menue i installed twrp touch so i should be able to touch the setting but i can't i press the power button and a fuzze Unlock with ''Slide to unlock'' comes up but i can't slide to unlock it.. Oh yeah and it is upside down so i have to turn my tablet upside ..
I think[I know] i installed the wrong version of twrp which does not work for my device, Is there any way i could get rid of this recovery or factory reset?
Click to expand...
Click to collapse
I think the easiest would be to just install the right version, the same way you installed this version. You are still able to connect your device to your pc, I guess, so you should be fine. To go back to your stock recovery, find the stock recovery for your device (you can probably find it somewhere here on the forums), and flash it.
Hope this works and good luck
pep18 said:
I think the easiest would be to just install the right version, the same way you installed this version. You are still able to connect your device to your pc, I guess, so you should be fine. To go back to your stock recovery, find the stock recovery for your device (you can probably find it somewhere here on the forums), and flash it.
Hope this works and good luck
Click to expand...
Click to collapse
Ok thank you for your help I figured it out thanks !! Happy new year 2014!
viperasap said:
Ok thank you for your help I figured it out thanks !! Happy new year 2014!
Click to expand...
Click to collapse
Glad I could help, you too!
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