Sorry if this is well known, but it took me a lot of searching to find an answer and even then it wasn't that obvious. I will explain the problem as simple as i can in case you are having it too...
At some point while running CM9/10 I started getting soft reboots everytime I plugged my phone in to transfer files. I would click the button for USB mass storage device / it would spin and then just reboot. I would see the drives on my PC but they would be light gray and not do anything when i clicked on them. This occured on a XP box a Win7 and Linux. I did the fix permissions, clear this clear that etc...
In the end it turned out that it was my Theme that was causing the issue. (Maybe someone smarter than I could chime in with why and then I can pass it on to the developer...)
I found a few posts (on and off XDA) where others were having the issue, but in one response someone with another phone/rom traced it down to their theme, removed the theme and then it worked.
In my case I can either freeze it with TB, or it seems like it's ok just switching back to system / mounting it / and then going back to the theme after.
I've seen a post for epinters CM10 build where someone referenced the problem but it cleared up on its own. I was farting around with this for about 6 hours and ready to go back to GB or ICS if needed. So hopefully if your reading this and have the same issue it will save you some frustration...
Again the Fix may be as simple as uninstalling/freezing/switching your theme to get it to work...
A huge Thanks to all the Devs that make my phone what it is... I'm an Inf/Ops guy and am always amazed how you guys can take something from concept to creation and make it work. But I could never do what you do 24/7...
Maybe a bad .9.png that is only displayed when the USB is in mass storage mode? I just went to try this for myself using epinter's 0907 build of cm10 with no extra themes installed, and it rebooted too. I could swear I just did this a few days ago with no problems. I tried again after the reboot, and it worked fine. So, I tried a third time and it rebooted again. Maybe it isn't theme related at all.
I have the same problem as you but I don't understand the solution. Can you explain it?. My rom is JellyTime R28.
Sorry for my English. Thanks
lauterm said:
Maybe a bad .9.png that is only displayed when the USB is in mass storage mode? I just went to try this for myself using epinter's 0907 build of cm10 with no extra themes installed, and it rebooted too. I could swear I just did this a few days ago with no problems. I tried again after the reboot, and it worked fine. So, I tried a third time and it rebooted again. Maybe it isn't theme related at all.
Click to expand...
Click to collapse
jsis83 said:
I have the same problem as you but I don't understand the solution. Can you explain it?. My rom is JellyTime R28.
Sorry for my English. Thanks
Click to expand...
Click to collapse
The draw9patch files that have the .9 in the end of the file name before the extension files typically wouldn't be the case. From experience, I ran into this issue multiple times when copying or editing those files manually using photoshop. If the .9 files are corrupt and do not meet the requirements set forth by the .9 specs for graphic files, the compile will fail error out and fail to complete the build instead of finishing with corrupt .9 files. It throws other weird errors when it picks up the .9 corrupt files and if you go up the terminal to see the chain of events during compiling, you'll see there was a malformed error thrown by improper alpha channels that are corrupt on the whatever file.
This USB to PC reboot error though is another annoying pain the ass error I ran into after compiling sources with changes I added to the XML code. It stems from some sort of improper code written somewhere. It's not critically an error that causes terminal errors but rather some sort of misuse of the layout coding on where things should be on the display.
I had this problem for a while when I played around with the status bar icon realigning to left or center of the screen. Although the code compiled and the build was successful and functional, this happened every single time I would connect the USB to the phone, once it reboots, I still had to disconnect and reconnect the USB cable into phone for it to properly recognize the memory card access. After taking a look at my changes to the structure of <LinearLayout children's parameters, I had some overlapping code that called for functions that weren't allowed from rules set by the parent. A little cleanup and correction, the error is completely gone and I have my end result shown in the snapshot of my status bar.
{
"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"
}
I cannot say 100% this is the root cause but from experience this is how I was able to create the error and then correct it to get things normally functional like they were before the error.
Out of curiosity what rom/theme are you using? Looks clean and smooth.
It's a project I've been working on daily for the last 2 months, it's a CM7 based rom I codenamed "Insight-7". Everything compiled from the CM7.2 source code and I made all tweaks, adjustments and changes to the source code directly before compiling the entire build together. I themed the entire rom with a blue\black color scheme and flashed hundreds of test builds to make sure everything works correctly in every scenario possible while maintaining a lasting battery throughout the day to be able to do anything on the phone during the day without worrying about switching batteries every few hours or looking for outlets to recharge at. I prefer to release a working & functional built rom instead of having it be alpha or beta with bugs and just provide updates to fix the bugs for months after initial release. It's reaching release to public status after I can correct a few final things so I can stress test the rom for proper functionality of each component that's worthy enough of releasing for others to use without issues.
same issue
Related
This is a Bus Guide application for SBS buses in Singapore. This app allows u to find out the bus routes in Singapore, as well as the time of arrival for that bus at a particular bus stop. The latest version now is location aware and will pull the nearest 8 bus stops from your current location and you can choose to see what time the bus will arrive at any of those stops.
latest version and updates can be found here.. http://myonline-site.com/busguide
Query Function
{
"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"
}
Search Function
Info Function
Nearby Function
Favourite Function
Feedbacks most welcomed
Any chance you could gather data for Perth Australia and make that? I'd put in money
Installed v4.2, the only error I get is "Invalid Bus Stop Number". The rest of the functions work.
I've checked the log, it mentioned
Please install ‘NETCFv35.Messages.EN.wm.cab’ for Windows Mobile 5.0 and above or ‘NETCFv35.Messages.EN.cab’ for other platforms. Restart the application to see the message.
Click to expand...
Click to collapse
So, I copied NETCFv35.Messages.EN.wm.cab from "C:\Program Files (x86)\Microsoft.NET\SDK\CompactFramework\v3.5\WindowsCE\Diagnostics\". But still fail to solve the problem.
Just wonder whether is there any other dependency programs for this?
stiucsib86 said:
Installed v4.2, the only error I get is "Invalid Bus Stop Number". The rest of the functions work.
I've checked the log, it mentioned
So, I copied NETCFv35.Messages.EN.wm.cab from "C:\Program Files (x86)\Microsoft.NET\SDK\CompactFramework\v3.5\WindowsCE\Diagnostics\". But still fail to solve the problem.
Just wonder whether is there any other dependency programs for this?
Click to expand...
Click to collapse
great UI only problem is getting the above error also.
stiucsib86 said:
Installed v4.2, the only error I get is "Invalid Bus Stop Number". The rest of the functions work.
I've checked the log, it mentioned
So, I copied NETCFv35.Messages.EN.wm.cab from "C:\Program Files (x86)\Microsoft.NET\SDK\CompactFramework\v3.5\WindowsCE\Diagnostics\". But still fail to solve the problem.
Just wonder whether is there any other dependency programs for this?
Click to expand...
Click to collapse
i also have this problem and i am currently running on WM 6.5.Pls help!!!tks.
hmm.. bro, any chance to add in updates for SMRT's buses timings too?
kks24 said:
i also have this problem and i am currently running on WM 6.5.Pls help!!!tks.
Click to expand...
Click to collapse
i also gt tis prob...
issit related to smrt bustop all those?
Presto80 said:
i also gt tis prob...
issit related to smrt bustop all those?
Click to expand...
Click to collapse
not related ... the invalid bus stop could be a netcf issue. i had that error in the previous rom tested but on the new rom it's working fine. only request now would be to have the smrt buses incorporated.
Many thanks for the app! Finally something to replace the web version of sbstransit...
Seems like quite a lot of people having issues with the new version.. Not really sure why it works for some and not for others.
Since it has no dependency on the new cf version other than to fix a few minor bugs, will try to revert back to the older dot net cf 2.0 in the next release. Next release will also have SMRT bus timing included but since my laptop is in the repair centre.. might take a while
I had the problem initially. I noticed that it only happens when my wifi or 3g connection is weak. Odd I know but so long my wifi or 3g connection is connected and stable before I switch on the program, the error will not occur.
New version available
http://www.myonline-site.com/busguide/
* Reverted back to use Compact Framework 2.0 (solve compatibility issues with some devices)
* Reduce the file size by about 80% (from 3000kb to 630kb)
* Added functionality to arrange and edit favourite list
* Added support for SMRT busses (limited to the 200+ stops where SMRT timing is available)
* Minor UI changes
* Google Static map size changed to 640 x 640 (the max allowed by Google)
* Files are provided as a Cab format and allow you to choose between storage card or device installation
Downloading now.. Thanks for your hardwork..
Good Work but no arrival status of bus..
Installed but cannot see the bus arrival status. Otherwise the apps is fabulous and 100% useful. For searches I generally use Mapking provided by SLA..but for IRIS searches I have to use opera and go to sbstransit site to get the bus status...this apps seems useful..Will try again....
slips while providing the status
only fewer times i can get the status..i believe better if you create two version of cabs..one for 2.5 and one for 3.5...
hmm kinda unable to get most of the smrt buses timing
Seems to have problem with the latest version of Singapore Bus Guide.
After installing it when searching for nearby bus-stops it was successful but when i choose the stop to view the individual bus timing i am not able to view it and an error msg was shown.
Tried uninstalling and installing it still have the same problem.
Any bros got this problem ???
hi i would like to ask is anyone had problem using the app? suddenly i was not able to check the bus timing ... BTW not app problem if i m not wrong
this will be my last cm7 build. from now on i will only be working on updates and the soon to be miui sense.
{
"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"
}
v1:
initial release
v1 link:
http://www.multiupload.com/098E03PJAN
reserved... mwhahahaha!!!!!!!!!!!!!!!!!!
Looks nice.
Still uploading???? Its taking ages Chef. thank you for your hard work
When to release?
Thanks! Works fine for me
Nice thx!
Sent from my HTC HD2 using xda premium
sadly none! Of your roms have worked for me! None! Tried booting from magldr and stuck on green htc screen forever despite of replacing rootfs after renaming it by deleting sdmagdr also replaced startup txt. Very sad cause i could never use any of ur roms and could you tell us what special features this rom has besides cm7 theming? Thnx
Fantastic!
Hi Isaiah12345
I have to say, this is a great ROM thanks. Im just booting from SD direct.
Been using it since you have uploaded it, and i must say, its great!
I had the Motoblur theme on my device aswell, but could not replicate the widgets
Your widget set is awesome, and looks exactly like the Atrix.
Speed is good, functionality great!
Thanks!!!!!
The Facebook widget is awesome!!!!!!!!
This is Awesome!! but for some reason the Market Force Closes everytime.. is there a fix?
Although its a great build, it's just not to my liking. I don't like the fact that everytime I.plug my phone into my ps3 it freezes my system and the phone rebooted with no USB support and non working leds
I think its the aca kernel
very nice rom , the first time i have 2.3.5 android version with such good battery life , thanks ...
there is only one annoying thing related to the copy-paste operation via usb cable , when i connect the phone to the pc and try to copy anything to the card , it shows that every thing is ok , and the files i need are copied , but when i open the file manager in the phone i find nothing , as if i didn't copy them .....
any idea ?
Copy files from PC to SD
ghassan haddad said:
very nice rom , the first time i have 2.3.5 android version with such good battery life , thanks ...
there is only one annoying thing related to the copy-paste operation via usb cable , when i connect the phone to the pc and try to copy anything to the card , it shows that every thing is ok , and the files i need are copied , but when i open the file manager in the phone i find nothing , as if i didn't copy them .....
any idea ?
Click to expand...
Click to collapse
Use the "Droid Explorer"
MAGLDR Friendly??
I want to try your ROM, but want to make sure first that it will boot with MAGLDR, I currently don't have Windows installed on my HD2..
hey been using ur rom, its fast and FC free(like most of ur roms ) but i have two issues:
1. gtalk doesnt work(cant sign in, it times out)
2. i cant get the bottom soft keys like the ones displayed on ur screen shot
keep up the good work man, i come online everyday in hope to see ur new rom (i dont like sense much, its too laggy and seems like an injustice to the HD2, the phone with many faces)
thanks
I'm sorry for all the delay with my builds, but i currently don't have an hd2. All of my roms will get an update as soon as i get a new one which will be within the week. And with a little luck i hope to be able to update winbuntu. Thanks for all your understanding.
For those of you that have greatly enjoyed my roms and my themes...
I unfortunately still don't have an hd2, but i will finally give you all a reason for that. I am in the process of making my own tablet and i had to sell my hd2 for money for said project. It has been a very long and grueling project, but hopefully it should be done within two months or so. I won't be giving any specs just yet, but keep a heads up for it and know that as soon as it is done i will be selling them and continuing my hd2 development with cyanogenmod. If my timing is right i will be working with cyanogenmod 9 stable release. Thank you all for your understanding and see you soon.
./\____/\
( =' + '= ) meow...
(,,)(,,)
p.s. this is indeed a very expensive project and it will help the community so if you have anything please make a small donation. I will only accept up to ten dollars. Any more is completely unnecessary.
I just reset my touchpad. (doctor + on device data wipe). My touchpad used to 14 gb before this now it shows 12gb. Any suggestions?
did you install touchdroid android, or modify the partitions in any way?
also, check your installed apps/preware veifry app space usage
I tried that chroid ipk and thats it thats why I doctered my device because I wouldent let me use uberkernel anymore.
curious...do you know how to use novaterm?
No idea man...
blerg...the big problem i have with webOS doctor is that it doesnt restore the partition table...it doesnt even touch it...so im thinking that either something modified your partition, or you can try to reinstall 3.0.2 again...
if you knew how to use novaterm, we could check the partition tables to see if theyre valid, but if you dont have the sdk/pdk set up, its not worth it to do it if you dont know how to use it
Is there a toutorial I can follow that can help redo my partitons?
i TOTALLY do not recommended doing that! As far as I know, that is the only surefire method to bricking your touchpad if you miss a single character on the command line.
Id say google it, but you might be better off taking the 2gb hit and wait for some partition guides to come available. Most of the advanced nova stuff is on webosinternals.com and the palm SDK site, so you cam start your research there.
Also ask some other 16gb users who can use nova to post the size/locations of their partitions, that way you have a reference point
Sent from my HTC Sensation Z710e using XDA App
Thanks man... ill try that do you think CM7 will rest the partitions.
UnderZone7 said:
Thanks man... ill try that do you think CM7 will rest the partitions.
Click to expand...
Click to collapse
highly, unlikely, if anything you will end up with LESS spaace on your webOS partition because CM will need to reallocate partition space for its own use
My Touchpad shows only 12,6 gb too, but it've been that way all along. Other strange thing was that i wasn't able to update from 3.0 to 3.0.2 by OTA, it just showed me "your device is up to date", had to use Doctor. Hope that all those things are just a software hickup, not a damn hardware malfunction.
Unrealwolf said:
My Touchpad shows only 12,6 gb too, but it've been that way all along. Other strange thing was that i wasn't able to update from 3.0 to 3.0.2 by OTA, it just showed me "your device is up to date", had to use Doctor. Hope that all those things are just a software hickup, not a damn hardware malfunction.
Click to expand...
Click to collapse
wow, that is strange... i hope it isnt a hardware defect either...unless webOS 3.x.x takes up 2gb
heres how you can check (make sure you have palm SDK, novaterm and a calculator handy )
-connect TP via usb straight to your pc (no usb hubs!)
-on the TP, either hit cancel or do nothing, do not enter usb mode! you dont need dev mode either.
-load up novaterm
-hit connect
-type "df -h" (without the quotes)
-add up the size totals, and see whatcha got!
if possible, please post results, im curious to see if its hardware or software
I have the same issue.. I will try it out once I get home later today
Solidus_n313 said:
-connect TP via usb straight to your pc (no usb hubs!)
-on the TP, either hit cancel or do nothing, do not enter usb mode! you dont need dev mode either.
-load up novaterm
-hit connect
-type "df -h" (without the quotes)
-add up the size totals, and see whatcha got!
if possible, please post results, im curious to see if its hardware or software
Click to expand...
Click to collapse
I've got some problems with novaterm - it shows an error (which could be ignored) after every keypress, it doesn't scroll proper, ant it doesn't allow me to copy/paste. I've made a screensot of the beginning of that long output thing, here
http://dl.dropbox.com/u/21304732/unt.png
BTW. i've found that it's quite common: here is the thread of a guy who has 12.6 gigs too http://forums.precentral.net/hp-touchpad/298469-where-my-16gb.html
I also had 12.6 GB free space when I received my TP. But I was able to update it to 3.0.2 via OTA without any problems. Though, the free space was still 12.6 GB after the update.
I have a 32gb only showing 23.5 gb available. It seems to lose 2gb each time I do webos doctor. Hopefully there's someway to reset its partitioning.
I'm only showing 12 Gb as well.
Here's what I show in Novaterm:
{
"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"
}
theniel said:
I have a 32gb only showing 23.5 gb available. It seems to lose 2gb each time I do webos doctor. Hopefully there's someway to reset its partitioning.
Click to expand...
Click to collapse
I would hope that is not the case....can anyone verify this? Would make WebOS doctor a pretty crappy restore tool.
Originally Posted by pixut
I have graphic issue with the ICS leak. Everything is fine and smooth at first. However, I can't use the phone if I turn off the screen and turn it on again because the screen looks like a lost-signal TV. Something likes that . My installation procedures: motofastboot full wipe then flash boot, system and vendor.img. I also try CMW zip of upndwn4par, epinter and lokifish but none of these work.
My tegrapart is 1100:100:800. AT&T atrix.
By the way, I have SOD with whatever rom I use after unlocking bootloader. Does it relate to graphic issue above?
{
"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"
}
I have the same problem. Help solve the problem ....
update:
video1
video2
video3
video4
file quiz
| MB860.ATT.en.US | ReservedOdm 10000000000010001000300004000 |tegrapart=mbr:1100:100:800 |
xxcombat said:
Originally Posted by pixut
I have graphic issue with the ICS leak. Everything is fine and smooth at first. However, I can't use the phone if I turn off the screen and turn it on again because the screen looks like a lost-signal TV. Something likes that . My installation procedures: motofastboot full wipe then flash boot, system and vendor.img. I also try CMW zip of upndwn4par, epinter and lokifish but none of these work.
My tegrapart is 1100:100:800. AT&T atrix.
By the way, I have SOD with whatever rom I use after unlocking bootloader. Does it relate to graphic issue above?
I have the same problem. Help solve the problem ....
| MB860.ATT.en.US | ReservedOdm 10000000000010001000300004000 |tegrapart=mbr:1100:100:800 |
Click to expand...
Click to collapse
tegrapart=mbr:d00:100:800
you are not alone.
Guys, can you type here your full tegrapart line along with kpanic line too? I'd like to investigate more about this issue
ex: tegrapart=mbr:d00:100:800,kpanic:2100:400:800
ex2: tegrapart=mbr:1100:100:800,kpanic:2500:400:800
tegrapart=mbr:d00:100:800,kpanic:2100:400:800
[email protected] [email protected] [email protected] vmalloc=320M video=tegrafb console=null usbcore.old_scheme_first=1 tegraboot=sdmmc tegrapart=mbr:1100:100:800,kpanic:2500:400:800 security=tomoyo mot_prod=1 androidboot.serialno=TA20703..
upd
A small survey data from our forum (tegrаpart- graphic problem)
1100 all ok - 9 person
1100 graphic problem - 6 person
d00 all ok - 15 person
d00 graphic problem -1 person
I guess it's because we have displays from different manufacturers.
tegrapart=mbr:1100:100:800,kpanic:2500:400:800
international atrix. I don't have graphic issues apart for the camera that shows purple lines on the bottom...
Random reboots occur very often instead and they are really annoying
lightlord said:
Ok, i have the other tegra part but same issue. I go arround this by putting phone into dock or connect it to tv via hdmi and the screen magically
stabilizes. So what i do is:
When booted with the garbled screen i:
-conect to lapdock and open the lid,
-wait a few seconds, on laptop screen there is some out of phase webtop screen (on my bravia hdmi screen gets perfect at that moment)
-i close the lid on lapdock, the screen on phone digitizer reapears stabilized with unlock circle
-i unlock and disconect the phone and it works till next reboot. mileage may vary from 9 hrs to few minutes when connecting and disconnecting a tv via hdmi
Click to expand...
Click to collapse
anyone can confirm this?
So this could be an issue with webtop? :S
Should we do a depth-in debugging with logcat when putting the screen off?
try to remove all /system/lib/hw/sensors*
don't solve the problem, but I think something changed ...
jhonnyx said:
So this could be an issue with webtop? :S
Should we do a depth-in debugging with logcat when putting the screen off?
Click to expand...
Click to collapse
Can't be webtop or otherwise the "Somebody's" CM10 wouldn't have the same issue.
As far as the heat issues. Is everybody seeing this on the bottom near the speaker? If so, the radio and flash memory are in that area.
Got the graphic problem too. :\
tegrapart=mbr:1100:100:800
Could it be related to parts of the leak people have or haven't flashed? I flashed all .img files as outlined in the .bat other than motoboot and that was only due to an error. I noticed many instructions only suggested flashing the main .img files like system, preinstall, webtop and boot but there were several more. These may not be included in the .zip files created either.
Sent from my Thunderbolt using xda app-developers app
And did you have any problems?
Not one single problem related to the display glitches. I have had a mostly stable experience but I am also running wifi only without a simcard. I have had maybe a total of two reboots since the leak.
Edit:
I don't have a lap dock and have yet to try out my HDMI cable to my LCD. No other docks except for car dock.
Sent from my MB860 using xda app-developers app
This is what sucks to thing about. We have this probably relatively old build we use to try and get stuff working..there might be extremely later builds with everything working great just no leak for it.
someone tells me change the DPI from 240 to 242 . 6 people find it worked. i hope it may helps you
I notice in the OP there was no mention to flash the preinstall or recovery .img files. I believe these files have necessary functions on first boot. I wonder if it is an incomplete flash or something related to the radio or both?
Sent from my MB860 using xda app-developers app
xxiaoxinjiang said:
someone tells me change the DPI from 240 to 242 . 6 people find it worked. i hope it may helps you
Click to expand...
Click to collapse
more details...
did they have graphic problem?
upd
I changed 240 to 242 in build.prop - that did not work ((
JPBeard21 said:
Could it be related to parts of the leak people have or haven't flashed? I flashed all .img files as outlined in the .bat other than motoboot and that was only due to an error. I noticed many instructions only suggested flashing the main .img files like system, preinstall, webtop and boot but there were several more. These may not be included in the .zip files created either.
Sent from my Thunderbolt using xda app-developers app
Click to expand...
Click to collapse
Can you list the specific .img files you had installed? Or, let me try listing and can you confirm? lol.
boot.img, preinstall.img, radio.img, recovery.img, system.img, vendor.img
Thats what I see from another download I have called "olympus-userdebug-4.0.4-6.7.7_95-95-test-keys-ATT-US - 7.5.0.83.zip"
Seems like with CWM I shouldn't be installing recovery.img though, right?
Should I keep radio.img?
Background:
I'll admit, I've been messing around a bit too much with the software/hardware of my Nook Tablet without any real prior knowledge, so this came of little surprise when it eventually stopped working. Originally, I had Rooted my Nook Tablet to expand on its capabilities, but wasn't satisfied; therefore I attempted to run CyanogenMod 10.1 on the Nook Tablet, but I realized (a little too late) that the version of ClockWorkMod I was running was too old to handle Android 4.1/4.2 Jelly Bean, which got the Nook stuck in a bootloop. Additionally, in the process I'd messed up the partition tables and they are no longer intact at all. I then proceeded here, to the XDA Forums, to find a potential solution, and found one that pretty much worked all the way up until I was physically restoring the partitions; I had ADB into the Nook and used a few partition images. After restoring the most important ones I went around to fix the others lesser ones, but the terminal on Linux said I'd run out of space.
After that the Nook had been shutdown with out fully restoring the partitions (probably leaving them corrupt, for all I know) and this is the end result:
1.) Nook cannot boot to any sort of recovery or operating system.
2.) Nook will not recognize and boot to an SD card upon start-up.
3.) Nook doesn't hold charge even though battery is tested and working.
4.) When Nook boots up, there is a large "N" logo and nothing else happens.
So the boot sequence is like this:
1.) Press power button; gives battery low/charge for 15 minutes error.
1.) Plug-in and charge for 15 minutes.
2.) Nook powers on and boots to "N" logo.
3.) Cannot do anything before/after.
Is there any way I can remedy this? Preferably I would like to restore the Nook Tablet to full working condition and restore the operating system to a stock ROM.
Note: I have a Nook Tablet 16 GB.
{
"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"
}
Go to the Nook Tablet development section. There are tons of guides to unbricking your tab.
The Ubuntu total wipe and reflash method
Unbrick Nook Tablet on Windows Vista/7
I'm pretty sure there are many other methods, but those 2 are the best ones I found so far (with a lot of "thanks" feedback from users).
About the battery level: use any regular microusb charger for a cellphone. Let it charge overnight, then proceed to unbricking.
sagirfahmid3 said:
Go to the Nook Tablet development section. There are tons of guides to unbricking your tab.
The Ubuntu total wipe and reflash method
Unbrick Nook Tablet on Windows Vista/7
I'm pretty sure there are many other methods, but those 2 are the best ones I found so far (with a lot of "thanks" feedback from users).
About the battery level: use any regular microusb charger for a cellphone. Let it charge overnight, then proceed to unbricking.
Click to expand...
Click to collapse
I should've added the "Bro, Do You Even Read?" to this response too; I should allude to you the fact that I have tried several methods from the XDA Forums (as I mentioned previously), including the total wipe method on Ubuntu as well as Windows (my Macs are undergoing hardware/software upgrades right now, and they're probably too old to be any use for me anyway). Additionally, while the results/symptoms are similar to other cases I hear here and other places on the web, there seems to be some uniqieness about it, which leads me to believe that the device is more than "just bricked".
Tell you what, when I attempted to restore the partition tables initially, it got messed up leading to the device's demise. The internal EMMC as well as any sort of recovery and bootloader has been completely obliterated from existance. The device can no longer physically recognize the micro SD Card Slot, and half the time it won't even boot on command (I have to wait until it feels like doing so when charging).
Secondly, I have tried other USB cables and adapters and I've gotten the same results, I even left it at a B&N store to charge during a one week period and the same results occur; doesn't keep the charge. The battery was swapped with another device and was proven to be working as it charged in the other device just fine.
I think I should also mention that the Windows-restore Method that you linked me to mentioned the following:
"Update: If you have followed every steps from above instruction and still getting "please contact nook support" then you have "erased" factory partition table which means that now your device doesn't have any "build history" associated with it, like serial number, build info and so on. That means that factory ROM will not be able to run without getting that information from your device so your best choice is to call BN or go to BN and get a warranty or replacement service."
And as I said in the initial post, the partition tables are no longer intact, in fact, they no longer exist at all. And when I did bring it to Barnes & Noble, they were of no help whatsoever in my two local stores, so . . .
I guess you're SOL then...
(I always make sure to create a backup of the /rom partition before doing any major mods. That's where the serial number and wi-fi mac address are stored).
Try and see if this works http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/