I have asked about this before, but now I'm here to inform. If you have the problem of not being able to flash roms, and it says something like
''Installing: SDCARD:update.zip
Finding update package...
E:Can't mount /dev/block/mmcblk1p1
(No such file or directory)
E:Can't mount SDCARD:update.zip
Installation aborted.'
There is a semi-simple fix. This issue is happening because for whatever reason, a certain directory in your internal sd card can not be read. It can happen for 2 reasons. 1. Your inner sd card reader is fried (but if that was the case, chances are you can't boot your phone either) or more likely
2. Your innersd card needs to be reformatted. If I had to come up with a reason, it would have to be that somehow, when your innersd card was formatted, it never created that directory. I'm not sure on the reason for that happening. Anyway, the solution is simple (though part of it is a pain in the butt). Again, you have 2 choices.
1. Take your phone COMPLETELY apart, to be able to get to your inner sd, so you can format or replace it. Or the much easier, though still a pain in the butt option of
2. Cutting off the plastic above your innersd. This can be easy, but chances are, it won't be pretty. Mine wasn't. Some have been able to make it a pretty clean cut, but I wasn't able to. The reason I say this is easier is because it's a lot easier to mess up a phone, if you take it apart. You have to worry about esd (Electro Static Discharge), worry about smudging the screen (though, if memory serves me right, the screen to this phone is actually stuck to the gorilla glass), as well as you have to worry about every single little piece in the phone... Another reason cutting off the plastic piece would be a better solution is you don't have to do it everytime you need to get to your innersd. It's a once and done deal. Anyway, on to what I did to fix this issue.
I first started having this error, when trying to go from 1.9 to 1.9.1. I gave up on it for a while, until I saw that GingerStreak came out. I was really excited. I wanted to get Gingerbread on my phone! It's faster. It drains less battery... I wanted it. With hours of help from lordmorphous, we determined the problem, and he told me to cut the plastic above it, and replace the innersd. I did so, and VOILA! It worked! I was ecstatic to have Gingerstreak on my phone! It is faster, and more battery efficient (I could put the cpu down to 384 with almost no lag). But it restarts itself... At first, it was a couple times a day. That I could live with... But it got to the point where it happened every half hour, to every 2 hours. Everytime it reset, it would turn off my alarm. I wouldn't wake up on time, when I needed to. And it was just a big pain in the ass! Also, sometimes it would even get stuck on the Dell logo, DRAINING battery like crazy! So, I looked it up, and found out that that was simply a glitch in Gingerstreak, and that DSC didn't have that glitch, HUZZAH! So, I put the zip file for DSC 0.72 on my phone, and try to flash... But I got that error again... The way I fixed it this time, I just switched the internal and external sd cards. Worked just fine. And you just switch the cards back, when you're done. Sorry for this big story, but my fingers wouldn't stop typing. :3
PS. You might have to format both, after switching. Just format the internal via Streakmod, and the external via phone settings.
Dell streak won't start
Hi
I tried to run the following command in fastboot mode after flashing to 407 ROM
fastboot -w reboot
wishing to clear all the cache data and my phone won't start. Doesn't show any thing on the screen. Is there anything i can do to start my phone??
All these happened while i was trying to root my DS.
Thanks in advance
If you did a "fastboot -w", you have a brick... a virtually unrecoverable brick
http://forum.xda-developers.com/showthread.php?t=1500290
http://forum.xda-developers.com/wiki/Dell_Streak_5/Flashing_Guide
WARNING ABOUT FASTBOOT: Do not attempt to use fastboot erase or fastboot -w on the Streak
The fastboot program on the streak has issues and attempting to erase partitions with it may result in it hanging.
If it hangs the Streak will not be able to start up and is likely not rescuable by any manner (including QDL Tool)
Use factory reset via recovery mode instead.
Click to expand...
Click to collapse
Thanks
Hi Radimus thank you so much.
I appreciate the time you spent to help and give your advices and expertise to all the newbies like me.
Well i think i bricked my DS and can't even repair it since there is no Dell's service center in my country(Nepal). Since it is still has warranty I was thinking to send it back to UK (where i bought it) last year but since i had changed from custom ROM i don't think the warranty still valid.
So I think I'm gonna have to give it up, but I'm gonna get the same again.......
best phone ever...
Carrire locked
hi everyone,
since i bricked my DS (apparently) i gave it to a local repair center run by a friend of mine. He was able to give it a new life , but the only problem is that it is now locked!!! Since my DS was a factory unlocked i didn't have a unlock code or anything like that to unlock it and i don't think the guys from dell would give any random code to unlock it now. so is there any way out of it???
Related
First off, I must apologize and say. Yes, I know there are all ready two other posts just this week on 'Did I kill my phone, Is it dead etc.'
So, to make a long story short.
After much research, I started at the ppcgeeks.com forums, then ppckitchen.org and finally made my way over here. I decided it was time to start working on updating my phone.
First off; I downloaded the wrong link and flashed the Olipro 1.20 boot loader on the phone, instead of the 2.4x version that is being used now. No big deal, I then got into boot loader mode and went to flash a stock rom to fix the issue. The rom had an error in the middle and reset. Then my phone reset. It went back into boot loader mode and then after using titan_exitbl.exe it booted to the standard HTC screen. After a moment now at this screen it will display the HTC logo and No Radio in red. After much reading I found that I could simply flash my 512mb MicroSD card, and did. And I placed the TITAIMG.nbh file on the root. (that is the only thing on the card) to upgrade the radio. But now when I try to restart into boot loader mode (power, camera, reset) it only resets and does not go into boot loader mode. I can perform a hard reset and go through the prompts there, but after it completes it simply brings me back to the HTC logo, and No Radio.
There is no connection via Active sync, nor through the USB, so I can not use mtty to edit anything on the boot loader end.
I have done quite a bit of reading and I figure this probably has been asked before, but is there a way to get my phone to get back to boot loader mode so I can load at least a stock rom onto it?
I don't know a whole lot about troubleshooting phones considering I have only had mine for a few weeks. However I have worked for Geek Squad for 3 years so troubleshooting is kind of in my nature.
Have you tried putting it in bootloader mode without your SD card in there? If there is something wrong with the .nbh you have on it and it keeps trying to load it when in bootloader, that could be your problem. I would remove the SD card and try bootloader, at which point you should be able to flash via usb.
Worth a shot at least.
Flash a new bootloader like 2.47 via sd. Then start loading radio and rom from there.
flipzmode said:
I don't know a whole lot about troubleshooting phones considering I have only had mine for a few weeks. However I have worked for Geek Squad for 3 years so troubleshooting is kind of in my nature.
Have you tried putting it in bootloader mode without your SD card in there? If there is something wrong with the .nbh you have on it and it keeps trying to load it when in bootloader, that could be your problem. I would remove the SD card and try bootloader, at which point you should be able to flash via usb.
Worth a shot at least.
Click to expand...
Click to collapse
Yes I have tried with and without the SD card in the phone. I have also tried with and without the phone connected to a USB cable.
I cannot flash anything to the phone because i cannot establish a connection to the phone via ActiveSync.
Did you try what I suggested? Can you get to just the bootloader screen? Hold power and camera then push reset at same time for bootloader.
drewcam888 said:
Did you try what I suggested? Can you get to just the bootloader screen? Hold power and camera then push reset at same time for bootloader.
Click to expand...
Click to collapse
That is the problem. I have tried that. power, camera, and reset. And any combination of other button, SD card in/out, USB in/out, and anything else i can think of...
The bootloader screen will Not come up.
What can the phone do? Kinda sounds like it might be bricked.
drewcam888 said:
What can the phone do? Kinda sounds like it might be bricked.
Click to expand...
Click to collapse
I know, I hope it is not. This is my phone for work, and my boss is pretty pissed that I might have just bricked a phone he just paid for.
It will turn on from the power button, i can reset it normally with the reset push switch. (it then returns to the HTC logo, and No Radio in red). I can also do the 'bootloader' reset, but this does not bring it to the bootloader, it simply acts as a standard reset. I can also do a 'hard' reset, both of the select keys, and the reset switch. It will then boot into the 'do you want to hard reset your phone' prompt, and it will let me go through those steps that would normally hard reset the phone. After the reboot when that is finished it again goes to the HTC logo and No Radio. So, with that, I sure hope that some part of the bootloader is in tack.
Thank you for your help so far.
Are you sure you are holding both the camera and power button at the same time and then pushing reset button while still holding?
psycopyro182 said:
Yes I have tried with and without the SD card in the phone. I have also tried with and without the phone connected to a USB cable.
I cannot flash anything to the phone because i cannot establish a connection to the phone via ActiveSync.
Click to expand...
Click to collapse
From what it sounds like, you're trying to run the bootloader with and without the SD card in. The problem is, it sounds like you don't have a working file actually on the SD card. It also seems that since you cannot make an ActiveSync connection, you aren't able to transfer files to and from the card.
Do you have a microSD card reader?
Check this out: http://wiki.xda-developers.com/index.php?pagename=TitanRecentHome
Particularly Section II.2.A. That may fix your problem.
Hope this helps!
Oh and if it doesn't something you said about your boss having 'just' paid for your phone. If its new enough... w-a-r-r-a-n-t-y!
He can't follow those suggestions on the wiki exactly because he cant get a usb connection. But I agree he needs to load the 2.47 on his card using a adapter then try bootloader again.
Did you try EnterBL.exe?
DustinEarnhardt said:
From what it sounds like, you're trying to run the bootloader with and without the SD card in.
Oh and if it doesn't something you said about your boss having 'just' paid for your phone. If its new enough... w-a-r-r-a-n-t-y!
Click to expand...
Click to collapse
I cannot even get the bootloader to come up. Yes I know that I am pressing both buttons and hitting Reset.
And as for Warranty, Will they warranty a phone that has the updated bootloader on it? I know there is a utility to Re-flash your phone to stock, but well, i cant even get mine to do anything at this point. I dont want sprint to tell me that they will not warranty it because I have 'tampered' with it, or 'voided the warranty'.
bitserve said:
Did you try EnterBL.exe?
Click to expand...
Click to collapse
I did not know there was such a tool.
A direct link would be great. That sound like what i need to get out of this mess.
Heres the deal, if you can't get it to go to bootloader, the carrier probably can't either....
I think the enter_BL only works if active sync works, but I could be wrong.
I've never seen a phone yet, or heard of one for that matter that boots as far as yours does yet doesn't go to a bootloader screen when reset properly. It does sound pretty messed up.
More than likely, if you go into the store and say "Hey this is messed up because I tried to update the bootloader on it" you'll get some pretty quizzical looks. They'll more than likely take your phone in the back, not do a thing with it, and then issue you a replacement (if they have one in stock) or mail you one as soon as possible.
It does sound like you may have created a brick, but luckily this one is replaceable. Consider it a "lesson learned" for the next one.
(My apologies if I offend any VZW store employees. I sure there is a rare breed of highly competent and capable technicians out there, but I have yet to meet one in my area.)
Boots Up?
Does your phone boot all the way up where you can explore your SD card on your phone? If you can PM me and I may have a solution for you if your bootloader allows you to flash by SD card.
Brick = New Phone
DustinEarnhardt said:
More than likely, if you go into the store and say "Hey this is messed up because I tried to update the bootloader on it" you'll get some pretty quizzical looks. They'll more than likely take your phone in the back, not do a thing with it, and then issue you a replacement (if they have one in stock) or mail you one as soon as possible.
It does sound like you may have created a brick, but luckily this one is replaceable. Consider it a "lesson learned" for the next one.
one in my area.)
Click to expand...
Click to collapse
So, I walked into the store, and simply said. "I have insurance, what do I need to tell you in order to get the phone fixed." "what do you mean?" "Well i have my phone here, it is totally bricked, the bootloader is toast, and there is no radio or rom, and it will not connect to activesync. So, if i need to come back and tell you my phone is stolen i can."
"Um ok? bricked? bootloader?... Here, let me see it"
(Lucky for me my company had just purchased about a dozen phones from this store, and the techs were happy to work with me)
The tech took the phone in back, and he and another tech looked at it, tried to hard reset, tried the enter bootloader key press. tried to plug it in. Then they both scratched their heads with a completly dumbfounded look on their faces. One of them walked to the closet, grabbed a new phone and brought it to me and said. "Congrats, this is the most screwed up phone I have seen come in here. Here is a brand new one, We will have to send this one back to corporate."
So, now shiny new phone in hand.
I can say simply "Lesson Learned"
Thanks for all of your help guys.
OK well I have trying my best as a noob to research for 2 days not in and out on how to fix my issue
My friend tried rooting my phone and to install a different rom. I am on 2.1 and unfortunately I got the phone used with 2.1 already on it so I don't know if it was a leaked or legit 2.1 rom, and I am learning as I go here to fix this issue as I have never new how to do this stuff nor have I ever done it.
Where I am at now:
only thing that happens when I hit power is the phone "vibrates then stays on the 3 skateboard screen" or press "volume down + power" and it goes to the Hboot screen. I go into recovery and it goes to clockworkmod and from there after trying to install any roms from the sd card it says on the last 3 lines
"E:Failure at line 9:
copy_dir PACKAGE:system SYSTEM:
Installation aborted.
and every time I go back or power up to the Hboot screen it does not have any "update bar" (I guess if this was done right as I read on other threads there should be some type of update bar) on the right corner or any other options "for me to select" accept:
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
and then with some other info above the Hboot highlighted in blue
I have tried formatting the sd card a bunch of times, I did the clearing of the "wipe data, wipe cache partition, wipe dalvikcache" as I read to do over my reading, but I see that if I go under any restore options under clockwork, no files are found for me to back up too so I am seeing he did not back up any of my info, I also have tried using 2 different ds cards.
So more less it looks like my options are to get this fixed from the only place my phone will boot to with options and thats when I press volume + and power so I guess loading whatever I need to my sd card>>if thats an option or am I screwed, I have seen many tutorials but none of them start where my particular position is stuck at in Hboot. this is my only phone and I had to buy a prepaid which is just about out of minutes, I put an add on craigslist trying to get someone I will pay to fix my issue but no luck, please I need help and I will pay u somehow to guide me through this of my exact issue, I was trying to get to rom 2.3 but if it's easier to get back to 2.1 rom then so be it.
PLEASE!~~
Please HELP!
Cheeva316 said:
Please HELP!
Click to expand...
Click to collapse
Got a solution in the making for you, just give me about 30 minutes.
Edit: Maybe 45 minutes lol, sorry i'm testing this before I have you do it to see if it works.
Ok download the following files:
http://www.mediafire.com/?njwqa7axwzyaqgb
http://www.mediafire.com/?f69cl8dc747h0l9
http://www.mediafire.com/?xg8nnqs177xggx4
http://www.mediafire.com/?qxpi5wsx5lzbhbo
http://www.mediafire.com/?4tg67hck7vh1xxs
Edit: Flash the "rootme.zip" first then follow the rest.
Now what you need to do first is extract the "nandroid" file to somewhere you can easily find it.
Now take the folder called "nandroid" along with all the other zip files you downloaded and place them on your sd card. Put your sd card in your phone and power on with volume down+end. Press volume up. Use the trackball to select "Backup/Restore". Use the trackball again to select "Nand Restore". Use it again to select "HT9BGHG01402". Use it again to select "BDS-20110125-0901". Let the restore run, then power off your phone. Turn your phone back on with just the power button, let it run (might even take up to 10 minutes for the phone to start up). Let me know if the phone boots up or not after about 10-15 minutes. This should work and if it does then we can go from there, even to getting you 2.3 if you want.
You might be asking, what the hell is he having me do ? Here's what i'm doing. I made a nandroid backup a few months ago of when I had kaosfroyov39 which is a 2.2 rom. I am going to have you flash MY backup to YOUR phone which when done right, CAN work. Anyway, let me know what happens and remember to give the phone about 10-15 minutes to boot all the way.
Cheeva316 said:
"E:Failure at line 9:
copy_dir PACKAGE:system SYSTEM:
Installation aborted.
Click to expand...
Click to collapse
( Another phone on the precipice of being ruined by someone's cobbled-together "clockwork" recovery. )
If the /system flash memory partition got corrupted in a way that left a lot of pages marked as bad pages, then the /system partition will be "short", and only small ROMs will successfully load into it, if at all. That might be the cause of the above error messages.
But - because you are using Clockwork, there is really no way to know if that is the case, or if you simply have a whole bunch of corrupted ROM files on your SD card. That's because Clockwork does not verify ROM files before it starts flashing them - which allows total garbage to be flashed to the phone. (That's why Clockwork should never be used by newbs).
Here's what I would suggest you do.
- Make sure you are keeping the phone well charged. (Leaving the phone in HBOOT mode will discharge the battery quickly, even if it is plugged in to the charger, BTW).
- Report the exact bootloader version you have - probably 1.47.0000 or 1.49.0000, but it could be something other. Please be precise.
- With the power off, eject the SD card out of the slot and see if you can boot into the normal HBOOT menu with no SD card in the slot. Report your result.
- Boot into the recovery menu and tell us what version # of the recovery you have. If you can determine the details of how your friend attempted to root the phone, that might be pertinent. Again - precise details are valuable; vague hand-waving not so much.
- The Amon_RA recovery has a mode ("USB-MS toggle") which allows you to mount the SD card to the PC. Does your "Clockwork" recovery have this feature, or are you able to put files onto the micro-SD card using a media slot on a PC?
- Be aware that one or two people that were in situations that are very close to what you described ended up bricking their phones because they went from where you are now to attempting to use either a PB00IMG.ZIP ROM, or an RUU utility. Their phones went from bootable (in the way that yours is now) to bricks in that process.
What I would suggest you do at the moment is to find the SMALLEST Eris** ROM you can find, get it onto your SD card, verify that you didn't corrupt it, and then perform a "wipe data/factory reset" in your recovery and attempt to install it. If you get the same errors as above, then you should definitely NOT try to do a PB00IMG.ZIP or RUU installation. (The current gingerbread ROMs (e.g. GSB v1.4) are pretty small - they only use about 65% of the /system partition.)
I have a flashable "repair" file which might be applicable. It is not a "ROM" per se - it uses some low-level MTD (flash memory) repair techniques, and also flashes into place the original Amon_RA (v1.6.2) recovery, instead of whatever p.o.s. "Clockwork" recovery you currently have on the phone; but I regard it as something which should only be used as a last resort. But - without some more details and testing on your part, I don't feel comfortable about posting it up.
Let me know.
**PS I wanted to ask one more question - this is an Eris we are talking about, right? (I note you were posting in the Hero CDMA forum not so long ago).
Well I want to thank you for replying with such info but it seems that the recovery image file that I reinstalled on the phone was bad cause when it was updating the bar was going up but as it was going through each item it was updating.. I noticed "bootloader in red letters" with I believe saying "error" next to it and then same on another item it tried updating then the phone powered off and now it's dead, tried everything, no charging light comes on, computer (2 different computers) wont reconize it, it's doing nothing at all, I will try to get my hands on another battery but I am broke, but I doubt it's the battery cause I heard with a bootloader error (or damaged) then the phone won't boot up or do anything so I guess the phone is scrap for parts which sucks cause now my friend who started this deal killed my only phone me n my family had, another lesson learned...time to try n sell some stuff on craigslist..damn
Yes it's a Droid Eris...or was! damnnnn...
Again thank you for your help very much appreciated...
Wish I would of read this part before I let my friend re-load the "PB00IMG.ZIP" cause thats exactly what he loaded and then it started the process what I jus described above..f***k!
Be aware that one or two people that were in situations that are very close to what you described ended up bricking their phones because they went from where you are now to attempting to use either a PB00IMG.ZIP ROM, or an RUU utility. Their phones went from bootable (in the way that yours is now) to bricks in that process.
Cheeva316 said:
Wish I would of read this part before I let my friend re-load the "PB00IMG.ZIP" cause thats exactly what he loaded and then it started the process what I jus described above..f***k!
Be aware that one or two people that were in situations that are very close to what you described ended up bricking their phones because they went from where you are now to attempting to use either a PB00IMG.ZIP ROM, or an RUU utility. Their phones went from bootable (in the way that yours is now) to bricks in that process.
Click to expand...
Click to collapse
Well, I am very sorry that this happened to you and my advice to you didn't reach you in time. From the details that you added, I am pretty sure that you indeed have a hard brick.
BUT - the death of your Eris can still help others avoid the same fate. If you can reconstruct the rooting process you went through,
[SIZE=+2]PLEASE LET US KNOW EXACTLY WHAT ROOTING METHOD YOU USED[/SIZE] - and then we can wave people away from it.
When I say exactly, I mean extremely specific: do you still have the download file that you used? If so, push it up to an uploader site and give a link to it. (I think you mentioned unrevoked or something). Do you still have the exact link you used to download that rooting software? Was it Unrevoked? Z4root?
bftb0
I will tomorrow as I saved all the files on my laptop n I am on my pc now, but will do try my best as I am a newb to this phone stuff
Did you try what I suggested or is it too late ?
phone wont do anything so cant do nothing...
Did you find out any more details about the rooting method you used?
might be a couple more days till I can get to it, my laptop is messing up now...all the saved info was on it
Please help me, I played around with BBs yesterday and lost radio, so installed a stock FW with FlashTool, and got radio back again, but on some 4x BB.. Wanted the new 58 BB, and found out that a .. ..0.16 FW would give me that, so installed the polish one (found no other), and after that no response when touching the screen!
xRecovery is of course gone after "stocking" (also rooting?), but I have tried a number of FWs for FlashTool, and even FW directly from S-E using Update Service, but still my phone is next to bricked.. I am n00b and could very well have done something wrong unknowingly, and/or overlooked something, but what might that be, and what are my options?
Sounds like corrupted FW. Not a big deal cause without a cracked Bootloader, you realy can't screw the phone up.
Turn phone completely off.
Pop Battery - SIM card - Micro-SD card out.
Let it sit for a few minutes.
While your letting it sit, take your Micro SD card and Format it using your PC.
"not saying this is your issue but I have had the phone lock up and appear to be unresponsive due to a corrupt file on the SD Card and it fails to mount and gets stuck." If you have any files you want to save, copy them to your PC Hard Drive.
Reinsert your SD Card - Sim Card.
Plug your USB cord into your phone " LEAVE THE BATTERY OUT "
Start up SEUS " Sony Erricson Update Service ".
While holding the back button, reinsert the battery.
Follow the instructions and restore the phone to factory settings.
I hope this works for you as this should elliminate any problems that could have or would be occuring prior. If it doesn't, shoot me a mail and I will get with you on messenger for trouble shooting.
_-_- Press Thanks if its useful-_-_
Nope, didn't do it, touched the thanks-bottom anyway, because on my PC I can...
PM'ed xKrisx, but everybody are welcome with suggestions as I'm completely lost without my phone!
Edit while waiting, hoping:
Followed instructions above several times now, except
xKrisx said:
.. .. .. and restore the phone to factory settings.
Click to expand...
Click to collapse
no such option, wouldn't that be S-E-Android 1.6 ? In fact I see no other options in SEUS than accepting (or not) uneditable choices towards an update -and done-, so I suppose that's what was meant(?)!
Have tried a number of slight variations including SEUS update without sim and SD at all (was actually allowed that), but most noticeable difference was that first boot pre-choose English instead of Danish (my language), and still no response from touch screen, so can't select anything at all!
My phone shows evidence of "moderate physical pressure" (bought second hand with one corner missing), so I can't totally reject the possibility of a sudden HW digitizer breakdown though I think that would more likely have occurred while phone in use than while sitting on my mouse-pad.. No matter what, I would really like to exclude any SW related errors before moving to torx-driver surgery! Plz help guys!
Hi seek4
Did you ever find a solution for your touchscreen?
ok, here comes the story.
i know you guys hate when we open new forums, but this here is a topic that i have been dealing with since about 2 weeks ago.
also, i wanted to thank you all for your help,ever since than...
the problem started as i said, few weeks ago. i have an s2, i tried to install a rom, and an error occued. the problem was know that i needed to factory reset and wipe the data from the phone in order to boot the phone. this was not possible due to an internal error (i got sucked), later on, i also discover that the problem i faced was due to the partions inside my phone.so, i tried to fix the partions, but i was unable,until i found a thread here dealing with the same problem on Note 2. so after a lot of work, i was able to repartion my internal memory (lost 6 GB) to fix partions 9, and 10. once that was done i was able to wipe data and factory reset.the problem was now that i was unable to install any rom using odin except CM10 which stucked also at the end of the process. but luckily for me i was able to get into the recovery of CM10 and i installed from the restriction remix rom. after wiping and factory reset, i was finally able to boot successively into the home-screen.
now, my phone seams to have swamped the internal and external memories. in the build in device manager of rr-rom, i only see my memory card labeled as internal. but this is not the big deal. the real problem is that this phone constantly keeps on restarting itself from time to time. so, it shut down from alone, tries to boot up, gets stucked at the logo, reboots itself several time in the same way, until in finally boots successively,
any help??
ah, i just wanted to add a funny fact, which is that on the day i fixed my phone,i accidently dropped it in the toilet (it fall from my pocket, no bad ideas please, it was fully at random from alone). i manged to save it also at that day. so, i some got a feeling that this phone just don't want to get repaired
Reinstall stock rom and start from scratch.
Sent from my GT-I9100
Well I have seen some ridiculous generic topic titles in my time (like "Help" and "Help please" etc) but this topic with its complete lack of a title just takes the crown as the most idiotic.
Hello all!
First of all, I am no developer.
Long story short.. I purchased an HTC 10 because I was sick and tired of my at&t galaxy s5 being bootlocked. I received the 10 and set out the next day to root it. I followed a video on youtube (not saying that the info was not correct...I may have done something wrong...not trying to discredit anybody) to the letter and lo and behold I ended up in a bootloop. My heart probably came close to a complete blockage at this point. This bootloop lasted maybe a minute before it would reboot. So... In my infinite wisdom I chose to relock the bootloader. Oh Boy!!! Fun times were ahead for me!! As soon as I relocked said bootloader, the bootloop increased its timing to about 1 point 5 seconds. I remember waking up on the floor in the fetal position. Now I am stuck with a phone that adb will not recognize. It does however recognize the device at the fastboot devices prompt. So my question is this.... Is this a salvageable phone? If so, How would one go about fixing this problem?
*** Relocked ***
htc_pmew1 pvt S-ON
os-2.28.617.8
I would prefer that the money I spent on this thing would amount to something more than a small ant bed.
Any help at all would be greatly appreciated. Also I have been doing a lot of digging around and (I may be wrong) but. I could not find this scenario in the forums here. I apologize if this has already been covered.
...So..after looking around for a bit more, I discovered out that there is a way to flash a ruu/zip from an sd card. I have tried multiple times with what I thought were the right ones. As I am unable to boot into recovery, I feel I am limited as to what I should do. I have read about that I should wipe dalvik but I am very limited in my knowledge on an android system and would prefer to not mess this phone up anymore than it already is. I was trying to root and I used TWRP as the recovery but I never made it to the end before it started the loop. The Phone is an htc 10 unlocked version. and it just constantly reboots about 3 seconds apart. ADB says no device connected, so I cannot execute commands that way... really at a loss here. all the tutorials I have read refer to using and and being able to boot into rrecovery. when i boot into recovery, I get an immediate reboot and the 3 second bootloop forever. Is there a way to use twrp to somehow resolve this?Is there a tool that will help me at least get into recovery mode?
SOLVED... Ran across Batchtool by sneakyghost. Quite the bunch of tools there! Ended up solving my problem by placing the stock RUU in the root folder as the batch tool. Before I could not install from a factory RUU (would not recognize the phone through ADB or install the RUU. After the install of the batch tool I was able to get a clean install back to my factory settings.. Now I am free to mess it up again!!
BIG THANKS TO SNEAKYGHOST!!!!!
I'm unsure why the batch tool has worked for you and the sdcard method didn't - getting fastboot to work and all the bits and pieces together (drivers, Windows VCRedist, correct fastboot, correct adb) is usually more error prone than just identifying the correct zip and placing that in your sdcard root.
At this time, I'm a bit in a "scratch my head" mood, thinking this is weird. Same zip? Really the same zip didn't work from sdcard but would work in fastboot? I think I haven't come across that myself yet (non booting phones are a daily thing, almost).
I wish I had the time to analyze your steps with you, so I could gain understanding as to why that happened, so I can use that in the future, but alas! I have no time for XDA and deep digging around in issues of other people. Lately I can't even solve my own phone's problems anymore due to too many other things going on.
Well, glad it worked for your phone, anyhow. I'll keep this in mind for the next one messing up his/her phone.