Good afternoon friends, my case is the following superoneclickv2.1.1 rootee my team and follow a post on taringa release but after following all the steps to restart just started, I am in flight mode and does not recognize samsung kies
You can do to solve the problem ... and excuse my carelessness and ignorance
mkr09 said:
Good afternoon friends, my case is the following superoneclickv2.1.1 rootee my team and follow a post on taringa release but after following all the steps to restart just started, I am in flight mode and does not recognize samsung kies
You can do to solve the problem ... and excuse my carelessness and ignorance
Click to expand...
Click to collapse
So you only rooted? Did you do anything else?
Sent from my GT-I5500 using Tapatalk
post reply
Jordanooo said:
So you only rooted? Did you do anything else?
Sent from my GT-I5500 using Tapatalk
Click to expand...
Click to collapse
I did all this:
Steps 1 and 2 do not chip.
1 - First we have to root the phone.
For this we will use ftp://shortfuse.org/SuperOneClick/Packages/SuperOneClickv2.1.1-ShortFuse.zip SuperOneClick
and the superOneClick unzip OneClick is a folder called ADB is copied to the root directory or C:
2 - Within SuperOneClick files windows open a console (Start> Run> cmd) and
cd wrote .. twice and then, cd adb, then enter the following
adb shell-
- its
- Cd /
- Mount-o remount, rw-t rootfs rootfs /
- Mkdir / efs
- Mount-o nosuid, ro, nodev-t vfat / dev/block/stl5 / efs
- Cat / efs / mits / perso.txt
Write the code 8 digits
- Umount / efs
That was all I did just as indicated
You unlocked your phone using a very dangerous method. Some phones can be broken by unlocking through your stl5.
I find it difficult to understand your post. Is your phone broken? Or are you only concerned about Samsung KIES?
Yeah, quite a bad way to unlock. Could you explain more what is wrong?
Sent from my GT-I5500 using Tapatalk
original
mkr09 said:
I did all this:
Steps 1 and 2 do not chip.
1 - First we have to root the phone.
For this we will use ftp://shortfuse.org/SuperOneClick/Packages/SuperOneClickv2.1.1-ShortFuse.zip SuperOneClick
and the superOneClick unzip OneClick is a folder called ADB is copied to the root directory or C:
2 - Within SuperOneClick files windows open a console (Start> Run> cmd) and
cd wrote .. twice and then, cd adb, then enter the following
adb shell-
- its
- Cd /
- Mount-o remount, rw-t rootfs rootfs /
- Mkdir / efs
- Mount-o nosuid, ro, nodev-t vfat / dev/block/stl5 / efs
- Cat / efs / mits / perso.txt
Write the code 8 digits
- Umount / efs
That was all I did just as indicated
Click to expand...
Click to collapse
I'm worried because I can use my sim card in my phone and my phone is restarted at all times, no imei and is in airplane mode (flight mode
that I can suggest?
ThinksAmoral said:
You unlocked your phone using a very dangerous method. Some phones can be broken by unlocking through your stl5.
I find it difficult to understand your post. Is your phone broken? Or are you only concerned about Samsung KIES?
Click to expand...
Click to collapse
I'm worried because I can use my sim card in my phone and my phone is restarted at all times, no imei and is in airplane mode (flight mode
that I can suggest?
jordanooo
Jordanooo said:
Yeah, quite a bad way to unlock. Could you explain more what is wrong?
Sent from my GT-I5500 using Tapatalk
Click to expand...
Click to collapse
I'm worried because I can use my sim card in my phone and my phone is restarted at all times, no imei and is in airplane mode (flight mode)
that I can suggest?
mkr09 said:
I'm worried because I can use my sim card in my phone and my phone is restarted at all times, no imei and is in airplane mode (flight mode)
that I can suggest?
Click to expand...
Click to collapse
Do you speak Spanish? as I am using the google translator does not translate to perfection
mkr09 said:
I'm worried because I can use my sim card in my phone and my phone is restarted at all times, no imei and is in airplane mode (flight mode)
that I can suggest?
Click to expand...
Click to collapse
Sounds like you have damaged your efs or something similar.
Try getting into download mode, and flashing back to stock. Can you do that?
Sent from my GT-I5500 using Tapatalk
Related
HI, I have an S3 9300 which was damaged by water. I finally managed to revive it by using Isopropyl Alcohol and cleaning it. The piece worked perfectly fine except for the display screen which kept blurring out. Unfortunately, the S3 display gave up and i cannot see anything or even use the touch. I tried opening the display to clean out any moisture, but again unfortunately even after carefully removing the display it wont work. Now the S3 is working with no display or Touch. repairing it here in India is costing me more than a second hand unit available. so i decided to not repair it. But since the motherboard and the rest are working fine, i thought i could use it for something else like a security IP camera.
Now i have a problem, the USB debugging was not enabled before the display konked off. the S3 is not rooted either. Can anyone help me how can i get the USB debugging enabled somehow so i can operate the phone from the desktop PC using MyPhoneExplorer. this way i can install apps, use the phone for SMS, calls and use the camera too.
I just need the USB debugging on so i can do the needful.
Anybody has any ideas? how can you help me here?
i have tried putting it in download mode and flashing a rooted stock firmware. this will at least have USB debugging on by default (i think).
Please help. what can i do?
If anyone has a working display with a busted motherboard, can i buy it? how much? i live in mumbai - India
Please reply in the thread or PM me
Thanks guys.
try connecting s3 to tv via hdmi and goto settings>developer option>enabled usb debugging ?
MoonBlade said:
try connecting s3 to tv via hdmi and goto settings>developer option>enabled usb debugging ?
Click to expand...
Click to collapse
would have tried it. but the digitizer does not work either. cannot use the display or touch. secondly i dont have the MHL HDMI connector too.
francisdsa said:
would have tried it. but the digitizer does not work either. cannot use the display or touch. secondly i dont have the MHL HDMI connector too.
Click to expand...
Click to collapse
looks like you are in a bit of a trouble.. i would have suggested flashing any other rom with usb debugging already enabled like cm10.1 . but with screen not working accessing recovery to flash rom will be tricky.
MoonBlade said:
looks like you are in a bit of a trouble.. i would have suggested flashing any other rom with usb debugging already enabled like cm10.1 . but with screen not working accessing recovery to flash rom will be tricky.
Click to expand...
Click to collapse
Ha ha ha. Actually the issue is that USB debugging is not enabled. that is the reason i am jumping around trying stuff. in fact i am on ODIN FU##ng around and now the device just wont go off the download mode. still fooling around.
i think i may brick the phone... anyways, the piece was a lab rat for me...
can i salvage anything from it? can i use the camera elsewhere? anything???
do let me know
francisdsa said:
Ha ha ha. Actually the issue is that USB debugging is not enabled. that is the reason i am jumping around trying stuff. in fact i am on ODIN FU##ng around and now the device just wont go off the download mode. still fooling around.
i think i may brick the phone... anyways, the piece was a lab rat for me...
can i salvage anything from it? can i use the camera elsewhere? anything???
do let me know
Click to expand...
Click to collapse
i heard somewhere that you can use usb keyboard with your s3. but then i am not sure whether u need usb debugging to be ON for this to work. if its not needed then i think you can use the keyboard to navigate to settings to enable usb debugging.
i have never tried this though try searching a bit in google. might find a solution.
http://forum.xda-developers.com/showthread.php?t=1749902
You cannot use input device and video output simultaneously. This means you cannot change any settings. Only bet is to try to find an adaptor that allows MHL and usb simultaneously.
Sent from my GT-I9300 using Tapatalk 4
rootSU said:
You cannot use input device and video output simultaneously. This means you cannot change any settings. Only bet is to try to find an adaptor that allows MHL and usb simultaneously.
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
You are right.
Well, please let me know if there is any other method to control the phone from the PC and enable the USB debugging settings.......I would be delighted and thankful
any ADB command mode to start USB vai command prompt
francisdsa said:
You are right.
Well, please let me know if there is any other method to control the phone from the PC and enable the USB debugging settings.......I would be delighted and thankful
Click to expand...
Click to collapse
There's no other method.
Heres a thread about MHL and OTG : http://forum.xda-developers.com/showthread.php?t=1741583
rootSU said:
There's no other method.
Heres a thread about MHL and OTG : http://forum.xda-developers.com/showthread.php?t=1741583
Click to expand...
Click to collapse
Need to know something.
What if i flash a pre-rooted ROM from ODIN? USB debugging should be enabled on it by default.
but will i get a rooted custom ROM in odin flashable format?
will i be able to flash the ROM if the device is not rooted and USB debugging disabled?
have never tried this method and hence asking a nooby question
Please help
francisdsa said:
Need to know something.
What if i flash a pre-rooted ROM from ODIN? USB debugging should be enabled on it by default.
but will i get a rooted custom ROM in odin flashable format?
will i be able to flash the ROM if the device is not rooted and USB debugging disabled?
have never tried this method and hence asking a nooby question
Please help
Click to expand...
Click to collapse
i was just googling around . i found something interesting. i think you can enable usb debugging via adb in CWM if u have proper knowledge of adb commnads. just do a search for enabling usb debugging by changing value of a property in the settings.db file located in data/data/com.android.providers.settings/databases/settings.db
rootSU said:
There's no other method.
Heres a thread about MHL and OTG : http://forum.xda-developers.com/showthread.php?t=1741583
Click to expand...
Click to collapse
MoonBlade said:
i was just googling around . i found something interesting. i think you can enable usb debugging via adb in CWM if u have proper knowledge of adb commnads. just do a search for enabling usb debugging by changing value of a property in the settings.db file located in data/data/com.android.providers.settings/databases/settings.db
Click to expand...
Click to collapse
Thanks dude, but the issue is i dont have root or CWM installed. With no display this is will be even painful as i will blindly be shooting around and possibly brick the device.
i have spoken to a few friends if they can arrange an S3 and maybe with the USB keyboard over OTG i can enable the developer settings. Secondly have also spoken around with a few service centers and mobile repair shops if they can temporarily swap a working display from a repair piece and enable the mode for me. no one has a piece at present. fingers crossed...
by the way, you are from india.. Where are you from? which city? I am from Mumbai
francisdsa said:
Thanks dude, but the issue is i dont have root or CWM installed. With no display this is will be even painful as i will blindly be shooting around and possibly brick the device.
i have spoken to a few friends if they can arrange an S3 and maybe with the USB keyboard over OTG i can enable the developer settings. Secondly have also spoken around with a few service centers and mobile repair shops if they can temporarily swap a working display from a repair piece and enable the mode for me. no one has a piece at present. fingers crossed...
by the way, you are from india.. Where are you from? which city? I am from Mumbai
Click to expand...
Click to collapse
Flashing CWM is easy. You just need to be in download mode which is easy enough to bet into blind.
ADB is done from a computer. If the settings.db has the answer, all you do is adb pull it, make the change and adb push it. Seems simple enough to me.
rootSU said:
Flashing CWM is easy. You just need to be in download mode which is easy enough to bet into blind.
ADB is done from a computer. If the settings.db has the answer, all you do is adb pull it, make the change and adb push it. Seems simple enough to me.
Click to expand...
Click to collapse
could try that. but i read elsewhere that the settings change will not affect ti as the boot.img file also needs to be stripped and modified to work with it.
francisdsa said:
could try that. but i read elsewhere that the settings change will not affect ti as the boot.img file also needs to be stripped and modified to work with it.
Click to expand...
Click to collapse
Can't you just flash a supported custom kernel then? That's all boot image is. A kernel available in .tar? Siyah 1.9.1 tar flashed from Odin.
Then boot into recovery:
Code:
adb shell
mount system
sqlite3 /data/data/com.android.providers.settings/databases/settings.db
SELECT * FROM global;
update global set value=1 where name='adb_enabled';
SELECT * FROM global;
CTRL + C
adb shell
mount system
echo "persist.service.adb.enable=1" >> /system/build.prop
This should work. Yes, adb_enabled is the value set as 0 or 1 when turning usb debugging on or off, I tested it all
Note SELECT * FROM global; shows all the values in the global table which is where adb_enabled is. It should say 0. Then you run the update command and then SELECT again to witness the change. I noticed that this did not persist after booting into android, which is why we need to put persist in the build prop. Hope this helps.
rootSU said:
Can't you just flash a supported custom kernel then? That's all boot image is. A kernel available in .tar? Siyah 1.9.1 tar flashed from Odin.
Then boot into recovery:
Code:
adb shell
mount system
sqlite3 /data/data/com.android.providers.settings/databases/settings.db
SELECT * FROM global;
update global set value=1 where name='adb_enabled';
SELECT * FROM global;
CTRL + C
adb shell
mount system
echo "persist.service.adb.enable=1" >> /system/build.prop
This should work. Yes, adb_enabled is the value set as 0 or 1 when turning usb debugging on or off, I tested it all
Note SELECT * FROM global; shows all the values in the global table which is where adb_enabled is. It should say 0. Then you run the update command and then SELECT again to witness the change. I noticed that this did not persist after booting into android, which is why we need to put persist in the build prop. Hope this helps.
Click to expand...
Click to collapse
Huh. That's seeming a bit tough fer me especially after I left linux almost 10 years ago. But am eager to try it out. Will try so and check. yhanks fot the great info. Will revert
francisdsa said:
Huh. That's seeming a bit tough fer me especially after I left linux almost 10 years ago. But am eager to try it out. Will try so and check. yhanks fot the great info. Will revert
Click to expand...
Click to collapse
You can literally copy and paste that (line by line) into windows cmd prompt, once you have adb.exe dropped in c:\windows\system32
But yeah let me know please. I did test successfully so works for me
rootSU said:
You can literally copy and paste that (line by line) into windows cmd prompt, once you have adb.exe dropped in c:\windows\system32
But yeah let me know please. I did test successfully so works for me
Click to expand...
Click to collapse
Yea yea. Surely. I shall try tomorrow itself.
francisdsa said:
Yea yea. Surely. I shall try tomorrow itself.
Click to expand...
Click to collapse
Did not work. Flashes the Siyah kernel via odin, the phone went into a boot loop.
went into recovery mode
started ADB
here is the output
====================
C:\>adb devices
List of devices attached
4df7dfa9572f3051 recovery
C:\>adb shell
[email protected]:/ $ mount system
mount system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]:/ $
=============================
here are the mount paths
================
C:\>adb shell
[email protected]:/ $ mount
mount
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p9 /system ext4 rw,nodev,noatime,nodiratime,barrier=1,data=ord
ered 0 0
[email protected]:/ $
=========================
Am stuck please help
Hi,
first of all, forgive my poor english.
I have a noob question: a friend of mine set a password on his Galaxy Note and then he forgot it.
Now, I know the solution is to access recovery and wipe data/factory reset.
BUT unfortunately he has lot of pictures and videos stored in the phone memory, not on SD, and he'd like not to lose all of it
.
Is there a workaround for that?
The Note is stock, but I can work on it, if there's a way to unlock the phone without losing data.
Inviato dal mio SK17i con Tapatalk 2
Landrea said:
Hi,
first of all, forgive my poor english.
I have a noob question: a friend of mine set a password on his Galaxy Note and then he forgot it.
Now, I know the solution is to access recovery and wipe data/factory reset.
BUT unfortunately he has lot of pictures and videos stored in the phone memory, not on SD, and he'd like not to lose all of it
.
Is there a workaround for that?
The Note is stock, but I can work on it, if there's a way to unlock the phone without losing data.
Inviato dal mio SK17i con Tapatalk 2
Click to expand...
Click to collapse
Method 1 - Using ADB:
1. Plug the device in PC using an USB cable
2. Type (after set the ADB localization)
Code:
adb shell
3. Type
Code:
adb shell rm /data/system/gesture.key
4. Type
Code:
reboot
Method 2 - Recovery:
Flash the resetpattern.zip (attached) through recovery mode.
I tested theses two methods and no data was lost!
@Landrea
So, did you try?
eduds said:
Method 1 - Using ADB:
1. Plug the device in PC using an USB cable
2. Type (after set the ADB localization)
Code:
adb shell
3. Type
Code:
adb shell rm /data/system/gesture.key
4. Type
Code:
reboot
Method 2 - Recovery:
Flash the resetpattern.zip (attached) through recovery mode.
I tested theses two methods and no data was lost!
Click to expand...
Click to collapse
is USB debugging required?
@nico12000
First method: yes, without USB debugging the ADB won't work.
Second method: no, it isn't required.
Sent from my GT-I9070 using XDA Premium 4 mobile app
eduds said:
@nico12000
First method: yes, without USB debugging the ADB won't work.
Second method: no, it isn't required.
Sent from my GT-I9070 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
When i try to flash the file i get this error:
E: signature verification failed
how can i fix it?
nico12000 said:
When i try to flash the file i get this error:
E: signature verification failed
how can i fix it?
Click to expand...
Click to collapse
stock recovery will check the zips signature that's why it failed
btw I don't know about password but when you forget a pattern there is an option to login with your gmail id and password after 5 attempts the phone locks and a new option appears as forgot my pattern and by clicking that you can login using your gmail
sangalaxy said:
stock recovery will check the zips signature that's why it failed
btw I don't know about password but when you forget a pattern there is an option to login with your gmail id and password after 5 attempts the phone locks and a new option appears as forgot my pattern and by clicking that you can login using your gmail
Click to expand...
Click to collapse
It's not a pattern, it's a password! And even if you make many attemps it doesn't ask for the gmail account
hello guys need hacker for hire ?recover lost passwords , hack criminal records, school grades and many more contact [email protected]
[CONFIRMED]
This is for Z1: http://forum.xda-developers.com/showthread.php?t=2646405
but nothing for Z2 .. :`
discipuloosho said:
[CONFIRMED]
This is for Z1: http://forum.xda-developers.com/showthread.php?t=2646405
but nothing for Z2 .. :`
Click to expand...
Click to collapse
What did you do actually? That caused it.
stanley08 said:
What did you do actually? That caused it.
Click to expand...
Click to collapse
The last commands entered were:
[email protected]#mount -o remount,rw rootfs /
[email protected]#chmod -R 0777 /storage/sdcard1 ####### because i can't create folder (in my external sdcard miniSD with ext4 format) from (cyanogenmod 11 latest nigthly release) file explorer as non-root.
[email protected]#adb reboot
and The End... :`...
discipuloosho said:
The last commands entered were:
[email protected]#mount -o remount,rw rootfs /
[email protected]#chmod -R 0777 /storage/sdcard1 ####### because i can't create folder (in my external sdcard miniSD with ext4 format) from (cyanogenmod 11 latest nigthly release) file explorer as non-root.
[email protected]#adb reboot
and The End... :`...
Click to expand...
Click to collapse
The phone has two weeks old....... :` two weeks, man ..
discipuloosho said:
The phone has two weeks....... :` two weeks, man ..
Click to expand...
Click to collapse
Will the phone enter fastboot of flashmode?
blueether said:
Will the phone enter fastboot of flashmode?
Click to expand...
Click to collapse
[CONFIRMED], man .. :`(
if you cant recover your device try this
http://forum.xda-developers.com/showpost.php?p=53968631&postcount=35
xperia Z2 doesnt support EXT4 on stock firmware, only fat32 but this applies only to internal storage
im sure cm11 supports all kinds of formats
i think your device bricked because the block partition unasigned from your sdcard1 or storage/sdcard1
none the less its a softbrick and apears to be repairable
Envious_Data said:
if you cant recover your device try this
http://forum.xda-developers.com/showpost.php?p=53968631&postcount=35
xperia Z2 doesnt support EXT4 on stock firmware, only fat32 but this applies only to internal storage
im sure cm11 supports all kinds of formats
i think your device bricked because the block partition unasigned from your sdcard1 or storage/sdcard1
none the less its a softbrick and apears to be repairable
Click to expand...
Click to collapse
Thanks Envious_data, but my device is BRIK, brik completly. Only solution is testpoint with s1tool and specific files.
discipuloosho said:
Thanks Envious_data, but my device is BRIK, brik completly. Only solution is testmode with s1tool and specific files.
Click to expand...
Click to collapse
if you can perhaps rebuild the corrupted partitions, or other solutions may include force reboot to flashmode and like said before try flashtool
maybe fastboot and see if you can format your boot and install a kernel just in attempts to get past nothing
try anything to get response, even sony logo frozen is good enough for now
if all fails you could just throw it out of a window and claim it was stolen or perhaps get a free replacement under warrenty if sony cant determine if the device has been modified
but those last solutions i think are illegal in some countries
doing a chmod shouldn't brick a device, what else did you do?
blueether said:
doing a chmod shouldn't brick a device, what else did you do?
Click to expand...
Click to collapse
That's what I think too
Guys, Unfortunately for me, I was the first to suffer Xperia Z2 (D6503) HARDBRIK in this community. On one hand I'm very sorry for what happened, but on the other hand am willing to experience the solution with testpoint, s1tool and files, but I have the knowledge to make such files. I can only goodwill engineer our community.
Thanks everybody.
I am not responsible for bricked devices!!!
DRIVERS/LINKS
LG usb drivers: https://www.mylgphones.com/lg-android-usb-device-drivers
KingoRoot: https://kingo-android-root.en.softonic.com/
LG Flash Tool 2014: http://lgflashtool.com/
VERY NEEDED (d620r10g poland) : http://lg-kdz-firmware.com/download-LGD620R-P4P-P4-POLAND-V10g/11618.html
Root Checher : https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=pl
Terminal Emulator: https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=pl
Rashr (flashtool) : https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools&hl=pl
aboot4.img : http://www.mediafire.com/file/j31gdti9jqdqsa5/aboot4.img
HOW TO DO IT?
Go to developer settings and turn on usb debugging. Root your device with KingoRoot. Turn on your phone in download mode ( hold vol - button and at the same time plug micro usb to phone). CSE flash d620r10g.kdz and boot it to the system. If system is not booting do a wipe. Now go to settings and turn on usb debugging. Now download Terminal Emulator, Root Checker and Rashr. Now root it again with KingoRoot. Now MOVE aboot4.img to internal storage to any folder. Now check if you have root access. If you don't have root access root phone again. Now open terminal emulator and paste this code (do not rewrite!!!) su (confirm)
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system (confirm)
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img (confirm)
dd if=/sdcard/aboot4.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot (confirm)
reboot (confirm)
Now you have rooted and unlocked bootloader in D620r!
You don't put aboot4.img into any folder you want. You need to put it in /sdcard/ because that is the command you are using.
hi this is what i get when i input the 2 lower commands into the shell: "abootb.img: cannot open for write: No such file or directory".
Any ideas?
fucpl said:
hi this is what i get when i input the 2 lower commands into the shell: "abootb.img: cannot open for write: No such file or directory".
Any ideas?
Click to expand...
Click to collapse
Abootb is not in the folder you targeted.
Find where it is and target it, or move it.
Ok so I searched through all the folders with no joy. I just don't get it. I followed all the steps from this tutorial and tried the other as well but got the same message. Btw root is present in able to execute first command but the remaining two give me the error message. I'm in 620r
fucpl said:
hi this is what i get when i input the 2 lower commands into the shell: "abootb.img: cannot open for write: No such file or directory".
Any ideas?
Click to expand...
Click to collapse
You can tri change sdcard with storage/emulated/0 and probably work. For me this method worked.:laugh:
syrrix01 said:
You can tri change sdcard with storage/emulated/0 and probably work. For me this method worked.:laugh:
Click to expand...
Click to collapse
Yeah, he is right.
dd doesn't work well with symlinks (like /sdcard).
Hi guys thanx for the reply. I have figured it out myself by it was indeed as syrrix01 suggested. Everything was in storage/emulated/0....again thanx for quick replies
Does this guide work? My brother made a joke when I left the phone at home and blocked my bootloader
Aourek said:
Does this guide work? My brother made a joke when I left the phone at home and blocked my bootloader
Click to expand...
Click to collapse
It should.
Just replace /sdcard with /storage/emulated/0
Also, wasn't it you who wrote this guide?
Yes, I wrote this guide XD i get inspired by this video : https://www.youtube.com/watch?v=JH7TSyxv_0E
edit:
I am afraid to unlock the bootloader because I think I will make brick for the third time
Aourek said:
Yes, I wrote this guide XD i get inspired by this video :
edit:
I am afraid to unlock the bootloader because I think I will make brick for the third time
Click to expand...
Click to collapse
The guide seems good.
Just replace /sdcard with /storage/emulated/0 and you will be fine.
Still, I take no responsibility.
Your device, your mess.
I will try to help you fix it though, of course.
Okay, I will try this.
Aourek said:
I am not responsible for bricked devices!!!
DRIVERS/LINKS
LG usb drivers: https://www.mylgphones.com/lg-android-usb-device-drivers
KingoRoot: https://kingo-android-root.en.softonic.com/
LG Flash Tool 2014: http://lgflashtool.com/
VERY NEEDED (d620r10g poland) : http://lg-kdz-firmware.com/download-LGD620R-P4P-P4-POLAND-V10g/11618.html
Root Checher : https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=pl
Terminal Emulator: https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=pl
Rashr (flashtool) : https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools&hl=pl
aboot4.img : http://www.mediafire.com/file/j31gdti9jqdqsa5/aboot4.img
HOW TO DO IT?
Go to developer settings and turn on usb debugging. Root your device with KingoRoot. Turn on your phone in download mode ( hold vol - button and at the same time plug micro usb to phone). CSE flash d620r10g.kdz and boot it to the system. If system is not booting do a wipe. Now go to settings and turn on usb debugging. Now download Terminal Emulator, Root Checker and Rashr. Now root it again with KingoRoot. Now MOVE aboot4.img to internal storage to any folder. Now check if you have root access. If you don't have root access root phone again. Now open terminal emulator and paste this code (do not rewrite!!!) su (confirm)
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system (confirm)
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img (confirm)
dd if=/sdcard/aboot4.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot (confirm)
reboot (confirm)
Now you have rooted and unlocked bootloader in D620r!
Click to expand...
Click to collapse
That .kdz is not v10g !!! is a v10h !!!
I don't know how much it matters but, I've being trying to unlock my bootloader and I can't...
Hello,
I'm using some scripts that gather information from phones. Mainly IMEI number. However this stopped working;
adb shell service call iphonesubinfo 1
Normally it would return something like that:
Result: Parcel(
0x00000000: 00000000 0000000f 00350030 00320095 '........1.2.3.4.'
0x00000050: 00380035 00330030 00654083 00320058 '4.5.6.7.8.9.0.1.'
0x00000060: 00370097 00000033 '2.3.4... ')
But... with S22+ it does this:
Result: Parcel(fffffffc ffffffff 00000000 '............')
Something have changed... any one have any idea how to get IMEI from S22+ via ADB?
PS: phone is rooted, model SM-S906B
PPS: this method was working form S6 to S21
Edit:
It seems to be an FW issue, on first released S906BXXU1AVA7 it was working (with and w/o root).
Now I have issues on S906BXXU1AVC6.
BR, Doman.
use phone info from samsung, you have a lot of info
pitelasssss said:
use phone info from samsung, you have a lot of info
Click to expand...
Click to collapse
Nope. ADB only. I know that there are apps...
Update; I can confirm that this is an FW issue. I've rolled back to S906BXXU1AVA7 and all is ok. Any thoughts?
Update 2; well... I know "whats up" now. Staring from S906BXXU1AVBF (second available FW) there is a change in Android 12 that deprecated some functions... there is possibility for a workaround, but it's not elegant. I'm currently working on it.
I am having the same issue. Were you able to make any progress?
Hey, yes, I have a method... you need to call a code *#06# an then retrieve IMEI from it.
Here's a working example:
adb shell "imei=$(input keyevent KEYCODE_CALL;sleep 1;input text '*#06#'; uiautomator dump --compressed /dev/stdout|sed s/\>\<\/\\n/g|grep -A1 IMEI|tail -n1|sed -e 's/.*text=\"//' -e 's/\".*//'); echo ${imei:0:16}"
The above line is not mine, I'm doing it a bit differently, but it still works.
You guys able to rewrite original imei?
i'm in trouble with my s22 U
This even works for older devices,
Code:
adb shell service call iphonesubinfo 1 s16 com.android.shell | cut -d "'" -f2| grep -Eo '[0-9]'| xargs| sed 's/\ //g'
Let me know if this works!
Thank you
luckk said:
You guys able to rewrite original imei?
i'm in trouble with my s22 U
Click to expand...
Click to collapse
I haven't tryed to change IMEI on any new phone, as I remember it was a hassle 10 years ago...
uncommonthinker said:
This even works for older devices,
Code:
adb shell service call iphonesubinfo 1 s16 com.android.shell | cut -d "'" -f2| grep -Eo '[0-9]'| xargs| sed 's/\ //g'
Let me know if this works!
Thank you
Click to expand...
Click to collapse
Ha! It works on Android 13 (S23) and Android 8 (S8). Thats awesome, thanks!
I mean:
adb shell service call iphonesubinfo 1 s16 com.android.shell
The whole oneliner doesn't work on windows (but can be run in linux/android shell).
BR, Doman.
Doman2011 said:
I haven't tryed to change IMEI on any new phone, as I remember it was a hassle 10 years ago...
Ha! It works on Android 13 (S23) and Android 8 (S8). Thats awesome, thanks!
I mean:
adb shell service call iphonesubinfo 1 s16 com.android.shell
The whole oneliner doesn't work on windows (but can be run in linux/android shell).
BR, Doman.
Click to expand...
Click to collapse
Cool
Hi,
I have created a script to extract device information (including IMEI) which theoretically works on all Android versions.
For those interested: https://github.com/micro5k/microg-unofficial-installer/blob/main/utils/device-info.sh
Note: My script also works on Windows, it just need BusyBox for Windows to be executed.
ale5000 said:
Hi,
I have created a script to extract device information (including IMEI) which theoretically works on all Android versions.
For those interested: https://github.com/micro5k/microg-unofficial-installer/blob/main/utils/device-info.sh
Click to expand...
Click to collapse
These service calls can vary for the different versions of Android! You should be aware of this because you don't know what will happen for all the different devices and versions. It could be very dangerous for users to execute them.
Where to find info on Android's "service call" shell command?
Using adb shell or a terminal emulator on the device, entering this will clear all notifications (requires su) service call notification 1 This will send an sms (doesn't require su) service call...
stackoverflow.com
WoKoschekk said:
These service calls can vary for the different versions of Android! You should be aware of this because you don't know what will happen for all the different devices and versions. It could be very dangerous for users to execute them.
Where to find info on Android's "service call" shell command?
Using adb shell or a terminal emulator on the device, entering this will clear all notifications (requires su) service call notification 1 This will send an sms (doesn't require su) service call...
stackoverflow.com
Click to expand...
Click to collapse
Have you looked at the script?
It execute the right command for every Android version.
Doman2011 said:
PS: phone is rooted, model SM-S906B
PPS: this method was working form S6 to S21
Edit:
It seems to be an FW issue, on first released S906BXXU1AVA7 it was working (with and w/o root).
Now I have issues on S906BXXU1AVC6.
BR, Doman.
Click to expand...
Click to collapse
Anybody seeing Odin silently disappearing when trying to flash April security patch level firmware (Snapdragon S22+ SM-S9060)? Was fine all previous firmwares...
Edit: Post removed
I need to use adb cuz the screen is shattered. How do I pull imei while in stock recovery?
Rootmaster906 said:
I need to use adb cuz the screen is shattered. How do I pull imei while in stock recovery?
Click to expand...
Click to collapse
Stock recovery only accepts 'adb sideload'. There is no cmd to pull IMEI.
WoKoschekk said:
Stock recovery only accepts 'adb sideload'. There is no cmd to pull IMEI.
Click to expand...
Click to collapse
Can you assist me then? I cannot get any information off the phone because the screen is shattered and I can't see what is on it and my uncle forgot his password to get into it and we need the IMEI to do a trade-in
Rootmaster906 said:
Can you assist me then? I cannot get any information off the phone because the screen is shattered and I can't see what is on it and my uncle forgot his password to get into it and we need the IMEI to do a trade-in
Click to expand...
Click to collapse
IMEI is also written on the phone's package.