Hello guys. I have problem with my i5500.
After method to obtain network code, my phone starts blinking with samsung logo and keep reseting. I use method that i posted below, and i got code.. but when i start phone, SIM wasnt readed correctly because i didnt have Provider logo or network signal, but phone was started correctly. So i turn off phone, re-insert SIM again and then i got that problem with blinking screen and restart loop. When is on charger screen is blinking too but with no logo.
Method that i use:
Code:
C:\ADB>adb shell
$ su
su
# cd /
cd /
# mkdir /efs
mkdir /efs
# mount -o nosuid,ro,nodev -t vfat /dev/block/stl5 /efs
mount -o nosuid,ro,nodev -t vfat /dev/block/stl5 /efs
#cat /efs/mits/perso.txt
# umount /efs
umount /efs
#
exit
exit
Also i remove cable before turnin off phone.
I already got 2 gti 5500 and 1 s5570 workin with this method but this time i have no clue whats the problem.
I am beginner, so i need help to solve this. Odin and original firmware doesnt help, i already try that.
So any chance to save my phone?
Thank you in advance.
Regards.
Remove battery
Wait 5 seconds and put it back
Press volume down + center button + power
Connect USB and flash clockworkmod or an official rom with odin
Sent from my GT-I5500 using Tapatalk
This method failed, i tried that but it can not finish
He did not root the phone and that is why it happened. )
darko032 said:
This method failed, i tried that but it can not finish
He did not root the phone and that is why it happened. )
Click to expand...
Click to collapse
This conclusion is so superficial, i have an i5500 and the phone was rooted (cm7.2) and happened to me too, i have flashed downgrade tar's file from madteam and a lot of stock roms and the phones still does samsung logo bootloops. I want to try flashing I5500XXJEA stock rom but i can not find it
Related
ok, I've looked everywhere else but I haven't been able to find the answer. My friend was trying to put gingerbread on his atrix 4g (att) and the battery died halfway through. Now we borrowed a charged battery from a friend and now when ever we turn it on it says
SVF 105:1:2
failed to boot 0x1000
then waits a few seconds then flashes "starting hv flash recovery" then turns off. The hv part might be wrong. But no matter what I press the device will not go into usb bootloader for me to put a new sbf on
any help would be much appreciated. Thank you for your time
so you can't get into fastboot mode either?
How were you installing gingerbread?
turl1 said:
How were you installing gingerbread?
Click to expand...
Click to collapse
well when my friend was doing it it was rsd lite 4.6 i think
lifetaker said:
well when my friend was doing it it was rsd lite 4.6 i think
Click to expand...
Click to collapse
if you can only get into NVFlash mode, then i'm pretty sure that you're not gonna be able to fix it. i don't believe we have the nvidia flashing tools needed to get past this option.
Alcapone263 said:
if you can only get into NVFlash mode, then i'm pretty sure that you're not gonna be able to fix it. i don't believe we have the nvidia flashing tools needed to get past this option.
Click to expand...
Click to collapse
so what your telling me, is that under no circumstance, at all. there is no way to ever fix this phone. ever, in a million years. there is no way to force the phone into bootloader?
yea you need to charge the battery outside the phone then check the dev section there is a program just fir your situation!
A soft brick, in this case, is when you make a bad edit to your framework files and the phone won't fully boot and starts flashing a red LED at you.
There is one catch, you only get about 1-2min to do all of this before the phone reboots on its own. If that happens, do SuperOneClick steps again and continue where you left off. Better yet, build a script to do it all for you 
Power off your device
Enter Fastboot:
Hold Volume down + power until you see Fastboot at the top left
Use volume down to scroll down to "Early USB Enumeration" (only shows one item at a time, if you pass it, keep going down, up selects)
Press Volume up to select
Wait for ADB to enable, run "Shell Root" from SuperOneClick, wait until it says you have root.
Enter adb shell from command line, You should have root(#) access:
adb shell
Mount the system directory as read/write:
mount -o rw,remount /dev/block/mmcblk0p12 /system
Make a new directory on /data for your recovery files: (sdcard wont be mounted yet)
mkdir /data/recover
Exit adb shell:
exit
Push your known working files to the new directory:
adb push /path/to/local/file.ext /data/recovery
Enter adb shell from command line:
adb shell
Copy your newly pushed recovery files to their proper location:
cp /data/recover/services.jar /system/framework
cp /data/recover/framework.jar /system/framework
cp /data/recover/famework-res.apk /system/framework
Reboot:
reboot now
ltdanno360 said:
yea you need to charge the battery outside the phone then check the dev section there is a program just fir your situation!
A soft brick, in this case, is when you make a bad edit to your framework files and the phone won't fully boot and starts flashing a red LED at you.
There is one catch, you only get about 1-2min to do all of this before the phone reboots on its own. If that happens, do SuperOneClick steps again and continue where you left off. Better yet, build a script to do it all for you 
Power off your device
Enter Fastboot:
Hold Volume down + power until you see Fastboot at the top left
Use volume down to scroll down to "Early USB Enumeration" (only shows one item at a time, if you pass it, keep going down, up selects)
Press Volume up to select
Wait for ADB to enable, run "Shell Root" from SuperOneClick, wait until it says you have root.
Enter adb shell from command line, You should have root(#) access:
adb shell
Mount the system directory as read/write:
mount -o rw,remount /dev/block/mmcblk0p12 /system
Make a new directory on /data for your recovery files: (sdcard wont be mounted yet)
mkdir /data/recover
Exit adb shell:
exit
Push your known working files to the new directory:
adb push /path/to/local/file.ext /data/recovery
Enter adb shell from command line:
adb shell
Copy your newly pushed recovery files to their proper location:
cp /data/recover/services.jar /system/framework
cp /data/recover/framework.jar /system/framework
cp /data/recover/famework-res.apk /system/framework
Reboot:
reboot now
Click to expand...
Click to collapse
wont go into fastboot or i would have used that already
also i have a video of the phone. but i dont have enough posts to post the link. dont get mad mods
watch?v=XuV5A6mH-Qw
of course just post this at the end of a youtube url
lifetaker said:
also i have a video of the phone. but i dont have enough posts to post the link. dont get mad mods
watch?v=XuV5A6mH-Qw
of course just post this at the end of a youtube url
Click to expand...
Click to collapse
no, this is a hard brick to your Atrix. it's a nice paperweight now.
did you attempt to flash a froyo .sbf on a gingerbread Atrix?
Alcapone263 said:
no, this is a hard brick to your Atrix. it's a nice paperweight now.
did you attempt to flash a froyo .sbf on a gingerbread Atrix?
Click to expand...
Click to collapse
Alcapone263 said:
no, this is a hard brick to your Atrix. it's a nice paperweight now.
did you attempt to flash a froyo .sbf on a gingerbread Atrix?
Click to expand...
Click to collapse
it was the other way around. but now i guess ill sell it on ebay for $200. its still in perfect condition. lets see what happens. thanks guys
lifetaker said:
it was the other way around. but now i guess ill sell it on ebay for $200. its still in perfect condition. lets see what happens. thanks guys
Click to expand...
Click to collapse
Why would you sell a broken phone on Ebay and claim it's in perfect condition?
Sent from my MB860 using xda premium
Hi guys, hope anyone of you can help me with a problem here.
My phone is on DXLPB firmware by SingTel, Singapore. I was surfing through Facebook when all of a sudden, my phone hanged. I waited for 2 minutes but it did not respond, and proceeded to pull out the battery. Now my phone is in an infinite boot loop. Tried to go into recovery mode to wipe cache / factory reset but the phone reboots itself after I pressed the confirmation (power) button. Flashing a stock firmware via ODIN keeps failing as well.
Any ideas?
Flashing a stock firmware via ODIN keeps failing as well.
Click to expand...
Click to collapse
Does the flashing fail or is the phone still in a bootloop afterwards?
If flashing fails; what error?
Tried to go into recovery mode to wipe cache / factory reset
Click to expand...
Click to collapse
Remove the SDcard if any is inserted.
Connect the phone to the computer in Recovery Mode and use adb
f you don't have adb, I've attached it to the post for your conveniance; copy the contents of the zip into C:\Windows then type 'adb shell' on the Windows Dos Promt (cmd)
Now type:
Code:
e2fsck -y -c -f /dev/block/mmcblk0p12
Put the output (or at least the part you can still see afterwards) in your next post.
d4fseeker said:
Does the flashing fail or is the phone still in a bootloop afterwards?
If flashing fails; what error?
Remove the SDcard if any is inserted.
Connect the phone to the computer in Recovery Mode and use adb
f you don't have adb, I've attached it to the post for your conveniance; copy the contents of the zip into C:\Windows then type 'adb shell' on the Windows Dos Promt (cmd)
Now type:
Code:
e2fsck -y -c -f /dev/block/mmcblk0p12
Put the output (or at least the part you can still see afterwards) in your next post.
Click to expand...
Click to collapse
Hi, thanks for the reply. Flashing via ODIN used to give me a "NAND write fail", now for some reason it just stops at "SetupConnection.. Can't open the serial(COM) port"
To add on, when I go into recovery mode, I also see this:
Code:
Applied the CSC-code : SIN did not match sized '/system/csc/common/system/csc/others.xml' (No data available)
This are the results from adb:
Code:
[email protected]:/ $ e2fsck -y -c -f /dev/block/mmcblk0p12
e2fsck -y -c -f /dev/block/mmcblk0p12
e2fsck 1.41.11 (14-Mar-2010)
e2fsck: Permission denied while trying to open /dev/block/mmcblk0p12
You must have r/w access to the filesystem or be root
This are the results from adb:
Click to expand...
Click to collapse
Argh, I keep forgetting to post that line....
You need to type "su" (Enter) before executing the command.
Flashing via ODIN used to give me a "NAND write fail"
Click to expand...
Click to collapse
That doesn't look good.
Have you tried downloading the ROM anew on samfirmware.com and please report if the phone starts showing the blue bar in Download mode (should be a little below the Android logo) when flashing with Odin.
d4fseeker said:
Argh, I keep forgetting to post that line....
You need to type "su" (Enter) before executing the command.
Click to expand...
Click to collapse
I believe su means superuser? It says su not found, then executing the command gives the same result. I have not rooted my phone if this helps.
Code:
C:\Users\c1em3ntchua\Desktop\adb>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $ e2fsck -y -c -f /dev/block/mmcblk0p12
e2fsck -y -c -f /dev/block/mmcblk0p12
e2fsck 1.41.11 (14-Mar-2010)
e2fsck: Permission denied while trying to open /dev/block/mmcblk0p12
You must have r/w access to the filesystem or be root
8|[email protected]:/ $
C:\Users\c1em3ntchua\Desktop\adb>
d4fseeker said:
That doesn't look good.
Have you tried downloading the ROM anew on samfirmware.com and please report if the phone starts showing the blue bar in Download mode (should be a little below the Android logo) when flashing with Odin.
Click to expand...
Click to collapse
Yes, tried another ROM by another carrier as well, same problem. No blue progress bar.
I kinda forget there are people without root, my bad.
Try this to fix nand write:
http://forum.xda-developers.com/showthread.php?t=1737996&page=2
Also make sure the drivers are correctly installed on your computer and Kies is not running
Sent from my GT-I9300 using xda premium
what kernel are you using?
No idea, everything's stock, only thing I did was update via Kies. I guess I will bring it down to the service centre later on. Nothing works at the moment.
Just tell them the phone immediatly didn't work after upgrading through Kies and don't mention Odin or XDA. That should guarantee hassle free repair service or replacement.
Technicians see "I haven't done anything, I swear" very suspicious since that usually means the user did something he doesn't want to admit.
Maybe keep complaining about having lost all your data so they give you a reduction on your next invoice
d4fseeker said:
Just tell them the phone immediatly didn't work after upgrading through Kies and don't mention Odin or XDA. That should guarantee hassle free repair service or replacement.
Technicians see "I haven't done anything, I swear" very suspicious since that usually means the user did something he doesn't want to admit.
Maybe keep complaining about having lost all your data so they give you a reduction on your next invoice
Click to expand...
Click to collapse
I'd probably just tell them the Facebook story, short and simple. Will keep this thread updated. Thanks for the help anyway.
c1em3ntchua said:
I'd probably just tell them the Facebook story, short and simple. Will keep this thread updated. Thanks for the help anyway.
Click to expand...
Click to collapse
Turns out it was a hardware issue, had the motherboard replaced.
Copy/Paste from BOOT LOOP post:
It's my girlfriend's phone, and she's going to kill me if i dont fix this!
The phone is a Galaxy GT 5500L (phone company: Claro, country: Argentina).
I rooted and updated to Android 2.2.2 with Kies.
The phone reboots as soon as it turns on. (No samsung logo on it)
I can enter into Download Mode, and I tried to flash everything i found with Odin, but it always says:
<1> Close serial port and wait until rebooting.
<1> PASS!!!
Click to expand...
Click to collapse
And the phone reboots and enter in the loop again.
Really, if someone could point me into the right direction it would be awesome ( i lost my samsung warranty, and the company doesnt offer any tech support in Argentina).
Thanks....
Please HELP! I'm in the same situation.
I made the steps to unlock my phone:
1 c:> cd C:android/android-sdk-windows/platform-tools
2 >adb
3 > adb shell
4 > su
5 # cd /
6 # mount -o remount rw / (
7 # mkdir /efs
8 # mount -o nosuid,ro,nodev -t vfat /dev/block/stl5 /efs
9 # cat /efs/mits/perso.txt
10 # umount /efs
it seems like I format the efs partition, or the bootloader.
Anyway, I tried everything I found, with no luck... I can enter in Download mode, and Odin detects the phone, but if I install any stock firmware or cmw, the phone enter in a loop and reboot without showing me the Samsung Logo.
Please HELP!
---------- Post added at 11:22 PM ---------- Previous post was at 10:59 PM ----------
Anybody?
Click to expand...
Click to collapse
143 views and counting.... THERE MUST BE SOMEONE WITH AN ANSWER.
Enviado desde mi GT-N7000 usando Tapatalk 2
Why go play with the efs partition???
In the Galaxy5 even trying read the efs partition bricks the phone... it's kind of a security feature.
U didn't format the efs partition. You mounted it so the phone is bricked.
Unlike other phones (mostly high end one's) u can't do anything with the efs partition!!!!.(no backup,no restore,etc.,)
My suggestion is Google more or else go to samsung.. They'll fix it for you.
today i saw the nexus v1.1 rom and i followed the instruction
but i found a step need to edit build.prop
for convenient, i use build.prop.zip attached in http://forum.xda-developers.com/showthread.php?t=2582773
after replaced the prior one and rebooted, my device bricked
now it just can show the silver logo and then the screen black when i push power 20 seconds
Or boot into <Kindle Fire System Recovery>
i reset to factory defaults twice after it bricked
please help me, im not an american so i cannot send my device to Amazon
i tried adb but just show me that device not found.
what should i do now:crying:
12312412312 said:
today i saw the nexus v1.1 rom and i followed the instruction
but i found a step need to edit build.prop
for convenient, i use build.prop.zip attached in http://forum.xda-developers.com/showthread.php?t=2582773
after replaced the prior one and rebooted, my device bricked
now it just can show the silver logo and then the screen black when i push power 20 seconds
Or boot into <Kindle Fire System Recovery>
i reset to factory defaults twice after it bricked
please help me, im not an american so i cannot send my device to Amazon
i tried adb but just show me that device not found.
what should i do now:crying:
Click to expand...
Click to collapse
Follow the guide here for how to get adb to work.
Then do the following as it sounds like you didn't change the permissions of the build.prop after copying it.
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 644 /system/build.prop
then reboot and try again.
If you can't get adb mode working you won't be able to fix this.
good luck.
thanks for your helping
im trying it not
i tried your method but there still nothing different on pc
hdx still cannot get connect with pc
well
12312412312 said:
thanks for your helping
im trying it not
i tried your method but there still nothing different on pc
hdx still cannot get connect with pc
Click to expand...
Click to collapse
You have to uninstall the Microsoft drivers for your device before you can install the ADB drivers which will allow you to get ADBworking and make these commands. There's only a dozen or more threads already for this exact problem in the general and the troubleshooting section... And they all contain links for the drivers and explain how to uninstall Microsoft drivers etc...
heyo, i'm new here, i don't even know if i'm in the right place but welp..
the thing is that i need help
i have a huawei p6 ascend, the screen was failing and one day it just died and revived few days ago
but it's a bootloop, so i was going to factory reset and then boom, failed to mount /cache /data (invalid argument), so wipe data and cache show a big FAIL, and can't install a rom, still fails
i know this problem is common and probably here in the forum but i really need help, things that i tried didn't work
i tried some things, like adb to try to install TWRP (it seems that it could help) but usb debugging is disabled so adb won't detect my device, tried to install rom through "dload" pressing volume + and volume - but nothing, it takes me to the recovery menu soo... :/ and then i tried the huawei miracle box, but ehm, my main pc detected virus and then i used a "disposable" pc but it didn't open
any suggestions? thanks