Related
Can someone tell me why I keep getting the directory error at the bottom on my linux box? Sorry am learning linux as i go. I created a zip directory under bin so not sure why I am still getting this error?
no files for configid 26220739write xip block starting at 81800000, with 3 fileswrite xip block starting at 81980000, with 0 filesthis rom seems to be 3.17.03 ENG 2003-05-15 o2eurothis bootloader seems to be V5.22 2003-05-15 17:46:5580000000 - 80040000 -- bootloader 0 files 1 modules80040000 - 8026a804 -- kernel 13 files 11 modules802c2000 - 8057d330 9 OS 15 files 32 modules80580000 - 8075a69c 8 SHELL 79 files 27 modules80780000 - 80a13b04 7 BROWSING 9 files 14 modules80a40000 - 80d8a33c 6 COREAPPS 46 files 30 modules80dc0000 - 80ebd150 5 SYNC 12 files 22 modules80ec0000 - 810388e0 4 24MAPPS 13 files 13 modules81080000 - 81348248 3 24MCONSUMER 69 files 1 modules81400000 - 814019a4 -- xip chain 10 xip entries81440000 - 817f6f14 1 MISC 209 files 40 modules81800000 - 8184ac20 10 XDA_DEVELOPERS1 3 files 0 modules81900000 - 81925800 -- bitmap : 101a301a .. beb6fc8d81940000 - 81960278 -- operator rom 10 files81980000 - 81981054 11 XDA_DEVELOPERS2 0 files 0 modules./mkrom.sh: /bin/zip: No such file or directory
It looks as though you do not have an appropriate ZIP program...
You may want to see if bzip2 will work instead of zip, or get the linux version of RAR.
The issue though, is you do not have /bin/zip, which is an executable file, not a directory.
Maybe someone can verify what compression executable to use instead of /bin/zip...
J
Ok got that resolved but now when doing zip it gets permission denied. Any other assistance is greatly appreciated. Then should be able to have yorch and company's kitchen running
I would verify that the user that is executing the shell (mkrom) has execute permissions to the zip program...
you can run (as root)
Code:
chmod 755 /usr/bin/bzip2
to change permissions on the bzip2 executable file.
That will give root all access, and everyone else read/execute access.
Also, if the zip program uses any temp directories, make sure the same user has read/write permissions to those directories as well (Probably not your problem, though)
J
Ok got that resolved....now here's what i get....is this a safe error or something I need to worry about? How can I correct it?
./mkrom.sh: ./tounicode: Permission deniedwrite xip block starting at 81720000, with 6 fileswrite xip block starting at 81cb0000, with 72 filesCan't exec "./dumprom": Permission denied at drparse.pl line 22.readline() on closed filehandle FH at drparse.pl line 24.Can't exec "./dumprom": Permission denied at drparse.pl line 22.readline() on closed filehandle FH at drparse.pl line 24.Can't exec "./dumprom": Permission denied at drparse.pl line 22.readline() on closed filehandle FH at drparse.pl line 24.!!! your rom is not known to me: md5: dad2e3cad6095282bf1d58ccf12171e8this bootloader seems to be V5.22 2003-05-15 17:46:55no operator rom found80000000 - 80040000 -- bootloader 0 files 1 modules80040000 - 8015df78 9 XIPKERNEL 5 files 5 modules80180000 - 80376f10 8 KERNEL 10 files 14 modules80380000 - 8064306c 7 OS 20 files 36 modules80670000 - 80be66a8 6 SHELL 107 files 88 modules80c00000 - 8102ce98 5 BROWSING 11 files 36 modules81050000 - 813ef114 4 COREAPPS 95 files 44 modules81400000 - 815d2238 3 EXAPPS 34 files 7 modules815f0000 - 8171bc7c 2 PHONE 56 files 19 modules81720000 - 8177ffe0 10 XDA_DEVELOPERS1 6 files 0 modules81780000 - 81781c34 -- xip chain 11 xip entries817c0000 - 81ca1b44 1 MISC 225 files 42 modules81cb0000 - 81d4eb7c 11 XDA_DEVELOPERS2 72 files 0 modules81ec0000 - 81ee5800 -- bitmap : ffffffff .. ffffffff../rom.exe: found a preamble of 35328 bytes adding: English/NK.nbf (deflated 44%)Archive: rom.exe;The comment below contains SFX script commandsSetup=start.batTempModeSilent=1Overwrite=1 Length Method Size Ratio Date Time CRC-32 Name-------- ------ ------- ----- ---- ---- ------ ---- 0 Stored 0 0% 07-28-03 15:28 00000000 English/ 262144 Defl:N 11018 96% 05-20-02 18:27 f4419bea English/CLoader_serial.nb 262144 Defl:N 12683 95% 05-20-02 18:17 d576b33c English/CLoader_usb.nb 4608 Defl:N 1094 76% 07-17-02 17:22 578b9c86 English/GetConnectionType.dll 18432 Defl:N 7650 59% 04-24-02 15:44 e4ed8f0a English/remote_flash.exe 3584 Defl:N 856 76% 08-21-01 16:43 da38a539 English/SetSystemTime.dll 73728 Defl:N 36119 51% 07-09-03 07:09 95cf7c18 adaptrom.exe 155648 Defl:N 50839 67% 08-28-02 15:23 f5a4ac25 PROGRAMME A.exe 3548 Defl:N 1078 70% 08-28-02 15:25 65d98105 readme.rtf 25 Stored 25 0% 07-28-03 15:28 ecfe543d start.bat32505888 Defl:N 18306975 44% 10-11-03 21:28 34cc9720 English/NK.nbf-------- ------- --- -------33289749 18428337 45% 11 files
Looks like you have the same execute permission problem with the tounicode exe.
Try to fix that.
About the drparse.pl, I have to look at that file, to see what it is trying to do...
Ok, here is the line:
Code:
open FH, "./dumprom $romfile|";
Looks like it is trying to open (as a file) the output of the dumprom executable.
So, dumprom is failing, probably ... yes, I see it now..
Verify the permissions on dumprom as well...
In fact, all *.pl and *.sh files should have execute permissions, use the same command as above to set them.
This reply is a rambling one, I know, but I wrote is as I was doing the research.
Let me know if it helps you.
J
Here's what is weird. I have changed those permissions as you said previously and still get the same error. What's strange to me though is I can run the kitchen with rom ver 3 something, but all of the ver 4 roms come back with the error. Any idea as to what the cause of that might be?
btw jta thanks for all the help. If you have time and would like to look at the box for me I will get access to it for you. Thanks.
I got it all working now. Thank you thank you thank you very much for the help.
Ah, good to hear that you have it all working now!
So, when do we get to try it out?? (wink wink)
J
Very soon....we are now putting finishing touches with other software installs....so will be very very soon.....
type:
cd /usr/local/bin
# ln -s /usr/bin/zip zip
run this command: cat /proc/L*/bmlinfo
then post your result:
mine runs RFS
Code:
FSR VERSION: FSR_1.2.1p1_b139_RTM
minor position size units id
1: 0x00000000-0x00040000 0x00040000 1 0
2: 0x00040000-0x00080000 0x00040000 1 1
3: 0x00080000-0x00a80000 0x00a00000 40 20
4: 0x00a80000-0x00bc0000 0x00140000 5 3
5: 0x00bc0000-0x00d00000 0x00140000 5 4
6: 0x00d00000-0x01200000 0x00500000 20 21
7: 0x01200000-0x01980000 0x00780000 30 6
8: 0x01980000-0x02100000 0x00780000 30 7
9: 0x02100000-0x12d80000 0x10c80000 1074 22
10: 0x12d80000-0x32f80000 0x20200000 2056 23
11: 0x32f80000-0x3de80000 0x0af00000 700 24
12: 0x3de80000-0x3eb00000 0x00c80000 50 11
(0)(0) bad mapping information
No BadUnit RsvUnit
0: 208 4090
1: 919 4089
2: 1023 4088
i have only 3 bad blocks
I am doing research and no flaming!
I don't think we would see results of bad sectors that fast as most people had it for a week max..but I guess for the sake of research
Rfs _ had epic since sept 20th around
$ export PATH=/data/local/bin:$PATH
$cat /proc/L*/bmlinfo
FSR VERSION: FSR_1.2.1p1_b139_RTM
minor position size units id
1: 0x00000000-0x00040000 0x00040000 1 0
2: 0x00040000-0x00080000 0x00040000 1 1
3: 0x00080000-0x00a80000 0x00a00000 40 20
4: 0x00a80000-0x00bc0000 0x00140000 5 3
5: 0x00bc0000-0x00d00000 0x00140000 5 4
6: 0x00d00000-0x01200000 0x00500000 20 21
7: 0x01200000-0x01980000 0x00780000 30 6
8: 0x01980000-0x02100000 0x00780000 30 7
9: 0x02100000-0x12d80000 0x10c80000 1074 22
10: 0x12d80000-0x32f80000 0x20200000 2056 23
11: 0x32f80000-0x3de80000 0x0af00000 700 24
12: 0x3de80000-0x3eb00000 0x00c80000 50 11
(0)(0) bad mapping information
No BadUnit RsvUnit
0: 1628 4090
1: 2812 4089
2: 3002 4088
3: 3584 4087
4: 3646 4086
5: 3838 4085
export PATH=/data/local/bin:$PATH
# cat /proc/L*/bmlinfo
FSR VERSION: FSR_1.2.1p1_b139_RTM
minor position size units id
1: 0x00000000-0x00040000 0x00040000 1 0
2: 0x00040000-0x00080000 0x00040000 1 1
3: 0x00080000-0x00a80000 0x00a00000 40 20
4: 0x00a80000-0x00bc0000 0x00140000 5 3
5: 0x00bc0000-0x00d00000 0x00140000 5 4
6: 0x00d00000-0x01200000 0x00500000 20 21
7: 0x01200000-0x01980000 0x00780000 30 6
8: 0x01980000-0x02100000 0x00780000 30 7
9: 0x02100000-0x12d80000 0x10c80000 1074 22
10: 0x12d80000-0x32f80000 0x20200000 2056 23
11: 0x32f80000-0x3de80000 0x0af00000 700 24
12: 0x3de80000-0x3eb00000 0x00c80000 50 11
(0)(0) bad mapping information
No BadUnit RsvUnit
0: 100 4090
1: 1068 4089
2: 2584 4088
3: 3540 4087
#
Now lucky me I get my first bad within the first 100 units. Had the Epic since mid October
I bought my Epic when it came out(sept 1st I think).
Running Ext4 sinse it came out(3 days I think).
Is this good?How long my Epic got to live?lol.
export PATH=/data/local/bin:$PATH
$ $su
# cat /proc/L*/bmlinfo
FSR VERSION: FSR_1.2.1p1_b139_RTM
minor position size units id
1: 0x00000000-0x00040000 0x00040000 1 0
2: 0x00040000-0x00080000 0x00040000 1 1
3: 0x00080000-0x00a80000 0x00a00000 40 20
4: 0x00a80000-0x00bc0000 0x00140000 5 3
5: 0x00bc0000-0x00d00000 0x00140000 5 4
6: 0x00d00000-0x01200000 0x00500000 20 21
7: 0x01200000-0x01980000 0x00780000 30 6
8: 0x01980000-0x02100000 0x00780000 30 7
9: 0x02100000-0x12d80000 0x10c80000 1074 22
10: 0x12d80000-0x32f80000 0x20200000 2056 23
11: 0x32f80000-0x3de80000 0x0af00000 700 24
12: 0x3de80000-0x3eb00000 0x00c80000 50 11
(0)(0) bad mapping information
No BadUnit RsvUnit
0: 912 4090
1: 937 4089
2: 1027 4088
3: 3701 4087
#
Been running ext4 since a few days after its port.
export PATH=/data/local/bin:$PATH
$ $su
# cat /proc/L*/bmlinfo
FSR VERSION: FSR_1.2.1p1_b139_RTM
minor position size units id
1: 0x00000000-0x00040000 0x00040000 1 0
2: 0x00040000-0x00080000 0x00040000 1 1
3: 0x00080000-0x00a80000 0x00a00000 40 20
4: 0x00a80000-0x00bc0000 0x00140000 5 3
5: 0x00bc0000-0x00d00000 0x00140000 5 4
6: 0x00d00000-0x01200000 0x00500000 20 21
7: 0x01200000-0x01980000 0x00780000 30 6
8: 0x01980000-0x02100000 0x00780000 30 7
9: 0x02100000-0x12d80000 0x10c80000 1074 22
10: 0x12d80000-0x32f80000 0x20200000 2056 23
11: 0x32f80000-0x3de80000 0x0af00000 700 24
12: 0x3de80000-0x3eb00000 0x00c80000 50 11
(0)(0) bad mapping information
No BadUnit RsvUnit
0: 1023 4090
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
hope this can be read
running "twin jets" launch day unit
When I type this in terminal it says not found.
I'm a little concerned about mine when compared to the others so far... Though I must admit that I've flashed mine more times than I can count just testing:
I've yet to ever flash ext4 on my phone. This phone I've had since early October.
FSR VERSION: FSR_1.2.1p1_b139_RTM
minor position size units id
1: 0x00000000-0x00040000 0x00040000 1 0
2: 0x00040000-0x00080000 0x00040000 1 1
3: 0x00080000-0x00a80000 0x00a00000 40 20
4: 0x00a80000-0x00bc0000 0x00140000 5 3
5: 0x00bc0000-0x00d00000 0x00140000 5 4
6: 0x00d00000-0x01200000 0x00500000 20 21
7: 0x01200000-0x01980000 0x00780000 30 6
8: 0x01980000-0x02100000 0x00780000 30 7
9: 0x02100000-0x12d80000 0x10c80000 1074 22
10: 0x12d80000-0x32f80000 0x20200000 2056 23
11: 0x32f80000-0x3de80000 0x0af00000 700 24
12: 0x3de80000-0x3eb00000 0x00c80000 50 11
(0)(0) bad mapping information
No BadUnit RsvUnit
0: 821 4090
1: 1821 4089
2: 2119 4088
3: 2215 4087
4: 2261 4086
5: 2936 4085
6: 2950 4084
7: 2968 4083
8: 3158 4081
9: 3236 4080
10: 3479 4079
11: 3486 4078
12: 3510 4077
13: 3780 4076
14: 3820 4075
15: 3980 4074
Sent from my SPH-D700 using Tapatalk
konaman said:
When I type this in terminal it says not found.
Click to expand...
Click to collapse
Type it exactly as it is wrtten!
sent from deez
If this is the entirety of my output does that mean no bad blocks yet?
Code:
FSR VERSION: FSR_1.2.1p1_b139_RTM
minor position size units id
1: 0x00000000-0x00040000 0x00040000 1 0
2: 0x00040000-0x00080000 0x00040000 1 1
3: 0x00080000-0x00a80000 0x00a00000 40 20
4: 0x00a80000-0x00bc0000 0x00140000 5 3
5: 0x00bc0000-0x00d00000 0x00140000 5 4
6: 0x00d00000-0x01200000 0x00500000 20 21
7: 0x01200000-0x01980000 0x00780000 30 6
8: 0x01980000-0x02100000 0x00780000 30 7
9: 0x02100000-0x12d80000 0x10c80000 1074 22
10: 0x12d80000-0x32f80000 0x20200000 2056 23
11: 0x32f80000-0x3de80000 0x0af00000 700 24
12: 0x3de80000-0x3eb00000 0x00c80000 50 11
(0)(0) bad mapping information
No BadUnit RsvUnit
Have had my epic since 9/03/10, flashed a new ROM or revision about 4 or 5 times only. Been on ext4 for about 4 days only.
Running rfs had the phone since release day
$cat /proc/L*/bmlinfo
FSR VERSION: FSR_1.2.1p1_b139_RTM
minor position size units id
1: 0x00000000-0x00040000 0x00040000 1 0
2: 0x00040000-0x00080000 0x00040000 1 1
3: 0x00080000-0x00a80000 0x00a00000 40 20
4: 0x00a80000-0x00bc0000 0x00140000 5 3
5: 0x00bc0000-0x00d00000 0x00140000 5 4
6: 0x00d00000-0x01200000 0x00500000 20 21
7: 0x01200000-0x01980000 0x00780000 30 6
8: 0x01980000-0x02100000 0x00780000 30 7
9: 0x02100000-0x12d80000 0x10c80000 1074 22
10: 0x12d80000-0x32f80000 0x20200000 2056 23
11: 0x32f80000-0x3de80000 0x0af00000 700 24
12: 0x3de80000-0x3eb00000 0x00c80000 50 11
(0)(0) bad mapping information
No BadUnit RsvUnit
0: 324 4090
1: 1864 4089
2: 2567 4088
3: 2789 4087
4: 2830 4086
5: 2985 4085
$
Sent from my SPH-D700 using XDA App
I bought my Epic end of Sept.
Running Ext4 since release
minor position size units id
1: 0x00000000-0x00040000 0x00040000 1 0
2: 0x00040000-0x00080000 0x00040000 1 1
3: 0x00080000-0x00a80000 0x00a00000 40 20
4: 0x00a80000-0x00bc0000 0x00140000 5 3
5: 0x00bc0000-0x00d00000 0x00140000 5 4
6: 0x00d00000-0x01200000 0x00500000 20 21
7: 0x01200000-0x01980000 0x00780000 30 6
8: 0x01980000-0x02100000 0x00780000 30 7
9: 0x02100000-0x12d80000 0x10c80000 1074 22
10: 0x12d80000-0x32f80000 0x20200000 2056 23
11: 0x32f80000-0x3de80000 0x0af00000 700 24
12: 0x3de80000-0x3eb00000 0x00c80000 50 11
(0)(0) bad mapping information
No BadUnit RsvUnit
0: 3475 4090
1: 3779 4089
2: 3442 4088
Seems as though we all have the same info up top, the (0)(0) bad mapping information is what seems different among devices..
I only have 3 bad blocks.. not sure how many block I have though LOL
Hope this helps
export PATH=/data/local/bin:$PATH
$ $cat /proc/L*/bmlinfo
FSR VERSION: FSR_1.2.1p1_b139_RTM
minor position size units id
1: 0x00000000-0x00040000 0x00040000 1 0
2: 0x00040000-0x00080000 0x00040000 1 1
3: 0x00080000-0x00a80000 0x00a00000 40 20
4: 0x00a80000-0x00bc0000 0x00140000 5 3
5: 0x00bc0000-0x00d00000 0x00140000 5 4
6: 0x00d00000-0x01200000 0x00500000 20 21
7: 0x01200000-0x01980000 0x00780000 30 6
8: 0x01980000-0x02100000 0x00780000 30 7
9: 0x02100000-0x12d80000 0x10c80000 1074 22
10: 0x12d80000-0x32f80000 0x20200000 2056 23
11: 0x32f80000-0x3de80000 0x0af00000 700 24
12: 0x3de80000-0x3eb00000 0x00c80000 50 11
(0)(0) bad mapping information
No BadUnit RsvUnit
0: 84 4090
1: 1398 4089
2: 3418 4088
Had my epic since a week after launch. Had ext4 for 2 days now. Personally, I see no correlation so far between people running ext4 and a higher number of dead blocks.
Sent from my ext4 Epic 4G running Bonsai4all 1.1.3!
Can this be done from terminal emulator?
Sent from my SPH-D700 using Tapatalk
adamw1101 said:
Can this be done from terminal emulator?
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Yes paste this
cat /proc/L*/bmlinfo
Into your terminal emulator
Sent from my ext4 Epic 4G running Bonsai4all 1.1.3!
Im lost it keeps saying it isn't found is there a prior command I have to insert first?
Sent from my SPH-D700 using Tapatalk
Oct 27th 2010 -- ext4 since it released, flashed new 2.2 roms almost weekly since nov
$ export PATH=/data/local/bin:$PATH
# cat /proc/L*/bmlinfo
FSR VERSION: FSR_1.2.1p1_b139_RTM
minor position size units id
1: 0x00000000-0x00040000 0x00040000 1 0
2: 0x00040000-0x00080000 0x00040000 1 1
3: 0x00080000-0x00a80000 0x00a00000 40 20
4: 0x00a80000-0x00bc0000 0x00140000 5 3
5: 0x00bc0000-0x00d00000 0x00140000 5 4
6: 0x00d00000-0x01200000 0x00500000 20 21
7: 0x01200000-0x01980000 0x00780000 30 6
8: 0x01980000-0x02100000 0x00780000 30 7
9: 0x02100000-0x12d80000 0x10c80000 1074 22
10: 0x12d80000-0x32f80000 0x20200000 2056 23
11: 0x32f80000-0x3de80000 0x0af00000 700 24
12: 0x3de80000-0x3eb00000 0x00c80000 50 11
(0)(0) bad mapping information
No BadUnit RsvUnit
#
(on a side note I have two epic. Mine on EXT4 and my Wife's as close to stock as i can (rooted though so i can run terminal)) so I can randomly run compares over the next 2 years (unless sprint allows early upgrades after the first year) I feel doing this is the only way we can truly due a real life compare and end the which is better argument.
Had my phone for 3 months,flashed more ROMs than I can count,more than 100 Im sure,running EXT4 for 3 days,only got 7 bad blocks,Im using connect bot and cant copy the text right now.
chadit said:
(on a side note I have two epic. Mine on EXT4 and my Wife's as close to stock as i can (rooted though so i can run terminal)) so I can randomly run compares over the next 2 years (unless sprint allows early upgrades after the first year) I feel doing this is the only way we can truly due a real life compare and end the which is better argument.
Click to expand...
Click to collapse
You sir would be a valuable tool in testing the file-system effects and helping put any misconceptions to rest.
export PATH=/data/local/bin:$PATH
$ $ cat/proc/L*/bmlinfo
cat/proc/L*/bmlinfo: not found
$su
# cat/proc/L*/bmlinfo
cat/proc/L*/bmlinfo: not found
#cat /proc/L*/bmlinfo
FSR VERSION: FSR_1.2.1p1_b139_RTM
minor position size units id
1: 0x00000000-0x00040000 0x00040000 1 0
2: 0x00040000-0x00080000 0x00040000 1 1
3: 0x00080000-0x00a80000 0x00a00000 40 20
4: 0x00a80000-0x00bc0000 0x00140000 5 3
5: 0x00bc0000-0x00d00000 0x00140000 5 4
6: 0x00d00000-0x01200000 0x00500000 20 21
7: 0x01200000-0x01980000 0x00780000 30 6
8: 0x01980000-0x02100000 0x00780000 30 7
9: 0x02100000-0x12d80000 0x10c80000 1074 22
10: 0x12d80000-0x32f80000 0x20200000 2056 23
11: 0x32f80000-0x3de80000 0x0af00000 700 24
12: 0x3de80000-0x3eb00000 0x00c80000 50 11
(0)(0) bad mapping information
No BadUnit RsvUnit
0: 3698 4090
#
Have flashed pretty much every rom released have set up ext4 twice on my phone odined like 30 times
Sent from my SPH-D700 using Tapatalk
Anyway, I was using Miui V3 2.4.20 [2.6.35], and Google maps wasn't very happy with it. So I decided it was time to move on to the .32 kernal version, since the developer was going that way too. Downloaded a stock rom with .32 kernal, went to the pink screen and flashed, and then boot loop.
Luckily, I'm awesome, so my phone won't die on me. Tried flashing some roms through clockwork, no bootloop, just stuck at huawei logo. Tried flashing some stock roms, and at about 98% done flashing it goes error. Some parts get flashed causing my recovery reverts to stock, but I'm still stuck at the huawei logo.
Also, in clockworkmod I get errors mounting data and emmc, so that might be a problem. Other partitions mount fine.
I'm sure I'll find a solution eventually, so there's no rush. I've been in similar situations before. Just wanted to see what other people had used for similar situations. So if you know of something that would help, please let me know.
Found these through search (I'll do a better search again later), i will try them tomorrow:
http://forum.xda-developers.com/showpost.php?p=18944228&postcount=4
http://forum.xda-developers.com/showthread.php?t=1683249
http://forum.xda-developers.com/showthread.php?t=1689469
http://forum.xda-developers.com/showthread.php?t=1682501
http://forum.xda-developers.com/showthread.php?t=1011527
After reading a lot of threads, attempting to flash a lot of roms (stock and others), replacing all kinds of images, and offering a sacrifice to the cellphone gods, still at the same problem:
To reiterate problem:
1) Stuck/reboots at Huawei logo
2) Flashing stock roms via pink screen never finish installing, get error message at ~95% finished (During install, unpacks fine)
3) Flashing roms via recovery say they installed, but still boot problem
4) This problem occurred while trying to downgrade from .35 to .32
My next step is to try using Linux to put the Dload folder on the internal SD card and try installing from there. I have a feeling it is related to the partitions having problems. I used both the "get back pink screen" and "data partition resize," maybe something went wrong with them that only appeared when I tried to go back to stock. I'll find out more when I install linux and can see if the partitions are OK or not.
I've always wanted to try linux, and now that my phone is broke I have found the motivation to do so. So a word of advice for people for people wanting to try linux but are too lazy to download the linux file: Soft-brick your phone, it gives you motivation.
UPDATE: I'm pretty sure my partition table is broke pretty bad. In adb shell, df gives me:
Filesystem Size Used Free
/dev 173M 64K 172M
/system 203M 200M 2M
/cache 127M 4M 123M
and that's it. No /HWUserData, /.cust_backup, /mnt/asec, /mnt/obb, or /data.
Would someone be as kind as to tell me how to fix the partition table? I've got a soldering iron, duct tape and super glue. Also, I'm not afraid to buy a "box" to do some Jtag stuff.
Anybody know what Blefish uses to format the phone memory? I read on his tumbler page and his github that he has altered the partition table (he split the /hwuserdata into three sections, which means he has the ability to create partitions) If I can get that tool, then I have a plan:
0) If my understanding is correct, the updates don't install because the needed partitions are missing, which causes an error. I guess the updates won't create partitions, just alter them.
1) Use the tool blefish used to setup the partition table as described in this thread: http://forum.xda-developers.com/showthread.php?t=1504488
2) Once the partitions are back, i should at least be able to get the blue screen, if I'm good, then I can put all right files in /dev/sdb1, which will get me the pink screen.
3) Using the blue/pink screen, I can install stock firmware, which should correct any problems that the partition table has. Maybe even install android.
4) Do the happy dance
5) ???
6) Profit
I've done my homework, searched the forums, made a plan, and cleaned my room. Someone please give me some feedback and at least let me know if I'm heading in the right direction.
typci said:
Anybody know what Blefish uses to format the phone memory?
Click to expand...
Click to collapse
I am using fdisk, the main partitioning tool for MBR table. You can check the table by doing fdisk /dev/block/mmcblk0 and then "p" which should print the current partition table. From there, you can also modify the partitions.
Sent from my U8800 using Tapatalk 2
Blefish said:
I am using fdisk, the main partitioning tool for MBR table. You can check the table by doing fdisk /dev/block/mmcblk0 and then "p" which should print the current partition table. From there, you can also modify the partitions.
Sent from my U8800 using Tapatalk 2
Click to expand...
Click to collapse
Awesome. I used to use fdisk back in the dos days, so I just need to brush up on my skills and learn the adb specifics. I really need to take the time to go learn all the commands associated with adb.
INTERESTING UPDATE: If I flash a rom with locked boot loader, I still get the pink screen but it doesn't work, i.e. I can't access the image folder via windows. If I flash a rom without a locked boot loader, pink screen works. Granted none of these roms actually fully flash, I still get the error near the end.
Fdisk = Permission denied, su = permission denied. Rooted boot image prevents me from getting into recovery, which means adb won't work. Any other way to get root? I'll try flashing a custom rom when I can get clockworkmod working again. For some reason I can't get recovery to load via vol+ & power.
Also something weird is going on. When it boots, it reboots once, then goes to stock recovery, tries to do a factory reset, gets errors on formating. Also in windows two removable disks appear, but I can access them. I take it that they represent the internal SD card and maybe the pink screen image folder partition. Tomorrow I'll try linux and see what happens.
UPDATE:
1) I can't use FDISK because SU won't work. I'm not sure how SU/root works on a software/partition bricked phone.
2) Rooted boot.img won't boot into recovery. SuperOneClick won't work because it can't find the data partition (probably because I don't have one).
3) I was going to try flashing a custom rom but for some reason I can't get clockworkmod working again. The phone will boot into stock recovery on it's own, after a couple of reboots. However, if I change the boot.img or recovery.img to anything else, it gets stuck at huawei logo or boot loop.
4) Unbuntu LiveCD won't work (says it can't find the kernal) even though I used the installer from the website and tried it both via cd and flash drive. Working on installing a dual-boot system now.
I'm really striking out here. Couple of questions if anyone would care to answer.
1) Besides recovery, how else can I establish an adb connection? Pink screen and huawei logo give me device not found.
2) Is there a root exploit available that doesn't require a data partition or is there a root exploit I can modify so it doesn't require a data partition? It's OK if it's a manual exploit, while I'm new with android/adb, I got plenty of experience with command prompt input from back in the dos days.
Also learned there is a HuaWei office in my town. Don't know what they do there, but if I don't make any progress after I couple more days, I'll go find out.
typci said:
UPDATE:
1) I can't use FDISK because SU won't work. I'm not sure how SU/root works on a software/partition bricked phone.
2) Rooted boot.img won't boot into recovery. SuperOneClick won't work because it can't find the data partition (probably because I don't have one).
3) I was going to try flashing a custom rom but for some reason I can't get clockworkmod working again. The phone will boot into stock recovery on it's own, after a couple of reboots. However, if I change the boot.img or recovery.img to anything else, it gets stuck at huawei logo or boot loop.
4) Unbuntu LiveCD won't work (says it can't find the kernal) even though I used the installer from the website and tried it both via cd and flash drive. Working on installing a dual-boot system now.
I'm really striking out here. Couple of questions if anyone would care to answer.
1) Besides recovery, how else can I establish an adb connection? Pink screen and huawei logo give me device not found.
2) Is there a root exploit available that doesn't require a data partition or is there a root exploit I can modify so it doesn't require a data partition? It's OK if it's a manual exploit, while I'm new with android/adb, I got plenty of experience with command prompt input from back in the dos days.
Also learned there is a HuaWei office in my town. Don't know what they do there, but if I don't make any progress after I couple more days, I'll go find out.
Click to expand...
Click to collapse
On pink screen, your device is just like any other mass storage device. So you can still use fdisk on ubuntu with the correct /dev/sdX path. You can also format the data/system/cache using other tools if you need to.
Sent from my U8800 using Tapatalk 2
Sweet, so I just need to get Unbuntu working. I still can't figure out why the live CD/flash drive didn't work. Oh, well. When I get off of work I'll get to installing the dual-boot system. Thanks for your help.
typci said:
Sweet, so I just need to get Unbuntu working. I still can't figure out why the live CD/flash drive didn't work. Oh, well. When I get off of work I'll get to installing the dual-boot system. Thanks for your help.
Click to expand...
Click to collapse
i actually understood nothing from your posts but i would like to congratulate you for being a user who does research before asking ppl something
and I gladly give you a bump
JaymzBond said:
i actually understood nothing from your posts but i would like to congratulate you for being a user who does research before asking ppl something
and I gladly give you a bump
Click to expand...
Click to collapse
Thanks. Unfortunately the project is on hold for a couple of days. My electric motorcycle has been having some problems and I've been repairing it. Also, I think I found out why linux wasn't working. Apparently the "alternative" downloads aren't useable as a live CD, which is why the kernal wasn't there. Anyway, it's been a great learning experience. Maybe after I "break" my phone enough times I'll learn enough to become a developer.
Doing some research before getting back to working on the phone.
Looks like Blefish is talking about using linux's fdisk, when I was trying to use adb's fdisk. That would certainly allow me to bypass the su problem with adb. I think I got all the correct files for my linux livecd, so that shouldn't be a problem. After I'm done with my workout, I'll try it out and see how it goes. It's time to learn how to use linux.
Update: Got unbuntu working. Storage devices are all /media instead of /dev like I was expecting. But I think I'm not looking in the right place.
Plugged in phone via pink screen and 3 drives came up:
System - has system stupp (app, bin, etc, fonts, ...) - sdb12
256 MB File system - image folder with all the .img and .mbn files - sdb1
136 MB File system - has fotapkg, lost+found, recovery folders- filesystem type ext3/ext4 - I'm not sure what this is, maybe sdb6? If it was data (sdb13) then I wouldn't get the error in recovery, If it was the internal SD card the filesystem should be vfat. If someone knows better, please let me know.
For some reason I don't have permission to access the lost+found folder, or so Unbuntu tells me.
Tried to used fdisk with system, got error: I don't know how to handle files with mode 40755
Also found some recovery log files in the fotapkg and recovery folders. I'll post it here incase someone can get some more useful information out of it. Does anyone know what all these (null) mean?
Tomorrow I'll get to work on learning how to use unbuntu and fdisk.
Starting recovery on Sun Jan 6 00:03:50 1980
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 800)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot vfat /dev/block/mmcblk0p1 (null)
2 /fat vfat /dev/block/mmcblk0p1 (null)
3 /cache ext4 /dev/block/mmcblk0p6 (null)
4 /data_pseudo ext4 /dev/block/mmcblk0p13 (null)
5 /misc emmc /dev/block/mmcblk0p7 (null)
6 /recovery vfat /dev/block/mmcblk0p1 (null)
7 /HWUserData vfat /dev/block/mmcblk0p14 (null)
8 /system ext4 /dev/block/mmcblk0p12 (null)
9 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
I:cmdline: console=ttyDCC0 androidboot.hardware=huawei androidboot.localproppath=hw/default androidboot.emmc=true androidboot.image=recovery androidboot.mode=user androidboot.baseband=msm
Ita_move_command_file
I:Got arguments from boot message
Command: "recovery" "--wipe_data" "--wipe_cache"
Formatting /cache...
Creating filesystem with parameters:
Size: 136314880
Block size: 4096
Blocks per group: 32768
Inodes per group: 4160
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 33280
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/8320 inodes and 1585/33280 blocks
E:failed to mount /data_pseudo (No such file or directory)
E:failed to mount /data_pseudo (No such file or directory)
Formatting /data...
Need size of filesystem
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p13
E:failed to mount /data_pseudo (No such file or directory)
E:failed to mount /data_pseudo (No such file or directory)
Formatting /cache...
Creating filesystem with parameters:
Size: 136314880
Block size: 4096
Blocks per group: 32768
Inodes per group: 4160
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 33280
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/8320 inodes and 1585/33280 blocks
Data wipe failed.
wipe internal sdcard fail.
It could be that the data partition (originally mmcblk0p13) got wiped out and now mmcblk0p13 is internal sd card. Here's the original partition table:
Code:
Disk /dev/block/mmcblk0: 3959 MB, 3959422976 bytes
1 heads, 16 sectors/track, 483328 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 30721 245760 b Win95 FAT32 CUST
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 30721 30783 500 4d Unknown SBL1
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 30783 31158 3000 46 Unknown TZ
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 31158 483328 3617363+ 5 Extended EBR
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 32769 34304 12288 59 Unknown OEMINFO/BOOTLOADER IMAGES
/dev/block/mmcblk0p6 40961 57600 133120 4c Unknown CACHE
/dev/block/mmcblk0p7 65537 65599 500 5a Unknown MISC
/dev/block/mmcblk0p8 73729 74112 3072 58 Unknown FSG?
/dev/block/mmcblk0p9 81921 82795 7000 50 Unknown ADSP
/dev/block/mmcblk0p10 90113 90496 3072 4a Unknown MODEM_ST1
/dev/block/mmcblk0p11 98305 98688 3072 4b Unknown MODEM_ST2
/dev/block/mmcblk0p12 106497 134656 225280 83 Linux SYSTEM
/dev/block/mmcblk0p13 139265 216064 614400 83 Linux USERDATA
/dev/block/mmcblk0p14 221185 483328 2097152 69 Unknown INTERNAL_SD
The sdb6 is indeed cache, and it is used for recovery communication between Android.
If everything would be ok, it would mount sdb1, sdb6, sdb12, sdb13 and sdb14 inside Ubuntu, so it seems that something is wrong at the end.
If you have 14 partitions, use disk utility from Ubuntu and try manually formatting the 13 for ext4 and 14 for vfat. Taking ownership is not needed, it should work either way.
Blefish, thanks for the help. Got unbuntu up and working along with fdisk and identified the phone.
I have 13 partitions (including one empty one) , not 14. Here's the print out:
[email protected]:~$ sudo fdisk /dev/sde
omitting empty partition (13)
Command (m for help): p
Disk /dev/sde: 3959 MB, 3959422976 bytes
1 heads, 62 sectors/track, 124729 cylinders, total 7733248 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sde1 1 491520 245760 b W95 FAT32
/dev/sde2 * 491521 492520 500 4d QNX4.x
/dev/sde3 492521 498520 3000 46 Unknown
/dev/sde4 498521 7733247 3617363+ 5 Extended
/dev/sde5 524288 548863 12288 59 Unknown
/dev/sde6 655360 921599 133120 4c Unknown
/dev/sde7 1048576 1049575 500 5a Unknown
/dev/sde8 1179648 1185791 3072 58 Unknown
/dev/sde9 1310720 1324719 7000 50 OnTrack DM
/dev/sde10 1441792 1447935 3072 4a Unknown
/dev/sde11 1572864 1579007 3072 4b Unknown
/dev/sde12 1703936 2154495 225280 83 Linux
Comparing with your partition table I see two differences:
1) the ending block of sde1 is 491520 on mine and on the original it is 30721, however the blocks are the same, so that is probably not a problem
2) sde13 is empty, and sde14 is missing.
This actually makes sense. When I was using MIUI, I reduced the size of the internal sd to near zero, since MIUI could only either the internal or external sd, not both. After trying to downgrade, I had a problem, so I tried to restore the internal sd card back to stock size, just to bring my phone back to stock. Something must have gone when I did that.
So if I understand the problem correctly, to fix this I need to:
1) Split sde13 into 2 partitions
2) Format sde13 to ext4 and sde14 to vfat
3) Try installing adroid again
Do I need to name the partitions a certain name or do anything else?
In the mean time I'll be looking into how to use disk utility and fdisk to deal with sde13 and sde14.
Had an idea that I only need sde13 (data) to get things working again, the system shouldn't need sde14 (internal sd) to work.
So I went to disk utility, found Qualcomm MMC storage and tried to format the free 2.9GB at the end. Got an error:
Error creating partition: helper exited with exit code 1: In part_add_partition: device_file=/dev/sde, start=1103101952, size=2856000000, type=0x83
Entering MS-DOS parser (offset=0, size=3959422976)
MSDOS_MAGIC found
looking at part 0 (offset 512, size 251658240, type 0x0b)
new part entry
looking at part 1 (offset 251658752, size 512000, type 0x4d)
new part entry
looking at part 2 (offset 252170752, size 3072000, type 0x46)
new part entry
looking at part 3 (offset 255242752, size 3704180224, type 0x05)
Entering MS-DOS extended parser (offset=255242752, size=3704180224)
readfrom = 255242752
MSDOS_MAGIC found
readfrom = 255243264
MSDOS_MAGIC found
readfrom = 255243776
MSDOS_MAGIC found
readfrom = 255244288
MSDOS_MAGIC found
readfrom = 255244800
MSDOS_MAGIC found
readfrom = 255245312
MSDOS_MAGIC found
readfrom = 255245824
MSDOS_MAGIC found
readfrom = 255246336
MSDOS_MAGIC found
readfrom = 1140842496
No MSDOS_MAGIC found
Exiting MS-DOS extended parser
Exiting MS-DOS parser
MSDOS partition table detected
containing partition table scheme = 1
got it
Error: Invalid partition table on /dev/sde -- wrong signature 0.
ped_disk_new() failed
So, my partition table is corrupt? I'll need to figure out how to fix this.
Here's some options I've found:
http://forum.xda-developers.com/showpost.php?p=21572216&postcount=12
ksatta mentions a couple of ideas:
1) If someone backed up their phone using dd, I could use that to restore my phone.
Here's a link on how to do it: http://linuxpoison.blogspot.com/2009/04/creating-backuprestore-images-using-dd.html
dd if=/dev/sdX | gzip > /home/sdX.bin.gz
where sdX is the U8800
2) I could clone someone's partition table. If someone could give me a copy of their MBR that should work.
Here's a link on how to do it: http://embraceubuntu.com/2005/10/20/backing-up-the-mbr/
Create a backup of your MBR by doing a:
dd if=/dev/sdX of=MBR-backup bs=512 count=1
That should read “create a disk dump of the input file, which is /dev/sdx (change to hda, or hdb or sda, depending on where the MBR is on your computer), and save it in the output-file MBR-backup in the directory from where the command is issued. Backup the first sector only, while you are at it”.
3) gparted - it's some kind of partition tool. Might be able to use it to fix the error. Not sure how to use it though.
For now I'm going to look into gparted for Ubuntu. If someone can help me out with a dd backup or cloning the partition table that would be awesome.
UPDATE: For people following this thread, and to keep me more organized, I'll start adding more of the important resources I find. They may one day help you fix your phone.
https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/434463
Seems a guy fixed his the same error with gparted. However it wasn't on a phone. Also I'm seem a lot of people refer to sfdisk. I'll need to learn more about it.
https://answers.launchpad.net/ubuntu/+question/113539
"I got an answer in a forum, which looks easy.
Do a
sudo fdisk /dev/sda
then type
w
to write partition table, without any modification of it.
The signature should be fixed."
Is this safe to do to my phone? I know I'll have to write the MBR eventually, but I have to get it right the first time. If I screw up, I may not be able to connect to ubuntu anymore. Anyway, the guy said it fixed the error with his harddrive, so it's worth a try.
http://www.thegeekstuff.com/2010/09/linux-fdisk/
How to use fdisk, in case anyone needs to know
So my new plan is to:
1) dd Backup and MBR backup - in case I break it worse than it is
2) try to fix with fdisk w or gparted
I think the change in start and end is caused by Ubuntu using cylinders/sectors/blocks. Should not too much difference though.
Using MBR restore would not work here, as it restores the main 4 partitions list. MBR uses EBR aswell, which is located at the beginning of every extended partition. So we would have to copy the EBR of every partition.
I'd suggest deleting sde13, adding sde13 and sde14.
When adding sde13, note that starting block should be at the end of sde12, so simply insert last block of sde12 there. If it gives error, simply press enter as it automatically finds free block after the last one. End block could be for example +500M so fdisk automatically finds the correct end block. Do the same for sde14, but note the start block again. sde14 end block should be the last block there is on the card.
After you've done that, do w to write and if it tells you to restart or something, unplug the phone, take out the battery and restart to pink screen again. Then try to use disk utility again or gparted (have not tested this) to reformat sde13 and sde14 to ext4 and vfat.
You should be safe until you don't mess with the primary partitions, especially the mmcblk0p2 and mmcblk0p3.
Thanks again for the reply, Blefish. I may have just fixed it. I'll know soon enough.
I did two things:
1) sudo fdisk /dev/sde12 followed by w
2) sudo fdisk /dev/sde followed by w
After that it enabled me to add the 13 and 14 partition. I used disk utility so I didn't have to worry about the blocks. Afterwards they mounted in ubuntu like they should.
UPDATE: Not quite fixed, but the rom installed without error. So I think the partition problem is fixed.
Now I just have a boot loop. I'll go back to ubuntu, clear the cache, and try installing from the internal sdcard
2nd UPDATE: Stock recovery gives and error about mounting the cache partition. However CWM mounts it fine. My partition problems may not be over.
3rd UPDATE: genokolar's "Custom you partition" file to return to stock file deletes my partition 13 and 14. Had 13 and 14 back working, used the file as per instructions, afterwards ubuntu drive utililty shows 13 and 14 as "free." So that is where part of my problem comes from.
4th UPDATE: Fixed the problem with stock recovery. Turns out froyo doesn't like ext4 partitions. Changed cache partition to ext3, no more error.
Here are some exerts from the CMW log when I tried to flash cyanongen. Can anyone tell me if any of these errors are problems, and if they are what they mean?
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
failed to open /sys/class/android_usb/android0/state: No such file or directory
-- Installing: /sdcard/CM7-070512.zip
Finding update package...
I:Update location: /sdcard/CM7-070512.zip
Opening update package...
Installing update...
unmount of /system failed; no such volume
package_extract_file: no backup_initd.sh in package
set_perm: chown of /tmp/backup_initd.sh to 0 0 failed: No such file or directory
set_perm: chmod of /tmp/backup_initd.sh to 777 failed: No such file or directory
about to run program [/tmp/backup_initd.sh] with 2 args
run_program: execv failed: No such file or directory
run_program: child exited with status 1
Pass 5: Checking group summary information
/dev/block/mmcblk0p12: 11/56448 files (0.0% non-contiguous), 7142/225280 blocks
mount: failed to mount /dev/block/mmcblk0p12 at /system: Invalid argument
set_perm: chown of 0750 to 0 2000 failed: No such file or directory
set_perm: chmod of 0750 to 755 failed: No such file or directory
set_perm: chown of /system/etc/init.qcom.post_boot.sh to 0 2000 failed: No such file or directory
set_perm: chmod of /system/etc/init.qcom.post_boot.sh to 555 failed: No such file or directory
set_perm: chown of /system/xbin/apply_firewall to 0 0 failed: No such file or directory
set_perm: chmod of /system/xbin/apply_firewall to 6755 failed: No such file or directory
set_perm: chown of /system/xbin/apply_theme to 0 0 failed: No such file or directory
set_perm: chmod of /system/xbin/apply_theme to 6755 failed: No such file or directory
set_perm: chown of /system/xbin/dumplog to 0 0 failed: No such file or directory
set_perm: chmod of /system/xbin/dumplog to 6755 failed: No such file or directory
set_perm: chown of /system/xbin/mv2sd to 0 0 failed: No such file or directory
set_perm: chmod of /system/xbin/mv2sd to 6755 failed: No such file or directory
set_perm: chown of /system/xbin/ota to 0 0 failed: No such file or directory
set_perm: chmod of /system/xbin/ota to 6755 failed: No such file or directory
Updating BOOT Image...
about to run program [/tmp/backup_initd.sh] with 2 args
run_program: execv failed: No such file or directory
run_program: child exited with status 1
Installation complete!script result was [Installation complete!]
Install from sdcard complete.
failed to open /sys/class/android_usb/android0/state: No such file or directory
My phone is fixed. I have no idea how it became fixed, but it is fixed.
I placed b518 on the internal sd card, and installed it. Then bootloop. So I held both volume keys+power to try another rom. It installed again. Went to recovery, it did a factory reset. Bootloop. Went back to recovery to see if I could wipe the sd card. No option for it, so I did another factory reset and rebooted my phone. I left my phone bootlooping for a minute while I looked online for a Huawei service center, and then my phone booted. I gues it got scared and didn't want to go to a service center.
This been a great learning experience, although at times a major headaches. I want to thank blefish for all his help. Thanks to this, i've bee reading his blog and other stuff, and now will follow some of his other projects.
Now to downgrade back to 2.2!!!!
UPDATE: All official roms are working correctly (b136, b138, b518, b528), recovery (5.0.2.6) works. However I haven't been able to get a single custom rom to work. Tried a couple .32 MIUI and CM, but they all stick at the huawei logo. Did factory reset and dalvik wipe, get error can't mount /sd-ext during dalvik wipe, and still doesn't boot.
Maybe I need to try a newer verison of CWM? I tried the newer versions before, and I didn't like them. Buggy and often wouldn't find my sd card.
This thread must be made sticky because it consists of pure information about dealing with soft-bricks. Thanks a lot for your curiosity, you're my hero.
QFLASH Problem
What the hell .. squint emoticon
"No data read from USB. This may not be an error. Trying again..."
if anyone knw about it so Guide me .i am very close :|
D:\Downloads\Compressed\Moto.X.Unbrick\Python27>python 8960_blankflash.py
Emergency download enumeration detected on port - com3
Starting qflash!
Executing command qflash.exe -com3 -ramload MPRG8960.hex -mbn 33 MSM8960_bootloa
der_singleimage.bin -v -o
Motorola qflash Utility version 1.3
COMPORT :COM3
RAMLOADER :MPRG8960.hex
type is 0x21
7 mbn file name MSM8960_bootloader_singleimage.bin type 33
verbose mode on
Motorola qflash dll version 1.6
RAMLOADER VERSION: PBL_DloadVER2.0
------------------------------------------------------
DEVICE INFORMATION:
------------------------------------------------------
Version : 0x8
Min Version : 0x1
Max Write Size: 0x600
Model : 0x90
Device Size : 0
Description : Intel 28F400BX-TL or Intel 28F400BV-TL
------------------------------------------------------
Using passed in packet size, changing from 0x600 -> 0x600
EXTENDED_LINEAR_ADDRESS_REC @ 0x2a000000
Write 65536 bytes @ 0x2a000000
100EXTENDED_LINEAR_ADDRESS_REC @ 0x2a010000
Write 11840 bytes @ 0x2a010000
100START_LINEAR_ADDRESS_REC @ 0x2a000000
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
Still no data, giving up!
dmss_go : failed to receive ACK
Error loading MPRG8960.hex into device
Blank flashing successful
Device will now enumerate in fastboot mode
D:\Downloads\Compressed\Moto.X.Unbrick\Python27>pause
Press any key to continue . .
The X cores GUIDE
About
I have created many bootloop-fix boot images in the past and as the way to do it on your own is (in general) very easy I wanted to write it down so everyone can do it by himself.
The reason? The ILAPO (hardware related bootloop) happens due to overheating and so throttling the device may help in extends the life of your device and can even resurrect your phone when in a bootloop.
Again using a reduced amount of cores will be a temporary fix only as the ILAPO is a hardware issue! Read the bootloop-fixit-list for details.
Maybe you do not need to create one - checkout the current available 4-core boot images here: temporary-bootloop-fix-thread
This requires an unlocked device to flash and use!
Howto
Creating a custom boot image is very easy and done in 5 sec.
you need the tool: abootimg - so Linux or FWUL (included since v3.0)
Code:
abootimg -i boot.img
note and copy the whole cmdline output. Example (in red and bold):
Code:
Android Boot Image Info:
* file name = boot.img
* image size = 29614080 bytes (28.24 MB)
page size = 4096 bytes
* Boot Name = ""
* kernel size = 26722280 bytes (25.48 MB)
ramdisk size = 1668572 bytes (1.59 MB)
* load addresses:
kernel: 0x00008000
ramdisk: 0x01000000
tags: 0x00000100
* [B][COLOR="Red"]cmdline = console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 msm_rtb.filter=0x37 boot_cpus=0-5 buildvariant=userdebug[/COLOR][/B]
* id = 0xf19c37df 0x9734fb7a 0x3c6b45f4 0x3a8d0267 0x32786841 0x00000000 0x00000000 0x00000000
Ok now you need to modify - NOT UNPACK the boot image!! thats 1) not necessary and 2) it will make your boot image unbootable (when using abootimg).
Now modify for your wanted amount of cores.
Let's assume you want to use in Android 4 cores as max and on boot 4 cores max as well:
Code:
abootimg -u boot.img -c "cmdline = [B]maxcpus=4 boot_cpus=0-3[/B] [COLOR="Red"]console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 msm_rtb.filter=0x37 boot_cpus=0-5 buildvariant=userdebug[/COLOR]"
Noted the bold part: maxcpus=4 boot_cpus=0-3 ? That is the magic which sets the wanted cores.
Noted the red part: console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 msm_rtb.filter=0x37 boot_cpus=0-5 buildvariant=userdebug ?
Thats just the regular cmdline copied from the original boot image you written done in the first step.
You may noticed that there is another boot_cpus value in that particular case set right? boot_cpus=0-5 in this case. You can remove or leave it as u like.
The reason is: the boot cmdline will be handled like: first match = wins. so when doing as explained you will set boot_cpus and maxcpus at the very beginning of the cmdline and so we will overwrite whatever comes next.
maxcpus=X (recommended value for bootloop devices: 4)
> Maximum number of processors that an SMP kernel should make use of. maxcpus=n : n >= 0 limits the kernel to using 'n' processors. n=0 is a special case, it is equivalent to "nosmp", which also disables the IO APIC. (source)
X can be from 1 to 6 and defines the maximal available amount of cores in Android. If you set it to 4 Android can use 4 only. For Android you must enable them manually which requires always root access (e.g. by an app like Kernel Adiutor)
boot_cpus=Y-Z (recommended value for bootloop devices: "0-3" or if that still bootloops "0-1")
> Rather than attempting to online all possible CPUs at boot time, only online the specified set of CPUs. (source)
Y-Z can be 0-5(!) yes there is no 6! Thats the CPU core "IDs" to use on boot. 0-3 will use 4 cpus (so only the little cores which are: 0,1,2,3 - as 4 and 5 are the big ones causing the ILAPO more) on boot. Note that the setting differs to maxcpus as the numbers here starting from 0 where 0 is the first core. You can set a single core, comma separated core IDs or define ranges here. When you want to set just a single core here it may be required to set boot_cpus=1 instead of boot_cpus=0.
Verify your modified boot image:
Code:
abootimg -i boot.img
Android Boot Image Info:
* file name = boot.img
* image size = 29614080 bytes (28.24 MB)
page size = 4096 bytes
* Boot Name = ""
* kernel size = 26722280 bytes (25.48 MB)
ramdisk size = 1668572 bytes (1.59 MB)
* load addresses:
kernel: 0x00008000
ramdisk: 0x01000000
tags: 0x00000100
* [B]cmdline = maxcpus=4 boot_cpus=0-3 console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 msm_rtb.filter=0x37 boot_cpus=0-5[/B]
buildvariant=userdebug
* id = 0x00000160 0x4bd3a2b4 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
Whats next?
So now you're prepared to flash your modified X cores boot image via fastboot and see if it boots
Code:
fastboot boot boot.img
This above will *temporary* boot your modified boot image and is meant for testing it only.
To install it permanently use this command in fastboot mode:
Code:
fastboot flash boot boot.img
You can do this on every boot image or recovery image (so yes even on TWRP !)
Cheers
steadfasterX
reserved.
Any way to fix issue in locked device? Still stucked on lollipop with root.
kalanakodicara said:
Any way to fix issue in locked device? Still stucked on lollipop with root.
Click to expand...
Click to collapse
depends on your device and current ARB. I added the aboot TOT flashing method which also works on locked devices but u need to take care of the ARB (all mentioned there including links etc):
https://forum.xda-developers.com/g4/help/guide-ultimate-bootloop-fixit-list-t3667688
,
steadfasterX said:
depends on your device and current ARB. I added the aboot TOT flashing method which also works on locked devices but u need to take care of the ARB (all mentioned there including links etc):
https://forum.xda-developers.com/g4/help/guide-ultimate-bootloop-fixit-list-t3667688
,
Click to expand...
Click to collapse
Its h815 SEA and can i use tot method for v29a or 20p?
How can I extract boot.img from phone or KDZ file, so I can modify it. I tryed to make backup from twrp, but the file is boot.emmc.win...
I have H815 20g_00_0720.kdz, rooted, TWRP
steadfasterX said:
The X cores GUIDE
About
I have created many bootloop-fix boot images in the past and as the way to do it on your own is (in general) very easy I wanted to write it down so everyone can do it by himself.
The reason? The ILAPO (hardware related bootloop) happens due to overheating and so throttling the device may help in extends the life of your device and can even resurrect your phone when in a bootloop.
Again using a reduced amount of cores will be a temporary fix only as the ILAPO is a hardware issue! Read the bootloop-fixit-list for details.
Maybe you do not need to create one - checkout the current available 4-core boot images here: temporary-bootloop-fix-thread
This requires an unlocked device to flash and use!
Howto
Creating a custom boot image is very easy and done in 5 sec.
you need the tool: abootimg - so Linux or FWUL
Code:
abootimg -i boot.img
note and copy the whole cmdline output. Example (in red and bold):
Code:
Android Boot Image Info:
* file name = boot.img
* image size = 29614080 bytes (28.24 MB)
page size = 4096 bytes
* Boot Name = ""
* kernel size = 26722280 bytes (25.48 MB)
ramdisk size = 1668572 bytes (1.59 MB)
* load addresses:
kernel: 0x00008000
ramdisk: 0x01000000
tags: 0x00000100
* [B][COLOR="Red"]cmdline = console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 msm_rtb.filter=0x37 boot_cpus=0-5 buildvariant=userdebug[/COLOR][/B]
* id = 0xf19c37df 0x9734fb7a 0x3c6b45f4 0x3a8d0267 0x32786841 0x00000000 0x00000000 0x00000000
Ok now you need to modify - NOT UNPACK the boot image!! thats 1) not necessary and 2) it will make your boot image unbootable (when using abootimg).
Now modify for your wanted amount of cores.
Let's assume you want to use in Android 4 cores as max and on boot 4 cores max as well:
Code:
abootimg -u boot.img -c "cmdline = [B]maxcpus=4 boot_cpus=0-3[/B] [COLOR="Red"]console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 msm_rtb.filter=0x37 boot_cpus=0-5 buildvariant=userdebug[/COLOR]"
Noted the bold part: maxcpus=4 boot_cpus=0-3 ? That is the magic which sets the wanted cores.
Noted the red part: console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 msm_rtb.filter=0x37 boot_cpus=0-5 buildvariant=userdebug ?
Thats just the regular cmdline copied from the original boot image you written done in the first step.
You may noticed that there is another boot_cpus value in that particular case set right? boot_cpus=0-5 in this case. You can remove or leave it as u like.
The reason is: the boot cmdline will be handled like: first match = wins. so when doing as explained you will set boot_cpus and maxcpus at the very beginning of the cmdline and so we will overwrite whatever comes next.
maxcpus=X (recommended value for bootloop devices: 4)
X can be 1-6 and this defines the maximal amount of cores in Android. If you set it to 4 Android can use 4 only.
boot_cpus=Y-Z (recommended value for bootloop devices: "0-3" or if that still bootloops "0-1")
Y-Z can be 0-5(!) yes no 6! Thats the CPU core number to use on boot. 0-3 will use 4 cpus (so only the little ones) on boot. The difference to maxcpus is that the cpu number starting from 0 where 0 is the first core.
Verify your modified boot image:
Code:
abootimg -i boot.img
Android Boot Image Info:
* file name = boot.img
* image size = 29614080 bytes (28.24 MB)
page size = 4096 bytes
* Boot Name = ""
* kernel size = 26722280 bytes (25.48 MB)
ramdisk size = 1668572 bytes (1.59 MB)
* load addresses:
kernel: 0x00008000
ramdisk: 0x01000000
tags: 0x00000100
* [B]cmdline = maxcpus=4 boot_cpus=0-3 console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 msm_rtb.filter=0x37 boot_cpus=0-5[/B]
buildvariant=userdebug
* id = 0x00000160 0x4bd3a2b4 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
Whats next?
So now you're prepared to flash your modified X cores boot image via fastboot and see if it boots
You can do this on every boot image or recovery image (so yes even on TWRP !)
Cheers
steadfasterX
Click to expand...
Click to collapse
Snapdaragon 808 only!
All you have to do is flashing in twrp
Off the kernel's big core
https://drive.google.com/file/d/1ij-qm5qWezoRykwjoTlg0BcQ-do21QIp/view?usp=drivesdk
DomagojX said:
How can I extract boot.img from phone or KDZ file, so I can modify it. I tryed to make backup from twrp, but the file is boot.emmc.win...
I have H815 20g_00_0720.kdz, rooted, TWRP
Click to expand...
Click to collapse
Use SALT to take a basic backup. You will find the boot image there too.
Use SALT as well to extract a kdz.
lq092009 said:
Snapdaragon 808 only!
All you have to do is flashing in twrp
Off the kernel's big core
https://drive.google.com/file/d/1ij-qm5qWezoRykwjoTlg0BcQ-do21QIp/view?usp=drivesdk
Click to expand...
Click to collapse
Awesome. I have everything prepared to modify boot images on the fly but no time yet to finish it.
Before I started with implementing this I tried unpacking and packaging like you do here (mkbootimg etc) and failed:
Unless you use special versions of unpack image your method will not work for the g4 and results in a soft brick as we need to unpack and pack including the dt.img. Otherwise the kernel will not boot. I tried that already and that was an issue with TWRP long time ago, too.
But thanks anyways and let me know if you can do the same but including the dt
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Use SALT to take a basic backup. You will find the boot image there too.
Use SALT as well to extract a kdz.
Awesome. I have everything prepared to modify boot images on the fly but no time yet to finish it.
Before I started with implementing this I tried unpacking and packaging like you do here (mkbootimg etc) and failed:
Unless you use special versions of unpack image your method will not work for the g4 and results in a soft brick as we need to unpack and pack including the dt.img. Otherwise the kernel will not boot. I tried that already and that was an issue with TWRP long time ago, too.
But thanks anyways and let me know if you can do the same but including the dt
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
It must be flashing before modifying the kernel with a magisk or supersu
lq092009 said:
It must be flashing before modifying the kernel with a magisk or supersu
Click to expand...
Click to collapse
Sure. That's not the problem. I referring to the dt.img which does not get extracted from the boot image the way you do it. Without this the device will not boot as the bootloader aboot needs it!
This has nothing to do with magisk or supersu.
Sent from my LG-H815 using XDA Labs
I've been using this on a phone that was overheating a couple times a day. It's been two days without a reboot/loop. Thanks!
You've given new life for a phone that was sitting in a drawer. This, combined with the bootloader unlock, and the roms are fantastic!
DoughMucker said:
I've been using this on a phone that was overheating a couple times a day. It's been two days without a reboot/loop. Thanks!
You've given new life for a phone that was sitting in a drawer. This, combined with the bootloader unlock, and the roms are fantastic!
Click to expand...
Click to collapse
I'm glad it helps
Sent from my LG-H815 using XDA Labs
Can I do it on Nougat or Oreo based roms? Do I need to flash the rom first and then edit or do it before?
ojcu said:
Can I do it on Nougat or Oreo based roms? Do I need to flash the rom first and then edit or do it before?
Click to expand...
Click to collapse
ANY means ANY right?
You would first first flash your ROM then the modified boot image.
.
steadfasterX said:
ANY means ANY right?
.
Click to expand...
Click to collapse
I know it was one of the noobest questions I could ask but I've never done it before so just making sure. Thanks
I've had a quick look for a way to do this from within android but had no luck. I wonder if there's a kitchen tool in the play store that would work, or some android shell or busybox type add-on.
@steadfasterX Apologies for the noob request, I am not very good with linux , i followed the steps above , and when i try to flash the boot image it raises an error in fastboot remote:image is not a boot image
Kindly assist me.
steadfasterX said:
The X cores GUIDE
About
I have created many bootloop-fix boot images in the past and as the way to do it on your own is (in general) very easy I wanted to write it down so everyone can do it by himself.
The reason? The ILAPO (hardware related bootloop) happens due to overheating and so throttling the device may help in extends the life of your device and can even resurrect your phone when in a bootloop.
Again using a reduced amount of cores will be a temporary fix only as the ILAPO is a hardware issue! Read the bootloop-fixit-list for details.
Maybe you do not need to create one - checkout the current available 4-core boot images here: temporary-bootloop-fix-thread
This requires an unlocked device to flash and use!
Howto
Creating a custom boot image is very easy and done in 5 sec.
you need the tool: abootimg - so Linux or FWUL
Code:
abootimg -i boot.img
note and copy the whole cmdline output. Example (in red and bold):
Code:
Android Boot Image Info:
* file name = boot.img
* image size = 29614080 bytes (28.24 MB)
page size = 4096 bytes
* Boot Name = ""
* kernel size = 26722280 bytes (25.48 MB)
ramdisk size = 1668572 bytes (1.59 MB)
* load addresses:
kernel: 0x00008000
ramdisk: 0x01000000
tags: 0x00000100
* [B][COLOR="Red"]cmdline = console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 msm_rtb.filter=0x37 boot_cpus=0-5 buildvariant=userdebug[/COLOR][/B]
* id = 0xf19c37df 0x9734fb7a 0x3c6b45f4 0x3a8d0267 0x32786841 0x00000000 0x00000000 0x00000000
Ok now you need to modify - NOT UNPACK the boot image!! thats 1) not necessary and 2) it will make your boot image unbootable (when using abootimg).
Now modify for your wanted amount of cores.
Let's assume you want to use in Android 4 cores as max and on boot 4 cores max as well:
Code:
abootimg -u boot.img -c "cmdline = [B]maxcpus=4 boot_cpus=0-3[/B] [COLOR="Red"]console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 msm_rtb.filter=0x37 boot_cpus=0-5 buildvariant=userdebug[/COLOR]"
Noted the bold part: maxcpus=4 boot_cpus=0-3 ? That is the magic which sets the wanted cores.
Noted the red part: console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 msm_rtb.filter=0x37 boot_cpus=0-5 buildvariant=userdebug ?
Thats just the regular cmdline copied from the original boot image you written done in the first step.
You may noticed that there is another boot_cpus value in that particular case set right? boot_cpus=0-5 in this case. You can remove or leave it as u like.
The reason is: the boot cmdline will be handled like: first match = wins. so when doing as explained you will set boot_cpus and maxcpus at the very beginning of the cmdline and so we will overwrite whatever comes next.
maxcpus=X (recommended value for bootloop devices: 4)
X can be 1-6 and this defines the maximal amount of cores in Android. If you set it to 4 Android can use 4 only.
boot_cpus=Y-Z (recommended value for bootloop devices: "0-3" or if that still bootloops "0-1")
Y-Z can be 0-5(!) yes no 6! Thats the CPU core number to use on boot. 0-3 will use 4 cpus (so only the little ones) on boot. The difference to maxcpus is that the cpu number starting from 0 where 0 is the first core.
Verify your modified boot image:
Code:
abootimg -i boot.img
Android Boot Image Info:
* file name = boot.img
* image size = 29614080 bytes (28.24 MB)
page size = 4096 bytes
* Boot Name = ""
* kernel size = 26722280 bytes (25.48 MB)
ramdisk size = 1668572 bytes (1.59 MB)
* load addresses:
kernel: 0x00008000
ramdisk: 0x01000000
tags: 0x00000100
* [B]cmdline = maxcpus=4 boot_cpus=0-3 console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 msm_rtb.filter=0x37 boot_cpus=0-5[/B]
buildvariant=userdebug
* id = 0x00000160 0x4bd3a2b4 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
Whats next?
So now you're prepared to flash your modified X cores boot image via fastboot and see if it boots
You can do this on every boot image or recovery image (so yes even on TWRP !)
Cheers
steadfasterX
Click to expand...
Click to collapse
Hello @steadfasterX
I wanted to request your assistance in creating a custom boot image for my device I tried to do it from your thread a couple of times I really don't know what the issue could be.
It raises the error remote :image is not a boot image when I try to flash it in fastboot
I have attached a link to my boot.bin image file
Thanks.https://mega.nz/#!m8QRXSJJ!R90SoS48O...IJ_Uvdrsp9tYoE
I am on the latest twrp for N posted on your server
izzle47 said:
Hello @steadfasterX
I wanted to request your assistance in creating a custom boot image for my device I tried to do it from your thread a couple of times I really don't know what the issue could be.
It raises the error remote :image is not a boot image when I try to flash it in fastboot
I have attached a link to my boot.bin image file
Thanks.https://mega.nz/#!m8QRXSJJ!R90SoS48O...IJ_Uvdrsp9tYoE
I am on the latest twrp for N posted on your server
Click to expand...
Click to collapse
first of all I have a friendly advice for you never ever quote big posts like mine. Regarding your problem try FWUL to modify it. I have no time at the moment sorry but maybe someone else can help you as well if FWUL doesn't help
Sent from my LG-H815 using XDA Labs
Hi
Thanks for sharing the method. I want to boot with only 1 core and later use 4 cores. How can i write for that:
maxcpus=4 boot_cpus=0-0
OR
maxcpus=4 boot_cpus=0
Also wanted to confirm that when do the maxcpus=4 become functional, i gues that starts to happen right after the LG logo appears or it happens when the boot process has finished.
I am guessing that boot_cpus=0-0 and 0 are not working. I can guess that because of the speed the animated logo appears. WHen it set it like max_cpus=1 it only boots and works on one core.
WHat i want is to boot with one core and later automatically switch to 4 cores when the system has loaded.