Related
Hello all
I need help
Unfortunately I have managed to damage my 2.1 rom. (i have replaced 2.1 framework-res.apk)
Now I cannot boot into it , problem is that I do not have a backup, so I cannot just easily "reburn" the firmware.
I have 2.2 ROM implemented. but I do not -know how to reach 2.1 system files from it. There is some chroot done in boot process imho .
Can anybody help me how to reach the files
I have a backup of framework-res.apk
thermoska said:
Hello all
I need help
Unfortunately I have managed to damage my 2.1 rom. (i have replaced 2.1 framework-res.apk)
Now I cannot boot into it , problem is that I do not have a backup, so I cannot just easily "reburn" the firmware.
I have 2.2 ROM implemented. but I do not -know how to reach 2.1 system files from it. There is some chroot done in boot process imho .
Can anybody help me how to reach the files
I have a backup of framework-res.apk
Click to expand...
Click to collapse
Code:
adb shell
mkdir 21system
mount -o rw /dev/block/mtdblock2 /21system
If you're lucky it will mount your 2.1 system partition as /21system
Most likely it will say "Device or resource busy"... But worth trying anyway.
Cheers
Thanks
I had to think about remount
Going to try now ..
EDIT:
You are absolutelly right : Device or resource busy .
What should I try now ?
I found out that I can reach 2.1 system in adb , but my root do not work. so I cannot do anything to the system partition . Any ideas how to achieve root in this state ? On phone display there is still only firts sony ericsson logo ..
thermoska said:
Hello all
I need help
Unfortunately I have managed to damage my 2.1 rom. (i have replaced 2.1 framework-res.apk)
Now I cannot boot into it , problem is that I do not have a backup, so I cannot just easily "reburn" the firmware.
I have 2.2 ROM implemented. but I do not -know how to reach 2.1 system files from it. There is some chroot done in boot process imho .
Can anybody help me how to reach the files
I have a backup of framework-res.apk
Click to expand...
Click to collapse
I did the same thing at least twice. I was able to save it without restoring by replacing my framework-res.apk before it rebooted or froze.
Basically, try to adb into it while it is still at the Sony logo or if you get the blackscreen after the logo.
One weird thing I did notice was that I was able to replace the framework-res.apk file apparently without using 'su'. After I killed it when I was doing adb at/after the logo I tried to 'su' but it gave some error and remained at the '$' prompt. I then did the 'dd if=/sdcard/framework-res.apk of=/system/framework/framework-res.apk' command and it completed. Rebooted and it worked again.
Think my whole thing was tested second time with a script.
Try making a frameworkfix.cmd file and putting this in it.
@echo off
@echo.
@echo Installing Framework
@echo.
@adb shell su
@adb push framework-res.apk /sdcard/framework-res.apk
@adb shell dd if=/sdcard/framework-res.apk of=/system/framework/framework-res.apk
The keep trying to run it while at the Sony logo. Give it a few runs before you give up, I swear it worked for me.
thermoska said:
I found out that I can reach 2.1 system in adb , but my root do not work. so I cannot do anything to the system partition . Any ideas how to achieve root in this state ? On phone display there is still only firts sony ericsson logo ..
Click to expand...
Click to collapse
Heck just try the following from folder with your original framework.
adb push framework-res.apk /sdcard/framework-res.apk
adb shell dd if=/sdcard/framework-res.apk of=/system/framework/framework-res.apk
or
adb push framework-res.apk /sdcard/framework-res.apk
adb shell
su
dd if=/sdcard/framework-res.apk of=/system/framework/framework-res.apk
thanks guys , but I do not need commands,
I know them already , I had permissions problem.
Instructions mentioned above did not worked for me
I've got permission denied
anyway thanks
thermoska said:
Thanks
I had to think about remount
Going to try now ..
EDIT:
You are absolutelly right : Device or resource busy .
What should I try now ?
I found out that I can reach 2.1 system in adb , but my root do not work. so I cannot do anything to the system partition . Any ideas how to achieve root in this state ? On phone display there is still only firts sony ericsson logo ..
Click to expand...
Click to collapse
You can access the 2.1 /system partition through 2.2 with adb.
Use this to unmount 2.2 /system
Code:
su
busybox umount /dev/block/loop1
You can check if all worked well this way:
Code:
busybox ls -1d /system/* | grep xbin
If it gives you anything, it's 2.1 -- if not, try
Code:
busybox umount -l /dev/block/loop1
Now, you should have the old 2.1 /system structure available. Ignore all errors appearing *on the phone* it'll be screwed up, unusable. Until a restart.
Now through adb you can overwrite your 2.1 framework apk with dd
(assuming you already have it on the sdcard, else, well, push it there (adb push framework.apk /mnt/sdcard/ )
Code:
dd if=/mnt/sdcard/framework.apk of=/system/framework/framework.apk
for remount system, just do
Code:
busybox mount -o remount,rw /system
after you have the 2.1 system available.
I installed 2.2 to my nand (almost fully working) at one point this way =3
Or...
You can flash again just using system.bin and everything you had would be there.
;-)
You also will need loader.sin
I did this a couple of times and work for me; I only need to root again
Good luck!
PS: In the firmware folder, you need to leave ONLY this 2 files: System.sin and loader.sin. Backup and delete all other files like amss.sin, cache.sin, etc.
well thank you
This a good idea ..
Unfortunatelly I already reflashed the phone
Hope it will help to somebody in the future
ttxdragon said:
I installed 2.2 to my nand (almost fully working) at one point this way =3
Click to expand...
Click to collapse
Thought that would work, was going to do it with .003, but I guess the recovery tool will do that for us - now we see what Z has been working on - excellent news
Just curios. Any speed improvements when extracting the img files to nand and mount/run it from there ?
Even running from sdcard img files is a perfect backup solution by just copy the img files away from time to time. But of course r/w cycles of the card are increased --> less lifetime.
But otherwise running from images is nice, as you're able to mount them. (diskinternals linux reader but R-only)
Anyone knows a win32 prog to mount the img files r/w ?
Hey there , I'm a new Lg P500 User and I am really Unclear how to flash a custom recovery mod / megatron v1 / screen lag touch fix by milk_os
About Phone
Model: LG-P500
Android Version: 2.2.2
Kernel Version: 2.6.32.9
Software Version:V10F
Rooted with Superuser using GingerBreak .
The original thread: http://forum.xda-developers.com/showthread.php?t=1044765
Also Installed with busybox from the market.
So if anyone can show me a step by step guide to how to install custom recovery mod , megatron v1 and touch screen lag fixer by milk_os. I will reward
you with $100 Singapore by PayPal.I believe in meritocracy
Links
Custom Recovery Mod:http://androidforums.com/getitnowmarketing/221388-custom-recovery-optimus-one-p500-thunderg.html
Megatron V1: http://forum.xda-developers.com/showthread.php?t=870640
Touch Screen Bug: http://forum.xda-developers.com/showthread.php?t=929941
Let the hack rage begin!
Thank You.
danialrocker said:
Hey there , I'm a new Lg P500 User and I am really Unclear how to flash a custom recovery mod / megatron v1 / screen lag touch fix by milk_os
About Phone
Model: LG-P500
Android Version: 2.2.2
Kernel Version: 2.6.32.9
Software Version:V10F
Rooted with Superuser using GingerBreak .
The original thread: http://forum.xda-developers.com/showthread.php?t=1044765
Also Installed with busybox from the market.
So if anyone can show me a step by step guide to how to install custom recovery mod , megatron v1 and touch screen lag fixer by milk_os. I will reward
you with $100 Singapore by PayPal.I believe in meritocracy
Links
Custom Recovery Mod:http://androidforums.com/getitnowmarketing/221388-custom-recovery-optimus-one-p500-thunderg.html
Megatron V1: http://forum.xda-developers.com/showthread.php?t=870640
Touch Screen Bug: http://forum.xda-developers.com/showthread.php?t=929941
Let the hack rage begin!
Thank You.
Click to expand...
Click to collapse
lol luckly i live in singapore
first of all, lets start with custom recovery
1. Download the custom recovery file from here and here
2. DO NOT rename them, and put them neatly inside the ROOT of the SD CARD (that means it should be at /sdcard/ on androids
3. next, get Terminal Emulator from the market. search it.
4. Get a nice keyboard to work on for a while. you need to type A LOT
5. get titanium backup and backup everything. menu > batch
6. reboot phone.
7. Turn on phone and go to terminal and type the following
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
flash_image recovery /sdcard/recovery-RA-GNM-thunderg-1.1.0.img
Click to expand...
Click to collapse
*there should be no error except at stage 5 there could be, but not always.
8. good. flash complete. now grab the megatron ROM and the lagfix. they both should be .zip . DONT OPEN IT.
9 put the two inside the root of SD card
10. go to terminal, write
su
*press enter*
reboot recovery
11. you should have a menu of things. go to flash zip or sth (you will know) w/ ur volume buttons
12. press menu and you will be able to choose the two zips. flash any of them first, and do the second afterwords.
13. YAY DONE
14. no need for bucks thanks. just press the thanks button down there. its free.
*PM or EMAIL ME IF YOU WANT FURTHER HELP*
*[email protected]*
Also, isnt 2.2.2 not rootable??
I think it has to be downgraded to 2.2 and then rooted..
Edit:
Sorry, My mistake.. Didnt realize 2.2.2 is rootable now..
2.2.2 it's now rootable
It says that "/system/etc/install-recovery.sh ": No such file or directory.
I'm sure that I placed both of the files on the root of my sdcard
Well, I guess the hardest part is getting the recovery. Well I share my method so, here we go.
What you need:
1. terminal emulator(download from market - free)
2. recovery installer(download here)
3. your ROM which is megatron(download here)
4. Touch-screen bug fix(download here)
5. Back-up all your SD contents to your PC.
-. optional: if your file explorer doesn't support unrar/unzipping, download one. but since you have a PC just use winrar.
when you have everything, lets start.
1. extract contents of "recovey_installer.rar" to the root(meaning the base) of your SDcard.(it contains 3 files, so you should also see 3 new files on your SD card).
2. open terminal emulator, enter these lines(press enter after each line):
Code:
su
sh /sdcard/rf.sh
just wait and this should reboot you directly to recovery.
3. now in recovery(remember: "vol + and - button" is "up and down" "menu button is ok/select" and "back button" is back) select options:
Partition sdcard > partition SD
4. when asked choose your desired partition size then choose swap size as 0. This should format your SD card.(initially this will leave you with an ext2 partition, if you want ext3 then upgrade it to ext3 and so on using the same menu)
5. when done, press back repeatedly and reboot.
6. now, move your ROM(megatron) and the touchscreen-lag-fix files to the root of your SD card.
7. open terminal again and enter these commands
Code:
su
reboot recovery
just wait and it should bring you back to recovery.
8. in recovery, choose option:
- flash zip menu
- to avoid hiccups just toggle the signature verification
- flash zip from sdcard
- first flash your rom(megatron), when done immediately flash touchscreen-bug-fix
- press back repeatedly then reboot.
9. enjoy
danialrocker said:
It says that "/system/etc/install-recovery.sh ": No such file or directory.
I'm sure that I placed both of the files on the root of my sdcard
Click to expand...
Click to collapse
just ignore that error message. this line is only there for those with different phone models which has the mention file in the phone internal storage. so this shouldn't affect optimus one users.
@ungaze, i did your way . It took me to android system recovery .
Anyway it didnt ask me for partition sdcard. So should i just reboot my phone?
congratulations, you now have recovery. you should see some options.
press volume buttons to navigate up and down(menu button=select/ok). Choose the option:
- Partition sdcard
- Partition SD
If you want to explore your phone a bit more, you could just reboot your phone for now. Just remember, to go back to recovery you could open terminal and enter:
Code:
su
reboot recovery
or when phone is off, press and hold "power/lock button"+"home button"+"vol down button" until recovery menu shows up.
Alright , did that . My friend told me about nandroid how can i do that before i flash the other roms ?
theres a menu option "backup/restore" open it and choose "nand backup". when done, there should be a folder in your SD named "nand" copy the contents to a pc or somewhere safe as this will serve as your backup file.
Okay, i did a nandroid and ready to flash roms . Wish me well =)
Anyway why do i receive E:Bad boot message when i reboot recovery.
everyone has it. it's perfectly fine. good luck
Anyway, as I was nandroid-ing i saw this video http://www.youtube.com/watch?v=s5GWgjJT2zo in the end, it shows the guy having no reception?
edit: He didnt have it on at the first place anyway. Sorry for the inconvenience.
i didnt view the link but im guessing hes using amon_ra v1.1, the method i gave you installs amon_ra v1.2 which fixes most bugs with ext4 and nand recovery/backup
By toggl-ing signature verification do you mean to enable or disable it?
disable. this is really not necessary as the zips youre about to apply are surely signed. but in case you have problems in the future, just remember that disabling sig veryfication may fix the problem.
Thanks man, how do i donate to you?
Btw i just screw my phone. Stuck at android screen page ;(. How do i restore the nandroid backup? Should i wipe my phone first, then do nandroid restore?
Will it restore me my version 2.2.2?
When i nandroid it , my phone was on ver 2.2.2
Ungaze?
Sent from my LG-P500 using XDA Premium App
Check your inbox
I'm just writting this because i've recently had this problem. I managed to sort it out by my own but didn't really find it written anywhere, just bits and pieces scavenged from so many pages that might point to a solution (granted, part of my problem was also finding what was really my problem since the phone stopped working so fast i didn't really had the time to get what happened)
I was trying out swap for my S3, i had created a swap partition in my external card and then followed a guide here from xda to use an app called swapper2 (from market) to enable swap. I must have done something wrong because what it did was format my /efs partition instead as if it was a swap partition. Phone stopped working on the spot, obviously, and wouldn't past samsung's bootscreen.
Also, keep in mind while this worked for me there might be other ways of doing this which may be simpler. This is just what i figured for a solution.
When this helps:
- you accidentally formated your /efs partition
- you have a backup from your /efs partition, files copied with root explorer but not an image you can just flash back to the partition.
- your phone boots to download and to recovery but not to main system (which every tutorial i found seemed to assume to be able to do, i just figured their /efs was not as screwed as mine was)
- your recovery won't mount the /efs partition because it expects it to be ext4 but it's formated to something else and it showing the message:
"e: failed to mount /efs (Invalid argument)"
What doesn't work:
- any kind of standard solution like reflashing a stock rom with odin, with or without .pit file, clear EFS, whatever. It will flash, just won't solve since, apparently, nothing touches the /efs partition because it's so sensible. Even custom recoveries do mount it and apparently format and replace every single other partition but the /efs, which is why i had to do it manually.
Solution:
- simply format the /efs partition back to ext4 and copy your backup files there
What's needed:
- phone drivers installed on the computer. If you had kies installed, this should be covered already. Think you can't have it running while doing this though. Also, for what's worth, i've done this with windows 8 x64.
- updated android sdk tool, mainly adb. If adb is saying device not connected or not found, you may be using an outdated adb.exe (i was). I used adb.exe that came with this software here:
http://forum.xda-developers.com/showthread.php?t=1308546
- root. If your rom isn't rooted you can always flash CF-root from odin in download mode.
http://forum.xda-developers.com/showthread.php?t=1695238
- busybox, am not really sure if i actually got to need this, think so for the formating tool. Can't hurt to have more options though. This is how to install:
http://www.omappedia.com/wiki/Android_Installing_Busybox_Command_Line_Tools
- custom recovery that allows root through adb, i used Philz which is pretty awesome
http://forum.xda-developers.com/showthread.php?t=2002953
- backup files from your /efs. I had mine unzipped and copied to my externalsd while in windows. They were in an efs folder in the sd card. You can push this through adb to the phone later, but i found this way simpler.
How to:
- get into recovery (vol up+home+power button) and plug your phone to the computer. You'll hear an usb connected sound from windows after a bit.
- in recovery, navigate to Mounts and try the "mount /efs". It'll fail. Now, navigate to advanced and "view log". You'll see below that the phone tried to mount a partition and failed, in my case, it had unsucessfully tried to mount /dev/block/mmcblk0p3 which is the partition /efs uses. Take note of this partition name.
- On windows, open a command line (type cmd on you start menu), navigate to where you have adb.exe and type:
adb shell
If all went well, command prompt has changed. You can now issue commands directly to your phone from terminal.
- type "su" to get root permissions. Your command line should change to something like [email protected] Before i had this working i needed to use "Fix permissions". It's an option in the recovery menus on the phone.
- this step is optional but i did it anyway. I created an image of the partition i was going to mess with. If anything went wrong i could always flash it back even if it was broken. By the way, this is what i should have done in the first place instead of just copying /efs files. Would have made the process so much simpler... also, do this if you ever get the phone back working again. Type:
dd if=/dev/block/mmcblk0p3 of=/externalsd/efs.img
The /externalsd/efs.img is just a place you can save stuff to, like your external sd card. You can check what's your mounting point for the card with the command "mount" and look for something relevant like "externalsd".
Also, you may want to copy that efs.img to somewhere else from your phone (like your computer) for safekeeping. Literally remove card from phone, put in computer and copy files there. Notice you may need to reboot phone to recovery if you remove your card so it detects and mounts your card again. Sure, you can also do that from the command line, but it's just easier to reboot the phone.
- Now, we'll format the partition to something your phone can mount (ext4) and is expecting. Be careful, by doing this, you're actually erasing what's left of your partition and replacing by something clean. Type:
mk2fs /dev/block/mmcblk0p3
If all went well, you should see some kind of small report about what was just done.
- To mount this we'll need a mounting point. Type:
mkdir /efs
this will create an /efs folder in root, if it doesn't exist already, and to mount, type:
mount -t ext4 /dev/block/mmcblk0p3 /efs
- if all went well, you now have access to the /efs folder and can copy you files back:
cp -r /externalsd/efs/* /efs
where externalsd was my external sd card mounted on my phone.
- Check if your /efs folder has it's contents properly
ls /efs
I had to reboot the phone to recovery once more at this point and use the "fix permissions" option again.
After this, my phone booted up normally again.
I'm getting Segmentation fault, I guess there's some kinda hardware error on my phone. Gonna take it to Sammy's tomorrow.
Code:
mke2fs -F /dev/block/mmcblk0p11
Segmentation fault
sh-4.2#
Hi thnx for your Guide. I have the EFS problem, after installin 4 diferent rom in 2 hours my imei and baseband lost.( dont now why) i dont have a backup. I was thinking if it take the EFS from another S3 does it work?
Will this work with a Galaxy S4? I545
Enea307 said:
Hi thnx for your Guide. I have the EFS problem, after installin 4 diferent rom in 2 hours my imei and baseband lost.( dont now why) i dont have a backup. I was thinking if it take the EFS from another S3 does it work?
Click to expand...
Click to collapse
No. Read General > Sticky roll-up thread > "IMEI / EFS - Know this stuff"
is normal this output? (i'm meaning the tar.gz unfinding file)
Code:
*****************************************
* BACKUP EFS *
*****************************************
WARNING: Do you wish to Continue? (This will make EFS BACKUP) [Y,N]?Y
--- STARTING ----
--- WAITING FOR DEVICE
--- Backup efs image ---
761 KB/s (9357 bytes in 0.012s)
7 KB/s (39 bytes in 0.005s)
SM-N9000ZWEXXV_N900XXUCMJ3_RF1DA111EAY_
Creating filesystem with parameters:
Size: 20971520
Block size: 4096
Blocks per group: 32768
Inodes per group: 1280
Inode size: 256
Journal blocks: 1024
Label:
FLEX_BG size: 0
Blocks: 5120
Block groups: 1
Reserved block group size: 0
Created filesystem with 59/1280 inodes and 2432/5120 blocks
40960+0 records in
40960+0 records out
20971520 bytes transferred in 7.271 secs (2884269 bytes/sec)
unknown option -- ZBusyBox v1.19.4-cm9 bionic (2012-02-05 18:40 +0100) multi-cal
l binary.
Usage: tar -[cxtzjahmvO] [-X FILE] [-T FILE] [-f TARFILE] [-C DIR] [FILE]...
Create, extract, or list files from a tar file
Operation:
c Create
x Extract
t List
f Name of TARFILE ('-' for stdin/out)
C Change to DIR before operation
v Verbose
z (De)compress using gzip
j (De)compress using bzip2
a (De)compress using lzma
O Extract to stdout
h Follow symlinks
m Don't restore mtime
exclude File to exclude
X File with names to exclude
T File with names to include
2684 KB/s (9962352 bytes in 3.623s)
2805 KB/s (20971520 bytes in 7.299s)
remote object '/sdcard/SM-N9000ZWEXXV_N900XXUCMJ3_RF1DA111EAY_EFS.tar.gz' does n
ot exist
7-Zip (A) 4.65 Copyright (c) 1999-2009 Igor Pavlov 2009-02-03
Scanning
SM-N9000ZWEXXV_N900XXUCMJ3_RF1DA111EAY_EFS.tar.gz: WARNING: Impossibile trovare
il file specificato. [COLOR=Red](impossible to find the specify file)[/COLOR]
Creating archive SM-N9000ZWEXXV_N900XXUCMJ3_RF1DA111EAY_EFS.zip
Compressing getprop.txt
Compressing SM-N9000ZWEXXV_N900XXUCMJ3_RF1DA111EAY_EFS.raw.img
Compressing SM-N9000ZWEXXV_N900XXUCMJ3_RF1DA111EAY_EFS.tar.md5
WARNINGS for files:
SM-N9000ZWEXXV_N900XXUCMJ3_RF1DA111EAY_EFS.tar.gz : Impossibile trovare il file
specificato.[COLOR=Red] (impossible to find the specify file)[/COLOR]
----------------
WARNING: Cannot find 1 file
-
-
Finished. Output file is SM-N9000ZWEXXV_N900XXUCMJ3_RF1DA111EAY_EFS BACKUP
Premere un tasto per continuare . . .
well in the zip there are only the txt + md5 + .raw.img
Thanks for this great tutorial. It was my final step to recover my efs partition, without any backup. I copied the efs folder from another device and modified the files according my devices info (bluetooth mac, serial etc). Worked great on my SGS4
By the way I had the same error:
Code:
mke2fs /dev/block/mmcblk0p10
Segmentation fault
You get this error if you run adb shell when you booted to your ROM.
You need to run adb shell in recovery mode
Great tutorial but i hope you can help me, I can't seem to properly find the SDcard. When I type cp -r /externalsd/efs/* /efs
it comes back with cp: can't stat '/sdcard/efs*' : No such file or directory
I cleared my whole sdcard card except for efs directory. I also tried sdcard instead of externalsd but same thing.
I am getting stuck trying to fix this as I have a boot loop or corrupt /efs or something. I have tried to get my phone working by installing my ROM ( Omega v58 ) and also by trying to flash the latest stock 4.3 through Odin v3.09. I havent tried total stock 4.0.3 yet. No matter what I have done though I can't get past the boot logo ( or the walking Omega droid ). My phone just sits there and hangs
I have followed your steps and I have Philz ( 6.07.9.19 ) installed ( but not busybox unless it is sat there somehow from the Omega install ) but when i try to get adb shell running nothing happens or works..as you can see
What am i doing wrong? OR is my phone totally borked?
hi..
Blackwatch said:
I am getting stuck trying to fix this as I have a boot loop or corrupt /efs or something. I have tried to get my phone working by installing my ROM ( Omega v58 ) and also by trying to flash the latest stock 4.3 through Odin v3.09. I havent tried total stock 4.0.3 yet. No matter what I have done though I can't get past the boot logo ( or the walking Omega droid ). My phone just sits there and hangs
I have followed your steps and I have Philz ( 6.07.9.19 ) installed ( but not busybox unless it is sat there somehow from the Omega install ) but when i try to get adb shell running nothing happens or works..as you can see
What am i doing wrong? OR is my phone totally borked?
Click to expand...
Click to collapse
I have successfully fix my efs partition follwing this thread.
you are receiving such message in cmd. I faced it too.
Sol: Use Philoz Recovery 5.0.
Fix permissions.
there you are.. done..
Philz 6.0 do not have an option for "fix permission".
hope it helps..
I wrote a script that attempts to recover your nv_data.bin from a corrupted EFS partition for the i9300. Thus if you don't have a backup and your EFS is corrupt, try the script. The script is still in Alpha phase and may not work for other devices. Feedback would be much appreciated.
You can find the script at: https://github.com/chriscz/efs_recover
I dont have /efs backed up
Hi ,
If i dont have /efs backed up , can I copy any other mobile (same model) efs data to my mobile and try?
Thanks and Regards
Vamshi Pulumati
vamshipulumati said:
Hi ,
If i dont have /efs backed up , can I copy any other mobile (same model) efs data to my mobile and try?
Thanks and Regards
Vamshi Pulumati
Click to expand...
Click to collapse
No, it won't work and trying to clone another imei is illegal.
boomboomer said:
No, it won't work and trying to clone another imei is illegal.
Click to expand...
Click to collapse
How to register for a new IMEI ? Is it possible?? Could you please help me with any site or link?? I don't want to replace motherboard..
Any help are highly appreciated.
No, it isn't possible and discussion about changing imei is banned on xda.
Take your phone to a service centre and pay then to recode it for you, make sure it works on 4.3 before you pay.
boomboomer said:
No, it isn't possible and discussion about changing imei is banned on xda.
Take your phone to a service centre and pay then to recode it for you, make sure it works on 4.3 before you pay.
Click to expand...
Click to collapse
Hey I would like to tell you that a miracle happened for my S3. Yesterday i tried to do same as per in this guide. After taking backup of broken efs backup i tried to clear the efs folder with this command "mk2fs /dev/block/mmcblk0p3"
After that i just flashed 4.4.4 based stock ROM and somehow phone booted up perfectly. No network issues. Bluetooth wifi sim card everything works. IMEI & Serial No is there. But when i'm checking network unlock status it is showing as everything locked. But still I can use everything... I'm amazed.!!!!
Do you have any idea how this happened??
@boomboomer
Same problem with a Samsung gt-i9070 - Galaxy S Advance
Hi!
My i9070 has the same problem, but when i run the command: "mke2fs /dev/block/mmcblk0p3" shows the "Segmentation fault" error message.
Some one can help?
Thanks.
Bro U stated to format but How to format /efs partition
/efs not backed up
boomboomer said:
No, it won't work and trying to clone another imei is illegal.
Click to expand...
Click to collapse
I Dont have efs backed up and I also have formatted efs partition from adb shell and using that Dev type commands now i am in factory mode and my network is not working please give me any solution.
kaynpayn said:
I'm just writting this because i've recently had this problem. I managed to sort it out by my own but didn't really find it written anywhere, just bits and pieces scavenged from so many pages that might point to a solution (granted, part of my problem was also finding what was really my problem since the phone stopped working so fast i didn't really had the time to get what happened)
I was trying out swap for my S3, i had created a swap partition in my external card and then followed a guide here from xda to use an app called swapper2 (from market) to enable swap. I must have done something wrong because what it did was format my /efs partition instead as if it was a swap partition. Phone stopped working on the spot, obviously, and wouldn't past samsung's bootscreen.
Also, keep in mind while this worked for me there might be other ways of doing this which may be simpler. This is just what i figured for a solution.
When this helps:
- you accidentally formated your /efs partition
- you have a backup from your /efs partition, files copied with root explorer but not an image you can just flash back to the partition.
- your phone boots to download and to recovery but not to main system (which every tutorial i found seemed to assume to be able to do, i just figured their /efs was not as screwed as mine was)
- your recovery won't mount the /efs partition because it expects it to be ext4 but it's formated to something else and it showing the message:
"e: failed to mount /efs (Invalid argument)"
What doesn't work:
- any kind of standard solution like reflashing a stock rom with odin, with or without .pit file, clear EFS, whatever. It will flash, just won't solve since, apparently, nothing touches the /efs partition because it's so sensible. Even custom recoveries do mount it and apparently format and replace every single other partition but the /efs, which is why i had to do it manually.
Solution:
- simply format the /efs partition back to ext4 and copy your backup files there
What's needed:
- phone drivers installed on the computer. If you had kies installed, this should be covered already. Think you can't have it running while doing this though. Also, for what's worth, i've done this with windows 8 x64.
- updated android sdk tool, mainly adb. If adb is saying device not connected or not found, you may be using an outdated adb.exe (i was). I used adb.exe that came with this software here:
http://forum.xda-developers.com/showthread.php?t=1308546
- root. If your rom isn't rooted you can always flash CF-root from odin in download mode.
http://forum.xda-developers.com/showthread.php?t=1695238
- busybox, am not really sure if i actually got to need this, think so for the formating tool. Can't hurt to have more options though. This is how to install:
http://www.omappedia.com/wiki/Android_Installing_Busybox_Command_Line_Tools
- custom recovery that allows root through adb, i used Philz which is pretty awesome
http://forum.xda-developers.com/showthread.php?t=2002953
- backup files from your /efs. I had mine unzipped and copied to my externalsd while in windows. They were in an efs folder in the sd card. You can push this through adb to the phone later, but i found this way simpler.
How to:
- get into recovery (vol up+home+power button) and plug your phone to the computer. You'll hear an usb connected sound from windows after a bit.
- in recovery, navigate to Mounts and try the "mount /efs". It'll fail. Now, navigate to advanced and "view log". You'll see below that the phone tried to mount a partition and failed, in my case, it had unsucessfully tried to mount /dev/block/mmcblk0p3 which is the partition /efs uses. Take note of this partition name.
- On windows, open a command line (type cmd on you start menu), navigate to where you have adb.exe and type:
adb shell
If all went well, command prompt has changed. You can now issue commands directly to your phone from terminal.
- type "su" to get root permissions. Your command line should change to something like [email protected] Before i had this working i needed to use "Fix permissions". It's an option in the recovery menus on the phone.
- this step is optional but i did it anyway. I created an image of the partition i was going to mess with. If anything went wrong i could always flash it back even if it was broken. By the way, this is what i should have done in the first place instead of just copying /efs files. Would have made the process so much simpler... also, do this if you ever get the phone back working again. Type:
dd if=/dev/block/mmcblk0p3 of=/externalsd/efs.img
The /externalsd/efs.img is just a place you can save stuff to, like your external sd card. You can check what's your mounting point for the card with the command "mount" and look for something relevant like "externalsd".
Also, you may want to copy that efs.img to somewhere else from your phone (like your computer) for safekeeping. Literally remove card from phone, put in computer and copy files there. Notice you may need to reboot phone to recovery if you remove your card so it detects and mounts your card again. Sure, you can also do that from the command line, but it's just easier to reboot the phone.
- Now, we'll format the partition to something your phone can mount (ext4) and is expecting. Be careful, by doing this, you're actually erasing what's left of your partition and replacing by something clean. Type:
mk2fs /dev/block/mmcblk0p3
If all went well, you should see some kind of small report about what was just done.
- To mount this we'll need a mounting point. Type:
mkdir /efs
this will create an /efs folder in root, if it doesn't exist already, and to mount, type:
mount -t ext4 /dev/block/mmcblk0p3 /efs
- if all went well, you now have access to the /efs folder and can copy you files back:
cp -r /externalsd/efs/* /efs
where externalsd was my external sd card mounted on my phone.
- Check if your /efs folder has it's contents properly
ls /efs
I had to reboot the phone to recovery once more at this point and use the "fix permissions" option again.
After this, my phone booted up normally again.
Click to expand...
Click to collapse
I have restored my s6 edge by following this method. The EFS partition name is "sda3" for s6 edge if anyone want to restore s6 edge. There is typo in command "mk2fs /dev/block/mmcblk0p3" it should be mke2fs i think.
After restoring EFS my phone recovered from boot loop. But the imei is still invalid. Do you know any method to repair imei for s6 edge?. Thank You
---------- Post added at 02:18 PM ---------- Previous post was at 02:14 PM ----------
Blackwatch said:
I am getting stuck trying to fix this as I have a boot loop or corrupt /efs or something. I have tried to get my phone working by installing my ROM ( Omega v58 ) and also by trying to flash the latest stock 4.3 through Odin v3.09. I havent tried total stock 4.0.3 yet. No matter what I have done though I can't get past the boot logo ( or the walking Omega droid ). My phone just sits there and hangs
I have followed your steps and I have Philz ( 6.07.9.19 ) installed ( but not busybox unless it is sat there somehow from the Omega install ) but when i try to get adb shell running nothing happens or works..as you can see
What am i doing wrong? OR is my phone totally borked?
Click to expand...
Click to collapse
You don't have to run "su" command. "#" shows you already have root access.
After I flashed a couple roms I couldn't boot jelly bean anymore and I noticed the error in recovery: E:\ Cant Mount /efs, when installing. But I could still boot ICS but not jellybean. I still had my IMEI and could make calls but could not boot jelly bean because it couldn't mount.
How does this issue happen?
Sometimes when installing a rom something goes wrong and it changes the partition type of /efs making it unable to be mounted. The partition is usually from ext4 to swap.
Most likely this will work on your phone but if it doesn't and your phone stops working I am not responsible.
If your like me and you couldn't get jelly bean to work then flash your device back to ics and it should boot. Once your booted inside of ics we can start the process.
Pre-Setup:
1. Be rooted and have a custom recovery installed.
2. Be on Ics and it boots.
3. Your need to have a Jelly Bean rom like Cyanogenmod on your sdcard.
4. Have adb installed on your pc and usb debugging on in your phone/tab.
Now that that's done its time to start.
Part One:
1. Boot into recovery.
2. We need to find the efs block location.
3. Go to mounts and select efs
4. It should say unable to mount
5. Go to advance and make a recovery.log
6. Put that file on your computer and open it.
7. Look through the file and you should fine something like this around the beginning of the file:
E:Unable to mount '/efs'
I:Actual block device: '/dev/block/mmcblk0p3', current file system: 'swap'
My location is /dev/block/mmcblk0p3 But yours could be different! Most likely the difference will be instead of it ending with a 3 it will be a different number. I will be saying /dev/block/mmcblk0p3 if yours is different just change it to your location.
*WARNING* Sometimes when you copy paste into adb it will auto run the command without you pressing enter. If your location is different then mine and you copy past and it auto runs it could be BAD so to be careful if you want to copy past. Copy the command paste it into Google make the change and copy that and paste into adb
Part Two:
1. When your inside recovery connect your phone to your computer and get into a adb shell. (Sometimes it will take awhile for adb to recognize your device so be patient.)
2. Once you have adb access its time to start entering the commands.(Again my location may be different the yours! Most likely the difference will be instead of it ending with a 3 it will be a different number.
Part Three Inside ADB:
1. su
2. dd if=/dev/block/mmcblk0p3 of=/sdcard/efs.img
3. mke2fs /dev/block/mmcblk0p3
4. mkdir /efs
5. mount -t ext4 /dev/block/mmcblk0p3 /efs
DONT REBOOT PHONE
Part Four On Your Phone:
1. Now /efs is mounted don't unmount it
2. Do a factory reset
3. Install your Jelly Bean rom
4. It should install without any errors
5. Boot your phone
6. If everything went well it should boot.
7. After it boots your signal notification most likely will be gray and internet or calls may not work
8. To fix just install gapps and it will be fixed
There you have it if everything went correctly your efs should be working good and you should be able to go back and do your normal rom flashing.
If jelly bean boots but you don't have phone do this:
1. Go back into recovery and get adb access.
2. su
3. mke2fs /dev/block/mmcblk0p3
4. mkdir /efs
5. mount -t ext4 /dev/block/mmcblk0p3 /efs
6. dd if=/sdcard/efs.img of=/dev/block/mmcblk0p3 bs=4096
And that should fix it and you should still be able to boot jelly bean and have no efs errors.
If you have any questions feel free to post down below in the comments
Please Help!
Got my Note2 back to life! Thanks bro
EDIT: Not exactly :\
I did get my IMEI back, but there's some problem with the factory mode and factory test apps with the stock tw rom.
I cant access the power menu nor the lockscreen.
I've tried to change the factorymode and keystr to ON in the efs/factoryapp folder, gave them the required permissions (744) and also changed the owner (1000.1000).
Still getting the two apps (factory mode and factory test) to FC on every boot and also this message if wifi is on during the boot.
the stock ROM that i've flashed is MC3.
And just to let you know, the phone works flawlessly on CM10.1 20130807 build which has LK6 baseband.
No power menu nor phone, Imei Ok
I have same behavior on my note 3. Can you tell me how got out this situation(no power menu nor phone).
Thanks
parthpatels007 said:
Got my Note2 back to life! Thanks bro
EDIT: Not exactly :\
I did get my IMEI back, but there's some problem with the factory mode and factory test apps with the stock tw rom.
I cant access the power menu nor the lockscreen.
I've tried to change the factorymode and keystr to ON in the efs/factoryapp folder, gave them the required permissions (744) and also changed the owner (1000.1000).
Still getting the two apps (factory mode and factory test) to FC on every boot and also this message if wifi is on during the boot.
the stock ROM that i've flashed is MC3.
And just to let you know, the phone works flawlessly on CM10.1 20130807 build which has LK6 baseband.
Click to expand...
Click to collapse
vit0r94 said:
I have same behavior on my note 3. Can you tell me how got out this situation(no power menu nor phone).
Thanks
Click to expand...
Click to collapse
I gave right permissions to all the files in the efs folder (almost gave all permissions '-rwrxr' ), and rebooted, and that's it!
parthpatels007 said:
I gave right permissions to all the files in the efs folder (almost gave all permissions '-rwrxr' ), and rebooted, and that's it!
Click to expand...
Click to collapse
Wow you are a good. It fix my issue. However if I have a correct efs backup, still my SGS3 i9300 not detect the IMEI. Don't know what is the reason.
Can't get it to work on my phone galaxy s2 i9100, i tried a number of times, doesn't matter what i do, i get a boot loop, tried 4 different roms , stock 4.1.2, custom 4.1.2, 4.4.2 and 5.0.2, i get the same result
worked, at the end, thanks
THANK YOU!
XylerSmith said:
After I flashed a couple roms I couldn't boot jelly bean anymore and I noticed the error in recovery: E:\ Cant Mount /efs, when installing. But I could still boot ICS but not jellybean. I still had my IMEI and could make calls but could not boot jelly bean because it couldn't mount.
How does this issue happen?
Sometimes when installing a rom something goes wrong and it changes the partition type of /efs making it unable to be mounted. The partition is usually from ext4 to swap.
Most likely this will work on your phone but if it doesn't and your phone stops working I am not responsible.
If your like me and you couldn't get jelly bean to work then flash your device back to ics and it should boot. Once your booted inside of ics we can start the process.
Pre-Setup:
1. Be rooted and have a custom recovery installed.
2. Be on Ics and it boots.
3. Your need to have a Jelly Bean rom like Cyanogenmod on your sdcard.
4. Have adb installed on your pc and usb debugging on in your phone/tab.
Now that that's done its time to start.
Part One:
1. Boot into recovery.
2. We need to find the efs block location.
3. Go to mounts and select efs
4. It should say unable to mount
5. Go to advance and make a recovery.log
6. Put that file on your computer and open it.
7. Look through the file and you should fine something like this around the beginning of the file:
E:Unable to mount '/efs'
I:Actual block device: '/dev/block/mmcblk0p3', current file system: 'swap'
My location is /dev/block/mmcblk0p3 But yours could be different! Most likely the difference will be instead of it ending with a 3 it will be a different number. I will be saying /dev/block/mmcblk0p3 if yours is different just change it to your location.
*WARNING* Sometimes when you copy paste into adb it will auto run the command without you pressing enter. If your location is different then mine and you copy past and it auto runs it could be BAD so to be careful if you want to copy past. Copy the command paste it into Google make the change and copy that and paste into adb
Part Two:
1. When your inside recovery connect your phone to your computer and get into a adb shell. (Sometimes it will take awhile for adb to recognize your device so be patient.)
2. Once you have adb access its time to start entering the commands.(Again my location may be different the yours! Most likely the difference will be instead of it ending with a 3 it will be a different number.
Part Three Inside ADB:
1. su
2. dd if=/dev/block/mmcblk0p3 of=/sdcard/efs.img
3. mke2fs /dev/block/mmcblk0p3
4. mkdir /efs
5. mount -t ext4 /dev/block/mmcblk0p3 /efs
DONT REBOOT PHONE
Part Four On Your Phone:
1. Now /efs is mounted don't unmount it
2. Do a factory reset
3. Install your Jelly Bean rom
4. It should install without any errors
5. Boot your phone
6. If everything went well it should boot.
7. After it boots your signal notification most likely will be gray and internet or calls may not work
8. To fix just install gapps and it will be fixed
There you have it if everything went correctly your efs should be working good and you should be able to go back and do your normal rom flashing.
If jelly bean boots but you don't have phone do this:
1. Go back into recovery and get adb access.
2. su
3. mke2fs /dev/block/mmcblk0p3
4. mkdir /efs
5. mount -t ext4 /dev/block/mmcblk0p3 /efs
6. dd if=/sdcard/efs.img of=/dev/block/mmcblk0p3 bs=4096
And that should fix it and you should still be able to boot jelly bean and have no efs errors.
If you have any questions feel free to post down below in the comments
Click to expand...
Click to collapse
Thanks so much!! This helped me out tons!
I installed [ROM] [4.4.2] CyanogenMod 11.0 from here
everything runs fine,but i cant write files to the internal storage.
For instance if i start the gallery app it tells me "No internal storage available",another app tells me it "cant write to the cache folder" because the sd is full,mounted,or write locked.Root explorer sees all the files but cant delete,move or copy/paste anything.
Apps that save/download files like podkicker or reddit act normal when trying to save the file but after the download starts the notification disapears and the file is simply not downloaded.Apps that stream content work fine,like youtube,or the stream feature of podkicker.
I have over 2gb free space so its not that,and if i plug into my pc i can move and delete files no problem.I like the rom and like i said everything else seems to work fine.
Thanks in advanced for any help.
I installed [ROM] [4.4.2] CyanogenMod 11.0 from here
everything runs fine,but i cant write files to the internal storage.
For instance if i start the gallery app it tells me "No internal storage available",another app tells me it "cant write to the cache folder" because the sd is full,mounted,or write locked.Root explorer sees all the files but cant delete,move or copy/paste anything.
Apps that save/download files like podkicker or reddit act normal when trying to save the file but after the download starts the notification disapears and the file is simply not downloaded.Apps that stream content work fine,like youtube,or the stream feature of podkicker.
I have over 2gb free space so its not that,and if i plug into my pc i can move and delete files no problem.I like the rom and like i said everything else seems to work fine.
Thanks in advanced for any help.
EDIT:
YAY i got it,
thanks stevemp and Quallenauge,a couple of the things needed to be a bit different though like the "# rm -rf data/*",and the push location line,heres what i did
Plug in the tablet with usb debugging enabled
run cmd and get adb going
type
adb shell
stop
rm -r data/*
mkdir data/local
mkdir data/media
exit
then push the rom file with [adb path]/adb push [rom path] /mnt/storage
when the push finished type adb reboot hold the volume down button and press enter
once rebooted into sde go to dev menu remove android kernel if necessary then choose flash kernel and initramfs
copy the files over
reboot
Everything seems to be working now i can read write files all day.
THANKS AGAIN!!
I'm having the same problem, with both CM11 and 10.2.0 on Verizon LG G2. Could it be a permissions problem?
lalalalas said:
I'm having the same problem, with both CM11 and 10.2.0 on Verizon LG G2. Could it be a permissions problem?
Click to expand...
Click to collapse
Its weird because i can write to the root directory but not any folders in it.Root explorer and es file manager say that its read only but neither will let me switch to read/write.
I made a logcat from boot[at least i think i made it rite,never had to do one before]
But i cant post the link because i dont have 10 posts just add this rpqjxGhG to pastebin
This all also happens with external sdcards as well it turns out,i just tried to make a new file with the built in file manager on the external sd and it said it requires elevated permissions,
root explorer just says file creation failed.
I also get constant "unfortunately,Trebuchet has stopped" messages when doing any thing.
I have also tried terminal emulator for kicks.
I gave it su then tried
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system]
didnt change a thing
then i tried
adb remount
this said error: device not found
Im pretty sure its not my tablet as i can can go back to stock/stock root and write files perfectly fine,ive also re-downloaded the rom twice just to make sure it wasnt bad,and ive probably flashed it around 20 time by now all with the same result.
I hope someone can figure something out.
leadtk said:
Its weird because i can write to the root directory but not any folders in it.Root explorer and es file manager say that its read only but neither will let me switch to read/write.
I made a logcat from boot[at least i think i made it rite,never had to do one before]
But i cant post the link because i dont have 10 posts just add this rpqjxGhG to pastebin
This all also happens with external sdcards as well it turns out,i just tried to make a new file with the built in file manager on the external sd and it said it requires elevated permissions,
root explorer just says file creation failed.
I also get constant "unfortunately,Trebuchet has stopped" messages when doing any thing.
I have also tried terminal emulator for kicks.
I gave it su then tried
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system]
didnt change a thing
then i tried
adb remount
this said error: device not found
Im pretty sure its not my tablet as i can can go back to stock/stock root and write files perfectly fine,ive also re-downloaded the rom twice just to make sure it wasnt bad,and ive probably flashed it around 20 time by now all with the same result.
I hope someone can figure something out.
Click to expand...
Click to collapse
When installing the CM11 firmware, did your format/reset your "android+storage" in "format device" recovery menu?
Storage files should be /mnt/sdcard/ (internal storage) and /mnt/media_rw/sdcard1/ (extern sdcard).
I'm able to create files in both directories as well on the file explorer.
If you want to "unlock" the root ( / ) partition you have to use this one inside the shell:
Code:
mount -o remount,rw /
but this don't have some effects to the mounted storage files.
Quallenauge said:
When installing the CM11 firmware, did your format/reset your "android+storage" in "format device" recovery menu?
Storage files should be /mnt/sdcard/ (internal storage) and /mnt/media_rw/sdcard1/ (extern sdcard).
I'm able to create files in both directories as well on the file explorer.
If you want to "unlock" the root ( / ) partition you have to use this one inside the shell:
Code:
mount -o remount,rw /
but this don't have some effects to the mounted storage files.
Click to expand...
Click to collapse
I was updating by putting the firmware file on the the device then rebooting and flashing the zimage and initramfs,
The reason being if i reset the "android+storage" dosnt that mean the firmware is deleted?
adb dose not see the tablet when its in recovery,it does see it when its on[am i doing something wrong there?],so i cant push the files,and if i export the data partition in windows a pop up and says it needs to be formatted before it can be used.so how am suppose to get the file to the device if i format everything?
leadtk said:
I was updating by putting the firmware file on the the device then rebooting and flashing the zimage and initramfs,
The reason being if i reset the "android+storage" dosnt that mean the firmware is deleted?
adb dose not see the tablet when its in recovery,it does see it when its on[am i doing something wrong there?],so i cant push the files,and if i export the data partition in windows a pop up and says it needs to be formatted before it can be used.so how am suppose to get the file to the device if i format everything?
Click to expand...
Click to collapse
From the guide, install using adb. http://forum.xda-developers.com/showthread.php?t=1871912
Originally Posted by surdu_petru
Installation : Now should be work on all devices Gen9 !!!
...connect USB cable to PC and ( you need to use a Rom with root access ) :
> adb shell
# stop
# rm -rf data/*
# mkdir data/local
# mkdir data/media
# exit
> adb push archos.ext4 /local/ ( need to wait about ~150 seconds ) !
> at the same time do : adb reboot & press and keep volume down ; in SDE -> DEM-> Remove Android Kernel ( if exist ) -> Flash Kernel & Initramfs -> copy here zImage & initramfs.cpio.gz -> OK -> wait to reboot !
Click to expand...
Click to collapse
If you are a Linux user. http://forum.xda-developers.com/showpost.php?p=48731942&postcount=1
YAY i got it,
thanks stevemp and Quallenauge,a couple of the things needed to be a bit different though like the "# rm -rf data/*",and the push location line,heres what i did
Plug in the tablet with usb debugging enabled
run cmd and get adb going
type
adb shell
stop
rm -r data/*
mkdir data/local
mkdir data/media
exit
then push the rom file with [adb path]/adb push [rom path] /mnt/storage
when the push finished type adb reboot hold the volume down button and press enter
once rebooted into sde go to dev menu remove android kernel if necessary then choose flash kernel and initramfs
copy the files over
reboot
Everything seems to be working now i can read write files all day.
THANKS AGAIN!!
leadtk said:
YAY i got it,
thanks stevemp and Quallenauge,a couple of the things needed to be a bit different though like the "# rm -rf data/*",and the push location line,heres what i did
Plug in the tablet with usb debugging enabled
run cmd and get adb going
type
adb shell
stop
rm -r data/*
mkdir data/local
mkdir data/media
exit
then push the rom file with [adb path]/adb push [rom path] /mnt/storage
when the push finished type adb reboot hold the volume down button and press enter
once rebooted into sde go to dev menu remove android kernel if necessary then choose flash kernel and initramfs
copy the files over
reboot
Everything seems to be working now i can read write files all day.
THANKS AGAIN!!
Click to expand...
Click to collapse
I do not know what i am doing wrong but when i type adb shell ..all i get is BUSYBOX v1.7.2 (2012-10-19 CEST) built in shell (ash) Enter help for a list of built in commands ...
I did have ics blue v04 rom on my tablet that i was trying to go from to 4.4.2 ..
I did this before and had the write problem . any help you can give would be appreciated