Develop Bugs

recovery loop problem

I now cannot get into an operating system. The device loads FFF 1.4a says "booting" goes blank for a little while then comes back to the 1.4a screen and says "booting" again and loads up TWRP. This is how I got to this point:
I recently decided to go from an older CM7 rom to a new jb one.
Because I had an older version of FFF and had a CWM recovery, I downloaded the new version of FFF (1.4a) and the newest version of TWRP (2.2.0) (flashable zip file) as well as the new jellybean rom and jb gapps. I checked all md5s prior to doing anything.
I booted into recovery and created a backup in CWM. I then cleared cache and Davlic cache and installed FFF 1.4a. I then rebooted to CM7. After loading CM7, I rebooted into recovery, cleared cache and davlic cache and installed TWRP 2.2.0. I then rebooted into CM7, rebooted into recovery. I then cleared cache, davlic cache, factory reset, and wiped system. I then installed CM10 and jb gapps and attempted to reboot to system, but have not ever been able to get there.
I have tried installing the CM7 rom I had before, no difference, CM9 rom, no difference. I tried to use a recovery file I had, still no good.
Adb does not seem to behaving properly as well. I can't seem to be able to get the device into fastboot mode for one. In TWRP I can see the device as the following:
4B8E000600000001 recovery
when I try to change the bootmode, this is how it behaves:
adb shell
~ # <-[6n idme bootmode 4002
/sbin/sh: idme: not found
KFU also seems to not be much help at changing the bootmode. I have tried older version as sited elsewhere (0.9, 0.3), but these fair no better.
Also, In my haste and desire to get this working I thought,"maybe there is some conflict with the sd card", so I wiped that only to realize while wiping that I never backed up my recovery files, "doh!".
Also, I have full battery.
I am a noob, so I could have done anything wrong. Any help would be appreciated.

When you get to the bootloader screen select boot normal in the boot menu by quickly depressing your power button a few times if it does not boot normal then flash the bootloader again in recovery http://forum.xda-developers.com/showthread.php?t=1632375 also you will have to mount your sdcard in twrp to do so make sure there are no checks in the boxes of system and data then mount transfer 1.4a bootloader a new ROM and gapps then unmount flash bootloader reboot it get back to twrp wipe factory reset wipe cache wipe dalvik wipe system flash ROM flash gapps select reboot if prompted select system see where your at after that

http://forum.xda-developers.com/showpost.php?p=29186989&postcount=157

Thanks
Thepooch said:
When you get to the bootloader screen select boot normal in the boot menu by quickly depressing your power button a few times if it does not boot normal then flash the bootloader again in recovery http://forum.xda-developers.com/showthread.php?t=1632375 also you will have to mount your sdcard in twrp to do so make sure there are no checks in the boxes of system and data then mount transfer 1.4a bootloader a new ROM and gapps then unmount flash bootloader reboot it get back to twrp wipe factory reset wipe cache wipe dalvik wipe system flash ROM flash gapps select reboot if prompted select system see where your at after that
Click to expand...
Click to collapse
Thanks, I will try this when I get a chance.

Thanks
kinfauns said:
http://forum.xda-developers.com/showpost.php?p=29186989&postcount=157
Click to expand...
Click to collapse
Thanks for this as well, did not see this information anywhere else.

fixed
Yep, it was a bad FFF flash. All good now. Thanks for the help.

Help I hosed my Verizon Nexus

I tried to install Paranoid Android and GAPPS. It get force closing on setup so I booted back into recovery to try to fix it and now there is no OS. I can boot into Recovery and Fastboot only

so you wiped system in recovery?
why dont you provide us with EVERYTHING you did to cause this?
did you do a factory reset before installing PA? that would have prevented the force closes.
if all you can do is boot into recovery, then just do a factory reset and reflash your rom...its pretty simple

I had a similar issue and it was caused by not using the correct gapps package. Correct gapps for PA 4.2 http://goo.im/devs/paranoidandroid/roms/gapps/pa_gapps-full-4.2-20130209.zip
I put it on a flashdrive and used an OTG cable to connect, then used "external SD" in TWRP.

Pirateghost said:
so you wiped system in recovery?
why dont you provide us with EVERYTHING you did to cause this?
did you do a factory reset before installing PA? that would have prevented the force closes.
if all you can do is boot into recovery, then just do a factory reset and reflash your rom...its pretty simple
Click to expand...
Click to collapse
I forgot which app I used to download the new image and GAPPS. I figured ig GAPPS was the issue i could wipe, so from Team Win Recovery Console I did a wipe of Cache, Dalvik Cache. I* *may* have also chosen to wipe System and Format data but I can't remember right now.
So I can boot into the recovery console but nothing else. If I try to boot it sits on the white Google logo until I pull the battery

ElevyNJ said:
I forgot which app I used to download the new image and GAPPS. I figured ig GAPPS was the issue i could wipe, so from Team Win Recovery Console I did a wipe of Cache, Dalvik Cache. I* *may* have also chosen to wipe System and Format data but I can't remember right now.
So I can boot into the recovery console but nothing else. If I try to boot it sits on the white Google logo until I pull the battery
Click to expand...
Click to collapse
you definitely wiped /system.
go back to stock from the return to stock thread in general. it's stickied.

ElevyNJ said:
I forgot which app I used to download the new image and GAPPS. I figured ig GAPPS was the issue i could wipe, so from Team Win Recovery Console I did a wipe of Cache, Dalvik Cache. I* *may* have also chosen to wipe System and Format data but I can't remember right now.
So I can boot into the recovery console but nothing else. If I try to boot it sits on the white Google logo until I pull the battery
Click to expand...
Click to collapse
if you selected wipe DATA, then your SDCARD is gone...you need to adb push your rom zip back to the sdcard and flash it. if you wiped system, then you have no OS installed any more...

Zepius said:
you definitely wiped /system.
go back to stock from the return to stock thread in general. it's stickied.
Click to expand...
Click to collapse
I assume it's also the link in your sig and must be done from a PC. I won't have access to a PC until tonight but I do have access to a MAC this afternoon
Pirateghost said:
if you selected wipe DATA, then your SDCARD is gone...you need to adb push your rom zip back to the sdcard and flash it. if you wiped system, then you have no OS installed any more...
Click to expand...
Click to collapse
Thanks.

ElevyNJ said:
I assume it's also the link in your sig and must be done from a PC. I won't have access to a PC until tonight but I do have access to a MAC this afternoon
Click to expand...
Click to collapse
yes, but for a mac just change fastboot to ./fastboot in the terminal window. instructions are still the same.

Zepius said:
yes, but for a mac just change fastboot to ./fastboot in the terminal window. instructions are still the same.
Click to expand...
Click to collapse
I'm at the screen with the android laying on it's back and the panel open. When I do ./adb devices it says list of devices attached but doesn't show anything.
I'm following the guide from http://forum.xda-developers.com/showthread.php?t=1917237

ElevyNJ said:
I'm at the screen with the android laying on it's back and the panel open. When I do ./adb devices it says list of devices attached but doesn't show anything.
I'm following the guide from http://forum.xda-developers.com/showthread.php?t=1917237
Click to expand...
Click to collapse
Because your phone is in fast boot.

063_XOBX said:
Because your phone is in fast boot.
Click to expand...
Click to collapse
Sorry I'm being dense today

Ok phone is up and running again or shall I say limping. The 3G/4G indicator just shows bars.

[Q] Hardware navigation buttons do not work on some ROMS after clean install

Hi,
I'm finding with some ROMs (SlimBean, ProBAM, CM Domination) after an install on my HOX that the hardware navigation keys don't work anymore. I have to enable the soft keys in order to be able to use the phone - obviously not desirable as it wastes screen space.
I've done a crapload of googling, searching the forums, etc and can only find info on disabling the buttons. Is there some obscure setting I am missing somewhere?
The process I use is the same as is recommended on most of the other posts:
- fastboot erase cache
- fastboot flash boot boot.img (of the rom I am installing)
- in CWM, delete userdata, format cache/dalvik
- install rom
- reboot
When the phone boots up - straight away the capacitive buttons no longer work.
Reflash with a different ROM (CM10, Blade) and they are fine.
Can anyone help?
Thanks

I've had that happen on probam/slimbean if I don't flash Gapps.
Sent from my HTC One X using Tapatalk 4 Beta

sinkster said:
I've had that happen on probam/slimbean if I don't flash Gapps.
Sent from my HTC One X using Tapatalk 4 Beta
Click to expand...
Click to collapse
Aha - thanks for the suggestion, I'll give it a go. From memory I probably hadn't installed Gapps at that stage since I was just checking the ROM out..
thanks man

Gapps would have no bearing on such a problem, coincidence. And to prove a point, gapps are included in the ProBAM rom and the fault still occurred. I would suggest you change slightly the method of wiping between roms.
From CWM recovery, format data,system and cache. Then mount usb storage and format the sdcard to fat32 from your pc or laptop, but change the allocation unit size from 16 to 32 in the dropdown. Then while usb is mounted copy over the rom, and gapps if required. Just to be sure wipe dalvik cache in recovery then reboot the bootloader and flash boot image in fastboot and fastboot erase cache.
Very important to erase cache in fastboot.
Once that is done, back to recovery and flash rom and gapps if required and your done. This is the method I use every day and never have a problem.
Just re-read OP and I noticed that you fastboot erase cache before flashing boot image, you must also erase cache after flashing boot.
sent from my shorts

nogotaclue said:
Gapps would have no bearing on such a problem, coincidence. And to prove a point, gapps are included in the ProBAM rom and the fault still occurred. I would suggest you change slightly the method of wiping between roms.
From CWM recovery, format data,system and cache. Then mount usb storage and format the sdcard to fat32 from your pc or laptop, but change the allocation unit size from 16 to 32 in the dropdown. Then while usb is mounted copy over the rom, and gapps if required. Just to be sure wipe dalvik cache in recovery then reboot the bootloader and flash boot image in fastboot and fastboot erase cache.
Very important to erase cache in fastboot.
Once that is done, back to recovery and flash rom and gapps if required and your done. This is the method I use every day and never have a problem.
Just re-read OP and I noticed that you fastboot erase cache before flashing boot image, you must also erase cache after flashing boot.
sent from my shorts
Click to expand...
Click to collapse
notgotaclue, thanks for the detailed response - I will most definitely give this a go when I get some time over the next few days. Cheers mate

@nOtgotaclue: I went through your process and it did work for me with CM10 Domination - but not ProBam or Slimbean, they still had the same problem with hardware keys not working.
I've ended up flashing another kernel (TripNDroid v15 AOSP) and it has fixed the issue (for SB at least, yet to try it on ProBam).
Thx again for your help

[Q] Its either no touch or no carrier network on my HTC One X

Hello,
After last one 4.2.2 update my phone was stuck at the HTC One Beats audio logo.
Then I tried restoring nandroid backup(with CID HTC__038)(http://forum.xda-developers.com/showthread.php?t=1975140) and then flashing boot.img. But this left me with no touch support.
So I tried a rom from here(http://forum.xda-developers.com/showthread.php?t=2107669) but then my phone stuck at HTC Quietly brilliant logo even after flashing boot.img.
Now when I tried to restore the nandroid back from the first link, the phone worked and the touch was working again. But this time, the phone doesn't show any carrier networks. flashing with the boot.mg from this nandroid stopped the phone's touch from working, but then the carrier network came back.
So what do I do next?
My HBOOT version is 1.73.0000

The second should work, did you perform a real full wipe before installing the rom.zip ?
sent from my .......

Yes I cleared any caches and formatted by partitions using the recovery.
Also I did clear the cache using fastboot command, but still no luck. I heard something like AROMA installer's boot.img won't work or something like that. Could that be the problem?
And thanks for replying.

What recovery are you using so i can describe all steps in detail
sent from my .......

TWRP recovery.
BTW I think you should know this. My phone was stuck at boot screen(the htc one beats audio logo) after I did the latest update. I was doing this for recovering from that.

Try this :
Flash this recovery
https://db.tt/MNtVjpOJ
Rename the file to recovery.img and flash it
Fastboot flash recovery recovery.img
Then flash the boot.img from the sd rom.zip
Fastboot flash boot boot.img
Fastboot erase cache
Then enter the recovery and do :
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & storage - format cache, data, system
Then install the sd rom.zip and reboot
sent from my .......

I think you had suggested this same steps to someone else in here right?
I am not sure, but if you had I have already tried it.
Anyway I will try to do it again. Thanks so much for this!

Yep but its a method that should work flawlessly ! If not report back and see for other solutions
sent from my .......

Bricked?

Im in desperate need of help.
My one X randomly locked up and on a hard reboot (held power button) it now no longer boots to CM, instead it boot loops.
On booting to recovery (CWM) I was presented with a black screen. So using fastboot I was able to flash TWRP 2.4.0.0 and successfully boot to it.
It opens with a password prompt to which I can click cancel and get to the options. This is where it complains things get complicated :/
If I try to wipe anything:
E: error unable to mount '/cache'
It will do the same with /data and /system.
adb sideload so far has failed me,
failed to write data 'protocol fault (no status)'
It seems once one attempt fails the phone seems to go into some locked status until the battery is fully drained and recharged. Which makes everything so long and tedious to troubleshoot.
adb push cm.zip /sdcard returns an error. But this is all in vain as I have cm10.1 on the /sdcard but twrp fails to flash it.
Any help would be greatly appreciated! Ive been without internets at work for days now :crying:

bump.

Update your twrp to latest 2.7 or whatever its near the top in development thread. Then fastboot erase cache, flash boot image for desired ROM fastboot erase cache, boot to recovery flash ROM then gapps, wipe davlic and cache, enjoy..
Sent from my alarm clock.

myheroduane said:
Update your twrp to latest 2.7 or whatever its near the top in development thread. Then fastboot erase cache, flash boot image for desired ROM fastboot erase cache, boot to recovery flash ROM then gapps, wipe davlic and cache, enjoy..
Sent from my alarm clock.
Click to expand...
Click to collapse
Brilliant mate. There was an option in 2.7 to repair the partitions. I had to set /data back to ext4 (even though it said it already was) then repair the partition, and voila. Its all working again