Related
Hey all,
I RSD'd the other day and then re-rooted and re-unlocked the bootloader (yes, I now know it stays unlocked) and flashed CWM v6.0.1.4 recovery.
Now none of the custom ROMs will boot, though they install correctly in recovery. From CyanogenMod to Carbon to AOSP, it just sits on the boot animation... I've let it sit for up to half an hour.
I'm wiping data and cache, though CWM says E:Can't mount /cache/recovery/pretty-much every subfolder, but that doesn't seem like a big deal...
So what am I doing wrong, here, any ideas? It doesn't matter if I install the ROMs and GAPPS from external SD, right?
I RSD'd to 96.15.66, the one where I can unlock the bootloader, and the only ROM I can get to boot is Clean Rom (basically stock with tweaks of course).
jimmyco2008 said:
Hey all,
I RSD'd the other day and then re-rooted and re-unlocked the bootloader (yes, I now know it stays unlocked) and flashed CWM v6.0.1.4 recovery.
Now none of the custom ROMs will boot, though they install correctly in recovery. From CyanogenMod to Carbon to AOSP, it just sits on the boot animation... I've let it sit for up to half an hour.
I'm wiping data and cache, though CWM says E:Can't mount /cache/recovery/pretty-much every subfolder, but that doesn't seem like a big deal...
So what am I doing wrong, here, any ideas? It doesn't matter if I install the ROMs and GAPPS from external SD, right?
I RSD'd to 96.15.66, the one where I can unlock the bootloader, and the only ROM I can get to boot is Clean Rom (basically stock with tweaks of course).
Click to expand...
Click to collapse
are you mounting system first? never used CWM on this device, but in TWRP, they install just fine. I believe that most devs use TWRP (although, it should not make a difference).
Thanks for the reply, actually I have two cwm recovery images, and after the RSD I flashed the "wrong" one... After flashing the other, I was able to flash and boot just fine.
jimmyco2008 said:
Thanks for the reply, actually I have two cwm recovery images, and after the RSD I flashed the "wrong" one... After flashing the other, I was able to flash and boot just fine.
Click to expand...
Click to collapse
Hi Im not sure if Im having this exact issue but I have been having problem since I used Utility 1.20 and re-rooted and re-unlocked my phone. Every ROM I have tried has random reboot issue. Can you tell me exactly how you did it correctly?
Also I didnt understand the two recovery image concept. I was having safe strap before and had issue with stock partition and was using slot1 partition as daily rom. And I couldnt flash any other ROM. So I had to go back to stock with Utility 1.2 and start over. Right now Im having liquidsmooth ROM with CWM recovery. Still having those reboots.
jcxmej said:
Hi Im not sure if Im having this exact issue but I have been having problem since I used Utility 1.20 and re-rooted and re-unlocked my phone. Every ROM I have tried has random reboot issue. Can you tell me exactly how you did it correctly?
Also I didnt understand the two recovery image concept. I was having safe strap before and had issue with stock partition and was using slot1 partition as daily rom. And I couldnt flash any other ROM. So I had to go back to stock with Utility 1.2 and start over. Right now Im having liquidsmooth ROM with CWM recovery. Still having those reboots.
Click to expand...
Click to collapse
are you sure you uninstalled SS via the app (and not via the android system)?
jco23 said:
are you sure you uninstalled SS via the app (and not via the android system)?
Click to expand...
Click to collapse
I dont think I have uninstalled safestrap with an app. I followed the instruction in this thread.
http://forum.xda-developers.com/showthread.php?t=2238341
This thread was started by me when I had problem with flashing ROMs in the stock slot using safestrap. Rikrong suggested I use Utility so that I go back to stock and start all over again. So I did. I guess thats how it should have been done?
jcxmej said:
I dont think I have uninstalled safestrap with an app. I followed the instruction in this thread.
http://forum.xda-developers.com/showthread.php?t=2238341
This thread was started by me when I had problem with flashing ROMs in the stock slot using safestrap. Rikrong suggested I use Utility so that I go back to stock and start all over again. So I did. I guess thats how it should have been done?
Click to expand...
Click to collapse
what I would suggest doing is going into SS via the app (not via recovery once the phone boots up) and click the uninstall button.
then, return to stock as rik suggested.... then root, then install TWRP, then you'll be able to slap on whatever ROM you like.
jco23 said:
what I would suggest doing is going into SS via the app (not via recovery once the phone boots up) and click the uninstall button.
then, return to stock as rik suggested.... then root, then install TWRP, then you'll be able to slap on whatever ROM you like.
Click to expand...
Click to collapse
Actually I did all that already just not by uninstalling SS. Now Im on CWM recovery. I was on SS one week back and then i followed the instructions by rik. I m having reboots ever since.
jcxmej said:
Actually I did all that already just not by uninstalling SS. Now Im on CWM recovery. I was on SS one week back and then i followed the instructions by rik. I m having reboots ever since.
Click to expand...
Click to collapse
I'm thinking the combination of SS and CWM could be the issue.... try to get a clean fresh start would be best....
jco23 said:
I'm thinking the combination of SS and CWM could be the issue.... try to get a clean fresh start would be best....
Click to expand...
Click to collapse
Thats interesting. I dont see safe strap or the rom i was using with SS (energy rom). So then how can i erase SS and get a fresh start? I was assuming Matts Utility already did that for me and I was on a fresh start.
jcxmej said:
Thats interesting. I dont see safe strap or the rom i was using with SS (energy rom). So then how can i erase SS and get a fresh start? I was assuming Matts Utility already did that for me and I was on a fresh start.
Click to expand...
Click to collapse
safestrap could still be there if uninstalled incorrectly. trying re-installing it, then uninstall it within its own app. this worked for me.
jco23 said:
safestrap could still be there if uninstalled incorrectly. trying re-installing it, then uninstall it within its own app. this worked for me.
Click to expand...
Click to collapse
Just installed SS and unnistalled it thru the app. I ll wait for any reboots before I reflash the ROM. Hope this works. (finger crossed)
This isn't my very first time with flashing/rooting/etc. but I'm not that adept with it.
Got my S4 2 days ago but managed to get time today to work on it. I rooted successfully and everything was running perfect. I flashed over the newest Beanstalk ROM w/ gapps and it ran fine the first time it ran.
I can't get passed the Samsung Galaxy S4 boot logo every time I try to reboot the phone though...
If I wipe the cache/dalvik and reflash it still doesn't boot passed logo.
If I wipe the cache/dalvik and then wipe data (including the internal SD card, completely wiping it clean), flashing the ROM will work the first time it runs; once I reboot or just power it off then power it back on, stuck at Galaxy S4 logo... I let the ROM run first time through, input only what is needed to get to the home screen (google account/wifi setup/phone name/etc.), then I've tried rebooting it, shutting it down and powering it back up, letting everything update and waiting half an hour and restarting it... all have the same result, stuck at boot logo
I'm using TWRP, I have a recovery for stock but I don't want to use stock.
If anyone can help me out I'd appreciate it.
Try flashing a different compatible kernel.
ObrienDave said:
Try flashing a different compatible kernel.
Click to expand...
Click to collapse
This is EXACTLY what I was about to try... I'm literally reflashing the ROM fresh right now, going to put the kernel on the SD card, then reboot into recovery and wiping cache then flashing the kernel.
Will using a recovery that was made on a different kernel have any effect if I decide to use the recovery? I've heard bad things about flashing the wrong kernel (even though I know the one I'm about to use is the correct one) and really screwing stuff up if not done properly. I just want to make sure I don't screw anything up permanently.
Thanks.
Spazzzin said:
This is EXACTLY what I was about to try... I'm literally reflashing the ROM fresh right now, going to put the kernel on the SD card, then reboot into recovery and wiping cache then flashing the kernel.
Will using a recovery that was made on a different kernel have any effect if I decide to use the recovery? I've heard bad things about flashing the wrong kernel (even though I know the one I'm about to use is the correct one) and really screwing stuff up if not done properly. I just want to make sure I don't screw anything up permanently.
Thanks.
Click to expand...
Click to collapse
Use twrp 2.5.0.2 because if your using 2.6 its bringing problems. Also report this to their thread for better help
Sent from my SPH-L720 using xda app-developers app
Since there are no recovery categories according to this page,
http://forum.xda-developers.com/showthread.php?t=2303917
I don't see where it would matter. No guarantees though.
I do know it is ESSENTIAL to match the type (TW or AOSP) ROM and kernel to avoid major problems.
I also recommend TWRP 2.5.0.2
D/L TWRP from here:
http://techerrata.com/browse/twrp2/jfltespr
ObrienDave said:
Since there are no recovery categories according to this page,
http://forum.xda-developers.com/showthread.php?t=2303917
I don't see where it would matter. No guarantees though.
I do know it is ESSENTIAL to match the type (TW or AOSP) ROM and kernel to avoid major problems.
I also recommend TWRP 2.5.0.2
D/L TWRP from here:
http://techerrata.com/browse/twrp2/jfltespr
Click to expand...
Click to collapse
How do you go about installing TWRP? I used Goomanager and installed it from there when I was following the rooting guide
Spazzzin said:
How do you go about installing TWRP? I used Goomanager and installed it from there when I was following the rooting guide
Click to expand...
Click to collapse
Flashing a different kernel didn't do anything, I still keep getting stuck at the boot logo :/
Spazzzin said:
How do you go about installing TWRP? I used Goomanager and installed it from there when I was following the rooting guide
Click to expand...
Click to collapse
Just flash it by odin by the link provided above. Make sure to use the tar file v 2.5.0.2
Sent from my SPH-L720 using xda app-developers app
---------- Post added at 09:22 PM ---------- Previous post was at 09:19 PM ----------
Spazzzin said:
Flashing a different kernel didn't do anything, I still keep getting stuck at the boot logo :/
Click to expand...
Click to collapse
By the way can you provide the steps and which files you flashing. Also redownload everything could be a bad download. Make sure to download them in computer and transfer them to your sd card
Sent from my SPH-L720 using xda app-developers app
I did a fresh install of the LiquidSmooth ROM and it's not hanging at boot logo whenever I reboot, and everything is working well. I suppose I'll stick with this for a while.
For my steps trying Beanstalk:
Boot into recovery (TWRP 2.6.0.0)
Factory reset;wipe cache/dalvik
Format Data
Factory reset;wipe cache/dalvik
Install ROM + Gapps
Wipe cache/dalvik
Reboot
I then tried doing that exact process, after letting it boot once I rebooted into recovery and flashed KT Kernel and wiped then rebooted and it hung at boot logo.
I did it again but I installed ROM + Gapps + Kernel then wiped then rebooted and it still hung at boot logo.
I'll download and prepare a new install of Beanstalk and give it another try tomorrow. I'll make sure to backup Liquid in case I want to switch back.
Thanks again for the help!
Glad it's working out for you.
If I may ask here; how do I know if a certain kernel is compatible with a ROM? I know to match the version (4.2, 4.3. etc,) and base (AOSP/ TW) but is there anything else specific that I need to watch out for that could cause problems with flashing a kernel on a ROM?
Spazzzin said:
If I may ask here; how do I know if a certain kernel is compatible with a ROM? I know to match the version (4.2, 4.3. etc,) and base (AOSP/ TW) but is there anything else specific that I need to watch out for that could cause problems with flashing a kernel on a ROM?
Click to expand...
Click to collapse
Not really unless the rom dev for some reason doesn't recommend using a certain one. Kernels will act differently for everyone even on the same device with the same rom. Just need to flash them and find out which one works the best for you (battery life, overheating, smoothness, etc).
Always have a backup handy just in case something doesn't work right.
hey all,
so i am incredibly new to this scene and just recieved my s4. i was preparing to flash a ROM onto my phone, and got it rooted and installed CWM.
I forgot to download the actual ROM zip file, and went into CWM via goo manager, wiped factory/data and cache. It was only AFTER i wiped everything that i realised i didnt download the ROM zip file, so i rebooted the phone and now it is stuck on the start-up splash screen where it displays "Samsung galaxy S4 GT-I9505" and will not continue :crying:
I was running on stock, and had only rooted the phone.
PLEASE i urgently need to fix this ASAP. Help!
Hi,
is there a Odin Version of the Rom you tried to flash? If yes, you could simply bring your device to download-mode and flash the Rom with Odin.
Alternatively search for a odin flashable Recovery and flash this first. Then you could boot to recovery and flash the zip of the Rom.
Sent from my GT-I9505 using xda app-developers app
i tried installing the liquid smooth rom, and from what i can see there is no odin version of the rom :\
Are you able to direct me to an Odin flashable recovery I can use?
im really stressing out about this
i'm in the process of downloading a stock firmware and will try to flash it on, but it's taking forever to download
I don't see why you can't boot again if you have only wiped the user data and cache, just press the home button for 10 seconds and see if it restarts with your reset stock firmware. Otherwise you can reboot into recovery and do the wipes again (not the option to install a new ROM), or put the ROM zip you want to flash on an SD card and then flash from the SD.
I hope this helps.
suwidji said:
hey all,
so i am incredibly new to this scene and just recieved my s4. i was preparing to flash a ROM onto my phone, and got it rooted and installed CWM.
I forgot to download the actual ROM zip file, and went into CWM via goo manager, wiped factory/data and cache. It was only AFTER i wiped everything that i realised i didnt download the ROM zip file, so i rebooted the phone and now it is stuck on the start-up splash screen where it displays "Samsung galaxy S4 GT-I9505" and will not continue :crying:
I was running on stock, and had only rooted the phone.
PLEASE i urgently need to fix this ASAP. Help!
Click to expand...
Click to collapse
You should of made a backup with CWM. That's what it's used for also, besides flashing .zips. Always make a backup that you can restore and keep an extra copy on ur computer and/or a usb drive.
You have to use Odin to flash a stock firmware from Sammobile website. Make sure you download the correct firmware for your phone.
Dont worry, your phone isn't brick.
when i first did the wipe, i chose the option that i was going to install a new ROM. I'm now assuming that's where i made a mistake.
I did make a backup before i wiped everything onto my SD card, but now i can't even access that backup because it's saying there's nothing.
I've tried flashing a ROM onto it, but it says aborted.
Yes SORF ist right. It should boot into resetted stock firmware.
First try to copy the Rom to SD and then boot to recovery an try flashing it.
If booting to recovery doesn't work (but it should work if you just wiped user data and cache) you should try flashing new recovery with odin.
You could use Philz recovery for GT-I9505 from here http://forum.xda-developers.com/showthread.php?t=2281367
Installation Instructions for installation with odin you find here http://forum.xda-developers.com/showpost.php?p=39433857&postcount=4
windozeanti said:
You have to use Odin to flash a stock firmware from Sammobile website. Make sure you download the correct firmware for your phone.
Dont worry, your phone isn't brick.
Click to expand...
Click to collapse
Thanks, that's what I'm doing right now, but the file is about 1.8GB and taking so long to download...
i wish there was a faster server, but this is the only option i could find :\
Have you tried to boot into recovery again and then flash your already downloaded rom from sd? So you don't have to download a complete sammy rom.
j0ch3 said:
Have you tried to boot into recovery again and then flash your already downloaded rom from sd? So you don't have to download a complete sammy rom.
Click to expand...
Click to collapse
yes i have tried that, and it says that install aborts.
Also when i re-wipe everything and then try to reboot, it says my device is missing root.
When i try to re-root, and the device reboots, it gets stuck on the intro screen again so the root doesn't actually complete installing
have you fixed it yet?
so im going to try a different ROM other than the liquid smoothe one i wanted (since it keeps saying aborted)
question: does it matter if i use ANY s4 ROM regardless of carrier? I'm from Australia and there is no specific carrier for my phone on xda
Why does it fails to install? Are there any more error messages?
Also you can try the point "Fix Permissions" under Advanced Options. This could help.
suwidji said:
so im going to try a different ROM other than the liquid smoothe one i wanted (since it keeps saying aborted)
question: does it matter if i use ANY s4 ROM regardless of carrier? I'm from Australia and there is no specific carrier for my phone on xda
Click to expand...
Click to collapse
try something lite like miui - it will save you time on download and is a good solid base to work from. dont flash the lite gapps without a reboot.
for a solid Sami based rom then i suggest using GoldenEye.
scottyf79 said:
try something lite like miui - it will save you time on download and is a good solid base to work from. dont flash the lite gapps without a reboot.
Click to expand...
Click to collapse
ok so i went ahead and found the cyanogenmod one
http://forum.xda-developers.com/showthread.php?t=2317040
and installed this and it works
though i dont like the look of this ROM lol, i prefer something a little more stock looking.
Any recommendations?
When reflashing a new ROM, what is the process i need to follow?
Cyanogenmod is themeable. So you could search for a stock like theme and install that.
If you like an overall more stock rom try scottyf79's recommendation.
If you want to flash a complete new Rom first copy zip onto sd, then boot into recovery, wipe data and cache, then falsh zip file.
Try the Omega Roms. They are close to stock.
Closest to stock are the prerooted DJembey ROMs (the CWM ones) or the Wanam Lite ROM (it's what I am on now)
suwidji said:
ok so i went ahead and found the cyanogenmod one
http://forum.xda-developers.com/showthread.php?t=2317040
and installed this and it works
though i dont like the look of this ROM lol, i prefer something a little more stock looking.
Any recommendations?
When reflashing a new ROM, what is the process i need to follow?
Click to expand...
Click to collapse
personally -
i use Philz recovery
before install of a new rom - i use the "new rom" wipe option rather than the normal data,cache and dalvik wipe (it does this but adds in some extra steps)
then flash the rom of choice
if you get any other messages before reboot - select no
like i said before, if you want a stock looking Sami rom then try Golden Eye.
Try the Omega Roms. They are close to stock.
Closest to stock are the prerooted DJembey ROMs (the CWM ones) or the Wanam Lite ROM (it's what I am on now)
I just want to share my experience after a bad flash and no way to recover.
I was still able to get to TWRP. I had flashed a Rom and it went bad. Long story short. No Loki causing boot into fastboot screen.
Tried using flash tools to restore stock with kdz. No good kept stopping at 49% because it was not the expected firmware.
The fix.
Wipe system in recovery then try again. With system wiped. The firmware matches and installs as expected.
Just wanted to share my experience. Maybe it will help someone else with the same problem.
Brian
Sent from my LG-D801 using Tapatalk
THANK YOU!!
I registered specifically so I could post here.
I was looking for ages trying to find a fix. Always getting stuck at that 49%. Back to normal now!
Thanks alot
cambuchan said:
I registered specifically so I could post here.
I was looking for ages trying to find a fix. Always getting stuck at that 49%. Back to normal now!
Thanks alot
Click to expand...
Click to collapse
Glad it was if help for you!
Sent from my LG-D801 using Tapatalk
What fixed it for my friend was "format data," as in internal storage as well.
Thank you!
h
cheami said:
What fixed it for my friend was "format data," as in internal storage as well.
Thank you!
Click to expand...
Click to collapse
Hi, sorry for my english , I'm french
I wanted to flash a custom rom on my LG G2 D802 .
I wanted the Paranoid Android (PA +) with 4.3 JellyBean .
So I made the
Backup
Wipe data / factory reset
Wipe cache partition
Wipe dalvik Cache
After I
Choose zip ( custom ROM ) from sd card
Then I
Reboot System Now
And turn on my laptop, I get an error message saying
[640 ] started Fastboot Mode
[ 690] udc start ()
I realized I had to flash AOSP kernel before changing to a ROM paranoid . But my kernel is blocked and so I have to go back to the stock ROM
When I did this tutorial using lg tools , flashing stops at 49% with an error message .
I also saw that I could access the recovery mod by following this link http://forum.xda-developers.com/showthread.php?t=2565904(but I saw that I could not otherwise reboot my phone after it was bricking ) and therefore flash my stock Rom which I had made the backup . But I do not know if the ROM has been saved and if it remained in my files after the Wipes.
If it is not there, is that in buying a micro USB ====> HUSB adapter, I could install a stock ROM from a USB key ? Or is there a way I can put files from my computer to my laptop which has no port micro sd?
And is what I could with my kernel "blocked " ?
Thank you very much
harryleplusfort said:
Hi, sorry for my english , I'm french
I wanted to flash a custom rom on my LG G2 D802 .
I wanted the Paranoid Android (PA +) with 4.3 JellyBean .
So I made the
Backup
Wipe data / factory reset
Wipe cache partition
Wipe dalvik Cache
After I
Choose zip ( custom ROM ) from sd card
Then I
Reboot System Now
And turn on my laptop, I get an error message saying
[640 ] started Fastboot Mode
[ 690] udc start ()
I realized I had to flash AOSP kernel before changing to a ROM paranoid . But my kernel is blocked and so I have to go back to the stock ROM
When I did this tutorial using lg tools , flashing stops at 49% with an error message .
I also saw that I could access the recovery mod by following this link http://forum.xda-developers.com/showthread.php?t=2565904(but I saw that I could not otherwise reboot my phone after it was bricking ) and therefore flash my stock Rom which I had made the backup . But I do not know if the ROM has been saved and if it remained in my files after the Wipes.
If it is not there, is that in buying a micro USB ====> HUSB adapter, I could install a stock ROM from a USB key ? Or is there a way I can put files from my computer to my laptop which has no port micro sd?
And is what I could with my kernel "blocked " ?
Thank you very much
Click to expand...
Click to collapse
It sounds like you have access to recovery, so you can use adb to push or pull files from your phone. Your backup should still be on your phone, as long as you didn't wipe the internal storage.
I'd suggest pulling the important photos/videos/backup/files/etc from your phone to your computer, then wiping internal storage or wipe factory reset. Then hopefully it wont get stuck at 49%, as that is what I did for my friend's D801 to allow it to go back to stock 100%.
Exactly what i keep telling people with the same issue, Just do a full wipe in cwm/twrp before restoring to stock. the problem is allot of them can't get into recovery :silly:
Thanks for sharing! Will be useful someday
Sent from my LG G2 using Tapatalk
Posted this problem in another thread but haven't had an answer so hoping this one will help, have a vs980 with B firmware, rooted and was running cm11 Sat I installed rayglobe Rom ported to vs980 after running it for a few hours I decided to install twrp then I was gonna try phills recovery cause I was used to it, I installed freegee from the market and it ran a check and sshowed me the recoveries available for my phone, the short version is for some reason it read my phone version as the rayglobe 802 firmware and I hit install not realizing it wasn't. Reading vs980 now I have no recovery, flash tool does not work ( says wrong phone) rayglobe runs perfect but all maps dealong with root sees a 802 phone. Anyone have a idea how to fix this?
Sent from my LG-D802 using Tapatalk
quinejh said:
Posted this problem in another thread but haven't had an answer so hoping this one will help, have a vs980 with B firmware, rooted and was running cm11 Sat I installed rayglobe Rom ported to vs980 after running it for a few hours I decided to install twrp then I was gonna try phills recovery cause I was used to it, I installed freegee from the market and it ran a check and sshowed me the recoveries available for my phone, the short version is for some reason it read my phone version as the rayglobe 802 firmware and I hit install not realizing it wasn't. Reading vs980 now I have no recovery, flash tool does not work ( says wrong phone) rayglobe runs perfect but all maps dealong with root sees a 802 phone. Anyone have a idea how to fix this?
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Edit your build.prop to the correct device and install the correct recovery
Sent from my LG-D802 using Tapatalk
No clue how to do that can u use Rom manager app to do that?
Sent from my LG-D802 using Tapatalk
quinejh said:
No clue how to do that can u use Rom manager app to do that?
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Search is your friend, any app that can edit the build prop should work, please make a backup of your build prop. if you get it wrong your device will not boot.
Ok I found a thread on here about how to use file explorer to change the build prop it says there r 2 entries I need to change but my question is do I change it from d802 to vs980 or vs980b?
Sent from my LG-D802 using Tapatalk
leomd333 said:
Exactly what i keep telling people with the same issue, Just do a full wipe in cwm/twrp before restoring to stock. the problem is allot of them can't get into recovery :silly:
Click to expand...
Click to collapse
Well I could get into recovery but it did not fix the problem.
Please explain!
bri315317 said:
I just want to share my experience after a bad flash and no way to recover.
I was still able to get to TWRP. I had flashed a Rom and it went bad. Long story short. No Loki causing boot into fastboot screen.
Tried using flash tools to restore stock with kdz. No good kept stopping at 49% because it was not the expected firmware.
The fix.
Wipe system in recovery then try again. With system wiped. The firmware matches and installs as expected.
Just wanted to share my experience. Maybe it will help someone else with the same problem.
Brian
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
I have same problem with my F320L. I will try your method but please explain bit more that how should i do?
In twrp, first hard reset and then do full wipe (all wipe except internal memory and do not format any thing) or describe the way please?
Thanks!
bri315317 said:
I just want to share my experience after a bad flash and no way to recover.
I was still able to get to TWRP. I had flashed a Rom and it went bad. Long story short. No Loki causing boot into fastboot screen.
Tried using flash tools to restore stock with kdz. No good kept stopping at 49% because it was not the expected firmware.
The fix.
Wipe system in recovery then try again. With system wiped. The firmware matches and installs as expected.
Just wanted to share my experience. Maybe it will help someone else with the same problem.
Brian
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
When i go to recovery mode i only have function Factory reset...
Can you help me please ?
Hi guys, need some help here. I'm sure this has been asked before but i just couldn't find any
Installed slimkat 20140406-0134 rom (cm11) last night and it's basically working. But I'm still not feeling comfortable using it as there's still bugs around. So thought of going back to cm7.2 for now. But for the life of me couldn't figure out how to get to the tool section so I can re-partition it back to ext3!!!
All I could get in to is twrp recovery and that's it. how do I even get into the bootmenu section where I can choose recovery, cpu settings, tools, etc? There's no red Moto logo with blue LED at boot up anymore
Is there any uninstall instruction somewhere, or perhaps someone should write one?
44 viewers but no reply
any idea if i can install some sort of apps to achieve the same end? like a wipe app to re-partition it to ext3, and then an older recovery to install cm7 rom, or restore my cm7 backup?
don't really want to just try and see what will happens. also trying to avoid flashing sbf and start from scratch.....
edit: will aromawiper work? reboot to twrp recovery 2.6.3.0, aromawipe to ext3 and then flash cm7.2 rom straight after? expert opinion and advice please.
edit 2: oh well, tried it and didn't work. might be because i didn't install an older, compatible recovery before i rebooted. stuck at red moto logo and had to flash sbf and start all over again......
case closed...........
jh20 said:
44 viewers but no reply
any idea if i can install some sort of apps to achieve the same end? like a wipe app to re-partition it to ext3, and then an older recovery to install cm7 rom, or restore my cm7 backup?
don't really want to just try and see what will happens. also trying to avoid flashing sbf and start from scratch.....
edit: will aromawiper work? reboot to twrp recovery 2.6.3.0, aromawipe to ext3 and then flash cm7.2 rom straight after? expert opinion and advice please.
edit 2: oh well, tried it and didn't work. might be because i didn't install an older, compatible recovery before i rebooted. stuck at red moto logo and had to flash sbf and start all over again......
case closed...........
Click to expand...
Click to collapse
you can flash cm10 to get the boot menu to format to ext3 then flash to cm7.2.
Thats what i did when i tested cm11.
Or use Aroma wiper to format to ext3 and flash CM7.2.
Sent from my Nexus 7 using Tapatalk
aperture said:
you can flash cm10 to get the boot menu to format to ext3 then flash to cm7.2.
Thats what i did when i tested cm11.
Click to expand...
Click to collapse
thanks. i'll remember that next time. don't know why i didn't think of that. panic striken maybe
hotdog125 said:
Or use Aroma wiper to format to ext3 and flash CM7.2.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
that's exactly what i did but didn't work. aromawiper seems to have worked properly but twrp 2.6.3.0 keep saying "no os installed" after i installed the gb rom and tried to reboot. tried maniac's cm7.2 and an older wiui gingerbread rom. i thought it might be a hickup and rebooted anyway and that was it.
don't know what went wrong there. has anyone actually tried this method before and got it to work?
edit: imho twrp is not worth it. it rebooted 8-10 times on me after installing cm11 and tried to get back into recovery to flash gapps. also other problems like blank backup files and my failures to install rom problem. they should have stuck to cwm until the problems are fixed.
edit 2: and i think removing bootmenu is not a good idea. more steps to take if you want to go back to cm7.2.