Related
So... Anyone have any experience getting sticky bit turned off on fastboot? My phone boots to it anytime I try to reboot or do a regular boot up.
fallnSaint said:
So... Anyone have any experience getting sticky bit turned off on fastboot? My phone boots to it anytime I try to reboot or do a regular boot up.
Click to expand...
Click to collapse
Mine did that for a short while after I screwed up a flash, I reflashed boot and while running tossed the adb command to get into fastboot and then left it properly. Haven't seen it since.
KitsunePaws said:
Mine did that for a short while after I screwed up a flash, I reflashed boot and while running tossed the adb command to get into fastboot and then left it properly. Haven't seen it since.
Click to expand...
Click to collapse
To clarify... Flash boot from recovery, while that is running adb reboot bootloader? If that is the case I have a different set of problems to "boot", I can't get my pc to recognize the phone while in recovery. Everything else is recognized, even reinstalled drivers to be certain, pc doesn't even try to install a driver for recovery. Tried both TWRP & CWM.
fallnSaint said:
To clarify... Flash boot from recovery, while that is running adb reboot bootloader? If that is the case I have a different set of problems to "boot", I can't get my pc to recognize the phone while in recovery. Everything else is recognized, even reinstalled drivers to be certain, pc doesn't even try to install a driver for recovery. Tried both TWRP & CWM.
Click to expand...
Click to collapse
Memory is fuzzy but I'm pretty sure I did it from fastboot, this happened to me about the time shabby was trying to fastboot boot boot.img and I ended up flashing it instead.
KitsunePaws said:
Memory is fuzzy but I'm pretty sure I did it from fastboot, this happened to me about the time shabby was trying to fastboot boot boot.img and I ended up flashing it instead.
Click to expand...
Click to collapse
I had this same issue when porting TWRP ^^^.
I can't seem to find my posts on it right now, but someone just said do a clean flash. No problems since
how did you do this please!
fallnSaint said:
So... Anyone have any experience getting sticky bit turned off on fastboot? My phone boots to it anytime I try to reboot or do a regular boot up.
Click to expand...
Click to collapse
Okay, this will probably help you...while your device is in Sticky Bit Factory Fastboot, open up a command prompt and connect to your device (given you know how to do so in your folder containing your fastboot app and drivers). Then type "fastboot oem fb_mode_clear" This command will allow your device to boot into system normally. Problem is (I think) when a failed flash occurs sometimes it sets your device in that mode and the above command clears it. Another way to manually place a device in the same state you described is to enter this command using fastboot: fastboot oem fb_mode_set. I believe that is how RSD Lite automatically reboots your device into factory fastboot mode after flashing partitions (.mbn) on your system so that it may resume flashing the boot, recovery, and system images, etc. Let me know if it helps.....
Sent from my XT897 using xda premium
RECOVERY IMAGE for SU760 ICS leak build for P920
This is all based on wkpark's thread here but focused only for p920.
ClockWorkMod(6.0.1.5) and TWRP(2.2.2.1) images as flashable images, to be used after you installed WKPark's alternate bootloader using his root signature. then we get full recovery back working on top of ICS.
Instructions on how to install the recovery.
Click to expand...
Click to collapse
Download wkparks fastboot loader from here
and extract contents into a temp folder.
1a. follow his instructions on how to install device drivers then goto step 2 or
1b.
remove battery, attach usbcable between pc and mobile.
Install the omap4430 driver, when you see a device appearing in "devicemanager" named omap4430,
rightclick on it and install driver from the 7z download and look in folder usb_drv_windows for the device driver.
remember to be fast to rightclick as it wil disappear and re-appear often until driver is installed.
1c. pc will find and install driver at next mobile restart (which is some seconds after.
Download the modified x-loader.bin,u-boot.bin,boot.img from this post and extract content into the temp folder from step1 and put files into the files directory found there.
extract attached p920-2-twrp.zip to the files folder you find in your files directory in the temp folder
extract attached p920-3-cwm.zip to the files folder you find in your files directory in the temp folder
remove battery and disconnect usb cable from mobile.
enter the temp you extracted to at step1, and run start_fastboot and select "2" in the menu shown in the commandline console.
attach usb cable
wait for the "start_fastboot to show alot of details and show booting 2ndboot.
attach battery when the 2ndboot information shows
fastboot v0.5 should be shown with a grey LG logo on your mobile now. , if not, go back and follow steps again.
at this stage, it can happen that "fastboot" driver for "LG Cosmo" device is installing but cannot find a driver, so you need to update driver through device manager, and point to the drivers, where the omap4430 driver was located too and update it.
Now its time to flash to new files run the 3 commands (one by one, do not try to copy/paste all 3 lines) shown just below as shown.
execute: fastboot flash x-loader files\x-loader.bin
execute: fastboot flash u-boot files\u-boot.bin
execute: fastboot flash boot files\boot.img
Lastly time to flash your recovery,
execute: fastboot flash recovery files\cwm.img
or
execute: fastboot flash recovery files\twrp.img
you cannot flash both images, as its not possible to have both recoveries installed.
11-nov-2012 - BOOTING INTO RECOVERY
Click to expand...
Click to collapse
You can always boot into recovery by holding 3D-BUTTON + VOL-UP down while pressing power-button to turn on mobile (without any cables attached to pc or power).
NOTES:
Click to expand...
Click to collapse
- If you do happen to get a bootloop it has been mentioned now, that it can happen if you copy/paster fastboot commands into the commandline shell.
these steps do NOT change anything of your system or data. it is only the bootloaders and boot.img/recovery.img which will change for the ICS build.
- both recoveries got USB mount storage issues, you will have to transfer files to sdcard or internal memory through windows.
- IMPORTANT: do not try and restore boot.img partition (before this install) from your ICS backups, it will cause the mobile not to boot.
and you will have to do the fastboot steps flashing this boot.img again. (it is caused by the signature is no longer a match)
THANKS TO:
Click to expand...
Click to collapse
wkpark - for his incredible work on getting us a custom uboot (still signed but a big help) - we await the unsigned boot
milaq - for the initial work on recoveries for our devices and cwm/twrp is used as base in these 2 images attached.
xbsall - the original release of ICS for p920/su760 edition.
A FEW STATEMENTS - CONFIRMING IT WORKS:
Click to expand...
Click to collapse
GlossGhost said:
I just installed it and it works as it should.
Click to expand...
Click to collapse
lemach said:
I have installed it on w7 64 bits and no problems. also i have installed rom manager and i can restart into recovery through rom manager o through app like quickboot.
Click to expand...
Click to collapse
Here is an alternative:
- download p920-1.zip and unpack to a temp directory.
- download usb_drv_windows.zip and install the driver. This is done when you see "omap4430" appear for a few seconds in device manager, when you attach phone to pc using usb without battery inserted.
- when driver is installed, install one of the recoveries attached to post #1 and unpack to the temp directory too, and finally run "runme.bat" from the temp directory you unpacked. and follow guideline here.
- when you see the commandline information "wait 5 seconds", you re-insert the battery.
- When "fastboot v0.5" shows in the optimus 3D display, you might need to install the fastboot driver(device: LG Cosmo) as well also located in the same zip above where OMAP4430 is found.
- If you do not get the "fastboot v0.5" in the phone display, something went wrong. and you might need to double check that your device manager in windows also shows the "OMAP4430 FastBoot USB device"
Never mind, wainting for a fix. Thanks
sorry guys, my guide works fine and so does the TWRP image and getting into it. But problem is, it seems original recovery does a trick to reset the flag "booting into recovery". So problem now is that it keeps booting into recovery and it cannot boot normally if you get TWRP started once.
I flashed back the original recovery for now and it works fine, when i sign that image with the new signature as well. but not worth much
booting original recovery once and the flag is reset and normal boot is possible.
Ill dig into this and report back and upload a working image, when i figured out the workaround this sad behaviour.
First, thanks for the tutorial and for your work. I wanted to know if this tutorial could be installed boot.img compiled by myself.
Google Translator
Enviado desde TheDarkRoom
adri_360 said:
First, thanks for the tutorial and for your work. I wanted to know if this tutorial could be installed boot.img compiled by myself.
Click to expand...
Click to collapse
yes, we can make custom boot.img as well with the solution he made. scripts and solution is posted in same thread mentioned in step1. i used it to create the recovery.img, but same goes for boot.img.
I hope u can find the solution for this. For some people like me, after we flash the bin, fls, root the device and use twrp. It just wont boot to recovery. So i hope this would work. But thanks again to xbsall for bringing ics to our device. At least now im on ics. Is there anyway i can use original recovery? So u can make a backup and restore if i need to reflash the ics bin again?
Thanks
Sent from my GT-P7500 using xda app-developers app
and it is working!!!!!
Finally got the continous reboot to recovery fixed!!!!
The images are bootable and do only reboot once into the recovery now.
the fix was to use some of the original binaries in the recovery so that mounts and binaries were started once.
So its all ok now.
I have also compiled a new CWM v6.0.1.5 from Recovery Builder clockworkmod, so its using latest release here, but it is not tested yet for full functionality.
This is nice. Thanks.
Sent from my LG-P920 using xda app-developers app
Thank you very much!! now it is late for me, but tomorrow i will follow your guide.
HELL YEAH! haha
HUGE THANKS, MAN!!! :victory: I was just about to flash the whole ROM again, just to make the TWRP work again :crying:
Im goin to start downloading and following the guide in a few min's.
I'll report as soon as im done with it :good:
-TMP
---------- Post added at 11:37 PM ---------- Previous post was at 10:50 PM ----------
ok.. im stuck @ 11.
"waiting for device"
it just wont start flashing. so i went to device manager and theres this new "connection" called LG Cosmo
and it says that the drivers for LG Cosmo are not installed.. what to do?
TMProduct1onZ said:
ok.. im stuck @ 11.
"waiting for device"
Click to expand...
Click to collapse
im stuck on highways, but where, might sometime be a good question if you want to avoid it
you cannot get much help unless you give more, so that kinda ends here.
but it might just be that when the OMAP4430 driver is installed and it loads fastboot v0.5 menu, it could be that the "fastboot" driver also needs to be updated.
check your device manager and find any new android device, and refer to the drivers you got with the step1 package or from my post#2 (i believe it could be your LG Cosmo device)
hmm
Dexter_nlb said:
im stuck on highways, but where, might sometime be a good question if you want to avoid it
you cannot get much help unless you give more, so that kinda ends here.
but it might just be that when the OMAP4430 driver is installed and it loads fastboot v0.5 menu, it could be that the "fastboot" driver also needs to be updated.
check your device manager and find any new android device, and refer to the drivers you got with the step1 package or from my post#2 (i believe it could be your LG Cosmo device)
Click to expand...
Click to collapse
lol ive told you where exactly i stuck :/
ok.. im stuck @ 11.
"waiting for device"
it just wont start flashing. so i went to device manager and theres this new "connection" called LG Cosmo
and it says that the drivers for LG Cosmo are not installed.. what to do?
Click to expand...
Click to collapse
So...
ive installed the LG COSMO drivers and it flashed.
and here's what happend:
-rom manager installed, reboot recovery
-bootloop
-had to flash XBSA404 again :/
-tryed again, same (bootloop)
-gived up
so at the end i had to do exactly that what ive tryed to avoid lol
but one good thing happend tho': Dualclock is gone :good:
now ive installed p940 recovery/TWRP again and it works...
Dont know if its only me
TMProduct1onZ said:
Dont know if its only me
Click to expand...
Click to collapse
you are not alone, its all those that do not understand the installation and wkpark's guide on using his tool. it is not that simple as just running an app. if drivers fail to install or you install the wrong driver, you never get fastboot opened, and if you never see fastboot menu on the phone when the tool starts and you insert battery as his guide says many things goes wrong.
but the instructions cannot be much more simple as they are, its 2 drivers its some steps in a command line to execute and thats pretty much it.
I will try it asap. I could go into fastboot mode last time so finger crossed. For those u have some problem going to fasboot mode try search the how to recover ur device to gb from xbsall. It works for me
Sent from my GT-P7500 using xda app-developers app
Dexter_nlb said:
you are not alone, its all those that do not understand the installation and wkpark's guide on using his tool. it is not that simple as just running an app. if drivers fail to install or you install the wrong driver, you never get fastboot opened, and if you never see fastboot menu on the phone when the tool starts and you insert battery as his guide says many things goes wrong.
but the instructions cannot be much more simple as they are, its 2 drivers its some steps in a command line to execute and thats pretty much it.
Click to expand...
Click to collapse
Hmm idk... maybe i really did something wrong but im sure it was all ok i did see the fastboot menu and i executed everything.
However ill do a backup and then try again later today
Sent from my P920 using ICS 4.0.4 by XBSA
Now its time to flash to new files run the 3 commands shown just below as shown.
fastboot flash x-loader files\x-loader.bin
fastboot flash u-boot files\u-boot.bin
fastboot flash boot files\boot.img
I could start fastboot with the grey logo and fastboot v0.5 on the top left of my device
when i type fastboot flash x-loader files\x-loader.bin
it says waiting for device
after i waited for 2-3 minutes the device just boot normally.
what did i do wrong?
thanks
edit:
i flashed all the command sucessfully
install rom manager
reboot into recovery and it boot loop
it only shows twrp logo and then reboot to lg logo
what should i do?
HOW TO INSTALL RECOVERY IMAGE WITH SUCCESS
I just installed it and it works as it should.
Here's how to do it.
1. Boot into fastboot
2. After installing drivers for OMAP and LG Cosmo, start the shell.
3. Execute lines one by one:
fastboot flash x-loader files\x-loader.bin
then
fastboot flash u-boot files\u-boot.bin
and
fastboot flash boot files\boot.img
EXECUTING THEM ALL WILL LEAD IN A BOOTLOOP, DONT WORRY ITS FINE
4. Boot into fastboot and flash them again.
fastboot flash x-loader files\x-loader.bin
then
fastboot flash u-boot files\u-boot.bin
and
fastboot flash boot files\boot.img
5. Flash recovery image.
fastboot flash recovery files\cwm.img
or
fastboot flash recovery files\twrp.img
After boot, install ROM Manager and reboot into recovery.
If you still have problems, go back and do everything right.
GlossGhost said:
HOW TO INSTALL RECOVERY IMAGE WITH SUCCESS
I just installed it and it works as it should.
Here's how to do it.
Click to expand...
Click to collapse
thanks, hope your assistance above will help those still failing, because when it works, its actually rather nice to have working.
i will also try to improve the documentation executing the lines now.
awi05 said:
what did i do wrong?
Click to expand...
Click to collapse
try and flash all the "fastboot" files as written once more, and maybe for testing purposes, try the cwm.img instead of twrp image. you can also switch to twrp when you see you got it working. i do not flash all files switching, only cwm or twrp images needs to be flashed.
When the bootloader is updated, we can actually flash boot and recovery images from a shell prompt now. as long as the image is with signature. but fastboot will just be a brick recovery step when you first got it working.
Hi everyone,
I was hoping someone might have some advise for me to try. I did the following and now I can't seem to boot the ROM I installed and/or load the partitions to wipe them. TWRP is asking for a password (which I just cancel) and then it can't mount the partitions. Here is what I did.
unpacked the tablet and started it up. Put my Wi-Fi and google account on it and updated the firmware.
I then downloaded the ASUS unlock application and unlocked my bootloader. It shows as unlocked now when starting up.
I installed TWRP (Latest version) via fastboot.
I created a backup with TWRP.
I installed a custom ROM.
Restarted
System not booting. I attempted to recover from backup and/or wipe the partitions and it won't mount them. also TWRP asks for a password and I just cancel out of it. I believe you know the symptoms.
I then read that maybe an older version of TWRP would work. I tried 2.3.3.0 I believe and it had the exact same affect. I installed it via fastboot as well.
Any advise would be appreciated. Thank you. The custom ROM I installed has a filename of cm-4.4.2-20131226-cmb4. I think it's a CM mod file. Thanks so much for your time. Someone is helping me on the side via PM, if I get anywhere with that, I'll post the resolution here.
-Tony
qzmicro said:
The custom ROM I installed has a filename of cm-4.4.2-20131226-cmb4. I think it's a CM mod file.
Click to expand...
Click to collapse
The file cm-4.4.2-20131226-cmb4 is for Verizon HTC One only and not for the ASUS TF700T.
You must download the CM from this site: Link
I run my TF700T with CM11 (nightly build) and with TWRP 2.6.3.2.
Regards
Matthias
Any suggestions?
manhart said:
The file cm-4.4.2-20131226-cmb4 is for Verizon HTC One only and not for the ASUS TF700T.
You must download the CM from this site: Link
I run my TF700T with CM11 (nightly build) and with TWRP 2.6.3.2.
Regards
Matthias
Click to expand...
Click to collapse
Thanks for the reply but the ROM I used is indeed for the TF700T mode. The exact filename is cm-4.4.2-20131226-cmb4.4-tf700t-rc3.zip. As you can see my device model is in the filename. I also only downloaded ROMS that are form this forum (TF700.) Any suggestions?
-Tony
qzmicro said:
Thanks for the reply but the ROM I used is indeed for the TF700T mode. The exact filename is cm-4.4.2-20131226-cmb4.4-tf700t-rc3.zip. As you can see my device model is in the filename. I also only downloaded ROMS that are form this forum (TF700.) Any suggestions?
-Tony
Click to expand...
Click to collapse
That is a rom based on CM11 kitkat. Did you read the requirements (which the cmb creators unfortunately just touch upon in their op) before you flashed it?
The CM11 OP states that you have to be on 10.16.1.14.x bootloader and CWM 6.0.4.4 as a recovery.
It also clearly states that TWRP has problems with KitKat. Supposedly the latest TWRP version works, but to my knowledge that is not confirmed. Don't know what TWRP version you initially flashed, but then you flashed one that's totally outdated and possibly not even compatible with your bootloader.....
I hope you still have access to fastboot.... download CWM 6.0.4.4. and flash it. Then try to flash the rom again.
But check your bootloader version first!
Read this: http://forum.xda-developers.com/showthread.php?t=1957660
Now I can't seem to erase certain partitions or write to system...
Hi everyone,
So, I tried to erase all partitions using fastboot and then install the asus firmware blob back on my system to see if I can get it back to where it was. At this point I can't seem to write to the system partition. I get a failed error on fastboot and a failed command error on my tablet. Any suggestions? Is there any way to install a bootloader with fastboot? I suspect it's the bootloader as it is still ASUS's stock bootloader. I would like to change it to something that may be able to write and wipe the partitions properly using CWM or something similar. Please advise, I'm running out of options here. I'd hate to think I bricked my first device ever... thanks so much for your time. Cheers.
-Tony
qzmicro said:
Hi everyone,
So, I tried to erase all partitions using fastboot and then install the asus firmware blob back on my system to see if I can get it back to where it was. At this point I can't seem to write to the system partition. I get a failed error on fastboot and a failed command error on my tablet. Any suggestions? Is there any way to install a bootloader with fastboot? I suspect it's the bootloader as it is still ASUS's stock bootloader. I would like to change it to something that may be able to write and wipe the partitions properly using CWM or something similar. Please advise, I'm running out of options here. I'd hate to think I bricked my first device ever... thanks so much for your time. Cheers.
-Tony
Click to expand...
Click to collapse
You do have fastboot access? If you enter
Code:
fastboot devices
in the cmd prompt, does it return the serial number of your device.
If not, you may have a driver problem on your PC.
The only method I know of to get a bootloader via fastboot is to flash the system blob, but you seem to have tried that already. The question is: How?
Please post the commands you used and the output you get back.
You also may want to look at buster99's method:
http://forum.xda-developers.com/showthread.php?t=2179759&page=2
It's been a single ? since I started using fastboot.
berndblb said:
You do have fastboot access? If you enter
Code:
fastboot devices
in the cmd prompt, does it return the serial number of your device.
If not, you may have a driver problem on your PC.
The only method I know of to get a bootloader via fastboot is to flash the system blob, but you seem to have tried that already. The question is: How?
Please post the commands you used and the output you get back.
You also may want to look at buster99's method:
http://forum.xda-developers.com/showthread.php?t=2179759&page=2
Click to expand...
Click to collapse
I've installed fastboot on two separate systems (both windows 8.1 64-bit) and both have drivers installed (device manager shows it installed fine.) Since I started using fastboot it simply shows a ? instead of my device's serial number. Could this be the issue from the start? I was able to install TWRP with it, so I assumed it worked. * Sigh * I should know better. (I kept moving forward once I saw TWRP installed) Would it surprise you to know I'm a network engineer?
I put up a windows 7 system at this point to see if I have a better time with fastboot and the drivers simply aren't recognized, even when I install the asus software that has the drivers (Asus pad pc suite.)
How can I get just the raw drivers for my system to use with fastboot? Either for Windows 8 or 7. Any help would be appreciated, thank you for your time.
-Q
qzmicro said:
I've installed fastboot on two separate systems (both windows 8.1 64-bit) and both have drivers installed (device manager shows it installed fine.) Since I started using fastboot it simply shows a ? instead of my device's serial number. Could this be the issue from the start? I was able to install TWRP with it, so I assumed it worked. * Sigh * I should know better. (I kept moving forward once I saw TWRP installed) Would it surprise you to know I'm a network engineer?
I put up a windows 7 system at this point to see if I have a better time with fastboot and the drivers simply aren't recognized, even when I install the asus software that has the drivers (Asus pad pc suite.)
How can I get just the raw drivers for my system to use with fastboot? Either for Windows 8 or 7. Any help would be appreciated, thank you for your time.
-Q
Click to expand...
Click to collapse
Ain't computers great? If you are a network engineer you should be used to this! LOL!
On Win 8 there's some nasty stuff where you have to turn off "windows driver verification" or some such in system settings - just google "Windows 8 fastboot" and you should find the necessary steps.
The attached drivers work fine for me with Win 7 (forgot which one's I installed). Try the Universal Naked Drivers first and uninstall the ones you have now prior to installing these.
But one thing is for sure: ? is not an acceptable return for "fastboot devices"
Edit: XDA won't let me upload the Google Universal Naked Drivers, so download them from here:
http://forum.xda-developers.com/showthread.php?t=2263822
I would try these first, then the adb recovery driver I attached as a zip
Drivers are installed now and stilll ? for fastboot devices.
berndblb said:
Ain't computers great? If you are a network engineer you should be used to this! LOL!
On Win 8 there's some nasty stuff where you have to turn off "windows driver verification" or some such in system settings - just google "Windows 8 fastboot" and you should find the necessary steps.
The attached drivers work fine for me with Win 7 (forgot which one's I installed). Try the Universal Naked Drivers first and uninstall the ones you have now prior to installing these.
But one thing is for sure: ? is not an acceptable return for "fastboot devices"
Edit: XDA won't let me upload the Google Universal Naked Drivers, so download them from here:
http://forum.xda-developers.com/showthread.php?t=2263822
I would try these first, then the adb recovery driver I attached as a zip
Click to expand...
Click to collapse
Hi, so I installed the naked drivers and they seemed to work. Once that was done, I used fastboot devices and got a questionmark again. Please keep in mind that since the tablet was out of the box, I have only seen a ?. I don't believe that this issue is related to the other only because it's been consistently ? the whole time, across 3 workstations. I can now erase the system partition but can't seem to write to it. I guess it would help to resolve the drivers issue but I am not sure how. Naked drivers are installed. commands like erase and reboot tend to work properly. write worked the first time as well but since then I cannot write to certain partitions. Any ideas how I might resolve the ? issue in fastboot devices?
-Tony
qzmicro said:
Hi, so I installed the naked drivers and they seemed to work. Once that was done, I used fastboot devices and got a questionmark again. Please keep in mind that since the tablet was out of the box, I have only seen a ?. I don't believe that this issue is related to the other only because it's been consistently ? the whole time, across 3 workstations. I can now erase the system partition but can't seem to write to it. I guess it would help to resolve the drivers issue but I am not sure how. Naked drivers are installed. commands like erase and reboot tend to work properly. write worked the first time as well but since then I cannot write to certain partitions. Any ideas how I might resolve the ? issue in fastboot devices?
-Tony
Click to expand...
Click to collapse
I have never heard of this issue.....
Please post the fastboot commands you are using.
Liunx Mint 32 bit
You need Linux Mint 32 bit, to have a fighting chance of solving this issue...Let me know if I can help... Thx, the cmb team, and lj50036
I will document what I have done so far, step by step.
berndblb said:
I have never heard of this issue.....
Please post the fastboot commands you are using.
Click to expand...
Click to collapse
I'll post shortly what I have done and how it went down. Specifically the commands used in fastboot as that is the ONLY tool I've used so far besides the ASUS Unlock Tool. Standbye...
-Tony
I'll be installing linux mint 32 on a VM....
lj50036 said:
You need Linux Mint 32 bit, to have a fighting chance of solving this issue...Let me know if I can help... Thx, the cmb team, and lj50036
Click to expand...
Click to collapse
@lj50036:
I would love to try anything... even if it's just for educational purposes.
Can I install Linux Mint on a VM? If so, I'll have this done soon and get back to you. If not, please let me know and I can put up a physical machine with it. Thanks. Cheers.
At this point it seems by biggest problem is that I can't write to the damn system partition... Fastboot is all I have used to modify the tablet but it has never shown my serial number. Is this what we are trying to address with mint? Would you mind giving me some more info while I get this done is possible. Thank you.
-Tony
UPDATE: Here is all the commands I've tried on my Tablet...
Originally I did this:
unpacked the tablet and started it up. Put my Wi-Fi and google account on it and updated the firmware.
I then downloaded the ASUS unlock application and unlocked my bootloader. It shows as unlocked now when starting up.
I installed TWRP (Latest version) via fastboot.
I created a backup with TWRP.
I installed a custom ROM.
Restarted
System not booting. I attempted to recover from backup and/or wipe the partitions and it won't mount them. also TWRP asks for a password and I just cancel out of it. I believe you know the symptoms.
I then read that maybe an older version of TWRP would work. I tried 2.3.3.0 I believe and it had the exact same affect. I installed it via fastboot as well.
Since then I've tried this:
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system blob (blob was in same directory as fastboot and I got it form the latest asus firmware zip file) <-- Failed It sends the data okay but fails to write to the disc. Error on ASUS tablet in red also confirms the command write:system failed and gives a memory address.
fastboot -i 0x0B05 reboot
Please note that some of the erase commands simply hung. I had to restart the tablet to go back into fastboot mode. When I restart it sometimes they erase successfully. Not sure why. I know I couldn't erase userdata at all, and recently tried again and it worked.
I now have a copy of Mint Linux 32-bit ready to go. What should I try?
-Tony
VM Mint
qzmicro said:
@lj50036:
I would love to try anything... even if it's just for educational purposes.
Can I install Linux Mint on a VM? If so, I'll have this done soon and get back to you. If not, please let me know and I can put up a physical machine with it. Thanks. Cheers.
At this point it seems by biggest problem is that I can't write to the damn system partition... Fastboot is all I have used to modify the tablet but it has never shown my serial number. Is this what we are trying to address with mint? Would you mind giving me some more info while I get this done is possible. Thank you.
-Tony
Click to expand...
Click to collapse
I can not say about VM. I have not done that because I have lots of hard drives, so I cant give any feedback about VM and if that will work. I would say to stay away from VM but thats just me... So really what we need is like a 80 gig or bigger hard drive you can just slap mint 32 bit on... If you need any help with this just let me know.. Just to clarify, have enable nvflash?? you can send me a email at [email protected]
lj50036 said:
I can not say about VM. I have not done that because I have lots of hard drives, so I cant give any feedback about VM and if that will work. I would say to stay away from VM but thats just me... So really what we need is like a 80 gig or bigger hard drive you can just slap mint 32 bit on... If you need any help with this just let me know.. Just to clarify, have enable nvflash?? you can send me a email at [email protected]
Click to expand...
Click to collapse
Done. I have mint installed on an x86 system. No VM. I figured why risk it. What can I do from here? Install fastboot and try again from this platform? Do I need to install drivers for my tablet? If so, manufactureres website best ones to use? I'm ready to do this... and praying...
-Tony
P.s. I do not believe I have NVFLASH. I had firmware that didn't alow for it, so I just did the Asus Unlock Tool. Please refer to my previous message about anything/everything I've done so far. Cheers.
qzmicro said:
Done. I have mint installed on an x86 system. No VM. I figured why risk it. What can I do from here? Install fastboot and try again from this platform? Do I need to install drivers for my tablet? If so, manufactureres website best ones to use? I'm ready to do this... and praying...
-Tony
Click to expand...
Click to collapse
Open a terminal window and type fastboot, it will not be installed but it will prompt you how to get it...do the same for adb just type adb and will prompt..... Than boot your tablet into fastboot.... Connect it to your mint pc and type fastboot devices see what it says......
Just to clarify you do have a unlocked bootloader, yes??
EDIT TYPE----- sudo fastboot devices
lj50036 said:
Open a terminal window and type fastboot, it will not be installed but it will prompt you how to get it...do the same for adb just type adb and will prompt..... Than boot your tablet into fastboot.... Connect it to your mint pc and type fastboot devices see what it says......
Just to clarify you do have a unlocked bootloader, yes??
EDIT TYPE----- sudo fastboot devices
Click to expand...
Click to collapse
Roger that. ... and yes, I do have an unlocked boot loader. It's the factory ICS from what I understand. Unlocked with the ASUS Unlocker Tool. it completed successfuly. It states it is unlocked when I boot the device. I'll let you know what happenes in an hour or two. I have to finish some work. Thank you, I'll post shortly.
-Tony
Great
qzmicro said:
Roger that. ... and yes, I do have an unlocked boot loader. It's the factory ICS from what I understand. Unlocked with the ASUS Unlocker Tool. it completed successfuly. It states it is unlocked when I boot the device. I'll let you know what happenes in an hour or two. I have to finish some work. Thank you, I'll post shortly.
-Tony
Click to expand...
Click to collapse
Sounds great!!! No worries on a time.. Just let me know... Thx lj
Linux Mint still shows ?????? as my serial.
lj50036 said:
Sounds great!!! No worries on a time.. Just let me know... Thx lj
Click to expand...
Click to collapse
So, I installed fastboot and ADB and installed all updates on the OS for kicks. Then tried the fastboot devices command and I recieved:
Code:
[email protected] ~ $ fastboot devices
no permissions fastboot
[email protected] ~ $ sudo fastboot devices
[sudo] password for amascolo:
???????????? fastboot
[email protected] ~ $
...? Still no serial number. I've seen this since I took it out of the box. Not sure what that is all about, I have found no one else with this issue. I'm going to try to flsh and I'll let you know what happens.
-Tony
UPDATE: I have tried to re-flash the damn thing and it still fails. Here is what I see...
Code:
[email protected] / $ sudo fastboot -i 0x0B05 flash staging /home/amascolo/Desktop/blob
sending 'staging' (800927 KB)...
OKAY [135.763s]
writing 'staging'...
FAILED (remote: ()
finished. total time: 136.934s
[email protected] / $
Any ideas fellas? Seems I simply am not able to write to the system partition again.
-Tony
* SIGH *
Anyone have any ideas as to why I can't write to my device? Any ideas as to what I may try? Please advise, I'm not looking forward to throwing this thing away. Cheers.
-Tony
Hi everybody!
I get from Google the factory image hammerhead-lmy47d-factory-6c1ad81e.tgz for my nexus 5
In downloaded two times (and verify MD5) on two different computers.
To perform a clean upgrade manually.
I following the instructions below:
- Unzip factory image file and copy all neccesary .img files on platform-tools on windows directory
- Turn off the phone and enter to bootloader mode and running the following instructions:
fastboot flash bootloader bootloader.img
[succesful]
fastboot reboot-bootloader
[succesful]
fastboot flash radio radio.img
[succesful]
fastboot reboot-bootloader
[succesful]
fastboot flash system system.img
target reported max download size of 1073741824 bytes
error: cannot load 'system.img'
is pending
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
On the same Nexus 5 I test and performed the same steps to flash 5.0.1 version (hammerhead-lrx22c-factory-0f9eda1b.tgz) and have no problem, everything works fine
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
[all succesful]
The only way they could make the upgrade to 5.1 was using the OTA file:
e16268c5a3df75a65054ab258d7d615288b7e3b4.signed-hammerhead-ota-LMY47D-from-LRX22C-radio-restricted.zip
Using the following command in ADB mode:
adb sideload e16268c5a3df75a65054ab258d7d615288b7e3b4.signed-hammerhead-ota-LMY47D-from-LRX22C-radio-restricted.zip
I was left with the question of:
Why it could not flash the system.img file?
What does it mean error: cannot load 'system.img' in this case?
And how to fix it?
I need your support guys, thanks in advanced!
This may be daft, but you did have it in the same folder as the radio and bootloader img's as when extracting, the rest are in the next folder along
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
All files are in the same folder.
Ben36 said:
This may be daft, but you did have it in the same folder as the radio and bootloader img's as when extracting, the rest are in the next folder along
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
Click to expand...
Click to collapse
thanks, this helped
Thank you bmita. I had exactly the same problem as you. I followed your steps to revert back to 5.0.1 then used ADB process to upgrade to 5.1
I was totally stuck and thanks to you, I could find a solution.
This doesn't make any sense. I (and of course, many others) was able to flash 5.1 factory images, no problem.
Do you have the latest fastboot.exe?
Sent from my Nexus 9 using XDA Free mobile app
Anything that can go wrong, will go wrong. This time It happened to me. If that error had not occurred, then I would not give the job of writing this thread... :good:
beekay201 said:
This doesn't make any sense. I (and of course, many others) was able to flash 5.1 factory images, no problem.
Click to expand...
Click to collapse
I forget to mention, but before doing an update run the SDK Manager.exe program and perform the upgrade to support the new version of Android. Can you tell me please how I can check the version of fastboot.exe file?
jd1639 said:
Do you have the latest fastboot.exe?
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
bmita said:
I forget to mention, but before doing an update run the SDK Manager.exe program and perform the upgrade to support the new version of Android. Can you tell me please how I can check the version of fastboot.exe file?
Click to expand...
Click to collapse
fastboot version
But Google 15 second adb install xda. That'll put the latest version of fastboot and adb on your pc.
Sent from my Nexus 5 using XDA Free mobile app
Previously try running fastboot version command, but only get the help screen display of fastboot.
adb version display: Android Debug Bridge version 1.0.32
jd1639 said:
fastboot version
But Google 15 second adb install xda. That'll put the latest version of fastboot and adb on your pc.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
bmita said:
Previously try running fastboot version command, but only get the help screen display of fastboot.
adb version display: Android Debug Bridge version 1.0.32
Click to expand...
Click to collapse
Looks like you have the latest.
Sent from my Nexus 9 using XDA Free mobile app
Yep.
On SDK Platforms Release Notes site
Android 5.1
Dependencies:
Android SDK Platform-tools r22 or higher is required. I have Rev. 22
Android SDK Tools 23.0.5 or higher is required. I have Rev. 24.1.2
jd1639 said:
Looks like you have the latest.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Hello,
Did you test on another computer?
I was in exactly the same situation as you and I tested on another computer with exactly the same cable and the fastboot flash system system.img worked without any problem.
Have look at the comments from Sp0KI in this thread : http://forum.xda-developers.com/goo...e-update-rooted-device-to-5-1-lmy47d-t3050789
you will see he also had the problem and also solved it by switching computer.
I still don't understand why it is so (memory or driver problem?) but it solved my problem.
Thanks for the info, I did the following:
I use the new hammerhead-lmy47i-factory-df127988.tgz on another machine with minimal_adb_fastboot_v1.2_setup.exe (adb version 1.0.32) and clean upgrade works fine.
I do not understand what could have happened...
Thises said:
Hello,
Did you test on another computer?
I was in exactly the same situation as you and I tested on another computer with exactly the same cable and the fastboot flash system system.img worked without any problem.
Have look at the comments from Sp0KI in this thread : http://forum.xda-developers.com/goo...e-update-rooted-device-to-5-1-lmy47d-t3050789
you will see he also had the problem and also solved it by switching computer.
I still don't understand why it is so (memory or driver problem?) but it solved my problem.
Click to expand...
Click to collapse
after googling for ages i think i finally have found the solution:
http://highonandroid.com/android-sm...re-error-could-not-allocate-1778070480-bytes/
Ntress said:
after googling for ages i think i finally have found the solution:
http://highonandroid.com/android-sm...re-error-could-not-allocate-1778070480-bytes/
Click to expand...
Click to collapse
Did this work for you? Usually when you get that error it's because you don't have the latest fastboot.exe. I'd be interested if this works. Thanks
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Did this work for you? Usually when you get that error it's because you don't have the latest fastboot.exe. I'd be interested if this works. Thanks
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, this method is worked for me.
The method you stated is wrong, i was using Wugfresh toolkit and then also downloaded the latest fastboot files and nothing solved it until i saw that link.
Ntress said:
Yes, this method is worked for me.
The method you stated is wrong, i was using Wugfresh toolkit and then also downloaded the latest fastboot files and nothing solved it until i saw that link.
Click to expand...
Click to collapse
Hey !
I got the same problem with Nexus 5 and the 5.1.1 factory image ... tried different computers, cables ... tried the mfastboot and got this:
target max-download-size: 1024MB
load_file: could not allocate 1046266608 bytes
error: cannot load 'system.img': Not enough space
Could someone help me ?
neuraman said:
Hey !
I got the same problem with Nexus 5 and the 5.1.1 factory image ... tried different computers, cables ... tried the mfastboot and got this:
target max-download-size: 1024MB
load_file: could not allocate 1046266608 bytes
error: cannot load 'system.img': Not enough space
Could someone help me ?
Click to expand...
Click to collapse
are you trying with a USB 3.0 port, my laptop has all USB 3.0 ports, and i get this error no matter what, so i flash on my friends laptop with USB 2.0 port and it works fine. try with USB 2.0 port.
madarchod said:
are you trying with a USB 3.0 port, my laptop has all USB 3.0 ports, and i get this error no matter what, so i flash on my friends laptop with USB 2.0 port and it works fine. try with USB 2.0 port.
Click to expand...
Click to collapse
At the beginning I was trying a USB 3.0 port ... but I tried with a 2.0 just after on the same computer and with my old laptop with the same results.
I can't flash my current system image again ... it's not the new system.img ... I guess ...
---------- Post added at 03:17 PM ---------- Previous post was at 02:25 PM ----------
neuraman said:
At the beginning I was trying a USB 3.0 port ... but I tried with a 2.0 just after on the same computer and with my old laptop with the same results.
I can't flash my current system image again ... it's not the new system.img ... I guess ...
Click to expand...
Click to collapse
Ok ... think I solved with this command:
Code:
fastboot flash -S 512M system system.img
source: Original post
It seems it divides the image in two and writes them in two phases ... if it works I would guess is some kind of fastboot or Windows limit ... even though I tried the "limitless" mfastboot with the same results.
EDIT: ok it worked ! 5.1.1 up and running !
So i recently decided to update my Oneplus 7 Pro from the public stable release to the OxygenOS 11 Open Beta 3 on a whim. Tried to go back to the old stable release by flashing fastboot roms from Tool All In One and it somehow broke everything, even though I did it multiple times before.
Phone can't boot into anything -- even with stock roms installed. Simply shows the bootloader is unlocked screen and nothing after. I can get into recovery and edl and fastboot, but nothing else. I think I flashed an older version from TAIO's fastboot rom flasher, making it impossible (!) for my computer to interact with my phone.
MSM Tool also doesn't work. Param preload, even though I have the QC and OP drivers installed.
Anything I can do?
You could try, moving the 10 stable on to a usb drive you could plug into the phone, then fastboot boot twrp.img via fastboot . Once in, format and install A10 from usb drive, done it many times
@soka said:
You could try, moving the 10 stable on to a usb drive you could plug into the phone, then fastboot boot twrp.img via fastboot . Once in, format and install A10 from usb drive, done it many times
Click to expand...
Click to collapse
That's just it -- I can't fastboot anything. Be it roms or TWRP.
Besides, my phone doesn't really interact with my computer so no adb. Only edl (i think).
VictimOfMagic said:
That's just it -- I can't fastboot anything. Be it roms or TWRP.
Besides, my phone doesn't really interact with my computer so no adb. Only edl (i think).
Thanks for replying
Click to expand...
Click to collapse
Sorry about that bud, sounds like your drivers are not installed properly. Maybe start there. I used the tool in one app to install the needed drivers. Worth a shot.
Try this post
Fastboot waiting for any device
Hello everybody, I was trying to update my Magisk and that process failed. I thought nothing of it put it off. Tried to restart my phone a few days later and now it's stuck in a fastboot loop. Cannot even go into recovery. So I'm like okay...
forum.xda-developers.com
@soka said:
Sorry about that bud, sounds like your drivers are not installed properly. Maybe start there. I used the tool in one app to install the needed drivers. Worth a shot.
Try this post
Fastboot waiting for any device
Hello everybody, I was trying to update my Magisk and that process failed. I thought nothing of it put it off. Tried to restart my phone a few days later and now it's stuck in a fastboot loop. Cannot even go into recovery. So I'm like okay...
forum.xda-developers.com
Click to expand...
Click to collapse
Well, TIAO only installs google's WinUSB. I already had that installed. I just don't know why I keep getting stuck on the param preload, even with all the drivers that could be needed being installed. Maybe it has something to do with the OOS version? I have GM1915, fastboot flashed to 10.0.4 Global.
Also, I think i messed up my msm tool since now it always says connected lmao
VictimOfMagic said:
Well, TIAO only installs google's WinUSB. I already had that installed. I just don't know why I keep getting stuck on the param preload, even with all the drivers that could be needed being installed. Maybe it has something to do with the OOS version? I have GM1915, fastboot flashed to 10.0.4 Global.
Also, I think i messed up my msm tool since now it always says connected lmao
Thanks for replying.
Click to expand...
Click to collapse
I had the same problem with drivers. (I tried the ones that come with the device (in an .iso image I think?) and then I tried with the patched L2 drivers.)
What worked for me: installing the ALL IN ONE tool (on windows) then runing it as administrator*, then installing the drivers from within the All In One Tool program.
md5hasher said:
I had the same problem with drivers. (I tried the ones that come with the device (in an .iso image I think?) and then I tried with the patched L2 drivers.)
What worked for me: installing the ALL IN ONE tool (on windows) then runing it as administrator*, then installing the drivers from within the All In One Tool program.
Click to expand...
Click to collapse
Running TAIO as an admin? That still only downloads WinUSB.
Can you expand on what you mean?
Under windows 10 open CMD as admin and enter bcdedit /set testsigning on
now reboot. This resolved for me the driver issue and phone was then correctly seen by msm unbrick tool