Motorola Atrix Screen Alignment issue! everything is shifted down! - Atrix 4G General

basically my motorola atrix doesn't work any more!!
the bit of the screen which is meant to be used to access the buttons bellow, work as though you are pressing the bottom of the visible screen!!
EVERYTHING is shifted down! if i want to press something, i have to press the area 1cm bellow the location!
I suspect it is cause by me formatting every single folder on the internal storage using clockwork recovery...
i have tried installing the original Rom using RSD, i have tried everything!!!
ANY HELP PLEASE?
the device is a piece of garbage now!
i saw that NO ONE else has reported this issue anywhere on the net!!
it can't be a hardware problem cause it was working before i formatted all of those folders! including the ones with the 3 character names... can't remember the names... but basically i formatted everything...

this is a common problem when you format / partition the internal memory. it screws up your PDS partition, which i hope you backed up. search a little more, there are lots of topics on this in the dev forum and I believe there MAY be a solution but i don't remember.

Just found a couple of threads...
I didn't back it up... does this mean that my Motorola atrix is practically worthless now? :s

Solution
http://forum.xda-developers.com/showthread.php?t=1131649
this apparently is supposed to work... will try it in a bit.
but still, you won't get the original mac address and bluetooth number and the rest...
:/ sad times... there must be someway to acquire the original values?!?!

benedict.s said:
http://forum.xda-developers.com/showthread.php?t=1131649
this apparently is supposed to work... will try it in a bit.
but still, you won't get the original mac address and bluetooth number and the rest...
:/ sad times... there must be someway to acquire the original values?!?!
Click to expand...
Click to collapse
i'm not sure there are, as those values were never meant to be cleared out.
can ask why you decided to format every folder in the memory?

dLo GSR said:
i'm not sure there are, as those values were never meant to be cleared out.
can ask why you decided to format every folder in the memory?
Click to expand...
Click to collapse
Well, if you look in the post i linked to, it is an image that i pushed into the partition...
it's working now at least!
I do have my mac address and IMEI, do you know how i can edit that image file to put my own values in it? i have no clue as to how the image can be edited.... :/
the reason i did that was because i had an HTC HD2 before. it originally comes with windows, and so when you installed Android, it had a horrible process... in that process, the MAGLDR and CWR as they were called, did not erase every folder in the phone's main memory... so i had gotten used to formatting them individually in that phone.. that's why i did it on the Atrix...
also, in the HD2 they were folders not partitions... so basically, i wasn't familiar with the exact core of Motorola android devices...
there must be a way to put in my own hardware details into the PDS image file?

benedict.s said:
Well, if you look in the post i linked to, it is an image that i pushed into the partition...
it's working now at least!
I do have my mac address and IMEI, do you know how i can edit that image file to put my own values in it? i have no clue as to how the image can be edited.... :/
the reason i did that was because i had an HTC HD2 before. it originally comes with windows, and so when you installed Android, it had a horrible process... in that process, the MAGLDR and CWR as they were called, did not erase every folder in the phone's main memory... so i had gotten used to formatting them individually in that phone.. that's why i did it on the Atrix...
also, in the HD2 they were folders not partitions... so basically, i wasn't familiar with the exact core of Motorola android devices...
there must be a way to put in my own hardware details into the PDS image file?
Click to expand...
Click to collapse
well, that's a little over my head, but i know some of the devs would be able to help you if you PMed them maybe.

coolios...
know anyone in particular?

Related

Extracting Seperate Files from a .img?

Ok, I'm sorry if this has been asked already (or is too obvious to have been asked), but I'm having problems with my phone after rooting it and I'd like to get it fixed if possible.
Basically, I rooted my phone and flashed Cyanogen. Everything works perfectly by the accelerometer and compass, which are both completely kaput it seems.
I've tried the method in Cyanogen's FAQ (the one involving restore and deleting two files), but one of the two sets of files that he asks to delete doesn't exist.
I've already tried performing multiple wipes and reinstalls of different roms (Including Cyanogen, JF's, even the original T-mobile mytouch rom) to no avail. I even flashed back to JF's 1.5 since some people said their problems started with the 1.51 update.
Now I'm back on Cyanogen since it's my favorite so far and it seems that the problem follows me no matter what.
Now it seems that my only choice as determined by this thread is to port in some files from JF's 1.42 and delete the Cyanogen version. I have no idea if this will work since these guys are obviously on G1's and I'm using a mytouch, but I figure it shouldn't hurt too much as long as I can still get to the recovery console if something goes crazy.
This is the method given:
reboot recovery
mount /system
rm /system/bin/akmd
mount /sdcard
cp /sdcard/jf1.43_akmd /system/bin/akmd
Click to expand...
Click to collapse
And I understand every single bit of it but the part where he copies the jf1.43 akmd to bin because I can't seem to get my hands on that single file.
Here's the actual question in case you want to skip all of that crap.
How do I extract the particular file that i need (akmd from JF's 1.42) from the .img file that I downloaded. Is there a particular method, or am I just downloading the incorrect package?
Furthermore, if you have any other possible solutions to my problem, I'd be glad to hear them. I'm pretty much shooting in the dark here since the first time I even looked into the system was yesterday when it was rooted.
Ok I found the perl script that I needed and ran it to extract the image. Now I'm looking for the file.
Oh my god. I'm an idiot. Opened the file in Linux and everything showed up. I think I might've had hidden files not showing.
Sorry for the stupid question, hah.
Edit: No luck. Am I really the only one who got a broken accelerometer from rooting?
Edit2: For someone who usually picks up on stuff like this quickly, I'm an idiot. For some reason every problem crossed my mind but the fact that I was using a rom that was not specifically made for the MyTouch. I flashed with the modded Cyanogen rom and the accelerometer works again.
You can delete this thread if you'd like mods.

[Q] Factory restore

I need a .img of the original rom, where can i find? Thanks
Aran83 said:
I need a .img of the original rom, where can i find? Thanks
Click to expand...
Click to collapse
You cant, every NST is unique and using an image from another NST will cause trouble for both you and the NST it came from.
Thanks, nook is bricked but I can read the main partition, which .img I install?
Sorry for my english.
Aran83 said:
Thanks, nook is bricked but I can read the main partition, which .img I install?
Sorry for my english.
Click to expand...
Click to collapse
There's no img you can install.
You can try booting n2T-Recovery (v0.2) from a SD card and see if that helps. (Do not write that image to your NST!)
If not, send me a PM and I'll try to help you out
Something else you can try:
1) Flash noogie.img to an sd card.
2) Hook up your nook to a pc via usb once it has booted, and you should see all the partitions exported there.
3) In one of those partitions (recovery maybe? I'm struggling to remember), there's a factory.zip, which you can then install using the "Install from zip" feature of clockwork mod.
If you go this route, you'll have to reflash your sd card with clockwork mod after you've extracted the factory.zip using noogie.
Seems like kind of a pain, but I just recovered my device using this.
Remains in the screen ROOTED FOREVER and i can't do anything
I think, for michaelwill's method, you need to have linux running. I suggest you to try ros87's suggestion.
if I use backup from nook of my friend?
Aran83 said:
if I use backup from nook of my friend?
Click to expand...
Click to collapse
That is not a good idea, since each NookTouch has a unique information to register. If you are thinking of full restore from your friend's image (1.8GB image), it will overwrite your unique information. In that case, you and your friend's devices cannot register to BnN (or just one device). People says the info is stored in /rom. If you want to know more, you need to dig more. Otherwise try factory reset suggested by ros.
herofmm said:
That is not a good idea, since each NookTouch has a unique information to register. If you are thinking of full restore from your friend's image (1.8GB image), it will overwrite your unique information. In that case, you and your friend's devices cannot register to BnN (or just one device). People says the info is stored in /rom. If you want to know more, you need to dig more. Otherwise try factory reset suggested by ros.
Click to expand...
Click to collapse
Correct!
Using a image from another NST is a very very bad idea!
There are a lot of stuff that's unique to your NST stored in /rom and in rombackup.zip on the Factory partition.
This includes:
Serial Number
Main Board Serial
Product ID
Manufacturing date
SHA hash of Private Key
Public Key in modulus form
WiFi Calibration file
Some unique binary file for your eInk screen
MAC Address
Battery Type
Duplicating the serial will make you or your friend unable to register with B&N
Duplicating / Faking the private/public key pair, will most likely make you unable to register with B&N (I'm currently testing this)
Duplicating a WiFi calibration can cause degraded WiFi performance
Duplicating that EPD vcom file (eInk screen).. well who knows
Duplicating the MAC will cause network troubles if used on the same network.
The wrong Battery Type (I've seen three different so far) can cause charging troubles, and will cause incorrect charge indication.
Don't go there!
NookRestore.img
Try writing NookRestore.img to an mSD card. (You can get a copy at my website: NootRoot)
Hard reset
I had issues rooting my NST and got stuck in a boot loop. After digging and digging through forums I finally discovered the secret to a hard reset. The instructions said to hold the power and the two bottom side buttons down together for over 20 seconds. That worked! My NST was back to when I pulled it out of the box. I then proceeded to re rooting. (my mistake was I did not upgrade the OS before rooting). My bad. Hope this helps someone recover from a stuck boot loop.
Good luck.
chucktate said:
My NST was back to when I pulled it out of the box.
Click to expand...
Click to collapse
No it wasn't, Factory Reset doesn't remove root files or system apps installed by root tools, it only clears custom apps and settings.
While you might think it's back to stock, there are still leftover files and changes in /boot and /system
ros87 said:
Correct!
Using a image from another NST is a very very bad idea!
There are a lot of stuff that's unique to your NST stored in /rom and in rombackup.zip on the Factory partition.
Click to expand...
Click to collapse
Hi, I've just found a way around this - it is possible to restore somebody else's .img file, provided you've backup up your rombackup.zip. Then after, using Noogie, you can overwrite rombackup.zip and the contents of it which are on a different partition. The only danger is that you would potentially overwrite battery type config file, as Nook has couple of them. I gave it a try on mine and it seems fine.
sokoow said:
Hi, I've just found a way around this - it is possible to restore somebody else's .img file, provided you've backup up your rombackup.zip. Then after, using Noogie, you can overwrite rombackup.zip and the contents of it which are on a different partition. The only danger is that you would potentially overwrite battery type config file, as Nook has couple of them. I gave it a try on mine and it seems fine.
Click to expand...
Click to collapse
That is correct.
Problem is that most people who end up in a state where Factory Restore doesn't work has usually managed to overwrite their partition tables and part of the /rom partition.
And at this point it is too late to backup rombackup.zip as it's usually fragmented and cannot be recovered by ext2 file recovery tools.
So.. do a full backup before you do anything to your NST
I found if you restore with holding the two lower buttons it will remove all rooted files.
Googie2149 said:
I found if you restore with holding the two lower buttons it will remove all rooted files.
Click to expand...
Click to collapse
Read post 13 by ros87!
ros87 said:
No it wasn't, Factory Reset doesn't remove root files or system apps installed by root tools, it only clears custom apps and settings.
While you might think it's back to stock, there are still leftover files and changes in /boot and /system
Click to expand...
Click to collapse
Go to my website, download nookRestore.img and write it to an mSD card, Erase and De register, Power Off, then insert mSD then power up, then follow on screen instructions!
[OT - Removed]
[OT - Removed]
Torimu.Joji said:
I'll update the website and post links to XDA.
Click to expand...
Click to collapse
Thank you sir!
By posting proper links you help ensure that people get the most recent software and information

[Problems & Questions] With Official 2.3 Update V2

Hello !
I am feeling really down today after been trying to get my phone working again.
There is a huge problem currently, I am really annoyed that it doesn't work at all.
First thing, my phone won't start after update it just boot loops and never seem to end it.
First thing I noticed /boot, /cache /system and most things are gone, I can load up recovery but nothing more. I have no idea what happened but the whole image folder was wiped and I had to myself put in the CWM recovery.
I can't do an upgrade "again" as it will be stuck @ the unpacking part without starting it at all.
I been trying with 2.3 V2 and with B133(My stock rom I got).
If anyone has a solution that can solve this problem please help out if you could. Also if you are about to tell me get this and that, please most cases I haven't seen any of the Firmware roms in @modaco wiki links work. Means I can't download them, so if you happen to have spare copy please upload it and link it to me. I have been googling and looking through this section twice, nothing really worked out.
Thanks in advance !
If you didn't erase the .cust_backup partition which contain the image folder with all system' s .img files, then maybe it' s damaged. I had some problems with this partition before and when I checked it with windows check disk it repairs it and I had no problems from then. So, try this, and if you still haven' t any file on image folder, you can find the original folder on X5' s forums. Is definately here, but I don't remember where is the link and I don't gonna search it for you. If you cannot find it, you can allways reflash the original rom. If you fix the partition(if this is the problem), I don't think that you'll have problems with update any more.
dancer_69 said:
If you didn't erase the .cust_backup partition which contain the image folder with all system' s .img files, then maybe it' s damaged. I had some problems with this partition before and when I checked it with windows check disk it repairs it and I had no problems from then. So, try this, and if you still haven' t any file on image folder, you can find the original folder on X5' s forums. Is definately here, but I don't remember where is the link and I don't gonna search it for you. If you cannot find it, you can allways reflash the original rom. If you fix the partition(if this is the problem), I don't think that you'll have problems with update any more.
Click to expand...
Click to collapse
Hello, thanks for the reply.
I have no idea about this .cust_backup partition and how I am supposedly to access it via windows. Also the thing you said about fixing partition within Windows, the check disk thing. I am not sure about that part either as I can load CWM and it can read the partitions but they are empty. Also there is nothing in this forums that contains original things, only way for me to fix this if someone have extra copy and can guide me on how and where to place the all needed files. I am pretty sure it's only things that are missing and I can't get a grip out of this.
So to sum up what my problem is.
I did an upgrade from 2.2 to 2.3 with official firmware, it worked out normally but after a reboot my phone became stuck in an endless loop, I can't do anything and it will not I repeat it will not allow me to "re flash" any firmware I tried so far, the 2.3 V2 and B133.
I am begging someone in this forum section, please if you have the knowledge about this problem care to help?
I can't get a refund out the phone warrenty is off and I do not have that much spare money.
Thanks in advance !
If you can get to recovery, wipe cache and data. It should be possible in stock recovery.
The cust partition has all the images for bootloader, recovery etc. You can get to it with the pink screen. Reformatting and then reinserting the images and files could help, but try that when nothing else works.
I can't give you good help via phone, but try wiping data first. Also, try if you can use some other sd card.
Sent from my U8800 using Tapatalk
Blefish said:
If you can get to recovery, wipe cache and data. It should be possible in stock recovery.
The cust partition has all the images for bootloader, recovery etc. You can get to it with the pink screen. Reformatting and then reinserting the images and files could help, but try that when nothing else works.
I can't give you good help via phone, but try wiping data first. Also, try if you can use some other sd card.
Sent from my U8800 using Tapatalk
Click to expand...
Click to collapse
The most common things I have already done, but do enlighten me what this "custom" parition is. Because in windows I do not see such partition I see a removable partition which I have now added a folder called image with these containing files.
http://forum.xda-developers.com/showthread.php?t=1370960
EDIT ** Also regarding to first person who said about Windows partition manager. The thing is I see a lot of partitions and there is no labeling for them, might be because they are ext2/3 or even something else? In anycase I can't do so much I just find it really odd I have many duplicates and I am guessing that must be errors... Because I am seeing the main recovery partition which has no label too... its at 240 MB where 135MB is used. Lastly there is my internal SD card empty and healthy still I can't reach it within Windows if I do not mount it...And can't now without going into the android OS. I Have loads of free space "partitions I don't understand why they are there".
**
Thanks for helping out, it feels not good to have a half dead phone, it's still not solved :'-(
The .cust_backup is the mount point on android for this removable partition with image folder. In windows haven' t this name. I didn't mean to use the windows partition manager, just to use windows explorer, right click on the partition and choose properties, then tools and then check disk. Of course you can use partition manager too, but because as you found there are all no labeled other partitions there and is a bit confused.
As you mentioned, you found the original image folder and you replaced the files. Did you tried to do the update again after that?
Also you can see and the internal sd partiton, but you need linux system. This partition is not fat32, so windows cannot see it.
dancer_69 said:
The .cust_backup is the mount point on android for this removable partition with image folder. In windows haven' t this name. I didn't mean to use the windows partition manager, just to use windows explorer, right click on the partition and choose properties, then tools and then check disk. Of course you can use partition manager too, but because as you found there are all no labeled other partitions there and is a bit confused.
As you mentioned, you found the original image folder and you replaced the files. Did you tried to do the update again after that?
Also you can see and the internal sd partiton, but you need linux system. This partition is not fat32, so windows cannot see it.
Click to expand...
Click to collapse
I have placed all things that I got from here.
http://forum.xda-developers.com/showthread.php?t=1370960
And I can't run the upgrade firmware, it gets stuck at first stage which is to unpack the the update.app thing.
It just stays like that not blinking and frozen.
Did you tried now that you have the original files, to go to recovery mode and wipe data etc?
Also when you try to do the upgrade do you have the device connected with the cable?
I had this problem once and I think that when I disconnected the cable(or maybe wasn' t connected and I connected it, I don't remember well), the proccess bar starts to moving after a while and the upgrade completed successfully.
dancer_69 said:
Did you tried now that you have the original files, to go to recovery mode and wipe data etc?
Also when you try to do the upgrade do you have the device connected with the cable?
I had this problem once and I think that when I disconnected the cable(or maybe wasn' t connected and I connected it, I don't remember well), the proccess bar starts to moving after a while and the upgrade completed successfully.
Click to expand...
Click to collapse
You are not understanding me :-(, I have wiped already millions of times in millions of different ways just to get it work. And no, I don't have the device connrected when I upgrade, it won't work properly then, I have tried to wait for the progress bar to "start" move it won't happen the battery will die, and nothing happened.
I can't go in with normal Recovery mode, can only go in with CWM, the normal recovery mode is really small, I mean only 3mb, while the froyo version is 5mb. Now I am asking if you have the time to upload the image files from 2.3 V2, the ones in forums are for V1. Which I don't know might conflict.
Thanks again for trying to help me out, this is really frustrating to get it to work.
**EDIT**
I worked it out !
I think I understood what you meant, I did as you told I started first with pluggin in the charger forced it to upgrade and now it's upgrading, thank you so much dancer_69. I was going to go tomorrow to buy a new 2nd hand smartphone. But now I can save my money for other things !
**EDIT of EDIT **
I seem to have downgraded to B133, I will try now with B158 2.3 V2 again and hopefully it will work now.
Yes, wasn't clear because I don' t remember what I've done and solve it. But I think that I did it like you discribed too.
Anyway I'm glad that was helpful(kind of)..
And don' t give up so soon with smartphone' s bricks, I've faced brick kind of problems many times and if the device it' s not completely dead, there is something you can do. Maybe need more search or many tries(sometimes the same things) but at the end(and of course If there isn't a hardware problem) device can unbrick.

[Q] Seriously messed up glowlight

Hi lovely people,
Ive managed to mess up my glowlight - Ive managed to have a look at the partition table using noogie and the rom partition is showing as unallocated. I've tried data recovery to no avail. I dont suppose anyone has a complete image of a uk nook simple touch glowlight by any chance, or even just a copy of the rom partition that I can copy back into place using minitool partition wizard?
Thanks for reading folks
cortexbomber said:
Hi lovely people,
Ive managed to mess up my glowlight - Ive managed to have a look at the partition table using noogie and the rom partition is showing as unallocated. I've tried data recovery to no avail. I dont suppose anyone has a complete image of a uk nook simple touch glowlight by any chance, or even just a copy of the rom partition that I can copy back into place using minitool partition wizard?
Thanks for reading folks
Click to expand...
Click to collapse
I don't have a full image, but I do have a copy of the /rom partition for you!
Here you go! :good:
thenookieforlife3 said:
I don't have a full image, but I do have a copy of the /rom partition for you!
Here you go! :good:
Click to expand...
Click to collapse
Thanks :0)
Umm how do I use the qr code on my pc? I dont have a webcam or decent mobile phone
cortexbomber said:
Thanks :0)
Umm how do I use the qr code on my pc? I dont have a webcam or decent mobile phone
Click to expand...
Click to collapse
You don't need the QR code to download the .zip. Just click the name of the file up there ^, it's to the left of the "Click for QR Code" text.
thenookieforlife3 said:
You don't need the QR code to download the .zip. Just click the name of the file up there ^, it's to the left of the "Click for QR Code" text.
Click to expand...
Click to collapse
Doh! i thought it was just the one link.
Ive been using computers since the early 80's - embarrasing!
cortexbomber said:
Doh! i thought it was just the one link.
Ive been using computers since the early 80's - embarrasing!
Click to expand...
Click to collapse
The eighties? Wow, you're an old pro, then! :good:
I, on the other hand, wasn't even alive in the eighties!
Let me know how that /rom partition treats you.
thenookieforlife3 said:
The eighties? Wow, you're an old pro, then! :good:
I, on the other hand, wasn't even alive in the eighties!
Let me know how that /rom partition treats you.
Click to expand...
Click to collapse
Ha! Old Pro indeed Old yes. Pro? Definitely questionable. :good:
Will do. Just having trouble now creating a fat32 partition. The various programs ive tried only let me make a 16mb fat16 partition and after putting the rom data on it, the nook still doesnt want to boot. There may be other problems with the rest of the software. Ah well. I'll either get there or buy another e-reader )) But the challenge is more entertaining.
cortexbomber said:
Ha! Old Pro indeed Old yes. Pro? Definitely questionable. :good:
Will do. Just having trouble now creating a fat32 partition. The various programs ive tried only let me make a 16mb fat16 partition and after putting the rom data on it, the nook still doesnt want to boot. There may be other problems with the rest of the software. Ah well. I'll either get there or buy another e-reader )) But the challenge is more entertaining.
Click to expand...
Click to collapse
lol :laugh:
Have you tried booting NookManager from your sdcard and using the "Restore factory.zip" function? That seems to work very consistently.
thenookieforlife3 said:
lol :laugh:
Have you tried booting NookManager from your sdcard and using the "Restore factory.zip" function? That seems to work very consistently.
Click to expand...
Click to collapse
Just trying that now
cortexbomber said:
Just trying that now
Click to expand...
Click to collapse
No joy sadly. More scouring the internet later i think - House chores to do now. SIgh.
Mayn thanks for the rom and the rest of your advice tho
cortexbomber said:
No joy sadly. More scouring the internet later i think - House chores to do now. *sigh*
Many thanks for the rom and the rest of your advice tho
Click to expand...
Click to collapse
If it was logical, I'd totally give you a full image, but the problem is that each device has its own serial number - if I give you an image of my device, then your device will have mine's serial number, which won't work out so well!
I'd love to keep trying to help you, though - Nook Touch related things are really my forte.
Let's start at the beginning - in your first post, you said that "you managed to mess up your GlowLight". What did you do to mess it up?
Is/was your Nook rooted?
Will your device boot and be used properly, but the GlowLight itself just doesn't work?
thenookieforlife3 said:
If it was logical, I'd totally give you a full image, but the problem is that each device has its own serial number - if I give you an image of my device, then your device will have mine's serial number, which won't work out so well!
I'd love to keep trying to help you, though - Nook Touch related things are really my forte.
Let's start at the beginning - in your first post, you said that "you managed to mess up your GlowLight". What did you do to mess it up?
Is/was your Nook rooted?
Will your device boot and be used properly, but the GlowLight itself just doesn't work?
Click to expand...
Click to collapse
Hi again, sorry for not getting back sooner - that damned thing called life always gets in the way
Yeah, it was rooted. I had used cwm and had adw running as a front end and had installed the screen lock bypass, but the bypass didnt work out so well - quite a bit of battery drain - even when left on a table(so no accidental waking up) - i tried to return it to stock - cant remember what i did tho - and now it just starts with the read forever screen and gets no further - it also seems that it doesnt power off and stays on till the battery is flattened. Trying to boot from the sd card using either nook manager or noogie works just fine tho.
I can see the partitions though minitool partition wizard and the Rom partition is "unallocated" there is also an unallocated space of 56mb at the end of the partitions.
I have tried recreating a fat32 rom partition and then copying the rom backup info from the factory partition, but no joy. For some reason, no partition software I have could create a fat32 partition directly on the nook, so I had to create one on the pc and then copy it over :-/
Thanks for the continued help btw
cortexbomber said:
Hi again, sorry for not getting back sooner - that damned thing called life always gets in the way
Yeah, it was rooted. I had used cwm and had adw running as a front end and had installed the screen lock bypass, but the bypass didnt work out so well - quite a bit of battery drain - even when left on a table(so no accidental waking up) - i tried to return it to stock - cant remember what i did tho - and now it just starts with the read forever screen and gets no further - it also seems that it doesnt power off and stays on till the battery is flattened. Trying to boot from the sd card using either nook manager or noogie works just fine tho.
I can see the partitions though minitool partition wizard and the Rom partition is "unallocated" there is also an unallocated space of 56mb at the end of the partitions.
I have tried recreating a fat32 rom partition and then copying the rom backup info from the factory partition, but no joy. For some reason, no partition software I have could create a fat32 partition directly on the nook, so I had to create one on the pc and then copy it over :-/
Thanks for the continued help btw
Click to expand...
Click to collapse
Are you interested in getting back the B&N functions? Because if not, then what I can do is back up my rooted GlowLight, factory wipe it back to 1.1.5, bypass Oobe (B&N registration), update to 1.2.1, and then make an image of that for you.
Beware, though, you won't be able to use any of the B&N functions if you want me to do that, because your device will have mine's serial number. But don't worry, it won't share anything except for that, so your device will be plenty usable.
thenookieforlife3 said:
Have you already tried booting into NookManager and restoring factory.zip?
Are you interested in getting back the B&N functions? Because if not, then what I can do is back up my rooted GlowLight, factory wipe it back to 1.1.5, bypass Oobe (B&N registration), update to 1.2.1, and then make an image of that for you.
Beware, though, you won't be able to use any of the B&N functions if you want me to do that, because your device will have mine's serial number. But don't worry, it won't share anything except for that, so your device will be plenty usable.
Click to expand...
Click to collapse
Yeah, i tried factory reset with nookmanager, but when I pressed the button to choose factory reset, it came up with the screen that showed the start of progress, but nothing else happened - even after several hours.
by b&n function i assume you mean the shop etc - cant say I'm worried about that bit, but if It will be back to stock, with just the stock software on, that would be cool. )
How would I transfer the complete image? I presume fire up noogie and partition wizard, wipe(err backup) all the partitions on my nook and then copy your partitions over?
cortexbomber said:
Yeah, i tried factory reset with nookmanager, but when I pressed the button to choose factory reset, it came up with the screen that showed the start of progress, but nothing else happened - even after several hours.
by b&n function i assume you mean the shop etc - cant say I'm worried about that bit, but if It will be back to stock, with just the stock software on, that would be cool. )
How would I transfer the complete image? I presume fire up noogie and partition wizard, wipe(err backup) all the partitions on my nook and then copy your partitions over?
Click to expand...
Click to collapse
It will be back to stock, but you won't be able to register with B&N and/or buy any books from them. The Social features also will not work.
If you're interested, I'll make that image for you. See the "back up you Nook" link in my signature for a guide on making and restoring Noogie images.
thenookieforlife3 said:
It will be back to stock, but you won't be able to register with B&N and/or buy any books from them. The Social features also will not work.
If you're interested, I'll make that image for you. See the "back up you Nook" link in my signature for a guide on making and restoring Noogie images.
Click to expand...
Click to collapse
Yep! Interested doesnt quite describe it tho More like biting your hand off
cortexbomber said:
Yep! Interested doesnt quite describe it tho More like biting your hand off
Click to expand...
Click to collapse
EDIT - See OverByter's post below, it has shown me that this wouldn't work out.
Try his method. I'll only give you an image of my device as a last resort.
Your image will also have your mac address besides the serial number, don't think that this is the way to go, basically he'll have an unworkable clone of your device. Why doesn't he use cwm to wipe the partition and then either adb push the rom or use a flashable image?
OB
Sent from my SPH-D710VMUB using Tapatalk 2
thenookieforlife3 said:
Ah. :laugh:
I'm kind of busy with school work right now, but I'll try to get it to you today.
Check for PMs from me in a few hours or so. :good:
Click to expand...
Click to collapse
Hehe. Absolutely no rush. I just appreciate the help.
cortexbomber said:
Hehe. Absolutely no rush. I just appreciate the help.
Click to expand...
Click to collapse
Okay, I may actually have solved your problem! Try the following steps - it's called the "eight interrupted boot" method.
1. I am expecting your Nook is still stuck at the "Read Forever" screen. If it's not, go ahead and turn your Nook all the way off.
2. Now, press the power button to take it to the "Read Forever" screen.
3. After it's there, press and hold the power button again to make the screen flash black and go back to the "Read Forever" screen.
4. Perform step 3 seven more times.
5. After the 8th interrupted boot, your Nook will restore itself to the factory image that it came with right out of the box.
6. Done!
Hope this works! :good:

Files get deleted when cut/pasting

So when I connect my phone to my PC and enable file transfer, I try and copy or cut and paste files and it doesn't work. Yesterday I created a new folder where my pictures are stored by default. I then copied and pasted the pics from the main folder to the new one and it went through the motions but didn't display any. I refreshed and still nothing. I backed out of the directory and the folder said it was empty but so was my main pic folder. So it basically deleted everything instead of pasting them in the new folder. Is there an easy fix to this? Never had this issue with my note 3 and 4. Or any other phone for that matter. Is there like a Read/Write command to turn on or something? Seams like a pretty big flaw to not be able to cut paste files and they just get deleted....
Any help on the subject would be greatly appreciated,
Never had any issues like this, both on encrypted and decrypted data. Try flashing the userdata again and see if the issue still persist.
Also, have you checked for the pics in Recycle Bin?
sufoalmighty said:
Never had any issues like this, both on encrypted and decrypted data. Try flashing the userdata again and see if the issue still persist.
Also, have you checked for the pics in Recycle Bin?
Click to expand...
Click to collapse
If it helps, I am not rooted and completely stock. How would I go about finding the recycling bin?
I have the same issue with my OP5 (decrypted)
Have you tried copy pasting?
Mine worked well when I did it (encrypted).
Just drag and drop, don't copy so much, try one folder at a time instead.
Also I'd never use cut and paste, if it fails you could end up in limbo with files missing.
Always copy.
Sent from my ONEPLUS A5000 using XDA-Developers Legacy app
strider5236 said:
If it helps, I am not rooted and completely stock. How would I go about finding the recycling bin?
Click to expand...
Click to collapse
You were moving pics from your PC to the phone, were you not?
Windows moves the files to Recycle Bin when you cut-paste.
sufoalmighty said:
You were moving pics from your PC to the phone, were you not?
Windows moves the files to Recycle Bin when you cut-paste.
Click to expand...
Click to collapse
No, just moving files from one folder to another within the phone. Just using the PC to play middle man to issue the command.
Pwnycorn said:
Have you tried copy pasting?
Mine worked well when I did it (encrypted).
Click to expand...
Click to collapse
I am not concerned about the files as I have a backup. What concerns me is that the OP5 does this to begin with. I have had several iphones and several Samsung phones and never encountered this issue. That is a design flaw within the software. I was hoping to get an answer as to if this can be fixed or if it is just a flaw with OP5's operating system. Just seems odd this phone does that.
strider5236 said:
I am not concerned about the files as I have a backup. What concerns me is that the OP5 does this to begin with. I have had several iphones and several Samsung phones and never encountered this issue. That is a design flaw within the software. I was hoping to get an answer as to if this can be fixed or if it is just a flaw with OP5's operating system. Just seems odd this phone does that.
Click to expand...
Click to collapse
It doesn't happen to everyone. So we can't really talk about a design flaw in the software, otherwise it would affect every device. It's more like a random bug I guess.
As I said, when I got this device I successfully copied my files. Granted, it did seem to have missed a few files (2 Titanium Backup backuped files) and possibly more I did not notice so far.
I've noticed dodgy OTG on the O+5 never had it in a phone before
Because the copying is done by the operating system of your PC, shouldn't there be the problem? The phone is just connected by the internal storage as an external drive. Or is this a driver thing?
Pwnycorn said:
It doesn't happen to everyone. So we can't really talk about a design flaw in the software, otherwise it would affect every device. It's more like a random bug I guess.
As I said, when I got this device I successfully copied my files. Granted, it did seem to have missed a few files (2 Titanium Backup backuped files) and possibly more I did not notice so far.
Click to expand...
Click to collapse
Well to me, bugs are inherently design flaws. lol But I don't want to argue semantics. I would just like to find a fix to this "design flaw"/bug. I can understand having a few files deleted or not transferred. But every single file that was selected, cut and pasted? That is just frustrating beyond belief. I just don't get why it does that to begin with. Never encountered this issue with any other phone I have done this same procedure with. I have no issues with transferring files from the pc to the phone. The problem is encountered when I am trying to do things with the internal storage. That is what is confusing me.
@strider5236, tried doing it again on decrypted data using Windows 10 and and Ubuntu 14.04. Moved with no issues. Encrypted data then did it again. No issues still.
Have you tried flashing the userdata image like I initially suggested?
sufoalmighty said:
@strider5236, tried doing it again on decrypted data using Windows 10 and and Ubuntu 14.04. Moved with no issues. Encrypted data then did it again. No issues still.
Have you tried flashing the userdata image like I initially suggested?
Click to expand...
Click to collapse
Can that be done on a stock, non rooted phone? If so, how do I go about that? Would odin be needed?
strider5236 said:
Can that be done on a stock, non rooted phone? If so, how do I go about that? Would odin be needed?
Click to expand...
Click to collapse
LOL. No, we aren't using a Samsung device. I'll send you the steps in a PM.
sufoalmighty said:
LOL. No, we aren't using a Samsung device. I'll send you the steps in a PM.
Click to expand...
Click to collapse
That would be great thank you.
There seems to be a bug in the Media Transfer Protocol (MTP) between Android and Windows 10. It loses files while copying.
http://winfuture.de/news,99331.html (German)

Resources