Related
This happened before but I can't remember how I fixed it.
1. Flashed TWRP (over codename if that helps)
2. it bootlooped back to recovery instead of starting the system
3. tried flashing another rom/ didn't work
4. finished season 2 of the walking dead
5. reflashed TWRP didn't help (TWRP flashing failed even tho it was the same file I used to get TWRP in the first place)
6. Took the battery out but that didn't help either
I really don't want to odin or use one click any ideas??
lonoguge said:
This happened before but I can't remember how I fixed it.
1. Flashed TWRP (over codename if that helps)
Click to expand...
Click to collapse
Where did you get twrp?
lonoguge said:
2. it bootlooped back to recovery instead of starting the system
3. tried flashing another rom/ didn't work
Click to expand...
Click to collapse
What is "another rom"?
lonoguge said:
4. finished season 2 of the walking dead
5. reflashed TWRP didn't help (TWRP flashing failed even tho it was the same file I used to get TWRP in the first place)
6. Took the battery out but that didn't help either
I really don't want to odin or use one click any ideas??
Click to expand...
Click to collapse
Meh, lets start with the first two...
To stop the reboot to recovery, you must flash eollie's oneclick with bootloaders (so flash it twice, second time flash bootloaders) and go back to mtd.
bhundven said:
Where did you get twrp?
What is "another rom"?
Meh, lets start with the first two...
To stop the reboot to recovery, you must flash eollie's oneclick with bootloaders (so flash it twice, second time flash bootloaders) and go back to mtd.
Click to expand...
Click to collapse
I got it from what I thought was the official XDA TWRP thread but I'm not sure if it was official or not
at first I tried reinstalling codename but now I'm trying Beam (Tuk edition) and it seems to be working
TWRP Major Boot Loop
hey guys, im new here and i desperately need help with my phone!
the other day i was flashing a rom on my samsung galaxy s 4g. Things were turning out fine, until i had some complications on my phone.. so, i removed the rom. when i rebooted my phone, it went directly into the team win recovery project boot loop and every time i try to reboot my phone, it goes into the twrp. I also can't wipe anything and i can't delete anything! Does anybody know how I can solve this or is my phone basically bricked
more details would be helpful..
As in what rom, or what kernel.... etc... and make sure you have the corret phone.
Same problem with t959p
Looks like I'm not alone.......here's my story
the other day I wanted to switch from a stock rom to a custom, so I flashed redux 1.3 which was actually a froyo rom, and it started draining my batt like crazy so I flashed another rom on top of the froyo rom not realizing what I was doing and somehow messed it up cuz now it will only boot into recovery.
Now just to be clear I know this was my fault, I know I should have odin'd back to stock first, but I wasn't thinking at the time.....Ohh and just so you know I've flashed this sucker hundreds of times and was always able to get out of any mess I got in.
So here is the situation as it stands now, 3 button combo to enter download does not work. I can only get it into download with the jig I made. the problem is even in download mode none of my pc's will detect the device as a Samsung composite device, so odin will not see it. I've installed every possible 32 n 64 bit driver I could find including reinstalling kies. Kies wont even see it. I've tried flashing a few roms that I know worked and still it just boots into recovery. Now one thing I'll tell you is that depending on which rom I flash I can get recovery to switch from cwm to twrp. right now I left it with cwm 6.x.
what I need is a cwm flashable stock telus t959p rom complete with bootloaders or at the very least a cwm flashable zip file containing the bootloaders to see if I can recover the phone.
ohh and if your thinking about telling me to google search for the answer then don't bother.......I've spent the last 4 days reading posts and going to different websites and repositories trying to find something that would help me and so far nothing has.
the only thing that might work as a last resort is pushing the bootloaders as per one of raver's or whitehawks posts but it's a little more complicated for me as I would have to set up a laptop with Linux as I don't think i'll be able to pull it off with any of my windows pc's, win7 and win 8 only.
so if anyone has the files I need or can make them please let me know....or if you think you have another solution I could try i'm all ears err eyes.
thanks
Jedi
Have you tried heimdall one-clicks? Maybe it's showing up as gadget or something like that. I've had luck using zadig and heimdall to bring it back from the brink of death.
http://forum.xda-developers.com/showthread.php?t=1358498
EDIT
Woops replied to the wrong thread .
Nothing to see here, move along
Would like to revive a slightly dead thread.
I upgraded to a Galaxy S3 and no longer use my SGS4G for daily use. I had AOKP and disliked it, FC's and didn't like the feel. I have been trying to install a new rom ( old rom, VH Black Ed. ). Every time It loads into TWRP I have the ability to select the zip, install, it says complete, but reboots right back to TWRP menu. I've tried flashing CWM and it will install, flash the rom, reboot, and right back to this TWRP B.S... what am I doing wrong? I want to continue to use this SGS4g for music and internet duties.
How can I install CWM and have it stay even after a reboot? This TWRP is starting to me off
Did you happen to one click to stock before you went ham at the recovery?
Sent from my SGH-T959V using Tapatalk 4
Download CWM Recovery.7z from attachments. Extract Recovery.tar
Download Superuser-3.1.3-arm-signed.7z (or newer from http://androidsu.com/superuser/). Extract Superuser-3.1.3-arm-signed.zip and copy it to your SD card (internal or external).
Put your phone in Download mode. Flash Recovery.tar using Odin.
Put your phone in Recovery mode. Flash Superuser-3.1.3-arm-signed.zip from recovery
Reboot and ready
Thanks developers!
So no need to make kernel un secure?
This post goes to my complete guide for Samsung galaxy ace plus...
Sent from my GT-S7500 using xda premium
I didn't needed. The other method posted makes the S7500L keep rebooting into recovery. So, I flashed stock firmware (S7500LVJLH1) with Odin and start over again, but same result.
I'd flashed again stock firmware and just flash recovery with Odin, then just write Superuser from recovery.
I hadn't time to verify if the problem was with boot.tar or with files that are installed in recovery mode by .bat file.
Sent from my GT-P1010 using xda app-developers app
شكراااااااااااااااااااااااااااااااا
thanxssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss
Can i use this Superuser 3.1.3-arm.zip for rooting Galaxy Ace S5830 ??
Sent from my GT-S5830 using xda premium
Yeah... For any phone with ARM CPU core
Sent from my GT-I9100 using xda app-developers app
issues after flashing gt-s7500T
lokeshsaini94 said:
So no need to make kernel un secure?
This post goes to my complete guide for Samsung galaxy ace plus...
Sent from my GT-S7500 using xda premium
Click to expand...
Click to collapse
I got my hands on a gt-s7500t yesterday and started xda searching on how to put a custom rom on it. i tried all the methods listed under s7500 to put cwm in it but none worked and whenevr i tried to enter either through pressing vol "+" "-" home and power it never enetred recovery nor it enetered through adb so i moved onto flashing cwm through s7500L guide. so by using http://forum.xda-developers.com/showthread.php?t=1725198 guide, i flased successfully flashed cwm and the phone was stuck in recovery boot loop.
I successfully rooted by through cwm and even installed a custom rom but the dammit phone never came out of the recovery loop, so i went to the next step and downloaded a stock UK vodafone firmware from sam mobile and tried flashing that since australian s-7500t stock rom is unavailable.
Now odin gave a "fail" meesage when it reached to flashing fat.bin, i tried almost 3 different stock roms but same problem. I took the battery out, and tried starting the phone the phone started but no display, so i connected it to samsung kies hoping kies will have a solution, well as it turned out that when i went into emergency firmware recovery, the device screen magically lit up for few seconds and went dark again.
i was baffled so i decided to repeat the process http://forum.xda-developers.com/showthread.php?t=1725198 and flash cwm and boot again. well this time when this completed and phone restarted the phone restarted normally and everything seemed fine, so through adb i went into recovery mode again just to see if all was working fine, but now its the same recovery loop again, have tried wiping the dalvik cache, factory reset and cache reset but nothing happening, HAVENT tried the advanced>recovery reboot> procedure, yet.
now am thinking of two options. first to try install another custom rom and see if that might hellp or since iv got another galaxy ace plus, try to extract the custom s7500T rom out of it somehow, (if u guys can tell me howto, cuz i tried titanium backuo but since it requires root and since i cant get into cwm without using s7500L technique which soft bricks i cant use titanium backup to extract the rom)
Anyone got any idea what to do? is there a pit,bootloader,csc,phone etc files that i can flash through odin rather than flashing a complete package through PDA?
or can i just flash boot.img from a stock rom using PDA and you guys think that will solve the problem>?
Android System Recovery (3e) problem
i flashed "recovery.tar" as PDA via Odin3...then went into recovery mod but it say "Android System Recovery (3e)"..i think its Samsung's default recovery ... so where is CWM???
hi guys!
i have a problem with my ace plus and i have to bring it to a warranty center.. so i have to restore the stock rom and un-root.. any help?
is there a guide to do it? do you know where i can find the stock rom?
thanks a lot
If I root my phone, any advantage in the new root between old 1....
Can someone help me?
My Galaxy Ace Plus (S7500) doesn't want to boot in download mode
Thanks guys, great work
However, my Ace plus is GT - S7500W (London 2012 limited edition)
Is there anyway to root it?
Thanks so much!
Hi, Is there a easy way to unroot this method? Do all my files and settings remain intact when using this root method?
Thanks.
kol12 said:
Hi, Is there a easy way to unroot this method? Do all my files and settings remain intact when using this root method?
Thanks.
Click to expand...
Click to collapse
This method don't erase your data, just write a custom recovery and add SuperUser app and bin to your system.
The best method to unroot is installing stock firmware package.
farodriguez said:
This method don't erase your data, just write a custom recovery and add SuperUser app and bin to your system.
The best method to unroot is installing stock firmware package.
Click to expand...
Click to collapse
Thanks. So does installing stock firmware not write any files to the data partition of android? What about the apps that are included in stock firmware sms app, contacts,call logs, maps etc, will those apps data be lost with installing stock firmware?
---------- Post added at 11:27 AM ---------- Previous post was at 11:23 AM ----------
The recovery.img you have is larger than the stock firmware recovery.img. Does this write more data somewhere?
here is Android 4.1.2 for Galaxy ace plus working
http://forum.xda-developers.com/show...5#post38450355
fido747 said:
I got my hands on a gt-s7500t yesterday and started xda searching on how to put a custom rom on it. i tried all the methods listed under s7500 to put cwm in it but none worked and whenevr i tried to enter either through pressing vol "+" "-" home and power it never enetred recovery nor it enetered through adb so i moved onto flashing cwm through s7500L guide. so by using http://forum.xda-developers.com/showthread.php?t=1725198 guide, i flased successfully flashed cwm and the phone was stuck in recovery boot loop.
I successfully rooted by through cwm and even installed a custom rom but the dammit phone never came out of the recovery loop, so i went to the next step and downloaded a stock UK vodafone firmware from sam mobile and tried flashing that since australian s-7500t stock rom is unavailable.
Now odin gave a "fail" meesage when it reached to flashing fat.bin, i tried almost 3 different stock roms but same problem. I took the battery out, and tried starting the phone the phone started but no display, so i connected it to samsung kies hoping kies will have a solution, well as it turned out that when i went into emergency firmware recovery, the device screen magically lit up for few seconds and went dark again.
i was baffled so i decided to repeat the process http://forum.xda-developers.com/showthread.php?t=1725198 and flash cwm and boot again. well this time when this completed and phone restarted the phone restarted normally and everything seemed fine, so through adb i went into recovery mode again just to see if all was working fine, but now its the same recovery loop again, have tried wiping the dalvik cache, factory reset and cache reset but nothing happening, HAVENT tried the advanced>recovery reboot> procedure, yet.
now am thinking of two options. first to try install another custom rom and see if that might hellp or since iv got another galaxy ace plus, try to extract the custom s7500T rom out of it somehow, (if u guys can tell me howto, cuz i tried titanium backuo but since it requires root and since i cant get into cwm without using s7500L technique which soft bricks i cant use titanium backup to extract the rom)
Anyone got any idea what to do? is there a pit,bootloader,csc,phone etc files that i can flash through odin rather than flashing a complete package through PDA?
or can i just flash boot.img from a stock rom using PDA and you guys think that will solve the problem>?
Click to expand...
Click to collapse
I've been having the exact same problem as you with my S7500L. Boot loop error after installing custom roms. I can, however, install CWM and obtain root without problems.
I really don't understand how the s7500L rom guys developed them... how did they get out of the boot loop.
I tried replacing the boot.img from the custom ROM with one from a stock rom... nothing.
Corsario_Negro said:
I've been having the exact same problem as you with my S7500L. Boot loop error after installing custom roms. I can, however, install CWM and obtain root without problems.
I really don't understand how the s7500L rom guys developed them... how did they get out of the boot loop.
I tried replacing the boot.img from the custom ROM with one from a stock rom... nothing.
Click to expand...
Click to collapse
Hi i have the same problem and the solution is flash this http://forum.xda-developers.com/showthread.php?t=2255561
i used odin, and works perfect.
i installed the cwm and i cant enter recovery it sthows a trinagle sith ! ander the samsung and after it boots normaly
vasilisaerox said:
i installed the cwm and i cant enter recovery it sthows a trinagle sith ! ander the samsung and after it boots normaly
Click to expand...
Click to collapse
Just flashed recovery and i'm having the same issue. Original 2.3.6 installed never touched.
i'm stuck in an endless bootloop after trying to upgrade the CM10 Beta 4 version on my Samsung Galaxy S Plus.
This is what i did
I'd upgraded from 2.3.3 to 2.3.6 some months ago. Then flashed CM10 Beta 4 by ivendor.
For this i first downloaded the CWM -> recovery-clockwork-5.5.0.4-ariesve.tar.md5 and flashed it using Odin.
Then the ROM file -> cm-10-20130324-ivendor-beta4-ariesve.zip
Was checking the updates on this and found much advances in the 2.5 release of 2 May 2013.
So downloaded the CWM -> CWMRecovery-6.0.2.8-ariesve-kernel26.tar.md5. When i tried to flash using Odin it gave me the MD5 error.
Saw somewhere on the forum to flash using zip file, so downloaded CWMRecovery-6.0.2.8-ariesve-kernel26.zip and tried to flash. This was when my phone got soft-bricked.
Removed the cable, battery etc. After some time, was able to go into Download mode but not Recovery.
Then i tried to flash to stock ROM (2.3.6) - I9001XXKQI_I9001XXKPM_I9001OXFKQ3_HOME.tar.md5. This completed and Odin said PASS. But the phone now goes into a bootloop. Tried the Recovery mode but after the Android-out-of-the-box symbol it again said SAMSUNG and started the boot. This is repeating continuously. What should i do now? Please help.
This is the sequence of things...
1) 2.3.3 to 2.3.6 - Success !!
2) Flash with CM10-Beta 4.a) recovery-clockwork-5.5.0.4-ariesve.tar.md5 - OK
b) cm-10-20130324-ivendor-beta4-ariesve.zip - Success!!!
c) gapps-jb-20121011-signed.zip - Success!!3) Flash with CM10-Release 2.5a) CWMRecovery-6.0.2.8-ariesve-kernel26.tar.md5 - MD5 checksum error !!
b) CWMRecovery-6.0.2.8-ariesve-kernel26.zip - Soft-bricked !!!4) Flash stock ROM (2.3.6) a) I9001XXKQI_I9001XXKPM_I9001OXFKQ3_HOME.tar.md5 - PASS
Bootloop
Cannot go into Recovery mode too (after Recovery mode icon appears SAMSUNG logo comes up and phone boots with the blue spiral, this goes into a continuous loop)
anoopgkris said:
i'm stuck in an endless bootloop after trying to upgrade the CM10 Beta 4 version on my Samsung Galaxy S Plus.
This is what i did
I'd upgraded from 2.3.3 to 2.3.6 some months ago. Then flashed CM10 Beta 4 by ivendor.
For this i first downloaded the CWM -> recovery-clockwork-5.5.0.4-ariesve.tar.md5 and flashed it using Odin.
Then the ROM file -> cm-10-20130324-ivendor-beta4-ariesve.zip
Was checking the updates on this and found much advances in the 2.5 release of 2 May 2013.
So downloaded the CWM -> CWMRecovery-6.0.2.8-ariesve-kernel26.tar.md5. When i tried to flash using Odin it gave me the MD5 error.
Saw somewhere on the forum to flash using zip file, so downloaded CWMRecovery-6.0.2.8-ariesve-kernel26.zip and tried to flash. This was when my phone got soft-bricked.
Removed the cable, battery etc. After some time, was able to go into Download mode but not Recovery.
Then i tried to flash to stock ROM (2.3.6) - I9001XXKQI_I9001XXKPM_I9001OXFKQ3_HOME.tar.md5. This completed and Odin said PASS. But the phone now goes into a bootloop. Tried the Recovery mode but after the Android-out-of-the-box symbol it again said SAMSUNG and started the boot. This is repeating continuously. What should i do now? Please help.
This is the sequence of things...
1) 2.3.3 to 2.3.6 - Success !!
2) Flash with CM10-Beta 4.a) recovery-clockwork-5.5.0.4-ariesve.tar.md5 - OK
b) cm-10-20130324-ivendor-beta4-ariesve.zip - Success!!!
c) gapps-jb-20121011-signed.zip - Success!!3) Flash with CM10-Release 2.5a) CWMRecovery-6.0.2.8-ariesve-kernel26.tar.md5 - MD5 checksum error !!
b) CWMRecovery-6.0.2.8-ariesve-kernel26.zip - Soft-bricked !!!4) Flash stock ROM (2.3.6) a) I9001XXKQI_I9001XXKPM_I9001OXFKQ3_HOME.tar.md5 - PASS
Bootloop
Cannot go into Recovery mode too (after Recovery mode icon appears SAMSUNG logo comes up and phone boots with the blue spiral, this goes into a continuous loop)
Click to expand...
Click to collapse
AFAIK, CM10 would have already consisted of the latest CWM, so there is no need of u to flash a CWM again over it!
Ur biggest mistake, u MUST have had a nandroid backup before doing anything to ur phone! This might have been even recommended by the thread of the CM10.
So my last suggestion from the things that u have done, flash the CWM through odin if possible right now and if successful get into recovery mode and wipe data & cache and check whether the bootloop is gone.
Else try reflashing the stock firmware.
If that doesn't even help, get help from the devs related to ur device through PM.
If hopeless still, then hit a samsung service center near u
Hit thanks rather than typing it
Will try this
parkourkarthik said:
AFAIK, CM10 would have already consisted of the latest CWM, so there is no need of u to flash a CWM again over it!
Ur biggest mistake, u MUST have had a nandroid backup before doing anything to ur phone! This might have been even recommended by the thread of the CM10.
So my last suggestion from the things that u have done, flash the CWM through odin if possible right now and if successful get into recovery mode and wipe data & cache and check whether the bootloop is gone.
Else try reflashing the stock firmware.
If that doesn't even help, get help from the devs related to ur device through PM.
If hopeless still, then hit a samsung service center near u
Hit thanks rather than typing it
Click to expand...
Click to collapse
Thanks, will try this tonight
I already took the Nandroid backup before flashing CM10 Beta 4. But was not able to go into it after my phone was soft-bricked.
Solved - booted into 2.3.6 !!!
parkourkarthik said:
AFAIK, CM10 would have already consisted of the latest CWM, so there is no need of u to flash a CWM again over it!
Ur biggest mistake, u MUST have had a nandroid backup before doing anything to ur phone! This might have been even recommended by the thread of the CM10.
So my last suggestion from the things that u have done, flash the CWM through odin if possible right now and if successful get into recovery mode and wipe data & cache and check whether the bootloop is gone.
Else try reflashing the stock firmware.
If that doesn't even help, get help from the devs related to ur device through PM.
If hopeless still, then hit a samsung service center near u
Hit thanks rather than typing it
Click to expand...
Click to collapse
A million thanks!! It somehow started now into the 2.3.6.
Flashing the recovery-clockwork-5.5.0.4-ariesve.tar.md5 did not solve the bootloop. Then i flashed the Boot_loader.tar. That too did not solve the bootloop. Tried Recovery mode again but the SAMSUNG logo kept coming and going until i released my fingers after a full two minutes. Then before the android-out-of-the-box icon came it went straightaway into Recovery .
Wiped Data and Cache and rebooted. After a very very long time it started and asked if im okay with the Google data collection policy asked in Polish language.
Wow, going to update to 4.1.2 Release 2.5 in some time.
Thanks again man. :good:
Got CM10 Beta 4 again !
parkourkarthik said:
AFAIK, CM10 would have already consisted of the latest CWM, so there is no need of u to flash a CWM again over it!
Ur biggest mistake, u MUST have had a nandroid backup before doing anything to ur phone! This might have been even recommended by the thread of the CM10.
So my last suggestion from the things that u have done, flash the CWM through odin if possible right now and if successful get into recovery mode and wipe data & cache and check whether the bootloop is gone.
Else try reflashing the stock firmware.
If that doesn't even help, get help from the devs related to ur device through PM.
If hopeless still, then hit a samsung service center near u
Hit thanks rather than typing it
Click to expand...
Click to collapse
All went smooth. CM10 Beta 4 is back on my SGS+.
Thanks for the advises and help
anoopgkris said:
All went smooth. CM10 Beta 4 is back on my SGS+.
Thanks for the advises and help
Click to expand...
Click to collapse
U got it man:victory:
It's good that u posted the way u solved it! so that it would help others who face the same problem
BTW add the word [solved] in ur thread topic..
Hit thanks rather than typing it
[SOLVED] Bootloop problem after soft-brick
parkourkarthik said:
U got it man:victory:
It's good that u posted the way u solved it! so that it would help others who face the same problem
BTW add the word [solved] in ur thread topic..
Hit thanks rather than typing it
Click to expand...
Click to collapse
Sure, thanks !!
Also pasting here an easter egg that i saw after loading Gingerbread 2.3.6 before this CM10.
Putting this because i tried this for the first time in GB (the seven times click on android version)
Hey everyone,
My little brother is trying to learn more things about mobile devices and wanted to have a go at my old piece of junk, stock optimus one p500h. So i let him have a go and now it's not working so here is the problem.
First he rooted it and that worked fine with gingeroot and then proceeded to install romanager which bricked the phone but he was able to recover the phone with a recovery.img and using LGMDP-v1.5 and emergency mode.
After that he installed some android system recovery thing "RA-thunderg-1.2.0-gnn" not sure what the software was originally, regardless he tried flashing from the flash from zip from sdcard and used a cyanogenmod zip which he said worked and then the phone said success and rebooted.
Now the phone just sits at the cyanogenmod loading screen and will not boot.
I am able to get into the recovery menu with home,down and power and emergency mode also works.
Where did he go wrong and what does he need to do in order to get this to work properly? Thanks for your help everyone and sorry if the post is a bit disjointed i'm trying to translate what he's saying into the post xD
forthecake said:
Hey everyone,
My little brother is trying to learn more things about mobile devices and wanted to have a go at my old piece of junk, stock optimus one p500h. So i let him have a go and now it's not working so here is the problem.
First he rooted it and that worked fine with gingeroot and then proceeded to install romanager which bricked the phone but he was able to recover the phone with a recovery.img and using LGMDP-v1.5 and emergency mode.
After that he installed some android system recovery thing "RA-thunderg-1.2.0-gnn" not sure what the software was originally, regardless he tried flashing from the flash from zip from sdcard and used a cyanogenmod zip which he said worked and then the phone said success and rebooted.
Now the phone just sits at the cyanogenmod loading screen and will not boot.
I am able to get into the recovery menu with home,down and power and emergency mode also works.
Where did he go wrong and what does he need to do in order to get this to work properly? Thanks for your help everyone and sorry if the post is a bit disjointed i'm trying to translate what he's saying into the post xD
Click to expand...
Click to collapse
If running a Windows PC and the device can boot in to fastboot, you can use Android Flash Recovery ( link in my signature ) to flash another recovery image. There are some more complicated ways using ADB, but well try to avoid them ATM You can also use LGMDP to flash a different recovery image. There are several floating around here at XDA.
As for where he went wrong, I cannot say. Piece of advice, if in doubt - don't do it.
Have you tried booting to recovery and wiping cache and dalvik cache then attempt to boot to Andorid?
shinobisoft said:
If running a Windows PC and the device can boot in to fastboot, you can use Android Flash Recovery ( link in my signature ) to flash another recovery image. There are some more complicated ways using ADB, but well try to avoid them ATM You can also use LGMDP to flash a different recovery image. There are several floating around here at XDA.
As for where he went wrong, I cannot say. Piece of advice, if in doubt - don't do it.
Have you tried booting to recovery and wiping cache and dalvik cache then attempt to boot to Andorid?
Click to expand...
Click to collapse
thanks for the fast reply, looks like recovery is gone now? I had attempted to clear the cache though. Would you mind giving me a step by step as im unsure of what i need to do now xD not sure what i need downloaded or to do what with what after my brothers done all this haha
Just flash a recovery from LGMDP for your phone.. then download a rom for your phone and wipe everything in recovery and flash the rom
And do not flash stock rom from kdz or lgmdp if you cannot boot your phone. It has high chances of bricking
Junior Einstein said:
Just flash a recovery from LGMDP for your phone.. then download a rom for your phone and wipe everything in recovery and flash the rom
And do not flash stock rom from kdz or lgmdp if you cannot boot your phone. It has high chances of bricking
Click to expand...
Click to collapse
ok now it's running again and sadly it's giving me an unkown baseband and no service now! I tried flashing to the old legacy baseband for cyanogenmod 7.2 / 2.3.7
forthecake said:
ok now it's running again and sadly it's giving me an unkown baseband and no service now! I tried flashing to the old legacy baseband for cyanogenmod 7.2 / 2.3.7
Click to expand...
Click to collapse
Cm7(except a very old one from mik_os), stock gb and up requires new baseband. You can search for baseband fix and install through recovery ( I don't remember if it's old bb fix or new bb fix, try for yourself )
You can also search how to install new bb permanently but it's more difficult and has(I think) chances of bricking your phone
Sent from my LG-P500 using xda premium
My old phone got lost so I am using my Infuse again. I decided to update it since it is still on the old version from when it first came out. I was trying forever to update through the kies software until I realized I rooted it and so this won't work. So then I found out there are roms for way better versions anyways. So I found the Cyanfox rom and I wanted to do that, but I needed to first upgrade to cm9 so I went and downloaded the cm9 file and got the clockworkrecovery, and I installed it.
Now my phone will not turn on, it sits as samsung screen. And if you try to go to recovery it is just a messed up screen with all different colors as if the screen was broken. So now my only option to bea ble to install anything on it is through odin. I can get to download mode fine.
But this damn odin software will not detect my phone for the life of me. It literally will not work. I don't understand. I have spent hours upon hours on this between the past few days. I just want to update my damn phone.
Now I have to leave for work in 30 minutes and my phone doesn't work. This is just great.
How did you install CWM?
Sent from my Asus MeMO Pad 8"
Well I tried clockworkmod through the rom manager app, but I was running the android recovery 3e and it said I needed a modified version of that to be able to install 3e. So I replaced the recovery file with the one I was given, and then I manually installed cwm by naming it update.zip and running it on the recovery
The only problem was that every time I wanted to use cwm, it would go back to android recovery 3e, and I would have to click install again to get it to go into cwm.
Either way, it doesn't work anymore and I just need the damn thing to connect to Odin so I can flash it back.
Are you using a desktop or laptop? If desktop, are you using the USB ports in the back? If laptop, have you tried different USB ports? Maybe try a different computer? I've heard that USB 3.0 doesn't play nicely with ODIN so it's good to find some 2.0 connections. What Windows version? I've heard that Win8 can cause problems. Could also try Heimdall instead of Odin.
Unless I think of anything else, is the cable in good working order (recent successful file transfer)?
Alright. I got things working somewhat. I had to use different drivers for each program for it to be able to detect it. I don't know, its annoying as hell, but it worked when I went back and forth between drivers.
Anyways, I got my device restored. But the whole point of this was that I was trying to get to the KitKat rom(Cyanfox). I am still quite a few steps away from that. I am actually further away than when I started,
This is what originally happened: I had my device rooted(from when I last used it, 1-2 years ago) and had the 3e recovery. So I found out I needed a modified 3e so I could install Clockworkmod. Got that, all was well, and the thing basically got bricked when I went to update to a new rom. It wasn't the kitkat rom, but a CM9 rom that I needed to go to first so that I could then update to kitkat.
Now I got it unbricked, and I updated it using kies. So now I am on gingerbread. So then I rooted it again. So now I have the 3e recovery again, the only problem is when I go to system/bin/ there is no file called recovery, and I can put one there but it does not affect the recovery, it still looks for signed files, meaning I cannot install Clockworkmod.
Not sure what to do...
Seems everyone follows this process (looks like you already did step one) now....
1. Either use Odin or Heimdall One-Click. Follow instruction on how to do it.
2. While phone running install sgs kernel flasher from Market/Google Play.
2a. Copy/transfer Synthesis GB Kernel to your Internal SD card.
2b. Start up sgs kernel flasher and choose it from your Internal SD card. Phone will auto-reboot after done flashing.
2c. Wait a bit while your phone convert to new partition format and activate lagfix. Your CWM recovery version should be 2.5.1.3
3. Reboot phone into CWM Recovery and DISABLE vodoo lagfix and /system lagfix. Reboot once done. Phone will convert partition to old format. If you don't turn the lagfix off the phone will hang at Samsung logo when you install new rom.
4. Prepare your flavor rom/gapp for installation by copying them to your Internal SD card.
4a. Go into CWM Recovery mode and install the rom. You will need to do this twice since the 1st time was just a warning about partition format being different.
4b. Reboot once done. You will need to REMOVE the battery to power down the booting process and put it back in.
4c. Go into the New CWM Recovery and install the rom again since the previous attempt only install the new CWM Recovery.
5. Install Gapp.
6. a. Wipe: Cache / Factory Reset <--- Probably don't need it since it's new install from stock unless you installed stuff. Just to be safe.
b. Wipe: Cache Partition
c. Wipe: Dalvik Cache
7. Reboot
Click to expand...
Click to collapse
I never tried step two myself, as I found a flashable download for ODIN that did this for me. But mine is a Rogers phone (not AT&T) so that would not work for you. Hope this helps.
Thanks you so much man. I know that is just copy/paste but I didn't see it, and it works. I was looking in Cyanfox thread, never looked at the Beanstalk thread.
Anyways I am in the process of doing this and it seems like it will work. Appreciate all your help!
Edit: Boom. Worked like a charm. Thanks so much. I am very happy now The funny thing is, half the reason I wanted this is cause everyone was group messaging, and I didn't have that capability anymore when I lost my phone(I was on such an old version). Again thanks so much.