Not sure how to fix it. Before it happened, I was rooted with a Cyanogen rom on 1.6. I also had a black and green theme on. I went to install a new rom called "OpenEclair". I downloaded it, placed it in my sdcard root folder, and tried to install it. I had an installation error and it aborted. At this point, I figured ok, I'll just reboot. It kept me at the G1 screen for over 25 minutes, so I knew something was wrong. So no matter what I did from here on out (trying to perform a backup restoration, flash a different rom, etc), I would be stuck on the G1 screen. Finally, I flashed a JesusFreke rom and it let my phone come back on, so I haven't tried anything since. However, this rom is ANDROID 1.1. It sucks. Is there any way I can get back to either where I started, or even get this OpenEclair 2.1 rom working properly? Any help would be greatly appreciated. When I try to install the OpenEclair rom (before and after downgrade) it will say
E:Can't chown/mod /system/xbin/librank
*No such file or directory)
D:Failure at line 221:
set perm 0 0 06755 SYSTEM:xbin/librank
Installation aborted.
Press Home+Back to reboot
I had this also. The problem went away after I installed DangerSPL which, as stated at the top of the OpenEclair thread, is required to install this on the G1.
If you don't have DangerSPL, OpenEclair will fail to install as it doesn't have enough room to place its files.
However, if you do have it...
I have noticed this with some of the 2.1 ROMs. I think the reason is that, since we flash using an "updater", it wont wipe the partition before flashing. This leaves the possibility that there are old files with different permissions that prevent the new ROM from properly taking.
Boot your phone into fastboot (for the G1, hold the camera button while powering up), set it into usb mode (by the "back" button, I think), then use the fastboot tool to clear the boot and system partitions:
/fastboot wipe boot
/fastboot wipe system
This will clear the "ROM" component from the phone, and you can then go and flash whatever ROM you want. Make sure to wipe the data partition via recovery.
If, after wiping the ROM and rebooting, the phone is stuck at the carrier screen and says "Fastboot USB", that means it tried to boot the usual way and found no data in the boot partition. You need to boot into recovery and flash a ROM. Using "fastboot reboot" or the reboot command from the phone's fastboot screen will cause this. Use the phone's fastboot "power off" button ("menu" in the G1), then boot it into recovery.
Also remember that any install that fails after the "verification" phase will destroy the existing ROM, since you will be left with a partially installed ROM on top of the older one.
Thanks a lot guys. will try all of this when I get off of work. Much appreciation!
Got everything worked out. Just had to install that danger spl :]
Just flashed FastTest rom, pretty freakin' nice I must say!
Is there a way to backup all my apps/contacts/texts before wiping and flashing a new rom?
Related
So I installed this --> showthread.php?t=1197768
However, my phone doesn't like getting into recovery, so what I did was odin to KD1 and after the installation finishes, for some reason phone always boot into recovery (stock). I applied update.zip, then got to orange recovery. Wiped data/factory and cache, then checked mounts UMMU, and installed zip from sdcard (deodexed root kg6), installs completes ok but after rebooting its on a boot loop. Nothing happens.
What can I do to get this working? I'm going to odin back to kf2+root for the time being. Is there a way to install leak KG6 and apply root?
ps: this is my 2nd time attempting to install via CWM. the first time failed as well, the robot voice would say that my partition was, something, not enough space (probably has to do with not disabling voodoo, however I didn't find any option to do that). But that was another rom.
Odin to KG4, might have to root. Then do it again
Here is the history
NS4G
Rooted in early January and flashed an ICS rom (Vgomez)
Then flashed CM9 alpha 20 and made a couple of Nandroid backups over the course of the month.
Briefly flashed the Stock 4.0.4 rom. Didn't like it.
Restored via Nandroid to the CM9 alpha 20
everything was great.
Yesterday I went to make a call and the phone locked. I tried to power down...no luck. So I pulled the battery.
It never came back. (got some type of 'android lost encryption' error)
I power up the phone and it brings me to a brand new user page where I would have to login with my gmail creds.
Then it starts throwing errors like calander stopped working, google settings app stopped working, android.process.acore stopped working. etc...
I can boot to CWM and but it will not allow me to recover to anything other than what I described above.
I can mount the USB partition and it appears to allow me to copy files into that partition. However, if I try to flash a ROM, Kernel, etc. It terminates the operation and says the file is bad.
When I reboot CWM and go to view the USB partition again, those files that I had just moved into the partition are now missing.
It is as though I have not copied the file at all.
Without access to the allow USB debug setting, I cannot adb anything.
I have tried the Samsung yellow boot/restore (odin?) when I click the 'Download files' button it throws a generic error and halts the process.
At this point, I don't care if the phone is put back to stock because I won't lose anything important. I just want to get my phone working again.
edit: I do have access to fastboot. I have wiped everything and tried to boot and it sticks in the bootloader (good?) I assume that when I try to flash one of the ROMs that I do have in the USB partition...it will go back to the way it was. (errors and all)
I suspect that the Kernel is corrupt. How would I fix this without being able to write to the USB partition?
deralaand said:
Here is the history
NS4G
Rooted in early January and flashed an ICS rom (Vgomez)
Then flashed CM9 alpha 20 and made a couple of Nandroid backups over the course of the month.
Briefly flashed the Stock 4.0.4 rom. Didn't like it.
Restored via Nandroid to the CM9 alpha 20
everything was great.
Yesterday I went to make a call and the phone locked. I tried to power down...no luck. So I pulled the battery.
It never came back. (got some type of 'android lost encryption' error)
I power up the phone and it brings me to a brand new user page where I would have to login with my gmail creds.
Then it starts throwing errors like calander stopped working, google settings app stopped working, android.process.acore stopped working. etc...
I can boot to CWM and but it will not allow me to recover to anything other than what I described above.
I can mount the USB partition and it appears to allow me to copy files into that partition. However, if I try to flash a ROM, Kernel, etc. It terminates the operation and says the file is bad.
When I reboot CWM and go to view the USB partition again, those files that I had just moved into the partition are now missing.
It is as though I have not copied the file at all.
Without access to the allow USB debug setting, I cannot adb anything.
I have tried the Samsung yellow boot/restore (odin?) when I click the 'Download files' button it throws a generic error and halts the process.
At this point, I don't care if the phone is put back to stock because I won't lose anything important. I just want to get my phone working again.
edit: I do have access to fastboot. I have wiped everything and tried to boot and it sticks in the bootloader (good?) I assume that when I try to flash one of the ROMs that I do have in the USB partition...it will go back to the way it was. (errors and all)
I suspect that the Kernel is corrupt. How would I fix this without being able to write to the USB partition?
Click to expand...
Click to collapse
If you have access to fastboot and assuming your flash storage isn't damaged, you should be able to flash over /boot with a boot.img and over /system with a system.img... But you might have to search around for them. Sorry i can't be more help.
kernels ; battery ; ROM ; gov/sched
http://www.mediafire.com/?wg9krukqp43nq1i theres a link to the boot.img for the apex bigxie rom (ics 4.0.3), try flashing that through fastboot i think the command is "fastboot flash boot %imglocation%.img" so just put the img in the folder you usually flash stuff with the fastboot bat in it, then try and flash this boot and tell me what happens.
ps, the %imglocation% should be the name of the img wherever you put it, so it will probably be boot.img.
Long time listener, first time caller.
I have the latest hboot 1.45.0013, S-On, Unlocked with HTC Dev Tool.
I used the Hasoon2000 tool to install SU, CWM, and a recovery image. I then used the instructions in the thread (http://forum.xda-developers.com/showthread.php?t=1508556) to install ICS and obtain root installing pyr-o-ice sense 1.1.1 (http://forum.xda-developers.com/showthread.php?t=1469615) Everything worked, created nandroid backup and installed titanium.
Some buttons didn't work, so I looked for updates and found Virtuous ROMs. So, I used CWM to clear dalvic, flashed boot image of the Virtuous Inquisition then used CWM to install zip. Bootloop. ROM just hangs on black screen with white V for 15 to 20 minutes.
MT4GS thread stated that Primadonna and Inquisition were comparable, so I followed the same proceedure, flashed Primadonna boot image then installed ROM through CWM. This time there was tmobile splash screen, but the same system hang.
At this point I tried to restore a recovery, but CWM could not find one. Used Astro to delete all boot images from SD root, assuming this may be the problem, and flashed a Virtuous ROM again. Same problem.
Based on this thread, I thought it might be the kernal, and tried flashing the pyr-o-ice boot image that worked initially. (http://forum.xda-developers.com/archive/index.php/t-1628171.html). No dice. CWM could not install the ROM (error 1)
So, at this point, I used CWM factory reset and wipe all data. And of course that made things worse, because the SD card with recoveries was wiped. I used adb to push the recoveries from Hansoon's toolkit, but stock recovery was not available (red triangle screen hang) and cwm could not mount the SD card.
So, at this point I used CWM to format SD card (blank anyway), and at this point adb failed to recognize the decive and I could no longer fastboot into recovery or hboot through adb. (volume down + power stopped working with pyr-o-ice install)
if i remove the battery and hold power + volume while using an adb reboot hboot command i can get into hboot about every 10th attempt. adb doesn't recognize the device ("waiting on device", or adb devices yields a blank list); however the phone in hboot will transfer to usb fastboot when connected with a cable.
i looked at pushing a zip file through adb to the sd root, but that was ineffective (adb does have write access to the sd root, maybe because i am s-on?). i purchased a second sd card, and copied the recovery images from hansoons toolkit and rebooted into recovery. still went to tmobile splash, followed by V-screen bootloop.
i looked at placing a stock ruu on the sd and naming the file PG59IMG.zip, but because i'm S-on i can't flash radios, so that's out.
So, here we are. Iffy access to fastboot, 2 sd cards, a lot of determination, and a persistent bootloop.
Can someone, PLEASE help me?
Thanks!
AFAIK, you cannot flash the boot.img with CWM if you are S-ON, you *MUST* use Fastboot to flash that. So, before you messed it all up, if you had just extracted the boot.img from the ROM and flashed it using Fastboot, it likely would have worked just beautifully.
Try booting into recovery and doing a regular flash of the ROM, THEN a fastboot flash of the boot.img.
SOLVED!!
Thanks to the folks heading up the HTC Unbricking Project (http://forum.xda-developers.com/showthread.php?t=1627881) ESPECIALLY Dexter93!! who patiently unraveled this for me, and Blue6IX for the Restore to Stock instructions in the Developers Reference Guide (http://forum.xda-developers.com/showpost.php?p=17424340&postcount=24) I'm back to stock, and ready to try it all again!
Can someone send me an apk that automatically clicks the thanks button for selected developers at regular intervals?
Thanks again!
Solved???
Fuzi0719, thanks for your reply. I may have written this inappropriately, but what coded in the command prompt was "fastboot flash boot boot.img".
The ROM zip file was placed on the SD card, and I rebooted into recovery, and used CWM to install zip from SD. I'm new to this so I may have used the wrong term for installing the zip through CWM, the boot image file was always handled through the above command.
I'm back to "stock" at this point, but when I boot into the bootloader, the phone looks for PG59DIAG.zip and PG59DIAG.nbh before PG59IMG.zip.
It then asks if I want to install the update. (This is after I have already installed the "update", and the phone reset itself even with my old wallpaper.) When I got to the home screen there was a white circle in upper left corner of the status bar, with "check content" message. Each time the screen locked (default 30 seconds) unlocking it took me to the mytouch splash screen with the green circle and white background for about 10 seconds before resuming.
Each time I check to see if the phone registers requiring any updates. It doesn't. Two installs of the PG59IMG.zip. "recovery" eliminates the unlock splashscreen, and wiped any customizations. However, the phone will not manually boot into the bootloader; I have to use adb. Hboot reinstalls the PG59IMG.zip as an update every time.
If I accept it reboots within seconds like a fresh doubleshot. If I decline the "update" it reboots to the Tmobile MyTouch 4G Slide text splash screen, then moved to the green circle screen for a few minutes before I get to the homescreen.
Blue6IX was looking for help with these last month (http://forum.xda-developers.com/showthread.php?t=1580077), so maybe they are just extraction files that HTC sends with the OTA update that would prevent my phone from trying to install the "update" every time?
In any case, my question at this point is after coming from such an unstable point with my phone, is this what every relocked bootloader does? Or, is this a problem that means something else is still wrong with the system? Because taking it back to stock has not solved this.
Thanks.
Thanks for clarifying, you wouldn't believe the number of people who fail to follow that one simple step of fastboot flashing the boot.img, so that's why I stated that. So, now you have the phone relocked, and running a stock ROM (the 1.55?), but with CWM 5.0.2.7? Were you wanting to update to the 1.63 ROM? I'm unclear on what it is you want to do. For one thing, if you've already flashed the PG59IMG then I would delete it off the sd card so it doesn't keep trying to load it.
Yup.
It was just that simple.
Mainly I wanted to make sure that my phone was stable before I went back to unlock the bootloader, etc.
Went back to HTC, got a new token (just in case), and I'm creating a nandroid backup right now. Thanks.
I really appreciate it.
Hopefully the next time I get stuck, it's just as simple to fix, but far less embarrassing.
Before I get into the gist of my current problem I think it might be relevant to provide some backstory. I decided I wanted to try and root my phone so I could install a new custom ROM. I had done some jailbreaking back when the iPod touches came out, back when jailbreaking was extremely ghetto and unreliable, so I figured I could teach myself this fairly easily. I unlocked bootloader using the htcdev method without an issue, and, following a guide, downloaded something called Rootboot to flash the phone. There was only one step to this portion, so I assumed it would be easy. Running the rootboot started rooting my phone, however after a couple of lines in the command prompt it said something about the adb, failed, and the phone was stuck in a boot loop with no roms on it at all. I stayed up all night with the damn thing attempting to fix it, and at one point, actually got it to load up the stock ROM from the computer using some combination of RUU's and fastboot commands. I have no clue how I did it, all I know is that it was not through adb sideload because the recovery I had at the time wouldn't work with adb sideload for whatever reason. It was the recovery that came with the All-In-One toolkit, for the AT&T / TELUS version. At this point I figured since the phone was working I would just install the VenomROM, and after a few hours of playing around with fastboot and the bootloader trying to get a ROM loaded, I figured I was familiar enough with all of them to load the ROM.
Which is what brings me to my current issue. I KNOW the boot.img is flashed to the device because I used the All-In-One Toolkit to do it, erased the cache, did it again using fastboot commands in the command prompt, erased the cache, and continued to use recovery to install the ROM. I got it to load and install, cleared the darvik cache, data, and cache, but when booting, the phone would get to the lock screen, upon which sliding to unlock, presented me with a white screen that says "htc" on it instead of a launcher. After a couple of seconds of waiting, it says, "setup has quit responding" and gives me the option to close or to wait. Either option results in the phone rebooting wherein I only see a black screen with the notification bar at the top displaying my battery and no internet/network connection. I have gone back and flashed the boot.img again and cleared cache, darvik cache, and data several times and just have no clue what I'm doing wrong to not get this phone to boot with the ROM. I can reflash at any point from my sideload.zip file and the installation process has an option to flash the kernel (boot.img) because it is included in the zip. Any help would be much appreciated. I highly doubt theres anything wrong with the ROM or boot.img, it is probably me just not doing it right.
I am using (or attempting to use) the 1.2.7 version of VenomXL+ on the HTC One X+ along with TWRP 2.5 as the recovery.
been postponing flashing a ROM for a while, and today i decided to take the big step.
follow everything by the book:
-un-locked the phone as per HTCDev instructions.
-installed twrp 2.6.0.0 recovery
-installed super-user
after all this phone rebooted into a fully restored stock OS.
downloaded CM10.2 (didn't want to mess around with nighties just yet) and copied to phone.
downloaded and copied compatible g-apps.
extracted cm 10.2 to get the boot.img file, and ran the command fastboot flash boot boot.img
didn't get any error messages.
ran the command fastboot reboot.
since then, phone is stuck in splash screen, and won't get past it, wont go into recovery, won't go into boot.....
if i try pressing the vol-down +power button, it will turn off after a while, and the indication light won't turn on if i connect it to the pc.
for the time being, i have managed to get the identification light on again, and put it in the charger.
any help would be appreciated.
------------------------------------------------------------
HTC one s s4
Same thing happened to me. I will tell you what I followed. It was not making any sense to me before but it worked so here it is.
Go into recovery wipe all data including caches 3 times. Now flash the ROM zip again and wipe cache and dalvic cache once. Now reboot.
Really worked for me.
Sent from my HTC One S using Tapatalk
Had the same thing. Nothing worked for me. Had to pay someone to restore to stock. The boot.img is the problem. It corrupts the phone.