Hi, this is my first post on XDA after about 3 months of surfing the site reading tutorials and such :good::good:, and found much useful stuff as this guide here :good::good:
..... I used the method to backup certain partitions (data, system, boot) via adb to *.raw images which i tested on PC and found working
Now what i really want is a similar method to restore these *.raw images to the device directly from PC (the same but to restore without the need of an sdcard as i dont have one) , but i couldn't figure out how to do it. ..... Any help please???
Any help or suggestions please .... after backing up i installed Revolt ROM to try it thinking that i could restore at a later time but now I can't and i dont have any of my apps !!
A while back i decided to downgrade my stock 4.3 to 4.1.1 in order to try to unlock it from carrier... the thing is i lost my IMEI and Serial Number
The good news is i have a backup of my EFS folder (only copy-paste with "root explorer" app though... no ".img" file sadly), but I understood that the most important file is "nv_data.bin"
So... my problem seems to be like this: http://forum.xda-developers.com/galaxy-s3/help/successful-imei-repair-i9300-backup-t2544109
but only the last step (put back the nv_data.bin, delete backups of bad nv_data.bin, reboot and magic)
The sad part: it doesn't resolve anything because everytime I reboot the phone it recreates the "nv_data.bin" even if I restore the original one (the one i had before downgrading)
Can anyone help me please :angel: ?
I have also tried as seen in other posts to change it's owner into radio:1001, unfortunately it still recreates the file after reboot.
I am currently trying to go back on 4.3 to try to restore the nv_data.bin on that verison (but i don't think it has anything to do with the android version)
Anyone encountered this problem or knows a solution ? Thank you !
Hi,
I see you've already asked about this in the appropriate section for your device. Xda Assist is here to help navigate the site, not for support.... And you found your way already. ?
Thread closed.
Just quoting one of my posts in a related thread, seems like I am not the only one
I had the same problem the last week.
actually, the problem came after doing a factory reset from Salfish OS (installed with multirom), the wifi did not worked in CM12 and Sailfish and I don't know how, but the bootloader reverted to the 4.4 version, so I tried reflashing stock 5.0 with success, the wifi was working, until I did it again (woops. damn curiosity) and reflashing 5.0 stock did not helped
I tried everything;
-Reflashed to stock, 4.4, 5.0, 5.1
-Reflashed Franco kernel (with success, for only the first attempt then after another stock flash the problem came again)
-Reflashed CM11, CM12 and PArom.
After that, I was desperate, and I started deleting everything from /boot, /persist/, /dev without success (maybe I made things worse, in the nexus 5 is pretty much different than a basic linux distro for the computer)
I've also tried generating a new mac in /persist/wifi/.macaddr with no success
Just called google on thursday... They will send me a new phone, hoping they won't notice anything as I have reverted all to stock and relocked bootloader...
(sorry for my bad english, lol)
I also can't connect to bluetooth (it does not have the MAC address too)
Click to expand...
Click to collapse
I may have made a mess deleting some files in /dev and /proc folder, that does not have nothing to do with /persist, macs etc. can someone explain why are these files not included in the stock rom and how can I take it from another phone (if someone can please dump their and upload it on mega i will bless you, or just the entries releated to wifi and bluetooth should be wlan0 and idk)
the .macaddr and .bdaddr are correctly created in the persist folder and configured, but still have this problem
Can be this an hardware problem? ifconfig result no such device
Just because I want to understand what happened in case I'll make this mess too with the new phone
The logcat:
http://pastebin.com/EKrvcYgA
lukypuie said:
Just quoting one of my posts in a related thread, seems like I am not the only one
I may have made a mess deleting some files in /dev and /proc folder, that does not have nothing to do with /persist, macs etc. can someone explain why are these files not included in the stock rom and how can I take it from another phone (if someone can please dump their and upload it on mega i will bless you, or just the entries releated to wifi and bluetooth should be wlan0 and idk)
the .macaddr and .bdaddr are correctly created in the persist folder and configured, but still have this problem
Can be this an hardware problem? ifconfig result no such device
Just because I want to understand what happened in case I'll make this mess too with the new phone
The logcat:
http://pastebin.com/EKrvcYgA
Click to expand...
Click to collapse
Hi. I know I'm late on the bat but I've been battling for ages on this problem.
I read through the forum where you made this post aswell and nothing worked for me.
I thought id reply to this one as it more focused on what I want to ask.
I cannot seem to find the .macaddr and .bdaddr
I dont see any data/persist folder anywhere.
Sorry for noob question but Im really desperate on this one.
My device
(IPRO SENSEI FI)
(OS : KITKAT)
(ROOTED"Using kingoroot but I change to supersu") (ORIGINAL ROM NO CUSTOM)
(STOCK RECOVERY)
(NO HAVE ORIGINAL BACKUP OR Etc. T_T )
If you need more information Ask me.
My problem is Bootloop "Or you have another name, because I do not understand", just stop on logo but it still can go into recovery mode.
The story before the events bootloop or whatever name this problem, So as I recall before this incident I edit files and install Tweaks build.prop with applications My pimp and try other features, it works, but when I restart my device. You know what happened. when just stopped in my logo I does not do anything just to wait so that I fell asleep and when I woke up I realized this a bootloop Or what ? I do not know his name.
At that time I was just doing the usual way way., list.
(Wipe data / Factory reset)
(Wipe cache partition)
(reboot system now)
but no change
(Restore user data)
(backup user data)
(Reboot again)
Still same
(Apply update from ADB - I do not have a pc)
(Apply update from sdcard - No have ORIGINAL ROM, BACKUP ROM, CUSTOM ROM Etc.)
(Apply update from cache - I do not understand what this)
Just information There is writing on my recovery mode "Android System Recovery <3e> ALPS.KK1.MP7.V1" I do not know what this is but I show in case you need it.
Just info :
"I have submitted my problem is on the web and social media owned IPRO but no response, I also have to ask in the thread "is concerned about this issue but no response. I do not know if I really make this thread in the forum Q & A if any anyone please notifications where should I post this thread, I hope anyone can help me here, if no input on how to make this a better thread again please write your comment"
I think your reading if this type of problem?
Is it still could be improved?
Installing custom rom whether other devices can fix this? What is this due to file damage build.prop?
How to fix it?
Can you tell tutorial to solve this problem?
If you told me to look for tutorials on the internet what keywords for this problem?
What is correct I asked here or I OOT?
What do I need to make this thread or just my neighbor asking questions like this course in every thread that said key bootloop?
You do not have to answer all of them just answer that you know or your own statement to me, I am newbie please guidance, Sorry in advance, and thanks afterward
Nano.nano said:
My device
(IPRO SENSEI FI)
(OS : KITKAT)
(ROOTED"Using kingoroot but I change to supersu") (ORIGINAL ROM NO CUSTOM)
(STOCK RECOVERY)
(NO HAVE ORIGINAL BACKUP OR Etc. T_T )
If you need more information Ask me.
My problem is Bootloop "Or you have another name, because I do not understand", just stop on logo but it still can go into recovery mode.
The story before the events bootloop or whatever name this problem, So as I recall before this incident I edit files and install Tweaks build.prop with applications My pimp and try other features, it works, but when I restart my device. You know what happened. when just stopped in my logo I does not do anything just to wait so that I fell asleep and when I woke up I realized this a bootloop Or what ? I do not know his name.
At that time I was just doing the usual way way., list.
(Wipe data / Factory reset)
(Wipe cache partition)
(reboot system now)
but no change
(Restore user data)
(backup user data)
(Reboot again)
Still same
(Apply update from ADB - I do not have a pc)
(Apply update from sdcard - No have ORIGINAL ROM, BACKUP ROM, CUSTOM ROM Etc.)
(Apply update from cache - I do not understand what this)
Just information There is writing on my recovery mode "Android System Recovery <3e> ALPS.KK1.MP7.V1" I do not know what this is but I show in case you need it.
Just info :
"I have submitted my problem is on the web and social media owned IPRO but no response, I also have to ask in the thread "is concerned about this issue but no response. I do not know if I really make this thread in the forum Q & A if any anyone please notifications where should I post this thread, I hope anyone can help me here, if no input on how to make this a better thread again please write your comment"
I think your reading if this type of problem?
Is it still could be improved?
Installing custom rom whether other devices can fix this? What is this due to file damage build.prop?
How to fix it?
Can you tell tutorial to solve this problem?
If you told me to look for tutorials on the internet what keywords for this problem?
What is correct I asked here or I OOT?
What do I need to make this thread or just my neighbor asking questions like this course in every thread that said key bootloop?
You do not have to answer all of them just answer that you know or your own statement to me, I am newbie please guidance, Sorry in advance, and thanks afterward
Click to expand...
Click to collapse
I edit files and install Tweaks build.prop
Click to expand...
Click to collapse
more than likely, it is not booting because you made some bad edits to the build prop. i see this happen a lot.
you will need to find a stock firmware for your device and install it back to fix the problem.
use search terms like "(your device name) return to stock" to try and locate the files.
bweN diorD said:
more than likely, it is not booting because you made some bad edits to the build prop. i see this happen a lot.
you will need to find a stock firmware for your device and install it back to fix the problem.
use search terms like "(your device name) return to stock" to try and locate the files.
Click to expand...
Click to collapse
Thanks for your suggestions and answers, Before I made this thread I have searched from internet Stock firmware or stockrom for my device but I never found it, Is there any other way than to install stock rom or firmware to fix my device, or install a custom rom firmware or install other devices can be made in alternative
Nano.nano said:
Thanks for your suggestions and answers, Before I made this thread I have searched from internet Stock firmware or stockrom for my device but I never found it, Is there any other way than to install stock rom or firmware to fix my device, or install a custom rom firmware or install other devices can be made in alternative
Click to expand...
Click to collapse
you can try searching for a custom rom, that should fix it.
other than that, with no stock firmware, i dont see any way you could fix it.
no, you cant use files from another device, unless it specifically says its ok for your device (very rare, but happens occasionally)
bweN diorD said:
you can try searching for a custom rom, that should fix it.
other than that, with no stock firmware, i dont see any way you could fix it.
no, you cant use files from another device, unless it specifically says its ok for your device (very rare, but happens occasionally)
Click to expand...
Click to collapse
Thank you for your prompt response.
Similarity such as what should I look for when taking custom rom or files from other devices?
Nano.nano said:
Thank you for your prompt response.
Similarity such as what should I look for when taking custom rom or files from other devices?
Click to expand...
Click to collapse
look for it to say directly, it can be used on your device. thats the only way.
bweN diorD said:
because you made some bad edits to the build prop.
Click to expand...
Click to collapse
So there will be plenty of experiments,
CMIIW.
If this error in build.prop can I fix it with this way?:
-Take the backup file build.prop.bak with ADB
-Then Edit it by removing the code that previously I input
-And I input back into the system folder in my device with ADB
-And delete files that are in init.d
What a way as it could to improve my device, because I think if it's just damage build.prop file.
And if I use a custom rom whether he would change the system information such as kernel, android version, and whether he will change the code in the file build.prop and What it will also transform the tweaks in the init.d folder or even add to the pile? I think if a custom rom working to add code or tweaks both in build.prop or init.d I think it will worsen, CMIIW, because I think if true custom rom works like that then it is not a good solution
Nano.nano said:
So there will be plenty of experiments,
CMIIW.
If this error in build.prop can I fix it with this way?:
-Take the backup file build.prop.bak with ADB
-Then Edit it by removing the code that previously I input
-And I input back into the system folder in my device with ADB
-And delete files that are in init.d
What a way as it could to improve my device, because I think if it's just damage build.prop file.
And if I use a custom rom whether he would change the system information such as kernel, android version, and whether he will change the code in the file build.prop and What it will also transform the tweaks in the init.d folder or even add to the pile? I think if a custom rom working to add code or tweaks both in build.prop or init.d I think it will worsen, CMIIW, because I think if true custom rom works like that then it is not a good solution
Click to expand...
Click to collapse
1. i have no idea what CMIIW means
2. yes, if you have an original copy of the build prop or can remove edits from the current one, and can replace with adb, that would be good.
3. i would try fixing one thing at a time to see what actually caused the issue. init may or may not need to be fixed.
4. custom rom would clean and replace the entire system including kernel, so it should fix the issue. however, this is your choice, its not a bad option, just a different one.
bweN diorD said:
1. i have no idea what CMIIW means
2. yes, if you have an original copy of the build prop or can remove edits from the current one, and can replace with adb, that would be good.
3. i would try fixing one thing at a time to see what actually caused the issue. init may or may not need to be fixed.
4. custom rom would clean and replace the entire system including kernel, so it should fix the issue. however, this is your choice, its not a bad option, just a different one.
Click to expand...
Click to collapse
CMIIW is Correct Me If I'm Wrong.
Finally, I have two ways for the try, the title and content of this thread may be changed if it is successful.
Thank you for helping me
Thank you for patiently explained
Now I know what to do,
thank you for your participation
thank you very much :good:
no problem
Hello all. I am new to the forum and I do not speak English. Helping a google translator.
I have a phone Allview x2 Xtreme and a small problem.
I root my phone out of your forum and I fell android system, so I downloaded the go with your forum and installed. everything went without any problems with one exception. My problem is the inability to save any files to the phone memory. Downloading various applications from Google Play but do not sign up and grind endlessly. Factory settings restored more than once and not washed your any positive results. It seems to me that after installing rom should create folders, unfortunately, nothing. Computer and telephone see partition, but you can not have any utorzyć folders. Please help and sorry for my language.
Something else I noticed. On the phone memory is formed TWRP folder and no other can not be next to him to create. But in the middle of TWRP you can create other folders may help. Or YWRP adapted at each other partition memory and therefore does not see the android. Please help phone admittedly under warranty but with us is how to give the equipment to the site takes a long time to repair.
I'm having the same issue... currently looking for a fix. Seems that TWRP is incorrectly formatting the device.
OK, I had to utilize the Gionee scatter file and stock ROM in order to get the phone partitioned correctly,
I then took the BLU Scatter file and Stock ROM , boot, and recovery and flashed it afterward. Then did a factory reset. Took updates then rooted, again. You are left with the Gionee splash screen... But that's an easy fix.
Appears that the versions of TWRP posted DO NOT partition the phone correctly and writes a TWRP partition that screws everything up.
I will post links or you can find them yourself in the meantime. They are all on xda mainly on the thread about rooting... Odd thing is. Phone seems to run better than before... I would have left the Gionee ROM up and running if it wasn't 4G only... I'll post links later.