After installing TWRP 2.6.3.2 (latest atm) I tried to flash the ROM CMB rc2 on my G pad. I am unable to post in that topic because of my low post count.
Everything went fine, though during the boot it just never stopped showing the boot screen/CMB logo (I am aware that the first time it is used to take a while). The thing I might have done wrong is before the new flash, is to erase everything at first. I didn't do that =(.
I am now unable to reach in through ADB. It just doesn't find the device. Any other way of booting in to recovery is unknown to me. I tried several times rebooting with a variety of button-combinations, but it just continues to the boot screen/logo. I dont even know if there even IS an button combination to boot into recovery.
Sadly when force-shutdown (holding the power button) it doesn't shut down. It restarts. I am now unable to shutdown my own tablet.
Help would be much appreciated. Thanks in advance!
Any additional info:
I have not flashed gApps right after, or any thing else for that matter.
I have installed TWRP from 2.6.3.0 => 2.6.3.1 => 2.6.3.2 in just about 3 minutes after each other. I was mistaken in the files, picked the #.1 in stead of the #.2 directly.
If there is any information I could provide extra that would help sort this out I would gladly do so.
jhjoosten said:
After installing TWRP 2.6.3.2 (latest atm) I tried to flash the ROM CMB rc2 on my G pad. I am unable to post in that topic because of my low post count.
Everything went fine, though during the boot it just never stopped showing the boot screen/CMB logo (I am aware that the first time it is used to take a while). The thing I might have done wrong is before the new flash, is to erase everything at first. I didn't do that =(.
I am now unable to reach in through ADB. It just doesn't find the device. Any other way of booting in to recovery is unknown to me. I tried several times rebooting with a variety of button-combinations, but it just continues to the boot screen/logo.
Sadly when force-shutdown (holding the power button) it doesn't shut down. It restarts. I am now unable to shutdown my own tablet.
Help would be much appreciated. Thanks in advance!
Any additional info:
I have not flashed gApps right after, or any thing else for that matter.
I have installed TWRP from 2.6.3.0 => 2.6.3.1 => 2.6.3.2 in just about 3 minutes after each other. I was mistaken in the files, picked the #.1 in stead of the #.2 directly.
If there is any information I could provide extra that would help sort this out I would gladly do so.
Click to expand...
Click to collapse
Your best bet would be to restore the factory firmware and start over. To do this, follow the instruction in this thread. The only change is that to enter Download Mode on the G Pad, you hold volume up and volume down while inserting the USB cable rather than just volume up.
Related
I am not new to the concept of rooting and loading a custom rom. This is the 3rd android phone that I have bothered with. However it is the first one I have had to use Odin to root or push files to.
I have used CarpeNoctem's writeup on how to root and utkanos' CWMR port writeup. Ofter verifying I had root, I decided I would try out Carpe's OsiMood. No problem right? Here is where I am wondering what if anything went wrong on the previous steps.
I made a back up ofter finally getting it to recovery mode, and when I tried flashing the new rom, it would not complete the process.
As it sits, when I choose recovery from CWM it reboots to the android with triangle screen(see attached video). What concerns me is the lack of fluidity into the recovery, the fact that it loads in only after the battery is removed and the phone is turned back on and lastly that I cannot flash a new rom.
It appears as though I need more posts to add my link for youtube.
Please add standard youtube weblink before this to watch the video.
/watch?v=qpQyQB1aozs
What would you recommend my first action be?
Thanks,
Steve
This also quite unfortunate for ROM manager, "somewhat", not working fully for the Glide (yet). I can't really go into 3e/CWM recovery with the app, but manually (volume down + power/lock button) has no problems. This also happens on my Captivate (SGH-I896/7), I need to restart the device for a second time to boot into recovery. As per your flashing issues, you might need to mount /system manually and then flash the ROM, when it fails, try and try again, always happens to me from stock rogers ROM. Also, if you have Titanium Backup, it now supports reboot device features (recovery and hard reboot)
Thanks for your insight. I tried volume down and power before but when I saw the samsung logo pop up I figured it wouldn't work.
I will try flashing again and report back. Thanks again.
-Steve
Tried flashing again, worked great. If only the glide had more support. Lol.
Currently running OsiMood.
Sent from my SAMSUNG-SGH-I927R using Tapatalk
gabby131 said:
This also quite unfortunate for ROM manager, "somewhat", not working fully for the Glide (yet). I can't really go into 3e/CWM recovery with the app, but manually (volume down + power/lock button) has no problems. This also happens on my Captivate (SGH-I896/7), I need to restart the device for a second time to boot into recovery. As per your flashing issues, you might need to mount /system manually and then flash the ROM, when it fails, try and try again, always happens to me from stock rogers ROM. Also, if you have Titanium Backup, it now supports reboot device features (recovery and hard reboot)
Click to expand...
Click to collapse
My glide does not boot. I can get into Download Mode. I can NOT get into de recovery mode. I think my NAND is corrupted.
How can I mount the /system partition? Because I flashed too many roms with ODIN, but nothing, still not booting, I get stuck in the samsung logo.
Use Odin to reflash recovery,you backups should still be there unless like you say maybe they got corrupted as well,but its worth a shot.
Here is a link to the latest,with instructions:
http://forum.xda-developers.com/showthread.php?p=34479219#post34479219
Kodiack99 said:
Use Odin to reflash recovery,you backups should still be there unless like you say maybe they got corrupted as well,but its worth a shot.
Here is a link to the latest,with instructions:
http://forum.xda-developers.com/showthread.php?p=34479219#post34479219
Click to expand...
Click to collapse
I've already flashed the stock recovery, the CWM, a lot of kernels, even I tried to flash the kernel and bootloader of the Galaxy S II, but nothing.
I'm starting to think that maybe is a hardware problem. Hope not, but I'm not moving foward.
If you havent already,pull out the sim and sd card.
Reboot your pc and download a fresh up to date Odin.
So when you flash it says it successful and then just doesnt boot?
I had a boot loop once ,had me stumped and it turned out to be my sd card was poached and caused the loop.
Kodiack99 said:
If you havent already,pull out the sim and sd card.
Reboot your pc and download a fresh up to date Odin.
So when you flash it says it successful and then just doesnt boot?
Click to expand...
Click to collapse
Exactly... It goes all over the process bar, says succesfull, the phone turns off, and nothing. The phone not even restart itself, I have to remove the battery, put it back again, and then it turns on, but just to show me the samsung logo.
I've used the ODIN version 1.85 and the new one 3.04. But nothing. This is so frustating.
---------- Post added at 04:23 AM ---------- Previous post was at 04:04 AM ----------
I've opened a thread with all the symptoms of my bricked phone:
http://forum.xda-developers.com/showthread.php?t=2035742
Please, tell me there is a solution...
There are one alternative to boot
1. Shut down and then restart phone in recovery mode. For the Samsung Captivate Glide, this required pressing the power, volume down and home keys all at the same time.
2. The initial screen which appears gives you a choice of loading a replacement OS (volume up) or entering recovery mode (volume down). Note you have to hold the volume down key for several seconds before the recovery mode menu appears.
Hi. I was trying out Blisspop on this tablet and decided I preferred CM11 so decided to restore a backup. After rebooting, nothing turned on, only download mode worked so I just flashed stock firmware using Odin (which I had used successfully previously). Now it boots but gets stuck at the Samsung Logo. I can still get to download mode, but nothing else. I've read that if factory reset in the stock recovery, it'll work itself out but I can't even get to it. Any suggestions? Thanks.
jalchemyst said:
Hi. I was trying out Blisspop on this tablet and decided I preferred CM11 so decided to restore a backup. After rebooting, nothing turned on, only download mode worked so I just flashed stock firmware using Odin (which I had used successfully previously). Now it boots but gets stuck at the Samsung Logo. I can still get to download mode, but nothing else. I've read that if factory reset in the stock recovery, it'll work itself out but I can't even get to it. Any suggestions? Thanks.
Click to expand...
Click to collapse
Dont panic really common problem happened to me.
1. Boot into recovery, if not flash one with odin coz your gonna need something...like philz touch or team win or whatever.
2. Wipe cache and dalvik, reboot and wait, samething might appear to happen but it should boot.
Basically ive noticed a few times now on my t805 that the cache wouldnt format propperly and became corrupt and caused this.
I knew this because in the recovery a bunch of errors appeared saying couldnt acces log from cache/blah zt each time i navigated the menu of revoveryand so i wiped cache and they stopped
Booted and viola...if you see any other errors in recovery tell us here.
Good luck m8.
pdolton2000 said:
Dont panic really common problem happened to me.
1. Boot into recovery, if not flash one with odin coz your gonna need something...like philz touch or team win or whatever.
2. Wipe cache and dalvik, reboot and wait, samething might appear to happen but it should boot.
Basically ive noticed a few times now on my t805 that the cache wouldnt format propperly and became corrupt and caused this.
I knew this because in the recovery a bunch of errors appeared saying couldnt acces log from cache/blah zt each time i navigated the menu of revoveryand so i wiped cache and they stopped
Booted and viola...if you see any other errors in recovery tell us here.
Good luck m8.
Click to expand...
Click to collapse
The problem was that I couldn't even get into recovery. But found thread on xda that mentioned if you turn off the tablet from download mode (pressing power and volume down) then you can use the normal three button method to get to recovery. And then yes, I wiped everything I could and it finally booted back up. Thanks for the help mate.
jalchemyst said:
The problem was that I couldn't even get into recovery. But found thread on xda that mentioned if you turn off the tablet from download mode (pressing power and volume down) then you can use the normal three button method to get to recovery. And then yes, I wiped everything I could and it finally booted back up. Thanks for the help mate.
Click to expand...
Click to collapse
No worries pal glad all went well in the end m8
Hey there. I've been using Candy5 for a bit, but kept a nandroid backup of stock. Today I restored stock (was working for a day) but when I tried to restore back my Candy5 nandrood backup from recovery it won't boot, and shows up a LG logo with 'Security error' under it. What may be the problem? I had to go to work and left my phone at home. Will look at it in a few hours,just wondering if you guys saw something similar? Any workarounds to that? Or how to fix it?
Jast flash aosp kernel Furnace od 777jon.
How do I that ? Can't access recovery because it won't boot. From what I've read so far D855 can't go into fastboot.
Have you tried with button combination volume down and power to boot in to recovery? If not then go into download mode with volume up and plug usb cable and reflash to stock rom with Flash Tool.
Didn't even know the combination exists, was used to it from former Sony phones, but it isn't working here.
Yup, reflashing stock now, thanks.
The problem prob was I installed recovery through AutoRec app. That seems to be for 5.0 only.
Which is the best recovery/kernel for 5.1.1?
Furnance and 777jon kernel both are good and work well on 5.1
reboot to recovery with hard keys (hold power+volume down, when see the LG logo, release and hold again keys, then you see the factory reset option, double yes)
flash your current rom again, (no need to GApps again, just rom) wipe cache+dalvik, reboot system.
AutoRec is the problem for me to see this error, and my solve
sorry for bad english
I was on stock F240L20D, 4.4.2 Kitkat, rooted, PhilZ Touch 6 installed. I've tried some ROMs before but reverted back to this one. So, basically, I've been to the recovery several times, but only used the ADB method to access it, and I've made several backups too.
However, one thing that happened today has frustrated me completely. Long story short, I thought about making a backup again, although this time, I used the power keys to get to the recovery instead of the ADB method, backup completes successfully, nothing wrong just yet, but just as I tap on 'Reboot System Now', it boots back in to recovery.
I've tried everything, tried using all the ADB commands, even going through all the options in the recovery, but it always seems to boot back in to the recovery. Really can't figure out what's happening. Any help would be extremely appreciated.
UPDATE: So I've flashed a KDZ, the Lollipop one using the LG Flash Tool. It's taking a bit too long to start, currently stuck at the U+ Lte logo. I hope it gets fixed.
UPDATE 2: It says Android is upgrading, YES YES!!!!! This is so exciting, but I'm still not convinced.
With most of cwm version after 6.4.7, any time you use power + volume up to access the recovery, you will get the boot loop. Go here and down load the zip file from the first post. Flash the zip and you should be go to go.
http://forum.xda-developers.com/showthread.php?t=2619403
Hi, I don't usually ask for help, because I can easily find the answer in Google, but this time I made an exception because I couldn't find a solution to this error.
There is a funny story about it, I updated to Lollipop 5.0.2 right after I got my tab, then I found KingRoot and rooted it, but then I noticed my tab was slowing down with it installed so I changed to SuperSU using a script, after that I decided that I wanted CM on this tab, I've found it, after I flashed the recovery and tried to restart into the recovery it appears this message (error : boot certification verify) above the LG logo.
Summarizing all that, I was an idiot and flashed a recovery AFTER I updated to 5.0.2 ?
The V410 can be downgraded to kitkat using the method in the linked thread, it is a long read. The kdz you have to use messes up aboot and internal storage, so it is a pretty long and involved process to get everything back to normal.
http://forum.xda-developers.com/g-pad-10/general/tutorial-lg-gpad-v410-5-1-to-4-4-t3232150
Greydus said:
Hi, I don't usually ask for help, because I can easily find the answer in Google, but this time I made an exception because I couldn't find a solution to this error.
There is a funny story about it, I updated to Lollipop 5.0.2 right after I got my tab, then I found KingRoot and rooted it, but then I noticed my tab was slowing down with it installed so I changed to SuperSU using a script, after that I decided that I wanted CM on this tab, I've found it, after I flashed the recovery and tried to restart into the recovery it appears this message (error : boot certification verify) above the LG logo.
Summarizing all that, I was an idiot and flashed a recovery AFTER I updated to 5.0.2
Click to expand...
Click to collapse
I just did the same thing (similar, after installing supersu for root, not remembering CM root is built in).
All I had to do to recover was:
1. Boot into recovery mode manually. Press volume down, then power and hold both, release the power button when the LG logo comes up, then instantly press the power and volume up buttons and hold (so now you are holding all 3 buttons). Just use volume down and power to select yes twice.
2. Once in recovery, I was able to flash an older CM13 rom/image I had (not even a stock one), booted, then just flashed my CM14.1 back, with its gapps, whip dalvik cache.
3. Reboot - when it asks to install supersu do not install option doesn't work, but the install option fails and it reboots for me.
Good to go.
I've got v-410 rooted in 5.0.2. Do I have to downgrade to KK in order to flash twrp (so I can go to another rom)?