Related
Anyone download P3Droid's EP1Q leak and Odin and then boot loop to Samsung screen. I can't get it to work?
Same thing happened to me. I'm going to ODIN back to factory and then try and see if that works. What were you coming from? I was coming from Gummy ee4
I am coming from Gummy GBE 1.8 EP1F/H.
I am going to try and re-odin Gummy 1.8.
Let me know if that works. I was thinking about going to that anyways. Thanks
Same here, odin'd from gummy froyo.
Bootloop,
flashed EP1H
then
Flashed the EP1Q again
Bootloop
Going back to Gummy 1.8 GBE fixed it ok for me....have to wait for Kejar to get his hands on it and figure out what P3Droid did.....
Wipe your DATA...
I did wipe after I odined because it booted me into recovery but typically you don't need to wipe after a leak Odin because it formats everything? Can anyone confirm they are up and running on the P3Special Odin file?
I have been looking for it but can't find it.
It's apparently only available on the TBH app at the moment. I don't use Paypal so I can't say with any authority.
Yeah you can only get it with his app.
Sent from my SCH-I510 using Tapatalk
What a load of crap...charging for leaks indirectly. Release the damn ROM, TBH! Shame.
Only p3 would release a leak that doesnt even boot. Such a joke.
So is it still not booting?
imnuts figured out some boot files weren't included and when put into the package make it boot correctly.. check out his twitter
blazing through on my VZ Droid Charge 4G
Success
I've tried all of the following and was finally able to get it to boot:
Tried: odin(norepart,nopit,noautoreboot) NON SPECIAL from existing chargeGBE-1.8
Result: booted to cwm-4.0.0.4, factory reset, splash ep1q spash, then splash loop
Tried: odin(repart,pit,noautoreboot) revert to ed1, then odin(noautoreboot) to ep1q NON SPECIAL
Result: FAIL, could not mount stl11
Tried: odin(repart,pit,noautoreboot) revert to ed1 stock, odin(noautoreboot) to ep1h, odin(noautoreboot) to ep1q NON SPECIAL
Result: booted into into 3e recovery, selected reboot, am now @ stock EP1Q.
update:
flashed latest cwm recovery via odin, and proceeded to manuall convert rfs to ext4 via (tar -cvpf /sdcard/ep1q_{system,dbdata,data,cache}, etc....), am now on ext4 w/ EP1Q.
I just posted a seperate thread noting that I've tried different ways to get my phone back up. I can not either. Subscribing looking for a fix.
I only downloaded the debloated version, not the full version for EP1Q, unable to try that fix at the moment.
ive tried it. bootloops. odin back to ee4. tried it. bootloops. odin to leak EP1F. tried it. now CWR doesnt load up and theres a whole ish bout sd card not found. and yes ive data wipe multiple times. did it all for giggles and kicks to cover all bases just so you know. anyhow. back to stable ee4 for me.
Does the EP1Q leak have changes to the radio as well?
when did u reboot?
c0ns0le said:
I've tried all of the following and was finally able to get it to boot:
Tried: odin(norepart,nopit,noautoreboot) NON SPECIAL from existing chargeGBE-1.8
Result: booted to cwm-4.0.0.4, factory reset, splash ep1q spash, then splash loop
Tried: odin(repart,pit,noautoreboot) revert to ed1, then odin(noautoreboot) to ep1q NON SPECIAL
Result: FAIL, could not mount stl11
Tried: odin(repart,pit,noautoreboot) revert to ed1 stock, odin(noautoreboot) to ep1h, odin(noautoreboot) to ep1q NON SPECIAL
Result: booted into into 3e recovery, selected reboot, am now @ stock EP1Q.
update:
flashed latest cwm recovery via odin, and proceeded to manuall convert rfs to ext4 via (tar -cvpf /sdcard/ep1q_{system,dbdata,data,cache}, etc....), am now on ext4 w/ EP1Q.
Click to expand...
Click to collapse
Hi did you just flash one after other without rebooting in between?
First, I'm already pretty certain I'm going to have to reflash EP3HA, but I have a question I'm hoping to get answered.
So last night I flashed TBH's EP3HA. I was previously on a stock, rooted EE4 with the PB&J lagfix kernel. I didn't even think about the lagfix because I figured since I was going to Odin EP3HA I didn't need to turn the lagfix off. The phone has been working fine for 24 hours but today I restarted it and now I'm in a boot loop.
Could the Voodoo lagfix be the reason I'm boot looping? I totally forgot to use TB too so I'm going to have to re-download everything I don't want to have to do this over and over again.
Thanks.
Yes your issue is going to be that you were using a froyo kernel with a gingerbread ROM. If I was you I would flash the charge Pit file and stock ee4 ROM then boot up and flash your gingerbread rom and or kernel.. You can find those files on the thread how to fix your phone.. You may be able to just flash back to the ee4 ROM leaving your Kernel in tact as well
Sent from my charge 1012 tw_infinity_tsm_beta 5
Thanks for the quick reply. I already had the ED1 downloaded. So I just reflashed that with the PIT file. So now I'll reflash EP3HA and I'm thinking that will fix it.
By the way. I actually wasn't using the PBJ kernel with EP3HA. I just used the kernel that came with it.
Yep you got it... Make sure if you want the lagfix back to flash an updated kernel after getting your ep3h loaded. I'm running imo 3.1.0 with good results
Sent from my charge using Infinity beta 5
vegasjones said:
Thanks for the quick reply. I already had the ED1 downloaded. So I just reflashed that with the PIT file. So now I'll reflash EP3HA and I'm thinking that will fix it.
By the way. I actually wasn't using the PBJ kernel with EP3HA. I just used the kernel that came with it.
Click to expand...
Click to collapse
You do know there an EE4 stock right?
Sent from my Droid Charge running Infinity Beta
How can I boot back to pure stock KD1? I am on KJ6 right now? Could you hit me up with some links too? Thanks
Johnmonkey0 said:
How can I boot back to pure stock KD1? I am on KJ6 right now? Could you hit me up with some links too? Thanks
Click to expand...
Click to collapse
Get your ROM here
T959VKD1 fully flashable through CWM
For those of you who are not sure if they have CWM of if you have Gingerbread Boot loaders installed follow this guide
GB Ext4 Starter Pack
Or use ODIN and install the ROM
T959VKD1 DeOdexed
If you have any boot loop or boot up problems just go through these steps again and try the ODIN again afterwards.
GB Ext4 Starter Pack
*** Read each step carefully! Do not skip anything (unless your going to use Kies to update to a stock official Rom)!! ***
*** If your going to use kies to go to a stock update then you might want to change step 10) to this
Step 10) Go into the voodoo menu > Disable lagfix and /system lagfix off
You should be able to update using Kies after this. You will lose root capabilities but if you’re looking to go back to stock then that's a given.
Dmx is partially correct. If you want pure, you'll have to odin Kc1 stock rom, which has froyo bootloaders. I think some searching on this forum will grant you a link. I know I've seen it somewhere.
Sent from my rockin' Galaxy S 4G using XDA Premium App
You can't update to KD1 using Kies, it only updates you to KJ6. If you plug your phone onto Kies with KC1, it says phone can't be updated FYI. The closest to KD1 would be deodexed KD1, I can't remember where I found the original odex KD1 but I have the file.
_DMX_ said:
Get your ROM here
T959VKD1 fully flashable through CWM
Click to expand...
Click to collapse
Tried this, and cwm aborts the flash without explanation very early. Any thoughts on this?
Managed to get it working. Thanks guys
_DMX_ said:
Get your ROM here
T959VKD1 fully flashable through CWM
For those of you who are not sure if they have CWM installed follow this guide
GB Ext4 Starter Pack
Or use ODIN and install the ROM
T959VKD1 DeOdexed
Or you could ODIN and install KC1 and then use Kies to get the Official Stock KD1 or Official Stock KJ6
Leaked T959VUVKC1
If you have any boot loop or boot up problems just go through these steps and try the ODIN again afterwards.
GB Ext4 Starter Pack
*** Read each step carefully! Do not skip anything (unless your going to use Kies to update to a stock official Rom)!! ***
*** If your going to use kies to go to a stock update then you might want to change step 10) to this
Step 10) Go into the voodoo menu > Disable lagfix and /system lagfix off
You should be able to update using Kies after this. You will lose root capabilities but if you’re looking to go back to stock then that's a given.
Click to expand...
Click to collapse
So, apparently I can get the KD1 to flash properly but when I try to update via Samsung Kies Mini it won't recognize my device. Also, when I flash the KC1 I get a boot loop and nowhere do I see anything about removing bootloop in the GB Ext4 link. Also, how do I get rid of the Root when I flash KD1?
i0423x said:
So, apparently I can get the KD1 to flash properly but when I try to update via Samsung Kies Mini it won't recognize my device. Also, when I flash the KC1 I get a boot loop and nowhere do I see anything about removing bootloop in the GB Ext4 link. Also, how do I get rid of the Root when I flash KD1?
Click to expand...
Click to collapse
What message/error are you getting from Kies? Mine was telling me my device was not registered. I had to flash back to KD1 & register the device @ Samsung. After that I was able to flash to KJ6 with Kies.
Ah, so I need to register my device on the samsung website? My Kies mini was saying my phone isn't recognized so I don't know what else is going on.
Edit: I just NOW realized where the IMEI number was! lol, forgot it was under about phone. Gosh, so silly.
oops wrong thread
kmandel said:
Tried this, and cwm aborts the flash without explanation very early. Any thoughts on this?
Click to expand...
Click to collapse
What kernal and CWM version are you running? Maybe you should just Odin the KD1 instead.
---------- Post added at 07:56 PM ---------- Previous post was at 07:44 PM ----------
i0423x said:
So, apparently I can get the KD1 to flash properly but when I try to update via Samsung Kies Mini it won't recognize my device. Also, when I flash the KC1 I get a boot loop and nowhere do I see anything about removing bootloop in the GB Ext4 link. Also, how do I get rid of the Root when I flash KD1?
Click to expand...
Click to collapse
ODIN back to KD1 and make sure you have settings, applications, development, USB debugging turned on. Then try Kies again. Don't worry about root just update with kies. It will all go back to stock.
Samsung galaxy s 4g... Help!!!!!!!!!!!!!!!!!!!!!
hello dmx, i have tried to download this file of urs, but the link is dead.... Pls help me, i'm have the same issue with my galaxy s 4g since i ve upgraded it to gingerbread... It kicked me back in every window, text, calls, freezen, reboot.... God bless
If you're wanting to get back to KD1, go grab FBis251's KD1 one-click. You'll probably have to flash it twice & the 2nd time make sure you have "Flash bootloaders" checked. It'll probably boot into recovery & when it does, do a factory reset, wipe the cache, and select reinstall packages. After that you'll be on stock KD1. Make sure you back up your contacts and any other files/apps you want to keep.
Dear Stephen, Thanks for your info. However, I would not wanna flash twice... I will just wait for DMX to reply me if he can get the link working again..... I really wanna do it thru Kies because am sending it back for warranty
dammie2great said:
Dear Stephen, Thanks for your info. However, I would not wanna flash twice... I will just wait for DMX to reply me if he can get the link working again..... I really wanna do it thru Kies because am sending it back for warranty
Click to expand...
Click to collapse
DMX is probably not going to get back to you. The file Stephen linked you to is a repackaged version of the file DMX posted a while back. It is completely stock.
It won't matter that you're not flashing it through Kies, since your phone will wind up with the same stock KD1 files anyway. They won't be able to tell the difference if you're sending it back for warranty.
Stephen is the one you want to listen to. He recommended flashing it twice in case you are on Gingerbread and need Froyo bootloaders.
You do not need to be on KD1 to send phone back. KJ6 is an official release and you an send it in using KJ6.
EDIT: What FB said We must have been writing our posts at the same time.
After painstaking deliberation, they had reached the decision to eat gingerbread. Cautious and deliberate by nature, they opted to install stock 2.3.6 using Kies, presumably the safest choice. KB5 had been having a hard time connecting to the pc via usb with debugging active - no choice was given how to connect to pc, and Kies was not recognizing the phone. Finally bypassing the usb hub allowed Kies to recognize the device, and after a long download, a usb error message flashed up and process failed. Removed phone battery and reboot, all is well but SCREW KIES
Odin from now on
Probably the most creative thing I've seen here all night. Kudos to you my friend!
Sent from my SGH-T959V using XDA App
Downloaded the stock ODIN version of GB 2.3.6 KJ6 .tar here to flash via ODIN but phone will not connect via usb at all now. I think I reverted it's firmware back to the paleolithic era somehow. Could someone share the link the newest ODIN? I have v1.85 and I think also 4.03?
Unless anyone has any ideas, looks like CWM may be my only chance. How can I upgrade firmware if the method used to update is inoperable? Whenever I go into download mode it will not connect with USB. Instead windows says
"USB Device Not Recognized
One of the USB devices attached tho this compter has malfunctioned and windows does not recognize it. For help with this problem, click here."
Great bricked in a factory reset version of kb5 ugh. And this all happened because I tried to use stupid Kies!
Son of a ginger biscuit I figured out why it would not connect it was the 6 FOOT CORD I had hooked up for convenience it WILL NOT GO INTO ODIN OR KIES without the original 3' cord wow
Don't know if it was related to the Kies failure or not but now I am up and running though I cannot flash any .zip with cwm, says signature not verified, and I cannot find a toggle, I have 2.3.6 running now, rooted with super one click zerg, recovery 3e, is there a difference between "rom manager" and "cwm"?? How do I fix this I'd like to install the custom debloater .zip... upgraded from kb5
Farlander said:
Don't know if it was related to the Kies failure or not but now I am up and running though I cannot flash any .zip with cwm, says signature not verified, and I cannot find a toggle, I have 2.3.6 running now, rooted with super one click zerg, recovery 3e, is there a difference between "rom manager" and "cwm"?? How do I fix this I'd like to install the custom debloater .zip... upgraded from kb5
Click to expand...
Click to collapse
Definitely stay away from ROM Manager, from what I've read. You're getting that signature verification error probably because the phone now has standard recovery vs. CWM. That's an assumption on my part, though. You would have to ODIN one of Drhonk's modded kernels that comes with voodoo/cwm/root to get CWM installed. Within the standard recovery there is not a place to toggle the signature verification.
Considering you're on KJ6 now, go to http://forum.xda-developers.com/showthread.php?t=1194032 and grab drhonk's KJ1 kernel. Put it into the PDA section of ODIN and flash it. Then you'll have CWM.
Farlander said:
is there a difference between "rom manager" and "cwm"??
Click to expand...
Click to collapse
I had the same issue when I first started. ROM Manager is an app used to download & install custom ROMs, make backups, etc., but it does not work correctly on our phones. "CWM" (as used in the context of the SGS4G) is the custom recovery menu we install to do basically the same things. Anyway, follow stephen_w's instructions to install a custom kernel and that will solve your issues.
Awesome response stephen_w. A link! So much info out there I'm compiling a small database but when I need something it's usually back to search!
I was up and running KJ6, trying to install .zip files from root of sd card using cwm. Did not work - error was E:\ signature verification failed
So, decide to ODIN back to KB5, and try to load cwm, upgrade via cwm, and see if there was a glitch there. Did not work. Upon ODINING back to KB5, download screen has different look, and phone bootloops at Galaxy S logo. I'm about to ODIN flash 2.3.6 again and hope that it works....
This all started because Kies failed (presumably due to length of cord) the KJ6 from Raver that I ODIN'd in I THOUGHT was all stock actually came with CWM and super user preloaded. CWM did not recognize su.apk in the root and was therefore less functional. I fixed permissions and the error went away, but many icons were still greyed out. I wanted to bring back my apps/data from rom manager backup, but my recovery would not work. It would not open the .zip files, and there was no toggle to enable/disable signature verify. This may have been because I did not buy the pay version of CWM, or I don't know how to use it properly. Do you have to somehow flash the recovery to enable CWM? Is there a particular recovery designed for KJ6 SGS4G??
Also, what is the "bootloader update" option for in ODIN?
Farlander said:
Awesome response stephen_w. A link! So much info out there I'm compiling a small database but when I need something it's usually back to search!
I was up and running KJ6, trying to install .zip files from root of sd card using cwm. Did not work - error was E:\ signature verification failed
So, decide to ODIN back to KB5, and try to load cwm, upgrade via cwm, and see if there was a glitch there. Did not work. Upon ODINING back to KB5, download screen has different look, and phone bootloops at Galaxy S logo. I'm about to ODIN flash 2.3.6 again and hope that it works....
Click to expand...
Click to collapse
Weird; I've not had the signature verification error with CWM, only with the standard recovery.
When you went back to KB5 you went from a Gingerbread (GB) ROM to a Froyo ROM. Froyo & GB require different boot loaders so if the ROM you flashed did not have both boot loaders, then you get stuck in a boot loop. Going back to KJ6 will probably get you going again.
This all started because Kies failed (presumably due to length of cord) the KJ6 from Raver that I ODIN'd in I THOUGHT was all stock actually came with CWM and super user preloaded. CWM did not recognize su.apk in the root and was therefore less functional. I fixed permissions and the error went away, but many icons were still greyed out.
Click to expand...
Click to collapse
I thought Raver's ODIN version of KJ6 was pure stock. I didn't think it had CWM or Superuser.
I wanted to bring back my apps/data from rom manager backup, but my recovery would not work.
Click to expand...
Click to collapse
You might have problems recovering to GB ROMs. This is due to an error in CWM for GB. The problem prevents the /system partition from unmounting. From what I've been told, you have to flash back to a Froyo ROM, like Bali, to do the recovery then flash back to the GB ROM afterward. Not sure if that's your problem here, though, as I've never used ROM Manager.
It would not open the .zip files, and there was no toggle to enable/disable signature verify. This may have been because I did not buy the pay version of CWM, or I don't know how to use it properly. Do you have to somehow flash the recovery to enable CWM? Is there a particular recovery designed for KJ6 SGS4G??
Click to expand...
Click to collapse
I've never paid for a version of CWM. I've always used one of drhonk's modded kernels to get CWM. Installing the KJ1 kernel I mentioned earlier should do that for you.
Also, what is the "bootloader update" option for in ODIN?
Click to expand...
Click to collapse
My best ODIN advice: Let ODIN decide what needs to be checked and what should not. I've not used the "Phone Bootloader Update" feature. Don't go anywhere near the "Phone EFS Clear", either. I've a feeling that would wipe out your IMEI and other things.
See if you can get Raver's ODIN Stock KJ6 to install, then install drhonk's KJ1 kernel. Once done, reboot into recovery mode and see if it is CWM Red recovery, which is should be. Note the version number at the top and report it back here.
If all of that works well and the right version of CWM is there, then maybe we need to examine what ZIP you're trying to flash. Maybe it's a corrupt file.
Thank you very much, succesfully flashed GB 2.3.6 KJ6, succesfully flashed Drhonks KJ1, had a hard time entering recovery boot mode
RECOVERY BOOT MODE 3 BUTTON SGS4G 959V
HOLD: vol up, vol dn, power
RELEASE: power
RELEASE: vol up, vol dn
Disabled voodoo and I'm about to load up busy box, (CWM i.e. rom manager???) per the instructions......
UPDATE 20:02 ownloaded "rom manager", re-enabled VOODOO, rebooting. I think I get what's going on here. The file system is being reformatted / partitioned every time voodoo is enabled/disabled. I'm assuming the enabled mode is ext4 partitioning. However, cwm must be installed during fat32 mode, thus the reasoning for enable/disable voodoo. Can't wait to try this out, is it really faster than stock KJ6?? Love the look and feel of the rom already!
Farlander said:
Thank you very much, succesfully flashed GB 2.3.6 KJ6, succesfully flashed Drhonks KJ1, had a hard time entering recovery boot mode
RECOVERY BOOT MODE 3 BUTTON SGS4G 959V
HOLD: vol up, vol dn, power
RELEASE: power
RELEASE: vol up, vol dn
Disabled voodoo and I'm about to load up busy box, (CWM i.e. rom manager???) per the instructions......
Click to expand...
Click to collapse
Yeah, since being on GB I've been unable to get into recovery unless I use an app like Quick Boot or using ADB from the Android SDK.
Rom Manager and CWM, to my knowledge, are different animals. Good luck getting it going; it sounds like your 95% of the way there.
Heck yea workin good now to restore those apps I lost and debloat and play with boot animations!!!
UPDATE: Just also flashed via CWM .zip the debloater file, SWEET
Bloatware remover flashed with cwm works awesome, just browse to find the .zip doesn't even need to be in root dir
So far no noticeable deficiencies and without even installing app killer I have 165 used and 343 megs of ram free!!
I'm about to try to backup progs using rom manager, but when I click "backup/restore" it tells me I have to flash clockwork mod, which I'm pretty sure is already flashed??
Farlander said:
Heck yea workin good now to restore those apps I lost and debloat and play with boot animations!!!
Click to expand...
Click to collapse
Awesome, glad you got it working
MY PHONE IS NOW ALL THAT IS PERFECT
Thank you EVERYBODY
This took me about 2 weeks of 3-4 hours a day research and thumb work
now operating
2.3.6 KJ6 GB w/
KJ1 drhonk stock + voodoo + cwm
debloater.zip
Titanium Backup to restore all apps (adfree, app killer, etc. etc.)
Icons and background are gone but no bigggy
mine got unplugged in odin download screen can anyone help?
Andrew.80 said:
mine got unplugged in odin download screen can anyone help?
Click to expand...
Click to collapse
That blows. Does ODIN recognize it when you plug it back in? If so, just reflash.
Sent from my SGH-T959V using XDA App
When in doubt take the battery out! (to dinner)
UPDATE: I want to make a total phone backup (of all my current settings) using rom manager. When I go to "backup current ROM" it says cwm needs to be installed and gives me options for several phones, including the i9000. Should I do this even though cwm red is already installed on my phone? Need a workaround here...
thanks in advance
Farlander said:
When in doubt take the battery out! (to dinner)
UPDATE: I want to make a total phone backup (of all my current settings) using rom manager. When I go to "backup current ROM" it says cwm needs to be installed and gives me options for several phones, including the i9000. Should I do this even though cwm red is already installed on my phone? Need a workaround here...
thanks in advance
Click to expand...
Click to collapse
ROM manager doesn't work on the SGS4G. Your best bet right now is titanium backup, or flashing the bali kernel for 2.2 if you want to make a full backup using cwm recovery.
stephen_w said:
Definitely stay away from ROM Manager
Click to expand...
Click to collapse
ultimakillz said:
ROM Manager is an app used to download & install custom ROMs, make backups, etc., but it does not work correctly on our phones.
Click to expand...
Click to collapse
FBis251 said:
ROM manager doesn't work on the SGS4G.
Click to expand...
Click to collapse
Man, this should really be posted somewhere.
stephen_w said:
That blows. Does ODIN recognize it when you plug it back in? If so, just reflash.
That fixed it
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Sent from my SGH-T959V using xda premium
So I was rooted on synergy r72 then went to jellybean...tried flashing back to clean rom and s*it hit the fan...I ended up Odin back to stock and started from square 1...unlocked and rooted I made a nandroid and tried to flash clean rom once again...it installed but when it got to the boot animation it looked strange and the screen where it said Samsung had a bunch of different colors and then it rebooted...battery pulls didn't work...restored my root66 from Odin but can't flash any new roms! Any ideas what is going on!?!? I would greatly appreciate the help!
Did you check the md5 hash of the file you downloaded? Either way try downloading it again and check the hash.
Brian Gove said:
Did you check the md5 hash of the file you downloaded? Either way try downloading it again and check the hash.
Click to expand...
Click to collapse
Yes... I haven't done anything differently from when it worked prior to this
Sent from my SCH-I535 using xda app-developers app
So heres an update...I flashed back to root 66 in odin and everything is normal...when I go to flash a rom in CWM it goes into bootloop and i have to restore my back up...What do I do ?
Did you try downloading the file again? It could have corrupted. Just a thought. Make sure your bootloader is still unlocked(You can tell because it will boot by the first 'Samsung' screen in a split second then go onto the 'Samsung Galaxy SIII' screen.). And before you flash cleanrom wipe everything, data, cache, davlik. Run the fix permissions too just to be sure.
pschatz12 said:
So heres an update...I flashed back to root 66 in odin and everything is normal...when I go to flash a rom in CWM it goes into bootloop and i have to restore my back up...What do I do ?
Click to expand...
Click to collapse
I think your boot loader is relocked when you flash factory stock. Try to flashed back to root 66, then do unlock..the rest should be straight forward.
buhohitr said:
I think your boot loader is relocked when you flash factory stock. Try to flashed back to root 66, then do unlock..the rest should be straight forward.
Click to expand...
Click to collapse
This. If you ODIN back to stock, you need to unlock again.
I have odined back to stock, unlocked, made a nandroid & tried to flash clean rom...I got it flashed but it bootlooped and i had to do 3-5 battery pulls and let it sit for a while in between pulls...I then flashed the kernel and had to do the same thing...then i tried to flash dirty tweeks and then it sat and bootlooped again...Any time i try and flash a rom it does the same thing...Do you guys think that something is wrong with the internal storage and the phone is defective now? Should I get it back to factory stock and try and return it to verizon?
pschatz12 said:
I have odined back to stock, unlocked, made a nandroid & tried to flash clean rom...I got it flashed but it bootlooped and i had to do 3-5 battery pulls and let it sit for a while in between pulls...I then flashed the kernel and had to do the same thing...then i tried to flash dirty tweeks and then it sat and bootlooped again...Any time i try and flash a rom it does the same thing...Do you guys think that something is wrong with the internal storage and the phone is defective now? Should I get it back to factory stock and try and return it to verizon?
Click to expand...
Click to collapse
Please list the steps you took step by step so we can see what's going on here. Don't embellish, don't exaggerate, tell us what you did and what you didn't do. Based on your steps you shouldn't be bootlooping. I would follow droidstyle's guide step by step in each category that is relevant (going back to stock, unlocking, flashing ROMs, etc.). Follow each step closely in whatever ROM you're flashing as well. Don't take shortcuts.
You sure you're unlocked? Maybe try unlocking again. It doesn't seem to bother anything if unlock an unlocked phone. If that makes sense...
+1 to listing your exact steps to help troubleshoot.
mustbepbs said:
This. If you ODIN back to stock, you need to unlock again.
Click to expand...
Click to collapse
Using Odin to go back to stock does not re lock the boot loader.
Unlocking it again doesn't hurt as was just mentioned.
@OP are you sure you're using the correct variant? You are on Verizon and do not have one of the developer phones, etc?
Brian Gove said:
Using Odin to go back to stock does not re lock the boot loader.
Unlocking it again doesn't hurt as was just mentioned.
@OP are you sure you're using the correct variant? You are on Verizon and do not have one of the developer phones, etc?
Click to expand...
Click to collapse
I swore that it did. Are you sure?
http://forum.xda-developers.com/showthread.php?t=1842830 - Yes it does. It rewrites the aboot.img to the secure one.
Positive, I tested it out and that's why droidstyles guide has changed.
I odined back to stock...unlocked...made nandroid...tried to flash clean Rom...it worked...flashed the clean kernel...went into bootloop...restores backup...copied synergy r72 to sd and installed with everything working perfect...I came from synergy 72 before I tried to get to clean Rom...when synergy gets installed does it do anything special in the installation process?
Sent from my SCH-I535 using xda app-developers app
Boot loop sounds like a kernel issue. Are you sure you're not using a TW kernel on AOSP, etc?
Also have you tried redownloading the files that are giving you problems? Try redownloading the kernel to see if that makes a difference. If you're successful in flashing ROMs then I think a fresh download might fix your issue.
pschatz12 said:
I odined back to stock...unlocked...made nandroid...tried to flash clean Rom...it worked...flashed the clean kernel...went into bootloop...restores backup...copied synergy r72 to sd and installed with everything working perfect...I came from synergy 72 before I tried to get to clean Rom...when synergy gets installed does it do anything special in the installation process?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
When you install synergy it installs a custom kernel. It used to detect if you are unlocked before the kernel was flashed but later versions assume you are unlocked. Watch the text as you flash in CWM and see if it gives you any error message or if ziggy's kernel was flashed successfully.
Thats a wired problem I would try going back to the stock rooted image again
Wontfinishlast said:
When you install synergy it installs a custom kernel. It used to detect if you are unlocked before the kernel was flashed but later versions assume you are unlocked. Watch the text as you flash in CWM and see if it gives you any error message or if ziggy's kernel was flashed successfully.
Click to expand...
Click to collapse
Ziggys kernel was flashed successfully and synergy r72 running successfully... Do you guys think I should try dirty flashing clean rom? Idk what else to try... From synergy I can do a full wipe and try install clean rom but I doubt it will work
Sent from my SCH-I535 using xda app-developers app
cleanrom doesn't come with their own kernel baked into it already??? Why would they make you flash the ROM then the kernel..... And if you're getting the bootloop after installing the kernel then it's as mustbepbs said, re-download the kernel file.