Develop Bugs

[Q] Error switching to Cyanogen

I have a G2. I decided to root it using the guides on Lifehacker and Cyanogens wiki. I got a temproot using Visionary, and permaroot using terminal. Everything went swimmingly. I only used download links that I found on Lifehacker and on Cyanogen's site (the same places I got the guides to root my phone) I attempted to root my phone and put CM7 on it. I backed up everything with Titanium Backup. I downloaded Rom Manager, flashed ClockworkMod Recovery to get the latest version, downloaded CM7 through Rom Manager, and attempted to install it as well as backup existing ROM and wiping data and cache. My G2 returns to the HTC startup screen and just stops.
I tried to do a factory reset, it just stops at the same area. I tried doing a factory reset from the startup options (power and down volume), nada. I tried reflashing ClockworkMod Recovery, zilch. I restored my backup from Titanium, nothing.
The phone works, I'm able to do everything I would normally do on it, but I just can't get this to work and I don't know where I went wrong or how to fix it. I have experience with UNIX based systems so I know how to work a command line to an extent and I know that part went off without a problem. I just can't figure out what's going on with it.

can you connect to your phone using adb? if you can access the shell you might be able to figure out why it's hanging.

ADB
I'm not sure I've tried ADB, any tips?
Are you talking about hooking it up to my computer as an alternative method to flash it? I had a bit of trouble with that because my computer is currently down (I just moved and don't have the room to set it up yet). I think I need a copy of the original ROM for my phone as well, if I get that I believe I can restart the whole process and do it right this time. Any ideas where to get it?

yes hook it up to the PC, even if it's in a bootloop you might be able to access the phone's system to do repairs using adb to enter the shell.
check this thread: http://forum.xda-developers.com/showthread.php?t=865685
it also explains how to use it
http://developer.android.com/guide/developing/tools/adb.html
this one got all the adb commands.
I'm not sure about the log command, but there's a way to call on the system log to see where it fails.
it's not recommended to flash an original image again, you can try to restore the backup of the original ROM (nandroid backup) if you made one...
hope this can help you.

Sounds like there is a problem with your recovery, try to manually flash recovery using flash_image instead of ROM Manager.
Use this thread for a guide: http://forum.xda-developers.com/showthread.php?t=902493
You can get the latest version of CWM (currently 3.0.2.4) here: http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html just scroll down to the link that says "HTC G2"
After you flash try to manually go into recovery by shutting down the phone and powering it up while holding the volume button down, this should bring you into the bootloader menu and allow you to launch recovery.

Thanks!
I'll give that a try as soon as I can, thanks for the assistance!

HELP PLEASE - EVO 3D Stuck in Bootloop!

Hello All,
I recently rooted my EVO3D using the HTCDEV method because the bootloader was version 1.5.
Here are the steps I followed to root (sorry for the copy and past but I want to be as detailed as possible)
Files Used
su 2.3.6.3
TWRP Recovery
Steps Taken:
1)Take both the su.zip and recovery.img files and put them in your sdk tools folder.
2)Now do the following in ur command prompt, hitting enter after each command.
3)Code:adb push recovery.img /sdcard/And,
4)Code:adb push su-2.3.6.3.zip /sdcard/Then,
5)Code:adb reboot bootloaderUr phone will go to fastboot and should look like the after picture above. Now you can flash the twrp recovery, so do,
6)Code:fastboot flash recovery recovery.imgIt will ouput something like this,
7)Code:sending 'recovery' <5068 KB>... OKAY////writing 'recovery'... OKAY///finished. total time: 11.355sNow you have twrp recovery, so you can navigate to it. On ur phone, use the power button to pick bootloader, then scroll down to recovery and pick that. You will then be booted into recovery.
8)Here you can pick "install zip" and then pick the "su-2.3.6.3.zip"
It will flash, the you can pick "back to main menu", then "reboot system now"
9)You will boot back up and have working Superuser. I have had no trouble with Titanium Backup, Root Explorer, Quick Boot or any other app that requires root. Before you do too much, it would be good to go back to recovery and do a Nandroid backup. Always best to get one ready before you start modding anything.
All of this worked fine, and the phone was "unlocked."
Then, I flashed the most recent version of CleanRom (2.7)
Again, the phone worked fine, battery life was a little crappy.
I decided to flash Ziggy's kernel.I flashed the kernel simply by putting on the SD card, and then rebooting into recovery. This worked fine as well, but I noticed some of the buttons for example the menu popups displayed volume where it should have said more, or bluetooth options where it should have said preferences. so this is where the trouble started, I downloaded kernel manager, and flashed silverneedle through that program. Now, I am stuck at the White HTC Splash screen bootloop. The phone turns on and after 15 seconds reboots, and reboots, and reboots.
What Ive attempted:
I have done countless wipes and clears of the dalvik cache and cache
ive formatted the system and the date sections (advanced menu in twrp)
ive reflashed the rom after wiping countless times
ive tried flashing different kernels in recovery to no avail
factory reset and wipe havent helped
im not concerned losing the contents of the SD card
I need help because I already had two phone claims in the past 11 months, and if I claim another lost phone I will lose insurance for life with Asurion (sprint)
anytips or help would be greatly appreciated
i can provide any additional info

Similar situation, Not sure if you've already solved the problem but I'm going to copy paste my solution from another thread...
Hi, I'm not sure if this is the right place to ask but this is a preety derp question. I've gone across the internet and tried a lot of reflashing to repair my sort of "bricked" evo. What happened, was that I had a evo 3d s-on htc bootloader unlocked, with custom recovery -clockwork..anyways I had flashed the leedroid 3d 4.0 rom and It worked the only problem was my wifi, so i attempted to flash another kernel onto it, but I had accidently flashed "Rcmix" kernel which I later found out was cdma =.=. so now my phone keeps rebooting at the htc screen, it would just load up with the green htc letters, then after 10 seconds or so it'd reboot, and then begin the process again. I can boot into bootloader and recovery but whatever I flash doesn't seem to work including restoring my backups...and then the battery died so i couldn't even charge it or go in. But i managed to work out I could load into bootloader from the CMD and the furthest i've gotten to is to have the bootloader show FASTBOOT USB. SO I must be getting somewhere...? I did read that i had to load from the cmd and not just from power+vol down..but I'd appreciate any help towards restoring my phone to the way it is or at least before i flashed the rcmix.
Just a note tho I've tried factory resetting but all i get is that it loads into recovery at the bootloader options i dont get "clear storage" as an option and "restore to factory settings" and what not just boots me into recovery agian.
EDIT:
I Managed to fix the phoneeee!!!..just for future preferences and anyone else who has this problem...
I followed bits and piece of IL DUCE's advice to izzy spun, the important part was booting the recovery from cmd. I wasn't able to "erase recovery" But I tried just booting it,
First I would remove the battery,
Put it back in,
Plug the usb cable in
1. Type command, from your Adb/fasboot folder, "adb reboot-bootloader"
2. After that I made sure my bootloader said "Fastboot USB", and then I issued the command, "fastboot boot cwm-4.0.1.4-shooteru.img" or with whatever recovery you had..
3. From there I restored from my backups my original rom. Rebooting, and fixed.
--- and It worked. At the time I was on clock work recovery, i only had the Revolutionary recovery img. Cwm-4.0.14.-shooteru.img to be exact,
after going in there I just cleared the cache and davlik and then, proceeded to restore my backups (I'm not sure if it would've worked if I had re-flashed the leedroid or a custom rom)
and then I simply rebooted the phone, and it got back into my phones original state before leedroid (as I had Only backedup before then)....
Apologies for the lengthly post, but I guess reading does help, but I've been going nuts before I managed to fix this. Just thought I'd leave this post incase someone were to need this.

Same problem
Hi there. I just recently joined so excuse my noobness but i have a similar problem. I recently just rooted my evo 3d sprint with the the boot 1.5 and everything went well. I decided i wanted to overclock my phone so i followed zeemaxs way. Before going into the overclock procedure i decided to do the the RCMIX Evo 3d kernel v. 2.2.3 first so i would have better results when done with the overclock procedure.I bootup the kernel through the recovery mode on the phone butit failed to load so i just reeboted. After that my wifi and 4g stopped working. So i downloaded an app on the market called "flash image GUI" which lets me flash the kernels through the app. I flashed the RCMIX kernel and rebooted and now im stuck ima boot loop. I COULD just go back and back up to my old rom and settings etc...........but the problem is i dintmake any kind of back up or recovery i think. I know i know im stupid and an idiot but i just sort of panicked n ended up with this. If anyone can help please tell me.I do not want to pay for a new phone at full price. PLEASE HELP THIS POOR NOOB!!!!! X(

awsomepanda20 said:
Hi there. I just recently joined so excuse my noobness but i have a similar problem. I recently just rooted my evo 3d sprint with the the boot 1.5 and everything went well. I decided i wanted to overclock my phone so i followed zeemaxs way. Before going into the overclock procedure i decided to do the the RCMIX Evo 3d kernel v. 2.2.3 first so i would have better results when done with the overclock procedure.I bootup the kernel through the recovery mode on the phone butit failed to load so i just reeboted. After that my wifi and 4g stopped working. So i downloaded an app on the market called "flash image GUI" which lets me flash the kernels through the app. I flashed the RCMIX kernel and rebooted and now im stuck ima boot loop. I COULD just go back and back up to my old rom and settings etc...........but the problem is i dintmake any kind of back up or recovery i think. I know i know im stupid and an idiot but i just sort of panicked n ended up with this. If anyone can help please tell me.I do not want to pay for a new phone at full price. PLEASE HELP THIS POOR NOOB!!!!! X(
Click to expand...
Click to collapse
What your going to have to do is flash the original kernel you started with. thats why your in a bootloop

Similar problem
Hi everyone!
I have a kind of similar problem, so I won't post it in a new thread.
Yesterday I rooted my phone following this guide: androidforums.com/evo-3d-all-things-root/494212-complete-newbies-guide-rooting-flashing-evo-3d-roms-kernels-using-fastboot . html (i am not allowed to post links to prevent spam).
I unlocked it with htcdev and installed a custom ROM without getting any errors. After restarting the phone, it got into a boot loop; it showed the starting animations of htc and the ROM and then shut down again.
Here some more information:
-Evo 3d Europe gsm
-hboot 1.5
-s-on
-image version 3.28.401
-installed ROMs using clockworkrecoverymod (as proposed in guide)
I have tried these ROMs (all leading to boot loop):
ICS NonSense
Cyanogen Mod 10 – DisarmedToaster (v. 1.4 and 1.5)
Jelly Bean 3d (by Ubuntuz)
SAD 2.1 DEsenseX
I installed the ROMs by doing:
Connect device via usb > flash boot.img via fastboot (from pc) > clear Cashe/UserData/DalvikVM > install rom.zip from sdcard > reboot
I really don't know what to try
Any ideas how I could install a running Android OS are highly appreciated.
Thx for any help

Problem solved!
Ok, I solved the problem by simply relocking the phone and installing the stock ROM with the RUU.exe

RUU.exe
I'm glad someone else mentioned Relocking before running the RUU. I've read several posts be others that have actually stated that Relocking wasn't necessary but in order for the RUU to take you have to Relock. IF you get a chance check out CoolICS Rom and MeanRom both are pretty good.

Thanks all for the help, had to revisit this issue today.

[Q] Oddities of rebooting CWM

Sooo, I got my OTA update for Tiny's CM rom today from GooIM. And low and behold... now I can't seem to access my Clockwork Recovery Mod. I enter Rom Manager, order it to reboot to Recovery, and comes to Fastboot. Or, the two finger salute, Pwr/DnVol yields the same result.
Now the phone insists that it's still Soff, Hboot 0.92, and the like... Rom Manager insists that ~it~ can detect CWM 5.0.2's presence, but any attempt to actually boot into it just results in me ending up on the Fastboot screen.
After various attempts at battery pulls and and at reinstalling RomManager and CWM, I tried instead to flash in an image for TWRP both from the GooIM app, and from ADB. That went nowhere as the phone just keeps returning remote access denied type errors in ADB, and merely booted to fastboot and stayed there till I rebooted it normally when done via the app.
Also, the refresh feature seems to have gone kerplooey. From within the rom it just restarts and sends me to the fastboot screens when I ask it to go nuclear, and if I try it from the fastboot screen, it just restarts.
So, I could use some help at this point on how to retake control of my Dinc. Right now I can't change rom's, wipe the caches, etc...

eoraptor said:
Sooo, I got my OTA update for Tiny's CM rom today from GooIM. And low and behold... now I can't seem to access my Clockwork Recovery Mod. I enter Rom Manager, order it to reboot to Recovery, and comes to Fastboot. Or, the two finger salute, Pwr/DnVol yields the same result.
Now the phone insists that it's still Soff, Hboot 0.92, and the like... Rom Manager insists that ~it~ can detect CWM 5.0.2's presence, but any attempt to actually boot into it just results in me ending up on the Fastboot screen.
After various attempts at battery pulls and and at reinstalling RomManager and CWM, I tried instead to flash in an image for TWRP both from the GooIM app, and from ADB. That went nowhere as the phone just keeps returning remote access denied type errors in ADB, and merely booted to fastboot and stayed there till I rebooted it normally when done via the app.
Also, the refresh feature seems to have gone kerplooey. From within the rom it just restarts and sends me to the fastboot screens when I ask it to go nuclear, and if I try it from the fastboot screen, it just restarts.
So, I could use some help at this point on how to retake control of my Dinc. Right now I can't change rom's, wipe the caches, etc...
Click to expand...
Click to collapse
Reflash cwm http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip thru hboot.
How to flash - http://pvillecomp.com/?page_id=79.
Then see if you can access it. If you can do a full wipe, and then either restore a backup or flash a rom of your choosing.

I would aslo recommend using Team Wins recovery now its more user friendly has some tools you might find handy and well touch based lol
Sent from my rooted GameBoy Color!!! ^¬^

Took me a month, but I finally got past both my frustration and some meat-space interruptions. Yes, the instructions provided by cmlusco did the trick, thank you SOOOO much.
And ironically, I WAS going to install TWRP onto the device, elzimmer, but when I booted it up, it said it had the OTA update to install, so I let it do that first *rolls my eyes* On reboot I found out that that had tanked the recovery mod before I could even begin doing the factory resets and so forth.
Either way, thanks again both of you.

[Q] Need to get back to stock, no TWRP or recovery.

I'd like to preface this by saying I read the FAQ and did some searching here, but couldn't spot anything that sounded like my problem. I've half got an idea of what to do, but I'm quite confused and feel like some stuff needs clarifying. I apologize if this is more common than I realize, cause if it is I'm sure y'all are sick of answering questions like this.
---
I got a used Kindle Fire from a friend that came with CM10 on it. I wanted to use it for reading, but the Kindle android app was recently broken by Amazon so I reluctantly reverted it back to stock (I really liked having a tablet, but I've got a phone for that stuff and I needed an e-reader). The very next day they fixed the app so I decided I should load CM10 back onto the Kindle. Now, I flashed CM10 onto my phone last year and it was a painless process so I figured it'd be the same here. Somehow in the process I completely messed things up.
From stock FireOS, I used Kindle Fire Utility to flash TWRP on my Kindle, then from there installed CM10 again. What I didn't know, was that CM no longer comes with gApps preloaded. I had no clue, as when I flashed it onto my phone it had all the gApps on there. So I google it and find out I need to flash gApps on there. Here's the problem: I can't boot this thing into recovery. Somehow TWRP was lost in the process. I enabled developer options in the settings, then enabled the option to choose reboot into recovery in the power menu but when I choose it, it just reboots into CM10 again. I'm not sure how I'm supposed to revert back to stock or flash gApps in if I can't get to TWRP again.
It's clear this has gotten way over my head.
Summary:
* Have a kindle w/ fresh install of CM10 on it.
* No gApps and can't boot into recovery.
* I think TWRP might be gone somehow.
* I want to either return to stock or get TWRP back safely and gApps flashed on here.

You need to boot back into Kindle Fire Utility and install the boot loader FireFireFire to boot into recovery.

themetalman said:
You need to boot back into Kindle Fire Utility and install the boot loader FireFireFire to boot into recovery.
Click to expand...
Click to collapse
I can't seem to get KFU to recognize my plugged in Kindle. IIRC when I first used KFU, when it recognized the Kindle it displayed "ADB Status: Online" and "Boot Status: 4000". Now it's ADB Offline / Boot Unknown.

I've been told elsewhere that I need to locate a stock recovery image and load it up using terminal emulator since it appears my recovery was broken. Where might I find one for my Kindle? I perused the various stickied threads / guides around here but did not see one.
e: Would it be against the rules re: buying/selling if I offered whoever helps me get this fixed $10? Haha.

TheSMP said:
I've been told elsewhere that I need to locate a stock recovery image and load it up using terminal emulator since it appears my recovery was broken. Where might I find one for my Kindle? I perused the various stickied threads / guides around here but did not see one.
e: Would it be against the rules re: buying/selling if I offered whoever helps me get this fixed $10? Haha.
Click to expand...
Click to collapse
I have used the download and the bottom of this page to repair a bricked kindle fire.
Link: http://n2aos.com/
Then go back into kindle utility and reinstall TWRP and firefirefire.
You might also want to look at this site. He has great tutorial videos. Link: https://sites.google.com/site/tomsgt123/all-videos/kindle-fire

help my firetv stuck in boot loop

first timer here,
so I had my fire tv for a week it was rootable so I had it rooted and running on 51.1.4.1_514013920
fixed, for some reason i decide to install boot menu, so I could just update once the 51.1.4.2 comes out
and now it would not boot kernel. every time i try it just loops back I could still boot in to recovery
but i already have the rom removed from the device
I just wanna ask if there's anyway i could load the rom back into the firetv with recovery mode
and install it from there? Or could i remove the boot menu in anyway?
thank you so much for your help

gk83916 said:
first timer here,
so I had my fire tv for a week it was rootable so I had it rooted and running on 51.1.4.1_514013920
fixed, for some reason i decide to install boot menu, so I could just update once the 51.1.4.2 comes out
and now it would not boot kernel. every time i try it just loops back I could still boot in to recovery
but i already have the rom removed from the device
I just wanna ask if there's anyway i could load the rom back into the firetv with recovery mode
and install it from there? Or could i remove the boot menu in anyway?
thank you so much for your help
Click to expand...
Click to collapse
If you can boot in recovery install 51.1.4.0_514006420-rooted+updated, this is the last firmware that does not required a boot menu. As far as I know 51.1.4.1 requires it so not sure how did you manage to run this rev without the boot menu. Let me guess, did you try installing boot menu using Firetv Utility s/w? After reverting back to 51.1.4.0 follow the guide from AFTnews and install boot menu manual sending one commend at the time.

Thank you for the reply
But how do I install the frimware in recovery?
Because u had it deleted from the firetv
Is there any way I could load it back in the within recovery?

gk83916 said:
Thank you for the reply
But how do I install the frimware in recovery?
Because u had it deleted from the firetv
Is there any way I could load it back in the within recovery?
Click to expand...
Click to collapse
I've always used adb push but if that's not an option (because you can't connect) I'm pretty sure you can copy the update to a usb drive then insert in aftv and get it from there. Actually I've read that's the preferred method for lots of people.
But it doesn't hurt to re-read Rbox's threads and/or aftvnews guides.

KLit75 said:
I've always used adb push but if that's not an option (because you can't connect) I'm pretty sure you can copy the update to a usb drive then insert in aftv and get it from there. Actually I've read that's the preferred method for lots of people.
But it doesn't hurt to re-read Rbox's threads and/or aftvnews guides.
Click to expand...
Click to collapse
So I could just plug a USB drive in there and it would work?!
Thank you so much I will give it a try tonight

alright this is what happened I finial took care of this boot loop thing
the reason is i install boot menu twice so once the first boot menu try
to boot into kernel it goes to the second boot menu and that's how the
boot loop started
luckily i could still get into recovery so from there I tried everything
finally i find the think called advanced putty
from there I was able to load 5140 and removed both menus
reroot busybox did everything and now got a fire tv fully working
rooted and all good
Thank everybody for helping out
good luck