Related
i updated it to modaco 6.2.2, don't know why but did a factory reset in the settings menu. it deleted everything. only left with twrp folder, still able to get into recovery. tried reflashing modaco zip, but says unable to open zip.
can i flash a stock rom?
Yes you should probably flash something. That's why you always make a backup
Sent from my Kindle Fire using xda premium
pete_kowalski83 said:
Yes you should probably flash something. That's why you always make a backup
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
made a backup and it erased that too. just tried cm7 with no success. will keep trying.
Ok, This happened to me on my DHD, Try to fastboot a recovery and flash it. Use the one doomlord made then Flash. BUT before you do that make sure to have the update on your sdcard.
every zip i tried says installed then when u reboot system it goes directly back twrp
nitty917 said:
every zip i tried says installed then when u reboot system it goes directly back twrp
Click to expand...
Click to collapse
I was in the same situation last month. The only solution for me was to flash the stock ROM and start over from scratch.
worldwidepmp said:
I was in the same situation last month. The only solution for me was to flash the stock ROM and start over from scratch.
Click to expand...
Click to collapse
where did you find the stock roms?
Im looking for a pre rooted one, the 6.2.2 link seems heavy traffic
nitty917 said:
where did you find the stock roms?
Im looking for a pre rooted one, the 6.2.2 link seems heavy traffic
Click to expand...
Click to collapse
I followed these instructions http://forum.xda-developers.com/showpost.php?p=20438599&postcount=1 I've never tried it with a pre-rooted ROM, so YMMV. Like I said I flashed this and started the root process over from scratch and this is what worked.
worldwidepmp said:
I followed these instructions http://forum.xda-developers.com/showpost.php?p=20438599&postcount=1 I've never tried it with a pre-rooted ROM, so YMMV. Like I said I flashed this and started the root process over from scratch and this is what worked.
Click to expand...
Click to collapse
thanks back to stock. will be more careful now.
worldwidepmp said:
I was in the same situation last month. The only solution for me was to flash the stock ROM and start over from scratch.
Click to expand...
Click to collapse
NOT TRUE. You are just stuck in recovery mode. View the thread for how to get out. I would post a link but I'm mobile..
Sent from my myTouch_4G_Slide using XDA App
jmcoffey said:
NOT TRUE. You are just stuck in recovery mode. View the thread for how to get out. I would post a link but I'm mobile..
Sent from my myTouch_4G_Slide using XDA App
Click to expand...
Click to collapse
??? You sure you're in the right thread?
too late anyways, I'm on 6.2.2 and having a hell of time to root with a mac.
worldwidepmp said:
??? You sure you're in the right thread?
Click to expand...
Click to collapse
absolutely right:
adb shell su -c "idme bootmode 4000"
adb reboot
done
Last evening I attempted to flask Binary Bishop's JB 4.1.1. 7/30 build. Nuts! I followed the flashing instructions exactly and I am bootlooping at the CM9 screen. Are there any other steps/alternate methods to try to push this through? I'm assuming the answer is "bad download", but, I don't understand what that means exactly when I d/l'ed from the OP? Using CW non-touch recovery. 3 questions: is there any distinct advantage as far as integrity of the build by using the Goo app on the phone versus from the XDA website and then putting it on the phone, and, if I were to use the "Settings/Factory data reset" versus the one in CWM Recovery, what does it do differently? When it says at the bottom "erases all data on phone", how is that different than what factory reset in CWM does, as a practical matter? Is the TWRP recovery any more reliable for what I am trying to do? This just makes no sense that it bootloops when I am doing everything exactly as the OP says to!!!
Did you try dark side cache wipe?
Sent from my SAMSUNG-SGH-T989 using xda premium
born2gethard said:
Did you try dark side cache wipe?
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Yes, many times over, for whatever reason it's just not doing it. But, thanks for the response...
wbexpress said:
3 questions: is there any distinct advantage as far as integrity of the build by using the Goo app on the phone versus from the XDA website and then putting it on the phone,
Click to expand...
Click to collapse
Technically no. Are you checking the md5sum of the files you download? If the answer is no, you should be. If you use the Goo.im app it will automatically check them for you when it finishes downloading. Just because you are downloading from the recommended source does not mean that the file cant be corrupted during the download. Goo.im checks the md5sum for you when you go through the app.
bFORTIFIED said:
Technically no. Are you checking the md5sum of the files you download? If the answer is no, you should be. If you use the Goo.im app it will automatically check them for you when it finishes downloading. Just because you are downloading from the recommended source does not mean that the file cant be corrupted during the download. Goo.im checks the md5sum for you when you go through the app.
Click to expand...
Click to collapse
Yes, thank you, I am using the GOO app on the phone to download the ROM. The MD5 is good. I am just beyond baffled as to why I cannot get thid damned thing to boot up. Would you be able to share exactly what steps you did to get yours going. All things being equal, it just makes no sense. I odin'ed back to stock, redid everything exactly as the OP says and it just will not boot, no matter what I do or wipe. PS: I'm using TWRP 2.2 recovery now. Doesn't seem to matter what I do.
Edit: Just switched back to CWM, followed the OP instructions to a "t", no go!!!
Edit: Just tried both the "Unofficial" and "Experimental" CM10 builds, still no go. WTF!!!??? Why can I get AOKP to boot alll the time? I "get" that it is JB, but the damn thing should either boot all the time or never boot, correct? (I'm sure it's not quite that simple.)
bFORTIFIED said:
Technically no. Are you checking the md5sum of the files you download? If the answer is no, you should be. If you use the Goo.im app it will automatically check them for you when it finishes downloading. Just because you are downloading from the recommended source does not mean that the file cant be corrupted during the download. Goo.im checks the md5sum for you when you go through the app.
Click to expand...
Click to collapse
How can i check if the md5 sums are correct if i have downloaded it from xda website from computer ?
Sent from my GT-S5830 using xda premium
Manvendra05 said:
How can i check if the md5 sums are correct if i have downloaded it from xda website from computer ?
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
I dono I dont know what OS you are using. For linux... md5sum /path/to/file/foo.zip
For windows search.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Manvendra05 said:
How can i check if the md5 sums are correct if i have downloaded it from xda website from computer ?
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
Just search PC md5sum checker there are tons of them out there ..
flashed miui.us rom clockwork and after 30 mins its still showing splash screen,
i booted into recovery and when tride to mount usb storage i keep getting error,
i have no sd card to load with.
please tell me this is fixable...
thanks \
josh
If worse comes to worse there is a guide on how to flash back to stock rom and then start from the start. Re-rooting and reflashing etc etc.
got it to revert.
thing is any rom i flash it gets stuck in splach screen and never boots up even after an hour.
\
any suggestions?
You can try flashing a new clockwork recovery or maybe update it?
Jyjieng11 said:
You can try flashing a new clockwork recovery or maybe update it?
Click to expand...
Click to collapse
is there a 4ext recovery for this device? or twrp?
tried to update and flash cwm and still stuck on splash
thanks
Just go into the too manager app and go into the menu and click install openrecoveryscript to install twrp
Sent from my SGH-T989 using xda app-developers app
abhi08638 said:
Just go into the too manager app and go into the menu and click install openrecoveryscript to install twrp
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
i used goomanager app and it had none of those options
im more curious as to why i cant get past splash screen no matter what rom i try. just want a nice stable cyanogen without touchwiz
juustnoticed that i was on gb...wold that possibly be the problem?
any word.
Sent from my SGH-T989 using xda premium
Spastic909 said:
any word.
Click to expand...
Click to collapse
Menu=left capacitive button. Press that in GooManager and you will see the open recovery option.
got twrp installed. but still having the issue of no rom booting after 30 mins plus...any ideas?
Factory Reset with Odin
http://forum.xda-developers.com/showthread.php?t=1513359
Hi guys, longtime lurker but I've been active on Android Central. Not a noob when it comes to flashing roms, but I think I did something wrong today when trying to flash liquid smooth, coming from cm10.1. Can someone please help me, PM me and I can get a chat or phone call started?
Please and thank you.
Please tell us what you did, and what the phone is doing? Can you get into custom recovery or download mode?
Sent from the future via Tapatalk 4
Ok. So I was running CM10.1 RC4 I think, and running TWRP 2.4 or something around that version. I downloaded the latest liquidsmooth apk, gapps, and BMS kernel. Wiped cache, dalvik, the rom and system. Then I kept getting this error while wiping:
E:error not a directory
error opening "/data/lost+found
Then I flashed liquidsmooth, gaps 3/1/2013, and BMS and restarted. What was weird was The rom flashed ok and I think the kernel was fine, but I had no gapps upon booting into liquid smooth. Redid the wiping process and installing process, same result. Started googling how to fix the error I was getting and someone recommended wiping the data.
So I wiped my data. A big red triangle showed up and I thought I was doing the right thing. When I try to boot my phone, its stuck on the "Samesung Galaxy S3" screen. I try to go into recovery mode, but all that shows up is the TWRP splash screen and then my phone reboots into the bootloop.
I'd appreciate any help, I know i screwed up here.
Edit: I can get into download mode evidently, and it shows my binary count as 1.
Ok so your saying you can not boot into TWRP?
Edit: do not panic, the fact that you get to the Samsung screen is good, you are not bricked.
If you can not successfully boot into TWRP power the phone off and do power+volume down +home at the same time and see if you can get into download mode? If you can then you will need a computer and we can reflash to stock.
Sent from the future via Tapatalk 4
edfunkycold said:
Ok so your saying you can not boot into TWRP?
Edit: do not panic, the fact that you get to the Samsung screen is good, you are not bricked.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
I can't get into TWRP. All that shows is the splash screen and then reboots. So I cant get to any of the wiping/installing options.
I think you just formated everything, as long as it still boots up, try reflashing TWRP, then try flashing again
Sent from my Nexus 4 using xda app-developers app
whisper13 said:
I think you just formated everything, as long as it still boots up, try reflashing TWRP, then try flashing again
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
How would I reflash TWRP?
If you can get into download mode you can use odin to return to stock using these files http://www.sxtpdevelopers.com/showthread.php?t=233
Real simple. Then you would just reflash your custom recovery and root your phone again.
Sent from the future via Tapatalk 4
Would using this guide be better?
Next time don't flash the ROM, the gapps and the kernel all at once.
Make sure you flashed the 3.4 kernel as well. If you downloaded the 3.0 ... You soft bricked your phone. Its fixable.
---------- Post added at 02:47 PM ---------- Previous post was at 02:44 PM ----------
@xplode196
xxStarbucksxx said:
Next time don't flash the ROM, the gapps and the kernel all at once.
Make sure you flashed the 3.4 kernel as well. If you downloaded the 3.0 ... You soft bricked your phone. Its fixable.
---------- Post added at 02:47 PM ---------- Previous post was at 02:44 PM ----------
@xplode196
Click to expand...
Click to collapse
Oh I wasn't aware I wasn't supposed to do that. I mean generally I never do that, it was just this once. How should I flash things the right way? And yeah it was the 3.4 kernel.
xplode196 said:
Oh I wasn't aware I wasn't supposed to do that. I mean generally I never do that, it was just this once. How should I flash things the right way? And yeah it was the 3.4 kernel.
Click to expand...
Click to collapse
Wipe/factory
Wipe Dalvik
Wipe cache
Flash ROM/gapps.
Set your phone settings to the way you prefer. Always let it set for about 5 minutes. Make a back up.
THEN flash kernel, giving that its flash able, which BMS is. Let kernel set for about 5 minutes as well and tweak and tinker as you please.
xplode196 said:
Would using this guide be better?
Click to expand...
Click to collapse
Idk that thread is over a year old. If you want outdated stuff.
Sent from the future via Tapatalk 4
edfunkycold said:
Idk that thread is over a year old. If you want outdated stuff.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
Okay everythings working, rooted and stuff. But the persistent problem is when I try to wipe stuff in recovery it says:
E:error: no such file or directory
E: error opening '/data/lost+found'
xplode196 said:
Okay everythings working, rooted and stuff. But the persistent problem is when I try to wipe stuff in recovery it says:
E:error: no such file or directory
E: error opening '/data/lost+found'
Click to expand...
Click to collapse
Go download GooManager app and update your TWRP version.
Sent from the future via Tapatalk 4
xplode196 said:
Okay everythings working, rooted and stuff. But the persistent problem is when I try to wipe stuff in recovery it says:
E:error: no such file or directory
E: error opening '/data/lost+found'
Click to expand...
Click to collapse
You're most likely getting that when doing a Dalvik wipe. Just continue to wipe you're dalvik cache. And everything else before flashing your new ROM.
I put TWRP Recovery on my LS970 and tried flashing the Liquid Jelly Bean ROM on and it ended up with just pure stress. Before I flashed it I had wiped the dalvik and normal cache and even factory reset it before flashing and it said it installed correctly. I restarted my phone (and I do have an unlocked boot loader and recovery of course) and it was stuck on the Google unlocked boot picture. I tried flashing it again and Ive used LGNPST and LG Flashtool and none helped. I was wondering if there is a possible solution to this perhaps I could send a flashable zip through my computer? Please help
ETR174 said:
I put TWRP Recovery on my LS970 and tried flashing the Liquid Jelly Bean ROM on and it ended up with just pure stress. Before I flashed it I had wiped the dalvik and normal cache and even factory reset it before flashing and it said it installed correctly. I restarted my phone (and I do have an unlocked boot loader and recovery of course) and it was stuck on the Google unlocked boot picture. I tried flashing it again and Ive used LGNPST and LG Flashtool and none helped. I was wondering if there is a possible solution to this perhaps I could send a flashable zip through my computer? Please help
Click to expand...
Click to collapse
So do you have recovery or fastboot now? If you LGNPST you should be locked and have stock recovery.
Sent from my LG-LS970 using XDA Premium 4 mobile app
engine95 said:
So do you have recovery or fastboot now? If you LGNPST you should be locked and have stock recovery.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It has TWRP recovery and has fastboot. When I try LGNPST its stuck at 1% and it says verifying files. I waited 30 minutes and it was still there.
ETR174 said:
It has TWRP recovery and has fastboot. When I try LGNPST its stuck at 1% and it says verifying files. I waited 30 minutes and it was still there.
Click to expand...
Click to collapse
Do you have any other roms on your SD? If not, try to adb sideload a stockish ROM. Adb sideload is on first page of this. http://forum.xda-developers.com/showthread.php?t=2082084
Edit. Have you tried reflashing your ROM? This time wipe system, dalvic, cache, and data. NOT INTERNAL data. That's your SD.
Sent from my LG-LS970 using XDA Premium 4 mobile app
engine95 said:
Do you have any other roms on your SD? If not, try to adb sideload a stockish ROM. Adb sideload is on first page of this. http://forum.xda-developers.com/showthread.php?t=2082084
Edit. Have you tried reflashing your ROM? This time wipe system, dalvic, cache, and data. NOT INTERNAL data. That's your SD.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I only have that and GApps. And for adb you have to have usb debugging on right? I dont.
ETR174 said:
I only have that and GApps. And for adb you have to have usb debugging on right? I dont.
Click to expand...
Click to collapse
You'd said you had liquid installed and LGNPST failed, so liquid should still be installed. So in recovery, wipe those 4, flash liquid then gapps and see if it works. Then we'll go from there.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Ok. Ill give you pictures of the end processes too.
Edit: Well I cant give you pictures but I wiped the four and my phone is stuck on the Google unlocked boot.
ETR174 said:
Ok. Ill give you pictures of the end processes too.
Edit: Well I cant give you pictures but I wiped the four and my phone is stuck on the Google unlocked boot.
Click to expand...
Click to collapse
So you did the wipes, installed liquid, installed gapps, then rebooted and are stuck. Do you have ADB installed? If so DL this TWRP. http://www.androidfilehost.com/?fid=22909751817929287.
Extract the recovery image using 7zip.
Boot your phone into fastboot/bootloader Then cd to the folder the image is in. Then issue this command.
"fastboot flash recovery recovery.img"
You may need to do this first. "fastboot erase recovery" then "fastboot flash recovery recovery.img"
If your not comfortable doing this, just google fastboot and you'll find info on how to do it. This thread seems pretty thorough. http://forum.xda-developers.com/showpost.php?p=41374534&postcount=1
Then go here, http://forum.xda-developers.com/showpost.php?p=36270473&postcount=1 to ADB sideload a Stockish Rom
If this doesn't work then you'll probably end up having to use LGNPST
engine95 said:
So you did the wipes, installed liquid, installed gapps, then rebooted and are stuck. Do you have ADB installed? If so DL this TWRP. http://www.androidfilehost.com/?fid=22909751817929287.
Extract the recovery image using 7zip.
Boot your phone into fastboot/bootloader Then cd to the folder the image is in. Then issue this command.
"fastboot flash recovery recovery.img"
You may need to do this first. "fastboot erase recovery" then "fastboot flash recovery recovery.img"
If your not comfortable doing this, just google fastboot and you'll find info on how to do it. This thread seems pretty thorough. http://forum.xda-developers.com/showpost.php?p=41374534&postcount=1
Then go here, http://forum.xda-developers.com/showpost.php?p=36270473&postcount=1 to ADB sideload a Stockish Rom
If this doesn't work then you'll probably end up having to use LGNPST
Click to expand...
Click to collapse
Thanks but I really dont understand adb. What needs to happen on the phone end in order to use adb? And for the computer?
ETR174 said:
Thanks but I really dont understand adb. What needs to happen on the phone end in order to use adb? And for the computer?
Click to expand...
Click to collapse
Read that link above and it explains adb and fastboot
But if you're not comfortable with that then just LGNPST
Go to the teeny bin thread under "Additional info" and follow the LGNPST walkthru.
engine95 said:
Read that link above and it explains adb and fastboot
But if you're not comfortable with that then just LGNPST
Go to the teeny bin thread under "Additional info" and follow the LGNPST walkthru.
Click to expand...
Click to collapse
Oh I forgot to mension that I did flash teeny bot with LGNPST but this cane with the SBL. Should I download a different version and try flashing again with LGNPST?
ETR174 said:
Oh I forgot to mension that I did flash teeny bot with LGNPST but this cane with the SBL. Should I download a different version and try flashing again with LGNPST?
Click to expand...
Click to collapse
Ok now we're getting somewhere.
When you used teeny bins, it installed the wrong version of TWRP to use with KK Roms. In your recovery is the version 2.6.0.0?
The easiest way to change that recovery is to use fastboot and install a KK version 2.6.3.3. You can find those in the TWRP thread or the root guide under Working recoveries.
You can also use CWM recovery if you want
So follow what is posted above, install a KK recovery, then you should be able to install Liquid.
engine95 said:
Ok now we're getting somewhere.
When you used teeny bins, it installed the wrong version of TWRP to use with KK Roms. In your recovery is the version 2.6.0.0?
The easiest way to change that recovery is to use fastboot and install a KK version 2.6.3.3. You can find those in the TWRP thread or the root guide under Working recoveries.
You can also use CWM recovery if you want
So follow what is posted above, install a KK recovery, then you should be able to install Liquid.
Click to expand...
Click to collapse
I mean I used Freegee to unlock the bootloader and install TWRP Version 2.6.0.0 and from what it sounds like there is a lot of problems with it. Could I flash CWM or a newer version of TWRP with LGNPST?
If you use LGNPST you'll be back to Factory stock. Recovery included. There's no way to install another recovery until to root/unlock
Sent from my LG-LS970 using XDA Premium 4 mobile app
engine95 said:
If you use LGNPST you'll be back to Factory stock. Recovery included. There's no way to install another recovery until to root/unlock
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well do you know any reason why it stays at 1% verifing files? Or any fixes to it?
ETR174 said:
Well do you know any reason why it stays at 1% verifing files? Or any fixes to it?
Click to expand...
Click to collapse
Are you selecting the right DLL? Using either ZVB or ZVC bin?
Other than that, I don't know. Maybe you need to uninstall then reinstall the LG drivers or LGNPST.
Sent from my LG-LS970 using XDA Premium 4 mobile app
engine95 said:
Are you selecting the right DLL? Using either ZVB or ZVC bin?
Other than that, I don't know. Maybe you need to uninstall then reinstall the LG drivers or LGNPST.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I dont know let me go check. I thought it had something to do with the phone not the dll or bin files.
It must be the bin file because I flashed teeny bin just fine with the dll
Im an idiot. Turns out that the firmware was in a cab file which was supposed to be extracted into a bin file. It got deleted to I downloaded a stock bin from your android file host profile and Im going to flash in just a minute and tell you the results.
ETR174 said:
Im an idiot. Turns out that the firmware was in a cab file which was supposed to be extracted into a bin file. It got deleted to I downloaded a stock bin from your android file host profile and Im going to flash in just a minute and tell you the results.
Click to expand...
Click to collapse
No worries. I can't remember where that bin file gets extracted to, but if you're downloading the bin that's fine too. I forgot to mention that ZVC is the most current, but if you have ZVB that's fine if you're gonna run CM/AOSP
Sent from my LG-LS970 using XDA Premium 4 mobile app