Hi there,
Tried to install Hyperdrive but unfortunately I have crazy lags and problems with it. It is almost impossible to move around on the phone with it. The biggest problem I have is that It wont boot into TWRP recovery anymore. I made a backup before but when I try to install it with the android system recovery it fails (E:footer is wrong and E: signature verification failed)
I tried to flash Hyperdrive from recovery again (didn't work); I tried to wipe cache and format (didn't work)
Now I tried to flash a new Rom but apparently you cannot flash with the android recovery environment(I am also getting the two E: errors)?
Would like to get the phone back. Hope someone can help.
Do you remember the system baseband? This is critical. If it was MDK, then you could have used safestrap. If not, then you should have used safestrap, not MDK.
The A.R.E won't work, you need Odin + the tar file..
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.
I've flashed a few phones in my time including 2 S2's and an S3 although I had a big problem with this S3 my friend had. It had 4.1.2 default samsung software on it and i tried to ODIN flash an autoroot cwm v5 file i usually use to root phones, it did not go as expected eg. it just turned the phone off but came out as a pass on ODIN, and ii flashed it again with another CWM recovery file i found from the net, this time its V6+ and it flashed like a charm you know the usual result right. Now that CWM works i tried to flash 4.4.2 on the phone and it gave me that "set metadata recursive some changes failed" error thing and the phone wont restart. I have wiped the data, dalvik and cache every single time i flash mind you using the CWM recovery. Now when i flash to some random rom lower than KITKAT it would flash well and would function quite well. I once again tried to flash kitkat by downloading rom manager and flashing to the latest version of CWM but here's the thing it CWM wont update and the current version installed just wont flash the KITKAT rom and just gives the same 'set metadata recursive some changes failed error' and again wont boot to system if i didn't flash back to 4.3 i tried twrp too to the same result "set metadata recursive some changes failed". The fix that the forums explained was updating to the latest CWM(CWM touch wont flash neither) but it didnt work forme even TWRP didnt work, someone help please.
First reset all you've done by flashing a full stock 4.3 rom, factory reset and make sure everything works.
Then flash philz recovery and use that to flash your custom rom.
Make sure you read the guides in general forum, sticky threads before you start.
Hello Everybody,
my boss got me a Galaxy ACE S5830i in order to test some app development and I immediately managed to root it and install a custom ROM.
These were the steps I took
1- I flashed the update.zip I found around the web, for example here -> http://www.theandroidroot.com/root-install-cwm-recovery-samsung-galaxy-ace-s5830i/
2- I flashed CWM 5.0 and immediately, without rebooting, saw the new Recovery. So it really did install!
3- I updated to CWM 6
4- I flashed thunder kernel in order to make the CWM permanent -> http://forum.xda-developers.com/showthread.php?t=2335947
5- I rebooted the phone in recovery mode and got the CWM. Everything was fine up to now
6- I flashed a ROM (after wiping everything). Actually, several roms. I tried first with CGM, then with Aroma and Retribution Beta. http://forum.xda-developers.com/showthread.php?t=1806471 All of them managed to install but none of them works. What ALWAYS happens is that the ROM installs, then I reboot and the phone does not go past the Samsung Logo. Then, and here we come to the weirdest part, when I reboot in recovery mode in order to flash another rom... I get the stock recovery! No CWM, no customizations!
What's happening, in your opinion? I tried to flash a custom ROM with Odin as well, but being on Linux I had to use JOdin and could not manage to flash anything because (as it ALWAYS happens with JOdin) I was not able to load a suitable PIT file. No success with wine+odin as well.
Please, could somebody help me? I can't use my boss phone, and can't return it to him until I get a working ROM on it
Thank you in advance
P.S. When I get to the Recovery I see some rows to the bottom:
-- Appling Multi-CSC --
E:failed to mount /system (Invalid argument)
E:failed to mount /system (Indalid argument)
and (I know 'cause I tried) I can't mount or format the /system partition. Maybe it's related, maybe it's not...
ilsecondodasinistra said:
Hello Everybody,
my boss got me a Galaxy ACE S5830i in order to test some app development and I immediately managed to root it and install a custom ROM.
These were the steps I took
1- I flashed the update.zip I found around the web, for example here -> http://www.theandroidroot.com/root-install-cwm-recovery-samsung-galaxy-ace-s5830i/
2- I flashed CWM 5.0 and immediately, without rebooting, saw the new Recovery. So it really did install!
3- I updated to CWM 6
4- I flashed thunder kernel in order to make the CWM permanent -> http://forum.xda-developers.com/showthread.php?t=2335947
5- I rebooted the phone in recovery mode and got the CWM. Everything was fine up to now
6- I flashed a ROM (after wiping everything). Actually, several roms. I tried first with CGM, then with Aroma and Retribution Beta. http://forum.xda-developers.com/showthread.php?t=1806471 All of them managed to install but none of them works. What ALWAYS happens is that the ROM installs, then I reboot and the phone does not go past the Samsung Logo. Then, and here we come to the weirdest part, when I reboot in recovery mode in order to flash another rom... I get the stock recovery! No CWM, no customizations!
What's happening, in your opinion? I tried to flash a custom ROM with Odin as well, but being on Linux I had to use JOdin and could not manage to flash anything because (as it ALWAYS happens with JOdin) I was not able to load a suitable PIT file. No success with wine+odin as well.
Please, could somebody help me? I can't use my boss phone, and can't return it to him until I get a working ROM on it
Thank you in advance
P.S. When I get to the Recovery I see some rows to the bottom:
-- Appling Multi-CSC --
E:failed to mount /system (Invalid argument)
E:failed to mount /system (Indalid argument)
and (I know 'cause I tried) I can't mount or format the /system partition. Maybe it's related, maybe it's not...
Click to expand...
Click to collapse
can u get temporary cwm recovery when selecting
'apply update from sd'
then look at this thread
forum.xda-developers.com/showthread.php?t=1118688
as9333 said:
can u get temporary cwm recovery when selecting
'apply update from sd'
then look at this thread
forum.xda-developers.com/showthread.php?t=1118688
Click to expand...
Click to collapse
Hello,
thank you for answering.
I can temporary get to CWM recovery for sure, but I don't know how to push the erase_image file (that I found) to the device. I'm only able to copy files on the SD, using another phone, and then flash them from CWM. Is there a way to make adb able to detect the device even when it's in recovery?
Thank you
ilsecondodasinistra said:
Hello,
thank you for answering.
I can temporary get to CWM recovery for sure, but I don't know how to push the erase_image file (that I found) to the device. I'm only able to copy files on the SD, using another phone, and then flash them from CWM. Is there a way to make adb able to detect the device even when it's in recovery?
Thank you
Click to expand...
Click to collapse
First try to flash another rom..if that not work then flash stock rom from odin..
Here is the link for unbrick your device.go here and try to unbrick..
http://forum.xda-developers.com/showthread.php?t=1840645
Sent from my GT-S5830i using Tapatalk 2
Are the ROMs you tried based on CM7/9? Because if they are, you need to format your system partitions to EXT4. You can do that with the multi-formatter.
Also, you say that you have your stock recovery back. Check the ROM zips that you flashed for any boot.img. If there is, check which kernel and which version. Some older kernels still have stock recovery.
As even stock recovery cannot mount /system, clearly your system partitions are corrupt. Format with the multi-formatter and flash a CM7/9 based ROM or flash back stock firmware via Odin.
If you choose the multi-formatter, remember to flash a kernel afterwards. And if you prefer, one with a permanent CWM.
Sent because I <3 Aerith
Hello,
I searched in many threads as I could and although I learned that mediatek phones were virtually "unbrikable", I'm afraid it keeps getting worse and won't do more without your expertise.
So a few days ago I was wiping my phone to install another rom and besides wiping data and cache, I also made the huge mistake of wiping SYSTEM... My phone now just boots into recovery and nothing else.
I have an Efox Smart e4, equals to no.1 s6 and hdc galaxy s4 according to other posts here. MTK 6589, 1gb internal, 1,84gb internal sd.
The first custom rom that i installed was Essefour no.1 s6 by iceman and also the touch recovery. The rom performed great but I wanted to solve the issue that the phone kept switching between sd external and internal randomly. Also, I wanted to merge the internal memory with the internal sd so I was gonna try another rom. With this problem, was even trying the stock rom but to no avail.
When I try to install the Smart e4 factory rom for cwm and I get status 7.
E:Resource type (image) failed to load
Installing /sdcard/SMART-E4_V1.0_V01_2013-10-29_CWM.zip
Checking for MD5 file
Skipping MD5 check: no MD5 file found.
... Writing boot...
assert failed: write_raw_image("/tmp/boot.img", "boot")
Error in /sdcard/SMART-E4_V1.0_V01_2013-10-29_CWM.zip
(Status 7)
Click to expand...
Click to collapse
Other roms it just fails.
Right now, my computer windows 8.1 x64 can't identify correctly my phone, only access the sd. So can't do any adb push. In download mode it identifies as lenovo composite interface?? and cdc serial, the last I can't install. In other modes, I get gt-9500 but with the yellow triangle.
I would really really appreciate any help, thanks!
Might try to just edit the updater-script and remove the asserts.
Reference this for more info: http://forum.xda-developers.com/showthread.php?t=2522762
But I think your issue is that since you wiped the system, there's no /tmp folder to store the boot.img. However, if the last rom and this rom can use the same kernel (boot.img) then removing the assert for the boot.img install might do it since wiping the system does not affect the kernel.
What happened to the other rom you know is working somewhat? Can you just reflash that?
Otherwise, you'll just have to find the official way to flash with the scatter file and all that.
I searched for that updater and there are no lines for assert on the stock rom. Also inside the main zip, there are zips for system, boot, recovery and logo...
I'm trying to install the stock rom to play it safe since it was the same that came with the phone. The previous rom I talked about, I deleted it and now the phone isn't recognized on the computer..
Since I don't know if they have the same kernels, is it safe to try and reinstall the custom rom?
As of using scatter and such, maybe I need other pc to get the drivers running again.
Will let you know
I got it!!
The zip from the stock rom wouldn't let me install the kernel (boot). Managed to install only the rom, and as you said the kernel wasn't the same.
Eventually I reinstalled the custom rom and afterwards flashed a completely different rom via spflash tools since it connected successfully to my computer this time.
As I'm already restoring apps and data, I think everything is working properly.
Once more, thank you very much
Hi I am currently having a problem with my Galaxy S4 (NC5) I am running 4.4.2 with HyperDrive 18.1 installed. Yesterday I noticed that I couldn't access the web over data so I decided to bring my phone back to stock ROM to see if that would fix the problem.
I Did a factory reset and wiped cache. After that I tried flashing a stock ROM I found online via Odin. Odin got to system and then kept failing every single time. I am now stuck at a Samsung logo with a open lock that says custom. I have an External SD and I have a backup of when I first got the phone.
What can I do ?
Chrome1909 said:
Hi I am currently having a problem with my Galaxy S4 (NC5) I am running 4.4.2 with HyperDrive 18.1 installed. Yesterday I noticed that I couldn't access the web over data so I decided to bring my phone back to stock ROM to see if that would fix the problem.
I Did a factory reset and wiped cache. After that I tried flashing a stock ROM I found online via Odin. Odin got to system and then kept failing every single time. I am now stuck at a Samsung logo with a open lock that says custom. I have an External SD and I have a backup of when I first got the phone.
What can I do ?
Click to expand...
Click to collapse
Try a different USB cable, different USB port, and if that fails, redownload the TAR
npjohnson said:
Try a different USB cable, different USB port, and if that fails, redownload the TAR
Click to expand...
Click to collapse
Okay so I follow the instructions in this thread http://forum.xda-developers.com/showthread.php?t=2735172 and used the files provided. I flashed the full wipe via Odin with the PIT file. And I was able to boot successful. After that I rooted my phone via Towel root and then I installed safestrap. However in safe strap it says
E: Unable to mount '/system'
E: Unable to mount '/systemorig'
I tried installing Hyperdrive 19 and when it started to install it got to 30% and then came right back to the safestrap menu.
Chrome1909 said:
Okay so I follow the instructions in this thread http://forum.xda-developers.com/showthread.php?t=2735172 and used the files provided. I flashed the full wipe via Odin with the PIT file. And I was able to boot successful. After that I rooted my phone via Towel root and then I installed safestrap. However in safe strap it says
E: Unable to mount '/system'
E: Unable to mount '/systemorig'
I tried installing Hyperdrive 19 and when it started to install it got to 30% and then came right back to the safestrap menu.
Click to expand...
Click to collapse
Huh. Make sure you are using 3.75 for the SCH-i545. Not for the S5
I would use the full wipe TARs and try it. That should clear all the error issues up you are seeing. A few of us have the seen the system mount issue that you describe and so far the only way I've found to get rid of them is to use the full wipe TARs.