Database Info

Hackerize- ace clean help

i got the phone downgraded but when i type in hackerize- ace clean it either says permission denied or no such file or directory

bigb2k01 said:
i got the phone downgraded but when i type in hackerize- ace clean it either says permission denied or no such file or directory
Click to expand...
Click to collapse
take off the .sh and it should work.

how do i take of the .sh thanks

bigb2k01 said:
how do i take of the .sh thanks
Click to expand...
Click to collapse
Are you on step 2?

yes im on step 2 the last part were it says to type in hackerize- ace clean it tells me no such file or directory

ok make sure your usb debugging is on before you run commands. If thats on try to just copy and paste the command instead of typing them. If that doesn't work then start over. Your gold card should be good.

I had to type it in about four times before it actually worked.
Sent from my Desire HD using XDA App

also i was wandering i downloaded attn1 hack kit to do this he just updated it the other day so i was wandering if something might of changed

You should use the most updated version of the hack kit in case something important has changed, also make sure your not typing hackerize- ace clean" as you did above. It should be hackerize-ace clean, no space between -ace like you had put.

alright i tried it like that and i got the same error

Are you using Version 8 of the hack kit? if so just copy "hackerize-ace clean" and paste it in case there is any miscommunicastion and let me know.

branjgsclb said:
Are you using Version 8 of the hack kit? if so just copy "hackerize-ace clean" and paste it in case there is any miscommunicastion and let me know.
Click to expand...
Click to collapse
yes i am using version 8 of the hack kit and when i enter it it still says no such file or directory

I had the same problem the first time I ran it and it stopped for some reason. Tbh I think the "clean" action just kills the adb server and restarts it but I could be wrong.

ya im just not sure what to do at this pointe since its not working

I had to redo the hack kit a little while ago and I didnt do the "clean" step just did adb kill-server and then adb start-server. I havent had any problems and everything is fine but thats just me, there still is a possibility it can mess up your phone im assuming.

No.. your not doing anything wrong the command runs in the background and doesnt return anything... if you keep running again and again it wont do anything cus you already cleaned..
just continue to the next step

bigb2k01 said:
alright i tried it like that and i got the same error
Click to expand...
Click to collapse
well i personally just skipped that part and am very happy with my rooted inspire 4g, but that was just my choice

wrxtcy379 said:
No.. your not doing anything wrong the command runs in the background and doesnt return anything... if you keep running again and again it wont do anything cus you already cleaned..
just continue to the next step
Click to expand...
Click to collapse
so you thiknk im good to continue

bigb2k01 said:
so you thiknk im good to continue
Click to expand...
Click to collapse
Pretty sure the 'clean' part just deleted unnecessary left over files so you are probably fine if the rooting worked.
Sent from my Desire HD using XDA App

Yes your good to move on

restoring a lost IMEI

in the process of flashing the phone no longer show it's IMEI in status or in *#06#.
Carrier blocks the phone, i assume because of this.
seems to me that /efs/root/afs/settings/nv_data.bin is corrupted.
there is no backup file. :-( How do I recreate the file? can I use some other file and patch it with the correct IMEI?

zagzag99 said:
in the process of flashing the phone no longer show it's IMEI in status or in *#06#.
Carrier blocks the phone, i assume because of this.
seems to me that /efs/root/afs/settings/nv_data.bin is corrupted.
there is no backup file. :-( How do I recreate the file? can I use some other file and patch it with the correct IMEI?
Click to expand...
Click to collapse
What were you doing prior to this?
Does it ask you for a unlock code?
Details please.

i used odin to flash roms to upgrade to gingerbread.
kc1, kh1, voodoo kernel... it's now at kg6.
the phone was t-mobile unlocked, supposedly.
after i had issues with no calls in or out i noticed the imei reported in software (about phone or *#06#) is 00000000000000.
phone reports registered to the cellular network.
nv_data.bin in /efs/root/afs/settings is only 265kb and in hex editor it's all FF apart from one location with 00000000 values.
on an identical phone i have imei reported correctly. can i use it to recover the other one?
Sent from my NookColor using xda premium

zagzag99 said:
i used odin to flash roms to upgrade to gingerbread.
kc1, kh1, voodoo kernel... it's now at kg6.
the phone was t-mobile unlocked, supposedly.
after i had issues with no calls in or out i noticed the imei reported in software (about phone or *#06#) is 00000000000000.
phone reports registered to the cellular network.
nv_data.bin in /efs/root/afs/settings is only 265kb and in hex editor it's all FF apart from one location with 00000000 values.
on an identical phone i have imei reported correctly. can i use it to recover the other one?
Sent from my NookColor using xda premium
Click to expand...
Click to collapse
256kb is the right size. It sounds like someone went the route of trying to hex edit the nv_data.bin to unlock and so on.
It's protected by a md5 checksum file.
Try this - back up the nv_data.bin.md5 in the /efs/root/afs/settings folder as well as the nv_data.bin ( just in case ) and DELETE only the nv_data.bin.md5 file. Reboot. Check your IMEI. Post back.

thegoo said:
256kb is the right size. It sounds like someone went the route of trying to hex edit the nv_data.bin to unlock and so on.
It's protected by a md5 checksum file.
Try this - back up the nv_data.bin.md5 in the /efs/root/afs/settings folder as well as the nv_data.bin ( just in case ) and DELETE only the nv_data.bin.md5 file. Reboot. Check your IMEI. Post back.
Click to expand...
Click to collapse
I've tried different, suggested to me in another forum, deleting both files. They got recreated at boot. Still imei zeros.
Sent from my HTC HD2

zagzag99 said:
I've tried different, suggested to me in another forum, deleting both files. They got recreated at boot. Still imei zeros.
Sent from my HTC HD2
Click to expand...
Click to collapse
Did you try just the.md5 file? And also, did you check your lock statuses? *#7465625#

I have tried that didn't help still zeros.
As for locks, it reports all off.
Sent from my HTC HD2

zagzag99 said:
I have tried that didn't help still zeros.
As for locks, it reports all off.
Sent from my HTC HD2
Click to expand...
Click to collapse
Try this.
Download hex editor.
Open hex editor.
Go look for the nv_data.bin file.
Hit options (the paper looking icon on the botton left of your phone) and click jump to address.
Type 1x1468.
After FF, the next 2 digits probably say 00. Try changing it to 01. And reboot.
If it doesnt work, go back to hex editor and change it back to 00 as thats the network lock.....
Sent from my SGH-T959V using XDA Premium App

You mean address 1468 in hex?
Tried it.
It turned back to 00 after reboot.
Imei still in problem.
Do I need to have the sim in?
I took it out for fear of troubling the network.
Sent from my HTC HD2

I guess not. And no. Having the sim in or not, it doesnt really matter. And you can use the phone perfectly with the imei being straight out 0's. You can call, text, and even use data. Tried it for myself . Unless theres someone else with the same imei. Id say thats a pretty low chance seeing that most people want their own unique imei. Sorry i couldnt help. but hope you can solve your problem!
Sent from my SGH-T959V using XDA Premium App

Unfortunately I can't use the phone with IMEI all in Zeros.
The Carrier blocks me out :-(
I can only switch carrier, but that's a hard option.

Do you think this could help?
Anyone had success?
http://forum.gsmhosting.com/vbb/f452/nvm-repair-android-phones-gift-spt-team-1296409/

Some more ideas, anyone?
Sent from my HTC HD2

I dunno i read around the forums try taking out the sim and sd card, delete the md5 file, and factory resetting. Then turn off your phone for 15 minutes. Havent tried it myself
Sent from my SGH-T959V using XDA Premium App

Light-라이트 said:
I dunno i read around the forums try taking out the sim and sd card, delete the md5 file, and factory resetting. Then turn off your phone for 15 minutes. Havent tried it myself
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
Tried that, it results with new efs files being created with the default 000 IMEI :-(
I suspect I found the offsets of the IMEI in the file of the SGS4G (it differs from other models) but I can't decrypt/encrypt it so to write there the correct IMEI value matching the sticker.
Parallel to that I could find people able to do that to other samsung models , but no one that can do that to SGS4G

did u get a solution
hi i am using SGH-t959v samsung galxy s 4g. and i unlocked it using nv_data.bin file modification. after i unlocked it says NO service.
did u find any solution for it

Recover your IMEI without a backup!

I can't really take credit for this, but I just restored my IMEI without a backup of the efs folder. Keep in mind that I actually deleted my efs folder by accident, so I didn't even have the original efs folder.
The original thread I referenced is here:
http://forum.xda-developers.com/showthread.php?p=31771228#post31771228
FYI, this method will restore your phone to stock Gingerbread.
Here is what you do:
1.)
A) Download and unzip the Gingerbread unbrick package here from (http://forum.xda-developers.com/showthread.php?p=27286083#post27286083):
w/ root - http://d-h.st/ewu
w/o root - http://d-h.st/G6g
B)
Download and unzip the efs zip here:
http://forum.xda-developers.com/attachment.php?attachmentid=1152914&d=1340558510
2.) Place phone in download mode.
3.) If needed, install latest Samsung USB drivers by installing Samsung Kies from HERE.
4.) Open the included Odin exe.
5.) If phone is detected, the window under ID:COM will turn yellow.
6.) Click on "PIT" to browse to and select infuse_gb.pit. Make sure that Re-Partition is selected.
7.) Click on "PDA" to browse to and select PDA_UCLB3.tar.md5.
8.) Click on "PHONE" to browse to and select PHONE_UCLB3.tar.md5.
9.) Click on "CSC" to browse to the efs.tar
10.) Click the Phone EFS Clear checkbox
11.) Click on "Start", and allow Odin to flash the phone. Do not unplug or power off the phone until Odin is finished.
12.) When the Odin dialogue reads "PASS!", the phone should reboot into the stock UCLB3 Setup Wizard. For me this step just proceeded to install an update and the reboot the phone.
Once the phone reboots, if your SIM card is installed you should be good to go, otherwise you will get an alert about your SIM card which means you need to power off and pop in the SIM card.
Thanks to the original thread author for this one.

It works perfect for me even without the .nv_data file. Before this i only get simbols instead the imei number. You save my phone!

recovered IMEI by just flashing the CM10 base
I dunno if it's just me or what. I lost my IMEI on Slim Bean.. so I had this thought. I hadn't had this issue with the CM10 rom, so I decided to do the standard flashing procedure. Once CM10 was installed my IMEI came back. I had full signal and all is good. I decided to go back to Slim Bean to see if it would fix the IMEI issue. I flashed it just like the OP stated and walah! I had my IMEI back and everything worked without having to go back to GB, ICS and then JB again. I don't know if this will help anyone, but just wanted to note other people about it. Why did this work for me?

will this mess up my phone more?
I am running froyo 2.2.1 ,I guess it is stock, as I pick this phone up in pawn shop, and it was already rooted. I was doing the command line argument dd and a bunch of stuff, to get some file to get my unlock code. I didn't get no bak file copy, gave up put my sim card back in and that's when I noticed my imei was gone, then I had go launcher installed, so my screen goes blank I end up having to do the three finger data wipe, then I see I got no wifi either. Then I get this phone, DL some apk files, try to reinstall busy box, no go, teller me it don't think it has su permission after I gave it through that super user program, then it say it cant install into /dev/sh/ what ever, so all I got is a really nice looking video player.
So now that I got all that out of me.
2 questions, will flashing gingerbread overtop of froyo, will not make it worse?
Why do one have to flash in the first place, why can't one just copy over the old-time files, or someone find which file goods the imei number then just to in isinglass a file manager open that file, as it should be just what is caller a flat file, meaning no special formating like a Word file.
Then just save it. I am not an expert at android wse (whatsoever) but I have played with copying over top of files, or deleting the old-time one then replacing it with a new one. Why Doesn't that work, has anyone player around just opening there files to see what they look like and figure out where they stick the imei number?
Seems to me should be an easy manner of doing, but now that I don't have an individual showing I am not even sure which file I should try to type that number in to to see what will happen as I don't want to make this phone completely useless.
Any commentary, ideas, anything?
Thanks
MikieD

mikied12 said:
I am running froyo 2.2.1 ,I guess it is stock, as I pick this phone up in pawn shop, and it was already rooted. I was doing the command line argument dd and a bunch of stuff, to get some file to get my unlock code. I didn't get no bak file copy, gave up put my sim card back in and that's when I noticed my imei was gone, then I had go launcher installed, so my screen goes blank I end up having to do the three finger data wipe, then I see I got no wifi either. Then I get this phone, DL some apk files, try to reinstall busy box, no go, teller me it don't think it has su permission after I gave it through that super user program, then it say it cant install into /dev/sh/ what ever, so all I got is a really nice looking video player.
So now that I got all that out of me.
2 questions, will flashing gingerbread overtop of froyo, will not make it worse?
Why do one have to flash in the first place, why can't one just copy over the old-time files, or someone find which file goods the imei number then just to in isinglass a file manager open that file, as it should be just what is caller a flat file, meaning no special formating like a Word file.
Then just save it. I am not an expert at android wse (whatsoever) but I have played with copying over top of files, or deleting the old-time one then replacing it with a new one. Why Doesn't that work, has anyone player around just opening there files to see what they look like and figure out where they stick the imei number?
Seems to me should be an easy manner of doing, but now that I don't have an individual showing I am not even sure which file I should try to type that number in to to see what will happen as I don't want to make this phone completely useless.
Any commentary, ideas, anything?
Thanks
MikieD
Click to expand...
Click to collapse
This is either a joke or a joke.

Many Thanks
zackdjones said:
I can't really take credit for this, but I just restored my IMEI without a backup of the efs folder. Keep in mind that I actually deleted my efs folder by accident, so I didn't even have the original efs folder.
The original thread I referenced is here:
http://forum.xda-developers.com/showthread.php?p=31771228#post31771228
FYI, this method will restore your phone to stock Gingerbread.
Here is what you do:
1.)
A) Download and unzip the Gingerbread unbrick package here from (http://forum.xda-developers.com/showthread.php?p=27286083#post27286083):
w/ root - http://d-h.st/ewu
w/o root - http://d-h.st/G6g
B)
Download and unzip the efs zip here:
http://forum.xda-developers.com/attachment.php?attachmentid=1152914&d=1340558510
2.) Place phone in download mode.
3.) If needed, install latest Samsung USB drivers by installing Samsung Kies from HERE.
4.) Open the included Odin exe.
5.) If phone is detected, the window under ID:COM will turn yellow.
6.) Click on "PIT" to browse to and select infuse_gb.pit. Make sure that Re-Partition is selected.
7.) Click on "PDA" to browse to and select PDA_UCLB3.tar.md5.
8.) Click on "PHONE" to browse to and select PHONE_UCLB3.tar.md5.
9.) Click on "CSC" to browse to the efs.tar
10.) Click the Phone EFS Clear checkbox
11.) Click on "Start", and allow Odin to flash the phone. Do not unplug or power off the phone until Odin is finished.
12.) When the Odin dialogue reads "PASS!", the phone should reboot into the stock UCLB3 Setup Wizard. For me this step just proceeded to install an update and the reboot the phone.
Once the phone reboots, if your SIM card is installed you should be good to go, otherwise you will get an alert about your SIM card which means you need to power off and pop in the SIM card.
Thanks to the original thread author for this one.
Click to expand...
Click to collapse
I just wanted to thank all of you who have contributed your brain power to the xda forums. This advise worked great and after a lot of self doubt I now consider myself a semi-noob. Thanks again.
A J

Thanks on this. I had a backup of my EFS folder, but the tool I used to create it made a .img file and once I got it into JB, the tool didnt work. UGH.

Just want to say thank you for posting this. I have a friend who had her Infuse stop getting calls, texts, etc. Turns out her IMEI was all question marks and other invalid characters. ATT wouldn't help her at all and either did a full reset.

thank you, this method really works!! finally my imei is back...no more symbols, now is time for a efs back up

Since when do phones lose their imei's? That's a new one on me.

sholsten said:
Since when do phones lose their imei's? That's a new one on me.
Click to expand...
Click to collapse
It happened for me twice on two separate phones when using MIUI. Basically the ROM managed to corrupt the system partition, specifically the efs folder.
I don't know the specifics of why, but it happens to a lot of people. That's why I always now make sure I have a backup of the efs just in case.
Sent from my SAMSUNG-SGH-I717 using xda premium

zackdjones said:
It happened for me twice on two separate phones when using MIUI. Basically the ROM managed to corrupt the system partition, specifically the efs folder.
I don't know the specifics of why, but it happens to a lot of people. That's why I always now make sure I have a backup of the efs just in case.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
This method didn't work for me :\ Any other ways to solve this issue?

can i use this Efs on galaxy R to repair unknown baseband & Blank imei????

Thank you very much. This is what I need

worked great. thank you.

zackdjones said:
I can't really take credit for this, but I just restored my IMEI without a backup of the efs folder. Keep in mind that I actually deleted my efs folder by accident, so I didn't even have the original efs folder.
The original thread I referenced is here:
http://forum.xda-developers.com/showthread.php?p=31771228#post31771228
FYI, this method will restore your phone to stock Gingerbread.
Here is what you do:
1.)
A) Download and unzip the Gingerbread unbrick package here from (http://forum.xda-developers.com/showthread.php?p=27286083#post27286083):
w/ root - http://d-h.st/ewu
w/o root - http://d-h.st/G6g
B)
Download and unzip the efs zip here:
http://forum.xda-developers.com/attachment.php?attachmentid=1152914&d=1340558510
2.) Place phone in download mode.
3.) If needed, install latest Samsung USB drivers by installing Samsung Kies from HERE.
4.) Open the included Odin exe.
5.) If phone is detected, the window under ID:COM will turn yellow.
6.) Click on "PIT" to browse to and select infuse_gb.pit. Make sure that Re-Partition is selected.
7.) Click on "PDA" to browse to and select PDA_UCLB3.tar.md5.
8.) Click on "PHONE" to browse to and select PHONE_UCLB3.tar.md5.
9.) Click on "CSC" to browse to the efs.tar
10.) Click the Phone EFS Clear checkbox
11.) Click on "Start", and allow Odin to flash the phone. Do not unplug or power off the phone until Odin is finished.
12.) When the Odin dialogue reads "PASS!", the phone should reboot into the stock UCLB3 Setup Wizard. For me this step just proceeded to install an update and the reboot the phone.
Once the phone reboots, if your SIM card is installed you should be good to go, otherwise you will get an alert about your SIM card which means you need to power off and pop in the SIM card.
Thanks to the original thread author for this one.
Click to expand...
Click to collapse
1stly thanks a lot for this thread. Really millions of thanks.
Now one silly question:- I unzipped the efs file attached and it says "efs.rfs" but your instructions above says "efs.tar" needs to be selected under CSC option. Am I missing something?

Punnyabrata said:
1stly thanks a lot for this thread. Really millions of thanks.
Now one silly question:- I unzipped the efs file attached and it says "efs.rfs" but your instructions above says "efs.tar" needs to be selected under CSC option. Am I missing something?
Click to expand...
Click to collapse
Strange things are happening to me.
About 2 weeks back this problem started and today when I reconnected the SIM and restarted the phone everything was back to normal. Phone is picking up signal/3G etc.
Surprised is the word. Leads me to believe some app must be responsible for all of this.
Thanks,
PC

It is showing invalid mds sum...what I do?

At the end of the task odin shows blue screen and show fail.
Now my phone doesnt get start..what I do?

sachinppatel16 said:
At the end of the task odin shows blue screen and show fail.
Now my phone doesnt get start..what I do?
Click to expand...
Click to collapse
Have you tried Odin as administrator ? that's might be the problem

[UNSOLVED] Unknown IMEI/Baseband

LESSON LEARNT (for everyone): Please make sure to do a complete EFS backup before you do anything or you will end up like me!!!
So yeah I flashed Deodex_LF2_Cwm.zip yesterday, trying to deodex my DDFL2.
And following that I experienced total loss of mobile signal, baseband, IMEI, IMEI SV, and phone (*#1234#).
And I haven't been seeing this kinda thing to come, I did not back up EFS. (Yeah brilliant me)
So I tried a few of these:
[GUIDE] Recover your IMEI in 9 steps
Repair IMEI using EFS Pro
Reflashing from latona.pit then XXKPE; for a few times
Flashing stock ROM for Malaysia region (Froyo and GB)
Flashing various Modem.tar (DDLE1, DXKP7, etc) via Odin3 at different ROM levels (XXKPE, DDLF2, even CM10A4)
Restoring Nandroid backup from other SL user (Thanks Rich'Dawg')
But nothing worked so far yet.
Now that I checked the /efs folder is empty and there is only a folder named lost+found.
Some websites said about fixing IMEI for small fees but in cases of blank IMEI (*#06#), chances are only 30%.
And my last resort would be getting it replaced in Samsung service centre or any repair shop, which I suspect that the motherboard would be more expensive than some simple new Android phones.
Leaving this forum for the moment as to collect more money to get a new phone . . . :crying:
Lastly, thanks for all the input. Greatly appreciated.

Do you able to call anyone. ? if yes then no need to change anything. if no then you should search for imei solution on xda. there is some tutorial for fake imei.

nicsptl said:
Do you able to call anyone. ? if yes then no need to change anything. if no then you should search for imei solution on xda. there is some tutorial for fake imei.
Click to expand...
Click to collapse
Nope. I totally lost signal and mobile network.

cheeyeen said:
Nope. I totally lost signal and mobile network.
Click to expand...
Click to collapse
do you flash b4 CM10? if yes, search your sd card and External sd card for the installation backup of efs folder

chongns said:
do you flash b4 CM10? if yes, search your sd card and External sd card for the installation backup of efs folder
Click to expand...
Click to collapse
Yes I did but nope I couldn't find. sucks.

It is in a folder name backup
Sent from my GT-I9003 using Tapatalk 2

chongns said:
It is in a folder name backup
Sent from my GT-I9003 using Tapatalk 2
Click to expand...
Click to collapse
Sad enough this folder does not exist in my phone....
Have you had any idea if Samsung would fix this in Malaysia..? Or how much would that be.
I spent like 10 hours trying to look for a solution but >"<

cheeyeen said:
Sad enough this folder does not exist in my phone....
Have you had any idea if Samsung would fix this in Malaysia..? Or how much would that be.
I spent like 10 hours trying to look for a solution but >"<
Click to expand...
Click to collapse
no idea of how much it should be.
but a idea to help you,
1st idea:
go in recovery and fix permission.
2nd idea:
you said you flash Deodex LF2 in CWM, it should not touch efs folder. so, very high change of your nv_data.bin file backup still good.
OK. use any file browser look in the efs folder, see if the below file still exiting, (they are hidden file)
check on the file date. is the date older than the date you flash the zip, if yes, this is the one original from your phone.
the file name start with a dot
.nv_data.bak - ( this is your imei backup file) copy and rename the .nv_data.bak to nv_data.bin and set permission and change owner.
.nv_data.bak.md5 - (delete this file first)

chongns said:
no idea of how much it should be.
but a idea to help you,
1st idea:
go in recovery and fix permission.
2nd idea:
you said you flash Deodex LF2 in CWM, it should not touch efs folder. so, very high change of your nv_data.bin file backup still good.
OK. use any file browser look in the efs folder, see if the below file still exiting, (they are hidden file)
check on the file date. is the date older than the date you flash the zip, if yes, this is the one original from your phone.
the file name start with a dot
.nv_data.bak - ( this is your imei backup file) copy and rename the .nv_data.bak to nv_data.bin and set permission and change owner.
.nv_data.bak.md5 - (delete this file first)
Click to expand...
Click to collapse
Fixed permission.
I found one .nv_data.bak dated year 1994 , which I think came in when I was trying to flash some efs fixes i found in XDA.
Without much hope I tried what you said, but still nothing happened. IMEI blank, baseband unknown.
Is it possible to have the mobile phone repair shop with RIFF or Jtag or some box thingy to have this done?

i think you must change the motherboard

cheeyeen said:
[Request] Is it possible if anyone could send me a Nandroid backup of a working rom, so I could restore it via CWM? (It is a way I found in the XDA forum).
...
So yeah I flashed Deodex_LF2_Cwm.zip yesterday, trying to deodex my DDFL2.
And following that I experienced total loss of mobile signal, baseband, IMEI, IMEI SV, and phone (*#1234#).
And I haven't been seeing this kinda thing to come, I did not back up EFS. (Yeah brilliant me)
So I tried a few of these:
[GUIDE] Recover your IMEI in 9 steps
EFS Pro
Reflashing from latona.pit then XXKPE; for a few times
Flashing various Modem.tar (DDLE1, DXKP7, etc) via Odin3 at different ROM levels (XXKPE, DDLF2, even CM10A4)
But nothing worked so far yet.
Now that I checked the /efs folder is empty and there is only a folder named lost+found.
And my last resort would be getting it replaced in Samsung service centre??
I don't know how much would it cost in Malaysia to change the motherboard but I'm sure it will be stupidly high...
Or.. does that mean my time in i9003 forum is up..? :crying:
Please help me because I don't want to buy a new phone yet! :crying:
Click to expand...
Click to collapse
Mate, do you like JellyBam V.1.3.0? Because that's the only Nandroid backup i have in my phone. I was thinking to upload it to my Box account for Emergency Backup if i don't have my computer. If you like, i can upload it for you, but the size of the backup would be nuts, it's 850 MB. It's up to you.

Rich'Dawg' said:
Mate, do you like JellyBam V.1.3.0? Because that's the only Nandroid backup i have in my phone. I was thinking to upload it to my Box account for Emergency Backup if i don't have my computer. If you like, i can upload it for you, but the size of the backup would be nuts, it's 850 MB. It's up to you.
Click to expand...
Click to collapse
I would try anything as long as it works! Please do!

Best of Luck
a friend of mine ran through the same same problem and i think he did some sort of repair from a shop but later we came to know that the backup can do the task not sure whether that work or not but u can give it a try,, BEST of Luck with that..... Hopit Fix the Issue

Good luck sir! As far as I know, if you would choose to replace the motherboard from repair center, it would cost you more or less 80% of the original price of the phone. So it would seem that you have to buy a new one. I hope that a nandroid backup (as stated above) would solve the problem. God bless you! Think positive

i have the same problem and tried those solution the TS tested and still no luck, i wan't to try those nandroid backup but can't find any.

Rich'Dawg' said:
Mate, do you like JellyBam V.1.3.0? Because that's the only Nandroid backup i have in my phone. I was thinking to upload it to my Box account for Emergency Backup if i don't have my computer. If you like, i can upload it for you, but the size of the backup would be nuts, it's 850 MB. It's up to you.
Click to expand...
Click to collapse
Bro,pls upload... let me try it... if imei is changed to 043xxxxxxx then we can fix with z3x box

Xperia.IN said:
Bro,pls upload... let me try it... if imei is changed to 043xxxxxxx then we can fix with z3x box
Click to expand...
Click to collapse
can you share it with me if you have nandroid backup, i will try to fix it with z3x and asansam

never thought deodexing gonna brick the phone.. ive deodex once without any problem.. without any doing backup before that.. lucky me.. huhu
try other people's nandroid and see.. i dont think it needs a specific emei or what so ever.. as long as its a backup.. goodluck..

the problem is we can't find someone to lend us their nandroid backup.

I did it!
Bro, try use Efs Pro, http://forum.xda-developers.com/showthread.php?t=1308546
Try the new version, you can choise Qualcom version, write you IMEI number, go back to initial and do NV Restore.
My SG Fit go back to life (after maybe 4 months with 0000000000000 Imei). :good:
I´m very happy
Hope it work for you! Good luck!

Can't root h810pr!!!

I flashed the h810pr onto my att g4 and it works amazingly. But, I've done the root method about 10 times, and when ever I enter the last line of code the # just shows up right away, and root doesn't install I've made sure to read everything carefully and no root. Am I doing something wrong? Any help would be appreciated thank you.

russianwaffle said:
I flashed the h810pr onto my att g4 and it works amazingly. But, I've done the root method about 10 times, and when ever I enter the last line of code the # just shows up right away, and root doesn't install I've made sure to read everything carefully and no root. Am I doing something wrong? Any help would be appreciated thank you.
Click to expand...
Click to collapse
I guess you have to install the driver again..in download mode...uninstall then install back..then try the code

Tried that and still no luck.

I've got that problem too. The way i fixed it was to reflash the H810pr brand new. Do not mess with any setting yet. Then enable USB debugging. Make sure you use MTP mode, be certain that the phone itself ask you if you want to install driver. Hit yes, then reinstall the LG driver on your pc. Put the phone in download mode and root. Make sure you run the "send command" line and "id" line as instructed.

Tried that, it still doesnt want to work properly.
Sent from my LG-H810 using XDA Free mobile app

russianwaffle said:
Tried that, it still doesnt want to work properly.
Click to expand...
Click to collapse
Make sure the img file is extracted properly from the rar file that you downloaded.
Also ensure the name of the file on the internal memory matches the name in the flash command.
Perhaps the rooted image didn't download correctly.
Could be a driver or com port issue, but you were able to flash the original image so that shouldn't be the problem.

Ya i was triple checking everything. It seems like a driver problem ill look into ot later.
Sent from my LG-H810 using XDA Free mobile app

russianwaffle said:
I flashed the h810pr onto my att g4 and it works amazingly. But, I've done the root method about 10 times, and when ever I enter the last line of code the # just shows up right away, and root doesn't install I've made sure to read everything carefully and no root. Am I doing something wrong? Any help would be appreciated thank you.
Click to expand...
Click to collapse
If you are still having this problem, make sure the file is on the internal SDcard at the top level (root directory) and not the external sdcard.

Ya I made sure of that too, I don't even own an external sd card. I've just been using on the stock unrooted h810pr, haven't had time to look into the problem. If I figure it out ill post how to fix it just in case someone else has this problem in the future. If anyone has any other suggestions let me know I'll try them this week end.

russianwaffle said:
Ya I made sure of that too, I don't even own an external sd card. I've just been using on the stock unrooted h810pr, haven't had time to look into the problem. If I figure it out ill post how to fix it just in case someone else has this problem in the future. If anyone has any other suggestions let me know I'll try them this week end.
Click to expand...
Click to collapse
Have tried both com?
com 4 or com 3

Be sure to let supersu update before you reboot the phone.

faizalotai said:
Have tried both com?
com 4 or com 3
Click to expand...
Click to collapse
For my phone is always showed up as com6, I've changed the devices com number then tried the new one and nothing.

phineous said:
Be sure to let supersu update before you reboot the phone.
Click to expand...
Click to collapse
That's the thing I never get to that point the phone just won't root. I have no super user nothing. And when I do the process and I send the code to device on the screen with the # nothing happens it's just shows # again with in a second.

russianwaffle said:
That's the thing I never get to that point the phone just won't root. I have no super user nothing. And when I do the process and I send the code to device on the screen with the # nothing happens it's just shows # again with in a second.
Click to expand...
Click to collapse
Did you make sure to rename the file to system.img?

Make sure the image file is on internal storage and you are using the correct image filename in the dd command.