This thread is for noobs by noobs , a place to talk about the app so that we don't clutter the ROM threads .
I hope this works out and helps anyone including myself with using this app.
Here is another GUIDE by JJsax posted on The Root Of All EVO that is a lot more detailed then this one.
The Official forum for BootManager is Init2winit if you would like to learn even more about the app.
As I learn about this app ,as to how and what works with it I'll update this and maybe it will help everyone out that is trying to use BootManager.
This app also works with EVO 3D's with hboot 1.50 s-on
Thank XDA member mnomaanw for that information.
If you use this app and have the time to reply to this post , please share what ROMs you've got to work and a little info on how you installed it. This way I can add it to the op to make it easier and faster for everyone to find.
This is what I've learned so far.
How to install* ROMs via Boot Manager...
Thank seraph863 for filling me in and writing this up. I just changed a few details cause his was for a specific ROM.
MAKE SURE THE ROM IS ON THE ROOT OF YOUR SD CARD NOT IN ANY FOLDERS
1.)* PURCHASE Boot Manager. It does a License check upon boot, so your jacked version will just give you a headache. Seriously, I tried it. Doesn't work.
Here is a Market link to Boot Manager if you didn't already purchase it.
1.a) IF you didn't purchase it... WIPE ALL Boot Manager data and files, including the folder on your SD Card. Then buy it and let it setup again.
2.) Open SuperUser. Hit Menu -> Settings -> Disable Logging.
3. Open BootManager. If you're at work and on Wi-Fi, you may not pass the License check due to firewall issues. If you get a black screen, or license failures, switch to 3/4G and try again.
4.) If all is good, you're asked to Setup the Phone. Do so now. [ You will need to set up your Phone ROM any time you flash a new ROM or kernel to your phone ROM.]
5.) Once installed, hit Menu -> Settings -> Force Large Boot.img
6.) Swipe right to Slot 1. Hit Install .zip and browse to your downloaded ROM.zip file. Make sure to check the Wipe System, Data, and Cache boxes so that it will wipe before it flashes the ROM. Select EXT4 as the file structure.
[This is the important part. This build will take a LONG time. Do NOT use your phone while it is running.]
8.) Once the install has been successful if you need to flash a kernel , theme gapps etc..., go back to Slot 1 and select Install .zip (again). Choose the .zip file. Do NOT wipe system, data or cache. It will ask you to over write it just hit OK.
9.) You should now be ready to boot to your new ROM! Celebrate!
Since this is for the EVO 3D I recommend to always use ext4 as your file structure.
If you get any error messages start over.
Known working ROMs to my knowledge.
These are ROMs that I've set up.
Infected Eternity Phone ROM and sd ROM
KMyers CM7 beta 7.4* with gapps ext4 sd ROM
MeanROM ext4 sd ROM
TrevE Zone v2.3.12 ext4 phone and sd ROM
Mikrunny ext4 phone ROM and sd ROM
XDA members setups
JJsax setup
CDMA Evo3D
hboot 1.50 s-on
TWRP 2.0 touch recovery
Phone ROM SteeleROM 2.73
ROM1 CM9 (The latest version couple days old)
ROM2 Evervolve ICS
mnomaanw's set up
PhoneROM: ViperROM Redline v2.5 RC2
ROM1:CyanogenMOD9
ROM2:MIUI v2.1.6
I've found it to work better to flash and set up my ROM on the phone ROM and then back it up and restore it to a slot.
If your having problems restoring backups and your using TWRP recovery try using CWM. I was having issues with TWRP and since I went back to CWM (touch and 5.0.2.0 both work great but there is no usb mount on the touch version) and I haven't had a single issue restoring a backup to a ROM slot.
My setup will be changing all the time.
CDMA EVO 3D
Eng Hboot s-off
Radio 1.06.00.1216
Phone ROM Infected Eternity Sense 3.0
ROM1 Mikrunny
ROM2 EVOZone
ROM3 SteelROM
ROM4 MeanROM Aria51
Thank you for putting this here. I know I'm to blame for going off topic in some threads about Boot Manager.
I too am having issues getting a ROM to load into slot 1.
Here's my setup...
SteeleROM 2.73
Anthrax #2 kernel
Over 5GB of storage space available.
HBOOT 1.50
TWRP 2.0 recovery (the newest touch one)
I load steele just fine as the phone ROM then try to load CM9, or whatever other ROM into slot 1 it goes through everything then it get's killed at mounting img's. I have it setup for screen on, to load large files, and I even have SU logging turned off. This happens everytime I try to load a ROM into slot 1 it just kills it and never finishes 100%
JJsax said:
Thank you for putting this here. I know I'm to blame for going off topic in some threads about Boot Manager.
I too am having issues getting a ROM to load into slot 1.
Here's my setup...
SteeleROM 2.73
Anthrax #2 kernel
Over 5GB of storage space available.
HBOOT 1.50
TWRP 2.0 recovery (the newest touch one)
I load steele just fine as the phone ROM then try to load CM9, or whatever other ROM into slot 1 it goes through everything then it get's killed at mounting img's. I have it setup for screen on, to load large files, and I even have SU logging turned off. This happens everytime I try to load a ROM into slot 1 it just kills it and never finishes 100%
Click to expand...
Click to collapse
Mine say they install fine and they finish but when I hit boot to the slot it just gets stuck on the splash screen.
I had TrevE Zone on my phone ROM but just switched to eternity. I got MeanROM to install in slot 2 and it booted up fine and is running great but thats the only one I out of the 3 I tried. I set the boot.img to large or what ever the setting is cause thats what they said to do in the video on the site for the app. My real issue though is that restoring my backup to a slot it installs to my system memory. I would like to be able to install backups cause I've read they run better. Hopefully some that knows more about this will come in here and school us a little, I'll even add it to the op and make this a guide if we get enough info.
Here's my quick and dirty instructable I posted in the CM9 thread.
How to install this via Boot Manager...
1.) PURCHASE Boot Manager. It does a License check upon boot, so your cracked version will just give you a headache. Seriously, I tried it. Doesn't work.
1.a) IF you didn't purchase it... delete ALL Boot Manager files, including the folder on your SD Card. Then buy it and let it setup again.
2.) Open SuperUser. Hit Menu -> Settings -> Disable Logging
3. Open BM. If you're at work and on Wi-Fi, you may not pass the License check due to firewall issues. If you get a black screen, or license failures, uninstall BM and delete the folder. Switch to 3/4G and try again.
4.) If all is good, you're asked to Setup the Phone. Do so now.
5.) Once installed, hit Menu -> Settings -> Force Large Boot.img
6.) Swipe right to Slot 1. Hit Install .zip and browse to your downloaded CM9 .zip file. Wipe System, Data, and Cache. Select EXT4 as the file structure
7.) This is the important part. This build will take a LONG time. Do NOT use your phone while it is running.
8.) Once the install has been successful, go back to Slot 1 and select Install .zip (again). Choose the Google Apps .zip file. Do NOT wipe system, data or cache.
9.) You should now be ready to boot to your new ROM! Celebrate!
Warning: Several users report to NOT use any Backup app such as Titanium to restore your apps and data, since the apps on this ROM are very very different. Your mileage may vary.
FYI I'm doing this by memory, so the minor steps might not be accurate (i.e. disable Superuser logging).
If you get any error messages, start over. I assure you, this process worked for me step by step.
Go to their official forum
Applications-->boot manager
You will find my thread named [REF]working and not working rom list
There are many phones
And if you test a rom that is not listed please report if it is working or not
Thanks
Sent from my HTC Desire S using XDA Premium App
I saw your guide in the cm9 thread and tried it with no luck I did exactly what you said and everything seemed to go fine but when I hit boot to ROM on slot one where I installed the ROM I'm stuck on the splash screen. Any ideas why? Thanks for the help also.
kylon said:
Go to their official forum
Applications-->boot manager
You will find my thread named [REF]working and not working rom list
There are many phones
And if you test a rom that is not listed please report if it is working or not
Thanks
Sent from my HTC Desire S using XDA Premium App
Click to expand...
Click to collapse
I was on there I even posted my issue and my log but haven't gotten any help. I did see your list of ROMs but didn't know if its up to date.
I'll have another look at it cause I really want to get this to work and its driving me crazy cause I can usually figure problems out on my own or by searching but I just can't get this.
Thanks for the replies.
linsalata28 said:
I saw your guide in the cm9 thread and tried it with no luck I did exactly what you said and everything seemed to go fine but when I hit boot to ROM on slot one where I installed the ROM I'm stuck on the splash screen. Any ideas why? Thanks for the help also.
Click to expand...
Click to collapse
Which ROM are you using?
I would start over. Use a file manager to delete your ROM from the SD Card and take another image. Make sure you have plenty of storage on your SD card. You could also try clearing the Cache and Dalvik.
You can always get back to your phone ROM manually by booting to Recovery and flashing sdcard\bootmanager\phonerom\update.zip
Edit: Don't forget to check "Use Large boot.img" within Boot Manager
seraph863 said:
Which ROM are you using?
I would start over. Use a file manager to delete your ROM from the SD Card and take another image. Make sure you have plenty of storage on your SD card. You could also try clearing the Cache and Dalvik.
You can always get back to your phone ROM manually by booting to Recovery and flashing sdcard\bootmanager\phonerom\update.zip
Edit: Don't forget to check "Use Large boot.img" within Boot Manager
Click to expand...
Click to collapse
Should I just delete the whole bootmanager folder and clear the data for the app also?
another thing is why when I restore a backup to a slot its installing to my internal memory?
Yeah I just had another look at your list and there aren't many ROMs for this phone on there and they look old.
Thanks again for the help.
It up to date
Anyway gflame is busy
What do you do to install the rom
And wich rom?
Sent from my HTC Desire S using XDA Premium App
I wiped everything out and starting over. I'm going to just try and install viperom in one slot and see if that boots, then I'm going to try and restore a backup to another slot from within a ROM slot to see if that will fix my internal memory issue cause it wont have anywhere to install to . I'll post back with what happens.
kylon said:
It up to date
Anyway gflame is busy
What do you do to install the rom
And wich rom?
Sent from my HTC Desire S using XDA Premium App
Click to expand...
Click to collapse
I disabled logging in su checked off larg boot.img then whet to slot one hit install zip choose cm9 ext4 then checked all the wipe opinions, when that finished I flashed the gapps the same way but without wiping . Everything finished with that I didn't get any errors but when I went to boot to that slot it just hung at the splash screen.
I did that 2 times with cm9 , 1 time with the Eternity ROM sense 3.0 r130 , 1 time with Team Nocturnal's Blackened ROM and they all got stuck at the splash screen.
I did get MeanROM to work using those same steps last night.
Now with the restore of my backup I did basically the same thing but it doesn't give any wipe options when you install it but it would get an error saying boot.img something like that and then I would get a low memory popup saying I only had about 30mb left internal memory when I had over 800mb when I started.
Edit: I have about 6gb free on a 16gb class 10 sd card. I believe its a Samsung card I think.
Edit2: I finished flashing viperom and now that to is stuck on the splash screen. Is there a way to wipe caches for that slot and fix permissions like you would for a regular ROM in recovery if something like this happened.
I'm really starting to think I wasted $3 this is very frustrating sorry.
Thanks for your replies and trying to help.
I went into recovery to go to flash the update zip to restore my phone ROM but when I open the bootmanager folder I don't see anything in it. I'm using twrp 2.0 recovery. Could this have something to do with my problems?
linsalata28 said:
I went into recovery to go to flash the update zip to restore my phone ROM but when I open the bootmanager folder I don't see anything in it. I'm using twrp 2.0 recovery. Could this have something to do with my problems?
Click to expand...
Click to collapse
The steps in your previous post were all correct, except you said you turned OFF "Use large boot.img" ? Make sure that option is ENABLED (has an X on it)
I'm confused as to why the app is trying to install to your internal memory... Mine installs to my SD Card. Make sure the USB cable is not plugged into the phone, and try increasing your screen timeout so it doesn't sleep during the install.
The fact that you're getting the splash screen means you're getting somewhere. Maybe you're being too impatient on the install? Wait a few minutes even after it says Install Complete before continuing.
seraph863 said:
The steps in your previous post were all correct, except you said you turned OFF "Use large boot.img" ? Make sure that option is ENABLED (has an X on it)
I'm confused as to why the app is trying to install to your internal memory... Mine installs to my SD Card. Make sure the USB cable is not plugged into the phone, and try increasing your screen timeout so it doesn't sleep during the install.
The fact that you're getting the splash screen means you're getting somewhere. Maybe you're being too impatient on the install? Wait a few minutes even after it says Install Complete before continuing.
Click to expand...
Click to collapse
I said I checked the larger boot.img off meaning it was enabled sorry for that misunderstanding. I flashed 2 of the slots last night and didn't even test them till today so I don't think that its cause I'm not waiting long enough. Why would none of the folders inside of the bootmanager folder show up in twrp recovery? Could I copy and paste the phone update.zip to the root of my sd card so that I can recover without having to nand restore cause I've already wiped and restored about 10 times trying to get this to work.
Sent from my Eternity 3D using tapatalk
linsalata28 said:
I disabled logging in su checked off larg boot.img then whet to slot one hit install zip choose cm9 ext4 then checked all the wipe opinions, when that finished I flashed the gapps the same way but without wiping . Everything finished with that I didn't get any errors but when I went to boot to that slot it just hung at the splash screen.
I did that 2 times with cm9 , 1 time with the Eternity ROM sense 3.0 r130 , 1 time with Team Nocturnal's Blackened ROM and they all got stuck at the splash screen.
I did get MeanROM to work using those same steps last night.
Now with the restore of my backup I did basically the same thing but it doesn't give any wipe options when you install it but it would get an error saying boot.img something like that and then I would get a low memory popup saying I only had about 30mb left internal memory when I had over 800mb when I started.
Edit: I have about 6gb free on a 16gb class 10 sd card. I believe its a Samsung card I think.
Edit2: I finished flashing viperom and now that to is stuck on the splash screen. Is there a way to wipe caches for that slot and fix permissions like you would for a regular ROM in recovery if something like this happened.
I'm really starting to think I wasted $3 this is very frustrating sorry.
Thanks for your replies and trying to help.
Click to expand...
Click to collapse
My phone:
Phone ROM: SteelROM 2.72
Slot 1: AOSP ICS - wifi doesn't work
Slot 2: CM9 - (google talk and books FC)
Slot 3: MIUI
Slot 4: CM7 (kmeyers)
Boot Manager has a problem trying to restore from a NAND backup, it did the same thing to me where it was installing to the phone's internal memory. I was trying to figure out the problem, but I moved on without success.
I've had the best time installing tricking ROM's by this method. I installed CM7 to a slot, booted into CM7 and installed the ICS and CM9 from there. It's been pretty successful.
If you are getting it to freeze with mounting images, I came across this issue because my SD card did not have enough room. You can try to free up some more space to see if this is the same issue.
I had most problems installing due to not enough space on my SD card, I now have a 32gb card, and have had no issues
Also, I've never had to set it to large boot.img to get things to work, and make sure you disable logging in SU, and use EXT4
---------- Post added at 02:08 PM ---------- Previous post was at 02:04 PM ----------
linsalata28 said:
I said I checked the larger boot.img off meaning it was enabled sorry for that misunderstanding. I flashed 2 of the slots last night and didn't even test them till today so I don't think that its cause I'm not waiting long enough. Why would none of the folders inside of the bootmanager folder show up in twrp recovery? Could I copy and paste the phone update.zip to the root of my sd card so that I can recover without having to nand restore cause I've already wiped and restored about 10 times trying to get this to work.
Sent from my Eternity 3D using tapatalk
Click to expand...
Click to collapse
To quickly get back to your phone ROM (make sure you setup your phoneRom in boot manager first to create the update.zip file, you need to recreate this anytime you change the ROM or Kernel for your phoneROM)
Boot into Recovery
Install the update.zip inside the \boot manager\phonerom\update.zip (not sure if location is accurate, but you get the idea)
Reboot system
Phone should boot to phone ROM, or you can install any other update.zip from your slots, to boot to them etc
spookytay said:
My phone:
Phone ROM: SteelROM 2.72
Slot 1: AOSP ICS - wifi doesn't work
Slot 2: CM9 - (google talk and books FC)
Slot 3: MIUI
Slot 4: CM7 (kmeyers)
Boot Manager has a problem trying to restore from a NAND backup, it did the same thing to me where it was installing to the phone's internal memory. I was trying to figure out the problem, but I moved on without success.
I've had the best time installing tricking ROM's by this method. I installed CM7 to a slot, booted into CM7 and installed the ICS and CM9 from there. It's been pretty successful.
If you are getting it to freeze with mounting images, I came across this issue because my SD card did not have enough room. You can try to free up some more space to see if this is the same issue.
I had most problems installing due to not enough space on my SD card, I now have a 32gb card, and have had no issues
Also, I've never had to set it to large boot.img to get things to work, and make sure you disable logging in SU, and use EXT4
---------- Post added at 02:08 PM ---------- Previous post was at 02:04 PM ----------
To quickly get back to your phone ROM (make sure you setup your phoneRom in boot manager first to create the update.zip file, you need to recreate this anytime you change the ROM or Kernel for your phoneROM)
Boot into Recovery
Install the update.zip inside the \boot manager\phonerom\update.zip (not sure if location is accurate, but you get the idea)
Reboot system
Phone should boot to phone ROM, or you can install any other update.zip from your slots, to boot to them etc
Click to expand...
Click to collapse
What cm7 ROM would you recommend ? For some reason I couldn't see files inside of the BootManager folder but I checked and they are there. I have about 5gb free on a 16gb card ,I was looking into getting a 32gb if I get this app working.
Sent from my Eternity 3D using tapatalk
try
http://forum.xda-developers.com/showthread.php?t=1393613
I upgraded my card, I had about 3-4 gb free and was having problems, but once I upgraded I haven't had many since
I've purchased boot manager and when i run it, it says "application not licenced" Any fix?
spookytay said:
try
http://forum.xda-developers.com/showthread.php?t=1393613
I upgraded my card, I had about 3-4 gb free and was having problems, but once I upgraded I haven't had many since
Click to expand...
Click to collapse
cm7 worked thanks.
Related
Greetings.
I just bought my Thunderbolt the other day and so far I'm loving it more each day. I successfully rooted it and got ROM Manager on it.
I'm confused as to what exactly a ROM is and how to get it working on my phone. I've been reading about a few ROMs that de-bloat the phone and those are the ones that I'm looking to get onto my phone, but I'm rather confused as to how to install them. I've downloaded the Des BAMF one and put it on my phone's SD card and renamed it to "update.zip" and chose the option "Install ROM from SD Card." It then reboots into a different looking theme/skin that appears to be the default. I'm not sure if I did something wrong or not.
Could someone fill me in on how exactly to install a custom ROM on the Thunderbolt?
Any help is appreciated.
Hey.
I am in the exact same boat as you. Just got my tbolt and unlocked it.. And for the longest time.. 5 hours i had no idea how to install the roms.
So from what I did.
I backed up my user app on Titanium back up.
I downloaded the zip file.. and placed it in my SD CARD. Don't put it in any folder. or you could you just have to find it, without changing the name.
So then with Rom Manager, you should backup current ROM
Then you should reboot into Recovery.
First we will wipe the data/factory reset.
wipe the cache partition.
Apply the new rom. To do this select the install zip from sdcard.
The next option would be to select chose zip from sd card.
Then you will select your rom from the sd card.
Once you have selected the rom you will get to the conformation page.
I have a link that can show you step by step.. but i am not over my 10 post to post link outside the site
there is no need to rename to update.zip. if you are properly rooted with s-off all you need to do is choose choose "install rom from sd card" in rom manager. Find the rim you want to install (name doesn't matter) and click it. It will then prompt you with two checkboxes.
1. Will be to make a back up
2. Will be to wipe data and cache.
MAKE A BACKUP. As for wiping data and cache that erases everything from your phone (not things on the sd card) it is recommended to do that because sometimes the phone gets weird and force closes if you don't, but sometimes it works fine.
After clicking ok, it will boot into recovery, go through back up and installing and reboot. First reboot may take awhile but after thar you have your new rom.
Let me know if that answered your question. If it didn't, clarify for me so I can better assist you.
Sent from my ADR6400L using XDA App
greg i have a question. when you wipe data and cache.
your sdcard is safe right?. or does the sdcard get wiped as well
MisterDonut said:
greg i have a question. when you wipe data and cache.
your sdcard is safe right?. or does the sdcard get wiped as well
Click to expand...
Click to collapse
sdcard will not get wiped.
another thing, if your just flashing a new kernel, or updating a rom, like from bamf 1.2 to 1.3, usually a full wipe is not necessary.
But if your switching roms like from BAMF to CM7 always wipe.
just make sure you read the threads and backup before you change anything.
The easiest and simple method of putting a rom on you phone is thru clockwork. You can access the xda site thru an app on the market, just search for xda. Download the app, open the app and sign in. Find the t-bolt forum and download the desired rom using your phone. Once the rom is downloaded, boot into recovery, select "wipe data/factory reset" , select "wipe cache partition", then select "advanced", select "wipe dalvik cache". I usually do this process twice just to make sure. The select "install zip from sd card", find the folder where you downloaded the rom select that then select the file/rom. Install it.
Thanks alot appreciate the feed back and the community
Sent from my ADR6400L using XDA App
Thank you for all the replies everybody. Clarified a lot of things for me.
I forgot to ask something in my original post; what exactly is a kernel and how would I come about installing it on my TB?
I've been reading a lot about them and I am still clueless as to what a kernel does.
Tethers said:
Thank you for all the replies everybody. Clarified a lot of things for me.
I forgot to ask something in my original post; what exactly is a kernel and how would I come about installing it on my TB?
I've been reading a lot about them and I am still clueless as to what a kernel does.
Click to expand...
Click to collapse
The kernel controls the power and sped of the phone. You can install it the same way I explained prior. The devs tweak the kernel to get better performance and battery life. Adrynalynes 2.0 is good. Dont worry about quadrant scores/ speeds as they are bs. I am also not a fan of overclocking, just my preference.
Tethers said:
Thank you for all the replies everybody. Clarified a lot of things for me.
I forgot to ask something in my original post; what exactly is a kernel and how would I come about installing it on my TB?
I've been reading a lot about them and I am still clueless as to what a kernel does.
Click to expand...
Click to collapse
im not sure exactly, but without getting too technical, it controls your processor speed.
it can make your phone faster, smoother, and more efficient.
if you flash a good rom, i see your on das bamf, it already has a decent kernel.
Tethers said:
Thank you for all the replies everybody. Clarified a lot of things for me.
I forgot to ask something in my original post; what exactly is a kernel and how would I come about installing it on my TB?
I've been reading a lot about them and I am still clueless as to what a kernel does.
Click to expand...
Click to collapse
Check out the section on kernels on wikipedia, it does a decent job explaining it. The reason you might want to run a custom kernel is to add support for something that is disabled in the stock kernel config, like extra filesystem support or tunneling or to undervolt the processor to save on battery. More slots can be added so you can change clock speeds, etc.
title shows the way it is...i've had it UP TO HERE with Boot manager.
I love the HTC Sense 4.1 camera on Newts HTC One XxX ROM but I dont like the bloaty sense framework that It has...right now i'm running AOKP 1.6 Linaro because it's fast and has no sense. unfortunately, I can't have both..and I found out that an app can "dual boot" your phone into 2 separate ROMS so that you can enjoy both. However i've been having NOTHING but PROBLEMS with boot manager. What started off as a simple idea has become a curse spewing nightmare
I'm s-Off and running Snuzzo's kernel from AOKP 1.6
1. I've searched the forums and done everything that other people have said
2. I'm using the Lite Version of Boot Manager since I only need one slot.
3. I have errors with "Error building new boot.img"
4. Disabled SU Logging and even wiped and tried SuperSU instead! (with logging disabled of course)
5. tried to install slot 1 via Zip file AND NANDROID BACKUP. Still having issues!
6. When installs are successful with no errors, when rebooting into the SDCARD Rom it just hangs at the HTC splash screen. mocking me.
7. Tried installing from external and internal storage..same problems...and i'm having a flip flop issue as well in regards to that..**
I'm at my wits end and am about to scrap this whole dual boot idea
**What I will say is that file explorer apps show my SD card as Internal Storage. and the internal storage shows my SDcard files...dafuq?! maybe SD card format?? that's for another forum question though...
If anyone can help me get this to work..I'll thank you and be sure to buy the app. But as for now...I'm glad I didn't spend my damn money!
stanleyopar2000 said:
title shows the way it is...i've had it UP TO HERE with Boot manager.
I love the HTC Sense 4.1 camera on Newts HTC One XxX ROM but I dont like the bloaty sense framework that It has...right now i'm running AOKP 1.6 Linaro because it's fast and has no sense. unfortunately, I can't have both..and I found out that an app can "dual boot" your phone into 2 separate ROMS so that you can enjoy both. However i've been having NOTHING but PROBLEMS with boot manager. What started off as a simple idea has become a curse spewing nightmare
1. I've searched the forums and done everything that other people have said
2. I'm using the Lite Version of Boot Manager since I only need one slot.
3. I have errors with "Error building new boot.img"
4. Disabled SU Logging and even wiped and tried SuperSU instead! (with logging disabled of course)
5. tried to install slot 1 via Zip file AND NANDROID BACKUP. Still having issues!
6. When installs are successful with no errors, when rebooting into the SDCARD Rom it just hangs at the HTC splash screen. mocking me.
7. Tried installing from external and internal storage..same problems...and i'm having a flip flop issue as well in regards to that..**
I'm at my wits end and am about to scrap this whole dual boot idea
**What I will say is that file explorer apps show my SD card as Internal Storage. and the internal storage shows my SDcard files...dafuq?! maybe SD card format?? that's for another forum question though...
If anyone can help me get this to work..I'll thank you and be sure to buy the app. But as for now...I'm glad I didn't spend my damn money!
Click to expand...
Click to collapse
From what ive heard the app has been abandoned by the developers. I wanted to dual boot too but I got the same error with the error building new boot.img as well so i quit trying. btw are you s-off? the app requires s-off so it can flash the other boot.img of the Sd roms.
jon7701 said:
From what ive heard the app has been abandoned by the developers. I wanted to dual boot too but I got the same error with the error building new boot.img as well so i quit trying. btw are you s-off? the app requires s-off so it can flash the other boot.img of the Sd roms.
Click to expand...
Click to collapse
yes..I'm S-Off and recently in April of this year the developer made an update to support the Rezound. So even if the app has been abandoned for future devices....it supports the Rezound...and I've looked in the forums and people HAVE got it working on the Rezound. Pisses me off that It's not working for me
stanleyopar2000 said:
yes..I'm S-Off and recently in April of this year the developer made an update to support the Rezound. So even if the app has been abandoned for future devices....it supports the Rezound...and I've looked in the forums and people HAVE got it working on the Rezound. Pisses me off that It's not working for me
Click to expand...
Click to collapse
Same with me it was part of the reason i went to s-off. Hopefully sometime in the future the dev of the app can update it to fix the bugs.
jon7701 said:
Same with me it was part of the reason i went to s-off. Hopefully sometime in the future the dev of the app can update it to fix the bugs.
Click to expand...
Click to collapse
what about the other people that have got it working???...how come they didn't have to quit?
Maybe the AOKP ROM i'm using is bad (since the SD CARD and INTERNAL MEMORY labels are switched and it possibly is confusing the boot partition)...perhaps I should try installing the AOKP Rom on sense
Took me a few tries but I did this :
Use ext4
Use internal sd
Force screen on
Install from nandroid
For me it's actually easier to just restore nandroids if u wanna jump from one rom to another..
Sent from my ADR6425LVW using xda app-developers app
Squirrel is right ot much easier to just make a nandroid and bounce back and forth..
Sent from my ADR6425LVW using xda app-developers app
Squirrel1620 said:
Took me a few tries but I did this :
Use ext4
Use internal sd
Force screen on
Install from nandroid
For me it's actually easier to just restore nandroids if u wanna jump from one rom to another..
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
In AOKP the labels are switched..so use the bullet option "external SD" because the internal SD is labeled as the external.
INTERESTING: when I set boot manager to install to internal (i have to select "external) it STILL installs it to the sdcard but in a folder that says sdcard/sd-ext.
NOT to the actual internal memory. I will move that folder to the real internal memory when the install finishes and see if it will work. If not. I'm almost POSITIVE that the switched Internal Memory and SD card labels in AOKP are to blame...and it that's not the problem. boot manager can f$#k itself.
Edit: I fuking quit. I did everything and the install worked from a sense ROM.but it past the splash screen and hung at a black screen.
I'm such a whore for screencast and that 4.1 Sense camera..i'll stay with One xXx for a while (even though sense ROMS are against my grain)
Boot manager hasn't worked properly with aosp since the mount points were fixed in aosp. It's the way it differs from sense. Using emmc as internal unlike sense which It's mounted as sd card. You can use it to switch between sense roms all you want to but not aosp
Sent from my ADR6425LVW using Xparent SkyBlue Tapatalk 2
im not sure if this is one of the problems but i noticed when i tried to use it earlier that it asked if i was on the newest hboot (2.21) or an older one but we are actually on 2.27 so that could be messing with things
I used to use Boot Manager with 2.25 with no issues, and there isn't much difference between 2.25 and 2.27.
I'm in a very similar boat....I have a recent ota RUU and s-off and bootmanager actually installs for me (yay) but I never have data. EVER. Data never works for any slot roms, only for my phone rom. I hear this is because of AOKP vs sense. My phone rom is Viper rom, and I tried to put AOKP linario for my slot 1. It installs and boots fine but I dont have data. I also tried MIUI but again no data. However if I put them on my phone rom, I have data. I figured I put it on the phone rom, make a nand, put viper back as my phone rom, then nand restore MIUI or linario to a different slot ..... no go - still no data. I think I read here that at this point I can only user boot manager to switch between sense roms and not between aokp/sense.
If it's also true that they dropped support for it I will be extremely sad. I paid for an app that doesn't even work/have suppor then .......
I actually just pm'd both devs the other day. I'd have emailed but their email rejects anything saying "over quota" or something. And their forums give me a 500 http server error.
If you make and headway let me know because I'm lost too
[See post http://forum.xda-developers.com/showpost.php?p=43326042&postcount=123 for the new version of this post with updated links/pointers to Succulent's recent CM10.1 builds as well as CWM/TWRP recovery tool compilation].
[Caveat emptor: adopt/follow this guide at your own risk].
I've been running CM10 build by XDA Developer Succulent version 12/08 on SD card since its release ten days ago, and its reliable/stable performance has crossed the threshold for me to finally take the plunge and install it internally on emmc.
FWIW, here the process I used to install CM10 internally on my 16GB Nook Tablet (i.e., on its emmc).
Using a disk partition tool (such as MiniTool Partition Wizard Home Edition) create on SD card a Primary FAT32 partition, and set the partition ID type for the partition to 0x0C FAT32 LBA and set its Active flag. Once this is done, the partition should appear as a (read/write accessible) drive under Windows. If you are going to use this card for backing up your NT, keep in mind that each backup will require at least 600MB (for a barebone stock or CM config) and size the partition accordingly.
Obtain and copy to the SD card the following files:
MLO, u-boot.bin, and flashing_boot.img in SD_boot.zip obtained from http://iamafanof.wordpress.com/2012/11/11/how-to-guide-bootable-cm7cm9cm10-sdcard-for-nook-tablet/
either one of the two recovery program image files: cwm_6012_sd.img (ClockworkMod Recovery (aka CWM)) in CM9-10_CWM_v6.0.1.2_8-16gb_tools_sdcard.zip, or twrp_2220_sd.img (TeamWin Recovery Project (aka TWRP)) in CM9-10_TWRP_v2.2.2.0_8-16gb_tools_sdcard.zip from http://forum.xda-developers.com/showthread.php?t=1640958, rename it to recovery.img. If you want to try out (or use) both, name your alternate choice altboot.img.
the file cm-10-yyyymmdd-UNOFFICIAL-acclaim.zip from http://iamafanof.wordpress.com/2012/11/03/cm10-0-jelly-bean-for-nook-tablet-uploading/
the file gapps-jb-20121011-signed.zip from http://goo.im/gapps/gapps-jb-20121011-signed.zip
Put the SD card into the NT, and boot from its power off by inserting a powered USB cable. Press and hold the N button as soon as CyanoBoot comes up to get the boot menu to display.
Select either SDC Recovery (or Alternate Boot depending on which recovery tool you want to use).
Select Backup to backup your current NT config (/boot, /recovery, /system, and /data). Before proceeding to next step, see note (ii) near the end of this post.
Select Wipe data & factory reset.
Select install zip from SD card and install cm-10 zip file.
Select install zip from SD card and install gapps zip file.
Select power of and remove SD card from NT and power NT on again using the power button (alternatively you can just remove SD card and select reboot).
Once the NT boots up, set up the wifi connectivity and your google account info. If you had previously used Google backup service your apps will be auto-downloaded (but their settings will not be auto-restored)
A few additional points worth noting:
Installing CM10 ROM and gapps will override your NT's BN-provided boot, recovery, ROM, and Apps, so make sure that you backup all this stuff using backup process in step #5 above, safekeep the backup data on your PC/Laptop and better yet archive it on CD/DVD. Your media files in the NT media partition BN allocates for user should be intact.
To play it safe you should do the above in 2 phases: steps 1 through 5, then exit recovery and remove and mount SD card on PC to verify that backup data got newly created; then insert SD card and continue steps 6 through 9.
CWM and TWRP use different backup archive formats, so keep this in mind if you decide to switch. Furthermore, CWM has changed its archive format going from release 5.x to 6.x, so I think it would be prudent to save a copy of the recovery program together with the backup data it generated. (FWIW I prefer the tar/zip compatible backup data structure TWRP uses (which CWM 5.x had also used) over the BLOb structure which CWM 6.x use -- but YMMV).
To restore from backup data, boot into SD card and select from boot menu the same recovery program that was used to create the backup data, then select the particular backup dataset (indexed by date/time) you want to reinstall on your NT.
I would advise against blindly using other functions of the CWM and TWRP without looking up info and researching to understand what they really do.
See my post at http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more "Info and Tips for Mitigating Risks in Rooting and Flashing Custom-ROM".
My thanks to all the developers who collective work created this wonderful ROM as well as the tools and info I made use of to install it. IMHO this ROM helps make the Nook Tablet one of the best-value tablets for the money (at least at the moment).
great post...fwiw here's my experience to get two NT16's up and running (I started with an old CM7 on both of them).
Backup nook with titanium backup on existing 32GB card.
Take screenshots for replacements
Reset nook to stock (1.4.2) and update to latest (1.4.3) with a fresh SD Card with repart.img copied to root (my red 2GB card):
http://raywaldo.com/2012/06/make-unbrick-repartition-image/
http://www.youtube.com/watch?v=Nu6e4m62tFc
c. 1.4.3 can be downloaded from B&N site directly. (http://www.barnesandnoble.com/u/Software-Updates-NOOK-Tablet/379003187/)
Create a CWM SD Card (ideally 4GB SanDisk) as per these instructions - http://raywaldo.com/2012/05/root-nook-tablet-with-cwm-sdcard/
Copy CM7 BETA and compatible GAPPS onto this card or another blank one. You can get the files from here: http://forum.xda-developers.com/showthread.php?t=1481826 and http://wiki.cyanogenmod.com/wiki/Latest_Version/Google_Apps
Boot into this CWM Card, wipe data/wipe cache and dalvik cache. Install zip from sdcard (either current or pop in the new one). Choose cm-7 beta first, then gapps. Remove sd card. Reboot. Wait a while for it to set itself up.
Go into settings/applications and clear the cache for google market/play.
You now have CM7 installed and can setup the basics (google, wifi etc..)
Insert your 32GB (or 16 or 8 or whatever) Sandisk SD Card (it should ideally have the Titanium Backup folder from step 1, any media you want in Music and Movies folder and the CM10 and gapps zip in the downloads folder -- and that's it!)
Once mounted, download Goo Manager from the google play store and run it, accepting superuser requests.
Choose settings menu and "Install OpenRecoveryScript" and it should install openrecovery twrp recovery manager. Once it has installed and informed you of success, reboot into recovery (this is important), upon reboot hold the "n" and choose internal emmc recovery from the menu.
You will now find yourself in TWRP. From the install menu, add the CM10 PURE AOSP 4.1.2 JBV06.1-Hashcode and then the gapps-jb-20121011-signed.zip and swipe to confirm flash. This is it. Fingers Crossed!
NOTE: On one NT 16 (I have two), step 12 DID NOT WORK. It wouldn't install the CM10...zip -- and simply rebooted itself or hung...so I powered off, and rebooted to the CWM Card in #6..and used CWM to wipe caches etc… and then installed the two zips...and voila.
hope it helps.
digixmax said:
I've been running CM10 build by XDA Developer Succulent version 12/08 on SD card since its release ten days ago, and its reliable/stable performance has crossed the threshold for me to finally take the plunge and install it internally on emmc.
Click to expand...
Click to collapse
How do you feel about it now that you've installed it internally? I took the plunge as well today, but I'm not sure it's runs any better internally than it does from the sd card. Having said that, it runs so incredibly well from the card, so it's really hard to beat, but still... I'm actually having more issues with the internal install than the sd version.
I had had enough of the stock reader (that I'm actually pretty fond of) not remembering my place in sideloaded books, so I didn't feel I had anything to loose and am glad I made the install though. Installed once makes it easier to reinstall when an even better build comes along.
I made the switch since the stock ROM was so barebone and clumsy I virtually never use it since I had the NT, and the rooted stock ROM is just marginally better -- I found out there are so many apps I 've been using on CM10 that are simply not available for BN's (Android) Gingerbread. I also like the fact that I can now reboot (if ever needed) untethered.
I think performance-wise it runs about the same as it was running on SD, if it's better then it's not yet noticeable.
What kind of issues are you having with your new setup?
Some apps misbehaved. Didn't install properly or gave error messages. I decided to re flash and this this second install hasn't had any issues at all. Same files from the same card.
It is nice to have it internally and be able to switch sd cards should I want to.
Sent from my Barnes & Noble Nook Tablet using Tapatalk 2 and SwiftKey
I ran into a problem with v12/08: when I connect the NT to the PC I do not get the “USB connected” notification with option to “turn on the USB storage”, and thus cannot access neither the emmc media partition nor the sdcard. The problem exists with both CM10 running on emmc and running on sdcard. Furthermore when running on sdcard, hitting “storage” in “settings” results in a force-close of “settings”.
I am curious if anyone else has the same problem, or I am just missing some setup setting somewhere.
In the meantime, I am back to running another ROM off SD.
Those storage setting issue I had with the 1118 build but not with later ones. Connection to PC work fine but I don't think I need to do the turn on USB thing. No PC nearby at the moment
Edit: I am now near a PC, and I do get the "touch to turn on USB" or words to that effect. So it works as it should..
Sent from my Nook Tablet using Tapatalk 2 and SwiftKey
Thanks, I've tried reinstalling a couple of times (as well as installing a different ROM) without success.
I found the answer to my problem: I was used to getting the full-screen alert “USB mass storage” (upon insertion of tethered USB cable), and didn’t notice the tiny alert “USB connected” on the status bar (which when pulled down would in turn launch the “USB mass storage” alert).
Question: I'm not new to rooting and flashing, but am new to NT. I rooted my wifes NT, installed a launcher to switch back and forth, and loaded a few apps. I did not change the stock recovery and used a boot sdcard to run an older version of CWM. I forgot to hack OTA off so while messing around the darn thing upgraded to 1.4.3. The stock rom is such an old version of GB it is really worthless. So here is my question. Can I use this method to go directly to CM10? Im not too concerned about the issues mentioned in this thread, but more concerned about the method and the type of issues I might encounter. I see some threads say to flash CM 7 first, why I'm not sure. It almost looks to simple. Just looking for confidence. If it were mine I wouldnt care. Thanks for any help.
Sent from my SAMSUNG-SGH-I317 using xda premium
Dean1650 said:
Question: I'm not new to rooting and flashing, but am new to NT. I rooted my wifes NT, installed a launcher to switch back and forth, and loaded a few apps. I did not change the stock recovery and used a boot sdcard to run an older version of CWM. I forgot to hack OTA off so while messing around the darn thing upgraded to 1.4.3. The stock rom is such an old version of GB it is really worthless. So here is my question. Can I use this method to go directly to CM10? Im not too concerned about the issues mentioned in this thread, but more concerned about the method and the type of issues I might encounter. I see some threads say to flash CM 7 first, why I'm not sure. It almost looks to simple. Just looking for confidence. If it were mine I wouldnt care. Thanks for any help.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
Cm7 is a gingerbread rom, it can be flashed by cwm 5 and 6 both. But cm10 is jellybean and must be flashed with cwm 6 only (or twrp) . And once you have cm7, you get cyanoboot (2nd bootloader) which is necessary to load cwm6, whether its internally flashed recovery or SD card recovery.
If you still have your bootable SD card, boot into recovery and check the version (cwm 5 most likely) , then do the longer, but simpler method - stock > cm7 > flash cwm6 internal and boot into it from cyanoboot > cm10.
I see the difference between the 2 methods..a few more questions. I dont see where or how recovery gets flashed in the first method. Looks like either/both are used but not flashed. In both methods, I dont see any sdcard additional partition requirements so can I assume everything can get copied to the boot partition? Haven't looked at the card I made yet, but if CWM is current enough for CM7 it should work fine. I appreciate this thread. It has cleared up a lot of questions.
Sent from my SAMSUNG-SGH-I317 using xda premium
Dean1650 said:
...
I forgot to hack OTA off so while messing around the darn thing upgraded to 1.4.3. The stock rom is such an old version of GB it is really worthless. So here is my question. Can I use this method to go directly to CM10? Im not too concerned about the issues mentioned in this thread, but more concerned about the method and the type of issues I might encounter. I see some threads say to flash CM 7 first, why I'm not sure. It almost looks to simple. Just looking for confidence. If it were mine I wouldnt care. Thanks for any help.
Click to expand...
Click to collapse
Yes, you can use this process to go directly from stock or rooted stock to CM10 -- I used it to go from rooted 1.4.3 directly to CM10. With SD-based flash, there is no need to go the circuitous multi-stage flashing process.
And if you use Succulent's CM10 builds from http://iamafanof.wordpress.com/2012/11/03/cm10-0-jelly-bean-for-nook-tablet-uploading/ his ROM zip files all include emmc recovery so you don't even have to separately flash recovery as you would have with other ROMs. I think his approach, in addition to being convenient, has the benefit of avoiding intermediate states where there is potential incompatibility between ROM and recovery versions (which I think is conducive to causing bootloop).
Of course if for some reason you later prefer a different version of recovery than the one he includes (CWM 6.0.2.5) you can always reflash your particular choice of recovery by itself.
FWIW I am running Succulent's cm-10-20121225-acclaim-HD.zip (GCC 4.6) at the moment and it works great.
Dean1650 said:
I see the difference between the 2 methods..a few more questions. I dont see where or how recovery gets flashed in the first method. Looks like either/both are used but not flashed. In both methods, I dont see any sdcard additional partition requirements so can I assume everything can get copied to the boot partition? Haven't looked at the card I made yet, but if CWM is current enough for CM7 it should work fine. I appreciate this thread. It has cleared up a lot of questions.
Click to expand...
Click to collapse
Everything that gets flashed via recovery (either CWM or TWRP) comes in zip archive form, and this applies to ROM, gapps, as well as recovery itself. (If you ever want to flash recovery, the simplest way is to get a recovery zip file, such as one of those with keyword emmc from http://forum.xda-developers.com/showthread.php?t=1640958, and flash it from SD using the process in the first post, just as you would flash a ROM build or gapps).
If you are curious about what gets installed and where, just open (but don't extract) the to-be-flashed zip file (e.g., using winrar/winzip/7-zip): everything except the META-INF folder is what get installed, and the updater-script file in META-INF\com\google\android\ (which you can open using a text editor like notepad) contains installation script detailing where (i.e., which partition on the NT) various components of the zip file get installed.
Typical ROM builds zip contain boot.img which gets installed on /boot partition, and a bunch of system files and apps to be installed on /system partition. Succulent's ROM builds also include recovery which gets installed on /recovery partition. Finally gapps apps get installed on /system as well.
Really, really appreciate this OP, the replies, and the knowledge. VERY helpful. Wont do this til the 1st and will let you know the results... Again, THANKs
Sent from my SAMSUNG-SGH-I317 using xda premium
Well your method worked flawlessly. I had a few minor operator errors but it went just as you explained. I did, however, have a fatal bug in the rom. Not sure who to report it to, but while messing around in settings I tried to change the color of the clock in the status bar. It totally blew away systemui. I tried everything I knew of to restart and recover but had to resort to wipe/factory reset. Could not figure out what data file got corrupted. That in turn made me have to flash the gapps again because none of the Google apps worked including play store. The net result is to add 1 more step to your method. BEFORE messsing with settings, and after the initial setup is complete, boot to recovery and do another backup..I forgot to mention I flashed 20121231, which is the latest release. Thank you so much for your knowledge and reseach. STOCK ROOTED TO CM10 RELEASED.
Sent from my SAMSUNG-SGH-I317 using xda premium
Stuck on backup in CWM 6.0.1.2
My 16gbNT is currently running Team_B CM7. I'm trying to install Kuzma30's CM10.1 from a SD card. Following the instructions from this OP. While trying to perform my backup the process gets about 3/4 of the way through and then sticks at the file named "generic11.lda". It doesn't continue after that and I have left it alone for a considerable amount of time. Any idea what's causing the stick? I've tried it about three or four times with occasionally sticking at different files but it is still about 3/4 of the way through. Backup will not finish.
Any help is greatly appreciated.
I'd suggest trying a version of CWM that is considered compatible with CM7, e.g., CM7-9_CWM_v5.5.x_8gb-16gb_tools_sdcard.zip from http://forum.xda-developers.com/showthread.php?t=1640958 (but then remember to flash CM10.1 with 6.0.1.2).
Also check and make sure that you have enough space on your SDcard (you can/should remove backup data associated with failed partial backup attempts).
Backup success, Install failure
digixmax said:
I'd suggest trying a version of CWM that is considered compatible with CM7, e.g., CM7-9_CWM_v5.5.x_8gb-16gb_tools_sdcard.zip from http://forum.xda-developers.com/showthread.php?t=1640958 (but then remember to flash CM10.1 with 6.0.1.2).
Also check and make sure that you have enough space on your SDcard (you can/should remove backup data associated with failed partial backup attempts).
Click to expand...
Click to collapse
Backup successful! Thanks button pressed. Now on the install I used CWM 6.0.1.2 and I'm not allowed to complete the install. It aborts installation and gives the following error:
"Installing update...
set_perm: some changes failed
E:Error in /sdcard/cm-10.1-20130102-UNOFFICIAL-acclaim.zip
(Status 7)
Installation aborted."
Any ideas?
Your guide is quite clear but somehow it is not working for me. I have a fresh NT 8GB with stock 1.2 on it.
I obtained the 6 files you mention:
- u-boot.bin
- MLO
- flashing_boot.img
- recovery.img (= cwm_6012_sd.img)
- gapps-jb-20121011-signed.zip
- cm-10-20121231-NOOKTABLET-acclaim-HD.zip (from: http://iamafanof.wordpress.com/2012/11/03/cm10-0-jelly-bean-for-nook-tablet-uploading/)
I copied them to a 16GB 10x SD card and placed the SD card in my NT.
The problem is that whatever I do, it always boots the stock os and never into Cyanoboot. I know I have to connect the NT to my computer with USB and wait for it to boot, but even then it only load the stock OS.
Am I doing something wrong here?
Help much appreciated!
Hello XDA,
I am a noob to the forum, but not to rooting my peripherals. I just came from an HTC Inc 2 that I previously had just DevUnlocked via HTC, then went full root with S-off via tacoroot method. I since have retired the phone and now have a DInc 4G LTE verizon. I have just used the FakeCID script method to gain bootloader unlock. I now have superuser installed and TWRP as the recovery. The question I have is relating to ROM installation. I have tried to install both ViperLTE and PizzutoClaws ROM's with no luck. I erase every thing 3x as stated in various posts as well as factory reset and system erase. When installing the ROM's, the aroma installer boots up and does the usual walk through, but at the end of the selections to install right after the selection for 'dirty wipe or full wipe' the aroma installer shows it's wiping the cache and such for a few seconds then immediately goes right to the 'Installation complete' screen. There should be some wait time and a loading bar showing the rom is loading. Both ROM's are doing this and thus the ROM is not installed. Is it possible I have an issue with the bootloader unlock? I have since reverted back to the stock ROM still at ****TAMPERED**** ****UNLOCKED**** with super user. I really would like to install a new ROM and could use some guidance. Thanks.
rudyo78427 said:
Hello XDA,
I am a noob to the forum, but not to rooting my peripherals. I just came from an HTC Inc 2 that I previously had just DevUnlocked via HTC, then went full root with S-off via tacoroot method. I since have retired the phone and now have a DInc 4G LTE verizon. I have just used the FakeCID script method to gain bootloader unlock. I now have superuser installed and TWRP as the recovery. The question I have is relating to ROM installation. I have tried to install both ViperLTE and PizzutoClaws ROM's with no luck. I erase every thing 3x as stated in various posts as well as factory reset and system erase. When installing the ROM's, the aroma installer boots up and does the usual walk through, but at the end of the selections to install right after the selection for 'dirty wipe or full wipe' the aroma installer shows it's wiping the cache and such for a few seconds then immediately goes right to the 'Installation complete' screen. There should be some wait time and a loading bar showing the rom is loading. Both ROM's are doing this and thus the ROM is not installed. Is it possible I have an issue with the bootloader unlock? I have since reverted back to the stock ROM still at ****TAMPERED**** ****UNLOCKED**** with super user. I really would like to install a new ROM and could use some guidance. Thanks.
Click to expand...
Click to collapse
are you flashing the boot.img via adb this is required if you are not s-off.
also check the zip on the sdcard and make sure you don't have (2)zips on it, make sure the rom zip is not in any other folder on card, must be at the root of the sdcard
also, you need to be on software 2.17.605.2-which I assume you are to be unlocked
Aldo101t said:
are you flashing the boot.img via adb this is required if you are not s-off.
also check the zip on the sdcard and make sure you don't have (2)zips on it, make sure the rom zip is not in any other folder on card, must be at the root of the sdcard
Click to expand...
Click to collapse
Thanks for the response. I have verified both ROM files are just .zip files. I even did MD5 check sum and the files are matching. I have placed them on the root of the SD card. I did notice however that when I am in ES file explorer the directory shows /sdcard/ with files that look similar to the root of the SD card, but then there is also ext_sd and when I select that, it lists the files I loaded on the SD card. I load the files via SD reader and not through the phone. Is it possible I could move the ROM over to the sdcard/ directory or should it be on the ext_sd. This Inc4g storage allocation is different than the DInc2....confusing.
rudyo78427 said:
Thanks for the response. I have verified both ROM files are just .zip files. I even did MD5 check sum and the files are matching. I have placed them on the root of the SD card. I did notice however that when I am in ES file explorer the directory shows /sdcard/ with files that look similar to the root of the SD card, but then there is also ext_sd and when I select that, it lists the files I loaded on the SD card. I load the files via SD reader and not through the phone. Is it possible I could move the ROM over to the sdcard/ directory or should it be on the ext_sd. This Inc4g storage allocation is different than the DInc2....confusing.
Click to expand...
Click to collapse
yes the zip needs to be on ext-sdcard not the internal card.
rudyo78427 said:
Thanks for the response. I have verified both ROM files are just .zip files. I even did MD5 check sum and the files are matching. I have placed them on the root of the SD card. I did notice however that when I am in ES file explorer the directory shows /sdcard/ with files that look similar to the root of the SD card, but then there is also ext_sd and when I select that, it lists the files I loaded on the SD card. I load the files via SD reader and not through the phone. Is it possible I could move the ROM over to the sdcard/ directory or should it be on the ext_sd. This Inc4g storage allocation is different than the DInc2....confusing.
Click to expand...
Click to collapse
Forgot to mention that I have also tried to flash the boot.img files via fastboot. this is normal practice for HTC phone with unlocked bootloader only if I am not mistaken. I pull the boot.img file from the ROM zip. a quick note though, I noticed when doing the flash for the recovery or boot image, in the bootloader screen, the right side load bar show's up green as it's loading, but right after the bar is highlighted red and will show a quarter of red bar for a brief second. I noticed too that the twrp recovery will not load all the time. sometimes I have to pull the battery and retry.
rudyo78427 said:
Forgot to mention that I have also tried to flash the boot.img files via fastboot. this is normal practice for HTC phone with unlocked bootloader only if I am not mistaken. I pull the boot.img file from the ROM zip. a quick note though, I noticed when doing the flash for the recovery or boot image, in the bootloader screen, the right side load bar show's up green as it's loading, but right after the bar is highlighted red and will show a quarter of red bar for a brief second. I noticed too that the twrp recovery will not load all the time. sometimes I have to pull the battery and retry.
Click to expand...
Click to collapse
what version of twrp are you using-the is an official twrp 2.4.3 now
http://techerrata.com/file/twrp2/fireball/openrecovery-twrp-2.4.3.0-fireball.img
Aldo101t said:
what version of twrp are you using-the is an official twrp 2.4.3 now
I initially used the 2.4.3.0 version. after the initial issues, I went to twrp site and downloaded the latest 2.4.4 and still having the same issues. Another note, I noticed on the ROM installation instructions on either rom, there is no mention of the System-erase button use. This is the one that erases the current ROM. I tried just factory reset 3x, cache erase 3x and delvik cache 3x with out doing the system erase. flash the rom going through the aroma installer, then flashing the boot img. the phone will boot back into the stock ROM. I'm still wondering why the aroma installer says the rom loaded so quickly after doing the full wipe 4xt format with out showing any load progress. On the Inc2 I had, I switched rom's regularly with no issues and the ones that used aroma installer, has some wait time to load the rom files. I guess I will try a full format on the SD card and just load the rom zips to see if that does anything. Thanks again for the replies. Much appreciated.:good:
Click to expand...
Click to collapse
rudyo78427 said:
Aldo101t said:
what version of twrp are you using-the is an official twrp 2.4.3 now
I initially used the 2.4.3.0 version. after the initial issues, I went to twrp site and downloaded the latest 2.4.4 and still having the same issues. Another note, I noticed on the ROM installation instructions on either rom, there is no mention of the System-erase button use. This is the one that erases the current ROM. I tried just factory reset 3x, cache erase 3x and delvik cache 3x with out doing the system erase. flash the rom going through the aroma installer, then flashing the boot img. the phone will boot back into the stock ROM. I'm still wondering why the aroma installer says the rom loaded so quickly after doing the full wipe 4xt format with out showing any load progress. On the Inc2 I had, I switched rom's regularly with no issues and the ones that used aroma installer, has some wait time to load the rom files. I guess I will try a full format on the SD card and just load the rom zips to see if that does anything. Thanks again for the replies. Much appreciated.:good:
Click to expand...
Click to collapse
there is an option under wipe for system.
---------- Post added at 01:16 PM ---------- Previous post was at 01:10 PM ----------
Aldo101t said:
rudyo78427 said:
there is an option under wipe for system.
Click to expand...
Click to collapse
you should wipe data/factory reset--wipe cache--wipe dalvic--wipe system then install rom
Click to expand...
Click to collapse
Click to expand...
Click to collapse
rudyo78427 said:
...I have tried to install both ViperLTE and PizzutoClaws ROM's with no luck. I erase every thing 3x as stated in various posts as well as factory reset and system erase. When installing the ROM's, the aroma installer boots up and does the usual walk through, but at the end of the selections to install right after the selection for 'dirty wipe or full wipe' the aroma installer shows it's wiping the cache and such for a few seconds then immediately goes right to the 'Installation complete' screen...
Click to expand...
Click to collapse
I had this exact same problem when using TWRP 2.4.3.0. I re-flashed my phone with TWRP 2.3.3.0 and my ROMS installed without any issues.
Atomic83 said:
I had this exact same problem when using TWRP 2.4.3.0. I re-flashed my phone with TWRP 2.3.3.0 and my ROMS installed without any issues.
Click to expand...
Click to collapse
Thanks for the suggestion. That was my other consideration, to go with a lower rev recovery. I will try that and see if it works. :good:
Success!!!
rudyo78427 said:
Thanks for the suggestion. That was my other consideration, to go with a lower rev recovery. I will try that and see if it works. :good:
Click to expand...
Click to collapse
Success!!!!! Thanks for the last tip to try a lower recovery version. Seems TWRP 2.4 on up didn't work allowing the Aroma Installer to complete installation. I have downgraded to twrp version 2.3.3.0 and the ROM's flash now. Thank you XDA community!!! :laugh:
rudyo78427 said:
... I erase every thing 3x as stated in various posts ....
Click to expand...
Click to collapse
A discussion about this starts here and continues for a couple pages.
The 2.4.x series TWRP recoveries have been working fine to install Sense based ROMs with Aroma installers for numerous individuals. You should only need to: Wipe > Factory Reset (this takes care of all types of cache as well) and Wipe > System. As mentioned before, ensure the zip file you're installing is on the external storage. In TWRP, at the install screen, toggle the radio button back and forth between Internal Storage and External Storage to make sure you are reading the zip from the external storage (I've seen the file list show the wrong contents before until it is toggled).
Edit: TWRP 2.4.3.0 and newer seem to have trouble with Aroma
mdmower said:
A discussion about this starts here and continues for a couple pages.
The 2.4.x series TWRP recoveries have been working fine to install Sense based ROMs with Aroma installers for numerous individuals. You should only need to: Wipe > Factory Reset (this takes care of all types of cache as well) and Wipe > System. As mentioned before, ensure the zip file you're installing is on the external storage. In TWRP, at the install screen, toggle the radio button back and forth between Internal Storage and External Storage to make sure you are reading the zip from the external storage (I've seen the file list show the wrong contents before until it is toggled).
Click to expand...
Click to collapse
Thanks for the feedback, mdmower. I had done a complete format of my sd card on the comp and loaded only the zip file on the card. I also had done 3x factory wipe/reset, 3x cache delete and 3x delvik cache wipe. All of my attempts at getting the ROMS to load failed. The aroma installer would go through the setup, but when it executed the actual writing/flashing of the files, it wouldn't finish. The program stated that the zip file was 'Installed successfully, but no OS was actually loaded(stuck at white HTC boot screen). I tried this with different twrp recoveries. It wasn't until I used twrp version 2.3.3.0 that the ROM's load successfully. I have since flashed Pizzuto claw's and now running ViperLTE. I am thinking of going with CM10.1 now, but not sure of the latest nightly release. Waiting for a stable release. Question, noticed your device list shows your using CM10.1. How is it working for you? any real bugs? I need sim card support as i travel overseas and have different sim cards for the various regions I visit. :good:
rudyo78427 said:
I also had done 3x factory wipe/reset, 3x cache delete and 3x delvik cache wipe.
Click to expand...
Click to collapse
First thing, drop this habit. A single factory reset will suffice.
rudyo78427 said:
All of my attempts at getting the ROMS to load failed. The aroma installer would go through the setup, but when it executed the actual writing/flashing of the files, it wouldn't finish. The program stated that the zip file was 'Installed successfully, but no OS was actually loaded(stuck at white HTC boot screen). I tried this with different twrp recoveries. It wasn't until I used twrp version 2.3.3.0 that the ROM's load successfully.
Click to expand...
Click to collapse
Issues with aroma and TWRP versions 2.4.3.0 and greater have been confirmed (possibly other 2.4.x releases). The folks behind TWRP suspect a problem with make_ext4fs, but it is unclear whether the blame lies within TWRP, the update_binary, or the particular make_ext4fs called by Aroma.
rudyo78427 said:
I am thinking of going with CM10.1 now, but not sure of the latest nightly release. Waiting for a stable release. Question, noticed your device list shows your using CM10.1. How is it working for you? any real bugs? I need sim card support as i travel overseas and have different sim cards for the various regions I visit. :good:
Click to expand...
Click to collapse
Read the first post in the CM thread. Others have successfully used CM outside the U.S.
Hello all,
I'm having a ton of trouble with my nook tablet 16GB. Yesterday I decided to to try to completely turn it into an android tablet with no trace of the nook remaining software wise. So at first I went to youtube and saw a vid how to root it, it had a link in the description on the software I would need.
Everything went fine, It gave me root and even had a separate home launcher/ menu that had gapps and all. Now If I knew the hassle I was in for i'd have left it there, but I didn't. So the next thing I did was go to the cyanogen site and and dl the latest stable build which is cm-10.1.2, dated july 11 2013. I put the zip on the root of my sd card and try to flash with CWM based recovery 5.0.2.8. It looks like it completes as it doesn't abort or give any error messages but It would just get to the cm logo screen, and spin for about two seconds and go back to cyanoboot.
Since I didn't want to go any further based on frustration, I decided to go back to stock and just forget it. I downloaded a stock 1.4.2 rom and flashed it with the 5.0.2.8 and it was fine. It booted into the nook os and everything was good. Now since my nook was originally 1.4.3 I wanted to get it back to that before I quit for good. So I dl the 1.4.3 update from B&N, place it on the root of the actual tablet to do the manual update but it keeps booting into the 5.0.2.8 recovery and thats there I am now.
Tried flashing different versions of stock roms, stock- rooted roms, custom roms, some fail to flash, some look like they flash completely but it always takes my back to the cm recovery. In need of some help guys/gals. Also, I know most of the responses will be "use the search" However I doubt that anyone is having exactly this issue, with exactly these circumstances surrounding it, so I probably wont get an answer that actually helps me any.
You need CWM 6.x.x to flash CM10 properly. You can use your current CWM to flash a new one but I would suggest using this near fool proof way instead. You can use whatever CM10.x ROM you want but make sure you get the right version gapps to go with it.
Copied from another topic:
I would suggest you start over again and here is really easy way to do it:
1. Download, extract and burn this ready-made CM10 sd image to a 2 GB (?) (or larger - not 100% sure of the size since I use a larger card myself) sd card. Use this card as a bootable CWM card. Even if it's a complete run-able CM10 it also works as a bootable CWM! Very handy!
http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/ t's a big download, but it's a more or less fool proof way of doing it! If I remember correctly there is actually room enough to put CM10 and GApps on the card. At least the one I use.
2. Boot into the recocvery of that card by pressing the "n" right after the power button and then hold the "n" to get to boot menu
3. In boot menu choose "sd recovery" ot something similar. This will take you to CWM
4. When in CWM install zips, wipe cache and Dalvik and you should be fine!
Once CM10 is installed it probably comes with CWM (the one I use does), so to get into CWM next time you need it, just hold "n" like before, but no need for a CWM card.
Edit: I checked, and there IS enough room for my favourite ROM and gApps on the boot section of the card. "My favourite" is the 1231 build on Iamafanof site. I have tried more recent ones, but I always go back to this one. Just my opinion of course! http://iamafanof.wordpress.com/2012/11/03/cm10-0-jelly-bean-for-nook-tablet-uploading/
Sent
Sent from my BNTV600 using Tapatalk 4
---------- Post added at 11:11 PM ---------- Previous post was at 10:47 PM ----------
And FWIW, you'll find pretty much exactly the same story as yours told quite a few times here and pretty much always with a happy ending as long as you haven't started wiping and formatting things randomly.
Something you might have discovered if you had actually done some searches. I actually find your assumption that you wouldn't find a solution a little bit both nonchalant and slightly offending.
Sent from my BNTV600 using Tapatalk 4
Ok i'm a little lost. I did what you said and got the image and wrote with win32diskimager. Put sd in and turned on power and to the sdc recovery and flashed it. I'm lost here. I figured there would just be another image cm mod 10 or something in the card and I would simply choose to flash it after selecting flash from sd or something to that effect.
I didnt see anything like that. Is there something i'm supposed to be flashing to install the clockwork mod? Your post says once I install cwm i'm good, but I don't know how to do that apparently because I don't see any rom to do so.
I am able to boot cyanogenmod from the card but that's not what I want to do. I want to flash it permanent to the rom and not have to worry about it again. How can I do this?
Btw I'm not sure if the flash worked totally, as If I just power one and do nothing it takes me to the clockwork mod 5.0.2.8. If I power on and hold the n the cyanboot will come up and I have to select the sdc recovery everytime just to make it show the 6.x.x.x version. I though your instructions would make the 6.x.x.x the default version from now on.
In any even, I'm still a little stuck. Lil more help please?
You need to put the files you want to flash on either that card or another card. Hence the comment about checking for space.
Sent from my BNTV600 using Tapatalk 4
---------- Post added at 01:05 AM ---------- Previous post was at 12:46 AM ----------
tical2399 said:
I am able to boot cyanogenmod from the card but that's not what I want to do. I want to flash it permanent to the rom and not have to worry about it again. How can I do this?
Click to expand...
Click to collapse
Are you actually reading what I write? I clearly tell that the card is meant to get you started as a bootable CWM card.
That means that it takes you into a CWM version that is correct for flashing CM10.X.
Once you are in the correct CWM you flash the same way you did when you had the wrong CWM.
Once you've done your flashing you will have everything installed internally and you can throw away the card.
And to be extra clear: You have to add the actual ROM and gApps to the card, or if there isn't enough room to another card.
Sent from my BNTV600 using Tapatalk 4
asawi said:
You need to put the files you want to flash on either that card or another card. Hence the comment about checking for space.
Sent from my BNTV600 using Tapatalk 4
Click to expand...
Click to collapse
That actually came to me as I was waiting for a reply. The reason I didnt thin of it sooner was that when I did the steps with the rooting stock nook it shrunk my card down to like 4 mb in size. I though this would do the same, and thus there would be no room for cm 10. However I decided to look and it was enough space. I just added the zip and flashed it with cwm 6.x.x. We'll see if it works
No luck. I flashed the cm 10.1.2 zip, I watch the blue status bar go all the way to the end, and the messages at the bottom say complete. I wipe the cache and the dalvik as suggested. and I hit reboot system. It just boots me right back into the cwm 5.0.2.8
Wich zip do you flash?
Try the one I suggest and if that works you can then flash another one to replace it if you want to.
You can start over with a completely 'virgin" stock Tablet in case it's your previous install of CWM 5 that's messing up things. Search for repart.img and run it and then start over again fresh
Sent from my BNTV600 using Tapatalk 4
asawi said:
You need to put the files you want to flash on either that card or another card. Hence the comment about checking for space.
Sent from my BNTV600 using Tapatalk 4
---------- Post added at 01:05 AM ---------- Previous post was at 12:46 AM ----------
Are you actually reading what I write? I clearly tell that the card is meant to get you started as a bootable CWM card.
That means that it takes you into a CWM version that is correct for flashing CM10.X.
Once you are in the correct CWM you flash the same way you did when you had the wrong CWM.
Once you've done your flashing you will have everything installed internally and you can throw away the card.
And to be extra clear: You have to add the actual ROM and gApps to the card, or if there isn't enough room to another card.
Sent from my BNTV600 using Tapatalk 4
Click to expand...
Click to collapse
There is no need for all that. I did what you said. I booted into the proper clockwork mod 6.0.2.7, I figured out that I need to copy the cm10.2 rom to the card and flash. I did that. the problem is that even after flashing it wont boot to cm 10 from the internal storage. It still boots to cwm 5.0.2.8
tical2399 said:
That actually came to me as I was waiting for a reply. The reason I didnt thin of it sooner was that when I did the steps with the rooting stock nook it shrunk my card down to like 4 mb in size. I though this would do the same, and thus there would be no room for cm 10. However I decided to look and it was enough space. I just added the zip and flashed it with cwm 6.x.x. We'll see if it works
No luck. I flashed the cm 10.1.2 zip, I watch the blue status bar go all the way to the end, and the messages at the bottom say complete. I wipe the cache and the dalvik as suggested. and I hit reboot system. It just boots me right back into the cwm 5.0.2.8
Click to expand...
Click to collapse
Did you mistakenly format the /boot partition? It sounds like a bootloop. That could happen because a 512 byte file in that partition got deleted, I forgot the name of the file though.
Also, for future reference, you don't even have to root your devices (most of the time) to get a recovery image and aftermarket OS installed. This is what I followed to get CM10.1 on my Nook Tablet, a video guide by Ray Waldo: https://www.youtube.com/watch?v=c6D4s3okNQk
The OS he is using in that video is a live Ubuntu CD/USB, one of many Linux distributions. You need a program called GParted to set flags on the partition. If you want, you can instead get the live CD of GParted, but it wont be as user friendly as Ubuntu. (I'm a Debian guy myself though).
asawi said:
Wich zip do you flash?
Try the one I suggest and if that works you can then flash another one to replace it if you want to.
You can start over with a completely 'virgin" stock Tablet in case it's your previous install of CWM 5 that's messing up things. Search for repart.img and run it and then start over again fresh
Sent from my BNTV600 using Tapatalk 4
Click to expand...
Click to collapse
I flashed cm-10.1.2-acclaim directly from the cm site under stable releases. So that's exactly what its called? repart.img? Is that one size fits all or is there a specific one for the nook tablet?
http://forum.xda-developers.com/showthread.php?t=1663836 go to first page first post. You already have the tools so you just download the BN file, extract it and burn the repart.img
When you run the repart.img a green check mark should appear after a couple of minutes. When it does take out the card and the restore starts. If you get a red cross instead of the green check mark it means you messed up something when you were fiddling around in CWM 5.
If it does work I suggest you then follow my previous instructions again and use the exact ROM I link to as a starter setup that you then can change once you've seen things work.
Sent from my BNTV600 using Tapatalk 2
asawi said:
http://forum.xda-developers.com/showthread.php?t=1663836 go to first page first post. You already have the tools so you just download the BN file, extract it and burn the repart.img
When you run the repart.img a green check mark should appear after a couple of minutes. When it does take out the card and the restore starts. If you get a red cross instead of the green check mark it means you messed up something when you were fiddling around in CWM 5.
If it does work I suggest you then follow my previous instructions again and use the exact ROM I link to as a starter setup that you then can change once you've seen things work.
Sent from my BNTV600 using Tapatalk 2
Click to expand...
Click to collapse
I followed that guild to the letter, but there is no green check, it just says that it will shut down in 5 secs and remember to take the card out before powering up . The guide says that it should restart, but it doesnt. So thats where I am now.
What's on the screen before it says it will shut down? I have not heard of anyone not getting either the green or red mark.
Sent from my BNTV600 using Tapatalk 4
---------- Post added at 02:38 AM ---------- Previous post was at 02:27 AM ----------
How far into this description from that topic does things work as described? I don't connect to computer when I do this. I just turn on power, but maybe some devices need to be kick started by inserting the powered USB cable. If so I would do that instead of pushing power button.
* Put that SD card in your Nook Tablet
* Connect your Nook to your PC/Laptop
* Hold the power button of your Nook until you see "n" logo pops up
* release the powe button, in 1-2 minutes you will see a messsge "Please DO NOT turn off your device.....installing new software"
* Now DONT do anythign to your Nook - Just sit back and relax
* Once Nook finishes installing IMG, a "Green Checkmark" will appear on top right hand corner
* Remove your SD card from your Nook Tablet
* You will see Nook will restart itself
* Then you will be see a message displaying "Clearing Data"
* Afterwords you will see a message displaying "Installing factory Software...Do not Turn off your device"
Sent from my BNTV600 using Tapatalk 4
its a black screen with a picture of a nook with a green arrow pointing down and a red X at the top right of the screen.
I figure the red X will turn into a green check once its done because it says in red letters installing software do not turn off the machine.
the green check never comes it just says shutting down in 5 seconds remember to remove SD card before powering on.
I have to remove the SD card I have tried leaving to SD card in I have waited for it to reboot on its own I have tried to reboot it myself it just never gets to the clearing data portion that is described in the guide
Well like I said before, the red x means you messed up something when in CWM 5. Probably what Sagirfahmid suggested. If you've ruined the boot section I can't help you. It is fixable and there are instructions here since you're certainly not the first one to have done it. I haven't dealt with that myself though so I can't help.
Until you find out what to do, run CM10 from that image you downloaded. It's very good and performs very well even from sd-card
Sent from my BNTV600 using Tapatalk 4
---------- Post added at 03:07 AM ---------- Previous post was at 02:54 AM ----------
Could this be something? I haven't checked it out myself so I don't know.
http://forum.xda-developers.com/showpost.php?p=25355594&postcount=8
Sent from my BNTV600 using Tapatalk 4
Since I suspect there's only a minor fault, here's something you can try. I have no idea if it can work, but it's worth a try! I have made a backup from a Tablet running CM10 and put a zip file of it in my Public DropBox folder. You can unzip it and try to use the restore fucntion in the CWM 6.x.x that you can get into with the sd-card you made. I don't think there is enough room for the backup file, but once CWM 6.x.x. is running you can switch sd cards. The reason I thought this would be worth a try is that the boot section is backed up, and in case there's a tiny problem with yours maybe this is all it needs to get going.
I will leave the link and the file for about 24 hours or until you say you've downloaded it (or say you're going to try something else instead).
Edit: Link removed. New link in later post!
asawi said:
Since I suspect there's only a minor fault, here's something you can try. I have no idea if it can work, but it's worth a try! I have made a backup from a Tablet running CM10 and put a zip file of it in my Public DropBox folder. You can unzip it and try to use the restore fucntion in the CWM 6.x.x that you can get into with the sd-card you made. I don't think there is enough room for the backup file, but once CWM 6.x.x. is running you can switch sd cards. The reason I thought this would be worth a try is that the boot section is backed up, and in case there's a tiny problem with yours maybe this is all it needs to get going.
I will leave the link and the file for about 24 hours or until you say you've downloaded it (or say you're going to try something else instead).
https://dl.dropboxusercontent.com/u/21757912/2013-09-16.17.11.14.zip
Click to expand...
Click to collapse
Thanks for the hint, but it didnt work either. It just aborted. I actually had enough space to put your image on the bootable card. I book into cyanoboot, and go to sdc recovery. It brings up cwm 6.0.2.7 and i try to flash your image from the sd card but it fails.
Anyone know where I can get instructions on how to repair/restore/reflash boot section. I've running the tab off the card with the cm 10 rom as mention in earlier posts, but I'd really like to get this fixed so it boots internally. Any help in pointing me to some instructions would help. Thanks
tical2399 said:
Thanks for the hint, but it didnt work either. It just aborted. I actually had enough space to put your image on the bootable card. I book into cyanoboot, and go to sdc recovery. It brings up cwm 6.0.2.7 and i try to flash your image from the sd card but it fails.
Click to expand...
Click to collapse
Did you unzip it like I said you should? You are NOT supposed to flash it! You go to "backup and restore" in CWM 6.x.x and choose restore. Doesn't sound to me like that's what you did.
When unzipped it's a folder that probably is too big for the boot card but you can switch to another card once CWM 6.X.X is running.
Sent from my BNTV600 using Tapatalk 4
asawi said:
Did you unzip it like I said you should? You are NOT supposed to flash it! You go to "backup and restore" in CWM 6.x.x and choose restore. Doesn't sound to me like that's what you did.
When unzipped it's a folder that probably is too big for the boot card but you can switch to another card once CWM 6.X.X is running.
Sent from my BNTV600 using Tapatalk 4
Click to expand...
Click to collapse
My fault I didn't unzip it before. However, I just tried it now with the unzipped folder on the root of the sd card, and i selected backup and restore and it just keeps saying cant mound sd card. I'm going to try to from the internal storage since i was able to get the tablet to boot with the help of cyanoboot.
Edit:
I booted into cyanoboot and got to the os, I attached tab to pc and copied your unzipped file to the internal storage. It says no files found when I selected backup and restore in cwm 6.x
tical2399 said:
My fault I didn't unzip it before. However, I just tried it now with the unzipped folder on the root of the sd card, and i selected backup and restore and it just keeps saying cant mound sd card. I'm going to try to from the internal storage since i was able to get the tablet to boot with the help of cyanoboot.
Edit:
I booted into cyanoboot and got to the os, I attached tab to pc and copied your unzipped file to the internal storage. It says no files found when I selected backup and restore in cwm 6.x
Click to expand...
Click to collapse
I think this time it's my mistake! It suddenly dawned on me that in CWM 6.x.x you can't just load the backup file like I was thinking. It need more. Hang on to the file and I'll see if I can figure out what else id needed!
asawi said:
I think this time it's my mistake! It suddenly dawned on me that in CWM 6.x.x you can't just load the backup file like I was thinking. It need more. Hang on to the file and I'll see if I can figure out what else id needed!
Click to expand...
Click to collapse
OK cool I'm at work now so I can't work on it either way, but post your suggestion/ links when you can and I'll try it out when I get home and report back. Thanks.