Okay so I bought this phone few months ago and rooted it soon after that. But then maybe a week after rooting I got stuck in a bootloop. I fixed it by installing the stock rom but still after few weeks it got stuck again. This started happening constantly and I always fixed it by installing the stock rom. But now I'm stuck because when I tried updating from external sd card it said "can't install package over newer build" (and the dates). I tried downloading the newest stock rom from huawei site but still the same thing happened. Then I removed the date check from the edify script and resigned it but now it just says "installation aborted". Now I'm pretty desperate and help would be appreciated.
Related
Hello everyone.
I am having a big issue installing custom ROMs nowadays. Previously it was no deal, but now, whatever ROM I get, it is stuck att the Edify crap in the beginning of installation. Tried using the Amend (or whatever) to Edify on the update script in com -> android or something like that. It does everything fine, but rezipped the archive after saving and tried to flash it. This time I got some message from the tool and it ended with an "Update complete" message. Started the phone. NO change.
So I tried opening just the zip of the rom and yet again, seemed to do some stuff. Transfer to my SD card and everything goes well on installation. Getting the regular "Update complete" message. Restart phone, no change.
Thats how far I got, tried flashing the recovery thinking the recovery obviously might be outdated. No luck, at all.
Might add that the reason I want to use a custom ROM is since the one im using now (Mokee Epic) does not support USB. My computer doesn't recognize it. This way I can get it to work in Sony Ericsson PC Companion and reinstall the stock ROM.
So, im sorry for a big read, but I am in a very bad mood now.
EDIT: Might add that I tried out FeraVolt's ROM which installed fine. The problem was that when I started it and entered my PIN, the screen would go black. I guess this is a result of me NOT flashing with their custom FeraKernel. But when I tried to flash the kernel with FeraVolt's GB 5.3 kernel released earlier this month, It gave me the Edify error.
Sincerily,
I've been trying different ROMS and I used SlimROM for awhile until I realized GPS didn't work and my cell connection sucked comapred to TW-based ROMS. Then I tried Hyperdrive which worked at first but every time I would reboot after the first power on after the install, it would stay stuck on the Samsung screen. I reinstalled it time after time (like 6 times) and it would never REboot after the first boot. Every other ROM I've tried installing (Illusion, Synergy, CleanROM) just gets stuck right after the install and they never boot.
I've also noticed that when I try to do a factory wipe after installing anything but SlimROM, I get "error mounting /data" and "error mounting /sdcard/.android_secure".
I've tested installing all of these with the newest verison of TWRP and CWM v6.0.3.2
any ideas?
Factory reset Last option
snowman4839 said:
I've been trying different ROMS and I used SlimROM for awhile until I realized GPS didn't work and my cell connection sucked comapred to TW-based ROMS. Then I tried Hyperdrive which worked at first but every time I would reboot after the first power on after the install, it would stay stuck on the Samsung screen. I reinstalled it time after time (like 6 times) and it would never REboot after the first boot. Every other ROM I've tried installing (Illusion, Synergy, CleanROM) just gets stuck right after the install and they never boot.
I've also noticed that when I try to do a factory wipe after installing anything but SlimROM, I get "error mounting /data" and "error mounting /sdcard/.android_secure".
I've tested installing all of these with the newest verison of TWRP and CWM v6.0.3.2
any ideas?
Click to expand...
Click to collapse
if nothing works, factory-reset but last option.
yeah I just started downloading the stock rom to flash with ODIN in the morning. I just wanted some reason why this would happen so I won't always have have this problem and to know why it only works with some roms over others.
Please read forum rules before posting
Questions and help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Im having the same problem. I've done a complete ODIN restore to stock like 10 times, while trying Hyperdrive downloaded from 2 sources all with a matching MD5.
I'm on rooted stock right now until someone can figure this out.
I followed the rooting procedure... tried TWRP and Clockwork recoveries... Followed all instructions to the T...
Not sure what else to try... Or what I could be doing wrong... All I can think of now is restoring someones nandroid backup...
Being stuck at the Samsung Galaxy S4 screen sucks...
Zothar said:
Im having the same problem. I've done a complete ODIN restore to stock like 10 times, while trying Hyperdrive downloaded from 2 sources all with a matching MD5.
I'm on rooted stock right now until someone can figure this out.
I followed the rooting procedure... tried TWRP and Clockwork recoveries... Followed all instructions to the T...
Not sure what else to try... Or what I could be doing wrong... All I can think of now is restoring someones nandroid backup...
Being stuck at the Samsung Galaxy S4 screen sucks...
Click to expand...
Click to collapse
I restored to stock using these files http://www.sxtpdevelopers.com/showthread.php?t=237 to flash through ODIN. Rerooted by flashing the older kernel, rooting, installing superSU, then reflashing the newer kernel (normal root procedure). Then I insatlled ROM Manager and gave it root to install CWM recovery. Then I flashed to my same Hyperdrive ROM I was using before and now everything works beautifully. Nothing gets stuck anywhere an no more "cannot mount /data"
Just use that site and restore to stock and everything should work fine.
I'd like to add some confirmation to this. I had similar problems after flashing my first ROM- phone wouldn't reboot a second time, and when I attempted to make nandroids the files would be ridiculously large (~1 TB). I restored to the stock Touchwiz, rerooted normally, and reflashed normally. The strange thing is that I did the rooting and the flashing with the same files I had used the first time, implying something went wrong during the first rooting/flashing process.
It's quite a long story,but I'll try to keep it short, yet detailed.
I rooted my Samsung Galaxy S3 (SGH-T999) about two weeks ago. I made sure to practice the rooting process and read up on the dos' and don't-s' when it comes to rooting and installing custom Roms. A week ago I installed a custom Rom from Aokp known as "AICP (Android Ice Cold Project)." Everything was going good till yesterday when I saw that I was having some memory issues. My internal memory was quite full and I realized and understood that when I wipe--factor reset--my phone, that there is still some data that is left over. Now before I installed AICP I made a backup of the S3 stock Rom. When I seen that the internal memory was getting full I formatted the internal-SD in recovery mode (forgetting that the S3 backup was in it). I decided to, after formatting the internal-SD, try some new Roms. I followed the flashing instructions carefully as always. I went back to AICP and put the phone down for a bit. When I came back to use it, it was frozen. So I restated the phone and then I began getting a message that stated that "Unfortunately, the com.android.systemui (something regarding the task/notification bar) has stopped." I pressed okay but it kept popping up, and the home screen kept flashing. I could move around but only for 1sec before the message popped up. And when I cut the screen off it just froze. I did a factory reset, it didn't work; I reinstalled the Rom and other Roms, didn't work; I couldn't clear the system ui because the Roms didn't allow it. I've Youtubed and read everything, nothing. So I re-rooted my phone, didn't work. Now here is where the problem is. When I re-rooted my phone, it booted to AICP but the message still popped up. I tried to reinstall the Rom but it aborted the installation. I tried to install other Roms, same thing. Now the phone will only boot Recovery Mode and nothing else. I've been trying to flash the S3 4.3 Jelly Bean Stock Rom via Odin, but every website I go to ether doesn't have the file or it won't let me download the file. Now I did get one S3 Stock Rom, but I can't get the file to unzip . Does anyone have a solution to this weird problem... X( BECAUSE I CAN'T ANSWER THE PHONE IF MY GIRLFRIEND CALLS!!!!
DeathsSatellite said:
It's quite a long story,but I'll try to keep it short, yet detailed.
I rooted my Samsung Galaxy S3 (SGH-T999) about two weeks ago. I made sure to practice the rooting process and read up on the dos' and don't-s' when it comes to rooting and installing custom Roms. A week ago I installed a custom Rom from Aokp known as "AICP (Android Ice Cold Project)." Everything was going good till yesterday when I saw that I was having some memory issues. My internal memory was quite full and I realized and understood that when I wipe--factor reset--my phone, that there is still some data that is left over. Now before I installed AICP I made a backup of the S3 stock Rom. When I seen that the internal memory was getting full I formatted the internal-SD in recovery mode (forgetting that the S3 backup was in it). I decided to, after formatting the internal-SD, try some new Roms. I followed the flashing instructions carefully as always. I went back to AICP and put the phone down for a bit. When I came back to use it, it was frozen. So I restated the phone and then I began getting a message that stated that "Unfortunately, the com.android.systemui (something regarding the task/notification bar) has stopped." I pressed okay but it kept popping up, and the home screen kept flashing. I could move around but only for 1sec before the message popped up. And when I cut the screen off it just froze. I did a factory reset, it didn't work; I reinstalled the Rom and other Roms, didn't work; I couldn't clear the system ui because the Roms didn't allow it. I've Youtubed and read everything, nothing. So I re-rooted my phone, didn't work. Now here is where the problem is. When I re-rooted my phone, it booted to AICP but the message still popped up. I tried to reinstall the Rom but it aborted the installation. I tried to install other Roms, same thing. Now the phone will only boot Recovery Mode and nothing else. I've been trying to flash the S3 4.3 Jelly Bean Stock Rom via Odin, but every website I go to ether doesn't have the file or it won't let me download the file. Now I did get one S3 Stock Rom, but I can't get the file to unzip . Does anyone have a solution to this weird problem... X( BECAUSE I CAN'T ANSWER THE PHONE IF MY GIRLFRIEND CALLS!!!!
Click to expand...
Click to collapse
Wrong forum my friend.
DeathsSatellite said:
It's quite a long story,but I'll try to keep it short, yet detailed.
I rooted my Samsung Galaxy S3 (SGH-T999) about two weeks ago. I made sure to practice the rooting process and read up on the dos' and don't-s' when it comes to rooting and installing custom Roms. A week ago I installed a custom Rom from Aokp known as "AICP (Android Ice Cold Project)." Everything was going good till yesterday when I saw that I was having some memory issues. My internal memory was quite full and I realized and understood that when I wipe--factor reset--my phone, that there is still some data that is left over. Now before I installed AICP I made a backup of the S3 stock Rom. When I seen that the internal memory was getting full I formatted the internal-SD in recovery mode (forgetting that the S3 backup was in it). I decided to, after formatting the internal-SD, try some new Roms. I followed the flashing instructions carefully as always. I went back to AICP and put the phone down for a bit. When I came back to use it, it was frozen. So I restated the phone and then I began getting a message that stated that "Unfortunately, the com.android.systemui (something regarding the task/notification bar) has stopped." I pressed okay but it kept popping up, and the home screen kept flashing. I could move around but only for 1sec before the message popped up. And when I cut the screen off it just froze. I did a factory reset, it didn't work; I reinstalled the Rom and other Roms, didn't work; I couldn't clear the system ui because the Roms didn't allow it. I've Youtubed and read everything, nothing. So I re-rooted my phone, didn't work. Now here is where the problem is. When I re-rooted my phone, it booted to AICP but the message still popped up. I tried to reinstall the Rom but it aborted the installation. I tried to install other Roms, same thing. Now the phone will only boot Recovery Mode and nothing else. I've been trying to flash the S3 4.3 Jelly Bean Stock Rom via Odin, but every website I go to ether doesn't have the file or it won't let me download the file. Now I did get one S3 Stock Rom, but I can't get the file to unzip . Does anyone have a solution to this weird problem... X( BECAUSE I CAN'T ANSWER THE PHONE IF MY GIRLFRIEND CALLS!!!!
Click to expand...
Click to collapse
1. Flash this file: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2tmo/philz_touch_6.15.4-d2tmo.tar.md5 in odin3.09, uncheck autoreboot.
2. go to your recovery, select clean to install a new rom
3. download latest firmware (http://www.sammobile.com/firmwares/3/?download=26636) and install it in Odin3.09
4. reboot your phone.
See I figured that's what I needed to do. Just couldn't find a Rom to flash with Odin. I'll use this method right now.
Here's one of the problems I was having when it came to Odin and the Firmware. The website, "Sammobile," you sent me was one of the websites that I had the files I need, but the link you sent me to, which is the file I downloaded, didn't show up when I clicked AP/PDA in Odin and tried to mouth it. The .zip didn't show up and when I tried to unzip the T999UVUENC2 file, it stopped at
%63 and says:
! Read error in the file C:\Users\Mrs Woods\Downloads\T999UVUENC2_T999TMBENC2_TMB.zip
Data error (cyclic redundancy check).
! Not enough memory
What should I do?
Greetings everyone, wish you had some nice Christmas Days,
so here is my problem:
while updating to MM beta, I got stuck in a bootloop, so I tried the rollback and I got stuck again *sigh* at installing the B130 version of 5.0.2, after succesfully installing b300.
ATM the phone says "installing update... 5%" ...since 30 minutes.
Have you tried what I did?
http://forum.xda-developers.com/showthread.php?t=3278532
[Solved] Bricked? What can I do?
A bit old post but I have the same problem..
Trying to flash the official stock rom,and it's stuck at 5% for hours and nothing happens..
Valittaja said:
A bit old post but I have the same problem..
Trying to flash the official stock rom,and it's stuck at 5% for hours and nothing happens..
Click to expand...
Click to collapse
Which firmware number you tried??
You should know that the firmware version you chose to install matter , the device won't accept a previous ROM without rollback package as well as a too high one
So it has been a VERY, VERY, long time since I attempted to root a device. I admit, that I completely forgot most of what I knew from back in the day rooting like the Motorola OG Droid. Here's the deal. I tried rooting a USC XT1526 and I had no idea what I was doing. I followed the steps through and managed to install TWRP and SU. So I assume I got full root. Well The issue started after I got an UPDATE AVAILABLE message and tried to go through with the OTA Update. When it got to the point of installing the OTA Update, my device turned off like normal but instead of updating, it booted into TWRP recovery. It didn't update at all and when I booted my phone normally, it kept trying to update so my phone turn off (loop) every time it tried to install the update. I did a factory reset and it stopped rebooting. I later tried to flash back to fully stock but I believe I might have downloaded the wrong file because I now have a device with no WiFi. Can someone please help me.