Hi guys,
First I want to say I have been researching many forums for quite some time.
I hope someone can help or confirm that my phone is brick or not. I searched throughout the forum and have not found anything similar to my situation and if there's a fix. I also searched the other android forums.
I was trying to manually do the temp root on my Inc4G and after changing the CID from VZW_001 to 11111111, I did adb reboot bootloader and now it won't turn on. adb doesn't detect it as connected and I tried to go into hboot by pressing power+vol.down and nothing works, no response from the phone.
I hope I didn't totally bricked the phone
stormified said:
Hi guys,
First I want to say I have been researching many forums for quite some time.
I hope someone can help or confirm that my phone is brick or not. I searched throughout the forum and have not found anything similar to my situation and if there's a fix. I also searched the other android forums.
I was trying to manually do the temp root on my Inc4G and after changing the CID from VZW_001 to 11111111, I did adb reboot bootloader and now it won't turn on. adb doesn't detect it as connected and I tried to go into hboot by pressing power+vol.down and nothing works, no response from the phone.
I hope I didn't totally bricked the phone
Click to expand...
Click to collapse
have you tried using a different battery?, any other things you noticed while temp rooting?
jose51197 said:
have you tried using a different battery?, any other things you noticed while temp rooting?
Click to expand...
Click to collapse
I have not tried a different battery since I don't have a spare. I guess I should get one to test it.
As far as temp rooting, everything seemed fine until I finished changing/flashing the fakeCID and did a reboot to bootloader. That's when it stopped responding. Although, now that I remember, I was probably within the halfway point of battery/power. How much would that have affected the flashing and such? I would assume minimal since it would be charging via USB while connected wouldn't it?
stormified said:
I have not tried a different battery since I don't have a spare. I guess I should get one to test it.
As far as temp rooting, everything seemed fine until I finished changing/flashing the fakeCID and did a reboot to bootloader. That's when it stopped responding. Although, now that I remember, I was probably within the halfway point of battery/power. How much would that have affected the flashing and such? I would assume minimal since it would be charging via USB while connected wouldn't it?
Click to expand...
Click to collapse
htc phones do not charge while in bootloader mode
Related
was using zedomax's root method and got a bunch of errors "too many devices, more than 1 emulator" and now it won't finish booting. Gets just to the point where the unlock ring should come up and then nothing...
I can pull down the status bar and thats about it ...please help. I have the insurance, but will they be able to see that i started rooting it...
I would try to install the RUU to get it back.
It's probably not Bricked.
You can also check out the more full unlocking procedure http://forum.xda-developers.com/showthread.php?t=1690919
I believe one or both these procedures could be started while in the bootloader.
I'd try the RUU first though.
Look in the Sticky thread in Dev for the RUU (an EXE you run on the PC).
greek goddess said:
was using zedomax's root method and got a bunch of errors "too many devices, more than 1 emulator" and now it won't finish booting. Gets just to the point where the unlock ring should come up and then nothing...
I can pull down the status bar and thats about it ...please help. I have the insurance, but will they be able to see that i started rooting it...
Click to expand...
Click to collapse
This happened to me as well. Then i realized i have both my old Epic4g AND my new EVOLTE plugged into my computer. I unplugged my epic and voila. it worked just fine. If it still doesnt work, try restarting your PC and redo the process.
Thanks guys for your answers. problem is resolved, but I will what happened in case anyone else has this problem.
I couldn't get the drivers to install on my laptop so I went to the desktop and ran the root. The error messages I got were like this: after the second reboot (supposed to reboot 3 times) it would say "device offline" and it filled the whole screen with that line. Then it said "error too many emulators" and then it would say it was done and that is as far as it would go. It did not boot a third time. I could reboot it, but it would only get as far as the screen JUST before the unlok ring comes up, and that's it.
After posting this thread I read another thread where someone suggested holding the volume down and power to bring up stock recovery and doing a factory reset from there (rookie mistake, I have had the Epic Touch for a while and forgot about the Evo's stock recovery). That got me back. THANK GOD! But still no root.
I didn't want to give up trying to I went back to my laptop and still without necessarily "installing" the drivers, went ahead and tried running the root and VIOLA! It worked flawlessly!
So I don't understand what was going on with the desktop though with the "device offline" and "too many emulators" thing, so if anyone could shed some light on that, I would appreciate it.
glad to hear you got it fixed but if you would have had to filed a claim then you can always say you lost it or something like that.
I know there are lots of posts about bicks, but after a week searching I could not find any fix for my problem.
I have a S-Off, rooted GSM Evo 3D running Yoda ICS ROM and 4ext Recovery. One day, I was charging it when it hung, I restarted the phone, but it went directly to the bootloader (I didn't touch anything), as I was unaware of what was happening, I simply power it off (using the menu option), when I tried to power it on again, I got no success, only a dim red light appeared, and it is this way eversince.. I cannot power it on, go to the bootloader or anything, the computer recognizes it as QSUSB-DLOAD but there is no partition on it (I tried both Linux and Windows). I tried some unbricking methods without success. I am in Brazil, I tried to call HTC but they said I have to send the device to the origin country (mine is from Rogers, I believe it is Canada), but I don't even know where to send and I'd prefer to fix it by myself if possible. I am open to suggestions anyone could help?
Thanks a Lot!!
AW: [Q] Hard Brick evo 3D
Does adb detect the device?
In that case you could try to run a ruu...
If he can get it into recovery mode then yes. Most of the time its usually something that the end user has done to make it get bricked. I am not saying he actually did something. We also don't know what he has done with his . Phone changing your cid is a good way to brick it. Pulling the battery during a ruu update, flashing a CDMA firmware etc things like that are guaranteed brick makers. However there's only one solution I know of should you not be able to boot into recovery. Try and Google up JTAG. I'm fuzzy on the details about how it works but it can restore your hboot. If you know somebody that knows how to do it, that's your best shot. Otherwise, you will have to send it into HTC Canada or you could try to buy the JTAG hardware and learn how to use it to restore your phone. If anybody has a solution for him please feel free to chime in. Sorry about your phone though. I wish you the best of luck on getting it restored.
Quantenhall said:
Does adb detect the device?
In that case you could try to run a ruu...
Click to expand...
Click to collapse
No, it does not detect the phone. I was searching more thoroughly and found some places here in Brazil that do jtag repairs, I think I will give it a shot.
Thanks!
RonaldoPA said:
No, it does not detect the phone. I was searching more thoroughly and found some places here in Brazil that do jtag repairs, I think I will give it a shot.
Thanks!
Click to expand...
Click to collapse
Just to let you guys know, I did the jtag repair and it worked for about a week, I put back my cfw and yesterday, out of nothing it stopped work again. It was working normally, I left it on the table, checked the time and went do other things, later (about 2 hours) I took the phone to set the alarm for the next day and it didn't turn on...
If someone has any ideas, I appreciate!
Thanks in advance.
RonaldoPA said:
Just to let you guys know, I did the jtag repair and it worked for about a week, I put back my cfw and yesterday, out of nothing it stopped work again. It was working normally, I left it on the table, checked the time and went do other things, later (about 2 hours) I took the phone to set the alarm for the next day and it didn't turn on...
If someone has any ideas, I appreciate!
Thanks in advance.
Click to expand...
Click to collapse
Try using this to unbrick the phone (aimed specifically for DLOAD error, but has worked for other cases): http://forum.xda-developers.com/showthread.php?t=1522351. Afterward, use a combination of both the official instructions from Unlimited.io and this video tutorial to achieve S-OFF. The instructions give you an idea of how-to, the video actually gives you a better sense for the timing. The timing is very specific that needs to be done just right (might take quite a few times to get it done).
If you have an HTC Evo V 4G with Virgin Mobile USA, then you can use this flashable RUU to return to stock (I extracted this from the RUU.exe; just ensure that your bootloader is LOCKED. You can check this by Holding Pwr+Vol Down during boot; top of the screen should say LOCKED). If your phone skips loading into your bootloader and boots into the main OS, pull the battery to bypass quickboot (or turn it off in the settings). To flash the RUU, move the file to the root of your SD card, boot into bootloader, and follow the directions on screen.
brick evo 3d
when i update mwakiousSGS2rom_v.3.0.03 to my evo 3d . this is my bi mistake .and after that my mobile is of ..so pls what can i do .help me
listen this is my last resort, i did everything I possibly could before coming here. & I searched people I freaking searched and ive tried every method I came across that related to my issue specifically, where the users found resolution. That being said, NONE of them worked for me. So i am not going to detail everything ive tried in the last 120+ hours dedicated to this issue in the last 10 days, so please understand that if your solution is one that is commonly/easily found online, chances are ive tried/applied but to no avail. Now to my issue, my specs are provided on the attached pic, but its hboot 1.58.0 radio is 1.09.00.0108 S-On & relocked bootloader, it was rooted with S-off but I am not sure if it is still rooted after the many attempts to get this device up & running. So now what happened, this is an inactive device of mine & i havent had it long, its mint condition tho and worked fine when i got it originally. I have an evo 4g as well and thats the whole reason i wanted the 3d. Ok, so I unlocked the bootloader thru htcdev & I rooted the 3d with s-on of course cause i am on 1.58. But then 2 critical things happened. When i got the 3d it wouldnt charge fully. it would charge til a green light but the battery would never show anything over 85% and either way i was flashing a rom and the battery just died when it supposedly had well over 50%. oh & btw, the rom was cynmod V? but the zip file is called "wild-for-the-night", which I have since learned wouldnt have worked anyway. & Then all of sudden the 3d wouldnt charge or turn on, but the orange light would act a specific way that I found others experiencing all over the web, but none of their solutions worked for me and i spent alotta f-ing time with the batt issue, that is until the new batt i ordered arrived, & solved the issue entirely. either way from that point on it will only boot into fastboot/bootloader. no recovery no rom, its not happening. In fact when I plug it in to a pc or to charge it wont stay powered down, it boots str8 into fastboot & simply wont stay off while plugged in live. but it does show its charging while plugged in. anyway I relocked bootloader so I could run the ruu and thats just not happening either. the 3d is updated to 2.89.651.5. At one point I followed methods to downgrade hboot to get s-off & I flashed hboot 1.4 or 1.5 in my attempts to downgrade but I lost that page with the exact instructions i was following and I havent been able to find it again, and ontop of that I lost the files I had downloaded to a usb that has been formatted since.. But regardless, it still shows 1.58, I just thought it might be relevant that I did attempt to flash an earlier version but things clearly havent worked out for this device. Adb doesnt seem to be recognizing the evo 3d & wont even show up as a connected device. fastboot is recognizing the evo tho, however when I try to unlock the bootloader thru htcdev, now it gives me an error talking about the unlock code isnt long enough or somwething like that. I can take a screenshot of it if needed. I really just wanna get this device back to an oem/stock condition, & then be able to follow methods that ive since come across to root with s-off. Please Help
I bought a cheap android phone off of a friend a few weeks ago (ZTE Solar, Z795G). This phone has lots of problems out of the box, one of which includes the inability to be rooted (seriously, I have tried every single rooting option available). Another problem I have found, is the fact that this phone is apparently missing a bootloader U.I.
I tried holding down power & V-down or up during startup. I have tried hooking the phone up to my laptop with USB Debugging enabled, and everything works fine, but when I type "ADB reboot bootloader/fastboot/reboot-bootloader" it simply reboots to system. "ADB reboot recovery" works fine, the phone has no problem rebooting into it's, frankly useless, stock recovery.
My question is this... is it actually possible that this device does not have an interactive bootloader?
There are many devices that don't have an interactive bootloader menu. Saw a random post from androidforums.com that someone found a way to temp root, but you lose it after a reboot. I didn't see them say which program. I'm afraid it's just another unloved Android with absolutely no interest from developers to try and do anything for, with, or to.
es0tericcha0s said:
There are many devices that don't have an interactive bootloader menu. Saw a random post from androidforums.com that someone found a way to temp root, but you lose it after a reboot. I didn't see them say which program. I'm afraid it's just another unloved Android with absolutely no interest from developers to try and do anything for, with, or to.
Click to expand...
Click to collapse
This being the case, do you have any idea how I might use the Fastboot utility without access to the bootloader?
Hey all,
I've never rooted a phone before so since I have a spare model, I figured I'd give it a go.
Hearing about this forum, I checked it out and was sent to the Sony site. I understand I needed to unlock the bootloader first, which I did and can confirm I get that alert as my phone starts about it not being safe.
Hint for future readers: don't do this in a virtual environment, I had issues doing this until I used an actual computer and not a VM (mods and folks with more experience: feel free to correct me on this or shed some light). To be clear, I have a separate host running Proxmox (Type I hypervisor) and was able to forward my USB connection to test with ADB and such. I do most things in a virtual environment to not mess up my physical computer.
This was all done last week. Well today, Monday, I decided to continue with my rooting excursion, only to run into the issue I am currently facing.
After many, many Google attempts and following whatever links in this, I finally found this link. Well, I was within a VM, downloaded the linked flashing tool, and ran the first two commands:
- adb devices
- adb reboot bootloader
After doing this, my phone turned off and I wasn't sure what to expect, so I pressed the Power button to see what would happen - nothing. So then I remembered that Friday I was having issues communicating with my mobile phone in the VM to unlock the bootloader in the first place, so I figured I'd try to move it to my physical computer....then I was stuck on a reboot cycle!
To be clear, my issue is that I am stuck on a boot loop. It prompts the error of the device being unsafe, waits 5 seconds, then displays the Sony splash screen. Rinse, wash, repeat; same thing.
I have a Sony Xperia XA1 (G3123) model.
Can anyone shed some light?
Am I screwed?
Please halp!
I dug around a bit more, found this link but the issue is that I cannot boot into anything, at least not that I'm aware of.
tryingToSurvive said:
I dug around a bit more, found this link but the issue is that I cannot boot into anything, at least not that I'm aware of.
Click to expand...
Click to collapse
have you tried installing a custom recovery?
this may help https://forum.xda-developers.com/xa1-ultra/development/g3221-built-sources-t3622886
keifus.rahn said:
have you tried installing a custom recovery?
this may help https://forum.xda-developers.com/xa1-ultra/development/g3221-built-sources-t3622886
Click to expand...
Click to collapse
Hey @keifus.rahn for following up.
I did find that thread after continued poking, which I am still checking now. And I eventually made a post on there just now discussing my current dilemma.
I downloaded the Flashtool but didn't understand how it worked, nor do I still yet. I tried debugging it and the issue is that the "java -version" call doesn't work within the directory's own structure. I do have java installed on my test Linux VM though.
Past that, I tried with the latest boot.img as well as the recovery.img that I found. I think that the build numbers are off, or maybe I am just not understanding where I am lacking.
You can look at the bottom of the last page for a breakdown of what I did:
https://forum.xda-developers.com/xa...21-built-sources-t3622886/page94#post80481385