Most of the threads surrounding Streakdroid address Windows users. While the nvflash commands are identical, the method for getting nvflash set up is very different on a Linux based system. Additionally, there is no bash shell script included to flash the device.
PREPARATION
Device *must* be in APX mode. You do NOT need to install any drivers.
To put the device in APX mode:
1) Power off the device.
2) Disconnect the cable from the device.
3) Press and hold BOTH Volume buttons.
4) Press and hold the Power button.
The hardware buttons of the Streak will start to glow approx 8 seconds after pressing the power button.
If the buttons glow right away you may not be not in APX mode.
Now connect the device to your USB port.
As of August 19, 2011 this is the latest Linux for Tegra
Instead of using tar directly for file extraction I prefer unp. You may of course extract files any way you like.
Extract nvflash and drop it in your $PATH. I used /usr/local/bin/
Code:
$ unp tegra-linux-12.alpha.1.0.tar.gz
$ su
# cp ldk/bootloader/nvflash /usr/local/bin/
Download the latest Streakdroid / Honeystreak
(get the wifi-only if you have that device)
FLASHING
Prior to flashing, you'll need to copy the appropriate Region_**.img to RC_download.img. I'm in the US so:
Code:
$ unp Streakdroid-HD7-2.0R2-wifionly.zip
$ cd Streakdroid\ HD7-2.0R2-wifionly/
$ cp region_img/RC_us.img RC_download.img
Currently, there are 4 different partitioning schemes contained within the .cfg files. The gb quantity refers to how much space is alloted to internal app storage. This partition will be mounted to /data. The remainder will be mounted to /mnt/sdcard
Code:
android_2gb.cfg
android_5gb.cfg
android_4gb.cfg
android_3gb.cfg
Once you've chosen your preferred partition layout use nvflash to flash your Streak 7 calling that specific .cfg from the nvflash command.
Flash as root!
Code:
$ su
# nvflash --bct Streak7.bct --setbct --configfile android_4gb.cfg --create --bl bootloader.bin --odmdata 0x8b0c0011 --go
A sample output from nvflash
Code:
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x028040c642e13517
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: Streak7.bct
- 4080/4080 bytes sent
Streak7.bct sent successfully
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 1208404/1208404 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: EB1
creating partition: NVC
creating partition: NV1
creating partition: MBR
creating partition: SOS
creating partition: LNX
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: FDR
creating partition: UDA
creating partition: OLG
creating partition: LGF
creating partition: RES
creating partition: RGN
creating partition: VAR
creating partition: USP
creating partition: SDC
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 EB1 please wait.. done!
Formatting partition 6 NVC please wait.. done!
Formatting partition 7 NV1 please wait.. done!
Formatting partition 8 MBR please wait.. done!
Formatting partition 9 SOS please wait.. done!
Formatting partition 10 LNX please wait.. done!
Formatting partition 11 APP please wait.. done!
Formatting partition 12 CAC please wait.. done!
Formatting partition 13 MSC please wait.. done!
Formatting partition 14 FDR please wait.. done!
Formatting partition 15 UDA please wait.. done!
Formatting partition 16 OLG please wait.. done!
Formatting partition 17 LGF please wait.. done!
Formatting partition 18 RES please wait.. done!
Formatting partition 19 RGN please wait.. done!
Formatting partition 20 VAR please wait.. done!
Formatting partition 21 USP please wait.. done!
Formatting partition 22 SDC please wait.. done!
done!
sending file: bootloader.bin
| 1208404/1208404 bytes sent
bootloader.bin sent successfully
sending file: bootloader.bin
| 1208404/1208404 bytes sent
bootloader.bin sent successfully
sending file: microboot.bin
\ 115880/115880 bytes sent
microboot.bin sent successfully
sending file: microboot.bin
\ 115880/115880 bytes sent
microboot.bin sent successfully
sending file: recovery.img
/ 3612672/3612672 bytes sent
recovery.img sent successfully
sending file: boot.img
- 3459072/3459072 bytes sent
boot.img sent successfully
sending file: system.img
/ 352321536/352321536 bytes sent
system.img sent successfully
sending file: logfilter.img
\ 131072/131072 bytes sent
logfilter.img sent successfully
sending file: RC_download.img
- 120/120 bytes sent
RC_download.img sent successfully
sending file: variables.img
- 144/144 bytes sent
variables.img sent successfully
Once all files have been 'sent', press and continue to hold the Power button until the device powers on.
Partition layout after using the 4gb.cfg file:
Code:
Filesystem Size Used Available Use% Mounted on
tmpfs 182.5M 32.0K 182.5M 0% /dev
tmpfs 182.5M 0 182.5M 0% /mnt/asec
tmpfs 182.5M 0 182.5M 0% /mnt/obb
/dev/APP 330.7M 217.6M 113.1M 66% /system
/dev/UDA 3.9G 428.1M 3.5G 11% /data
/dev/CAC 108.4M 9.4M 99.0M 9% /cache
/dev/SDC 10.2G 793.6M 9.4G 8% /mnt/sdcard
*Note* Disc space usage above does not reflect disc usage after a fresh flash.
Good work man.
An hero! My S7 wouldn't boot, fastboot or boot into recovery. Had to reflash via nvlfash with your instructions. Thanks.
Related
Hey my LG Optimus 2x P990 has a full brick (black screen, only ). I try to fix it with "progmaq-default-cm-10-20121105" Tool from this Site.
http://forum.xda-developers.com/showthread.php?t=1975274
But everytime i try it, i get a error.
Code:
ProgMaq LG Optimus 2X (P990) repairer
========================================
* Remove the battery.
* Simultaneously press Vol+ and Vol- and connect the microUSB cable to device.
* Wait 5 seconds and stop pressing Vol+ and Vol-.
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x02888884477745d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
sending file: 0-bct-settings.bct
- 4080/4080 bytes sent
0-bct-settings.bct sent successfully
odm data: 0xc8000
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: 0-fastboot.img
/ 1024992/1024992 bytes sent
0-fastboot.img sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MBR
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: EB1
creating partition: LNX
creating partition: EB2
creating partition: DRM
creating partition: EB3
creating partition: SOS
creating partition: EB4
creating partition: UDA
creating partition: EB5
creating partition: UDB
failed executing command 12 NvError 0x120002
command failure: create failed (bad data)
bootloader status: fatal failure to read / write to mass storage (code: 9) messa
ge: nverror:0x42008 (0x19042008) flags: 0
Can anybody help me to repair my phone please? :angel:
If you are able to access the recovery mode then directly flash a rom n gapps it would help i guess try it
Good luck
Sent from my LG-P880 using xda app-developers app
Try with this rom http://forum.xda-developers.com/showthread.php?t=1715272
This rom, will erase all you data, and return to gb
Hey there!
I hope you could help a total beginner getting his phone working again.
The whole thing started a couple of weeks ago when my optimus had several factory resets and was so slow I couldn't use it any longer.
I sat down and searched on the interwebz for a solution and the answer I got was: Put a different ROM on it, then it will be a SOLID phone.
So after some fiddling I got CM7 on it, but I couldn't use the Play store, and I eventually got an error which kept popping up all the time so I was, once again, unable to use the phone.
Then I thought, Hey! This wasn't that hard, maybe I'll try something else!
Well, it was.
I tried getting Jellybam on it, but because I'm a total idiot I did a complete wipe of the phone so I had no OS installed (I took no backup of course)
I've tried and I've tried to fix it but quite frankly I'm at a loss.
This is the error I get:
__________________________________________________________________________________________
The phone will display a S/W download.. screen,
while the command-window will inform you of the progress.
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x02884182415fb057
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
download command failed NvError 0x120002
command failure: bootloader download failed (bad data)
bootloader status: Bct file not found (code: 21) message: flags: 1073844220
An error occured. Read above lines for details.
** Remove the usb-cable from the phone. **
press a key when ready and retry from step 2.
________________________________________________________________________________________
I use this phone daily at work and it's been a real pain in the bum to not have it
Can anyone please help me? I would be very grateful!!!
Thank you for your time!
This could help
So if ur able to access the recovery mode just flash this rom http://forum.xda-developers.com/showthread.php?t=216719 . It is as far the most stable rom for p990 as per my usage and also install proper cm10.1 gapps. dont nv flash the phone see the instructions for wiping !
This might fix you problem try it
Hey! Thanks for the response!
It seems the link to the thread is dead unfortunately
I am not able to reach recovery mode.
http://forum.xda-developers.com/showthread.php?t=2020737
Try this. this phone is unbrickable.
Sent from my LG-P990 using xda premium
wawyed said:
http://forum.xda-developers.com/showthread.php?t=2020737
Try this. this phone is unbrickable.
Sent from my LG-P990 using xda premium
Click to expand...
Click to collapse
Hey!
It's unbrickable?! That's great!!
I've tried out the toolkit and I'm trying to use function 4 (Partitions), the problem is that it gets stuck sending the bootloader, it looks like this;
==============================================================
Change layout to NEW ICS Partition layout (Point of NO Return)
==============================================================
The phone will display a S/W download.. screen,
while the command-window will inform you of the progress.
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x02884182415fb057
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
sending file: star.bct
- 4080/4080 bytes sent
star.bct sent successfully
odm data: 0xc8000
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1027184/1027184 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MBR
creating partition: AP2
creating partition: CAC
creating partition: EB1
creating partition: MSC
creating partition: EB2
creating partition: LNX
creating partition: EB3
creating partition: DRM
creating partition: EB4
creating partition: SOS
creating partition: EB5
creating partition: UDA
creating partition: EB6
creating partition: VE
creating partition: EB7
creating partition: UDB
creating partition: EB8
creating partition: APP
creating partition: EB9
creating partition: FOT
creating partition: SWP
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 MBR please wait.. done!
Formatting partition 6 AP2 please wait.. done!
Formatting partition 7 CAC please wait.. done!
Formatting partition 8 EB1 please wait.. done!
Formatting partition 9 MSC please wait.. done!
Formatting partition 10 EB2 please wait.. done!
Formatting partition 11 LNX please wait.. done!
Formatting partition 12 EB3 please wait.. done!
Formatting partition 13 DRM please wait.. done!
Formatting partition 14 EB4 please wait.. done!
Formatting partition 15 SOS please wait.. done!
Formatting partition 16 EB5 please wait.. done!
Formatting partition 17 UDA please wait.. done!
Formatting partition 18 EB6 please wait.. done!
Formatting partition 19 VE please wait.. done!
Formatting partition 20 EB7 please wait.. done!
Formatting partition 21 UDB please wait.. done!
Formatting partition 22 EB8 please wait.. done!
Formatting partition 23 APP please wait.. done!
Formatting partition 24 EB9 please wait.. done!
Formatting partition 25 FOT please wait.. done!
Formatting partition 26 SWP please wait.. done!
done!
sending file: ics-bootloader.bin
I've waited for 1 hour and the phone doesn't seem to recieve the bootloader
Any tips?
Thanks!
have you tried to change it back to Old Bootloader?
I also encountered this problem ages ago, my solutions was NVFlashing a Stock Froyo ROM from Modaco. I was also a complete idiot back then
Ok, I've fixed it now!
What I did was to try a different USB-port, After I did that the file was sent succesfully,
thank you for your supportl!
castpnt said:
Ok, I've fixed it now!
What I did was to try a different USB-port, After I did that the file was sent succesfully,
thank you for your supportl!
Click to expand...
Click to collapse
THANK YOU!!!! i did the same and it worked!
Good job you guys!
you just Zombified your phone!
Hello –
Thanks in advance for reading and any help you can provide..
my phone is currently dead ... I’ve managed searched xda forums/internet and downloaded various NV Flash and read a bunch of threads and guides but still need some help.
I can hold vol up and down and plug the phone in to my computer (win 7)
Windows loads the APX device (ive checked device manager and the drivers are successfully installed.
(USB Controllers reads - NVIDIA USB Boot - recovery driver for mobile devices)
Driver version 1.0.1.0
NV Flash starts and the phone changes from a blank screen to “S/W Upgrade please wait while upgrading…”
but I’m getting an error part way through the nvflash sending the system img.. see below
ive tried a couple of different system images / nvflash guides and im still struggling
sending file: 1-system.img
- 166002688/358400000 bytes sentdata send failed NvError 0x120002
command failure: create failed (bad data)
Please let me know if theres some additional information which I can provide that will maybe help resolve this.
Code:
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x028841c842df3157
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
sending file: 0-bct-settings.bct
- 4080/4080 bytes sent
0-bct-settings.bct sent successfully
odm data: 0xc8000
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: 0-fastboot.img
/ 1024992/1024992 bytes sent
0-fastboot.img sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MBR
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: EB1
creating partition: LNX
creating partition: EB2
creating partition: DRM
creating partition: EB3
creating partition: SOS
creating partition: EB4
creating partition: UDA
creating partition: EB5
creating partition: UDB
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 MBR please wait.. done!
Formatting partition 6 APP please wait.. done!
Formatting partition 7 CAC please wait.. done!
Formatting partition 8 MSC please wait.. done!
Formatting partition 9 EB1 please wait.. done!
Formatting partition 10 LNX please wait.. done!
Formatting partition 11 EB2 please wait.. done!
Formatting partition 12 DRM please wait.. done!
Formatting partition 13 EB3 please wait.. done!
Formatting partition 14 SOS please wait.. done!
Formatting partition 15 EB4 please wait.. done!
Formatting partition 16 UDA please wait.. done!
Formatting partition 17 EB5 please wait.. done!
Formatting partition 18 UDB please wait.. done!
done!
sending file: 0-fastboot.img
/ 1024992/1024992 bytes sent
0-fastboot.img sent successfully
sending file: 1-system.img
- 166002688/358400000 bytes sentdata send failed NvError 0x120002
command failure: create failed (bad data)
seems like repeating many times is good for you. its failed again but this time got a lot further.
going to keep trying.
input the battery after start is OK.
my friend,
have you tried the AIOT...link in my signature (I have used the V5 version many times...dont know about the v5.5)...read the thread and you will have more info
but, there are tools and ROMs which are based on the NVflash method....progmaq's NVflash and unbrick tool, Homero's NVflash, Stefan's NVflash ROM....
LG O2X is almost unbrickable....so try it
Hi!
It seems like your usb ports dont like your phone. I have the same problem. Every time I try to flash full nvflash rom or flash stock rom or basbeband with smartflash it keeps failing. Nvflash showes the same error which you have and smartflash always write time out errors. I dont know why is this keep happening. The only solution for me is using usb3 ports. Strange, isn't it?
So if you have usb3 port try that. If you dont have usb3 port download aio-toolkit from the development section and use it to repartitionate your phone then flash a custom rom. I think aoi-toolkit should work because it does not take too long, so the timeout error will not happen
Sent from my LG-P990 using xda app-developers app
SREEPRAJAY said:
my friend,
have you tried the AIOT...link in my signature (I have used the V5 version many times...dont know about the v5.5)...read the thread and you will have more info
but, there are tools and ROMs which are based on the NVflash method....progmaq's NVflash and unbrick tool, Homero's NVflash, Stefan's NVflash ROM....
LG O2X is almost unbrickable....so try it
Click to expand...
Click to collapse
bitdomo said:
Hi!
It seems like your usb ports dont like your phone. I have the same problem. Every time I try to flash full nvflash rom or flash stock rom or basbeband with smartflash it keeps failing. Nvflash showes the same error which you have and smartflash always write time out errors. I dont know why is this keep happening. The only solution for me is using usb3 ports. Strange, isn't it?
So if you have usb3 port try that. If you dont have usb3 port download aio-toolkit from the development section and use it to repartitionate your phone then flash a custom rom. I think aoi-toolkit should work because it does not take too long, so the timeout error will not happen
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
Hi guys, thanks for the replies
I've tried the AOI toolkit that got me so far, before i used that i couldn't even get anything on the phone screen
I've resolved the issue now - but for those who come across this thread bitdomo was kinda correct with my phone and USB. heres the stuff i tried before it finally worked
tried every usb port on my laptop
the same port multiple times
using the LG cable which came with my phone and other usb cables -
it finally worked when i used a new cable which came with my nexus 4 in one of the USB port at the side of my laptop.
not sure what the problem was but i know some usb cables arent the same as others - and some can provide more power - why the cable which came with my phone didnt work i dont know.
Thanks
Hi Guys,
been trying different USB Ports since yesterday, 3 different PCs with USB 2.0 and three different Cables, LG Original, Sony Xperia Arc S and a SGS3 Cable, but with every Cable I get the NvFlash error with "Bad Data".
Code:
sudo nvflash --bct 0-bct-settings.bct --setbct --odmdata 0xC8000 --configfile progmaq-default-partitions.cfg --create --bl 0-fastboot.img --go
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x0288414143604097
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
sending file: 0-bct-settings.bct
- 4080/4080 bytes sent
0-bct-settings.bct sent successfully
odm data: 0xc8000
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: 0-fastboot.img
/ 1024992/1024992 bytes sent
0-fastboot.img sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MBR
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: EB1
creating partition: LNX
creating partition: EB2
creating partition: DRM
creating partition: EB3
creating partition: SOS
creating partition: EB4
creating partition: UDA
creating partition: EB5
creating partition: UDB
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 MBR please wait.. done!
Formatting partition 6 APP please wait.. done!
Formatting partition 7 CAC please wait.. done!
Formatting partition 8 MSC please wait.. done!
Formatting partition 9 EB1 please wait.. done!
Formatting partition 10 LNX please wait.. done!
Formatting partition 11 EB2 please wait.. done!
Formatting partition 12 DRM please wait.. done!
Formatting partition 13 EB3 please wait.. done!
Formatting partition 14 SOS please wait.. done!
Formatting partition 15 EB4 please wait.. done!
Formatting partition 16 UDA please wait.. done!
Formatting partition 17 EB5 please wait.. done!
Formatting partition 18 UDB please wait.. done!
done!
sending file: 0-fastboot.img
/ 524288/1024992 bytes sentdata send failed NvError 0x120002
command failure: create failed (bad data)
Been trying it on Ubuntu, on Windows 7, with and without Battery plugged in.
What the hell am I doing wrong, how could I solve this ?
Is there any fix, which resolves this USB issue ?
BTW this is the promaq fix @ ubuntu 12.04 LTS
Greetings
Alpha
You have to keep trying.
I have the same problem, but after the 15th or the 16th times it works.
Try to flash the bootloader only after the partitionating.
So the partitionating done then it will fail after sending the bl.image file. Disconect then reconnect the phone then download the boatloader to the 4th partition.
To make the phone works you need the bootloader on the 4th (EBT) partiton and cwm recovery on the 14th (SOS) partition. Then you can boot into cwm and flash custom rom.
Sent from my LG-P990 using xda app-developers app
nvflash
EDIT: This is stolen from AIO Toolkit
Code:
sudo nvflash --bct star.bct --setbct --odmdata 0xC8000 --configfile ics-stock.cfg --create --bl fastboot.bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x0288414143604097
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
sending file: star.bct
- 4080/4080 bytes sent
star.bct sent successfully
odm data: 0xc8000
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1027184/1027184 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MBR
creating partition: AP2
creating partition: CAC
creating partition: EB1
creating partition: MSC
creating partition: EB2
creating partition: LNX
creating partition: EB3
creating partition: DRM
creating partition: EB4
creating partition: SOS
creating partition: EB5
creating partition: UDA
creating partition: EB6
creating partition: VE
creating partition: EB7
creating partition: UDB
creating partition: EB8
creating partition: APP
creating partition: EB9
creating partition: FOT
creating partition: SWP
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 MBR please wait.. done!
Formatting partition 6 AP2 please wait.. done!
Formatting partition 7 CAC please wait.. done!
Formatting partition 8 EB1 please wait.. done!
Formatting partition 9 MSC please wait.. done!
Formatting partition 10 EB2 please wait.. done!
Formatting partition 11 LNX please wait.. done!
Formatting partition 12 EB3 please wait.. done!
Formatting partition 13 DRM please wait.. done!
Formatting partition 14 EB4 please wait.. done!
Formatting partition 15 SOS please wait.. done!
Formatting partition 16 EB5 please wait.. done!
Formatting partition 17 UDA please wait.. done!
Formatting partition 18 EB6 please wait.. done!
Formatting partition 19 VE please wait.. done!
Formatting partition 20 EB7 please wait.. done!
Formatting partition 21 UDB please wait.. done!
Formatting partition 22 EB8 please wait.. done!
Formatting partition 23 APP please wait.. done!
Formatting partition 24 EB9 please wait.. done!
Formatting partition 25 FOT please wait.. done!
Formatting partition 26 SWP please wait.. done!
done!
sending file: ics-bootloader.bin
\ 891024/891024 bytes sent
ics-bootloader.bin sent successfully
sending file: ics-recovery.img
\ 7200768/7200768 bytes sent
ics-recovery.img sent successfully
sending file: ics-recovery.img
\ 7200768/7200768 bytes sent
ics-recovery.img sent successfully
just tried this one, seems to work now, could get into recovery.
Has anyone had errors when copying the ROM zips from PC to internal mem ?
Is the internal sd formated as fat32?
Sent from my LG-P990 using xda app-developers app
-.-
Tried to install MIUIv4 from ext.SD - Failed because of a symlink error - ok.
Tried then to copy the ZIP to internal SD - get a freeze after copying about 90 Megabytes.
Is this normal ???
Is that MIUIv4 for new bootloader? Because you are on the new partition layout and using the new bootloader. If that MIUI is for the old bootloader and pt layout, then your partition layout is got damaged. This could explain the symlink error and the freezing copy to the internal sd.
=(
Yes now it is formatted FAT32
O2X totally freezes - regardless of taking cwm or twrp ...
Now trying to push it via ADB - Maybe it doesn't freeze then ...
Got to think more about what to write always have a 5 Minutes Timeout between Posts
Ok - just done adb shell ls -l /sdcard and got 100 MB less than expected
tried to push another file to this directory but had no succes - stops after 4096 KB
now adb shell /sdcard doesnt do anything .. wtf is wrong with this device ?
alph4d0g007 said:
Yes now it is formatted FAT32
O2X totally freezes - regardless of taking cwm or twrp ...
Now trying to push it via ADB - Maybe it doesn't freeze then ...
Got to think more about what to write always have a 5 Minutes Timeout between Posts
Ok - just done adb shell ls -l /sdcard and got 100 MB less than expected
tried to push another file to this directory but had no succes - stops after 4096 KB
now adb shell /sdcard doesnt do anything .. wtf is wrong with this device ?
Click to expand...
Click to collapse
I don't really know. I've never performed nvflash from linux, but I think this not the problem.
Maybe your phone and Ubuntu does not like eachother. Try the copy on windows. If it still failing to copy the zip file, then perform the whole nvflashing on windows.
I hope the phone's internal flash memory don't get damaged.
Edit: I remember when I was copying files to my phone on ubuntu. It hanged up for 2-3 minutes at some point but the copying was finished after all
Some output from dmesg
And here's what dmesg says to this phenomenon:
Code:
[15270.208474] usb 2-1.3: new high-speed USB device number 21 using ehci_hcd
[15270.315821] usb 2-1.3: New USB device found, idVendor=1004, idProduct=61a6
[15270.315826] usb 2-1.3: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[15270.315829] usb 2-1.3: Product: LG-P990
[15270.315832] usb 2-1.3: Manufacturer: LGE
[15270.315834] usb 2-1.3: SerialNumber: 0288414143604097
[15270.331213] scsi13 : usb-storage 2-1.3:1.0
[15271.330649] scsi 13:0:0:0: Direct-Access LGE P990 Storage 0000 PQ: 0 ANSI: 2
[15271.332641] scsi 13:0:0:1: Direct-Access LGE P990 SD Card 0000 PQ: 0 ANSI: 2
[15271.333971] sd 13:0:0:0: Attached scsi generic sg2 type 0
[15271.335823] sd 13:0:0:1: Attached scsi generic sg3 type 0
[15271.381063] sd 13:0:0:1: [sdc] Attached SCSI removable disk
[15271.397036] sd 13:0:0:0: [sdb] Attached SCSI removable disk
[15887.818655] sd 13:0:0:0: [sdb] 9734144 512-byte logical blocks: (4.98 GB/4.64 GiB)
[15887.822636] sd 13:0:0:0: [sdb] No Caching mode page present
[15887.822641] sd 13:0:0:0: [sdb] Assuming drive cache: write through
[15887.830649] sd 13:0:0:0: [sdb] No Caching mode page present
[15887.830655] sd 13:0:0:0: [sdb] Assuming drive cache: write through
[15887.832771] sdb:
[15946.692396] sd 13:0:0:0: Device offlined - not ready after error recovery
[15946.692406] sd 13:0:0:0: [sdb] Unhandled error code
[15946.692408] sd 13:0:0:0: [sdb]
[15946.692410] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK
[15946.692412] sd 13:0:0:0: [sdb] CDB:
[15946.692414] Write(10): 2a 00 00 03 9d 78 00 00 c0 00
[15946.692422] end_request: I/O error, dev sdb, sector 236920
[15946.692440] sd 13:0:0:0: rejecting I/O to offline device
[15946.692443] sd 13:0:0:0: killing request
[15946.692462] sd 13:0:0:0: rejecting I/O to offline device
[15946.692465] sd 13:0:0:0: [sdb] killing request
[15946.692468] sd 13:0:0:0: rejecting I/O to offline device
Tried to NvFlash from windows yesterday @ Home, Will try again later that day if I'm home from work, but if this fails too I think this is related to the internal SD on the device (PLEASE correct me ) -.-
Will be back in about 2 hours or so ...
alph4d0g007 said:
And here's what dmesg says to this phenomenon:
Code:
[15270.208474] usb 2-1.3: new high-speed USB device number 21 using ehci_hcd
[15270.315821] usb 2-1.3: New USB device found, idVendor=1004, idProduct=61a6
[15270.315826] usb 2-1.3: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[15270.315829] usb 2-1.3: Product: LG-P990
[15270.315832] usb 2-1.3: Manufacturer: LGE
[15270.315834] usb 2-1.3: SerialNumber: 0288414143604097
[15270.331213] scsi13 : usb-storage 2-1.3:1.0
[15271.330649] scsi 13:0:0:0: Direct-Access LGE P990 Storage 0000 PQ: 0 ANSI: 2
[15271.332641] scsi 13:0:0:1: Direct-Access LGE P990 SD Card 0000 PQ: 0 ANSI: 2
[15271.333971] sd 13:0:0:0: Attached scsi generic sg2 type 0
[15271.335823] sd 13:0:0:1: Attached scsi generic sg3 type 0
[15271.381063] sd 13:0:0:1: [sdc] Attached SCSI removable disk
[15271.397036] sd 13:0:0:0: [sdb] Attached SCSI removable disk
[15887.818655] sd 13:0:0:0: [sdb] 9734144 512-byte logical blocks: (4.98 GB/4.64 GiB)
[15887.822636] sd 13:0:0:0: [sdb] No Caching mode page present
[15887.822641] sd 13:0:0:0: [sdb] Assuming drive cache: write through
[15887.830649] sd 13:0:0:0: [sdb] No Caching mode page present
[15887.830655] sd 13:0:0:0: [sdb] Assuming drive cache: write through
[15887.832771] sdb:
[15946.692396] sd 13:0:0:0: Device offlined - not ready after error recovery
[15946.692406] sd 13:0:0:0: [sdb] Unhandled error code
[15946.692408] sd 13:0:0:0: [sdb]
[15946.692410] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK
[15946.692412] sd 13:0:0:0: [sdb] CDB:
[15946.692414] Write(10): 2a 00 00 03 9d 78 00 00 c0 00
[15946.692422] end_request: I/O error, dev sdb, sector 236920
[15946.692440] sd 13:0:0:0: rejecting I/O to offline device
[15946.692443] sd 13:0:0:0: killing request
[15946.692462] sd 13:0:0:0: rejecting I/O to offline device
[15946.692465] sd 13:0:0:0: [sdb] killing request
[15946.692468] sd 13:0:0:0: rejecting I/O to offline device
Tried to NvFlash from windows yesterday @ Home, Will try again later that day if I'm home from work, but if this fails too I think this is related to the internal SD on the device (PLEASE correct me ) -.-
Will be back in about 2 hours or so ...
Click to expand...
Click to collapse
It seems like your phone got a bad sector on the internal sd partition. I hope it is not true, and this happening due the timeout error (what you had during the nvlfash) which I have with nvflash and smartflash.
bitdomo said:
It seems like your phone got a bad sector on the internal sd partition. I hope it is not true, and this happening due the timeout error (what you had during the nvlfash) which I have with nvflash and smartflash.
Click to expand...
Click to collapse
ok how could I get rid of this USB Timeout ?
ps: some news from dmesg:
[18515.672887] sdc: detected capacity change from 15820914688 to 0
Now managed to get MIUI installed (recovery said so) but I'm now starving @ the Bootlogo ...
Just wondering if after half an hour the boot process could be canceled ...
Is there a way to get the system installed on a partitioned ext_sd instead of the internal ?
I ran into this problem before. This caused by the format of the DRM partition, and this is only happens with miui. If you check the dmesg log you can see the problem. So ADB is working even if you stucked at the boot logo. Here is my post about solving this problem. It is for windows, but you seem to be clever, so flashing the drm partition on linux would not cause you problem.
To see the flashing commands look at the content of the flash.bat file.
Edit: Answering to your question. Yes you can install rom to your external sd card, but you have to do a little work. If you are intrested in, then I can help you. I was able to boot up a rom from external sdcard.
bitdomo said:
I ran into this problem before. This caused by the format of the DRM partition, and this is only happens with miui. If you check the dmesg log you can see the problem. So ADB is working even if you stucked at the boot logo. Here is my post about solving this problem. It is for windows, but you seem to be clever, so flashing the drm partition on linux would not cause you problem.
To see the flashing commands look at the content of the flash.bat file.
Edit: Answering to your question. Yes you can install rom to your external sd card, but you have to do a little work. If you are intrested in, then I can help you. I was able to boot up a rom from external sdcard.
Click to expand...
Click to collapse
Just asking myself why I just didn't wait for you to answer :crying:
While you were typing this hint I nvflashed agin and, now I'm unable to install MIUI again
TWRP just says "Error unable to open Zip", CWM sometimes says it has a wrong header, sometimes there are some symlinks that cant be created and so on ...
Now trying to install via twrp ADB Sideload ... maybe I get as far as before ... will post if I have success.
You don't have to stick to MIUI. I had a lot of problem with that. It is RAM hungry. Bunch of google app dont work. After a day or two the phone become slow, even if I enabled 128 mb swap. I recomend to use tonyp's paranoidandroid or cm10.1 rom. You will save yourself from a lot of suffer.
Hello!
I have problem with my device.
First i tried upgrade from v20q to v30a software.
First
I was tried flash by offline kdz And fail.
I was tried via smart flash flashing near 4-6x and fail.
And last try was bricked device.
When i plug device to usb he was know as APX(only).
I was try aio, nv flash and fail i cant repartytion this
Code:
[Back]
E:\2x-v10b-1300166062-nvflash>.\nvflash.exe --bct E1108_Hynix_512MB_H8TBR00U0MLR
-0DM_300MHz_final_emmc_x8.bct --setbct --odmdata 0xC8000 --configfile android_fa
stboot_emmc_full.cfg --create --bl fastboot.bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x0288500542616057
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
sending file: E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct
- 4080/4080 bytes sent
E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct sent successfully
odm data: 0xc8000
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MBR
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: EB1
creating partition: LNX
creating partition: EB2
creating partition: DRM
creating partition: EB3
creating partition: SOS
creating partition: EB4
creating partition: UDA
creating partition: EB5
creating partition: UDB
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 MBR please wait.. done!
Formatting partition 6 APP please wait.. done!
Formatting partition 7 CAC please wait.. done!
Formatting partition 8 MSC please wait.. done!
Formatting partition 9 EB1 please wait.. done!
Formatting partition 10 LNX please wait.. done!
Formatting partition 11 EB2 please wait.. done!
Formatting partition 12 DRM please wait.. done!
Formatting partition 13 EB3 please wait.. done!
Formatting partition 14 SOS please wait.. done!
Formatting partition 15 EB4 please wait.. done!
Formatting partition 16 UDA please wait.. done!
Formatting partition 17 EB5 please wait.. done!
Formatting partition 18 UDB please wait.. done!
done!
sending file: fastboot.bin
\ 917504/1024992 bytes sent
When i try via nv for near xxx tries fastboot.bin was sent complety and was closed.
And device is only on s/w upgrade.....
I dont know memory sectors was broken? Mainboard fully broken?
arthurus said:
Hello!
I have problem with my device.
First i tried upgrade from v20q to v30a software.
First
I was tried flash by offline kdz And fail.
I was tried via smart flash flashing near 4-6x and fail.
And last try was bricked device.
When i plug device to usb he was know as APX(only).
I was try aio, nv flash and fail i cant repartytion this
Code:
[Back]
E:\2x-v10b-1300166062-nvflash>.\nvflash.exe --bct E1108_Hynix_512MB_H8TBR00U0MLR
-0DM_300MHz_final_emmc_x8.bct --setbct --odmdata 0xC8000 --configfile android_fa
stboot_emmc_full.cfg --create --bl fastboot.bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x0288500542616057
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
sending file: E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct
- 4080/4080 bytes sent
E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct sent successfully
odm data: 0xc8000
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MBR
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: EB1
creating partition: LNX
creating partition: EB2
creating partition: DRM
creating partition: EB3
creating partition: SOS
creating partition: EB4
creating partition: UDA
creating partition: EB5
creating partition: UDB
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 MBR please wait.. done!
Formatting partition 6 APP please wait.. done!
Formatting partition 7 CAC please wait.. done!
Formatting partition 8 MSC please wait.. done!
Formatting partition 9 EB1 please wait.. done!
Formatting partition 10 LNX please wait.. done!
Formatting partition 11 EB2 please wait.. done!
Formatting partition 12 DRM please wait.. done!
Formatting partition 13 EB3 please wait.. done!
Formatting partition 14 SOS please wait.. done!
Formatting partition 15 EB4 please wait.. done!
Formatting partition 16 UDA please wait.. done!
Formatting partition 17 EB5 please wait.. done!
Formatting partition 18 UDB please wait.. done!
done!
sending file: fastboot.bin
\ 917504/1024992 bytes sent
When i try via nv for near xxx tries fastboot.bin was sent complety and was closed.
And device is only on s/w upgrade.....
I dont know memory sectors was broken? Mainboard fully broken?
Click to expand...
Click to collapse
Try other pc, usb cable, usb port or usb3 port. I have been suffering from this issue, but after 8-10 tries i can successfully flash the rom.
bitdomo said:
Try other pc, usb cable, usb port or usb3 port. I have been suffering from this issue, but after 8-10 tries i can successfully flash the rom.
Click to expand...
Click to collapse
Thanks
I was tried on my netbook and succefull
i was flashed cm10 promaq and how i can back it to stock rom?
arthurus said:
Thanks
I was tried on my netbook and succefull
i was flashed cm10 promaq and how i can back it to stock rom?
Click to expand...
Click to collapse
With offline kdz flash