I guess my real question is what's the best way about flashing this rom
1) Reboot into recovery
2) Wipe data
3) Install ROM
4) Install GAAPS
5) Clear cachse/dalvik/etc.
6) reboot
?
Well bricked my phone (sort of)
I got the (Status 7)
installation aborted error
I used the att CM file which is compatible with the Bell version in Canada.
Can someone please help ?
ask in q&a, where this post belongs. cheers
So my phone is messsssssssssed. I got the status 7 error -- and it aborted. So I went to try to sideload the rom (after editing the file -- there was a fix for this) and it says sideload started -- it's waiting for me to send the file
BUT I CAN'T GET ADB TO RECOGNIZE MY PHONE.
am i screwed ? I installed the drivers and stuff and still it won't recognize my phone ... do i have to reboot the computer ?
So my phone is messsssssssssed. I got the status 7 error -- and it aborted. So I went to try to sideload the rom (after editing the file -- there was a fix for this) and it says sideload started -- it's waiting for me to send the file
BUT I CAN'T GET ADB TO RECOGNIZE MY PHONE.
am i screwed ? I installed the drivers and stuff and still it won't recognize my phone ... do i have to reboot the computer ?
update your recovery.
Where did you get the rom and what did you edit in it?
also I would suggest wiping system when you flash new roms, not just data/caches
Related
So I have a compilation of three issues that I've found on the forums but after two days, of researching and troubleshooting, no luck so hoping someone out there has had a chance to fix this and can share their knowledge.
Here's what I've done so far:
Ran Super One Click to root and worked
Flashed bootloader 30.04
Booted to "critical error 1337 510b"
RSD flashed to VRZ_MB810_2.3.32_1FF_01.sbf (Happy_Holidays_From_TBH.zip) using RSD Lite 4.8
RSD flashed to SHADO_X6_2.3.34_SYSTEM-ONLY.sbf (SHADO_X6_2.3.34_SYSTEM-ONLY.zip)
Lost root so tried Super One Click - wouldn't work
Installed Koush Bootstrap recovery
Installed and successfully rooted with z4root
Tried installing to C_01.43.01P.zip from Peter Alfonso and fails with error in list below
So here are the three errors I'm getting now and haven't been able to find a fix to any of them. I'm thinking it's possible permission issues on my device. I ran the Fix Permissions options from ROM Manager but it didn't help.
When I reboot into recovery mode, get error: "e: can't open /cache/recovery/command"
When try to install baseband update and says"Writing RDL/BP image... E:Error in /sdcard/update.zip (Status 0) Installation Aborted"
Tried flashing a few other SBF's and about 10 seconds into each, DX shows error "critical error 1337 510b" and flash never moves ahead
Here are some of the items I've tried and none of them have helped:
Rename to update.zip
Install using built in recovery
Installed ROM Manager
Installed ClockWork
Battery pull
Wipe cache (several times)
Install package with DroidExplorer
This list could go on and on an on - I've been working on this for two days
EDIT: Realized I hadn't upgraded the kernel from TBH so I just installed it and it worked properly, but still doesn't fix above issue when trying to update my baseband.
The good news is that I took a backup using ClockWork and I've restored it a half dozen times over past few days (so that I could actually leave the house and use my phone) so my phone is working, I just can't do any more flashing
Any suggestions? Thanks in advance!
EDIT: Been a few days and no replies. Very uncommon for this forum. Did I post in the wrong area? or not follow forum rules? Or I'm just an idiot? I've tried formatting all partitions (except for sdcard) and get "Error formatting boot partition". All other partitions format correctly but still can't install the latest baseband. The only thing that still works is flashing sbf of VRZ_MB810_2.3.32_1FF_01.sbf and SHADO_X6_2.3.34_SYSTEM-ONLY.sbf to get back to stock and restore my latest backup. Please help, I would really like to get the latest baseband installed.
I've been told that C_01.43.01P is only for original Droid, not the X - which is why it wouldn't work.
Go to the Droid X Android Development subforum and look at my thread for the update zip. Its a zip you download and flash through clockwork to upgrade and /or fix issues with the latest OTA. That should fix you right.
hi
motoroladefy plus MB526 from australian
i copy many of files to SD (downloaded till i finsh my monthly limit) change the name to update.zin files
same msg
now my phone cant start system freezing @ motorola logo
when i chioce power and down button then down + up open a windows wrote this :
Android system recovery <3e>
1. reboot system now
2. apply update from sdcard
3.wipe data/factory rest
4.wipe cache partion
copy may ROMs to SD and i choiced 2.apply update from sd
show me after check this msg:
E: signature veification failed
install aborted
I installed RSD v5.6 but all i downloaded (i try many of files) show me this msg:
status wrote: Error validating image file ..when i press start change msg to:
Failed flashing process.Failed flashing process. (0x7100);phone connected
how can i solve this please
can i get australian service center for motoroladefy plus email ?
thank you
Questions go in the Q&A section
What were you trying to flash and why from stock recovery? Have you rooted your defy and installed 2ndinit? You can't install any custom roms from Stock Recovery. CWM recovery is meant for such purposes.
need help
MarcinRN said:
What were you trying to flash and why from stock recovery? Have you rooted your defy and installed 2ndinit? You can't install any custom roms from Stock Recovery. CWM recovery is meant for such purposes.
Click to expand...
Click to collapse
in first thank you
yes installed 2ndinit and super1c,rom manger = cwm and <3e rerovery>..(byaway still <3e> see it when i prss down volum:
Android system recovery <3e> isnt mean its not stack recovery?
in first the recovery boot work with all option ( backup,recovery,back,...) i think it mean root succeed _saw blue LED
but cant install ROM ...E:signature verification failed Installation aborted)-nothing accept to install same error ..thats mean NO i cant install any ROM
restarted and wiped data,cache, again and again + (system formt) after restart cant see all option @ recovery mode only that 4 option:
Android system recovery <3e>
1. reboot system now
2. apply update from sdcard
3.wipe data/factory rest
4.wipe cache partion
this time i have use both -,+ volum to enter recoverymode!
i dont remember i choice unroot under recoverymode!
about LED now only white when i off the phone and connect cable but not charging only white LED
I installed RSD v5.6 but all i downloaded (i try many of files) show me this msg:
status wrote:
Error validating image file
when i press start change msg to:
Failed flashing process.Failed flashing process. (0x7100);phone connected​
dlshad said:
I installed RSD v5.6 but all i downloaded (i try many of files) show me this msg:
status wrote:
Error validating image file
when i press start change msg to:
Failed flashing process.Failed flashing process. (0x7100);phone connected​
Click to expand...
Click to collapse
In order to flash SBF phone must be in bootloader mode. Follow this guide:
http://forum.xda-developers.com/showthread.php?t=1618718
Make sure you're flashing a proper sbf file...
MarcinRN said:
In order to flash SBF phone must be in bootloader mode. Follow this guide:
http://forum.xda-developers.com/showthread.php?t=1618718
Make sure you're flashing a proper sbf file...
Click to expand...
Click to collapse
thank you
im sure im in bootloader the white fonts black backgraound
usb conected andthe RSD see the phone
the secount of your note
i install may of files from here:
http://sbf.droid-developers.org/umts_jordanplus/list.php
all of that same error
sure i remove last 2 word (.gz)
in past i upgrate to 2.3.6 seccesed from official site
when i bought it they said its unlocked maybe not factory unlocked is that help!
in recovery mode there is <32> isnt mean its rooted not stock recovery
can i add backup option to recovery mode coz i have backup file
any help
thank you
dlshad said:
sure i remove last 2 word (.gz)
Click to expand...
Click to collapse
You can't just remove the extension. You need to unpack the sbf file with WinRar or 7-zip then flash it. .gz means that file is compressed and you need to unpack it!
Downloaded sbf file but unable to unpack
MarcinRN said:
You can't just remove the extension. You need to unpack the sbf file with WinRar or 7-zip then flash it. .gz means that file is compressed and you need to unpack it!
Click to expand...
Click to collapse
I downloaded 2 different versions of sbf files but cant unpack then as when I try to do that it gives an error any solution for that ?
rahulpillai said:
I downloaded 2 different versions of sbf files but cant unpack then as when I try to do that it gives an error any solution for that ?
Click to expand...
Click to collapse
what error does it actually give? which program are you unpacking archive with?
E:signature verification failed. Installation aborted; after rooting spice mi 500
Just yesterday I rooted my spice mi 500. Was fine untill i paid and downloaded a bunch of pro apps like ROM Manager Pro, and ran some scripts, thinking it might be routine clean up. but after running some script...I am only getting the followin message. I can see my spice phone in device manager on my PC, and drivers are up to date. I am unable to use the USB properly as the PC is not recognizing my device...Pls help asap. thanks.
Android system recovery <3e>
1. reboot system now
2. apply update from sdcard
3.wipe data/factory rest
4.wipe cache partion
Plese Help... !!!
:crying:
I m having MMX A25 .
i have installed CWM 5.x.x.x.version
whenever i tried to install custom Rom in it .
It just shows me an error SIGNATURE VERIFICATION FAILED
i am totally stuck,.. !! plese somebody help me out to install custom rom.
Help would b appriciated. :good:
I have same problem with galaxy s gt i9000 Froyo with recovery 3e.
I read that this recovery doesn't allow installation of files not signed.
Tried many but no luck I'm rooted but cannot install even a custom recovery.
Did you find the solution please.
Thanks
Sent from my GT-I9000 using Tapatalk 2
I have a Sprint 7 Tab running EF17, Firmware v. 2.3.4 and Kernal 2.6.35.7.
Long ago I rooted the Tab and installed Root Explorer, Rom Manager and Titanium RootPro, all without any problems at all. When I use Rom Manager, it states I have Clockworkmod version 2.5.1.2 (which might be the problem).
I wipe Dalvik and factory reset. No matter which version I try to flash, the update process starts and sates "Verifying update package..." then I get the signature verification failed message.
I spent a couple of hours in this forum trying to find out what I was doing wrong and it seems either I have too old a version of CWM or my SDCARD is somehow corrupt.
If the problem is the version of CWM, is there a simple way to update it? I tried to use Heimdall to update the kernal. Zadig recognizes the Tab when shut off, but when I put the Tab into downloading mode and list devices, the Tab does not show up.
If the problem is the SDCARD is corrupt, what next?
The Old version CWM was the problem. For some reason my old 32 Laptop would not install Heimdall so I tried a new 64 windows machine and I installed the new kernal. The install then went fine.
Unless there is a belief that this post might help another user, please delete this post.
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
Hi guys i have an problem i was trying to downgrade my phone from Y560-L01V100R001C577B046 version to V100R001C577B040_Europe but the recovery says : "Can't install this package(date) over newer build (date) E:error in /sdcard/dload/update.App(status 7) Installation aborted.
Is there any way to just install ANY another stock rom to my phone just to clear weird stuff that i did at him.
Thanks for help and sorry for english.
ziomcA said:
Hi guys i have an problem i was trying to downgrade my phone from Y560-L01V100R001C577B046 version to V100R001C577B040_Europe but the recovery says : "Can't install this package(date) over newer build (date) E:error in /sdcard/dload/update.App(status 7) Installation aborted.
Is there any way to just install ANY another stock rom to my phone just to clear weird stuff that i did at him.
Thanks for help and sorry for english.
Click to expand...
Click to collapse
Hi.
Sorry for late answer, but I find the solution just two days ago.
A) Huawei recovery don't allow to flash rom wich version is minor that current recovery's version,
https://forum.xda-developers.com/showpost.php?p=65074910&postcount=18
>AND
B) each time the phone boot, the recovery is updated if stored version is old
https://forum.xda-developers.com/showpost.php?p=65212304&postcount=193
(antoher android device, but the function is the same foe Huawei)
The solution
1: enable USB debug & Unlock bootloader (erase all data's !!!!)
2: copy desired DLOAD rom version to SD card and put it in phone (not older than recovery you flash, see next)
3: flash old recovery via fastboot, and DON'T boot phone normally
4: boot into recovery (just flashed)
5: wipe cache and Dalvik
6: apply update from external sdcard
7: reboot to system, if recovery don't do it
Links to recovery and rom are at the first link, reference for recovery updates at the second one.
Regards
M.A.