Because of the incredibly slow and laggy tablet I have I decided to try to do something about it.
So going from some thread here I decided to try to Root it using Motochopper, it seemed to go well but then the SuperSU app did not run, giving me a error No SU binary. I found out the supposedly Motochopper doesn't work with the 10.6.1.14.10 build. Anyways I later read that rooting wasn's necessary when adding custom roms so I unlocked with official app and then tried installing via fastboot a custom recovery TWRP 2.7.0.0
After running the command it just seemed to be stuck, nothing happened. I allowed it to go on but in the end I think the table was out of battery power and this was left on my command prompt.
{
"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"
}
anyone have any idea what the problem might be?
ingovals said:
Because of the incredibly slow and laggy tablet I have I decided to try to do something about it.
So going from some thread here I decided to try to Root it using Motochopper, it seemed to go well but then the SuperSU app did not run, giving me a error No SU binary. I found out the supposedly Motochopper doesn't work with the 10.6.1.14.10 build. Anyways I later read that rooting wasn's necessary when adding custom roms so I unlocked with official app and then tried installing via fastboot a custom recovery TWRP 2.7.0.0
After running the command it just seemed to be stuck, nothing happened. I allowed it to go on but in the end I think the table was out of battery power and this was left on my command prompt.
anyone have any idea what the problem might be?
Click to expand...
Click to collapse
You may want to put the twrp.blob in the adb directory/folder and try again, good luck.....:fingers-crossed:
LetMeKnow said:
You may want to put the twrp.blob in the adb directory/folder and try again, good luck.....:fingers-crossed:
Click to expand...
Click to collapse
Haha, no I did not forget to do that. Perhaps it was because the trwp.blob was blocked or something, but tried again and it worked instantly now.
thank you.
ingovals said:
Haha, no I did not forget to do that. Perhaps it was because the trwp.blob was blocked or something, but tried again and it worked instantly now.
thank you.
Click to expand...
Click to collapse
It is good to hear that it worked out for you...:good: I recommended that because I did not see the twrp.blob from your screen shot when you were executing the fastboot command. In your adb directory, you have only four files, two .exe for adb/fastboot and two libraries or dll supporting adb/fastboot....
Congratulations by the way!!! :highfive:
Related
Hi All,
I've been reading this forum for a good few days now as I am trying to get my Kyros functioning the way I need it to. However, I've run into a few problems and am not 100% sure as to what to do. Before I go on, I'm not very techy, so I would be very greatful if replies could be as straight forward as possible, without much jargon as that really loses me
First off, we've just managed to install the windows and ADB drives. I'm following all the instructions from here: http://forum.xda-developers.com/showthread.php?t=858952. That took some hacks our side, but is now working.
I'm pretty stuck on the clockwork reboot though. Again, followed the instructions from the link above. When it initially rebooted, it went straight into the Android System Recovery mode (the robot with the triangle opening screen.) I've tried it over and over, following the directions exactly as explained in the link, but all I'm getting is the generic Androis system recov.
The Recovery zip file is on my SD card. Do I need to unzip it to get the recovery.img to show? Is that something that I'm doing wrong? I also updated the OS (I guess) from the coby site before I started working on these other changes.
So basically, this is the issue right now. Trying to get the clockwork to run and all I'm getting is the android system...and that's when it doesn't just reboot back to the home screen directly.
Any advice would be great. Thanks
And out of the blue, after an hour of angry TV watching, it's now worked. I can't tell you what I did differently as I followed all the same steps as before. Must just have been lucky I guess.
I am having the same issue, and i tried to unzip the update.zip but i boot back to the recovery mode, can someone assist me with this, i have a galaxy s (Vibrant).
thanks
Try going to your sd folder and delete the clockwork recovery folder then uninstall rom manager and redownload it from the market after it installs open up rom manager and click on flash clockworkmod recovery and let it download the update.zip file and your done
Sent from my SGH-T959 using XDA App
Oh yeah after all those steps and you still get back into the stock recovery system click on reinstall package and it should boot into cwm I hope that helps
Sent from my SGH-T959 using XDA App
ASR
baalcat said:
Trying to get the clockwork to run and all I'm getting is the android system
Click to expand...
Click to collapse
like this ?
{
"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"
}
Right, I'm sure there is similar here, but I had loads of difficulty finding it, so I thought I'd create my own version.
I'm a complete noob at this, so I'll make it easier on you, and put it as plainly as possible. EVERY step is listed as if you're in the same [or similar] situation.
I only recently tried to get CM10 onto my phone, and on first try, I soft-bricked it. I unlocked the Bootloader, Rooted, Installed TWRP and a version of CWM when it didn't work, and CM10 seemed to work fine, but upon booting for the first time, and leaving it for about 15 minutes, I realised something went wrong. Tried going back to the most recent RUU [the EU OTA version], and that didn't work [after relocking the bootloader, yes]. Started freaking out a small bit, as it stopped letting me mount the storage in Recovery, even though ADB could still see the phone.
Asked a friend to help, and we found this over on the One X sub-forum.
BEING AWARE THIS IS RELATIVE TO hasoon2000's All-In-One Toolkit
[nice work btw! Might wanna look into this btw - it may be a small bug with your software. No offense ]
Turned out it was the boot.img that installed incorrectly, so making sure the .zip MD5 is correct is first step.
If that's not the issue, the 2nd step is to just open the .zip and take the boot.img out of the root of the container, and pushing that to the phone using ADB [the one that come's with the AIO is perfect]. If you're not sure how to get into ADB, and get it to stay open, here's what you do:
1. Copy the directory of "adb.exe" within your AIO's "data" folder [for example, mine is D:\Administrator.Sheol\HTC\All-In-One\Data\]
Click to expand...
Click to collapse
2. Open Command Prompt [in Vista onwards, type "cmd" into the Start menu Search Bar, in XP, open the "run" dialog in type cmd. Alternatively, find it in Start > Accessories, in all recent versions of Windows]
Click to expand...
Click to collapse
3. Type the following into Command Prompt:
cd D:\Administrator.Sheol\HTC\All-In-One\Data\
{
"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"
}
Remembering your directory WILL be different, so adjust accordingly!
Click to expand...
Click to collapse
4. It'll list all ADB's command's. Don't worry, it's meant to. If you want to, skim through them to familiarise yourself with it. At this point you may want to maximise the window, to fill the screen height [makes every thing much easier]
Click to expand...
Click to collapse
5. Follow this thread to the tee > [Tutorial] How to flash a new boot.img via Fastboot
Click to expand...
Click to collapse
Doing exactly this, worked a charm, and now I have a flawless CM10 HTC One S! After the GApps install of course [which can be done in your Recovery after downloading it/pushing it to your phone, by using the "Install from .zip" option]
I have a TF300T on stock 4.2 rooted and unlocked.
I downloaded twrp for 4.2 and renamed it to twrp.blob
I put it on my internal sd storage and followed this guys tutorial
http://www.youtube.com/watch?v=D2ATyGP5JAk
I used this command on terminal emulator
SU
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
{
"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"
}
Not sure if this is an issue either http://i.imgur.com/PpHoOBS.png
I've tried redoing that command then letting it restart then trying to boot to recovery but that didn't work.
I tried installing TWRP through GooManager but it couldn't find the recovery for me.
Chris9446 said:
I have a TF300T on stock 4.2 rooted and unlocked.
I downloaded twrp for 4.2 and renamed it to twrp.blob
I put it on my internal sd storage and followed this guys tutorial
http://www.youtube.com/watch?v=D2ATyGP5JAk
I used this command on terminal emulator
SU
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Not sure if this is an issue either http://i.imgur.com/PpHoOBS.png
I've tried redoing that command then letting it restart then trying to boot to recovery but that didn't work.
I tried installing TWRP through GooManager but it couldn't find the recovery for me.
Click to expand...
Click to collapse
Same issue here, I've tried multiple versions of TWRP, 1.5/1.6/1.7 and all of them are causing issues like this.
I did the same thing you've been doing as well.
Mario
Does anyone know the solution to this?
desantim said:
Same issue here, I've tried multiple versions of TWRP, 1.5/1.6/1.7 and all of them are causing issues like this.
I did the same thing you've been doing as well.
Mario
Click to expand...
Click to collapse
I found a solution..
Flash TWRP 2.4.4 for your device and it will fix the problem
Chris9446 said:
I found a solution..
Flash TWRP 2.4.4 for your device and it will fix the problem
Click to expand...
Click to collapse
Yes, but this is only true because you are on bootloader 10.6.1.8. If you upgrade to a newer like 10.6.1.15.3 you will need TWRP 2.5.0.0-4.2.
bwiberg said:
Yes, but this is only true because you are on bootloader 10.6.1.8. If you upgrade to a newer like 10.6.1.15.3 you will need TWRP 2.5.0.0-4.2.
Click to expand...
Click to collapse
yep this is right
and if you mean the key driver not found, mine says that too
Not to bring a dead thread back, but was there a fix implied in previous posts, or just ackowledgment of a known issue?
Mario
Nah not really a fix, but it does illustrate the importance of correctly matching bootloader and TWRP version. A very useful table was posted by pjc21 in this thread: http://forum.xda-developers.com/showthread.php?t=2195883
To recapitulate - for Android 4.2 you must match
- bootloader 10.6.1.8 with TWRP 2.4.4.0-4.2
- bootloader 10.6.1.15.3 with TWRP 2.5.0.0-4.2
As far as I have seen the latest bootloader 10.6.1.27.1 can be used with both TWRP 2.5.0.0-4.2 and 2.6.0.0-4.2, but I have not tested this.
Hello everybody
Well, I have his issue. I tried to flash some new roms into the OPO yesterday and I had some issues with one, so I decided to flash other one, but when I wiped the things I also wiped the internal storage and I didnt know that that would erase my OS, now i'm trying to flash a rom but it wont let me with the bootloader because it says its locked, and if i try to unlock it using OPO toolking via ADB sideload the phone shows it requires ADB 1.0.32 which is the same that i have installed on my computer and if I try it using the bootloader option it just restarts and it keeps being locked. If I try to send a rom with the CMD on my pc it says "error: closed"
I have done some research and found some similar cases but not simiilar enough to have the same fixes
I have windows 10 and TWRP is 2.8.7.0
If anybody helps me that would be pretty useful
Thanks!
minor9719 said:
Hello everybody
Well, I have his issue. I tried to flash some new roms into the OPO yesterday and I had some issues with one, so I decided to flash other one, but when I wiped the things I also wiped the internal storage and I didnt know that that would erase my OS, now i'm trying to flash a rom but it wont let me with the bootloader because it says its locked, and if i try to unlock it using OPO toolking via ADB sideload the phone shows it requires ADB 1.0.32 which is the same that i have installed on my computer and if I try it using the bootloader option it just restarts and it keeps being locked. If I try to send a rom with the CMD on my pc it says "error: closed"
I have done some research and found some similar cases but not simiilar enough to have the same fixes
I have windows 10 and TWRP is 2.8.7.0
If anybody helps me that would be pretty useful
Thanks!
Click to expand...
Click to collapse
SOLUTIONS THAT MIGHT WORK
1) Use Fastboot instead of Sideload
Cmd
Go to Fastboot folder with CD
Boot into Fastboot , then type fastboot devices.
If you see the Oneplus One, then just download a random ROM and FLASH the ZIP
2) [Toolkit] Wug's Bacon Root Toolkit v1.0.3 [Updated 04/16/15] by WugFresh ---> LINK
Screenshots 1
{
"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"
}
Screenshot 2
3) [GUIDE] How to unbrick or make your phone 100% stock by vigneshvar1
This installing Android CM11s but you can afther that installing a other rom of your choise. --> LINK
Hi,
I never saw this problem
My phone is unlocked (since a year more or less) and I can't install TWRP nor CWM. I tried many tutorials such as all the root methods listed on XDA for this smartphone.
{
"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"
}
Any idea would be really appreciated!
Thanks
There might be a problem with your drivers. You can try uninstalling and reinstalling them. Also, try using fastboot commands manually
Sent from my Mate
unlock again
Thank you. I'd like not to have to relock it as it's already done and rooted. Could you please tell me what drivers to install? I tested many of them (https://i.imgur.com/wBgsezr.png) but it seems I don't have the right ones then.
I'm using Win7 64bits.
Thanks again!
Use adbdriveinstaler and when it's install you can push recovery to add folder and try this command
cd C:/adb
Fastboot flash recovery recovery.img
Change name your twrp or cwm to recovery
Send frome globe
Okay. Here we go
ADB driver installed (https://i.imgur.com/PWrZoHH.png)
Went to flash and... still not allowed.
And in fastboot/rescue mode on my phone it's written PHONE Unlocked.
WTF
BTW, is there any other way to upgrade the phone? Cause every time I go to the software update in the menu i'm told it's up-to-date, but it's not... Android 4.4.2 & EMUI 3.0.
I read about a "local update" but can't find out how to update from the SDcard, I only have OTA.
Bud64 said:
Okay. Here we go
ADB driver installed (https://i.imgur.com/PWrZoHH.png)
Went to flash and... still not allowed.
And in fastboot/rescue mode on my phone it's written PHONE Unlocked.
WTF
BTW, is there any other way to upgrade the phone? Cause every time I go to the software update in the menu i'm told it's up-to-date, but it's not... Android 4.4.2 & EMUI 3.0.
I read about a "local update" but can't find out how to update from the SDcard, I only have OTA.
Click to expand...
Click to collapse
In your screen you have locked bootloader. Unlock againg
Send frome globe
Okay, I sent an email to Huawei, I'll get back in a few days.