I just reset my Nook HD Plus (Ovation) with CM 10.2, and ran into an issue where Setup Wizard is crashing upon first boot. This is due to some erroneous interactions between ROM & the version of the GAPPS I installed a while ago. Back then, I booted once first, and only then installed GAPPS, so things worked fine.
Strangely enough, until Setup Wizard is run once, the tablet is not fully functional. Swipe down does not work to get to Settings, had to run Settings as an app. Also, Home button does not work either.
Here is how I fixed the issue.
1) Reboot to TWRP, use the built in file manager to rename /system/apps/SetupWizard.apk to *apk_ (do not delete!)
2) Reboot into System, navigate half-halfheartedly to Settings (it is not well functioning at this point), turn on ADB, authorize your computer, then disconnect
3) Now, use a File manager (with root), rename /system/apps/SetupWizard.apk_ back to *apk
4) Plug ADB cable into your PC - at this point "Setup Wizard" is activated by ADB connection
5) Go through Setup Wizard, and that is it!
A few more links out there on the topic:
https://android.stackexchange.com/q...ooping-unfortunately-setup-wizard-has-stopped
Related
Ok, so I did all of these steps below and I was unable to get the marke to load. So after reading some of the post on here I went ahead and redid them again. Now when I try to bring my Wifi up it says error..and then I don't have a Mac address either. I was able to get the WiFi to work after the first root, but now I can get it to work.
1. Get the 1.3 update. YOU WILL LOSE ROOT! But don't fret - you shouldn't lose anything else.
2. Shut down your nook and boot with the bootable card.
3. Install manualnooter-4-5-18.zip and then reboot.
4. You have root now, so go launch the market and sign in.
5. Shut down your nook again and boot with the bootable card.
6. This time install manualnooter-4-6-16a.zip.
7. Reboot again.
8. Put your regular "data" SD card in for this step - Go into Rom Manager and run the 'Fix Permissions' option.
9. Go into Nook Color Tools and note the check box at the top. After 1.3 for most (if not all) people, the label is missing now. Uncheck and check the box anyway and close NCT.
10. Reboot
This is a 100% AOSP ICS build for the Lenovo Ideapad K1. It will wipe your entire system. You will lose all data except what is stored on the EXTERNAL sdcard.
Includes
Android ICS 4.0.4
ClockworkMod Recovery 6.0.1.0
Google Apps
Rooted version includes Superuser and busybox
Issues
Video Camera face effects
Rotation Lock Switch (Software switch works)
Downloads
As always flash at your own risk. I'm not responsible for your device.
Nvflash versions
K1_ICS_AOSP_Rooted_R2.zip
dfddf13bf51e357a4964a11a8adbfd53
Mirror
K1_ICS_AOSP_Stock_R2.zip
b359ec6a06289ccf8c6b83f07346be17
Mirror
CWM versions
CWM_K1_ICS_AOSP_Rooted_R2.zip
90341324a0927f3035e92dc81ffb9416
Mirror
CWM_K1_ICS_AOSP_Stock_R2.zip
c026beb4dc2a11defbc3c3bcbec041cc
Mirror
Instructions
Nvflash version
1. Download one of the packages above and extract it to a directory
2. Power off device
3. Press and hold both the Vol + and Vol - buttons
4. While holding both Volume buttons power the tablet on
5. The screen should go black and the two front LED's should remain lit. You are now in APX mode
6. Connect your device to USB
7a) Windows: Install the APX drivers from the 'drivers' folder
Double click the 'flash-windows.bat' file
7b) Linux: run 'chmod +x flash-linux.sh && sudo ./flash-linux.sh' from the extracted directory
CWM version
1. Download one of the CWM_K1_*.zip versions and move to external sdcard
2. Reboot into recovery
3. Install zip from sdcard
4. Choose zip from sdcard
5. Flash the update.
How to boot into recovery
Non-rooted version
1. Make sure you have the Android SDK installed. http://developer.android.com/sdk/index.html
2. Make sure USB Debugging is enabled on the tablet. Go to Settings > Developers options > and check "USB Debugging"
3. Connect the device to USB
4. Open a terminal or command prompt window and type
Code:
adb shell k1recovery
Rooted version
From a Terminal Application
Run the follow two commands
Code:
su
k1recovery
From adb
1. Make sure you have the Android SDK installed. http://developer.android.com/sdk/index.html
2. Make sure USB Debugging is enabled on the tablet. Go to Settings > Developers options > and check "USB Debugging"
3. Connect the device to USB
4. Open a terminal or command prompt window and type
Code:
adb shell k1recovery
Changelog
Code:
8/11/2012 R2
-Fixed external sdcard permissions
-Fixed keylayout
-Modifed build.prop to spoof Moto Xoom (App compatibility)
7/31/2012 R1
-Initial Release
Source Code
http://github.com/khanning
So from now on we will be able to flash future updates through recovery without wiping everything?
So from now on we will be able to flash future updates through recovery without wiping everything?
Click to expand...
Click to collapse
Exactly, future updates will be CWM flashable .zip's.
All, I just noticed that Google Chrome isn't showing in the market, but Maps is. I swear it was showing up when I was testing previously. Will have to investigate...
khanning88 said:
Exactly, future updates will be CWM flashable .zip's.
All, I just noticed that Google Chrome isn't showing in the market, but Maps is. I swear it was showing up when I was testing previously. Will have to investigate...
Click to expand...
Click to collapse
I dont know if it's me or because of the ROM. WIth the rooted ROM before AOSP, I was able to install Chrome with a APK downloaded from mobilism but sometimes the pages are fine then just rendered white , for all tabs.
Does anybody use SKYPE ? When I do video chat, my broadcast picture stretched vertically when I broadcast-only (no picture feed from the other side), the picture my friend saw is fine though.
Many thanks for your hard work.
That is the main thing that i hate about Lenovo's Factory ICS image, i still cant install Chrome or Evernote, or many of my NEEDED apps. I hope that you get this working soon. or at least a temp fix.
Just flashed the rooted aosp, the boot animation is a nice touch. The app compatibility issue seems fully resolved outside of Chrome, pointed out already, which is no biggie for me atleast. I still can sideload Chrome and runs perfectly. Also, so far the dictionary miss-spell issue doesnt seem to be a problem anymore. Maybe its just me but touch responsiveness seems a little better/quicker with this build. Just tried using the command 'k1recovery' to boot into recovery and it keeps giving me an error relating to permissions, saying it cant create /dev/block/mmcblk0p5. Seems like I just need to change the permissions of the /block folder but wasnt sure if I was just not doing something right.
Massive improvements from Lenovo's vanilla ICS still, thanx khanning!
Noticed some graphical glitches. Screen goes black if switching orientations on lockscreen and home screen.
@Khanning88 Can you provide a mirror please? Goo.im is down and shows "Internal server error".
Never mind. It's up again.
me_is_rushin said:
Noticed some graphical glitches. Screen goes black if switching orientations on lockscreen and home screen.
Click to expand...
Click to collapse
Yup the screen flashes when switching orientations, for a split second...
That's great. thanks for share.
Flashed this one and works wonderful.
Rebooting to recovery didn't work 1st, but then mounted filesystem as rw and tried the command and could get to recovery.
Got an error "Can't mount backup path" when trying to make a backup. Is it because I didn't have an external sd card.
If yes, is there a way to take a nandroid backup to internal memory?
BTW, thanks again for providing this ROM.
Thanks khanning88 for giving this fabulous AOSP ROM
Does this ROM support the Wifi+3G version?
I found some issues installing apps, including some games, Zinio magazine reader, google earth, etc, all saying incompatible with my device.
I experienced alot of freezes while restoring my backup with titanium backup.
I keep testing if it also occurs in normal use.
Installed AOSP-Rooted. So far, Chrome (already noted as issue in OP), and POGO Games showing up as Incompatible.
Other than that, and possible other apps being incompatible, looks great and installed as easy as can be.
Thanks Khanning!
-Cybie
we need an easy way to enter recovery. Rom Manager button doesn't work.
Reboot recovery from terminal emulator doesn't work either.
Could you implement the nice options when turning the unit off?
several more freezes. obviously not depending on any special app..
erickwan said:
Does this ROM support the Wifi+3G version?
Click to expand...
Click to collapse
I'm not sure if 3G works since I have a Wifi version, but if someone with a 3G version could meet me in freenode IRC room #ideapad-k1 I would be happy to work on it. If you aren't familiar with IRC just go to this link and join the chat.
http://webchat.freenode.net/?channels=ideapad-k1
we need an easy way to enter recovery. Rom Manager button doesn't work.
Reboot recovery from terminal emulator doesn't work either.
Could you implement the nice options when turning the unit off?
Click to expand...
Click to collapse
From a terminal app type:
Code:
su
k1recovery
Or from adb type:
Code:
adb shell k1recovery
Either method will reboot the device into recovery. I will work on adding the power menu options later.
several more freezes. obviously not depending on any special app..
Click to expand...
Click to collapse
I haven't experienced any "freezes" but when it happens to you could you please document what you were doing and take a logcat to help debug.
http://rootzwiki.com/topic/11930-learn-to-logcat-like-a-pro/
Here is a very simple way to reboot into khanning's CWM recovery.
1. Playstore --> Download/Install aShell app
2. Run App
3. Select Checkbox for "Root" (In Settings, you can set app to start Root as Default)
4. type "k1recovery" into textbox
5. press "start command" button.
Simple, no need to be in "true shell" mode. This app allows you to run shell commands without the terminal. Great for newbies, quicker for anyone.
Hope this helps!
-Cybie
Here is a quick fix for the hardware keys. Just flash the .zip file from recovery. Updated first post with more detailed booting into recovery instructions.
K1_keylayout_fix.zip
In this guide I'm going to assume you know how to get SDK working. Here's the video if you don't: http://www.youtube.com/watch?v=oaNM-lt_aHw
This is in reference to Hascode's guide http://forum.xda-developers.com/showthread.php?t=2128175]
for steps 4.5 AND BEYOND or if you just want to enter Fastboot for yourself.
1. Download this: https://dl.dropbox.com/u/54456659/KFFirstAide64.zip (64 bit) OR https://dl.dropbox.com/u/54456659/KFFirstAide32.zip (32 bit)
Latest version of Java: http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html
Source: prokennexusa
2. Extract it to your C Drive (or primary), keep the folder name the same KFFirst AIDE (Do not change it)
3. Make a Path to that folder, as shown in the video. Instead you will put ;C:\KFFirstAide
4. Download Hashcode's files and place them in that FirstAide Folder.
5. Before going further, uninstall any previous drivers for the Kindle in Control Panel and Device Manager.
6. Install ADB Drivers found within KFFirstAide -> KindleADB
7. Open up RunMe.bat and run option 11 to verify ADB is working.
8. Now run option 15 to boot into Fastboot, it may take a min.
9. Once in Fastboot, open Device Manager and update the driver, browse to C: -> Program Files -> Amazon -> Drivers -> WinUSB
10. Open CMD and type in cd C:\KFFirstAide
11. Now type in Hashcode's Fastboot lines and it should run (you can verify this because the files pushed will also show up on your Kindle)
NOTE: It's important that you do not have any ADB or Kindle drivers installed prior to installing the one in the FirstAide folder (Check Device Manager)
If you have questions, post a comment down below and I will try to answer them.
Fixed Links. Working Now.
I need some help! I was using KFFristaide64 with my 8.9 KFHD. I was trying to flash to the 8.1.2, option 5, and it flashed the boot, recovery and system, them hung at deleting user data for about 2 hours. When it finally rebooted the kindle screen never comes on, and windows emits the beeps it uses to notify a usb device attachment and removal back to back to back, and the kindle never shows up in windows or ADB. I have tried to get into fastboot with option 15 and 16 using a standard and factory USB cable, but no combination will bring up fast boot, just get the cycling connection/disconnect sounds from windows. Does anyone know if there is a way to recover from this? I have a full back up (all 11 partitions) that I created just before starting. My device was rooted before I began, but I have no clue where in the process it would be now. Can anyone help, or should I just start looking for a new 8.9 KFHD?
Whenever I try to run step 6 of this, the installer tells me that it's failed and that I need to install the drivers manually. Doing that doesn't change anything, I still get the Kindle in the device manager with the exclamation point telling me that drivers have not been installed. I've removed everything from device manager/control panel before I run it.
HTC Incredible S Rooting Guide
What we will do?
1. Install HTC Sync
2. Downgrade the HBOOT to 1.13
3. Create a GoldCard
4. Run the RUU update
5. S-OFF through Revolutionary
6. Gain root access using SuperUser
7. Install custom rom (Lacoste Mod V5)
What we need?
1. HTC Incredible S
2. MicroSD card (2GB, 4GB, 8GB)
3. USB Cable
4. Windows PC (XP, 7, 8)
5. HTC Sync
6. Downgrade
7. Goldcard
8. RUU
9. Revolutionary w/ BETA Key
10. SuperUser
11. Custom Rom (Lacoste Mod V5 is the best and has the least bug from all the custom rom I have tried, it has a
working camera, video playback, youtube, fast performance, latest 3.0 kernel, volume wake,
included Sweep2Wake to use the capacitive buttons to wake the phone.)
Notes:
1. BACKUP any data on your phone that is very important
2. It's best to factory reset your phone and format your SD card to ensure 99.9% success.
3. Don't attempt to run any registry cleaner like CCleaner or ACS until we finished rooting your phone, OK?
4. This method worked flawlessly on my HTC Incredible S GB-2.3.5 Sense-3.0 HBOOT-2.00.0000, if your phone is
Gingerbread (not Froyo or ICS), Sense 3.0 and below, HBOOT 2.0 and above, then it should work... As I have
said, all HTC Incredible S that have upgraded to Ice Cream Sandwich must DOWNGRADE it first to Gingerbread
before continuing to this tutorial... Look on threads on XDA on how to downgrade your ICS phone.
Let's Start...
1. Make sure you have Admin account on your Windows PC or else we can't proceed. It is also advisable to use a
fully charged laptop (not a slow netbook or tablet) connected through a charger so if the power supply fails
while we're in the rooting process, your phone will not be bricked... And also use a fast performance PC or
laptop to avoid hanging ar freezing computer.
2. Install the HTC Sync included, Restart PC, Uninstall the "HTC Sync" ONLY on control panel and leave all other
drivers, and please don't attempt to run any registry cleaner like CCleaner or ACS unless we finished rooting
your phone, OK?
3. Place the folder "HTC Incredible S Rooting Guide" on Desktop for easy access.
4. Open this folder, open "2 - Downgrade" folder, click "runme.cmd"
5. Now it will ask question based on your phone
a. Do you have UNLOCKED ICS?
n - if you are not running the OFFICIAL ICS rom from HTC and has the stock gingerbread rom (2.3.5)
b. Do you have root?
n - if your device is stock and never been rooted before
c. Do you want to create goldcard?
y - best choice to avoid CUSTOM ID ERROR while running RUU
d. Do you unlocked on HTCDev?
y - IF THE MAIN-VERSION 2-3 steps above tells 2.00.000 (look on the output texts above the question!)
n - IF IT DOES NOT STATE 2.00.000 or if you have an unlocked bootloader from HTCDev.
6. You may receive this error during the script operation "rm failed for /data/data/recovery/log, No such file or directory"
This error can be disregarded. NOTE: If your device shows HTC with red triangle!, press VOL+,VOL-,POWER at the same time
and choose reboot, then run the runme.cmd again...
7. Read the script and make sure there is no error, if it has, close the cmd and click "runme.cmd" again...
8. NOTE: if the script write to many "The file specified was not found," disconnect the phone and connect it
again and click "runme.cmd" again...until you succeed. If it still shows "The file specified was not found"
disconnect, restart pc and phone, and follow again the procedure.
9. If all run successfully without error, proceed with the RUU.
10. This stage is very CRITICAL, if the RUU update proceeds, do not attempt to remove the usb of turn off the PC
or else you will brick your device.
11. Click "RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199308_signed.exe"
12. Next, Next, Next...
13. If it shows CUSTOM ID ERROR, you need to create a goldcard because the downgrade kit might not succeded in
creating goldcard in step 5. Search threads on xda on how to
14. If it seems to proceed without error, do not attempt to remove the usb of turn off the PC
or else you will brick your device. Close any open application on your PC to ensure it won't hang...
15. The RUU will run less than 10 minutes, if it's 20 minutes or so, there might be a problem (slow pc, faulty usb cord, etc)
16. When its finished running, you can verify if you have 1.13.0000 hboot by entering hboot (power on phone + vol down).
17. Then you can run revolutionary to get your s-off. FIRST, press windows + R, type cmd. Open the "Revolutionay folder"
click the address bar and copy. NEXT, on the cmd, type "cd(space here) then right-click paste. NEXT, type revolutionary.exe ENTER NOW!!!
input the beta key and wait...Download recovery? y- if you have internet...
18. Power OFF, press power + vol down, and see if it says
****Revolutionary****
S-OFF
6.13
19. Reboot, connect your device through mass storage. Copy the files "Superuser-3.0.7-efghi-signed",
"Lacoste_ModV5Incredible S_03.05", and "gapps-jb-20121212-signed" on the root of your SD card (not on any folder, just on the card itself)
20. Power OFF, press power + vol down, now go into RECOVERY, Install zip on SD card and choose "Superuser-3.0.7-efghi-signed". Wait. Choose Reboot Now...
21. Power OFF, press power + vol down, now go into RECOVERY, Install zip on SD card and choose "Lacoste_ModV5Incredible S_03.05". Wait. Choose Reboot Now...
22. Now it will load for less than 5 minutes, it it stays into a bootloop for more than 10 minutes, power it off by pressing the power button for 10 seconds or
remove the battery. Press power + vol down, now go into RECOVERY, Install zip on SD card and choose "Lacoste_ModV5Incredible S_03.05". Wait. Choose Reboot Now...
It should work now...
23. After it successfully booted into the homescreen, reboot the phone twice to ensure that the Home button will still work before flashing the Google Apps because it is a bug.
Google Apps will install some Google applications like a working Play Store and Google Now (like Siri on iPhone).
24. Power OFF, press power + vol down, now go into RECOVERY, Install zip on SD card and choose "gapps-jb-20121212-signed". Wait. Choose Reboot Now...
25. Now, everything should work fine. You are now using a Jelly Bean rom and can install limited apps to Gingerbread before like Google Chrome, Google Keep,etc.
It is advisable to download these apps available only on rooted phones
Cerberus - the best anti-theft app
Game Killer - cheating games
Lucky Patcher - removing license verification and Google adds on applications.
Root Explorer - remove the old chinese app using titanium backup and replace with the official RE app.
SetCPU - overclock your phone up to 1.2 Ghz-1.3 Ghz only to avoid overheating and battery drain.
Startup Manager - remove uneccesary startup, enable all system apps to ensure a working phone.
Sweep2Wake - included, use the capacitive buttons to wake the phone.
Titanium Backup - Freeze bloatwares, uninstall system apps.
CONGRATS!!!
Now you have a rooted device, I hope you enjoy my tutorial and don't hesitate to donate to my
account because I have spend so much time writing this tutorial and I would really appreciate it.
You can email me at [email protected] so I can give you my PayPal account or answer some of
your questions...
Nickson T. Delos Reyes
Bulacan, Philippines
UPDATE: I will post some of the links of all the downloads, just wait because our internet here in the Philippines is just 512KBPS...
Hello everyone,
If someone needed I am putting this link to not lost himself in the deep of google forests.
Ruu tested and makes you return to stock. (Tested by myself).
Link : http://dl3.htc.com/application/RUU_A11_UL_K44_DESIRE_SENSE60_AIO_Aio_Wireless_US_1.11.506.8.exe
Performing the ROM Update:
1. Download and save the HTC Desire™ ROM update to your PC.
2. Connect your device to your PC via the supplied USB cable.
3. If the device is not recognized by the PC, ensure you have HTC Sync Manager installed and then disconnect and reconnect the device from the USB cable.
4. Once the device is properly recognized on the PC, locate the HTC Desire 510 ROM Update that you downloaded. Double-click on the file to launch the system update wizard.
5. Follow all of the system update wizard instructions shown on your PC.
6. Once the update is complete, click Finish in the Wizard and the device will reboot.
7. Once the device reboots, the initial setup wizard will appear.
8. Once the initial setup process is complete, open Play Store, tap the Menu icon, then select My apps and ensure all installed apps are updated.
9. After initial setup and updating all apps, the device is ready for use.
Note : If the ROM update wizard fails to recognize the device, close the wizard and then follow the steps below:
· From a powered off state, hold VOLUME DOWN while powering on the device.
· Use the volume buttons to scroll to FASTBOOT and then press the POWER button to select it.
· Connect the device to the PC while in this state and attempt the ROM update again.
To exit FASTBOOT manually, use the volume keys to navigate to REBOOT and press the POWER button to select it.
Does this work with the VM version too? If not, can you post that RUU as well? Thanks.
rjmohit said:
Does this work with the VM version too? If not, can you post that RUU as well? Thanks.
Click to expand...
Click to collapse
Considering that you've made 283 posts on xda, don't you think a simple google search would have given you the VM RUU that you want? And no Crickets will not work. Sprint, Boost, Virgin Mobile RUU
benzersizadam said:
Hello everyone,
If someone needed I am putting this link to not lost himself in the deep of google forests.
Ruu tested and makes you return to stock. (Tested by myself).
Link : http://dl3.htc.com/application/RUU_A11_UL_K44_DESIRE_SENSE60_AIO_Aio_Wireless_US_1.11.506.8.exe
Performing the ROM Update:
1. Download and save the HTC Desire™ ROM update to your PC.
2. Connect your device to your PC via the supplied USB cable.
3. If the device is not recognized by the PC, ensure you have HTC Sync Manager installed and then disconnect and reconnect the device from the USB cable.
4. Once the device is properly recognized on the PC, locate the HTC Desire 510 ROM Update that you downloaded. Double-click on the file to launch the system update wizard.
5. Follow all of the system update wizard instructions shown on your PC.
6. Once the update is complete, click Finish in the Wizard and the device will reboot.
7. Once the device reboots, the initial setup wizard will appear.
8. Once the initial setup process is complete, open Play Store, tap the Menu icon, then select My apps and ensure all installed apps are updated.
9. After initial setup and updating all apps, the device is ready for use.
Note : If the ROM update wizard fails to recognize the device, close the wizard and then follow the steps below:
· From a powered off state, hold VOLUME DOWN while powering on the device.
· Use the volume buttons to scroll to FASTBOOT and then press the POWER button to select it.
· Connect the device to the PC while in this state and attempt the ROM update again.
To exit FASTBOOT manually, use the volume keys to navigate to REBOOT and press the POWER button to select it.
Click to expand...
Click to collapse
Link is not working bro...
i have new link, check, bro