Related
so i just ran LGNPST to get to ZV7, then i updated to ZV8
once i was on ZV8, i rooted and unlocked bootloader successfully using GAIO v1.50
i'm having problems booting into my custom recovery TWRP, after i install the custom recovery using GAIO
i try to shutdown the phone and boot into recovery, but every time i try i get a quick screen of the lg logo then it goes black and it doesn't load the os.
i cant even get to fast boot, so what i've done from here (the past 5 times) is i run LGNPST again and start all over again.
i tried the FreeGee method of installing the custom recovery but the results are the same..
any ideas?
avpmusic said:
so i just ran LGNPST to get to ZV7, then i updated to ZV8
once i was on ZV8, i rooted and unlocked bootloader successfully using GAIO v1.50
i'm having problems booting into my custom recovery TWRP, after i install the custom recovery using GAIO
i try to shutdown the phone and boot into recovery, but every time i try i get a quick screen of the lg logo then it goes black and it doesn't load the os.
i cant even get to fast boot, so what i've done from here (the past 5 times) is i run LGNPST again and start all over again.
i tried the FreeGee method of installing the custom recovery but the results are the same..
any ideas?
Click to expand...
Click to collapse
the same thing happened to me a while ago. if i remember correctly, what i did was after lgnst, i rerooted my phone, install cloworkrecovery from the play store. use the app to boot into recovery, then wipe cache and dalvik cache or whatever its called. hope this helps!
javskies said:
the same thing happened to me a while ago. if i remember correctly, what i did was after lgnst, i rerooted my phone, install cloworkrecovery from the play store. use the app to boot into recovery, then wipe cache and dalvik cache or whatever its called. hope this helps!
Click to expand...
Click to collapse
I downloaded rom manager from play store and it says my phone was unsupported
Any ideas?
avpmusic said:
I downloaded rom manager from play store and it says my phone was unsupported
Any ideas?
Click to expand...
Click to collapse
If it says your phone is unsupported then you are trying to load cwm on your phone which shouldn't be needed as free gee should load it on your device(if I remember correctly. Been a while since I unlocked). He is saying that he used it to boot into recovery not load cwm.
I assume that's what he is saying and you are doing if I'm wrong feel free to correct.
You could also install ROM toolbox scroll to the very bottom of the first page click Rebooter and click reboot recovery. That should hopefully take you to cwm where you can flash recovery.
Sent from my LG-LS970 using xda app-developers app
AOKPBrownNoser said:
If it says your phone is unsupported then you are trying to load cwm on your phone which shouldn't be needed as free gee should load it on your device(if I remember correctly. Been a while since I unlocked). He is saying that he used it to boot into recovery not load cwm.
I assume that's what he is saying and you are doing if I'm wrong feel free to correct.
You could also install ROM toolbox scroll to the very bottom of the first page click Rebooter and click reboot recovery. That should hopefully take you to cwm where you can flash recovery.
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
i tried using rom manager to kick me into recovery (chosing trwp recovery before hand with freegee) before and it did the same thing,
rebooted, showed lg logo for a split second, then black screen. i just did the whole process again of using LGNPST to get to ZV7, then i updated to ZV8 then free gee to give me twrp then rom toolbox to kick me into recovery and its the same thing! black screen!
i also tried BEFORE doing freegee to go into recovery after the LGNPST to see what happens, and it just took me to normal recovery.
so my issue has to be with freegee..
should i LGNPST again to get me back up and running and THEN uninstall freegee, reinstall it, and choose clockworkmod as my reovery?
maybe is trwp just failing to load? what are you guys using?
{guide} soft-brick fix
Happened to myself as well. Follow these steps from AdriVelazquez.
Fixed it in a jiffy!
Accessing Recovery Screen (First Step if you have bricked your phone)
This is our initial step for any problems that might arise. If you can access recovery, usually you're in a perfectly fine situation.
1. Power off your phone by holding Volume down & power at the same time.
2. When the screen shuts off, switch to entering fastboot by holding Volume Up & Power. Release immediately once you see a black screen with some text on the bottom.
3. You should see a black screen with some text at the bottom.
4. Press volume down 2x and then the power button.
5. You should see either TWRP or CWM recovery.
6. Wipe Cache, Dalvic Cache, and Factory Wipe
7. Flash new stock zip. Wipe caches again.
8. Restart.
My issue is after I use freegee to unlock the bootloader and to put on twrp recovery
At that moment when I restart my phone won't boot into the android os or fast boot
When I try to enter fast boot by holding power and volume up I never see any text at the bottom of screen it just shows the lg logo then a compete black screen
at this point I'm unable to even enter the OS. So the only thing I can access thankfully is Download mode.
I had the same problem. The way I fixed it was to lgnpst back. Root the phone and then run freegee. Then when I entered the bootloader it did the same lg symbol black screen thing. I held the volume up and down along with power while it was at the black back lit screen for about 20 seconds till it was completely off. Then I plugged it into my computer or you can use a charger to. Wait a few seconds and a battery animation should show up. Leave it on charge for a few minutes and then take it off and turn it on and you should be good to go. I can't guarantee it is going to work but it worked for me and I found it just by trying different things. I also read about someone else mentioning what I did in another soft brick post. I also read that shelnut2 has a special freegee version that you can only get from him. You can try him in irc. I read he dose not want it posted because it could permanently brick the phone.
-Frank
yeah... this is exact same problem that I had before..
You nees to go optimus g IRC channel and talk to shelnutt2 that you are having problem with unlocking bootloader. He will help you nicely cause he is super nice!
irc: http://webchat.freenode.net
channel: #lg-optimus-g
He told me it is very rare issue but I can tell there are several people having this issue now..
Sent from my LG-LS970 using xda app-developers app
issue resolved!
Shellnutt2 helped me out, i had to flash a special freegee to get everything working!
I was going to flash a new ROM on my DHD and did the usual steps: backup using TB, reboot to recovery, factory reset and then go find zip to install on SDCARD. But this time instead of finding my zips I had already transferred, I found none. So I mounted the SDCARD through the recovery menu and transferred the zip using my laptop.
I still couldn't see the zips, so I chose to reboot the phone from the recovery menu. Booted into old ROM, completed the setup wizard and rebooted to recovery again. Still no zips! So I turned the phone off and was just going to boot straight to recovery using VOL UP and POWER but then I only got three short vibrations and nothing happened, so I booted again to ROM and rebooted to recovery from there.
This time nothing happend, nothing at all. And now I'm stuck where I cant boot it, not to recovery, not to HBOOT and not to ROM. Tried taking out the battery and putting it back in. Tried turning it on using just POWER, using VOL UP and POWER, using VOL DOWN and POWER - and in different time length combinations. adb reboot bootloader cant find the phone. The LED doesn't light up when plugged to USB.
ROM: JELLYTIME for DHD/Inspire4g - 4.2.2 R4
Recovery: ClockworkMod
I'm guessing my DHD is completely bricked, right?
benregn said:
I was going to flash a new ROM on my DHD and did the usual steps: backup using TB, reboot to recovery, factory reset and then go find zip to install on SDCARD. But this time instead of finding my zips I had already transferred, I found none. So I mounted the SDCARD through the recovery menu and transferred the zip using my laptop.
I still couldn't see the zips, so I chose to reboot the phone from the recovery menu. Booted into old ROM, completed the setup wizard and rebooted to recovery again. Still no zips! So I turned the phone off and was just going to boot straight to recovery using VOL UP and POWER but then I only got three short vibrations and nothing happened, so I booted again to ROM and rebooted to recovery from there.
This time nothing happend, nothing at all. And now I'm stuck where I cant boot it, not to recovery, not to HBOOT and not to ROM. Tried taking out the battery and putting it back in. Tried turning it on using just POWER, using VOL UP and POWER, using VOL DOWN and POWER - and in different time length combinations. adb reboot bootloader cant find the phone. The LED doesn't light up when plugged to USB.
ROM: JELLYTIME for DHD/Inspire4g - 4.2.2 R4
Recovery: ClockworkMod
I'm guessing my DHD is completely bricked, right?
Click to expand...
Click to collapse
Oh dear poor you, I'm no expert, but unless your battery is dead, I'd say you killed your phone. Can't even get into recovery yikes.
Sent from my HTC Desire HD using xda app-developers app
If your battery is dead you may need to ask a friend to charge it for you? If your phone still boots into recovery you havent killed your phone, if you go to the htc web site & look for the correct software for your phone you may have to apply that to reboot your phone again, but after you will need to root again? But first try another rom a stable one & try doing this - factory reset/full wipe, then wipe cache, then wipe dev cache, then fash the new rom. Hope this helps
sent via my super modded Foxhnd 2.2 with Tapatalk 2
ranger4740 said:
Oh dear poor you, I'm no expert, but unless your battery is dead, I'd say you killed your phone. Can't even get into recovery yikes.
Sent from my HTC Desire HD using xda app-developers app
Click to expand...
Click to collapse
Unfortunately my battery is not dead, confirmed using a working DHD
deanr1977 said:
If your battery is dead you may need to ask a friend to charge it for you? If your phone still boots into recovery you havent killed your phone, if you go to the htc web site & look for the correct software for your phone you may have to apply that to reboot your phone again, but after you will need to root again? But first try another rom a stable one & try doing this - factory reset/full wipe, then wipe cache, then wipe dev cache, then fash the new rom. Hope this helps
sent via my super modded Foxhnd 2.2 with Tapatalk 2
Click to expand...
Click to collapse
I can't boot it at all, not even to recovery.
Unless u can use adb it sounds like your in trouble mate
sent via my super modded Foxhnd 2.2 with Tapatalk 2
Hello, I made a very foolish decision today. I just recently rooted my phone (i747), and i am still not familiar with roms or flashing or any of that. I installed the Rom Manage app by clockworkmod onto my phone. I did no other preperation other than creating a backup through that app on my phone. Then using that app, i downloaded the CyanogenMod 10.1, directly onto my phone. It then gave me the option to wipe data which i chose not to do. It then started the installation of the rom. Everything started off okay and it looked like it installed. When it rebooted it got stuck on the CyanogenMod circle boot and no matter what i try i cannot fix it.
I cannot stress this enough. I am very new to this stuff and am not exactly sure how everything works. It is my mistake and i understand it was the outcome of my stupidity. However, all I am trying to do is fix my phone. When i try to boot into recovery mode (power, home, and up vol) it just restarts still in the boot logo. Whenever i press power, home, and volume down it says "booting a custom rom can harm your device are you sure?" but whether i choose yes or no it is still stuck.
Sorry about all the text, but can somebody please explain to me in the most noob friendly way possible how i can just get my phone in working condition? Thanks for your time
Try booting into recovery this way, in this button pressing order: Vol up + home + power. When your phone vibrates and you see the blue text in the top left corner of the screen, release just the power button.
If this gets you into recovery, you can wipe data, cache and dalvik (under advanced) to see if this clears your issue.
For future reference, don't flash ROMs in rom manager. Only use that app to update or install recovery.
Thanks, that got me into recovery mode. I wiped the dalvic cache, and did a factory reset, but I am still stuck in the boot
crayonslayer said:
Thanks, that got me into recovery mode. I wiped the dalvic cache, and did a factory reset, but I am still stuck in the boot
Click to expand...
Click to collapse
I would suggest to download the CM10 ROM from their thread, and copy it to an external sd card. You can reflash it from the sd card in the recovery menu.
ya, now that you know how to successfully get into recovery, i would flash a rom and gapps again via that route. check out the link in my signature. its got some stuff to look over for a safe and smooth backup & installation
Thanks!
xBeerdroiDx said:
Try booting into recovery this way, in this button pressing order: Vol up + home + power. When your phone vibrates and you see the blue text in the top left corner of the screen, release just the power button.
If this gets you into recovery, you can wipe data, cache and dalvik (under advanced) to see if this clears your issue.
For future reference, don't flash ROMs in rom manager. Only use that app to update or install recovery.
Click to expand...
Click to collapse
Thanks! I couldn't get it to boot into Recovery until I saw your post.....
Thanks. I was stuck in CM11 loop.
Is this also applicable to HTC Desire 816. sorry for crushing, I am just getting frustrated on this matter. tried using my computer to boot from fastboot and tried also pressing the power button while pressing the -Volume. But still on the same cycling LOGO. Please help me if anyone knows how to fix this. Iv also tried to open the back of my unit. but the battery is embedded to the phone.
....
wrong post
how to fix
crayonslayer said:
Thanks, that got me into recovery mode. I wiped the dalvic cache, and did a factory reset, but I am still stuck in the boot
Click to expand...
Click to collapse
maybe you tried to make an advanced data wipe and selected internal storage, dalvic, cache, etc.
what you need to do is put the phone in recovery mode again, select install and then scroll down to find the OS zip that was broke when wiping, after flashing be sucessful reboot system. then turn off the phone again o get it in recovy once more, select install, scroll down but this time you must to install Gapps. to conclude you need to flash OS and Gapps again through recovery mode.
hope this help
Hi All,
Repost since I posted this question in the wrong forum before. Sorry for the spam.
I tried to flash my E980 (already rooted and running Carbon ROM nightly build 10/10/2013) with the latest ROM nightly build 10/24/2013.
When in TWRP 2.5.0.0, I wiped everything except the external SD, added 10/24/2013 build image, gapps, and modem zips and hit install rom.
The flashing stopped due to error saying the MD5 signature of the build image zip is bad.
Now I am left with a device with no OS installed. When I power it on, after the initial LG logo flash, nothing happens.
Would you please tell me how to get back into the recovery mode? Thanks a lot.
I have re-downloaded the ROM zip and put it in the external SD.
At this stage, do I have to use LG flash tool to flash the factory ROM first, then do root,...? Or can I flash the custom ROM directly.
Flash the ROM in cwm directly
Sent from my GT-P3100 using xda app-developers app
Do this
To boot into recovery do this.
Switch off by removing battery,
Re-insert battery,
now hold vol up+home+power button at same time n release it when u see LG logo. This will boot into recovery.
Wipe data and flash the ROM.
Good luck
Edit: I'm not sure if it's vol up or vol down. It's one of those though. Getting into recovery is bit tricky. But I have done it before. If it fails remove the battery again and try once again.
StarkV5 said:
To boot into recovery do this.
Switch off by removing battery,
Re-insert battery,
now hold vol up+home+power button at same time n release it when u see LG logo. This will boot into recovery.
Wipe data and flash the ROM.
Good luck
Edit: I'm not sure if it's vol up or vol down. It's one of those though. Getting into recovery is bit tricky. But I have done it before. If it fails remove the battery again and try once again.
Click to expand...
Click to collapse
Volume up
Sent from my Optimus G Pro using XDA Premium 4 mobile app
StarkV5 said:
To boot into recovery do this.
Switch off by removing battery,
Re-insert battery,
now hold vol up+home+power button at same time n release it when u see LG logo. This will boot into recovery.
Wipe data and flash the ROM.
Good luck
Edit: I'm not sure if it's vol up or vol down. It's one of those though. Getting into recovery is bit tricky. But I have done it before. If it fails remove the battery again and try once again.
Click to expand...
Click to collapse
StarkV5, thanks a lot!
It is "volume up + home + power". Returned to TWRP 2.6.1.0 recovery and flashed 20131104 CM10.2 today. Everything works smoothly except that the screen touch issue in TWRP. The touch calibration was spot on during the first use after TWRP install. After a reboot, the touch is so off. It is like working with a 960*540 screen, i.e. the top left quadrant of the E980 screen.
Thank you (and Neroga too) again!
Hi, I've managed to use Odin to install the bell with root image, phone now working with I747MVLUEMK5..downloaded clockworkmod recovery manager and used the att recovery image. Downloaded custom Roms, factory reset the phone, wiped cache and dalvik then installed the custom ROM. It installed properly but when I reboot, it won't turn on, I have to do the download mode to recover it back using the Odin. Tried different custom ROM and I made sure they are for this image MVLUEMK5... But same result, it won't boot up... Help...did I miss a step?
Copy a ROM to your SD card, install a custom recovery (I prefer CWM), boot into recovery, wipe cache, Dalvik, data, and system, install the custom ROM, reboot the phone.
Every 4.4.2 ROM I have tried (Valudus, Cyanfox, CM11) will boot with a stock 4.1.2 bootloader or newer so you should be fine.
Do you have any warranty left on your phone? Does your phone have Knox installed?
audit13 said:
Copy a ROM to your SD card, install a custom recovery (I prefer CWM), boot into recovery, wipe cache, Dalvik, data, and system, install the custom ROM, reboot the phone.
Every 4.4.2 ROM I have tried (Valudus, Cyanfox, CM11) will boot with a stock 4.1.2 bootloader or newer so you should be fine.
Do you have any warranty left on your phone? Does your phone have Knox installed?
Click to expand...
Click to collapse
Here’s the Steps I went through:
*
I have a Bell S3 with 4.3 JB from OTA
*
1.******Downloaded Odin to my PC
2.******Downloaded the image from* 66 CF Root….
3.******Loaded it to my phone (Using Odin)
4.******Made sure the phone is rooted after and it is
5.******Downloaded CWM Manager from Playstore
6.******Changed the Recovery image using the Manager to Samsung Galaxy S3 for AT&T (d2att)
7.******Downloaded Omni Rom then moved it to the SD card using My File app
8.******Rebooted to Recovery
9.******Backed up my phone
10.***Did a Factory reset
11.***Did a Wipe Cache
12.***Did a Wipe Davlik
13.***Flashed the Rom with no error
14.***Rebooted to System
15.***Samsung Logo showed up for a sec then the phone is dead
16.***Tried to turn it on by pressing the power button but not working, I thought the battery was drained when I rebooted, I plugged it in for half an hour but still not turning on. Was able to press the power_
17.***Vol down and home and it booted to Download mode
18.***Used Odin to load the image frok step 2 above and tried the same steps using different rom (Beanstalk-4.4) and the result is the same
Too much work for me. There is no need to have root before installing a custom ROM.
Do this:
Use Odin to install Philz Touch Recovery from here (use the tar version in PDA, do not check auto reboot): http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att
Once it flashes and you see Reset in the windows, pull the battery, disconnect the phone from computer, boot into recovery, wipe cache, dalvik, system, data, flash rom, reboot.
Thanks for the help...I'll try this tonight...when you say pull the battery, you mean literally take the battery out of the phone? Would it boot to recovery when I put the battery back? or will it normally boot then I would reboot to recovery.
Thanks!
snyph3r said:
Thanks for the help...I'll try this tonight...when you say pull the battery, you mean literally take the battery out of the phone? Would it boot to recovery when I put the battery back? or will it normally boot then I would reboot to recovery.
Thanks!
Click to expand...
Click to collapse
Yes, remove the battery. Disconnect the USB cable, replace the battery, press volume +, home, and power to get into recovery. Wipe cache, Dalvik, system, data, and flash your custom ROM.
audit13 said:
Yes, remove the battery. Disconnect the USB cable, replace the battery, press volume +, home, and power to get into recovery. Wipe cache, Dalvik, system, data, and flash your custom ROM.
Click to expand...
Click to collapse
Okay, installed Philz recovery using Odin, pulled bttery, unplug usb then boot to recovery...Philz recovery booted, was able to set to factory, wipe cache,dalvik and flash beanstalk rom,...rebooted the system and still shows samsung logo for a sec and phone turned off....I was still able to go back to phils recovery and tried a different rom and it did the same...just not booting up after flashing...
One thing I noticed is when flashing the rom it doesnt take long (less than 2 minutes) then it completed withoiut error....could it be the zip file or the SD card where i copied them?
snyph3r said:
Okay, installed Philz recovery using Odin, pulled bttery, unplug usb then boot to recovery...Philz recovery booted, was able to set to factory, wipe cache,dalvik and flash beanstalk rom,...rebooted the system and still shows samsung logo for a sec and phone turned off....I was still able to go back to phils recovery and tried a different rom and it did the same...just not booting up after flashing...
One thing I noticed is when flashing the rom it doesnt take long (less than 2 minutes) then it completed withoiut error....could it be the zip file or the SD card where i copied them?
Click to expand...
Click to collapse
Most of the 4.3 roms take a long time at the first boot once you flash it (when I flashed S3Rx it took 3 minutes 32 seconds, I timed it because most people say I waited a long time but have no recollection of how much time) it will stay at one of the boot image screens for several minutes then it should vibrate once the blue led should illuminate and then it will finish booting.
If the wait is too much for you turn it on, set it down, walk away, find something to do, 10 minutes later come back, if it hasn't booted now make sure you followed all the instructions correctly and flashed the right stuff for the phone model you have.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
---------- Post added at 06:09 AM ---------- Previous post was at 06:06 AM ----------
To make sure we are on the same page, is it just stuck at a boot screen or is it getting to a screen turning off and going back to the same screen repeatedly?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
snyph3r said:
Okay, installed Philz recovery using Odin, pulled bttery, unplug usb then boot to recovery...Philz recovery booted, was able to set to factory, wipe cache,dalvik and flash beanstalk rom,...rebooted the system and still shows samsung logo for a sec and phone turned off....I was still able to go back to phils recovery and tried a different rom and it did the same...just not booting up after flashing...
One thing I noticed is when flashing the rom it doesnt take long (less than 2 minutes) then it completed withoiut error....could it be the zip file or the SD card where i copied them?
Click to expand...
Click to collapse
Try a different ROM. I use validus and it installed without a problem.
audit13 said:
Try a different ROM. I use validus and it installed without a problem.
Click to expand...
Click to collapse
I was able to flash Validus and And Candykat but could not flash Omni and Beanstalk....flashes with no error but just wont boot up...
I quickly checked the difference between validus/candy Kat vs omni/beanstalk...I looked at the updater-script and found that both validus and candykat doesn't have "assert((getprop...." lines in the beginning of the script, they start at mount ("ext4","EMMC.... line...I wonder if I take the assert lines on the Omni and Beanstalk updater-script if it is going to work..
snyph3r said:
I quickly checked the difference between validus/candy Kat vs omni/beanstalk...I looked at the updater-script and found that both validus and candykat doesn't have "assert((getprop...." lines in the beginning of the script, they start at mount ("ext4","EMMC.... line...I wonder if I take the assert lines on the Omni and Beanstalk updater-script if it is going to work..
Click to expand...
Click to collapse
You can remove the asserts and try, but the phone still may not boot. Any particular reason you want Omni or Beanstalk? I personally prefer Validus.
audit13 said:
You can remove the asserts and try, but the phone still may not boot. Any particular reason you want Omni or Beanstalk? I personally prefer Validus.
Click to expand...
Click to collapse
didn't work without the assert either....just wanted to try different Roms...I'm on Validuz now but having a couple of issues...WiFi is not turning on, have to reboot to turn it on and reboot doesn't work either. It won't turn on unless I pulled the battery which is a pain....
snyph3r said:
didn't work without the assert either....just wanted to try different Roms...I'm on Validuz now but having a couple of issues...WiFi is not turning on, have to reboot to turn it on and reboot doesn't work either. It won't turn on unless I pulled the battery which is a pain....
Click to expand...
Click to collapse
That is strange. I run validus on mine and WiFi is fine. Calls and data ate fine as well.
snyph3r said:
Here’s the Steps I went through:
*
I have a Bell S3 with 4.3 JB from OTA
*
1.******Downloaded Odin to my PC
2.******Downloaded the image from* 66 CF Root….
3.******Loaded it to my phone (Using Odin)
4.******Made sure the phone is rooted after and it is
5.******Downloaded CWM Manager from Playstore
6.******Changed the Recovery image using the Manager to Samsung Galaxy S3 for AT&T (d2att)
7.******Downloaded Omni Rom then moved it to the SD card using My File app
8.******Rebooted to Recovery
9.******Backed up my phone
10.***Did a Factory reset
11.***Did a Wipe Cache
12.***Did a Wipe Davlik
13.***Flashed the Rom with no error
14.***Rebooted to System
15.***Samsung Logo showed up for a sec then the phone is dead
16.***Tried to turn it on by pressing the power button but not working, I thought the battery was drained when I rebooted, I plugged it in for half an hour but still not turning on. Was able to press the power_
17.***Vol down and home and it booted to Download mode
18.***Used Odin to load the image frok step 2 above and tried the same steps using different rom (Beanstalk-4.4) and the result is the same
Click to expand...
Click to collapse
Just curious... are you going into mounts and storage to format system along with the factory reset and dalvik / cache wipes ??