Related
GUYS HELP....the official website only let me download 6.0.3.1 touch,,,but the touch screen wont work on aroma....
so anybody can help me with a flashable zip file plzzzzz
Use the TWRP or the Philz CWM
darkoblade said:
GUYS HELP....the official website only let me download 6.0.3.1 touch,,,but the touch screen wont work on aroma....
so anybody can help me with a flashable zip file plzzzzz
Click to expand...
Click to collapse
Don't use the official website, the latest version can be found in the thread: http://forum.xda-developers.com/showthread.php?t=2173863
nkk71 said:
Don't use the official website, the latest version can be found in the thread: http://forum.xda-developers.com/showthread.php?t=2173863
Click to expand...
Click to collapse
thxxxxxx alot my friend.... last thing though...how do i install this img file???
darkoblade said:
thxxxxxx alot my friend.... last thing though...how do i install this img file???
Click to expand...
Click to collapse
Just as it says in the OP:
Make sure fastboot is unchecked in power options and turn phone completely off
Boot into HBOOT then Fastboot
From fastboot. Use command "fastboot erase cache"
From fastboot. Use command "fastboot flash recovery recovery.img"
nkk71 said:
Just as it says in the OP:
Make sure fastboot is unchecked in power options and turn phone completely off
Boot into HBOOT then Fastboot
From fastboot. Use command "fastboot erase cache"
From fastboot. Use command "fastboot flash recovery recovery.img"
Click to expand...
Click to collapse
another noob question....where do i type this commend...from computer of mobile???
darkoblade said:
another noob question....where do i type this commend...from computer of mobile???
Click to expand...
Click to collapse
From your computer. (you are unlocked right?)
But since you're asking, (sorry no offense intended at ALL), have you familiarized yourself with the various guides for unlocking, custom firmware, rooting, flashing, etc.
I really recommend doing that before proceeding.
Also once you do flash the custom recovery, do a nandroid backup of your stock rom, in case you need it in the future.
nkk71 said:
From your computer. (you are unlocked right?)
But since you're asking, (sorry no offense intended at ALL), have you familiarized yourself with the various guides for unlocking, custom firmware, rooting, flashing, etc.
I really recommend doing that before proceeding.
Also once you do flash the custom recovery, do a nandroid backup of your stock rom, in case you need it in the future.
Click to expand...
Click to collapse
no offence taken at all man...but no am not unlocked...i updated to 4.3 before rooting so i couldnt use the unlock method...
by unlock u mean s-off right???
cuz am already rooted with a custom rom
darkoblade said:
no offence taken at all man...but no am not unlocked...i updated to 4.3 before rooting so i couldnt use the unlock method...
by unlock u mean s-off right???
cuz am already rooted with a custom rom
Click to expand...
Click to collapse
no no, not s-off, just bootloader unlocked (using HTCdev), and since your already rooted and on a custom rom, you've obviously already done that.
You're good to flash the updated recovery as mentioned in the steps above.
Download the recovery img to your computer, and place it the same folder as your fastboot/adb commands are
then reboot your phone to bootloader
connect the phone to your PC, and on your phone it will read "FASTBOOT USB"
then on your PC run:
"fastboot erase cache"
"fastboot flash recovery <name of recovery>.img"
nkk71 said:
no no, not s-off, just bootloader unlocked (using HTCdev), and since your already rooted and on a custom rom, you've obviously already done that.
You're good to flash the updated recovery as mentioned in the steps above.
Download the recovery img to your computer, and place it the same folder as your fastboot/adb commands are
then reboot your phone to bootloader
connect the phone to your PC, and on your phone it will read "FASTBOOT USB"
then on your PC run:
"fastboot erase cache"
"fastboot flash recovery <name of recovery>.img"
Click to expand...
Click to collapse
haha..yeah ok man...i just realized i need to have the andriod sdk first to have the fastboot/adb folder.....am keep diging anyway....thankx for the help .
darkoblade said:
haha..yeah ok man...i just realized i need to have the andriod sdk first to have the fastboot/adb folder.....am keep diging anyway....thankx for the help .
Click to expand...
Click to collapse
yep, you need the sdk and also the drivers for your PC, a quick search through the forum or google will find you plenty of answers; there's also a toolkit here: http://forum.xda-developers.com/showthread.php?t=2183942
though I never use it myself, but it does contain the adb/fastboot commands in one of it's subfolders.
nkk71 said:
yep, you need the sdk and also the drivers for your PC, a quick search through the forum or google will find you plenty of answers; there's also a toolkit here: http://forum.xda-developers.com/showthread.php?t=2183942
though I never use it myself, but it does contain the adb/fastboot commands in one of it's subfolders.
Click to expand...
Click to collapse
nothing is working man....my recovery is stuck on cwm 6.0.3.1 and dont want to budge....
darkoblade said:
nothing is working man....my recovery is stuck on cwm 6.0.3.1 and dont want to budge....
Click to expand...
Click to collapse
are you sure you're not relocked? can you post a screenshot (or text) of your bootloader.
nkk71 said:
are you sure you're not relocked? can you post a screenshot (or text) of your bootloader.
Click to expand...
Click to collapse
sure...
darkoblade said:
sure...
Click to expand...
Click to collapse
you should be fine, in the attached screenshot use the POWER button to enter FASTBOOT, once it says FASTBOOT where it now shows HBOOT, connect it to your PC.
it should then show as FASTBOOT USB (if it doesn't then you're missing the drivers on your PC, and have to reinstall them)
then just follow the steps on your PC:
"fastboot erase cache"
"fastboot flash recovery <name of recovery>.img"
if any of those give you an error message (or any message), post them for us to see.
nkk71 said:
you should be fine, in the attached screenshot use the POWER button to enter FASTBOOT, once it says FASTBOOT where it now shows HBOOT, connect it to your PC.
it should then show as FASTBOOT USB (if it doesn't then you're missing the drivers on your PC, and have to reinstall them)
then just follow the steps on your PC:
"fastboot erase cache"
"fastboot flash recovery <name of recovery>.img"
if any of those give you an error message (or any message), post them for us to see.
Click to expand...
Click to collapse
mmmm...am sorry this is taking so mush of your time..but my problem is with the adb thing..i downloaded the sdk but the sdk manager wont start...and the adb just opens a cmd window and closes ,,,i installed the java and everything needed but i cant open the sdk manager...
darkoblade said:
mmmm...am sorry this is taking so mush of your time..but my problem is with the adb thing..i downloaded the sdk but the sdk manager wont start...and the adb just opens a cmd window and closes ,,,i installed the java and everything needed but i cant open the sdk manager...
Click to expand...
Click to collapse
adb is not a windows program, you have to open a command prompt. go to the folder where adb is located, then SHIFT + RIGHT CLICK -> "Open command window here"
then you should be able to run adb or fastboot
check your device is connected with "adb devices" or "fastboot devices"
nkk71 said:
adb is not a windows program, you have to open a command prompt. go to the folder where adb is located, then SHIFT + RIGHT CLICK -> "Open command window here"
then you should be able to run adb or fastboot
check your device is connected with "adb devices" or "fastboot devices"
Click to expand...
Click to collapse
okkkkkk...i done the erase cash thing but the flash recovery recovery.img commend is giving cannot load......a unknown error..
and yes the recovery.img is in the same folder....
sooo????
'recovery.img' has to be the name you've given the recovery image
This only works coming from KNX01R!
Edit, Camazza has found you can flash the stock 5.0.1 bootloader and sideload the update. See here http://forum.xda-developers.com/g-watch-r/development/manual-ota-update-root-t2969845
Download the update here http://android.clients.google.com/p....signed-lenok-LWX48P-from-KNX01R.149e0c34.zip
1. Root using tonu42's method here http://forum.xda-developers.com/g-watch-r/development/root-root-twrp-r-t2960511
2. After verifying you have root re install the stock recovery for 4.4w.2 from intersectRaven here http://forum.xda-developers.com/g-watch-r/development/stock-boot-recovery-g-watch-r-t2956964 (same command used during rooting).
3. Boot in the system and upload the update
adb push 149e0c34d0ab10d3e356d6301915dcc04552d9db.signed-lenok-LWX48P-from-KNX01R.149e0c34.zip /sdcard/update.zip
4. adb shell
5. cp /sdcard/update.zip /cache/update.zip
6. echo 'boot-recovery ' > /cache/recovery/command
7. echo '--update_package=/cache/update.zip' >> /cache/recovery/command
8. reboot recovery
9. Update installs
Thanks to tonu42 for root and intersectRaven for the stock boot.
Use at your own risk.
Does it remain rooted after the update ?
Would applying the update return the watch to stock? Including upgrading the bootloader and such?
I'm interested in manually updating, but I'd want the watch to be completely stock afterwards.
The bootloader and recovery are updated to stock, but, the device has still been oem unlocked so a fastboot oem lock command will need to be issued. This does remove the lock icon and the watch shows as locked, but, I don't know if lg can tell that is has been unlocked at one time. Root is lost after the update and will need to be reapplied.
nxt said:
Would applying the update return the watch to stock? Including upgrading the bootloader and such?
I'm interested in manually updating, but I'd want the watch to be completely stock afterwards.
Click to expand...
Click to collapse
superdave said:
The bootloader and recovery are updated to stock, but, the device has still been oem unlocked so a fastboot oem lock command will need to be issued. This does remove the lock icon and the watch shows as locked, but, I don't know if lg can tell that is has been unlocked at one time. Root is lost after the update and will need to be reapplied.
Click to expand...
Click to collapse
Yup, I knew that part so didn't ask. But I finally got it working (had issues flashing recovery, had to switch usb ports).
All is good now, thanks!
EDIT: Looks like SuperSU is still installed though (won't run)
Everything else seems stock, I even did oem lock/unlock a few times, recovery is stock
Between step 4 and 5 you need to type su
You'll lose root and I am working on a fix.
Sent from my A0001 using XDA Free mobile app
Why all this manipulations? Why not use ADB Sideload?
superdave said:
The bootloader and recovery are updated to stock, but, the device has still been oem unlocked so a fastboot oem lock command will need to be issued. This does remove the lock icon and the watch shows as locked, but, I don't know if lg can tell that is has been unlocked at one time. Root is lost after the update and will need to be reapplied.
Click to expand...
Click to collapse
I don't think LG cares as long as the lock icon is gone. I've already screwed up and sent them a G2 that was on older radios with TWRP installed, and they sent it back factory flashed to the latest firmware (ZVA at the time).
AntonChernov said:
Why all this manipulations? Why not use ADB Sideload?
Click to expand...
Click to collapse
I'd like to know as well, which method is better/safer, this or ADB sideload?
Adb does not work in Stock recovery that is why twrp is needed, . I am having the same issue with supersu crashing once booted. I have not had a chance to look at it yet. If you shell in and su before the phone boots su works fine though.
Actually there's a faster and safer way that does not involve rooting.
1) Unlock Bootloader
2) Flash 5.0.1 Stock Recovery
3) Enter recovery and sideload update (it works in the new recovery)
4) Profit
Nice, good catch. I'll add that to the first post.
Camazza said:
Actually there's a faster and safer way that does not involve rooting.
1) Unlock Bootloader
2) Flash 5.0.1 Stock Recovery
3) Enter recovery and sideload update (it works in the new recovery)
4) Profit
Click to expand...
Click to collapse
superdave said:
Nice, good catch. I'll add that to the first post.
Click to expand...
Click to collapse
I did the same as following and it's work for me:
recoveryll.bin => 5.0.1 Recovery http://forum.xda-developers.com/g-watch-r/development/stock-boot-recovery-g-watch-r-t2956964
1. adb reboot bootloader
2. fastboot oem unlock
3. fastboot boot recoveryll.bin
4. Select adb sideload then
adb sideload 149e0c34d0ab10d3e356d6301915dcc04552d9db.signed-lenok-LWX48P-from-KNX01R.149e0c34.zip
5. Done
6. Reboot to fastboot
7. fastbook oem lock
5.0.1 Recovery work with adb
kanzone said:
I did the same as following and it's work for me:
recoveryll.bin => 5.0.1 Recovery http://forum.xda-developers.com/g-watch-r/development/stock-boot-recovery-g-watch-r-t2956964
1. adb reboot bootloader
2. fastboot oem unlock
3. fastboot boot recoveryll.bin
4. Select adb sideload then
adb sideload 149e0c34d0ab10d3e356d6301915dcc04552d9db.signed-lenok-LWX48P-from-KNX01R.149e0c34.zip
5. Done
6. Reboot to fastboot
7. fastbook oem lock
5.0.1 Recovery work with adb
Click to expand...
Click to collapse
hey I am trying the same method:
ok, so I unlocked the bootloader, flashed the 5.0.1 recovery, then booted to recovery, selected the adb sideload (the watch now says "Now send the package you want to apply to the device with "adb sideload <filename>"..."
however, in CMD, adb devices is not returning anything. there is no 'new devices connected' sound in windows when removing/replacing the watch from the cradle.
can someone please tell me what am I doing wrong?
b0gd4n said:
hey I am trying the same method:
ok, so I unlocked the bootloader, flashed the 5.0.1 recovery, then booted to recovery, selected the adb sideload (the watch now says "Now send the package you want to apply to the device with "adb sideload <filename>"..."
however, in CMD, adb devices is not returning anything. there is no 'new devices connected' sound in windows when removing/replacing the watch from the cradle.
can someone please tell me what am I doing wrong?
Click to expand...
Click to collapse
adb version
make sure the adb version is > 1.0.32
kanzone said:
adb version
make sure the adb version is > 1.0.32
Click to expand...
Click to collapse
hey, nevermind, I did fastboot flash recovery, not adb boot recovery. I just did that, and I am now uploading the zip....exiting!
thanks!
So wait, the command to flash recovery is what exactly? I've seen 3 different commands on this very page. Also, we do it from the bootloader screen, right?
i am unlocked and rooted with twrp and everytime I try and fastboot the boot img. it says "remote image is not a boot image?
what the hell am i doing wrong?
I have also tried to fastboot a new recovery and I get the same thing?
Are you trying to restore the stock recovery? If so, you fastboot flash recovery recovery.img on the stock image.
cottageboy said:
i am unlocked and rooted with twrp and everytime I try and fastboot the boot img. it says "remote image is not a boot image?
what the hell am i doing wrong?
I have also tried to fastboot a new recovery and I get the same thing?
Click to expand...
Click to collapse
hi,
when I am trying to flash the recovery I get this error:
fastboot flash rcovery recoveryll.img
target reported max download size of 268435456 bytes
sending 'rcovery' (6634 KB)...
OKAY [ 0.312s]
writing 'rcovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.403s
adb version
Android Debug Bridge version 1.0.32
any idea?
do I need to flash the new boot.img before?
Think I may be officially bricked ... tried to sideload the OTA this morning with no luck (looped at Google splash screen). So I flashed the 5.0.1 images and went about my day. Came home and flashed the 5.1 images and looped at the Google splash again ... continued to tinker and play. Long story short, in my idiocy I oem locked. Now I can't flash any .img files cause I am locked, can't unlock because I can't boot into Android and uncheck the stupid box in dev options and trying to sideload the ota .zip again yields: "/dev/block/platform/msm_sdcc.1/by-name/system has been removed R/W; reflash device to reenable OTA updates E:Error in sideload/package.zip (Status 7)" ...
At this point I think I am screwed!! Any suggestions would be GREATLY appreciated!
Can you not get into fastboot and try to OEM unlock that way?
Xaikar said:
Can you not get into fastboot and try to OEM unlock that way?
Click to expand...
Click to collapse
I can get into fastboot but get this when I try to unlock
C:\Android\sdk\platform-tools>fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.000s
C:\Android\sdk\platform-tools>
And of course I cannot check that because I cannot boot into Android
So it currently says device locked?
Xaikar said:
So it currently says device locked?
Click to expand...
Click to collapse
10-4
I can get into stock recovery, but I don't know of anything to flash with the stock recovery and adb sideloading 5.1 isn't working
http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
There's a thread about this over at the Nexus 9 help forum. Might want to check there.
Xaikar said:
http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
Click to expand...
Click to collapse
Can't flash the images while locked, thanks though
ChristianJay said:
There's a thread about this over at the Nexus 9 help forum. Might want to check there.
Click to expand...
Click to collapse
Ah, thanks! Any idea which section?
Edit: Found it!
YankInDaSouth said:
Ah, thanks! Any idea which section?
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-9/help/warning-locking-bootloader-disabling-t2951312
Have you tried booting TWRP from fastboot? Maybe then you could install a ROM to boot into android.
fastboot boot recovery recovery.img
WugFresh Nexus Root Toolkit
Try the "Flash Stock + Unroot" option. It should take you back to square 1.
ajjames01 said:
Have you tried booting TWRP from fastboot? Maybe then you could install a ROM to boot into android.
fastboot boot recovery recovery.img
Click to expand...
Click to collapse
Custom recovery isn't currently on the device ...
Dusty Rhodes said:
WugFresh Nexus Root Toolkit
Try the "Flash Stock + Unroot" option. It should take you back to square 1.
Click to expand...
Click to collapse
Tried that too ... but the .img's cannot be flashed while locked, keeps failing
If you have TWRP on the device can you adb push a ROM to it and flash it so you can boot android and tick the "enable OEM unlock" box.
ajjames01 said:
If you have TWRP on the device can you a ROM to it and flash it so you can boot android and tick the "enable OEM unlock" box.
Click to expand...
Click to collapse
I don't have TWRP, sorry that was a typo. It's stock recovery as I was trying to go fully stock 5.1 ...
@YankInDaSouth
Did you try booting twrp and not flashing it and go from there?
Fastboot boot recovery twrp.img
when Google decided to add the "OEM Lock" checkbox they should have committed to every Nexus device also having SD card capability, not only for the convenience that SD cards bring but also to be able to load the images that way in the event of a catastrophe.
But I guess forcing everyone into buying cloud storage is the new modus operandi.
Try the following commands, one after the other:
fastboot format userdata
fastboot format cache
fastboot reboot-bootloader
fastboot oem unlock (if it works, great, if not, go to the next one below)
fastboot reboot
efrant said:
Try the following commands, one after the other:
fastboot format userdata
fastboot format cache
fastboot reboot-bootloader
fastboot oem unlock (if it works, great, if not, go to the next one below)
fastboot reboot
Click to expand...
Click to collapse
Still get the message about checking the box in dev options ...
Not sleeping tonight huh bro? I know the feeling when this **** happens, it sucks. I think someone will come up with a work around, a lot of brains around here.
Sent from my Nexus 9 using XDA Free mobile app
Hi guys
I want to install android 8 (emuı or custom rom) but the oreo twrp doesnt installing, ı tried every time and show an error, how to fix this thing?
kadirc5 said:
Hi guys
I want to install android 8 (emuı or custom rom) but the oreo twrp doesnt installing, ı tried every time and show an error, how to fix this thing?
Click to expand...
Click to collapse
You must give more info so that anyone can understand your problem. Which steps did you follow, which error is it...??? BTW better post it in its right thread (Oreo flashing guide)
CarlosAG10 said:
You must give more info so that anyone can understand your problem. Which steps did you follow, which error is it...??? BTW better post it in its right thread (Oreo flashing guide)
Click to expand...
Click to collapse
First part, is the twrp installation on the fastboot mode. I wrote this code > fastboot flash recovery_ramdisk recovery_ramdisk.img and pressed enter
Sending... Ok
Writing...
FAİLED
kadirc5 said:
First part, is the twrp installation on the fastboot mode. I wrote this code > fastboot flash recovery_ramdisk recovery_ramdisk.img and pressed enter
Sending... Ok
Writing...
FAİLED
Click to expand...
Click to collapse
Try sending command "fastboot devices". Does a number appear? In that case, check your recovery_ramdisk img and directory
CarlosAG10 said:
Try sending command "fastboot devices". Does a number appear? In that case, check your recovery_ramdisk img and directory
Click to expand...
Click to collapse
Yes, shows a number
How can ı check?
kadirc5 said:
Yes, shows a number
How can ı check?
Click to expand...
Click to collapse
Download the files again and make sure you are correctly using fastboot
since you rebranded the device, you should unlock the bootloader again. fastboot doesn't allow running command with a locked bootloader
fastboot oem unlock yourcodehere
Striike said:
since you rebranded the device, you should unlock the bootloader again. fastboot doesn't allow running command with a locked bootloader
fastboot oem unlock yourcodehere
Click to expand...
Click to collapse
Im gonna try at the weekend thanks
Hey folks,
has anyone already successfully rooted Android 13? If yes, is there an instruction available?
Thanks!
refresh5 said:
Hey folks,
has anyone already successfully rooted Android 13? If yes, is there an instruction available?
Thanks!
Click to expand...
Click to collapse
Just patch boot.img and flash it
Can we update firmware after root? If not where can we download full firmware? This is my first Sony phone so I don't know where to download full firmware and how to flash it
Adnan008 said:
Can we update firmware after root? If not where can we download full firmware? This is my first Sony phone so I don't know where to download full firmware and how to flash it
Click to expand...
Click to collapse
Xperiafirm on xda to download full fw and newflasher to flash it
King081 said:
Xperiafirm on xda to download full fw and newflasher to flash it
Click to expand...
Click to collapse
do we lose data when flashing firmware?
Adnan008 said:
do we lose data when flashing firmware?
Click to expand...
Click to collapse
You can choose using newflasher
King081 said:
Just patch boot.img and flash it
Click to expand...
Click to collapse
Can you tell me how?
zaxdamian said:
Can you tell me how?
Click to expand...
Click to collapse
Use unsin to get boot.img from stock file, then install magisk apk, use magisk to patch boot.img then flash in fastboot
King081 said:
Use unsin to get boot.img from stock file, then install magisk apk, use magisk to patch boot.img then flash in fastboot
Click to expand...
Click to collapse
I have stock file but dont know which file unsin. When I try to instal twrp, "Download is not allowed on locked devices". How to unlock bootloader? Command from cmd dosen't work
zaxdamian said:
I have stock file but dont know which file unsin. When I try to instal twrp, "Download is not allowed on locked devices". How to unlock bootloader? Command from cmd dosen't work
Click to expand...
Click to collapse
I don't know what twrp you have, because we don't have one here and clearly your phones bootloader locked, this is about root and not twrp
Ok. I cant unlock bootloader, so how to get boot.img from stock file?
Unlock bootloader:
https://developer.sony.com/open-source/aosp-on-xperia-open-devices/get-started/unlock-bootloader
I tried it. Either I'm doing something wrong or it's not working
Everything works, I unlocked it myself, I just don't remember which command:
fastboot oem unlock
or
fastboot flash unlock
fastboot devices ok
fastboot oem unlock 0xunlockcode "FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed"
fastboot oem unlock unlockcode the same
fastboot flash unlock "unknown partition 'unlock' fastboot: error: cannot determine image filename for 'unlock'"
I think the problem is with entering fastboot mode. When "phone is turned off and press and hold the Fastboot key Volume up* when you connect your phone to the computer" i have blue diode but in SDk no devices
On comand fastboot flash unlock i have "fastboot: error: ANDROID_PRODUCT_OUT not set"
zaxdamian said:
fastboot devices ok
fastboot oem unlock 0xunlockcode "FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed"
fastboot oem unlock unlockcode the same
fastboot flash unlock "unknown partition 'unlock' fastboot: error: cannot determine image filename for 'unlock'"
I think the problem is with entering fastboot mode. When "phone is turned off and press and hold the Fastboot key Volume up* when you connect your phone to the computer" i have blue diode but in SDk no devices
Click to expand...
Click to collapse
Did you do that in fastboot or fastbootD
Fastboot D