Related
I tried using the simple root and clockwork mod method and now my a100 keeps cycling thru bootloaderversion 0.03.06-ics-ics (unlock mode) with green acer logo. If I reboot holding power+down sd update command recovery
update_package=sd card update.zip
booting recovery kernal image
then it starts cycling again.
Please can someone help!
same
Same thing here (or at least very similar). Hoping there's a simple solution like the "Odin back to stock" I can do on my SGS phone.
are you sure that the bootloader say "unlock mode"?
If so, then try this.
try this
Install the USB drivers on your PC if you haven't done it already. ( http://global-download.acer.com/GDF...A TAB&Step3=A100&OS=a08&LC=en&BC=Acer&SC=PA_6 )
install android SDK. ( http://developer.android.com/sdk/index.html )
copy the update.zip file to your SD card root.
download TWRP recovery ( http://forum.xda-developers.com/showthread.php?t=1608152 ) and place it in the platform-tools dir where the SDK was installed ( ex. C:\Program Files\Android\android-sdk\platform-tools )
Once all that is done follow these steps
1) boot the tablet to fastboot mode
2) run command prompt on PC (cmd.exe)
3) cd to the platorm-tools dir
4) type the following lines one at a time.
adb.exe
fastboot erase recovery
fastboot flash recovery NAMEOFRECOVERY.img (ex. recovery-A100ICS-TWRP.img)
5) hold the vol down button on the tablet
6) type fastboot reboot.
The tablet should now reboot to the recovery program. Goto settings and mount the external SD card, then flash the update.zip by going to install.
Hope this helps
[email protected] said:
I tried using the simple root and clockwork mod method and now my a100 keeps cycling thru bootloaderversion 0.03.06-ics-ics (unlock mode) with green acer logo. If I reboot holding power+down sd update command recovery
update_package=sd card update.zip
booting recovery kernal image
then it starts cycling again.
Please can someone help!
Click to expand...
Click to collapse
Did you rename/delete /etc/install-recovery.sh ?
I think you're not. Try to make hard reset, then boot normaly rename/delete this file and after that flash recovery again, it should work.
All it's explained here.
Thank you
TheBlackshinobi said:
are you sure that the bootloader say "unlock mode"?
If so, then try this.
try this
Install the USB drivers on your PC if you haven't done it already. ( http://global-download.acer.com/GDF...A TAB&Step3=A100&OS=a08&LC=en&BC=Acer&SC=PA_6 )
install android SDK. ( http://developer.android.com/sdk/index.html )
copy the update.zip file to your SD card root.
download TWRP recovery ( http://forum.xda-developers.com/showthread.php?t=1608152 ) and place it in the platform-tools dir where the SDK was installed ( ex. C:\Program Files\Android\android-sdk\platform-tools )
Once all that is done follow these steps
1) boot the tablet to fastboot mode
2) run command prompt on PC (cmd.exe)
3) cd to the platorm-tools dir
4) type the following lines one at a time.
adb.exe
fastboot erase recovery
fastboot flash recovery NAMEOFRECOVERY.img (ex. recovery-A100ICS-TWRP.img)
5) hold the vol down button on the tablet
6) type fastboot reboot.
The tablet should now reboot to the recovery program. Goto settings and mount the external SD card, then flash the update.zip by going to install.
Hope this helps
Click to expand...
Click to collapse
I'm going to try this, one question though. My computer does not read the tablet anymore even though I have the drivers installed will it still work? Yes I'm a serious noob, but I'm trying...and thank you for your help it is much appreciated.
cpu doesnt read tablet anymore
[email protected] said:
I'm going to try this, one question though. My computer does not read the tablet anymore even though I have the drivers installed will it still work? Yes I'm a serious noob, but I'm trying...and thank you for your help it is much appreciated.
Click to expand...
Click to collapse
Okay, I downloaded everything but my computer doesnt recognize my a100 anymore, only if I put the tablet into fastboot then it see's it. My tablet just keeps on rebooting itself repeatedly unless I go into fastboot. Please tell me I dont have a paperweight.
were getting close
Blackshinobi or anyone that can help,
I'm getting close. I make it to: "fast boot flash recovey" cmd prompt
I get two different errors depending hoew I type the cmd prompt:
1. "fastboot flash recovery recovery-A100ICS-TWRP.img"
error (can not load recovery-A100ICS-TWRP.img)
2. "fastboot flash recovery-A100ICS-TWRP.img"
error ( cannort determine image file name for 'recovery-A100ICS-TWRP.img)
I was a little confuse on proper cmd line prompt, but I'm thinking #2 is the correct way.
Thanks so much for your help!
pfisher101 said:
Blackshinobi or anyone that can help,
I'm getting close. I make it to: "fast boot flash recovey" cmd prompt
I get two different errors depending hoew I type the cmd prompt:
1. "fastboot flash recovery recovery-A100ICS-TWRP.img"
error (can not load recovery-A100ICS-TWRP.img)
2. "fastboot flash recovery-A100ICS-TWRP.img"
error ( cannort determine image file name for 'recovery-A100ICS-TWRP.img)
I was a little confuse on proper cmd line prompt, but I'm thinking #2 is the correct way.
Thanks so much for your help!
Click to expand...
Click to collapse
That's awesome news!!!
Number 1 is the correct command.
Just making sure you are actually in fastboot (bootloader) mode. On the command-promt type "fastboot devices", if you see the result below, then you're good
? fastboot (yes that's a question mark)
Now be sure you are in the directory with the recovery image and issue number 1 command (fastboot flash recovery whatever-recovery.img). If you get some errors, be sure to check the MD5 hash of the recovery image cuz it could be a corrupted download.
Of course, you can't flash the custom recovery if you still have a locked bootloader.
you guys rock..even closer
Thank-you everyone ..I am soooo close. I did get the recovery image to load (I accidently had it in android-sdk and not platform-tools...oooops my bad). Now I can reboot to recovery and install the update.zip off my external sd card. However after I install the update.zip and reboot, I still get stuck on the acer screen (bootloader version 0.03.06-ICS (Unlock Mode) at top with acer logo in green at bottom.
Which update.zip am I suppose to be using? Currently I am trying to install one of the stock ROMS from the developer section of this forum. Am I suppose to be using a specific one?
Thanks again, I know I'm close. My tablet has been brick'd for weeks and I'm dedicated to getting it back now that I have time.
pfisher101 said:
Thank-you everyone ..I am soooo close. I did get the recovery image to load (I accidently had it in android-sdk and not platform-tools...oooops my bad). Now I can reboot to recovery and install the update.zip off my external sd card. However after I install the update.zip and reboot, I still get stuck on the acer screen (bootloader version 0.03.06-ICS (Unlock Mode) at top with acer logo in green at bottom.
Which update.zip am I suppose to be using? Currently I am trying to install one of the stock ROMS from the developer section of this forum. Am I suppose to be using a specific one?
Thanks again, I know I'm close. My tablet has been brick'd for weeks and I'm dedicated to getting it back now that I have time.
Click to expand...
Click to collapse
Congrats resurrecting your tab! Gotta be a great relief!
How about Flexreaper ROM? It will require full wipe before flashing: in recovery wipe/factory reset, wipe system, wipe cache, wipe dalvik cache, flash Flexreaper ROM zip file. This is basic guide, follow detailed instructions on this ROM thread (link is in my sig).
Sent from my A100 using xda premium
not quite recovered yet. I still get the hang on Acer screen. anyone know why? I will try flexreaper
I'm BACK
Thanks to all. I'm back up. flexreaper did work.. I hope the guy who actually started this thread is as lucky.
Not so lucky
I'm still stuck my pc doesnt read my acer a100 still....any helps out there?
[email protected] said:
I'm still stuck my pc doesnt read my acer a100 still....any helps out there?
Click to expand...
Click to collapse
Power down the unit. Set screen lock in the up position. Hold volume down and power. When powered on keep holding the vol down button. Then toggle the screen lock to down.
That should do a factory reset.
Then put a stock rom in the root of SD Card. Volume up then power until let the tablet recover.
This worked for me.
did u install the drivers from an earlier post? Also when you power up you your tablet you need to boot into fastboot mode? You're certain you have done both of these things?
I am unable to connect to, my pc doesnt recognize my acer anymore...unless by sd card you mean external card? Thank you for trying to help. I'm a serious noob but trying hard.
i'm in a similar situation. i accidentally deleted the build.prop file and rebooted. now it only displays a black screen after the acer logo drops out. my boot loader is locked but i cant install the mtp usb drivers to fix anything. think i have a paperweight now.
mechpilot_z said:
i'm in a similar situation. i accidentally deleted the build.prop file and rebooted. now it only displays a black screen after the acer logo drops out. my boot loader is locked but i cant install the mtp usb drivers to fix anything. think i have a paperweight now.
Click to expand...
Click to collapse
that's easily fixed, install this through stock recovery, http://forum.xda-developers.com/showthread.php?t=1611696
eww245 said:
that's easily fixed, install this through stock recovery, http://forum.xda-developers.com/showthread.php?t=1611696
Click to expand...
Click to collapse
tried. i had no alternative recovery on it. i could not get the sd card mounted to push the zip to it. both adb and fast boot wont see my tablet. every attempt at unlocking fast boot wouldn't work. I tried to check in device manager to see if it was connected, the driver was working but it had an error message "Device can not start (Code 10)"
My pc only sees my tablet when I boot it into fastboot mode and sees it as an adb interface...Is there anything I can do from there?
I have a nexus 7 2013 LTE build KOT49H
I initially managed to unlock and root using nrt 1.8...everything was perfect...there was some confusion getting adb setup though..
(for WugFresh...your instructions are fantastic but you should add a line to "check your device for the message to accept a connection for adb and select ok"...I found myself waiting and waiting, staring at my computer screen thinking that the nrt was hanging when all I needed to do was press "ok" on my device.)
Like I said...everything was perfect but I had to go one step further...
I then installed cyanogenmod 10.2 using twrp...tihs also went fine but I hated it and wanted to get back to my original google os. I had a really hard time getting adb set up once cyanogen was installed but once I finally did I was able to get back to stock again using nrt 1.8.
So now I'm back to stock image KOT49H. Everything runs fine and I see the unlocked logo when I boot so I assume I'm still unlocked.
Here's the problem..
When I try to root now, (I always run the NRT driver test until I get "success" message first) my device hangs on the "Booting modified boot.img to enable..." message.
And I mean hangs...can't even power it down without popping the cover and disconnecting the battery! Thankfully this gets me back to a running device but I still want to root this thing.
Any idea what might be wrong or where I should go to from here?
Thanks for any help you can suggest!
Did you re-enable USB debugging? Another thing is to switch to PTP mode instead of MTP. If none of that is the issue, it may be drivers, fire up wugs toolkit, hook up your device, and click the button "Full Driver Installation Guide", skip to Step 3 tab, and run the "Full Driver Test", if it fails then you're going to need to run through the steps in that "Full Driver Installation Guide, going through each step.
Well all you need to do for root is flash supersu.zip binary. If you have twrp on your device, boot to recovery. When you power on, hold down the volume down button also. When in boot loader mode, select recovery. If its not booting, you could just wipe to factory reset. Flash your supersu zip you'll be good.
Sent from my Nexus 7 using xda app-developers app
mdamaged said:
Did you re-enable USB debugging? Another thing is to switch to PTP mode instead of MTP. If none of that is the issue, it may be drivers, fire up wugs toolkit, hook up your device, and click the button "Full Driver Installation Guide", skip to Step 3 tab, and run the "Full Driver Test", if it fails then you're going to need to run through the steps in that "Full Driver Installation Guide, going through each step.
Click to expand...
Click to collapse
Thanks for the response...
All these check...I do have to switch to PTP to get adb functional and I do get success on the full driver test before I try rooting...device still hangs at "Booting modified boot.img to enable running privileged commands" message and then wont power down without disconnecting battery...
Which recovery are you on stock or still on twrp? If still on twrp, you might want to try flashing the supersu.zip yourself, just get the latest SuperSU put it on your device, and boot into twrp and manually flash it like datallboy suggests, this eliminates the PC/drivers/usb connection as a possible issue.
If you are on stock recovery either flash twrp, or if you want to keep stock recovery, you can boot into twrp temporarily without replacing the stock recovery.
datallboy said:
Well all you need to do for root is flash supersu.zip binary. If you have twrp on your device, boot to recovery. When you power on, hold down the volume down button also. When in boot loader mode, select recovery. If its not booting, you could just wipe to factory reset. Flash your supersu zip you'll be good.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the suggestions...
I lost twrp when I went back to stock build.
Sorry...I'm real green at all of this...
You think I should:
power up to fastboot mode...select boot loader mode...then select recovery to see if it boots?
You need to be real clear for me, I'm a total newb
I would need a link to thorough instructions for wiping to factory reset and flashing the supersu.zip...I do have adt installed and have my path modified so that I can run instructions like "adb devices" in a command window but I'm unclear as to where to place files so they will be seen if I try to flash them via adt. (like I say...this is all new to me and I'm not even sure if that last sentence makes sense)
mdamaged said:
Which recovery are you on stock or still on twrp? If still on twrp, you might want to try flashing the supersu.zip yourself, just get the latest SuperSU put it on your device, and boot into twrp and manually flash it like datallboy suggests, this eliminates the PC/drivers/usb connection as a possible issue.
If you are on stock recovery either flash twrp, or if you want to keep stock recovery, you can boot into twrp temporarily without replacing the stock recovery.
Click to expand...
Click to collapse
Thanks for responding!
TWRP was wiped when I went back to stock build...I'm assuming I have stock recovery now but when your device freezes in fastboot mode and wont power down without pulling the battery you cable you gotta wonder if you have any recovery at all!!!
I'll need instruction on how to flash twrp again...but I believe that this is the step that WugFresh's NRT is trying to do when the device freezes.
SMELZBAD said:
Thanks for responding!
TWRP was wiped when I went back to stock build...I'm assuming I have stock recovery now but when your device freezes in fastboot mode and wont power down without pulling the battery you cable you gotta wonder if you have any recovery at all!!!
I'll need instruction on how to flash twrp again...but I believe that this is the step that WugFresh's NRT is trying to do when the device freezes.
Click to expand...
Click to collapse
I typed this up on the fly so pardon any mistakes, there's more than one way to do this, but I'm basing this on already having wugs toolkit installed and updated and configured for your device on the PC you're going to do this on.
Plug device in, enable USB debugging mode, connect to PC, verify you can access your device through the PC, get the latest UPDATE-SuperSU-v1.XX zip, save it to your device (in the root of the sdcard).
EDIT: OR, even better, you can just boot the device and download it with chrome or whatever and save it to the sdcard, then you can continue:
Open windows explorer and navigate to (assuming you picked the default install directory):
C:\Program Files (x86)\WugFresh Development\data
...in that window, hold down shift, right click, select "Open command windows here", in it, type:
adb devices
...if nothing shows up post back (screenshot would be nice), if your device shows up, then open another windows explorer window and navigate to:
C:\Program Files (x86)\WugFresh Development\data\Recovery_Custom\TWRP\
...and copy the img (mine is openrecovery-twrp-2.6.3.1-flo.img) file you see in there to the other explorer window I told you to open earlier, now assuming you put the SuperSU file on your device in the root folder of the device, you should be able to do:
fastboot boot openrecovery-twrp-2.6.3.1-flo.img
This should reboot your device and boot twrp (this method does not replace whatever recovery you have on there now).
If you want to flash twrp and replace your current recovery you'd want to do:
fastboot flash recovery openrecovery-twrp-2.6.3.1-flo.img
Then once in twrp recovery you can select flash file, navigate to the UPDATE-SuperSU-v1.XX.zip file on your device, select it, and swipe to flash, reboot, run/install busybox and see what happens..it will let you know if there is a problem with root.
mdamaged said:
I typed this up on the fly so pardon any mistakes, there's more than one way to do this, but I'm basing this on already having wugs toolkit installed and updated and configured for your device on the PC you're going to do this on.
Plug device in, enable USB debugging mode, connect to PC, verify you can access your device through the PC, get the latest zip, save it to your device (in the root of the sdcard).
Open windows explorer and navigate to (assuming you picked the default install directory):
C:\Program Files (x86)\WugFresh Development\data
...in that window, hold down shift, right click, select "Open command windows here", in it, type:
adb devices
...if nothing shows up post back (screenshot would be nice), if your device shows up, then open another windows explorer window and navigate to:
C:\Program Files (x86)\WugFresh Development\data\Recovery_Custom\TWRP\
...and copy the img (mine is openrecovery-twrp-2.6.3.1-flo.img) file you see in there to the other explorer window I told you to open earlier, now assuming you put the SuperSU file on your device in the root folder of the device, you should be able to do:
fastboot boot openrecovery-twrp-2.6.3.1-flo.img
This should reboot your device and boot twrp (this method does not replace whatever recovery you have on there now).
If you want to flash twrp and replace your current recovery you'd want to do:
fastboot flash recovery openrecovery-twrp-2.6.3.1-flo.img
Then once in twrp recovery you can select flash file, navigate to the UPDATE-SuperSU-v1.XX.zip file on your device, select it, and swipe to flash, reboot, run busybox and see what happens.
Click to expand...
Click to collapse
Thanks a ton for the instruction!
I'm starting to make sense of this.
Found some other instruction for getting twrp back on the device which I think I'll try before flashing the superSU:
They're exactly what you're describing. I've also figured out where the flashboot.exe stuff is on my computer and added twp.img file there. I'' try getting twrp on and then I'll flash the superSU via twrp.
It'll probably be tomorrow before I get a chance to try all this but I'll be sure to post back once I do.
I'm still in the dark as to why missing this superSU thingy would be causing the device to freeze up the way it does when I try to root using WugFresh's NRT...I thought that flashing twrp and superSU is what the NRT is trying to do when it tries to root my device???
Anyway gtg...thanks all for assisting...I'll post back after the flash attempts...hopefully with happy news!
SMELZBAD said:
Thanks a ton for the instruction!
I'm starting to make sense of this.
Found some other instruction for getting twrp back on the device which I think I'll try before flashing the superSU:
They're exactly what you're describing. I've also figured out where the flashboot.exe stuff is on my computer and added twp.img file there. I'' try getting twrp on and then I'll flash the superSU via twrp.
It'll probably be tomorrow before I get a chance to try all this but I'll be sure to post back once I do.
I'm still in the dark as to why missing this superSU thingy would be causing the device to freeze up the way it does when I try to root using WugFresh's NRT...I thought that flashing twrp and superSU is what the NRT is trying to do when it tries to root my device???
Anyway gtg...thanks all for assisting...I'll post back after the flash attempts...hopefully with happy news!
Click to expand...
Click to collapse
Wug's toolkit is doing exactly that, the main difference in doing it manually is we get to see where the problem is.
If this fails then I would probably say you should backup anything on your device you don't want wiped, and try one click restore and try rooting again.
Good luck.
mdamaged said:
I typed this up on the fly so pardon any mistakes, there's more than one way to do this, but I'm basing this on already having wugs toolkit installed and updated and configured for your device on the PC you're going to do this on.
Plug device in, enable USB debugging mode, connect to PC, verify you can access your device through the PC, get the latest UPDATE-SuperSU-v1.XX zip, save it to your device (in the root of the sdcard).
EDIT: OR, even better, you can just boot the device and download it with chrome or whatever and save it to the sdcard, then you can continue:
Open windows explorer and navigate to (assuming you picked the default install directory):
C:\Program Files (x86)\WugFresh Development\data
...in that window, hold down shift, right click, select "Open command windows here", in it, type:
adb devices
...if nothing shows up post back (screenshot would be nice), if your device shows up, then open another windows explorer window and navigate to:
C:\Program Files (x86)\WugFresh Development\data\Recovery_Custom\TWRP\
...and copy the img (mine is openrecovery-twrp-2.6.3.1-flo.img) file you see in there to the other explorer window I told you to open earlier, now assuming you put the SuperSU file on your device in the root folder of the device, you should be able to do:
fastboot boot openrecovery-twrp-2.6.3.1-flo.img
This should reboot your device and boot twrp (this method does not replace whatever recovery you have on there now).
If you want to flash twrp and replace your current recovery you'd want to do:
fastboot flash recovery openrecovery-twrp-2.6.3.1-flo.img
Then once in twrp recovery you can select flash file, navigate to the UPDATE-SuperSU-v1.XX.zip file on your device, select it, and swipe to flash, reboot, run/install busybox and see what happens..it will let you know if there is a problem with root.
Click to expand...
Click to collapse
Followed your instructions...everything went as it should until I got to:
fastboot boot openrecovery-twrp-2.6.3.1-deb.img
instead of rebooting the device I only got waiting for device message in command window...
is device supposed to be put in bootloader mode before entering this instruction maybe???
okay I got twrp to flash...took like .7 seconds so I guess it was already on there...
when I tried to flash UPDATESuperSU (and by flash I assume you mean install???)
I get:
Updating partition details...
E: Unable to open zip file.
Error flashing zip ' /sdcard/UPDATE-SuperSU-v1.89.zip
Updating partition details...
and the in red underneath: Failed
and the 3 twrp button choices of home Wipe cache/davlik and Reboot System
I selected reboot system and then got message "this device is not rooted swipe to install SuperSU now
I swiped...and the system has rebooted and I now have SuperSU installer app icon in apps bit after running root checker I get device is not properly rooted message
I then ran the SuperSU installer app and it gave me an option to update via the play store...which I did...then ran SuperuserSU which was now updated and installed and it completed rooting...after rebooting the device Root Checker now shows device properly rooted!
THANKS A TON GUYS!!!
SMELZBAD said:
okay I got twrp to flash...took like .7 seconds so I guess it was already on there...
when I tried to flash UPDATESuperSU (and by flash I assume you mean install???)
I get:
Updating partition details...
E: Unable to open zip file.
Error flashing zip ' /sdcard/UPDATE-SuperSU-v1.89.zip
Updating partition details...
and the in red underneath: Failed
and the 3 twrp button choices of home Wipe cache/davlik and Reboot System
I selected reboot system and then got message "this device is not rooted swipe to install SuperSU now
I swiped...and the system has rebooted and I now have SuperSU installer app icon in apps bit after running root checker I get device is not properly rooted message
I then ran the SuperSU installer app and it gave me an option to update via the play store...which I did...then ran SuperuserSU which was now updated and installed and it completed rooting...after rebooting the device Root Checker now shows device properly rooted!
THANKS A TON GUYS!!!
Click to expand...
Click to collapse
Curious. It sounds like a permissions problem, not sure if fix permissions would have helped (no need to try if it's working as it should).
Oh well, glad to help and that it's sorted.
mdamaged said:
Curious. It sounds like a permissions problem, not sure if fix permissions would have helped (no need to try if it's working as it should).
Oh well, glad to help and that it's sorted.
Click to expand...
Click to collapse
Ya...something likely still abit wacky...I'll be sure to post if anything weird starts happening but for now all is good...I'm definitely rooted though...I was just able to mount a flash drive via Stick Mount and run a video off of it!
Hi. I recently rooted my phone Xperia S (LT26i) and unlocked its bootloader. I had installed CWM and TWRP recovery in the phone and I have ADB and Fastboot(Android SDK) in my computer. I had earlier flashed CWM but it wasn't working so I flashed TWRP. I had downloaded a custom ROM and Gapps in the PC and I extracted the zip files and copied them into the phone (this was a mistake). I went into TWRP and did factory reset, erased cache and wiped dalvik cache unknowingly:silly: Now I can't flash ROM or Gapps and I cannot boot normally. Earlier, ADB used to recognize the device and now it doesn't. When I turn on the phone, the Sony logo appears and pink light glows. But it doesn't go beyond that. It repeatedly restarts the phone till the splash screen. Now I can't boot the phone normally Please help, guys.
P.S. I saw a post suggesting to enter a code in the Terminal module of TWRP but it's not working.
Megaiamepic said:
Hi. I recently rooted my phone Xperia S (LT26i) and unlocked its bootloader. I had installed CWM and TWRP recovery in the phone and I have ADB and Fastboot(Android SDK) in my computer. I had earlier flashed CWM but it wasn't working so I flashed TWRP. I had downloaded a custom ROM and Gapps in the PC and I extracted the zip files and copied them into the phone (this was a mistake). I went into TWRP and did factory reset, erased cache and wiped dalvik cache unknowingly:silly: Now I can't flash ROM or Gapps and I cannot boot normally. Earlier, ADB used to recognize the device and now it doesn't. When I turn on the phone, the Sony logo appears and pink light glows. But it doesn't go beyond that. It repeatedly restarts the phone till the splash screen. Now I can't boot the phone normally Please help, guys.
P.S. I saw a post suggesting to enter a code in the Terminal module of TWRP but it's not working.
Click to expand...
Click to collapse
I'v got almost similar problem right now, but beyond that I'v flashed custom kernel to mine.
I hope someone will post here soon
edit: the kernel name is Open SEMC
but I think I can get to fast boot, so changing kernel should not be problem. But how to get some ROM to the phone, when I can't connect it anyhow?
Megaiamepic said:
Earlier, ADB used to recognize the device and now it doesn't. When I turn on the phone, the Sony logo appears and pink light glows. But it doesn't go beyond that. It repeatedly restarts the phone till the splash screen. Now I can't boot the phone normally Please help, guys.
P.S. I saw a post suggesting to enter a code in the Terminal module of TWRP but it's not working.
Click to expand...
Click to collapse
What do You menan by now not recognizing in adb? While being in adb? Are You able to boot to twrp?
fipsix said:
I'v got almost similar problem right now, but beyond that I'v flashed custom kernel to mine.
I hope someone will post here soon
edit: the kernel name is Open SEMC
but I think I can get to fast boot, so changing kernel should not be problem. But how to get some ROM to the phone, when I can't connect it anyhow?
Click to expand...
Click to collapse
If You both are able to boot into recovery(twrp), I recommend You boot into twrp, connect the phone to pc. Then Let the drivers install. After it, start the adb, use this command to command to check if Your device is connected:
Code:
adb devices
Copy the ROM zip to the folder of adb.
Then push the file to sdcard using:
Code:
adb push finlename.zip /sdcard
where filename.zip is Your ROM.
Mirhawk said:
What do You menan by now not recognizing in adb? While being in adb? Are You able to boot to twrp?
If You both are able to boot into recovery(twrp), I recommend You boot into twrp, connect the phone to pc. Then Let the drivers install. After it, start the adb, use this command to command to check if Your device is connected:
Code:
adb devices
Copy the ROM zip to the folder of adb.
Then push the file to sdcard using:
Code:
adb push finlename.zip /sdcard
where filename.zip is Your ROM.
Click to expand...
Click to collapse
I tried using the adb command but it says "error device not found"
Megaiamepic said:
I tried using the adb command but it says "error device not found"
Click to expand...
Click to collapse
You are using windows, right? Do You see the phone connected in the "Device Manager"? It might but under "Other Devices" by the name "Sony Xperia S"
Mirhawk said:
You are using windows, right? Do You see the phone connected in the "Device Manager"? It might but under "Other Devices" by the name "Sony Xperia S"
Click to expand...
Click to collapse
That's what I've done in the end. Bud I had problem with drivers for my xperia, it seemed that drivers were wrong or something. So I uninstalled them, downloaded new one and voila :good:
fipsix said:
That's what I've done in the end. Bud I had problem with drivers for my xperia, it seemed that drivers were wrong or something. So I uninstalled them, downloaded new one and voila :good:
Click to expand...
Click to collapse
Do post which drivers You installed with a link. It might help the other member.
Mirhawk said:
Do post which drivers You installed with a link. It might help the other member.
Click to expand...
Click to collapse
Ooh sorry, totally forgot about that. I dont have direct link, but I will upload them somewhere tommorow.
drivers
I hope those are the right ones, because I donwloaded tons of em
http://ulozto.cz/x4tSiM6N/drivers-fastboot-adb-flashtool-by-velcis-ribeiro-rar
I everyone,
I need your help, I tried to install a new rom (AICP : this one) , and somehow forgot to do a backup.
When I boot I only get the swirling logo, never get to fully load.
The phone is not bricked, I can still access the bootloader / fastboot and my recovery, so I could simply flash another rom... but I can't figure how to get the zip file on the /sdcard.
I can't use adb sideload or push, I have HTC sync and android sdk installed, I have no problem to use fastboot commands, so I guess I don't have any driver problem, but adb devices never shows my phone (Tried while off, booted on bootloader, on fastboot, and on recovery, never shows up when I try adb devices)
On windows I get a driver error when plugging my phone while in recovery, but I don't find how to install it.
So... is there a way to mount the /sdcard/ as an external drive in windows or ubuntu ? Or do you have a workaround for adb ?
Thanks a lot !
Vincent
Hello,
Something interesting happened... I have rebooted to fastboot, unlocked, jumped back to fastboot, and there were few thing to select "reboot" "shutdown" "reboot bootloader" "reboot recovery". I thought to myself, well lets look how does the stock recovery looks like... And now I'm stuck with this.
https://youtu.be/ea1gZ_KohAw
It doesn't matter how long I press the power button... It still reboots into this nonsense...
So... Anyone encountered the same problem?
Should I just wait until the battery will drain?
On the screen it says:
E:failed to mount /cache (invalid argument)
E:Can't mount /cache/recovery/last_locale
EDIT: SOLVED
Ereniemis said:
Hello,
Something interesting happened... I have rebooted to fastboot, unlocked, jumped back to fastboot, and there were few thing to select "reboot" "shutdown" "reboot bootloader" "reboot recovery". I thought to myself, well lets look how does the stock recovery looks like... And now I'm stuck with this.
https://youtu.be/ea1gZ_KohAw
It doesn't matter how long I press the power button... It still reboots into this nonsense...
So... Anyone encountered the same problem?
Should I just wait until the battery will drain?
On the screen it says:
E:failed to mount /cache (invalid argument)
E:Can't mount /cache/recovery/last_locale
EDIT: SOLVED
Click to expand...
Click to collapse
how did you solve??
xlylegaman said:
how did you solve??
Click to expand...
Click to collapse
Okay...
1) booted to fastboot through http://forum.xda-developers.com/huawei-watch/development/guide-boot-fastboot-mode-t3225382
2) booted to recovery, not with "FLASH" just with "fastboot boot twrp.img" (e.g. http://forum.xda-developers.com/hua...p-twrp-2-8-7-0-recovery-huawei-watch-t3224714 )
3) went to "reboot" in TWRP and clicked "reboot to recovery", since I haven't flashed the recovery, just booted into it, it rebooted to the stock recovery.
4) In stock recovery I have done factory reset and it started to work again.
PS: I rebooted from TWRP to stock recovery, because the TWRP couldn't mount any of my /system/ /cache/ /data/, but the stock worked flawlessly.
Won't work
Ereniemis said:
Okay...
1) booted to fastboot through http://forum.xda-developers.com/huawei-watch/development/guide-boot-fastboot-mode-t3225382
2) booted to recovery, not with "FLASH" just with "fastboot boot twrp.img" (e.g. http://forum.xda-developers.com/hua...p-twrp-2-8-7-0-recovery-huawei-watch-t3224714 )
3) went to "reboot" in TWRP and clicked "reboot to recovery", since I haven't flashed the recovery, just booted into it, it rebooted to the stock recovery.
4) In stock recovery I have done factory reset and it started to work again.
PS: I rebooted from TWRP to stock recovery, because the TWRP couldn't mount any of my /system/ /cache/ /data/, but the stock worked flawlessly.
Click to expand...
Click to collapse
I tried the above but after the bootloop adb won't recognize my device, so after entering bootloader I can't flash twrp. Any solutions?
Check your drivers, if you have eg. windows 7/8/8.1/10 you will have to install proper driver... which is not-official driver for hwatch, and I had to restart windows in "developer mode" "disable driver signatures" and then I have succesfully installed drivers and the computer recognized it.
To install hwatch drivers I've used this https://www.reddit.com/r/hwatch/comments/3n9ckp/how_to_get_adb_access_over_usb/
and maybe you can use this, but I'm not sure http://forum.xda-developers.com/huawei-watch/general/unlocking-easy-t3205219
Ereniemis said:
Check your drivers, if you have eg. windows 7/8/8.1/10 you will have to install proper driver... which is not-official driver for hwatch, and I had to restart windows in "developer mode" "disable driver signatures" and then I have succesfully installed drivers and the computer recognized it.
To install hwatch drivers I've used this https://www.reddit.com/r/hwatch/comments/3n9ckp/how_to_get_adb_access_over_usb/
and maybe you can use this, but I'm not sure http://forum.xda-developers.com/huawei-watch/general/unlocking-easy-t3205219
Click to expand...
Click to collapse
I tried installing the drivers from the above link, and disable signature verification too. Tried the second method suggested to force the drivers also and still no success.
Is it possible that my watch sin't allowing ADB access?
When the new update came, I factory reset my watch, unlocked bootloader, tried rebooting into recovery so i could flash and this happened.
Will I have to replace the watch?
Doesn't work. Makes me think my partitions are f**ked. In the past, I was able to odin myself out of this. I have no idea what to do guys.
Any idea?
FIXED: By doing what he said before by booting to TWRP. But when you do, do this. WIPE -> Advanced wipe -> Select Cache -> tap "Repair or change File System" -> Repair. After this, I had no more bootloops when going to stock recovery. Now to figure out why I keep throwing the error 7 when updating to MM.
hi
i managed to get mine working as well ! (Thanks to abhanli, pkt_lnt and skin180)
make sure you are in fastboot menu on your watch (holding the power button till switches off and the pressing again after vibrates)
most important thing next is to press shift and right click anywhere in the adb folder on your computer, and then run command prompt from there, otherwise adb will not load up and you will think that you have just run a dodgy script !
unlock your bootloader (typing "Fastboot Oem Unlock" in the command prompt in adb folder)
then you can use steps of skin180 (link above)
OR
https://developer.android.com/wear/preview/downloads.html
scroll down to huawei watch and choose second download option (non preview image for after testing) (thanks pkt_lnt)
extract into your adb folder (located in c:\)
then using the command prompt in adb folder, navigate to that extracted folder (using dos commands)
then if you are on windows, type "flash-all.bat"
hey presto - will work !
when it reboots, you may think "darn it still has spinning dots !" but if you wait about 5-10 mins it progresses past that stage and comes up with welcome screen !
My watch is working again !
HUAWEI customer services are a pile of POO. Their repair centre in UK is waste of time. They never answer the phone and never reply to messages.
If the Huawei watch wasnt so beautiful, i'd never bother with them !
Good luck and thanks all.
Good work poorak!
But, you only need to post this information once, not several times on different threads....
galaxys said:
Good work poorak!
But, you only need to post this information once, not several times on different threads....
Click to expand...
Click to collapse
thought id help as many people as i can for which ever thread they get to whilst searching for a solution !
Hwatch bootloop issue
Hi i have hwatch with bootloop too, tried to do everything i could and i can't get my computer to recognise hwatch, i only get "unknown device" in manager, i have stock recovery, locked bootloader and bricked device i've tried to force instal drivers, dissabling signed drivers, and manually from "naked drivers" post above, no success, PLEASE help
Recovery bootloop
titus1001234 said:
Hi i have hwatch with bootloop too, tried to do everything i could and i can't get my computer to recognise hwatch, i only get "unknown device" in manager, i have stock recovery, locked bootloader and bricked device i've tried to force instal drivers, dissabling signed drivers, and manually from "naked drivers" post above, no success, PLEASE help
Click to expand...
Click to collapse
Hi, i have the same problem. My watch has an infinite recovery bootloop. I tried to turn on the watch in fastboot mode but it isn' t recognized by the pc, no feedback sounds or unrecognized driver, it's like it isn"t connected. Did you solve the problem?
Ereniemis said:
Hello,
Something interesting happened... I have rebooted to fastboot, unlocked, jumped back to fastboot, and there were few thing to select "reboot" "shutdown" "reboot bootloader" "reboot recovery". I thought to myself, well lets look how does the stock recovery looks like... And now I'm stuck with this.
https://youtu.be/ea1gZ_KohAw
It doesn't matter how long I press the power button... It still reboots into this nonsense...
So... Anyone encountered the same problem?
Should I just wait until the battery will drain?
On the screen it says:
E:failed to mount /cache (invalid argument)
E:Can't mount /cache/recovery/last_locale
EDIT: SOLVED
Click to expand...
Click to collapse
this thing happen to me but not in my watch in my phone, Im currently using huawei gr5 2017, what should i do? please help me
poorak said:
hi
i managed to get mine working as well ! (Thanks to abhanli, pkt_lnt and skin180)
make sure you are in fastboot menu on your watch (holding the power button till switches off and the pressing again after vibrates)
most important thing next is to press shift and right click anywhere in the adb folder on your computer, and then run command prompt from there, otherwise adb will not load up and you will think that you have just run a dodgy script !
unlock your bootloader (typing "Fastboot Oem Unlock" in the command prompt in adb folder)
then you can use steps of skin180 (link above)
OR
https://developer.android.com/wear/preview/downloads.html
scroll down to huawei watch and choose second download option (non preview image for after testing) (thanks pkt_lnt)
extract into your adb folder (located in c:\)
then using the command prompt in adb folder, navigate to that extracted folder (using dos commands)
then if you are on windows, type "flash-all.bat"
hey presto - will work !
when it reboots, you may think "darn it still has spinning dots !" but if you wait about 5-10 mins it progresses past that stage and comes up with welcome screen !
My watch is working again !
HUAWEI customer services are a pile of POO. Their repair centre in UK is waste of time. They never answer the phone and never reply to messages.
If the Huawei watch wasnt so beautiful, i'd never bother with them !
Good luck and thanks all.
Click to expand...
Click to collapse
problem is i can't find that download