Hi
I tried to flash my phone to GENERIC x10a R2 firmware using PC companion today and after everything is finished I tried to turn my phone on with SIM card inserted but the damn phone is stuck a activating phone screen! but when i use the phone without a the SIM card it works phone and desktop is displayed
I tried to flash the phone again with different rogers firmware and same issue happnes
Did I brick my phone?!?
No, you didn't brick it. Brick is when the phone doesn't boot correctly if at all. How exactly does it freeze? Does the OS still work while it fails to connect to the network? Or does the phone become unresponsive completely?
I would try testing a different phone with your SIM, and a different SIM onto your phone.
Just curious, did you root your phone prior to flashing??
Here is what happened exactly
I had Rogers firmware R2A020 and I found a Gerneric X10a R2A020 so I decided to flash it. I didnt try to root or anything just used simple PC companion method.
Flashing went successful, when I booted up my phone it took me to the initial setup screen and the phone fucntioned normally that is of course without using a SIM card!
I turned off the phone and inserted the SIM card booted it up I was welcomed by the infamous lock screen it said at the top "no SIM card is inserted" I swapped my finder to unlock the screen and a black screen came up with a message that says "Activating phone" with a circular logo that spins next to it.
The message was setting there for almost 20 min I cant go past through that screen. I tired using my brother's SIM card but it still doing the same thing.
The phone works without SIM card but when I put any SIM in it same problem happens!!
I tried to repair and even flashed back to Rogers firmware but same issue.
I read that two people had the same problem on other forums, one possible cause is could my IMEI been blocked by AT&T?
Thanks Guys
It is not a problem with your Provider. I had the same problem as you 2 days ago.
Unfortunately I could not find an easy fix for it.
I tried to do the flash the same as you did and came across that error, but I had already rooted my phone.
I have a friend who works for SE, who I took the phone to. Even he had problems updating the phone. In the end he had to connect it to EMMA and do a "Phone Activation", this was the only way he could reflash the phone. After that, it worked ok.
I can only suggest you take it a service centre and ask them to reflash it. Sorry that I dont have a solution for you.
you could try unsetting DEVICE_PROVISIONED in build.prop
zephyrix said:
you could try unsetting DEVICE_PROVISIONED in build.prop
Click to expand...
Click to collapse
how can I access that?
I had the same issue. I rooted an Xperia X10i, everything worked fine. I then tried the MarketEnabler application on it and at reboot I got that "Activating Phone" message and it hangs there.
First, if you go to flight mode, that unblocks the phone. Going back to normal mode works but not the SIM card.
Then I changed DEVICE_PROVISIONED to 0 in build.prop and everything works fine now. Thanks to zephyrix for your help.
I'm new to Android so I don't know if this is the proper way of changing this but here's what I did:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb pull /sdcard/build.prop
Then edit build.prop in a text editor to set DEVICE_PROVISIONED to 0
adb push build.prop /sdcard/build.prop
adb shell dd if=/sdcard/build.prop of=/system/build.prop
adb shell rm /sdcard/build.prop
adb shell reboot
That should do it.
jaguarondi said:
I had the same issue. I rooted an Xperia X10i, everything worked fine. I then tried the MarketEnabler application on it and at reboot I got that "Activating Phone" message and it hangs there.
First, if you go to flight mode, that unblocks the phone. Going back to normal mode works but not the SIM card.
Then I changed DEVICE_PROVISIONED to 0 in build.prop and everything works fine now. Thanks to zephyrix for your help.
I'm new to Android so I don't know if this is the proper way of changing this but here's what I did:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb pull /sdcard/build.prop
Then edit build.prop in a text editor to set DEVICE_PROVISIONED to 0
adb push build.prop /sdcard/build.prop
adb shell dd if=/sdcard/build.prop of=/system/build.prop
adb shell rm /sdcard/build.prop
adb shell reboot
That should do it.
Click to expand...
Click to collapse
I'm going to root my phone tonight, thanks for the tip I hope it works
Related
Please help!
My andriod will not load at all, I start it up and it keeps going to the flash screen with the flashing green guy saying Andriod.
And it wont go away, I can't get on my phone I tried to factory reset and it's not working please someone!
It's a rooted g1 with JF 1.42.
reflash the JF 1.42 file, which can be done in two ways (That I know of):
1. Put your MicroSD card into another device or a card reader and replace the file, then put it back in your G1 and update it.
2. Go into the bootloader (I think thats what it's called, its Home+Power), press alt+x, then type in "echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file" (without the quotations.) Then, your computer should detect your G1, then just simply replace the file and reupdate.
AroundTheWorld said:
reflash the JF 1.42 file, which can be done in two ways (That I know of):
1. Put your MicroSD card into another device or a card reader and replace the file, then put it back in your G1 and update it.
2. Go into the bootloader (I think thats what it's called, its Home+Power), press alt+x, then type in "echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file" (without the quotations.) Then, your computer should detect your G1, then just simply replace the file and reupdate.
Click to expand...
Click to collapse
I don't got anything that will work wit my MircroSD..
and uhm I did that with the bootlader and all it said was
/dev/block/mmblk/ #
and nothing happened =[
NVM it worked!
You are my saviour!
Hi all,
I have an issue with my HTC Magic (Rogers' 32A), I am pretty pessimistic about being able to fix it, but if I don't ask I will never know
So here's the problem:
My phone fell in the water.
I took it out, removed the battery, let it dry.
Now everything is working fine except the USB connection, when I plug it to a PC via USB there is no notification, but the phone charges fine.
Basically I don't see the USB device and the can't browse the sd card, I have to take it out and use a card reader.
Also I can't adb, fastboot etc...
Other weird thing happening, when the phone is off the screen is always on, I have to remove the battery for the screen to completely shut off.
When the system is running, when I press the END/Hang Up key, the screen shuts off normally
It seems like a Hardware issue, that's why I don't think there is a (easy) way to fix it.
But I am asking here just in case.
Thank you.
sounds like a hardware issue...
Thank you, that's what I tought...
I ordered a screwdriver for the phone... gonna try to clean up the inside...
Anyone knows if there's a tutorial on how to take the phone appart and putting it back together with out breaking anything ?
check out this thread for service manuals with full tear down info, page 2 specifically for the download link (phandroid), the links on page 1 are dead now
http://forum.xda-developers.com/showthread.php?t=490774
also you can google magic service manual and find tons of links..
good luck, hope you can get your magic fixed
Go into terminal and see if you can manually mount it
$su
#mount /sdcard
___________________________
If that doesnt work, you might want to search for the /dev/block
that enables it internally.. Its around here, but im too lazy to look and link.
x) hope that helps you..
I got the PDF, that's exactly what i was looking for, I shall try it when I get the tools.
I tried the mount technique but it failed:
Code:
mount: mouting /dev/block/mmcblk0p1 on /sdcard failed: Device or resource busy
Thanks guys for all your help.
no, just
$su
#mount /sdcard
thats it lol no dev
jamsk8er1994 said:
no, just
$su
#mount /sdcard
thats it lol no dev
Click to expand...
Click to collapse
yes, that's what I did.
I just pasted the result.
sorry should have been more specific.
like this :
Code:
$su
#mount /sdcard
mount: mouting /dev/block/mmcblk0p1 on /sdcard failed: Device or resource busy
#
Ok, I finally got to disassemble the phone, clean up and blow away the dust/dirt.
And it seems like it fixed the USB issue, I am able to see the usb drive, adb, fastboot, etc...
But the screen is still back lit when the phone is turned off...
Anyways
Thanks for all you help guys.
I know this question is answered somewhere I just can't find it. I watched the you tube video on how to fix the wifi problem in the cm6.1 build but when I put the info into terminal emulator and reboot, it's not fixed. I enter the info just as it is in the info with the video, anyone else having problems?
Sent from my HTC HD2 using XDA App
I also had the same issue but I found the reason why. I actually used slightly modified versions of the commands via adb. The youtube video I referenced was:
http://www.youtube.com/watch?v=cvS4EvS0PAw
The commands I run were:
Code:
# rm -f /system/lib/modules/*
# cp -f /sdcard/hotfix/* /system/lib/modules
# chmod 755 /system/lib/modules/
I noticed that in order for this to work I had to do two things:
1.Make sure the Wifi is turned off before you run the commands.
2. Delete/Forget the Wifi Network that you attempted to connect to. Trying to reconnect with the same remembered network did not work. You have to delete it again.
Hope this helps.
slimatic said:
I also had the same issue but I found the reason why. I actually used slightly modified versions of the commands via adb. The youtube video I referenced was:
http://www.youtube.com/watch?v=cvS4EvS0PAw
The commands I run were:
# rm -f /system/lib/modules/*
# cp -f /sdcard/hotfix/* /system/lib/modules
# chmod 755 /system/lib/modules/
I noticed that in order for this to work I had to do two things:
1.Make sure the Wifi is turned off before you run the commands.
2. Delete/Forget the Wifi Network that you attempted to connect to. Trying to reconnect with the same remembered network did not work. You have to delete it again.
Hope this helps.
Click to expand...
Click to collapse
ive also done this and it took several attempts and several reboots. Was ready to throw my HD2 at my pc monitor in a huff.
Ricey
ricey1986 said:
ive also done this and it took several attempts and several reboots. Was ready to throw my HD2 at my pc monitor in a huff.
Ricey
Click to expand...
Click to collapse
you mean it worked this time around right?
Are you guys talking about your wifi timing out? Or just not being recognized at all?
slimatic said:
you mean it worked this time around right?
Click to expand...
Click to collapse
Yeah it worked
Sent from my HTC HD2 using XDA App
Tried the one on youtube no joy
Tried the and it worked first time
# rm%-f%/system/lib/modules/*
# cp%-f%/sdcard/hotfix/*%/system/lib/modules
# chmod%755%/system/lib/modules/
the % symbol represents spaces
hope this helps
I will try it with the percent symbols to see if it works for me.
Not talking about wifi timing out, phone says error when you try to connect to wifi. Will not connect at all.
Sent from my HTC HD2 using XDA App
I did a hard reset a few days ago and those files disappeared from system/lib. Now I can't get the files to copy from sd card to root. Any way to fix that?
Sent from my HTC HD2 using XDA App
Hello everybody! please help me wtih next situation. I've bought Galaxy tab 7.7 in Tailand about a week ago. It is working fine, but one thing im worrying about - it is the impossibility to make my device wroking on local sim cards ( I live in Russia -operatos are Megafon and Beeline). I tried to switch my ROM to a stock Russian with changing region, and i tried to unlock my device by editing nv_data.bin but i did not succeed - i could not find 0x181469 and 0x18150e bytes in order to edit nv_data.bin manually via HexEditor. So i tried script method and i ran this in adb shell, having my device in debug mode ofc:
su
cd /sdcard
echo "this takes about 45 seconds"
if [ ! -f /sdcard/nv_data.bin.orig ]; then
echo "copying file to /sdcard"
cp /efs/nv_data.bin /sdcard/nv_data.bin.orig
fi
echo -en \\x00 > out0
dd if=nv_data.bin.orig of=out1 bs=1 count=1578089
dd if=nv_data.bin.orig of=out2 bs=1 skip=1578090 count=163
dd if=nv_data.bin.orig of=out3 bs=1 skip=1578254
cat out1 out0 out2 out0 out3 > nv_data.bin.unlocked
rm out0 out1 out2 out3
rm /efs/nv_data.bin
cp nv_data.bin.unlocked /efs/nv_data.bin
rm /efs/nv_data.bin.md5
reboot
Click to expand...
Click to collapse
my device rebooted normally - i found new nv_data.bin.UNLOCKED file on sd-card. I replaced old nv_data with a new one (ofc i removed UNLOCKED tag) and rebooted. After both reboots (reboot via adb shell and manual reboot) - still no effect - it keeps telling me that i need to put my sim into a tab.
I am really desperate solving this problem - i cant find solution though i tried surfing internet more carefully. Please help!
Fuda163 said:
Hello everybody! please help me wtih next situation. I've bought Galaxy tab 7.7 in Tailand about a week ago. It is working fine, but one thing im worrying about - it is the impossibility to make my device wroking on local sim cards ( I live in Russia -operatos are Megafon and Beeline). I tried to switch my ROM to a stock Russian with changing region, and i tried to unlock my device by editing nv_data.bin but i did not succeed - i could not find 0x181469 and 0x18150e bytes in order to edit nv_data.bin manually via HexEditor. So i tried script method and i ran this in adb shell, having my device in debug mode ofc:
my device rebooted normally - i found new nv_data.bin.UNLOCKED file on sd-card. I replaced old nv_data with a new one (ofc i removed UNLOCKED tag) and rebooted. After both reboots (reboot via adb shell and manual reboot) - still no effect - it keeps telling me that i need to put my sim into a tab.
I am really desperate solving this problem - i cant find solution though i tried surfing internet more carefully. Please help!
Click to expand...
Click to collapse
Refer back to your operator & change your sim card with a new one, had the same issue with my Vodafone sim card & a replacement with a new one solved this issue.
lsherif said:
Refer back to your operator & change your sim card with a new one, had the same issue with my Vodafone sim card & a replacement with a new one solved this issue.
Click to expand...
Click to collapse
I already did! I tried with 4 different sim cards from 3 operators and i bought a new sim card just for an experiment like 2 days ago - still no result. Maybe i should try mini sim wtih adapter... but what confuses me most is absence of above mentioned bytes in my nv_data.bin...how can i check whether my device unlocked or not?
Maybe you have a broken Sim slot. Check the. Forums and you'll find lots of ppl with broken sim slots
Sent from my HTC Vision using Tapatalk 2
regius said:
Maybe you have a broken Sim slot. Check the. Forums and you'll find lots of ppl with broken sim slots
Sent from my HTC Vision using Tapatalk 2
Click to expand...
Click to collapse
Turned out my sim slot was rly broken.
But guys from tech support with replacing my slot also chagned IMEI number. They said imei should be chagned in order to use your device in your country... now its functioning normally.
Anyone know where to get a replacement sim slot? Mine is broken and no-one locally in Sydney can source it from anywhere.
the SIM Slot seriously has issues!
the last few days, my 3g connection keeps dropping randomly and the device alerts "please enter sim card". I've only used a solid old style sim card, nothing else
i had the same problem "No Sim", and i just flashed PIT file from here and it worked perfectly
http://forum.xda-developers.com/showthread.php?t=1749854&page=6
Yeah!
dotvoid said:
the SIM Slot seriously has issues!
the last few days, my 3g connection keeps dropping randomly and the device alerts "please enter sim card". I've only used a solid old style sim card, nothing else
Click to expand...
Click to collapse
glad to see i was not the only one with this problem :laugh:
After a month of purchasing my 7.7 tab i experienced this on HC but after a few weeks of just letting it happen, because i was thinking i have a defective sim card, the problem just went away and never occured again. But here comes ICS first 3 days are problem free but after that the sim card problem again is now reoccurring :crying:
mcbooth said:
Anyone know where to get a replacement sim slot? Mine is broken and no-one locally in Sydney can source it from anywhere.
Click to expand...
Click to collapse
+1
I would also like to know this. Thanks
JoJo2211 said:
+1
I would also like to know this. Thanks
Click to expand...
Click to collapse
sorry guys but i ve a question ...is it obligatory when i replace mine sim card slot as it brroken ..change my IMEI no. or it is optional...thank u in advance
Hi everyone.
First, I'm a noob on all this flashing Roms thing, so I'm a bit overwhelmed here. So please feel free to correct me if I'm saying the biggest mistake of all times.
I was setting up a Samsung Galaxy Tab 4 10.1 (SM-T530) for one of my colleagues, and was using Samsung's Device Configuration Tool (DCT) to set up most preferences.
I've played around some settings, and removed access to the "Settings" area, but I mistakenly thought that I still could adjust the profile afterwards, via DCT!
Unfortunately, it seems I've removed access to the Network "stack", so my device is isolated from the world.
When you remove access to "Settings", Samsung's tools immediately disables access to USB, Wifi, Bluetooth, SD card and other ways of connecting.
The device works, but cannot access anything, not even the machine that inserted the Security Policy.
I've tried to wipe data / factory reset on boot, but it says: MDM does not allow factoryReset
So my questions are:
- what should I do next?
- are there ways of bypassing security, to restore access and inject a new profile?
- should I flash a new ROM? (couldn't find a Stock version of it so far).
Thanks in advance to any kind soul that may spend his precious time helping this stupid f*ckup.
Also found this other guy that had the same problem as me, but the thread doesn't reflect the solution.
http://forum.xda-developers.com/galaxy-tab-3/help/reset-t2880721#post61484468
urbgimtam said:
Also found this other guy that had the same problem as me, but the thread doesn't reflect the solution.
http://forum.xda-developers.com/galaxy-tab-3/help/reset-t2880721#post61484468
Click to expand...
Click to collapse
U,
hi, after some attempts at starting settings or anything else from a terminal command line, for example
am start -a android.intent.action.MAIN -n com.android.settings/com.android.settings
Note- the above command still fails when;
am start --user 0 -a android.intent.action.MAIN -n com.android.settings/com.android.settings
not the correct "program", com.android.settings does not exist, but i just wanted to see about the permission issue , so when;
am start --user -2 -a android.intent.action.MAIN -n com.android.settings/com.android.settings
still denied.
i am learning you cannot do so as user, at least this way. You need to be rooted.
You are likely going to need to reflash firmware completely.
Alternately, flash a custom recovery so you can get adb access as root from terminal and try a surgical strike by that route
to undo what you did, after some research of course to figure out what changes you need to undo.
if you get that "fixed" then likely you can overwrite the custom recovery with a stock recovery from an sm-t530 device
If you know anyone who can get the above command corrected and working then that might be the way?
moonbutt74 said:
U,
hi, after some attempts at starting settings or anything else from a terminal command line, for example
am start -a android.intent.action.MAIN -n com.android.settings/com.android.settings
Note- the above command still fails when;
am start --user 0 -a android.intent.action.MAIN -n com.android.settings/com.android.settings
not the correct "program", com.android.settings does not exist, but i just wanted to see about the permission issue , so when;
am start --user -2 -a android.intent.action.MAIN -n com.android.settings/com.android.settings
still denied.
i am learning you cannot do so as user, at least this way. You need to be rooted.
You are likely going to need to reflash firmware completely.
Alternately, flash a custom recovery so you can get adb access as root from terminal and try a surgical strike by that route
to undo what you did, after some research of course to figure out what changes you need to undo.
if you get that "fixed" then likely you can overwrite the custom recovery with a stock recovery from an sm-t530 device
If you know anyone who can get the above command corrected and working then that might be the way?
Click to expand...
Click to collapse
Hi moonbutt74, and thanks for helping.
Just finished trying to flash an official ROM, which downloaded and installed successfully, but the problem still maintains...
I'm learning as I go, here, so I may be saying something wrong.
Shouldn't I just need to wipe the data? After all, this may just be a permissions problem, right?
When I flashed the ROM (using ODIN 3.09), it has options to "re-partition" and "Nand Erase All". Should I try one of these?
Also, when choosing the "apply update from adb", it says: "Now send the package you want to apply to the device with 'adb sideload <filename>'.
I've done the following:
"adb devices" to start adb-server and list the device (successful)
"adb sideload [pathtofile]" (successfull) - file is uploaded.
Device then says "E: footer is wrong" and "E: signature verification failed".
So no go.
Also, I just realized I don't have access to adb, as it says "error: closed" if you do any operation except "adb sideload".
So now, to root, what must I do? Flash a rooted ROM?
I do have other identical devices - is there a way to take an image from one of them and upload to the "bad" one?
Kind regards again, thanks for helping out.
Hi,
DO NOT play with Odin, no repartition or anything similar,
At this point you need to flash a custom recovery and root the tab, and/or find out what this samsung tool did and where,
Rule Number 1- never take on a job like that for someone else
So if the tab owner gives the go ahead, flash a custom recovery and root
Then;
first while in regular operation, plug tab into pc and try this in terminal ON TAB,
you must su first, su -c does not do it
su
echo 1 > /data/property/persist.service.adb.enable
now if you get the device pickup notification on pc, get terminal on pc open and run
adb shell
if that goes through run
mount
if all partitions are mounted then you should be good to go as far as access.
From there you will need to find out where this configuration software set and wrote what it did and undo it or correct it.
Try one of these recoveries https://www.androidfilehost.com/?w=files&flid=23537
for sm-t530nu recovery build rename from
sm-t530nu-Philz-6_58_9-final-recovery.tar.md5
to
sm-t530nu-Philz-6_58_9-final-recovery.tar
When you flash the recovery UNCHECK auto restart function in Odin, when flash is complete [res-ok]
unplug tab and manually reboot to RECOVERY --- Home Vol+ Power
if you don't the rom wil rewrite stock recovery and you will have to do it again
m