Related
I would like to ask that How can I write my orginal IMEI back to vox?
I don't want argue the legal issue. What I can tell is that what I am trying to do is only for myself and not for business.
I have been looking into this as well, you can pull disk images using bkondisk and you can locate the IMEI within, writing the file back however is harder.
h4waii said:
I have been looking into this as well, you can pull disk images using bkondisk and you can locate the IMEI within, writing the file back however is harder.
Click to expand...
Click to collapse
Can you please write more detail?
No. I'm not able to. Search threads for how to dump using bkondisk and once you have that you will be able to locate the section with the IMEI stored.
h4waii said:
No. I'm not able to. Search threads for how to dump using bkondisk and once you have that you will be able to locate the section with the IMEI stored.
Click to expand...
Click to collapse
Good, then How can I write it back to the device? I have searched this site and not got the answer.
Can Someone adb Pull The Triumph System Files And Send Them To Me? I Will IM My Email Address To You If Neccesary.
barnito at androidforums posted a stock 039 nandroid backup
http://androidforums.com/3036500-post178.html
it has system.img in there
Hello
I am here too, just can't post links yet, I backed up my Triumph without powering it on....
How do i extract the files from the system.img
souder14 said:
How do i extract the files from the system.img
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=961164
zurui said:
http://forum.xda-developers.com/showthread.php?t=961164
Click to expand...
Click to collapse
The system.img extraction keeps freezing and stopping could someone just adb pull their system folder and zip it then send it to me?
souder14 said:
The system.img extraction keeps freezing and stopping could someone just adb pull their system folder and zip it then send it to me?
Click to expand...
Click to collapse
I've got dd dumps of the entire MT "disk" and individual dd dumps of each partition. I also have tars of each file system.
I took the dd "images" prior to the first boot into the OS, by holding volume-down+power. That put me into the strange read-write boot loader mode. Then I connected the phone via USB to a linux box. Unfortunately, Ubuntu auto-mounted the phone "disk" and all the file systems which no doubt updated some file system timestamps, but I didn't change anything. I unmounted the file systems, took my dd images then mounted them again and tar'd them up. Then unmounted and rebooted the phone and activated it.
Unfortunately, I doubt I have enough karma to upload yet. Perhaps I can put them somewhere for you to download directly? PM me for the location. Sorry offer open to souder14 only, or someone else with enough karma to post them to xda.
Did you find an upload location? If so please share it.
Thanks
srmuc69
Hi there!
I was tinkering about on the system files of my Galaxy Beam, and (maybe) accidentally messed up with the partition of the device.
The device runs on Jelly Bean 4.1.2 and now its mobile data service is disabled, and when I checked the baseband it says "XXXX" (I believe this is the same case as baseband unknown).
I tried to repair it using Szaby59's method (http://forum.xda-developers.com/showthread.php?t=2145464), but to no avail.
I wonder if there is another way to restore the baseband of my phone? I understand I might have messed with the efs and modemfs files, will it help if there is anyone who is kind enough to share his/her stock efs/modemfs files, and I get to use those files to my phone?
Hope the information was clear enough, thanks in advance.
ardjet said:
Hi there!
I was tinkering about on the system files of my Galaxy Beam, and (maybe) accidentally messed up with the partition of the device.
The device runs on Jelly Bean 4.1.2 and now its mobile data service is disabled, and when I checked the baseband it says "XXXX" (I believe this is the same case as baseband unknown).
I tried to repair it using Szaby59's method (http://forum.xda-developers.com/showthread.php?t=2145464), but to no avail.
I wonder if there is another way to restore the baseband of my phone? I understand I might have messed with the efs and modemfs files, will it help if there is anyone who is kind enough to share his/her stock efs/modemfs files, and I get to use those files to my phone?
Hope the information was clear enough, thanks in advance.
Click to expand...
Click to collapse
hi ardjit the tow folders that u asked for they are zipped and attached above :good:
alameralshamry said:
hi ardjit the tow folders that u asked for they are zipped and attached above :good:
Click to expand...
Click to collapse
thanks a lot man! will try to replace the modemfs file in my phone with the ones you just gave, hopefully this'll work!
IT WORKEDD!!!
I replaced the modemfs folder in the root directory, with the ones given by alameralshamry, rebooted my phone, and voila! data plan is back!
thanks a million to alameralshamry...and hope this thread may help anyone with similar problem.
ardjet said:
IT WORKEDD!!!
I replaced the modemfs folder in the root directory, with the ones given by alameralshamry, rebooted my phone, and voila! data plan is back!
thanks a million to alameralshamry...and hope this thread may help anyone with similar problem.
Click to expand...
Click to collapse
im happy to know that its worked with you ... you are welcome
i8530
ardjet said:
IT WORKEDD!!!
I replaced the modemfs folder in the root directory, with the ones given by alameralshamry, rebooted my phone, and voila! data plan is back!
thanks a million to alameralshamry...and hope this thread may help anyone with similar problem.
Click to expand...
Click to collapse
how replaced modemfs folder
i m unable to download your files..
please help me... thanks in advance.
alameralshamry said:
hi ardjit the tow folders that u asked for they are zipped and attached above :good:
Click to expand...
Click to collapse
agan can ask EFS has a backup folder that agan ga bin or img shape.
alameralshamry said:
hi ardjit the tow folders that u asked for they are zipped and attached above :good:
Click to expand...
Click to collapse
I just registered and replied this post with many thanks! Because I also had headache with my i8530 phone which lost the baseband info.
Your file of "modemefs.zip" REALLY worked on my I8530 phone! I unzipped the files and copied into the root directory of "modemefs", then reboot, finally the baseband came back!!!:good:
I almost decided to throw away this cell phone before I found this post. You have greatly helped me to solve my problem.
Many thanks again!
alameralshamry said:
hi ardjit the tow folders that u asked for they are zipped and attached above :good:
Click to expand...
Click to collapse
how to replace the modem file in root directory plz tell
imran qasim said:
how to replace the modem file in root directory plz tell
Click to expand...
Click to collapse
First make sure your phone is rooted and Root Explorer is installed.
Open Root Explorer, copy the files to /modemfs directory.
If failed to copy, one reason may be that /modelfs directory has insufficient space. Because Android system allocates different space for some specific system directories.
When you turn to /modemfs, Root Explorer will show "XX MB used, XX MB free" on the top.
If the free space is very little, you will NOT be able to replace the model file, so you need to consider to delete some useless or irrelevant files inside this directory.
After flashing stock ROM on my Moto G I was not able to use Wi-Fi, it does not turn on. So I tried some other ROMS from various countries and nothing. However when I flashed the Nexus G - beta 4 custom ROM (http://forum.xda-developers.com/showthread.php?t=2606943) I got it working again.
Can someone please explain what is happening, and help me?
same here
TiagoPeixoto said:
After flashing stock ROM on my Moto G I was not able to use Wi-Fi, it does not turn on. So I tried some other ROMS from various countries and nothing. However when I flashed the Nexus G - beta 4 custom ROM (http://forum.xda-developers.com/showthread.php?t=2606943) I got it working again.
Can someone please explain what is happening, and help me?
Click to expand...
Click to collapse
same here its burnsyboo im just downloading Nexus G the problem i have is i formated /persist /pds /firmware and the rest because i thought this was now mandatory in 4.4 i formated them in the new 4.4 cwm and now when i flash a custom rom or stock i flick that switch for WIFI and nothing it wont turn on im not sure why help would really be appreciated it may be that me and TiagoPeixoto formated the files wifi runs on i hope the nexus g rom will fix my wifi issues if not could someone please go to the root of there phone in root explorer or file manager and pull persist for us and pds them are the main files that WIFI runs on i think if someone could do that for us and upload it then i will be very greatfull thanks
Solved
So, I got it working again. The problem was indeed in the persist folder, it was missing a file named WCNSS_qcom_wlan_factory_nv.bin. So I managed to extract it from the persist.img and moved it to persist folder again. After that I edited the bin file and inserted my MAC address. Finally I have flashed my phone to stock ROM again and it worked just fine.
Here's the file:
fixed
Thank you so much this fixed my problem as well
Ok. Let's try but first let me e sure how to do it.
1. Edit persist.img with the .bin file inside.
2. Installl stock rom on my phone.
3. Flash persist.img in fastboot mode.
It's that correct?
gerardomt said:
Ok. Let's try but first let me e sure how to do it.
1. Edit persist.img with the .bin file inside.
2. Installl stock rom on my phone.
3. Flash persist.img in fastboot mode.
It's that correct?
Click to expand...
Click to collapse
First of all check if your persist folder is missing the bin file I have mentioned. If it is, You have to extract that file from persist.img or You can just download the one I uploaded.Then you must edit it and insert your mac address and after that you just have move it to the persist folder using a root explorer.
I could not flash persist.img, bootloader was always returning an access denied message, so i figured a way to explore the persist.img file using LinuxReader and extracted the WCNSS_qcom_wlan_factory_nv.bin from it.
So basically i ''flashed'' persist manually. Copy, edit, paste.
Thanks
Fixed
I have 2 days searching the solution and try with so many files.
Thanks
Please, could someone explain me exactly (for n00b like me) how to solve this problem?
Solved
Im lost on how to do this... do i just extract the file to the persist folder??
I formated /persit folder also, tried install stock rom, but no success with wifi
The problem is: i have no persist folder inside root and when i try to create it, the folder was gone after reboot.
Bootloader dont let me flash persist.img
What can I do?
Could someone help me, please?
When I try to "fast boot flash persist persist.img", I get a permission denied. Am I missing something?
braindump03 said:
When I try to "fast boot flash persist persist.img", I get a permission denied. Am I missing something?
Click to expand...
Click to collapse
me too
it's weird cause stock rom dont recovery /persist /firmware and /modem partition, and I wiped they content -.-'
now I'm depending on you some gracious soul can post these folders for me
Wi fi problem
Hi guys,
i've a Moto G 16 Gb purchased on Amazon.De, so german phone. I live in italy and when i connect to wi fi no problem. When i go in switzerland and i try to connect to another wi fi net (my girlfriend's line) provided by Swisscom, it doesn't work: well, i insert passoword, but it cant connect ... i called Swisscom, they tried to reset router and so on , but still persist this problem. The person (swiss) that sells me the phone (i bought it as used) said that he has the swiss provider Cablecom and it didn't have any problem. I'm fully stock with 4.4.2 . Anyone has any idea? thank you
ps: with my galaxy s3 i have no problem both in italy and in switzerland
Can anyone help in explaining the above?
....to a relative newbie? I've downgraded from 4.4.2 down to 4.3 and now my wi-fi is not working anymore, the MAC address is lost.
I'd really, really appreciate any help with regards to the procedure in going about fixing the 'Persist Folder' .
Thank you for reading.
Please make any method to solve Persist folder
Downgrade from 4.4.2 to 4.3 XT1034 UMTS...
TiagoPeixoto said:
First of all check if your persist folder is missing the bin file I have mentioned. If it is, You have to extract that file from persist.img or You can just download the one I uploaded.Then you must edit it and insert your mac address and after that you just have move it to the persist folder using a root explorer.
I could not flash persist.img, bootloader was always returning an access denied message, so i figured a way to explore the persist.img file using LinuxReader and extracted the WCNSS_qcom_wlan_factory_nv.bin from it.
So basically i ''flashed'' persist manually. Copy, edit, paste.
Click to expand...
Click to collapse
I'm sorry, but can you please elaborate? I'm have this wifi issue and it's really annoying.
You say to extract the file from persist.img, but where exactly do I find that? The file you uploaded is not persist.img.
How would I edit and insert my mac address?
Where is this persist folder? I can't find it anywhere.
If you could respond that'd be great.
breadstyx said:
I'm sorry, but can you please elaborate? I'm have this wifi issue and it's really annoying.
You say to extract the file from persist.img, but where exactly do I find that? The file you uploaded is not persist.img.
How would I edit and insert my mac address?
Where is this persist folder? I can't find it anywhere.
If you could respond that'd be great.
Click to expand...
Click to collapse
The file which he uploaded in post 3 was extracted out of the persist image.
The problem was indeed in the persist folder, it was missing a file named WCNSS_qcom_wlan_factory_nv.bin. So I managed to extract it from the persist.img and moved it to persist folder again.
Click to expand...
Click to collapse
You'll find persist folder at /persist.
You need filemanger with root permission, the you can see this folder.
So copy WCNSS_qcom_wlan_factory_nv.bin to your SD card. Use your filemanger to copy this file to /persist.
Activate wi-fi, the you'll find your mac adress under Settings > About Phone > Status > Wi-fi MAC Adress
Open WCNSS_qcom_wlan_factory_nv.bin on your phone with a text editor and type your mac adress inside that file and save it.
I have not tried it because i did not have this issue. But this is the way how i understood it.
simply copied the file in /persist, set permissions and rebooted
No MAC adress to enter
Works fine now
Thanks, very much!
You resolved me
Only its the put the WCNSS in the /persist folder and OK.
(You need to have the firmware with /persist).
With all the random qhsusb_bulk hardbricks coming around, I've decided to create a thread to share debrick.img files just in case. You do not need to create this, but if you ever need it, you'll be glad you did.
EXPLANATION:
If you ever HARDBRICK your phone, which can be caused by flashing an incompatible ROM, bad bootloader flash, or anything, your processor will fallback into a mode called USB_BULK mode. In this mode, it will await an SD card with a special image flashed to it, called debrick.img, and boot to that. Once booted from the SDcard, it will await a firmware flash from a computer (download mode.)
However, this image needs to be specific to the bootloader version the phone was running before the hardbrick occured. That's why I've created this thread: people on different bootloaders can share their debrick images.
HOW TO MAKE ONE:
Flash this in TWRP/FlashFire/SafeStrap
Your debrick.img (may be named something else, look for the .img at the end) will be in your external SD card and share it here please for others who may need it
BACK THIS UP EVERYWHERE. Google drive, dropbox, mediafire, everywhere. DO NOT loose this.
HOW TO USE ONE:
If you ever have the unfortunate luck of needing to use a debrick image, here's what to do:
-Download Win32DiskImager
-Put your microsd into your PC (yes you will need an adapter in some cases)
-Use Win32DiskImager to write the debrick.img to the SD card
-Take battery out of phone
-Put the SDcard into the phone and put the battery back in
-Do Vol Dn+Power+Home
-Your device should boot into Download Mode, and you should see "SDCARD MODE" at the top right
-Flash stock firmware using Odin
Downloads will be added to the 2nd post
Downloads
PB1 BOOTLOADER DEBRICK
PD1 BOOTLOADER DEBRICK (thanks @klabit87)
PLEASE SHARE YOUR OWN DEBRICK IMAGES! I WILL ADD THEM HERE
Great thread to start!! Question, if i'm running PB1 firmware/kernel but I haven't taken any OTA's passed OC4. Would my debrick img be of the OC4 bootloader? Or do I need to flash the OC4 firmware/kernel to where everything is of OC4? This question may help people who are unsure of what's what.
al50 said:
Great thread to start!! Question, if i'm running PB1 firmware/kernel but I haven't taken any OTA's passed OC4. Would my debrick img be of the OC4 bootloader? Or do I need to flash the OC4 firmware/kernel to where everything is of OC4? This question may help people who are unsure of what's what.
Click to expand...
Click to collapse
It is completely based on bootloader version. You can use "Phone Info - Samsung" to confirm before creating an image.
This is great would be nice if you could create Bod5 img for us who are still able to downgrade
Sent from my SM-G900V using Tapatalk
When I get a chance I'll make one for the OC4. Just want to be sure to do it correctly. Since I'm on UL OC4 Bootloader, PB1 firmware
Nandr0idC0nsumer said:
Your debrick.img (may be named something else, look for the .img at the end) will be in your external SD card
Click to expand...
Click to collapse
Just for clarification, your script doesn't create a file ending in .img:
Code:
#Unbrick-Creator.zip\tools\Unbrick.sh: Line 5
mv /external_sd/Unbrick_Files/200MB.img.gz /external_sd/Unbrick_Files/Unbrick_IMG.gz;
ben_pr said:
Just for clarification, your script doesn't create a file ending in .img:
Code:
#Unbrick-Creator.zip\tools\Unbrick.sh: Line 5
mv /external_sd/Unbrick_Files/200MB.img.gz /external_sd/Unbrick_Files/Unbrick_IMG.gz;
Click to expand...
Click to collapse
yes but if you use an archiving program like winrar to open it there is a file called 200mb.img inside and that is the debrick image
I really appreciate ur efforts, but I have a question does it work on all devices ? I will be amuse to know.
Also how space does it requires? 2gb microsd ?
Sent from my SM-G900V using XDA-Developers mobile app
[email protected] said:
I really appreciate ur efforts, but I have a question does it work on all devices ? I will be amuse to know.
Also how space does it requires? 2gb microsd ?
Sent from my SM-G900V using XDA-Developers mobile app
Click to expand...
Click to collapse
200mb is all thats needed on sd.
Only for samsung devices.
Nandr0idC0nsumer said:
yes but if you use an archiving program like winrar to open it there is a file called 200mb.img inside and that is the debrick image
Click to expand...
Click to collapse
The file inside the archive just takes the name of the archive and excludes the ".gz". Since your script renames the file from "200mb.img.gz" to "Unbrick_IMG.gz", the file within the archive is simply named "Unbrick_IMG" and does not have an extension.
I can change the name of the archive to "Unbrick_IMG.img.gz", then extracting it results in a ".img" as expected. However, with the script you posted, users will have to do this last step manually. You could either not change the name in the script, or have the script include the ".img" to save users this last step.
ben_pr said:
The file inside the archive just takes the name of the archive and excludes the ".gz". Since your script renames the file from "200mb.img.gz" to "Unbrick_IMG.gz", the file within the archive is simply named "Unbrick_IMG" and does not have an extension.
I can change the name of the archive to "Unbrick_IMG.img.gz", then extracting it results in a ".img" as expected. However, with the script you posted, users will have to do this last step manually. You could either not change the name in the script, or have the script include the ".img" to save users this last step.
Click to expand...
Click to collapse
the non-extended extracted "UNBRICK_IMG" is the image file and simply adding .img to it will allow it to be flashed
Nandr0idC0nsumer said:
the non-extended extracted "UNBRICK_IMG" is the image file and simply adding .img to it will allow it to be flashed
Click to expand...
Click to collapse
Yes, sorry, but the reason I'm pointing this out is so that you might update the original post to accurately reflect the process.
Nandr0idC0nsumer said:
HOW TO MAKE ONE:
Flash this in TWRP/FlashFire/SafeStrap
Your debrick.img (may be named something else, look for the .img at the end) will be in your external SD card and share it here please for others who may need it
BACK THIS UP EVERYWHERE. Google drive, dropbox, mediafire, everywhere. DO NOT loose this.
Click to expand...
Click to collapse
People shouldn't be looking for a file ending in ".img", and they will also need to extract then rename "Unbrick_IMG.gz". Ideally, whoever created the Unbrick-Creator.zip should just fix the script inside and update the link. I'm not sure why the zipped file gets renamed at all, nor why the original image is called "200mb.img" instead of the expected "debrick.img".
The script could just look like this:
Code:
#!/sbin/sh
mkdir -p /external_sd/Unbrick_Files/;
# Changing name of image from 200MB.img to debrick.img
# dd if=/dev/block/mmcblk0 of=/external_sd/Unbrick_Files/200MB.img bs=4096 count=50000; # Original
dd if=/dev/block/mmcblk0 of=/external_sd/Unbrick_Files/debrick.img bs=4096 count=50000; # Modified
busybox gzip /external_sd/Unbrick_Files/*;
# Removing the rename command
# mv /external_sd/Unbrick_Files/200MB.img.gz /external_sd/Unbrick_Files/Unbrick_IMG.gz;
chmod -R 777 /external_sd/Unbrick_Files
Then, to get the image file, the user simply needs to connect their phone, navigate to the "Unbrick_Files" folder, copy "debrick.img.gz" to their computer, and unzip the archive.
ben_pr said:
Yes, sorry, but the reason I'm pointing this out is so that you might update the original post to accurately reflect the process.
People shouldn't be looking for a file ending in ".img", and they will also need to extract then rename "Unbrick_IMG.gz". Ideally, whoever created the Unbrick-Creator.zip should just fix the script inside and update the link. I'm not sure why the zipped file gets renamed at all, nor why the original image is called "200mb.img" instead of the expected "debrick.img".
The script could just look like this:
Code:
#!/sbin/sh
mkdir -p /external_sd/Unbrick_Files/;
# Changing name of image from 200MB.img to debrick.img
# dd if=/dev/block/mmcblk0 of=/external_sd/Unbrick_Files/200MB.img bs=4096 count=50000; # Original
dd if=/dev/block/mmcblk0 of=/external_sd/Unbrick_Files/debrick.img bs=4096 count=50000; # Modified
busybox gzip /external_sd/Unbrick_Files/*;
# Removing the rename command
# mv /external_sd/Unbrick_Files/200MB.img.gz /external_sd/Unbrick_Files/Unbrick_IMG.gz;
chmod -R 777 /external_sd/Unbrick_Files
Then, to get the image file, the user simply needs to connect their phone, navigate to the "Unbrick_Files" folder, copy "debrick.img.gz" to their computer, and unzip the archive.
Click to expand...
Click to collapse
Good point. I will update the OP later. This is not my package btw
Nandr0idC0nsumer said:
Good point. I will update the OP later. This is not my package btw
Click to expand...
Click to collapse
My mistake; I thought you made the zip!
Nandr0idC0nsumer said:
200mb is all thats needed on sd.
Only for samsung devices.
Click to expand...
Click to collapse
Thanks
Sent from my SM-G900V using XDA-Developers mobile app
ben_pr said:
My mistake; I thought you made the zip!
Click to expand...
Click to collapse
Lol nope. Usually I like to have it all in the updater-script so I wouldn't have had a seperate script
Could someone who has updated to the PD1 bootloader post an unbrick.img for that please?
I attempted to update; flashed the PD1 stock ROM and bootloader in muniz_ri's updated thread and ended up in a soft brick, so I decided to try a full stock PB1 reset, but something went horribly wrong and I'm currently in a hard brick state.
Since something must've gone wrong halfway through, I suspect I'm still holding onto the PD1 bootloader. I've tried the process with the PB1 unbrick.img provided earlier in this thread, but sadly it didn't do anything. Thanks for all the hard work!
akaplo said:
Could someone who has updated to the PD1 bootloader post an unbrick.img for that please?
I attempted to update; flashed the PD1 stock ROM and bootloader in muniz_ri's updated thread and ended up in a soft brick, so I decided to try a full stock PB1 reset, but something went horribly wrong and I'm currently in a hard brick state.
Since something must've gone wrong halfway through, I suspect I'm still holding onto the PD1 bootloader. I've tried the process with the PB1 unbrick.img provided earlier in this thread, but sadly it didn't do anything. Thanks for all the hard work!
Click to expand...
Click to collapse
"I've tried this process" is not specific enough. Please tell me EXACTLY what you did or I can't help.
Nandr0idC0nsumer said:
"I've tried this process" is not specific enough. Please tell me EXACTLY what you did or I can't help.
Click to expand...
Click to collapse
See my thread. http://forum.xda-developers.com/showpost.php?p=67159556&postcount=14