Related
My phone isn't a brick but it might as well be, I flashed a CM7 build but didn't much like it so I never bothered to add the Google Apps, instead, I did a restore to my original MyTouch 4G backup but.... it didn't work, got a flashing screen, etc. so back to the CM7 build, now I can't run ROM Manager, it goes to the red triangle symbol, I can't run ADB, it won't find my phone, I can't root, it just keeps saying S=ON! Since I didn't add the Google Apps and can't now, I can't use the phone!
Am I out a MyTouch 4g? Is there anything that'll fix it?
xs11e said:
My phone isn't a brick but it might as well be, I flashed a CM7 build but didn't much like it so I never bothered to add the Google Apps, instead, I did a restore to my original MyTouch 4G backup but.... it didn't work, got a flashing screen, etc. so back to the CM7 build, now I can't run ROM Manager, it goes to the red triangle symbol, I can't run ADB, it won't find my phone, I can't root, it just keeps saying S=ON! Since I didn't add the Google Apps and can't now, I can't use the phone!
Am I out a MyTouch 4g? Is there anything that'll fix it?
Click to expand...
Click to collapse
What google apps are you looking for, 99% of them can be found online and installed. Have you tried the online Android market (it can send downloads directly to your device) https://market.android.com/
You might be able use visionary to temp root the device, that will get you started
Bupahs said:
What google apps are you looking for, 99% of them can be found online and installed. Have you tried the online Android market (it can send downloads directly to your device) https://market.android.com/
You might be able use visionary to temp root the device, that will get you started
Click to expand...
Click to collapse
Online market won't install because I've flashed my HD2 to Android so it keeps saying that everything is already installed.
Visionary won't temp root, nothing will, don't know why? Do you know just how many rooting proceedures there are on the WWW? I've tried each that I've found 3 or more times with no luck.
I'm going to try to see if the online market will allow me to install Root Explorer, that may help me some....
It won't. There seems no way to change phones???
xs11e said:
My phone isn't a brick but it might as well be, I flashed a CM7 build but didn't much like it so I never bothered to add the Google Apps, instead, I did a restore to my original MyTouch 4G backup but.... it didn't work, got a flashing screen, etc. so back to the CM7 build, now I can't run ROM Manager, it goes to the red triangle symbol, I can't run ADB, it won't find my phone, I can't root, it just keeps saying S=ON! Since I didn't add the Google Apps and can't now, I can't use the phone!
Am I out a MyTouch 4g? Is there anything that'll fix it?
Click to expand...
Click to collapse
When you tried to restore, did you flash the recovery back to version 2.x? You need a 2.x recovery (use 2.5.1.2) to flash CM6, stock, and other Froyo roms. This should let you restore back to stock. Supposedly clockworkmod 3.0.0.6 can flash back and forth between Froyo and Gingerbread roms, but I haven't tried it yet.
Thanks but whatever version of Clockworkmod I have is what I have since the critter won't allow anything to be changed???
I can't get into Clockworkmod so I think changing versions won't help but I can't change so it's sort of moot at this point. The phone will do either one of these things:
1. Boot normally into the partial CM7 build which isn't usable as explained elsewhere.
2. It'll do the hold Vol Dn and hit power boot but then it won't do anything, the only option that works is normal boot and then I'm right back into CM7.
3. I can select "restore" or boot normally and select ROM Manager and hit boot into recovery and it'll reboot to the error screen, red triangle with ! sign on it.
That is the stock Recovery (which doesn't do anything but display the lovely triangle).
If Rom Manager is running in your broken CM7 system, you could re-flash Clockwork Recovery.
You can also flash a Clockwork Recovery image using adb or Fastboot.
xs11e said:
Thanks but whatever version of Clockworkmod I have is what I have since the critter won't allow anything to be changed???
I can't get into Clockworkmod so I think changing versions won't help but I can't change so it's sort of moot at this point. The phone will do either one of these things:
1. Boot normally into the partial CM7 build which isn't usable as explained elsewhere.
2. It'll do the hold Vol Dn and hit power boot but then it won't do anything, the only option that works is normal boot and then I'm right back into CM7.
3. I can select "restore" or boot normally and select ROM Manager and hit boot into recovery and it'll reboot to the error screen, red triangle with ! sign on it.
Click to expand...
Click to collapse
As mentioned the red triangle is the stock recovery. Not sure how you flashed CM7 with the stock recovery but for some reason it sounds like that is all you have on your phone. FYI...If you hold the vol up and power button at the red triangle screen it should boot you into the stock recovery.
A couple of things that caught my eye. You say that your phone now says s=on. did it used to say s=off? When you say you went back to CM7 after trying to flash your backup, what steps did you take to try and go back? Was your backup made thru Rom Manager? Did you try to use Rom Manager to restore your backup?
First thing I would try is a full wipe and factory reset from the stock recovery if you can get there. You need to try and get CM7 to load correctly. If you can do that then you should be able to flash a new recovery. You dont need s=off to flash roms but you do need root.
Do you still have root acces? Ie: can you use SuperUser? Try a few root apps and see if they as for su permission.
jggimi said:
That is the stock Recovery (which doesn't do anything but display the lovely triangle).
If Rom Manager is running in your broken CM7 system, you could re-flash Clockwork Recovery.
You can also flash a Clockwork Recovery image using adb or Fastboot.
Click to expand...
Click to collapse
Thanks, ROM manager is running but re-flashing Clockwork Recovery doesn't help anything, it completes successfully but any attempt to do anything with it gets me to the red triangle.
I wish I could flash a recovery image using ADB or Fastboot, neither will function.
TrueBlue_Drew said:
As mentioned the red triangle is the stock recovery. Not sure how you flashed CM7 with the stock recovery but for some reason it sounds like that is all you have on your phone. FYI...If you hold the vol up and power button at the red triangle screen it should boot you into the stock recovery.
Click to expand...
Click to collapse
Correct, that's all that's there or at least all I can access so far. Vol up + pwr does boot me into stock recovery but that doesn't help.... <sigh>
A couple of things that caught my eye. You say that your phone now says s=on. did it used to say s=off? When you say you went back to CM7 after trying to flash your backup, what steps did you take to try and go back? Was your backup made thru Rom Manager? Did you try to use Rom Manager to restore your backup?
Click to expand...
Click to collapse
Yes, I did have S=off to flash. Steps trying to go back were none, really, after the restore failed the phone wouldn't do anything as detailed in my posts. The backup was made through Rom Manager and that's what I used to try the restore.
First thing I would try is a full wipe and factory reset from the stock recovery if you can get there. You need to try and get CM7 to load correctly. If you can do that then you should be able to flash a new recovery. You dont need s=off to flash roms but you do need root.
Do you still have root acces? Ie: can you use SuperUser? Try a few root apps and see if they as for su permission.
Click to expand...
Click to collapse
Wiped and factory reset several times with no change in the problem. I'd love to get CM7 to load correctly but since I didn't originally load the GAPPS it's pretty useless, no gmail, no contacts or calendar, no Android market (which means all that's on the phone is all I can get, the online market won't work as mentioned in a previous post.) I cannot flash a new recovery, that's what I've been trying to do for several days now.
I do have root access, I can use SuperUser but it doesn't seem to do anything. Attempts to re-root have failed.
i feel ya bro, the reason I am asking these questions is to try and figure out what you have tried and not tried. CM7 isnt useless if you can get it to load. Just because you dont have the gapps installed, that shouldnt do anything but make you not have the market and google apps. Do you have adb set up and will it recognize your device? The biggest question is why would it have turned s=on and why wouldnt rom manager be able to flash a new recovery. Rom manager has a problem making/flashing backups using 3.0.0.X recoveries so that is where this problem started I think. Thats why I am trying to get you a clean working CM7. Does it give you a error when trying to install recovery through rom manager? Have you tried going to applications/manage applications/all/Rom Manager and clearing the data?
If you have su access you might also be able to flash a new recovery via terminal emulator.
Thanks, I appreciate the help and sympathy! I've fixed it in a very unorthodox way, it involved going to T-Mobile's website, changing phone to Blackberry 9700, moving SIM to 9700 and switching data plan to Blackberry.
Dang, that's a little screen....
The reason I'm maybe not giving you all the information you need is that I have very bad arthritis in my hands and I try to type as little as possible, I'm sorry if I'm not being clear but don't hesitate to ask if you need more info.
Not having the gmail means no sync, can't import contacts or calendar, no apps means what I have on the phone is ALL I HAVE, I can't get anything else. That's why I say it's unusable.
ADB does not recognize the device.
Installing recovery through Rom manager results in red triangle.
I did clear Rom manager data as you suggested but it didn't help.
How could I flash recover through terminal emulator, I do have that and can access it and typing SU does give me the # prompt so that's helpful maybe? I'd need step by step directions because I'm very unfamiliar with using terminal emulator, I've only used it to follow directions given in the rooting instructions.
xs11e said:
Thanks, I appreciate the help and sympathy! I've fixed it in a very unorthodox way, it involved going to T-Mobile's website, changing phone to Blackberry 9700, moving SIM to 9700 and switching data plan to Blackberry.
Dang, that's a little screen....
The reason I'm maybe not giving you all the information you need is that I have very bad arthritis in my hands and I try to type as little as possible, I'm sorry if I'm not being clear but don't hesitate to ask if you need more info.
Not having the gmail means no sync, can't import contacts or calendar, no apps means what I have on the phone is ALL I HAVE, I can't get anything else. That's why I say it's unusable.
ADB does not recognize the device.
Installing recovery through Rom manager results in red triangle.
I did clear Rom manager data as you suggested but it didn't help.
How could I flash recover through terminal emulator, I do have that and can access it and typing SU does give me the # prompt so that's helpful maybe? I'd need step by step directions because I'm very unfamiliar with using terminal emulator, I've only used it to follow directions given in the rooting instructions.
Click to expand...
Click to collapse
to flash a recovery image via terminal emulator if you are on cm7 is:
Type "su" and then enter the code below after putting the recovery on your sd card. Make sure you name it recovery.img
Code:
flash_image recovery /sdcard/[COLOR=black]recovery.img[/COLOR]
LMK if that works.
Thanks, I'm not sure what I expected but what happened is exactly nothing:
Put Recovery.img on card, booted up phone, started Terminal Emulator got:
export PATH=/data/local/bin:$PATH
$ export PATH=/data/local/bin:$PATH
$ su
# flash_image recovery /sdcard/recovery.img
#
And that's it, nothing happened at all, just went back to the # prompt.
xs11e said:
Thanks, I'm not sure what I expected but what happened is exactly nothing:
Put Recovery.img on card, booted up phone, started Terminal Emulator got:
export PATH=/data/local/bin:$PATH
$ export PATH=/data/local/bin:$PATH
$ su
# flash_image recovery /sdcard/recovery.img
#
And that's it, nothing happened at all, just went back to the # prompt.
Click to expand...
Click to collapse
As long as you named it recovery.img and not Recovery.img it should have worked. Try to boot into recovery by powering off your phone and then holding the vol but and power button at the same time. Then chose recovery. Or if you on CM7 just hold power button for a sec and then reboot and recovery.
LMK if that works.
I checked the name several times, booting into recovery just takes me to the red triangle, I've tried that many times before, nothing's changed.
I suspect it's a brick?
xs11e said:
I checked the name several times, booting into recovery just takes me to the red triangle, I've tried that many times before, nothing's changed.
I suspect it's a brick?
Click to expand...
Click to collapse
ok, I still dont believe its a brick. Are you running a rom at all? I mean does it boot into CM7 even though you dont have Gapps? Or is it totaly stuck on bootloop all the time. I am going to send you a PM with my Gtalk. Add me if you want and maybe it will make it a little easier to communicate and help.
TrueBlue_Drew said:
ok, I still dont believe its a brick. Are you running a rom at all? I mean does it boot into CM7 even though you dont have Gapps? Or is it totaly stuck on bootloop all the time.
Click to expand...
Click to collapse
It boots right up in CM7, if I'd added the Gapps at the beginning I'd just be running it happily I think? I'd be able to sync and get needed apps from the market, etc. etc.
I am going to send you a PM with my Gtalk. Add me if you want and maybe it will make it a little easier to communicate and help.
Click to expand...
Click to collapse
Thanks, I'd really prefer to do it this way. Why? Because I'm really sick of messing with it and I hate to spend much time working on it now, I've resigned myself to having a very costly paperweight! Using the thread here allows me to check in once or twice a day when the urge strikes, besides, I really don't IM, never have, never could figure it out. I don't text either, it's blocked at T-Mo's website and on my phones as well. I'm not really a technophobe but I'm 99.2 % one.....
That's fine. I was just trying to maybe make it a little easier in ya.
If you can install a .apk I can send you the market and a few things. We can try to get a few things going that way if you want. If we can get the market going you can get gmail and every thing else from there. will attach the market and tell you how to install if you want
Sent from my HTC Glacier
If he's still s=on, he's not going to be able to flash recovery. You need to get s=off.
Grab the .apk for Visionary. Grab gfree. Grab an apk for a terminal emulator if you don't have one. Put them all on your sdcard, boot into CM7, and follow the instructions for the gfree method here:
http://forum.xda-developers.com/showthread.php?t=858996
If you don't have a file manager to get to them, you could try SMS'ing the download links to the phone and installing through the browser for the .apk's.
TrueBlue_Drew said:
That's fine. I was just trying to maybe make it a little easier in ya.
If you can install a .apk I can send you the market and a few things. We can try to get a few things going that way if you want. If we can get the market going you can get gmail and every thing else from there. will attach the market and tell you how to install if you want
Sent from my HTC Glacier
Click to expand...
Click to collapse
I can't install an APK. I got all the Google apps and put them on the SD card, if I click on one I get "couldn't parse the file" what ever that means?
Actuall, it did install the Market apk but it won't open.....
I searched everywhere, but can't find the same problem as mine. I am stuck in the CW recovery screen, after rebooting times after times.
I have been updating the CM9 nightly for a while, didn't have any problem. But when I tried to flash 02-17 nightly, I messed up and in the middle of the install (flash), I hold the power forcing to reboot. Now, it keeps going loop back to the CW recovery screen every time I tried to reboot.
--
I tried to reinstall the whole thing with the boot-able sdcard, but didn't work. please help! someone?
I tried to wipe, reformatted the system, data, cash, boot. Still stack at the cw recovery screen. Help...
I love my nook and have a road trip coming up. It will be nice to watch a kid movie to keep the kids entertained.
Had you flashed CmWR into eMMC?
Check the ROM information on /dev/block/mmcblk0p2.... this sounds a LOT like the problem 12paq had...
http://forum.xda-developers.com/showthread.php?t=1495913
@Dizzyden, thanks for the tip.
I did repartition to 1g/5g awhile back. I am not sure where to start. 12paq tried many things, which one was the solution? Your rombackup.zip?
Many thanks....
@votinh
what do you mean? I am not using the N&O apps or OS. Pure CM9, therefore I guess it is flashed in eMMC. If not, please advice.
DizzyDen said:
Check the ROM information on /dev/block/mmcblk0p2.... this sounds a LOT like the problem 12paq had...
http://forum.xda-developers.com/showthread.php?t=1495913
Click to expand...
Click to collapse
how can I check this"Check the ROM information on /dev/block/mmcblk0p2"?
please advice.
I tried to adb shell the nook, but not devices found? please help.
Finally, with the help from the good people of this forum, I was able to restore back to B&N, and reflash CM9 from there.
Thank to you all.
Yesterday my nook color was working great. Today I turned the screen on and it hung. Now I'm having the above problem with it hanging at clockwork recovery.
I've got CM7.1 stable on there running from emmc.
can't get adb to recognize the device since it is in cwr... how did you do it?
chilimac02 said:
can't get adb to recognize the device since it is in cwr... how did you do it?
Click to expand...
Click to collapse
Install the google drivers for adb... if you are in CWR adb is enabled... just have to get the drivers loaded on your computer.
try this:
http://forum.xda-developers.com/showthread.php?t=958748
dumper1234 said:
I searched everywhere, but can't find the same problem as mine. I am stuck in the CW recovery screen, after rebooting times after times.
I have been updating the CM9 nightly for a while, didn't have any problem. But when I tried to flash 02-17 nightly, I messed up and in the middle of the install (flash), I hold the power forcing to reboot. Now, it keeps going loop back to the CW recovery screen every time I tried to reboot.
--
I tried to reinstall the whole thing with the boot-able sdcard, but didn't work. please help! someone?
I tried to wipe, reformatted the system, data, cash, boot. Still stack at the cw recovery screen. Help...
I love my nook and have a road trip coming up. It will be nice to watch a kid movie to keep the kids entertained.
Click to expand...
Click to collapse
It may be that your "boot to recovery" flag is set, and if so, it will always boot to that until it is cleared. When the cyanogenmod logo comes up hold the n button until the boot menu comes up. Then choose boot to emmc. If it works, go to ROM Manager and flash a new CWM Recovery to emmc.
Welcome to the nightmare I lived last week. Don't worry I woke up, was able to fully recover and forget the dream ever occurred.
I to tried to reformat to 1gb/5gb and ended up in the same boot loop.. If you are in the same spot I was, your boot partition got wiped out. And you may notice EMMC is gone.
After much searching I came across a file... Looking....Looking...Looking...
..........................Ah yes here it is. Here is what worked for me.
1. Boot to recovery (Should be easy at this point)
2. Format System, Data, and Cache.
3. Install the attached Zip file. (RecoveryFix.zip), this should recreate the Boot partition and fix the EMMC.
4. Reboot to recovery
5. Install favorite Rom or restore from backup.
6. Reboot to test.
Again this is what finally worked for me, and I went through a lot of trial and error to get there. I am guessing at your situation being exactly the same as mine.
PS. Ignore my since of humor if you need to.
Hey all! I've been lurking around XDA for years for various devices. I'm good with computers but newer to Android/Linux. And I don't have much of a programming background. I have done some installing of custom ROMS on a phone of mine and even dabbling in a kitchen some. So it's not totally foreign to me.
I've been reading about custom ROMS on and off for a few months thinking about installing a custom ROM. And then actually reading and researching it the last day or two. Since we're not going to get Jelly Bean I decided finally to update to a custom Jelly Bean ROM. I am finding all the information very unorganized and very spread out. And not very comprehensive. Which is making it hard to get a good grasp of everything. Things like what SKBs are and APX mode. And exactly what processes you need to take to install which ROMS. If you need to install a kernel or it does it automatically ect. Very confusing! I thought I had figured out enough to do it.
On my A500 I had the latest Acer ICS OTA update but rooted. I want to install the CM10 Jellytime ROM. I did a factory reset. Using AfterOTA v1.09 I installed first "Bootloader Ics v3.14.8+Thor v1.7.3". Then after that I changed to "Bootloader Ics v3.14.8+Recovery Twrp v2.1.3. It seemed to work fine. I got into the bootloader. I have the Jellytime ZIP file on my external SD card. The first time I think I just clicked install, picked the ZIP and did the swipe to install. Which brings me to my big question. What is it supposed to do after that? It just went back to the Recovery boot animation and back into the recovery without seemingly doing anything. If I rebooted holding the Vol-, it would just go into Recovery and not flash anything. If I just let it boot it would boot the factory ROM. The Thor recovery did something similar.
I then did the wiping/formatting of all of the cache, factory resets and system. And when I tried to install it again basically the same results. Except now it won't boot into the factory ROM since I wiped the system. Which will also not let it connect over USB and to the AfterOTA. If I turn it on holding the Vol+ and get the boot menu and pick the fastboot it tries to do the fastboot but just hangs on the Fastboot notification.
I've been searching and reading but can't figure out if I didn't do something I should have or missed a step. Any help would be appreciated.
Ah! I figured it out! I didn't realize that even though you're using a custom recovery program that you still have to name the ROM file "update.zip". I thought that might be the case but couldn't connect the tablet to the computer via USB and didn't have an SD adapter to connect the card to the computer and change the name. I ended up getting a card adapter. After I changed the name it worked.
briwayjones said:
Ah! I figured it out! I didn't realize that even though you're using a custom recovery program that you still have to name the ROM file "update.zip". I thought that might be the case but couldn't connect the tablet to the computer via USB and didn't have an SD adapter to connect the card to the computer and change the name. I ended up getting a card adapter. After I changed the name it worked.
Click to expand...
Click to collapse
great, thanks for posting your solution
I've heard ranting and raving about Malladus and I decided to flash it yesterday. It won't take the flash no matter what I do.
I've tried: Flashing 1.2.4, downloading both again to make sure it wasn't a download issue, using different gapps package, using a different lg apps package, using CWM, using TWRP, side-loading... ETC
Bottom line: My phone will not take the ROM. It flashes the LG logo and gets stuck at a black screen where the back-light is on but nothing is displayed on the screen.
I am an experienced flasher and I have no idea what is going on. I am backed up and can get into TWRP to restore so I am all good as far as not being bricked goes but I really want to try out this damn rom.
Any help would be much appreciated. Thanks.
Bump I'm having the same problem, I'm on Verizon.
NBushyy said:
Bump I'm having the same problem, I'm on Verizon.
Click to expand...
Click to collapse
Yeah same here. Verizon. Forgot to mention it.
Still a problem. Bumping.
I am in the boat with you. I thought it was just me.
Same Black Screen issue
Did anyone have any luck resolving this? Ive tried with both twrp and cwm and same issue...?
Same problem on my Verizon model. Using twrp 2.6.3.3. Other roms work fine.
How long have you left it at the black screen? Sometimes a fresh load can take up to 10 minutes.
Also, the rom will work without gapps and lgapps, so try just loading the rom. I know you downloaded twice, but did you check the md5 sum either time?
heleos said:
How long have you left it at the black screen? Sometimes a fresh load can take up to 10 minutes.
Also, the rom will work without gapps and lgapps, so try just loading the rom. I know you downloaded twice, but did you check the md5 sum either time?
Click to expand...
Click to collapse
I left it there for a good 15 minutes. I also had it plugged into my laptop. It kept detecting the phone as plugged in. Seems like it is stuck in a bootloop or something. I also tried installing only the ROM without the gapps and lgapps and had the same result. I also checked the MD5 sum and it matched. (I know I'm kinda hijacking this original post, but I think we are all having the exact same issue)
try this
trackstar1414 said:
I left it there for a good 15 minutes. I also had it plugged into my laptop. It kept detecting the phone as plugged in. Seems like it is stuck in a bootloop or something. I also tried installing only the ROM without the gapps and lgapps and had the same result. I also checked the MD5 sum and it matched. (I know I'm kinda hijacking this original post, but I think we are all having the exact same issue)
Click to expand...
Click to collapse
Can you restore your nandroid and flash say, CleanROM 1.0 or DigitalDream 2.1? OR try this:
1. Hold the power button until the device is OFF.
2. Download LG drivers to the PC (LG VZW_United_WHQL_v2.11.1) and LG mobile support tool (B2CAppSetup).
3. Install these packages.
4. Plug in you USB cable into the phone but not the computer.
5. Hold volume up and insert the USB cable to the PC- the phone should boot to 'download mode'.
6. Open the support tool and click Options>Upgrade Recovery, follow the prompts.
7. At the first prompt indentify your phone using IMEI/ESN, then click OK
8. Let it do its thing, the phone will reboot and most likely have a bunch of error messages and some FC's. Just hit okay to all messages, the phone will settle after 2 minutes or so.
9. Download freegee from market and reflash recovery of your choice.
10. Make sure you have a ROM saved to the SD to flash
11. Use freegee to reboot to recovery
12. Once in recovery you can reflash the ROM as normal.
13. Reboot and Profit!
*$* Or you could go back to Stock and start fresh!
*$* BEFORE ANY FLASH ALWAYS STOP and MAKE A NANDROID BACKUP!
Good Luck and if you get stuck let me know
geosnipe said:
Can you restore your nandroid and flash say, CleanROM 1.0 or DigitalDream 2.1? OR try this:
1. Hold the power button until the device is OFF.
2. Download LG drivers to the PC (LG VZW_United_WHQL_v2.11.1) and LG mobile support tool (B2CAppSetup).
3. Install these packages.
4. Plug in you USB cable into the phone but not the computer.
5. Hold volume up and insert the USB cable to the PC- the phone should boot to 'download mode'.
6. Open the support tool and click Options>Upgrade Recovery, follow the prompts.
7. At the first prompt indentify your phone using IMEI/ESN, then click OK
8. Let it do its thing, the phone will reboot and most likely have a bunch of error messages and some FC's. Just hit okay to all messages, the phone will settle after 2 minutes or so.
9. Download freegee from market and reflash recovery of your choice.
10. Make sure you have a ROM saved to the SD to flash
11. Use freegee to reboot to recovery
12. Once in recovery you can reflash the ROM as normal.
13. Reboot and Profit!
*$* Or you could go back to Stock and start fresh!
*$* BEFORE ANY FLASH ALWAYS STOP and MAKE A NANDROID BACKUP!
Good Luck and if you get stuck let me know
Click to expand...
Click to collapse
I am able to restore my nandroid backup so I'm not completely stuck without a phone. I will try flashing one of the other ROMs and see how it goes now. Thanks for the help so far.
trackstar1414 said:
I am able to restore my nandroid backup so I'm not completely stuck without a phone. I will try flashing one of the other ROMs and see how it goes now. Thanks for the help so far.
Click to expand...
Click to collapse
I was able to install the digital dream rom without any issue. At this point I think its the sequence I did everything. I did the latest ota before installing any Recovery. I used the loki method to install the recovery. In looking at all the roms, it appears that malladus may not be "loki patched" for people already on 12b? Other roms I have tried mention that so thats why I'm speculating this. I am by no means a developer so I might be out in left field on this one. I guess I'll stick with stock or another ROM for now until his next update.
It also looks like people are discussing this on the main ROM forum as well so hopefully it will work in the future.
Thanks again for the help and suggestions.
trackstar1414, say thanks by using the "Thanks' button like this.. keep me informed, CHEERS!
trackstar1414 said:
I was able to install the digital dream rom without any issue. At this point I think its the sequence I did everything. I did the latest ota before installing any Recovery. I used the loki method to install the recovery. In looking at all the roms, it appears that malladus may not be "loki patched" for people already on 12b? Other roms I have tried mention that so thats why I'm speculating this. I am by no means a developer so I might be out in left field on this one. I guess I'll stick with stock or another ROM for now until his next update.
It also looks like people are discussing this on the main ROM forum as well so hopefully it will work in the future.
Thanks again for the help and suggestions.
Click to expand...
Click to collapse
Wanted to share this if you haven't read it..
http://forum.xda-developers.com/showthread.php?t=2449670
I had issues originally and had to flash back to 1.2.3.
What I ended up doing was switching to CWM 6.0.4.4 ( I was using TWRP 2.6.3.3).
His boot skipped the set up wizard as well, which was odd.
His was also the only ROM I ever got stuck on the fastboot screen while using twrp.
Try ( at your own risk obviously) flashing back to an older malladus (wipe all and boot till you get through the set up wizard),
Then back to recovery, do a wipe, without wiping the system partition, Data Cache and Davlik, and flash back to 1.2.5.
I didn't try it on 1.2.5. But that's how I got into 1.2.4.
Srvisg0d said:
I've heard ranting and raving about Malladus and I decided to flash it yesterday. It won't take the flash no matter what I do.
I've tried: Flashing 1.2.4, downloading both again to make sure it wasn't a download issue, using different gapps package, using a different lg apps package, using CWM, using TWRP, side-loading... ETC
Bottom line: My phone will not take the ROM. It flashes the LG logo and gets stuck at a black screen where the back-light is on but nothing is displayed on the screen.
I am an experienced flasher and I have no idea what is going on. I am backed up and can get into TWRP to restore so I am all good as far as not being bricked goes but I really want to try out this damn rom.
Any help would be much appreciated. Thanks.
Click to expand...
Click to collapse
Are you on 12B OTA? If so, that would be your issue. I took the 12B OTA and tried flashing Malladus and got the same issue you have. You can revert your phone to 11A and that should resolve your issue. http://forum.xda-developers.com/showthread.php?t=2448960 it will erase everything on your phone and go back to unroot.
I unlocked my Nexus 10 bootloader, then installed the latest CWM, and finally the latest SuperSU, and it's all fine. But it seems that the only way to get into recovery is to first go into the bootloader (hold power, vol up and vol down) then select recovery from there. And when I leave recovery to boot back into the OS (stock - i've not flashed any other roms yet) I get a warning about how stock is going to revert my recovery and lose root, and do I want to try and fix it, and how this cannot be reversed. I select fix it, but next time I try and get into recovery it's not there. Is this normal, or a known problem? Have I done something wrong? I don't want to fiddle around too much and brick my device; it works perfectly and the only reason I did all this was so I could install an app to prevent me from having to connect my N10 to my pc to used ADB over USB - I much prefer doing it all over Wifi!
poldie said:
I unlocked my Nexus 10 bootloader, then installed the latest CWM, and finally the latest SuperSU, and it's all fine. But it seems that the only way to get into recovery is to first go into the bootloader (hold power, vol up and vol down) then select recovery from there. And when I leave recovery to boot back into the OS (stock - i've not flashed any other roms yet) I get a warning about how stock is going to revert my recovery and lose root, and do I want to try and fix it, and how this cannot be reversed. I select fix it, but next time I try and get into recovery it's not there. Is this normal, or a known problem? Have I done something wrong? I don't want to fiddle around too much and brick my device; it works perfectly and the only reason I did all this was so I could install an app to prevent me from having to connect my N10 to my pc to used ADB over USB - I much prefer doing it all over Wifi!
Click to expand...
Click to collapse
Try Quick Boot in the Playstore.
sfobrien said:
Try Quick Boot in the Playstore.
Click to expand...
Click to collapse
I might try that but really I'm more concerned about my recovery going missing when I exit it.
Strange, never seen that and can't reproduce it. I suggest switch to TWRP and maybe custom ROM and see if that corrects the issue.
Is recovery returned to stock or just flat out missing? I haven't had a permanent recovery, stock or non-stock, on mine for some time now though it will still work loading temp recoveries.
mhausig said:
Is recovery returned to stock or just flat out missing? I haven't had a permanent recovery, stock or non-stock, on mine for some time now though it will still work loading temp recoveries.
Click to expand...
Click to collapse
I don't think anything actually happened - it just warned me that it might, and that I could either do nothing, or copy some files into system.
In the end I used TWRP which doesn't have the same problem.
This allowed me to return to my original problem, where I discovered that my game doesn't have a bug; instead, every single Nexus 10 has a problem with multitouch which Google doesn't even acknowledge, let alone fix.