Related
OK, I made a zip. Who wants to be my guinea pig? It's at the bottom of the post. (erase -signed and put it on the internal sd)
blackjackboy said:
I guess my idea would be to take the settings.apk from either the Vibrant dump or cyanogenmod 5.0 and push it to /system/app or wherever the settings.apk is located. Does anyone think that this would work or be willing to try it? I'm just worried that this will brick the touchwiz, and without an "original ROM" or RUU and custom recovery, I'm afraid to try it. Is there anyone braver than me?
Click to expand...
Click to collapse
Did you check this thread?
http://forum.xda-developers.com/showthread.php?t=728121
tbae2 said:
Did you check this thread?
http://forum.xda-developers.com/showthread.php?t=728121
Click to expand...
Click to collapse
The thing is, root explorer isn't free. I want to give people an easy, free solution (maybe flashing something from recovery?). For now, ADB will work for me, but in the future I want to provide something flashable from recovery.
Well, the best thing to do, simply run a sql command along with the rooting update.zip.
I will work on this today and get back to you guys soon.
http://androidforums.com/samsung-ca...e-sideloading-apps-captivate.html#post1178618
Been done.
blackjackboy said:
The thing is, root explorer isn't free. I want to give people an easy, free solution (maybe flashing something from recovery?). For now, ADB will work for me, but in the future I want to provide something flashable from recovery.
Click to expand...
Click to collapse
It isn't free but it isn't expensive either. You just dropped a large wad of cash for the phone, seems like another $3 to get it the way you want it wouldn't be such a big deal.
blackjackboy said:
The thing is, root explorer isn't free. I want to give people an easy, free solution (maybe flashing something from recovery?). For now, ADB will work for me, but in the future I want to provide something flashable from recovery.
Click to expand...
Click to collapse
Droid Explorer is.
I'm an android noob but experienced linux user, so I came up with my own free solution: download a terminal emulator app (the one i got was free, and called, simply, Terminal Emulator, I think).
Then (in the terminal emulator):
Copy the settings.db file to the SD card:
To get superuser access so you can get to the settings.db file (need a rooted phone, obv):
Code:
$su
And confirm the popup allowing access.
Code:
#busybox cp /dbdata/databases/com.android.providers.settings/settings.db /sdcard/settings.db
Then hook up your phone via USB (mass storage method) and use your window manager to copy that from the phone to the computer, edit with an SQL database browser, save it, verify it's still good, move it back to the SD card, then, back on the phone in the terminal emulator:
To get superuser access again:
Code:
$su
Shouldn't have to confirm the popup allowing access again, as the first time appears to do it.
Move the original file to a backup name (just to be safe):
Code:
#busybox mv /dbdata/databases/com.android.providers.settings/settings.db /dbdata/databases/com.android.providers.settings/settings.db.old
Copy the new (edited) file into place:
Code:
#busybox cp /sdcard/settings.db /dbdata/databases/com.android.providers.settings/settings.db
Then reboot, and enjoy the ability to install non-market apps. My first install was Flash 10.1. Works fine on the Captivate.
blackjackboy said:
The thing is, root explorer isn't free. I want to give people an easy, free solution (maybe flashing something from recovery?). For now, ADB will work for me, but in the future I want to provide something flashable from recovery.
Click to expand...
Click to collapse
Grab Android Mate from the market, it is free and has root level exploration
blackjackboy said:
OK, I made a zip. Who wants to be my guinea pig? It's at the bottom of the post. (erase -signed and put it on the internal sd)
Click to expand...
Click to collapse
This might also work, I have used it, pretty simple
http://m.androidcentral.com/sideload-android-apps-all-you-want-sideload-wonder-machine
Superoneclickroot has a one click enable non market apps next to the root button, fyi.
terrymc said:
This might also work, I have used it, pretty simple
http://m.androidcentral.com/sideload-android-apps-all-you-want-sideload-wonder-machine
Click to expand...
Click to collapse
Smasher816 said:
Superoneclickroot has a one click enable non market apps next to the root button, fyi.
Click to expand...
Click to collapse
:faceplam:
bump a year old thread? with these no less....
whats wrong with bumping a (insert # here) old thread? it hasnt been closed or deleted. as long as info pertaining to the OP is being posted shouldnt it be a non-issue? now if it was bumped with something like 'why bump this fossil thread?' then that would be a pointless bump. i gained info from the 1 year late post about superoneclick and thanked the guy for posting it.
EDIT: you spelled 'facepalm' wrong.
Well first it shouldn't even be here in development. And second thread closed.
Debian for Desire.
If you are able to try this on another android device, please do as I will be very interested in the results.
Download
http://www.multiupload.com/79TSI1AAF9
You will need.
-Root access.
-Busybox (included in most custom roms)
-1.4gig free on SDCARD
-VNC Client (ie. AndroidVNC)
-Terminal Emulator (ie. ConnectBot)
-7zip
Instructions
-Extract the file deSIREbian.7z on your PC using 7zip.
-Copy the contents (debian.img and deboot) to root directory of SDCARD.
-On your phone in terminal emulator type
su
sh /sdcard/deboot
Click to expand...
Click to collapse
You should get a blank screen showing "localhost:/#" after a couple of seconds.
-On your phone in your VNC client log in using these details
Password - password
Port - 5901
Click to expand...
Click to collapse
Nickname and Address are not needed, call it what you want though.
Changing the colour to 24bit and enabling local mouse pointer and full screen bit map are not neccesary but reccomended.
-Thats it.
Notes.
-You can log in via ssh, (gives a much better terminal, ie works properly with aptitude). Use [email protected] and password "toor"
-The version of Debian is Armel Lenny, installed using debootstrap.
-It is just the base package with LXDE on top, you only get a desktop, a file browser, an internet browser, and a pic viewer.
-If you want more packages there's tonnes of room on the image. eg apt-get install openoffice.org or apt-get install abiword or apt-get install any flipping thing u want
-You can access the SDCARD from Debian at "root/sdcard" (read-write)
-You can access Debian filesystem from Android (When Debian is running) at "sdcard/debian" (read only)
-debian.img is mounted at "sdcard/debian" using "dev/block/loop5"
-So far the only rom i have come accross that this dont work with is one of the cyanogen nightlies from last week. apart from that, working on opendesire, cyanogen, defrost, leedroid, official 2.2 with busybox...
Issues.
Debian cannot be shut down. You need to reboot the phone to do this. (You can kill the VNC server with "vncserver -kill :1" there is an icon on the festoons to do this.)
Update log.
deSIREbain.
-First release.
deSIREbain2
Fixed
-Loading a second terminal no longer breaks vnc.
-You no longer need to create the folder debian on sdcard.
Added
-ssh server (login with root and toor)
Removed.
-The image has been downsized from 2 gig to 1.4
Hey,
thank you for your work, i will test it so far and will tell you the results
got this error:
Code:
# su
su
# sh /sdcard/deboot
sh /sdcard/deboot
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
mount: mounting /sdcard on /sdcard/debian/root/sdcard failed: No such file or di
rectory
net.ipv4.ip_forward = 1
chroot: can't change root directory to /sdcard/debian: No such file or directory
#
If you have the same problems try out
su
mkdir /sdcard/debian
losetup /dev/block/loop3 /sdcard/debian.img
mount -t ext2 /dev/block/loop3 /sdcard/debian
ls /sdcard/debian
thx to mercianary for help
greetings
I found this guide quite helpful at getting a bootstrapped Debian setup running.
http://www.saurik.com/id/10
I didn't need to insert the ext2 module as it's already loaded for me, I guess G1s didn't have that convenience back then.
blackstoneuser5 said:
I found this guide quite helpful at getting a bootstrapped Debian setup running.
www . saurik.com/id/10
I didn't need to insert the ext2 module as it's already loaded for me, I guess G1s didn't have that convenience back then.
Click to expand...
Click to collapse
I used parts of this for reference too. Its a great guide, explains things really well.
i've just updated this. link is in the first post.
Fixed
-Loading a second terminal no longer breaks vnc.
-You no longer need to create the folder debian on sdcard.
Added
-ssh server (login with root and toor)
Removed.
-The image has been downsized from 2 gig to 1.4
debian for desire--help please
hi
I spent much time for searching debian or ubuntu for desire, but nothin worked
know i found this and i have download everything and start to install over the terminal
but the " sh /sdcard/deboot" is not workin to
there's only this answer:
# su
su
# sh /sdcard/deboot
sh /sdcard/deboot
[: not found
losetup: not found
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
busybox: not found
sysctl: not found
chroot: not found
may somebody help me?
i really want to have it on the desire
thanks
It looks like you had not installed busybox
Which ROM do you use ?
oh i'm sorry
i'm a newbie and don't really know what a rom is
but i had problems with busybox and there was a somebody who said i can get the app titanium and let it install the busybox
could you please show me a tut how to install busybox
maybe a german tut
thanks
Getting error at: sh /sdcard/deboot
line 5: syntax error near unexpected token `else'
Rosi1337 said:
Getting error at: sh /sdcard/deboot
line 5: syntax error near unexpected token `else'
Click to expand...
Click to collapse
dont know why that happened.. works on mine. syntax looks ok to me.
try with this one (attatched), it's the same but without the bit that's not working for you.
what rom are you using, i shall try to replicate the error so I can try to fix properly.
thepuechen said:
could you please show me a tut how to install busybox
maybe a german tut
thanks
Click to expand...
Click to collapse
There should be a guide on installing busybox somewhere if you want to search for it, i know i remember seeing one a while ago.
Too be honest, your better off just flashing a rom that includes busybox, it would be MUCH easier.
have a look here and see what takes your fancy, I would recomend defrost, because it is stable and easy to overclock.
Thanks mercianary,
It works fine!,
I use customised DeFroST_0.9b_uvonly with USB-host patch.
By the way I would like to add more options to kernel line.
Where can I find like a menu.lst file ? or How to add it to kernel line.
There is no /dev/graphics/* in running Debian console.
I would like to use FrameBuffer on running Debian.
thanks,
Android VNC won't connect Trying to get a handshake, but then says that VNC connection failed
please paste at that time log
jacobtc said:
Android VNC won't connect Trying to get a handshake, but then says that VNC connection failed
Click to expand...
Click to collapse
Please paste at that time log.
Maybe vnc server does not running.
tknv said:
Thanks mercianary,
It works fine!,
I use customised DeFroST_0.9b_uvonly with USB-host patch.
By the way I would like to add more options to kernel line.
Where can I find like a menu.lst file ? or How to add it to kernel line.
There is no /dev/graphics/* in running Debian console.
I would like to use FrameBuffer on running Debian.
thanks,
Click to expand...
Click to collapse
You should understand that this is not a really booted native linux. Instead you are working in a chroot environment. So there is no kernel running that can get parameters. Only the the stock kernel of your DeFroST. Also there is no FrameBuffer as the graphic hardware ist not accessible. Instead this approach uses a vnc-server to which you can connect via a local viewer.
The advantage of this approach is clear:
- run almost any linux package available in the debian repository
- use your phone as before with the nice android
The disadvantage:
- no graphic output, so no 3D-games (which are rare under linux on the arm platform ;-)
- you can crash your android by eating up to much ram (not such a problem - it restarts on its own and if not you just have to reboot)
Thread is dead?
It seems this thread is dead. The problems many users seem to have come from a dirty setup. The image is broken in many terms:
- wrong file permissions on important binaries, like su
- wrong file permissions on many device files under /dev, so the ttys are only accessible by root
- wrong permissions on other places so there are always errors when installing additonal software (e.g. with the man pages)
- wrong setup that uses the root user for the desktop - instead an unprivileged user should be used
- missing packages for timezones and locales so the time is only right, if you are in a UTC region and console programs having trouble displaying anything else then plain english
I can not recommend using this setup image. It is better to use one of the instructions available online to get a clean setup.
Su doesn't work because your allready root.
Getting anything but root to work would be a real pain.
As you said its a chroot environment, its never going to be perfect.
The image was made using debootstrap just like all the other 'clean' ones.
Yep, it is broken as hell, but it works for what most people would need it for...make,gcc,python,a proper web browser,torrents, and some emergency word processing on the train to work.
The problem most people have is not being able to mount the image, this is due to fro-yo a2sd taking up all the loop devices.
Just thought I'd add my 2 cents.
I tried this on a MIUI rom and the scripy didnt do anything - ie i ran it using:
"# sh /sdcard/deboot"
.....and all it said was:
"#"
I entered all the lines in the shell script but the last one said it failed to launch VLC and no commands registered property (not even ls)
So i tried it on Defrost 5.1, and the script still didn't work.
But when i entered everything manually, it did work. Not too sure about the green theme though.
But thanks alot! Saves me spending a few hours trying to coax a working debootstrap out of my computer.
Thanks!
Josh.
mercianary said:
Su doesn't work because your allready root.
Click to expand...
Click to collapse
Nope. Actually su works only for root. It's missing the setuid root flag like all other binaries that should have it set.
mercianary said:
Getting anything but root to work would be a real pain.
Click to expand...
Click to collapse
Nope. I am always working as a normal, unprivileged user in my chroot. You just have to be in the proper groups. No need to work as root. Android works also with an unprivileged user.
mercianary said:
As you said its a chroot environment, its never going to be perfect.
The image was made using debootstrap just like all the other 'clean' ones.
Yep, it is broken as hell, but it works for what most people would need it for...make,gcc,python,a proper web browser,torrents, and some emergency word processing on the train to work.
Click to expand...
Click to collapse
This is what I do not understand. There is no need that it is broken, as mine works without any errors. So I think something went wrong in creating yours. For sure a chroot is no running OS but you can server almost any service with it and run anything you want (if your ram does not get exhausted ;-).
mercianary said:
The problem most people have is not being able to mount the image, this is due to fro-yo a2sd taking up all the loop devices.
Click to expand...
Click to collapse
Yes. Everyone with a good rom should have a2sd+ (aka the old a2sd) which saves more space than the froyo one and leaves your loop devices for you.
jo
Hey guys, need some help with this one from some of you with more android/linux experience than me.
In my continuing quest to make Blackhole as customizable as possible I've been working on a way for users to easily install paid apps (legally downloaded of course), and stuff that I don't have available in rom manager in one easy step at the same time the rom is installed. In pursuit of this goal I've found that it's possible for the update-script file inside a clockworkmod zip to call a script in the zip as well. I've gotten it to say it's run the script, but it doesn't do what it's supposed to. here's what i've got:
#! /bin/
busybox cp /sdcard/app/* /system/app/
When I type the command into a terminal on the phone it works. When I open an adb shell and type "bash install.sh" it works. But when I get the update.zip to run the script, or run it in root explorer it just says it's run it, but doesn't do anything.
Is there something I'm missing about how to call the script? Do I need to somehow add the bash program to the zip file so it can run the script right? Has anyone ever done something like this who can point me in the right direction?
do you have an output you can show us?
Sent from my SCH-I500 using XDA App
This is a shot in the dark but does writing to /system/app require root permissions? It could be that you've given your terminal app root, so it runs under su. But when the script is being executed it does not have root and fails, but perhaps the output is being held back a bit and you're not seeing the permission denied.
Steve_ ?!
whoa, didn't expect it to be you of all people
Anyhoo, this is a bit off topic, but I've got a small request, can you somehow make BlackHole 2.4 an option on Rom manager? I don't have DL09 so I can't use 3.0, but I really like the ability to select everything to customize, instead of me going and installing one thing at a time....
Why not just add the following to the end of the update-script:
Code:
copy_dir /sdcard/app SYSTEM:
Also, is the SDCard mounted by default when the phone boots to recovery? If it isn't, or it isn't mounted while the update is processing, that will also cause the problem.
wizang said:
This is a shot in the dark but does writing to /system/app require root permissions? It could be that you've given your terminal app root, so it runs under su. But when the script is being executed it does not have root and fails, but perhaps the output is being held back a bit and you're not seeing the permission denied.
Click to expand...
Click to collapse
Could very well be, it's not showing me any output when i run it the two ways it doesn't work, just says it's been run.
vegittoss15 said:
Steve_ ?!
whoa, didn't expect it to be you of all people
Anyhoo, this is a bit off topic, but I've got a small request, can you somehow make BlackHole 2.4 an option on Rom manager? I don't have DL09 so I can't use 3.0, but I really like the ability to select everything to customize, instead of me going and installing one thing at a time....
Click to expand...
Click to collapse
Haha, caught me. I was trying to remain incognito Yeah, i'll get 2.4 loaded back up on rom manager for you today. But if you flash 3.0 it will upgrade you to DL09 and the DJ05 kernels and modem are compatible, or at least no one i know of has had issues.
imnuts said:
Why not just add the following to the end of the update-script:
Code:
copy_dir /sdcard/app SYSTEM:
Also, is the SDCard mounted by default when the phone boots to recovery? If it isn't, or it isn't mounted while the update is processing, that will also cause the problem.
Click to expand...
Click to collapse
sdcard is mounted when you go to recovery, because it's got to access the update.zip file on it to install anything. I'll try your code, do you know what to put after SYSTEM: to make it go to the /app directory? thanks for the idea, it's a different way to go, i didn't think about the fact the update-script could access the device if you don't use the "package" tag.
Don't you need to add "sh" to the bin directory and define the script as so:
#! /bin/sh
if you want it to execute properly..
dcow90 said:
Don't you need to add "sh" to the bin directory and define the script as so:
#! /bin/sh
if you want it to execute properly..
Click to expand...
Click to collapse
normally yes, but there doesn't seem to be a /bin/sh directory on my fascinate, only /bin and that's where the cp and mv and cat, etc. are.
I made a script to do this forever ago on my G1 when it first came out... Let me see if I can find it.
This has been done lots of times before. If you look around on xda there are some backup scripts which do the same thing.
Sent from my SCH-I500
imnuts said:
Why not just add the following to the end of the update-script:
Code:
copy_dir /sdcard/app SYSTEM:
Also, is the SDCard mounted by default when the phone boots to recovery? If it isn't, or it isn't mounted while the update is processing, that will also cause the problem.
Click to expand...
Click to collapse
Well I gave that a shot, and i think it could work, but the recovery wouldnt do it. it says "non-package source path not yet supported" good idea tho.
yutsoku said:
I made a script to do this forever ago on my G1 when it first came out... Let me see if I can find it.
Click to expand...
Click to collapse
If you can that would be great.
n0yd said:
This has been done lots of times before. If you look around on xda there are some backup scripts which do the same thing.
Sent from my SCH-I500
Click to expand...
Click to collapse
I spent a good bit of time searching and most of the scripts I found were much more complex than what i need, or were written to run on a computer, which i've already done.
sonofskywalker3 said:
normally yes, but there doesn't seem to be a /bin/sh directory on my fascinate, only /bin and that's where the cp and mv and cat, etc. are.
Click to expand...
Click to collapse
Thats not the point. You need to set a shell interpreter, not a path. Cwm uses busybox sh, which is in /bin in recovery mode. Google search shebang
Sent from my SCH-I500 using XDA App
jt1134 said:
Thats not the point. You need to set a shell interpreter, not a path. Cwm uses busybox sh, which is in /bin in recovery mode. Google search shebang
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Going to go ahead and parade my stupidity in front of everyone here:
so does that mean i'm right using #! /bin/ or that it should be #! /bin/sh/ or something else entirely? I'm so confused.
sonofskywalker3 said:
Going to go ahead and parade my stupidity in front of everyone here:
so does that mean i'm right using #! /bin/ or that it should be #! /bin/sh/ or something else entirely? I'm so confused.
Click to expand...
Click to collapse
#!/bin/sh for scripts in recovery. #!/system/bin/sh for scripts in android.
Sent from my SCH-I500 using XDA App
I figured since getting a replacement A500 and updating to Acer_A500_1.139.04_COM_GEN1 I would update this post with the images.
System.img - http://www.fileserve.com/file/gvemmYd
Flexrom.img - http://www.fileserve.com/file/Suq5yBG
Boot.img - http://www.fileserve.com/file/sSjqpME
Hope this helps anyone.
Kernel Information: Linux localhost 2.6.36.3 #1 SMP PREEMPT Wed May 11 22:11:55 CST 2011 armv7l GNU/Linux
103 views and no-one is able to do it? I am sure there are quite a few Aussies on this forum. :-(
i would if i knew how
splinter6 said:
i would if i knew how
Click to expand...
Click to collapse
Here is your "knew how"... jejeje
You have to ROOT your A500 first... then use terminal emulator and type SU (this will give it Super User Access) then use the following commands:
dd if=/dev/block/mmcblk0p3 of=/sdcard/system.img
dd if=/dev/block/mmcblk0p6 of=/sdcard/flexrom.img
This will give you the actual system image (first command)
Second command gives you the partition where the update information is located.
Let me know if you need help rooting, its really easy, just remember to have your tablet in PORTRAIT not landscape or Gingerbreak will FORCE CLOSE!!!
Hope this helps... jejeje
I got a replacement A500 from JB HiFi. I will update to Acer_A500_1.139.04_COM_GEN1 then create a system.img.
This would be much appreciated! I'm in Australia, and having some issues too. Thanks again.
koprofile said:
This would be much appreciated! I'm in Australia, and having some issues too. Thanks again.
Click to expand...
Click to collapse
I'm at work today. Will hopefully get the system.img uploaded this evening, should take ~2 hours being 600MB and all. :-(
I'm not sure if the flexrom.img is needed though.
that would be appreciated as i have an issue of not being able to update after rooting and NO BACKUP
eliousneo said:
that would be appreciated as i have an issue of not being able to update after rooting and NO BACKUP
Click to expand...
Click to collapse
Here is the untouched Acer_A500_1.139.04_COM_GEN1 system.img.
http://www.fileserve.com/file/gvemmYd
thank you really appreciate it...
question 2 im a noob to all this so could you please let me know how ot install is
i know that it may sound like a dumb question but i have not got a clue.
I only rooted my a500 to be able to install apps to sd and that was a dissapointing move otherwise i think i may keep it stock from now on
thanking you in advance
eliousneo said:
thank you really appreciate it...
question 2 im a noob to all this so could you please let me know how ot install is
i know that it may sound like a dumb question but i have not got a clue.
Click to expand...
Click to collapse
You should be able to just copy the image onto your A500 and run the following as root: dd if=/dev/block/system-1.139.04.img of=/sdcard/mmcblk0p3
Be careful though, I honestly haven't tested the image but it should be fine.
Sent from my A500 using Tapatalk
so that means use command line and copy image onto SD card?
Sounds simple enough just gotta wait for 8 hours for download
Than again juzman very helpfull
Juzman said:
You should be able to just copy the image onto your A500 and run the following as root: dd if=/dev/block/system-1.139.04.img of=/sdcard/mmcblk0p3
Be careful though, I honestly haven't tested the image but it should be fine.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
We ALL should start using the MD5 checksum to rule out corrupted file size produced by online downloading
UnicornKaz said:
We ALL should start using the MD5 checksum to rule out corrupted file size produced by online downloading
Click to expand...
Click to collapse
I used the fsum utility on Windows and believe I created an MD5 checksum: 3A0AF183D5E582CBEA1D1F6BC7A61EA6
Will we need the flexrom as well when flashing this system image?
Also, this thread contains some original kernel modules: http://forum.xda-developers.com/showpost.php?p=13974214&postcount=62
Will the modules linked there be compatible with this current AU system image in the event of gps/wifi issues?
Thanks again!
Juzman said:
I used the fsum utility on Windows and believe I created an MD5 checksum: 3A0AF183D5E582CBEA1D1F6BC7A61EA6
Click to expand...
Click to collapse
Is that definitely the correct md5 checksum? I've downloaded the file twice and both times I get an md5 of 850d68aac56169b211a4913de7e4e8e9
Can anyone else confirm?
mapaz04 said:
Here is your "knew how"... jejeje
You have to ROOT your A500 first... then use terminal emulator and type SU (this will give it Super User Access) then use the following commands:
dd if=/dev/block/mmcblk0p3 of=/sdcard/system.img
dd if=/dev/block/mmcblk0p6 of=/sdcard/flexrom.img
This will give you the actual system image (first command)
Second command gives you the partition where the update information is located.
Let me know if you need help rooting, its really easy, just remember to have your tablet in PORTRAIT not landscape or Gingerbreak will FORCE CLOSE!!!
Hope this helps... jejeje
Click to expand...
Click to collapse
Can you say what terminal emulator to use or which is the best one to use?
urdaddi said:
Can you say what terminal emulator to use or which is the best one to use?
Click to expand...
Click to collapse
I used Better Terminal Emulator (with the extensions installed). Make sure after installing the extensions (after the prompt) to go into options, select root by default, then type exit (or CTRL-D) to close the terminal so it reinitializes with all the extensions (the icon on the taskbar must be gone). Afterwards do your stuff. After flashing the system.img the tablet might reboot (show the android boot logo) and cycle. Just power down holding the button long enough, and power back on, then flash the other img.
Hi Me again
dd if=/sdcard/system.img of=/dev/block/mmcblk0p3
I did the above thingy and it just extracted mmcblk0p3 into sdcard
How do i install it ??
i cant just run it so i presume there is some kind of command or something in terminal?
Is it possible to get the flexrom too?
Thanks
<RESOLVED> [HELP]N7100_IMEI 0049xx_SN 0000.._Service State "out of service"
Hi Guys. I got this issue after upgrading my Note II to the latest OMEGA ROM v17. After doing the upgrade I was able to use it for a couple of hours and then I realized though there is a signal I am not receiving any internet data (internet icon was gone). I restarted the phone, switch to flight mode back and forth, switch on/off data, but still no luck. I soon realized also that I am not receiving any SMS or call. I thought it was just my carrier so I called them and made a complaint like hell. They said that my line should be fine. From there I started reading for all possible reasons why I am getting this issue. I then found out that my IMEI that is showing on the phone is different on the sticker attached on the battery compartment. Serial number on the phone is 000000000. Service state is "Out of service" though it detects from which network my SIM is. I have tried to flash different custom ROMs and several stock ROMs, but with no go. Tried also different methods on restoring EFS and still no luck. Stupid me, I don't have any backup EFS file or a copy of a nand backup. I was able to get out of the factory mode, wifi and everything else are working except for not receiving any call or SMS because of the bad IMEI, SN, and the Service state "Out of service". I have read some fixes on other threads from a different android phones, but with no avail in fixing mine. I know there's a lot of thread of the same issue, but I want to create my own so I can make sure that people who got ideas on how to fix this is just referring to my "own" issue which will be easier for me to monitor the thread.
So I have tried the following:
- flashed different custom ROMs - no good
- flashed several stock ROMs - no good
- tried EFS Professional.exe - no good
- tried N7100_EFS_Backup_Restore_WIN - no good
- tried ARIZAPatch.apk - no good
- tried SGS tools - no good
- tried com.helroz.GSII_Repair_102.apk - no good
- tried NV-items_reader_writer.exe - I don't know how to make it work
- restored old EFS Backup - no good
- able to find an old NANDroid backup (when it was still working before), flashed it - no good
They say helps the modem from the topic http://forum.xda-developers.com/showthread.php?t=2333216
### --- XXDME4 modem --- ### fix IMEI - -unknown modem
on the XXDME6 base - you can not install old modems,
because it will cause for unknown modem & imei status.
Solution flash - XXDME4 modem
XXDME4 modem
flash via TWRP / CWM
ATTACHED FILES
modem XXDME4 .zip - [Click for QR Code] (4.84 MB, 1209 views)
Click to expand...
Click to collapse
tried that still no go
red_hanks said:
...
Click to expand...
Click to collapse
Read this
victorator said:
Read this
Click to expand...
Click to collapse
Tried that mate but no luck.
in /efs folder contains files *.bak?
aaleo said:
in /efs folder contains files *.bak?
Click to expand...
Click to collapse
yup
move the following files in a backup folder somewhere to your internal SD card
.nv_core.bak,
.nv_core.bak.md5,
.nv_data.bak,
.nv_data.bak.md5,
nv_data.bin,
nv_data.bin.md5
moving them they will be deleted from the efs folder
Reboot.
Now you will have the generic IMEI.
aaleo said:
move the following files in a backup folder somewhere to your internal SD card
.nv_core.bak,
.nv_core.bak.md5,
.nv_data.bak,
.nv_data.bak.md5,
nv_data.bin,
nv_data.bin.md5
moving them they will be deleted from the efs folder
Reboot.
Now you will have the generic IMEI.
Click to expand...
Click to collapse
I have tried that method but it just made my note2 switch to factory mode. Sorry to ask but have you tried that method on your own or you just copy pasted that from somewhere showing that you're willing to help but no certainty if that really works or will just mess up something?
I did it. I did not have IMEI (0000000000) I think you can help it. The last thing that comes to mind to flash the original firmware from sammobile.com through odin.
---------- Post added at 04:39 PM ---------- Previous post was at 04:23 PM ----------
You can restore files via adb
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p3 /efs
cp /mnt/sdcard/.nv_core.bak /efs/.nv_core.bak
cp /mnt/sdcard/.nv_core.bak.md5 /efs/.nv_core.bak.md5
cp /mnt/sdcard/.nv_data.bak /efs/.nv_data.bak
cp /mnt/sdcard/.nv_data.bak.md5 /efs/.nv_data.bak.md5
cp /mnt/sdcard/nv_data.bin /efs/nv_data.bin
cp /mnt/sdcard/nv_data.bin.md5 /efs/nv_data.bin.md5
aaleo said:
I did it. I did not have IMEI (0000000000) I think you can help it. The last thing that comes to mind to flash the original firmware from sammobile.com through odin.
---------- Post added at 04:39 PM ---------- Previous post was at 04:23 PM ----------
You can restore files via adb
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p3 /efs
cp /mnt/sdcard/.nv_core.bak /efs/.nv_core.bak
cp /mnt/sdcard/.nv_core.bak.md5 /efs/.nv_core.bak.md5
cp /mnt/sdcard/.nv_data.bak /efs/.nv_data.bak
cp /mnt/sdcard/.nv_data.bak.md5 /efs/.nv_data.bak.md5
cp /mnt/sdcard/nv_data.bin /efs/nv_data.bin
cp /mnt/sdcard/nv_data.bin.md5 /efs/nv_data.bin.md5
Click to expand...
Click to collapse
Just tried original firmware but same thing. I am getting frustrated now..
Stupid idea. Maybe it's in the sim card is broken. There is another test for?
aaleo said:
Stupid idea. Maybe it's in the sim card is broken. There is another test for?
Click to expand...
Click to collapse
SIM card is ok. Read my explanation on post #1.
Was able to find an old EFS backup of mine dated January 2013. Tried to restore it but still same issues.
red_hanks said:
Was able to find an old EFS backup of mine dated January 2013. Tried to restore it but still same issues.
Click to expand...
Click to collapse
Read this: http://forum.xda-developers.com/showthread.php?t=2332913
The Stability update on which is based the rom has some changes in the kernel and the efs folder. Maybe that thread can help you out....hope it does....:good:
red_hanks said:
Tried that mate but no luck.
Click to expand...
Click to collapse
Just wondering, did you tried Kies Emergency restore???
Sent from my GT-N7100 using xda premium
find someone who has a SGN2 ,back up the image of efs partition 20mb , open it with a compiler on your pc, change the IMEI to same as yours on the box , recompile and restore.
hagba said:
find someone who has a SGN2 ,back up the image of efs partition 20mb , open it with a compiler on your pc, change the IMEI to same as yours on the box , recompile and restore.
Click to expand...
Click to collapse
Wow sounds complicated lol hope this don't happen to me!
Sent from my GT-N7100 using xda app-developers app
glevitan said:
Read this: http://forum.xda-developers.com/showthread.php?t=2332913
The Stability update on which is based the rom has some changes in the kernel and the efs folder. Maybe that thread can help you out....hope it does....:good:
Click to expand...
Click to collapse
Done with this with no luck.
aspot72 said:
Just wondering, did you tried Kies Emergency restore???
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Not sure how to do that, never use Kies before
hagba said:
find someone who has a SGN2 ,back up the image of efs partition 20mb , open it with a compiler on your pc, change the IMEI to same as yours on the box , recompile and restore.
Click to expand...
Click to collapse
Like what I have said, found an old backup of mine and it doesn't work. So it's pointless to try this.
I was sleepless (haha) trying to find solution for this. I came across this site and tried the app there. But as you can see on the image below, the button to change the IMEI is grayed out. There is not clear instructions on the site so it is kinda hard what to do in times like that. The app might be for a specific device but if it recognized the IMEI on my phone then it should be able to change it.