Hi everybody,
So, there is my problem, I bought the nexus 5 in November. I rooted it.
And the last wednesday, while using my phone, the power button decided to not respond anymore.
The phone still worked but two days ago the batery became empty and now I can just go in the "bootloader menu" and the "download mode".
Google accepted to replace my phone, but I really want to save my files. And like you certainly know we can't save our files with the phone Off.
But my phone is detected in this two modes.
I installed the nexus driver but I still can't open my files.
I pretty sure there is a way to save my files, I searching and trying but nothing work, I would open my phone if I can activate the power button manually but I don't know how.
If you have any solution, I'll take it.
Per-haps the ADB can help me ? But I don't know how to use it.
Thanks a lot for reading.
Have a good day !
Ps : I'm new here please be gentle if I don't understand directly
And sorry for my poor english.
PeauMorte said:
Hi everybody,
So, there is my problem, I bought the nexus 5 in November. I rooted it.
And the last wednesday, while using my phone, the power button decided to not respond anymore.
The phone still worked but two days ago the batery became empty and now I can just go in the "bootloader menu" and the "download mode".
Google accepted to replace my phone, but I really want to save my files. And like you certainly know we can't save our files with the phone Off.
But my phone is detected in this two modes.
I installed the nexus driver but I still can't open my files.
I pretty sure there is a way to save my files, I searching and trying but nothing work, I would open my phone if I can activate the power button manually but I don't know how.
If you have any solution, I'll take it.
Per-haps the ADB can help me ? But I don't know how to use it.
Thanks a lot for reading.
Have a good day !
Ps : I'm new here please be gentle if I don't understand directly
And sorry for my poor english.
Click to expand...
Click to collapse
Hoping you have enabled the usb debugging you can indeed backup through adb: http://forum.xda-developers.com/showpost.php?p=51694433&postcount=2
Can you enter into recovery mode from the bootloader menu?
Primokorn said:
Hopping you have enabled the usb debugging you can indeed backup through adb: http://forum.xda-developers.com/showpost.php?p=51694433&postcount=2
Can you enter into recovery mode from the bootloader menu?
Click to expand...
Click to collapse
The usb debugging is enabled I hope too, I'll try it immediatly, thanks you.
But I can't enter in any thing in that menu.
PeauMorte said:
The usb debugging is enabled I hope too, I'll try it immediatly, thanks you.
But I can't enter in any thing in that menu.
Click to expand...
Click to collapse
You can use a fastboot command to boot into recovery: fastboot boot path/to/TWRP.img if you have TWRP Recovery.
Then you will be able use to use adb commands to backup your data.
Primokorn said:
You can use a fastboot command to boot into recovery: fastboot boot path/to/TWRP.img if you have TWRP Recovery.
Then you will be able use to use adb commands to backup your data.
Click to expand...
Click to collapse
Hmm, Have I to start eclipse ? Where can I find the "sdk platform" ?
I found a folder who have that name but nothing happens when I run the exe files.
And in eclipse nothing had that name.
Edit : Sorry I did'nt understand before. I'm trying your command in this folder, but it say me that there is no such files in this directory. Could you explain me ?
Edit 2 : Okay I have to read better i guess, I don't have TWRP, I'm downloading it, could you just explain me a little how does it work ?
Edit 3 : With the command "adb devices" I can't see my phone :/ Have I to surrender ?
PeauMorte said:
Hmm, Have I to start eclipse ? Where can I find the "sdk platform" ?
I found a folder who have that name but nothing happens when I run the exe files.
And in eclipse nothing had that name.
Edit : Sorry I did'nt understand before. I'm trying your command in this folder, but it say me that there is no such files in this directory. Could you explain me ?
Edit 2 : Okay I have to read better i guess, I don't have TWRP, I'm downloading it, could you just explain me a little how does it work ?
Edit 3 : With the command "adb devices" I can't see my phone :/ Have I to surrender ?
Click to expand...
Click to collapse
1. First off, you have to install and set up adb & fastboot on your PC. Here is a great tutorial: http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
However you can use this tool instead: http://forum.xda-developers.com/showthread.php?t=2588979
2. To boot into recovery mode from bootloader, connect your phone to PC then enter this command into cmd:
fastboot devices (check if your N5 is connected otherwise)
fastboot boot path/to/TWRP.img (you can download the latest TWRP img from this website)
Primokorn said:
1. First off, you have to install and set up adb & fastboot on your PC. Here is a great tutorial: http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
However you can use this tool instead: http://forum.xda-developers.com/showthread.php?t=2588979
2. To boot into recovery mode from bootloader, connect your phone to PC then enter this command into cmd:
fastboot devices (check if your N5 is connected otherwise)
fastboot boot path/to/TWRP.img (you can download the latest TWRP img from this website)
Click to expand...
Click to collapse
With the two methods, no devices are found. But when I try with an other phone, nothing is dected too (debug mod enabled).
I tried to remove driver and update with all sources but nothing apparently work per-haps my debug mode is disabled ? ...
Edit :
Okay fastboot device detected my phone !
The guaranty will stop if I use the second command ?
And last thing, where I need to put the img ?
Thanks a lot I looking at the end of that problem *o*
PeauMorte said:
With the two methods, no devices are found. But when I try with an other phone, nothing is dected too (debug mod enabled).
I tried to remove driver and update with all sources but nothing apparently work per-haps my debug mode is disabled ? ...
Edit :
Okay fastboot device detected my phone !
The guaranty will stop if I use the second command ?
Click to expand...
Click to collapse
Nope because you only BOOT and not FLASH TWRP.img. Actually I say TWRP because I have this recovery but I think you can use this command with the stock recovery. You just have to use recovery.img file from the factory images instead of TWRP.img.
---------- Post added at 02:30 PM ---------- Previous post was at 02:30 PM ----------
PeauMorte said:
And last thing, where I need to put the img ?
Thanks a lot I looking at the end of that problem *o*
Click to expand...
Click to collapse
Put the file into your platform-tools folder (where you have fastboot.exe file)
Primokorn said:
Nope because you only BOOT and not FLASH TWRP.img. Actually I say TWRP because I have this recovery but I think you can use this command with the stock recovery. You just have to use recovery.img file from the factory images instead of TWRP.img.
---------- Post added at 02:30 PM ---------- Previous post was at 02:30 PM ----------
Put the file into your platform-tools folder (where you have fastboot.exe file)
Click to expand...
Click to collapse
Okay, nice !
But I put the twrp.img in the adb folder, but it doeasn't found the file, where i need to put it ?
path/to means what ?
PeauMorte said:
Okay, nice !
But I put the twrp.img in the adb folder, but it doeasn't found the file, where i need to put it ?
path/to means what ?
Click to expand...
Click to collapse
Did you rename the downloaded file to "TWRP.img"? The file name must be the same into your command prompt.
Copy TWRP.img into your platform-tools folder then open a command prompt from this folder and enter: fastboot boot TWRP.img
The path is the directory of your file you want to use. If you open the command prompt from the folder you have TWRP.img (platform-tools) then you don't need to mention the path.
I think the bootloader needs to be unlocked first for "fastboot boot twrp.img" to work? Isn't it? If unlocking wasn't necessary, everyone would've just booted recoveries to root their phones. (so that the sdcard doesn't get erased).
I sincerely doubt that the OP has an unlocked bootloader.
vin4yak said:
I think the bootloader needs to be unlocked first for "fastboot boot twrp.img" to work? Isn't it? If unlocking wasn't necessary, everyone would've just booted recoveries to root their phones. (so that the sdcard doesn't get erased).
I sincerely doubt that the OP has an unlocked bootloader.
Click to expand...
Click to collapse
Actually I never tried fastboot boot command on a locked bootloader. If it requires an unlocked bootloader and OP has a locked one I have no idea to recover his data.
Primokorn said:
Actually I never tried fastboot boot command on a locked bootloader. If it requires an unlocked bootloader and OP has a locked one I have no idea to recover his data.
Click to expand...
Click to collapse
Please guy ! You're a genius !
I love you !
I just used the reboot comand and my phone goes On !
Now I can back up my files
(Ps : For the people who'll have the same problem, you have to use your charger with you're computer and keep pressing the volume down while putting the charger in the phone to go in boot menu, but be carfully, you can't shutdown after that only solution, remove batery !)
:fingers-crossed:
PeauMorte said:
Please guy ! You're a genius !
I love you !
I just used the reboot comand and my phone goes On !
Now I can back up my files
(Ps : For the people who'll have the same problem, you have to use your charger with you're computer and keep pressing the volume down while putting the charger in the phone to go in boot menu, but be carfully, you can't shutdown after that only solution, remove batery !)
:fingers-crossed:
Click to expand...
Click to collapse
Happy for you... and your data
Primokorn said:
Happy for you... and your data
Click to expand...
Click to collapse
I'll just ask a last question because you're a super user of twrp, the back up fonctionality could work if I use it on this phone and the put it in my new nexus sent by google ?
Thanks a lot again and have a good day, you made mine.
PeauMorte said:
I'll just ask a last question because you're a super user of twrp, the back up fonctionality could work if I use it on this phone and the put it in my new nexus sent by google ?
Thanks a lot again and have a good day, you made mine.
Click to expand...
Click to collapse
Yes, you can! Just make sure you don't restore the /efs partition which contains the imei and other files which are unique to every device!
- Sent from an IceCold Hammerhead!
Related
I'm going to probably get a lot of hate for this because there are a ton of forums that might get me here. I did search for about 3 hours tonight and discovered some things but am still confused. I hope someone can help this be more simple. So a friend has a Nexus S that isn't working (I have a Nexus S by the by too). It's unlocked but no ClockWork on it. I can press volume up and power to get to fastboot mode. When I click on "reboot," the phone will just loop on the Google logo. If I click recovery, it starts to boot then shows the triangle with the exclamation mark. From there, I can press power and up or down on volume to get the blue screen which says reboot system now, apply update, wipe, wipe. You get it. I'm stuck...I can also turn off the phone, hold volume up/down and plug in the usb to get to "downloading..."
I want to get this phone working and back to stock. I have the SDK Manager (my phone isn't rooted so I use it to take screenshots) and pda net (which I still don't understand why or how to use with this) and two versions of Odin. It seems like Odin can get this working but I can't get it to work or find a clear guide on how to use it and which ones to use. This is a Tmob Nexus S, I think the i9020. Any help would be so greatly appreciated and I will give you all the credit. Oh, and i can pull up the device on ddms with the sdk manager and can explore the files but there is nothing. I can't find a way to drag a file on the phone to "apply update from /sdcard." Sorry again and thanks again!
callison.168 said:
I'm going to probably get a lot of hate for this because there are a ton of forums that might get me here. I did search for about 3 hours tonight and discovered some things but am still confused. I hope someone can help this be more simple. So a friend has a Nexus S that isn't working (I have a Nexus S by the by too). It's unlocked but no ClockWork on it. I can press volume up and power to get to fastboot mode. When I click on "reboot," the phone will just loop on the Google logo. If I click recovery, it starts to boot then shows the triangle with the exclamation mark. From there, I can press power and up or down on volume to get the blue screen which says reboot system now, apply update, wipe, wipe. You get it. I'm stuck...I can also turn off the phone, hold volume up/down and plug in the usb to get to "downloading..."
I want to get this phone working and back to stock. I have the SDK Manager (my phone isn't rooted so I use it to take screenshots) and pda net (which I still don't understand why or how to use with this) and two versions of Odin. It seems like Odin can get this working but I can't get it to work or find a clear guide on how to use it and which ones to use. This is a Tmob Nexus S, I think the i9020. Any help would be so greatly appreciated and I will give you all the credit. Oh, and i can pull up the device on ddms with the sdk manager and can explore the files but there is nothing. I can't find a way to drag a file on the phone to "apply update from /sdcard." Sorry again and thanks again!
Click to expand...
Click to collapse
It seems your boot.img file either corrupted or missing.
Find a working copy of file, flash it via ADB interface or fastboot. Flash recovery file CWM. If that doesnt work, Try flashing CM7 Rom or someother ROM.
Did you check http://forum.xda-developers.com/showthread.php?t=895545 ?
Odin should be your last resort, if nothing really works for you.
If you want to return to stock, simply flash the NAND backup found here: http://forum.xda-developers.com/showthread.php?t=884093 .
Disclaimer : I take no responsibility of what so ever happens to your phone, however you should be good if you follow proper steps.
Thanks so much for the quick reply. I think I've made some headway...I can "see" the device with cmd by typing adb devices. After that though, I don't understand how to get the stock nexus s rom on the phone. How do I move that file to my phone (what's the line of code I type)? I've tried "adb install <c:\grh78> but it says the syntax isn't correct. Any more help is so greatly appreciated and I appreciate the already prompt response. Thanks!!!
callison.168 said:
Thanks so much for the quick reply. I think I've made some headway...I can "see" the device with cmd by typing adb devices. After that though, I don't understand how to get the stock nexus s rom on the phone. How do I move that file to my phone (what's the line of code I type)? I've tried "adb install <c:\grh78> but it says the syntax isn't correct. Any more help is so greatly appreciated and I appreciate the already prompt response. Thanks!!!
Click to expand...
Click to collapse
Download your rom of choice (stock, custom)
Flash Cwm via fastboot if you haven't already
Boot into recovery.
Use adb push to push your zipped rom to the sdcard (adb push file.zip /sdcard/file.zip)
Use cwm to flash this zip.
Sent from my Nexus S using xda premium
callison.168 said:
Thanks so much for the quick reply. I think I've made some headway...I can "see" the device with cmd by typing adb devices. After that though, I don't understand how to get the stock nexus s rom on the phone. How do I move that file to my phone (what's the line of code I type)? I've tried "adb install <c:\grh78> but it says the syntax isn't correct. Any more help is so greatly appreciated and I appreciate the already prompt response. Thanks!!!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=9866675
http://forum.xda-developers.com/showthread.php?t=884093
These threads should be a complete solution to your issue.
Disclaimer : I take no responsibility of what so ever happens to your phone, however you should be good if you follow proper steps.
Wow fast responses. I bet it's annoying to help yet another person having issues (again, phone was given to me like this but yeah...) while you guys or gals already know how to do these things very well. Here's where I'm stuck. I enter this code in cmd:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
and it just says < waiting for device >.
Here's a pic of the screen that I'm on with my phone when i enter the command.
http://imgur.com/Pey3W
If I'm just in the first screen by holding volume up and power, the computer won't read the phone. So I click recovery, the screen shows it's trying to install something then the triangle exclamation mark, i press volume up/down with power and get this screen and the computer can "see" my phone on cmd.
How do I get this flipping clockwork on this phone or get the stock image on my sd card? Thanks again for helping me out guys. I have taken a look at the links you have sent me and that's where i found the download as well as the code to enter. I will keep looking at them but if you find a faster solution, please let me know.
One more thing to be super clear on...when I'm on the screen on the Nexus S that says Fastboot Mode on top in red and Lock State - Unlocked...my computer won't read the phone, therefore I cannot fastboot the recovery img...
callison.168 said:
One more thing to be super clear on...when I'm on the screen on the Nexus S that says Fastboot Mode on top in red and Lock State - Unlocked...my computer won't read the phone, therefore I cannot fastboot the recovery img...
Click to expand...
Click to collapse
So you already tried "fastboot devices" while in fastboot mode?
Edit: Actually it sounds you really want stock so download the complete stock OTA ROM (including boot.img etc.), rename it to update.zip and put it on the root of your sdcard. Boot into the stock recovery like you did already and hit apply update.
EDIT: Go here to download the correct OTA http://forum.xda-developers.com/showthread.php?t=1056062
Find the correct 2.3.6 "Full ROM" for your phone model. Sounds like in those instructions you don't need to rename to update.zip. Haven't seen stock recovery for a while so I don't remember.
If there is a wipe option in the stock recovery then do that first.
Yes I have tried fastboot devices in fastboot mode but nothing because my computer doesn't read the phone in that mode. And yes, I want to put the stock rom on there but that's the key, I can't get access to the root of my sdcard. I can't push anything into the sdcard to flash it. Any ideas what to type or how to access the sdcard? Thanks a million, billion.
Also, I can't get the phone to boot at all, like I can't get passed the Google Logo if I reboot so I can't access the sdcard in the traditional way.
callison.168 said:
Yes I have tried fastboot devices in fastboot mode but nothing because my computer doesn't read the phone in that mode. And yes, I want to put the stock rom on there but that's the key, I can't get access to the root of my sdcard. I can't push anything into the sdcard to flash it. Any ideas what to type or how to access the sdcard? Thanks a million, billion.
Click to expand...
Click to collapse
Connect with adb and type this:
adb shell mount /sdcard
Then type:
adb push rom.zip /sdcard/update.zip
callison.168 said:
Yes I have tried fastboot devices in fastboot mode but nothing because my computer doesn't read the phone in that mode. And yes, I want to put the stock rom on there but that's the key, I can't get access to the root of my sdcard. I can't push anything into the sdcard to flash it. Any ideas what to type or how to access the sdcard? Thanks a million, billion.
Click to expand...
Click to collapse
If fastboot devices returns NOTHING then this is most likely a driver issue. Remove the device through device manager, make sure you have a recent SDK (for the USB driver) and let it re-detect.
callison.168 said:
Also, I can't get the phone to boot at all, like I can't turn on the phone so I can't access the sdcard in the traditional way.
Click to expand...
Click to collapse
If you can get into the boot loader and get a proper USB driver you should be able to flash a recovery.
Once you've flashed Clockwork Mod (recovery) you'll be able to push to the sdcard using ADB or possibly mount the sd card through the CWM menu (although I've yet to have that work).
In order to get a recovery flashed though you need to get fastboot to see your device (unless you can already boot into recovery, then just use ADB).
irishrally said:
Connect with adb and type this:
adb shell mount /sdcard
Then type:
adb push rom.zip /sdcard/update.zip
Click to expand...
Click to collapse
If he's stuck at the Google logo and has a trash boot.img it's not likely he'll be able to get a shell via ADB. Now, if the system is hanging starting a device or looping during boot then that's possible.
krohnjw said:
If he's stuck at the Google logo and has a trash boot.img it's not likely he'll be able to get a shell via ADB. Now, if the system is hanging starting a device or looping during boot then that's possible.
Click to expand...
Click to collapse
He said he can access stock recovery and has connected with adb, unless I read wrong.
irishrally said:
He said he can access stock recovery and has connected with adb, unless I read wrong.
Click to expand...
Click to collapse
Indeed - I saw no clockwork and figured he'd toasted his recovery image as well, but it does look like stock recovery is there. ADB should push fine to the sdcard from recovery then.
More...so if i type in adb reboot bootloader in the recovery screen, it does just that...great. But then my computer makes a noise, a double tap if you will...like a dun dun, like something didn't work. When you plug in something to the computer it usually goes like dun na...but the phone clearly won't read when I'm in bootloader/fastboot mode. So when I type a command, nothing will work...
callison.168 said:
More...so if i type in adb reboot bootloader in the recovery screen, it does just that...great. But then my computer makes a noise, a double tap if you will...like a dun dun, like something didn't work. When you plug in something to the computer it usually goes like dun na...but the phone clearly won't read when I'm in bootloader/fastboot mode. So when I type a command, nothing will work...
Click to expand...
Click to collapse
That noise is that it detects a device has been connected (assuming a recent version of windows). If you want to flash CWM you need to get the driver sorted for the device. No amount of plugging/unplugging is going to fix it.
If you have the stock recovery you can boot into the stock recovery, use adb to push the full OTA package to the sd card and then just flash that from the stock recovery.
callison.168 said:
More...so if i type in adb reboot bootloader in the recovery screen, it does just that...great. But then my computer makes a noise, a double tap if you will...like a dun dun, like something didn't work. When you plug in something to the computer it usually goes like dun na...but the phone clearly won't read when I'm in bootloader/fastboot mode. So when I type a command, nothing will work...
Click to expand...
Click to collapse
Go to the stock recovery like you have done before and type the adb command I wrote above.
Thanks is all I can say. Okay so when I type in the command, this is what I get:
- exec '/system/bin/sh' failed: No such file or directory (2) -
the "stock recovery" I can get into is the picture I posted a link for. That's what I can access as well as the fastboot mode when I first turn on the phone with volume up/power. But when my computer makes the noise that it's connected (using Windows 7 64bit) it makes a different sound then the normal "device connected." Like it's corrupted.
by the way...if we can get this working, I'll post a picture of me holding the fixed phone!
Tried various possible solutions and still can't get past the Google logo. Installed adb and Samsung driver but when executing commands such as "abd remount" or "adb push file.zip \sdcard\" in cmd I get an error saying "device not found".
Does anyone know how I could resolve this issue?
I tried clearing the cache and wiping the data from the phone, and even heating the phone with a hair dryer. I'd very much appreciate any help.
looks like you still be able to get in reovery ? if so , then nothing you should worry , just flash a new ROM
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
nodstuff said:
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
Click to expand...
Click to collapse
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
leeroy88 said:
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
Click to expand...
Click to collapse
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
leeroy88 said:
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
Click to expand...
Click to collapse
Hmmm try going to cmd prompt and typing in adb devices, if you get nothing then your adb isn't set up properly and you need to go into setting and change the path on your computer.
I know the details are sketchy but gimme a min and I will find you a link
---------- Post added at 03:05 AM ---------- Previous post was at 03:00 AM ----------
http://forum.xda-developers.com/showthread.php?t=1161776
Find the Android sdk folder in your computer, move it to the root of C.
I don't think adb is where this guide says it is, there is a read me in the folder where it was saying it has moved to the platform tools folder.
So anyway find the path to the file and put it where the guide says and you should be on the ball.
Forget adb. You need to use fastboot.
Open a command prompt in the directory with fastboot or cd into it.
Put phone in fastboot mode.
On the command prompt type fastboot devices.
You will see your serial number. If you don't recheck and make sure you did everything. Sdk PDA drivers if need be etc.
Fastboot flash recovery custom recovery img name.img
Boot into recovery
Mounts and storage.
Mount SD card
Put a rom for you device on there.
Unmount
Wipe everything but sdcard from recovery.
Flash the rom by going to install zip from SD card......
Okay still stuck trying to connect to my phone. I haven't been able to get my serial number show when typing fastboot devices in cmd. adb is set up and seems to be working but the list of devices is blank when I type in adb devices. The phone was put into fastboot mode both times. I get <waiting for device> when I try
fastboot flash recovery clockwork-5.0.2-crespo.img
I think the bootloader may be locked as it does say LOCKED under lock state, which is probably the reason why I can't get the recovery image to work. I couldn't install PDANet as it wanted to connect to my phone while in debugging mode at the end of the installation. Would it be possible that fastboot oem unlock won't work with without having PDANet installed? I'd really appreciate any further help on this topic.
You need the drivers.
albundy2010 said:
You need the drivers.
Click to expand...
Click to collapse
I have the Google USB driver package installed from SDK Manager. I had tried to install some other Samsung driver found on another post but it wouldn't install.
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
leeroy88 said:
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
Click to expand...
Click to collapse
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
ismailham said:
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
Click to expand...
Click to collapse
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
leeroy88 said:
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
Click to expand...
Click to collapse
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
nodstuff said:
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
Click to expand...
Click to collapse
After typing fastboot oem unlock I get three dots ...
Pretty much straight away it fails and says something about "too many links".
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
kvaju said:
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
Click to expand...
Click to collapse
Thanks for your reply, I followed the steps just now and got the exact same error. Before I was trying fastboot oem unlock while in platform-tools but this time I had downloaded the nexussrootICS.zip file, and extracted it to the root of C. I tried fastboot devices and my serial shows up and after fastboot oem unlock I get "status read failed: too many links."
The only difference I seem to have is that in my device manager I have Android Device > ADB Interface, as opposed to SAMSUNG Android Device > ADB Interface.
Not a big difference but that's all I can think of.
the same issue for me. is there any working solution for that?
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
GnubbyaBush said:
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
Click to expand...
Click to collapse
Thanks! I'll try to do this fancy dancing
Hy,
First sorry for my bad english
This is my first thread here. I made a modified boot and aboot.img for Acer E600.
With these files you can root your phone and unlock the tampered bootloader.
Edited 6/27/2015
1. Root (original thread: http://acer-club.fr/viewtopic.php?f=252&t=9804 )
- Install the correct adb & fastboot drivers https://drive.google.com/open?id=0B...nJDUnFRZnd4VDRYSkJtN19XbkpyS2ZoTHc&authuser=0
- Download cwm: http://acer.shreps.fr/dl.php?v=CWM-...3N0b3JhZ2UvRTYwMC9DV00tNi4wLjUuMF9FNjAwLmltZw and copy to the adb folder.
- Download UPDATE-SuperSU-v2.46.zip: http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1
- Copy the UPDATE-SuperSU-v2.46.zip to sdcard
- Turn on your phone in fastboot/bootloader mode (push the volume down and power button at same time) and connect to PC.
- Open a command line in the adb folder and type:
fastboot devices
if your device on the list:
fastboot boot CWM-6.0.5.0_E600.img
the phone will restart in cwm.
-Install the UPDATE-SuperSU-v2.46.zip from sdcard.
Now you have a root permission with read only system
2. Disable secure mount
You need open the bootloader.
Your warranty is now void! I'm NOT RESPONSIBLE FOR ANY DAMAGE CAUSED!
I made a solution to open tampered bootloader without wipe userdata.
If your phone's bootloader is already unlocked, skip the step a.)
a.) Download the aboot.img https://drive.google.com/open?id=0Byr5wBifihDyRTVnMDVVUUIxYzg&authuser=0
and copy to your adb folder on pc.
Connect the phone in fastboot mode and type:
fastboot flash aboot aboot.img (yes aboot.img, dont forget the "a")
unplug the phone, push the power button until the phone turn off then turn on again in fastboot mode. Then back to command line:
fastboot oem device-info
if you see device unlocked: true your bootloader is open
Download the secoff.img https://drive.google.com/file/d/0Byr5wBifihDyZlU2VFNPNHEzeWc/view?usp=sharing
b.) Flash my boot.img with this command:
fastboot flash boot secoff.img
fastboot reboot
Done, your phone is fully rooted with r/w system.
I have an question about how to root my phone by this guide, can you make english guide for me? plz i can't do it. from this Google translator not enough can you??
ryszardo said:
I have an question about how to root my phone by this guide, can you make english guide for me? plz i can't do it. from this Google translator not enough can you??
Click to expand...
Click to collapse
this is an english guide. if you need help, send me a pm
gabcs said:
this is an english guide. if you need help, send me a pm
Click to expand...
Click to collapse
I mean this link
help
how do i mount coz i got my phone rooted and i need to change platform.xml but doesnt give me premission, now you said mount systemrw.img well i have it on my phone (external card) and in the folder platform-tools
some help would be great kinda sucks, i cant download apps, acer did a bad job on this phone so if you could help me out would be great, if you have skype add me maaslandernld or mail me on [email protected]
am just seconds away from killing my phone meaning step on it till its in pieces such a bad phone with little internal memory
best regards
maaslander said:
how do i mount coz i got my phone rooted and i need to change platform.xml but doesnt give me premission, now you said mount systemrw.img well i have it on my phone (external card) and in the folder platform-tools
some help would be great kinda sucks, i cant download apps, acer did a bad job on this phone so if you could help me out would be great, if you have skype add me maaslandernld or mail me on [email protected]
am just seconds away from killing my phone meaning step on it till its in pieces such a bad phone with little internal memory
best regards
Click to expand...
Click to collapse
If you have adb on PC just copy the systemrw.img to adb root folder and flash with fastboot command.
Example: my adb folder is on the root C:\
so copy the systemrw.img to C:\adb\
then open a command line at the same place (C:\adb)
turn off the phone, then turn on into fastboot mode (hold the volume down button and the power button at same time)
connect to pc and type to command line:
fastboot boot systemrw.img
the phone will restart and you can edit the platform.xml with root explorer or etc.
where is the boot secoof.img file??
David Mojica said:
where is the boot secoof.img file??
Click to expand...
Click to collapse
Sorry, I forget the link Here: https://drive.google.com/file/d/0Byr5wBifihDyZlU2VFNPNHEzeWc/view?usp=sharing
Thank you Sir! it worked. but I think it messed up the system. I cannot Uprgrade my phone from android 4.4.2 to 4.4.4 it says "failed to update due to network or server problem. Please try Again later 0014" why is that? I tried to unroot and then run the update again but nothings working
David Mojica said:
Thank you Sir! it worked. but I think it messed up the system. I cannot Uprgrade my phone from android 4.4.2 to 4.4.4 it says "failed to update due to network or server problem. Please try Again later 0014" why is that? I tried to unroot and then run the update again but nothings working
Click to expand...
Click to collapse
You're welcome! I never met this problem before. 4.4.4? My device with 4.4.2 is up to date
I found this thread for samsung, but I think the problem is the same: http://forums.androidcentral.com/samsung-galaxy-s4/317378-software-update.html
"As far as I know, only the "Google Edition" has received 4.3 at this time. Some reports say that 4.3 for the other S4 variants will be released in October, but as you mention, that will also depend on your carrier as to when it actually gets to your phone."
aboot.img and secoff.img link is dead, does anyone have back up? TS, Can i have a copy of aboot and secoof.img, just bought acer e600. i really want to root it and remove some files. its eating a lot of space.
Hello,
is there anyone here who can reupload the files for acer e600?
I have a phone blocked in acer logo after wipe in fastboot and as I see all the links are dead
Thanks a lot!
MarianG said:
Hello,
is there anyone here who can reupload the files for acer e600?
I have a phone blocked in acer logo after wipe in fastboot and as I see all the links are dead
Thanks a lot!
Click to expand...
Click to collapse
Which file exactly?
Verstuurd vanaf mijn S56 met Tapatalk
nikagl said:
Which file exactly?
Verstuurd vanaf mijn S56 met Tapatalk
Click to expand...
Click to collapse
Hi Sir,
I need aboot.img, secoff.img and a nandroid backup for it.
Thanks a lot!
MarianG said:
Hi Sir,
I need aboot.img, secoff.img and a nandroid backup for it.
Thanks a lot!
Click to expand...
Click to collapse
Nope, searched for them and I only have the cwm file... sorry.
I need those files as well, if anyone could re upload them it would be greatly appreciated, thank you!
can some one upload the links again i need to reroot my phone after my sd card crashed i didnt made back ups
the links are dead can i have it coz i want my phone to be rooted so ill have a chance to see it runnin on lollipop thank you
links are dead please if some one can re upload again thanks
Someone can reupload de aboot.img, secoff.img files please?
While recently trying to update my opo running cm11 I clicked install update but then it rebooted and just went to a black screen and did nothing. I rebooted it but it hadn't installed. I found my boot loader was locked and i had no recovery at all installed does anyone know how to fix this.
tom_clegg said:
While recently trying to update my opo running cm11 I clicked install update but then it rebooted and just went to a black screen and did nothing. I rebooted it but it hadn't installed. I found my boot loader was locked and i had no recovery at all installed does anyone know how to fix this.
Click to expand...
Click to collapse
Use fastboot & ADB guide for beginners. Download all required files so your PC can Connect to OPO VIA USB from PC. What PC OS do u use? Windows or Linux. Watch how to unlock boot loader, root, & install recovery tool or Return to stock OnePlus one YouTube video. Easiest start. Your phone will be OK. U need to down load drivers so u can use your PC to talk to your phone - pass instruction & activate 1+1 options. Install CM 11 or whatever ROM u want to use, as well as, 1+1 tools u may have lost is Recovery Tool.
Fstop said:
Use fastboot & ADB guide for beginners. Download all required files so your PC can Connect to OPO VIA USB from PC. What PC OS do u use? Windows or Linux. Watch how to unlock boot loader, root, & install recovery tool or Return to stock OnePlus one YouTube video. Easiest start. Your phone will be OK. U need to down load drivers so u can use your PC to talk to your phone - pass instruction & activate 1+1 options. Install CM 11 or whatever ROM u want to use, as well as, 1+1 tools u may have lost is Recovery Tool.
Click to expand...
Click to collapse
I use a mac and i tried to use a recovery tool however it says boot loader needed to be unlocked which mine wasn't and it wouldn't unlock because i had no recovery at all.
tom_clegg said:
I use a mac and i tried to use a recovery tool however it says boot loader needed to be unlocked which mine wasn't and it wouldn't unlock because i had no recovery at all.
Click to expand...
Click to collapse
You don't need a recovery to unlock the bootloader. Just boot it into fastboot mode, connect it to your Mac, and type 'fastboot oem-unlock' on the Terminal. Be careful, though, because you WILL lose ALL of your data!
Sent from my LG-V500 using Tapatalk
GXGOW said:
You don't need a recovery to unlock the bootloader. Just boot it into fastboot mode, connect it to your Mac, and type 'fastboot oem-unlock' on the Terminal. Be careful, though, because you WILL lose ALL of your data!
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
where do i find the files for mac with fast boot adb etc.
tom_clegg said:
I use a mac and i tried to use a recovery tool however it says boot loader needed to be unlocked which mine wasn't and it wouldn't unlock because i had no recovery at all.
Click to expand...
Click to collapse
Hmmm no recovery? When u hold down volume + power ?
Did u find the fastboot & adb tools for Mac?
What happens when u hold volume key up + power button at same time after turning device off?
What happens if u $fastboot devices -
Can u issue cmd "$fastboot oem unlock"
Know its frustrating but have to keep trying till u get in. Just have the rom files unzipped on your Mac ready to flash 1+1 when u get in. Its how I did it. When I wasn't able to but into recovery. Get on fastboot go thru OEM unlock, then flash 1+1. Follow the install script manually. Open script w plain text reader & just issue cmds following script. I don't trust scripts I + automation to get things unstuck.
tom_clegg said:
where do i find the files for mac with fast boot adb etc.
Click to expand...
Click to collapse
Use Google, there are plenty of guides available online. Once you have fastboot working the best thing to do is to flash the stock images with fastboot. I have detailed instructions in section 8a of my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471
Please note that fastboot commands are slightly different on a Mac but you'll see that when you view a guide on how to set it up and use it.
Heisenberg said:
Use Google, there are plenty of guides available online. Once you have fastboot working the best thing to do is to flash the stock images with fastboot. I have detailed instructions in section 8a of my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471
Please note that fastboot commands are slightly different on a Mac but you'll see that when you view a guide on how to set it up and use it.
Click to expand...
Click to collapse
would u be able to do a short one for mac that would help a lot with the commands
tom_clegg said:
would u be able to do a short one for mac that would help a lot with the commands
Click to expand...
Click to collapse
There's no point in duplicating my guide when all that's needed are a couple of extra characters prefixing each fastboot command.
Heisenberg said:
There's no point in duplicating my guide when all that's needed are a couple of extra characters prefixing each fastboot command.
Click to expand...
Click to collapse
is it just ./ then the command?
can i message you somehow maybe so it is quicker
tom_clegg said:
is it just ./ then the command?
can i message you somehow maybe so it is quicker
Click to expand...
Click to collapse
Dude, in the time it's taken you to ask these questions here you could have already found the answers online and completed the task. I'm here to help people but I'm not about spoon feeding, it doesn't benefit you in any way.
Heisenberg said:
Dude, in the time it's taken you to ask these questions here you could have already found the answers online and completed the task. I'm here to help people but I'm not about spoon feeding, it doesn't benefit you in any way.
Click to expand...
Click to collapse
fine then
tom_clegg said:
would u be able to do a short one for mac that would help a lot with the commands
Click to expand...
Click to collapse
at the point where i do fastboot oem unlock it reboots but stays at the boot screen.
tom_clegg said:
fine then
Click to expand...
Click to collapse
Don't get an attitude because I'm trying to help you help yourself.
tom_clegg said:
at the point where i do fastboot oem unlock it reboots but stays at the boot screen.
Click to expand...
Click to collapse
Issue the Mac equivalent of this command:
Code:
fastboot oem device-info
What does it return?
Heisenberg said:
Don't get an attitude because I'm trying to help you help yourself.
Issue the Mac equivalent of this command:
Code:
fastboot oem device-info
What does it return?
Click to expand...
Click to collapse
I type fastboot oem unlock and it is meant to reboot into android but however it stays stuck on the boot screen
tom_clegg said:
I type fastboot oem unlock and it is meant to reboot into android but however it stays stuck on the boot screen
Click to expand...
Click to collapse
That isn't what I asked you, if you want help you need to answer the questions that you're asked.
Heisenberg said:
That isn't what I asked you, if you want help you need to answer the questions that you're asked.
Click to expand...
Click to collapse
it says device tampered true
unlocked false
charge screen enabled false
tom_clegg said:
it says device tampered true
unlocked false
charge screen enabled false
Click to expand...
Click to collapse
Ok, try the unlock command again. What recovery did you previously have installed?
Heisenberg said:
Ok, try the unlock command again. What recovery did you previously have installed?
Click to expand...
Click to collapse
still the same thing sorry just stuck on boot screen.
i would have been able to do it its just this which i wasn't sure about :/
tom_clegg said:
still the same thing sorry just stuck on boot screen.
i would have been able to do it its just this which i wasn't sure about :/
Click to expand...
Click to collapse
You definitely can't boot into recovery? Most times not being able to get into recovery it's a case of user error. Hold volume down, then hold power (so you're holding them together), when you see the OnePlus boot logo let go of power but keep holding volume down until you reach recovery.
I tried to flash a custom rom (KatKiss), and it seems that I did something wrong along the way because the tablet is stuck in a bootloop.
So I rebooted my tablet and access the bootloader ("fastboot devices" recognize my device) and try to go to the recovery (with the TWRP splash screen, "adb devices" recognize my device). Unfortunately after 20 seconds on the splash screen, the tablet reboots (tries to load my katkiss android but bootloop everytime).
Bootloader : 10.6.1.14.10
TWRP : 3.1.1.0
Since the fastboot recognize my device while in bootloader, I think that I should try to flash twrp since it seems to be corrupted somehow.
Every time I flashed a rom nothing went wrong but now that I have a problem I don't want to worsen it and would like some help on the issue.
Did you flash the rom in your current TWRP?
Something is off... Did you possibly flash the TF201 rom version??
Whatever you do - do not use Wipe Data from the bootloader!!
Reflash TWRP, format data, then reflash the rom
And report in more detail what you did
Sent from my Nexus 5X using Tapatalk
Thank you for the fast reply!
I did flash the rom with my current TWRP and only downloaded the rom version for the TF700. Below is what I tried from your suggestion:
I check that my device is recognized:
fastboot device
So I tried flashing TWRP:
fastboot flash recovery twrp-3.1.1-0-tf700t
After it succeeded, I reboot the tablet:
fastboot reboot
And as a result... nothing changes, I don't know if I should try with older version of TWRP. Seems like I only have access to the tablet with the fastboot.
That is very strange indeed. Yes, try a 3.0.2 version of TWRP and see if that works.
If not, I would flash the Asus stock blob in fastboot and start from scratch....
Sent from my TF700T using Tapatalk
Kromlech said:
And as a result... nothing changes, I don't know if I should try with older version of TWRP. Seems like I only have access to the tablet with the fastboot.
Click to expand...
Click to collapse
Not sure if this will help but I had a reboot problem with trying to load into TWRP. I posted my solution into a different thread but will toss it out here..
I just had this problem with a Transformer 201Prime. The cycle went something like this..
Power on.... get ASUS logo in middle, Tegra3 logo on lower right, and bootloader unlocked in upper left....
then a buzz... then reboot.....
So I would try the power button and hold the volume down... that got me into the bootloader but when I hit the volume up button it would give me the TWRP logo... then buzz and reboot...
After much monkeying around... I realized I would have to re install everything. Fortunately I had the original NVFLASH bloob files backed up so I was able to get into the NVFLASH commands.
Here is a great tutorial, it is for the 201 so be sure to download the correct files but the steps are basically the same.
https://forum.xda-developers.com/tra...prime-t3486237
The other problems is I had to download a bloob tool to 'unpack' the necessary .bin and .ebt files that are mentioned in the commands... I used the following link to download the tool.
https://github.com/AndroidRoot/BlobTools
I hope this helps shake loose a few answers.
Once I was able to get a working recovery I could flash an updated ROM. (KatKiss is my current favorite)
I tried to flash version 3.0.2 of TWRP and the problem is still the same.
@Unidave199 the link you put in your post points to a post that doesn't seems to exist anymore, has it been moved?
@berndblb how do I do for flashing a rom with the fastboot? any stock rom to recommend?
double post
Kromlech said:
I tried to flash version 3.0.2 of TWRP and the problem is still the same.
@Unidave199 the link you put in your post points to a post that doesn't seems to exist anymore, has it been moved?
@berndblb how do I do for flashing a rom with the fastboot? any stock rom to recommend?
Click to expand...
Click to collapse
Unidave's link would only help you if you generated your device specific nvflash blobs when the tablet was still functioning. Did you:
flash a specifically modded recovery - flash the moddded bootloader, use wheelie to generate and save your blobs, return everything to factory specs?
I highly doubt it since you would have mentioned...
To flash the stock blob in fastboot you download the Asus firmware from here: https://www.asus.com/my/support/Download/28/1/0/11/29/8/
Extract the zip twice until you see a blob and a meta-inf file.
Move the blob into your fastboot folder, discard the rest of the file
Issue these commands one by one, letting each one finish before starting the next. Some will finish quick, others may take up to 3 minutes:
Code:
fastboot erase system
fastboot erase boot
fastboot erase recovery
fastboot erase misc
fastboot erase cache
fastboot erase userdata
fastboot flash system blob
fastboot reboot
The first boot will take a while, but that should put you back on a stock JB 4.2 system.
Trash all the files you used in your last attempt and redownload the rom, gapps and supersu
Fastboot flash TWRP
Reboot
Format /data in TWRP (this will take up to 1 hour - let it finish!!), then convert /data to f2fs
Flash the rom, gapps, supersu
If you flash Nougatella remember that you have to turn on wifi right after the language selection during setup or Google framework will crash.
Spend the end of the day doing it, but it worked flawlessly! Thanks a lot @berndblb, now I can use my tablet again!
Kromlech said:
I tried to flash version 3.0.2 of TWRP and the problem is still the same.
@Unidave199 the link you put in your post points to a post that doesn't seems to exist anymore, has it been moved?
@berndblb how do I do for flashing a rom with the fastboot? any stock rom to recommend?
Click to expand...
Click to collapse
My apologies for the problem with my link, looks like you resolved it, but wanted to post a correct working link to take someone else into the full conversation and context...
https://forum.xda-developers.com/showpost.php?p=71150385
berndblb said:
To flash the stock blob in fastboot you download the Asus firmware from here: https://www.asus.com/support/Download/28/1/0/11/fq2B3oq64av1O95/8/
Click to expand...
Click to collapse
Broken link ? that post isn't very old, either. ??
berndblb said:
Did you flash the rom in your current TWRP?
Something is off... Did you possibly flash the TF201 rom version??
Whatever you do - do not use Wipe Data from the bootloader!!
Reflash TWRP, format data, then reflash the rom
And report in more detail what you did
Click to expand...
Click to collapse
I did wipe data from bootloader, now I can't go to bootloader. How to revive my tf700t?
Please help
Thanks
ketulharini said:
I did wipe data from bootloader, now I can't go to bootloader. How to revive my tf700t?
Please help
Thanks
Click to expand...
Click to collapse
You'll need to refer to post #8. However, the link to the tf700 stock blob is broken. You'll have to search Google for one. They're out there, but it does require digging .Make sure the one you get is for the proper SKU of your tablet (US, Worldwide, JP, etc.). I completed the process myself maybe a month ago. Good luck!
monogwai said:
You'll need to refer to post #8. However, the link to the tf700 stock blob is broken. You'll have to search Google for one. They're out there, but it does require digging .Make sure the one you get is for the proper SKU of your tablet (US, Worldwide, JP, etc.). I completed the process myself maybe a month ago. Good luck!
Click to expand...
Click to collapse
I got the stock blob ww version.
Just tab doesn't stay on fastboot mode keeps rebooting.
Don't know how to do it.
Is it possible to get stable fastboot screen some how? Or just flash the bootloader to get fastboot working.
May be this noob question but I don't know how to do.
Thanks
ketulharini said:
I got the stock blob ww version.
Just tab doesn't stay on fastboot mode keeps rebooting.
Don't know how to do it.
Is it possible to get stable fastboot screen some how? Or just flash the bootloader to get fastboot working.
May be this noob question but I don't know how to do.
Thanks
Click to expand...
Click to collapse
There is one more piece to the puzzle- hold short while I dig it up.
Here it is: http://www.transformerforums.com/forum/transformer-pad-infinity-tf700-tegra-3-development/46302-guide-help-my-transformer-tf700-boots-only-recovery.html
Do be *very* careful. Read thrice, do it once. Especially if you're feeling noob-y.
monogwai said:
There is one more piece to the puzzle- hold short while I dig it up.
Here it is: http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Do be *very* careful. Read thrice, do it once. Especially if you're feeling noob-y.
Click to expand...
Click to collapse
Thanks for this information.
One more question,
My tab is keep bootlooping neither it stays on twrp nor bootloader.
It has blue screen of recovery that is twrp after 5 to 10 seconds it boots again.
Is this enough time to execute the commands while it is on blue screen?
Thanks
ketulharini said:
Thanks for this information.
One more question,
My tab is keep bootlooping neither it stays on twrp nor bootloader.
It has blue screen of recovery that is twrp after 5 to 10 seconds it boots again.
Is this enough time to execute the commands while it is on blue screen?
Thanks
Click to expand...
Click to collapse
Well, that depends on several things. What I did was write a short little DOS batch file to process all the fastboot commands. So, with your batch file ready, open your command prompt (change directory to your adb/fastboot directory if it's not set in system's 'path=' environment variable) and have the batch command typed in, ready to hit enter. Tether to pc via USB, proceed to boot to adb. The second you hear windows make the USB notification sound, slap that enter key. It should just process and reset the tab and get you out of TWRP bootloop. Which is just step one.
If you aren't familiar with writing bat files for DOS, let me know.
monogwai said:
Well, that depends on several things. What I did was write a short little DOS batch file to process all the fastboot commands. So, with your batch file ready, open your command prompt (change directory to your adb/fastboot directory if it's not set in system's 'path=' environment variable) and have the batch command typed in, ready to hit enter. Tether to pc via USB, proceed to boot to adb. The second you hear windows make the USB notification sound, slap that enter key. It should just process and reset the tab and get you out of TWRP bootloop. Which is just step one.
If you aren't familiar with writing bat files for DOS, let me know.
Click to expand...
Click to collapse
You mean a batch file with the adb commands right? Once he can boot into fastboot he has all the time in the world to run the commands for the buster99 (description in post #8). Depending on what situation he came from before, it might be a good idea to start all fresh...
The tricky thing are the adb push bootit.ko and the insmod command. Those have to be timed just right to get executed, so a batch file might come in handy. Both commands only take a second or two to execute, so your window of 5 seconds could work. Maybe not in the same session, but they should work.
If the insmod command does not kick the tablet into the bootloader, there are 2 possible reasoons:
adb push bootit.ko did not work
the insmod command did not work
To find out if the file push worked you could add a simple list command for the contents of /sdcard/. Again - tricky, I know since you still are working with the 5 sec window, but that's what you got to work with...
That would look something like in the attached picture. So after pushing bootit.ko you issue:
Code:
adb shell ls /sdcard/
Try it with the batch file, try it with single commands... Don't give up. As long as you have any kind of adb access you should be able to solve it.
Good luck!
berndblb said:
You mean a batch file with the adb commands right?
Click to expand...
Click to collapse
Yeah.
berndblb said:
Once he can boot into fastboot he has all the time in the world to run the commands for the buster99 (description in post #8).
Click to expand...
Click to collapse
Again, mistake in my terminology. What I meant to say is, batch commands for the process involving the Bootit.ko- the adb portion.
Thanks for clearing that up.
@ketulharini
Anyhow, I was unable to get the process to take without having automated *every last step* of the process. Literally open the cmd window, have the command for your batch file typed in ready to go, and plug in. Hear the noise from windows and slap enter asap. That's the only way I could get it in time, and I'm a ridiculously fast typist.
monogwai said:
Yeah.
Again, mistake in my terminology. What I meant to say is, batch commands for the process involving the Bootit.ko- the adb portion.
Thanks for clearing that up.
@ketulharini
Anyhow, I was unable to get the process to take without having automated *every last step* of the process. Literally open the cmd window, have the command for your batch file typed in ready to go, and plug in. Hear the noise from windows and slap enter asap. That's the only way I could get it in time, and I'm a ridiculously fast typist.
Click to expand...
Click to collapse
Care to share the batch file?