Database Develop

Nexus One boot loop issues

Hi everyone,
I have a problematic Nexus One. I've googled the issue and read all the corresponding threads and none of them seem to have boot loop issues as bad as mine. At least I dont think so, anyway.
Where should I start? I recently bought the phone off ebay. The seller did clearly state the phone's issues and that he couldn't be bothered fixing it, let alone paying over $200 to send it back to Google to be repaired or replaced (from Australia). Call me a sucker for punishment, but I do like dabbling in electronics so I thought I'd give this a go and hopefully will be successful. It wouldn't bother me if it rebooted once every few days then rebooted again normally but this isn't the case. I'll try to describe it's behaviour as precisely as I an and I sincerely hope the collective expertise on this forum will be able to help me successfully resolve this issue. BTW, I've been using a gorgeous Desire since July.
The Nexus one is running Modaco r21, 4.06.00.12_7 radio, 2.6.32.9 kernel, CMR 2.5.1.0.
1. When the phone has been powered down for at least 5 mins, it will power up as normal. If left alone on the bench or very lightly used ie a few minutes, then pwr button sleep, no problem. If I continue 'sleeping' the phone every few minutes while using it it continues to function normally for a few hours. If I don't 'sleep' the phone and use it continuously, then after about 20 mins it goes into a reboot cycle with the static 'X' going on and off every few seconds then ending up with the continuously on "X" with the unlocked padlock underneath, which is unrecoverable until the battery is pulled.
2. Battery reinserted immediately after removal and the reboot cycle continues. I can boot into the white Recovery or Fastboot sreens but when I select an action like Recovery, the boot loops starts again. Battery pulled and reinserted again, boot loop occurs again. Pull battery and leave it out or powered down with battery inserted for 5 mins, reboots normally. Then point '1' above continues.
3. I have Rom Manager, Titanium and Superuser Permissions installed. I received the phone with Eclair installed and after many attempts managed to install the new radio and Modaco R21. Last night I tried doing a back up via Rom Manager since I cant get into the black Recovery screen and now Titanium and SU are force closing.
This is all I can think of right now and will update with more info as they come to light. I've been trying to install setcpu to see if underclocking will help however I have been unsuccessful due to SU force closing. I am an Android and Linux noob but am always willing to learn. I really would like to get more stability in this phone so I can either use it as my primary or back up.
Thanks in advance for all your help.
Edit. I magaed to do a factory reset when it dont momentarily allow me into Recovery mode. Wiped all data and davlic as well.

My first instinct is that the phone has suffered or is suffering from a heat problem of some type.
Do you have the android SDK set up on your computer? You should be able to flash an aftermarket recovery using the "fastboot flash" commands. You could also use the "adb reboot recovery" command to reboot the phone directly into recovery mode.

I'll give your suggestions a try. What fastboot commands should I be entering? I am an absolute virgin with all this.
Sent from my HTC Desire using XDA App

I think this thread should have some good information for you

Thanks for the link, mate. I'll have a read and I'm sure there'll be more Q's soon.
Sent from my HTC Desire using XDA App

Hi again,
I've installed Android SDK and usb drivers. Where do I go from there? I am a complete newbie at this so please be kind.

julian.kueh i was posting to ask how things have been progressing along this matter?

I got the same problem. No matter what I do, I can get into Recovery. It stay in loop with X
I change twice recover and nothing.

Incredible S not booting at all!

I bought this HTC a few weeks back, was installing Swype and the phone went into a boot loop and later on displayed a red traingle on booting, so I removed the battery and tried turning it on, it would not boot, I did not root it or did any customizations to it. The most annoying thing is that I bought it in Malaysia and now am on holidays in India and it just had to happen at this moment, lucky I took my old N 97 along. When I connect it to the laptop I get the QHSUSB_DLOAD in the device manager and have no clue what to do, if there is anything I can do before getting back to Malaysia and giving it for service please do help.

Try taking battery out - also take sd card out - and leave for a few mins then reboot.
you could also try booting into hboot ... power on whilst holding volume down - you maybe able to do a recovery from there.

Tried everything I could, nothing really helped, yet thanks for your interest in the issue

Can't you do a factory reset from recovery?
/ Sent from my HTC IncS
using XDA Premium App /

did u make any stock recovery thru htc sync? might as well send it back to htc..
basically without htc sync, the stock recovery is useless

[Q] Another boot loop, but this one is different! SOLVED

C6603 Stuck in bootloop! [Last update: 24/1/14]​
UPDATE 24/01/14
This issue has been SOLVED.
I replaced the battery with one from eBay and the phone is working flawlessly, all the ROM flashing I went through was not the problem at all. Remember that if you are going to try to replace the battery you may as well buy a new rear glass piece as it is almost guaranteed that the glass will break in the removal process. You will also require new a adhesive piece. The entire procedure cost me $51AUD (battery, glass, adhesive).
All the content below is irrelevant, if your phone randomly shuts off (instantaneously) on boot or soon after, try to replace your battery!
Thanks for your help.
I've got quite a story to tell and if you have the patience to read it, I will greatly appreciate your assistance. TL;DR BELOW
In the beginning I was running 4.2.2, on a stock Australian 10.3.A.0.423 Unbranded ftf. It had been working flawlessly for a month or so until quite recently. It had developed a problem where it would only remain switched on whilst being plugged into the wall socket. As soon as (or thereafter) I removed the plug out of the phone, with one touch, one action, BAM! The display was off and I had to restart the phone again. I spent a few hours browsing for solutions to this problem, most of them said to hold the power and vol+ buttons until the handset vibrated 3 times. That turned it off alright, but I'm looking to go in the other direction.
After a stressful while scrounging old forum posts, I came to the conclusion that the fault is in my ROM, after all, I had flashed from 4.1.2 (I think) to 4.2.2 just a month prior (I flashed a ROM instead of waiting until the snail-like carriers here in Australia decided to dribble out the release). So now being convinced that I ROM is at fault I browse XDA for a newer stock one. Hey! Look! 4.3 it being rolled out in Aust, I check whether it's available to me yet, and obviously, no, it is not. I stumble upon this thread in my travels. I spend a while working to meet it's requirements. Get flashtool, get unlocked bootloader, get root, install cwm, and attempt to install XzDualRecovery 2.6. I've placed the XDR.zip on the sdcard in the XZ, I run the zip using CWM, it seems successful, I then go to reboot and check whether my 4.3 works, after I select reboot I'm asked whether I wish to root the phone. Why yes! that seems easy enough, and just as I select 'ok' the screen goes blank. The bloody phone has switched off in the middle of my work! I try to boot and it hangs on the Sony logo then reboots, creating a cycle. I decide to plug it back in to the wall socket (as this is the only way to get it to boot and remain on), huzzah, it runs. But the root had failed. The rest of my rant is insignificant until now (around 7 hours of failed attempts later)
So in an attempt to keep this wall of text down, I try my best to summarize, If I am not clear enough, just say.
I tried reflashing my old 4.2.2 ROM back, this makes the whole thing worse, now the phone won't even get past the Sony logo (even when plugged to a socket), I flash a different 4.3 ftf, nothing, I restore with PCC, I restore with SUS, I create a ftf from the SUS files and attempt to flash that. Nothing, nothing works. So where am I at now?
The phone still has battery, although, I'm not sure how much, I can no longer get it to charge as it hangs on the Sony logo. The phone should be flashed with 10.3.A.0.423, but when I check the baseband version in Fastboot cmd prompt, it still says 10.4.B.0.569, I feel as though flashtool isn't flashing properly, but I've read that this is usually a non-issue. I can boot into flashmode and fastboot mode. I can unlock and lock the bootloader. I can use ADB and Fastboot CMD (Minimal version) to read values and run commands. Actually, I managed to use the phone in fastboot mode, in conjunction with ADB and Fastboot CMD, I ran the command "fastboot continue" and the phone went on to charge off the usb power, It didn't seem to charge very fast, or at all, and I haven't been able to get it to do it again. So a TL;DR:
-C6603 stuck in bootloop.
-Possibly has a 4.2.2 ROM installed (10.3.A.0.423 Unbranded AU)
-Cannot Charge
-Can run flashmode and fastboot mode
-Can use ADB and Fastboot
-Can use SUS, PCC, and Flashtool to flash stock roms
-Can't figure this out for the life of me!
UPDATE 01/01/14
Currently I have a kernel installed that allows me to use cwm twrp (doomkernel v19, maybe), I have flashed a 'flashable' stock 4.3 rom using cwm and the phone didn't manage to get past the kernel logo. HOWEVER, using fastboot mode, I run the command "fastboot continue", and if I allow the phone to go past the kernel logo it vibrates, the LED turns green as opposed to showing a purple one, and it will begin charging (The LED isn't green as a result of the battery level). EDIT [1/1/14 3:01AM]: I tried to launch the phone whilst it was charging, the charging symbol went away and the phone remained on a black screen (lcd is on, but nothing is displayed) for a few seconds before shutting off automatically.
I must mention, I cannot get into recovery unless I boot the phone into fastboot mode, run the command in fastboot: "fastboot continue". If I don't do this, it simply crashes (shuts off) when showing the kernel logo.
If you need to know more I will provide as much information as I can, as succinct as I can, as fast as I can. I am in this for the long run. Thank you for your time,
UPDATE 08/01/14
I've come to the conclusion that my issue is battery related. After repeated from flashes and fastboot attempts, I managed to get the phone charging a few times, I witnessed the level was sporadic upon infrequent viewings. I have come across a few other very similar threads and feel that it is necessary to try replacing the battery, I try and post a youtube clip that details what happens currently.
Keringkien

keringkien said:
C6603 Stuck in bootloop!​
I've got quite a story to tell and if you have the patience to read it, I will greatly appreciate your assistance. TL;DR BELOW
In the beginning I was running 4.2.2, on a stock Australian 10.3.A.0.423 Unbranded ftf. It had been working flawlessly for a month or so until quite recently. It had developed a problem where it would only remain switched on whilst being plugged into the wall socket. As soon as (or thereafter) I removed the plug out of the phone, with one touch, one action, BAM! The display was off and I had to restart the phone again. I spent a few hours browsing for solutions to this problem, most of them said to hold the power and vol+ buttons until the handset vibrated 3 times. That turned it off alright, but I'm looking to go in the other direction.
After a stressful while scrounging old forum posts, I came to the conclusion that the fault is in my ROM, after all, I had flashed from 4.1.2 (I think) to 4.2.2 just a month prior (I flashed a ROM instead of waiting until the snail-like carriers here in Australia decided to dribble out the release). So now being convinced that I ROM is at fault I browse XDA for a newer stock one. Hey! Look! 4.3 it being rolled out in Aust, I check whether it's available to me yet, and obviously, no, it is not. I stumble upon this thread in my travels. I spend a while working to meet it's requirements. Get flashtool, get unlocked bootloader, get root, install cwm, and attempt to install XzDualRecovery 2.6. I've placed the XDR.zip on the sdcard in the XZ, I run the zip using CWM, it seems successful, I then go to reboot and check whether my 4.3 works, after I select reboot I'm asked whether I wish to root the phone. Why yes! that seems easy enough, and just as I select 'ok' the screen goes blank. The bloody phone has switched off in the middle of my work! I try to boot and it hangs on the Sony logo then reboots, creating a cycle. I decide to plug it back in to the wall socket (as this is the only way to get it to boot and remain on), huzzah, it runs. But the root had failed. The rest of my rant is insignificant until now (around 7 hours of failed attempts later)
So in an attempt to keep this wall of text down, I try my best to summarize, If I am not clear enough, just say.
I tried reflashing my old 4.2.2 ROM back, this makes the whole thing worse, now the phone won't even get past the Sony logo (even when plugged to a socket), I flash a different 4.3 ftf, nothing, I restore with PCC, I restore with SUS, I create a ftf from the SUS files and attempt to flash that. Nothing, nothing works. So where am I at now?
The phone still has battery, although, I'm not sure how much, I can no longer get it to charge as it hangs on the Sony logo. The phone should be flashed with 10.3.A.0.423, but when I check the baseband version in Fastboot cmd prompt, it still says 10.4.B.0.569, I feel as though flashtool isn't flashing properly, but I've read that this is usually a non-issue. I can boot into flashmode and fastboot mode. I can unlock and lock the bootloader. I can use ADB and Fastboot CMD (Minimal version) to read values and run commands. Actually, I managed to use the phone in fastboot mode, in conjunction with ADB and Fastboot CMD, I ran the command "fastboot continue" and the phone went on to charge off the usb power, It didn't seem to charge very fast, or at all, and I haven't been able to get it to do it again. So a TL;DR:
-C6603 stuck in bootloop.
-Possibly has a 4.2.2 ROM installed (10.3.A.0.423 Unbranded AU)
-Cannot Charge
-Can run flashmode and fastboot mode
-Can use ADB and Fastboot
-Can use SUS, PCC, and Flashtool to flash stock roms
-Can't figure this out for the life of me!
If you need to know more I will provide as much information as I can, as succinct as I can, as fast as I can. I am in this for the long run. Thank you for your time,
Keringkien
Click to expand...
Click to collapse
download any FTF , 4.2.2 or 4.3 , connect your device to flash tool as flashmode , and select to flash the ftf , when you are selecting the ftf in the flash tool , at the right side check all at the wipe section , and uncheck all at the exclude section
but your internal storage might get also wiped , but i assume it already happened when you unlocked your boot loader

elias234 said:
download any FTF , 4.2.2 or 4.3 , connect your device to flash tool as flashmode , and select to flash the ftf , when you are selecting the ftf in the flash tool , at the right side check all at the wipe section , and uncheck all at the exclude section
but your internal storage might get also wiped , but i assume it already happened when you unlocked your boot loader
Click to expand...
Click to collapse
Alrighty then, I'll give that a go later. I have just found a 4.3 for Australia, perhaps it will be different. Thanks for the quick reply.

keringkien said:
Alrighty then, I'll give that a go later. I have just found a 4.3 for Australia, perhaps it will be different. Thanks for the quick reply.
Click to expand...
Click to collapse
this thread could be helpful : http://forum.xda-developers.com/showthread.php?t=2229250
i'm not sure if that problem could be solve, but it was, like you said, different. never saw anything like that either.
Anyway:
Can it boot into custom recovery in its state now?( for mounting storage for something else in case you have cwm or twrp installed)

Jambu95 said:
this thread could be helpful : http://forum.xda-developers.com/showthread.php?t=2229250
i'm not sure if that problem could be solve, but it was, like you said, different. never saw anything like that either.
Anyway:
Can it boot into custom recovery in its state now?( for mounting storage for something else in case you have cwm or twrp installed)
Click to expand...
Click to collapse
Thanks so much for the reply. The thread has something I can try, if this new rom fails (I expect it will). What is custom recovery? I cannot access the storage, only fastboot and flashmode. no cwm and xdr was never completed.
ROM just failed, trying SUS now.

keringkien said:
Thanks so much for the reply. The thread has something I can try, if this new rom fails (I expect it will). What is custom recovery? I cannot access the storage, only fastboot and flashmode. no cwm and xdr was never completed.
ROM just failed, trying SUS now.
Click to expand...
Click to collapse
oh dear, custom recovery is cwm (clockworkmod recovery) or twrp (team win recovery project), it means, it allows you to do something important just before it boot into system, which is bootstall or bootloop as you call it. you cannot boot into system, then try to boot into recovery ( which is before it boot the system), that might help.
both recoveries will allow you to mount storage to copy things to sd cards from pc.
you can try unlock bootloader and flash custom kernel with recoveries, maybe you "could" boot into one of those recoveries.

I also got the same problem, but mine is a C6602. I was trying to setup a mail exchange, then it asked for some permission. I push enter, then after an hour, it start the bootloop.
The phone boot till the main screen, i could swipe and play around for 10 second, then it reboot.
I have tried everything from hard reset, to FlashTool to SUS, relock, unlock, flash stock, from old stock to new stock, it just won't work :|

Jambu95 said:
oh dear, custom recovery is cwm (clockworkmod recovery) or twrp (team win recovery project), it means, it allows you to do something important just before it boot into system, which is bootstall or bootloop as you call it. you cannot boot into system, then try to boot into recovery ( which is before it boot the system), that might help.
both recoveries will allow you to mount storage to copy things to sd cards from pc.
you can try unlock bootloader and flash custom kernel with recoveries, maybe you "could" boot into one of those recoveries.
Click to expand...
Click to collapse
I'm well aware what cwm is, I just assumed that because you said 'custom' that it might possibly be different, as recovery is always custom anyway, sorry for the misunderstanding.
I am able to flash a 'boot.img' that enables me to use cwm and twrp, HOWEVER, the only way I can access it (as in cause the phone to remain on long enough for it to parse the boot.img) is to connect the phone to my computer in fastboot mode, then using the Fastboot command: "fastboot continue", it will run the 'img' and allow me to enter twrp or cwm. It still won't begin charging or even show the Xperia logo if I allow it to continue without accessing the recovery options.
Thanks for your help.

keringkien said:
I'm well aware what cwm is, I just assumed that because you said 'custom' that it might possibly be different, as recovery is always custom anyway, sorry for the misunderstanding.
I am able to flash a 'boot.img' that enables me to use cwm and twrp, HOWEVER, the only way I can access it (as in cause the phone to remain on long enough for it to parse the boot.img) is to connect the phone to my computer in fastboot mode, then using the Fastboot command: "fastboot continue", it will run the 'img' and allow me to enter twrp or cwm. It still won't begin charging or even show the Xperia logo if I allow it to continue without accessing the recovery options.
Thanks for your help.
Click to expand...
Click to collapse
if you can mount the storage, you could copy the flashable stock rom (4.3) and copy it into your sd card, and maybe you can flash through there by following instructions from that thread.
---------- Post added at 11:21 PM ---------- Previous post was at 11:20 PM ----------
billhainh said:
I also got the same problem, but mine is a C6602. I was trying to setup a mail exchange, then it asked for some permission. I push enter, then after an hour, it start the bootloop.
The phone boot till the main screen, i could swipe and play around for 10 second, then it reboot.
I have tried everything from hard reset, to FlashTool to SUS, relock, unlock, flash stock, from old stock to new stock, it just won't work :|
Click to expand...
Click to collapse
look for the disaster recovery thread i posted above

Jambu95 said:
if you can mount the storage, you could copy the flashable stock rom (4.3) and copy it into your sd card, and maybe you can flash through there by following instructions from that thread.
---------- Post added at 11:21 PM ---------- Previous post was at 11:20 PM ----------
Click to expand...
Click to collapse
I tried to mount the storage, my pc wouldn't detect the phones storage, I managed to push the stock rom zip to the sd card using ADB. I still had cwm recovery and could flash the zip using it. Still, however, the phone shuts down before it gets past the kernel logo. Again, I used the phone in Fastboot mode and forced it to continue using "fastboot continue", I left it go past the kernel logo and it is charging at the moment. I may try to start the phone now, yet expect it to crash again.
EDIT: I tried to launch the phone whilst it was charging, the charging symbol went away and the phone remained on a black screen (lcd is on, but nothing is displayed) for a few seconds before shutting off automatically.
EDIT: Happy New Year!
Thank you.

keringkien said:
I tried to mount the storage, my pc wouldn't detect the phones storage, I managed to push the stock rom zip to the sd card using ADB. I still had cwm recovery and could flash the zip using it. Still, however, the phone shuts down before it gets past the kernel logo. Again, I used the phone in Fastboot mode and forced it to continue using "fastboot continue", I left it go past the kernel logo and it is charging at the moment. I may try to start the phone now, yet expect it to crash again.
EDIT: I tried to launch the phone whilst it was charging, the charging symbol went away and the phone remained on a black screen (lcd is on, but nothing is displayed) for a few seconds before shutting off automatically.
EDIT: Happy New Year!
Thank you.
Click to expand...
Click to collapse
this problem occurs with every kernel you've used (including stock and custom kernels)?

Jambu95 said:
this problem occurs with every kernel you've used (including stock and custom kernels)?
Click to expand...
Click to collapse
Yes that is correct, it's current issue (turning off sponanteously) occurred when I was running stock 4.2.2 (no root, no bootloader unlock).

keringkien said:
Yes that is correct, it's current issue (turning off sponanteously) occurred when I was running stock 4.2.2 (no root, no bootloader unlock).
Click to expand...
Click to collapse
lol, you should unlock the bootloader before you flash a custom boot.img. the primary solution now is to flash any rom to see if it boots up normally , then you can still find a way to revert back to stock.

Jambu95 said:
lol, you should unlock the bootloader before you flash a custom boot.img. the primary solution now is to flash any rom to see if it boots up normally , then you can still find a way to revert back to stock.
Click to expand...
Click to collapse
I never said that I flashed a custom boot.img whilst on a locked bootloader. The reason I tried all the things that I have is because the phone was spontaneously shutting down (on stock, unedited). Perhaps once I made the mistake of flashing a boot.img before unlocking, but I have since unlocked and flashed many roms and kernels. Thanks for your reply.

keringkien said:
I never said that I flashed a custom boot.img whilst on a locked bootloader. The reason I tried all the things that I have is because the phone was spontaneously shutting down (on stock, unedited). Perhaps once I made the mistake of flashing a boot.img before unlocking, but I have since unlocked and flashed many roms and kernels. Thanks for your reply.
Click to expand...
Click to collapse
the device can't get pass the sony logo?

edNHour consum
Jambu95 said:
the device can't get pass the sony logo?
Click to expand...
Click to collapse
That is correct, it doesn't hang but suddenly turns off, the only way I can use recovery tools in the kernel is if I plug the phone into my pc in Fastboot mode, then issue the command "fastboot continue" from cmd.

keringkien said:
That is correct, it doesn't hang but suddenly turns off, the only way I can use recovery tools in the kernel is if I plug the phone into my pc in Fastboot mode, then issue the command "fastboot continue" from cmd.
Click to expand...
Click to collapse
i think there is something wrong with your motherboard or the battery connection, i'm not sure, because my pc got that problem before, it just boot up to starting windows... and then reboot, in the end i found out the capacitor got swelled in the power supply.

Jambu95 said:
i think there is something wrong with your motherboard or the battery connection, i'm not sure, because my pc got that problem before, it just boot up to starting windows... and then reboot, in the end i found out the capacitor got swelled in the power supply.
Click to expand...
Click to collapse
That is certainly possible, I have had to replace the back glass and during that operation it is possible that the battery got too hot and is now lower in voltage or something. Thanks for the suggestion, I would appreciate a second opinion with this...
Thank you.

keringkien said:
That is certainly possible, I have had to replace the back glass and during that operation it is possible that the battery got too hot and is now lower in voltage or something. Thanks for the suggestion, I would appreciate a second opinion with this...
Thank you.
Click to expand...
Click to collapse
if you still have your warranty, you can go to the center and request for a replacement, the best solution now is to revert to as stock as possible, if can get the bootloader locked again then it's good,

Jambu95 said:
if you still have your warranty, you can go to the center and request for a replacement, the best solution now is to revert to as stock as possible, if can get the bootloader locked again then it's good,
Click to expand...
Click to collapse
I imagine it is still under warranty, however I have read that unlocking the bootloader permanently voids warranty. And I have replaced the back of my white phone with a black glass, perhaps if I get a new white rear glass it will be ok, but then I might as well just replace the battery $40AUD isn't too expensive IMO.

[Q] Booting Trouble after Rooting HTC Desire 500 Dual Sim

Hi !
Warranty just finished of my HTC Desire 500 Dual Sim. So, I decided to root the phone. I followed the instructions available on unlockr.com.
Everything finished very well. But then after installation of SuperSU 0.9.8.zip, my phone didn't boot for next 15 minutes. So, I just took out the battery and tried to restart the phone. But it refused to restart. Then I kept the battery out for next 30 minutes and then tried to restart. After few retries, My phone started.
While accessing SuperSU application, it kept me informing about Update required. I tried to update the app, but it failed and restarted my phone. So, I downloaded the SuperSU 2.0.2.zip file from official site and kept it on sd card. And followed the process of installing SuperSU from FASTBOOT and Then Recovery. IT worked well.
After doing all this, everything seems fine. Only problem I am facing is - if I switch off my phone, it doesn't start immediately. I have to keep the battery out for next 10 minutes, and then have to re-insert the battery and then my phone will start.
Is there any way to overcome this starting problem?

JPSBhullar said:
Hi !
Warranty just finished of my HTC Desire 500 Dual Sim. So, I decided to root the phone. I followed the instructions available on unlockr.com.
Everything finished very well. But then after installation of SuperSU 0.9.8.zip, my phone didn't boot for next 15 minutes. So, I just took out the battery and tried to restart the phone. But it refused to restart. Then I kept the battery out for next 30 minutes and then tried to restart. After few retries, My phone started.
While accessing SuperSU application, it kept me informing about Update required. I tried to update the app, but it failed and restarted my phone. So, I downloaded the SuperSU 2.0.2.zip file from official site and kept it on sd card. And followed the process of installing SuperSU from FASTBOOT and Then Recovery. IT worked well.
After doing all this, everything seems fine. Only problem I am facing is - if I switch off my phone, it doesn't start immediately. I have to keep the battery out for next 10 minutes, and then have to re-insert the battery and then my phone will start.
Is there any way to overcome this starting problem?
Click to expand...
Click to collapse
Hey, i have the same problem, the only way is to not shut down the phone, but only restart it when needed. and if you want full root you should install the ultimate kernel

How to install ultimate kernel
gayTony said:
Hey, i have the same problem, the only way is to not shut down the phone, but only restart it when needed. and if you want full root you should install the ultimate kernel
Click to expand...
Click to collapse
Thanks for your response. Can you suggest me some guide to do full root by installing ultimate Kernel.
I got the link on XDA is http://forum.xda-developers.com/showthread.php?p=52681146#post52681146
But this thread says phone needs to have software version 1.32 or 1.26. I just checked my phone's software version is 1.12. So, it means I can not install ultimate kernel.
And is there any way to coming to original kernel after installing custom kernel ?

JPSBhullar said:
Thanks for your response. Can you suggest me some guide to do full root by installing ultimate Kernel.
And is there any way to coming to original kernel after installing custom kernel ?
Click to expand...
Click to collapse
Sure there is. you can go back anytime.
Heres how to install the Ultimate kernel.
1. Go and download boot7_no_oc.img http://forum.xda-developers.com/showthread.php?t=2752625
2. Put the .img file to the directory of adb.
3. Connect your phone to your PC.
4. Start up ADB and type *adb reboot bootloader*
5. Your phone should restart to the bootloader, DO NOT UNPLUG THE CABLE!
6. In bootlader mode you should see FASTBOOT USB in red letters.
7. When you see that, in your cmd type fastboot flash boot boot7_no_oc.img
8. After it finishes you can type fastboot reboot.
Be sure to click the thanks button if i helped

Phone not even booting
gayTony said:
Sure there is. you can go back anytime.
Heres how to install the Ultimate kernel.
1. Go and download boot7_no_oc.img http://forum.xda-developers.com/showthread.php?t=2752625
2. Put the .img file to the directory of adb.
3. Connect your phone to your PC.
4. Start up ADB and type *adb reboot bootloader*
5. Your phone should restart to the bootloader, DO NOT UNPLUG THE CABLE!
6. In bootlader mode you should see FASTBOOT USB in red letters.
7. When you see that, in your cmd type fastboot flash boot boot7_no_oc.img
8. After it finishes you can type fastboot reboot.
Be sure to click the thanks button if i helped
Click to expand...
Click to collapse
I followed the process, you mentioned. But it didn't work. After switching off, I had to keep out the battery for another 10 mins.
then re-inserted the battery and switched on the phone.

JPSBhullar said:
I followed the process, you mentioned. But it didn't work. After switching off, I had to keep out the battery for another 10 mins.
then re-inserted the battery and switched on the phone.
Click to expand...
Click to collapse
the ultimate kernel does not solve the problem, it just helps to get full root

gayTony said:
the ultimate kernel does not solve the problem, it just helps to get full root
Click to expand...
Click to collapse
I need solution for booting problem, full root is not desirable.

JPSBhullar said:
I need solution for booting problem, full root is not desirable.
Click to expand...
Click to collapse
Well i can't help you with that, if i know anything, i will pm you

gayTony said:
Well i can't help you with that, if i know anything, i will pm you
Click to expand...
Click to collapse
Thanks.
I hope any other XDA User will contribute to this thread.
According to my knowledge every HTC Desire 500 DUAL SIM user is facing the same issue after rooting the phone.
So, there should be some reason as well as solution to the problem.

S-off will helpfull for your problem. At least, restart and booting are working well immediately after power off.

JPSBhullar said:
Thanks.
I hope any other XDA User will contribute to this thread.
According to my knowledge every HTC Desire 500 DUAL SIM user is facing the same issue after rooting the phone.
So, there should be some reason as well as solution to the problem.
Click to expand...
Click to collapse
I had the same problem like you in the beginning,but now the phone doesn't even start..I left the battery outside the phone 24 hours and nothing...doesn't start anymore

Hboot not Showing on My Phone
Hello,
I want to Root my Desire 500. During the process of rooting when i was in middle of recovery process a wrong command to my phone was given by me the phone went kind of Dead for several Hours. Now it has Started but as by rootchecker app described not rooted properly . My phone doesnt starts quickly and and doesnt respond to the Power button and Volume Down press i.e. it doesnt show me the hboot screen. Kindly Let me know is There any fix to this issue. thanks

Human_Being said:
Hello,
I want to Root my Desire 500. During the process of rooting when i was in middle of recovery process a wrong command to my phone was given by me the phone went kind of Dead for several Hours. Now it has Started but as by rootchecker app described not rooted properly . My phone doesnt starts quickly and and doesnt respond to the Power button and Volume Down press i.e. it doesnt show me the hboot screen. Kindly Let me know is There any fix to this issue. thanks
Click to expand...
Click to collapse
Connect your phone to pc and then use adb toolkit to pass commands to your phone.
Copy latest supersu to sd card. then restart the phone into bootloader using adb commands.

staru22 said:
I had the same problem like you in the beginning,but now the phone doesn't even start..I left the battery outside the phone 24 hours and nothing...doesn't start anymore
Click to expand...
Click to collapse
Put your phone on charging for 5 minutes. then take out the battery for next 5 minutes. After 5 minutes, put the battery in, press power button, then nothing will happen at the same time. but it will take 2-3 minutes to start. After 2-3 minutes, phone will boot up with htc logo.
This is the way, I am doing with my phone.

Human_Being said:
Hello,
I want to Root my Desire 500. During the process of rooting when i was in middle of recovery process a wrong command to my phone was given by me the phone went kind of Dead for several Hours. Now it has Started but as by rootchecker app described not rooted properly . My phone doesnt starts quickly and and doesnt respond to the Power button and Volume Down press i.e. it doesnt show me the hboot screen. Kindly Let me know is There any fix to this issue. thanks
Click to expand...
Click to collapse
Disable fast boot under power under settings

Disabling fastboot is not working. Any other solution?
Sent from my HTC Desire 500 dual sim using XDA Free mobile app

JPSBhullar said:
Hi !
Warranty just finished of my HTC Desire 500 Dual Sim. So, I decided to root the phone. I followed the instructions available on unlockr.com.
Everything finished very well. But then after installation of SuperSU 0.9.8.zip, my phone didn't boot for next 15 minutes. So, I just took out the battery and tried to restart the phone. But it refused to restart. Then I kept the battery out for next 30 minutes and then tried to restart. After few retries, My phone started.
While accessing SuperSU application, it kept me informing about Update required. I tried to update the app, but it failed and restarted my phone. So, I downloaded the SuperSU 2.0.2.zip file from official site and kept it on sd card. And followed the process of installing SuperSU from FASTBOOT and Then Recovery. IT worked well.
After doing all this, everything seems fine. Only problem I am facing is - if I switch off my phone, it doesn't start immediately. I have to keep the battery out for next 10 minutes, and then have to re-insert the battery and then my phone will start.
Is there any way to overcome this starting problem?
Click to expand...
Click to collapse
Try to flash the stock room,maybe this will solve your problem

For flashing Stock ROM, I need ROM and Firmware both. But in XDA, there is no firmware for Dual Sim Htc desire 500. So, Can't do much

ROM and Firmware not available
driter said:
Try to flash the stock room,maybe this will solve your problem
Click to expand...
Click to collapse
For flashing Stock ROM, I need ROM and Firmware both. But in XDA, there is no firmware for Dual Sim Htc desire 500. So, Can't do much.
Tried requesting in few threads, but no response till now.

blitzzkrieg said:
S-off will helpfull for your problem. At least, restart and booting are working well immediately after power off.
Click to expand...
Click to collapse
how to s-off dual sim ?

Phone do not boot after Oreo update

As i installed update and clicked reboot to apply it, now my system do not boot. Phone always stuck on white NOKIA logo boot screen forever. I tried few times to restart it via VOL-UP + POWER, but it always have same result - never boots. Please give me advice how to deal with it

It happened to me too, in December already. Mobile is in service now.
They flashed original fw, tested and returned it with results no fault. Right after switch on and new Oreo update it starts to freeze and produce various mistakes again, so I have returned phone to service. Will complain with seller about exchange.

ravkhar said:
It happened to me too, in December already. Mobile is in service now.
They flashed original fw, tested and returned it with results no fault. Right after switch on and new Oreo update it starts to freeze and produce various mistakes again, so I have returned phone to service. Will complain with seller about exchange.
Click to expand...
Click to collapse
That really sucks. But what do you mean by various mistakes? Like your system boots, but some functionality is not working? As i said in my case it totally cannot boot and recovery mode i can't enter factory recovery mode by VOLUME UP + POWER on start.

gornex said:
That really sucks. But what do you mean by various mistakes? Like your system boots, but some functionality is not working? As i said in my case it totally cannot boot and recovery mode i can't enter factory recovery mode by VOLUME UP + POWER on start.
Click to expand...
Click to collapse
Ach yes, sorry. First it stucked in logo Nokia and rebooting again... VolumeUp+Power does not work normally on Nokia.
It helped procedure found here:
https://forum.xda-developers.com/showpost.php?p=74406267&postcount=34
Then I was able to make factory reset and mobile booted, but worked with various faults.

Did you unlock your bootloader , flashed TWRP and then changed the slot? Slot A to B or vice versa?
If so, then the solution is
How to solve!
I simply waited until the battery ran out
When battery was completely dead and no Nokia-logo appear any more >>
Then I charged the battery 3% juice without booting
and from there I entered recovery-mode with the help of a USB cable.
Holding the volume+ button while connecting the USB-cable
From TWRP-recovery I changed to the other inactive slot
and whooala, that's it!
Edit: I sucked the juice (mAh electric-capasity) out of the battery quicker with help of OTG-cable and an external USB-powerd fan.
Use almost any external max 5volt USB-powered devices available at home, even charging another phone unless the second phone doesn't reverse-charge, this Nokia can be used as a power-bank.