When I try to reinstall the firmware it will not work. I get a message update failed: (1). This is done in the recovery section. I have put the latest firmware in, but nothing happens other then the error message. When I turn on the Archos it just goes straight to the Archos A70S Recovery screen. I have totally reformatted the device several times. Any thoughts on this board? Thanks.
Aaron
Try to format the device and then install the firmware, also, make sure to have the right firmware so the archos stock .aos file and not the SDE firmware .aos file
have you tried redownloading the archos firmware again? maybe the download got corrupted?
Also try running the repair tools under recovery: specifically Check Disk?
do you have a (1) at the end of the aos file? "sdqsqdfkqsdomij(1).aos" like Firefox do, i had the same error like that
Thanks...but I think I have tried it all...no luck
Try using a different browser, like IE to download it.
I've got the same thing going on. Was trying to re-partition the app space and something didn't work for the 4th time. So I removed Android and the SDE and now I can't get it to boot. My problem is that I was running windows, not sure what you were using, and I changed the recovery location's format. So every time I go to load the file the archos will format the partition then windows says it will not read and formats the partition... I move the file and try to start the reload only to fail.
I'm going to run ADB hopefully tomorrow. I hardly know what I'm doing, but don't really care if I break it! Just playing around but if anyone has any ideas let me know!
If you removed sde and android, there is nothing to boot from.
You then have to go into the recovery, format the device from there and then restore the orginal Android by transfering the aos file from arcos.
Yeah, I might have done that 10 times. That is when the archos reformats itself to something and then windows can't read the drive.
After you have transfered the AOS File to the device and it installs the Archos Android
it reformats the device to something?
I think that the archos is formatting to ext3 but windows can't read it, so windows then formats to whatever and I move the file, then hit ok on archos and you get failed message.
I know that AOS files work because I have already used them once.
If any of you guys give up on trying to get life into your bricked gen8 devices, then shoot me a message... I might be interested in buying the device from you.
Have you tried tried to fully charge it before installing? I had that same problem and it got fixed by fully charging the device first.
Full charge and plugged in as we speak.
You now have 133 posts on xda and still are not able to post a complete detailed description of what you are doing and what is happening?
How should we help?
My suggestion if you get an Error, tell us what error exactly, as my crystal ball is on repair atm.
Ha! 393 posts and your only kind of a ****? Thanks!
All kidding aside It's not easy to describe whats going on, and I wasn't trying to hijack this thread but I think the original poster is way gone. I was only trying to say I had the same problem and was going to try a few things to get it working again, but this was only yesterday and I have not had luck. I never really even asked for help but appreciate everyones input.
So... Let me start again!
Archos 101.
Long ago I had Urik Droid 1.0 installed but it had since been removed. Before I messed everything up i had the latest Archos update and rooted. I was trying to create a large partition for apps and had just edited the init.rc and rebooted. Somewhere here I messed up! Boot loops start and I'm into recovery.
Recovery shows everything normal, but I'm unable to update archos via AOS file. So I totally reformat and remove SDE in an attempt to just start fresh. This is not the case and I figured it wouldn't be.
As I described before, using windows, in archos recovery this is what is displayed.
Archos A101IT Recovery
Would you like to recover system?
NO
REBOOT
UPDATE FIRMWARE
REPAIR SYSTEM
FORMAT SYSTEM
If you select updated firmware the archos will reformat to ext3. It then says USB connection: Press OK to disconnect. Windows then says that it is unable to use the disk and asks to re-format. I did, because I don't think I can do anything else, moved the AOS file over and hit ok. Update failed (1).
So today I installed linux in an attempt to move ext3 to ext3. I did get the file transfered and my archos even said plug into dc power. I did and waited... Update Failed (206). Not sure what this one is!
And that's really all I know. I can't even get the last thing I described to come up again. But I have all week on vacation.
And lastly I would like to thank you for the help
And I just got the AOS to install! Formated repair to Vfat, used repair option and moved AOS into archos. For whatever reason this time it worked. Rebooted and android just started up. Don't know if everything works yet but we will see!
Funny, you do the mistake and call others names.
fzelle said:
You now have 133 posts on xda and still are not able to post a complete detailed description of what you are doing and what is happening?
How should we help?
My suggestion if you get an Error, tell us what error exactly, as my crystal ball is on repair atm.
Click to expand...
Click to collapse
Let me make this clear...
I was kidding. Take a deep breath, relax and please try to help someone else if that is what you are on here to do.
I'm pretty sure what you said to me was worst then my little joke. It was hardly clever and I'm ok with it as it did make me laugh a little.
I didn't ask for your help.
I didn't need your help
You didn't help.
And I'm ok with it even if you are not.
I'm going fishing now. Good day everyone.
No, it was exactly what you needed, as before my message you didn't tell us what was happening on your side.
Please read what you have posted before and check yourself if you would be able to get any sence from that.
It is funny how some people handle kritik.
Related
Hi anyone and everyone,
So let me start by saying I am really in need of help two months ago i had a flawless CM7 Nook Tablet 16GB that worked like a dream and now i have a useless brick and im about to through it away the problem i have can be viewed here............ http://www.youtube.com/watch?v=0BAZ...&playnext=1&list=PL05B917C134DF82A7........It gets stuck on the white screen everytime i was able to boot into CWM with a bootable sd card and I have tried to flash many roms from there and yet every time i get stuck at white screen please help help help help!
WOW!!!!!!!!!!!!!!!!!
Thanks in advance to all that reply!
well for starters it would help if you could tell us how you came to be bricked in the first place. you say that you had a perfectly fine NT before, so what did you do to get to where you are now?
ShinnAsuka said:
well for starters it would help if you could tell us how you came to be bricked in the first place. you say that you had a perfectly fine NT before, so what did you do to get to where you are now?
Click to expand...
Click to collapse
I was editing my build prop and I made a mistake so it booted into cwm recovery and I think I might of partitioned my rom or something I really don't know what happens but I do know that everytime I go into cwm I get a bunch of errors and can't even mount it all fails I found my problem alot through these forums with no answer which is why I made the post
Clksk8 said:
I was editing my build prop and I made a mistake so it booted into cwm recovery and I think I might of partitioned my rom or something I really don't know what happens but I do know that everytime I go into cwm I get a bunch of errors and can't even mount it all fails I found my problem alot through these forums with no answer which is why I made the post
Click to expand...
Click to collapse
and as to where I am now......everytime I turn on my nook it gets stuck at the white screen with the cardboard box.....unless I use a bootable sd card which then I have tried to flash old roms new roms and I get nothing
Clksk8 said:
I was editing my build prop and I made a mistake so it booted into cwm recovery and I think I might of partitioned my rom or something I really don't know what happens but I do know that everytime I go into cwm I get a bunch of errors and can't even mount it all fails I found my problem alot through these forums with no answer which is why I made the post
Click to expand...
Click to collapse
Your partitions are : shot / corrupt / messed up. They "really" gotta be working okay . . . Will the near by B&N store put them back in good working order for you ?
Clksk8 said:
I was editing my build prop and I made a mistake so it booted into cwm recovery and I think I might of partitioned my rom or something I really don't know what happens but I do know that everytime I go into cwm I get a bunch of errors and can't even mount it all fails I found my problem alot through these forums with no answer which is why I made the post
Click to expand...
Click to collapse
With a bootable SD card are you able to.use ADB? If you are you might be able to push a normal build.prop to /system and be able to boot back into your rom. If not then like old fart said you may have messed up your partitions.
Sent from my Nook Tablet CM7 BETA using xda premium app
If my nook keeps loading to the white box which is part of cwm (right) won't B&N know iv rooted and most likely tell me in screwed if not I will gladly ask for there help
Thanks for the quick reply's......in not very familiar with adb
Clksk8 said:
If my nook keeps loading to the white box which is part of cwm (right) won't B&N know iv rooted and most likely tell me in screwed if not I will gladly ask for there help
Thanks for the quick reply's......in not very familiar with adb
Click to expand...
Click to collapse
assuming you have adb setup correctly the commands aren't too difficult. i believe the following should suffice. i only know windows commands so yeah..
open your start menu, type in cmd and then enter.
navigate to directory where you have adb installed. in my case it was -> cd C:/ntroot
then connect your NT to your computer, make sure usb debugging is enabled which it most likely is if you can get into cwm.
use adb devices, and there should a string of numbers which is your serial number. if you see it then that is a good sign.
then adb remount, which makes the file system writable.
next make sure you have the normal build.prop in that directory that you have adb installed in.
then do adb push build.prop /system
should be very quick, if all goes well you should be able to boot back into your rom. otherwise, your partitions are likely screwed up...
if your partitions are screwed up, there should be a couple of links in the android development section that tell you how to repartition so you can start anew.
good luck.
When I connect to adb I get 0000000000 as my serial does this make since can anyone point me to a link to re do partitions I will look around also
but it is just easier if some one can point me to the right area
Clksk8 said:
When I connect to adb I get 0000000000 as my serial does this make since can anyone point me to a link to re do partitions I will look around also
but it is just easier if some one can point me to the right area
Click to expand...
Click to collapse
that serial number is normal, you should really learn to use the search function provided by this forum but here are two that i found...
http://forum.xda-developers.com/showthread.php?t=1562130
http://forum.xda-developers.com/showthread.php?t=1605664
those two are assuming you screwed up your partitions.
Clksk8 said:
When I connect to adb I get 0000000000 as my serial does this make since can anyone point me to a link to re do partitions I will look around also
but it is just easier if some one can point me to the right area
Click to expand...
Click to collapse
adb is hooked up correctly but when i put adb devices i get
0000000000 recovery instead of a serial number?
So I have bricked my Nook dozens of time but when I do I just download the acclaim_update.zip from one of these threads and go to a file in it.
Go to /META-INF/com/google/android/updater-script and then I just edit the first two lines. Edit both parts where it says "blaze" and change it to "acclaim". If you're on ubuntu then all you have to do is press saveand it will ask if you want to update the file (or something like that) and click yes. Then just make a CWM bootable sd card and flash that file Hope it helps!
I hope someone can help me. I have a 16gb nook tablet that I rooted using the method described here http://liliputing.com/2012/03/how-to-dual-boot-cyanogenmod-7-nook-tablet-os-with-a-microsd-card.html over a year ago and I've never had an issue until last weekend. My daughter was playing a game and the nook started acting up. The touch screen became unresponsive and the screen started to flash. I let the Nook charge overnight and when I turned it on the next day the screen became stuck at the white Nook welcome screen. After 20 minutes I tried the holding down power and N button to see if I could get it to restart, but unfortunately that may have made it worse. Now my Nook won't start at all. I've read many many threads here on how to fix it, but I am not tech savvy in the slightest. The first thing I tried was Rays method http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/ but instead of getting the green checkmark I got the red X and the "nook is shutting down" message. I tried so many things that I cannot remember them all but I do know that one of the methods I tried I got this message.
E:Can’t mount / cache/recovery/command/
E:Can’t mount / cache/recovery/log/
E:Can’t open / cache/recovery/log/
E:Can’t mount / cache/recovery/last_log/
E:Can’t open / cache/recovery/last_log
After that I tried to use the method described here http://forum.xda-developers.com/showpost.php?p=24995518&postcount=1 and I did make the booktable cwm-sd and I went to lavero.burgos' thread to download the mmcblk files, but they weren't there.
Also I don't understand what adb is but I'm desperate, when I found the thread that explained it and tried to download the ADB + Fastboot + Drivers.zip that was in said thread (I'm sorry I can't remember which thread it was) the zip file didn't work.
I'm really sorry for posting yet another, "please help my nook is borked" thread but after all the reading I've done this past week the only thing I've become is very confused and frustrated. Thank you in advance to anyone who can help.
Notice on the link you posted
Ray Waldo; said:
If this procedure fails, try one of these:
Celtic has a possible solution on XDA here: http://forum.xda-developers.com/showthread.php?t=1513583
Succulent has more info on his Github page: https://github.com/succulent/acclaim_recovery_sdcard.
Click to expand...
Click to collapse
I can see how you got lost. There aren’t really any detailed instructions there.
I got the following zip from 2nd link
Flash the zip with CWM then try the bn_142_factory_recovery.zip SD card again and you should get a green checkmark this time.
udownwitopp said:
Notice on the link you posted
I can see how you got lost. There aren’t really any detailed instructions there.
I got the following zip from 2nd link
Flash the zip with CWM then try the bn_142_factory_recovery.zip SD card again and you should get a green checkmark this time.
Click to expand...
Click to collapse
Thank you for your reply. I will try this tonight and hopefully it will work.
Well I tried, and I hate asking but how exactly does someone add a zip file to an sd card after an image has been flashed to it? I've tried numerous times with sd cards of various sizes and I'm pretty sure I should have been able to do this with a 16gb card, but every time I try to drag and drop the flashstock zip over onto the card it says that there is no room available. Now I have been doing a lot of reading on here and I'm pretty sure I did not set the card up right, I did format it correctly with the sdformatter program, but I'm guessing I have to do something with the partitions on the card. I am not familiar with the programs because I've never had cause to use them before so I am not entirely sure how to do that. I tried following the directions found here http://forum.xda-developers.com/showpost.php?p=24995518&postcount=1 but I couldn't figure out how to enable boot, and lba flags. I realize that this has probably all been answered already, but again, there programs are so foreign to me that I'm not even sure what to look up first. Thank you again for any help that any one can give me.
evm22 said:
Well I tried, and I hate asking but how exactly does someone add a zip file to an sd card after an image has been flashed to it? I've tried numerous times with sd cards of various sizes and I'm pretty sure I should have been able to do this with a 16gb card, but every time I try to drag and drop the flashstock zip over onto the card it says that there is no room available. Now I have been doing a lot of reading on here and I'm pretty sure I did not set the card up right, I did format it correctly with the sdformatter program, but I'm guessing I have to do something with the partitions on the card. I am not familiar with the programs because I've never had cause to use them before so I am not entirely sure how to do that. I tried following the directions found here http://forum.xda-developers.com/showpost.php?p=24995518&postcount=1 but I couldn't figure out how to enable boot, and lba flags. I realize that this has probably all been answered already, but again, there programs are so foreign to me that I'm not even sure what to look up first. Thank you again for any help that any one can give me.
Click to expand...
Click to collapse
I'll try to explain the process for you. "The Red X" is a very common issue that people have with their devices. It's usually caused by digging into something that you don't fully understand. It's VERY important to understand the process of flashing custom ROMs because it could screw up your tablet, delete ROM partitions and such.
The first issue you need to attend to is "The Red X." First download the bn_142_factory_recovery.zip from the ray waldo site found here:
http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
Unzip the zip file and you should have a repart.img. Use win32diskimager to write this to an SD card. Once it's done writing, put the SD card in your device and it should boot from SD card and flash stock B&N 1.4.2 to your nook (if you have problems booting from SD card plug in the USB to your computer).
If you still get "The Red X" during this process please use the following method:
http://forum.xda-developers.com/showthread.php?t=1513583
If you have further problems please post or PM me. Once you have the issue fixed I HIGHLY recommend using the SDC version. It's a lot easier than the Internal Version and will prevent mistakes from happening.
Thank you for responding. I retried the method described on Ray's site, but sadly it's still a no go. I have downloaded the parted binary and I know how to get it onto the sd card, but what I don't know is how to ADB into my device. I'm not even sure I understand what ADB is.
evm22 said:
Thank you for responding. I retried the method described on Ray's site, but sadly it's still a no go. I have downloaded the parted binary and I know how to get it onto the sd card, but what I don't know is how to ADB into my device. I'm not even sure I understand what ADB is.
Click to expand...
Click to collapse
I'm not extremely knowledgeable with the ADB tool, but it's setting up your computer so you can write commands into your command prompt that will execute actions on your device. The link for setting it up is here:
http://forum.xda-developers.com/showthread.php?t=1474956
Once you get it set up just follow the rest of the directions in the parted binary post.
datallboy said:
I'm not extremely knowledgeable with the ADB tool, but it's setting up your computer so you can write commands into your command prompt that will execute actions on your device. The link for setting it up is here:
http://forum.xda-developers.com/showthread.php?t=1474956
Once you get it set up just follow the rest of the directions in the parted binary post.
Click to expand...
Click to collapse
Thank you for a link to the post with a working zip file for adb, I've downloaded and I've tried to follow the video, but unfortunately my laptop will not read my nook at all. Every time I connect it with a usb my device manager tries to find it, but it blinks, makes an error sound and I see
OMAP4330 under other devices. I' did a search for that error and came across this thread, but again the instructions call for installing an apk on the nook and since I can't get mine to turn on, it's a no go
evm22 said:
Thank you for a link to the post with a working zip file for adb, I've downloaded and I've tried to follow the video, but unfortunately my laptop will not read my nook at all. Every time I connect it with a usb my device manager tries to find it, but it blinks, makes an error sound and I see
OMAP4330 under other devices. I' did a search for that error and came across this thread, but again the instructions call for installing an apk on the nook and since I can't get mine to turn on, it's a no go
Click to expand...
Click to collapse
There is a possibility you could have deleted some partitions important to the nook then. Have you tried making an sdc version of cm10 to see if it could boot at all? You could see if you still have the device information to backup, recreate the partitions and flash back to stock.
Use this to make a bootable cm10 card:
http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
Just write the image file to an SD card and put it in your nook. It will boot into cm10. Once there go into your file manager and turn on root access. Go to your root drive/ROM/devconf to access all your device information. Make a backup of all them. There is a picture of my devices root drive. If you do not have the various partitions you will have to recreate them. There is a method on the Nook General Thread for doing this named "Unbrick Internal Partitions On NT" or something similar. You can use that recreate the internal partitions essential for your nook.
If you deleted the ROM partition with the Nook's product information you may be out of luck. The serial number and Mac address are the most essential, and can be found on your device hardware. The SN is under the SD slot (if readable) and Mac address is located inside your device. Not sure where I've never opened my nook to look, but probably on the WiFi chip.
Slight chance you may be able to fix it with this information and the rest of the device information you can use from a different nook since it doesn't have to do with internet and registration. There may be a way to fix that, but I don't know of any.
Best of luck. If you have problems just post a reply or send me an email.
I can get the Nook to turn on with the bootable cm10 card in it. I get the cyanoboot screen and see the boot menu, but honestly I don't know where to go from there. I think it's time for me to try and find someone who understands all of the programs involved in trying to fix this because I know I'm going to end up making things worse, if that's even possible. Thank you for trying to help me though. I do appreciate it
evm22 said:
I can get the Nook to turn on with the bootable cm10 card in it. I get the cyanoboot screen and see the boot menu, but honestly I don't know where to go from there. I think it's time for me to try and find someone who understands all of the programs involved in trying to fix this because I know I'm going to end up making things worse, if that's even possible. Thank you for trying to help me though. I do appreciate it
Click to expand...
Click to collapse
Hello! Did you ever figure out how to resurrect your Nook? I had trouble signing in Gmail and wanted to just unbrick and have the plain Nook again. I've been struggling getting the device to boot from the sd card with the repart imaged. I'm trying to get back to the ClockworkMod recovery screen but I can't at that moment. Someone suggested that I "flash" the B&N zip to the card but I'm trying to figure out how to do that.
Would love help!
Help, (PLEASE) I just "re-rooted) my Archos 101it tablet....I missed the setup screen where you fill out all the information on who you are (the developer)...now when I power it on, it gives me the Archos logo, then developers logo (angstrom) but then goes to very itsy bitsy lettering :
The angstrom distribution archos-gen-8
Angstrom 2009.X-stable archos-gen-8 tty1
archos-gen8 log in:
It does not respond to the touch screen. I am just sick inside...I had this tablet since mid-2011 and never did anything much with it, then after a download from Amazon, I started getting this popup saying that certain things could not open...lots of people had this error message, thus the reason for googling to this forum. I thank ANYONE in advance who can help me out...any way to get back to the screen to put in my user information and log in passcodes??? Jeanie
ps...then the new op version (android for Archos) that the person who wrote the tutorial on how to re-root is no longer available. (scream) I will need to know how to download the new op if I ever find it 8-(
I also had the same problem!!: After applying sde versions and trying numerous times to re-download firmware, I finally got my aos back!!! Seems I downloaded the newest version using Chrome and it wasn't copying right, so I followed another forum's advice and used Internet Explorer...it worked!!! Now after a week, I now have a "Like New) Archos 101it. What a learning experience!!!
P.S. I don't really know if it was Chrome or IE, seems I kept downloading different versions of the aos files with the same name...thus it was renaming them
firmware_archos_android_gen8. (2)aos
firmware_archos_android_gen8. (3)aos
well, before I copied the file over to the 101it drive, I took out the (2) or (3), then it worked!!!!
Try to delete SDE, reformat device and flash it again. Use chrulri's method to root it.
I've read LOTS of the threads here and maybe it's just beyond my brain to wrap around but I've also dl'd linked files in the hopes of fixing the one broken tablet.
Both tablets are Sony S and 111US. They have NEVER been rooted as I'm unfamiliar with the practice; though I can understand now why it's a nice thing to do from some of these posts/solutions.
I am borrowing this working tablet from a friend in the hopes I could find the answer by copying them via a File Explorer on the working tablet.. I can't send the broken one in to Sony as it was a gift and I don't have the receipt / proof of purchase; which the representative stressed that I needed in order for them to fix it.
Sometimes it's just stuck at the Sony Logo and one time when I tried to do a recovery from a file via SD card I got from condi or stifilz's 4shared.. well it was stuck at the shimmering boot animation; naturally I was SO excited but then it died down when I saw it was looped at that.
So my prime question is.. In putting a File Explorer on the WORKING tablet [not rooted and not updated, fresh from the box pretty much]: Is there a way to find the necessary files I need to fix the broken one?
Thanks!
kitka82 said:
I've read LOTS of the threads here and maybe it's just beyond my brain to wrap around but I've also dl'd linked files in the hopes of fixing the one broken tablet.
Both tablets are Sony S and 111US. They have NEVER been rooted as I'm unfamiliar with the practice; though I can understand now why it's a nice thing to do from some of these posts/solutions.
I am borrowing this working tablet from a friend in the hopes I could find the answer by copying them via a File Explorer on the working tablet.. I can't send the broken one in to Sony as it was a gift and I don't have the receipt / proof of purchase; which the representative stressed that I needed in order for them to fix it.
Sometimes it's just stuck at the Sony Logo and one time when I tried to do a recovery from a file via SD card I got from condi or stifilz's 4shared.. well it was stuck at the shimmering boot animation; naturally I was SO excited but then it died down when I saw it was looped at that.
So my prime question is.. In putting a File Explorer on the WORKING tablet [not rooted and not updated, fresh from the box pretty much]: Is there a way to find the necessary files I need to fix the broken one?
Thanks!
Click to expand...
Click to collapse
Best thing to do would be try to flash the lowest update you can such as signed-nbx03_001-ota-11000.001.zip or 0035 or 0042. These are all HoneyComb (oldskewl android). Then use ADB pull /tmp/recovery.log and post the file here, then we can see what is happening.
any questions see my FAQ on how to flash etc
Stifilz
stifilz said:
Best thing to do would be try to flash the lowest update you can such as signed-nbx03_001-ota-11000.001.zip or 0035 or 0042. These are all HoneyComb (oldskewl android). Then use ADB pull /tmp/recovery.log and post the file here, then we can see what is happening.
any questions see my FAQ on how to flash etc
Stifilz
Click to expand...
Click to collapse
I was afraid of that :/ Tried to download the files you directed me [I have bookmarked your 4shared]. They download fine however.. when I try to put them onto an SD card I get a popup to "Please insert the last disk of the Mult-Volume set and click OK to continue"
Trying to extract [for the heck of it] on computer.. I get that "The compressed (zipped) folder is empty."
Maybe the storms overhead here are making my net connection too funny to download anything atm.. I am not really sure. [Though I'm questioning why it's taking 30mins+ to download each file]
Despite those errors.. I pop the SD card into the tablet and not too surprised, the file doesn't show up TO load.
This happened with: signed-nbx03_001-ota-11000.zip and signed-nbx03_001-ota-0035.001.zip
I am still working on the others with the hope that I'll find success in ONE of them.
kitka82 said:
was afraid of that :/ Tried to download the files you directed me [I have bookmarked your 4shared]. They download fine however.. when I try to put them onto an SD card I get a popup to "Please insert the last disk of the Mult-Volume set and click OK to continue"
Trying to extract [for the heck of it] on computer.. I get that "The compressed (zipped) folder is empty."
Maybe the storms overhead here are making my net connection too funny to download anything atm.. I am not really sure. [Though I'm questioning why it's taking 30mins+ to download each file]
Despite those errors.. I pop the SD card into the tablet and not too surprised, the file doesn't show up TO load.
This happened with: signed-nbx03_001-ota-11000.zip and signed-nbx03_001-ota-0035.001.zip
I am still working on the others with the hope that I'll find success in ONE of them.
Click to expand...
Click to collapse
Use Fat32 sd I have same trouble with my exfat sd card
rooted lighting wildfire on unoffical j.b from benni
and sony XTS rooted stock j.b thanks djrbliss
kitka82 said:
I was afraid of that :/ Tried to download the files you directed me [I have bookmarked your 4shared]. They download fine however.. when I try to put them onto an SD card I get a popup to "Please insert the last disk of the Mult-Volume set and click OK to continue"
Trying to extract [for the heck of it] on computer.. I get that "The compressed (zipped) folder is empty."
Maybe the storms overhead here are making my net connection too funny to download anything atm.. I am not really sure. [Though I'm questioning why it's taking 30mins+ to download each file]
Despite those errors.. I pop the SD card into the tablet and not too surprised, the file doesn't show up TO load.
This happened with: signed-nbx03_001-ota-11000.zip and signed-nbx03_001-ota-0035.001.zip
I am still working on the others with the hope that I'll find success in ONE of them.
Click to expand...
Click to collapse
Yeh what dex9mm said. Try to format the disk and then put it onto sd card. Also the files are encrypted so you can't extract them. Are you copying straight to sdcard (laptop) or using a reader?
stifilz said:
Yeh what dex9mm said. Try to format the disk and then put it onto sd card. Also the files are encrypted so you can't extract them. Are you copying straight to sdcard (laptop) or using a reader?
Click to expand...
Click to collapse
Hmm.. didn't think of formating them first but okay shall do that.
When I click "download" it auto-downloads to my folder on Computer. From there I then "copy to" the card. Thanks guys!
UPDATE: Okay.. so I FINALLY got the tablet to see the ota 1100, 0035 and 0042 and got, to my unending frustration, the repetitive error:
"Erohibit update as a result of checking version or base sku
Installation aborted"
What's that mean exactly? and is there a way to fix that? Not sure if I need to find a decrypted zip and edit something in it now.. :/
Hello there,
I just registered on this forum to hopefully resolve my problem with the Kobo Arc tablet. I apologize if any similar issue regarding this was posted. So basically, my Uncle bought me a Kobo Arc tablet about 2 months ago and I know quite alot of things about it. Due to my stupidity I couldn't play a game I really wanted to and so I edited my build.prop to make my tablet compatible with the game. In build.prop I changed the product model to: "GT-I9100", product brand to: "Samsung" and product manufacture to: "unknown". After this I restarted my device. As I did, the kobo arc logo appeared and then a never ending start-up boot. I restarted my device many times but still couldn't get my device to fully on. I entered recovery mode by holding the up volume and power button together and tried to reset to factory, but my Kobo Arc just still won't go pass the never ending start-up screen. I even tried to connect it to my computer but it doesn't recognize it. I'm assuming it's bricked, is there any possible fix for this? if so I need to know asap.
Someone please help me, it would be so kind, and I'll appreciate it soo much.
Thanks in advance
SmootZ
Please, I'm in urgent need of help. I really want to go on my tablet again..
Any help to get my kobo arc to its original state and working properly again, I would be sooo grateful.
Do you have a nandroid backup? If so, restore it.
Otherwise, do you still have access to your SD card (probably using an adapter and connecting it to your PC)? Try using AROMA FM to edit build.prop to the original values.
If not, I'd suggest installing ADB (GIYF) and using that to edit build.prop.
For the last two solutions, you'll need to use the shell, and use a text editor such as nano, pico or vi (depending on what's available). BTW, how did you edit build.prop?
You can also flash back stock/any ROM. Restoring to factory settings doesn't restore build.prop AFAIK.
EDIT: Just noticed your PC doesn't recognize your phone. That rules out solution #3. Are you sure the required drivers installed on your PC?
Yes, I'm sure. But when I plug my tablet into my PC through my usb cable it makes a noise connoting its connected but it won't appear.
Could you possibly give me instructions on how to do a nandroid back-up or something that will get my device back with the following condition:
-My device not able to be recognized on my computer
EDIT: When I connect my device to my computer it charges, but it won't appear on my computer or anything, if this helps.
It's too late to make a nandroid backup now. Try using AROMA FM.
GermainZ said:
It's too late to make a nandroid backup now. Try using AROMA FM.
Click to expand...
Click to collapse
Could you possible give any instructions, I'm kinda new to this stuff.
SmootZ said:
Could you possible give any instructions, I'm kinda new to this stuff.
Click to expand...
Click to collapse
Click the link I posted.
Read the first few posts in full.
Ask about the specific part you don't understand.
I cannot even access my device apart from putting it in recovery mode since my device gets stuck at the start-up and loops, In addition I don't know how to access my sd card since my computer doesn't recognize my device as I said. Will this be a problem?and can I still do it?How do I access my sd card?
Sorry if this question seems stupid
Is your device still not detected in recovery mode?
To access your SD card directly from your PC you'll need a special reader/adapter.
Nope, it doesn't recognize it even in recovery mode. What is this "special" reader/adapter and where can I get it? Could you provide me a link or something?
Well, I'm out of ideas. Just Google "SD card adapter".
Actually my device does not offer any external memory card slot. Meaning There is no support for MicroSD or SD cards on my Kobo Arc.
What shall I do now?
Hey Germain or anyone else,
Is there any other possible way I can unbrick my tablet from this? Any solution would be grateful.
SmootZ said:
Hey Germain or anyone else,
Is there any other possible way I can unbrick my tablet from this? Any solution would be grateful.
Click to expand...
Click to collapse
I'm out of ideas you could try yourself. I'd try triple checking the drivers on your PC and see if you can get ADB to work.
Is sending your tablet to repair an option?
EDIT: Can't you update to the latest update using fastboot?
Hey.
First of all, messing with build.prop without backup wasn't the brightest idea in your life, but crap happens, like Forrest Gump used to say.
What is the exact model of your tablet? Kobo Arc? Kobo Arc 10 HD? Maybe Kobo released an update and you can update it directly by fastboot.
If not try to use Linux as it handles ADB much better than Windows, go to system and edit you build.prop back and wipe cache and dalvik cache. You need to have a working ADB to even think about reversing your changes.
Good luck.
Well thanks for the help.
Can I try taking this adb method without my device giving permissions for USB debugging? Since I haven't enabled this in my developer options as far as I know, in addition I cannot really check since my device is bricked but I'm 100% sure it's NOT enabled. Will this stop me from carrying an ADB method?