I was trying to root NT 1.4.2 8gb, rooted with the Market. And then I tried to root it to CM7, my NT was dead.
With Nook Recovery Flasher.apk., I rebooted, insert SD(...zip), when I tried to backup, it was dead. Then I tried again whithout backup, at first, it worked, but stopped during installing(updating... then stopped). And never boot again.
If i turn on, i can see 'N' logo with black screen, but no process. How can I reboot my NT? I want it to be the very factory setting. -.-;; Or can I find factory-base recovery file anywhere?
edit: Wait you have an 8gb tablet? Have you tried to flash 1.4.2 with cwm?
yes...
I have an 8g NT that was 1.4.2.
any backup file or booting file? please...
Good! Use cwm to flash 1.4.2 update. see if that works
thanks !!
for the quick and helpful response!!
but where can i find it? (sorry, I am not expert.)
any link? i've tried, but i can't.
and is it *.img? if so it will be OK.
but it cannot be booted, so i cannot use Nook Recovery Flasher.apk.
http://forum.xda-developers.com/showpost.php?p=24164043&postcount=1
.. read the ATTENTION 8GB USERS and apply it, and also read the READ ME (link)
~ Veronica
lavero.burgos said:
http://forum.xda-developers.com/showpost.php?p=24164043&postcount=1
.. read the ATTENTION 8GB USERS and apply it, and also read the READ ME (link)
~ Veronica
Click to expand...
Click to collapse
Wait wait wait, not to get off topic or anything. But is the 1.4.2 update, the same thing for both 8gb and 16gb nooks?/
---------- Post added at 02:26 PM ---------- Previous post was at 02:25 PM ----------
firstgleam said:
for the quick and helpful response!!
but where can i find it? (sorry, I am not expert.)
any link? i've tried, but i can't.
and is it *.img? if so it will be OK.
but it cannot be booted, so i cannot use Nook Recovery Flasher.apk.
Click to expand...
Click to collapse
Have you made a bootable sdcard?? Make you sure have at least a 2gb microsd.
soshite said:
Wait wait wait, not to get off topic or anything. But is the 1.4.2 update, the same thing for both 8gb and 16gb nooks?
Click to expand...
Click to collapse
Yes stock 1.4.2 works for both, remember 8GB NT came with 1.4.2 it is why devs base on 1.4.2 mlo, uboot, etc files to make their hacks that work for both models.
~ Veronica
Huh~
I cannot do it.
I tried several times, but failed.
My situatuion;
1. Cannot boot
2. If i try to boot, i can see only 'n' logo with black screen
3. I can boot with SD to CM7(Team-B-CM7SD-Alpha_final). In this case, I can do nothing with NT. but I can enjoy CM7 in SD.
4. I tried several times,especially, i can see sometimes <booti: bad boot img>.
How and where can i start?
firstgleam said:
I cannot do it.
I tried several times, but failed.
My situatuion;
1. Cannot boot
2. If i try to boot, i can see only 'n' logo with black screen
3. I can boot with SD to CM7(Team-B-CM7SD-Alpha_final). In this case, I can do nothing with NT. but I can enjoy CM7 in SD.
4. I tried several times,especially, i can see sometimes <booti: bad boot img>.
How and where can i start?
Click to expand...
Click to collapse
It's the stupid script in Barnes & Noble's file. Go ahead and unpack the 1.4.2 update into a folder, name it like "update" or something. Onto your computer by the way! Make a new zip, just call it update.zip
Now, on your "update" folder, navigate over to /META-INF/com/google/android/
And edit "updater-script" with notepad or something, and delete these two lines:
assert(getprop("ro.product.device") == "blaze" ||
getprop("ro.build.product") == "blaze");
Click to expand...
Click to collapse
Sweet amirite? Save it, and then move everything inside "update" onto the update.zip folder we just made. Don't move the folder, move the contents.
Then put that in the sdcard, boot into clockworkmod again and try to flash update.zip
The reason I have you do all that is because it's signed. At least that's what I think is going on, because I can't edit the files from within the zip itself.
I can't get into clockworkmod.
I can't make booting.
Always I failed.
I can just see 'N' logo....
But you said you tried to flash the update in cwm? ??
firstgleam said:
I cannot do it.
I tried several times, but failed.
My situatuion;
1. Cannot boot
2. If i try to boot, i can see only 'n' logo with black screen
3. I can boot with SD to CM7(Team-B-CM7SD-Alpha_final). In this case, I can do nothing with NT. but I can enjoy CM7 in SD.
4. I tried several times,especially, i can see sometimes <booti: bad boot img>.
How and where can i start?
Click to expand...
Click to collapse
Did you follow my instructions to the T? What errors do you get if any when flashing stock recovery or the B&N stock 1.4.2 update. zip?
If you can boot into cm7 or @meghd00t cwm recovery from sdcard all you have to do is use dd to flash stock recovery and then run the update from another sdcard.
Don't try random unbrick methods, you can make it worst, your problem is not to go and mess with advanced methods. At list yet. But if you have messed around even more since then your boot block can get damaged. Go safe first.
~ Veronica
Sent from my BNTV250A using xda premium
---------- Post added at 10:43 AM ---------- Previous post was at 10:25 AM ----------
soshite said:
It's the stupid script in Barnes & Noble's file. Go ahead and unpack the 1.4.2 update into a folder, name it like "update" or something. Onto your computer by the way! Make a new zip, just call it update.zip
Now, on your "update" folder, navigate over to /META-INF/com/google/android/
And edit "updater-script" with notepad or something, and delete these two lines:
Sweet amirite? Save it, and then move everything inside "update" onto the update.zip folder we just made. Don't move the folder, move the contents.
Then put that in the sdcard, boot into clockworkmod again and try to flash update.zip
The reason I have you do all that is because it's signed. At least that's what I think is going on, because I can't edit the files from within the zip itself.
Click to expand...
Click to collapse
CWM update.zip and B&N update.zip structure is different, so by naming B&N software update "update.zip" (meant to only be booted and flashed from sdcard) wouldn't be right and i doubt it could be flashed in CWM...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
However if you want to convert a B&N update.zip to CWM update.zip you just need:
* META-INF folder
* system folder
* boot.img
* romrestore.zip
But most likely when you attempt to reboot to stock unrooted 1.4.2 you will get bootloop, so it why is better to flash rooted roms in CWM so there is no conflict between unrooted ROM and CWM custom recovery. B&N Stock unrooted 1.4.x ROMS need stock recovery
~ Veronica
lavero.burgos said:
Did you follow my instructions to the T? What errors do you get if any when flashing stock recovery or the B&N stock 1.4.2 update. zip?
If you can boot into cm7 or @meghd00t cwm recovery from sdcard all you have to do is use dd to flash stock recovery and then run the update from another sdcard.
Don't try random unbrick methods, you can make it worst, your problem is not to go and mess with advanced methods. At list yet. But if you have messed around even more since then your boot block can get damaged. Go safe first.
~ Veronica
Sent from my BNTV250A using xda premium
---------- Post added at 10:43 AM ---------- Previous post was at 10:25 AM ----------
CWM update.zip and B&N update.zip structure is different, so by naming B&N software update "update.zip" (meant to only be booted and flashed from sdcard) wouldn't be right and i doubt it could be flashed in CWM...
However if you want to convert a B&N update.zip to CWM update.zip you just need:
* META-INF folder
* system folder
* boot.img
* romrestore.zip
But most likely when you attempt to reboot to stock unrooted 1.4.2 you will get bootloop, so it why is better to flash rooted roms in CWM so there is no conflict with the custom recovery. Stock unrooted 1.4.x ROMS need stock recovery
~ Veronica
Click to expand...
Click to collapse
All it will do is replace the recovery.img and all the other files. B&N updates not only flash /system but /recovery and /bootloader too if I remember correctly.
soshite said:
All it will do is replace the recovery.img and all the other files. B&N updates not only flash /system but /recovery and /bootloader too if I remember correctly.
Click to expand...
Click to collapse
Is why nooktablet_1_4_2_update.zip needs to be flashed from sdcard as it was meant to.
~ Veronica
lavero.burgos said:
Is why nooktablet_1_4_2_update.zip needs to be flashed from sdcard as it was meant to.
~ Veronica
Click to expand...
Click to collapse
That's what I`ve been saying :3
Sent from my NookTablet using XDA
thanks, lots of helps.
I'm not alone.
(but... mm... my knowledge is poor and so Engilsh.)
I can boot with Team-B-CM7SD-Alpha_final only with SDcard.
So I can see CM7 and use CM7.
BUT I can't access PC, PC and NT do not recognise each other so I cannot modify anything.
If I try to reboot with any other method, it will be fialed.
I tried meghd00t-r4, but just can see <booti: bad boot img...>.
I will try again today.
Then I will report.
Thanks anyway.
I Really appriciate.
soshite said:
That's what I`ve been saying :3
Sent from my NookTablet using XDA
Click to expand...
Click to collapse
i dont think so 'cause you were giving other instructions: " Go ahead and unpack the 1.4.2 update into a folder, name it like "update" or something. Onto your computer by the way! Make a new zip, just call it update.zip"
---------- Post added at 12:16 PM ---------- Previous post was at 12:09 PM ----------
firstgleam said:
thanks, lots of helps.
I'm not alone.
(but... mm... my knowledge is poor and so Engilsh.)
I can boot with Team-B-CM7SD-Alpha_final only with SDcard.
So I can see CM7 and use CM7.
BUT I can't access PC, PC and NT do not recognise each other so I cannot modify anything.
If I try to reboot with any other method, it will be fialed.
I tried meghd00t-r4, but just can see <booti: bad boot img...>.
I will try again today.
Then I will report.
Thanks anyway.
I Really appriciate.
Click to expand...
Click to collapse
Alright this "BUT I can't access PC, PC and NT do not recognise each other so I cannot modify anything." needs to be fixed, you need to get adb working if you want to unbrick your device is a must now these days until @meghd00t release a new powerful tool meant to be ran from sdcard so better let's troubleshoot that first.
Boot into CM7 or CWM from sdcard and let us know where are you stuck in setting adb up. what errors or notifications do you get if any.
Oh BTW which model do you have 8GB or 16GB? that's very important
[HOW-TO] Install & Use ADB tool | Android Debug Bridge | Drivers - Videos - Tutorial
~ Veronica
lavero.burgos said:
i dont think so 'cause you were giving other instructions: " Go ahead and unpack the 1.4.2 update into a folder, name it like "update" or something. Onto your computer by the way! Make a new zip, just call it update.zip"
Click to expand...
Click to collapse
The reason I had him unzip it is because the file is signed, but he needs to opt out two lines so that it can be flashed in cwm. This is what I said:
It's the stupid script in Barnes & Noble's file. Go ahead and unpack the 1.4.2 update into a folder, name it like "update" or something. Onto your computer by the way! Make a new zip, just call it update.zip
Now, on your "update" folder, navigate over to /META-INF/com/google/android/
And edit "updater-script" with notepad or something, and delete these two lines:
assert(getprop("ro.product.device") == "blaze" ||
getprop("ro.build.product") == "blaze");
Click to expand...
Click to collapse
Sweet amirite? Save it, and then move everything inside "update" onto the update.zip folder we just made. Don't move the folder, move the contents.
Then put that in the sdcard, boot into clockworkmod again and try to flash update.zip
The reason I have you do all that is because it's signed. At least that's what I think is going on, because I can't edit the files from within the zip itself.
Click to expand...
Click to collapse
acclaim_update.zip itself can be flashed in cwm as well. You just have to edit the updater-script in its folder. For whatever reason, B&N's updater script has device set to blaze. ????
-.-
thank you, Veronica and other guys^^
I will try again.
I have to go business trip with my boss.
-.-
It will be a sort of nightmare this weekend.
See you on the next week days.
Related
Hey everybody,
I apologize in advance if this post is a duplicate but I have tried searching for a solution and still lost. Here is what I did: I used the Odin to restore stock rom, then re-rooted using the one click method, then downloaded a rom from theunlockr.com, then used rommanger to install it. My rom has gave me no problems but now when I try to reboot into recovery to install something else(Like the 2.3 keyboard or a lagfix) i get this error:
E:Can't open /sdcard/update.zip
(No such file or directory)
Installation aborted
Can someone please help me? Thank you, BTW I have a Samsung Vibrant running axura-froyo-rom
I had the same problem too.
When I put update.zip at the root directory of internal memory... once I restart the phone (not get into the recovery mode), this file is missing / dissapear. So... I always got this message too :
E:Can't open /sdcard/update.zip
(No such file or directory)
Installation aborted
anybody can help us pleaseeeeee
I got my phone to factory settings using odin then i rerooted my phone and flashed the same custom rom back on and it worked. Try reflashing your phone, backup first, might work.
CarlosCruz15 said:
I got my phone to factory settings using odin then i rerooted my phone and flashed the same custom rom back on and it worked. Try reflashing your phone, backup first, might work.
Click to expand...
Click to collapse
thanks for reply.
how to use factory setting using odin ? tick the "re-partition" box ?
can you explain to us step by step please ?
I'm so frustated
Did you guys delete the update.zip after rooting?
If you do not see
sdcard/update.zip using a file manager, download the update.zip from my noob guide, move it to internal memory and then try to flash CWR.
Also, look in the bottom of the noob guide (last few posts) for a solution to a RECENT issue with CWR... I assume whatever Koush did in the last update is causing this problem? BUT, there is a fix posted by another XDA user... just a matte of downloading the file and putting it in the right place.
mikomikos said:
thanks for reply.
how to use factory setting using odin ? tick the "re-partition" box ?
can you explain to us step by step please ?
I'm so frustated
Click to expand...
Click to collapse
check out this link...its what i used
http://forum.xda-developers.com/showthread.php?t=734475
listen to s15's post....he knows what he is talking about. i followed his noob guide in his sticky and everythign worked perfectly! his vids are also very helpful. one thing i have found that works a lot as well is if you download ROM Manager from the market and then click on "fix permissions"... don't know if this would help in this situation but i have had that fix weird stuff.
s15274n said:
Did you guys delete the update.zip after rooting?
If you do not see
sdcard/update.zip using a file manager, download the update.zip from my noob guide, move it to internal memory and then try to flash CWR.
Also, look in the bottom of the noob guide (last few posts) for a solution to a RECENT issue with CWR... I assume whatever Koush did in the last update is causing this problem? BUT, there is a fix posted by another XDA user... just a matte of downloading the file and putting it in the right place.
Click to expand...
Click to collapse
yeah this, the update.zip is ESSENTIAL for your phone to run the clockwork recovery, it stores all the things needed, and when you click "reinstall packages" your system goes in update.zip and looks for what to boot up and finds CWR and boots that so you see that screen.
Don't delete it if you did.
i have tried numerous times to root,but cant seem to get update.zip file in right place,can anyone help? thanks. challenged noob!!
Rayn1328 said:
i have tried numerous times to root,but cant seem to get update.zip file in right place,can anyone help? thanks. challenged noob!!
Click to expand...
Click to collapse
When you usb into your phone it needs to be in the initial area of your sdcard.
You might have a bad update.zip file. Two things, verify the md5(if possible) from where you got it and check the properties and make sure it's not names update.zip.zip. The later is very common.
Try this method too btw, when I Odin back to stock I always use this one to root again. Follow the 'Automated Method' area.
http://forum.xda-developers.com/showthread.php?t=786877
you will need these drivers AND set your phone to debugging mode (settings/applications/development check USB debugging).
http://forum.xda-developers.com/showthread.php?t=728929
hey all,
Newbie here trying to flash a ROM, i am running into this same error, i have tried everything here and i have one question (might be a stupid question) but my root sd folder is called SD/, not SDCard/ ...is this a path error?
Please note it file must be in the internal card, not the SD card.
This step drove me nuts.
"2. Copy the update.zip (and the ROM) to the INTERNAL SD (not the external SD Card). sdcard/ " (http://forum.xda-developers.com/showthread.php?t=732458)
i ran into the same problem...how do i get from 3e to CWR?
here's what's shown in my vibrant directory: Android, DCIM, external_sd, LOST.DIR
i dont have an internal sd (the card) so it's not shown?
the path i got error on: /mnt/internal_sd/update.zip
1. when i tried to "reinstall packages" i keep getting the error that the update.zip file cant be found. should i create a folder for it or something? i think it's a matter of pathing but i cant find out the right place to put the file...(to get from 3e to CWR)
2. i see people suggesting boot with odin or sth like that...does that solve my problem and how do i do that?
janthe6th said:
i ran into the same problem...how do i get from 3e to CWR?
here's what's shown in my vibrant directory: Android, DCIM, external_sd, LOST.DIR
i dont have an internal sd (the card) so it's not shown?
the path i got error on: /mnt/internal_sd/update.zip
1. when i tried to "reinstall packages" i keep getting the error that the update.zip file cant be found. should i create a folder for it or something? i think it's a matter of pathing but i cant find out the right place to put the file...(to get from 3e to CWR)
2. i see people suggesting boot with odin or sth like that...does that solve my problem and how do i do that?
Click to expand...
Click to collapse
You definitely have an internal sd card. Use Astro file manager or something similar and put update.zip on the root of internal sd card, meaning not in a folder. It should look like sdcard/update.zip. If you are having the 3e mismatch recovery issue read this http://forum.xda-developers.com/showthread.php?t=833423
Sent from my SGH-T959 using Tapatalk 2
i go to the link that you linked and ran the script. then i download the update.zip file at the noob guide with a slimbean 4.2.2 rom and addons. this time i would just put it in the root folder (technically not in any folder). when i try to reinstall packages, the screen shows that it is "replacing stock recovery with clock work recovery"... but then it would go back to the 3e.
so...i guess putting the files in the root folder is correct. but someone it still wont let me get tot CWR...
janthe6th said:
i go to the link that you linked and ran the script. then i download the update.zip file at the noob guide with a slimbean 4.2.2 rom and addons. this time i would just put it in the root folder (technically not in any folder). when i try to reinstall packages, the screen shows that it is "replacing stock recovery with clock work recovery"... but then it would go back to the 3e.
so...i guess putting the files in the root folder is correct. but someone it still wont let me get tot CWR...
Click to expand...
Click to collapse
You have to reinstall packages twice for it to work properly. It is normal to not work the first time, just reinstall packages again and you should be good to go. If you keep having issues you should just flash back to stock 2.1 with Odin and go from there.
Sent from my SGH-T959 using Tapatalk 2
UPDATE: Since some of you guys are still finding this useful, I updated the CWM version to 3.0.2.8. Please note that ROM Manager is the best way to install CWM 3.0.2.8. You should only need this .zip if you need to restore the B&N boot loader.
There are a number of CWM installable .zip files being distributed that break Clockworkmod in a way that Rom Manager will not fix. This .zip file will reinstall the B&N bootloader (to enable the recovery buttons) and install ClockworkMod on your internal memory. This .zip will only help if you have installed a "flashable" .zip and can no longer get into CWM by holding N + Power on boot.
This file can be installed with IOMonster's bootable CWM to re-enable the ability to use CWM without an SD card.
How to use:
1) Create a bootable CWM SD card from the link above.
2) Mount the SD card on your computer and copy the RecoveryFix.zip file to it.
3) Boot the Nook into CWM from the SD card.
4) Choose "install zip from sdcard"
5) Choose "choose zip from sdcard"
6) Browse to the RecoveryFix.zip and select it.
7) Choose "Yes - Install RecoveryFix.zip"
CWM should now work by booting and holding the N + Power buttons.
Technical details:
The bootloader (u-boot.bin) file included with the stock image has code to look for the recovery key sequence on boot. It also contains the "Touch the Future of Reading" splash screen. Some of the update .zip releases include a custom uboot.bin (to change the splash screen) that does not look for the recovery keys...so there's no way to boot into recovery without an SD.
Currently the only automated way to put the correct files back is by using one of the stock recovery .zips. These take the entire system back to stock though. All this .zip does is replace the stock u-boot.bin file, CWM uRecRam and CWM uRecImg files on the /boot partition. This can also be easily fixed by booting any image from an SD card and copying these files manually.
is this for use with any flashable rom or only certain ones? i'm on hcv4 and want to make sure this is safe to use before flashing it.
This worked fantastic! Thank you!
byproxy said:
is this for use with any flashable rom or only certain ones? i'm on hcv4 and want to make sure this is safe to use before flashing it.
Click to expand...
Click to collapse
This is a standalone fix - its only necessary if you've flashed a rom and could no longer boot into CWM recovery afterward.
thanks again xawen!
Thanks so much for this! Great work!
Signature verification failed
Will This work with the Froyo builds?
Thanks
huemedia said:
Will This work with the Froyo builds?
Thanks
Click to expand...
Click to collapse
It should work with any build. It does not replace any of the build specific files, just the boot loader and the recovery images.
Works on phiremod (CM7). I was stressing why I couldn't reach my internal recovery, but was too lazy to do any research on the matter. Just stumbled upon this and everything is fixed again
Just what I was looking for... thanks!
omarsalmin said:
Works on phiremod (CM7). I was stressing why I couldn't reach my internal recovery, but was too lazy to do any research on the matter. Just stumbled upon this and everything is fixed again
Click to expand...
Click to collapse
what do you mean by "everything is fixed again"?
I like phiremod and all, but no internal storage is irking me and I want to go back to rooted stock and try to make a CM7 bootable SD.
Flashed this, now I'm stuck on the "Touch the Future of Reading" splash screen. Running CM7 nightly latest, dalingrin's 1100MHz Overclock.
Edit: Trying to boot, won't get past that damn splash screen. Tried reflashing cm7-encore-full-5.zip, gapps, got nothing. Going to try flashing the overclock again and see if that helps.
Edit2: No dice. I don't have a backup, either. Guess I have to flash a whole new boot.img?
This should be stickied. There are a LOT of CWR files around here right now.
oshigeru said:
Flashed this, now I'm stuck on the "Touch the Future of Reading" splash screen. Running CM7 nightly latest, dalingrin's 1100MHz Overclock.
Edit: Trying to boot, won't get past that damn splash screen. Tried reflashing cm7-encore-full-5.zip, gapps, got nothing. Going to try flashing the overclock again and see if that helps.
Edit2: No dice. I don't have a backup, either. Guess I have to flash a whole new boot.img?
Click to expand...
Click to collapse
Same thing kept happening to me. I would hold down the power button or power+n button or power+volume up + n button to get the NC to shut down. Then, I'd press the power+volume up + n button for a few seconds; this would get it to boot into CWR. From CWR I'd select reboot system. After that it would have no problem fully booting (until the problem happeend again). I did notice that after a while the startup boot took longer. After pressing the power button to power on the NC it would take several seconds before the "touch the future of reading" screen to come up, and it would take several more seconds (30 or so) for it to get past that screen.
I'm not sure what the beneft is of doing this; as long as I have a CWR bootable microSD with me (always in the NC's case) I don't need this.
xawen said:
There are a number of CWM installable .zip files being distributed that break Clockworkmod in a way that Rom Manager will not fix. This .zip file will reinstall the B&N bootloader (to enable the recovery buttons) and install ClockworkMod on your internal memory. This .zip will only help if you have installed a "flashable" .zip and can no longer get into CWM by holding N + Power on boot.
This file can be installed with IOMonster's bootable CWM to re-enable the ability to use CWM without an SD card.
How to use:
1) Create a bootable CWM SD card from the link above.
2) Mount the SD card on your computer and copy the RecoveryFix.zip file to it.
3) Boot the Nook into CWM from the SD card.
4) Choose "install zip from sdcard"
5) Choose "choose zip from sdcard"
6) Browse to the RecoveryFix.zip and select it.
7) Choose "Yes - Install RecoveryFix.zip"
CWM should now work by booting and holding the N + Power buttons.
Technical details:
The bootloader (u-boot.bin) file included with the stock image has code to look for the recovery key sequence on boot. It also contains the "Touch the Future of Reading" splash screen. Some of the update .zip releases include a custom uboot.bin (to change the splash screen) that does not look for the recovery keys...so there's no way to boot into recovery without an SD.
Currently the only automated way to put the correct files back is by using one of the stock recovery .zips. These take the entire system back to stock though. All this .zip does is replace the stock u-boot.bin file, CWM uRecRam and CWM uRecImg files on the /boot partition. This can also be easily fixed by booting any image from an SD card and copying these files manually.
Click to expand...
Click to collapse
This fixed my nook. Thanks!!!!!
Works - after a few tries!
Really appreciate the work. Thanks!
While I keep my boot disk with me, I am very happy to have the ability to power+N into CWR.
Great work, thanks m8s!
xawen said:
All this .zip does is replace the stock u-boot.bin file, CWM uRecRam and CWM uRecImg files on the /boot partition.
Click to expand...
Click to collapse
Can you be more specific about exactly which u-boot.bin, uRecRam and uRecImg files are included - including source and version ?
ADude said:
Can you be more specific about exactly which u-boot.bin, uRecRam and uRecImg files are included - including source and version ?
Click to expand...
Click to collapse
This .zip has the stock (B&N) u-boot.bin and the uRecRam and uRecImg for CWM 3.0.0.5. It was built a while ago to fix an issue with specific CMW installable Froyo .zip files that were being distributed. I haven't seen any CM7 images with this problem, but if anyone still has a need for this I can update to a current CWM version and post tonight.
xawen said:
This .zip has the stock (B&N) u-boot.bin and the uRecRam and uRecImg for CWM 3.0.0.5. It was built a while ago to fix an issue with specific CMW installable Froyo .zip files that were being distributed. I haven't seen any CM7 images with this problem, but if anyone still has a need for this I can update to a current CWM version and post tonight.
Click to expand...
Click to collapse
Aha - I looked more closely and saw that it is an old thread that was brought to the surface by a "thanks" comment.
question
So I flash this fix and can get into CWM 3.0.0.5, then I flash the official CWM 3.0.1.0 and can no longer get into recovery. I also tried the manual procedure using adb. Still no dice.
What am I doing wrong?
THIS THEME IS ONLY FOR THE BELL ATRIX. IT REQUIRES YOU TO HAVE A DEODEXED SYSTEM.
Disclaimer: I am not responsible for any softbricking that may happen to your device. I have tested it on my phone only.
I am releasing a Gingerbread theme I made for the Bell Atrix . Please let me know if you find any bugs that I haven't so far.
The next version will have the carrier removed from the notification bar, but for now its just invisible because of the black text.
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download:
CWM install zip (OLYEM U4 1.4.2):
BellGingerbread1.3-CWM.zip
Manual install files (OLYEM U4 1.4.2):
BellGingerbread-V1.3.zip
_________________________________________
Old Versions (Bell 0.37.4):
BellGingerbread-V1.2(with scripts).zip
Installation:
First you need to have deodexed your system files. This can be done by following the instructions in this thread:
[script][SCRIPT] OLYEM_U4 1.4.2 Telstra/Bell FULL Deodex for OLYEM 1.4.2
OR
[script] Deodexed files for Bell for Bell 0.37.4.
CWM
1. Download the CWM zip
2. Place the still compressed zip onto your SD card
3. Boot into recovery and install zip
Manual
1. Download the manual files package and extract it
2. Put the files from the install files directory in the root directory of your SD card
3. Run this code in ADB
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
cp -f /sdcard/framework-res.apk /system/framework/
cp -f /sdcard/services.jar /system/framework/
cp -f /sdcard/blur-res.apk /system/framework/
sync
reboot
Uninstall:
For CWM method:
1. Download the CWM backup BellGingerbread1.3-CWM-BACKUP.zip
2. Follow instructions for CWM install but use the backup zip
For manual method:
1. Download backup files BackupFilesBell-OLYEM1.4.2.zip
2. Follow instructions from the manual install but use the backup files
For install script (V1.2 Only):
1. Run RESTORE.BAT
Extras:
Gingerbread Keyboard: [MOD] Gingerbread Keyboard on Atrix!
Nexus Boot Animation (Much better then the Telstra one):
1. Download the bootanimation.zip
2. Put the bootanimation.zip in the root directory of your SD card
3. Run this code in ADB
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
cp -f /sdcard/bootanimation.zip /system/media/
sync
reboot
Chnagelog:
1.3 (Newest Version)
- OLYEM U4 1.4.2 Support
- Darker notification pulldown
1.2
- Added transparent notification pulldown
- Removed lock screen animation
1.1
- Added Gingerbread animations
1.0
-Original Release
Cool, I like. Are you planning on maybe making a couple different themes too?
Sent from my MB860 using XDA App
Thank you soo much! I have been waiting for something to start happening with the bell atrix's.
3 requests which im not sure are possible...
-different animations
-gingerbread screen off animation (looks like turning of a tv)
-power controls in pulldown menu??
Keep it up. Gonna try this as soon as i get home. Im assuming there is a thread on how to deodex system.
For now I'm going to keep working on this theme, maybe I'll make more later. I'm adding animations in the next version which should be out soon, and I am looking into the power controls in the notifications menu. Unfortunately its not possible to get the shutoff animation, I liked it a lot on my Desire Z, but that was actually running gingerbread.
script please or CWM
would you be able to make a script for this theme or a CWM update.zip for easy installation thanks and keep up the good work. im so happy that someone is finally creating something for the bell atrix.
Silent8Strike said:
For now I'm going to keep working on this theme, maybe I'll make more later. I'm adding animations in the next version which should be out soon, and I am looking into the power controls in the notifications menu. Unfortunately its not possible to get the shutoff animation, I liked it a lot on my Desire Z, but that was actually running gingerbread.
Click to expand...
Click to collapse
alright, i look forward to it
erik10002 said:
would you be able to make a script for this theme or a CWM update.zip for easy installation thanks and keep up the good work. im so happy that someone is finally creating something for the bell atrix.
Click to expand...
Click to collapse
i don't know what the OP's plan are, but i'd be happy to throw together a script that can do this for everyone
i haven't messed around making CWM stuff yet, so i can't promise anything there, but probably later tonight i'll post a script that can do this
we need more devs like you guys. gives me confidence in the community. Keep up the good work.
raybond25 said:
i don't know what the OP's plan are, but i'd be happy to throw together a script that can do this for everyone
i haven't messed around making CWM stuff yet, so i can't promise anything there, but probably later tonight i'll post a script that can do this
Click to expand...
Click to collapse
that would be awesome, i tried to do it through adb this morning but wasn't working for me and a script makes installing anything a heck of a lot easier.
also i have [THEME] Black Bar Bell. (Gingerbread) by toughbax on my phone, will there be any problems installing this over it?
thanks
Im gonna try the zip tonight. No rush but you think it will be up tonight?
erik10002 said:
that would be awesome, i tried to do it through adb this morning but wasn't working for me and a script makes installing anything a heck of a lot easier.
also i have [THEME] Black Bar Bell. (Gingerbread) by toughbax on my phone, will there be any problems installing this over it?
thanks
Click to expand...
Click to collapse
No, there will be no problems installing over, because you completely replace both files that are used to create the other theme. The script will be up around 10 tonight probably, got a bunch of things to do at school tonight.
Sent from my MB860 using XDA App
blunted09 said:
Im gonna try the zip tonight. No rush but you think it will be up tonight?
Click to expand...
Click to collapse
I won't upload a flashable .zip for use with cwm because I don't know how, maybe in the future, just not tonight. However, I will be uploading a .bat file later tonight around 10, so you will just be able to run that off of your pc.
Sent from my MB860 using XDA App
Awesome, I will wait for the bat file and try it tonight. Thanks again.
Sent from my MB860 using XDA Premium App
I'll see what I can do about making a zip to flash in cwm tonight when I get home from work in a few hours.
Silent8Strike said:
I'll see what I can do about making a zip to flash in cwm tonight when I get home from work in a few hours.
Click to expand...
Click to collapse
well, i just got a script working, and it makes a backup for the user too, i'm just about to make a recovery script that will restore the backup to the device, just in case the user doesn't like the theme, or if something happens to make it brick
i soft-bricked myself once because i made an absolutely retarded typo in my script the first time, and copied the files to the wrong directory, lmfao. that's fixed now obviously
raybond25 said:
well, i just got a script working, and it makes a backup for the user too, i'm just about to make a recovery script that will restore the backup to the device, just in case the user doesn't like the theme, or if something happens to make it brick
i soft-bricked myself once because i made an absolutely retarded typo in my script the first time, and copied the files to the wrong directory, lmfao. that's fixed now obviously
Click to expand...
Click to collapse
ALL DONE - install script will create a backup of your current (soon to be old) theme before installing new theme. Restore script will re-install your old theme to your device.
MUST BE DEODEXED STILL, JUST BECAUSE ITS A SCRIPT DOESN'T CHANGE THAT.
*NOTE* if the script runs through and says "Device not found" under everything, its probably because USB debugging got interrupted. I ran into this a whole bunch of times, and ran into device not found a few, but whenever that happens, if you simply run the script again right after, it will work (has been replicated by myself).
If you run into any problems further than that easily fixable one, you're probably not deodexed and rooted. If you have further problems feel free to PM me.
with the new bell SBF that was leaked will this still work? thanks
raybond25 said:
ALL DONE - install script will create a backup of your current (soon to be old) theme before installing new theme. Restore script will re-install your old theme to your device.
MUST BE DEODEXED STILL, JUST BECAUSE ITS A SCRIPT DOESN'T CHANGE THAT.
*NOTE* if the script runs through and says "Device not found" under everything, its probably because USB debugging got interrupted. I ran into this a whole bunch of times, and ran into device not found a few, but whenever that happens, if you simply run the script again right after, it will work (has been replicated by myself).
If you run into any problems further than that easily fixable one, you're probably not deodexed and rooted. If you have further problems feel free to PM me.
Click to expand...
Click to collapse
thanks man!! so where can i get the script from? i don't see any links
erik10002 said:
with the new bell SBF that was leaked will this still work? thanks
Click to expand...
Click to collapse
to be honest i'm not sure about that .sbf
unless you've already flashed it and can confirm that it works, then i would recommend that your wait until it's confirmed.
also - this will work with the new .sbf provided we can get root for the new Bell firmware. i would suggest waiting until root is completed to update, just so you can keep adding mods like this to it.
and yes - this theme should work on the new sbf, if you're on it and have root access.
aliafi90 said:
thanks man!! so where can i get the script from? i don't see any links
Click to expand...
Click to collapse
yeah, uploading now will edit this post with link in 2mins
EDIT: heres the link
For all you Shotputterz heres the factory image we've been waiting for
assuming you have debug mode enabled, ADB and fastboot working properly
EDIT 1: REUP'D CWM mod
EDIT 2: reordered process to make more sense
Method:
1. Download the Beta CWM mod from rootzwikis credit to birdman EDIT:REUP'ED http://d-h.st/Fdp
2. Using fastboot, DO NOT FLASH Clockwork mod just use the syntax
"fastboot boot 'File path of clockwork mod image'
Note* this will boot directly into the recovery without permanently writing to the recovery and boot partition on the eMMC on the Nexus Qs board
3. Download the posted CWM factory backup posted
4. make the directory on the device and adb push the backup folder (unzipped) to /sdcard/clockworkmod/backup while in CWM recovery
*The device should show up in "adb devices" while in the CWM recovery*
5. *TEXT WILL BE REALLY SMALL! Now navigate with the Scroll wheel to backups and restore and tap the mute button to select.
*IF SOMETHING IS SELECTED IN ERROR THERE IS NO BACK BUTTON JUST REBOOT AND REDO FASTBOOT BOOT*
6. Now select restore and select the image folder
7.blah blah CWM Freaking MAGIC
8. Your Q is back to factory state
If someone wants to PM me or show me how to package this in a nicer CWM zip to install with a script let me know
http://d-h.st/yeo
*Note* I am NOT responsible if you brick your already bricked Nexus Q*
You sir get a beer, since my 2nd (dev) Q won't arrive until later this week, and mine was a shot put until this post.
If you happen to be in NYC before I move to SF, you get three beers.
Hoppy ones.
I am moving to SF
Did the reflash go smoothly?
fiveipads said:
I am moving to SF
Did the reflash go smoothly?
Click to expand...
Click to collapse
No unfortunately it didn't--I blew away all partitions other than bootloader so I can't, to my knowledge at least, push the zip since I can't adb.
I've got factory recovery, boot, system imgs but the system img won't push out because of fastboot's apparent inability to handle files that large (1GB exactly I believe).
...I guess I have to patiently await my second Q but the point of having two was to *use* one and have one for dev... rather than have one as a heavy reminder of my overzealous endeavors...
Hopefully I can give it more time while on this SF trip...
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Does our Q's have internal memory.. if not wouldn't it be possible to run back up of off otg memory stick if recovery would support it
Sent from my Galaxy Nexus using xda premium
fiveipads said:
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
The problem I'm having is that ADB is not responding from CWM... at least not on a Windows machine. The drivers are fine as ADB was working in normal mode before my issue sprung up.
EDIT: As suspected Virtual Ubuntu on a Win host didn't see the device, Physical Ubuntu had no issue. NQ reloaded.
fiveipads said:
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Can we do this by say pushing the file to the download folder and then installing from zip?
And i know slightly off topic but once we've installed some apks for example, what's currently the best interface to use to navigate through the apps and use them?
How do I make a directory on Nexus Q
fiveipads said:
For all you Shotputterz heres the factory image we've been waiting for
assuming you have debug mode enabled, ADB and fastboot working properly
Method:
1. Download the posted CWM factory backup posted
2. make the directory on the device and adb push the backup folder (unzipped) to /sdcard/clockworkmod/backup
http://d-h.st/yeo
Click to expand...
Click to collapse
In step 2 you say make a directory for the file that is posted below. How do I create a directory on the Nexus Q? Currently my Q is stuck in a bootloop after trying to launch CWM from a Galaxy Nexus. If you could post command codes that would be awesome!
I figured it out. You can just follow step #4 and in CWM you can push the CWM Factory img to the /sdcard/Download/ folder and use CWM to unzip and launch.
Could someone please provide me the beta cwm image for Nexus Q? The links are all circular and point to
http://goo.im/devs/birdman/CWM-steelhead-beta.img
Which is dead...
discoltk said:
Could someone please provide me the beta cwm image for Nexus Q? The links are all circular and point to
http://goo.im/devs/birdman/CWM-steelhead-beta.img
Which is dead...
Click to expand...
Click to collapse
I've been trying to get ahold of this image too! Anyone?? anyone?? Bueller???
WildSatchmo said:
I've been trying to get ahold of this image too! Anyone?? anyone?? Bueller???
Click to expand...
Click to collapse
Me as well...not sure why I got this damn thing...lol
The edit didn't prompt an email to me even though I'm following the thread, so those of you looking for the clockworkmod beta image please take note that OP was kind enough to provide a working link to the image.
Thanks fiveipads!
Can someone post full backup please?
caioketo said:
Can someone post full backup please?
Click to expand...
Click to collapse
The link at the bottom still works for me...
http://d-h.st/yeo
..
ok this is really bothering me, i've restored with this factory image several times, and I have to do it again right now and I cannot seem to push this file folder to /sdcard/clockworkmod/backup
what am i doing wrong..
it should be:
adb push NexusQFactoryImage /sdcard/clockworkmod/backup/ (assuming the file is in same folder as adb which it is)
that's it right.... the extracted folder contents in a folder.. not the zip.. so i dont understand why this is not working. Everytime I go to CWM and try to restore it tells me nothing to restore...
what really bothers me is that i've done this a hundred times, and never had this problem..
UKROB86 said:
ok this is really bothering me, i've restored with this factory image several times, and I have to do it again right now and I cannot seem to push this file folder to /sdcard/clockworkmod/backup
what am i doing wrong..
it should be:
adb push NexusQFactoryImage /sdcard/clockworkmod/backup/ (assuming the file is in same folder as adb which it is)
that's it right.... the extracted folder contents in a folder.. not the zip.. so i dont understand why this is not working. Everytime I go to CWM and try to restore it tells me nothing to restore...
what really bothers me is that i've done this a hundred times, and never had this problem..
Click to expand...
Click to collapse
BUMP.. stuck in CWM unable to get a restorable file.. no idea why...
Download OneClickRestore (it's the factory image straight from Google with the needed fastboot files included)
Extract zip to OneClickRestore
Unplug Nexus Q
Plug in Nexus Q and place hand on it til the leds turn red then remove hand
Launch "flash-all.bat" from the OneClickRestore folder
You may need to do a full reset, it's hit or miss
Another option is push & flash (Nexus Q)uantum Singularity Project RTS ROM from CWM and again may need to hard reset.
RTS is
Based on stock 4.0.4 build IAN67K
Deodexed
Zip aligned
init.d Support
bash support
Busybox updated
Prerooted
Superuser
Updated Keymap (Home=Home, End=Back, Delete=Menu, Insert=Visualizer)
Lokifish Marz said:
Download OneClickRestore (it's the factory image straight from Google with the needed fastboot files included)
Extract zip to OneClickRestore
Unplug Nexus Q
Plug in Nexus Q and place hand on it til the leds turn red then remove hand
Launch "flash-all.bat" from the OneClickRestore folder
You may need to do a full reset, it's hit or miss
Another option is push & flash (Nexus Q)uantum Singularity Project RTS ROM from CWM and again may need to hard reset.
RTS is
Based on stock 4.0.4 build IAN67K
Deodexed
Zip aligned
init.d Support
bash support
Busybox updated
Prerooted
Superuser
Updated Keymap (Home=Home, End=Back, Delete=Menu, Insert=Visualizer)
Click to expand...
Click to collapse
The problem with putting Quantum singularity project on is that I can't turn on ADB debug, because i use a bluetooth mouse and keyboard, don't have an OTG mouse/keyboard, so somehow I need to be able to connect with adb to setup a bluetooth connected mouse/keyboard
I was thinking to install stock image, and then without wiping install Quantum SIngularity Project over top to preserve the settings for usb debug, on.
what's confusing to me is that i've restored the stock image many times before, and never had a problem.. that's why im wondering what the problem is.. if im typing something wrong.
I used the OneClickRestore as you said, and im just booting it up now
EDIT: didn't get past boot logo, i'll try again
So just to confirm this OneClickRestore is loading the stock nexus Q img right? I've never used it before I usually manually do it
EDIT: still stuck at the nexus q logo before home screen
do you see any error in my commands of trying to push the stock img folder (original post) to "/sdcard/clockworkmod/backup" ? I've done it many times before never had a problem
I never noticed that CWM was different for 1.2 and 1.1. I currently have 1.2 and tired to install CWM which was the wrong one.
When I try to enter recovery, I get a message of " booting recovery kernel image"
I can turn it off and enter into the stock rom no problem.
Any help would be great to how I can undo this and install CWM.
Used the link for CWM from step 1 from this LINK
Thanks very much.
Tap UI Version : 1.2-5699
Kernal - 2.6.32.9-svn4979
Build - FRF91
Here is a link to a .zip I built for you. You will need to have root access for this.
fix-recovery.zip
Download this to your Gtablet and unzip it to /sdcard. Iif you can't make that work, download to your PC and unzip, then transfer the files over to /sdcard. Using a root file manager (I like ES File Explorer), move the file 'flash_image' into /system/bin, overwrite or rename the existing version if there is one, and change the permissions to make it executable (match the other executable files in the /system/bin folder). Then move the file 'cwm5502.img' into /system/etc/recovery (you might have to create the 'recovery' folder). Next, go back to /sdcard and change permissions on 'fixrecovery.sh' to make it executable as well.
Now open Terminal Emulator (install from the Play store or by other means if you don't already have it) and enter the following commands:
Code:
su
sh /mnt/sdcard/fixrecovery.sh
If the second command won't run, bypass the script by running this instead:
Code:
su
/system/bin/flash_image recovery /system/etc/recovery/cwm5502.img
That will install a version of CWM that is compatible with the 1.2 boot loader. Reboot and you should be able to enter the new recovery. Post back if you cannot get this to work for you, and we can try another way. This would be easier if you have ADB installed and working, but I assume most people do not.
Rochey21 said:
I never noticed that CWM was different for 1.2 and 1.1. I currently have 1.2 and tired to install CWM which was the wrong one.
When I try to enter recovery, I get a message of " booting recovery kernel image"
I can turn it off and enter into the stock rom no problem.
Click to expand...
Click to collapse
Since you have the stock VS ROM, you'll have to use nvflash. See this thread.
---------- Post added at 08:05 PM ---------- Previous post was at 08:02 PM ----------
DaggerDave said:
Here is a link to a .zip I built for you. You will need to have root access for this.
...
Click to expand...
Click to collapse
Good try, but, there's no su on stock ROM; and the process to get one correctly installed is slightly involved.
The user will have to resort to nvflash.
rajeevvp said:
Since you have the stock VS ROM, you'll have to use nvflash. See this thread.
---------- Post added at 08:05 PM ---------- Previous post was at 08:02 PM ----------
Good try, but, there's no su on stock ROM; and the process to get one correctly installed is slightly involved.
The user will have to resort to nvflash.
Click to expand...
Click to collapse
Ok thanks, but I can not find the drivers for APX Mode, using Windows vista 32 bit?
Also just to make sure what Files would I need to use. Just want to make sure exactly what to do, and get it right.
Download the TeamDRH_350M_Prep.zip file from this post. It should have both the nVidia APX drivers and CWM-5.5.0.4 for a 1.2 bootloader (in part9.img).
Read the README file for the APX driver installation, but, don't run the NVFlash_gTablet.bat batch file. Instead, just write a new CWM using the commands in the link in my previous post.
EDIT: Note that you cannot install or upgrade the stock VS ROM using CWM. That can only be done using the stock recovery. For everything else, however, you can use CWM.
Feel like a total N00b :crying:
I have the drivers installed for AXB. I have downloads the zip folder with the img files and drivers etc. I renamed this folder to NVFlash for short.
Do I leave this folder on my laptop or put in on the tablet.
Could you please explain a bit more how to use the command window. I open it but cant seem to get it to work.
I have the folder I download unzipped and saved as C:\NVFlash
Not sure how to do step 2
2. Run this command to determine the partition no. of the recovery (SOS) partition--usually, it is 9: Open a CMD.exe window, then change into the directory containing both the nvflash.exe and the bootloader.bin files. Then run:
You have been very helpful thanks again.
Rochey21 said:
Do I leave this folder on my laptop or put in on the tablet.
Click to expand...
Click to collapse
It's meant to be used on an x86 system (desktop, laptop, ...) running Windows or Linux. You can't run .dll and .exe files--Intel binaries--on an ARM tablet, right?
Could you please explain a bit more how to use the command window. I open it but cant seem to get it to work.
I have the folder I download unzipped and saved as C:\NVFlash
Click to expand...
Click to collapse
Change to the directory containing the nvflash executable and bootloader.bin like this (only type in the stuff in bold):
Code:
[I]C:\SOME\PATH[/I]> [B]cd c:\NVFlash[/B] [I]Change to NVFlash directory[/I]
C:\NVFlash> [I] Note the changed prompt[/I] [I]now[/I]
After that, substitute C:\NVFlash\part9.img instead of C:\SOME\PATH\recovery.img in the given command line.
I understand I cant run the files on the tablet, just meant do I need to transfer any files to the tablet during the process or is it all done through the command window.
I have attached the command window. I typed cd c:\NVFlash and the directory changed to NVFlash.
Not sure how I substitute img 9 then?
EDIT* I got the p.txt file. How would I read this file?
Just looking to get CWM running so I can update to a new custom rom.
Rochey21 said:
I understand I cant run the files on the tablet, just meant do I need to transfer any files to the tablet during the process or is it all done through the command window.
Click to expand...
Click to collapse
No need to transfer anything.
EDIT* I got the p.txt file. How would I read this file?
Click to expand...
Click to collapse
Any editor will read that file. Just double-click on the filename.
Just looking to get CWM running so I can update to a new custom rom.
Click to expand...
Click to collapse
Which one?
rajeevvp said:
No need to transfer anything.
Any editor will read that file. Just double-click on the filename.
Which one?
Click to expand...
Click to collapse
JellyBean Smoother Seems to be good?
Sorry which editor would that be? I opened it in wordpad/notepad and it is all just symbols.
Would something like Hex editor read it?
Rochey21 said:
JellyBean Slim Seems to be good?
Click to expand...
Click to collapse
In that case, shut off the tablet; put it back into APX mode using Power and Vol [-]; then double-click the NVFlash_gTablet.bat batch file. It will do all the prep steps (including installing CWM) needed for a Jellybean ROM install. After the tablet boots into CWM, transfer the ROM install zip file onto the tablet and follow the instructions given in the ROM's first post to install the ROM.
Sorry which editor would that be? I hope it in wordpad/notepad and it is all just symbols.
Click to expand...
Click to collapse
Ah! You've got one of the screwey nvflash executables which produce a binary output. Ignore all this, then.
Ok So do I ignore everything or click the NVFlash_gTablet.bat file?
Rochey21 said:
click the NVFlash_gTablet.bat file?
Click to expand...
Click to collapse
Yes.
(Turn the tablet off, then put it back into APX mode again, though. Otherwise, the batch file will error out.)
rajeevvp said:
Yes.
(Turn the tablet off, then put it back into APX mode again, though. Otherwise, the batch file will error out.)
Click to expand...
Click to collapse
Finally :victory:
Thanks very much for all your help.
I have Smoother Bean installed, doesn't seem to be running correctly but il figure that out myself.
Thanks again.