Database Users

[Q] Can't flash recovery zip

Hi,
I'm at my wits end. I had SlimRom installed for a week and all was fine, but I was curious about what new ROMs were out there so I backed up my phone using ROM Manager and did all the usual stuff to get a new ROM. I installed Gummy, but didn't like it; I installed one other ROM that I can't remember its name, but also didn't like that. I realized my comfy home of SlimRom was where I wanted to be, so I tried to flash the backup.zip that I had created but it kept saying installation aborted (Status 0).
After hours of countless attempts and just weird behaviour (sometimes boot loops, sometimes not booting into recovery, etc.) I finally got my phone back to stock.
I downloaded the latest SlimRom file 3 times to make sure it wasn't a corrupt zip (twice from my PC and once from my phone directly). Both the zip directly from Slim as well as the backup.zip that I made with ROM Manager give me the same installation aborted. The other error it gives is "E: Error in /data/media/0/slim....zip". I'm wondering if somehow my partition is screwed up. I tried using Odin's repartition, which just erased my recovery partition, but I got that back thankfully! When I wipe data/factory reset it says wipe complete (and the ROM does reset to factory) but it also says "E:unknown volume '/sdcard/.android_secure' "...I'm wondering if that relates to why the backup.zip file won't read properly. Maybe the partition got screwed up somehow?
I can flash a SU zip so it's not a flashing problem, per se. And thankfully Odin always works!
I think I may need the stock PIT file for the Telus S4 l337m, which I found but my phone says "secure check fail: pit"
I'm not sure where to go from here...

Rom manager is your problem. That software I'd waaaaay out of date and rarely ever works on newer phones.
Get you goo manager. Allow SU. Then hit the menu button and then hit install openrecoveryscript. You will get TWRP recovery. Then you follow the OP of your ROM of choice to install.
Sent from my GT-I9505G using XDA Premium 4 mobile app

Thanks for the suggestion. I used Goo but it was no help. I can flash other ROMs fine. It seems to be just SlimBean that I can't flash :s. I've used TWRP recovery as well as CW and neither work.
Any other ideas?

This is a pickle I am completely unsure about, then... I am sorry I can't be of more assistance. It does seem like the partition is borked.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

[Q] Need some help here Stuck on bootloop, Can only use TWRP

Hello everyone!
I'm having a bit of an issue. apparently everything was deleted on my phone for some reason when i was using my phone. I decided that I should just Factory restore through TWRP and reinstall kitkat 4.4.1. when I went to go factory restore I see that on the commands it says "Unable to mount, failed to wipe dalvik, wipe complete Failed" I took off the -rf on the settings check mark and when I go to Factory reset, the phone stays on "Formatting Cache using make_ext4fs function" the progress bar is moving but after several minutes it's the same screen no changes no failed messages or anything. almost like it's still trying to format. - my phone starts to get kinda warm. I have tried sideloading a ROM but my computer doesn't seem to pickup my phone. Instead when I hit to sideload through adb in the device manager i see "Other devices g2" with a question mark.
I do have the LG usb drivers and also I believe I have adb installed.
What else can i do? My phone still tries to boot but all I get is the boot animation over and over again.I tried the "LG G2 Stock Firmware" thread but the program says wrong phone model.
I had installed Kitkat 4.4 with Wootever's version 6 kernel and my phone model is d800.
Thanks for all your help! Seems like flashing was a lot easier on my previous HTC One X+ lol

If ur adb can see ur phone in sideload mode then sideload kitkat Roms and gapps and the kernel.
Sent from my LG-D800 using xda app-developers app

Install koush drivers as stock lg driver does not help pc see ur phone in recovery mode
Sent from my LG-D800 using xda app-developers app

accidentally wiped everything after getting stuck in boot loop

As per the title, I accepted the system update on my rooted ls980 (didnt know it would mess anything up). Ended up putting me into a boot loop to TWRP recovery. Tried to restore all my backups and none of them yielded a different result. Thought i would try a quick wipe but i accidentally wiped everything... For some reason when i try to install the newest USB drivers it tells me the install worked but never recognized the phone. I have done all the steps in this thread http://forum.xda-developers.com/showthread.php?t=2432476 but not everything installs when plugged in from download mode. Also could not get LGflashtool to register properly. I'm not exactly sure where to go from here, I have no roms, backups, or adb access. what do?

Well if u can boot ur rom into recovery, then connect s pen drive with s flashable rom inside to ur mobile via OTG cable, and then flash
Sent from my LG-D802 using XDA Premium 4 mobile app

i had the same prob. only way out foe me was to flash via sideload

I think it's a bootloop

I wanted to do factory reset on my rooted nexus 4 , using CWM. It didn;t work (all files stayed) so I went to advanced and formated everything that was there. Now my phone doesn't start (the screen with "google" is on.
I can go to recovery or fastboot but in fastboot adb or anything can't see my device.
Is there anything I can do?

Yes, you wiped your os. Either adb push a rom zip onto your sdcard and flash in recovery or adb sideload a rom zip in recovery
Sent from my Nexus 5 using XDA Free mobile app

Should I sideload zip or tgz?
I tried zip, it says: installation aborted.
I tried tgz, it says e: can't open /tmp/update.zip (bad)
I also tried pushing, but installation aborted as well

If you're trying to get back to stock then flash individual partitions using fastboot.
This guide should help you out .
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
If you want to flash a custom ROM follow the steps in the previous post.

Doesn't work, like I said, adb can't see my nexus in bootloader.
Before I started doing anything I'd made a backup. Maybe I can restore it now somehow?
EDIT: @up, it worked, tkanks a lot

szajbuz said:
Doesn't work, like I said, adb can't see my nexus in bootloader.
Before I started doing anything I'd made a backup. Maybe I can restore it now somehow?
added: wait, smoething is happening
Click to expand...
Click to collapse
If your in the boot loader you need to use fastboot devices, not adb devices
Sent from my Nexus 5 using XDA Free mobile app

@up
yeah but I realized that after my previous post

If you are on bootloader you van use nexus foot toolkit for flash stock with bricked option

[Q] Stuck in recovery mode upgrading CM 10 to CM 11

I was running CyanogenMod 10.1.x versions, using ROM Manager to upgrade as new ones were available. However, when I tried to upgrade to 10.2.1 it kept rebooting every several minutes, showing the new bootup screen with the rotating arrow. I tried upgrading to version 11...M9 also with ROM Manager and now it only comes up in recovery mode (CWM v6.0.3.1). There seems to be no way to finalize the installation. I can't sideload from the PC, since, although DeviceManager shows "Google Galaxy Nexus ADB Interface," I do not see any entries in Device Management or in the Explorer, so I can't offload a full backup, nor can I use adb to sideload the new CM. I can't instal from the internal sdcard, since it starts with "...Installing /sdcard/update.zip" and then can't find it - it comes up with the "(no such file or directory)."
Since (except for Device Manager) nothing on the PC recognizes a connection with the Nexus 10, I'm pretty much out of options. I can do a complete "wipe data/factory reset" I suppose, but would like something not so drastic (given no backup). When I look at CWM's display of mounted and unmounted storage, sdcard is unmounted and won't mount. I've even done a full wipe and factory reset, with the same results.
A brand-new install of the Samsung USB Drivers 1.5.33.0 through Skip's app now results in an error message when I reattach the tablet saying the driver install failed. I still show the device in Device Manager.
I have Skip's Universal Android Toolkit v1.0.2 and it seems to recognize that a Nexus 10 is connected, but can't do anything to it (it expects you are originally booted to Android, not recovery.
This is my first Samsung device, so I'm totally unfamiliar using Odin and haven't figured out how to use it to correct the problem.
It seems that, if I can sideload a copy of CM 11, I should be okay, but all roads look closed.
Any ideas?
I'm locked in a loop.
'

Third post in this thread
http://forum.xda-developers.com/showthread.php?t=2670400
Will give you instruction to fully restore, but will be worst case scenario, you will also find links to drivers that are confirmed working, may need to manually update them
So yes you are right you should want to use adb sideload to get the proper ROM on
And in the future try to not use ROM manager as issues like this happen all to often, rather just boot to recovery, wipe, flash
Your other option is an sdcard and otg cable to flash a ROM
Let me know if you get stuck, best of luck!

Thanks - will keep trying.
demkantor said:
Third post in this thread
http://forum.xda-developers.com/showthread.php?t=2670400
Will give you instruction to fully restore, but will be worst case scenario, you will also find links to drivers that are confirmed working, may need to manually update them
So yes you are right you should want to use adb sideload to get the proper ROM on
And in the future try to not use ROM manager as issues like this happen all to often, rather just boot to recovery, wipe, flash
Your other option is an sdcard and otg cable to flash a ROM
Let me know if you get stuck, best of luck!
Click to expand...
Click to collapse
I downloaded the latest Android SDK with platform tools and put the cm zip file in the directory with adb.exe. On the tablet, in ClockworkmMod Recovery, I selected "install zip from sideload." The tablet went into sideload mode and instructed me to type "adb sideload <filename>. So I typed: "adb sideload cm-11-20140805-SNAPSHOT-M9-manta.zip" and hit the enter key. The PC reported 100% downloaded. The tablet listed:
Restarting adbd...
Finding update package...
Opening update package...
Installing update...
set_metadata_recursive: some changes failed
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
I'm at least communicating between the PC and tablet, but the update is still failing. Any hope of trying to flash standard ROM, re-root, and start again?

You need to update your recovery, grab the latest TWRP or CWM .img for manta and flash in via fastboot first, then boot to new recovery then flash ROM

Thanks, I grovel at your feet!
Thanks for the help. I ended up downloading the newest Android SDK, installing the platform-tools, and flashing the 4.4.2 factory rom. Normally, this loses all of your data (though, through carelessness I hadn't disabled autosave to the Google Cloud, so all was restored). Now I have an unrooted tab with KitKat on it, but it won't take me long to root it again and this time, I'll flash custom ROMs manually, the way I do on my other devices. Once burned...
So thanks again for the help. It did the trick.

Beartooth01 said:
Thanks for the help. I ended up downloading the newest Android SDK, installing the platform-tools, and flashing the 4.4.2 factory rom. Normally, this loses all of your data (though, through carelessness I hadn't disabled autosave to the Google Cloud, so all was restored). Now I have an unrooted tab with KitKat on it, but it won't take me long to root it again and this time, I'll flash custom ROMs manually, the way I do on my other devices. Once burned...
So thanks again for the help. It did the trick.
Click to expand...
Click to collapse
Great to see @demkantor help get you back up and running ..
@Beartooth01 Can you plz add "SOLVED" to the thread title
Thx Josh