Okay, so this is what happened:
1) I received the OTA update and everything went fine with upgrading the my T-mobile Springboard tab to ICS 4.0.3
2) I then got brave and went ahead with rooting and installing SU using the technique described in "Root Stock T-Mobile Springboard" by xdajunkman. That worked fine and I was able to get CWM recovery installed.
3) I then tried to install the [ROM][ICS] [Unofficial] Root-ready Huawei/Springboard International ROM and downloaded the dload folder to my SDCard, etc. I tried using the dload folder with the ulmt.cfg file in it and that failed with a "Installation aborted" message. I then removed that file and tried to go into CWM and tried "Install from zip" approach. Same thing...installation aborted message.
4) So, then I did the next stupid thing...in CWM, I formatted my /system, /data, and /cache. That was a big mistake! I now have officially bricked by tab.
5) I tried to get rid of CWM recovery by extracting the recovery.img file from the stock rom zip file. I fastboot flashed that to the recovery and recovery2 partitions. I then thought, let me try extracting the update.zip from the stock rom zip and put that on the root of my sdcard and tried to install that. No go...it just says, update failed with a big red "FAIL" message in the center.
6) I then tried to install CM10, to see if that would work. I downloaded the TWRP recovery and also the CM10 ROM .zip file, along with the google apps zip. I flashed the TWRP recovery using fastboot. That worked fine. I was also able to install the CM10 Rom, or at least it reported back "Successful". Same with the google apps zip. But then when I reboot, it only gets to the T-mobile Splash screen and stays there forever.
Please help! I tried to install the Stock Rom using the TWRP recovery, but again, it reports "Installation aborted." So, what am I doing wrong or what can I do to fix this?
Thanks.
[UPDATE] -
Okay, so I actually tried installing CM10 again using the TWRP recovery since it said that it was "Successful." And sure enough, it was successful, it seems. Once I installed it, rebooted the tablet and waited on the T-mobile Springboard screen for about 10 minutes, it launched CyanogenMod. I then set up the tablet with CM10. I had received the unlock code from T-mobile and so my tablet was sim unlocked. I put a AT&T sim card and sure enough it got signal and I was able to surf the web and make phone calls. I downloaded the speed test app from the Play Store and noticed that I was getting about 1.5Mbps download and about 600kbps upload. Not bad. The problem I noticed is that I can't receive calls. I can call out, but when someone tries to call me, the tablet doesn't acknowledge an incoming call. The caller just goes straight to voicemail. I do get a voicemail alert.
So, I don't know whether that is an issue with the CM10 build or a problem in my network / APN settings.
I would like to get the rooted T-mobile International stock ROM on there so that I can try it with that. I'll keep you all posted.
Thanks!
9 times out of 10, I get installation aborted errors because of a botched download. Try downloading the file again, and if available, verify that the MD5 sum of your downloaded file matches the one provided by the developer.
And if I'm not mistaken, TWRP recovery and CWM recovery aren't capable of flashing the T-Mobile stock recovery. If you have TWRP working properly, I would continue trying to flash one of the unlocked ROMs available. I highly recommend HWMOD's ICS (available here)
Best bet would be to fastboot flash the recovery img from the hauwei site update.zip. Then do the standard pop the stock hauwei update.zip on the sd card and do the normal upgrade method. That should full wipe the phone and then you can start tinkering with it again. Also huawei posted the offical root on their site.
nightanole said:
Best bet would be to fastboot flash the recovery img from the hauwei site update.zip. Then do the standard pop the stock hauwei update.zip on the sd card and do the normal upgrade method. That should full wipe the phone and then you can start tinkering with it again. Also huawei posted the offical root on their site.
Click to expand...
Click to collapse
I don't want to mix up the T-mobile images with the Huawei images. Even though I've screwed things up already. But, if you read my previous post, I've got CM10 working, but no incoming calls.
Related
Hi guys,
I have unlocked my bootloader a few days ago, and also installed the CWM recovery, which I used to install the ATT 2.3.4 ROM (I own an International Atrix), and it was working flawlessly. Being annoyed by that bunch of bloatware, I decided to install the Alien-ROM, so I wiped data with fastboot -w, and entered CWM to erase the cache partition/dalvik cache and install Alien. The problem is, when I tried to install the .zip package, CWM threw at me "Installation Aborted", with no error message whatsoever, just before "Beginning Installation". At first I thought my .zip was corrupted, so I re-downloaded it and tried again, but got the same error.
Being unable to install the AlienROM, I fastbooted the ORFR ROM (surely a lot cleaner than ATT's) and installed the ROM manager app, and through it, updated my CWM to the latest version. And then there I was trying to install the .zip again, with no success. As a last effort, I uninstalled manually the install-recovery.sh file and the recovery partition, reinstalled Tenfar's CWM, but fell into the same error: "Installation Aborted".
Does someone have a clue of that is happening??
Thanks in advance.
Rom manager recovery does not work always.what I suggest is use tenfar recovery and then put alien zip on your ext.SD card and use tenfar recovery --- choose zip from SD card--- browse and select alien.zip and flash through it.
Hope this helps.
Well, I tried to install Tenfar's CWM, as I said at the end of my first post. I recently installed a new CWM-based recovery, and it also failed to install any .zip. Could it be because I'm using ORFR ROM? I've noticed the misbehaving os CWM when I uninstalled ATTs ROM...
Install rom racer's recovery.
I voided my warranty.
Use this link: romracer's custom CWM
Let us know if this helps
pedrohz said:
Hi guys,
I have unlocked my bootloader a few days ago, and also installed the CWM recovery, which I used to install the ATT 2.3.4 ROM (I own an International Atrix), and it was working flawlessly. Being annoyed by that bunch of bloatware, I decided to install the Alien-ROM, so I wiped data with fastboot -w, and entered CWM to erase the cache partition/dalvik cache and install Alien. The problem is, when I tried to install the .zip package, CWM threw at me "Installation Aborted", with no error message whatsoever, just before "Beginning Installation". At first I thought my .zip was corrupted, so I re-downloaded it and tried again, but got the same error.
Being unable to install the AlienROM, I fastbooted the ORFR ROM (surely a lot cleaner than ATT's) and installed the ROM manager app, and through it, updated my CWM to the latest version. And then there I was trying to install the .zip again, with no success. As a last effort, I uninstalled manually the install-recovery.sh file and the recovery partition, reinstalled Tenfar's CWM, but fell into the same error: "Installation Aborted".
Does someone have a clue of that is happening??
Thanks in advance.
Click to expand...
Click to collapse
May be you want to try installing the CWM from here... http://forum.xda-developers.com/showthread.php?t=1204500
This should most likely help you fixing the issue you are facing.
Good Luck.
Cheers!!!
Just tried the recovery mentioned above by you all... and nothing, I keep getting the same error -> "Installation aborted", right after "Beggining installation" (or something like that)
Any clues?
pedrohz said:
Just tried the recovery mentioned above by you all... and nothing, I keep getting the same error -> "Installation aborted", right after "Beggining installation" (or something like that)
Any clues?
Click to expand...
Click to collapse
How are you installing RomRacer's CWM? Flashing the .zip or via fastboot?
Sent from my MB860 using XDA Premium App
I've installed it through fastboot, as it's the only way I can do it... my problem resides solely on the fact that I can't install any .zip through it, I keep getting "Installation aborted", no matter what I try to install (Kernels/ROMs/etc)
Pedrohz... Are you using a Mac? If so do you have it set to unzip after downloading? Then are you re-zipping the file before you try to install? If so turn off the unzip feature. Just a thought... Hope it helps
Similar Issue, can't boot into anything :/ if you can help, read below :S
Ok, so I backed up using Oringinal CWM, and it said all OK. After this, I restored the backup, just to check all was working. I got the error error formatting /system. Rebooting, I found that my phone wouldn't boot. Thinking the only way out was to flash a new ROM, I flashed the new boot.img from evals Orange France 2.3.4 firmware, so that I would have the ram fix. After this, I wiped all the caches and the user data, and tried to install the ROM.
SAME FRIGGEN ERROR. no error code, just installation aborted.
Finally, I tried AGAIN with romracers cwm, but same error. Restoring from backup now gives the error - "Unable to flash new boot.img" or something along those lines.
If anyone cares, heres what my phones running
Firmware = Orange UK 4.4.20 (Android 2.2.2)
SBF= Bell_ihop (the international bootloader unlock sbf)
State= Won't boot past the big red M in the centre of the screen.
Hi, I'm hoping somebody might be able to shed some light. My phone isn't rooted or unlocked and last night I did the OTA update. Upon the first reboot, the phone is stuck at the "Dual Core Technology" screen and won't go any further. I can hold volume down and power to get to Fastboot, a bunch of other things, and Android Recovery.
Within Android Recovery, I've tried the wipe options as well as the apply sdcard update.zip but the wipes don't help anything and the apply update resutls in a signature error.
I feel like if I could just get the .zip update onto the internal SD storage, the apply update would work (maybe the OTA download was corrupted somehow). Is there anyway to use Fastboot or Moto-Fastboot to copy files to the internal SD storage?
Any help would be much appreciated.
hi
Try putting the OTA on a micro SD card (thats where it looks for it anyways) rename it to update.zip and try to flash that update.
y2whisper said:
hi
Try putting the OTA on a micro SD card (thats where it looks for it anyways) rename it to update.zip and try to flash that update.
Click to expand...
Click to collapse
Thanks for the reply.
Tried and this is what happened (which is more than before):
Install from SDCARD
Finding update package
opening update package
Verifying update package
...installing update
Verifying current system
.....assert failed: apply_patch_check("preinstall/app/gameloft_3games.zip","5428aeff....."
Not sure what that means, but I'll google and search here for a bit.
Edit: Just noticed that there was more to the output:
E:Error in /sdcard/update.zip
(status 7)
Installation aborted.
either you removed some apps before or the install updated some of the files and now doesn't pass the verification check.
search on here for a bit possibly flash cwm recovery and then the 2.2 gobbstopper. or you could try to go through bell as everything you have done is through official methods.
Okay thanks a lot for the help. I have since Unlocked using the Pudding IHOP thread and next will install Gobstopper 2.3.4 Bell (http://forum.xda-developers.com/showthread.php?t=1195922), though the CWM (tenfar's) post only shows that it's only for AT&T, which is odd since it's linked from the Gobstopper Bell thread).
Any idea if I can safely use Tenfar's CWM Recovery from here?:http://forum.xda-developers.com/showthread.php?t=1138541
Actually i would recommend only using that one for gobstopper purposes.
Although I would either wait until the 2.3.4 version is updated or get the 2.2.2 version and upgrade your device with the official rom as there have been changes since the 2.3.4 leak
Would you recommend another recovery instead of Tenfar's CWM? I'm currently now using the one that came in the CWM_INT_Recovery.zip (recover-d00.img).
Seems really hard to find a recovery that is definitely safe with Bell Atrix, and I'm never sure if just "moto-fastboot flash recovery %recoveryfile.img% is all I need to do now that it's unlocked. I might have to find another ROM since the download isn't working so well.
to install the gobstopper? no only use the latest tenfar cwm for that. after which, you could go with romracer and it will be fine
Okay great, thanks. The latest Tenfar CWM says at the top of the thread that it's only for Unlocked ATT users in bold red text so I was hesitant to use it.
I have the same issue. I have tried EVERYTHING I can think of to get it to boot.
The only difference in my case is I have run the update multiple times all finishing successfully with no errors.
This is really bugging me, any help would be appreciated.
Thanks
Jeff53765 said:
I have the same issue. I have tried EVERYTHING I can think of to get it to boot.
The only difference in my case is I have run the update multiple times all finishing successfully with no errors.
This is really bugging me, any help would be appreciated.
Thanks
Click to expand...
Click to collapse
I'm an extreme novice Android/Atrix user but I would recommend doing what I did:
Use the Pudding IHOP instructions to RSDLite flash the unlocker SBF for Bell
Use moto-fastboot to flash recovery with Tenfar's latest CWM recovery (updated June 30)
Use Tenfar's CWM recovery to mount your USB storage, download the GobStopper 2.3.4 zip to your sdcard, then again using CWM, update from the zip.
See the GobStopper 2.2.2 thread for some pre-cleanup steps before trying to update with the 2.3.4 zip, all using Moto-Fastboot or regular fastboot from the Android sdk.
Thank you
You saved my life
Woot woot!
My old one started getting the sim card error.Still under warranty so...new phone in hand. (Refurb) I rooted using Odin 3v1.85 installed SuperUser and ClockworkModRecovery. All moves along fine. Now I try to install ROM zips (tried three) and they all abort quickly. It starts opening and checking and aborts saying error with zip file. I have downloaded three different ROMs and redid it from different sites too...same thing. What am I doing wrong?
Did you update your recovery after rooting? I recommend twrp which can be found in the original development section.
"Update my recovery" Hmmmm....since I am unsure what you mean...I guess not. TOG recommended TWRP over CWM too. I'll go take a look see. By "original dev section" I assume you mean the other subforum?
Quick explanation of updating my recovery?
Thanks for your valuable time. Here, have a coffee...U)
EDIT:
OK, I went, found and downloaded the latest TWRP2.zp for Odin install, since I'm most familiar with that method. So, am I right in these steps?
1. Re-root w Odin using .tar file from the TWRP.zip using the PDA button.
2.Update?
3. Reboot into recovery (does twrp use the same method as cwm?)
3.Install ROM zip of choice...rejoice?
That's way too complicated broseph...
You still have cwm right?
Just Go back to the twrp thread, download the recovery flashable zip.
Put it on your sdcard and flash it in cwm like a Rom.
Once that's done reboot recovery and you'll now have twrp
Button combos are built into the boatloaders, changing recovery has no effect on them whatsoever.
OK
Thanks again all....I did all of the above and finally got the ROM to load, then Gapps, and the rest of the drill. I never could access my back-up that I stored on my ext SD card and the card is not showing in any file explorers (although it shows in storage, under settings ?).
AT least I have a functioning phone...yay.
Sd card is named as /emmc and several other names.
I have a Nabi 2 UK for my son and had GAPPS installed but stayed on the 1.9.37 version as the OAT would not work.
I now see that I can get the tablet up to 4.1 and get GAPPS as well but I seem to be defeated at the last step every turn but the 'dead' android on it's back.
I don't have the original back up to start from.
I've gone to the 1937 stock image and via TWRP, the OAT'ed to 2.1, but the second 2.3 update fails with the dead android
I've tried 2311 which also fails in the same way.
I've seen some conversations on these boards but the file outlined are often out of bandwith and I can't comment on the threads to ask for help.
So now I'm back to 1.9.37 but I also can't seem to reinstate GAPP using Nabi Labs tools I as it braks the nabi mode and the tablet won't work.
All in all this is turing out to be a massive waste of time. Any suggestions how I can salavge this?
Cheers
Fulhair
Fulhair said:
I have a Nabi 2 UK for my son and had GAPPS installed but stayed on the 1.9.37 version as the OAT would not work.
I now see that I can get the tablet up to 4.1 and get GAPPS as well but I seem to be defeated at the last step every turn but the 'dead' android on it's back.
I don't have the original back up to start from.
I've gone to the 1937 stock image and via TWRP, the OAT'ed to 2.1, but the second 2.3 update fails with the dead android
I've tried 2311 which also fails in the same way.
I've seen some conversations on these boards but the file outlined are often out of bandwith and I can't comment on the threads to ask for help.
So now I'm back to 1.9.37 but I also can't seem to reinstate GAPP using Nabi Labs tools I as it braks the nabi mode and the tablet won't work.
All in all this is turing out to be a massive waste of time. Any suggestions how I can salavge this?
Cheers
Fulhair
Click to expand...
Click to collapse
Hi.
I had a similar issue (US ROM though). I had dead Android guys, messages in TWRP that I didn't have an operating system installed and all kinds of other issues. I really thought that I had bricked the Nabi as I was up against a wall and nothing I was finding online was working.
I have posted this before elsewhere -- this is what I did to get out of it:
I think when I was installing the JB version of TWRP I also tried to change the screenlock image not realizing that the process had changed for JB. I had a complete mess with very similar if not identical issues as you.
What I did:
1. Make sure TWRP 2.6.3.0 for Jellybean is on the Nabi.
2. Download the stock 2.3.11 ROM from the Nabi wiki site and unzip it into a folder on your PC.
3. Next you need to copy the 4 recovery files from your PC to your SD card. I put the SD card into my PC and copied the files over putting them into a TWRP back up folder on the SD card. Now, in order for Jellybean TWRP to recognize the backup, I had to fool it into thinking I had a "good" existing Jellybean TWRP backup and rename the TWRP backup folders to something like this:
TWRP\BACKUPS\0f41000001000000\2014-01-24--09-54-07 JRO03C\
4. Put the SD card back into the Nabi and then boot into TWRP mode.
5. Do a restore from there.
It *should* install a clean fresh copy of Jellybean on the Nabi. It does take what seems like an eternity for it to get past the spinning circle with the NABI logo when it's loading for the first time so be patient.
You may need to alter some of this since you are in the UK though.. but the main suggestion is to put whatever copy of the ROM onto an SD card (remember to follow the correct directory format for either ICS or JB) and then restore via TWRP to get you running.
2girlzdad said:
Hi.
I had a similar issue (US ROM though). I had dead Android guys, messages in TWRP that I didn't have an operating system installed and all kinds of other issues. I really thought that I had bricked the Nabi as I was up against a well and nothing I was finding online was working.
I have posted this before elsewhere -- this is what I did to get out of it:
I think when I was installing the JB version of TWRP I also tried to change the screenlock image not realizing that the process had changed for JB. I had a complete mess with very similar if not identical issues as you.
What I did:
1. Make sure TWRP 2.6.3.0 for Jellybean is on the Nabi.
2. Download the stock 2.3.11 ROM from the Nabi wiki site and unzip it into a folder on your PC.
3. Next you need to copy the 4 recovery files from your PC to your SD card. I put the SD card into my PC and copied the files over putting them into a TWRP back up folder on the SD card. Now, in order for Jellybean TWRP to recognize the backup, I had to fool it into thinking I had a "good" existing Jellybean TWRP backup and rename the TWRP backup folders to something like this:
TWRP\BACKUPS\0f41000001000000\2014-01-24--09-54-07 JRO03C\
4. Put the SD card back into the Nabi and then boot into TWRP mode.
5. Do a restore from there.
It *should* install a clean fresh copy of Jellybean on the Nabi. It does take what seems like an eternity for it to get past the spinning circle with the NABI logo when it's loading for the first time so be patient.
You may need to alter some of this since you are in the UK though.. but the main suggestion is to put whatever copy of the ROM onto an SD card (remember to follow the correct directory format for either ICS or JB) and then restore via TWRP to get you running.
Click to expand...
Click to collapse
Thanks for the outline. Sorry if I'm being a bit dim but how do I get the 2.6.3.0 TWRP onto it?
I've got the NaviLabs GUI and TWRP'd up to v 2.6.1.0 but need to get the Jelly Bean version.
I've tried the zip install with twrp-recovery-JBNV7AUS-263 but it just breaks TWRP and won't boot.
Thanks again.
Fulhair said:
Thanks for the outline. Sorry if I'm being a bit dim but how do I get the 2.6.3.0 TWRP onto it?
I've got the NaviLabs GUI and TWRP'd up to v 2.6.1.0 but need to get the Jelly Bean version.
I've tried the zip install with twrp-recovery-JBNV7AUS-263 but it just breaks TWRP and won't boot.
Thanks again.
Click to expand...
Click to collapse
Get whatever TWRP you want
http://forum.xda-developers.com/showpost.php?p=48891386&postcount=76
Follow this http://forum.xda-developers.com/showpost.php?p=49956448&postcount=49 to put that recovery in Nabilabgui except use
For XP
C:\Documents and Settings\username\Local Settings\Apps\2.0\xxx\xxx\nabixxxx\2\recovery\new
or Vista/7/8
C:\Users\username\appdata\local\apps\2.0\xxx\xxx\n abixxx\2\recovery\new
The post is for the JR I think the above will be right for the Nabi2, I'm mobile so I can't check.
aicjofs said:
Get whatever TWRP you want
http://forum.xda-developers.com/showpost.php?p=48891386&postcount=76
Follow this http://forum.xda-developers.com/showpost.php?p=49956448&postcount=49 to put that recovery in Nabilabgui except use
For XP
C:\Documents and Settings\username\Local Settings\Apps\2.0\xxx\xxx\nabixxxx\2\recovery\new
or Vista/7/8
C:\Users\username\appdata\local\apps\2.0\xxx\xxx\n abixxx\2\recovery\new
The post is for the JR I think the above will be right for the Nabi2, I'm mobile so I can't check.
Click to expand...
Click to collapse
Good advice. Thanks for the TWRP instructions,
I can now get the TWRP v2.6.3.0 on, but only the ICS version will boot, The Jelly bean install won't bring up the TWRP screens. I've even tried updating to 2311 from the ICS version and then trying to update to the TWRP JB version with no joy.
Now I can't even get the nabi to connect to the usb in Nabi Lab GUI This is doing my head in!!!
Fulhair said:
Good advice. Thanks for the TWRP instructions,
I can now get the TWRP v2.6.3.0 on, but only the ICS version will boot, The Jelly bean install won't bring up the TWRP screens. I've even tried updating to 2311 from the ICS version and then trying to update to the TWRP JB version with no joy.
Now I can't even get the nabi to connect to the usb in Nabi Lab GUI This is doing my head in!!!
Click to expand...
Click to collapse
If going to 2311 you need to update bootloader. That is in the addonfix zip. Then JB twrp should work.
aicjofs said:
If going to 2311 you need to update bootloader. That is in the addonfix zip. Then JB twrp should work.
Click to expand...
Click to collapse
Okay, so I managed to get back to TWRP 2.6.3.0 under ICS. I then install the 2311 rom, which succeeds. As per instructions, before I reboot I go back and try to install the addon zip in TWRP.
But I get an error
'E:Error executing updater binary in zip '/external_sdcard/addonzip'
Error flashing zip '/external_sdcard/addonzip'.
I'm not sure if the error is something with TWRP or the addon.zip.
One of the microsd I have won't show the addonzip and none of the other TWRP recovery roms..and yes I have checked the directory structure.
Any ideas?
Thanks
Fulhair said:
Okay, so I managed to get back to TWRP 2.6.3.0 under ICS. I then install the 2311 rom, which succeeds. As per instructions, before I reboot I go back and try to install the addon zip in TWRP.
But I get an error
'E:Error executing updater binary in zip '/external_sdcard/addonzip'
Error flashing zip '/external_sdcard/addonzip'.
I'm not sure if the error is something with TWRP or the addon.zip.
One of the microsd I have won't show the addonzip and none of the other TWRP recovery roms..and yes I have checked the directory structure.
Any ideas?
Thanks
Click to expand...
Click to collapse
Okay, I abandoned the addon.zip and went back to 2.1.27 rom and OAT over to get to the last update which failed.
Then installed the OAT2.zip via TWRP and bingo! Now working on Jelly Bean with Google Play - okay it's now the US version but it works
I would caution that the zip install had to be installed on the internal SD not the external one.
But otherwise a BIG thank you to all for building the tools to let me do the update and for your support.
Cheers:highfive:
Hi - My sister has asked me to take a look at her Nexus 7 as she wants to upgrade it to the latest Android version. Unfortunately she bought it second hand and it had been rooted. It also seems to have the clockworkmod boot loader.
I'm having issues just trying to get this thing un-rooted and back to factory as it will not install the Android 5 update. I have used the Nexus Root Toolkit and all goes well right up to the part where it puts the device into recovery mode - my PC loses its connection to the Nexus and then the connection attempt times out. I have downloaded the Android 5 zip from from google and put it on the phone, then booted into recovery mode and tried to install from the zip. I just get an unhelpful 'Installation aborted' message. just not sure as to where to go from here..,.
The download from Google isn't meant to be flashed in recovery... it's the factory image files zipped. You have to unzip it, then unzip the zip that's inside also, then you should be able to fastboot flash the bootloader, recovery, system, data, and userdata.