[Q] com.android.phone on CM 10.1 HTC One X - General Questions and Answers

As a newbie I wanted to try out the greatest roms developed by the developers associated with this forum. I went ahead and used Hasoon2000s to root my HTC One X (international), I was successful, later I flashed successfully the rom InserCoin, which got me bored in few days, then I went ahead and tried the CM 10.1, I used the instruction manual provided online, which seemed to me as the easiest of all, everything went very well but I forgot to flash kernel (boot.img) not I have fully functional CM 10.1 installed but it gives the following error:
"Unfortunately, the process com.andrid.phone has stopped" OK button comes and when I click it immediately shows the same message again and again.
Now I am stuck with this, I am still not able to reboot my cell phone directly (by holding volume down and power button) neither had any success with Hasoon2000s tool which previously worked like a charm.
Now any fellow can help me out in this regards, I have seen this question already been raised but to most extend no answers are give.

younismari said:
As a newbie I wanted to try out the greatest roms developed by the developers associated with this forum. I went ahead and used Hasoon2000s to root my HTC One X (international), I was successful, later I flashed successfully the rom InserCoin, which got me bored in few days, then I went ahead and tried the CM 10.1, I used the instruction manual provided online, which seemed to me as the easiest of all, everything went very well but I forgot to flash kernel (boot.img) not I have fully functional CM 10.1 installed but it gives the following error:
"Unfortunately, the process com.andrid.phone has stopped" OK button comes and when I click it immediately shows the same message again and again.
Now I am stuck with this, I am still not able to reboot my cell phone directly (by holding volume down and power button) neither had any success with Hasoon2000s tool which previously worked like a charm.
Now any fellow can help me out in this regards, I have seen this question already been raised but to most extend no answers are give.
Click to expand...
Click to collapse
I had the same problem about a week ago, and I solved it.
Did you/Are you sure you flashed the right boot image? That's extremely neccisary. Open up the CM10.1 folder and flash boot.img ('fastboot flash boot boot.img' in fastboot) and erase all of your cache and data and reboot.
Let me know if this worked or not!
Sent from my HTC One X using xda premium

I had the same problem, it was because i was flashing wrong. Because of The bootloader you have to flash from fastboot. You have probably flashed a zip from recovery?
You have tot place The boot.img in your fastboot folder, flash it to your device andere after that flash from recovery.
You can find your boot.img in the zipfile on your phone. Remember all your wiping andere stuff. The fastboot command is:
fastboot flash boot boot.img
At least that was the issue with me.

Related

[Q] Odd CWM bootloop

Hey guys, I installed CWM on my buddies HTC one S (ville) and I keep getting a weird problem with CWM. I have successfully flashed CM10 multiple times and have made only one back up. Every time his phone dies and he plugs it in and tries to power it on it boots straight to recovery and after you press reboot phone it boots right back to recovery again and again... The only way it fixes itself is when you restore the back up and then it sets him back to that date. I'm wondering if this is a problem with CWM or something else... I'm new to HTC devices because I have always been on the Galaxy line from Samsung so some of this is a little new to me...
Thanks in advance!!
This is a known glitch with CWM. If you plug it in when its off and try to turn it on, it'll automatically Boot into CWM Recovery. I prefer TWRP personally, had too many problems with CWM and getting into the same exact pain-in-the-neck Bootloop as you're referring to.
As far as I am aware, there isn't a way to get out of the CWM Bootloop unless you just let the phone run out of Battery, get into the Bootloader (Which is somewhat of a challenge with the CWM Bootloop), and then flash a different Recovery from Fastboot. Correct me if i'm wrong on there not being any other way around this.
It's happened to me once, I flashed the.stock boot.img and it worked fine.after that. Not sure if its a fix but it got me outta of it.
echo en Android
Thanks guys I think I'll try TWRP but just to check does CM10 work with TWRP and if so how do I flash a new recovery?
yes cm10 worx with twrp. For flashing recovery, download d appropriate recovery.img for ur device. place this in the fastboot folder or the platform-tools folder.
now, boot into bootloader and enter fastboot then connect phone to PC , it should say fastboot USB .
Now open a command window and use this command---
fastboot flash recovery recoveryname.img.
Sent from my One V
mattytom87 said:
Thanks guys I think I'll try TWRP but just to check does CM10 work with TWRP and if so how do I flash a new recovery?
Click to expand...
Click to collapse
Cyanogenmod 10 does indeed work with TWRP as far as I know. Along with mihirengg19's Reply above, there is also an Alternative way to flashing a new Recovery, and that is to use the HTC One S All-In-One Toolkit. Its the easiest/safest way, if you don't know what you're doing.
yes toolkit is great but manually is best...
Sent from my One V

Device stuck in bootloop?

Hi guys,
So this is my first post but I've been on XDA for a long time. I've been looking for an answer to this problem, and I haven't been successful in finding a post that regards to my situation...
Ok so I just got my tablet today. I upgraded to JB and then I unlocked it using the asus unlocker. I attempted to install TWRP, but when I use .blob files and attempt to load into recovery it didn't work. Anyway, I looked around and I installed CWM recovery instead.
I installed v5.5.0.4 following this guide:
http://theunlockr.com/2012/05/25/how-to-install-clockworkmod-recovery-on-asus-transformer-tf300t/
Now, I notice it's written back in may of 2012 aka before jelly bean... anyway so I installed this using fast boot, and booted into recovery and it worked. I believe I installed the ICS version of CWM. I tried to install Clean Rom v3.3 and I just get bootloops. I can still boot into fastboot and clockwork mod fine.
I tried to install v6.0.1.4 via this thread http://forum.xda-developers.com/showthread.php?t=1846554
But once again if I boot into recovery it just does nothing and reboots after a few seconds.
I re-installed v5.5.0.4 and I can wipe data/install everything just as I normally would, and I still have access to Fastboot. Can I get some help on how I can 1 install the correct CWM and 2 install a working rom? I don't think I bricked my device just yet since I can still flash in fastboot etc.
Thanks guys!
You cant't wipe data from bootloader menu, If you do that, you will get unrecoverable brick.
Sorry I believe I mislead you -> I wiped data from within CWM.
Anyway, I used this thread:
http://forum.xda-developers.com/showthread.php?t=1757077
I went back to stock and I think i'll stay there for a little while longer, this process made me nervous (I've rooted my thunderbolt, droid DNA, galaxy tab 2 7" and my friends phones) so anyway I believe I installed the wrong CWM and that caused errors trying to install a JB rom on a ICS CWM... If you have any insight let me know...
undergfx said:
Hi guys,
So this is my first post but I've been on XDA for a long time. I've been looking for an answer to this problem, and I haven't been successful in finding a post that regards to my situation...
Ok so I just got my tablet today. I upgraded to JB and then I unlocked it using the asus unlocker. I attempted to install TWRP, but when I use .blob files and attempt to load into recovery it didn't work. Anyway, I looked around and I installed CWM recovery instead.
I installed v5.5.0.4 following this guide:
http://theunlockr.com/2012/05/25/how-to-install-clockworkmod-recovery-on-asus-transformer-tf300t/
Now, I notice it's written back in may of 2012 aka before jelly bean... anyway so I installed this using fast boot, and booted into recovery and it worked. I believe I installed the ICS version of CWM. I tried to install Clean Rom v3.3 and I just get bootloops. I can still boot into fastboot and clockwork mod fine.
I tried to install v6.0.1.4 via this thread http://forum.xda-developers.com/showthread.php?t=1846554
But once again if I boot into recovery it just does nothing and reboots after a few seconds.
I re-installed v5.5.0.4 and I can wipe data/install everything just as I normally would, and I still have access to Fastboot. Can I get some help on how I can 1 install the correct CWM and 2 install a working rom? I don't think I bricked my device just yet since I can still flash in fastboot etc.
Thanks guys!
Click to expand...
Click to collapse
My suggestion is to flash the latest stock JB blob.
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 reboot
Once you get it sorted then flash the latest twrp for jb.
Now, when I try flashing blobs and I go to boot into RCK (I believe that's the term...) it just reboots the tablet instead of booting into recovery.
Android software is out of my element, if this was some C (somewhat similar to C) or Matlab I would better understand (I'm a senior Mechanical Engineer in college)
Edit:
Ah didn't see your post. I did what you recommended, and actually, while my device said it was on 4.1.1 JB, when I hold pwr/vol down I see a completely different menu now than last time, so I wonder if perhaps my OTA didn't correctly load everything from the firmware update hmm...
undergfx said:
Now, when I try flashing blobs and I go to boot into RCK (I believe that's the term...) it just reboots the tablet instead of booting into recovery.
Android software is out of my element, if this was some C (somewhat similar to C) or Matlab I would better understand (I'm a senior Mechanical Engineer in college)
Click to expand...
Click to collapse
The same way you flashed cwm.
Windows? Start - in search type cmd - press enter
In the cmd window cd to the directory with fastboot.
Hook cable between tablet and usb port on computer.
On tablet hold power and volume down till you see the bootloader menu.
Down volume till you are at the usb symbol - then volume up.
This should put you into fastboot mode - use the commands above.
Wait till the first command completes before you give the second command.
[INDEX][04 Feb 2013]TF300T & TG-INDEX of Roms/Dev Guides/Kernels/Recoveries/etc. You will find the stock firmware here as well as most other needs.
You will have to unzip to get the blob which you should place in the directory with fastboot.
Thank you very much.
So after flashing the most resent blob, I successfully installed CWM recovery and successfully flashed a rom. I'm not sure what the issue was before. Thank you for the help! much appreciated.
undergfx said:
Thank you very much.
So after flashing the most resent blob, I successfully installed CWM recovery and successfully flashed a rom. I'm not sure what the issue was before. Thank you for the help! much appreciated.
Click to expand...
Click to collapse
You're welcome.
Good Luck!

[Q] [HELP] Loop + No access to Recovery

That's my first post here in the One S forum and, unfortunately, not a happy one.
I used to have fun with modding a long time ago, with the HTC Desire, but when I bought the One S, I didn't even root it, until yesterday.
To unlock the bootloader and install the TWRP recovery I used the All-in-One toolkit; then I installed a MIUI v5 porting and updated to the latest version.
Not satisfied with it, this morning I decided to try Sense 5 with TrickDroid 10.3.2: I did a TWRP backup, wiped the necessary and installed the zip.
Now the phone is in an infinite loop.. that would be ok, but I can't get to fastboot or recovery.
The problem is that even before I wasn't able to get to fastboot with the button combo (even if I disabled fastboot in MIUI settings), and to access the recovery I used the command provided in the All-in-One toolkit.
I'm not able to use the All-in-One toolkit since the device can't be found while turning on.
So now I'm here with my phone vibrating every 30 seconds or so and that's a bit frustrating...
Do any of you know what to do?
If you need any further information just ask, and sorry for my English, I hope everything is clear.
Thank you in advance
Francesco
P.S.: It is the S4 version.
fracaccia said:
That's my first post here in the One S forum and, unfortunately, not a happy one.
I used to have fun with modding a long time ago, with the HTC Desire, but when I bought the One S, I didn't even root it, until yesterday.
To unlock the bootloader and install the TWRP recovery I used the All-in-One toolkit; then I installed a MIUI v5 porting and updated to the latest version.
Not satisfied with it, this morning I decided to try Sense 5 with TrickDroid 10.3.2: I did a TWRP backup, wiped the necessary and installed the zip.
Now the phone is in an infinite loop.. that would be ok, but I can't get to fastboot or recovery.
The problem is that even before I wasn't able to get to fastboot with the button combo (even if I disabled fastboot in MIUI settings), and to access the recovery I used the command provided in the All-in-One toolkit.
I'm not able to use the All-in-One toolkit since the device can't be found while turning on.
So now I'm here with my phone vibrating every 30 seconds or so and that's a bit frustrating...
Do any of you know what to do?
If you need any further information just ask, and sorry for my English, I hope everything is clear.
Thank you in advance
Francesco
P.S.: It is the S4 version.
Click to expand...
Click to collapse
Did you flash boot.img after flashing the rom ?
vatsaman said:
Did you flash boot.img after flashing the rom ?
Click to expand...
Click to collapse
I'm now having the same problem: exactly I forgot to flash boot.img after flashing the rom, and my HTC One S now seems to be bricked.
Yesterday I could turn it on and go into HBOOT, but when I chose Recovery or Factory Reset it rebooted and after the HTC logo, a warning logo appeared. Now I cannot do anything with this.
Can you pls give me some advise or how I can fix this problem? Many thanks!:good:
Trung Del said:
I'm now having the same problem: exactly I forgot to flash boot.img after flashing the rom, and my HTC One S now seems to be bricked.
Yesterday I could turn it on and go into HBOOT, but when I chose Recovery or Factory Reset it rebooted and after the HTC logo, a warning logo appeared. Now I cannot do anything with this.
Can you pls give me some advise or how I can fix this problem? Many thanks!:good:
Click to expand...
Click to collapse
That is not a brick lol :laugh:
That warning logo isn't a big deal. Everyone who has unlocked their bootloader gets it. And seems like you have erased your recovery by selecting "Factory Reset".
1. Download All-In-One Tool kit for HTC One S from the Development forum.
2. Flash a custom recovery. TWRP recommended.
3. Boot into recovery, mount sd card, copy your rom.
4. Flash your ROM.
5. Boot into fastboot
6. flash boot.img
7. Restart :good:
vatsaman said:
That is not a brick lol :laugh:
That warning logo isn't a big deal. Everyone who has unlocked their bootloader gets it. And seems like you have erased your recovery by selecting "Factory Reset".
1. Download All-In-One Tool kit for HTC One S from the Development forum.
2. Flash a custom recovery. TWRP recommended.
3. Boot into recovery, mount sd card, copy your rom.
4. Flash your ROM.
5. Boot into fastboot
6. flash boot.img
7. Restart :good:
Click to expand...
Click to collapse
On waiting for your reply I did exactly the same way that you recommended, thanks anyway. But even I tried so many times, my HTC One S's still stucked at the HTC logo
p.s: I tried to flash this ROM: http://forum.xda-developers.com/showthread.php?t=1910738
Trung Del said:
On waiting for your reply I did exactly the same way that you recommended, thanks anyway. But even I tried so many times, my HTC One S's still stucked at the HTC logo
p.s: I tried to flash this ROM: http://forum.xda-developers.com/showthread.php?t=1910738
Click to expand...
Click to collapse
Did you try to remove the SIM card? Mine was stuck in bootloop and only way it worked for me was to remove SIM card, press power button for 10 or more seconds and it eventually booted into bootloader. hope it work for you...

[Q] Help Needed: Unbrick my P500!

Hi,
I have put more than 12 hours of my time, before creating this thread. I have tried things, but still struck, so thought to post it in a new thread. Thanks for all your time.
Currently struck in,
fastboot mode started udc_start()
I tried, fastboot erase recovery -> fastboot flash recovery recovery.img -> fastboot reboot (successfully). But it still struck at same place after reboot.
I tried with different recovery images, but still the same observation. I tried to boot by key combination (volume down+home+power), still same observation.
Earlier, I installed ROM manager through google play and installed CWM recovery, version 5.xxx (which I feel now is a mistake), as I tried to install CM11 from MukilSoni, which needs CWM version 6.xx +. I am able to go into recovery and select CM11 image through CWM and proceed with install steps. But, after initial selection in CWM (like app install, etc) it rebooted and went into fastboot mode.I checked the log, it ended with some return error 7.
Then, I tried to Google and check how to recover from fastboot mode, but all failed. I didnt tried KDZ method, but thought to hear from you guys before making it more messy.
Glad, if I get any help and appreciate it.
Thanks for reading it and your time.
Regards,
Ganesh
Hi,
I have put more than 12 hours of my time, before creating this thread. I have tried things, but still struck, so thought to post it in a new thread. Thanks for all your time.
Currently struck in,
fastboot mode started udc_start()
I tried, fastboot erase recovery -> fastboot flash recovery recovery.img -> fastboot reboot (successfully). But it still struck at same place after reboot.
I tried with different recovery images, but still the same observation. I tried to boot by key combination (volume down+home+power), still same observation.
Earlier, I installed ROM manager through google play and installed CWM recovery, version 5.xxx (which I feel now is a mistake), as I tried to install CM11 from MukilSoni, which needs CWM version 6.xx +. I am able to go into recovery and select CM11 image through CWM and proceed with install steps. But, after initial selection in CWM (like app install, etc) it rebooted and went into fastboot mode.I checked the log, it ended with some return error 7.
Then, I tried to Google and check how to recover from fastboot mode, but all failed. I didnt tried KDZ method, but thought to hear from you guys before making it more messy.
Glad, if I get any help and appreciate it.
Thanks for reading it and your time.
Regards,
Ganesh
Click to expand...
Click to collapse
Did you ever try pull out the battery, reinsert, reboot system with 3 buttons combination? I got several fastboot mode as you're facing, and the system works just fine using above method.
I think you got just soft brick. Please, keep the device stay untouched until someone with such expertise to solve the problem will guide you. I think @akiratoriyama can share his bad experience bricking his lovely p500.
Wish you luck.
PS.
You must to press three buttons a bit longer, do not release it, until recovery mode appearing. Otherwise fastboot mode or blank screen showing instead.
Sent from my Optimus One using xda app-developers app
agk.ganesh said:
Hi,
I have put more than 12 hours of my time, before creating this thread. I have tried things, but still struck, so thought to post it in a new thread. Thanks for all your time.
Currently struck in,
fastboot mode started udc_start()
I tried, fastboot erase recovery -> fastboot flash recovery recovery.img -> fastboot reboot (successfully). But it still struck at same place after reboot.
I tried with different recovery images, but still the same observation. I tried to boot by key combination (volume down+home+power), still same observation.
Earlier, I installed ROM manager through google play and installed CWM recovery, version 5.xxx (which I feel now is a mistake), as I tried to install CM11 from MukilSoni, which needs CWM version 6.xx +. I am able to go into recovery and select CM11 image through CWM and proceed with install steps. But, after initial selection in CWM (like app install, etc) it rebooted and went into fastboot mode.I checked the log, it ended with some return error 7.
Then, I tried to Google and check how to recover from fastboot mode, but all failed. I didnt tried KDZ method, but thought to hear from you guys before making it more messy.
Glad, if I get any help and appreciate it.
Thanks for reading it and your time.
Regards,
Ganesh
Click to expand...
Click to collapse
Two years ago I bricked my phone also after using ROM manger. Though I will never ever use this or similar tools again. But at least, if I remember correctly, I could revive my phone with the "fastboot erase recovery" method http://forum.xda-developers.com/showthread.php?t=1088046. But since you failed is seems to be another problem. I am not a fastboot expert , but since you bricked your phone with ROM manager too, I wanted to share my success story with above mentioned method and installing AmonRa recovery. So maybe you will give it a second try? All I can remember is, that it is extremely important to follow the instructions exactly.
xu3sno said:
Did you ever try pull out the battery, reinsert, reboot system with 3 buttons combination? I got several fastboot mode as you're facing, and the system works just fine using above method.
I think you got just soft brick. Please, keep the device stay untouched until someone with such expertise to solve the problem will guide you. I think @akiratoriyama can share his bad experience bricking his lovely p500.
Wish you luck.
PS.
You must to press three buttons a bit longer, do not release it, until recovery mode appearing. Otherwise fastboot mode or blank screen showing instead.
Sent from my Optimus One using xda app-developers app
Click to expand...
Click to collapse
androidck said:
Two years ago I bricked my phone also after using ROM manger. Though I will never ever use this or similar tools again. But at least, if I remember correctly, I could revive my phone with the "fastboot erase recovery" method http://forum.xda-developers.com/showthread.php?t=1088046. But since you failed is seems to be another problem. I am not a fastboot expert , but since you bricked your phone with ROM manager too, I wanted to share my success story with above mentioned method and installing AmonRa recovery. So maybe you will give it a second try? All I can remember is, that it is extremely important to follow the instructions exactly.
Click to expand...
Click to collapse
Thanks @xu3sno & @androidck
I am also getting help from mukulsoni & others in Official CM11 version 10 thread.
I am able to go into the flash tool (pointed by mukulsoni, http://forum.xda-developers.com/showpost.php?p=49567169&postcount=45)
and able to go 'Select kernel to hotboot' with recovery.img (CWMod-6.4.0.6-Jan16)
But rebooting by HOME+Volume DOWN+POWER --> goes into CWM recovery of v5.0.2.0 (which i installed initially)
I am thinking, what to do next.
I will keep my progress posted here.
Thanks for listening..
agk.ganesh said:
Thanks @xu3sno & @androidck
I am also getting help from mukulsoni & others in Official CM11 version 10 thread.
I am able to go into the flash tool (pointed by mukulsoni, http://forum.xda-developers.com/showpost.php?p=49567169&postcount=45)
and able to go 'Select kernel to hotboot' with recovery.img (CWMod-6.4.0.6-Jan16)
But rebooting by HOME+Volume DOWN+POWER --> goes into CWM recovery of v5.0.2.0 (which i installed initially)
I am thinking, what to do next.
I will keep my progress posted here.
Thanks for listening..
Click to expand...
Click to collapse
Are you sure that you are booting into cwm v5.0.2.0? Version is listed at the top. If that is true, then either the flash tool failed to flash cwm v6.4.0.6, or you have chosen the wrong recovery.img. This can easily happen since they all have the same name. Try to flash it again, but make sure that you use the correct image.
Also, I believe that you may not have any rom installed, or existing rom might be corrupted. So you may want to flash a cm-9 or cm-10.x rom first, just to stabilize and to be sure that you are healthy. Those can be flashed using cwm 5.0.2.0. I can post a link or two, if you'd like.
Edit: Here is a link to cm-10.1.6:
http://jenkins.androidarmv6.org/view/All/job/android/597/
Gapps already included.
Sent from my LG-P509 using Tapatalk 2
ibub said:
Are you sure that you are booting into cwm v5.0.2.0?
Also, I believe that you may not have any rom installed, or existing rom might be corrupted. So you may want to flash a cm-9 or cm-10.x rom first, just to stabilize and to be sure that you are healthy. Those can be flashed using cwm 5.0.2.0. I can post a link or two, if you'd like.
Click to expand...
Click to collapse
+1
CM10.1.6 worked
ibub said:
Are you sure that you are booting into cwm v5.0.2.0? Version is listed at the top. If that is true, then either the flash tool failed to flash cwm v6.4.0.6, or you have chosen the wrong recovery.img. This can easily happen since they all have the same name. Try to flash it again, but make sure that you use the correct image.
Also, I believe that you may not have any rom installed, or existing rom might be corrupted. So you may want to flash a cm-9 or cm-10.x rom first, just to stabilize and to be sure that you are healthy. Those can be flashed using cwm 5.0.2.0. I can post a link or two, if you'd like.
Edit: Here is a link to cm-10.1.6:
http://jenkins.androidarmv6.org/view/All/job/android/597/
Gapps already included.
Sent from my LG-P509 using Tapatalk 2
Click to expand...
Click to collapse
Thanks @ibub for your helping hand.
I will check why recovery image not upgrading as expected. (I didn't manually download CWM5.xx version to my PC. I got it via ROM manager app, so i hope I haven't chosen wrong image)
Yes, I got CM10.1.6 from your link and installation went successfully and able to boot up..
But, it is very slow. (May be it will take some time?!) I will check it.
Between, @mukulsoni advised to install CWM6.xxx via CWM5.0.2.0. I will check how it goes.
mns123 said:
+1
Click to expand...
Click to collapse
Thanks.
agk.ganesh said:
Thanks @ibub for your helping hand.
I will check why recovery image not upgrading as expected. (I didn't manually download CWM5.xx version to my PC. I got it via ROM manager app, so i hope I haven't chosen wrong image)
Yes, I got CM10.1.6 from your link and installation went successfully and able to boot up..
But, it is very slow. (May be it will take some time?!) I will check it.
Between, @mukulsoni advised to install CWM6.xxx via CWM5.0.2.0. I will check how it goes.
Thanks.
Click to expand...
Click to collapse
Yeah, I chose to post that link only to make sure that your phone is healthy. Now you can install any recovery/rom that you want. If your volume keys are broken, I suggest that you flash to twrp recovery. It's touch driven.
Sent from my LG-P509 using Tapatalk 2
Thanks
ibub said:
Yeah, I chose to post that link only to make sure that your phone is healthy. Now you can install any recovery/rom that you want. If your volume keys are broken, I suggest that you flash to twrp recovery. It's touch driven.
Sent from my LG-P509 using Tapatalk 2
Click to expand...
Click to collapse
Yes, I will try installing now new recovery and then new ROM.
Very glad to see the support from you guys... Thanks ibub and all..
[rant] NEVER EVER USE KDZ. PERIOD. :crying: [/rant]
Best of luck on your ROM journey :good:
Thanks
akiratoriyama said:
[rant] NEVER EVER USE KDZ. PERIOD. :crying: [/rant]
Best of luck on your ROM journey :good:
Click to expand...
Click to collapse
Thanks @akiratoriyama.
I have upgraded CWM recovery 6.xx through CWM 5.0.2.0 and successfully installed MukulSoni's Kitkat ROM.
And enjoying eating kitkat..
Thanks all..

Disaster Recovery - Life after wrong Flash ? OnePlus

Hello all,
2 days ago when on vacation i decided to temper around with my OnePlus one that i recently bought (have bought the Chinese version but it was already rooted and had cyanoged mod on it)
All was fine until i decided to flash Paranoid Android and i posted a question here, about how to bypass the always apearing CyanogenMod Simple Recovery tool.
After trying what everyone suggested and not getting result i had 1 last thing that someone suggested:
http://forum.xda-developers.com/showthread.php?p=54717885
If you still have not fixed this issue, for some reason when I was flashing my recovery it would NOT work for the life of me until I changed the name of the custom recovery file to 'recovery.img'. Everytime I flash (for example) openrecovery-twrp-blah-bacon.img it would say success, but it kept rebooting into CM fastboot mode.
Click to expand...
Click to collapse
I misunderstood and i renamed the .zip file from paranoid sources into recovery.img and flash (Kernel) it via some app from play store, i thin it was TRWL
Now my phone is stuck into loading faze and the only thing i can do is enter Fastboot mode.
I tried to do a:
fastboot erase cache
But it did not work, its still stuck in loading and will not do anything.
Could you help me out ? I have a really bad feeling i just lost my phone due to hurrying and not having a pc around to read more.
You can try to fastboot flash recovery(original or proper one that works) but I don't know the exact commands.
In the first case where your recovery would not switch from CM to TWRP/CWR was because you had "Update CM Recovery" enabled in Developer Options. If you ticked that off, then it would have replaced CM Recovery. Its confusing yeah.
So wait... you renamed the .zip to a .img? Thats not good. But at least you can enter fastboot mode so thats at least something. Is your bootloader still unlocked? Are you able to boot into recovery mode? Try fastboot boot <name-of-recovery-for-twrp>.img and see if you can get into recovery.
If you can then perform a wipe and then enable adb sideload within TWRP and then type,
adb sideload <name-of-zip>.zip and then after its done sideloading, reboot
Thanks for the answer.
I managed last night out of 10 flash resets to get the Custom Recovery Tool to booth up.
I was about to give up when i saw it boot and i immediately flashed the CM .zip i had on the phone from last time.
I even managed to get Paranoid android to flash and im very happy.
Thanks for the help
vidockq said:
Thanks for the answer.
I managed last night out of 10 flash resets to get the Custom Recovery Tool to booth up.
I was about to give up when i saw it boot and i immediately flashed the CM .zip i had on the phone from last time.
I even managed to get Paranoid android to flash and im very happy.
Thanks for the help
Click to expand...
Click to collapse
I'd appreciate it if we helped give us a thanks.
Sent from my One using Tapatalk

Categories

Resources