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.

[Q] Rooted Kindle doesn't take roms through TWRP

Hi, I am running TWRP v2.2.2.1 and my kindle fire is rooted. When I go to flash a rom it seems like it is finished, but never gives me the success popup. It also says its verifying the partition sizes and filesystems. The home and restart buttons appear and so once I flash it I restart and the bootloader for each rom I have installed consistently just keeps loading indefinitely and never goes into the OS. Any idea's? In the mean time I have a backup and am running the stock os.

Restarting the bootloader selection puts your device in fastboot. Try selecting system after your flash that`s what you should be doing.

Thepooch said:
Restarting the bootloader selection puts your device in fastboot. Try selecting system after your flash that`s what you should be doing.
Click to expand...
Click to collapse
after i flash "wipe cache, home, and reboot system" appear. Do you mean reboot system or am I wrong. The success popup never showed up again.

Jlobel said:
after i flash "wipe cache, home, and reboot system" appear. Do you mean reboot system or am I wrong. The success popup never showed up again.
Click to expand...
Click to collapse
Depends on what your flashing as far as the wipes go but yes when you select reboot then you select system if prompted. If you are flashing a completely different system. Wipe factory reset , wipe cache, wipe dalvik, wipe system, flash Rom and flash gapps then select reboot and select system if prompted.
Edit: The final thing that TWRP does during a flash is verifying file systems and verifying partitions sizes. When you see the buttons show for wipe davik/cache and reboot this indicates the flash is complete even if it doesn't throw a successful statement

Device bricked? No adb-access

Hello!
My Oppo Find 7 (international) seems to be bricked.
I'm on stock ROM COS 1.2.5 with stock recovery 1.0
After booting it stuck in the Setup-Wizzard with "settings has stopped"-Loop.
Unfortunately in stock-ROMs the USB-debugging is disabled, so i can't acces via adb fastboot to flash other recoverys.
And cause of the loop i can not enable USB-debugging...
The recovery (stock 1.0) let me only flash 1.2.5, no other ROMs work.
Things that work:
- entering fastboot (but no access via adb as i wrote)
- entering recovery and execute "zip from sd" (while sd means only internal sd here)
- normal boot to the f****** Setup-Assistant, enter PIN. At slect Language the "setting has stopped"-loop starts
- while the device is in loop, i can access the internal and external SD-card via PC, copy and delete files works
Please, has anybody an idea what to do ?
Thanks to all
Marco

Since you can get into fastboot, download a custom recovery, go to fastboot, type
fastboot flash recovery x
Replacing x with the full name and extension of the file, and install a ROM. Alternatively, if you want ColorOS, try downloading 1.2.4i, and installing it through the stock recovery. Then you can update from there

Hmmmm....
Positive! At this moment i learned that USB-debugging is needed for adb-access on a booted device, not for fastboot-access
Yes, i could flash TWRP via fastboot (puuhh, not bricked)
THANKS !!
Now i can mess around the "settings has closed"-Loop, wich is still in place.
(No wiping fixes the problem, even 1.2.1 nor 1.2.3 or whatever)
But i'm on the road again and can check out fixes.
Thanks again!!

That's weird. Did you ever install custom ROMs before having this issue?
Did you try formatting System in TWRP? But be careful, when you format System you have to install stock Color OS BEFORE rebooting your device. That means stay in TWRP after you format and install the ROM, then reboot.

unable to mount storage and /data

Hello,
tried to upgrade my 1.4 watch to 1.5 via update.zip. While pushing the update.zip he stopped copying.
From this time the watch always stuck at Google bootanimation.
So I tried to push the update.zip again, success, but not boot up.
Then I unlocked the bootloader, pushed twrp, pushed a whole system.img, success, but not boot up.
In TWRP is saw that he cant mount storage (0 MB) and /data.
So what can I do? Remeber a rapair option of filesystem in TWRP of my Samsung. But cannot find.
So is there a way to rebuild storage and /data using fastboot or ADB?
I have no TWRP Backup. But if somebody can give me... may restoring would go or fail because he cannot mount?
Whole sh*t because cant wait for OTA
Ok. No help. So I had to help myself :-/
Luckily found images of all partitions for persons who installed the preview of Wear 2.0 and want go back to 1.5
Flashed all of them using fastboot and voilà I'm back in business

ArnomaF said:
Hello,
tried to upgrade my 1.4 watch to 1.5 via update.zip. While pushing the update.zip he stopped copying.
From this time the watch always stuck at Google bootanimation.
So I tried to push the update.zip again, success, but not boot up.
Then I unlocked the bootloader, pushed twrp, pushed a whole system.img, success, but not boot up.
In TWRP is saw that he cant mount storage (0 MB) and /data.
So what can I do? Remeber a rapair option of filesystem in TWRP of my Samsung. But cannot find.
So is there a way to rebuild storage and /data using fastboot or ADB?
I have no TWRP Backup. But if somebody can give me... may restoring would go or fail because he cannot mount?
Whole sh*t because cant wait for OTA
Ok. No help. So I had to help myself :-/
Luckily found images of all partitions for persons who installed the preview of Wear 2.0 and want go back to 1.5
Flashed all of them using fastboot and voilà I'm back in business
Click to expand...
Click to collapse
Hi, could you be so kind to share those partitions to me please?? My watch just turned into a brick...: ( Many thanks!

Stuck in twrp recovery
Here's my case
I have a huawei watch
i unlocked the bootloader successfully
I then flashed twrp recovery
then tried to flash a custom rom but failed.
I am stuck at twrp recovery and fastboot mode.
I cant boot into system
I tried to sideload adb from twrp but it said unable to mount storage and unable to mount data.
When i flash the stock recovery, it keeps rebooting itself.
PLease tell me if there is any hope for me.

Have you tried to format the partitions? or to repair it via "Wipe" > "File System Options" > "Data" > "->" > "Repair"? Or chance the filesystem? mine is f2fs (this only works for data and not for storage...

[FIXED] Unbrick ZE551ML without computer

Hello!
I made an OTA update while rooted so I soft bricked my phone lol
I dont have access to a computer for some weeks so I'd like to know how I could flash a stock ROM using an Android tablet (Samsung Galaxy Tab Pro 10.1")
I installed ADB and Fastboot by following this thread http://forum.xda-developers.com/showthread.php?t=2586472&page=1 but I apparently need 1.0.32 version of ADB and I can't find any guide to install it on an Android Device, plus when I use a Fastboot command the terminal emulator sticks on 'Waiting for device'
My Device does appear when I use 'adb devices' but it doesn't when I use 'fastboot devices'
I really need help guys
Thank you very much for reading this

Ok, you can follow this, but i'm not sure if it works:
1. Download the OTA package from Asus.
2. Rename it to mofd_sdupdate.zip.
3. Push that file to the root of your phone internal storage (/sdcard/mofd_sdupdate.zip) not anywhere else.
4. Reboot to recovery, it will flash the update automatically
5. Reboot your phone normally.
6. If it bootloops, try hold the power button to turn it off, then turn it on again.
7. If it still bootloop, wipe /cache in recovery, then reboot
8. If it still bootloop, wipe /data in recovery, then reboot
9. If still bootloop, do step 6
10. If it still loops, I have no idea . Try using a computer.
ELSE, enjoy the new update.
If in 5 min it doesn't show "Android is upgrading" it means that it fell into a bootloop

HungNgocPhat said:
Ok, you can follow this, but i'm not sure if it works:
1. Download the OTA package from Asus.
2. Rename it to mofd_sdupdate.zip.
3. Push that file to the root of your phone internal storage (/sdcard/mofd_sdupdate.zip) not anywhere else.
4. Reboot to recovery, it will flash the update automatically
5. Reboot your phone normally.
6. If it bootloops, try hold the power button to turn it off, then turn it on again.
7. If it still bootloop, wipe /cache in recovery, then reboot
8. If it still bootloop, wipe /data in recovery, then reboot
9. If still bootloop, do step 6
10. If it still loops, I have no idea . Try using a computer.
ELSE, enjoy the new update.
If in 5 min it doesn't show "Android is upgrading" it means that it fell into a bootloop
Click to expand...
Click to collapse
Thank you very much

HungNgocPhat said:
Ok, you can follow this, but i'm not sure if it works:
1. Download the OTA package from Asus.
2. Rename it to mofd_sdupdate.zip.
3. Push that file to the root of your phone internal storage (/sdcard/mofd_sdupdate.zip) not anywhere else.
4. Reboot to recovery, it will flash the update automatically
5. Reboot your phone normally.
6. If it bootloops, try hold the power button to turn it off, then turn it on again.
7. If it still bootloop, wipe /cache in recovery, then reboot
8. If it still bootloop, wipe /data in recovery, then reboot
9. If still bootloop, do step 6
10. If it still loops, I have no idea . Try using a computer.
ELSE, enjoy the new update.
If in 5 min it doesn't show "Android is upgrading" it means that it fell into a bootloop
Click to expand...
Click to collapse
How can I push the file? :/

I fixed the problem!
This is how I did it:
I downloaded last WW OTA Update from Asus site for my phone
I renamed it mofd_sdupdate
I've put it on a SD CARD
I inserted SD CARD in the phone and the update started alone, after it my phone was saved