Im using MAC OSX, so i've only use SEUS. So how can i get root for my NEO and unlock BL???
sorry for my bad ENG
I did unlock my bootloader and rooted my neo using a linux system. Never used windows. So I suppose it would be possible to do the same with osx.
For unlocking BL use this http://unlockbootloader.sonymobile.com/instructions
You would need android sdk and run fastboot from there.
For rooting I suggest you look here: http://forum.xda-developers.com/showthread.php?t=1468866
Good luck!
I used S1Tool to unlock bootloader and I think it is only in Windows.
If you use the official method (http://unlockbootloader.sonymobile.com/instructions) using fastboot, I assume you can do that on Mac, try this? http://blog.wapnet.nl/2011/05/setup-adb-and-fastboot-with-android-sdk-on-mac-osx/
If you unlocked the bootloader, it is far more simple to root, just boot into CWM using recoveryNeo.img.
http://forum.xda-developers.com/showthread.php?t=1183465
I used the files in here: http://androidsu.com/superuser/
1) Extract and copy `su` and `Superuser.apk` out.
2) Boot into fastboot (hold menu while plug in usb).
3) On computer type `fastboot boot recoveryNeo.img`.
4) Wait till CWM is loaded.
5) Go to Mounts and Storage and mount system.
6) On computer, type `adb devices` to make sure it is connected (You may need SE's driver)...
Code:
adb push su /system/bin
adb shell chmod 6755 /system/bin/su
adb shell ln /system/bin/su /system/xbin/su
adb push Superuser.apk /system/app
7) Reboot system.
Related
Hello,
Here i will give you a quick guide for HTC Hero to flash recovery image, root and flash custom rom and radio update.
1st download this package:
http://www.mediafire.com/?znq5hwjmldk
Or here
http://www.2shared.com/file/9305692/347b5ebf/sdk.html
Unzip it on c:\ so you have c:\sdk
In there you have 2 folders tools and usb driver for x86.
Connect your hero switch on to a usb and point to /sdk/usb drivers/x86 to install drivers
Download this rom:
http://content.modaco.net/hero/2.9-update-hero-modacocustomrom-core-signed.zip
And this Radio:
ftp://xda:[email protected]_6.35.08.22-signed.zip
copy them to sd card and rename rom image update.zip and radio to radio.zip
Now turn off hero and then press back+power to enter bootloader.
connect hero to usb port and let it install drivers or point to usb drivers/x86 folder again.
After done installing follow this commands to have root and recovery image to phone.
click start->run in open: write cmd
then cd\
cd sdk
cd tools
Copy paste this:
1. fastboot boot recovery.img
2. adb shell mount /sdcard
3. adb shell push recovery.img /sdcard/recovery.img
4. adb shell flash_image recovery /sdcard/recovery.img
5. adb shell mount /system
6. adb push su /system/bin/
7. adb shell chmod 4755 /system/bin/su
8. adb push Superuser.apk /system/app/
9. adb shell reboot
Let it reboot, then power off and press home+power and keep pressing home button until you see recovery image.
then you pick radio image radio.zip to flash, let it flash and will return to recovery then you can flash update.zip but before flash update.zip is recommended to wipe.
This is a collection of other tutorials so give credit to others not me.
thanks
The problem is that this works only on older versions of the Hero firmware. Newer versions are patched to not allow unsigned images to be fastbooted.
Soaa- you can use the GoldCard method to install an older ROM.
I know that. I did that.
But my point is this guide is outdated.
I think this guide is same as one Rooting HTC Hero ....success
Sorry to ask on many topics but I don't understand why we should "flash" the RADIO and SPL...What is "RADIO" and "SPL" ? What is the risk of flashing RADIO and SPL ?
Also why some ROMs need to flash RADIO and SPL ?
Thanks,
omokas
You need to worry about those things once decided to root or unroot.
HTC or your middle supplier will never ask you to do that. Because official Rom update will update everything.
I did updated with the latest European WWE update that updated my Build Number to 2.73.405.5.
Does this means that I can install MoDaCo 2.9 ROM (For Hero) without any risk of need to update Radio and SPL ?
I don't have warranty if I brick it Also yes I am rooted
I rooted my thunderbolt. After flashing clockwork mod, I downloaded the rom of my choosing. Then when booting to recovery to flash the rom, I get kicked to the bootloader. Help!??!?
Ps: It seems its that clockwork mod wont take even though rom manager says flashed sucessfuly
EDIT: I did some more investigation and after redoing this
"Step 5
Next, enter the following commands:
adb shell
/data/local/psneuter
To unlock eMMC:
adb shell
/data/local/wpthis
exit
Step 6
Please pay attention – this is very important. This step involves a small chance of bricking if you mess up.
To push the eng bootloader:
adb push hbooteng.nb0 /data/local/
adb shell
/data/local/busybox md5sum /data/local/hbooteng.nb0
If the output does not match "6991368ee2deaf182048a3ed9d3c0fcb" exactly, stop, delete it, and re-download it. Otherwise, continue.
Now we will write the new bootloader.
dd if=/data/local/hbooteng.nb0 of=/dev/block/mmcblk0p18
Confirm proper write:
/data/local/busybox md5sum /dev/block/mmcblk0p18
If the output does not match "6991368ee2deaf182048a3ed9d3c0fcb," try again; if it still doesn’t work, seek help from chat.andirc.net in channel #thunderbolt. DO NOT REBOOT.
Now, reboot your phone and put the custom RUU (PG05IMG.zip) on your SD card. Then flash it. This will upgrade you to release firmware with an S-OFF bootloader.
Next, run this command:
adb reboot bootloader
After it flashes, you will be running release firmware with S-OFF."
I have working recovery with S-Off. Just thought I would update incase this happens to anyone else
I'm having the same issue after rooting but I used the one click process. Guess at this point I should just try to go.throughit again? Or should I go.through adb and follow your steps?
Thanks you!
Nevermind
Sent from my ADR6400L using XDA App
Alright well i'm using the zedomax tutorial from htcevohacks. and i'm stuck at step Step 8:
Next, open up a command prompt and type:
cd \hbootdowngrade217
adb push misc_version /data/local/
adb shell /data/local/misc_version -s 1.10.651.2<<<<<now after i type that in i get Denied permissions.... WHY PLEASE HELP
adb reboot bootloader
fastboot getvar mainver
If you get back mainver: 1.10.651.2, you are good to go, go to the next step.
could anyone please help me with this
Spazzpyro said:
Alright well i'm using the zedomax tutorial from htcevohacks. and i'm stuck at step Step 8:
Next, open up a command prompt and type:
cd \hbootdowngrade217
adb push misc_version /data/local/
adb shell /data/local/misc_version -s 1.10.651.2<<<<<now after i type that in i get Denied permissions.... WHY PLEASE HELP
adb reboot bootloader
fastboot getvar mainver
If you get back mainver: 1.10.651.2, you are good to go, go to the next step.
could anyone please help me with this
Click to expand...
Click to collapse
Are you sure you are rooted?
well i'm using the directions for temp root... and when i go through that it says i am.. i'm relcocked hboot 1.5 s-on i re rooted it and then unrooted it again and tried this method again and i'm still getting the same thing
When u do adb shell, do u have $ or #?
cd \hbootdowngrade217
adb push misc_version /data/local/
adb shell /data/local/misc_version -s 1.10.651.2
adb reboot bootloader
fastboot getvar mainver
those are the codes i'm using if thats what u mean
Spazzpyro said:
cd \hbootdowngrade217
adb push misc_version /data/local/
adb shell /data/local/misc_version -s 1.10.651.2
adb reboot bootloader
fastboot getvar mainver
those are the codes i'm using if thats what u mean
Click to expand...
Click to collapse
No, I meant type adb shell and see if their is a # (meaning root) or a $ (meaning no root)
The downgrade thread here at xda made by unknownforce doesnt have that step anymore, its now in the last step. check it out its here
i got a # so i'm rooted i been looking on that thread
Are you giving that command while in android or recovey?
android
Is usb degugging on?
yeah
ok now i've got farther!!!! i think i was copy and pasting it thats why but now instead of it saying no permission or w.e its saying file not found... so whats the code i put in or file name? i got the hbootdowngrade217 file... in my root directory with the fastboot and adb...
ok nvm i'm back to square one same thing with no permission :-/
Did you go through steps again just to make sure you didn't miss a step
Try to restore with an official ruu. Download it and put it in your sd card. Let it boot and turn usb debugging on, then follow the instructions to temporarily root your phone and try again from there.
Hi There
So, I normally obtain adb root by the following process:
1. Unlock the Bootloader (if required)
2. Use fastboot to OEM unlock the boot loader
3. Get the boot.img and upack it
4. Change ro.secure=0 and ro.debbugable=1 in default.prop
5. repack boot.img
6. flash boot.img to device
7. Boot up device, ensure USB debugging is enable.
8. Then use adb root, adb remount rw and I usually always get adb root this way. So I can "adb shell" and I have a # root prompt.
However I think I have always had the ENG or DEBUG builds of the OS when I did this.
So I now only have a USER build of the OS.
I follow the above procedure but it doesn't matter how many times I change the ro.secure and ro.debggable settings , they are always locked. They must be being set somewhere else?
So I heard that this is normal for USER builds, the build simply does not allow access to ro.secure=0.
My questions are:
1. Is what do I need to change in the USER build of my OS or boot.img to get ro.secure=0 working?
2. Is it even possible?
3. Failing this, can you get generic DEBUG/ENG boot.img's for MTK 6755 devices?
Hello, i wanted to flash my phone(Motorola One Macro) to LineageOS 17.1, but it get error at flashing and now is phone permanently restarting.... i dont know how to flash new stock firmware, or any new android.
i know i can use adb, but it doesnt work or i do it bad. :angel:
pls help, thanks.
@drobec255
You by means of ADB always can re-flash phone's Stock ROM ( it's not necessary phone's boot-loader is unlocked )
Code:
adb devices
adb reboot recovery
[i][color=red]Note: In recovery menu presented select option Apply Update From ADB and confirm it, then proceed with[/color][/i]
adb sideload <PATH_TO_STOCK_ROM_IMAGE_FILE_ZIP>
adb reboot
jwoegerbauer said:
@drobec255
You by means of ADB always can re-flash phone's Stock ROM ( it's not necessary phone's boot-loader is unlocked )
Code:
adb devices
adb reboot recovery
[i][color=red]Note: In recovery menu presented select option Apply Update From ADB and confirm it, then proceed with[/color][/i]
adb sideload <PATH_TO_STOCK_ROM_IMAGE_FILE_ZIP>
adb reboot
Click to expand...
Click to collapse
ok, i flashed it to stock ROM, phone works.
I wanna flash it to LineageOS 17.1 but file is ".img.xz" ??? how to? bootloader is unlocked
@drobec255
1st of all things is you must have a TWRP matching your phone at your fingertips.
Next thing is that you must have a Lineage OS 17.1 version that's at 100% compatible with your phone - don't think this exists. BTW: Lineage OS always is offered as a signed ZIP-file.
If these requirements are met, then to replace phone's Android 9 by Lineage OS 17.1 you run this command sequence:
Code:
adb devices
[i][color=red]next 6 cmds backup /efs & /vendor partitions[/color][/i]
adb shell "cat /efs > /data/local/temp/efs_bkup"
adb pull /data/local/temp/efs_bkup %TEMP%\EFS_BKUP
adb shell "rm /data/local/temp/efs_bkup"
adb shell "cat /vendor > /data/local/temp/vendor_bkup"
adb pull /data/local/temp/vendor_bkup %TEMP%\VENDOR_BKUP
adb shell "rm /data/local/temp/vendor_bkup"
adb reboot bootloader
fastboot devices
fastboot erase system
fastboot erase cache
fastboot erase userdata
[i][color=red]temporarily boot into TWRP[/color][/i]
fastboot boot <PATH_TO_TWRP_IMG>
[i][color=red]In TWRP's menu select option Apply update from ADB and confirm[/color][/i]
adb sideload <PATH_TO_LINEAGE_OS_ZIP>
[i][color=red]next 2 cmds restore /efs & /vendor partitions[/color][/i]
adb push %TEMP%\EFS_BKUP /efs
adb push %TEMP%\VENDOR_BKUP /vendor
adb reboot
For anyone that this may still happen too....
Use RSA to put your phone back to it's stock rom. Even if it's bricked. it'll recovery it.
Rescue and Smart Assistant Tool - Motorola
<h6><span style="color:#FFFFFF"><strong>Our Rescue and Smart Assistant tool</strong><br />can help diagnose and resolve issues on your<br />Motorola phone or Lenovo phone/tablet.</span></h6>
www.motorola.com