Related
I AM IN NO WAY SAYING THIS ACTUALLY WORKS!
THIS THREAD WAS CREATED TO PROVE THIS EITHER TRUE OR FALSE!
I personally have never bricked a phone, so didn't do this and cannot really confirm it, but reading over the thread it seems like it has worked for numerous people. The only problem with this is I would have imagined it would have blew up and everyone would know. If this does work, I wanted to share it. I understand how much a bricked device can get under one's skin. Anyways, it's also an older thread. (From 14th October 2009) Found it playing around in Sapphire Android Development but here's the thread:
http://forum.xda-developers.com/showthread.php?t=571457
Any thoughts on this? Some people say it worked, so people say it didn't. One guy said keep pulling cord out then plugging in and it will eventually catch it and install. I want to try and get this more out in the open and see if it actually does work, or if it doesn't.
I'm not trying to post spam, or raise hopes and just crush them. If this works, though, I want EVERYONE to know about this, if it doesn't - it was worth a try.
EDIT: I forgot to put this - I also want to know what an actual brick is. Is it actually where the phone won't turn on at all? If so - this isn't for a brick. However, the most common way I hear "brick" referred to as is "phone won't get into recovery, bootloader, or boot." If a brick is where your phone won't turn on - this is not for you. Once again, though, if you can get to splash screen this may be able to save you!
I've tried this method for a while with no provail, atleast on windows 7. It seems that some people can get their devices reconised by their operating systems while others cant, if this is the case then possibly fastboot can reflash it. Mine charges the device but does not identiy it at all.
Hi all,
Firstly apologies for the long post, and thanks for all the info that is up here... however I have managed to get quite lost. I'll try to take you though the whole story as much as I understand it, but I woke up this morning and decided (after 8 months) to finally root my android.
That was 8am, it is now midnight, and I've had sandwiches while working at it, all day. It has been in various stages of bricked, and I think I might have just sent it back that way - should not be playing with it when tired.
Things I have
1 x UK Vodafone HTC Magic, doing return plus power = 32B, HBOOT-1.33.0009 (another story here).
1x 16GB SD-HC card
1x 1gb Card
1x cheap nokia I can use as a reader for the 1gig card, but it can't handle SD-HC
Anyway I started off with the 1 click root idea, which obviously doesn't work these days, so followed the next link, then the next, finding I need to do the 'goldcard' method.
theunlockr.com/2009/08/14/how-to-root-your-mytouch-3g/comment-page-3/
Anyway I'm not sure where all the time has gone (16 hours now), but I have learnt what an SPL was, flashed mine to an ‘imperfect’ one, managed to flash it to deteethed google, then cyanogen on top, but it would never boot, and just hangs saying HTC Magic, then managed to flash it using 'myhero' which gave me a Hero like phone.
However I now seem to have messed it up again as I'm determined to do the cyanogen mod - I really want to be able to tether, and lots of other bits and pieces.
The state at the moment therefore is I have it all working with fastboot, and can easily get the Amon_RA recovery image going, but the cm_recovery one makes it hang and do nothing. If I try and replace the recovery section using fastboot it tells me it has failed (I forget the exact message).
I can therefore upgrade things using the Amon_RA backup, but as I said things don't seem to entirely work, and at the moment my phone is hanging (I think as I'm tired I've overwritten my backup). I'm also not sure if this goldcard method is working – I asked a question in the thread and it seems that it might not be.
I guess I'm just looking for a few pointers, after 16 hours sat here I'm generally pretty frustrated and totally lost - there is a lot of information, but there are so many permutations of hardware, and a lot of the information is now out of date. Trying to take everything in as well as deal with a specific problem may actually be beyond me Which is something I hate- being the newbie needing help with a potentially simple problem (though I have had a good go at it).
I'm really not sure what stage the phone is at, have I rooted it? After all I can use the myhero rom, but on the other hand I can't do what I want to do, so therefore is there a problem? Exactly which step makes it ‘rooted?’ as every guide is obviously a chain of events to make it in to something else. I'm honestly not sure, but it isn't a fun feeling – I’m stressed and at the momentI have no phone just a brick that I can fastboot to recovery, and a bunch of backups as soon as I get it working again.
I really had no idea it would be this difficult, and am a big angry at Google/HTC for making it so - it is easier to get Hackintosh working than this! I’ve also managed to do hundreds of other similar things without any problem – Xbox Media Center (including soldering), and a few more spring to mind, all to use the hardware I already own! My hardware!
Anyway advice and pointers are appreciated, as although I've learnt a lot today, I'm still blundering about, and it is a matter of time until I cause serious damage in my attempts to make it better, al alternatively just throw in the towel, but then I don’t think I can go back as I have a horrible feeling that the restore I did didn’t work.
Again anything you can offer is appreciated, and if you need more detail, I’ll do what I can!
Anthony
Also just to add I've tried searching, which is partially how I've got myself in to this mess - solve one problem but make another!
Also I do have my APN settings, so when I get it installed, I can get my google account workign with it - I think i've had to do this about 6 times now! So if there is a way to get it in to 'myhero' which I think I can do again, and download an apk, then I should be able to do that.
Ant
There is a lot of information and everyone is recommended to do their research before rooting the phone.
That being said, it sounds like your phone is rooted if you can boot into recovery and load up a sense ROM. It'd been much easier to follow cyanogen's wiki instructions for non T-mobile 32B Magics. I also have a vodafone Magic and I rooted my phone successfully using the method.
Not having used the goldcard method, I don't exactly know where it went wrong. Have you done full wipes before applying a zip file? Stuff like that which might be easily overlooked?
Yeha I've been wiping it all before flashing, so that isn't the problem.
I also did as much reading as I could before starting (and watching the youtube guides before doing anything), but I guess a lot of the problems were unexpected (aren't they always?), for example I only found out half way through that I would need to flash the SPL, and it took me 40 minutes to figure out what SPL was, and what it did, then another 40 to work out how I was going to do it, then 40 to do so.
I have been following guides though - for the cyanogen one I get all the way down to flashing it with the detoothed google build, then cyanogen (obviously wiping before doing these). All the steps appear successful but then it doesn't boot.
The phone is also a rather strange one, a vodafone branded one that says 32B, but I'm sure it has more RAM.
Currently trying 'method 2' from here
android-dls.com/wiki/index.php?title=Magic_Rooting
to see if that works, but I'm not optimistic.
Yup 15 minutes laters same problem - it hangs on HTC magic screen, which is exactly what it does when I go for the Cyanogen one.
I'll goign to try and google for other roms, see if any of them work sucessfully (and might provide a bridghe to what I want to have.
Again however anybody knows good guides, sites or anythign else let me know.
As I said a big problem before is I'm reliant heavily on google, and a lot of the informaion out there is useless, as it is out of date in a big way. Also I don't know anyoen else who has doen this, so recommendations ofmethods/roms are dependent on my reading, not wword of mouth (which is generally better).
Ok I've tried the method 2, defiantely no sucess, went back to the myhero (which performs awfully, so much lag!), and have now tried flaskrec.apk on there.
It does not backup, but then bypassing that step, it gives me the error 'Flash failed'.
Really stuck now, and no idea what to try, any suggestions at all would be helpful. I'm almost at the stage of wishing I'd got an iphone :-(
Hi Everyone,
I searched and read many threads but didn't see my problem listed. I apologize if it has and I missed it. I received a Kindle Fire for Christmas yesterday. I plugged it in and let it reach a full charge. I then went through the registration steps. Upon completing registration, it automatically went to an updating screen. I left it alone to finish updating. After returning over an hour later I find it stuck on the "kindle fire" black screen. I've tried many hard resets but it always boots to the same black screen.
As I mentioned, it was brand new and I did not attempt to do any rooting or custom installs. If I plug it into my computer, Windows XP recognizes a device but does not having any drivers to install for it. Is there anything I can do to unbrick it?
Thank you in advance.
if u didnt install any roms like cm7 or havent even rooted it yet then its probably a hardware prob.. Try holding down power for like 20 secsand see what happens
Thanks for the suggestion movieaddict, but I've tried that many times now and it still just brings up the kindle fire screen.
Not as helpful as I would like a post to be, but I've had it freeze on that screen a few times as well and a hardware reset has always fixed it. If you have not rooted or done anytthing to void your warranty I see no reason to not contact amazon customer support as it is their problem to fix and hopefully they can, or get you a new one in a hurry. Good Luck, I know this is frustrating, my first one had a flickering line on the lcd and had to be rma'd.
Sent from my Epic (sleeper rom) using XDA App
Thanks Kapurnicus. I've already placed a called to Amazon and they are sending a new one and it should arrive later this week. I just thought I could play around and possibly fix this one in the meantime.
I don't blame you. Might as well try. Sorry I couldn't be of more help, mine is still stock lol. I only screw with the phone for now. Just have a new launcher and some streaming apps on the kindle, although, I still love it. Haven't put it down in days. Its going to be your best friend lol.
Sent from my Epic (sleeper rom) using XDA App.
I hate to have to write this asking for help but I wasn't able to use the other posts I found to help me. The directions for touchnooter seemed straight forward, but I am stuck anyway. Here is what I did and what is happening, and what I have tried to remedy situation. It is a bit long, but I wanted to be as complete as I can.
I have a new nook bought at end of March so assuming it has latest update. I followed directions and was able to get touchnooter onto microsd card. I stuck it in nook and turned on. I got an instruction screen saying to take card out when screen goes black and reboot. My screen did go dim but you could still see the writing behind. I wasn't sure if this what they meant by going black or if I was waiting for complete darkness. I think I panicked for a second (don't know why) and might have rebooted with the card still in (would this have created a problem that I will be describing).
So upon rebooting, it goes through the same reboot nook screen, gets to a screen with an n and the balls and that is the furthest I have gotten it. Messing with the power key seems to initiate a reboot, but it still never makes it past the n screen. Cannot turn off the nook. I was able to get it to give me the factory reset message by doing the failed reboot 8 times. I tried that a couple times but wasn't able to get any further past the screen with the n, so it seems it may not be doing any resetting. I tried repeating the rooting process (except for the shuting down the nook part since I can't actually get it to shut down) and it gave me the same rooting instruction page but no change the problem of not getting past n screen.
I have seen people asking similar questions about rooting with something else called CNW or something because the touchnooter didn't work for them but I didn't understand the instructions and wanted to get help first before trying something else. I had also read that there is something called a factory restore, which is supposed to be different from reset but I don't know how to do that. I downloaded barnes and nobles latest update thinking I would just reload it/ but I can't see my nook from my computer (do I need to download some drivers? Or is this because it can't get past the n screen?). I tried using a different microsd card in case the first was faulty, but didn't help.
Does it seem there is something wrong with the touchnooter content on the card, like maybe it doesn't work with the latest nook update? Also wanted to mention, I did not do a backup before trying to root. I originally planned to but after I was done researching what I needed to do and got to the touchnooter downloading directions, they didn't mention it, so I didn't do it (besides that, I don't know how to do it and don't know if it would help in this situation anyway). Could it be that the nook itself has a problem?
Anyway, I would still like to root but would be happy to at least get a basic nook back. If you have made it this far in reading my problem, what do you think I should try? I am thinking of taking it back since I don't think it actually rooted but if I can fix it, that would be better. Thanks in advance for anyone who takes the time to work on this with me. I wish I had someone right in front of me to ask questions to but this the next best thing.
Thanks!
Tara
I am really leaning towards just seeing if I can return it. The instructions for touchnooter seemed so straight forward and I thought I could handle it. Since it didn't work and I don't even know if it was a problem with something I did, the device, or the touchnooter (since other people with new nooks are having similar problems), then I don't even know if it is something that will work at all. Trying to use some of the other methods are just way beyond my ability without more detailed instructions. Sigh.
http://forum.xda-developers.com/showthread.php?t=1289233
Should help You to restore to factory state. After You can use any other ways to root(if You want )
PS: From what You say, You haven`t done anything irreversible yet. So calm down reread the forum and go on
Thanks for the reply! I did come across that at one point but didn't try it. But I will give it a go once I get the nook charged (it discharges by the end of everyday while having this prob so I have to charge it back up everyday). These directions look pretty straight forward though, so I am crossing my fingers.
"I did not do a backup before trying to root...besides that I don't know how to do it and don't know if it would help in this situation anyway."
After you get your Nook back to stock state don't shy away from making the backup. And do it before you make any other changes. Having a pristine image of your Nook's original state will make you nearly bulletproof. Give yourself time to understand the issues involved in making the backup. This new knowledge will generalize to other aspects of rooting.
The instructions for making the backup are here but you may find this isn't enough information. I found this post from Renate extremely helpful.
Finally, it will be helpful to know that, done correctly, your Nook v.1.1.2 backup will be exactly 1,958,739,968 bytes.
Efemmeral said:
Finally, it will be helpful to know that, done correctly, your Nook v.1.1.2 backup will be exactly 1,958,739,968 bytes.
Click to expand...
Click to collapse
Depend on nook memory chip used (manufacturing date) it should be either 1,958,739,968 or 1,962,934,272 bytes
ApokrifX said:
Depend on nook memory chip used (manufacturing date) it should be either 1,958,739,968 or 1,962,934,272 bytes
Click to expand...
Click to collapse
Yes? I have always gotten 1,957,616,640.
Hmm, mine is 2.000.683.008.
EDIT: I think that was 1.1.0 (or 1.1.1?)
Hello Guys,
I am posting this thread with a great deal of frustration and of course i'll try to leave the emotions out of this, although it's pretty hard (since that's NOT how i imagined i'll unbox the OPT which i was waiting for, for so long).
Anyways,
I'll cut to the point, I received my OPT package and happily went a head opened the box (hoped not to get a broken phone or anything (like someone who posted a thread here), and indeed the package looked okay and the device looked good (physically speaking).
I started the phone, and i can see the black background white android logo, and then.. Black Screen... I'm telling myself "Ahh that's probably nothing.. let's wait a bit or worse case another restart" waiting didn't help and as you probably know restarts did not help as well.
Okay, since i am not newbie to the android troubleshooting, i said to myself, probably a bad OS boot or some sort of OS issue, let's enter the RECOVERY to reset / wipe / factory reset.
Volume Down + Power Button, can't enter recovery just a Black Screen showing.
Starting the phone again regularly shows the Black Screen but the buttons are glowing blue and if i click on the volume buttons i can hear the sound tick.
Okay, at that point i was getting a bit worried, no recovery, several reboots and Black Screen when going to recovery or normal mode.
So now, i knew i had to go over and search the forums (XDA | One Plus) for more solutions on soft bricked / hard bricked devices.
I found the restoration thread of:
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
Including the QualCom driver method and 2 FULL restoration kits (1 Hidro OS 1 Oxygen).
I followed the steps (trying first the lighter Hidro Kit (without .img's of system etc') finished the process but when it should logon to recovery SAME result.
Then i went ahead and tried the OxygenOS recovery kit, same procedure it finished, phone restarting but same Black Screen.
This is where i am at right now, very frustrated, i raised a TT to the one plus support, i will update how it goes, i assume i passed most of the troubleshooting phases but if anyone has ANY ideas on how to proceed or assist i would be glad to try it out.
In addition i will use this stage to also update on the OnePlus support (refund wise, and TT dealing wise) as i think it's also important to report on the support when actual problems occur and how they handle it.
In any case guys, thanks for reading this, i really hope you will receive your products WORKING as they should, there's not much worse things when it comes to getting a NEW device starting it for the first time and not being able to use it, after waiting for so long for it.
--Video is also attached below.
https://dl.dropboxusercontent.com/u/33088939/20151005_132402.mp4
I will keep you updated.
Thanks & Regards,
Rest in peace. Contact Oneplus support m8 and send that **** back
Sent from my ONE A2003 using XDA Free mobile app
Small Update: I just wish you all to never wait for the OP customer service / technical support. (waiting time is really outrageous for a company which support customers online).
In addition, the technical support team sent me files to download (while i'm explaining her that i tried all of those already) + sending me ROM for OPO (Cyanogen........)
I was in a kind of a shock, while i'm correcting her and telling her there's no CM for OPT and the files she sent me (CM11s?!) are not the correct ones, she sent another mail.
Anyways, i guess you have to go for that "entire process" until they allow you to get a refund.
Hate to type it, but for me it's probably "Never Again" instead of "Never Settle".
CS is the same for most companies, someone in a call centre with little knowledge and a book of instructions to follow. There's no point you saying "I did this already" because they get in trouble if they don't follow the script they have.
I have got the black screen of death too and im a couple of mot=nths into using it
[/COLOR]
Tricepz said:
Hello Guys,
I am posting this thread with a great deal of frustration and of course i'll try to leave the emotions out of this, although it's pretty hard (since that's NOT how i imagined i'll unbox the OPT which i was waiting for, for so long).
Anyways,
I'll cut to the point, I received my OPT package and happily went a head opened the box (hoped not to get a broken phone or anything (like someone who posted a thread here), and indeed the package looked okay and the device looked good (physically speaking).
I started the phone, and i can see the black background white android logo, and then.. Black Screen... I'm telling myself "Ahh that's probably nothing.. let's wait a bit or worse case another restart" waiting didn't help and as you probably know restarts did not help as well.
Okay, since i am not newbie to the android troubleshooting, i said to myself, probably a bad OS boot or some sort of OS issue, let's enter the RECOVERY to reset / wipe / factory reset.
Volume Down + Power Button, can't enter recovery just a Black Screen showing.
Starting the phone again regularly shows the Black Screen but the buttons are glowing blue and if i click on the volume buttons i can hear the sound tick.
Okay, at that point i was getting a bit worried, no recovery, several reboots and Black Screen when going to recovery or normal mode.
So now, i knew i had to go over and search the forums (XDA | One Plus) for more solutions on soft bricked / hard bricked devices.
I found the restoration thread of:
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
Including the QualCom driver method and 2 FULL restoration kits (1 Hidro OS 1 Oxygen).
I followed the steps (trying first the lighter Hidro Kit (without .img's of system etc') finished the process but when it should logon to recovery SAME result.
Then i went ahead and tried the OxygenOS recovery kit, same procedure it finished, phone restarting but same Black Screen.
This is where i am at right now, very frustrated, i raised a TT to the one plus support, i will update how it goes, i assume i passed most of the troubleshooting phases but if anyone has ANY ideas on how to proceed or assist i would be glad to try it out.
In addition i will use this stage to also update on the OnePlus support (refund wise, and TT dealing wise) as i think it's also important to report on the support when actual problems occur and how they handle it.
In any case guys, thanks for reading this, i really hope you will receive your products WORKING as they should, there's not much worse things when it comes to getting a NEW device starting it for the first time and not being able to use it, after waiting for so long for it.
--Video is also attached below.
https://dl.dropboxusercontent.com/u/33088939/20151005_132402.mp4
I will keep you updated.
Thanks & Regards,
Click to expand...
Click to collapse
So the phone should be responsive even if you cant see the screen. SOOO forget letting it drain, but instead, connect it to pc and install latest twrp. Or crm. Unlocking the bootloader may be difficult as you have to use the power and volume buttons to choose yes or no but i think it starts on yes so just press the power button. Now copy over any rom and gapps (i used exodus and lollipop gapps). Flash them and the phone will boot up surprisingly quickly. This will hopefully stop you from wasting time with support teams that are already overloaded with queries. I hope this helped
I have the same problem I dont know what to do! please someone help !
This is really old news, I'll just add that I've sent the device back and got my money back,rocking a new lg v10 and happy a hell.
Sent from my LG-H960 using Tapatalk