I have been trying to update to the ACS custom recovery 1.0.0.4 but every time i try this in the ACS updater application it starts to download zImage, then gets to 99% and reboots my phonne. It doesnt go into recovery from there and the same version of CWM i was using is still the recovery system.
This has happened across 3 different roms i was trying (acs srf 1.2, and ERA rom, and bamboozle 1.1)
I would like to know iof this is a known issue, how i can get this work work, and if there is a flashable zip that i can use to install the custom recovery myself.
Interesting. I have been testing the recovery for like 2 months. I just thought it was labeled wrong because I am on 1.0.0.3. Let me try to get some info
Sent from my SPH-D700 using xda premium
Any info? It just downloads "zImage" to my sd card.
Sent from my SPH-D700 using xda premium
ac16313 said:
Any info? It just downloads "zImage" to my sd card.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
The person I asked didn't get back to me. Let me try again. It seems like most of the team hasn't been on here lately so I will hit some people up on G-Talk
Sent from my SPH-D700 using xda premium
JohnCorleone said:
The person I asked didn't get back to me. Let me try again. It seems like most of the team hasn't been on here lately so I will hit some people up on G-Talk
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Cool stuff thanks!
It appears I am having the same issue. Gets to 99%, reboots, and I still have cwm 3.1.0.1 on 3 finger and through acs app.
jeffro18 said:
It appears I am having the same issue. Gets to 99%, reboots, and I still have cwm 3.1.0.1 on 3 finger and through acs app.
Click to expand...
Click to collapse
Same here gets to 99 % reboots & nothing what's up with a flashable
Zip?
Sent from my SPH-D700 using XDA App
Hey guys, I'm looking into this issue now. Not sure what caused it to just stop working.... I'll get back to everyone when I have an answer.
As for the zImage file - that's the recovery. It downloads into to your sdcard, then uses bmlwrite to write it, and then reboots.
parabola949 said:
Hey guys, I'm looking into this issue now. Not sure what caused it to just stop working.... I'll get back to everyone when I have an answer.
As for the zImage file - that's the recovery. It downloads into to your sdcard, then uses bmlwrite to write it, and then reboots.
Click to expand...
Click to collapse
Thanks for the response. This recovery is the only one that has never failed on me so I hope people get to take advantage of it ASAP. I have been testing it for 6+ weeks or so and its the first thing I put back on my phone after rooting.
Sent from my SPH-D700 using xda premium
Fixed!
JohnCorleone said:
Thanks for the response. This recovery is the only one that has never failed on me so I hope people get to take advantage of it ASAP. I have been testing it for 6+ weeks or so and its the first thing I put back on my phone after rooting.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Alright, great news everyone - got it fixed. Just uploaded to the market, give it time to reach you. Version is:
(Free) 1.5.0.3
(Donate) 1.5.1.3
I apologize for the issues... not sure how it went so wrong when it worked in testing.... I tested both versions though, all is good.
By the way -
I was able to do the following:
ODIN to stock
Root with One-Click
Here's the best part - even if your one-click does NOT install a custom recovery - you can still install it from the app. After I did ODIN / root, did not have to touch computer at all.... Installed recovery, then kernel, then rom, all from app.
Once again, I apologize for the issues.
parabola949 said:
Hey guys, I'm looking into this issue now. Not sure what caused it to just stop working.... I'll get back to everyone when I have an answer.
As for the zImage file - that's the recovery. It downloads into to your sdcard, then uses bmlwrite to write it, and then reboots.
Click to expand...
Click to collapse
Thanks for the heads up, and information!
So does this have any compatability issues?
Sent from my SPH-D700 using xda premium
ac16313 said:
Thanks for the heads up, and information!
So does this have any compatability issues?
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
After it installs, make a new nandroid backup. I found huge errors when restoring a 3.1.0.1 backup under the new recovery.
Testing now. Uhhh, I can't seem to 3 finger into recovery at all. And now it won't boot at all. Time for some special odin time....
Expect a how to video as well
I have 1.5.03 and still out failed
Sent from my SPH-D700 using XDA App
mottipython said:
I have 1.5.03 and still out failed
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Same here.
Sent from my SPH-D700 using xda premium
parabola949 said:
Alright, great news everyone - got it fixed. Just uploaded to the market, give it time to reach you. Version is:
(Free) 1.5.0.3
(Donate) 1.5.1.3
I apologize for the issues... not sure how it went so wrong when it worked in testing.... I tested both versions though, all is good.
By the way -
I was able to do the following:
ODIN to stock
Root with One-Click
Here's the best part - even if your one-click does NOT install a custom recovery - you can still install it from the app. After I did ODIN / root, did not have to touch computer at all.... Installed recovery, then kernel, then rom, all from app.
Once again, I apologize for the issues.
Click to expand...
Click to collapse
I just saw this thread, but I have ACS Updater (Donate version 1.1) - I only use it for backup and restore and it works perfect - I don't understand this "stops at 99%" thing, but now you guys got me scared to update to the newest version.
One thing that is strange, I had to look up acs updater in the Market Place before I found you could update it - the Market Place never gave me a notification that there was an update until I saw this thread
mouseglider said:
I just saw this thread, but I have ACS Updater (Donate version 1.1) - I only use it for backup and restore and it works perfect - I don't understand this "stops at 99%" thing, but now you guys got me scared to update to the newest version.
One thing that is strange, I had to look up acs updater in the Market Place before I found you could update it - the Market Place never gave me a notification that there was an update until I saw this thread
Click to expand...
Click to collapse
We are talking about trying to install the acs recovery inside the acs updater app.
Sent from my SPH-D700 using xda premium
just to reiterate, this issue is not resolved...
The Root said:
After it installs, make a new nandroid backup. I found huge errors when restoring a 3.1.0.1 backup under the new recovery.
Testing now. Uhhh, I can't seem to 3 finger into recovery at all. And now it won't boot at all. Time for some special odin time....
Click to expand...
Click to collapse
I didn't have this problem I installed ACS Recovery & restored a backup I made earlier with cwm a week ago & everything great! I like the blue in the recovery a little change from the purple which was also nice thanks ACS Team!! Oh my roommate has the evo I told him to instal this but he's scared that it will brick his phone I told him it won't just to make sure so he can see this is it ok for him to have this acs recovery? Thanks for any help I will give you a flower lol!hahaha
Super SRF 1.2/Genocide 2.0 OC 1.4GHZ/Honeycomb Fusion v 1.1
This issue has yet to be resolved. The acsupdater still reboots my phone at 99% . Still no flashble zip yet either.
Sent from my SPH-D700 using XDA App
Related
Stock EG30Plus Kernel for Epic Touch 4g compiled from source, properly.
Proper initramfs
ClockworkMod 5 (Compiled by bubby323)
Various Virtual Machine, Kernel and Network Tweaks I've been using in my plus kernels for quite some time...
Bootanimation support, either bootanimation.zip or sanim.zip
init.d support
Does NOT install Root
Does NOT install Busybox
Odin the tar.md5 file
Immediately update profile
Made this one for cnz, calkulin, and crawrj
http://www.forums.acsyndicate.net/s...-Plus-Tweaks-(No-root-and-does-not-install-BB)
Source:
https://github.com/chris41g/EG30Plus
Thanks to qbking77 for the how to video:
http://www.youtube.com/watch?v=kExN-Y2pfxA
Thanks to:
bubby323
Drockstar
Johncorleone
pyrostic
rjmjr69
nubecoder
thefredelement
cnz
calkulin
crawrj
Not sure why but the .tar file is followed by a .md5 extention, so I just removed it and it became a .tar, just for others to know, thanks
the md5 extension is so you know it hasnt been messed with, and so you know the download is not corrupt...
odin flashes md5s and checks the downloads...
What would be the benefit of flashing this versus your other similar kernel? Sorry if this is a stupid question....
Thank you so much. This is perfect. Do have a question. Does this have a new version of cwm or the same one from yesterday? I ask cause the back soft button wasn't working and the storage mounts were reversed. Just checking to see if that has been fixed.
Sent from my SPH-D710 using xda premium
chris41g said:
the md5 extension is so you know it hasnt been messed with, and so you know the download is not corrupt...
odin flashes md5s and checks the downloads...
Click to expand...
Click to collapse
Ok, good to know, thanks for the reply and the lesson
Beejis said:
What would be the benefit of flashing this versus your other similar kernel? Sorry if this is a stupid question....
Click to expand...
Click to collapse
It is the same just without root and busybox. He made it for those of us that prefer having root controlled at the system level versus the kernel. You don't lose anything either way. If you use this you have to make sure you are running an already rooted rom. There is less conflict by doing this since most, if not all, roms are already rooted.
Sent from my SPH-D710 using xda premium
crawrj said:
It is the same just without root and busybox. He made it for those of us that prefer having root controlled at the system level versus the kernel. You don't lose anything either way. If you use this you have to make sure you are running an already rooted rom. There is less conflict by doing this since most, if not all, roms are already rooted.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Once again thanks for you help. One last stupid question before I retire from stupidity, but how do I know which way I am rooted? I thought the only way to root was FROM the kernel. I ask because I'm specifically on midnight rom v2 and have no clue which way I'm rooted.
Is there any way someone could upload a mirror to a different site? I'm wanting to flash this but I'm at work and my company is blocking the site that the link is for. If you can that would be awesome if not, no big deal. I'll try and get it when I get home.
Edit: Nevermind. Managed to get it from my phone.
I can up it to megaupload if that helps Tiffany.
Link deleted.
crawrj said:
It is the same just without root and busybox. He made it for those of us that prefer having root controlled at the system level versus the kernel. You don't lose anything either way. If you use this you have to make sure you are running an already rooted rom. There is less conflict by doing this since most, if not all, roms are already rooted.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I already rooted via odin with your Deodex method, if I flash this, I'll have CWM and still keep root...correct? My phone has been running great since using your method.
Sent from my GalaxyS2 Epic 4G Touch using XDA premium
rickyq12 said:
I already rooted via odin with your Deodex method, if I flash this, I'll have CWM and still keep root...correct? My phone has been running great since using your method.
Sent from my GalaxyS2 Epic 4G Touch using XDA premium
Click to expand...
Click to collapse
I just flashed this and I have CWM and I kept root so you should be good.
Sent from my SPH-D710 using xda premium
Tiffany84 said:
I just flashed this and I have CWM and I kept root so you should be good.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
+1 10chars
rickyq12 said:
I already rooted via odin with your Deodex method, if I flash this, I'll have CWM and still keep root...correct? My phone has been running great since using your method.
Sent from my GalaxyS2 Epic 4G Touch using XDA premium
Click to expand...
Click to collapse
Yes you will keep root cause the rom is rooted. As long ad the rom is rooted the kernel doesn't need to. be.
Sent From My Evo Killer!!!
Tiffany84 said:
I just flashed this and I have CWM and I kept root so you should be good.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Cool, thanks for letting me know. I take it as you were rooted prior to this method. I'll flash once I get home from work.
Sent from my GalaxyTab 10.1 using XDA premium
rickyq12 said:
Cool, thanks for letting me know. I take it as you were rooted prior to this method. I'll flash once I get home from work.
Sent from my GalaxyTab 10.1 using XDA premium
Click to expand...
Click to collapse
Your welcome. And yes, I was rooted prior to this.
Sent from my SPH-D710 using xda premium
Just curious, if someone has flashed chris' previous kernel, what benefit is there supposed to be? Is it not the same stock kernel with some tweaks? Especially if you're concerned with losing root. Not singling anyone out, just curious as to the rationale.
.....
Thanks to qbking77 for the how to video:
http://www.youtube.com/watch?v=kExN-Y2pfxA
Vegasden said:
Just curious, if someone has flashed chris' previous kernel, what benefit is there supposed to be? Is it not the same stock kernel with some tweaks? Especially if you're concerned with losing root. Not singling anyone out, just curious as to the rationale.
.....
Click to expand...
Click to collapse
Because kernels that have forced copying of root & busybox cause issues when you start using complete custom ROMs because they overwrite files that are already included. Plus if your including a custom recovery, what the point of including root, etc when the user can now flash what they want?
Also, Chris, the recovery you have included in this won't mount the internal storage or even make a backup to it or recover, it only wants to use the external sd card and since I don't use one because of the delay it causes coming from sleep, I can't do anything except test flash stuff
I flashed this around noon and once my phone rebooted, I updated my 'profile' under 'about phone'. Everything seemed fine, an hour later...I had a LOS, rebooted and got it back, an hour later, same thing...LOS. Rebooted and I updated the profile again, it's fine for now.
Do we have to update profile every time we do a reboot??
Didn't have any issues when in stock.
Epic Touch Blog: Temporary Stock E4GT from emmc
Utility for CM9 Epic Touch
This is a temporary ROM that boots Samsung's Gingerbread EL29 firmware entirely from emmc without making any changes to the ROM currently installed on your phone. When you reboot, you return to recovery where you can re-flash the ROM to return to CM9. This temporary ROM is useful for several purposes.
Update Profile.
Update PRL.
Sprint Activation.
Dial codes and diagnostic mode.
This should be helpful to users of any AOSP-based ROM including CM9, AOKP, etc.
Thanks to noobnl and mkasick for making this possible!
Really nice thanks a lot.
Awesome can't wait to test it out
Sent from my SPH-D710 using Tapatalk
. This will come in hand
Sent from my SPH-D710 using XDA Premium App
wilderckw said:
. This will come in hand
Sent from my SPH-D710 using XDA Premium App
Click to expand...
Click to collapse
Its a great tool and easy to use. Was testing earlier today.
Sent from my SPH-D710 using Tapatalk
Would this work to flash .zip updates (such as kobridge) or updated ROMs (such as alpha5)?
This definitely will come in handy, can I suggest seeing if you can get a video made of how it works. I can honestly say It seems to help out quite a bit in this forum for a lot of people and does cut down on the crazy questions.
Great job though!
bobjase said:
Would this work to flash .zip updates (such as kobridge) or updated ROMs (such as alpha5)?
Click to expand...
Click to collapse
You can use the directbootCWM file to update CM9 yes. Not sure about using it for Kobridge tweaks.
playya said:
This definitely will come in handy, can I suggest seeing if you can get a video made of how it works. I can honestly say It seems to help out quite a bit in this forum for a lot of people and does cut down on the crazy questions.
Great job though!
Click to expand...
Click to collapse
Maybe qbking can make one for those who need it.
Sent from my SPH-D710 using Tapatalk
I'm sorry but what does this do?
Sent from my SPH-D710 using XDA
m0j09987 said:
I'm sorry but what does this do?
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Its for AOSP roms. You currently can't update PRL/Profile, activate your device, or use dialer codes on them so this temporarily allows you to boot stock el29 off the SD card without changing your current rom. You can do what i said from there. Saves you time from doing backups, restoring, etc.
Sent from my SPH-D710 using Tapatalk
I'm hoping that someone can help me out as I am unable to boot into the temporary ROM. Here are the steps I followed:
1. I have everything extracted to emmc as directed.
2. I flashed directboot CWM utilizing mobile odin which correctly booted me into CWM version 5.0.2.7
3. I flashed boot_EL29.zip at location /emmc/multiboot/EL29 and received the following messages that appear to be correct.
Finding Update Package...Opening Update Package...Installing Update...Boot /emmc/multiboot/EL29/zImageCreate mount symlink.Remount partitions read-only.(Re)mount /emmc read-only.Unpack kexec.Load zImage and initramfs.Sync.Reboot into zImage.Install from sdcard complete.4. At this point I expected the phone to reboot into the temporary rom; however, it just shows the standard recovery menu. No reboot occured.
5. Because no automatic reboot occured, I selected "reboot system now" from CWM. Unfortunately this just brings me back into directboot CWM.
Thanks in advance for any help provided.
I am having the same problem I thought it could have been the downloading or unpacking so I downloaded it again and unpacked it and still have the same problem.
smmlee said:
I'm hoping that someone can help me out as I am unable to boot into the temporary ROM. Here are the steps I followed:
1. I have everything extracted to emmc as directed.
2. I flashed directboot CWM utilizing mobile odin which correctly booted me into CWM version 5.0.2.7
3. I flashed boot_EL29.zip at location /emmc/multiboot/EL29 and received the following messages that appear to be correct.
Finding Update Package...Opening Update Package...Installing Update...Boot /emmc/multiboot/EL29/zImageCreate mount symlink.Remount partitions read-only.(Re)mount /emmc read-only.Unpack kexec.Load zImage and initramfs.Sync.Reboot into zImage.Install from sdcard complete.4. At this point I expected the phone to reboot into the temporary rom; however, it just shows the standard recovery menu. No reboot occured.
5. Because no automatic reboot occured, I selected "reboot system now" from CWM. Unfortunately this just brings me back into directboot CWM.
Thanks in advance for any help provided.
Click to expand...
Click to collapse
I what having this same issue. There is a different version of direct boot, v3 that you have to use for this.
Sent from my SPH-D710 using Tapatalk 2
All I see is v1 up on the e4gtcm site. Where did you obtain v3 from?
Worked with V3 direct boot Thanks
---------- Post added at 03:35 PM ---------- Previous post was at 03:34 PM ----------
just click on the direct boot link and it will bring you to the V3
smmlee said:
All I see is v1 up on the e4gtcm site. Where did you obtain v3 from?
Click to expand...
Click to collapse
Nevermind. I found the v3 update. Thanks all!
Anymore questions don't be afraid to ask.
Sent from my SPH-D710 using Tapatalk
This sounds pretty cool and I would like to test it... what I don't understand is when I'm done with the temp rom, how do I get back to AOKP? Do I need to reflash the whole AOKP rom? Just the kernel?
epdp14 said:
This sounds pretty cool and I would like to test it... what I don't understand is when I'm done with the temp rom, how do I get back to AOKP? Do I need to reflash the whole AOKP rom? Just the kernel?
Click to expand...
Click to collapse
When done updating prl/profile, etc. Just reboot your phone and it will take you back to cwm recovery. From there you can either just reflash the rom or just a compatible kernel so it boots.
Sent from my SPH-D710 using Tapatalk
excellent. this could also help people do the gb GPS fix.. sweet man.
So I flashed miui & flashed Chris41g's CWM6 RC13 kernel, both through EL26 CWM. when it booted I kept getting force closes. It kept saying "android.com.process failed" or something like that. Booted back into cwm n reflashed. Same thing happened. So I tried to get back to recovery & it got stuck at the Galaxy S II screen. It still boots to download mode though. Is Odin my only way out of this? Will it even work?
Sent from my DROIDX using xda app-developers app
Honestly if it was me I'd just take a L and one click back to start fresh if that happened
- Sent From My Blu Kuban Themed Tapatalk Like A Boss
Which version of MIUI? If you're flashing Captain Morgans latest build, I believe you have to flash to the build before, mobile Odin/Odin to el26, and then flash the newest build + Chris's Kernel without any wiping. Info is in the OP.
Sent from my Samsung Epic 4G Touch using Tapatalk
MasterZen88 said:
I can confirm this too... Also If anyone is looking to flash this rom please follow these steps. I have repeated the process at least 10 times:
1. Odin EL26 repacked CWM 5
2. Wipe using Calkulin's_FORMAT_ALL.
3. Flash MIUI 2.6.15
4. After flashing let it reboot into MIUI 2.6.15 ** THIS IS VERY IMPORTANT**
5. Then Odin Chris41G AOSP CWM5 or EL26
6. And Finally flash MIUI 2.7.20 v4
Click to expand...
Click to collapse
..
nitro_c4 said:
Originally Posted by MasterZen88
I can confirm this too... Also If anyone is looking to flash this rom please follow these steps. I have repeated the process at least 10 times:
1. Odin EL26 repacked CWM 5
2. Wipe using Calkulin's_FORMAT_ALL.
3. Flash MIUI 2.6.15
4. After flashing let it reboot into MIUI 2.6.15 ** THIS IS VERY IMPORTANT**
5. Then Odin Chris41G AOSP CWM5 or EL26
6. And Finally flash MIUI 2.7.20 v4
Click to expand...
Click to collapse
Yeah I had to do the same thing. So @ChewDZ, basically you are going to have to flash that old one first, and then the new one on top of it as if you were upgrading, otherwise everyone gets that error. And make sure to use the right kernels mentioned above! (Also, I was tempted to just flash the old one and not upgrade, but trust me, the upgraded one has much better stability and battery life.) I have been running it since it was out with almost no issues.
Wow. I saw that no where in the op. Now I'm stuck using my DX until I reach a computer
Sent from my DROIDX using xda app-developers app
Chew DZ said:
Wow. I saw that no where in the op. Now I'm stuck using my DX until I reach a computer
Sent from my DROIDX using xda app-developers app
Click to expand...
Click to collapse
Yeah =/ Unfortunately the OP didn't mention anything about it, so you have to scroll through pages and pages to find it...
2momo123 said:
Yeah =/ Unfortunately the OP didn't mention anything about it, so you have to scroll through pages and pages to find it...
Click to expand...
Click to collapse
It's underlined in the OP
Sent from my Samsung Epic 4G Touch using Tapatalk
No. It isn't. It wasn't in the flashing instructions or anything. That's what pisses me off.
Sent from my DROIDX using xda app-developers app
It's right there and has been for over 2 weeks. Quoted below
Below step 4 - All else failed then try the link at the bottom, I too can confirm this is a most excellent way of getting this to work, thanks MasterZen88.
In bold & underlined at the bottom - If you are having difficulty with this version installation check this post for alternatives methods than stated above.
Jocelyn said:
It's right there and has been for over 2 weeks. Quoted below
Below step 4 - All else failed then try the link at the bottom, I too can confirm this is a most excellent way of getting this to work, thanks MasterZen88.
In bold & underlined at the bottom - If you are having difficulty with this version installation check this post for alternatives methods than stated above.
Click to expand...
Click to collapse
Ahh my bad. I will admit I havn't checked since I flashed it. Been maybe 3 weeks now. Although, instead of saying if you are having issues to check the post, I do think it should just include it in the instructions.
Jocelyn said:
It's right there and has been for over 2 weeks. Quoted below
Below step 4 - All else failed then try the link at the bottom, I too can confirm this is a most excellent way of getting this to work, thanks MasterZen88.
In bold & underlined at the bottom - If you are having difficulty with this version installation check this post for alternatives methods than stated above.
Click to expand...
Click to collapse
What Nitro posted is what isn't in the OP. Why would I immediately go for an alternative installation? My "difficulty installing" soft bricked me. I followed the instructions for flashing & bricked. There's nothing that could've prevented that.
Sent from my DROIDX using xda app-developers app
Chew DZ said:
What Nitro posted is what isn't in the OP. Why would I immediately go for an alternative installation? My "difficulty installing" soft bricked me. I followed the instructions for flashing & bricked. There's nothing that could've prevented that.
Sent from my DROIDX using xda app-developers app
Click to expand...
Click to collapse
I completely agree. It should just be the standard installation instructions, as no one has been successful without doing it this way. It shouldn't be "So now that you tried normally and it screwed up your phone, try it this way." XD They should just tell us to do it that way from the start.
Anyway, have you gotten it working yet?
Thank you, exactly. And yes I just had go Odin back to GB. Now all is well
Sent from my SPH-D710 using xda premium
go to youtube, qbking77 channel, look for his how to unroot video, then look for his how to root video again. maybe now sub and use his tutorials
I am trying to upgrade my Virgin ROM to the 9.12 build but get a fail upon trying to flash it. The background.... I'm using TWRP recovery and have tried the chainfire root method. Here are the results:
As you can see you can see some conflicting information... all shots were taken in sequence. I'm thinking the fail in twrp is coming from the system not having root but the info is telling me otherwise....
Bump... Anybody???
Sent from my GT-I9505G using xda app-developers app
th3h0ff said:
Bump... Anybody???
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
Do you have the latest SuperSU version?
I'm a little lost at what you are saying.
You flashed a rom, and it said fail, and you think it has to do with Root?
If you have TWRP installed it doesn't matter if you are rooted or not. It's going to over right the system partition regardless if you have root or not.
So it's either a bad download or bad transfer for it to fail.
Sent from my SGH-M919 using Tapatalk 4
I do have the latest SU version by chain fire. And maybe I'm doing something wrong the because I am running the virgin gpe ROM now and that flashed in twrp with no issues. Now when I go to install (after wiping) and select the 9.12 update that I downloaded it hangs on trying to open the zip and fails... I haven't changed any twrp settings but in the write options of twrp what boxes should be checked because system is not by default... Thanks for the replies!
Sent from my GT-I9505G using xda app-developers app
I previously only used cwm so I'm not sure if I should just try that or what... And I've checked the download and md5 for verification
Sent from my GT-I9505G using xda app-developers app
th3h0ff said:
I previously only used cwm so I'm not sure if I should just try that or what... And I've checked the download and md5 for verification
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
You can give CWM a try, I've been using it for a while without any issues. Out of curiosity what version if TWRP you are using? I think most people recommend TWRP 2.5.0.2. I'm using the latest version of CWM.
Sent from my GT-I9505G using xda app-developers app
If all else fails, just start from scratch, get stock UVUAMDL tar, flash it with Odin, make sure to do a factory wipe after you flash it, sometimes bootloops occur if you don't. You don't even have to go past the first screen where you pick the language. Just shut it down from there and boot into download mode and root with Chainfire with Odin, then shut down and boot up again into download mode again and flash custom recovery tar of ur choice with Odin. Then download whatever custom rom zip and install it via custom recovery.
norml said:
If all else fails, just start from scratch, get stock UVUAMDL tar, flash it with Odin, make sure to do a factory wipe after you flash it, sometimes bootloops occur if you don't. You don't even have to go past the first screen where you pick the language. Just shut it down from there and boot into download mode and root with Chainfire with Odin, then shut down and boot up again into download mode again and flash custom recovery tar of ur choice with Odin. Then download whatever custom rom zip and install it via custom recovery.
Click to expand...
Click to collapse
Thanks again to everyone... not going to have time to mess with it tonight but I'll update tomorrow. Thanks again
th3h0ff said:
Thanks again to everyone... not going to have time to mess with it tonight but I'll update tomorrow. Thanks again
Click to expand...
Click to collapse
heyyy saw your reply in my thread.
just as @byron1985 suggested there, it sounds like you got a bad download. the flashing scripts are essentially exactly the same from previous version. the flashing process has absolutely zero to do with SuperSU.
edit: re-read. so you've verified the download. if you had success with CWM previously, i would go back to that. i do not use TWRP.
mrvirginia said:
heyyy saw your reply in my thread.
just as @byron1985 suggested there, it sounds like you got a bad download. the flashing scripts are essentially exactly the same from previous version. the flashing process has absolutely zero to do with SuperSU.
edit: re-read. so you've verified the download. if you had success with CWM previously, i would go back to that. i do not use TWRP.
Click to expand...
Click to collapse
Im going to give the twrp 2.5.2 a try as it seems most of my troubles keep happening on the 2.6.3 build. Hopefully that works either way its back to CWM for me as well. Thanks again for taking the time to help out and again sorry about hijacking the thread for a page... Your ROM is absolutely perfect so I appreciate the efforts and time!,
Andrew
SOLVED... tried 2.5 version of TWRP and all went well... odd but apparently my device doesnt like 2.6 versions of TWRP! Thanks to everyone who helped me out and gave me suggestions and thank you to the dev for taking some of his time to assist! It was a great help to me!
th3h0ff said:
SOLVED... tried 2.5 version of TWRP and all went well... odd but apparently my device doesnt like 2.6 versions of TWRP! Thanks to everyone who helped me out and gave me suggestions and thank you to the dev for taking some of his time to assist! It was a great help to me!
Click to expand...
Click to collapse
Good to know you are out of trouble
Sent from my Nexus 10 using xda app-developers app
See you shoulda said you were running 2.6.3 lol
word of advice (and to all who run twrp)
DO NOT RUN ANYTHING GREATER THAN 2.5.2!!!!!!!!!!!!!!
Hello and thanks to all those before me who give great advice on troubleshooting....
Here's my situation:
Phone is Rooted.
I downloaded an app a few days ago from the Play Store, so I could move my app installs to the sdcard. When i installed the app it said that there was something wrong " can't remember the exact message " and it needed to fix it. My dumbass allowed it to fix it and here is where my problems began.
Right after that I began receiving a message "Shell has been granted Super User", phone began to run sluggish and the Play Store App would always say it was crashing.
So I figured, screw it I would format and start w/a new ROM anyway.... I did not have any sort of backup (of course dumbass)
However I loaded up the latest version of Odin 3.09 and just incase I installed the root.zip again incase that was destroyed. Then I installed the latest version of OUDHS CWM-Based Recovery 1.0.3.3 ( Previously I had TWRP )
I downloaded a few different roms so I could see what I wanted...However...here's where things get interesting, and I did do some research on it but couldn't find a way to resolve the 1st problem.
When I first started to install a ROM, don't remember which one I was getting a signature verification failed....I had read that it could be 2 things, one the MD5 was bad, I verified that, so that wasn't the issue. Then I came across that it may have been a ROM that my device(Samsung) somehow knew wasn't approved, therefore prevented it from being installed....OK fine...
Next I found a ROM that was going to work via installing...So i picked the CM10.2 and wiped/format/davik/cache...etc... Installation took a few mins...Then when I rebooted, it's been on the Cyangenmod screen for 45 mins +....
Is there anyway I can do some verification that something further isn't interfering w/my installs?
Thanks in advance and any guidance is GREATLY appreciated...
Regards
Erik
Odin to stock and try that, always the best choice
Sent from my SGH-M919 using xda app-developers app
aamir123 said:
Odin to stock and try that, always the best choice
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Actually I tried that and I used this one from stockroms.net TMB-M919UVUAMDL-1366964131.zip
the verification failed immediately, however, when I checked it w/the MD5 hash on my computer it checks out...That's where I'm wondering if there is something else going on...
Or are you talking about something else regarding stock? If so could you clarify...Thanks
Use sam mobile.com
And flash the mdl fw from there. Also you may have to unzip the original file to get a tar file
Sent from my SGH-M919 using xda app-developers app
aamir123 said:
Use sam mobile.com
And flash the mdl fw from there. Also you may have to unzip the original file to get a tar file
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Just wanted to say thank you for your help. Both the flashing the recovery back to default and the default ROM worked. Now in the future no more clicking yes when I don't have a backup
Have a great weekend!!
oregongreen said:
Just wanted to say thank you for your help. Both the flashing the recovery back to default and the default ROM worked. Now in the future no more clicking yes when I don't have a backup
Have a great weekend!!
Click to expand...
Click to collapse
glad it worked out for you, I know it can be scary to think you screwed up your phone.
Glad you solved it, ALWAYS MAKE A BACKUP
Sent from my customizable brickable device
mrhughy said:
Glad you solved it, ALWAYS MAKE A BACKUP
Sent from my customizable brickable device
Click to expand...
Click to collapse
This can nvr be said enough.