I messed up u8800 internal partitions. Tried to restore the official b526, b518, b137 with no luck. I think I need to repartition the whole internal memory (emmc) and put the right images to those partitions. The problem is I don’t know how and I don’t have the images. FYI, I have access to the pink screen.
Please help me...
Thank in advance!
__________________________________________
UPDATE WITH SOLUTION:
Disclaimer:
If you follow these procedures, you do so at your own risk. A typo in the needed commands may render your phone useless.
Requirements:
u8800 with accessible pink screen
linux box
Download HUAWEI_U8800_FullFlash.rar and extract it
Steps:
Pull out the battery and sdcard from your phone.
Connect your phone using USB cable to your computer while pressing the vol up and vol down to get to the Pink Screen.
Unmount any newly mounted disks/partitions of your phone.
Do in Terminal
Code:
sudo dd if=/path/to/HUAWEI_U8800_FullFlash.bin of=/dev/device_name
with "device_name" is the device name alocated to the U8800. It can be "sdb", "sdc", "sdd", "sde", etc.
Code:
Example (my case):
[email protected] ~ $ sudo dd if=/media/Data/u8800/HUAWEI_U8800_FullFlash.bin of=/dev/sdc
Wait for it... It took me 1,5 hours!
Code:
Output (my case):
[email protected] ~ $ sudo dd if=/media/Data/u8800/HUAWEI_U8800_FullFlash.bin of=/dev/sdc
7733248+0 records in
7733248+0 records out
3959422976 bytes (4.0 GB) copied, 5402.43 s, 733 kB/s
[email protected] ~ $
After the "long" process completed, disconnect your phone from your computer.
Reboot your phone and enjoy official 2.2 on your phone.
Thanks to Blefish, bonowax for his tutorial, and medusa!
Hope it can help others.
What did you do exactly? Maybe we can revert the process and fix it without wiping the device.
Blefish said:
What did you do exactly? Maybe we can revert the process and fix it without wiping the device.
Click to expand...
Click to collapse
I changed the system, data, and internal_sdcard with Minitool Partition Wizard to make the system partition 512mb just like my gnex.
Do you think the method mentioned in the thread [TUT] Full U8800 backup with Linux howto can solve this? Do you have a “clean” u8800.img? I can restore my IMEI with 5irom toolbox.
Edit:
Blefish said:
Yes, this backup has full Android dump, with modem partitions (IMEI and such), also the bootloader and splash screen images.
As long as you have pink screen access, you can restore the backup and your phone will be just like it used to be before.
Click to expand...
Click to collapse
buzzcomp said:
I changed the system, data, and internal_sdcard with Minitool Partition Wizard to make the system partition 512mb just like my gnex.
Click to expand...
Click to collapse
And now Android does not boot?
buzzcomp said:
Do you think the method mentioned in the thread [TUT] Full U8800 backup with Linux howto can solve this? Do you have a “clean” u8800.img?
Click to expand...
Click to collapse
Yes, the method described there would work. The problem is, I don't have my device to do it and upload it. I will do it with a proper tutorial when I get my device back, but for now you should prepare a Linux environment (Ubuntu for ex.), either install it or do a live CD/USB stick. We can recreate the last 3 partitions, I have the default sizes with block numbers for start/end. I will post the full tutorial tomorrow, I have to recheck the commands.
Blefish said:
And now Android does not boot?
Click to expand...
Click to collapse
Yes, it doesn't boot. No huawei logo whatsoever, only like the attached image.
Blefish said:
Yes, the method described there would work. The problem is, I don't have my device to do it and upload it. I will do it with a proper tutorial when I get my device back, but for now you should prepare a Linux environment (Ubuntu for ex.), either install it or do a live CD/USB stick. We can recreate the last 3 partitions, I have the default sizes with block numbers for start/end. I will post the full tutorial tomorrow, I have to recheck the commands.
Click to expand...
Click to collapse
I have live Linux Mint.
buzzcomp said:
Yes, it doesn't boot. No huawei logo whatsoever, only like the attached image.
I have live Linux Mint.
Click to expand...
Click to collapse
I believe the full wipe is the only thing to do in this case as it doesn't seem to even find mmcblk0p5. I believe this did not work?
With device connected to pc, check which /dev/sdX it is in dmesg and do in Terminal "fdisk -p /dev/sdX" with X replaced with the correct character. Copy the output here.
Blefish said:
I believe the full wipe is the only thing to do in this case as it doesn't seem to even find mmcblk0p5.
Click to expand...
Click to collapse
I believe so...
Blefish said:
I believe this did not work?
Click to expand...
Click to collapse
Already tried that and yes, it didn't work.
Blefish said:
With device connected to pc, check which /dev/sdX it is in dmesg and do in Terminal "fdisk -p /dev/sdX" with X replaced with the correct character. Copy the output here.
Click to expand...
Click to collapse
Working on it ... Done.
[email protected] ~ $ sudo fdisk /dev/sdc
Command (m for help): p
Disk /dev/sdc: 3959 MB, 3959422976 bytes
255 heads, 63 sectors/track, 481 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x60c808d5
Device Boot Start End Blocks Id System
/dev/sdc1 1 31 245760 b W95 FAT32
Partition 1 does not end on cylinder boundary.
/dev/sdc2 * 31 31 500 4d QNX4.x
Partition 2 does not end on cylinder boundary.
/dev/sdc3 31 32 3000 46 Unknown
Partition 3 does not end on cylinder boundary.
/dev/sdc4 32 480 3606339+ f W95 Ext'd (LBA)
/dev/sdc5 33 35 12288 59 Unknown
/dev/sdc6 41 58 133120 4c Unknown
/dev/sdc7 66 66 500 5a Unknown
/dev/sdc8 74 74 3072 58 Unknown
/dev/sdc9 82 83 7000 50 OnTrack DM
/dev/sdc10 90 91 3072 4a Unknown
/dev/sdc11 98 99 3072 4b Unknown
/dev/sdc12 100 127 224878+ 83 Linux
/dev/sdc13 128 204 618471 83 Linux
/dev/sdc14 205 480 2216938+ b W95 FAT32
Solved it!
Solution in the OP.
Nice. What about the IMEI/Wi-Fi mac address? Did you have to restore it or is it the same?
Blefish said:
Nice. What about the IMEI/Wi-Fi mac address? Did you have to restore it or is it the same?
Click to expand...
Click to collapse
Yes, I have to restore my own IMEI.
sorry, i've the pink screen but there isn't anything appearing in ubuntu, nothing to unmount, i don't if i can explane myself. (see atachment)
Uglamugla said:
sorry, i've the pink screen but there isn't anything appearing in ubuntu, nothing to unmount, i don't if i can explane myself. (see atachment)
Click to expand...
Click to collapse
I’m not an expert of Linux, however check if your phone’s disk/partitions are detected by your Linux machine. Maybe they’re not auto-mounted in Ubuntu.
In my case using Linux Mint, some of my phone’s disk/partitions were auto-mounted when connected, so it had to be unmounted just to be safe.
Open GParted. If you see like the attached image then you’re good to go. You can proceed to the next steps.
Good luck.
My Phone was bricked cause the Data Partition was totally messed Up.
Now its working again!!!
Thanks buzzcomp for your awesome guide!!! :laugh:
mitsosc said:
My Phone was bricked cause the Data Partition was totally messed Up.
No its working again!!!
Thanks buzzcomp for your awesome guide!!! :laugh:
Click to expand...
Click to collapse
You're welcome
For u8800PRO
Dows anyone have, or make a full phone backup for the u8800PRO?
I had one, that I made the first day I bought the phone,
but my HDD failed and now that I need it I don' t have it
PS: I have a backup from my IMEI so restoring that will not be a problem....
And here is the how to, if anyone willing to help...
buzzcomp said:
You're welcome
Click to expand...
Click to collapse
Hmm...Sorry I'm totally a newbie to Linux~
I've downloaded the FullFlash, so how to locate the file?
Hope you can solve my question :good:
3.Unmount any newly mounted disks/partitions of your phone.
how do i do it?
No Pink
I was wondering if Ubuntu could solve my issue if I have no Piink screen. My phone will not turn on ever since i tried to do the update. It said that the updated failed so i turned the phone off and then nothing. No matter what I do it (pull battery 3 button restart or 2 button restart plugged in to pc or not) all I get is a small vibration no screens no nothing just a buzz. Do you think this will work for me? If not could you direct me to the proper technique? I have been searching and searching with no luck. Thanks in advance for any help.
What? So do I need Linux system to restore full flash?
Edit. Now sudo command is working but [email protected] isn't. How to enable that in windows? Guide isn't very good at all, very difficult to understand.
Edit 2: Step 4 is weird. Do I need to write both of those commands to cmd or just the first one?
MerkTheMedia said:
I was wondering if Ubuntu could solve my issue if I have no Piink screen. My phone will not turn on ever since i tried to do the update. It said that the updated failed so i turned the phone off and then nothing. No matter what I do it (pull battery 3 button restart or 2 button restart plugged in to pc or not) all I get is a small vibration no screens no nothing just a buzz. Do you think this will work for me? If not could you direct me to the proper technique? I have been searching and searching with no luck. Thanks in advance for any help.
Click to expand...
Click to collapse
So Lets See Here..... your phone is Not Recognized in Pink Screen or You Cant get in Pink Screen.????
---------- Post added at 10:04 AM ---------- Previous post was at 10:01 AM ----------
Raineruf said:
What? So do I need Linux system to restore full flash?
Edit. Now sudo command is working but [email protected] isn't. How to enable that in windows? Guide isn't very good at all, very difficult to understand.
Edit 2: Step 4 is weird. Do I need to write both of those commands to cmd or just the first one?
Click to expand...
Click to collapse
i think its only one Command, any One Whichever Works..
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 all,
I tried yesterday this mod, messing with swap and stuff at the sd card and installed swapper2 from market, but after hitting "on" at the app and tried to reboot, my phone died... and by that I mean completely died...
It doesn't power up, it doesn't boot at CWM neither at bootloader (pink screen).
When I plug it to the charger nothing happens and it doesn't get recognised by the PC also.
I tried booting without the sd card, i tried reformatting it (with swap or without swap) but again... nothing.
I tried to flash the stock firmware (dload folder at sdcard and stuff) but again it doesn't start the bootloader...
Any suggestions before I through it off the window much appreciated
EDIT: I was on latest Aurora...
You may have better luck accessing it through Linux.
If you can get access then you can restore a dd backup from someone.
That program uses root, right? And you put swap partition as mmcblk0p2?
If so, then it simply replaced your main bootloader with the swap file and you have to take it to repair service.
The correct way would've been to use mmcblk1p2, as external SD uses mmcblk1.
m!xal!s said:
You may have better luck accessing it through Linux.
If you can get access then you can restore a dd backup from someone.
Click to expand...
Click to collapse
All the above where done with Linux.
Blefish said:
That program uses root, right? And you put swap partition as mmcblk0p2?
If so, then it simply replaced your main bootloader with the swap file and you have to take it to repair service.
The correct way would've been to use mmcblk1p2, as external SD uses mmcblk1.
Click to expand...
Click to collapse
That is exactly what it did... I will sent it to service then ... I hope my 1 year warranty covers this... Thanks
If anyone knows a way to change the bootloader manually I would love him forever...
spirosbond said:
If anyone knows a way to change the bootloader manually I would love him forever...
Click to expand...
Click to collapse
You have to get phone boot from USB and then use USB JIG which contains bootloader to boot phone and then use some flash tool to flash bootloader to phone. It's very hard and I have no idea how get it boot from USB. Another solution is write bootloader directly to internal sd. I can't help you more.
Sent from my U8800 using Tapatalk 2
Can someone upload the mmcblk0p2 file? I think is inside /dev/block/ folder.
Does anyone knows how to boot something from the sd card? I don't know what... another ROM, another OS...
Thanks a lot.
http://db.tt/Qb32A8Z0
I know how to boot my galaxy tab from USB but I don't know about u8800.
Sent from my U8800 using Tapatalk 2
Qqqxxxzzz said:
http://db.tt/Qb32A8Z0
I know how to boot my galaxy tab from USB but I don't know about u8800.
Sent from my U8800 using Tapatalk 2
Click to expand...
Click to collapse
Can you post here what do you do to boot your tab from USB, and then I may find something based on that... who knows...
I just can't think of a way of booting it up. I tried to make the sdcard bootable disk with cm7 but again I cannot start the phone (or make it boot from sdcard). Copying mannually the bootloader seems easy but again I have no idea who I can acces that partition of the phone....
Thank you all for the help/tips
spirosbond said:
Can you post here what do you do to boot your tab from USB, and then I may find something based on that... who knows...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1312391
I think it will not work in u8800 because I don't believe that u8800 has iROM and OM pins.
Sent from my U8800 using Tapatalk 2
spirosbond said:
Can you post here what do you do to boot your tab from USB, and then I may find something based on that... who knows...
I just can't think of a way of booting it up. I tried to make the sdcard bootable disk with cm7 but again I cannot start the phone (or make it boot from sdcard). Copying mannually the bootloader seems easy but again I have no idea who I can acces that partition of the phone....
Thank you all for the help/tips
Click to expand...
Click to collapse
Can you try to make a partition on your sd card and dd the bootloader to that partition? After that, give the partition a bootable flag with fdisk and insert to phone. Try to start in many different variations, press the volume keys etc. If the soc bootloader has enabled a function to boot from sd card, somehow it would boot.
The emmc is soldered onto the motherboard. I don't think there are any ways to desolder it or replace.
Of course there must be another way to boot directly from sd card by using some pins, but I have not taken my phone apart to seek on that. Might do it someday though.
JTAG is the thing that would help you definately, but I don't think you have that and the box is pretty expensive too.
-EDIT-
I found this link, it says the phone should go in emergency download mode if loading flash disk fails, do you get any messages in Windows or by listing lsusb in Ubuntu do you get any result when connected with USB? There has to be a way to boot that emergency mode.
Blefish said:
Can you try to make a partition on your sd card and dd the bootloader to that partition? After that, give the partition a bootable flag with fdisk and insert to phone. Try to start in many different variations, press the volume keys etc. If the soc bootloader has enabled a function to boot from sd card, somehow it would boot.
Click to expand...
Click to collapse
I 've tried some things like that but it didn't work. I will try with the bootloader. Should I dd the bootloader.bin from here? I was using this mod since I f***** things up.
fdisk is something I'm not familiar with. Can you let me know how to "give the partition a bootable flag" please? Thanks !
Blefish said:
The emmc is soldered onto the motherboard. I don't think there are any ways to desolder it or replace.
Of course there must be another way to boot directly from sd card by using some pins, but I have not taken my phone apart to seek on that. Might do it someday though.
Click to expand...
Click to collapse
That would be so cool but I don't want to risk any chance of loosing my warranty (if I haven't already) .
Blefish said:
JTAG is the thing that would help you definately, but I don't think you have that and the box is pretty expensive too.
Click to expand...
Click to collapse
Ohh I wish I had one of these things...
Blefish said:
-EDIT-
I found this link, it says the phone should go in emergency download mode if loading flash disk fails, do you get any messages in Windows or by listing lsusb in Ubuntu do you get any result when connected with USB? There has to be a way to boot that emergency mode.
Click to expand...
Click to collapse
I don't get any indication when I connect the phone to any OS. I will send it to service tommorow and if nothing happens I will give it a try then, because it seems little complicated.
I will try the first thing you suggested (with the bootable bootloader) today. If you could answer the above question of mine it would be great
I can't thank you enough... We are lucky having you at our community.
Cheers man
I'm currently learning how to use Fdisk in unbutu to fix my own problem: http://forum.xda-developers.com/showthread.php?t=1694914
Here's something that may help you out:
https://help.ubuntu.com/community/InstallingANewHardDrive
1) Initiate fdisk with the following command:
sudo fdisk /dev/sdX
2) Fdisk will display the following menu:
Command (m for help): m <enter>
Command action
a toggle a bootable flag
b edit bsd disklabel
c toggle the dos compatibility flag
d delete a partition
l list known partition types
m print this menu
n add a new partition
o create a new empty DOS partition table
p print the partition table
q quit without saving changes
s create a new empty Sun disklabel
t change a partition's system id
u change display/entry units
v verify the partition table
w write table to disk and exit
x extra functionality (experts only)
Command (m for help):
For: sudo fdisk /dev/sdX, where sdX is the disk or partition you want to modify.
If you don't know the disk or partition name, "ls /dev/sd*" should list all drives attached to the system.
From there, just use:
Command action
a toggle a bootable flag
I have not tried this, because I don't need to, but it seems to be what you're looking for. Hope it works for you.
If someone has better information, then please add to this. I just started learning unbuntu yesterday, and may not be completely correct.
If I come across anything that may help you, I'll let you know, and hope you'll do the same for me.
UPDATE: Also try disk utility in ubuntu. It's a lot easier and it has a gui.
Another UPDATE: http://www.thegeekstuff.com/2010/09/linux-fdisk/
Look for "6. Toggle the Boot Flag of a Partition Using fdisk Command a"
Thank you all. My phone has been fixed under warranty. They said that they changed the main board... Who knows... All good for now.
Thanks again!
spirosbond said:
Thank you all. My phone has been fixed under warranty. They said that they changed the main board... Who knows... All good for now.
Thanks again!
Click to expand...
Click to collapse
So there's no way for me to fix this myself without resorting to warranty?
S3nd41 said:
So there's no way for me to fix this myself without resorting to warranty?
Click to expand...
Click to collapse
Did you try the above solutions? If you did but no hope, then all you can do is send your phone to warranty.
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
Hello!
I have rooted my phone today. i wanted to install some rom but first I tried to install TWRP so I can back it up. I tried a few different methods and tools, but nothing worked. Eventually I followed this tutorial: http://www.android.gs/install-twrp-recovery-lg-g2/ (I don't know if I'm allowed to posts links here...) about 5 times because everytime I forgot something. It still didn't work so I just give up. I re-booted my phone and I noticed some error in upper left corner, along with LG logo. But I still could boot it if I keep pressing power button. After that, some update showed up (I don't know which... :/) so i installed it and re-booted. And then there was error "secure booting error boot certification verify" and nothing works. I tried every combinations possible but I still cant boot it. The only thing that shows up is that error and LG logo and then it goes black (but it's still on). When I connect it to my PC it creates 12 empty 'local disk' and one 63,9 mb local disk (with folder 'image' and files in it). I tried this already: http://forum.xda-developers.com/showthread.php?t=2582142 using VirtualBox + Unbuntu but i'm stuck at the beginning. When I type "ls /dev/sd*" it only shows me the first " /dev/sda /dev/sda1 /dev/sda2 /dev/sda5 " and nothing else...
I'm seriously pissed off at me right now, last time I bricked my phone 2 years ago and I promised myself not to ever play with any of this stuff and now I got my new phone and screw it up next day. Yeah I got it for one day and I screwed it up already.
I'm freaking out, can someone please help me?
It might be you have sent the recovery Image to the wrong partition, in the mean time you will have to read what you have done, and maybe see if you selected something incorrectly, you may have to get another phone while you see if you can fix the broken one. I take it you have tried all boot options and no reset is available ?
I recently broke a working phone it is annoying, but you live and learn.
Sent from my Nexus 7 using XDA Free mobile app
prophice said:
Hello!
I have rooted my phone today. i wanted to install some rom but first I tried to install TWRP so I can back it up. I tried a few different methods and tools, but nothing worked. Eventually I followed this tutorial: http://www.android.gs/install-twrp-recovery-lg-g2/ (I don't know if I'm allowed to posts links here...) about 5 times because everytime I forgot something. It still didn't work so I just give up. I re-booted my phone and I noticed some error in upper left corner, along with LG logo. But I still could boot it if I keep pressing power button. After that, some update showed up (I don't know which... :/) so i installed it and re-booted. And then there was error "secure booting error boot certification verify" and nothing works. I tried every combinations possible but I still cant boot it. The only thing that shows up is that error and LG logo and then it goes black (but it's still on). When I connect it to my PC it creates 12 empty 'local disk' and one 63,9 mb local disk (with folder 'image' and files in it). I tried this already: http://forum.xda-developers.com/showthread.php?t=2582142 using VirtualBox + Unbuntu but i'm stuck at the beginning. When I type "ls /dev/sd*" it only shows me the first " /dev/sda /dev/sda1 /dev/sda2 /dev/sda5 " and nothing else...
I'm seriously pissed off at me right now, last time I bricked my phone 2 years ago and I promised myself not to ever play with any of this stuff and now I got my new phone and screw it up next day. Yeah I got it for one day and I screwed it up already.
I'm freaking out, can someone please help me?
Click to expand...
Click to collapse
Will your phone enter download mode? While it's fully powered down, hold the volume down and plug in a usb cable that's plugged into your pc. If you can get there, you're OK, there are options.
Sent from my LG-D800 using Tapatalk
After you do the dvb and it gives out 5 partitions, have you tried typing the name of the largest which would be 5 and seeing what happens
Sent from LG-G2 D800 on AEONFLEX 4.4.2
fatcarrotcake said:
It might be you have sent the recovery Image to the wrong partition, in the mean time you will have to read what you have done, and maybe see if you selected something incorrectly, you may have to get another phone while you see if you can fix the broken one. I take it you have tried all boot options and no reset is available ?
I recently broke a working phone it is annoying, but you live and learn.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
One thing that comes to my mind is that maybe the recovery image is not comptabilite with my phone. I know that when I tried to install TWRP with TWRP Manager it gave me an error when I chose g2d802 in device name so I didn't do it. The first link (tutorial I used) I posted, I used "openrecovery-twrp-2.7.0.0-d802" but I'm 99% it's the right one for my phone?
Jank4AU said:
Will your phone enter download mode? While it's fully powered down, hold the volume down and plug in a usb cable that's plugged into your pc. If you can get there, you're OK, there are options.
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
Unfortunately it doesn't enter download mode...
XxZombiePikachu said:
After you do the dvb and it gives out 5 partitions, have you tried typing the name of the largest which would be 5 and seeing what happens
Sent from LG-G2 D800 on AEONFLEX 4.4.2
Click to expand...
Click to collapse
You mean that "/dev/sda /dev/sda1 /dev/sda2 /dev/sda5" thing? I did that but it doesn't do nothing.
PLEASE can someone else reply? I seriously don't know what to do.
prophice said:
PLEASE can someone else reply? I seriously don't know what to do.
Click to expand...
Click to collapse
Try this method
Then boot from the usb stick(don't install ubuntu..just boot)
open terminal
copy and paste this - line by line (enter)
gconftool-2 --type bool --set /apps/nautilus/preferences/media_automount False
gconftool-2 --type bool --set /apps/nautilus/preferences/media_automount_open False
Then follow the instructions
prophice said:
The only thing that shows up is that error and LG logo and then it goes black (but it's still on).
Click to expand...
Click to collapse
At that point, press and hold the power button for 30 seconds to make sure its off completely. Then try download mode again. If you've already been doing that, disregard.
bender_007 said:
Try this method
Then boot from the usb stick(don't install ubuntu..just boot)
open terminal
copy and paste this - line by line (enter)
gconftool-2 --type bool --set /apps/nautilus/preferences/media_automount False
gconftool-2 --type bool --set /apps/nautilus/preferences/media_automount_open False
Then follow the instructions
Click to expand...
Click to collapse
I used that tutorial and Im in ubuntu atm, but i dont think it is detecting my lg at all. When using -ls /dev/sd*- its now showing -/dev/sda /dev/sda1 /dev/sda2 /dev/sdb /dev/sdb1- And when using -gdisk -l /dev/sdb- it gives me
[email protected]:~$ sudo gdisk -l /dev/sdb
GPT fdisk (gdisk) version 0.8.5
Partition table scan:
MBR: MBR only
BSD: not present
APM: not present
GPT: not present
***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format.
***************************************************************
Warning! Secondary partition table overlaps the last partition by
33 blocks!
You will need to delete this partition or resize it in another utility.
Disk /dev/sdb: 15630336 sectors, 7.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): AB4CD8FE-B964-4DCD-8AF2-43C5051BC71D
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 15630302
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)
Number Start (sector) End (sector) Size Code Name
1 2048 15630335 7.5 GiB 0700 Microsoft basic data
Click to expand...
Click to collapse
and
[email protected]:~$ sudo gdisk -l /dev/sdb1
GPT fdisk (gdisk) version 0.8.5
Partition table scan:
MBR: MBR only
BSD: not present
APM: not present
GPT: not present
***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format.
***************************************************************
Exact type match not found for type code F400; assigning type code for
'Linux filesystem'
Exact type match not found for type code 1000; assigning type code for
'Linux filesystem'
Exact type match not found for type code 7400; assigning type code for
'Linux filesystem'
Warning! Secondary partition table overlaps the last partition by
3454418421 blocks!
You will need to delete this partition or resize it in another utility.
Disk /dev/sdb1: 15628288 sectors, 7.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): A3BCA950-18FB-4E37-9B41-0F662D454416
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 15628254
Partitions will be aligned on 1-sector boundaries
Total free space is 15628221 sectors (7.5 GiB)
Number Start (sector) End (sector) Size Code Name
1 3223366752 3470046675 117.6 GiB 8300 Linux filesystem
2 378192737 710426324 158.4 GiB 8300 Linux filesystem
3 225603442 225603451 5.0 KiB 8300 Linux filesystem
Click to expand...
Click to collapse
And also now when conected lg the ecran is flashing between black and very black,
And I used the lines you gave me obviously but I dont think it did anything,
Any messages popping up?
Sent from my LG-D802 using XDA Premium 4 mobile app
Nope, nothing.
OK it works!!!! I guess all I had to do is get some sleep and think fresh. =) Now that I'm in TWRP i'd like to install a rom, Am I safe to do it? I was thinking about Pardus HD but I have 2 questions.
1. I'm in TWRP but the computer doesn't detect my phone, how i am supposed to copy PardusHDC_7.1.zip to my phone?
2. it says "Upgrade your Recovery to TWRP 2.7.0.0 or Latest Philz Recovery" in installation guide, I have v2.6.3.2, will that make any difference?
Adb push pardushdc...zip /sdcard/pardus.zip
Sent from my LG-D802 using XDA Premium 4 mobile app
Ok I got it but before I start installing Id still like to know if im safe to do it with my current TWRP version?
prophice said:
Ok I got it but before I start installing Id still like to know if im safe to do it with my current TWRP version?
Click to expand...
Click to collapse
I think you need to update recovery or else install will just fail because of outdated files
Sent from LG-G2 D800 on AEONFLEX 4.4.2
It didn't work on v2.6.3.2 but it did on v2.7 and oh god I flashed that rom and it works!!!!! This is awesome, I don't know how I can thank you for all that help!!
please now make a backup and put it somewhere ie pc,usb stick,meenova safe, im glad you got it sorted and i know exactly how you felt as ive been in that situation a few times!!
prophice said:
OK it works!!!! I guess all I had to do is get some sleep and think fresh. =)
Click to expand...
Click to collapse
How do you make it? Please, I am stuck on this.
Please help dude....
prophice said:
OK it works!!!! I guess all I had to do is get some sleep and think fresh. =) Now that I'm in TWRP i'd like to install a rom, Am I safe to do it? I was thinking about Pardus HD but I have 2 questions.
1. I'm in TWRP but the computer doesn't detect my phone, how i am supposed to copy PardusHDC_7.1.zip to my phone?
2. it says "Upgrade your Recovery to TWRP 2.7.0.0 or Latest Philz Recovery" in installation guide, I have v2.6.3.2, will that make any difference?
Click to expand...
Click to collapse
Hi, I am facing the exact same issue as you described. I am using a LG G2 D802 international version. I did everything I could find on the internet. Could you please help me by telling how you got it working?? I am using a bootable USB of ubuntu and lsusb is showing my phone as Qualcomm 9006 but when I type ls /dev/sd* it is not giving me the device due to which I could not push the partition files. Please dude help me it has been 5 days since I am trying. You can PM me on my email [email protected]
Thanks in advance
---------- Post added at 11:07 AM ---------- Previous post was at 10:57 AM ----------
bender_007 said:
Try this method
Then boot from the usb stick(don't install ubuntu..just boot)
open terminal
copy and paste this - line by line (enter)
gconftool-2 --type bool --set /apps/nautilus/preferences/media_automount False
gconftool-2 --type bool --set /apps/nautilus/preferences/media_automount_open False
Then follow the instructions
Click to expand...
Click to collapse
Hi,
I saw your reply on the post which is related to the same issue I am facing since last 5 sleepless nights . I have a LG G2 D802 international variant and it had kitkat 4.4.2 earlier which I have successfully rooted. I recently received an OTA which I clicked to update [worst day of my life ] after that my phone is stuck in boot loop and rest you know. I trying to use ubuntu to push the partition files and recovery, but my phone is not detectable in ubuntu. lsusb is showing my phone as Qualcomm 9006 but when I type ls /dev/sd* it is not showing my phone. I saw your method in the quote and tried this also but it is still not working . Could you please let me know how can I solve this? Also by using the commands above does the phone needs to be connected or not ?? Please help me . You can PM me on [email protected].
Thanks is advance
Hello, i suggest to download vmware and slax ISO and run slax inside vmware. Then try the instructions. I can assist you but on monday , sorry
Poslano sa mog LG-D855 koristeći Tapatalk