When is it that I can expect an S-OFF tool/guide. I haven't found anything yet, if anyone is working on it, please post news here.
This one website I have found is not im English so I am unaware of it's contents. If this is a guide to achieving S-OFF, please translate and post.
Website - www(dot)shoujifans(dot)com(forwardslash)share-6-496-1(dot)html
Sorry for posting the link like this, i do not have priviledges to post a url yet.
HTC Desire 820 phone S-OFF method detailed tutorial
Start*
with the key combination win + R to open the Run, enter cmd carriage*
(due to our tool to extract the C root directory, if not just enter the command prompt is displayed, such as the root directory of the C in C time: \ Documents and Settings \ Administrator> look, you can enter cd .. and press Enter to return to parent directory until you return to the C root directory, which is C: \> way)*The following is unlocking the entire process, the content is to be entered in red, blue word content Adding comments is*C: \> adb PUSH revone / Data / local / tmp*2383 KB / s (six hundred and forty-six thousand seven hundred and four bytes in 0.265s)*C: \> adb shell*root @ Android: / # cd / Data / local / tmp (note some students but not the # $, initially concluded that the machine needs a thorough root, recommended a third party is a direct brush rom, root that comes, we can immediately solve this problem, the measured)*cd / Data / local / tmp*root android: / Data / local / tmp # chmod 755 revone*chmod 755 revone*root @ Android: / Data / local / tmp # su (PS: If you had a phone that can enter the root of this, or else do not need to enter su)*su*root @ Android : / Data / local / tmp # ./revone -P*-P ./revone*revone Successful - Please reboot to Continue.*root @ Android: / Data / local / tmp #*(PS: If there does not appear successful, but the show reboot words and try again, then that is the unlock failed approach: restart the phone, it is best to quickly turn off the power switch options, completely restart the phone, and then repeat the above steps correctly if the content that appears with the above display. then proceed to the next step after the restart the phone).*C:*\> adb shell*root @ Android: / # cd / Data / local / tmp*cd / Data / local / tmp*root @ Android: / Data / local / tmp # chmod 755 revone*chmod 755 revone*root @ Android: / Data / local / tmp # su (PS: If you had a phone that can enter the root of this, or else do not need to enter su)*su*root @ Android: / Data / local / tmp # ./revone -s -u 0*0 ./revone -s -u*revone Successful.*(PS: The above is s-off process, the following is a modified super CID began the process, and then enter the line)*root @ Android: / Data / local / tmp # reboot bootloader*reboot bootloader*(PS: phone reboot into bootloader screen, wait until then to continue to enter into the bootloader screen)*C: \> fastboot oem readcid*...*(bootloader) cid: HTC__622 (PS: This is to get their own cell phone CID , everyone may differ)*OKAY [0.016s]*Finished Total time:. 0.016s*C: \> fastboot oem writecid 11111111*...*(bootloader) Start Verify: 0*OKAY [0.047s]*Finished Total time:. 0.047s*C: \> fastboot reboot-bootloader*Rebooting into bootloader ...*OKAY [0.031s]*Finished Total time:. 0.031s*(PS: overloaded phone bootloader, wait until then to continue to re-enter the bootloader screen input)*C: \> fastboot oem readcid*...*(bootloader) cid: 11111111*OKAY [0.016s]*Finished Total time:. 0.016s*(PS: So far show cid: 11111111 super CID is successfully modified, the following is the word ** pered hboot top of the screen removed, Please normal restart the phone after entering the system continues to enter the following content)*C: \> adb shell*root @ Android: / # cd / Data / local / tmp*cd / Data / local / tmp*root @ Android: / Data / local / tmp # chmod 755 revone*chmod 755 revone*root @ Android: / Data / local / tmp # su (PS: If you had a phone that can enter the root of this, or else do not need to enter su)*su*root @ Android: / Data / local / tmp # ./revone -t*-t ./revone*revone Successful.*(PS: So far all the work is completed)*attached: from s-off again become locked in the unlock command:*adb PUSH revone / Data / local / tmp /*adb shell*su*chmod 755 / Data / local / tmp / revone*cd / Data / local / tmp /*./revone -l
vipulkothiya said:
HTC Desire 820 phone S-OFF method detailed tutorial
Start*
with the key combination win + R to open the Run, enter cmd carriage*
(due to our tool to extract the C root directory, if not just enter the command prompt is displayed, such as the root directory of the C in C time: \ Documents and Settings \ Administrator> look, you can enter cd .. and press Enter to return to parent directory until you return to the C root directory, which is C: \> way)*The following is unlocking the entire process, the content is to be entered in red, blue word content Adding comments is*C: \> adb PUSH revone / Data / local / tmp*2383 KB / s (six hundred and forty-six thousand seven hundred and four bytes in 0.265s)*C: \> adb shell*root @ Android: / # cd / Data / local / tmp (note some students but not the # $, initially concluded that the machine needs a thorough root, recommended a third party is a direct brush rom, root that comes, we can immediately solve this problem, the measured)*cd / Data / local / tmp*root android: / Data / local / tmp # chmod 755 revone*chmod 755 revone*root @ Android: / Data / local / tmp # su (PS: If you had a phone that can enter the root of this, or else do not need to enter su)*su*root @ Android : / Data / local / tmp # ./revone -P*-P ./revone*revone Successful - Please reboot to Continue.*root @ Android: / Data / local / tmp #*(PS: If there does not appear successful, but the show reboot words and try again, then that is the unlock failed approach: restart the phone, it is best to quickly turn off the power switch options, completely restart the phone, and then repeat the above steps correctly if the content that appears with the above display. then proceed to the next step after the restart the phone).*C:*\> adb shell*root @ Android: / # cd / Data / local / tmp*cd / Data / local / tmp*root @ Android: / Data / local / tmp # chmod 755 revone*chmod 755 revone*root @ Android: / Data / local / tmp # su (PS: If you had a phone that can enter the root of this, or else do not need to enter su)*su*root @ Android: / Data / local / tmp # ./revone -s -u 0*0 ./revone -s -u*revone Successful.*(PS: The above is s-off process, the following is a modified super CID began the process, and then enter the line)*root @ Android: / Data / local / tmp # reboot bootloader*reboot bootloader*(PS: phone reboot into bootloader screen, wait until then to continue to enter into the bootloader screen)*C: \> fastboot oem readcid*...*(bootloader) cid: HTC__622 (PS: This is to get their own cell phone CID , everyone may differ)*OKAY [0.016s]*Finished Total time:. 0.016s*C: \> fastboot oem writecid 11111111*...*(bootloader) Start Verify: 0*OKAY [0.047s]*Finished Total time:. 0.047s*C: \> fastboot reboot-bootloader*Rebooting into bootloader ...*OKAY [0.031s]*Finished Total time:. 0.031s*(PS: overloaded phone bootloader, wait until then to continue to re-enter the bootloader screen input)*C: \> fastboot oem readcid*...*(bootloader) cid: 11111111*OKAY [0.016s]*Finished Total time:. 0.016s*(PS: So far show cid: 11111111 super CID is successfully modified, the following is the word ** pered hboot top of the screen removed, Please normal restart the phone after entering the system continues to enter the following content)*C: \> adb shell*root @ Android: / # cd / Data / local / tmp*cd / Data / local / tmp*root @ Android: / Data / local / tmp # chmod 755 revone*chmod 755 revone*root @ Android: / Data / local / tmp # su (PS: If you had a phone that can enter the root of this, or else do not need to enter su)*su*root @ Android: / Data / local / tmp # ./revone -t*-t ./revone*revone Successful.*(PS: So far all the work is completed)*attached: from s-off again become locked in the unlock command:*adb PUSH revone / Data / local / tmp /*adb shell*su*chmod 755 / Data / local / tmp / revone*cd / Data / local / tmp /*./revone -l
Click to expand...
Click to collapse
I'm sorry, but that was difficult for me to follow. Is it possible that you have a link to a more simplictic guide, the instructions were rather unclear in the above post.
Related
I just bought an unlocked Motorola Backflip off ebay.
I had a few questions.
If I do a hard reset, do I need to unlock it again?
If I 'clear storage' or reset defaults, do I need to unlock it again?
When the Android 2.1 upgrade comes this fall, will I need to unlock it again after upgrading?
Anderdroid said:
I just bought an unlocked Motorola Backflip off ebay.
I had a few questions.
If I do a hard reset, do I need to unlock it again?
If I 'clear storage' or reset defaults, do I need to unlock it again?
When the Android 2.1 upgrade comes this fall, will I need to unlock it again after upgrading?
Click to expand...
Click to collapse
I did a hard reset (Factory refresh) and did NOT have to do Re _Unlock...I hope this helps
hard reset will not lock the phone i did it yesterday no problem go for it
how to root moto backflip???
plzzz help
motorola backflip rooted
I used these guide whith my backflip.Instructions :
Setup:
- Install adb unless you haven't done so and Motorola drivers unless you haven't done so
- Download attached archive
- Extract to a directory, I used c:\Moto_MSM_Root
- Make sure you have USB degugging enabled
- Change connection to PC Mode
Process:
- Open command prompt
- cd c:\wherever-your-sdk-tools-folder-is
- adb devices (to verify the connection)
- cd c:\Moto_MSM_Root
- adb push Superuser.apk /sdcard/Superuser.apk
- adb push su /sdcard/su
(optional) - adb push busybox /sdcard/busybox
- adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
- adb shell
- cd data/local/tmp
- chmod 0755 rageagainstthecage-arm5.bin
- ./rageagainstthecage-arm5.bin
- let the process run until it returns you to c:/Moto_MSM_Root (be patient, but may need to reboot the phone)
- cd c:/wherever-your-sdk-tools-folder-is
- adb kill-server
- adb devices (to verify the connection)
- adb shell
If you end up with "#" prompt, do the following. Otherwise reboot the phone and try again "adb shell". If even that doesn't give "#" prompt, go back to step "./rageagainstthecage-arm5.bin". There are mixed results atm., but some succeeded. See this post for possible way:
- mount -o rw,remount /dev/block/mtdblock1 /system
- cat /sdcard/su > /system/xbin/su
- chown root.root /system/xbin/su
- chmod 6755 /system/xbin/su
- cat /sdcard/Superuser.apk > /system/app/Superuser.apk
- chown root.root /system/app/Superuser.apk
- chmod 644 /system/app/Superuser.apk
(optional) - cat /sdcard/busybox > /system/bin/busybox
(optional) - chown root.root /system/bin/busybox
(optional) - chmod 755 /system/bin/busybox
- mount -o ro,remount /dev/block/mtdblock1 /system
- exit
- : google for......." Moto_MSM_Root "
how to unlock my backflip whit op lock?somoane can help me
Having dropped my desire and cracked the screen I would like to perform a factory wipe via ADB before I take it in for repair (I've backed it up).
I have the clockwork recovery which doesn't have the su/format commands and I am unable to find information on the other functions.
Any tips?
Many thanks!
Clockwork recovery offers all wipe and factory reset functions. 2.5.0.7, unless I'm missing something
He has no screen man, so gui is Wortes
Anyway, try this
Code:
adb shell
#wipe data
just a question, can you go from rooted desire with custom rom to stock by just wiping everyting in clockwork recovery?
I thought you needed to run a RUU update to put everything back to stock?
swimon said:
I thought you needed to run a RUU update to put everything back to stock?
Click to expand...
Click to collapse
That's right. But even if wipe all is not back to stock, it's better than leaving a rooted rom if you want to give it for repair i think.
try;
adb shell
wipe all
you need to add ./ to the start of adb if using a mac or linux
./adb shell
wipe all
Thanks for all the help guys!
I tried the *wipe* command, but I didn't have superuser mode set up.
To get into superuser, which was denied repeatedly I read that a popup usually shows on the phone requesting access. I think I managed to click that by tapping the screen on the left where "yes/accept" usually shows.
When I tried with superuser:
Code:
adb shell
su
wipe system
I got an long list of files that it was unable to delete.
At this point, I needed to leave and thought maybe the phone needed charging or something.
Coming back to it now, the phone is not recognised by ADB.
I've done a lot of searching and I think I must have unchecked the "usb debugging" from the notifications menu somehow.
So I have a new problem...
q) Is it possible to enable usb debugging with a cracked screen or otherwise get into the phone?
I connect the phone and just get android disk device/usb disk drive in windows manager.
I can reboot the phone into bootloader (with volume down held) and when I connect the phone I get bootloader interface appearing instead of disk drive but I just don't know where to go from there.
All I want is to clean the phone before I send it in for repair!
If anyone is able to help, I greatly appreciate it, if not thanks for your time.
In recovery you have full adb acces and can do all!
I would say, you try to make a nandroid backup and than flash the ruu
You take out your sd card and send than the device to them.
They wont to a forensic dataanalys, and most of the personal stuff is on the sd ;-)
Ps.: as far as i know you can flash ruus over fastboot(needs s-off)
And when you get your phone back, you root it and restore the last backup!
Pps.: if you haven't done a backup in the closer past you can sync, with htc sync with your pc! So you have atleast your contacts
Edit: when everything fails just keep the sd :-( they should be professional enough to keep your privacy! And i dont think your emails, sms and contacts are that different from all others :-D
Ah thanks, I thought I might be able to do that as I was mulling it over this morning. When I get home I'll give it a try and see if I succeed. I'll let you know how it goes!
Thanks for the tips and the advice on the nandroid backup - I do have a backup already - I did it when I cracked the screen as a pre-emptive, because at first I could see everything and I assumed it was just a crack but overnight the screen blacked out totally.
Ok, it's in recovery mode but doesn't seem to recognise wipe command. I added a directory listing of /sbin
Code:
C:\Program Files\Android\android-sdk\platform-tools>adb devices
List of devices attached
HT0XWPLXXXXX recovery
C:\Program Files\Android\android-sdk\platform-tools>adb shell
~ # wipe data
wipe data
/sbin/sh: wipe: not found
~ # wipe all
wipe all
/sbin/sh: wipe: not found
~ # wipe
wipe
/sbin/sh: wipe: not found
~ # ls
ls
cache etc res sdcard
data init root sys
default.prop init.rc sbin system
dev proc sd-ext tmp
~ # cd sbin
cd sbin
/sbin # ls
ls
[ erase_image mkswap sort
[[ expr mktemp split
adbd false mkyaffs2image stat
amend fdisk modprobe strings
ash fgrep more stty
awk find mount swapoff
basename flash_image mountpoint swapon
bbconfig fold mv sync
bunzip2 free nandroid sysctl
busybox freeramdisk nandroid-md5.sh tac
bzcat fuser nice tail
bzip2 getopt nohup tar
cal grep od tee
cat gunzip patch test
catv gzip pgrep time
chgrp head pidof top
chmod hexdump pkill touch
chown id printenv tr
chroot insmod printf true
cksum install ps tty
clear kill pwd tune2fs
cmp killall rdev umount
cp killall5 readlink uname
cpio killrecovery.sh realpath uniq
cut length reboot unix2dos
date less recovery unlzop
dc ln renice unyaffs
dd losetup reset unzip
depmod ls rm uptime
devmem lsmod rmdir usleep
df lspci rmmod uudecode
diff lsusb run-parts uuencode
dirname lzop sed watch
dmesg lzopcat seq wc
dos2unix md5sum setsid which
du mkdir sh whoami
dump_image mke2fs sha1sum xargs
echo mkfifo sha256sum yes
egrep mkfs.ext2 sha512sum zcat
env mknod sleep
/sbin #
su rm -rf *
Does that work? :/
Yep, that's done the trick. Thanks.
try a straight
adb shell wipe all
all on one line sometimes the shell boots incorrectly
Can't believe I was FINALLY able to achive this! Most of the hard work was put in by others for the original root (although tethered), I just tweaked the process a bit to come up with a non-tethered root solution...no more PC is needed upon reboot!
Thx to lalaihvfivfi - hxxp://forum.xda-developers.com/showthread.php?t=2194770 for the original post
Sorry for the lack of real links, I don't have 10 posts yet so I am not allowed to provide proper links - mods, fix this if necessary!
Also, not sure how if this will work on other models or rom versions, and listed below are my phone's specs:
System Version: 9.3.102.201M.SBM.en.JP
Model Number: 201M
Android Version: 4.1.2
Baseband Version: SM_T_BP_1539.000.35.03P
Kernel Version: 3.0.42-g721d60d
Build Number: 9.8.2Q-34_SMJ-102
1)Prep
- Download the Android SDK and USB drivers from the motorola homepage
- Download the following files:
- XT902_SBM ( hxxp://www1.axfc.net/uploader/so/2991543)
- su（ hxxp://www1.axfc.net/uploader/so/2918729 password：f10d）
- Download Motopoclpyse ( hxxp://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/ )
- Download the correct CWM for your phone from here --> ( hxxp://forum.xda-developers.com/showthread.php?t=2298521%E3%81%AE201M )
- Download the auto_root.sh file attached to this post
- Unzip the files and make note of the directory (I just dumped them all in the SDK > platform_tools folder as the adb files are newer than those contained in the zips above)
2) Plug the 201M in to the mac/win pc
3) Go to the directory where you Perform an adb push on the following files to the /data/local/tmp directory on the phone
- adb push su /data/local/tmp
- adb push Superuser.apk /data/local/tmp
- adb push busybox /data/local/tmp
- adb push auto_root.sh /data/local/tmp
- adb push unlock_security_module /data/local/tmp
- adb push break_setresuid /data/local/tmp/
- adb push mole-plough-ccsecurity.so /data/local/tmp/
- adb push mole-plough-lsm.so /data/local/tmp/
3) Use unlock_security_module to obtain temporary root
- adb shell
- [email protected]:/ $ cd /data/local/tmp/
- [email protected]:/data/local/tmp $ chmod 777 *
- [email protected]:/data/local/tmp $ ./unlock_security_module
- [email protected]:/data/local/tmp $ ./break_setresuid
4) You should see a stream of messages talking about the rooting process. If everything goes ok you should see:
- Unlocked LSM.
and
- Do setresuid...
Among the messages (sorry I don't remember the exact messages)
5) You should now be able to load su，Superuser.apk，busybox on to the system
- [email protected]:/data/local/tmp # mount -o rw,remount /system /system
- [email protected]:/data/local/tmp # cat /data/local/tmp/su > /system/xbin/su
- [email protected]:/data/local/tmp # cat /data/local/tmp/busybox > /system/xbin/busybox
- [email protected]:/data/local/tmp # cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
- [email protected]:/data/local/tmp # chmod 644 /system/app/Superuser.apk
- [email protected]:/data/local/tmp # cd /system/xbin
- [email protected]:/system/xbin # chown root.root su
- [email protected]:/system/xbin # chown root.root busybox
- [email protected]:/system/xbin # chmod 6755 su
- [email protected]:/system/xbin # chmod 755 busybox
- [email protected]:/system/xbin # mount -o ro,remount /system /system
6) After the opperation is done it is ok to remove the cable from the pc. Check and see if SuperSU was installed. If it wasn't download Chainfire from the play store (which you should probably do anyway to update su)
7) Next, download Busybox from the playstore and run the updates
8) By this point you should have a fully upgraded Superuser, su, and busybox installation - however the access is only temporary and will be reset on reboot
9) Put the CWM.img you downloaded in motoapoclypse directory you created in step 10
10) Plug the 201M back in to the mac/win pc
11) Run the following commands to prepare for CWM install and reconfirm root is enabled
- adb push unlock /data/local/tmp/
- adb push cwm.img /data/local/tmp/cwm.img > nul
- adb shell chmod 755 /data/local/tmp/unlock
- adb shell
- [email protected]:/ $ cd /data/local/tmp/
- [email protected]:/ $ chmod 777 *
- [email protected]:/ $ ./unlock_security_module
- [email protected]:/ $ ./break_setresuid
- [email protected]:/ $ ./unlock
If you get a mention that the phone is already rooted, it's ok...these steps are just to make sure!
12) Inserting CWM
- [email protected]:/ $ su -c 'mount -o remount,rw /system'
- [email protected]:/ $ su -c 'mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak'
- [email protected]:/ $ su -c 'mv /system/recovery-from-boot.p /system/recovery-from-boot.bak'
- [email protected]:/ $ su -c 'dd if=/data/local/tmp/cwm.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery'
- [email protected]:/ $ su -c 'rm /data/local/tmp/cwm.img'
- [email protected]:/ $ reboot recovery
13) Upon reboot, you should be in CWM!
14) Exit out of CWM and let the phone boot up normally - you will notice you no longer have root, but fortunately you do not have to go through the above process all over again
15) Renable root by running the following command (Thx to kprower - hxxp://forum.xda-developers.com/showpost.php?p=46842021&postcount=19)
- adb shell "./data/local/tmp/unlock_security_module"
16) Download Script Manager - S Manager ( hxxps://play.google.com/store/apps/details?id=os.tools.scriptmanager&hl=en ) or use your own preference
17) Download the script attached to the thread (feel free to read through it and make it better if you can! - Thx to Sepero for BootBuddy - hxxp://androidforums.com/rooted-devices-only/693743-bootbuddy-run-boot-scripts- as a base)
18) Using script manager, go to the /data/local/tmp directory and click on auto_root.sh and open as a Script/Executable
19) Toggle the Su picture to turn on the ability to run as SU, then click save, then run.
20) The script should run (hopefully w/o any errors) and create the necessary file with the proper permissions
21) At this point, shut down the phone and reboot....you should have permanent root!
Click to expand...
Click to collapse
Any questions or spot any mistakes? Please ask and/or feel free to modify and update as necessary!
how to update 4.1.2?
hungln03 said:
how to update 4.1.2?
Click to expand...
Click to collapse
I just did the OTA (over the air) update back in March under Settings -> About Phone --> System Update
Though, if you can install CWM using the method above, you should be able to update that way as well (just make sure you have the right rom)
Bootloader unlock? can update?
---------- Post added at 03:37 AM ---------- Previous post was at 03:10 AM ----------
step17 link die
hungln03 said:
Bootloader unlock? can update?
---------- Post added at 03:37 AM ---------- Previous post was at 03:10 AM ----------
step17 link die
Click to expand...
Click to collapse
Yes, the bootloader is unlocked! As far as update...no idea as I already had the newest rom...
And Step 17, don't download the link there --> download the attached file on the bottom of the original post called auto_lock.sh.zip -- don't go the the androidforum's link!
The zip attached to the this thread is ok, I just downloaded it! Good luck!
Will this root a phone that took the November OTA update and has locked bootloader?
wolfpack99 said:
Will this root a phone that took the November OTA update and has locked bootloader?
Click to expand...
Click to collapse
No idea...last update Softbank (Japan) models received was last March....give it a try as this method should allow you to unlock the bootloader as well, but not sure if it will work or not outside of the SB model
It won't work on the XT907 with 9.8.1Q-78 or 9.8.1Q-94, since the bugs were fixed here, so that "unlock_security_module" will cause a segfault.
It might work on 9.8.1Q-66 and older versions, but there you also have the regular motopocalypse. So it's really just for the 201M.
okay this is good news, but can anybody enlight me how execute those steps above since i'm new to this thing?
stuck on chmod777* can't go through
Congratulations about the Root & unlock!! Great Job LostInInaka!!
Is there a source for the latest SB xml?
SIM Free?
It may be a stupid question, but does unlocking the Bootloader and rooting the device make it SIM free?
Thanks for sharing all this exiting stuff.
:good::good::good:
root 201M
what am I doing wrong?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sumkos said:
what am I doing wrong?
Click to expand...
Click to collapse
What you have to type in step 3 is:
adb shell
cd /data/local/tmp/
chmod 777 *
./unlock_security_module
./break_setresuid
No hostnames, no prompt sings.
root 201M
lem22 said:
What you have to type in step 3 is:
adb shell
cd /data/local/tmp/
chmod 777 *
./unlock_security_module
./break_setresuid
No hostnames, no prompt sings.
Click to expand...
Click to collapse
many thanks! deal with it, but now another problem:
You get a segfault, just like I mentioned in #8.
Do you really have a SoftBank 201M?
201M
lem22 said:
You get a segfault, just like I mentioned in #8.
Do you really have a SoftBank 201M?
Click to expand...
Click to collapse
in principle without difference already. the bootloader unlocked. recovery was flashed (TWRP) by fastboot comand. But sim lock didn't disappear. I flash different firmware (xt905, xt907, AOKP 4.4) and different radio. very sad
Bricked?
Hi guys. I got up to step 6 and after installing Chanfire and updating it rebooted my phone now I am stuck on the boot screen with only =SoftBank logo showing.
Help!:crying:
OMG!
After trying a few different things i am now completely stuck in the Fastboot Flash Mode.
at the bottom it says:
Fastboot Reason: Flash Failure
usb connected
Bricked
This is what I am currently seeing:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-e92be7d, 2013-03-29 01:58:14)
eMMC Info: Size 8GB
Deivice is LOCKED, Status Code: 0
Battery OK
Transfer Mode:
USB Connected
Fastbook Reason: Flash Failure
usb connected
---------------------------------------update
From CMD i sent the following command: fastboot continue
Now it shows the Softbank logo but it doesn't seem to be going anywhere. However, Windows did suddenly notice the device as soon as the logo came up and started to install the MTP USB Device, Motorola Networking Interface, and Motorola ADB Interface which all failed.
---------------------------------------update 2
Whilst in the Softbank logo screen I was able to send ADM commands so I tried going through the steps again to see what would happen.
Now this is what I have:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-e92be7d, 2013-03-29 01:58:14)
eMMC Info: Size 8GB
Deivice is UNLOCKED, Status Code: 3
Battery OK
Transfer Mode:
USB Connected
Fastbook Reason: Flash Failure
usb connected
Thank you so much!!!!
Thank you so much for this. After a month or so of tinkering with my 201m, I had resigned myself to a locked controlled Android phone. This makes it so much better. I really cannot thank you enough!!!!:laugh::laugh::laugh:
Hi,
i just found a way to root the 80 xs you need Linux for it (i think a Virtual machine should do but i didn't test it).
FIRST OF ALL YOU CAN BRICK YOUR DEVICE AND I AM NOT RESPONSIBLE FOR IT
Based on "Rooting the Cube U30GT rk3066 android tablet" i think a copy and past version makes it more easy
http://valentijn.sessink.nl/?p=382
download
superuser and su from
http://forum.xda-developers.com/showthread.php?t=1835502
rkflashtool to readout your system
http://sourceforge.net/projects/rkflashtool
and linux_upgrade_tool to upload your modified system image
http://dl.radxa.com/rock/tools/linux/
put all (even Superuser.apk and su from the archive) in top of one directory (/home/user/archos) connect your device to the pc
open a terminal
get root
# cd archos
# adb reboot bootloader
# ./rkflashtool r 0x0000 0x2000 > /tmp/parm
# head -11 /tmp/parm
search for system, there you have the position of your system just to be sure if its the same for you
Code:
PARMDFIRMWARE_VER:4.0.4
MACHINE_MODEL:ARCHOS 80XSK
MACHINE_ID:007
MANUFACTURER:RK30SDK
MAGIC: 0x5041524B
ATAG: 0x60000800
MACHINE: 3066
CHECK_MASK: 0x80
KERNEL_IMG: 0x60408000
#RECOVER_KEY: 1,1,0,20,0
CMDLINE: console=ttyFIQ0 androidboot.console=ttyFIQ0 init=/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:[email protected](misc),[email protected](kernel),[email protected](boot),[email protected](recovery),[email protected](backup),[email protected](cache),[email protected](kpanic),[U][COLOR="Red"][email protected](system)[/COLOR][/U],[email protected](userdata)
# ./rkflashtool r 0x00154000 0x00100000 > system
# cp system new
# mkdir /mnt/img
# mount new /mnt/img
# cp su /mnt/img/bin/
# cp Superuser.apk /mnt/img/app/
# chown root:2000 /mnt/img/bin/su
# chmod 6774 /mnt/img/bin/su
# umount /mnt/img
# ./upgrade_tool di -s new
# ./rkflashtool b
and if all went right open terminal on the tablet and type su and watch superuser to come up
now you can install AdAway from F-Droid and be happy
Greetings
Sebastian
About
I know that there a lot of guides out there which help you in creating logcat reports.
As there are so many and not one of them was good enough for my requirements I decided to create an own simple guide where I can refer to..
Windows & Linux: Log to a file (recommended way!)
Follow Post #2
Alternative: Windows & Linux: Log to terminal window
Follow Post #3
Trouble, connection or other issues
If you encounter any issues consider to try FWUL which is made for a stable and out-of-the-box working android connection
.
RECOMMENDED: Windows & Linux: Log to a file
1) Ensure you have adb set up on your PC, and have adb debugging and "developer options -> Root access -> ADB only" enabled or rooted the device otherwise
2) open the adb shell:
option A) when: developer options -> Root access -> ADB only is enabled:
adb root
adb shell
option B) when: magisk/supersu installed:
adb shell
su
Click to expand...
Click to collapse
3) The next step depends on what is needed (if you are not sure which one then it is likely option B) :
option A) ONESHOT (e.g. to debug general issues. for boot issues go to option C instead) :
logcat -b all -d -D > /sdcard/Download/logcat.txt
Click to expand...
Click to collapse
option B) SPECIFIC ISSUE (e.g. app crashes etc. for selinux issues go top option D instead):
logcat -c -b all
(this will print nothing - it will just clear the log buffer)
now reproduce the issue
when the issue occurred:
logcat -b all -d -D > /sdcard/Download/logcat.txt
Click to expand...
Click to collapse
option C) FULL BOOT log (requires Linux / FWUL):
exit from "adb shell" screen.
Power off your phone and type in the the terminal:
when 2A) matches your setup:
adb wait-for-device && adb root && sleep 1s && while true;do adb shell dmesg -c; done >> dmesg.log
when 2B) matches your setup:
adb wait-for-device && while true;do adb shell su -c dmesg -c; done >> dmesg.log
now power on your phone and wait until Android has fully booted, login and when you see the Android Home screen:
CTRL + C in the terminal window
The log will be generated locally in Linux (name: dmesg.log) and so you can skip step 4 and go on with 5
Click to expand...
Click to collapse
option D) SELINUX (e.g. needed to debug selinux issues when in enforcing mode or if enforcing is what you want to achieve one day) :
logcat -b main -e avc: > /sdcard/Download/logcat.txt
if you have a specific issue reproduce it now or turn it on/off whatever not works atm.
CTRL + C in the terminal window once you are finished
Click to expand...
Click to collapse
4) exit from the adb shell & grab the log from your PC:
Code:
exit
adb pull /sdcard/Download/logcat.txt
5) Share the content of this logcat.txt using https://privatebin.at/ (ensure you select at least 1 month or more as expire date!)
If for any reason the above link does not work for you then use on one of the billions other paste services.
Here some examples:
https://bpa.st/
https://0bin.net
https://hastebin.com
https://controlc.com
https://justpaste.me
https://privatebin.net
https://pastebin.com
https://paste.ubuntu.com (login required)
more examples: https://wiki.ubuntu.com/Pastebin
6) Always share your model name (e.g. H811, H815, ...) and how you unlocked (official or e.g. by UsU)
ALTERNATIVE: Windows & Linux: Log to terminal window
Windows preparation
If the recommended way fails for any reason you can also print the logcat output in the terminal window.
For this open the terminal and type:
Code:
mode con lines=32766
and ENTER.
This sets the buffer in your terminal to the max possible which is needed due to the log verbosity.
Begin (Windows & Linux)
1) Ensure you have adb set up on your PC, and have adb debugging and "developer options -> Root access -> ADB only" enabled or rooted the device otherwise
2) open the adb shell:
option A) when: developer options -> Root access -> ADB only is enabled:
adb root
adb shell
option B) when: magisk/supersu installed:
adb shell
su
Click to expand...
Click to collapse
3) The next step depends on what is needed (if you are not sure which one then it is likely option B) :
option A) ONESHOT (e.g. to debug general issues. for boot issues go to option C instead) :
logcat -b all -d -D
Click to expand...
Click to collapse
option B) SPECIFIC ISSUE (e.g. app crashes etc. for selinux issues go top option D instead):
logcat -c -b all
(this will print nothing - it will just clear the log buffer)
now reproduce the issue
when the issue occurred:
logcat -b all -d -D
Click to expand...
Click to collapse
option C) FULL BOOT log (requires Linux / FWUL):
exit from "adb shell" screen.
Power off your phone and type in the the terminal:
when 2A) matches your setup:
adb wait-for-device && adb root && sleep 1s && while true;do adb shell dmesg -c; done
when 2B) matches your setup:
adb wait-for-device && while true;do adb shell su -c dmesg -c; done
now power on your phone and wait until Android has fully booted, login and when you see the Android Home screen:
CTRL + C in the terminal window
Click to expand...
Click to collapse
option D) SELINUX (e.g. needed to debug selinux issues when in enforcing mode or if enforcing is what you want to achieve one day) :
logcat -b main -e avc:
if you have a specific issue reproduce it now or turn it on/off whatever not works atm.
CTRL + C in the terminal window once you are finished
Click to expand...
Click to collapse
4) copy the whole console output
5) Share the content of this logcat.txt using https://privatebin.at/ (ensure you select at least 1 month or more as expire date!)
If for any reason the above link does not work for you then use on one of the billions other paste services.
Here some examples:
https://bpa.st/
https://0bin.net
https://hastebin.com
https://controlc.com
https://justpaste.me
https://privatebin.net
https://pastebin.com
https://paste.ubuntu.com (login required)
more examples: https://wiki.ubuntu.com/Pastebin
6) Always share your model name (e.g. H811, H815, ...) and how you unlocked (official or e.g. by UsU)
reserved