[ROM][CM9] Lenovo Ideapad K1 Unofficial Port - Thinkpad Tablet Android Development

This is an unofficial CM9 port for the Lenovo Ideapad K1 tablet. To flash this Rom you must be already running the official Lenovo ICS Rom or my AOSP ICS build. This WILL NOT work if you are currently running Honeycomb or the Alpha cm9 port, update to one of the newer Roms then flash this from CWM recovery.
Issues
Video Camera face effects
Rotation Lock Switch (Software switch works)
Reboot > Recovery in power menu not working (Rom Manager - Reboot Recovery and 'reboot recovery' command both work fine)
Downloads
As always flash at your own risk. I am in no way responsible for your device.
cm-9-20120809-UNOFFICIAL-k1.zip
181adb1e84090a7ecb37ac5215284afb
Mirror - thx unclecracker
Latest Gapps
Grab the latest gapps for 4.0.4
Instructions
1. Download zip to External SD
2. Reboot to recovery (Use Rom Manager or 'reboot recovery' command)
3. Wipe Device/Factory Reset
4. Flash the cm9 zip
5. Flash latest gapps
Changelog
Code:
8/9/2012
-Initial Release
Source Code
http://github.com/khanning

Thank you very much.
I'l try it asap.

No freaking way! I was just about to ask in the AOSP thread if we would be seeing some CM9 action. Great stuff!

Dude you freaking rock!!!!
Thanks a million
Sent from my Galaxy Nexus using xda app-developers app

Awesome job man! always look forward from a post from you
Sent from my Dark Unicorn Resurrected v.2.5 using xda premium

Hi all,
does 3g work in this build?
Cheers, Jorge

Installed over your AOSP r1 build. Restored all apps using titanium. Seems to be working fine so far. I will test out today more thoroughly and report back.
One thing noticeable. My Quadrant score went from 2510 to 2840. Nice improvement.
Sent from my K1 using XDA Premium HD app

khanning88 said:
This is an unofficial CM9 port for the Lenovo Ideapad K1 tablet. To flash this Rom you must be already running the official Lenovo ICS Rom or my AOSP ICS build. This WILL NOT work if you are currently running Honeycomb or the Alpha cm9 port, update to one of the newer Roms then flash this from CWM recovery.
Issues
Video Camera face effects
Rotation Lock Switch (Software switch works)
Reboot > Recovery in power menu not working (Rom Manager - Reboot Recovery and 'reboot recovery' command both work fine)
Downloads
As always flash at your own risk. I am in no way responsible for your device.
cm-9-20120809-UNOFFICIAL-k1.zip
181adb1e84090a7ecb37ac5215284afb
Mirror - thx unclecracker
Latest Gapps
Grab the latest gapps for 4.0.4
Instructions
1. Download zip to External SD
2. Reboot to recovery (Use Rom Manager or 'reboot recovery' command)
3. Wipe Device/Factory Reset
4. Flash the cm9 zip
5. Flash latest gapps
Changelog
Code:
8/9/2012
-Initial Release
Source Code
http://github.com/khanning
Click to expand...
Click to collapse
Hello,
totally new to this forum so pardon the hit and run. I have been helping someone install CM9 onto his K1 and ran into a roadblock that I can't seem to get around.
I rooted it and installed the previous CM9 that Khanning released and for a few hours all seemed well. The device then locked up and had to hard shut down. After I get about 3 rounds of the startup logo and then freeze.
I can't get back into CM9 at all so have not been able to figure out how to get back into k1recovery.
I have tried re-hooking it up to the computer and it won't see it as an external device at all (has a spot for something being recognized while the locked screen is up on the tablet, but windows just won't see it as a usable device to copy data to or from.
I also tried with the 2 lights on (sorry forget what that mode is called) connecting and a adb shell k1recovery command, but adb just won't see the device at all.
Even tried a battery disconnect (he already knew to try that from a previous lockup that could only be fixed that way - long before when it was still stock - not a recent need).
Any ideas?
Oh I also tried removing the external sdcard and putting a dummy update.zip file on it and in a directory I created called Download - no luck - read somewhere on TPTs that that could force a bootup into CMW - but no similar luck on the K1.
I know CMW installed at least before these lockups on every boot because I was able to terminal to it from within CM9 when it was working for the few hours it seemed to be all ok.
I feel bad - this is my old man and this is his first experience with bricking a device - any help appreciated.
Neil
p.s. Khanning and others - thanks for all you guys do - I use the CM9 (and hopefully CM10) on my HP TouchPad and can't believe how much enjoyment above and beyond the stock you guys add to these devices.

Hi Neil,
I haven't experienced a lockup yet. Was the device doing anything when this happened?
While the device is booting up, bootanimation playing, run 'adb reboot recovery' and see if you can get into CWM. If that doesn't work you may have to enter into APX mode and reflash with the nvflash package.

Great work but few issues remain.
First hats off to Khanning for all the great work. You have done more than Lenovo did with their half baked ICS update.
Few issues I see (same as AOKP build):
1. Window and transition animations lag a bit (as a workaround I have completely disabled animations)
2. Google Play incompatibility issues with some apps. (Although build.prop of Xoom does fix some apps)
3. Some of CM9 settings don't seem to work (like LED flashlight toggle, Am/PM style in the clock etc.)
The rotation lock doesn't work, but I don't care much for that anyway.
Other than these minor issues, it is great.
Thanks..
---------- Post added at 10:32 PM ---------- Previous post was at 10:02 PM ----------
Also, on rebooting to recovery, it works fine from terminal emulator or through ROM manager.
In the AOSP build, I used a notification widget using from Elixir2 (an awesome app btw), for rebooting to recovery (I edited the widget command settings to k1recovery). this worked in the AOSP build. But the same widget isn't working in the CM9 build (with the command reboot recovery).
I would love to have a notification widget which can be configured to reboot to recovery.
Anyone knows any other android app which can do that from notification area other than Elixir?
Thanks.

khanning88 said:
Hi Neil,
I haven't experienced a lockup yet. Was the device doing anything when this happened?
While the device is booting up, bootanimation playing, run 'adb reboot recovery' and see if you can get into CWM. If that doesn't work you may have to enter into APX mode and reflash with the nvflash package.
Click to expand...
Click to collapse
Hello Khanning,
my dad says he was just done installing some apks and he was in to the device settings screen when the device just totally locked up. I got it to shut down with a pressing of the power and home key, but on next boot up it goes through about 3 rounds of the CM boot animation then just locks up completely.
I tried adb reboot recovery also before - problem here is that all adb commands won't see the device attached. I confirmed the nvidia usb driver does show as installed when I attach the device, powered it on holding both volume keys and no luck. Same thing if I do the volume keys and power on before attaching to the computer - adb commands just grumble about no attached device. Also same result when I tried to connect it while the boot animation was playing - it just didn't stay on long enough before locking up to be recognized by the computer at all.
I'll try axp mode and complete re-flash and see what happens - I do see it just did an "Entering NvFlash recovery mode /NV3P Server" so maybe it will reflash back to the rooted base load and let me over flash to the CM9 new build next.
Update...
Thank you very much for the suggestion - I didn't think to re-apply the base through nvflash after being unable to get it to be recognized via any adb commands thinking if it didn't work through adb it wouldn't be seen through nvflash either. It'll be awhile before I know if there is joy or no joy so will post back once I know for sure. If we can't get this patient out of bed he's going to grab a Asus Prime 32gb - $369.99 and tax, but I'd like to avoid that since this tablet really does what he needs (well when it isn't serving 2nd duty as a boat anchor like it is atm).
Update - going back to the first image I used to root the device I'm back and re-applying your AOSP ICS build which just finished as well so looks like for now I'm back in business.
I just downloaded your 8/9 build and am downloading Gapps 4/29 so will do that next.
BTW - my dad isn't a poster type, but he is a "fan" of yours and appreciates everything you've been doing for the K1.
Sorry for the long post - you can tell I'm updating it as I re-flash etc.
Neil
---------- Post added at 10:42 AM ---------- Previous post was at 10:11 AM ----------
UPDATE...
8/9 installed fine - in process of re-adding the Shtuff (you know what that means) my dad collects - so do we really need 5 versions of solitaire
Thanks again for all you do...
Neil
More news... sad
Ok so on a download just did a cancel since didn't want the file and locked up... on subsequent reboot just get the spinning CM logo - really wish there was a way to boot into recovery at this point, but connecting to PC just yields "error: device not found". Of course I can reflash at this point, but not really sure how much good that will do if I can't when needed get back into recovery to restore backups etc.
I've tried all manor of connects (connect to pc while android logo is spinning, with power off to spinning logo, with power off to axp mode, with power on and already in axp mode - nothing makes adb see the device.
Any thoughts?
Neil

Battery usage
Another thing I noticed is that battery usage is not showing up.
This happens in both the AOSP and the CM9 versions.

Thorough testing
mjb32803 said:
Installed over your AOSP r1 build. Restored all apps using titanium. Seems to be working fine so far. I will test out today more thoroughly and report back.
One thing noticeable. My Quadrant score went from 2510 to 2840. Nice improvement.
Sent from my K1 using XDA Premium HD app
Click to expand...
Click to collapse
So all day today I have been exercising this CM9 build. As stated above, I flashed this from AOSP R1 using CWM. Made sure to do a wipe/factory reset, then flashed CM9, then flashed GAPPS. Nothing negative to report. I performed the following things without issue. I have a WiFi only K1. Everything is set to default except I am using Nova Launder and have 2D HW acceleration enabled. My Quadrand score was 2800 (average of 3 runs).
What I have done so far today...
Restored all my apps using Titanium Backup from SDCARD2 (32GB Class10)
Ran the following apps without issue: AdBlock, Acrobat Reader, BBC News, CNN News, Documents to Go, Angry Birds, Facebook, Twitter, MX Player v1.6e with DTS support, Google+, Google Maps, NavDroyd, SetCPU, Avast Security, Quadrant Benchmark, YouTube HD, XDA Developers HD, Rootzwiki, Temple Run, Root Explorer, Titanium Backup, Dolphin Browser, Superuser Elite, Bootlog Uptime, Amazon Kindle, Business Calendar, Amazon App Store, Paper Camera, Nova Launcher, Google Reader, K9 Mail, Netflix, Google Voice, Google Talk, GrooveIP, Weather Bug Elite, Pandora, Slacker Radio. Swiftkey3 Tablet.
Backuped of all user apps with Titanium Backup to SDCARD2
Connected tablet to Win7 x64 PC and can see both Internal Storage and SDCARD (aka SDCARD2), can copy files back and forth
Sideloaded Google Chrome as it does NOT show up in PlayStore, but it works fine (only compatability issue I had)
Front and Rear cameras take single shots
Rear camera takes video and plays back using Video Player
Rear camera takes panorama pictures
GPS seems to work fine with Google Maps (tethered to SGS3) and NavDroyd (stand alone GPS app)
Entered CWM by using Android Terminal Emulator, from prompt, #SU then #Reboot Recovery.
Performed a complete backup with CWM
End of todays testing. No freezes, No resets, No reboots
---------- Post added at 09:13 PM ---------- Previous post was at 09:10 PM ----------
ram1986 said:
Another thing I noticed is that battery usage is not showing up.
This happens in both the AOSP and the CM9 versions.
Click to expand...
Click to collapse
Battery usage is working fine for me... assuming you mean going into SETTINGS, BATTERY
I get the total time on battery and the graph showing a sloping graph
Battery percent is reflected accurately in status bar too
---------- Post added at 09:16 PM ---------- Previous post was at 09:13 PM ----------
nfigot said:
Hello,
totally new to this forum so pardon the hit and run. I have been helping someone install CM9 onto his K1 and ran into a roadblock that I can't seem to get around.
I rooted it and installed the previous CM9 that Khanning released and for a few hours all seemed well. The device then locked up and had to hard shut down. After I get about 3 rounds of the startup logo and then freeze.
I can't get back into CM9 at all so have not been able to figure out how to get back into k1recovery.
I have tried re-hooking it up to the computer and it won't see it as an external device at all (has a spot for something being recognized while the locked screen is up on the tablet, but windows just won't see it as a usable device to copy data to or from.
I also tried with the 2 lights on (sorry forget what that mode is called) connecting and a adb shell k1recovery command, but adb just won't see the device at all.
Even tried a battery disconnect (he already knew to try that from a previous lockup that could only be fixed that way - long before when it was still stock - not a recent need).
Any ideas?
Oh I also tried removing the external sdcard and putting a dummy update.zip file on it and in a directory I created called Download - no luck - read somewhere on TPTs that that could force a bootup into CMW - but no similar luck on the K1.
I know CMW installed at least before these lockups on every boot because I was able to terminal to it from within CM9 when it was working for the few hours it seemed to be all ok.
I feel bad - this is my old man and this is his first experience with bricking a device - any help appreciated.
Neil
p.s. Khanning and others - thanks for all you guys do - I use the CM9 (and hopefully CM10) on my HP TouchPad and can't believe how much enjoyment above and beyond the stock you guys add to these devices.
Click to expand...
Click to collapse
The problem sounds like you flashed THIS CM9 from KHannings old ALPHA CM9. What you probably need to do is flash KHannings AOSP R1 rom using APX mode and a PC. Once you get that flashed, use CWM to flash the NEW CM9.

mjb32803 said:
Battery usage is working fine for me... assuming you mean going into SETTINGS, BATTERY
I get the total time on battery and the graph showing a sloping graph
Battery percent is reflected accurately in status bar too
---------- Post added at 09:16 PM ---------- Previous post was at 09:13 PM ----------
.
Click to expand...
Click to collapse
Under Settings->Device->Battery, I get the battery percentage and the usage graph like you said.
But, I meant the individual app usage which is absent.
It says "Battery usage data not available".
---------- Post added at 02:10 AM ---------- Previous post was at 02:05 AM ----------
Another thing I noted elsewhere is that the system does not seem to remember App defaults. Like, if I choose to open web using the default browser and check 'use by default for this action', it continues to prompt me every time asking me to choose the default program.

Blue tooth mouse works
Blue tooth pairing with a mouse WORKS, and however when setting up Blue tooth I get a periodic "unfortunately Bluetooth sharing has stopped". I just close the message and proceed to pair and mouse pointer appeared and functions normally.
Sent from my K1 using XDA Premium HD app
---------- Post added at 10:30 PM ---------- Previous post was at 10:27 PM ----------
ram1986 said:
Under Settings->Device->Battery, I get the battery percentage and the usage graph like you said.
But, I meant the individual app usage which is absent.
It says "Battery usage data not available".
---------- Post added at 02:10 AM ---------- Previous post was at 02:05 AM ----------
Another thing I noted elsewhere is that the system does not seem to remember App defaults. Like, if I choose to open web using the default browser and check 'use by default for this action', it continues to prompt me every time asking me to choose the default program.
Click to expand...
Click to collapse
Ok then yes I have same issue, and no apps listed under battery use.
Sent from my K1 using XDA Premium HD app
---------- Post added at 10:35 PM ---------- Previous post was at 10:30 PM ----------
HDMI out is working with Netflix and audio comes through HDMI to tv correctly
Sent from my K1 using XDA Premium HD app

Another weird bug I noticed.
Reboot using power menu works ok when not charging, but doesn't reboot when charging. Just shuts down.

3g issue for K1-CM9
CM9 is great. Thanks Khanning.
But 3g is not working so may unwillingly return to official rom.
***Just installed K1_ICS_AOSP_Rooted_R2 for trying, it seems to have more issues than R1.
***Krook's K1_JB cannot be download in full so cannot try its 3g.
***Just returned to K1_ICS_120607_Rooted, though 3g is flawless but miss the CM9's smoothness and many apps cannot be accessed thru Play.
Will kind soul help to resolve this 3g issue preferably in Khanning's very smooth CM9.
Attached is logcat and dmsg log file.

mjb32803 said:
The problem sounds like you flashed THIS CM9 from KHannings old ALPHA CM9. What you probably need to do is flash KHannings AOSP R1 rom using APX mode and a PC. Once you get that flashed, use CWM to flash the NEW CM9.
Click to expand...
Click to collapse
Hello,
I can't remember the original path I took now tbh - first start was stock K1 to K1 - PermanentRoot.zip via AXP and PC... which builds from there not sure since I have collected 3 or 4 versions since then.
Ultimately what I did was re-flash via the same K1 - PermanentRoot.zip to get a good base point and then also from AXP and PC went to K1_ICS_AOSP_Rooted_R1.zip - spent the next day or so stable, but one issue remains that I'd like to fix if anybody has any thoughts.
I can go to terminal and k1recovery to get to recovery and be able to flash new roms, perform a backup etc, but I still can't get ADB from the PC to work. I connect and any ADB commands refuse to see the tablet, but I can mount it fine as an external device and see both the internal and external files on the tablet.
Is there a good way to re-install the Android SDK - maybe I picked a wrong option on install.. if nobody knows I'll just do a standard uninstall of it and reinstall it and see if that fixes it. I believe it asked some specific questions about which ADB driver to install and maybe I chose the wrong one?
We're doing a backup now and I'm going to flash to R2 from (Rom Manager) CWM recovery soon so that will test being able to update via CWM from this point forward, but in the event of a lockup and failure to be able to install again I'd like to have ADB access from the PC figured out.
Neil

Just noticed that Google Talk does NOT let me have the option to video chat. I can voice chat fine. Yes I installed latest Gapps from good.im
Can anyone else confirm this bug before I try re flashing Gapps.
Sent from my K1 using XDA Premium HD app

nfigot said:
Hello,
I can't remember the original path I took now tbh - first start was stock K1 to K1 - PermanentRoot.zip via AXP and PC... which builds from there not sure since I have collected 3 or 4 versions since then.
Ultimately what I did was re-flash via the same K1 - PermanentRoot.zip to get a good base point and then also from AXP and PC went to K1_ICS_AOSP_Rooted_R1.zip - spent the next day or so stable, but one issue remains that I'd like to fix if anybody has any thoughts.
I can go to terminal and k1recovery to get to recovery and be able to flash new roms, perform a backup etc, but I still can't get ADB from the PC to work. I connect and any ADB commands refuse to see the tablet, but I can mount it fine as an external device and see both the internal and external files on the tablet.
Is there a good way to re-install the Android SDK - maybe I picked a wrong option on install.. if nobody knows I'll just do a standard uninstall of it and reinstall it and see if that fixes it. I believe it asked some specific questions about which ADB driver to install and maybe I chose the wrong one?
We're doing a backup now and I'm going to flash to R2 from (Rom Manager) CWM recovery soon so that will test being able to update via CWM from this point forward, but in the event of a lockup and failure to be able to install again I'd like to have ADB access from the PC figured out.
Neil
Click to expand...
Click to collapse
Not to sound stupid, but debug mode is turned on on your tablet, right?

Related

[TUTORIAL] Fool-proof method to install latest CM7/MIUI without losing Baseband/IMEI

Lets get this out of the way first. I am not responsible if you screw up your phone, but you are probably here because you already screwed up your phone. I have now been through this several times over the last few days. Some will say this process is overkill, but there is no denying that it always works, so please refrain from stating the obvious.
If you have installed or updated CM7/MIUI and lost your baseband, IMEI, or both, this should help you. Due to the amount of people currently having this problem, I would recommend this be stickied at least temporarily until things are straightened out, so people can find it easily.
For Windows only, I do not have a Mac.
Step 1 - Read the entire post and understand everything involved before you attempt this. This is a long ride, probably 30-40 minutes from start to end. This is not for new people, and will assume you have a certain amount of knowledge because you attempted to flash CM7/MIUI.
DO NOT SKIP OR SHORTCUT ANY STEP IN THIS PROCESS, UNLESS I SPECIFICALLY STATED YOU MET THE CRITERIA TO DO SO. DO NOT EVEN THINK ABOUT TRYING THIS UNLESS YOU CAN REACH DOWNLOAD MODE AND RECOVERY USING BUTTONS WITH THE PHONE OFF!
Step 2 - Gather what you need...
1 - The AIO Vibrant Toolbox : http://forum.xda-developers.com/showthread.php?t=954509
Install according to directions in the post. Donate to this guy. He spent alot of time making this easy for you to do.
2 - The old CM7 install files : http://www.mediafire.com/?gn4qoonoe3cjyp6
Unzip to a location that is easy to get to.
3 - The new version of CM7/MIUI you want to install, from the thread of your choice. Donate to the developer you are using, they spend alot of their free time making your phone better. They don't get paid for it, and they dont charge you for it.
4 - Your phone, with a full battery.
Step 3 - Odin to JFD and install Clockwork 2.x
1 - Fire up the AIO Toolbox. Do not connect your phone yet, but power it down and pull your battery. See that sticker under it that says IMEI? Write it down! You will be referencing it a few times throughout the process. Start Odin and select your pit and pda files, they should automatically come up if you are using the toolbox. Hold down your volume up and down buttons, and insert your USB cable, then insert your battery. You should go to download mode, and see Odin connect. Hit start and let it fly. Once it reboots, unplug your phone. Go to settings/about phone and you should have a JFD baseband. Hit status, and check your IMEI. See how it matches the one you wrote down? Yay! Move on to the next item. If it does not, you have some reading to do because you really screwed something up, and it is beyond my power to help you...
2 - Mount phone and put the following files on the root of the sd card:
vibrant-efsbackup.zip (if you already have a backup/efs folder on your sd card you do not need this)
cm7-vibrant-initial-20110224.zip
The zip file of the new CM7/MIUI rom you want to flash.
3 - Download ROM Manager and install clockwork recovery 2.x (if you already have the update.zip on your sd card, which you should, you can also skip this) and power down your phone.
4 - Boot into recovery using the 3 button method (holding volume up and down and power, releasing power when the word VIbrant appears on your screen), hit reinstall packages, you may have to hit it twice to get to clockwork recovery. Choose to install zip from sd card, and select vibrant-efsbackup.zip. Let it do its thing. Then select reboot, and when it does, check your sd card for a backup/efs folder. Got it? Good. Power down the phone. (Obviously, if you already have the efs backup completed, you could have skipped this step.)
Step 4 - Install Clockwork 3.x and Old CM7
1 - Fire up the AIO Toolbox. Do not connect your phone yet, but pull your battery. Start Odin and hit the pda button, select the file cm7-vibrant-initial-kernel.tar from the CM7 package you unzipped (Remember, in a place that is easy to find). THIS IS IMPORTANT - UNCHECK AUTO REBOOT!!! Hold down your volume up and down buttons, and insert your USB cable, then insert your battery. You should enter download mode, and see Odin connect. Hit start and let it fly. Once it is finished, pull the usb cable. With the download mode screen still on your phone, boot into recovery using the 3 button method. You should now be in clockwork recovery 3.x. Move on to the next item! If you did not get in, you can try to pull your battery, replace it and boot into recovery from there. If you still can't get there, you get to go where the people who do not properly follow instructions go... back to Step 1.
2 - In clockwork 3.x, choose factory reset, and let it do it's thing. Then go to mounts and storage, and format system, data, and cache. Choose install zip from sd card and choose cm7-vibrant-initial -20110224.zip. As it is installing, one of the last things you see should be "restoring efs". Hit reboot when finished, and boot into CM7. When it boots, make sure you toggle the lockscreen a couple times so it connects to service. Check baseband and IMEI again. Baseband should have changed to KB1. IMEI still the same right? Awesome! Power down the phone, move to the next step! It's not? You my friend, get to meet all your other friends back at Step 1.
Step 5 - Installing what you really want...
1 - Boot into recovery using the 3 button combo. Do a factory reset, wipe cache partition, go to advanced and wipe Dalvik cache. Choose install zip from sd card, and pick that shiny new version of CM7/MIUI you picked out. You are almost there. Flash it! Reboot, and when it comes back up, take note of what time it is and DO NOT TOUCH THE PHONE FOR 15 MINUTES. You have no idea the amount of bugs this squashes. After that, check the baseband, it will be KB1 unless the rom you just flashed changed it. Check the IMEI, even though you already know it is right anyway. If it is not, do i have to say it again? You know where you are going...
2 - Destroy the paper you wrote your IMEI on, you would not want that info in the wrong hands...
3 - Enjoy your new rom
FAQ:
Q: I did everything you said, and it did not work!
A: You either skipped a step, or did not stop at the point I told you you were screwed.
Q: No, seriously, I did everything you said!
A: Seriously, I have done this 5 times in the past 3 days, and it worked every time.
Q: I installed CM7 nightly #9,10,or 11 with this method, and I have no sound on calls. What gives?
A: These builds have known issues with in call audio. Flash CM7.1
Q: Once I am on CM7/MIUI, do I have to do this every time or can I update normally?
A: Once you are on CM7 or MIUI with the proper IMEI and a good baseband, you should be able to update via the rom posting instructions. If you decided to switch from CM7 to MIUI or vice versa, I would go back to this process to get your initial installation.
Q: I installed CM7.1 and then tried to go to MIUI, and lost everything again, what happened?
A: There are changes betweeen CM7 to 7.1 that have made this difficult due to compatability issues, which is why I recommend doing this process again if you want to switch between the two.
Q: I thought there was an easier way to do this, why so many steps?
Read the first paragraph of the post, but I guess that is also asking too much...
Great post. Thanks for the info...
Pretty sure you can install the latest CM7 just via clockwork2.
i thought the baseband loss was due to kernel compatibility with the newer versions of CM7/Miui? Good post nonetheless hope it helps people out.
uurrnn said:
Pretty sure you can install the latest CM7 just via clockwork2.
Click to expand...
Click to collapse
Yes u can but some people loose baseband........didn't the op say that?
uurrnn said:
Pretty sure you can install the latest CM7 just via clockwork2.
Click to expand...
Click to collapse
Lets get this out of the way first. I am not responsible if you screw up your phone, but you are probably here because you already screwed up your phone. I have now been through this several times over the last few days. Some will say this process is overkill, but there is no denying that it always works, so please refrain from stating the obvious.
That is the first paragraph of my post. And it has already been stated that people are losing IMEI/Baseband anyway. This always works, period. Thanks for the input.
I did the steps properly and now my phone only boots to recovery...
yup i do this every time - the last few attempts with the quick two file flash method is causing all sorts of crap to go wrong on my phone even from a fresh odin - i am pdy05 and i approve this message
-screen tearing
-wifi drop
-incorrect model
-no cell connection etc....
PDY05 said:
yup i do this every time - the last few attempts with the quick two file flash method is causing all sorts of crap to go wrong on my phone even from a fresh odin
-screen tearing
-wifi drop
-incorrect model
-no cell connection etc....
Click to expand...
Click to collapse
Exactly why I went back to doing this. My last couple quick flash installs have been a disaster.
Sent from my MIUI powered Vibrant using the XDA app
Good info... subscribed for future reference. Any idea what is calling baseband/imei corruption; and why it is sporadic?
Sent from my SGH-T959 using XDA Premium App
I've done this twice now, and yet again I end up in a situation where my phone will only boot to Clockwork Recovery.
If it helps, Clockword always says E:no misc partition at the bottom. Never seen that before with all of my flashing endeavors.
darksonic said:
I've done this twice now, and yet again I end up in a situation where my phone will only boot to Clockwork Recovery.
If it helps, Clockword always says E:no misc partition at the bottom. Never seen that before with all of my flashing endeavors.
Click to expand...
Click to collapse
The e: thing means nothing, it is a old CM7 thing. At exactly what point are you getting stuck booting into recovery?
Is this your first time flashing CM7/MIUI?
Sent from my MIUI powered Vibrant using the XDA app
Great tut
I also posted something on this topic here:
http://forum.xda-developers.com/showthread.php?t=1089039
May help people that have already screwed up their EFS.
angryattheworld said:
The e: thing means nothing, it is a old CM7 thing. At exactly what point are you getting stuck booting into recovery?
Is this your first time flashing CM7/MIUI?
Sent from my MIUI powered Vibrant using the XDA app
Click to expand...
Click to collapse
Nope, I was previously running CM7.1. I said **** it and installed 7.1 from CWM2 and it worked perfectly. IMEI is correct and everything.
It seemed to **** up when ODINing the initial kernel.
darksonic said:
Nope, I was previously running CM7.1. I said **** it and installed 7.1 from CWM2 and it worked perfectly. IMEI is correct and everything.
It seemed to **** up when ODINing the initial kernel.
Click to expand...
Click to collapse
Glad it worked out for you anyway, may have been a bad download. Those are the exact files I use to do it... and I am on CM7.1 using this method after losing my IMEI trying to go from clockwork 2...
Was it when you tried to boot into clockwork 3 for the first time, or after you wiped and flashed the initial rom?
Sent from my MIUI powered Vibrant using the XDA app
Poser said:
Good info... subscribed for future reference. Any idea what is calling baseband/imei corruption; and why it is sporadic?
Sent from my SGH-T959 using XDA Premium App
Click to expand...
Click to collapse
Completely clueless, but that is why I put this up, so after I had a definite way to fix mine, others could fix theirs. The problem itself seems to be more with MIUI than CM7, but it is happening with both. I would not be surprised if it happened to more people who have simply not checked their IMEI, and are working off a generic one because they have service.
Curious what happens if the imei is in the wrong hands and stolen
- excuse my grammar im using swype-
My external sd card is not recognized after successfully booting MIUI. This has been bother me for days now... I see sd card icon in the status bar and it says "sd card safe to remove" I tried mounting/unmounting/formating - I only see the main partition when i plug usb cable to windows. EMMC folder is empty as well.
Does anyone else experience this?!
what i dont understand is Rom manager premium made it so easy a baby could install it! download rom off rom manager premium CM7 nightlies make sure u flash clockwork recovery vibrant mtd and 3x and not 2x! install download and wait......way too easy!!!!!!!!!!!!!!!!!
Make sure u wipe data, wipe dalvik and backup rom when it asks its pretty simple.
I've got a better way, install Rom manager, select rom, click flash. TADA!!!!

LG Marquee has CWM.

Okay guys, I thought what the hell, I'll try the LGE Black option in ROM manager and see what happens.
IT WORKS!!!!!!!!!!!!!!!!!!
Use the volume keys to move and the search button to select.
The first boot into it, you will get all kinds of errors saying it can't mount certain files.
Go to "Mounts and Storage" and select "mount /cache". The errors will go away.
Everything seems to work as it should.
A quirk that I found was that until you "Wipe cache partition" you will be stuck in recovery and you cannot get out. Once done, "Reboot System Now" and everything works great.
One last thing, I cannot figure out how to key combo into recovery. I have to use ROM manager to access it.
NOTE:CWM messes up turning off the phone. Pressing the power button and selecting OK to turn off will now reset the phone and then boot it back up. Now only way to power off phone (besides pulling battery) is to use ROM Manager to boot into recovery, wipe the cache, then select power off.
good news dude
no key combo on Black, I think it's the same on Marquee
tcaudill01 said:
NOTE:CWM messes up turning off the phone. Pressing the power button and selecting OK to turn off will now reset the phone and then boot it back up. Now only way to power off phone (besides pulling battery) is to use ROM Manager to boot into recovery, wipe the cache, then select power off.
Click to expand...
Click to collapse
This seems weird; does CWM allow you to make a backup?
Have you tried loading a backup to see how it works?
hoovhartid said:
This seems weird; does CWM allow you to make a backup?
Have you tried loading a backup to see how it works?
Click to expand...
Click to collapse
I have tried and you do not get a complete backup. You do get the boot and recovery img files but not much else.
I have tried (without luck) via twitter to contact Koushik Dutta, the man responsible for CWM. We really need his assistance for this to move forward.
well, I know its possible to use the Android Terminal Emulator to flash a custom recovery image from your sd card;
thedroiddemos.com/2010/07/23/how-to-flash-a-custom-recovery-on-android-tutorial
I wonder if it can be used to generate an image of your phones current state to create your own back up and file it on your sd card.
Haven't tried to do any type of restore yet. I have managed to get the boot and recovery IMG files and used adb to get a copy of the system files.
(The LG-Black Dev's are using these files to develop their Gingerbread version.)
I might try to figure out how to do this from the link you gave. If I do, I will post what I find out.
Honestly though, after guinea pigging the root and CWM without total bricking the phone, I'm afraid of pushing my luck too far.
It would be nice if some more people would jump in and help with some of this but I guess the phone is to new to have very many users. Seems like I see the same few names on the three Marquee forums I know of.
I know what you mean. I'm starting to think you are the only one out there with a rooted Marquee.
Hang in there... I think once all the chaos from the iphone settles down, more people will have the Marquee. Most stores in my area are saying they don't even have it. They don't even have them on display.
tcaudill01 said:
I have tried (without luck) via twitter to contact Koushik Dutta, the man responsible for CWM. We really need his assistance for this to move forward.
Click to expand...
Click to collapse
any response from koush?
Also, I was wondering...
I often download files from peers in forums instead of going strait to the source. I saw that you got CWM from the android marketplace via Rom Manager...
Do you have the premium version?
market.android.com/details?id=com.koushikdutta.rommanager
also, I was reading at the link above and noticed you can email koush directly for help with CWM via [email protected]
Have you tried this?
Also, according to this;
//market.android.com/details?id=com.koushikdutta.rommanager.license
it mentions the following;
"Did flashing break your recovery? Flash an alternate/experimental one and flash back to fix!"
I'm still looking for a place to download alternate/experimental ones but I think the latest is here;
koushikdutta.com/2010/02/clockwork-recovery-image.html?widgetType=BlogArchive&widgetId=BlogArchive1&action=toggle&dir=open&toggle=YEARLY-1293868800000&toggleopen=MONTHLY-1265011200000
where it says "ROM Manager (Changelog)"
also, there are other methods of getting in touch with koush here;
koushikdutta.com/search?updated-min=2011-01-01T00%3A00%3A00-08%3A00&updated-max=2012-01-01T00%3A00%3A00-08%3A00&max-results=8
via facebook, google+, etc...
hope this helps!
hoovhartid said:
any response from koush? None yet. I know he is a busy person so I am patient.
Also, I was wondering...
I often download files from peers in forums instead of going strait to the source. I saw that you got CWM from the android marketplace via Rom Manager...
Do you have the premium version? Yes I use the Premium version
market.android.com/details?id=com.koushikdutta.rommanager
also, I was reading at the link above and noticed you can email koush directly for help with CWM via [email protected]
Have you tried this? I did not know this and I appreciate this information. I have just sent him an email with all of the things that do and don't work.
Also, according to this;
//market.android.com/details?id=com.koushikdutta.rommanager.license
it mentions the following;
"Did flashing break your recovery? Flash an alternate/experimental one and flash back to fix!"
I'm still looking for a place to download alternate/experimental ones but I think the latest is here;
koushikdutta.com/2010/02/clockwork-recovery-image.html?widgetType=BlogArchive&widgetId=BlogArchive1&action=toggle&dir=open&toggle=YEARLY-1293868800000&toggleopen=MONTHLY-1265011200000
where it says "ROM Manager (Changelog)" Until we have a backup to work with, I will stick with the market version.
also, there are other methods of getting in touch with koush here;
koushikdutta.com/search?updated-min=2011-01-01T00%3A00%3A00-08%3A00&updated-max=2012-01-01T00%3A00%3A00-08%3A00&max-results=8
via facebook, google+, etc...
hope this helps!
Click to expand...
Click to collapse
ALL help is greatly appreciated.
so, I've done some digging...apparently the marquee isn't the only LG phone not supported by the ROM manager app.
http://forums.androidcentral.com/lg...ad-only-memory-manager-optimus-s-brick-6.html
post numbers 58-60 were disappointing to read...
...but maybe facebook is the best way to contact
Lq marquee key combo is volume down and power button until softkeys start to flash then release
worfner73 said:
Lq marquee key combo is volume down and power button until softkeys start to flash then release
Click to expand...
Click to collapse
Dang, that key combo should be implemented on Optimus Black as well. Marquee has the goodies.
Sent from my Optimus Black using xda premium
worfner73 said:
Lq marquee key combo is volume down and power button until softkeys start to flash then release
Click to expand...
Click to collapse
I have verified this to work on my LG Marquee.
Thanks Worfer73.
tcaudill01 said:
I have verified this to work on my LG Marquee.
Thanks Worfer73.
Click to expand...
Click to collapse
wait...this works for CWM and gets you into recovery...but the recovery itself is still temperamental correct? still no way to create a nandroid backup?
hoovhartid said:
wait...this works for CWM and gets you into recovery...but the recovery itself is still temperamental correct? still no way to create a nandroid backup?
Click to expand...
Click to collapse
hey guys, I have done a backup of my stock rom from cwm, I think it worked, but I have no reason to flash it back yet, I'm as geeked as everyone else for roms on this thing, but I still miss my captivate, firefly was awesome
well then, THAT's interesting. So everything appears to be working in CWM for you? Just using the OPBlack version?
Rmcc seemed to imply it would work here:
https://twitter.com/#!/CM_arcee/status/151624356311744512
https://twitter.com/#!/CM_arcee/status/151712659794964481
But I honestly haven't had enough time to delve into this much. I had the Marquee for about 2 weeks or so, but had to temporarily switch for work-related reasons. Will probably switch back to it as my personal phone, so I would love to see / hear some progress on this.
Didn't work quit as well for me... When I tried to mount the cache I got an error. The only way I could get out of the recovery screen was to 'Wipe Cache Partition'
By the way THANK YOU for posting that. I could not figure out how to get out of that screen. My phone is rooted and I have been waiting for people to develop... but it looks like there are not many people developing on the Marquee
---------- Post added at 12:06 PM ---------- Previous post was at 11:59 AM ----------
BTW I posted a request for the Marquee on Cyanogenmod facebook page... if we all do the same we may be able to get some love.

[Q] Unable to boot tablet.. please help

Hi I hope someone can help me as i'm a little stuck how to proceed....
Basically I purchased a new P7310 tablet 2 days ago with the idea of installing lovely JellyBean.
I firstly 'Rooted' the following the instructions on http://forum.xda-developers.com/showthread.php?t=1406137 and then installed and run 'Superuser' without problems.
Next I installed 'Titanium Backup Root' and 'RomManager from ClockWorkMod', I run Titanium Backup Root and carried out a full system and apps backup successfully.
Next I connected my tablet to my Windows PC and downloaded the latest two ROM zip files from http://forum.xda-developers.com/showthread.php?t=1777398 and copied them to the Root of my SDcard.
I then disconnected my tablet and clicked the 'RomManager' app, once opened I clicked on the 'Boot in Recovery' button and a message appeared saying it needs to install the Recovery Manager, so I clicked OK. Next a success message appear saying it installed OK. So I decided to click the 'Backup ROM' button before I started just to be safe but the tablet switched off... black screen, it then loaded up but the Samsung logo flash up then disappeared.
Now If I try to power on the tablet I just get to the logo then powers off, if I try to boot into recovery mode it displays the two icons on the screen ok but selecting the left icon (with mini android character) it powers off. If I select the other green icon it shows me a message about installing custom roms and asks me to connect the tablet to a USB... followed by asking about 'odin3'?
I'm totally confused what I can do now, as I say I haven't actually got to the point of installing the JelyBean Rom, I just wanted to make a few backups first.
Any help much appreciated..thanks.
From further investigation I think I have soft bricked my tab :crying:
Now trying to find out how I might be able to fix it, found this post which I really hope will help me - http://forum.xda-developers.com/showthread.php?t=1133590
Any help with trying to fix my tab would be great.. thanks.
Fixed it thanks to this forum :victory:
Encase anyone else has the same issue I just downloaded the original ROM file for my UK P7310 (P7310XEUKJ4_P7310XXKJ4_HOME.tar.md5) which was approx 600MB (once extracted to desktop) from http://forum.xda-developers.com/showthread.php?t=1582943
And followed the screen shot instructions further down the thread from user 'suwandiapr' which informed me which options to have selected when runing the 'Odind3 v1.85' application.
The whole process took around 10 minutes to complete.
Sounds like ROM Manager screwed you. This is why I'm not a big fan of these Play Store release ROM/recovery installers. You can't test on every device, therefore there are going to be issues and some people are going to end up with bricks. Sure, they're convenient, and they work most of the time, but when they don't work, it has the potential to be catastrophic.
IMO, stick with flashing things through working recovery (or Odin the first time).
EDIT: Also, glad you're back up and running.
had same problem with p7300 after Rom Manager.
now using cwm for total backups and 'my backup' for applications when moving between different roms.
I'll second everything said. Always use a recovery to flash a rom. Never rom manager or other such things i hard bricked my i727 using goo manager. Don't trust the rom either rom manager or goo manager say are compatible with you device. Pretty sure my hard brick was from a gapps goo manager said was compatible with the rom. Check xda and what others have said works
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
The best option to flash any rom is from the cwm recovery, unless its a stock rom and u want to use Odin from dl mode. Also, some versions of cwm recovery are deemed dangerous for ics. Pls visit tracids thread in development for details.

Cannot get into recovery

I have a LG Thrill that is stock ICS. If I boot the phone and check all the buttons the buttons work, however when I try to boot into recovery the phone just boots or turns off. I hold the 3d and volume down button then push the power button until a vibration and lg logo then release the power button. I've tried to go thru adb to reboot into recovery but I cannot see the device in adb.
Have you actually installed cwm recovery?
Sent from my LG-P920 using xda app-developers app
No, I'd love to be able to install CMW or TWRP but the guides I have found all say that I need to be able to boot into recovery.
You can install CWM (or TWRP) by flashing it with Fastboot, but you will need to place a recovery image file named "cwm.img" in the CWM folder in the Fastboot pack. Some available packs (check the Optimus 3D dev section, same device, Euro flavor) have the image files already included, I think.
The method I have mostly used is to flash xbsall's rooted ICS with recovery.
http://forum.xda-developers.com/showthread.php?t=2195753
His rooted ICS uses a type of recovery that is in system partition (not recovery partition). So if you want that, or you do not want to flash your device, use Fastboot (or one of the customized variants)
First, thanks for the help. I now have superuser available and couldn't be happier. The reason I decided to do this was that I couldn't get the wifi to switch on and even with the super user access it won't. Should I assume that this is a problem with the phone or is this something that would work if I were to roll back to gingerbread?
It's most likely a problem with the ROM/kernel you're using. I'd switch to another.
Sent from my LG-P920 using xda app-developers app
I can't say thanks enough for holding my hand so far. Is there a good guide that you would recommend for me to look at. Some of the ones I've viewed here have different information for each of them. Is the reason that thus phone is so different from what I'm used to due to the omap processor?
Sent from my SGH-I727 using Tapatalk
I had the wifi problem a while back; it was due to me installing a custom ROM without doing required wipes in recovery before installing it. Not sure how you got to ICS, but if you follow the guide I linked above it should solve your problem. You don't have to install the custom ROM if you don't want. Just stop after installing rooted ICS. Be advised that driver install for pc is fiddly, hence the detailed install instructions.
Can anyonne throw me a line here. When I install the omap drivers for the phone (step f4.1-4.5) the phone still keeps disappearing from the device drivers. Even disconnecting and reconnecting with the volume up button pressed isn't helping. Any ideas? I've tried uninstalling all of the drivers, using system restore to roll back, different cables. It used to work, now it doesn't any ideas?
If you mean the way it keeps blinking on and off, be ready with the mouse. Watch for when it appears and quickly right click on it, you kind of have to catch it. Then point it to the driver in the Fastboot folder (not the one in the omap4flash installer folder) as described. Once that is done you unplug phone, then replug, volume up, and let the two LG drivers install. All LG stuff on pc should be uninstalled and pc rebooted before beginning with all this. Also, some antivirus software can mistake the driver as being malicious and delete it when unraring the Fastboot folder, without it notifying you. And if you have a custom bootloader on your phone you may need to skip running omap4flash installer; they seem to not agree somehow.

[Q] LG D415 L90 - Stuck On "udc_start()"

This is the first issue with an android phone I've had in a while where I have absolutely no idea what I should do next.
The music player was beginning to stutter a LOT on my install of CM11, and I was having issues where if I selected a song to play on my music player, the volume would suddenly spike to THE HIGHEST LEVEL, and I had to adjust the volume down to get it to reset back to normal. So I figured I'd wipe everything clean and re-install CM11. I didn't just wipe /data and /cache, but I also wiped /system because I believe the issues mentioned above came from a Sony Walkman Mod ZIP I flashed. So after formatting all of the partitions, I went to the "Install" button of TWRP (by the way, I am using TWRP 2.8.1.0) to re-install the CM11 ROM. When I tried to open the CM11 ZIP, TWRP gave me an error saying it couldn't open the file to flash it. I tried using adb sideload as well but adb sideload gave me a similar error.
So I figured it was just an issue with TWRP and that I'd have to boot into fastboot and flash a different recovery image that I know works, like shinobisoft's CWM. I power off the phone, hold the volume up button while plugging the phone back in to the USB port and I am greeted with the Download Mode screen as usual. Here's where things start to get unusual: instead of the phone taking about 1-2 seconds and presenting me with a "Fastboot Ready" line of text or something similar to that, the Download Mode screen hangs on [270] udc_start().
What should I do from here? I tried flashing back to the stock KDZ, but Download Mode needs to be working to do that. Also, I can still get into TWRP recovery just fine, and TWRP can still see all of my partitions.
jasonmerc said:
This is the first issue with an android phone I've had in a while where I have absolutely no idea what I should do next.
The music player was beginning to stutter a LOT on my install of CM11, and I was having issues where if I selected a song to play on my music player, the volume would suddenly spike to THE HIGHEST LEVEL, and I had to adjust the volume down to get it to reset back to normal. So I figured I'd wipe everything clean and re-install CM11. I didn't just wipe /data and /cache, but I also wiped /system because I believe the issues mentioned above came from a Sony Walkman Mod ZIP I flashed. So after formatting all of the partitions, I went to the "Install" button of TWRP (by the way, I am using TWRP 2.8.1.0) to re-install the CM11 ROM. When I tried to open the CM11 ZIP, TWRP gave me an error saying it couldn't open the file to flash it. I tried using adb sideload as well but adb sideload gave me a similar error.
So I figured it was just an issue with TWRP and that I'd have to boot into fastboot and flash a different recovery image that I know works, like shinobisoft's CWM. I power off the phone, hold the volume up button while plugging the phone back in to the USB port and I am greeted with the Download Mode screen as usual. Here's where things start to get unusual: instead of the phone taking about 1-2 seconds and presenting me with a "Fastboot Ready" line of text or something similar to that, the Download Mode screen hangs on [270] udc_start().
What should I do from here? I tried flashing back to the stock KDZ, but Download Mode needs to be working to do that. Also, I can still get into TWRP recovery just fine, and TWRP can still see all of my partitions.
Click to expand...
Click to collapse
Check your PM's
shinobisoft said:
Check your PM's
Click to expand...
Click to collapse
I tried your suggestion of holding the power button but that didn't work. And this is the ONE TIME where I did not make any backups. I couldn't because TWRP couldn't read my /data partition since my phone was encrypted, but before this whole thing happened I formatted /data as EXT4 (which I did before without issue), so I don't think it should be encrypted anymore.
jasonmerc said:
I tried your suggestion of holding the power button but that didn't work. And this is the ONE TIME where I did not make any backups. I couldn't because TWRP couldn't read my /data partition since my phone was encrypted, but before this whole thing happened I formatted /data as EXT4 (which I did before without issue), so I don't think it should be encrypted anymore.
Click to expand...
Click to collapse
What I said about the power button was only to help you get out of fastboot mode so you could try to get to fastboot mode again. LOL.
BTW, I always have a least 2 backups on my sdcard.
You're in a bit of a pickle... I need to think about this for a few...
**BUMP***
I went back to TWRP and tried flashing a PurePerformances .zip and it was able to flash just fine. But even with a fresh download of the CM11 ZIP It still doesn't work. Maybe I'll try flashing a different ROM.
jasonmerc said:
**BUMP***
I went back to TWRP and tried flashing a PurePerformances .zip and it was able to flash just fine. But even with a fresh download of the CM11 ZIP It still doesn't work. Maybe I'll try flashing a different ROM.
Click to expand...
Click to collapse
That's really strange. As I stated in my ROM thread, I haven't changed anything with the last build...
Whoa, just noticed the 12/2 build! I was trying to flash the 10/22 this whole time. I'll try flashing 12/2.
I tried the new build with ADB Side load. It was able to load the zip!
But the device could not be found...
Sent from my MB520 using XDA Free mobile app
jasonmerc said:
I tried the new build with ADB Side load. It was able to load the zip!
But the device could not be found...
Sent from my MB520 using XDA Free mobile app
Click to expand...
Click to collapse
So ADB debugging isn't enabled in TWRP 2.8.1.0? Have you tried another recovery? And why sideload? Why not straight flash?
shinobisoft said:
So ADB debugging isn't enabled in TWRP 2.8.1.0? Have you tried another recovery? And why sideload? Why not straight flash?
Click to expand...
Click to collapse
I can't load another recovery on here without going into fastboot. And I am currently in the process of attempting a straight flash. I am going to save the rom on an SD card on another phone then inset it in the L90.
Sent from my MB520 using XDA Free mobile app
...And the moral of this story is: change your USB cables
I'm feeling a little stupid right now...
Sent from my MB520 using XDA Free mobile app
jasonmerc said:
...And the moral of this story is: change your USB cables
I'm feeling a little stupid right now...
Sent from my MB520 using XDA Free mobile app
Click to expand...
Click to collapse
LMFAO. Lesson learned I hope. LOL
shinobisoft said:
LMFAO. Lesson learned I hope. LOL
Click to expand...
Click to collapse
I've never had this happen to me before. What's weird is the cable was able to transmit power to the device, but not data.
Sent from my LG-D415 using XDA Free mobile app
jasonmerc said:
I've never had this happen to me before. What's weird is the cable was able to transmit power to the device, but not data.
Sent from my LG-D415 using XDA Free mobile app
Click to expand...
Click to collapse
Ya got me. I use the same cable for PC communication. My main charger is a hardwire charger so I basically just leave my data cable attached to my PC. In fact, it's the same cable I started modding my P506 with about 2 years ago .
jasonmerc said:
...And the moral of this story is: change your USB cables
I'm feeling a little stupid right now...
Sent from my MB520 using XDA Free mobile app
Click to expand...
Click to collapse
Speaking of feeling stupid, is that the fastboot screen? Like, if I have that screen and it says "hold up till download mode" does that mean I can do fastboot commands like that????? Maybe I DID enable fastboot mode????
whodisname said:
Speaking of feeling stupid, is that the fastboot screen? Like, if I have that screen and it says "hold up till download mode" does that mean I can do fastboot commands like that????? Maybe I DID enable fastboot mode????
Click to expand...
Click to collapse
Yes, that is the fastboot screen in the picture and it passed the UDC START. What you have to do is power off the phone, hold volume up while inserting USB cable to phone, and KEEP HOLDING VOLUME UP until you see something like "fastboot: processing commands". Then you will be in fastboot.
Sent from my LG-D415 using XDA Free mobile app
How long you got to hold it? I been holding it for about 3 min and counting'
---------- Post added at 11:42 PM ---------- Previous post was at 11:27 PM ----------
http://forum.xda-developers.com/showthread.php?t=2559363
---------- Post added at 11:42 PM ---------- Previous post was at 11:42 PM ----------
For your problem
whodisname said:
How long you got to hold it? I been holding it for about 3 min and counting'
---------- Post added at 11:42 PM ---------- Previous post was at 11:27 PM ----------
http://forum.xda-developers.com/showthread.php?t=2559363
---------- Post added at 11:42 PM ---------- Previous post was at 11:42 PM ----------
For your problem
Click to expand...
Click to collapse
Its only for a few seconds.
Sent from my LG-D415 using Tapatalk
I don't think I got it. It goes into the screen but if I hold down the button it stays the same. I unplugged the coed and plugged it back in (saw something about that here but I can't find it again) fastball devices comes back with nothing. Fastboot OEM unlock gets "waiting for device" as does fastboot reboot and fastboot flash recovery recovery.IMG (I have twrp in my fastboot folder called recovery.IMG) does download mode look like all the rest of the LG phones I have seen with the S/W UPGRADE IN PROGRESS DO NOT TURN OFF TARGET. Just asking because these things are subject to change!
whodisname said:
I don't think I got it. It goes into the screen but if I hold down the button it stays the same. I unplugged the coed and plugged it back in (saw something about that here but I can't find it again) fastball devices comes back with nothing. Fastboot OEM unlock gets "waiting for device" as does fastboot reboot and fastboot flash recovery recovery.IMG (I have twrp in my fastboot folder called recovery.IMG) does download mode look like all the rest of the LG phones I have seen with the S/W UPGRADE IN PROGRESS DO NOT TURN OFF TARGET. Just asking because these things are subject to change!
Click to expand...
Click to collapse
Download mode and fastboot mode are the same. S/W Upgrade mode is totally different. S/W Upgrade mode is what you should have if you DIDN'T zero out your laf partition. If you did zero out your laf partition, then you should have access to fastboot/download mode.
If the fastboot executable isn't recognizing your device, then you must be in S/W Upgrade mode, or fastboot mode on the device had become corrupted somehow.
I remember reading in the Android Original Development section that you used the script to increase your internal data storage. Does that script mess with the laf partition? If so, there's your issue.

Categories

Resources