Related
Here's the rundown:
I installed the Dark Paranoid Android (Grouper) ROM this morning. I flashed Gapps, and rebooted the device. No issues at that point, because I came from another ROM I did a clean install and got through the registration screens no problem. Once at the home screen, I remembered I had not flashed the Trinity (Grouper) kernel like I had planned, so I rebooted to recovery and flashed it.
That's when I ran into problems. Rebooted device and it stuck at the Google screen. Tried to bootloader into recovery, I still get stuck at the Google screen. Have tried to boot up both the recovery and into Android several times from bootloader, but I always get stuck at the Google screen. I guess my device didn't like the kernel, or somehow installing it damaged my recovery maybe?
Basically, I am asking if I am soft-bricked and have to restore factory and therefore wipe the device clean. Doing that would suck, but it's better than not having the device.
Also, I'd like to know if it's possible to flash stock through the Wugfresh toolkit without removing root. I just want to get back to stock so I can reinstall the ROM and try a different kernel.
liquid150 said:
Also, I'd like to know if it's possible to flash stock through the Wugfresh toolkit without removing root. I just want to get back to stock so I can reinstall the ROM and try a different kernel.
Click to expand...
Click to collapse
Try to wipe everything and reinstall
kinhbang1989 said:
Try to wipe everything and reinstall
Click to expand...
Click to collapse
Impossible with my device in the state I described.
Since the answers were fairly slow I already flashed factory image from Google with the toolkit. Issue was resolved, just will take a while to get everything put back on it.
Sent from my Paranoid Galaxy Nexus
Did you check the md5 on the kernel download? If there wasn't an md5 supplied, download the file a few times and compare the md5's between them for consistency. Could've been as simple as a bad download.
mustbepbs said:
Did you check the md5 on the kernel download? If there wasn't an md5 supplied, download the file a few times and compare the md5's between them for consistency. Could've been as simple as a bad download.
Click to expand...
Click to collapse
I did not check it. Maybe I will try it again later. Was able to right the problem by using the Nexus Toolkit to flash 4.1.2. Then I put DarkPA on it and started over. Not really the end of the world, just slightly time consuming.
I love the Trinity kernel on my phone. I want to use one for Nexus but I didn't see a stable one yet, all are in experimental phase.
Sent from my Paranoid Galaxy Nexus
This is my FINAL VERSION of my Idiots Guide for the HP Touchpad. Now that a stable enough version of CM10 is available, I finally created a guide for you.
Here are links to the files you will need:
CM10 03/04/2012 Build
GAPPS 10/11/2012
ACMEInstaller3
Moboot 3.8
Anything else that you might need, you'll find on http://www.reverendkyle.com
Thanks for the video. It came just in time as I just purchased a used TP that had an older version of android ICS already on it and I wanted to upgrade but seeing as how this is the first device I have sort of inherited already rooted, it is hard to just jump in and know everything that I would have learned from the beginning like i did with my previous phones.
Anyways, I did everything you said except I used the newest AOKP rom. But my tp is still booting to the older version of android that I had on it. Any ideas? Feel free to pm me if you prefer that.
aujbman said:
Thanks for the video. It came just in time as I just purchased a used TP that had an older version of android ICS already on it and I wanted to upgrade but seeing as how this is the first device I have sort of inherited already rooted, it is hard to just jump in and know everything that I would have learned from the beginning like i did with my previous phones.
Anyways, I did everything you said except I used the newest AOKP rom. But my tp is still booting to the older version of android that I had on it. Any ideas? Feel free to pm me if you prefer that.
Click to expand...
Click to collapse
If the AOKP ROM is using a unique uImage file, then you may see two different entries on your moboot screen for two different Android builds.
What does your moboot menu have in it?
Maybe your install failed. Try downloading and flashing it again. If you're trying AOKP JB, you should wipe both /data and dalvik cache to avoid a boot loop!
If using AcmeInstaller3 remember to rename the ROM with ”update-” at the beginning so that it looks like update-AOKPJB_UnOfficial.zip
Sent from my SAMSUNG-SGH-T989 using xda premium
-SGA- said:
Maybe your install failed. Try downloading and flashing it again. If you're trying AOKP JB, you should wipe both /data and dalvik cache to avoid a boot loop!
If using AcmeInstaller3 remember to rename the ROM with ”update-” at the beginning so that it looks like update-AOKPJB_UnOfficial.zip
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
I believe it was the "update-" thing that was keeping it from updating. I followed another video tutorial which provided files that had the "update" in front of them and it worked.
I haven't tried yet but now that it worked will the regular method of wiping and flashing through recovery work? (Like, if I want to try out different JB Roms) Are there any files that need to be in a particular place for the recovery method to work? I tried that method first and it would never take, would always revert back to the original version. Don't know if, because I just jumped in and haven't been here from the beginning, I am just missing a necessary step that is hardly even talked about anymore.
Love your work Rev! Thank you again for everything that you do!
Update went like clockwork, unfortunately I can't seem to get the camera to work (not a terrible loss, but I was sorta excited to see it actually working with this release).
Jubmasterflex said:
Love your work Rev! Thank you again for everything that you do!
Update went like clockwork, unfortunately I can't seem to get the camera to work (not a terrible loss, but I was sorta excited to see it actually working with this release).
Click to expand...
Click to collapse
I can attest to the improved battery life on this cm10 build. Amazingly, it holds battery life when it's sleeping now.
Thank you so much for taking the time in making the video for us. Your instructions are easy to follow, hard for anyone to mess up.
(The hosting site for the files is not working, not sure if you were aware)
Hi, I have CM9 running on my TP. With the latest release, the camera works great. But before updating it to CM10, I'd like to know about the issues currently in this build.
Thanks.
Where does one go when the goo.im site appears down, to get the needed files? Mirror somewhere?
ljderm said:
Where does one go when the goo.im site appears down, to get the needed files? Mirror somewhere?
Click to expand...
Click to collapse
Don't go for external mirrors unless some recognized developer suggests them. Best will be to wait for goo.im to come up again, being a prime site, it won't be down for long.
The goo servers do appear to go down on occasion. They always come back up a bit later.
Problem with installing GAPPS using ACMEInstaller3
Excellent tutorial for an idiot like me. Thanks for again for the guide! Question:
I followed the instructions step by step and was able to get CM10 installed successfully. However, I wasn't able to get GAPPS installed using this method. From researching I understand sometimes there is a problem installing GAPPS through ACMEInstaller3 and one can simply get GAPPS installed through CWM Recovery. However, I would like to use/have TWRP instead so is there a way to get GAPPS installed properly through ACMEInstaller3 and then I can install TWRP through GooManager?
Alternatively, is there a way to install GAPPS without using CWM Recovery?
Or, I guess I can install CWM Recovery first, then install TWRP Recovery, then remove CWM Recovery while keeping TWRP and not go back to the stock Recovery? I tried to search the forums and wasn't able to find instructions on removing CWM Recovery WHILE still keeping CM10 and not go back to the Stock recovery.
Any help would be much appreciated. Thanks in advance for your help.
@reverendkjr - appreciate your videos. they're awesome. definitely helped me (and several other friends) many times and saved a ton of time. super easy to follow.
Yes you can install TWRP normally, flash gapps in CWM then install goomanager app, open and click the 3 dot menu and install custom recovery script then it will install it
Now using a root file manager go to the directory called boot and delete uimage.cwm.img (this is from memory but still should be correct
Sent from my cm_tenderloin using XDA Premium HD app
waynekirby said:
Yes you can install TWRP normally, flash gapps in CWM then install goomanager app, open and click the 3 dot menu and install custom recovery script then it will install it
Now using a root file manager go to the directory called boot and delete uimage.cwm.img (this is from memory but still should be correct
Sent from my cm_tenderloin using XDA Premium HD app
Click to expand...
Click to collapse
Dumb question. I had dual boot installed with moboot and one day my dumbarse clicked erase SD card.well it did...EVERYTHING accept twrp. I successfully reinstalled webos and installed preware. Its actually pretty cool.its like a fledgling play store for webos. Now....where should i go from here.i no longer think twrp is on it. All i have is webos with preware.sorry if this is newbie
Sent from my Galaxy Nexus using xda premium
Crwolv said:
Dumb question. I had dual boot installed with moboot and one day my dumbarse clicked erase SD card.well it did...EVERYTHING accept twrp. I successfully reinstalled webos and installed preware. Its actually pretty cool.its like a fledgling play store for webos. Now....where should i go from here.i no longer think twrp is on it. All i have is webos with preware.sorry if this is newbie
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
My goodness you have forgotten everything, you will need to install acmeuninstaller 3, moboot, CMW and the rom you want along with the relevant gapps. Sounds complicated this thread will make it easy
http://forum.xda-developers.com/showthread.php?t=2147284 and has all the necessary links. Have fun.
Sent from my Transformer Prime TF201 using Tapatalk 2
Heck ya i did lol. That refreshed my memory instead of a long video. Thank yo very much
Awesome!
Sent from my cm_tenderloin using xda app-developers app
Great vid!! Finally got CM10 on my Touchpad.
I panicked and probably did something quite stupid...
So I tried to flash the new cyanogenmod rom to have a taste of kit kat, but then I had the status 7 error.
This never occurred to me before, I didn't keep a backup to fall back onto... ( yes, I am an idiot, I learned my lesson, the hard way)
Than the device won't boot, it shows the Google logo twice, and then goes into the clockwork mod, where you choose to flash roms
and I am stuck.
I tried Nexus Root Toolkit, doesn't help because my device is not booting up, no way can it install the drivers properly...
and I think I did something more ingenious... I just tried anything on the Toolkit, and I got my rooted Nexus 7 locked...
But it's still the same, I am stuck at the clockwork mod thing just as before... Wiped whatever I can. and even formatted the sdcard and system...
Some Android Wizard out there... Please help...
If at boot you go to recovery directly... You have had to flash new version of recovery in wrong partition. You must flash it last version of recovery with "fastboot flash recovery yourrecovery.IMG" (see 'recovery' as partition to flash). Then flash boot and system partitions from factory image (in XDA have you multiples threads about it) if you want to keep your data. If not, flash factory image from usual ways (this wipes your data) and then flash recovery like I say above.
After that, try to flash CM again.
PS: I recommend TWRP instead of CWM.
Sent from my Nexus 7 (grouper) using Tapatalk.
but its more serious than that... My computer doesnt recognize the tablet because of some driver issues... I am not sure, at this moment, whether the USB debugging thing still works
i can only get to the clockwork mod page, bootloader and thats it.
I cant flash anything, I cant transfer files from the PC to tablet....
please, please help.
bump!,
Im in a similar boat. I bricked my tablet while trying to force an update. It wouldnt autoupdate (there was always an error about cant find zip file...) so I tied to install it with Skipsoft program. After 20 minutes i realize my computer has frozen....So I waited 2 hours and nada. So I had to reboot my desk top. At that time my tablet is now bricked....what do we do?
Vishnuisgod said:
bump!,
Im in a similar boat. I bricked my tablet while trying to force an update. It wouldnt autoupdate (there was always an error about cant find zip file...) so I tied to install it with Skipsoft program. After 20 minutes i realize my computer has frozen....So I waited 2 hours and nada. So I had to reboot my desk top. At that time my tablet is now bricked....what do we do?
Click to expand...
Click to collapse
hello friend.
1. we can pray
2. i think we have to look at some software that can do something more "fundamental" than wugus nexus tool kit, and communicate with the tablet
i am just guessing, i crashed my tablet, so....
dangercl0se said:
hello friend.
1. we can pray
2. i think we have to look at some software that can do something more "fundamental" than wugus nexus tool kit, and communicate with the tablet
i am just guessing, i crashed my tablet, so....
Click to expand...
Click to collapse
I think I got it!!!!!!!!!!
using the skipsoft,
first i did option 1, install usb settings; then
I used option #6 force recovery.. I think i did stock rom.
now Im update with kitkat and it updating to 4.4.2
Vishnuisgod said:
I think I got it!!!!!!!!!!
using the skipsoft,
first i did option 1, install usb settings; then
I used option #6 force recovery.. I think i did stock rom.
now Im update with kitkat and it updating to 4.4.2
Click to expand...
Click to collapse
hey
can you post links to where u got the stuff?
coz looks like the skipsoft homepage is not working
dangercl0se said:
hey
can you post links to where u got the stuff?
coz looks like the skipsoft homepage is not working
Click to expand...
Click to collapse
it was already on computer....
make sure you look for "android tool kit"....
So this evening decided to go back to CM11 after using stock for a while on my N4. So I downloaded the latest CM11 nightly, along with the latest PA gapps. I did a full wipe in recovery, then flashed CM11, followed by a flash of the gapps. However, it immediately appeared that the gapps file must have been bad (gave me the red exclamation triangle android background). So rebooting leaves me in a endless bootloop. Only problem is I don't have another gapps file saved on my SDcard. And to make matters worse (yeah I know) I didn't nandroid my system prior to this, though I do have everything (apps, etc) saved on my SDcard. Now my problem is, I need to find a way of loading a new gapps file onto my phone. I have tried ADB, but I suspect that as a result of the factory reset I no longer have USB debugging on, as I can't connect to the device in ADB. I am becoming more than a little stressed right now, as I need to get this phone back up and running. Does anyone have any idea what I might do next?? I am not a total newbie to flashing roms, been at it a few years now, but this is the first time I've been stuck like this. Ugh! Please help! :crying::crying::crying:
joeski27 said:
So this evening decided to go back to CM11 after using stock for a while on my N4. So I downloaded the latest CM11 nightly, along with the latest PA gapps. I did a full wipe in recovery, then flashed CM11, followed by a flash of the gapps. However, it immediately appeared that the gapps file must have been bad (gave me the red exclamation triangle android background). So rebooting leaves me in a endless bootloop. Only problem is I don't have another gapps file saved on my SDcard. And to make matters worse (yeah I know) I didn't nandroid my system prior to this, though I do have everything (apps, etc) saved on my SDcard. Now my problem is, I need to find a way of loading a new gapps file onto my phone. I have tried ADB, but I suspect that as a result of the factory reset I no longer have USB debugging on, as I can't connect to the device in ADB. I am becoming more than a little stressed right now, as I need to get this phone back up and running. Does anyone have any idea what I might do next?? I am not a total newbie to flashing roms, been at it a few years now, but this is the first time I've been stuck like this. Ugh! Please help! :crying::crying::crying:
Click to expand...
Click to collapse
Nobody has a suggestion? This isn't looking good...
What is strange to me is, even after doing another factory reset, it still boots to the same CM boot screen and is stuck in a boot loop. I have no idea what is going on here. And at the very least, at least I have everything still on my SDcard (backups of apps in TB, and all my other locally saved stuff...just that now I have no idea of how to get to any of it, or how to load on a working rom & gapps so I can have something to boot to!)
Do a full wipe, flash CM11 without Gapps. It should boot but you won't be able to sign in to google and all that jazz. Just use the browser and download another gapps, then flash it.
Your computer won't detect ADB because ADB is only when android is running. If you're running a sideload-enabled recovery, you can push a zip and flash it through ADB.
exb0 said:
Do a full wipe, flash CM11 without Gapps. It should boot but you won't be able to sign in to google and all that jazz. Just use the browser and download another gapps, then flash it.
Your computer won't detect ADB because ADB is only when android is running. If you're running a sideload-enabled recovery, you can push a zip and flash it through ADB.
Click to expand...
Click to collapse
I've tried this now (wipe, and then flash of CM) and its STILL stuck at the damn CM boot animation. I just don't understand what the problem is here. I have never, ever had something like this happen before. Could it be a bad nightly? And if so, how the hell am I going to get another flashable rom onto my SDcard??
joeski27 said:
I've tried this now (wipe, and then flash of CM) and its STILL stuck at the damn CM boot animation. I just don't understand what the problem is here. I have never, ever had something like this happen before. Could it be a bad nightly? And if so, how the hell am I going to get another flashable rom onto my SDcard??
Click to expand...
Click to collapse
Hmmm, yeah it could be.
1 : Download a ROM. Check the MD5 checksum.
2 : Copy the ROM to your ADB folder and rename it to something easy (eg: Rom.zip)
3 : Fire up CMD, Navigate it to your ADB folder
4 : Boot your phone into recovery, find for a function called "ADB Sideload" or something along those lines.
5 : In CMD, type in "adb sideload *romname*.zip
6 : ??
7 : Enjoice.
This can be done for any type of flashable files.
or yknow. just return back to stock and do everything all again if you're uncomfortable doing this.
exb0 said:
Hmmm, yeah it could be.
1 : Download a ROM. Check the MD5 checksum.
2 : Copy the ROM to your ADB folder and rename it to something easy (eg: Rom.zip)
3 : Fire up CMD, Navigate it to your ADB folder
4 : Boot your phone into recovery, find for a function called "ADB Sideload" or something along those lines.
5 : In CMD, type in "adb sideload *romname*.zip
6 : ??
7 : Enjoice.
This can be done for any type of flashable files.
or yknow. just return back to stock and do everything all again if you're uncomfortable doing this.
Click to expand...
Click to collapse
So I don't know if anything is different, but I am doing this on a Mac running Mavericks. But I do have the latest SDK installed with a fresh download of tools. I am running CMW recovery 6.0.4.3, which does have sideload, and I attempted to use it a moment ago but it didn't work....will try again now...
joeski27 said:
So I don't know if anything is different, but I am doing this on a Mac running Mavericks. But I do have the latest SDK installed with a fresh download of tools. I am running CMW recovery 6.0.4.3, which does have sideload, and I attempted to use it a moment ago but it didn't work....will try again now...
Click to expand...
Click to collapse
Ah, it shouldn't matter that much. Instead of CMD just use terminal(that's what it's called in OSX right?).
didn't work? what error did you get?
joeski27 said:
So I don't know if anything is different, but I am doing this on a Mac running Mavericks. But I do have the latest SDK installed with a fresh download of tools. I am running CMW recovery 6.0.4.3, which does have sideload, and I attempted to use it a moment ago but it didn't work....will try again now...
Click to expand...
Click to collapse
Yeah its not working, just brings up the splash of command prompts that comes up with you don't enter a proper adb command.
joeski27 said:
Yeah its not working, just brings up the splash of command prompts that comes up with you don't enter a proper adb command.
Click to expand...
Click to collapse
Enable sideload on your phone and then try using "adb devices", do you get anything? or random splash of commands again?
exb0 said:
Enable sideload on your phone and then try using "adb devices", do you get anything? or random splash of commands again?
Click to expand...
Click to collapse
No that's what I've been countering the whole time; I have ADB sideload set on the phone, and then after cd'ing my way to the folder with adb, I try "adb devices" and nothing, doesn't see the device at all. WTF?
joeski27 said:
No that's what I've been countering the whole time; I have ADB sideload set on the phone, and then after cd'ing my way to the folder with adb, I try "adb devices" and nothing, doesn't see the device at all. WTF?
Click to expand...
Click to collapse
sounds like a driver issue. You're gonna have to fix that or there's almost no way of fixing your phone :/
Hang on....sideload looks like its working! But I ain't out of the woods yet, won't celebrate til it gets there, AND if it boots...
Now I guess the best bet is to try a fresh rom rather than a fresh gapps, would you say? I'm downloading both now, just wondered which would be my best bet. I mean at this point I just need something that will allow me to boot.'
By the way when a sideload is performed where is the sideloaded file saved? Just wondering where to find it when the time comes to flash.
joeski27 said:
Hang on....sideload looks like its working! But I ain't out of the woods yet, won't celebrate til it gets there, AND if it boots...
Click to expand...
Click to collapse
#prayforjoeski27 goodluck!
---------- Post added at 05:38 AM ---------- Previous post was at 05:37 AM ----------
joeski27 said:
Now I guess the best bet is to try a fresh rom rather than a fresh gapps, would you say? I'm downloading both now, just wondered which would be my best bet. I mean at this point I just need something that will allow me to boot.
Click to expand...
Click to collapse
try flashing a rom without gapps first. if the rom boots then wipe and reflash rom with gapps.
exb0 said:
#prayforjoeski27 goodluck!
---------- Post added at 05:38 AM ---------- Previous post was at 05:37 AM ----------
try flashing a rom without gapps first. if the rom boots then wipe and reflash rom with gapps.
Click to expand...
Click to collapse
Sounds like a plan. This time I'm loading the latest snapshot release of CM rather than the damn nightly, lol. At least we know that that version *should* reliably boot up....and we'll know shortly...going to save the rom to the appropriate folder, rename, and sideload....
joeski27 said:
Sounds like a plan. This time I'm loading the latest snapshot release of CM rather than the damn nightly, lol. At least we know that that version *should* reliably boot up....and we'll know shortly...going to save the rom to the appropriate folder, rename, and sideload....
Click to expand...
Click to collapse
I think all nightlies should boot up (i mean it IS cyanogen mod...). I think you just got a bad download. Remember to check MD5 if it's available!
exb0 said:
I think all nightlies should boot up (i mean it IS cyanogen mod...). I think you just got a bad download. Remember to check MD5 if it's available!
Click to expand...
Click to collapse
WOO HOO! Friggin thing booted, baby! Hello CM welcome screen! Never looked so beautiful!
So now I just need to 1) get a fresh gapps, 2) load it on to my SD via android file transfer, do a fresh wipe in recovery, flash CM again, followed by the fresh gapps, and I should be in business...yes?
joeski27 said:
WOO HOO! Friggin thing booted, baby! Hello CM welcome screen! Never looked so beautiful!
So now I just need to 1) get a fresh gapps, 2) load it on to my SD via android file transfer, do a fresh wipe in recovery, flash CM again, followed by the fresh gapps, and I should be in business...yes?
Click to expand...
Click to collapse
Congrats!
You can try just flashing gapps on top of it, that's what I do. but if you're worried you can do a full wipe and flash it again. Completely up to you!
exb0 said:
Congrats!
You can try just flashing gapps on top of it, that's what I do. but if you're worried you can do a full wipe and flash it again. Completely up to you!
Click to expand...
Click to collapse
Hey thanks a million for the help on this one! Like I said, I've done quite a bit with rom tinkering over the last few years, but sideloading was a first for me tonight. Though it is very good to know for the future! More importantly, however (and this is really not like me) in the future I either A) have to make sure I have enough SD space for nandriods, or B) keep a previous, working zip of a rom on the SD when I go to flash a new one (which is what I have always done but have not recently).
Again, thanks a bunch!!!! :highfive:
joeski27 said:
Hey thanks a million for the help on this one! Like I said, I've done quite a bit with rom tinkering over the last few years, but sideloading was a first for me tonight. Though it is very good to know for the future! More importantly, however (and this is really not like me) in the future I either A) have to make sure I have enough SD space for nandriods, or B) keep a previous, working zip of a rom on the SD when I go to flash a new one (which is what I have always done but have not recently).
Again, thanks a bunch!!!! :highfive:
Click to expand...
Click to collapse
No problem as long as you're willing to learn I'm willing to help! if you ever run into any other problems feel free to PM me. I'll try to help as much as I can. :good:
So I'm pretty desperate and I apologize if similar info was posted somewhere else. I've been researching several hours but couldn't find anything.
I originally installed CM11 and decided to experiment with a different rom TriForce ROM [TouchWiz]. I put the zip file on my SD card and booted into clockworkmod it gave an error of bad zip. I tried different usb port to transfer the zip, downloaded it multiple times with no result. So I decided to try a different rom Stock_Rooted_Deodexed_MF9_Rom.zip. The installation finished but the phone would not boot.
Recently I flashed the stock rom from odin, it finished successfully but still not boot, Galaxy sreen lights up quickly and that's it.
rmngorelov said:
So I'm pretty desperate and I apologize if similar info was posted somewhere else. I've been researching several hours but couldn't find anything.
I originally installed CM11 and decided to experiment with a different rom TriForce ROM [TouchWiz]. I put the zip file on my SD card and booted into clockworkmod it gave an error of bad zip. I tried different usb port to transfer the zip, downloaded it multiple times with no result. So I decided to try a different rom Stock_Rooted_Deodexed_MF9_Rom.zip. The installation finished but the phone would not boot.
Recently I flashed the stock rom from odin, it finished successfully but still not boot, Galaxy sreen lights up quickly and that's it.
Click to expand...
Click to collapse
Restore from nandroid backup. I hope you made one. Try going into recovery do a factory reset and wipe all cache and data and what not and then install a ROM from Odin.
rmngorelov said:
So I'm pretty desperate and I apologize if similar info was posted somewhere else. I've been researching several hours but couldn't find anything.
I originally installed CM11 and decided to experiment with a different rom TriForce ROM [TouchWiz]. I put the zip file on my SD card and booted into clockworkmod it gave an error of bad zip. I tried different usb port to transfer the zip, downloaded it multiple times with no result. So I decided to try a different rom Stock_Rooted_Deodexed_MF9_Rom.zip. The installation finished but the phone would not boot.
Recently I flashed the stock rom from odin, it finished successfully but still not boot, Galaxy sreen lights up quickly and that's it.
Click to expand...
Click to collapse
Make sure you're using roms for your version of your phone. the MF9 bootloader is really old and probably wont install anymore. My phone did this before and I thought I bricked it, but I kid you not I took the battery out and removed the SIM card and rebooted and it booted up just fine. May not work for you, but I suggest you go back to update stock firmware then try again. If you're using the triband model, there's a post around here somewhere with confirmed roms that wont brick your device. I'm currently using the Google Play Edition Stock ROM and it's working GREAT.
Link for new firmware (NG5 Firmware): https://mega.co.nz/#F!0JdRkIZR!AqqKdbvba_Hpg5VrCmrbPw
i7vSa7vi7y said:
Restore from nandroid backup. I hope you made one. Try going into recovery do a factory reset and wipe all cache and data and what not and then install a ROM from Odin.
Click to expand...
Click to collapse
I restored to this stock ROM before and everything worked well. Currently I can't boot into recovery, Samsung flashes once and that's it, that's why I'm desperate the only thing I can do is boot in to download mode for odin.
silentdeath631 said:
Make sure you're using roms for your version of your phone. the MF9 bootloader is really old and probably wont install anymore. My phone did this before and I thought I bricked it, but I kid you not I took the battery out and removed the SIM card and rebooted and it booted up just fine. May not work for you, but I suggest you go back to update stock firmware then try again. If you're using the triband model, there's a post around here somewhere with confirmed roms that wont brick your device. I'm currently using the Google Play Edition Stock ROM and it's working GREAT.
Link for new firmware (NG5 Firmware):
Click to expand...
Click to collapse
Does it matter that I can't get into recovery to clear the cache first before trying new roms?
silentdeath631 said:
Make sure you're using roms for your version of your phone. the MF9 bootloader is really old and probably wont install anymore. My phone did this before and I thought I bricked it, but I kid you not I took the battery out and removed the SIM card and rebooted and it booted up just fine. May not work for you, but I suggest you go back to update stock firmware then try again. If you're using the triband model, there's a post around here somewhere with confirmed roms that wont brick your device. I'm currently using the Google Play Edition Stock ROM and it's working GREAT.
Link for new firmware (NG5 Firmware):
Click to expand...
Click to collapse
Maybe I'm doing something foolish but every time I try to download files from the link you gave I get a decryption error so I can't download them zip or original.
rmngorelov said:
I restored to this stock ROM before and everything worked well. Currently I can't boot into recovery, Samsung flashes once and that's it, that's why I'm desperate the only thing I can do is boot in to download mode for odin.
Click to expand...
Click to collapse
Just hold home power and volume up. Right when you see text at the top left let go. You have to have the right timing
i7vSa7vi7y said:
Just hold home power and volume up. Right when you see text at the top left let go. You have to have the right timing
Click to expand...
Click to collapse
After almost eight hours of troubleshooting I finally got it to work.
I've tried flashing clockworkmod several times to see if I could get into recovery with no result so I gave up on that and I flashed the newest stock rom I could find L720VPUFNG2_L720SPTFNG2_SPR and it was still not booting. Than I thought maybe twerp would make a difference and god almighty it finally booted! I felt as if I gave birth to a child after eight hours of labor!
Now I'm extremely paranoid about touching anything because it took me forever to do this. Does anyone know why flashing twerp would make such a difference? I know this sort of stuff can get extremely complicated but I'd like to try to understand.
I hope my foolish agony contributed to this community if not in any other way except by the comedic relief caused by my ignorance.
rmngorelov said:
After almost eight hours of troubleshooting I finally got it to work.
I've tried flashing clockworkmod several times to see if I could get into recovery with no result so I gave up on that and I flashed the newest stock rom I could find L720VPUFNG2_L720SPTFNG2_SPR and it was still not booting. Than I thought maybe twerp would make a difference and god almighty it finally booted! I felt as if I gave birth to a child after eight hours of labor!
Now I'm extremely paranoid about touching anything because it took me forever to do this. Does anyone know why flashing twerp would make such a difference? I know this sort of stuff can get extremely complicated but I'd like to try to understand.
I hope my foolish agony contributed to this community if not in any other way except by the comedic relief caused by my ignorance.
Click to expand...
Click to collapse
Depends what recovery you had and what version. I personally like Philz touch recovery but TWRP is good. Now wipe and flash a ROM my friend or restore a backup
rmngorelov said:
After almost eight hours of troubleshooting I finally got it to work.
I've tried flashing clockworkmod several times to see if I could get into recovery with no result so I gave up on that and I flashed the newest stock rom I could find L720VPUFNG2_L720SPTFNG2_SPR and it was still not booting. Than I thought maybe twerp would make a difference and god almighty it finally booted! I felt as if I gave birth to a child after eight hours of labor!
Now I'm extremely paranoid about touching anything because it took me forever to do this. Does anyone know why flashing twerp would make such a difference? I know this sort of stuff can get extremely complicated but I'd like to try to understand.
I hope my foolish agony contributed to this community if not in any other way except by the comedic relief caused by my ignorance.
Click to expand...
Click to collapse
im having similar issues. which version of TWRP worked for you?
thank you
fearthemarchx said:
im having similar issues. which version of TWRP worked for you?
thank you
Click to expand...
Click to collapse
I recommend flashing the newest one here using odin
http://teamw.in/project/twrp2
Then once you are able to boot into recovery go to wipe and perform both factory reset and format data. Then install whatever rom you like, I used Sprint Galaxy S4 SPH-L720 VPUFNAE (Androdi 4.4.2) found here
http://galaxys4root.com/galaxy-s4-stock-firmware/ (or maybe find a newer stock rom if this one gives you errors)
Just copy the zip file to the phone, boot into twrp, do wipe factory reset again, select install then select the zip in whatever directory and you should be good to go. Make sure you do a back up in twrp once you get the phone to boot so you can always revert to stock.
I hope I was thorough enough that some of the information was useful. Let me know if you need any more help.
only certain recoveries will stick. ive tried the most recent twrp, with no luck. only a few versions of philztouch work.
Sent from my LGL34C using XDA Free mobile app
fearthemarchx said:
only certain recoveries will stick. ive tried the most recent twrp, with no luck. only a few versions of philztouch work.
Sent from my LGL34C using XDA Free mobile app
Click to expand...
Click to collapse
Format with philztouch that works then try flashing a new stock rom with odin. That should bring everything back to stock including the recovery.
ive tried. when i flash rom via odin i only get a blue "recovery booting" at the top of boot screen. even when i only power on, not into recovery. im going to attempt to flash rom provided in previous post via philz.
Sent from my LGL34C using XDA Free mobile app
fearthemarchx said:
ive tried. when i flash rom via odin i only get a blue "recovery booting" at the top of boot screen. even when i only power on, not into recovery. im going to attempt to flash rom provided in previous post via philz.
Sent from my LGL34C using XDA Free mobile app
Click to expand...
Click to collapse
You're in download mode when you flash from odin right? If you your getting an error flashing, try a different stock rom after reformating/resetting to factory (it's crucial to clear the cache before trying a different rom). I had to try a few roms before I found one that worked.