I need help guys!!! Here is the thing i was using many roms starting from DFT LEO NAND to latest ICS, and with ICS instalation started with problems. hd2 started to crush while he was working and when i wanted to boot bootloader was loading and keep loading forever (using (Android 4.0.3) (AOSP ICS ROM for HD2) NexusHD2-IceCreamSandwich Beta10).
I used again ROM who was before ICS - NexusHD2-Gingerbread V3.2a (GWK74)(Android 2.3.7)[tytung_r13] and more roms using MALDGR >> all roms i install normaly and boot up and when i reboot they are going on Splash loader and keep it there forever. I tried all methods using task29, radio, magldr (installing again) still nothing and when i wanted to install DFT LEO NAND again i have error on the end of installation :
Error Description: send partition data failed
Info: .\RSPL\RSPL.cpp (802)
Error Description: flash write failed.
Info: .\RSPL\RSPL.cpp (586).
I tried to remove sd card and also did active sync detach still nothing
Any ideas.
Why will you type a whole message in bold?!
Looks like you're volumes keys may be stuck or acting up... I had this happen sometime back, ended up changing the main flex circuit strip.
Sent from my HTC HD2 using XDA
ph03n!x said:
Why will you type a whole message in bold?!
Looks like you're volumes keys may be stuck or acting up... I had this happen sometime back, ended up changing the main flex circuit strip.
Sent from my HTC HD2 using XDA
Click to expand...
Click to collapse
Sorry for my bold writing
i checked mu volume keys and everything is ok. Today i changed my radio and booted ROM everything was fine several time i rebooted and when i go in clockwork mode mode on botom of screen it is written somthing like E:/error/ recovery log etc etc. is it possible that i did something wrong with mu internal partition
here is the thing with DFT LEO NAND on my screen
USB Flasher mode
Wait USB...USB
Lauout...PC=4, ASI=3 OASI=5
Erase...
k = 25-> 23D 25 219, 1000
0: part = 37, part2 = 37
1: total = 1999, extra = 99
2: total = 320, extra = 16
[ASIZE] START: BB0 END: f40 SIZE: 390
PARTITION LAYOUT NEW
0: 0219 023E 50 89
1: 023E 0A70 50 01
2: 0A70 0BB0 50 01
3: 0BB0 0F40 20 01
Erase...
D S: 0 E: 219
D S: 1 E: 23E
D S: 2 E: A70
D S: 3 E: BB0
Save EMBR...
Default OS is AD NAND...
Flashing 0 partition...0 [219-23E] M1 OK 8B21 22C
Flashing 1 partition...1 [23E-A70] M1
and stuck loading on almost 90 %
There i get erroron DFT FLASHER:
Error Description: send partition data failed
Info:.\RSPL\RSPL.cpp (802)
Error Description: flash write failed.
Info: .\RSPL\RSPL.cpp (586)
Related
Hi
Yesterday with SEUS my X10 is bicked, today i try all this ways and all the same result BRICKED.
1º Several times with SEUS, 2 pcs, and not installed.
2º pccompanion connect to X10 but not identifie.
3º flashupdate with step 1 of root way, several times, KO
Code:
INFO: <<<ERR_SEVERITY="MAJOR";ERR_CLASS="PROTOCOL_CLASS";ERR_STATIC="UNVALID_COMMAND";ERR_DYNAMIC="";
30-jun-2010 12:11:52 X10flash writeCmd
INFO: write(cmd=10) (finish)
30-jun-2010 12:11:52 X10flash readReply
INFO: <<< cmd=10,flags=0,length=0
30-jun-2010 12:11:52 X10flash writeCmd
INFO: write(cmd=4) (finish)
30-jun-2010 12:11:52 X10flash readReply
INFO: <<< cmd=4,flags=1,length=0
30-jun-2010 12:11:52 X10flash run
INFO: ###test end.
4º With special pack unbrick XIOFUB, the same result, KO
hotfile.com/dl/44983907/9d54b5e/XIOFUB.rar.html
5º With Omnius, the same result, KO
Code:
13:11:49 Flash
13:11:49 Allows to change languages supported by the phone and upgrade its firmware.
13:11:49 Operating system: Microsoft Windows XP Home Edition Service Pack 3 (build 2600)
13:11:49 Application version: 0.04.2151 (beta)
13:11:49 . The action name is 'Flash'
13:11:49 Selected phone type: Xperia™ X10
13:11:49 i Instructions
13:11:49 i 1. Make sure the phone battery is charged to at least 50%.
13:11:49 i 2. Switch off the phone!
13:11:49 i 3. Remove the phone battery and wait at least 5 seconds before reinserting it!
13:11:49 i 4. Press and hold the return back button, then connect the cable to the phone!
13:11:49 . The action started waiting for the user
13:12:31 . The action finished waiting for the user
13:12:31 Conectado por medio de Dispositivo Flash USB SEMC (USB1)...
13:12:31 Version del controlador: 2.2.0.5
13:12:31 Cip detectado: QSD8250
13:12:31 Modo de Arranque: EROM
13:12:31 IMEI:
13:12:31 Enviando Cargador...
13:12:33 Establishing connection to the server...
13:12:38 Receiving news...
13:12:39 i No news
13:12:40 Actual credit: 0.00
13:12:46 Writing file R1FA016_APP_SW_RACHAEL_GENERIC_1227_4612_S1_SW_LIVE_AC12_0001_S1_PARTITION.zip...
13:13:16 e ¡Fallo!
13:13:16 . The action entered shutdown phase
13:13:16 . The action reported failure
Error code
# C882780696072EA7
Detalles del error
---
11 2C C9 F3 6E FE 3A DF 5C 3D FE F8 38 EA 82 99
EE D9 94 3C B0 8F 36 FB 3D B5 B1 B8 86 08 EE A7
44 5B AA 5E 60 2C A6 D1 86 58 4C 8A E8 79 A2 23
11 08 38 33 3E 30 EA 6F D4 29 2A D4 0A 7E 9C 18
DC B5 8A 47 D4 C6 F8 BF B2 4C C2 35 08 29 3E C9
14 65 FA E3 70 CF A4 62 F4 3D CE 0B 18 76 AE 99
04 EB 62 74 CE B3 9A 01 04 1D A2 D5 D8 C3 D6 3C
61 E8
---
6º With Davinci, the same result, KO
Code:
Getting Software List From Server For: X10 / 0001 / Red...
SELECTED: Flash / Debrand / Re-Brand [SonyEricsson] X10 / 0001 / Red / R2BA020 / O2 DE/LUSTER WHITE (1233-2794/R14A | GENERIC)
Script Execution Started...
Checking Files...
Downloading 85Kb...OK! (1 sec)
Downloading 16268Kb...OK! (47 sec)
Downloading 131984Kb...OK! (413 sec)
Starting up...
Script initialization. Please wait...
Loading S1 Loader... OK
20091222 15:39:00 S1_LOADER R4A024 1226-2250
Memory Stick: 8GB
Opening TA...OK
Reading TA Please Wait...OK
Closing TA...OK
Opening MiscTA...OK
Reading TA Please Wait...OK
Requesting Account Status...OK
User: 49574 / Credits: 0 / Counters: 10
Writing TA Data...OK
Writing APP-SW/amss_fs.sin...OK
Writing APP-SW/apps_log.sin...OK
Writing APP-SW/amss.sin...OK
Writing APP-SW/fota0.sin...OK
Writing APP-SW/fota1.sin...OK
Writing APP-SW/recovery.sin...
Error! SIN Body Block Not Accepted! Done 0x575000 of 0x575880
Writing APP-SW/dsp1.sin...
Error! APP-SW/dsp1.sin Header Is Not Accepted!
Writing APP-SW/boot.sin...
Error! APP-SW/boot.sin Header Is Not Accepted!
Writing APP-SW/cache.sin...
Error! FSP/cache.sin Header Is Not Accepted!
Writing APP-SW/preset.ta...FAILED
Error! SIN Body Block Not Accepted! Done 0x575000 of 0x575880
Writing APP-SW/dsp1.sin...
Error! APP-SW/dsp1.sin Header Is Not Accepted!
Writing APP-SW/boot.sin...
Error! APP-SW/boot.sin Header Is Not Accepted!
Writing APP-SW/cache.sin...
Error! FSP/cache.sin Header Is Not Accepted!
Writing APP-SW/preset.ta...FAILED
Failed To Write: 0x08FD Size 0x0010
Writing FSP/system_S1-SW-LIVE-AC12-0001-S1-PARTITION-WITH-SPARE.sin...
Error! FSP/system_S1-SW-LIVE-AC12-0001-S1-PARTITION-WITH-SPARE.sin Header Is Not Accepted!
Writing FSP/userdata_S1-SW-LIVE-AC12-0001-S1-PARTITION-WITH-SPARE.sin...
Error! FSP/userdata_S1-SW-LIVE-AC12-0001-S1-PARTITION-WITH-SPARE.sin Header Is Not Accepted!
Writing TA Data...FAILED
Starting Advanced Section...
Closing TA...FAILED
Shutting Down...OK
Your X10 Has Been Successfully Updated!
Execution Time - 00:10:07
Done!
Loading User Info...
User: / Credits: 0 / Counters: 10
You are, of course putting the device into flash mode each try right?
what do you mean by bricked? bricked usually means unable to do anything including flash roms....
x edude03, of course always put return key and x10 is in flash mode.
x dan-htc-touch, bricked is like you say, power on my x10 and in 30/40 seconds one phone with warning appear in the screen.
May be this problems is by status battery < than 50% ?
thanks a lot
alucine
alucine said:
x edude03, of course always put return key and x10 is in flash mode.
x dan-htc-touch, bricked is like you say, power on my x10 and in 30/40 seconds one phone with warning appear in the screen.
May be this problems is by status battery < than 50% ?
thanks a lot
alucine
Click to expand...
Click to collapse
I have a feeling that is has to do with an incompatible baseband (amss) currently on your phone, and the OS image...
the easy way: why don't you try the root method again?
rodrigofd said:
the easy way: why don't you try the root method again?
Click to expand...
Click to collapse
rodrigofd, if you look first post "way 3" is with root method of this forum, "way 4" is unbrick method of this forum, "way 5" is with Omnius server, and "way 6" is with Davinci server.
I think that is impossible, that 4 differents methods fail.
My last theory is battery status, it is possible to update firm with less than 50% battery ?
May be my X10 brick has less than 50% battery and ALL method fail buy this...
Anybody can updated x10 with less than 50% battery ?
Thanks agains.
alucine
P.D: Gracias amigo, desde Madrid
I updated yesterday, using Omnius, with 38% battery. Then I rooted it. No problems here.
when you tried with omnious , did you try to flash with software that was for your version of the x10, ie, did you use x10a software with an x10a or x10a software on a x10i?
my bricked phone came back to life only after flashing with the correct version of the software
instigator008 , sure that with 38% battery ? you are the first my friend
hondaguy, i sure that firmware is for X10i
by bricked you mean that you have a phone with a triangle on screen?
If so, I had the same problem.
what I did was to flash the latest firmware R2. This booted the phone for me.
Grab the flash tool, and download the Telenor R2 version from here
forum.xda-developers.com/showthread.php?t=683793
backup system.sin and userdata.sin from the flash folder, and rename the files that you got in the R2 rar to system.sin and userdata.sin (userdata.sin should be the file that is 5kb)
and then flashed it, this fixed the issue
stop what you are doing and start with the BASICS.
first of all if your phone goes to yellow triangle then it is not bricked so stop worrying
secondly re download an omnius firmware of your choice ( i suggest UK generic r1b0016 as it will prepare you for root )
i tell you to re-download because your old download may be corrupt
extract the file you downloaded so you get the 2 .zip files
try omnius again. large zip in top , small zip in bottom
if that fails then try from different a computer.
What version of Omnius are you using and where did you get the firmware that you are trying to flash through it from?
Also can you add how you "stuffed" it exactly.
Global Generic R1FA016 for Omnius:
http://www.2shared.com/file/rWZ3YeGm/X10i_GLOBAL_GGL_GENERIC_1232_9.html
http://www.megaupload.com/?d=0JMUI3I5
R1FA016_APP_SW_RACHAEL_GENERIC_1227_4612_S1_SW_LIVE_AC12_0001_S1_PARTITION in as the application file and
R7A_R1FA016_FSP_X10i_GENERICGLOBAL_GGL_GENERIC_1232_9897_S1_SW_LIVE_AC12_0001_S1_PARTITION_WITH_SPARE as the customised file.
and also have you tried emptying your blob_fs folder and getting SEUS to do a repair with its own files ? rather than with the 2 files you put in
andy8271 said:
and also have you tried emptying your blob_fs folder and getting SEUS to do a repair with its own files ? rather than with the 2 files you put in
Click to expand...
Click to collapse
Ok, bad thing what you have there. Seems like part of the erase/write procedure for the recovery image has crashed. What might mean you have a hardware problem (and seus crashed because of that) or some essential area has got corrupt.
First pick omnius and try to backup the Trim Area (TA). Just in case you might need it, and to check it still exists.
Pick Any of the rooting packages, and from step1 move all SIN files EXCEPT loader.sin to another folder.
Then, one by one, go flashing those files, in no particular order, but one by one:
amss first
dsp second
amss_fs
apps_log
boot
fota0
fota1
system
userdata
recovery
If any of them give any kind of error, the rest won't flash. If it always get stucked on recovery, you probably have a bad block on the flash chip, and you should go to a service center, tell them you were updating with SEUS and it crashed. See if you can get a swap.
alucine said:
My last theory is battery status, it is possible to update firm with less than 50% battery ?
May be my X10 brick has less than 50% battery and ALL method fail buy this...
Click to expand...
Click to collapse
Yes it might completely fail with less than 50% battery, I myself had one rooting routine where my battery dropped from 60% to less than 10% in a full ROM flashing. So the guy who did it with only 38% just had a lucky run period.
I can't remember where it was posted but I did see a post from somebody who failed flashing with 48% of battery power.
So before starting any recovery attemp I'd suggest you let your X10 load up to a full 100% (when the led turns off) before trying anything else. I also noticed that when loading the battery directly from a power outlet it loads faster than from powering from USB.
alucine said:
instigator008 , sure that with 38% battery ? you are the first my friend
hondaguy, i sure that firmware is for X10i
Click to expand...
Click to collapse
My impression is the 50% battery is a recommendation for safety, not a must have to proceed.
Hi guys, this morning my battery in another X10 say 30% left only...
My X10 with the battery of a friend, not work update firmware, pccompanion, SEUS and flashtool.
This afternoon i will go to oficial SE support of my city, i hope that will be revive
while rooting yesterday, i left my phone in flash mode for around 20 mins
and from 80% battery it dropped to 10%
if you try rooting or restoring firmware with only 30% battery you are asking for trouble!
I guess I was lucky then lol.. had around 35-40%
Sent from my X10i using XDA App
alucine said:
Hi
Yesterday with SEUS my X10 is bicked, today i try all this ways and all the same result BRICKED.
[/CODE]
Click to expand...
Click to collapse
You mean that its bricked while you used SEUS update?
If this is true and you cannot run X10flash or others again you have a nand failure (hw related).
Then please connect SE and let it fixed by them. I know exactly one person with the same problem, they replaced his device directly .
Regards
Bin4ry
i bricked my sgy last week
actually i installed a new kernal to overclock sgy
-i installed jellyblast rom
-installed creedsix rom
-installesd new kernal
-wipe data, cache, dalvik cache
problem
-stuck in samsung galaxy y logo
-flashed too many times, still stuck in samsung galaxy y logo
i flashed at least 30 times, with different firmwares.
but still no luck, still stuck there.
i had definitely no idea what to do.
help me. thanks.
Try Flashing the Stock Firmware with ODIN. Search for the Stock Firmware Thread in XDA. If you tried that and it didn't work, you may have to take it to the Service Centre....Here's a tutorial you could find help from--http://forum.xda-developers.com/showthread.php?t=1640668
mayank_saxena said:
i bricked my sgy last week
actually i installed a new kernal to overclock sgy
-i installed jellyblast rom
-installed creedsix rom
-installesd new kernal
-wipe data, cache, dalvik cache
problem
-stuck in samsung galaxy y logo
-flashed too many times, still stuck in samsung galaxy y logo
i flashed at least 30 times, with different firmwares.
but still no luck, still stuck there.
i had definitely no idea what to do.
help me. thanks.
Click to expand...
Click to collapse
Turn it on and leave it off for a day,then try again :good:
Status 7 stands for incorrect zip file.
Btw, i don't get it. Your title asks a question and your post says something else.
||I'm just a PM away for help||
anasdcool71 said:
Status 7 stands for incorrect zip file.
Btw, i don't get it. Your title asks a question and your post says something else.
||I'm just a PM away for help||
Click to expand...
Click to collapse
I am not able to start my phone.
Every time i switch on it .The phone gets stuck on the samasung galay y logo.
When I went in the Android System Recovery Mode (not in CWM) there were lines written in the end stating:
E:failed to mount/cache (Invalid argument)
E: Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
And when I went into the CWM tried to flash savie kernel #73 went to device information it stated as follows:
Your Device System and Partition Information
Brand : (didnt state any thing)
Model : (didnt state any thing)
Baseband : (didnt state any thing)
Build Number : (didnt state any thing)
Board Name : (didnt state any thing)
CPU : (didnt state any thing)
LCD Density : (didnt state any thing)
System Size : -1 MB
Free : -1 MB
Data SIze : -1 MB
Free: -1MB
SD Card Size : 969MB
Free : 809MB
SD-EXT Size :-1MB
Free : -1MB
and when I started the installation of this kernel it stoped and stated
" assert failed:
getprop("ro.product.device") ==
"GT-S5360" "
and also stated
Installer Status:7
.
I tried to flash the stock rom and checked the device information and now it stated as follows:
Your Device System and Partition Information
Brand : samsung
Model : GT-S5360
Baseband : S5360DDLE1
Build Number : GINGERBREAD.DDLE1
Board Name : totoro
CPU : armeabi
LCD Density : 120
System Size : -1 MB
Free : -1 MB
Data SIze : -1 MB
Free: -1MB
SD Card Size : 969MB
Free : 809MB
SD-EXT Size :-1MB
Free : -1MB
but when i started the installation of this kernel. Still the error was same.
Now please tell me what to do .
Please tell me via CWM
Help me asap.
Thanks
mayank_saxena said:
I am not able to start my phone.
Every time i switch on it .The phone gets stuck on the samasung galay y logo.
When I went in the Android System Recovery Mode (not in CWM) there were lines written in the end stating:
E:failed to mount/cache (Invalid argument)
E: Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
And when I went into the CWM tried to flash savie kernel #73 went to device information it stated as follows:
Your Device System and Partition Information
Brand : (didnt state any thing)
Model : (didnt state any thing)
Baseband : (didnt state any thing)
Build Number : (didnt state any thing)
Board Name : (didnt state any thing)
CPU : (didnt state any thing)
LCD Density : (didnt state any thing)
System Size : -1 MB
Free : -1 MB
Data SIze : -1 MB
Free: -1MB
SD Card Size : 969MB
Free : 809MB
SD-EXT Size :-1MB
Free : -1MB
and when I started the installation of this kernel it stoped and stated
" assert failed:
getprop("ro.product.device") ==
"GT-S5360" "
and also stated
Installer Status:7
.
I tried to flash the stock rom and checked the device information and now it stated as follows:
Your Device System and Partition Information
Brand : samsung
Model : GT-S5360
Baseband : S5360DDLE1
Build Number : GINGERBREAD.DDLE1
Board Name : totoro
CPU : armeabi
LCD Density : 120
System Size : -1 MB
Free : -1 MB
Data SIze : -1 MB
Free: -1MB
SD Card Size : 969MB
Free : 809MB
SD-EXT Size :-1MB
Free : -1MB
but when i started the installation of this kernel. Still the error was same.
Now please tell me what to do .
Please tell me via CWM
Help me asap.
Thanks
Click to expand...
Click to collapse
u need to flast stock rom via odin. go to this site it will surely help u http://s5360rom.blogspot.com/p/how-to-install-or-flash-stock-rom-on.html
please press thanks if i helped u.
mayank_saxena said:
I am not able to start my phone.
Every time i switch on it .The phone gets stuck on the samasung galay y logo.
When I went in the Android System Recovery Mode (not in CWM) there were lines written in the end stating:
E:failed to mount/cache (Invalid argument)
E: Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
And when I went into the CWM tried to flash savie kernel #73 went to device information it stated as follows:
Your Device System and Partition Information
Brand : (didnt state any thing)
Model : (didnt state any thing)
Baseband : (didnt state any thing)
Build Number : (didnt state any thing)
Board Name : (didnt state any thing)
CPU : (didnt state any thing)
LCD Density : (didnt state any thing)
System Size : -1 MB
Free : -1 MB
Data SIze : -1 MB
Free: -1MB
SD Card Size : 969MB
Free : 809MB
SD-EXT Size :-1MB
Free : -1MB
and when I started the installation of this kernel it stoped and stated
" assert failed:
getprop("ro.product.device") ==
"GT-S5360" "
and also stated
Installer Status:7
.
I tried to flash the stock rom and checked the device information and now it stated as follows:
Your Device System and Partition Information
Brand : samsung
Model : GT-S5360
Baseband : S5360DDLE1
Build Number : GINGERBREAD.DDLE1
Board Name : totoro
CPU : armeabi
LCD Density : 120
System Size : -1 MB
Free : -1 MB
Data SIze : -1 MB
Free: -1MB
SD Card Size : 969MB
Free : 809MB
SD-EXT Size :-1MB
Free : -1MB
but when i started the installation of this kernel. Still the error was same.
Now please tell me what to do .
Please tell me via CWM
Help me asap.
Thanks
Click to expand...
Click to collapse
U will still be able to go into download mode
Down+home+Power
Get a stock rom from http://forum.xda-developers.com/showthread.php?t=1465800
And flash using odin
From where u got creed six rom...???
Sent from my GT-S5360 using xda app-developers app
Ritayan Roy said:
Try Flashing the Stock Firmware with ODIN. Search for the Stock Firmware Thread in XDA. If you tried that and it didn't work, you may have to take it to the Service Centre....Here's a tutorial you could find help from--http://forum.xda-developers.com/showthread.php?t=1640668
Click to expand...
Click to collapse
please tell me via CWM
anmolsharma1293 said:
From where u got creed six rom...???
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
Didnt remember coz i switched to jellyblast after that.
U can view my problem above
I THINK U HAVE FLASHED ANOTHER PHONE ROM ON U R YOUNG THAT'S WHY IT IS HAPPENING I SUGGEST U TO FLASH STOCK ROM FROM ODIN OR TAKE IT TO SAMSUNG CENTRE
bY
-----------------------SS------------------------OO-----------------------------MM-------------------------KK------------------------LL
mayank_saxena said:
please tell me via CWM
Click to expand...
Click to collapse
Friend, I know you'd prefer CWM as you are a New User...Believe me, I too preferred CWM sometime ago..I bricked my phone atleast three times using CWM before I succesfully installed Merruk 2.5 Deluxe using ODIN(on first attempt)..you just follow the tutorial carefully.You'll get it done for sure..READ THIS AT FIRST-- http://forum.xda-developers.com/showthread.php?t=1640668
There's the ODIN section..Go through it and you'll find it much simpler...I did. Good Luck..!
mayank_saxena said:
please tell me via CWM
Click to expand...
Click to collapse
here u go .try this at your own risk.
Procedure to install Stock ROM in Samsung Galaxy Y GT-5360
1.First download the zip file (link https://hotfile.com/dl/164864526/e7ba5c1/clockworkmod.zip.html) in your computer,extract it. After extracting you will get a folder with three files i.e. Backup, Desktop.jpg, Thumbs.db. and then with the help of USB cable connect the Galaxy Y with computer to place the three files i.e. Backup, Desktop.jpg, Thumbs.db right away in the SD card inside clockworkmod folder. Do not place in any subfolder.
2.Detach the cable
3.Just check that in the backup files there is a folder DDLE1 and in that there is Nandroid.rsf.tar, System.rfs.tar, Cache.rfs.tar etc. if these are missing then again continue the process from beginning.
4.Now its time to turn off the Y to boot into Clockworkmod recovery by pressing the Volume Up key, Home and then power button together. In case you have install the creed ROM then press the power button and select the Clockwork Mod to boot the same.
5.Now wipe data and cache partition. After this select Backup & restore-> Restore-> DDLE1->Confirm-restore DDLE1 and wait for 10 minutes to flash the ROM.
6.When the installation is finished, select ‘Reboot system now’.
If this doesn’t work then you have use odin way.
PLZ PRESS THANKS
I hate to see the people getting their basics wrong and doing it all complicated.
1) First of all, DONT use Creed six ROM, its NOT an official one(not by creed series OP pratyush.creed), its outdated, way better ROMs out there now. Try USSRv8/ Jelly Blast/ Hyperion, they are way better than Creeds Six in every way.
2) Use only XDA posts/ROMs/Kernels to get the correct info, dont rely on 3rd party websites. If you cant find something in xda, you cant find anywhere!
3) Im assuming you are installing Merruk Kernel 2.5 (deluxe #206 kernel) which only supports overclock.
The error code you are getting there is due to the ext4 flashing. Merruk #206 involves the conversion of system,data and cache to ext4 and flashing the kernel in ext4, its a ALL-IN-ONE pack.
To get a perfect combo of flashing merruk dev #206 follow these steps:
1) Flash back to stock ROM (Refer to doky73 thread in development)
2) Flash any custom ROM you desire via CWM( Refer its thread for instructions)
3) Download and copy the latest merruk kernel package(#206 deluxe all-in-one pack) to SD card
4) Backup your ROM using nandroid backup option from CWM
5) Flash the merruk kernel zip via CWM
6) Now, Go to advanced restore in CWM and restore data,system, cache
7) Reboot..
Thats it, your phone is now installed with latest merruk kernel(which involves the overclocking capability).
its mean here is not any solution
its mean here is not any solution of real [Q] how to fix error status 7 in samsung galaxy y
we all know about odin packages on XDA...
i think here is cygwin software issue....... its not for all
or
is this solution?
extract the boot.img and flash it via fastboot. Then perform a Full Wipe and try to flash the ROM again....
An unlocked bootloader is recommend for flashing custom Roms and kernels.
i think its solution..
There is a prob in ur updater script
Sent from my GT-S5360 using XDA
Kashif.Ali said:
its mean here is not any solution of real [Q] how to fix error status 7 in samsung galaxy y
we all know about odin packages on XDA...
i think here is cygwin software issue....... its not for all
or
is this solution?
extract the boot.img and flash it via fastboot. Then perform a Full Wipe and try to flash the ROM again....
An unlocked bootloader is recommend for flashing custom Roms and kernels.
i think its solution..
Click to expand...
Click to collapse
hell_lock said:
There is a prob in ur updater script
Sent from my GT-S5360 using XDA
Click to expand...
Click to collapse
Error 7 means error in updater script. But his query isnt that. The topic heading and the question he asked is completely different.
hitme987 said:
Error 7 means error in updater script. But his query isnt that. The topic heading and the question he asked is completely different.
Click to expand...
Click to collapse
cygwin automatic generating updater script u mean its issue of cygwin...
because u r saying right "its updater script error"
E:Can't mount cache/recovery.....
pustinjak said:
Turn it on and leave it off for a day,then try again :good:
Click to expand...
Click to collapse
Hi, i istalled JellyBlastV3 on Samsung Galaxy Y and it worked perfectly fine..but then I try to install a New Kernel smthng Marvk v2.0, i dnt remember exactly..and i did smthng wrong..it got stuck in bootloops.But Then i Flash Stock ROM with Odin..and it worked pretty good.But Now i am again try to install JellyBlast V3 ..abd When IN CWm when i try to wipe data/reset & Wipe Cache Partition..I Get
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
thsese errors..Nw i dnt know what is the problem ..when i try to wipe in Android Recovery ..it just worked fine...
Please help
Yudi
[email protected]
yudibakshi said:
Hi, i istalled JellyBlastV3 on Samsung Galaxy Y and it worked perfectly fine..but then I try to install a New Kernel smthng Marvk v2.0, i dnt remember exactly..and i did smthng wrong..it got stuck in bootloops.But Then i Flash Stock ROM with Odin..and it worked pretty good.But Now i am again try to install JellyBlast V3 ..abd When IN CWm when i try to wipe data/reset & Wipe Cache Partition..I Get
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
thsese errors..Nw i dnt know what is the problem ..when i try to wipe in Android Recovery ..it just worked fine...
Please help
Yudi
[email protected]
Click to expand...
Click to collapse
Flash ur stock rom by odin or take it to servic centr if ur phone is in waranty...
Press thnx if u got ur phone working back
Hi.
EDIT: Update Info added at the end of the page.
I hope someone will be able to help me.
First I apologize if this question already exist, but I'm too tired, and I hope there won't be a lot of grammar errors.
My brother had some error with LG Optimus L7 saying "Modem crash has been occured".
But first more details.
As I said:
LG Optimus L7 is what he is using.
He have few apps installed: sofascore, avg, viber, WhatsApp - I will be able to write full list of apps later this day.
Yesterday he update it to newest version of android - "Android 4.2, Jelly Bean"
There wasn't any problem for the whole day;
And then in the morning something happened with the phone.
And this message was on the phone - And since the picture I had taken with another phone is little doubled I hope I will write what does the error says correctly :
-----------------------------------------------------------------------------------------------------
Modem crash has been occured
Please do following action
Capture this screen
Get ramdump file from "OPBT" (I think) - Memory Debug App Tool
Send email to (I think it says) [email protected]
-----------------------------------------------------------------------------------------------------
ERR crash log report, Version 2. - Does this mean that there was also another crash......if yes, did phone restart itself then.....and is it possible to restart itself.
Error in file NV (I think), line 0
Time of crash.... some time - 3 a.m.
Now it says something I can't read.....
Build ID: PF00-M722FA-V20a-MAR-08-2013-XX - something like this.
REX-TOB ptr: 0x2?4f6300 ?-means something
tCD: task_name: DOO
Register values from nex (I think) core:
And now there is ~15 more or less "errors" which I can't read, but they say this I think:
ARM_SWC_R0 : 0x0A0A0A0A
ARM_SWC_R0 : 0x000000000
.........
ARM_SWC_R10 or RT0 : can't read.
ARM_SWC_R10 or RT0 : can't read.
ARM_SWC_R12 or RT2 : can't read.
More likely it is R12 and R10.
........
What else I can read:
ARM_JVH_SPSR : 0x00000000
....... - means that Error repeat itself or I can't read it so I can't write it
And it is possible that SWC is actually SVC
Above is on the left column, and this is on the right one:
ARM_SVC_R1 : 0x00000000
ARM_SVC_R3 : 0x00000000
ARM_SVC_R5 : 0x00000000
ARM_SVC_R7 : 0x00000000
ARM_SVC_R9 : 0x00000000
ARM_SVC_R11 : 0x00000000
ARM_SVC_CP (I think) : 0x00000000
.........
ARM_CPSR : 0x00000000
Click to expand...
Click to collapse
Also - the battery drained a lot, from 70% (12:30 am - 8 a.m.) to 10%, even more.
Also, it is a new Phone, 1 week old, so it is still under warranty if this is some bigger problem.
Thank You for your help, hope someone knows what could be the problem, any advice appreciated.
Should we worry about this.
EDIT: Update Info:
It seems that "we" needed to "restart" the phone after we update it. (Since the phone restarted itself after the update we didn't think about that then)
And that Notice we didn't saw anywhere till yesterday on some forum.
After that day, after phone crash error has appeared - ALL works perfectly since then.
All improvements by Update you can really notice, especially about battery, battery drain is a lot slower with this new update.
So, I could say that the problem is solved. If one day repeat itself, I will be back.
Thank YOU!
Best Regards
my phone sometimes hang but its kinda weird bcs if happening when im wathing video the video is still running for about 1 min but back button, home button and all things are not working.
and im trying to downloading logcat and show error like this:
ABS y overstep the boundary !!!
Device driver report y =1900, but max is 1745
(i've found this so much! and idk what to do)
https://image.ibb.co/krQ6f7/Screenshot_2018_03_12_17_00_51_95.png
protecteyesinit, try to dlopen arm32 so:/system/lib/libprotecteyes.so
protecteyesinit, dlopen arm32 so, dlhandle null: open ***fail****,now dlerror info:: dlopen failed: "system/lib/libprotecteyes.so" is 32-bit instead of 64-bit
protecteyesinit, try to open 64so, now dlerror info : (null)
protecteyesinit, dlopen arm64 so:/system/lib64/libprotecteyes.so, open ***success****, now dlerror info : (null)
Detect_Icon_Margin Bottom failed ! PixelIndex = 9264, templineSize = 9215
any solution without reflashing os? when its happen, i should restart 3-4 times for get everything back to normal.
pls help
I am having Huawei Honor 3C H30-U10, It was running fine but some days back when I plugged in charger it restarted and hung up on welcome screen (no animated logo). Seems like I need to install Stock Rom to it.
Phone Details:
Huawei Honor 3C H30-U10
Build Number: H30-U10 V100R001C900B108
International Variant
I download Stock ROM for it with version B108 but it was in SP Flash Tool format. My phone isn't recognised by my laptop even though I have VCOM drivers installed.
This force me to think I need to download Stock ROM but which is in dload and UPDATE.APP form. It was hard for me to get any ROM H30-U10 V100R001C900B108 in UPDATE.APP form. Fortunately I got one from
forum.lowyat . net/topic/3237141/+1260
(Please look at: 7. V100R001C900B108 ROM (update.app))
Upon pressing Volume UP+Power Key It successfully went to updating from SD Card but I am receiving this error log on screen:
Code:
md5_verify success
dloading module CURVER.....
main version string=H30-U10 V100R001C900B108
dloading module VERLIST.....
Main version from property is H30-U10 V100R001C900B108
main version check: the market is same. go to continue..
current version in VERLIST, allow to update.
dloading module MBR.....
dload:update partition MBR failed
Update /sdcard/dload/update.app failed
=============================
@@@@@ @ @@@ @
@ @ @ @ @
@@@ @ @ @ @
@ @@@@@ @ @
@ @ @ @@@ @@@@@
=============================
My question is
Why I am getting this error?
What are the other possibilities that I can do to bring back this phone to life?
PS:
Pointing to this dload:update partition MBR failed Shopkeeper (Mobile technician) told me your phone internal memory is full or corrupted. You can't get it right until you change the hardware part associated with memory. Is he right?
Guys, I tried hard to search this question on internet and I didn't find anything. Please provide rich information so that other community use it for reference.