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.
Related
please dont shout, just take pitty on me.
I have been getting into the world of rooting and have used the HTC Bootloader unlock, and have installed clockwork. i then had a few issues but managed to get some roms working but Im still not fully understanding exactly what im doing.
but i can flash by:
1. Power on'ing and vol down,
2. fastboot - bootloader - loading PG58IMG
3. recovery -wipe data/factory reset - yes
4. install zip from sdcard - chose zip from sdcard - Sensation_3.32.401.5_deodexed - Yes
5. wait for: install from sdcard complete
7. go back - rebootsystem now
Ive tried a few roms, 2 didnt work but this is the 3rd (Sensation_3.32.401.5_deodexed) that has loaded up.
My issue is I dont get how to get my wireless to work. If someone could give simple instructions Id be more than helpfl as all guides i read are too full of jargon. . . . .im not afraid to hit your thanks buttons . . .
Thanks
Tim
PS
my cid is VADAP001
my MID is PG5813000
taffytim said:
please dont shout, just take pitty on me.
I have been getting intot he world of routing and have used the HTC Bootloader unlock, and have installed clockwork. i then had a few issues but managed to get some roms working but Im still not flly understanding exactly what im doing.
but i can flashing by
1. Power on'ing and vol down,
2. fastboot - bootloader - loading PG58IMG
3. recovery -wipe data/factory reset - yes
4. install zip from sdcard - chose zip from sdcard - Sensation_3.32.401.5_deodexed - Yes
5. wait for: install from sdcard complete
7. go back - rebootsystem now
Ive tried a few roms, 2 didnt work but this is the 3rd (Sensation_3.32.401.5_deodexed) that has loaded up.
My issue is I dont get how to get my wireless to work. If someone could give simple instructions Id be more than helpfl as all guides i read are too full of jargon. . . . .im not afraid to hit your thanks buttons . . .
Thanks
Tim
Click to expand...
Click to collapse
Hi,
Are you talking about wifi?
Have you got a router?
When you use HTC Dev to unlocj your bootloader it does unlock the Recovery, System, and Boot partitions to allow your device to write to those partitions and not just read rose partitions. But Terri is a catch, if you want to flash a custom recovery you have to use ABD fastoot commands to flash it. When you flash as ROM in a .zip file via Recovery, it only flashes the System partition. You then have to open the dot zip file and extract the boot.img and then use ADB fastboot commands to flash the boot.img to your boot partition. If you do not you will still have the boot.img of the ROM you was using before you flashed te New ROM.
Now let me explain the boot.img a little so you know why it is so important. The boot.img does just watt te name implies, it is what boots the Android ROM on your device. Now let me explain this a little further, the Android OS runs on top of eat is called a Lenox kernel. This means that your bootloader boots the Lenox kernel and the hardware of the device. The Lenox kernel then boots the Android OS. The kernel is also te connection between the hardware and the Android OS. So you see if the kernel is not compatible with the system that is on te system partition you will have troubles like WiFi not working or other I hardware reliant functions. So when you flash a new ROM and you are HTC Dev unlocked you will have to flash the boot.img for te ROM are you will more than likely have troubles.
Malybru, i do have a router but my wifi wont turn on so i cant connect to it.
T-Macgnolia said:
When you use HTC Dev to unlocj your bootloader it does unlock the Recovery, System, and Boot partitions to allow your device to write to those partitions and not just read rose partitions. But Terri is a catch, if you want to flash a custom recovery you have to use ABD fastoot commands to flash it. When you flash as ROM in a .zip file via Recovery, it only flashes the System partition. You then have to open the dot zip file and extract the boot.img and then use ADB fastboot commands to flash the boot.img to your boot partition. If you do not you will still have the boot.img of the ROM you was using before you flashed te New ROM.
Now let me explain the boot.img a little so you know why it is so important. The boot.img does just watt te name implies, it is what boots the Android ROM on your device. Now let me explain this a little further, the Android OS runs on top of eat is called a Lenox kernel. This means that your bootloader boots the Lenox kernel and the hardware of the device. The Lenox kernel then boots the Android OS. The kernel is also te connection between the hardware and the Android OS. So you see if the kernel is not compatible with the system that is on te system partition you will have troubles like WiFi not working or other I hardware reliant functions. So when you flash a new ROM and you are HTC Dev unlocked you will have to flash the boot.img for te ROM are you will more than likely have troubles.
Click to expand...
Click to collapse
That is very informative thanks T-Macgnolia. I understand the theorybut i cant work out the process?
How do i get to flash the boot image?
If i go into my rom folder on my pc then try to open the boot file i just get a Windows Disc Image Burner message box asking me to burn to disc.
I used to burn images using virtal drives when making dvds. Will i need to do the same again here with a virtual drive?
Can you break the process down for me?
taffytim said:
That is very informative thanks T-Macgnolia. I understand the theorybut i cant work out the process?
How do i get to flash the boot image?
If i go into my rom folder on my pc then try to open the boot file i just get a Windows Disc Image Burner message box asking me to burn to disc.
I used to burn images using virtal drives when making dvds. Will i need to do the same again here with a virtual drive?
Can you break the process down for me?
Click to expand...
Click to collapse
First you have to download and install the Android SDK. Here is a video by Elite Recognized Developer Adam Outler that shows you how to install the Android SDK. After you have the SDK installed and all the packages are downloaded and installed. Take the boot.img and copy it to the same folder in ADB that has fastboot in it. Now while you are in the folder with fastboot in it hold down the shift key and right click anywhere on the screen and select "open command promt here". This will open a command promt with you already on the right directory. Now boot your Sensation into Hboot by holding the volume down button down while booting your Sensation. when in Hboot select fastboot and connect your Sensation to your computer with your USB cable. Now type the following into the command promt.
Code:
fastboot flash boot boot.img
That is all it is to it. Also the boot.img is a iso file that is why you get that message when you try to open it. You have to use a Android kitchen or another program that can decompile the file if you want to open it and look around.
T-Macgnolia said:
First you have to download and install the Android SDK. Here is a video by Elite Recognized Developer Adam Outler that shows you how to install the Android SDK. After you have the SDK installed and all the packages are downloaded and installed. Take the boot.img and copy it to the same folder in ADB that has fastboot in it. Now while you are in the folder with fastboot in it hold down the shift key and right click anywhere on the screen and select "open command promt here". This will open a command promt with you already on the right directory. Now boot your Sensation into Hboot by holding the volume down button down while booting your Sensation. when in Hboot select fastboot and connect your Sensation to your computer with your USB cable. Now type the following into the command promt.
Code:
fastboot flash boot boot.img
That is all it is to it. Also the boot.img is a iso file that is why you get that message when you try to open it. You have to use a Android kitchen or another program that can decompile the file if you want to open it and look around.
Click to expand...
Click to collapse
You sir deserve a big pint of something great. Point by point I:
1. I already had sdk installed so didnt need to install this.
2. I cleared the phone back to factory with Recovery (Power on with holding -Vol, RECOVERY, Wipe data/Factory Reset, Power Off)
3. I went into HBOOT (by powering on holding down -vol)
4. Opened FASTBOOT and connected phone to computer via USB
5. Opened up command prompt on PC (start menu, typed cmd in the search box)
6. I then Typed the following:
7. "cd c:\Android" (to get me into the folder where my files are)
8. "fastboot flash boot boot.img"
9. this then loaded my boot file and bosh, Im done.
I then restarted the phone and bobs your mothers brother Im using wiresless again. Its such an easy process but on the first go it seems like rocket science.
You cant appreciate how greatful i am for your help. Thank you more than a lot.
If i chose a different ROM at what point is it best to do this stage? Are you able to do this to the boot image before you use recovery to 'insatll zip from sd card'? Or do you have to install then come back to it like i did?
For every custom rom you install you need to follow the same procedure.
1. First flash/install the rom via recovery
2. Get the boot.img and flash it via fastboot (some rom's have more than one kernel then choose the best you want)
As long as you stay in HTC unlocked bootloader the above steps are necessary to flash the rom completely to prevent bootloops and wifi errors
sent from my blazing fast pyramid through sonic waves
ta gane shp, this is a good place with good people
Thanks this post helped me a lot!
I got Android Revolution fully working, but I'm trying to flash the newest OC Kernel of SebastianFM over it. But his zip doesn't have a "boot.img", it does however contain the following: mkbootimg, mkbootimg.sh and unpackbootimg. Is it any of those I need to flash, if not, which "boot.img" do I flash then?
Asskicker2 said:
Thanks this post helped me a lot!
I got Android Revolution fully working, but I'm trying to flash the newest OC Kernel of SebastianFM over it. But his zip doesn't have a "boot.img", it does however contain the following: mkbootimg, mkbootimg.sh and unpackbootimg. Is it any of those I need to flash, if not, which "boot.img" do I flash then?
Click to expand...
Click to collapse
Hi,
I believe the boot.img refers to the ROM you are flashing.
This is a kernel.
So,make a nandroid backup,
wipe cache and dalvik,
and flash the kernel from the root of the sd card,choosing install zip from sd card in recovery.
malybru said:
Hi,
I believe the boot.img refers to the ROM you are flashing.
This is a kernel.
So,make a nandroid backup,
wipe cache and dalvik,
and flash the kernel from the root of the sd card,choosing install zip from sd card in recovery.
Click to expand...
Click to collapse
Yeah, that isn't working.
Wifi ain't working now.
Asskicker2 said:
Yeah, that isn't working.
Wifi ain't working now.
Click to expand...
Click to collapse
Hi,
Just restore the nandroid backup you made.
malybru said:
Hi,
Just restore the nandroid backup you made.
Click to expand...
Click to collapse
Yeah, but I wanted to update to newest kernel. Thanks though
Doesn't work with me.
taffytim said:
You sir deserve a big pint of something great. Point by point I:
1. I already had sdk installed so didnt need to install this.
2. I cleared the phone back to factory with Recovery (Power on with holding -Vol, RECOVERY, Wipe data/Factory Reset, Power Off)
3. I went into HBOOT (by powering on holding down -vol)
4. Opened FASTBOOT and connected phone to computer via USB
5. Opened up command prompt on PC (start menu, typed cmd in the search box)
6. I then Typed the following:
7. "cd c:\Android" (to get me into the folder where my files are)
8. "fastboot flash boot boot.img"
9. this then loaded my boot file and bosh, Im done.
I then restarted the phone and bobs your mothers brother Im using wiresless again. Its such an easy process but on the first go it seems like rocket science.
You cant appreciate how greatful i am for your help. Thank you more than a lot.
If i chose a different ROM at what point is it best to do this stage? Are you able to do this to the boot image before you use recovery to 'insatll zip from sd card'? Or do you have to install then come back to it like i did?
Click to expand...
Click to collapse
I tried this with OrDroid and ViperS laterst versions and the wifi still doesnot work with my device.
It does nor even turn on from the settings, someone please help!
Wi-Fi Issues
theumairahmad said:
I tried this with OrDroid and ViperS laterst versions and the wifi still doesnot work with my device.
It does nor even turn on from the settings, someone please help!
Click to expand...
Click to collapse
Post 3 in this thread explains exactly where the problem is. But ........you will never unlock that boot partition if ur phone is S-ON. The trick with the wire works...it took me couple of times to do it but it worked. Then.....the lates ViperS version does it for you. You do not have to use ADB or whatever that program was to flash the boot.img It is all in the ROM. I even flashed the newest bricked 1.4 kernel on top.....but that 3rd comment is the key to all problems with Wi-Fi and other kernel issues:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
Hello, all. I've spent the last four hours trying update my AT&T HTC One X running Android 4.1.1 to 4.2.2 and I failed hard!
First, I used the all-in-one toolkit to unlock my bootloader, flash clockwork recovery, and root the phone. The first guide I was following gave me error status 7 when I tried to flash the ROM so I wen to this guide:
update-htc-one-x-cm101-android-422-jelly-bean-custom-firmware/2/ (from team android website)
I got to the step below using the SDK I downloaded from dev.android.com and now my phone is dead! The HTC logo appears and then it goes to a black screen. Luckily, I can still reach my fastboot and clockwork recovery menu but nothing I try makes the phone boot.
Step 8 - Type the following command and press Enter.
fastboot flash boot boot.img
Step 9 - Then, type the following command and press Enter.
fastboot reboot
I just want my phone back to normal please! I don't care about rooting anymore. Thank you.
zenkix said:
Hello, all. I've spent the last four hours trying update my AT&T HTC One X running Android 4.1.1 to 4.2.2 and I failed hard!
First, I used the all-in-one toolkit to unlock my bootloader, flash clockwork recovery, and root the phone. The first guide I was following gave me error status 7 when I tried to flash the ROM so I wen to this guide:
update-htc-one-x-cm101-android-422-jelly-bean-custom-firmware/2/ (from team android website)
I got to the step below using the SDK I downloaded from dev.android.com and now my phone is dead! The HTC logo appears and then it goes to a black screen. Luckily, I can still reach my fastboot and clockwork recovery menu but nothing I try makes the phone boot.
Step 8 - Type the following command and press Enter.
fastboot flash boot boot.img
Step 9 - Then, type the following command and press Enter.
fastboot reboot
I just want my phone back to normal please! I don't care about rooting anymore. Thank you.
Click to expand...
Click to collapse
Alright, the ROMs you've been trying to flash are for the quad core One X... please stay in this forum and you should be good to go!
Any ROMs and kernels from here http://forum.xda-developers.com/forumdisplay.php?f=1541 and here http://forum.xda-developers.com/forumdisplay.php?f=1726. Try to flash something from there and report back (you'll still need to flash boot.img
RollTribe said:
Alright, the ROMs you've been trying to flash are for the quad core One X... please stay in this forum and you should be good to go!
Any ROMs and kernels from here http://forum.xda-developers.com/forumdisplay.php?f=1541 and here http://forum.xda-developers.com/forumdisplay.php?f=1726. Try to flash something from there and report back (you'll still need to flash boot.img
Click to expand...
Click to collapse
Thank you very much for your help? Could you please point me to a ROM to flash? I looked through those links and have no idea which to pick/what to do. It doesn't even have to be 4.2...I just want a working phone again. Thanks again!
zenkix said:
Thank you very much for your help? Could you please point me to a ROM to flash? I looked through those links and have no idea which to pick/what to do. It doesn't even have to be 4.2...I just want a working phone again. Thanks again!
Click to expand...
Click to collapse
Well... What would you like? Completely stock? Sense with tweaks? 4.2 with minor tweaks? 4.2 with a ton of tweaks?
RollTribe said:
Well... What would you like? Completely stock? Sense with tweaks? 4.2 with minor tweaks? 4.2 with a ton of tweaks?
Click to expand...
Click to collapse
4.2 with minor tweaks sounds great! Although right now I kinda just want to the stock "boot.img" to verify that my phone is still usable and not totally bricked.
zenkix said:
4.2 with minor tweaks sounds great! Although right now I kinda just want to the stock "boot.img" to verify that my phone is still usable and not totally bricked.
Click to expand...
Click to collapse
Alright then CM10.1 http://forum.xda-developers.com/showthread.php?t=2064621 and AOKP http://forum.xda-developers.com/showthread.php?t=2064724 will both suit you. These have the different boot.img than stock, but just extract and fastboot flash boot boot.img and you should be good to go!
RollTribe said:
Alright then CM10.1 http://forum.xda-developers.com/showthread.php?t=2064621 and AOKP http://forum.xda-developers.com/showthread.php?t=2064724 will both suit you. These have the different boot.img than stock, but just extract and fastboot flash boot boot.img and you should be good to go!
Click to expand...
Click to collapse
Quick update...I flashed boot.img of the first link (CynogenMod) and my phone got passed the "HTC Quietly Brilliant" screen! But now it seems stuck on HTC One (Beats Audio at the bottom) screen. I'll give it a few minutes...
I'm really worried that I did major damage to my phone in the bootloader and clockwork recovery menus. I literally tried every single option there trying to get my phone to boot earlier.
Oh man...it seems stuck. Maybe I should just flash the completely stock boot.img file. If that works, I will factory reset my phone just to make sure everything is back to how it was before.
Dude it sounds like you're trying to flash a cm boot.img with a Sense ROM, that ain't gonna work. You can't just extract a boot.img and flash it with a different ROM.
You need to extract the boot.img from the ROM you're about to flash, then flash that ROM, then flash the boot.img you just extracted.
Sent from my Evita
timmaaa said:
Dude it sounds like you're trying to flash a cm boot.img with a Sense ROM, that ain't gonna work. You can't just extract a boot.img and flash it with a different ROM.
You need to extract the boot.img from the ROM you're about to flash, then flash that ROM, then flash the boot.img you just extracted.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for your help man. If what you're saying is correct, does that mean my phone is hopeless? I deleted/wiped everything using the ClocworkMod Recovery menu. When I choose "install zip from sdcard" I get "E: Can't mount /sdcard/" and when I try to mount an sdcard I get "Error mounting /sdcard". I don't think I can flash any ROMs right now unless install zip from sideload is an option (I don't know how sideloading works).
Try using TWRP recovery instead, you'll find it here:
http://goo.im/devs/OpenRecovery/evita
Download it, check md5 is correct, then:
fastboot flash recovery filename.img
(Filename = exact TWRP recovery filename)
Then issue this command:
fastboot erase cache
Then:
fastboot reboot-bootloader
Now you should be able to select recovery on your phone screen and it should boot into TWRP. Next go to mount and mount usb storage. See if it comes up in Windows, it might need to be formatted from the sounds of it. If it doesn't show up as a usable drive, format it to fat32.
Once that's done you should be able to copy a ROM to your phone to flash. So copy it over, then extract the boot.img from the copy on your pc, then put the boot.img in your fastboot folder.
Do a full wipe in recovery (cache/dalvik/factory reset/system), then install the ROM, then reboot to bootloader, make sure phone is connected by usb, make sure fastboot usb comes up on your phone screen then issue the following command:
fastboot flash boot boot.img
Make sure it's the boot.img from the ROM you just flashed. Now once that's done you should be able to reboot into the ROM.
Sent from my Evita
timmaaa said:
Try using TWRP recovery instead, you'll find it here:
http://goo.im/devs/OpenRecovery/evita
Download it, check md5 is correct, then:
fastboot flash recovery filename.img
(Filename = exact TWRP recovery filename)
Then issue this command:
fastboot erase cache
Then:
fastboot reboot-bootloader
Now you should be able to select recovery on your phone screen and it should boot into TWRP. Next go to mount and mount usb storage. See if it comes up in Windows, it might need to be formatted from the sounds of it. If it doesn't show up as a usable drive, format it to fat32.
Once that's done you should be able to copy a ROM to your phone to flash. So copy it over, then extract the boot.img from the copy on your pc, then put the boot.img in your fastboot folder.
Do a full wipe in recovery (cache/dalvik/factory reset/system), then install the ROM, then reboot to bootloader, make sure phone is connected by usb, make sure fastboot usb comes up on your phone screen then issue the following command:
fastboot flash boot boot.img
Make sure it's the boot.img from the ROM you just flashed. Now once that's done you should be able to reboot into the ROM.
Sent from my Evita
Click to expand...
Click to collapse
This sounds like a good plan. I will give it a try tomorrow after work. Thank you guys for your help!
I couldn't sleep...so I followed your steps and my phone is now alive! Thank you!
I think now I need to flash GApps, right? I have this ---> gapps-jb-20130301-signed.zip
Any chance that's the wrong zip file? Do I need a special one for CM10.1?
That's the right gapps zip, it's the most recent one so yeah you're good to flash it.
And no problems, you're welcome
Sent from my Evita
Hello, I had a MIUI ROM and I flashed a new version , doing the wipes and flashing it, but after the reboot, I see the HTC logo and nathing else, only the black screen.
In my bootloader appears "unlocked", saga pvt ship s-on rl, hboot 2.00.0002.
I tried to flash others ROMs and it happens the same, black screen after the HTC logo.
Thank you.
Did u flash the boot.img after flashing the roms? Since ur s-on u need to flash a rom then boot straight into bootloader and flash the boot.img then reboot. The boot img is inside the rom zip.
jmcclue said:
Did u flash the boot.img after flashing the roms? Since ur s-on u need to flash a rom then boot straight into bootloader and flash the boot.img then reboot. The boot img is inside the rom zip.
Click to expand...
Click to collapse
Can you tell me how to do it? I read something about that but I don't know how to do it.
I had the same problem today but the flash fixed it.
Estrada88 said:
Can you tell me how to do it? I read something about that but I don't know how to do it.
Click to expand...
Click to collapse
The Linux / ubuntu method
I had the same problem and followed the advice of the previous post this is how I did it:
1. First I made sure the fastboot programme was in my home directory
2. Then using a compression program I extracted the boot.img file from the "cm-11-20141214-UNOFFICIAL-saga.zip" rom. I also extracted it to my home directory (same directory as the fastboot program)
3. After installing the Rom and Gapps on my phone via TeamWin Recovery I immediately rebooted into the bootloader. and selected fastboot
4.I connected the phone via usb cable to my laptop.
5.On my laptop I opened a terminal for commandline
6. I entered the following command:
"sudo /home/simon/fastboot flash boot boot.img"
After the flash was successful I rebooted and CM11 is now working. I suppose the windows meathod follows similar principles.
Or use fastboot adb on windows.
Sent from my HTC Desire S using XDA Free mobile app
I'm totally unable to make it works. I have the "waiting for device" message, I'm reading tutorials but nothing works.
Estrada88 said:
I'm totally unable to make it works. I have the "waiting for device" message, I'm reading tutorials but nothing works.
Click to expand...
Click to collapse
U using windows? If so use this tool to setup drivers
http://forum.xda-developers.com/showthread.php?t=2588979
I got it! thank you very much
I'd like to know how to update my TWRP from v 2.4.4.0 to a later version. This version doesn't seem to allow flashing of an img file on external sd card. I have tried without success on 2 computers to get windows to recognise this android, so I'm hoping there is another way. Eventually I'd like to install Katkiss,Gapps and SU on this android. At present it has no rom.
Secondly, I tried to install Cromi X and all goes well up until I reboot and it continually spools on the opening screen so I don't know what that is about but hoping with a later TWRP I may be able to set the partitioning better which may or may not be part of the cause.
Reboot recovery twrp.
Go to install.
Click on install image.
Search downloaded recovery.
Select recovery.
And install.
Done
sent from moto g2014 with cm13
---------- Post added at 03:12 AM ---------- Previous post was at 03:11 AM ----------
Ot use flashify app.
It requires root.
sent from moto g2014 with cm13
There is no 'install image' on v2.4.4.0 and that version of TWRP does not seem to recognise .img files on the external sd card. On a later version of TWRP your solution would work.
If you want to flash the recovery in recovery it has to be inside a flashable zip (except for the latest versions).
You can use the Kang TWRP 2.8.x from post 2 here: http://forum.xda-developers.com/tra...overy-kang-twrp-tf700t-2-8-x-xarea51-t3049395
You can flash Katkiss with it no problem, and it supports the dock SD which the official TWRP does not do.
Somewhere there's also a thread where some dude keeps posting TWRP 3.x in a flashable zip, but I can't think of where right now.
That CROMi-X does not boot can have a number of reasons:
You did not format data before flashing the rom
You are on an outdated bootloader
Something is physically wrong with your emmc.
Your problem to get the tablet recognized in Windows is almost certainly a driver problem an you should get that fixed. At minimum it sucks not to have fastboot access to the tablet. And it easily could be lethal. For the tablet - not for you
Could also be a problem with a cheap knock-off replacement USB cable. If you are not using the original Asus cable that's worth investigating. And if you are using the original it may become worn. Mine is starting to allow a connection only in certain positions... Age....
Make sure the device drivers are installed and try the Google Universal Naked drivers. Minimal ADB and fastboot is an excellent tool that shimp208 still keeps current after all this time, and if none of those work try the 15 second adb installer if you are on Win 7 or earlier (just google it).
Hello my old friend. Well I have finally managed to get an adb connection and am going over to old posts of previous help you gave me with this device. Although the device is now recognised I can't get any commands to work e.g. fastboot devices simply returns me to the c:/adb prompt and adb reboot bootloader just takes the flashing underline symbol to the next line and nothing happens. I have hope that I will be able to get this working OK now I have adb access. How do I know if I am on an outdated bootloader? thanks
plato2 said:
Hello my old friend. Well I have finally managed to get an adb connection and am going over to old posts of previous help you gave me with this device. Although the device is now recognised I can't get any commands to work e.g. fastboot devices simply returns me to the c:/adb prompt and adb reboot bootloader just takes the flashing underline symbol to the next line and nothing happens. I have hope that I will be able to get this working OK now I have adb access. How do I know if I am on an outdated bootloader? thanks
Click to expand...
Click to collapse
This is not the same device you helped me with earlier...it now purrs beautifully.... this is a new challenge.
plato2 said:
Hello my old friend. Well I have finally managed to get an adb connection and am going over to old posts of previous help you gave me with this device. Although the device is now recognised I can't get any commands to work e.g. fastboot devices simply returns me to the c:/adb prompt and adb reboot bootloader just takes the flashing underline symbol to the next line and nothing happens. I have hope that I will be able to get this working OK now I have adb access. How do I know if I am on an outdated bootloader? thanks
Click to expand...
Click to collapse
Thought you looked familiar..... :cyclops:
Time to re-read this I think http://forum.xda-developers.com/showthread.php?t=2688891
Boot into the bootloader and read the small script. The last bootloader for this tablet is 10.6.1.14.10.
Yes, that is the bootloader I have. Typing fastboot devices takes me back to the/adb prompt and then typing
fastboot -i 0x0B05 flash recovery <name-of-file>
I get a <waiting for device> but nothing happens.
plato2 said:
Yes, that is the bootloader I have. Typing fastboot devices takes me back to the/adb prompt and then typing
fastboot -i 0x0B05 flash recovery <name-of-file>
I get a <waiting for device> but nothing happens.
Click to expand...
Click to collapse
Yeah, so you have a driver problem. This is nothing you have to do now. Just download the flashable zip of Kang TWRP and flash it in your current recovery.
But when you have some time to kill open Device Manager and connect and disconnect the cable to the tablet. It should give you SOME change in device manager. If it doesn't, reboot both tablet and PC and try again.
Then try a different cable.
Still nothing? This could take longer. Driver problems suck in Windows....
So - you got yourself another TF700? Had just too much fun getting Katkiss to work on the last one, eh?
berndblb said:
Yeah, so you have a driver problem. This is nothing you have to do now. Just download the flashable zip of Kang TWRP and flash it in your current recovery.
But when you have some time to kill open Device Manager and connect and disconnect the cable to the tablet. It should give you SOME change in device manager. If it doesn't, reboot both tablet and PC and try again.
Then try a different cable.
Still nothing? This could take longer. Driver problems suck in Windows....
So - you got yourself another TF700? Had just too much fun getting Katkiss to work on the last one, eh?
Click to expand...
Click to collapse
Just download the flashable zip of Kand TWRP and flash it in your current recovery.
I don't know what you mean here.... how do I 'flash it in my current recovery' I have v 2.4.4.0 and it doesn't see img files on external sd.
plato2 said:
Just download the flashable zip of Kand TWRP and flash it in your current recovery.
I don't know what you mean here.... how do I 'flash it in my current recovery' I have v 2.4.4.0 and it doesn't see img files on external sd.
Click to expand...
Click to collapse
If you downloaded from the second link, the flashable zip, you will see a zip file, not an img file.
Just hit Install, select the zip and swipe the button. Reboot when the flash is finished
All good so far. Up to the wiping data bit before converting to f2fs but this guide is missing, not sure why. I recall it was only a short set of instructions: Once that is done follow this guide to convert internal data to f2fs: http://forum.xda-developers.com/tran...p-2-8-t3073471. Can you recall that part? thanks
Got it, found it or rather another post of yours here: tf700/help/how-to-update-twrp-withoput-adb-t3437702/post68163144#post68163144 so did that and successfully installed Katkis, Gapps pico and SU....another beautiful TF700T purring...many thanks yet again...
hi guys,
i my shield is stuck on the nvidia logo when booting normally, if it brings up the bootloader, it shows unlocked but hitting continue caused it to freeze on the screen, recovery freezes on nvidia logo and fastboot protocol just brings it back to this screen. i orginally installed twrp and it confirmed successful flash of new os .... on reboot it bricked to its now state, i cant get into twrp or get my pc to see it to install a new copy
anyone got any ideas
thanks
@Fairmax don't click continue, it freezes because there is nothing to continue to, as long as you can enter bootloader your device isn't fully bricked. So, to fix your problem you will have to download official ROM from nvidia's site (https://developer.nvidia.com/shield-open-source find your model and click recovery images).
When you download latest ROM unzip it and follow the textual guide, but, there will be one file missing (i can't remember which one, user data maybe or something like that), don't worry and just continue with the next step. After you flash just reboot to system by holding power button. Good luck !
i cant seem to get it to be recognised by windows all i get is this-- Windows has stopped this device because it has reported problems. (Code 43) A request for the USB device descriptor failed.--
trying to install nvidia usb driver via have disk bring up an error that the file is not usable with x64 system
ok after many driver reinstall iv got device manager to say android adb interface but still not showing on on device list in cmd
Fairmax said:
ok after many driver reinstall iv got device manager to say android adb interface but still not showing on on device list in cmd
Click to expand...
Click to collapse
Which command did you type in?
fpozar said:
Which command did you type in?
Click to expand...
Click to collapse
adb devices shows no devices
i tried the 3 different option in the driver install which was android adb, bootloader, and something else and nothing shows in devices. i tried it on my laptop and a different cable and cant get adb to list the device :crying:
Fairmax said:
adb devices shows no devices
i tried the 3 different option in the driver install which was android adb, bootloader, and something else and nothing shows in devices. i tried it on my laptop and a different cable and cant get adb to list the device :crying:
Click to expand...
Click to collapse
Well of course adb devices shows no devices because you are not actually in adb mode, you are in the bootloader mode. Just download minimal fastboot and adb, install it and extract recovery image into the folder where you installed minimal adb and fastboot (you don't need any other drivers).After you did this and your device is in bootloader and connected, click on the path in your fastboot & adb folder and delete everything and type cmd. No need to do adb devices, just proceed with fastboot flash ...
fpozar said:
Well of course adb devices shows no devices because you are not actually in adb mode, you are in the bootloader mode. Just download minimal fastboot and adb, install it and extract recovery image into the folder where you installed minimal adb and fastboot (you don't need any other drivers).After you did this and your device is in bootloader and connected, click on the path in your fastboot & adb folder and delete everything and type cmd. No need to do adb devices, just proceed with fastboot flash ...
Click to expand...
Click to collapse
ah now that makes sence....silly me i dont do this very often . so fastboot saw device and iv uploaded all parts of the recovery image and rebooted but it is still stuck on the nvidia logo, that was the original file so now il try 5.2.0 and see if that works
Fairmax said:
ah now that makes sence....silly me i dont do this very often . so fastboot saw device and iv uploaded all parts of the recovery image and rebooted but it is still stuck on the nvidia logo, that was the original file so now il try 5.2.0 and see if that works
Click to expand...
Click to collapse
You can also try flashing twrp and then lineageos or something from twrp.
fpozar said:
You can also try flashing twrp and then lineageos or something from twrp.
Click to expand...
Click to collapse
good news after a few hours of trying (usb dropped connection a few times then battery died) it finally works again .....been over 2 years since iv had this shield running after nvidia did the recall , now goto put a different rom on there so it dosnt update and kill itself
Hello I had a similar issue with my k1 tablet and ended up flashing factory images via adb fastboot and all flashed fine. Now my tablet is stuck on the boot screen with the green and white nvidia logo. How long does it take to boot please?
I have same issue too. I can load TWRP and flash the other partitions but TWRP shows un-mountable partitions and even a full stock ROM flash will not allow it to boot. I have a similar issue with a recall tablet. what did you do to fix it?