Related
I used RSD lite to flash to 4.1.2.6 and when it boots up the touch screen is way off and i can even go back or click the buttons on the bottom row. Anyone else have this happen? I reflashed twice already to see if it would fix it.
I've been toiling day and night for the last few days with the exact problem!!!
Tenfar is trying to help me via PM.
Because I partitioned internal SD this happened. I figure we need to do following command:
adb shell mkfs.vfat /dev/block/mmc0p18
And then
#newfs_msdos -F 32 -S 512 -L MB860 -c 64 -u 16 /dev/block/mmcblk0p18
But I'm getting random daemon errors now because my PC is a piece of ****!! Trying to fix that problem to run the first command. Second command goes through okay but I'm still having touch screen issues.
Waiting for him to PM back. I'm in Canada with an AT&T Atrix and although the seller can send me proof of purchase, to send it to Motorola would take super long and would cost lots in shipping.
If you find anything, please post it here. I'll do the same!
lol
lol yup thats what i did. I realized it wouldnt let me install from internal sd and i didnt have a external sd at the time so is figured let me format it.. whats the harm. Well the harm is the whole bottom row of buttons doesnt work and the bottom of the screen is a half inch off lol. Been driving me crazy, let me know if u get anywhere with tenfar
Getting stupid daemon errors I can't fix. Going to try on another machine and will let you know if there's any progress. Seems simple enough in concept but I'm no Linux genius.
I'll keep you posted.
Have u tried booting into the recovery and partitioning the internal sd another way?
fallchild said:
Have u tried booting into the recovery and partitioning the internal sd another way?
Click to expand...
Click to collapse
Yep. I've tried it all. Has to be manual now from what I gather... didn't get the chance to try on a new computer last night but will after work. I'll send you the commands if it works.
Dear lord, I hope it works!
Any Luck? I use my phone heavily for work and i had to use bluetooth all day with voice commands just to use the phone half way decently lol.
I had the same issue. I wasn't able to boot into my custom recovery and repartition. I ended up taking it back to AT&T and getting it exchanged. Can always pass it off as a bad device.
No luck. Same error. I tried mounting SD but I think I must be doing something wrong..
Still giving it another few tries. What a bummer. Gotta rip through the Atrix dump to see if I can find something else useful.
Can't unmount my SD card and successfully run the other command. Not sure what the heck I'm doing wrong. Now I'm uncertain what state my phone should be in when I run these commands.
I'm going to keep tinkering around but I'm waiting for the proof of purchase because I think I'll need to send it in. Damn. Wish I had someone in person that knew how to use shell commands properly. I'm not the greatest at this. Using an Xperia X10 in the meanwhile and dying to use my Atrix again. :'(
Hopefully someone will be kind enough to do a Nandroid backup of a fresh install and post it. I'm not sure but I think it could possibly help. It's worth a shot. Would pay someone $10 via Paypal if they could upload it to their Dropbox or something.
Hey OP, any luck?
If you have a new Atrix. Could you do a Nandroid backup and upload it to Dropbox by any chance???
I've exactly the same problem! (And when you are in some menu, you can't go back, so you have to reboot!!)
I did the same thing (Root, put recovery and so...)
I partitioned internal SD... And now, it's like touchscreen completly disturbed.
When you click on home - back or search, the screen select the bottom of the android interface!
I need to know if someone has a correct issue for that... I'm not at home, I will test the commands in adb from the second post later...
Also, I don't understand how a nandroid backup could resolve the problem... A backup will resize and fix the internal memory?
Thanks
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.
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:
I am beyond ecstatic, after 3 months of research, trial and error, I fixed my tablet!!
I am pleased to announce a fix to the dreaded QDLOAD 9008 brick! I've written this tutorial on the one tablet experimented on (LG-V410 aka Gpad 7.0 LTE US ATT), but I'm pretty certain others may find this helpful to other qualcomm msm based devices.
Background: I maintain that I can fix anything I break so I did the worst thing and corrupted the data on my LG GPAD LTE 7.0 (V410). As a result the tablet wouldn't go into any mode, no lights, even when charging, no screen image or light, nothing. When I plugged it into my computer, it wasn't even recognized, windows told me the device was having a problem. After a little experimentation I got it recognized (held power while connected to power cycle) by the computer as "QD BULK". Further research I found some drivers for Qualcomm devices and got the computer to recognize it as "QDLOADER 9008". I thought this was great news but from there got no where. I tried qpst, qfuse, hyperterminal, LG B2C, LG SUPPORT TOOL, EFS Professional, miflash, blankflash, etc... everything I tried got me nowhere. After 3 months, It is now fully operational and apparently CARRIER UNLOCKED, talk about a pot of gold at the end of a rainbow!!
WORD OF WARNING: This is not a simple matter, 9008 most likely means your Grand Partition Table is corrupted, and the poor thing doesn't have a clue how to function. My method is NOT GUARANTEED in any way, I will not be responsible if you turn your paper weight of a device into permanent paper weight or half functioning paper weight etc...PROCEED WITH CAUTION, this is not for the feint of heart nor a simple fix!! You've been warned!
PreRequisites:
-Windows (for expanding the KDZ) (there may be a linux alternative to LGFirmwareExtract)
-Linux and some basic experience with dd and navigating the terminal (I used ubuntu) --(again, nearly everything I'm about to explain can probaly be translated to another os.)
-KDZ for your device. http://forum.xda-developers.com/g-pad-10/general/kdz-lg-g-pad-7-0-v410-t3224867
-Replacement aboot and boot (see attached)
-KDZ Extractor ---http://forum.xda-developers.com/showthread.php?t=2600575
-TWRP http://forum.xda-developers.com/g-pad-10/development/recovery-twrp2-8-5-0lgv400-410-t3049568
-Fasboot and ADB http://forum.xda-developers.com/showthread.php?t=2588979
-A modified rom like Cyanogen mod etc... http://download.cyanogenmod.org/?device=v410
-16GB microsd card + a way of directly writing to it (i.e. usb card reader etc..) a second one is helpful but not required.
-Most important, Patience, beer, more patience, and more beer...
To teach a man to fish, some pertinent understanding: First thing to understand is how your main board works. Personally I disassembled my device and cross referenced every chip to do this, Good news is you don't have to. When power goes to the device, the SoC (system on a chip) looks to built in storage media for booting instructions (think low level here) and that in turn fires up everything else and then loads your kernel etc... You may be aware, there are two different types of computer systems out there, the old method used a BIOS, and the current uses UEFI. Older machines, when power was given to the system, the BIOS was responsible for firing up peripherals and finding the bootloader etc... UEFI (Unified Extended Firmware Instruction) however, relies on firmware on storage media to do all that.
For example, an x86 PC with a bios, when power is given to the board, the bios runs the show, testing equipment and waking up devices, then when it's ready, it looks to external media for a little magic byte at the end of the first sector of that media to indicate that it is bootable and in turn will boot (let those instructions take over). This style of booting media is called MBR or Master Boot Record.
Modern machines and most mobile devices use GPT or global partition table. There are quite a few advantages to GPT one primary being the possibility of many many more primary partitions, (MBR was very limited). The GPAD 7 LTE has 34 partitions to put things in perspective. When your device is stuck in 9008 mode, it is because it doesn't have a clue how to boot, most likely your GPT is corrupted. Fortunately, at least with the Gpad 7.0 this information does not have to be on the onboard internal memory chip. For this fix we will be constructing an sdcard to have all this info to get into a mode capable of writing to the emmc.
Without Further Ado, Here are the steps:
]PLUG THE TABLET INTO A CHARGER while you do the following (you may think it's been off and fully charged, but in reality it's probably been trying to boot over and over again while looking lifeless)
1.) Get the KDZ for your device (stock firmware)
2.) Extract the DZ using LGFirmwareExtractor
3.) Extract all the .bin files from the DZ using LGFirmwareExtractor
3b.) V410 US LTE ONLY - Replace aboot and boot with the files I attatched --I was fortunate enough to back them up before I hosed my tablet and they proved invaluable as the ones in the KDZ I linked to were causing strange graphic issues.
4.) open a terminal in linux and dd the sdcard with the file you extracted called "PrimaryGPT...."
I.E. "sudo dd if=/PATHTODZFILES/PrimaryGPT_0.bin of=/dev/sdx" (BE CERTAIN of the of= path, you can find yourself with more problems if you get that wrong) (run "sudo fdisk -l | less" first to verify what your sdcard's path is.)
This is where it gets tedious...:
5.) Do some hand stretches and start charting all 34 partitions on paper. Your sdcard is now partitioned with GPT and you need to know the name of each partition and its path. I.e. ("Partition name: LAF Located at /dev/sdXx")
6.) now for the fun part: dd every .bin to the corresponding partition EXCEPT: laf.bin and any of the system_xxxxx.bin files. (laf disables fastboot and the next step will bring you to a useless LG firmware download mode)( I.e. sudo dd if=/PATHTODZFILES/laf_xxx.bin of=/dev/sdXx) If some fail out, don't fret too much, I'm currently uncertain which ones are required and don't feel like corrupting my tablet again to figure that out. If the next step doesn't work you may need to revisit this step and ensure everything was accurate. It's easy to write down the wrong location for a partition and throw everything off
7.)Unmount your sdcard and put it in the tablet
8.) Press and hold power and volume up...If all went well, there is suddenly life to your paperweight!! Congratulate yourself and prepare for more fun... If nothing happened, revisit the above steps, more than likely something got flashed to the wrong partition.
9.)Now that you have fastboot, plug your tablet into the computer and use the following command: "fastboot boot TWRP.img" (or whatever the name or path is for your downloaded TWRP image.
10.) You should now be in TWRP and now your device is ADB ready, we are close to the home stretch...
11.) Now we need to load up an sdcard with all those dz files (except for laf and system images) and the custom rom like cyanogen mod. (if you only have the one sdcard you can unmount it and remove it while the table is in TWRP...crazy right?, if you opt for this, reformat the sdcard to ext or fat or whatever you please so the tablet can see all the bin files) Then put the sdcard into the tablet. You may need to remount the card in twrp before proceeding...
12.) Now from your computer type the following command "adb shell".
13.) now just like you did with the sd card dd PrimaryGPT_0.bin to the internal memory card, with the following command: dd if=/sdcard/PrimaryGPT_0.bin of=/dev/block/mmcblk0
14.) Grab the paper you wrote all the partitions down on and start doing the same thing you did to the sdcard to your tablet. You'll adjust the following command accordingly: "dd if=/sdcard/PARTITIONNAME.bin of=/dev/block/mmcblkpX (X being the partition number)
(again skip all system bin's and laf_xxxx.bin. Flashing laf disables fastboot on LG devices.)
15.) now time to install your custom rom, go through the prompts, clear your cache, and delvik cache and choose power off.
If all went well, you now have a tablet again, that's unlocked too!!!!! If not, don't lose faith, revisit the steps and ensure you didn't mistype or overlook something, this is so tedious it's easy to do. For instance, if you mistype your of=xxx it will create the file instead and give no error.
Post with your success stories, questions or difficulties and I'll try to help.
Yours Truly,
TheKiln
UPDATE/WARNING: Do not at any time under any circumstances dd directly from your host computer to the internal memory on your tablet, only do this via the asb shell. This may render a mode that I have not yet found a fix to, I will be working on it soon but from initial observation may be more complicated then the above instructions. With any invasive hacks like this tutorial there is always the possibility of making matters worse, so exercise caution and patience.
Quick Update/Revision : I am actively experimenting with this device and wanted to share that if your sbl1 and sbl1b partition is corrupt I have confirmed it will also cause 9008 mode. Therefore, it may be best to determine if the table is corrupt (try "parted /dev/block/mmcblk print"), and if not instead of wiping rewriting mmcblk0 try restoring sbl1 and sbl1b first. The V410 boots in the following order from what I can tell slb1->aboot->boot->system. So far I haven't found a downside to my prior instructions but to be less invasive just in case it might be wise to try this amendment.
I know my grand partition is corrupt, because after doing fastboot erase, basically everything, it came up as /dev/sdb. In a panic, I had deleted all the partitions, so now obviously my emmc storage is one big formated 16gb HD that cannot be seen in windows or linux no longer.
I just tried your method, found this post by doing a google search for:
sudo dd if=PrimaryGPT_0.bin
Had been doing just this, including the laf and many other ways. Am still getting the same thing though when putting the sdcard in the tablet, shows a 0% battery.
with the sdcard in the tablet I do get:
Bus 003 Device 063: ID 05c6:f006 Qualcomm, Inc.
Then after a few minutes, leaving it plugged into the USB I get:
Bus 003 Device 058: ID 1004:61a1 LG Electronics, Inc.
Also, with the sdcard in I do get KDZ_FW_UPD_EN to start updating but then get a perimeter error.
bethnesbitt said:
I know my grand partition is corrupt, because after doing fastboot erase, basically everything, it came up as /dev/sdb. In a panic, I had deleted all the partitions, so now obviously my emmc storage is one big formated 16gb HD that cannot be seen in windows or linux no longer.
I just tried your method, found this post by doing a google search for:
sudo dd if=PrimaryGPT_0.bin
Had been doing just this, including the laf and many other ways. Am still getting the same thing though when putting the sdcard in the tablet, shows a 0% battery.
with the sdcard in the tablet I do get:
Bus 003 Device 063: ID 05c6:f006 Qualcomm, Inc.
Then after a few minutes, leaving it plugged into the USB I get:
Bus 003 Device 058: ID 1004:61a1 LG Electronics, Inc.
Also, with the sdcard in I do get KDZ_FW_UPD_EN to start updating but then get a perimeter error.
Click to expand...
Click to collapse
Ive seen the exact mode you are referring to. Three possibilities:
1.) unplugged, hold down the power button for 30 seconds (or less if fastboot comes up)
2.) your sd card does not have all the necessary partitions to boot (which i just confirmed are specifically rpm, rpmb, tz, tzb, sbl1, sbl1b, PrimaryGpt(has to be done first), aboot and abootb)
3) They didn't dd quite right. from my active testing Ive found if you script the dd'ing it doesn't quite flash right, unless you add a delay after each step.
Its actually a very good sign you are seeing the 0% battery logo, sounds like you are almost there. Let me know what happens. Ill be happy to help guide you. Ive dedicated my v410 as a dev board so Im constantly running tests and reverse engineering it.
The 0% only shows up with the sdcard in, after I remove it, nothing. Tried wall charging it all night, that did nothing.
My theory is that if there was some way to mount the raw emmc and dd the primarygpt.bin to the raw emmc hd then the rest would be not problem.
I deleted the original EMMC partitions in gparted under linux after doing an erase fastboot -w laf, system, etc... something like that. After that the tablet did not show up again in gparted as soon as I unplugged it.
Right now I'm zero dd'ing my 16gb sd card, dang dd'ing seems to glue the partitions to the sdcard, If I try to fdisk the sdcard or delete the partitions using gparted, as soon as I dd the primarygpt.bin the old files reappear. Need to start fresh with 0s to the card.
In windows I can actually install specific lg drivers while in qualcomm hs_usb 9008 mode. The interesting thing with the sdcard in I can install the LG Android Net USB serial driver, which will not work while in 9008 mode.
bethnesbitt said:
The 0% only shows up with the sdcard in, after I remove it, nothing. Tried wall charging it all night, that did nothing.
My theory is that if there was some way to mount the raw emmc and dd the primarygpt.bin to the raw emmc hd then the rest would be not problem.
I deleted the original EMMC partitions in gparted under linux after doing an erase fastboot -w laf, system, etc... something like that. After that the tablet did not show up again in gparted as soon as I unplugged it.
Right now I'm zero dd'ing my 16gb sd card, dang dd'ing seems to glue the partitions to the sdcard, If I try to fdisk the sdcard or delete the partitions using gparted, as soon as I dd the primarygpt.bin the old files reappear. Need to start fresh with 0s to the card.
In windows I can actually install specific lg drivers while in qualcomm hs_usb 9008 mode. The interesting thing with the sdcard in I can install the LG Android Net USB serial driver, which will not work while in 9008 mode.
Click to expand...
Click to collapse
The 0% comes up when your sdcard is inserted because you are close to getting it done. You're going to have your computer running all night on the zero'ing but I can assure you that will be in vein. The whole point of this tutorial is so you can get into a mode in which you can flash the emmc. I can tell you are a little lost in the steps so pm me and I'll help you out. Also a word to the wise, you can try all you want with windows and the 9008 drivers, but seriously there is nothing out there specific to the v410 thats going to help you "engage" the 9008 mode. Not being stubborn I've just literally tried it all. If it's any credit I am clinically OCD. I can't sleep till I figure things out.
Finally, I see a hope is shining here!
I bricked my LG VK810, when I was trying to flash twrp, I refered to v500 pad instead and I flashed wrong img files (aboot, boot, sb1, sb2, sb3, tz & twrp.img) "only those 6 files" so I only need to replace those with the correct files, which I downloaded now.
I do not have Ubuntu, however I have CentOS, which i have not used for couple of years, so I forgot how to use it. also do I still need to use the LG Firmware Extractor?
please help
thekiln said:
This is where it gets tedious...:
5.) Do some hand stretches and start charting all 34 partitions on paper. Your sdcard is now partitioned with GPT and you need to know the name of each partition and its path. I.e. ("Partition name: LAF Located at /dev/sdXx")
6.) now for the fun part: dd every .bin to the corresponding partition EXCEPT: laf.bin and any of the system_xxxxx.bin files. (laf disables fastboot and the next step will bring you to a useless LG firmware download mode)( I.e. sudo dd if=/PATHTODZFILES/laf_xxx.bin of=/dev/sdXx) If some fail out, don't fret too much, I'm currently uncertain which ones are required and don't feel like corrupting my tablet again to figure that out. If the next step doesn't work you may need to revisit this step and ensure everything was accurate. It's easy to write down the wrong location for a partition and throw everything off
Click to expand...
Click to collapse
Please please please help, how to do those steps!
nmnm4alll said:
Please please please help, how to do those steps!
Click to expand...
Click to collapse
I am not certain exactly which partitions have to be flashed, the attached note I made was from what I can tell so far. I was simply noting that it may be best to try one partition at a time vs doing them all at once, it is at your own descretion. So as far as listing the partitions, I'm not familuar with the centos distro but in Ubuntu it is something to the effect of fdisk /dev/sdb -l or gdisk /dev/sda then p. I hope that answers your question, If not please be more specific to your exact question.
thekiln said:
I am not certain exactly which partitions have to be flashed, the attached note I made was from what I can tell so far. I was simply noting that it may be best to try one partition at a time vs doing them all at once, it is at your own descretion. So as far as listing the partitions, I'm not familuar with the centos distro but in Ubuntu it is something to the effect of fdisk /dev/sdb -l or gdisk /dev/sda then p. I hope that answers your question, If not please be more specific to your exact question.
Click to expand...
Click to collapse
Thank you very much for your response, I am sorry I have never flashed partitions before, sbut I noticed gparted is not on CentOS, so I downloaded Puppy precise Linux as I was able to find gparted and I tried using it as shown in this video, https://www.youtube.com/watch?v=6z1Tu9l8WNc
But I am confused now about how big and what are the formats for the 34 partitions which need to be created?
nmnm4alll said:
Thank you very much for your response, I am sorry I have never flashed partitions before, sbut I noticed gparted is not on CentOS, so I downloaded Puppy precise Linux as I was able to find gparted and I tried using it as shown in this video, https://www.youtube.com/watch?v=6z1Tu9l8WNc
But I am confused now about how big and what are the formats for the 34 partitions which need to be created?
Click to expand...
Click to collapse
Flashing PrimaryGPT_0.bin will automatically create the partitions. Flashing the individual partitions will give each partition the data needed. There should be no need to manually create partitions, if no partitions show up in gparted, the problem goes back to primarygpt, as that is the partition table.
I am not quite sure what you mean by:
thekiln said:
5.) Do some hand stretches and start charting all 34 partitions on paper. Your sdcard is now partitioned with GPT and you need to know the name of each partition and its path. I.e. ("Partition name: LAF Located at /dev/sdXx")
Click to expand...
Click to collapse
how to can I get the Partition names?
Edit: I finally was able to get Ubuntu installed on my computer, so please instruct accordingly, sorry I have been googling everything you have mentioned in your OP with no luck!
Thanks in advance.
nmnm4alll said:
I am not quite sure what you mean by:
how to can I get the Partition names?
Edit: I finally was able to get Ubuntu installed on my computer, so please instruct accordingly, sorry I have been googling everything you have mentioned in your OP with no luck!
Thanks in advance.
Click to expand...
Click to collapse
For the names I like to use "parted /dev/sdb" then "print" (sdb being the location of the sd card, might be sdc, sdd, etc..)
thekiln said:
For the names I like to use "parted /dev/sdb" then "print" (sdb being the location of the sd card, might be sdc, sdd, etc..)
Click to expand...
Click to collapse
Thanks for the command line, I came up with this 36 partitions
https://www.dropbox.com/s/bw8nj317y3v7pw6/VirtualBox_Ubunto_05_01_2016_08_59_03.png?dl=0
now how do I know each partition's path?
you have mentioned "I.e. ("Partition name: LAF Located at /dev/sdXx")"
so do I type for example: "modem: LAF located at /dev/sdb1" (sdb1 is my sdcard's path)?
thekiln said:
6.) now for the fun part: dd every .bin to the corresponding partition EXCEPT: laf.bin and any of the system_xxxxx.bin files. (laf disables fastboot and the next step will bring you to a useless LG firmware download mode)( I.e. sudo dd if=/PATHTODZFILES/laf_xxx.bin of=/dev/sdXx) If some fail out, don't fret too much, I'm currently uncertain which ones are required and don't feel like corrupting my tablet again to figure that out. If the next step doesn't work you may need to revisit this step and ensure everything was accurate. It's easy to write down the wrong location for a partition and throw everything off
Click to expand...
Click to collapse
Those are the files got extracted from the DZ file
https://www.dropbox.com/s/z3ebiy4vvnsy9oo/Untitled.png?dl=0
and this is a screenshot in Ubuntu after copying the file on a 64 memory stick and mounting it
https://www.dropbox.com/s/gqn35n1npklq8ld/VirtualBox_Ubunto_05_01_2016_09_30_15.png?dl=0
Do I just type: "sudo dd if=/media/mike/MEMORY/aboot_153600.bin of=/dev/sdb1" and so on for all .bin files?
Please try to write command lines as I do not have experience with Linux
I'll be honest and blunt, if you do not have experience with linux, a simple keystroke mistake could wipe your entire computer. I can't in good conscience recommend touching dd if you're not familiar with it. Not trying to be condescending or anything just really dangerous tools we are working with here.
it have problem
wow !!! i can see the LG logo in my tablet !!!
but i can't run next step !!!
pushed power + volume up button but i never changed screen !!
This is written on the screen.
"boot certification verify"
please help me i copy 34 partition on SDcard after that what can i do? please answer , this does not work (( 8.) Press and hold power and volume up...If all went well, there is suddenly life to your paperweight!! Congratulate yourself and prepare for more fun... If nothing happened, revisit the above steps, more than likely something got flashed to the wrong partition.
Issue
Hello, I've successfully followed the tutorial until step 9. When i flash TWRP it reboots and comes back to the fastboot screen.
If I hold the vol+ button when it is booting, the download mode screen flashes for a second and then it comes back to the fastboot.
I haven't been able to to anything else and would be very grateful if someone could help me with this.
Apparently there is no bootloader so it is stuck
I attached a picture of my screen
LG G Pad 7.0 V400
Is there a way to unlock Qualcomm 9008 from LG V400?
Finally my dead tablet went into fastboot mode.
Except windows cannot find a fastboot driver and fastboot command can't locate the device either. Any suggestions?
Hey guys,
Quick newbie question for you. I followed the procedure in this thread ([ROM][5.1.1][LMY47V] 21 May- Stock Flashable Rom/Factory Image) to a T and have 5.1.1 on the Nexus 4 but for some reason my internal SD card paths are all messed up. I couldn't use my camera to take a photo - it wouldn't save anywhere.
I used Terminal to run the restorecon -FR command for /data/media/0/* and then I restarted the phone and I could use my camera, so that was a good step.
Now I'm in WhatsApp and I can't see any media that people are sending me. The photos stay blurry. Is WhatsApp pointing to a directory that doesn't exist? How can I solve that? Or is my internal SD card ****ed?
I am using TWRP so if you have any solutions I can fully utilize that to fix the path errors or re-flash system img or whatever you think will work! My brother is trying to send me photos through WhatsApp and I can't see 'em!
Any help is appreciated!
--Mike
Did usie the script included with the stock ROMs to flash back to stock?
audit13 said:
Did usie the script included with the stock ROMs to flash back to stock?
Click to expand...
Click to collapse
You mean the flash_all.bat? Nah - I manually flashed as per the forum thread I linked to. I installed through TWRP, not fastboot. My Nexus 4 only connects as an AC source so I can't even get it communicating with my PC to unroot and flash stock.
So the phone is not recognized in OS X, window, or Linux? Tried different USB cables and USB ports?
audit13 said:
So the phone is not recognized in OS X, window, or Linux? Tried different USB cables and USB ports?
Click to expand...
Click to collapse
Yeah I've pretty much tried everything to get it communicating with the computer again. I think it's a hardware issue - I had my screen replaced and I think some part of the battery assembly wasn't re-installed properly and thus communication ceased. I thought flashing to 5.1.1 would fix what could have been a 4.4.4 issue, as I had USB fast charge enabled with various kernels, but alas this was not to be.
Any ideas about the internal paths?
A screen replacement does involve moving the USB charging port to the new screen and it is possible that this part was damaged and vertical seems to be the case. I assume you don't have access to another phone to test the port.
audit13 said:
A screen replacement does involve moving the USB charging port to the new screen and it is possible that this part was damaged and vertical seems to be the case. I assume you don't have access to another phone to test the port.
Click to expand...
Click to collapse
Yeah no other phone to test the port. I just got an X Play and am using the same cable I was using with my Nexus 4 and communication is flawless - adb, fastboot, all the goodies. I thnk I'll need to take the Nexus to a shop or open it up myself.
Thanks for paying attention to this thread, audit.
Try opening the phone yourself as it is pretty easy but that choice is yours. Good luck!.
Hi Mike, just a hint... did you check the partition status on your device ? To check if it's a logical or hardware issue, here's a reference: http://forum.xda-developers.com/moto-x-play/general/partition-layout-t3196367
You can analyze yours with something like: https://play.google.com/store/apps/details?id=com.cls.partition
and eventually mount manually the missing mounts.
dev>null;5160773 said:
Hi Mike, just a hint... did you check the partition status on your device ? To check if it's a logical or hardware issue, here's a reference: http://forum.xda-developers.com/moto-x-play/general/partition-layout-t3196367
You can analyze yours with something like: https://play.google.com/store/apps/details?id=com.cls.partition
and eventually mount manually the missing mounts.
Click to expand...
Click to collapse
Great idea, dev. How do I go about manually mounting? Do I need to use Terminal or something similar?
Thanks for your reply.
mounts & partitions
@XxMikeMasterxX Yes! In terminal emulator.
Code:
su
cat /proc/mounts
- or -
mount
- or -
df
- or -
cat /proc/partitions
to list all partitions/devices/... a bit messy output
The mount command is also what you'll need after you find the problem.
It can mount a partition, remount read-write...in case it's a permission problem, or bind a folder to another, in case it's looking for a specific folder, but your system named it in a different way.
Not sure if this applies to your case...just an idea Did your partitions check return any anomaly ?
dev>null;5160773 said:
@XxMikeMasterxX Yes! In terminal emulator.
to list all partitions/devices/... a bit messy output
The mount command is also what you'll need after you find the problem.
It can mount a partition, remount read-write...in case it's a permission problem, or bind a folder to another, in case it's looking for a specific folder, but your system named it in a different way.
Not sure if this applies to your case...just an idea Did your partitions check return any anomaly ?
Click to expand...
Click to collapse
Not that I can see. I'm a bit of a noob with Terminal so I'll even have difficulty identifying the erroneous file paths. It's too bad my adb and fastboot don't work. Or else I'd just revert to stock and re-flash everything.
@XxMikeMasterxX If you don't want to mess with terminal, try using the app linked in my first message then (or others that show mount points and partition details), and please use this as a reference. I posted the MXP one by mistake !!!
dev>null;5160773 said:
@XxMikeMasterxX If you don't want to mess with terminal, try using the app linked in my first message then (or others that show mount points and partition details), and please use this as a reference. I posted the MXP one by mistake !!!
Click to expand...
Click to collapse
@dev>null Eeeek! Scared! I'll try the app and see what I can see. I guess from there it's a simple remount.
So hypothetically let's say that sdcard is mounted somewhere else by mistake and some app folders end up on the wrong partition/location, do I use a remount to remount that particular folder/location to the proper sdcard path?
Whoa I think I just got it.
@XxMikeMasterxX Exactly! There used to be a bug in CM with wrong sdcard mount point. Take a look at this, I'm sure it will address you to the right direction
And also give you examples for command syntax...
dev>null;5160773 said:
@XxMikeMasterxX Exactly! There used to be a bug in CM with wrong sdcard mount point. Take a look at this, I'm sure it will address you to the right direction
And also give you examples for command syntax...
Click to expand...
Click to collapse
You're the man. I'll try it soon. My brother has the phone now so it could be a bit.
XxMikeMasterxX said:
You're the man. I'll try it soon. My brother has the phone now so it could be a bit.
Click to expand...
Click to collapse
@dev>null
My brother tried the Terminal commands but after he entered su and tried the other 4 commands Term returned "nothing found" each time. What does that mean?
Also, it appears that he needs to remlunt his entire SD card somewhere. What's the folder? Root/sfcard
@XxMikeMasterxX Nexus 4 does not have a physical sdcard, so I guess it's just a missing symbolic link.
Try:
Code:
su
mount -o bind /data/media /sdcard
and see if Whatsapp can save the images now.
Also you may want to check this guide: http://forum.xda-developers.com/google-nexus-5/general/howto-repairing-corrupted-data-partition-t2577447
dev>null;5160773 said:
Also you may want to check this guide: http://forum.xda-developers.com/google-nexus-5/general/howto-repairing-corrupted-data-partition-t2577447
Click to expand...
Click to collapse
@dev>null
Thanks for your recommendations. Yet again, though, the command you provided didn't work. I tried to get him to bind different locations to sdcard but that didn't help either.
A funny thing he told me is that under Settings>Storage he can't open the Internal storage section. He said it just doesn't open.
It's almost like Android installed to a really weird location and isn't recognizing anything. I am really baffled.
I checked out the guide - the o ly problem.is that the phone doesn't connect as a USB device (broken link...battery maybe?) and as such he can't run the adb commands.
I wish it did connect USB though - I'd just have him return to stock and then this would all be erased. Any other ideas, dev? I really don't know what to do next... Thanks for your ideas so far - you've been a great help.