Related
Hi all,
I installed a kernel on my phone so that I was able to Root my device.
My phone was booting up and I saw the yellow explenation mark underneath the the Samsung Galaxy S II logo.
There's only one issue, my phone won't start, it freezes at the boot logo and won't do a thing :/
How can I fix this?
It freezes or is it in a bootloop?
If you got into bootloop, check out this thread http://forum.xda-developers.com/showthread.php?t=1108499
see this !!!
Dark Emotion said:
It freezes or is it in a bootloop?
If you got into bootloop, check out this thread http://forum.xda-developers.com/showthread.php?t=1108499
Click to expand...
Click to collapse
It won't enter in Recovery mode,
When i hold down home, power, and volume UP the bootup-logo (Samsung galaxy S II ''With Explenation mark) shows up, than dissapears for 1 second than shows itself again and it's just freezes like it did before.
Now I never heard about a Boot Loop but this looks very disturbing.
I need some help with this.
Jeezus Christ, you joined today and already posted in the wrong section, didn't bother to read or search. So on that note I HOPE your device is Bricked just to serve you a purpose of reading before hand.
However since you are unable to read or search, we will treat you like a child. Your device is not bricked. Turn it off, take out battery, unplug from computer. Put back in battery and press volume DOWN, power and home until you get into download mode. Then plug into computer, start odin and either reflash the kernel in PDA box, or flash a stock rom.
Now this is been covered numerous times, so I will ask again to read next time before you post a question that has been answered 10000x times over.
Also if you would have read anything at all, you would know that you will get the yellow triangle when flashing any kernel but a stock on. There is a way to get rid of it, but that requires searching and reading. Something you know nothing about.
Sent from my Cognition powered SGS2
antiochasylum said:
Jeezus Christ, you joined today and already posted in the wrong section, didn't bother to read or search. So on that note I HOPE your device is Bricked just to serve you a purpose of reading before hand.
However since you are unable to read or search, we will treat you like a child. Your device is not bricked. Turn it off, take out battery, unplug from computer. Put back in battery and press volume DOWN, power and home until you get into download mode. Then plug into computer, start odin and either reflash the kernel in PDA box, or flash a stock rom.
Now this is been covered numerous times, so I will ask again to read next time before you post a question that has been answered 10000x times over.
N00b.
Sent from my Cognition powered SGS2
Click to expand...
Click to collapse
At first I would like for you to tone it down a little bit, I searched down the whole Internet, I just didn't now under what name I had to search.
Since I don't know the name of this particular issue, I couldn't find it on this website nor on the Internet (wich is obvious). So I started a treath to release my question.
Before claiming and occusing me of something, aks me the questions first.
You're judging a book by it's cover and your arrogance blind you.
But i'm not here to occuse people of something or giving them names etc, I'm here for some serious bussines.
Now...
I saw your answer (possible solution) and I wan't to thank you for this, I will give this a try and keep this treath updated.
antiochasylum said:
Jeezus Christ, you joined today and already posted in the wrong section, didn't bother to read or search. So on that note I HOPE your device is Bricked just to serve you a purpose of reading before hand.
However since you are unable to read or search, we will treat you like a child. Your device is not bricked. Turn it off, take out battery, unplug from computer. Put back in battery and press volume DOWN, power and home until you get into download mode. Then plug into computer, start odin and either reflash the kernel in PDA box, or flash a stock rom.
Now this is been covered numerous times, so I will ask again to read next time before you post a question that has been answered 10000x times over.
Also if you would have read anything at all, you would know that you will get the yellow triangle when flashing any kernel but a stock on. There is a way to get rid of it, but that requires searching and reading. Something you know nothing about.
Sent from my Cognition powered SGS2
Click to expand...
Click to collapse
Every hear the phrase, 'lest you have something positive to say, be silent.'
I'm gathering not.
Sure, he's new. Sure, he isn't supposed to post here.
Belittling him is, I assure you, productive only in YOUR universe.
What is with the freaking attitudes in XDA as of late? If you don't want to reply, don't. No one is forcing you to.
The kicker here: I'm just about as sick of seeing people post in the wrong area as I am about people complaining about people posting in the wrong area.
So on that note I HOPE your device is Bricked just to serve you a purpose of reading before hand
Click to expand...
Click to collapse
Wow.. Wishing loss to someone? Nice.
L A X said:
It won't enter in Recovery mode,
When i hold down home, power, and volume UP the bootup-logo (Samsung galaxy S II ''With Explenation mark) shows up, than dissapears for 1 second than shows itself again and it's just freezes like it did before.
Now I never heard about a Boot Loop but this looks very disturbing.
I need some help with this.
Click to expand...
Click to collapse
I had the same problem few days ago.
For me the logo showed up, disappered, showed up again and than it went in recovery. Hold those 3 buttons until phone goes in recovery mod, don't stop holding them.
mostyle said:
Every hear the phrase, 'lest you have something positive to say, be silent.'
I'm gathering not.
Sure, he's new. Sure, he isn't supposed to post here.
Belittling him is, I assure you, productive only in YOUR universe.
What is with the freaking attitudes in XDA as of late? If you don't want to reply, don't. No one is forcing you to.
The kicker here: I'm just about as sick of seeing people post in the wrong area as I am about people complaining about people posting in the wrong area.
Wow.. Wishing loss to someone? Nice.
Click to expand...
Click to collapse
Yes wishing loss, due to lack of reading. If you notice my reply I did offer help. Just had to ensure he posts in the correct section next time. And as for your phrase you said. Never heard it.
It's called constructive criticism. Bet me he will search before making another post. Otherwise I will be lurking in the darkness.
Oh and don't like my reply? Don't really care.
Sent from my Cognition powered SGS2
Dark Emotion said:
I had the same problem few days ago.
For me the logo showed up, disappered, showed up again and than it went in recovery. Hold those 3 buttons until phone goes in recovery mod, don't stop holding them.
Click to expand...
Click to collapse
It's called download mode. NOT recovery.
Sent from my Cognition powered SGS2
antiochasylum said:
Yes wishing loss, due to lack of reading. If you notice my reply I did offer help. Just had to ensure he posts in the correct section next time. And as for your phrase you said. Never heard it.
It's called constructive criticism. Bet me he will search before making another post. Otherwise I will be lurking in the darkness.
Oh and don't like my reply? Don't really care.
Sent from my Cognition powered SGS2
Click to expand...
Click to collapse
If you read my post to you correctly, I did searched before posting, I just did not know what the name of the problem was.
antiochasylum said:
It's called download mode. NOT recovery.
Sent from my Cognition powered SGS2
Click to expand...
Click to collapse
You are wrong... step 2 says: Hold down home, power, and volume UP. This will enter recovery mode. If you are using CF-Root, you'll get CWM recovery. If not, you get stock recovery. It doesn't matter which appears.
As I said, you should enter recovery
Yes wishing loss, due to lack of reading. If you notice my reply I did offer help. Just had to ensure he posts in the correct section next time. And as for your phrase you said. Never heard it.
It's called constructive criticism.
Click to expand...
Click to collapse
It's called belittling, but I wont debate semantics.. lost cause I fear.
Bet me he will search before making another post. Otherwise I will be lurking in the darkness.
Oh and don't like my reply? Don't really care.
Click to expand...
Click to collapse
Totally unsurprised.
The only thing your post insures to me is a proficiency in rudeness. I know, you don't care.
Have a good life.
Dark Emotion said:
You are wrong... step 2 says: Hold down home, power, and volume UP. This will enter recovery mode. If you are using CF-Root, you'll get CWM recovery. If not, you get stock recovery. It doesn't matter which appears.
As I said, you should enter recovery
Click to expand...
Click to collapse
No it won't go in Recovery mode unfortunately.
I think my phone is bricked as I noticed the ''Phone...!...Computer'' logo when I tried to start it up.
Can happen, now It's just the challenge to find the solution.
Perhaps I should go to the store and tell them if they can help recover it.
If you got any suggestion what I should do it would be wel used.
In the mean time I will earch on the Internet and the forums how to unbrick the phone by myself.
Note - I still can enter Download Mode.
L A X said:
No it won't go in Recovery mode unfortunately.
I think my phone is bricked as I noticed the ''Phone...!...Computer'' logo when I tried to start it up.
Can happen, now It's just the challenge to find the solution.
Perhaps I should go to the store and tell them if they can help recover it.
If you got any suggestion what I should do it would be wel used.
In the mean time I will earch on the Internet and the forums how to unbrick the phone by myself.
Note - I still can enter Download Mode.
Click to expand...
Click to collapse
Did you have a custom rom installed before you ended like this?
Did you even try DOWNLOAD MODE? You dont not need recovery. You need download to flash the kernel again or a stock rom.
VOLUME DOWN, HOME, POWER until you see the "downloading, do not turn off"
Then connect to odin and reflash the kernel in PDA
Dark Emotion said:
You are wrong... step 2 says: Hold down home, power, and volume UP. This will enter recovery mode. If you are using CF-Root, you'll get CWM recovery. If not, you get stock recovery. It doesn't matter which appears.
As I said, you should enter recovery
Click to expand...
Click to collapse
Thats just the thing, the phone wont go past the triangle, meaning a bad odin flash. So recovery wont do **** for him. he needs download.
READ my post. ****.
antiochasylum said:
Thats just the thing, the phone wont go past the triangle, meaning a bad odin flash. So recovery wont do **** for him. he needs download.
READ my post. ****.
Click to expand...
Click to collapse
Than, maybe, just maybe you could try to explain to him how to do it... As I said, I can't help him because I am not that much experienced.
antiochasylum said:
Did you even try DOWNLOAD MODE? You dont not need recovery. You need download to flash the kernel again or a stock rom.
VOLUME DOWN, HOME, POWER until you see the "downloading, do not turn off"
Then connect to odin and reflash the kernel in PDA
Click to expand...
Click to collapse
antiochasylum said:
However since you are unable to read or search, we will treat you like a child. Your device is not bricked. Turn it off, take out battery, unplug from computer. Put back in battery and press volume DOWN, power and home until you get into download mode. Then plug into computer, start odin and either reflash the kernel in PDA box, or flash a stock rom.
Sent from my Cognition powered SGS2
Click to expand...
Click to collapse
Dark Emotion said:
Than, maybe, just maybe you could try to explain to him how to do it... As I said, I can't help him because I am not that much experienced.
Click to expand...
Click to collapse
Really? Both of those posts explain how to do it. **** it people dont want to listen to me. Have fun trying to fix it.
Dark Emotion said:
Did you have a custom rom installed before you ended like this?
Click to expand...
Click to collapse
No,
It all happened after I installed a costum-kernel (The one that I need in order to root my phone) I followed the instuructions of a Youtube webpage.
I did root my phone before to try it out and it worked smoothly.
After I realised that I could so much once a SuperUser i wan't it to Root my phone again but it all went wrong when my phone was rebooting after I installed the costum-kernel.
I went into Download mode, I tried to install the latest firmware on my phone, yet it failed to do so, so i plugged out my phone, shut it off, turned it on and all of a sudden I saw the *Phone...!...Computer* logo wich (if i am correct) stands for a (Soft)brick.
I re-installed the costum-kernel and the Brick-Logo isn't visible anymore, but I'm back at the previous problem, The Samsung Boot Logo with Explenation Mark freeze issue.
Once I entered Download mode I noticed that Costum Binary Download is set to (Count 5).
I need a good tutorial how to fix this, I'm quite new with the Android (half a week)
Help is well appreciated.
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
To sum it up with what happened over all. I went through several attempts at rooting with none of them working, including attempting several of the recommended ways on reddit which didn't work. I ended up using ODIN a few different times and eventually was hit with a ROM that made my search/back buttons no longer work and my home button turn into a back button. So I attempted to try Un-root it using a one-click rooter with an unroot feature. After trying that I was thrown into a loop where no matter how many times I restart my phone it takes me directly to the clockworkMod screen with orange text. When this happens I can still scroll using the volume up/down buttons but when I click power to try to select one of them what happens is that the selection screen will disappear and I'm left with only the background image of the clockworkMod screen.
Ideas? Suggestions? So far my only idea is using a USB Dongle Jig from Ebay to force it into download mode to try a proper rom I know works.
Try to flash it with flashtools (with a ttf file) the official firmware). If that is not working i would reconsider using a flash station.
Mind explaining how I could pull that off? I'm not that good with androids.
IBreakAndroids said:
To sum it up with what happened over all. I went through several attempts at rooting with none of them working, including attempting several of the recommended ways on reddit which didn't work. I ended up using ODIN a few different times and eventually was hit with a ROM that made my search/back buttons no longer work and my home button turn into a back button. So I attempted to try Un-root it using a one-click rooter with an unroot feature. After trying that I was thrown into a loop where no matter how many times I restart my phone it takes me directly to the clockworkMod screen with orange text. When this happens I can still scroll using the volume up/down buttons but when I click power to try to select one of them what happens is that the selection screen will disappear and I'm left with only the background image of the clockworkMod screen.
Ideas? Suggestions? So far my only idea is using a USB Dongle Jig from Ebay to force it into download mode to try a proper rom I know works.
Click to expand...
Click to collapse
Please search and read up on what you are doing. You buttons being messed up was do to the wrong kernel for your device. Also if you would like help it might be nice to know what device you are using.
zelendel said:
Please search and read up on what you are doing. You buttons being messed up was do to the wrong kernel for your device. Also if you would like help it might be nice to know what device you are using.
Click to expand...
Click to collapse
I'm using the Samsung Android Galaxy S II SGH-i777
Account removal
Deleted
I can't do that, I have no way to get to the ODIN/Download screen, only the recovery screen it auto-boots to.
IBreakAndroids said:
I can't do that, I have no way to get to the ODIN/Download screen, only the recovery screen it auto-boots to.
Click to expand...
Click to collapse
Read and follow this thread
http://forum.xda-developers.com/showthread.php?t=1286432
No just try to finish the process they are not doing anything until they are out in the proper place and in the sdcard they are not doing anything
there's no possibility to flash some other's nandroid?
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Hi everybody, i'm Riccardo, from Italy, and i've just bought this amazing tablet, Kindle Fire HDX "7.
I've tried to follow the steps in order to root the device, but i think i've screwed up everything lol
It literally won't start, when i push the power button, appears a black screen with only written "Kindle fire", without "HDx" or whatever it was, as it happened before. And this written won't fade, it lasts forever
I've tried to reset to factory defaults, with a manual way ( 20 secs double pushing bottons power and up ) but, after the process, it doesn't boot anyway.
Is there some drastic way to reset everything, maybe through computer or usb devices?
I hope I were as understandable as possible... sorry for my bad english
And i also hope that is allowed to speak of rooting situations
Sanatrax said:
Hi everybody, i'm Riccardo, from Italy, and i've just bought this amazing tablet, Kindle Fire HDX "7.
I've tried to follow the steps in order to root the device, but i think i've screwed up everything lol
It literally won't start, when i push the power button, appears a black screen with only written "Kindle fire", without "HDx" or whatever it was, as it happened before. And this written won't fade, it lasts forever
I've tried to reset to factory defaults, with a manual way ( 20 secs double pushing bottons power and up ) but, after the process, it doesn't boot anyway.
Is there some drastic way to reset everything, maybe through computer or usb devices?
I hope I were as understandable as possible... sorry for my bad english
And i also hope that is allowed to speak of rooting situations
Click to expand...
Click to collapse
Check the unbricking guides in the General forums.
Curious
Sanatrax said:
Hi everybody, i'm Riccardo, from Italy, and i've just bought this amazing tablet, Kindle Fire HDX "7.
I've tried to follow the steps in order to root the device, but i think i've screwed up everything lol
It literally won't start, when i push the power button, appears a black screen with only written "Kindle fire", without "HDx" or whatever it was, as it happened before. And this written won't fade, it lasts forever
I've tried to reset to factory defaults, with a manual way ( 20 secs double pushing bottons power and up ) but, after the process, it doesn't boot anyway.
Is there some drastic way to reset everything, maybe through computer or usb devices?
I hope I were as understandable as possible... sorry for my bad english
And i also hope that is allowed to speak of rooting situations
Click to expand...
Click to collapse
What method were you using root?
The same issue like mine. My hdx unbricked by a local vendor with a OEM software. So please don't give up.
Sent from my KFTHWI using XDA Free mobile app
jimyv said:
What method were you using root?
Click to expand...
Click to collapse
i've followed the guide that i've found on this forum, i'm actually not able to find it right now :asd:
Root was ok, the real problem was popped out after my vain try to install google play store, following this guide http://forum.xda-developers.com/showthread.php?t=2787813
What kind of unbrick tools should i use for? I looked for, but i didn't find anything...
have root and adb?
Sanatrax said:
i've followed the guide that i've found on this forum, i'm actually not able to find it right now :asd:
Root was ok, the real problem was popped out after my vain try to install google play store, following this guide http://forum.xda-developers.com/showthread.php?t=2787813
What kind of unbrick tools should i use for? I looked for, but i didn't find anything...
Click to expand...
Click to collapse
Do not FACTORY reset first then try this http://forum.xda-developers.com/showthread.php?t=2792225
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