Develop Bugs

***need help please***

two days ago, i rooted my phone using simple root, nand unclocked and flashed clockwordmod and everything. i was using fresh rom, and i wanted to use the vanilla lockscreen. but in order to do that, i needed to flash amons ra. i tried doing that, and somehow i got rid of my clockword recovery mod (and amons ra didnt work) so whenever i went into recovery mode, it just stayed at the screen with the phone and triange and red exclamation mark. i tried running the recovery windows .bat file, but it didnt work. and i tried running the ruu .exe file to unroot my phone, but everytime it said it couldnt find my device, even though it was connected via a usb chord. i tried it in charge only mode, disk drive mode, and htc sync mode and none of them worked. i tried using rom manager, but everytime i tried doing something it said error attempting to run privilidged scrips or something. i tried downloading the superuser .apk file and installing it onto my phone, but that didnt work either. the terminal emulator didnt work when i tried to flash something, it just said it couldnt find the file on my sd card, even though i put it on there. help?

Okay, number one: Did you try holding volume UP + power at the red exclamation screen? I think that's how you enter AR recovery.
Number two: You can flash Fresh tweaks without using AR. You just have to reboot into ClockworkMod and flash the .zip files manually.
Are you able to boot ANY ROM right now? If so, is it rooted? If it is, try to reinstall ROM Manager.
Sounds like you went a little off the deep end when you couldn't get into AR.

any suggestions?

Yeah, answer my questions or provide more info so you can get better direction.

you can reflash either recovery with the simple root program or you can follow the first part of toasts root method part 2 to restore recovery.

SilverZero said:
Okay, number one: Did you try holding volume UP + power at the red exclamation screen? I think that's how you enter AR recovery.
Number two: You can flash Fresh tweaks without using AR. You just have to reboot into ClockworkMod and flash the .zip files manually.
Are you able to boot ANY ROM right now? If so, is it rooted? If it is, try to reinstall ROM Manager.
Sounds like you went a little off the deep end when you couldn't get into AR.
Click to expand...
Click to collapse
ill try your first suggestion. and i cant boot any rom right now, because rom manager isnt working. and im pretty sure my phone is rooted, because i still have dev tools and CIQ settings and all those rooted apps.
update: your first suggestion worked, except once i entered AR recovery, the only options i had were: reboot system now, apply sdcard:update.zip, wipe data/factory reset, and wipe cache partition. at the bottom, it said "E: can't open /cache/recovery/command,

t3project said:
you can reflash either recovery with the simple root program or you can follow the first part of toasts root method part 2 to restore recovery.
Click to expand...
Click to collapse
i tried reflashing with simple root but it didnt work. can you give me a link for toasts method?

i had a similar problem, i used the OTA simple root, get that and plug ur phone back in with debugging on , one of the drop down menus will let you flash a recovery so flash clockworkmod

okay so somehow i managed to unroot it by wiping my data/cache..but now whenever i try using simpleroot or OTA simpleroot it doesnt work, because it says device is not found. i have it plugged in via usb, usb debugging is on, and ive tried it in charge mode and disk drive mode. anyone know what the problem is?

I'm sure there is a way to fix this, but I would suggest using the full root method by toastcfh.

okay i'll just reroot using that method, thanks. also, whenever im on my computer and im using command prompt, none of the adb commands ever work. do i need to download something for it to work?

Yes, you need the ADB framework. Read the guide (or the one by TheBiles, which is basically a rewrite). The ADB framework is a part of the Android SDK. You have to run ADB commands from the ADB directory (which is actually the "tools" folder inside of the SDK directory, wherever you extract that). Just cd to the tools folder, then run your commands from there.

Recovery induced reboot loop - help!

I need help understanding why I'm stuck in reboot loop with my EVO 4G.
I originally was trying to root the device using unrevoked3 but getting the ERROR "Backup CID is Missing" message and unable to proceed. I followed the instructions at http://androidforums.com/evo-4g-all-things-root/194918-rooting-dummies.html which talk about troubleshooting this. It talks about going into recovery mode to see if I've lost the recovery mode which I did (black screen with phone and read arrows). It says to reboot but I was unable to so I unplugged the battery.
Since then I have been stuck in a mode where the device boots but the sdcard is not recognized and upon completion of boot up it shuts down and vibrates five times. I did a bunch of research last night on understanding what I thought I needed to do alleviate this. My thought was since I was stuck without a recovery image I need to flash new one. At this point I'm fine with not being rooted with all the trouble I've had.
I downloaded the latest stock recovery rom (3.70.651.1) from http://androidforums.com/evo-4g-all-things-root/259446-clockwork-amon-ra-pc36img-files.html and pushed it to my sdcard under the name PC36IMG.zip (with two files .info and recovery.img). I restarted my phone via HBOOT and it sees the zip file, reads it in, goes to checking and then does nothing (back to HBOOT screen). I don't get what I'm doing wrong. I also tried getting the stock image from http://forum.xda-developers.com/showthread.php?t=874091 but I can't seem to open the firmware.zip file to try that recovery image.
Again I just want to get back to stock ROM and recovery files now. Any help would be greatly appreciated!

Boot Loop stuck in Animation help.

Hey everyone. I know there are already a few threads with boot loop animations, and am having difficulties finding the same situation as what I'm going through. Here is what the phone used to have before it randomly started looping:
Rooted - with Stock rom, using ClockwordMod Recovery 5.5.0.2
Used Go Launcher Theme ( if that even matters )
No additional roms installed or anything, the phone is 3 months old.
Ok here is where I'm stuck. I understand I should reflash somethings like recovery image or something, but I'm stuck with one big problem. My computer and phone don't recognize using the USB mount.
The message I get is called "Unable to open lunfile ( no such file or directory)
Here's what screens I can get to:
1. Hold vol up/down while holding power ( the little android with its belly open, and the options Start - Restart Bootloader - Recovery mode - Power Off )
2. Hold vol down - ODIN mode, with the START option only
I can access WMD recovery and factory reset, Try to install my old backup, nothing works at all in that area, no matter what I do.
Can someone advise me a step by step way of getting my computer to recognize my phone, so that I am able to do fastboot, or reflash, or anything to get my phone working again. I can't access my internal memory at all.
It's even possible that I've read too much, and my frustration is getting in the way, if so I apologize! Some guidance would be greatly appreciated!
Thanks in advance of course! I need my phone for business!
Cheers,

Install the drivers on a computer then use fastboot oem unlock. Or just factory reset it from within recovery.
Sent from my Galaxy Nexus using Tapatalk 2 Beta-4

Try my siggy.
I'm not sure about the exact error:
But the link there will get you the correct drivers.
Also, as stated...try to factory reset.
You'll lose your apps/data that way though =/
Hopefully you can get the driver installed and get your computer to recognize.
If so, follow this to back up your apps:
http://forum.xda-developers.com/showthread.php?t=1420351

Have exactly the same setup as you (rooted/stock/CWM) and had the animation bootloop - animation would just loop until a battery pull.
Only thing that solved it was a factory reset from recovery. Been working fine for the 4 weeks since. No need for any reflashing etc. Titanium recoveries have all worked fine as well. Didn't try my Nandroid backup as I thought that may still have the 'fault' built in.

I had a boot loop for every from I tried to flash...wat fixed it was before flashing u need to wipe system data and wipe the cache in the recovery...ie a clean install...then every rom I tried worked...so I think ur missing that crucial step coz it worked for me
Sent from my Galaxy Nexus using Tapatalk

Hey guys, as stated above I've done numerous factory resets, it still seems to boot. I will for sure try to get the drivers installed so my phone is recongised by the computer, but would need step-by-step assistance when doing fastboot, or whatever the next step is.
Looking for more help though! Keep em coming!

?
Any other ideas?
Thanks!

Ok guys, so here's where I'm at now. I've used Jubakuba's sticky link, located here:
http://forum.xda-developers.com/showthread.php?t=1529058
Everything is able to be recognized up to the point where it says "Put the su.zip on your phone."
Since I cannot access my phone contents, since I keep getting this "Unable to open lunfile ( no such file or directory), it does not allow me to add anything to my phone.
I re-installed CWD as stated in the list of things to do, and all that went well. But I have the same issue, I tried factory resetting all that. erase cache, and still stuck with the same issue.
What's my next step now peeps? Looking for a quick answer as I have time to do it tonight!

Edit***
Just tried this trick: but it says it does not recognize the device?? what is going on! Please help someone! Thanks!
Panic Section! (Something is Wrong)
Q: My phone won't boot!
A: The easiest option is to get into recovery and restore a nandroid using the above guide (pull battery to put phone in an off-state if needed).
However, more advanced options are available if you don't have a nandroid available (You're naughty).
Do you have another rom .zip available on your SD card? If so, simply use the above guide for installing a rom to get you booting again.
If not, you can download one on your PC. Boot into fastboot (the green Android with open chest menu).
Move the .zip to the C:\android-sdk-windows\platform-tools folder.
Open ADB.
Change the NAMEOFZIP.zip below to the correct file name...and perform the action.

Surely your computer recognizes your phone. Otherwise how were you able to unlock the bootloader and flash the recovery?
And I've never seen that error message before. It doesn't even make any sense to me. Where are you seeing it? On your phone or on your computer? And in what context? What are you trying to do when it shows up?
If your phone isn't booting I'm not sure that you can copy any files to it yet. (Maybe you can use adb in clockworkmod? I'm not sure) What I do know you can do is flash the stock ROM and start over.
Download the image from Google here:
http://code.google.com/android/nexus/images.html
Here's a instructions for the GSM version:
http://forum.xda-developers.com/showthread.php?t=1366806
For the Verizon version, I can't find the thread at the moment but you just replace the filenames and also there's 2 radios to flash so:
fastboot flash radio *filename*
fastboot reboot-bootloader
fastboot flash radio-cmda *filename*

"Unable to open lunfile ( no such file or directory) appears on the phone, in CWD mode, when trying to attempt "mount Usb" to be able to access my internal storage .
I am attempting your thoughts right now.
I will post with results

Ok I tried to do this step. This is the outcome I received on the computer after even typing the first step:
'fastboot-windows' is not recognized as aninternal or external command, operable program or batch file.
A thing to stress, I'm not sure how to do step 1: 1) Take a Nandroid Backup if you have CWM installed.
EDIT***
GREAT NEWS!
used this setup!
http://android.modaco.com/topic/348161-01-feb-r4-superboot-rooting-the-gsm-lte-galaxy-nexus/
and it worked!
Thank you everyone! Going to play with my phone and make sure it all works!

Macinshak said:
Ok here is where I'm stuck. I understand I should reflash somethings like recovery image or something, but I'm stuck with one big problem. My computer and phone don't recognize using the USB mount.
The message I get is called "Unable to open lunfile ( no such file or directory)
Click to expand...
Click to collapse
the problem is when that happen?? when ur phone is booted and u plug the usb cable to ur pc? or when u are under recovery and want mount the usb mass storage? the second one doesn't work

[Q] Unable to boot Nexus after trying to root

I have the GSM version of the Galaxy Nexus (fresh never booted). I wanted to root the device and install custom roms on it. I booted up the device, enabled debugging, then put the rom i wanted into the /sdcard location via adb. I then tried to follow the instructions found here (can't post links yet, sorry) "galaxynexusroot dot com galaxy-nexus-root how-to-root-galaxy-nexus-universal-guidegsmverizonsprintwindowslinuxmac" to root the phone. I did the following:
1) unlock the device (fastboot oem unlock)
2) flash recovery (fastboot flash recovery optimus_prime-touch-v5.5.0.4-6-GSM.img)
3) rebooted
When I tried to reboot the device gets to the Google screen, vibrates, then reboots. I have tried to go back to the recovery and was able to get to the optimus prime recovery system. I then tried to backup the device to both internal sdcard and to sdcard, each one errored saying "E:unknown volume for path [/emmc/clockworkmod/backup/2012-06-29.00.33.06]
Cant mount backup path."
At this point in time I am unable to do anything with the device. Is there anything I can do to fix this?
Thanks for your time reading this post

I was able to fix this by locking then unlocking the device again. Backing up the phone right now.

Galaxy Note 8 (GT-N5110) PC Connection Problems - Boot Loop - SOLVED by ME

NO ONE?????
ODIN --> Flash Stock Recovery (AP) with NAND Erase All Option Checked (because it seemed to make sense) + Auto Reboot + F. Time Reset --> Reboots to Stock Recovery (did not work before) --> Reboot into Recovery --> Wipe Data/Cache and Dalvik just to be safe (this crashed it before) --> Reboot. THE END
TL/DR: I am currently stuck on recovery/update mode. Any attempt to wipe data or clear dalvik crashes it. any attempt to access data through TWRP crashes it. Flashing stock rom or custom rom does not help. Somethings wrong with /data? It thinks it has root from the CF Auto Root, but does not really? Something wrong with partitions? Should I wipe the nand with ODIN 3.10? Repartition? ugh ... Please help ...
I have searched the forums and found nothing that describes this issue precisely. I have also tried to apply various suggestions to repair, which, for the most part seems to have made it worse. I am hoping that people still look at this forum.
PC - Windows 7
Initially @4.2.2 ---> Touchwiz debloated stock ROM which I rooted. It worked for a couple years, but the device crashed frequently. I do not recall much about the installation, but believe that I used CWM/TWRP at the time. After installing the ROM, I ran triangle away (out of the box, it had 4.1.2, i recall)
I decided to upgrade to the most recent stock ROM (4.4.2). In order to do so, I used an easy installer I found else where on XDA. (http://forum.xda-developers.com/showthread.php?t=2773712 ---ODIN One Click exe). The device was not initially recognized, so I reinstalled the official driver package (said that they already existed, but I installed again anyway). Ran 1-click and it appeared to work.
Initially, the device booted (long startup) and seemed to function. It also preserved all data and programs (presumably did not touch the internal memory - 16 GB) and possibly root /data.
I then tried to root through most recent ODIN with CF auto root. This appeared to work and rebooted (again, showing the updating android apps screen before fully booting).
The only thing that i could find that had changed was the wallpaper (showed on lock screen but not on home screen). I could no longer find the image, so tried to go to /data/data to find it with root explorer equivalent. This is where it started to act weird.
NOTE: I did not clear anything (system cache, etc. at any point)<--a lie (see below)
It showed the root folder fine, but when I clicked on /data it took a while and could not access it. It either rebooted itself or I rebooted, but this time it was stuck in a boot logo loop. I entered download mode and flashed TWRP through ODIN. I set it to not reboot automatically so that the bootloader was not overwritten automatically (thus losing recovery). TWRP came up. The computer recognized it as a Media Device after I mounted USB storage. Just in case, I copied all of the important files from the internal SD Card to my computer. I then tried to go to the file explorer to copy the wall paper and it forced a reboot. At this point it was stuck on a logo screen boot loop again. I was able to enter Download mode and reflash TWRP. This allowed me to enter recovery again, however, now it would only boot directly into recovery (or Download mode if I did the button combo). The interesting thing was that it would reboot two or three times before successfully entering TWRP.
I believe I tried to reflash the stock ROM at this point, which might have worked but made no difference.
I was also having a lot of problems getting Windows to properly recognize the device. I had to reinstall the drivers a couple times. I tried Kies after the problems started and it tried to connect by failed. The diagnose connection did not work either. I was not able to get Kies to connect though I tried several times throughout the attempted repair
I downloaded a stock-rooted 4.4.2 ROM from here and tried to flash it. It failed.
I also tried to flash via Heimdall, but initially could not find any stock ROMs for Heimdall for the Galaxy 8. (The driver utility that is included helped to get the phone recognized by Windows sporadically).
I decided to switch over to CWM touch recovery, which I flashed via ODIN (I was having issues with TWRP again and also could not get windows to recognize the device as a media device when I mounted USB storage). This worked after a couple tries and I was able to enter CWM. I attempted to flash the stock ROM but it failed. Either at that point or when I tried to mount data it returned an error that device did not have root. Again, it would only boot into CWM (on its own) or Download mode (with key combo). At some point around here I cleared the cache and dalvik (error) after it returned an error saying insufficient space when trying to flash ROM.
I dissected the .exe from the autoflash used in the beginning (stock unrooted 4.4.2) and used the contents (system.img, cache.img, hidden.img, tz.img, recovery.img and one other I do not remember) in Heimdall to create a Heimdall package. At this point I figured out I did not need to create the package, but just specify the individual files. I flashed. It appeared to complete System.img successfully and then failed. Tried again with the same result.
Now when I rebooted, it would enter download mode with the Key combo, but otherwise it booted instantly to an error screen to the effect that a firmware installation had failed and to use the repair function in Kies to fix. Kies still did not recognize it.
At this point, I figured I should stop. Currently I can get to the download screen or the error screen. The computer recognizes it but intermittently fails to install driver. Zadig.exe sees it as Gadget Serial. Sometimes Windows just sees it as SAMSUNG_Android, in which case drivers fail. Once or twice I got it to recognize it as Samsung USB Composite Device, but Kies would still not work.
That's all i have for now. If more information is needed, let me know and I will update the post when I get home from work tonight (this is from memory).
Thank you
UPDATE: last night I went home and was able to get it back to the point where I could flash TWRP or CWM recovery. If I try to flash Stock Recovery, it fails. A minor problem is that I cannot turn it off - it just turns it self on again, so the battery keeps running down.