** UPDATED WITH .BCT saving, include USB as well as NVFLASH just copy in
** 1 dir, run the batch and keep those you may need them one day
** Read the batch file for more info
It is clear for me is that it is not a perfect solution to use nvflash with images that you do not know the source.
The tegra S.O.C. use the information from a file stored in partition#2 to configure some low level setting like flash memory chip speed, total memory installed, video memory installed, flash type etc. As an example, if for some reason a batch of tablet is built with more memory then the .bct files will need to be changed accordingly
It is already confirmed that there's at least 2 different type of hardware. (2 different images by bekit do not use the same .bct configuration)
When flashing after a full wipe after using the create command, nvflash read the .bct configuration files and store it in the partition #2 on the tablet, bct files are created by the manufacturer using a tool from nvdia called buildbct. They are not writen during regular nvflash (where the partition are not re-created)
This also mean it is MUCH safer to NOT replace the partition 2 when nvflashing a device... (the hardware configuration would not be touched).
This batch files will work under windows and will not modify your tablet in anyway
please make sure you use the nvflash tools that is 151K there's an older and smaller one in some package, it will output binary inside the partition.txt instead of plain text. The version 2 include everything you need to backup the device under windows
Thanks to the various poster of thread about nvflash for the correct command THEY did the hard work not me !
To Restore individual partition the command is
"nvflash.exe" --bl bootloader.bin --download X partX.img
where X is the partition number you wish to flash, as stated you can also use your backup from clockwork mod for partition 11 restore.
this will not work for partition below 4
P.S.
I am not trying to start a debate on the validity of the current recovery (thumb-up to the guy who offered those!) They are valid for MOST device however
if you do have a different device this will alleviate any issue that may happen with nvflash restore.
see 2 post below for full restore info
Hi,
I know that the partitiontable shows a partition named "BCT", but is there also something else, perhaps flashed into the SOC itself that is referred to as "the BCT"?
The reason for the question is that nvflash has a setbct and a getbct command, separate from the read and download commands, which work with the partitions.
Jim
Reserved
(will be completed a bit later)
so, we possibly share more internals with the 10s than previously expected? maybe... can we get this thing to dual boot in the future??
10roller said:
so, we possibly share more internals with the 10s than previously expected? maybe... can we get this thing to dual boot in the future??
Click to expand...
Click to collapse
My guess is yes, the platform of the ac100 laptop by toshiba is tegra based and they do it!
P00r said:
The set bct command probably write the 4080 byte to the partition named bct in the cfg, I have yet to test flashing a dummy FF filled partition with the command to confirm the flash.bct get writen there
So in fact when you restore with the nvflash restore images from bekit I think you are actually writing it twice... (it is in the image and you telling the nvflash to create it) but I have not confirmed this yet
Once the bct info is there, the SOC read his configuration there, as well as the ODM info, I have not found a way to use --getbct that reads back the BCT from mass storage yet...
I am not sure either why there's so many section being flashed it should work with only a few of those (I plan to test this) since nvflash is simply puting those one after the other. It make sense only sense for a dual booting unit
Click to expand...
Click to collapse
Hi,
I was able to get --getbct to output a 2048 byte file awhile ago. I think I had posted about it, but, sorry, I don't remember which thread. The only thing I vaguely remember was that I had to use some unobvious combination of parameters. Also, I think that it only worked right after pushing the bootloader.bin. If I find my post, I'll provide a link.
Jim
Thanks OP, I like the idea of being able to back up the partitions directly from my tablet so I know I'm restoring the proper thing should I ever have to resort to that.
Just starting to get into modding this thing after it showed up from Woot yesterday, been planning on buying one for quite some time to compliment my Epic 4g and when the woot sale dropped I had to jump on it. So far all I have done is flash clockwork, and make a nandroid backup with that. Also doing this backup method now.
So have you actually done a successful restore using this method?
so is it possible to back up your original hardware configuration and restore it when you got problems???
Yes and NO, I have error reading partition #11 (system) on my tablet (bad block)
if I use it as is for restore, it doesn't restore and boot, however replacing this partition with clockwork system.img backup give me back a full working tablet.
I can also reboot into recovery and restore from there.
Letters and numbers oh my
I ran the backup on my new replacement GTab yesterday. I had a size mismatch on partition 5, everything else backed up properly. Also, my partition 7 is BLO and partition 6 is MSC. Thanks for the script and capability.
Mike
P00r said:
This also mean it is MUCH safer to NOT replace the partition 2 when nvflashing a device... (the hardware configuration would not be touched). I will post later on how to flash back those if someone request it...
Click to expand...
Click to collapse
Instructions on how to flash back using this would be great. I'd like to have the option to do so if I need to, but haven't gotten familiar enough with nvflash yet to figure it out on my own.
iamchocho said:
Instructions on how to flash back using this would be great. I'd like to have the option to do so if I need to, but haven't gotten familiar enough with nvflash yet to figure it out on my own.
Click to expand...
Click to collapse
You can flash back the partition using
"nvflash.exe" --bl bootloader.bin --download X partX.img
where X is the partition number you wish to flash, as stated you can also use your backup from clockwork mod for partition 11 restore.
If needed you can use the nvflash format kit prior to restoring however it would be better to use your own .bct with that option
Getting stuck at partition 7.
xkwwwx said:
Getting stuck at partition 7.
Click to expand...
Click to collapse
What is the error you are getting ?
stock recovery image
Thank you very much for the sharing this.
Now I have 10 img files (part-2 to part-11)... wich one is the stock recovery image? I did this before installing clockwork mod...
Thanks!
I think this is fantastic. Gives us a chance to backup our gtab before deciding to try a new rom. I tried this today in the hopes to backup and then install the flashback HC rom. But unfortuntaly it stopped on image 7, as xkwwwx has also mentioned. The message seemed to be a issue with the size expected of the image as to what was received. Ill try and copy the message.
"nvflash.exe" -r --read 7 part-7.img
nvflash started
[resume mode]
receiving file: part-7.img, expected size: 16777216 bytes
/ 131072/16777216 bytes received
At that point it stops, and i have to control c to exit the batch file. Id love to be able to backup with this pls, so i can try another rom, and know i can use this to return to this rom if i dont like the new one, any chance this can be resolved pls ?
Was also wondering if some form of GUI maybe of benifit, i know alot of people feel wary of NVFlash, perhaps with a GUI people would feel more comfortable using it. Maybe a simple screen with a backup and restore set of buttons ?
P00r, any chance you can help mate ? Cant use this unfortunatly because of the image size issue.
Icedvoco said:
P00r, any chance you can help mate ? Cant use this unfortunatly because of the image size issue.
Click to expand...
Click to collapse
This mean you probably have a bad block in this section, try skipping it to get the other parts first. this is not a major issue, you may also encounter one in the last data section (my tablet has a few byte less than the regular one)
For the data partition you can substitute the cwm images
Also try using a different bootloader and nvflash this can help even shorter usb cable or a different one can help
The part that you can read is probably usable for a restore anyway
Bad block are not unusual in flash and I have seen a few with this, ideally and usually it's located at the end, you could try using the format image a few time it could be a stuck byte and writing different data can revive it (format write FF all over)
P00r said:
This mean you probably have a bad block in this section, try skipping it to get the other parts first. this is not a major issue, you may also encounter one in the last data section (my tablet has a few byte less than the regular one)
For the data partition you can substitute the cwm images
Also try using a different bootloader and nvflash this can help even shorter usb cable or a different one can help
The part that you can read is probably usable for a restore anyway
Bad block are not unusual in flash and I have seen a few with this, ideally and usually it's located at the end, you could try using the format image a few time it could be a stuck byte and writing different data can revive it (format write FF all over)
Click to expand...
Click to collapse
Bad blocks may be common, but bad blocks in the exact same spot probably not. I get the exact same thing:
"nvflash.exe" -r --read 7 part-7.img
Nvflash started
[resume mode]
receiving file: part-7.img, expected size: 16777216 bytes
/ 131072/16777216 bytes received
Any other thoughts on this?
Maybe someone here knows,
So with NVflashing, I've found only one file that has the alternative BCT (it's a tnt1.0 rom on BL1.1) and no other NVflash file sets work without causing a APX bootloop.
This is the NVflash file set that works for me http://db.tt/FvSeAZj
Ive read it was made when someone was trying to configure for the hardware variations.
Now is it possible to take my backup and insert just the files needed into another NVflash file set?
Related
How to Access HPA
How to access HPA Partiton and extract all driver
Hello all.
I need Recovery Partition on English.
I talk with Pof he say that me must English Recovery partiton.
Please Send to my.
Thanks in advance!!!
I have sent the copy of my HPA partition to danielherrero which was hagving the same problem as you, and he could recover his vista with it, the problem is that my recovery partition installs a Spanish language Vista, which will not be good for you (as you might not understand spanish), so if someone could dump an HPA in english, this would be useful to people who lost it.
Instructions to dump and restore the recovery partition are on my blog:
http://pof.eslack.org/blog/2008/04/...re-the-vista-recovery-partition-on-htc-shift/
I can if acess to FTP/HTTP server for upload a Image and all software for HTC Shift and access for all people needet
pof said:
I have sent the copy of my HPA partition to danielherrero which was hagving the same problem as you, and he could recover his vista with it, the problem is that my recovery partition installs a Spanish language Vista, which will not be good for you (as you might not understand spanish), so if someone could dump an HPA in english, this would be useful to people who lost it.
Instructions to dump and restore the recovery partition are on my blog:
http://pof.eslack.org/blog/2008/04/...re-the-vista-recovery-partition-on-htc-shift/
Click to expand...
Click to collapse
hello
i dont mind doing that on my english shift..ive had quick look at the page discribing how to do it but being a bit of a thicko it would great if you could send step by step destructions for me..i have the capability of loading it onto external drive where i could give you access to upload..please advise me if you wish
pof said:
I have sent the copy of my HPA partition to danielherrero which was hagving the same problem as you, and he could recover his vista with it, the problem is that my recovery partition installs a Spanish language Vista, which will not be good for you (as you might not understand spanish), so if someone could dump an HPA in english, this would be useful to people who lost it.
Instructions to dump and restore the recovery partition are on my blog:
http://pof.eslack.org/blog/2008/04/...re-the-vista-recovery-partition-on-htc-shift/
Click to expand...
Click to collapse
Yes, It saved my shift from SAT and several weeks out of home. Thanks again Pau
pd: Remove SD when dumping/restoring....
It takes 4 hours to dump or restore.
Pau....Maybe when I copied your fist MB did the trick?
plasticplanet said:
hello
i dont mind doing that on my english shift..ive had quick look at the page discribing how to do it but being a bit of a thicko it would great if you could send step by step destructions for me..i have the capability of loading it onto external drive where i could give you access to upload..please advise me if you wish
Click to expand...
Click to collapse
Basically you need:
~1Gb USB stick
~3,5 Gb of free space on your Vista partition
1) Install Slax on the USB pendrive, follow instructions here:
http://www.pendrivelinux.com/2006/09/20/all-in-one-usb-slaxzip/
2) Reboot your Shift
3) Press Fn+F10 to choose the boot device, select USB pen drive
4) Slax boot menu will appear, choose the first option (KDE)
5) Open a Konsole (Terminal program), right next to the "K" menu in the menu bar.
6) Type the following command:
Code:
# dd if=/dev/hda of=/dev/hda1/shift-vista-recovery.bin bs=1 skip=36773560320
7) This will last about 4 hours, keep your Shift on charger and wait until it finishes. When it finishes you'll see something similar to this:
Code:
3226976256+0 records in
3226976256+0 records out
3226976256 bytes (3.2 GB) copied, 11938 s, 270 kB/s
8) Now reboot into Vista again, the backup of the HPA holding the vista recovery will be in c:\shift-vista-recovery.bin
9) Zip or Rar the 'shift-vista-recovery.bin' file and upload it somewhere, keep in mind this is a big file so you might want to split it in several volumes before uploading it.
10) There is no 10
That's all, feel free to ask if some point is not clear enough.
On Privet messegi send to Pof and plasticplanet FTP access for upload a HPA Partition on English or ES.
pof said:
6) Type the following command:
Code:
# dd if=/dev/hda of=/dev/hda1/shift-vista-recovery.bin bs=1 skip=36773560320
7) This will last about 4 hours
Click to expand...
Click to collapse
not really 4 hours, for me that only did 98MB in 4 hours, and I had to use /mnt/hda1 anyway.
so tell me why is bs set to 1?
is bs=16384 fine? because that's how i did it in the end.
any way to verify the contents?
P.S: oh yes and my shift is hardspl'ed man!!
Probably I am in wrong but that command is dumping the last 3GiB of hda disk to the first partition of the same partition. Wouldnt be safer to dump to the sd or a usb pen?
no, the source is /dev so the hw device, like the whole hdd on windows
and the dest is /mnt/hda1 so the partition like C: on windows
the HPA "partition" is not part of the visible partition. no risk....
and the proper and FAST command is (if you are using the slack usb distro that pof linked to in his description) :
dd if=/dev/hda of=/mnt/hda1/shift-vista-recovery.bin bs=16384 skip=2244480
I assume similar method works for copying it back (the point is bs=16384).
if you want to be sure your shift has a partition of the exact same size, then read dmesg until you find the HPA (host protected area) information, should say what it said for pof and for me:
sda: Host Protected Area detected.
current capacity is 71826615 sectors (36775 MB)
native capacity is 78126048 sectors (40000 MB)
sda: Host Protected Area disabled.
sda: 78126048 sectors (40000 MB), CHS=16383/255/63
(ignore the "sda" part of course)
someone downloaded the backup I uploaded and confirmed it works.
cmonex said:
so tell me why is bs set to 1?
is bs=16384 fine? because that's how i did it in the end.
Click to expand...
Click to collapse
"bs" was set to 1 because I was too lazy to do the maths
Yes, you can increase it as long as you change the "skip" part too.
I have a problem.
I have two shift devices, one got screwed trying to install ubuntu MID and the other one is fine
I've tried your method with dd to the to copy the recovery partition from the working shift however it always fails during the fn f3(same failure that I got even before restored the image). IT starts the restore but fails somewhere along the line at 2%.
I noticed my hpa is at a slightly different location to yours using dmesg. Probably because it has office in it. How do I calculate the seek/skip
Also I tried doing a dd from higher on the drive just to see if I can atleast pick it up as excess got the same error.
Any help guys
btw good work on everything else you all have done
ok i got it..you guys were slightly off in your calculations so i wasn't sure that the address you got was by 512. Anyhow I have the .bin dump for anyone who needs it for the vista with office demo or those who partition size is different to that of the above postings. I also took it a little higher just to ensure i don't miss any of the partition
BTW posting from the previously bricked shift
Could you please stick this thread.
pof
Could you please stick this thread too. It has a lot of useful information.
Thanks
Ram
Hi there
if someone have a german Recovery partition Image for me, please let me know
My new HTC Shift has a Recovery Partiton but don´t boot with this. Don´t know why.
Maybe a recover of this partition may be work
But only for testing, i have made (before starting the Shift first time) a complete Acronis Image
I have a somewhat related question. I've basically busted my Vista recovery partition, long story short, I decided to try out ubuntu mid and didn't realize it was going to wipe my whole hdd (installed on my other laptops the regular images of ubuntu hardy and it asked me to specify partitions etc., but the mid didn't and I was half awake or vice versa).
I have now installed XP, and even though ubuntu mid appears to have wiped the HPA, it is still hidden from windows. I don't plan on going back to Vista (if I have to, I will just throw the thing out, xp just gave it a new lease on life). Is there a safe and easy way to unhide the hidden partition and use it, without having to install linux and without affecting my XP install (took too long to get it running and I'd rather give up the 3GB than have a go at it again, at least not until I really have to)?
I suppose I managed to unhide it, whiped it out and put it together with the rest of my HDD. Though now I used about 3GB with Acronis and created my own hidden/protected partition with XP completely set-up and some essential software. Worked like a charm.
Restore recovery partition
What is the correct command for restoring the rescovery partition bin file?
I used "dd if=/dev/hda of=/mnt/hda1/shift-vista-recovery.bin bs=16384 skip=2244480" to create the dump file.
I need you.
Hello.
I had installed ubuntu 8.04 and it run good, but the resolution was horrible.
With vista, the virtual resolution permits work without external panel, for not very long time, of course.
I don't now what i do wrong, and now i can't recovery the Vista by the recovery partition. I have installd a Vista Bussiness from a copy and with the activation key from my htc shift and it works good.
I wouid like recovery the recovery partition of my htc.
know you where i could get the "shift-vista-recovery.bin" image from?
thanks. and "help" me please
I hope this information is useful to you. It allowed me to restore my phone, after flashing the 2.3.5BETA from Huawei, effectively reverting the process. If you follow these procedures, you do so at your own risk. A typo in the needed commands may render your phone useless, so if you feel uneasy DON'T DO IT! That being said, on with the show.
Rationale: The U8800's memory is accessible as a mass storage device, when the phone is powered up in pink screen mode. This device holds the boot sector, partitions, operating system and user data. As such, it can be treated as any other block device and can be imaged to a file, through a bit-by-bit copy. The inverse is also possible and thus constitutes a valid backup/restore method.
Motives: Some weeks ago, I imaged my U8800 having in mind that spending time flashing ROMs, recovery and boot images could at some point go wrong and brick the device. Having a full dump of the device, done while it was in good working condition, would give me a chance of disaster recovery.
Requirements: Linux box and familiarization with Linux. I use Slackware 13.37 x86_64, but any flavour of Linux should do.
1 - Enter pink-screen mode by pressing power + vol up + vol down;
2 - Connect the USB cable. I recommend using the USB ports on the back of your PC (irrelevant if it's a laptop) as some PC cases have inadequate wiring to the front ports and will only allow slow data transfer. I've done it all while logged in as root, and not running X. If you're running X and HALD (automount of CD's and USB sticks, etc), you should unmount whatever units get automaticaly mounted when you plug the U8800 in. Avoid X if possible;
3 - Run 'dmesg' to ensure your U8800 was correctly detected. last output on screen should look like this:
[ 4444.026295] usb 1-2: New USB device found, idVendor=12d1, idProduct=1035
[ 4444.026300] usb 1-2: New USB device strings: Mfr=3, Product=2, SerialNumber=0
[ 4444.026304] usb 1-2: Product: Qualcomm CDMA Technologies MSM
[ 4444.026308] usb 1-2: Manufacturer: Qualcomm, Incorporated
[ 4444.029209] usb 1-2: selecting invalid altsetting 1
[ 4444.029265] scsi4 : usb-storage 1-2:1.20
[ 4445.031474] scsi 4:0:0:0: Direct-Access Qualcomm MMC Storage 2.31 PQ: 0 ANSI: 2
[ 4445.031755] sd 4:0:0:0: Attached scsi generic sg2 type 0
[ 4445.034576] sd 4:0:0:0: [sdb] 7733248 512-byte logical blocks: (3.95 GB/3.68 GiB)
[ 4445.035947] sd 4:0:0:0: [sdb] Write Protect is off
[ 4445.035952] sd 4:0:0:0: [sdb] Mode Sense: 0f 0e 00 00
[ 4445.035956] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[ 4445.042568] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[ 4445.053569] sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 sdb6 sdb7 sdb8 sdb9 sdb10 sdb11 sdb12 sdb13 sdb14 >
[ 4445.059328] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[ 4445.059335] sd 4:0:0:0: [sdb] Attached SCSI removable disk"
"sdb" is the device name alocated to the U8800. It can be "sdc", "sdd", "sde". Depends on the number of block devices (hard disks, USB sticks, card readers, etc) already present on your system.
4 - If your U8800 is showing up in "dmesg"' output, you are ready to create the image file, by typing "dd if=/dev/sdb of=u8800.img bs=512". Remeber: this example assumes the device name to be "sdb", yours may be different. If all goes well, you'll end up with the "u8800.img" file in the current directory. This is a 4GB transfer so it will take some time and there will be no progress indicator whatsoever. Final output should look like:
3959420000 bytes (3866621 KB) copied, [ time spent], [KB/s] ( These figures vary according to your transfer speed )
If the transfer fails, the output will show how many bytes were transfered along with the indication that there was an error; should it indicate an error, retry from the beginning, using a different USB port.
The resulting u8800.img file can be ziped, gziped, bziped, rared, whatever to reduce it's size to around 600 MB.
4A - This concludes the backup part;
5 - Having hold of the u8800.img file, you can restore it back to your U8800. Connecting and finding the device name of your mobile through the output of "dmesg" is the same as for backup and is described in (1), (2) and (3). To restore it, and assuming the img file resides in the current directory, type "dd if=u8800.img of=/dev/sdb bs=512". Don't forget to decompress the file in case you ziped it. Again, your device name may be other than "sdb".
Since writing to flash memory is a slower process than reading it, this operation will take longer than performing the backup. As an example, mine took around 45 minutes to complete, while other user reported 25 minutes for the same operation.
BEWARE: There's no way to perform a sanity check of the img file you're dumping back! Those commands will hapilly flash an Excel spreadsheet to your mobile's memory if you give it as a parameter to the "dd" command!
Final words
I used this method to revert to a pre 2.3.5BETA state. Huawei's update wrote a new bootloader, which is something not included in CWM backups and restores. Furthermore: CWM restores showed up errors about mountpoints. Ignoring these errors and performing a factory reset would allow FROYO to boot up and run, but my carrier's costumizations, which reside in the same volume as boot.img, and restore.img, were ignored afterwards. I didn't want this to be used as an argument by the carrier to consider my warranty void, should I need it...
Cheers
First of all, thanks for your tut, it's very helpfull for those who have linux
I have a question
The u8800.img contains all partition data?
Thanks in advance, regards
sewa2k said:
First of all, thanks for your tut, it's very helpfull for those who have linux
I have a question
The u8800.img contains all partition data?
Thanks in advance, regards
Click to expand...
Click to collapse
Yes. You can mount the image through /dev/loop and run fdisk on it to see the partition table.
There are windows tools to accomplish the same tasks of byte-copying to a file and vice-versa, but I haven't used them, since it was straight-forward with Linux.
Cheers
Thank you very much for this tutorial.
But what about us who have not made this backup when we had the original froyo and flashed the original 2.3.5?
I have several CWM backups but none of them works(it keeps booting in recovery mode or not booting at all),unless i restore to factory data which is useless.
Can you or someone else please upload a clean froyo backup so we can flash it and go back to our 2.2 backups via CWM?
bonowax said:
Yes. You can mount the image through /dev/loop and run fdisk on it to see the partition table.
There are windows tools to accomplish the same tasks of byte-copying to a file and vice-versa, but I haven't used them, since it was straight-forward with Linux.
Cheers
Click to expand...
Click to collapse
Thanks m8, i'll do it tonight, so i can start to porting roms to U8800-51
Wow nice. I was waiting for something like this. I ran "sudo -i" before the process and it's copying right now. This is good for recovering the phone in case of soft brick.
That was a great tutorial! Thank you!
I did it on an Atom netbook last night, booting Linux from a USB thumb drive.
I saved the image on an external USB ntfs HDD, that it had to first be mounted, of course. I had to to this because the internal disk is an 8GB SSD with no room for a 4GB image file.
The imaging process took about 25 minutes on this machine, with all 3 USB 2.0 ports occupied (Boot USB drive, u8800, external USB drive). Transfer speed was about 2.7 MB/s.
Right now I'm trying to compress it with 7zip (maximum) and at 65% progress it has a 45% compression ratio (output/total). (The phone has many apps installed (1GB) and also I have the ndrive folder on the internal memory as a backup in case there is a problem with the ext SD.)
So I suggest you, to do the backup on an empty phone if possible, if you want the smallest size for your image.
Regards.
sport_billy said:
Thank you very much for this tutorial.
But what about us who have not made this backup when we had the original froyo and flashed the original 2.3.5?
I have several CWM backups but none of them works(it keeps booting in recovery mode or not booting at all),unless i restore to factory data which is useless.
Can you or someone else please upload a clean froyo backup so we can flash it and go back to our 2.2 backups via CWM?
Click to expand...
Click to collapse
It should be possible to dump and restore only the first two partitions, in which case it would make a much smaller up/download. This would restore the previous bootloader and allow CWM to operate normally ( or at least I hope so ).
I'll look into it.
EDIT: I dumped primary partitions 1, 2 and 3 to a image file which is around 140 MB after ziped. This could be enough to restore the old bootloader. "Could" is the keyword here, as it assumes the partition scheme is the same in every U8800.
bonowax can you please upload it so we can give it a try?
I am having bootloops even with the new beta v2 they released today.
So your solution is the only way to revert back to 2.2 .
sport_billy said:
bonowax can you please upload it so we can give it a try?
I am having bootloops even with the new beta v2 they released today.
So your solution is the only way to revert back to 2.2 .
Click to expand...
Click to collapse
you could just install stock 2.2 firmware normal way ... easy as that
Sent from my u8800 using XDA App
Yes but if i restore my CWM backup after flashing via the classic method it keeps rebooting in recovery mode.
So it is useless and it also means that it is not completely the same as before.
Some people mentioned having issues after flashing 2.2 with the classic method .
I want to try the method mentioned here.
sport_billy said:
bonowax can you please upload it so we can give it a try?
I am having bootloops even with the new beta v2 they released today.
So your solution is the only way to revert back to 2.2 .
Click to expand...
Click to collapse
Unfortunately there is the IMEI issue. I don't know where it is stored, and dumping from phone to phone might not be a good idea, unless we're talking about two devices you can actually get a hold of AND you do a full backup of both devices prior to any experiments...
Many, many thanks for posting this tutorial.
I ended up with a unformatted 4GB drive after trying to revert genokolar's custom partition script due to boot loops with the 2.3 beta. Luckily I had done a backup via this method so I was able to restore it successfully.
Be warned that it takes a long time to restore the full 4GB, well over an hour on my phone. I had almost given by the time it had finished.
I would definitely recommend this to anyone who wants to try any custom roms or messing around with scripts. I just wish I'd done it when my phone was completely stock.
Excellent!
I actually did a dd backup before 2.3.5 upgrade, but I didn't dare to restore it. Now I know it worked for you
I started the phone in bootloader mode and WOW, my Ubuntu crashes. It gives some kernel message and the display is completely messed up. It worked before, but it made my computer not shut down properly. Any help is appreciated.
Blefish said:
I started the phone in bootloader mode and WOW, my Ubuntu crashes. It gives some kernel message and the display is completely messed up. It worked before, but it made my computer not shut down properly. Any help is appreciated.
Click to expand...
Click to collapse
I was not able to use Ubuntu 11 - it auto mounted all the partitions and like you crashed when trying to dismount them.
I have tried every way to stop this auto mount behaviour - looking in all the forums I could find, but nothing worked, so yesterday I grabbed LinuxLive USB creator, http://www.linuxliveusb.com/ and used it to create a live Puppy Linux on my usb stick, it runs sweetly on my laptop (booting from the USB drive not running it using the vbox option inside Windows).
It immediately recognises all the U8800 partitions but does not automount them.
I ran the dd command after navigating in terminal to a spare folder on my laptop hard drive (after mounting the laptop hard drive with Puppy's useful mounter app), and now I have a u8800.img on my laptop hard drive! Perfect!
Oh - and of course once again - EVERY time I have used pink screen mode on my U8800 with the latest Stock Beta 2 Gingerbread, it re-boots ok but the SD card is gone. Booting into recovery mode and wiping the Dalvik cache is the way to solve this - it is now completely predictable and after doing this I am back to a really great phone - faster, cooler, great camera and video, BBC iPlayer etc.
will this method work also on u8800pro?
Isn't it the same of going to the pink screen, open the image directory and do a backup of all files in it?
BTW, the problem is that we need to go to the pink screen to restore the phone, right?
Inviato dal mio u8800pro usando Tapatalk
matteof93 said:
will this method work also on u8800pro?
Isn't it the same of going to the pink screen, open the image directory and do a backup of all files in it?
BTW, the problem is that we need to go to the pink screen to restore the phone, right?
Inviato dal mio u8800pro usando Tapatalk
Click to expand...
Click to collapse
Simply copying the image is not enough, full copy (dd) backups system, cache, even IMEI, if I am not mistaken.
Easiest way is of course copying when in pink screen, but with some hacking it should be possible in Android aswell.
Sent from my U8800 using Tapatalk
Blefish said:
Simply copying the image is not enough, full copy (dd) backups system, cache, even IMEI, if I am not mistaken.
Easiest way is of course copying when in pink screen, but with some hacking it should be possible in Android aswell.
Sent from my U8800 using Tapatalk
Click to expand...
Click to collapse
but we already have a way to downgrade from 2.3.5 to 2.2.2 on u8800pro using update.app and update_g.app
matteof93 said:
but we already have a way to downgrade from 2.3.5 to 2.2.2 on u8800pro using update.app and update_g.app
Click to expand...
Click to collapse
Well if for example for reason x the partition table gets messed up or anything else, you can restore everything back with dd. If you can get into the pink screen.
Sent from my U8800 using xda premium
Hi Everyone,
after experiencing the reboot problem and then acceidentaly bricking the tablet I managed to unbrick my tablet (or better a friend managed).
Now though, the storage is 16GB instead of 32GB
My question now: how can I get the tablet back to 32GB?
Thanks for the help
I think you probably need to update either the transformer.bct file or odmdata for the 32gb version. I *believe* that these set things like memory size and other hardware parameters, although I'm not sure which one controls what. Unfortunately, I don't know where you would find these either. Maybe if you ask nicely and ask the right people at ASUS, they might send it to you.
EDIT- It's probably the bct. I forgot there is a getbct command in nvflash- you could ask someone who has a working 32gb version to extract theirs and see if it works for you. Note there are no guarantees that this will work since nvflash might not be fully implemented on the tf. You'll probably need to get comfortable with the command line. Prepackages scripts and one click solutions will probably not work in this case.
Code:
--getbct
reads back the BCT from mass storage
--setbct
updates the chip specific settings of the BCT in mass storage to
the bct supplied,used with --create, should not be with --read,and
--format(delete)_all,format(delete)_partition,--download, and--read
http://androidroot.mobi/technical/tf-secure-boot-key/
Code:
In order to get a working (e.g. --create) nvflash, we need a few bits of information as well as some files:
Secure Boot Key
[B] BCT file (boot device setup, ram configuration and a bit more)[/B]
ODM data (board-specific bit-field specifying various board settings. *Needs* to be correct
flash.cfg (e.g. list of settings and names/identifiers of partitions.
So I can't just re-flash nvflash with the proper settings? just seems a bit easier
On another note, does anybody have a working bct file? :fingers-crossed:
I think the proper settings are in the bct file.
Thanks for the help. I have found in other sources that it seems to be indeed in the bct file, so that is confirmed
Unfortunatly, that is all I could find out till now
I am sort of stuck on now getting a bct file for a TF101 with 32GB. Either that, or I am not copying it over properly. I am sort of at a lost here. I would appreciate any help
I have a sprint phone that can only get into bulk mode. I followed this guide: http://forum.xda-developers.com/showthread.php?t=2582142 and everything works fine except for the dd command. When I write to a partition (well at least aboot and recovery since those are the only 2 I've tried) and then cmp the image to the partition I just wrote to only the first 64k bits match out of the 1MB partition. I've tried ubuntu fatdog and gparted and all have the same problem. What's weirder is that before I borked my phone I used the Zv8_aboot.img that is around and when I just try to rewrite that image it is still only the first 64k bits that match so it's like I'm not writing to the write part of the partition because the img and the partition should match.
I didn't make a backup of the aboot partition before doing all of this so if anyone else has a sprint phone with a ZV8_aboot.img in the aboot partition, and has access to bulk mode can you use dd to make an image of the partition so that I can try to at least get my aboot back? After that I'll try this: http://forum.xda-developers.com/showthread.php?t=2708466&page=2 to get into fastboot.
Also, for anyone else that has no download mode and no recovery you can get into bulk mode by going into factory reset mode. I can't remember the exact button presses for that but after you are in and you hit power 3 times your phone shouldn't reset (you might have to have a custom recovery installed for that to be the case though) but it will end up going into bulk mode; it did for me anyway.
sorry for responding to my own thread, the edit of the 1st post just wasn't saving
Alternatively does anyone know an alternative to DD?
Update:
Tried on different computer, tried with my tongue sticking out at a 33 degree angle, tried with ddrescue, always the same thing..... fts
Update
I finally looked at the entire hex file for aboot and I found that it seems to write everything fine except for the bits between 65537 and 122880, 64k-120k or sectors 129 to 240 given 512bit sector sizes. This seems really odd. I think my only hope would be getting a good aboot from someone's sprint and writing only to the other sectors and not 129 to 240. Even then I might have to figure out if 129 through 240 aren't changed or are somehow purposefully scrambled when written to through hardware.... this is so lame.
So if you have a sprint phone with a zv7 or zv8 aboot and can get into bulk mode I'd very much like a copy of your aboot.img when you do a raw copy of it using dd.
going to reply to myself cause
I need to help someone in the development forum, so I need 6 more posts to post there
more self posting
self posting is natural there's no need to be ashamed
man this is annoying why 10 posts
If anyone can help me to create a loop back device that maps to the sectors in question, I'd appreciate the help.
ya, i setup a loop back device
losetup -o 65536 --sizelimit 57344 /dev/loop3 /dev/sdi5
Omg it has worked so far!!!!
setting up a loopback device over the sectors that weren't writing correctly has so far worked for aroot... I think I want to do the same for the recovery and see my phone actually boot first though
Works but.....
This is going to take forever, I guess I better figure out how to right scripts since I'm manaully putting in 4 commands to go 64k at a time out of 16MB.... fml
SOLVED
I did it my way..... oh franky
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?