Related
Hey guys,
So, basically I'm giving my finishing touches to the new version 1.2.0.0 of my application Android Recovery Manager...
Since my phone has been stolen, so I'm not able to test..
I just want any of you to test this for me:
1. Do not connect your device.
2. Execute this command "fastboot -s SERIALNUMBER" where the SERIALNUMBER is your device's serial number.
3. it will say "< waiting for device >"
4. Connect your phone.
What happens?
Can you post me the output please? I need to know what happens exactly after that
About ADB, what's the output of something like this:
"adb -s SERIALNUMBER wait-for-device"
If you write a wrong serial number, and connect your device will it continue? or will it still wait for the device with the correct "SERIALNUMBER" to be connected?
Thanks
Where's the link to v1.2.0.0? I will test for you.
dansharpy said:
Where's the link to v1.2.0.0? I will test for you.
Click to expand...
Click to collapse
I still didn't release it, I just wanna know if both adb and fastboot commands wait for only the device with the entered serial number..
Those are the last things I need to know to release the new version..
It would be great if you can test them for me
Thanks
Mine still says 'waiting for device' when i connect it. Dont think there's anything wrong with my adb as i can use it to read the device serial and reboot. Tried everything and still doesnt do anything.
dansharpy said:
Mine still says 'waiting for device' when i connect it. Dont think there's anything wrong with my adb as i can use it to read the device serial and reboot. Tried everything and still doesnt do anything.
Click to expand...
Click to collapse
Thank you!
I think I know what's wrong.
Can you execute those commands please?
- adb reboot-bootloader
- fastboot -s SERIALNUMBER
Write them exactly after each other, don't wait for the device to get into bootloader.
It should say < waiting for device >, I'm wondering if it still waits even when the device enters into bootloader and says on your device "FASTBOOT USB".
If yes, you can cancel the command by pressing CTR + C on your keyboard.
To restart your phone into OS execute fastboot reboot
When you're done with the steps above, can you also test this for me please:
- Make sure your device is opened normally and USB debugging is enabled.
- Do not connect your phone.
- Execute adb -s SERIALNUMBER wait-for-device
- Connect your phone.
- Does it recognize it?
Thanks alot dude
Should i have the phone connected for the first bit:
'Can you execute those commands please?
- adb reboot-bootloader
- fastboot -s SERIALNUMBER'
Or connect it when it says 'waiting for device'?
The second thing you asked me to do comes up saying adb version and then a long list of adb commands. It does this as soon as i press enter on the command, before i have a chance to connect the device. Then goes back to an empty command prompt 'c:\adb:>'
---------- Post added at 02:04 PM ---------- Previous post was at 01:55 PM ----------
Ok on the first bit you asked me to do;
If the device is connected: It doesnt allow you to type anything until it has rebooted into bootloader. So you cant type the 'fastboot -s SERIAL NUMBER' until its already in bootloader menu. EDIT: Sorry just tried it again but typing the command regardless of if it showed up on the screen, it did say <waiting for device> but boots into bootloader so quickly you have to type the commands really quickly.
If the device isnt connected: It just comes up saying 'error: device not found' after you press enter after the 'adb reboot-bootloader' command.
Should i have the phone connected for the first bit:
'Can you execute those commands please?
- adb reboot-bootloader
- fastboot -s SERIALNUMBER'
Click to expand...
Click to collapse
Yes, connect your phone then execute those commands.
The second thing you asked me to do comes up saying adb version and then a long list of adb commands. It does this as soon as i press enter on the command, before i have a chance to connect the device. Then goes back to an empty command prompt 'c:\adb:>'
Click to expand...
Click to collapse
are you sure you wrote it exactly the same with no typos?
it should be "adb -s SERIALNUMBER wait-for-device" where the serial number is your phone's serial number and without quotes for sure.
Make sure there is only one space when needed and wait-for-device is written eactly like that right after the space after your serial number.
Thanks
Ok on the first bit you asked me to do;
If the device is connected: It doesnt allow you to type anything until it has rebooted into bootloader. So you cant type the 'fastboot -s SERIAL NUMBER' until its already in bootloader menu.
If the device isnt connected: It just comes up saying 'error: device not found' after you press enter after the 'adb reboot-bootloader' command.
Click to expand...
Click to collapse
Can you execute the command "fastboot -s SERIAL NUMBER" and when it says < waiting for device >:
- Open your phone into HBOOT manually and press bootloader.
- Anything happens next?
ah, sorry didnt write the wait for device part, i thought that was what it should come up with after entering the command!
When entered properly the cursor waits under the command, then when i connect the phone it starts a new blank command prompt 'c:\adb>'
dansharpy said:
ah, sorry didnt write the wait for device part, i thought that was what it should come up with after entering the command!
When entered properly the cursor waits under the command, then when i connect the phone it starts a new blank command prompt 'c:\adb>'
Click to expand...
Click to collapse
hahah it's okay
That's exactly what I wanted to know thanks
I need to know one more thing about ADB please, can you try this:
"adb -s 1234566 wait-for-device" exactly as it is, and connect your phone.
Does the the wait cursor go away and starts a new blank prompt? or it just stays there?
claudenegm said:
Can you execute the command "fastboot -s SERIAL NUMBER" and when it says < waiting for device >:
- Open your phone into HBOOT manually and press bootloader.
- Anything happens next?
Click to expand...
Click to collapse
How do i get into HBOOT with the phone plugged in still? Or do you mean execute the command, put phone into HBOOT and then connect phone?
If you press vol- and power it just vibrates but doesnt load into HBOOT.
---------- Post added at 02:20 PM ---------- Previous post was at 02:17 PM ----------
claudenegm said:
hahah it's okay
That's exactly what I wanted to know thanks
I need to know one more thing about ADB please, can you try this:
"adb -s 1234566 wait-for-device" exactly as it is, and connect your phone.
Does the the wait cursor go away and starts a new blank prompt? or it just stays there?
Click to expand...
Click to collapse
It just stays waiting under the command, i assume for the device with serial 1234566?
How do i get into HBOOT with the phone plugged in still? Or do you mean execute the command, put phone into HBOOT and then connect phone?
If you press vol- and power it just vibrates but doesnt load into HBOOT.
Click to expand...
Click to collapse
Yes, that's what I meant, sorry
- Execute the command.
- Turn off your phone.
- Press Vol. Down + Power
- Press power down to select Bootloader.
- Connect your device, it should read on your phone FASTBOOT USB.
- What happens next on your PC? A new blank line shows or what?
It just stays waiting under the command, i assume for the device with serial 1234566?
Click to expand...
Click to collapse
Yea, that's exactly what I needed. I was checking if the wait-for-device is only for the right serial number or not, as my application needs to wait for the specific device until it restarts to begin executing the commands, so basically this is an easier way for me to wait for the device than by doing a loop, which takes more memory resources
claudenegm said:
How do i get into HBOOT with the phone plugged in still? Or do you mean execute the command, put phone into HBOOT and then connect phone?
If you press vol- and power it just vibrates but doesnt load into HBOOT.[/
Yes, that's what I meant, sorry
- Execute the command.
- Turn off your phone.
- Press Vol. Down + Power
- Press power down to select Bootloader.
- Connect your device, it should read on your phone FASTBOOT USB.
- What happens next on your PC? A new blank line shows or what?
Yea, that's exactly what I needed. I was checking if the wait-for-device is only for the right serial number or not, as my application needs to wait for the specific device until it restarts to begin executing the commands, so basically this is an easier way for me to wait for the device than by doing a loop, which takes more memory resources
Click to expand...
Click to collapse
Yep, it brings up a new blank command line when the device is in HBOOT.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
dansharpy said:
claudenegm said:
How do i get into HBOOT with the phone plugged in still? Or do you mean execute the command, put phone into HBOOT and then connect phone?
If you press vol- and power it just vibrates but doesnt load into HBOOT.[/
Yep, it brings up a new blank command line when the device is in HBOOT.
Click to expand...
Click to collapse
Wow, you really helped me a lot
Thank you!
I just have one last question please, if you execute this:
"fastboot -s 1234566" does it wait even if you connected your device in hboot?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
claudenegm said:
dansharpy said:
claudenegm said:
Wow, you really helped me a lot
Thank you!
I just have one last question please, if you execute this:
"fastboot -s 1234566" does it wait even if you connected your device in hboot?
Click to expand...
Click to collapse
Yes, it keeps waiting even if device is in HBOOT.
Ive just got to pop out for a while, ill check this thread when i get back though to make sure you dont need anything else.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
dansharpy said:
claudenegm said:
dansharpy said:
Yes, it keeps waiting even if device is in HBOOT.
Ive just got to pop out for a while, ill check this thread when i get back though to make sure you dont need anything else.
Click to expand...
Click to collapse
Thanks a lot
That's all I needed to know anyways!
Thanks again, you really helped me out
Click to expand...
Click to collapse
Click to expand...
Click to collapse
v1.2.0.0 has been released!
Android Recovery Manager
I hope I can save it but after 4 hours of trying and reading I can't seem to do it.
I was running an unlocked tf300 with cleanrom. I wanted to update to the newest version of cleanrom and have my tablet on that and ready for school for next term. I downloaded cleanrom on laptop and put it on my micro sd. Went and grabbed the tablet and tried using rom manager to install from sd and backup the os that was on it. Didn't work. So booted into the fastboot spot (vol down and power) and decided i should wipe data since i was there. Went over to that and pushed vol up (once). Let it sit for like 45 minutes and was still on the same screen. Thought to myself well it must be done. Shut off the tablet to restart it.
This is where the problem came up. Now i'm stuck on asus logo. The VD+P doesn't do anything but reboot into the asus logo. The VU+P will put it into a black screen and windows sees it as Asus transformer Prime APX interface. But adb can't see the device. Just device manager. typing fastboot -i 0x0b05 thing just says <waiting for device>
Every post i've read seems to tell people to just push VD+P but if i could do that and get to recovery i wouldn't be doing this. I can't put a blob file into the root sd of the tablet because I can't see the tablet.
Any help would be greatly appreciated.
Maybe this link can help.
http://forum.xda-developers.com/showthread.php?t=2034866
Device manager already sees it as transformer prime apx thing though. So i assume by getting it into APX mode doing the VU+P method it is in apx? or is that not mean it's actually in apx?
bigworm82 said:
Device manager already sees it as transformer prime apx thing though. So i assume by getting it into APX mode doing the VU+P method it is in apx? or is that not mean it's actually in apx?
Click to expand...
Click to collapse
Apx mode is not going to do you any good. The previous link also provides info on blootloader " recovery " mode.
Try the universal naked drivers from this link and try fastboot again.
http://forum.xda-developers.com/showthread.php?t=1766220
If that does not work leave off ' -i 0x0b05 ' in fastboot -i 0x0b05 command and try again.
tobdaryl said:
Apx mode is not going to do you any good. The previous link also provides info on blootloader " recovery " mode.
Try the universal naked drivers from this link and try fastboot again.
http://forum.xda-developers.com/showthread.php?t=1766220
If that does not work leave off ' -i 0x0b05 ' in fastboot -i 0x0b05 command and try again.
Click to expand...
Click to collapse
Already installed the naked drivers and that's when the computer recognized it in the device manager portion as the asus prime apx interface thing. It still just says <waiting for device> in everything i try on fastboot.
bigworm82 said:
Already installed the naked drivers and that's when the computer recognized it in the device manager portion as the asus prime apx interface thing. It still just says <waiting for device> in everything i try on fastboot.
Click to expand...
Click to collapse
Are you in fastboot mode or apx when you give the commands?
tobdaryl said:
Are you in fastboot mode or apx when you give the commands?
Click to expand...
Click to collapse
i just go into cmd and go to the folder i put fastboot and all in and type fastboot..... so on.. what should i do?
bigworm82 said:
i just go into cmd and go to the folder i put fastboot and all in and type fastboot..... so on.. what should i do?
Click to expand...
Click to collapse
I know you previously said you couldn't get into recovery-bootloader menu but that is what we have to accomplish. Apx mode on this unit is only good if you previously installed nvflash and had all of the proper backup files.
The first link I provided provides 9 ways to get into bootloader menu and from there either fastboot mode (usb symbol) or recovery (RCK). I know some may not work but we only need one.
tobdaryl said:
I know you previously said you couldn't get into recovery-bootloader menu but that is what we have to accomplish. Apx mode on this unit is only good if you previously installed nvflash and had all of the proper backup files.
The first link I provided provides 9 ways to get into bootloader menu and from there either fastboot mode (usb symbol) or recovery (RCK). I know some may not work but we only need one.
Click to expand...
Click to collapse
I'm confused the first link is to get into APX mode from how i read it on the page. Am i wrong? I have no issues getting into this mode.
bigworm82 said:
I'm confused the first link is to get into APX mode from how i read it on the page. Am i wrong? I have no issues getting into this mode.
Click to expand...
Click to collapse
apx or bootloader menu-recovery.
To use this guide to enter the bootloader menu just use volume down everywhere it says volume up. Everything else is the same.
4. with unit powered on hold volume down and press reset with paperclip - (don't press hard) reset is located about 25mm or 1in below the sdcard
try this one.
tobdaryl said:
apx or bootloader menu-recovery.
4. with unit powered on hold volume down and press reset with paperclip - (don't press hard)
reset is located about 25mm or 1in below the sdcard
try this one.
To use this guide to enter the bootloader menu just use volume down everywhere it says volume up. Everything else is the same.
Click to expand...
Click to collapse
nope just back to asus logo
bigworm82 said:
nope just back to asus logo
Click to expand...
Click to collapse
use cmd(terminal) in same directory as fastboot
adb reboot then immediately hold volume down
if no help then
adb reboot bootloader - no need for volume on this one
tobdaryl said:
use cmd(terminal) in same directory as fastboot
adb reboot then immediately hold volume down
if no help then
adb reboot bootloader - no need for volume on this one
Click to expand...
Click to collapse
Device not found.
bigworm82 said:
Device not found.
Click to expand...
Click to collapse
Force power off by holding power a few seconds.
Plug power cord into tab with the other end of the power cord not plugged into anything. Hold volume down and plug other end of power cord into pc. This done without pressing power again after it is powered off. Easier to do than describe.
tobdaryl said:
Force power off by holding power a few seconds.
Plug power cord into tab with the other end of the power cord not plugged into anything. Hold volume down and plug other end of power cord into pc. This done without pressing power again after it is powered off. Easier to do than describe.
Click to expand...
Click to collapse
The Problem lies in holding the volume down button. No matter how i turn it on. either plugging it in while holding power down, reset button, letting it die and then plugging it in and turning it on....it just goes into the asus logo screen .
bigworm82 said:
The Problem lies in holding the volume down button. No matter how i turn it on. either plugging it in while holding power down, reset button, letting it die and then plugging it in and turning it on....it just goes into the asus logo screen .
Click to expand...
Click to collapse
I'm sorry, I did understand that from the beginning but the only things that can save you is get into that menu or recovery or your tab accepts a fastboot or adb command. That is the reason you keep getting pushed into that direction.
My best guesses are out. Sometimes redoing something you have already done twice works.
My experience and all I have read rom manager has issues on this tab. Also many who wiped data from the bootloader- recovery menu reach this same point when they reboot.
Some have recovered by just doing each thing again and again and suddenly something works.
Yeah i fear i'm just going to have to call ASUS . sad panda. i keep trying different methods of doing the VD+P method but it just won't get into recovery.
bigworm82 said:
Yeah i fear i'm just going to have to call ASUS . sad panda. i keep trying different methods of doing the VD+P method but it just won't get into recovery.
Click to expand...
Click to collapse
I'm sorry but I am afraid you are correct. If unable to use adb, fastboot, or get into recovery there aren't any other options. Sorry if I pushed more than I should but I wanted to see a more positive result than calling Asus.
Good Luck!
tobdaryl said:
I'm sorry but I am afraid you are correct. If unable to use adb, fastboot, or get into recovery there aren't any other options. Sorry if I pushed more than I should but I wanted to see a more positive result than calling Asus.
Good Luck!
Click to expand...
Click to collapse
I appreciate the attempts though . I really didn't want to have to call them lol.
bigworm82 said:
I appreciate the attempts though . I really didn't want to have to call them lol.
Click to expand...
Click to collapse
If you explain you were having issues with your tab and used wipe data hoping to correct the problem. Now when you turn on it just stays on the asus logo maybe they will repair it without cost.
If you go into detail you probably won't get lucky.
Is anyone else having issues while in recovery? I am running CWM and I can't see my tablet properly. Windows tells me it can't identify the device and when I try to make it use nvidias drivet (or any driver) it tells me it's not compatible and something about it not being 64bit even though there are x64 drivers available. Works perfect everywhere else, just looking to see if anyone else has dealt with that.
Sent from my One M8
Keithn said:
Is anyone else having issues while in recovery? I am running CWM and I can't see my tablet properly. Windows tells me it can't identify the device and when I try to make it use nvidias drivet (or any driver) it tells me it's not compatible and something about it not being 64bit even though there are x64 drivers available. Works perfect everywhere else, just looking to see if anyone else has dealt with that.
Sent from my One M8
Click to expand...
Click to collapse
Figured out my issue in a way. While in CWM it doesn't appear to report to windows properly, stock recovery works fine.
Keithn said:
Figured out my issue in a way. While in CWM it doesn't appear to report to windows properly, stock recovery works fine.
Click to expand...
Click to collapse
Could you send me stock recovery so I can take a look inside the init.rc
Yeah, I'll do that today
Sent from my One M8
Keithn said:
Yeah, I'll do that today
Sent from my One M8
Click to expand...
Click to collapse
I found it inside the stock nvidia images for testing on the k1 board thanks.
This appeared to be the issue https://github.com/cm-ardbeg/androi...b4fd46180/rootdir/etc/init.recovery.ardbeg.rc
Unjustified Dev said:
I found it inside the stock nvidia images for testing on the k1 board thanks.
This appeared to be the issue https://github.com/cm-ardbeg/androi...b4fd46180/rootdir/etc/init.recovery.ardbeg.rc
Click to expand...
Click to collapse
If you want me to test anything out with it let me know. Maybe this will help pinpointing the issues for the touch driver if I can pull logs while in recovery.
Keithn said:
If you want me to test anything out with it let me know. Maybe this will help pinpointing the issues for the touch driver if I can pull logs while in recovery.
Click to expand...
Click to collapse
I compiled this one earlier let me know if it works. It doesn't have touch support but I can add it once adb is confirmed working
Unjustified Dev said:
I compiled this one earlier let me know if it works. It doesn't have touch support but I can add it once adb is confirmed working
Click to expand...
Click to collapse
Still having issues in windows it shows up as "Unknown USB Device (Configuration Descriptor Request Failed)" and gives me
Code:
Windows has stopped this device because it has reported problems. (Code 43)
A request for the USB configuration descriptor failed.
for device status.
I'll give it a try in Linux but if it is not reporting properly then I don't think it will work there either.
__________________________
Nothing in Ubuntu either, even lsusb doesn't list it.
Keithn said:
Still having issues in windows it shows up as "Unknown USB Device (Configuration Descriptor Request Failed)" and gives me
Code:
Windows has stopped this device because it has reported problems. (Code 43)
A request for the USB configuration descriptor failed.
for device status.
I'll give it a try in Linux but if it is not reporting properly then I don't think it will work there either.
__________________________
Nothing in Ubuntu either, even lsusb doesn't list it.
Click to expand...
Click to collapse
This is crazy does adb work in the recovery you compile from their git?
Unjustified Dev said:
This is crazy does adb work in the recovery you compile from their git?
Click to expand...
Click to collapse
I can't even get the menu to pop up. On stock it's just vol + and power and then you can see the menus and select adb sideload etc. On my compiled one it just sits at the No Command screen even after pressing those buttons, and it shows up as the same thing in my PC as CWM did.
Keithn said:
Is anyone else having issues while in recovery? I am running CWM and I can't see my tablet properly. Windows tells me it can't identify the device and when I try to make it use nvidias drivet (or any driver) it tells me it's not compatible and something about it not being 64bit even though there are x64 drivers available. Works perfect everywhere else, just looking to see if anyone else has dealt with that.
Sent from my One M8
Click to expand...
Click to collapse
I am having same issue
---------- Post added at 02:50 AM ---------- Previous post was at 02:46 AM ----------
Keithn said:
I can't even get the menu to pop up. On stock it's just vol + and power and then you can see the menus and select adb sideload etc. On my compiled one it just sits at the No Command screen even after pressing those buttons, and it shows up as the same thing in my PC as CWM did.
Click to expand...
Click to collapse
I have same issue but have a boot loop so I am bricked at the moment
---------- Post added at 02:55 AM ---------- Previous post was at 02:50 AM ----------
Okay now when I also enter recovery mode I have a blank screen can not boot into the system because of a boot loop, does anyone have any surgestions ?????????
MRobbo80 said:
I am having same issue
---------- Post added at 02:50 AM ---------- Previous post was at 02:46 AM ----------
I have same issue but have a boot loop so I am bricked at the moment
---------- Post added at 02:55 AM ---------- Previous post was at 02:50 AM ----------
Okay now when I also enter recovery mode I have a blank screen can not boot into the system because of a boot loop, does anyone have any surgestions ?????????
Click to expand...
Click to collapse
go into fastboot and flash a recovery then boot into recovery
Just tested stock recovery and the device doesn't even show as being connected until I select sideload then all I get is sideload.
Keithn said:
go into fastboot and flash a recovery then boot into recovery
Just tested stock recovery and the device doesn't even show as being connected until I select sideload then all I get is sideload.
Click to expand...
Click to collapse
My screen is black I can not see any options I am using the custom new cwm
Did you try what I said? Can you at least get into the boot loader?
Sent from my SHIELD Tablet
Keithn said:
Did you try what I said? Can you at least get into the boot loader?
Sent from my SHIELD Tablet
Click to expand...
Click to collapse
sorry not sure how to boot in to fastboot?
MRobbo80 said:
sorry not sure how to boot in to fastboot?
Click to expand...
Click to collapse
I meant to say boot into the bootloader so you can use fastboot. From Nvidia
Code:
HW method:
Turn off the device
Press "Volume Down" -> "Power", hold "Volume Down" and leave Power buttons till device boots
So basically just hold vol - then press power and keep the vol button held but not the power. Should give you a black screen with some words on it and you can select a few different things. When you are there use fastboot like you would adb. Get a cwm image and give it the command
Code:
fastboot flash recovery cwm.img
Put what ever name and location you have for your recovery image in place of cwm.img.
Keithn said:
I meant to say boot into the bootloader so you can use fastboot. From Nvidia
Code:
HW method:
Turn off the device
Press "Volume Down" -> "Power", hold "Volume Down" and leave Power buttons till device boots
So basically just hold vol - then press power and keep the vol button held but not the power. Should give you a black screen with some words on it and you can select a few different things. When you are there use fastboot like you would adb. Get a cwm image and give it the command
Code:
fastboot flash recovery cwm.img
Put what ever name and location you have for your recovery image in place of cwm.img.
Click to expand...
Click to collapse
Thanks for your fast reply here is whats happening I have been working with a dev to get acip up and running, I have cwm recovery and have fully wiped the device and installed acip which currently is bootlooping. Now my problem is when I try to enter fastboot holding down -volume key and pressing the power it just splashes to the boot logo so no luck there but when I hold down volume + and power key I can hear the sound of a usb connecting to my computer but have a black screen only. So when I check device manager under windows I can see a yellow caution mark APX unknown device so at the moment trying to find a driver that will work so that's where I am really
MRobbo80 said:
Thanks for your fast reply here is whats happening I have been working with a dev to get acip up and running, I have cwm recovery and have fully wiped the device and installed acip which currently is bootlooping. Now my problem is when I try to enter fastboot holding down -volume key and pressing the power it just splashes to the boot logo so no luck there but when I hold down volume + and power key I can hear the sound of a usb connecting to my computer but have a black screen only. So when I check device manager under windows I can see a yellow caution mark APX unknown device so at the moment trying to find a driver that will work so that's where I am really
Click to expand...
Click to collapse
Grab theses and see if they work. They are included with Nvidias tegra development tools.
Nvidia Drivers (shouldn't be much different than googles drivers but here they are.)
I don't think you are going to want it in APX anyways. I noticed it can be a pain to get the bootloader try keeping vol - held and only pressing power for a couple of seconds at most and give it a second for the screen to turn on. If you hit the splash screen then you missed the bootloader.
Keithn said:
Grab theses and see if they work. They are included with Nvidias tegra development tools.
Nvidia Drivers (shouldn't be much different than googles drivers but here they are.)
I don't think you are going to want it in APX anyways. I noticed it can be a pain to get the bootloader try keeping vol - held and only pressing power for a couple of seconds at most and give it a second for the screen to turn on. If you hit the splash screen then you missed the bootloader.
Click to expand...
Click to collapse
M8 IM IN MASSIVE THANK YOU :good::good::good::good::good::good::good::good::good::good::good::good::goodAM THAT TEXT IS SMALL HONESTLY thank you very much :good:
---------- Post added at 12:18 AM ---------- Previous post was at 12:07 AM ----------
MRobbo80 said:
M8 IM IN MASSIVE THANK YOU :good::good::good::good::good::good::good::good::good::good::good::good::goodAM THAT TEXT IS SMALL HONESTLY thank you very much :good:
Click to expand...
Click to collapse
My tablet is now fully restoring my backup in cwm as I speak have one big grin on my face at the mo.
MRobbo80 said:
M8 IM IN MASSIVE THANK YOU :good::good::good::good::good::good::good::good::good::good::good::good::goodAM THAT TEXT IS SMALL HONESTLY thank you very much :good:
---------- Post added at 12:18 AM ---------- Previous post was at 12:07 AM ----------
My tablet is now fully restoring my backup in cwm as I speak have one big grin on my face at the mo.
Click to expand...
Click to collapse
No problem good to hear :good:
So guys, the thing is: I haven't found a way to root nor to unlock the bootloader in this phone.
Focusing on the bootloader, there is an option in the Developer options which says "OEM unlocking", that supposedly allows the bootloader to be unlocked. Plugging the phone on the pc USB and using adb to get into fastboot works fine, but after typing "fastboot flashing unlock" the command prompt keeps on waiting with "..." for the next phone's action, that's where the problem begins: on the cellphone screen, right after the warnings about the consequences of unlocking the bootloader, appears: "Press the Volume UP/Down buttons to select Yes or No." If Volume_Down is pressed, it returns to fastboot, but if Volume_UP is pressed nothing happens, literally nothing, Power button also does nothing, the only one who works is Volume_Down, making it unable to unlock the bootloader via this method.
I tried to use "adb shell input keyevent 24" (knowing it wouldn't work) to try to send the Volume_Up command from the pc.
So I wanna know if there is a way that, through that fastboot waiting instance (the three dots "..."), I can send the Volume_Up command from the pc, enabling the Bootloader to be unlocked, making the root easy or even possible.
Thanks in advance!
Matt1355 said:
So guys, the thing is: I haven't found a way to root nor to unlock the bootloader in this phone.
Focusing on the bootloader, there is an option in the Developer options which says "OEM unlocking", that supposedly allows the bootloader to be unlocked. Plugging the phone on the pc USB and using adb to get into fastboot works fine, but after typing "fastboot flashing unlock" the command prompt keeps on waiting with "..." for the next phone's action, that's where the problem begins: on the cellphone screen, right after the warnings about the consequences of unlocking the bootloader, appears: "Press the Volume UP/Down buttons to select Yes or No." If Volume_Down is pressed, it returns to fastboot, but if Volume_UP is pressed nothing happens, literally nothing, Power button also does nothing, the only one who works is Volume_Down, making it unable to unlock the bootloader via this method.
I tried to use "adb shell input keyevent 24" (knowing it wouldn't work) to try to send the Volume_Up command from the pc.
So I wanna know if there is a way that, through that fastboot waiting instance (the three dots "..."), I can send the Volume_Up command from the pc, enabling the Bootloader to be unlocked, making the root easy or even possible.
Thanks in advance!
Click to expand...
Click to collapse
Just because you have the "OEM unlock" option in settings doesn't necessarily mean you can unlock bootloader, the manufacturer or your carrier may have disabled that option in fastboot. Not all devices can be unlocked.
Sent from my SM-S903VL using Tapatalk
still waiting for rooting app, too...
Why God! Why??!! Why Google & Lenovo d'nt just make possible 4 rooting?
Kirzoczek said:
Why Godzin why??!! Why Google d'nt just make possible 4 rooting?
Click to expand...
Click to collapse
Well i'm pissed of. Lenovo just turn off vol up button. U just can't press it in fastboot mode to unlock bootloader. F...... ?
Kirzoczek said:
Why God! Why??!! Why Google & Lenovo d'nt just make possible 4 rooting?
Click to expand...
Click to collapse
Google isn't the the one that has control of that, that's controlled by the device manufacturers and/or each mobile carrier. In this case, it's controlled by Lenovo
The only devices that Google has control over whether they're rootable or not is only the Nexus and Pixel devices, not any of the others.
I DO NOT PROVIDE HELP IN PERSONAL MESSAGE, I DO NOT TAKE REQUESTS IN PERSONAL MESSAGE, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
---------- Post added at 04:01 PM ---------- Previous post was at 03:47 PM ----------
Matt1355 said:
So guys, the thing is: I haven't found a way to root nor to unlock the bootloader in this phone.
Focusing on the bootloader, there is an option in the Developer options which says "OEM unlocking", that supposedly allows the bootloader to be unlocked. Plugging the phone on the pc USB and using adb to get into fastboot works fine, but after typing "fastboot flashing unlock" the command prompt keeps on waiting with "..." for the next phone's action, that's where the problem begins: on the cellphone screen, right after the warnings about the consequences of unlocking the bootloader, appears: "Press the Volume UP/Down buttons to select Yes or No." If Volume_Down is pressed, it returns to fastboot, but if Volume_UP is pressed nothing happens, literally nothing, Power button also does nothing, the only one who works is Volume_Down, making it unable to unlock the bootloader via this method.
I tried to use "adb shell input keyevent 24" (knowing it wouldn't work) to try to send the Volume_Up command from the pc.
So I wanna know if there is a way that, through that fastboot waiting instance (the three dots "..."), I can send the Volume_Up command from the pc, enabling the Bootloader to be unlocked, making the root easy or even possible.
Thanks in advance!
Click to expand...
Click to collapse
The command is supposed to be
fastboot OEM unlock
I DO NOT PROVIDE HELP IN PERSONAL MESSAGE, I DO NOT TAKE REQUESTS IN PERSONAL MESSAGE, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Yes, you have right. But what with this vol+ button?
Volume+ button is not working on Lenovo C2 ?
GPSSlovakia said:
Volume+ button is not working on Lenovo C2 ?
Click to expand...
Click to collapse
I mean that vol up did' t work in fastboot mode. When u try to unblock bootloader u have two options. U may choose yes or no. Offously vol up is for "yes" answer. And whoop!!! It don't work
How to restore the imei number of this phone ..i tried several methods to restore..pls help me
rijukrishnan said:
How to restore the imei number of this phone ..i tried several methods to restore..pls help me
Click to expand...
Click to collapse
If you didn't make an IMEI backup then we can't discuss restoring your IMEI at XDA, it's in the Forum Rules.
Sent from my SM-S903VL using Tapatalk
then what can i do next to make it in stock condetion
What is this message means
rijukrishnan said:
What is this message means
Click to expand...
Click to collapse
I think it is saying that the connection between PC and your device was interrupted for some reason. I was probably a problem with your cable being loose and losing connection where it plugs into your device.
It is not very likely but it could also be an unstable electrical supply grid in your area, the power in the building where you are could have dropped momentarily, I doubt this was the cause though, but it is one possibility.
Use a different cable or find a way to make sure it connects and stays connected, then try flashing again.
The error you have is described in the attachment below, it explains how to solve.
For future reference, the link below has a list of all flash tool errors and how to solve them.
https://forum.hovatek.com/thread-439.html
Sent from my SM-S903VL using Tapatalk
Droidriven said:
If you didn't make an IMEI backup then we can't discuss restoring your IMEI at XDA, it's in the Forum Rules.
Click to expand...
Click to collapse
i have a bckup of imei number
Eh..,,.... no unlock oem ... no root , bad phone
Droidriven said:
Just because you have the "OEM unlock" option in settings doesn't necessarily mean you can unlock bootloader, the manufacturer or your carrier may have disabled that option in fastboot. Not all devices can be unlocked.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
You can access the recovery for this model after you send the command (ADB and fastboot commands): "Adb reboot recovery" where "Adb reboot boot loader" and then you have to click on the volume up and the power button at the same time and its success
* But the problem is that I have not found the trwp compatible with this model to make the root that can help us
medzbody said:
You can access the recovery for this model after you send the command (ADB and fastboot commands): "Adb reboot recovery" where "Adb reboot boot loader" and then you have to click on the volume up and the power button at the same time and its success
* But the problem is that I have not found the trwp compatible with this model to make the root that can help us
Click to expand...
Click to collapse
TWRP for your device probably doesn't exist, you'll have to wait for someone to be interested in building TWRP for your model (not likely to happen if it hasn't already) or you can port or build your own TWRP.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
TWRP for your device probably doesn't exist, you'll have to wait for someone to be interested in building TWRP for your model (not likely to happen if it hasn't already) or you can port or build your own TWRP.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I do not know how to build twrp for my device you can help me
What about making a TWRP and then flashing it thru modified scatter file in flash tool
Hello,
At one point this tablet was working just fine. It sat for a while and now it boot loops. Shows the amazon logo and auto restarts.
I can hold the proper volume up or down key and it says "Recovery Mode" on the bottom left but never enters into it.
Oddly enough I wasn't screwing around trying to do something I shouldn't have, but for the life of me I can't figure out what the deal is. Have anything I can try to possibly recover it? or is it straight to the bin.
Thank you in advance.
Take care,
Try fastboot boot recovery.img with the help of PC, if it boots format data and install rom.
Shiva Kumar A said:
Try fastboot boot recovery.img with the help of PC, if it boots format data and install rom.
Click to expand...
Click to collapse
Yeah good idea I'll report back .. I mean I can't break it anymore heh. I'm going to blame gamma rays coming down from from space and flipping a single bit in my 6 year old tablet............... causing it to boot loop.
So thinking out
Shiva Kumar A said:
Try fastboot boot recovery.img with the help of PC, if it boots format data and install rom.
Click to expand...
Click to collapse
So thinking out loud.
How do I get the tablet in a spot to accept a fastboot via USB?
It doesn't start up correctly to booted android. It doesn't enter TWRP... it seems as if I am stuck right?
likwidchz said:
So thinking out
So thinking out loud.
How do I get the tablet in a spot to accept a fastboot via USB?
It doesn't start up correctly to booted android. It doesn't enter TWRP... it seems as if I am stuck right?
Click to expand...
Click to collapse
What's happening when you try to boot into fastboot mode? After entering fastboot mode in cmd "fastboot boot twrp.img" "(drag and drop twrp file after boot )" it'll boot into twrp.
Shiva Kumar A said:
What's happening when you try to boot into fastboot mode? After entering fastboot mode in cmd "fastboot boot twrp.img" "(drag and drop twrp file after boot )" it'll boot into twrp.
Click to expand...
Click to collapse
You will have to explain how I would boot it into fastboot mode if
1 The tablet doesn't fully boot up past the amazon logo.
2 I cant even enter TWRP.
What am I missing?
Thank you and cheers!
When the device is fully shutdown press volume down + power.or maybe volume up check your device's combination key
Shiva Kumar A said:
When the device is fully shutdown press volume down + power.or maybe volume up check your device's combination key
Click to expand...
Click to collapse
Right then what? I'm missing something here.
likwidchz said:
Right then what? I'm missing something here.
Click to expand...
Click to collapse
I can't understand you what you trying to ask?
Shiva Kumar A said:
I can't understand you what you trying to ask?
Click to expand...
Click to collapse
Hello apologies,
I'll try and be as verbose as possible this time
This executes
[email protected]:/usr/src/giza# ./boot-fastboot.sh
[2023-02-08 12:26:26.386801] Waiting for preloader
[2023-02-08 12:26:50.335150] Found port = /dev/ttyACM0
[2023-02-08 12:26:50.365886] Handshake
[2023-02-08 12:26:50.386040] Preloader ready, sending FACTFACT
*Holding the left volume button + power button for some time.
[email protected]:/usr/src/giza# fastboot flash recovery bin/recovery.img
< waiting for any device >
Ive had this execute once, but when it does it looks like it wiped out TWRP as I cant get the small text to appear on the bottom left hand corner of the tablet while it does a boot holding power and the volume button.
So I'm not quite sure what I can do now.
Is there a method to flash TWRP with fastboot? or is that what the recovery is?
Could you provide a detailed list of items to try out and some high level instructions.
I've been thumbing through https://forum.xda-developers.com/t/unlock-root-twrp-unbrick-fire-hd-8-2016-giza.4303443/ this guide, but realize I'm not sure which step I need to start from, so I have bene trying a bunch of things and kind of stumped.
Thank you Shiva,
likwidchz said:
Right then what? I'm missing something here.
Click to expand...
Click to collapse
Bootloops are definitely a hassle sometimes. On your device your can either play the button game , watching the device closely and holding the the right button combo when the device goes black in hope that the device will boot into recovery or fastboot when it starts the bootloop again. The easiest thing for me to do sometimes is wait for the battery to drain completely dead then plug the device into the computer while holding the button combination to enter fastboot or recovery. The crappy part is waiting for the battery to drain. I did do a google and learned that Giza uses vol down button and pwr button to enter recovery. But with a dead battery it's likely one will only need to hold vol down button while plugging in the device. If it's in a bootloop it's probably not necessary to hold power button as well, just need to hold the vol down button at the time. I will say with a fair amount of confidence that the device is not a loss cause. Good luck, hope you get it working.
jonpjingleheimler said:
Bootloops are definitely a hassle sometimes. On your device your can either play the button game , watching the device closely and holding the the right button combo when the device goes black in hope that the device will boot into recovery or fastboot when it starts the bootloop again. The easiest thing for me to do sometimes is wait for the battery to drain completely dead then plug the device into the computer while holding the button combination to enter fastboot or recovery. The crappy part is waiting for the battery to drain. I did do a google and learned that Giza uses vol down button and pwr button to enter recovery. But with a dead battery it's likely one will only need to hold vol down button while plugging in the device. If it's in a bootloop it's probably not necessary to hold power button as well, just need to hold the vol down button at the time. I will say with a fair amount of confidence that the device is not a loss cause. Good luck, hope you get it working.
Click to expand...
Click to collapse
I had a weird assumption that I had to wait for the battery to drain. Its just weird this thing happened when it was working just fine.. usually I know when I screw something up pretty good.
I'm more curious on what command I need to be running and constantly retry to load up TWRP via fastboot.
Thanks!
likwidchz said:
I had a weird assumption that I had to wait for the battery to drain. Its just weird this thing happened when it was working just fine.. usually I know when I screw something up pretty good.
I'm more curious on what command I need to be running and constantly retry to load up TWRP via fastboot.
Thanks!
Click to expand...
Click to collapse
From what you have described issuing any command from a computer to the device wouldn't be possible as the device is bootlooping. I could not find any info on button combination to enter fastboot only recovery. from recovery there is a reboot to bootloader or fastboot option. that is your best bet. I have messed with at least a few different kindles in my time but there is always someone out there that has done more and may have another option they can add.
likwidchz said:
Hello apologies,
I'll try and be as verbose as possible this time
This executes
[email protected]:/usr/src/giza# ./boot-fastboot.sh
[2023-02-08 12:26:26.386801] Waiting for preloader
[2023-02-08 12:26:50.335150] Found port = /dev/ttyACM0
[2023-02-08 12:26:50.365886] Handshake
[2023-02-08 12:26:50.386040] Preloader ready, sending FACTFACT
*Holding the left volume button + power button for some time.
[email protected]:/usr/src/giza# fastboot flash recovery bin/recovery.img
< waiting for any device >
Ive had this execute once, but when it does it looks like it wiped out TWRP as I cant get the small text to appear on the bottom left hand corner of the tablet while it does a boot holding power and the volume button.
So I'm not quite sure what I can do now.
Is there a method to flash TWRP with fastboot? or is that what the recovery is?
Could you provide a detailed list of items to try out and some high level instructions.
I've been thumbing through https://forum.xda-developers.com/t/unlock-root-twrp-unbrick-fire-hd-8-2016-giza.4303443/ this guide, but realize I'm not sure which step I need to start from, so I have bene trying a bunch of things and kind of stumped.
Thank you Shiva,
Click to expand...
Click to collapse
Message me on telegram brother @HeyShiva
Shiva Kumar A said:
Message me on telegram brother @HeyShiva
Click to expand...
Click to collapse
Whats wrong with this forum?
likwidchz said:
Whats wrong with this forum?
Click to expand...
Click to collapse
Nothing, I can guide you there flawlessly. If you concerned about privacy no problem.
Shiva Kumar A said:
Nothing, I can guide you there flawlessly. If you concerned about privacy no problem.
Click to expand...
Click to collapse
I don't think you are the best person to guide on this one. You don't even seem to know what an Amazon tablet is, considering you suggested to fastboot boot when that cmd was patched back then in 2015.
@likwidchz If you're able to access fastboot thru boot-fastboot, erase preloader with fastboot erase boot0, reboot and run bootrom-step.sh again.
Rortiz2 said:
I don't think you are the best person to guide on this one. You don't even seem to know what an Amazon tablet is, considering you suggested to fastboot boot when that cmd was patched back then in 2015.
@likwidchz If you're able to access fastboot thru boot-fastboot, erase preloader with fastboot erase boot0, reboot and run bootrom-step.sh again.
Click to expand...
Click to collapse
Yes I don't know about this tablet, I thought it was just like any other tablets sorry
Rortiz2 said:
I don't think you are the best person to guide on this one. You don't even seem to know what an Amazon tablet is, considering you suggested to fastboot boot when that cmd was patched back then in 2015.
@likwidchz If you're able to access fastboot thru boot-fastboot, erase preloader with fastboot erase boot0, reboot and run bootrom-step.sh again.
Click to expand...
Click to collapse
Would you happen to be on IRC or some discord group?
I have done about ~7 of these tablets Suez/Giza but when something goes south, its not clear to me which step I need to start back from. Having a side conversation might help. In the end of the tablet is done, I am not going to be too broken up about it. But it's not a lost cause yet.
Thank you for the assistance! Much love.
--Take care.
likwidchz said:
Would you happen to be on IRC or some discord group?
I have done about ~7 of these tablets Suez/Giza but when something goes south, its not clear to me which step I need to start back from. Having a side conversation might help. In the end of the tablet is done, I am not going to be too broken up about it. But it's not a lost cause yet.
Thank you for the assistance! Much love.
--Take care.
Click to expand...
Click to collapse
I don't use IRC, but I do have Discord (R0rt1z2#3415).