Database Info

HTC Incredible 2 Unroot help! (USB Problems)

1st off I'd like to say thanks to who ever helps can help me out.
Long story short, I rooted my phone awhile back. my USB port is outta wack (this exact some thing happened to my GF.. is this common?)! It will not charge up, and up until about 20 min ago it just barely started being recognized by my PC (well not 100% but about half way). So I need to send it in and get a replacement phone BUT we all know that rooting your phone voids warranty's.
OK here it goes...
I just restored back to the stock rom (I backed up after I rooted but before i installed a custom rom), and now I just need to get the damn "AlphaRev" off the bootloader.
So my question is, is how do I do that?
When I plug my phone into the usb be it starts charging for about 5 to 10 or sometimes 40 seconds then cuts off AND "adb devices" in cmd.exe just says "list of devices attached" and is just blank. My GF has a DInc2 also and I can get hers to show up with the serial so I know I'm doing it right. Why do you think mine won't show, even when it's charging and has the orange light lit up, it still doesn't detect it.
Is there a way unroot/flash back to the original bootloader from a SD card?
If I just install Gingerbread via Verizon OTA updates will it automatically reset the damn phone?
Thanks in advance.. seriously!!! I need some sleep though, but I'll be back tomorrow morning!!!

Randycigar said:
1st off I'd like to say thanks to who ever helps can help me out.
Long story short, I rooted my phone awhile back. my USB port is outta wack (this exact some thing happened to my GF.. is this common?)! It will not charge up, and up until about 20 min ago it just barely started being recognized by my PC (well not 100% but about half way). So I need to send it in and get a replacement phone BUT we all know that rooting your phone voids warranty's.
OK here it goes...
I just restored back to the stock rom (I backed up after I rooted but before i installed a custom rom), and now I just need to get the damn "AlphaRev" off the bootloader.
So my question is, is how do I do that?
When I plug my phone into the usb be it starts charging for about 5 to 10 or sometimes 40 seconds then cuts off AND "adb devices" in cmd.exe just says "list of devices attached" and is just blank. My GF has a DInc2 also and I can get hers to show up with the serial so I know I'm doing it right. Why do you think mine won't show, even when it's charging and has the orange light lit up, it still doesn't detect it.
Is there a way unroot/flash back to the original bootloader from a SD card?
If I just install Gingerbread via Verizon OTA updates will it automatically reset the damn phone?
Thanks in advance.. seriously!!! I need some sleep though, but I'll be back tomorrow morning!!!
Click to expand...
Click to collapse
Why don't you purposefully brick it so it doesn't turn on at all? If your USB port doesn't work, there's no way to return to stock.

Phone won't turn on, can't get into Hboot

Hi,
I was just wondering if anyone can give me any pointers on what I could do.
I don't own the device since its my girlfriend's, but her phone is refusing to turn on, tried getting into the bootloader by pressing volume down and power - nothing. This happened after she left it in her locker at work with no problems and upon returning she found it like this.
Charging it up with battery plugged in does nothing, red led shows for about 5 secs then it turns green indicating the battery is charged? Tried taking the battery out and tried to power it from mains, nothing.
When I plug the phone into my computer it does show in devices and printers as a android phone so something must still be working.
Is there any way I can flash a new RUU this way or access adb? I've tried installing the drivers but when searching for devices it says not found.
She didn't let me root the phone when she first got it so it is covered under warranty, however when we phoned HTC to process a repair we told them about a screen crack which she incurred MONTHS ago, but they are now saying she has to pay for the screen to be fixed for the phone to be fixed under warranty even if we don't want it fixed? They can't even tell us how much it would cost either because they have to see it to get a quote :/
Needless to say I'm not very happy with HTC right now and not even sure if they are allowed to do this.
Is there anything I can do to see if I can sort the phone, or do we have to chalk up at least £27 for courier costs?
Cheers

cmonthegas said:
Hi,
I was just wondering if anyone can give me any pointers on what I could do.
I don't own the device since its my girlfriend's, but her phone is refusing to turn on, tried getting into the bootloader by pressing volume down and power - nothing. This happened after she left it in her locker at work with no problems and upon returning she found it like this.
Charging it up with battery plugged in does nothing, red led shows for about 5 secs then it turns green indicating the battery is charged? Tried taking the battery out and tried to power it from mains, nothing.
When I plug the phone into my computer it does show in devices and printers as a android phone so something must still be working.
Is there any way I can flash a new RUU this way or access adb? I've tried installing the drivers but when searching for devices it says not found.
She didn't let me root the phone when she first got it so it is covered under warranty, however when we phoned HTC to process a repair we told them about a screen crack which she incurred MONTHS ago, but they are now saying she has to pay for the screen to be fixed for the phone to be fixed under warranty even if we don't want it fixed? They can't even tell us how much it would cost either because they have to see it to get a quote :/
Needless to say I'm not very happy with HTC right now and not even sure if they are allowed to do this.
Is there anything I can do to see if I can sort the phone, or do we have to chalk up at least £27 for courier costs?
Cheers
Click to expand...
Click to collapse
Could you just send it and say the screen got cracked in the post
Sent from my HTC Desire S using xda app-developers app

[Q] Received OPO today, shutdown immediately after boot.

Just received today my brand new OPO from OnePlus, buyed it with invite, it came from LONDON-HEATHROW - UK.
The phone immediately powers down after boot. It displays the "Power off, Shutting Down" message, but simply refuses to actually let me into the OS.
I've tried:
- Full factory reset (all wipes)
- Reinstalling rom with fastboot (30O) AND with simple recovery sideload (25R)
- Formatting again
- Different cable, Different charger
- Without SIM card, with SIM card (with and without sim deck)
- With cable, without cable
- Boot cycle (+30secs power button)
The battery is at ~35%, But battery does NOT charge. Tried with different chargers and cables, over an hour but it doesn't charge at all. Screen turns on when "charging" and shows battery icon with percentage. And plug is all way in.
Have made a ticket to OnePlus but i dont think i get answer in half a month.
It will stay alive if I hang in Recovery and in Fastboot. It will stay on in that all day. The minute I boot into the OS it shuts down.
Edit: Found out that someone has same problem with nexus5.
http://forum.xda-developers.com/google-nexus-5/help/nexus-5-shutdown-immediately-boot-t2569000
On video same thing as me. I haven't rooted device.
Anybody have any ideas?
Very disappointed because waited this day 2 months and then i can't even try the software. Phone feels and looks good. But its too expensive to only be a paperweight.

Did you unlock your bootloader and flash a custom recovery before you tried to flash a rom?

Mr Woolf said:
Did you unlock your bootloader and flash a custom recovery before you tried to flash a rom?
Click to expand...
Click to collapse
yes i did.
Also tried the boot cycle (at least 30sec power button) with no luck.

I think its a hardware issue... Replacing is good way..
Sent from my Miui v6 by Abhi

okay, i try to get logcat from boot. First issue is that usb debugging is off by default. So i found a way to change this ON with TWRP, and adb and sqlite3.
Changed adb_enabled value from /data/data/com.android.providers.settings/databases/settings.db to 1.
And
Added persist.service.adb.enable=1 to /system/build.prop
Next problem is that when i turn phone on, it boots normally, and when it has booted up it shows on back: Allow USB debugging? And buttons Cancel and OK, but i can't press those because of that stupid Power off. Shutting down... window.
Any solution how to confirm usb debugging?

Micco85 said:
Just received today my brand new OPO from OnePlus, buyed it with invite, it came from LONDON-HEATHROW - UK.
The phone immediately powers down after boot. It displays the "Power off, Shutting Down" message, but simply refuses to actually let me into the OS.
I've tried:
- Full factory reset (all wipes)
- Reinstalling a rom with fastboot AND with simple recovery sideload
- Formatting again
- Different cable, Different charger
- Without SIM card, with SIM card (with and without sim deck)
- With cable, without cable
- Boot cycle (+30secs power button)
The battery is at ~35%, But battery does NOT charge. Tried with different chargers and cables, over an hour but it doesn't charge at all. Screen turns on when "charging" and shows battery icon with percentage. And plug is all way in.
Have made a ticket to OnePlus but i dont think i get answer in half a month.
It will stay alive if I hang in Recovery and in Fastboot. It will stay on in that all day. The minute I boot into the OS it shuts down.
Edit: Found out that someone has same problem with nexus5.
http://forum.xda-developers.com/google-nexus-5/help/nexus-5-shutdown-immediately-boot-t2569000
On video same thing as me. I haven't rooted device.
Anybody have any ideas?
Very disappointed because waited this day 2 months and then i can't even try the software. Phone feels and looks good. But its too expensive to only be a paperweight.
Click to expand...
Click to collapse
I suggest you do an RMA ASAP or you'll be screwed. I was having issues with my device not the same as yours and 3 emails after never got a response from OnePlus so I contacted Paypal. I'm sure they'll reply back that way, good luck.

Knight-Rider said:
I suggest you do an RMA ASAP or you'll be screwed. I was having issues with my device not the same as yours and 3 emails after never got a response from OnePlus so I contacted Paypal. I'm sure they'll reply back that way, good luck.
Click to expand...
Click to collapse
Ticket has been made on same day i received OPO.
I Managed to get LogCat from startup. See attachment.

Micco85 said:
Ticket has been made on same day i received OPO.
I Managed to get LogCat from startup. See attachment.
Click to expand...
Click to collapse
You're better off asking a Dev I can't help you there.

Slot Unbootable, no USB

Okay, this one seems slightly different, so anyone who has had the problem and found a solution, I'm all ears. While reflashing the second Q beta (over the second Q beta - I was getting Play Services FCs and rebooting didn't fix it) everything went fine until the command window closed and the phone stayed in the bootloader. After that the PC didn't recognize anything being plugged in or our, it's stuck on slot b, which is unbootable, I can't change it and I can't boot from it, because I can't talk to it. I've removed and replaced the driver, I'm using a USB 2.1 connection, the computer recognizes other phones on that cable, I've used the same combination to flash factory versions and sideload updates all year using exactly the same thing, so ...
Google recommended an RMA, so they did, and Fedex has it on the truck today for delivery but ... has anyone found a way to get this to work without changing the motherboard? (I've treated this battery well, and the phone's been a case since day 1 - who knows what I'm getting.)

Rukbat said:
Okay, this one seems slightly different, so anyone who has had the problem and found a solution, I'm all ears. While reflashing the second Q beta (over the second Q beta - I was getting Play Services FCs and rebooting didn't fix it) everything went fine until the command window closed and the phone stayed in the bootloader. After that the PC didn't recognize anything being plugged in or our, it's stuck on slot b, which is unbootable, I can't change it and I can't boot from it, because I can't talk to it. I've removed and replaced the driver, I'm using a USB 2.1 connection, the computer recognizes other phones on that cable, I've used the same combination to flash factory versions and sideload updates all year using exactly the same thing, so ...
Google recommended an RMA, so they did, and Fedex has it on the truck today for delivery but ... has anyone found a way to get this to work without changing the motherboard? (I've treated this battery well, and the phone's been a case since day 1 - who knows what I'm getting.)
Click to expand...
Click to collapse
I would try skipsoft Android toolkit. It might not recognize your phone right off. Try uninstalling and reinstalling USB drivers through the toolkit with phone plugged in. Downloading and installing firmware, etc. It got me out of a bind once. Worth a try.

Hi, I got to this "not bootlable" situation for second time when I was downgrading from Q beta 2 back to Pie. But I am probably lucky one Same situation like you, only bootloader screen and PC didn't see my phone, but I was able to fix it I was in bootloader, connected to PC and I hold power button for long time (2 minutes maybe more). Phone was still restarting, bootlader screen, black screen, bootlader, black.....sometimes it vibrated. After this 2 minutes I just tried "flash-all.bat" command and phone arose from the dead and is working.

somin.n said:
Hi, I got to this "not bootlable" situation for second time when I was downgrading from Q beta 2 back to Pie. But I am probably lucky one Same situation like you, only bootloader screen and PC didn't see my phone, but I was able to fix it I was in bootloader, connected to PC and I hold power button for long time (2 minutes maybe more). Phone was still restarting, bootlader screen, black screen, bootlader, black.....sometimes it vibrated. After this 2 minutes I just tried "flash-all.bat" command and phone arose from the dead and is working.
Click to expand...
Click to collapse
This should work. Had something similar happen to me, keep holding power for about 10 seconds or so while it keeps rebooting until you feel the phone vibrate. Release the power button, connect to the computer and it should detect it then.
https://forum.xda-developers.com/showpost.php?p=78744315&postcount=31

somin.n, I just wanted to thank you for rescuing my phone. After a lot of problems with Q, I decided to go back to Pie and bricked the bootloader. I tried your trick and it came back - but ... I flashed Pie, it rebooted and hung on the "G" screen. So I did a factory reset and resigned myself to use the refurb they sent me. This morning I tried once more and flashed Pie. Voila! The phone works. The original, non-refurb, phone. So now, since the refurb they sent me has the "bootloader unlockable flag = '1', but the bootloader won't unlock" problem, which seems to be common, there's another refurb on its way. So on Tuesday, I'm returning two refurbs to Google.
But you saved my phone so, again, thank you.

Rukbat said:
somin.n, I just wanted to thank you for rescuing my phone...
Click to expand...
Click to collapse
Hey, you are welcome I was really lost when it happened to me, because google is not selling phones in our country officialy, so no RMA and secondly, my pixel is my bussiness phone so I can't tell to my boss that my phone is broken because of flashing beta builds Yeah, I had to find a solution

Zenfone 6 stays black after EDL Mode

Hi!
TL,DR:
Phone froze while using, and it kept freezing. Now phone wont boot at all, only EDL Mode works. However, after EDL phone wont still boot.
Longer story:
I've got quite a problem here. I was playing Pokemon GO with my friend yesterday. Suddenly my phone went quiet. I saw PoGo froze for 5 seconds and then phone rebooted itself. It went back to LineageOS (17.1) which I've installed successfully via TWRP. Then the phone rebooted itself again many times again and again, and each time it crashed earlier than before. When LineageOS did fail for booting for several times, the phone went straight to bootloader. I tried to open recovery but it crashed too. Then It came back to bootloader and I said Power Off.
I waited for half an hour but the phone was failing boot. It wen't even worse: the phone wont go to bootloader any longer, it just stays black.
I've done an EDL Mode recovery couple of times before when I was messing around my first custom ROM installation with Lineage. Now when I set the phone to EDL Mode via cable I made (it was an easy task) I can hear Windows detecting my phone (which it didn't detect before) and uses the QDLoader 9008 EDL Driver.
Then I use the "update_image_EDL.bat" to regenerate the partitions.
Now here's the tricky part: After the .bat file the phone should reboot to bootloader, however this doesn't happen, and the phone just exits ELD mode (I can hear it from Windows it doesn't detect the phone anymore) and then just stays black. It doesn't react to any buttons or cables, and Im also sure it has battery. I even opened the case and removed the battery from its port and putting it back to see if the phone reacts then my actions, but no.
It feels like the only thing I can do here is the ELD mode. I tried it several times later, and that's all.
Also trying to continue with the instructions with QDLoader 9008 fix (the flashall_AFT.cmd) won't lead anywhere, because Windows doesn't detect the phone after that.
Thank you in advance for any tips and tricks.
Edit: Just to add; I've tried removing SDcard and SIM cards also. No effect.
Edit2: Here's the copy of the 'update_install_EDL.bat' results: https: //paste.ofcode.org/bPLQA6T484rKEEb2URa8yv

After more failed tries and thinking, my friend was looking at my log from update_install_EDL.bat he was thinking about the warning it gave. Well, I went looking for the sector limit which was put by rawprogram4.xml and I added the missing sector to the count. Now the error is missing from log but it went nowhere in the progress however. I've done the .bat now many times, but nothing seems to be working. I've removed the battery and put it back before edl and after edl and tried booting with just the powerbutton and with the Vol+ and power btn, but nothing comes up.
If you got a log from the update_install_EDL.bat, I'd appreciate if you could post it somewhere for me to see did you get the same warning as I did.
I also want to point out that ANY comment is welcome... I keep you posted whenever theres some progress.

Okay. I decided to take my Zenfone 6 to Asus authorized repair shop. They said I've got short circuit in the motherboard. God knows how that happened. However I can't get it under the warranty because earlier I repaired my broken screen glass in a unauthorized repair shop. which has voided the warranty. Asus told me that the repair would cost me 527,2 EUR (624,30 USD). I'll not be paying that much for a repair, so it looks like Im out of the business..
I also want to note that I purchased the phone 4.6.2020 and it was in the screen repair for 30 days. So with my quick calculations I paid totally 12 eur for each day I had a chance to use it.
Edit: I want to say here that the repair shop takes 60€ (71 USD) for their excellent service. Okay, I admit that they we're quick on the result, for about 30 hours they responded, but ofc I'd like to have more info but they told the phone must be taken to the ASUS factory then.

Hey bud stumbled upon the post somehow!
What was your error code with the EDL script? (Link that you had shared expired :/) was if shahara error? I'm not so experienced but combining the infos that I've read across the forum maybe try charging the phone for 8+ hrs and try again. Also try diff cable, the one that came with the phone. There are two contact points at the back with which you can force EDL mode as said here. Also the firmware folder should be kept in the main drive (C:// or D) and named without spaces just alpha numerics. Lots of people seems to be getting the same Sahara error damn. Let us know any of these got it fixed! Cheers

Honestly it seems like whoever ASUS sourced to make the main motherboards did a rubbish job with all the failures. My wifes bog standard firmware just died 16 days out of warranty.
ASUS should either offer extended warranty and free motherboard replacements or conduct a voluntary recall to fix them.
I didn't spend a grand to use a phone for 12 months.

abx12 said:
Hey bud stumbled upon the post somehow!
What was your error code with the EDL script? (Link that you had shared expired :/) was if shahara error? I'm not so experienced but combining the infos that I've read across the forum maybe try charging the phone for 8+ hrs and try again. Also try diff cable, the one that came with the phone. There are two contact points at the back with which you can force EDL mode as said here. Also the firmware folder should be kept in the main drive (C:// or D) and named without spaces just alpha numerics. Lots of people seems to be getting the same Sahara error damn. Let us know any of these got it fixed! Cheers
Click to expand...
Click to collapse
Yeah Im sorry for the log. The warning on there was basicly telling that the bios.img is larger by one sector than the sector size given to the update_install_edl.bat. It was fixed by adding the one sector to the rawprogram4.xml file.
I was aware of the sahara fail, it was fixed by unplugging the cable and back in (restarting the edl mode ofc). And I also tried another cable.
What comes to the directory (folder) names I was aware of that too, the script don't do a very good job with folders having spaces or special letters.

homerlovesbeer said:
Honestly it seems like whoever ASUS sourced to make the main motherboards did a rubbish job with all the failures. My wifes bog standard firmware just died 16 days out of warranty.
ASUS should either offer extended warranty and free motherboard replacements or conduct a voluntary recall to fix them.
I didn't spend a grand to use a phone for 12 months.
Click to expand...
Click to collapse
My working theory is that this high failure rate is affecting all of series so they have no way to determine which units should be fixed/replaced. It's very sketchy but they've put themselves into this situation with poor QC in the first place.