I installed the 3.0 update and it never removed TWRP, however TWRP is not working. If I flash the zip file for 3.0 it reboots the system in the middle of installing. I tried flashing the cm12 and cm13 zip files and they say they flashed successful but nothing appears to have installed, and I currently have no rom or firmware installed and can't seem to boot to fastboot. Any ideas?
Here is what happens when i flash the 3.0 zip file. https://youtu.be/-ZVnaNdn6-M
I seen the same logo don't know what to do as well. My parent click update while i was away from home when i got back it just the logo with nvidia.
Restore using the recovery images here for your device https://developer.nvidia.com/gameworksdownload using fastboot not twrp.
The way I get to bootloader is pull the power cable, plug back in and hold power immediately until the menu appears YOU MUST HAVE micro usb connected to a pc while doing this.
I'll give it a try. Thank you for the reply
Try this:
http://forum.xda-developers.com/shield-tv/general/guide-how-to-flash-recovery-image-t3321404
Related
I just got the new CWM recovery update through Rom Manager today, and it said it was successfully flashed, but the phone only hangs on the HTC logo when goingto recovery. I can still do fastboot and boot to Android tho, so I'm now gonna try to figure out how to get my recovery back before something bad happes xD
anyone have advice or know where I can download a standalone copy of CWM 5.0.0.1 for G2?
Wish me luck I'll keep updating as things progress
okipokey, solved my own issue. Just had to reflash back to an older recovery and try again a couple times before it stuck.
Time to test out the new recovery!
I decided to flash the upgrade as well. The flash went perfectly. However, I couldn't boot into recovery while within Android. I had to power off and boot into the bootloader and then select recovery... Whenever I tried to reboot to recovery via the Android UI, it restarted and hung at the boot splash screen.. It didn't even work if you selected the option from the ROM Manager itself... I rolled back to previous version as well and its working again. It may be a bug... Early adopters nightmare....
Same here just reinstalled the new version and it worked second time round
must be a bug they havn't quite worked out. Next time I'll do a fastboot flash instead for a low build number.
First time I flashed I tried it from a battery pull through HBOOT and it still hung. Reflash to 3.5 and then back to 5.0 fixed it like you guys
epolaris said:
I decided to flash the upgrade as well. The flash went perfectly. However, I couldn't boot into recovery while within Android. I had to power off and boot into the bootloader and then select recovery... Whenever I tried to reboot to recovery via the Android UI, it restarted and hung at the boot splash screen.. It didn't even work if you selected the option from the ROM Manager itself... I rolled back to previous version as well and its working again. It may be a bug... Early adopters nightmare....
Click to expand...
Click to collapse
try just reflashing version 5 I had the same problem,but rebooted the phone reflashed version 5 from the rom manager and now is all good
I just sent the dev a comment about it on his Google+
maybe he'll have a fix out soon
Nice one, seems a "double flash" fixes it have just tested 3 or 4 times,seems to be working
yessir, seems to me that if it's a bug its really minor. I can see this being a problem if someone accidentally screws up something on their phone right after flashing the recovery, but not very likely and they'd still be able to reflash through fastboot
Seemed to flash the new version ok. But then, when trying to boot into recovery for the first time, the phone hung on the HTC logo boot splash. Pulled battery, and booted into recovery ok after that.
that's interesting that some of you didn't hang after the battery pull while mine did. Maybe it depends which version we're upgrading from?
stuck at htc
hey i also had this problem and i can't get my g2 to boot up at all. It hangs at the htc screen. I don't know how to fix this issue as i was trying to restore a backup from recovery right after the update. i can't get into recovery or anything else...all i get is the htc screen. Any ideas how I can fix this?
Luis
Any sign of a changelog?
I have no idea how to get to a changelog...can you tell me how?
biglou421 said:
I have no idea how to get to a changelog...can you tell me how?
Click to expand...
Click to collapse
found this
-From Mr.Dutta via G+
I've just finished releasing updates to a bunch of devices to ClockworkMod Recovery 5.
Major changes:
Backups now use tar over yaffs for everything except mtd partitions. Backups got way faster.
Backups now preserve the filesystem type at time of backup. Restores will restore the appropriate filesystem type at restore.
Please update to ROM Manager 4.4.0.3 or higher and try out the new recovery!
Troubleshooting:
Flashing issues: If a recovery does not flash properly, enable erase recovery in settings and try flashing it again. Recovery flashing can be finicky at times.
Bugs: Report them to me! You can always revert back to the older recovery too from within ROM Manager!
So far no issues here while playing around.
my issue is i can't get back to android at all now. i went into rom manager to restore a backup and was told there was an update, then it reflashed the recovery. When i tried to restore my backup it froze and i have not been able to get past the htc screen at all.
biglou421 said:
my issue is i can't get back to android at all now. i went into rom manager to restore a backup and was told there was an update, then it reflashed the recovery. When i tried to restore my backup it froze and i have not been able to get past the htc screen at all.
Click to expand...
Click to collapse
can you get into the HBOOT?
pull the battery, put it back in, hold the volume down button and then hit the power button. you should come to a white screen with some options
In the case you want to update your recovery using fastboot method, heres what you'll need:
CWM 5.0.0.1 for G2 (Vision)
HTC Sync drivers
ADB fastboot from Android SDK
Make sure your phone is all the way off by pulling the battery. Get into the HBOOT by holding down the volume down button and then hitting the power. use the volume keys to navigate and the power button to select. Choose "FASTBOOT"
Rename the recovery that you downloaded from CWM to "recovery.img" and put it in your ADB and Fastboot folder
plug your phone into your computer and pull up a command line for your adb/tools/ or adb/platform-tools/ folder where you should have ADB and Fastboot.
under the command line type in:
fastboot devices
<list of devices>
If you do not see your device make sure the cable is plugged in and your drivers are installed. if still nothing try a different cable til you get it to be recognized by the computer.
Once it's recognized do:
fastboot flash recovery recovery.img
when its done:
reboot
I flashed through ROM manager. On suggestion, I checked the box for "erase recovery - recovery will be erased prior to flashing". On first reboot to recovery it sticks at HTC screen. Pulling battery and vol. up+power then entering recovery the 2nd time works just fine.
Hope this helps.
Hey guys.
After the time I spent trying to unbrick my softbricked shield 2015 16gb, I decided to share how I was able to solve it.
I was on 5.2 and decided to update to 6.1 since the developer image was released and my previous upgrade from 5.1 to 5.2 with flashfire run so smoothly so what could go wrong??
After install lastest flashfire 0.73, I select all but data on the flash firmware package, and let it run.
I had my shield on 5.2 rooted and with TWRP as recovery.
After flashing vendor.img it restart and get stucked on the nvidia logo, and there was where
my problems started.
After 30 min I switched off and on again and same thing. Nvidia logo and nothing more. 1 hour after that I finally was able to go into bootloader mode.
I needed to use the default USB cable that came with the shield connected to OTG and USB on my computer. As soon as I connect the power and the led goes on I pressed the power button until I was
able to see the menu.
From there I was able to run fastboot. I reinstall every build and the shield refused to back to life. Flashed successfully but wont go through nvidia logo.
I enter recovery and did a reset assuming I had some problem with my data. No luck. I start to assume my shield has a hardware problem.
I downloaded both the stock recovery and the developer image 6.1, 6.0, 5.2, 5.1.
Tried to flash all of them one by one. Nothing worked. It complete the flash process but after reboot keep stucked on the logo.
Lots of time reading XDA and googling it I found a TWRP 5.1 flashable zip image, and in last resort I download it, reflash TWRP and flashed the 5.1 zip image.
It worked!!
I run the wizard as a new shield, and return to TWRP and flashed SuperSu 2.79. Rebooted, and install flashfire and run again the process with the 6.1 developer image.
This time flashed ok, and I finally get 6.1 rooted and working perfectly.
So resuming all the steps for those who dont want to read all
If you are stuck on Nvidia logo after flash 6.1
1 - Download firmware 5.1 zip TWRP flashable (search on XDA)
2 - enter bootloader on your shield hardware mode. Connect the OTG port on Shield using the default USB cable, and after connecting the power and the green light turn on press the power button until the bootloader menu appears.
3 - Assuming you already had the shield drivers and ADB installed on your computer, go to TWRP recovery or install it. I flashed TWRP 3.02 (once again search for it on XDA). fastboot flash recovery "twrp filename.img"
4 - Boot to TWRP and upload the firmware with the command adb push "firmware filename.zip" /sdcard/
5 - Upload also the SuperSu 2.79 binaries. adb push "supersu filename" /sdcard/
5 - from TWRP install the firmware and let it run. It will generate some errors but it will work.
6 - Reboot and complete the wizard.
7 - Reboot to TWRP (you can activating developer mode, and run adb reboot recovery from inside the androidsytem) and flash the SuperSU
8 - Reboot again and install the latest flashfire.
9 - Download the 6.1 developer image (search XDA for it)
10- Run flashfire and install the firmware package. Thats it!
Hope this will help someone
Hi guys
SO Ive tried a number of things.
Im currently stock in recovery or fastboot.
It happened after I applied a substratum theme on 8.1 Resurrection Remix and I restarted the phone because it froze on applying the theme.
No mater what I do I always end up in recovery.
Things tried so far:
Everything besides ext. Sd wiped numerous times before and after reinstall.
Full restore including everything (bootloader, recovery, cache, all the restore options you can use in TWRP aka the full monty. based on Fulmics 4.2 ive used to restore beforehand)
Full reinstall of Resurrection Remix
Full reinstall of Fulmics
Reinstall of TWRP
Reinstall of MElina TWRP
Each and every reinstall and restore takes me promptly to TWRP just after the LG logo..
My question is, how do I fix this?
I have full access to both fastboot and recovery
Lgup and uppercut clean flash
Thanks do you know how I get Windows 10 to detect it as a LG handset not just ADB or Bootloader interface? LG USB drivers are installed.
It does recognize it as portable device. (probably MTP mode as I have full access to)
Edit 2: I discovered as soon as I plug in USB on the PC the phone boots up and into TWRP even if I've turned it off prior to that
So I thought locking the bootlooker was a good idea.. Apprently not as I now can't get past "Your device is corrupt" screen.
I can almost boot into bootloader until the last confirmation "delete userdata screen" after where it goes back to "your device is corrept" screen..
Can get into iMEI display screen - Never seen that one before
Power off your phone and when the screen turns black press and hold vol up and plug in your usb cable. Your pc must find your G6. Then download a stock rom and flash it with lgup and uppercut.
MozezzFG said:
Power off your phone and when the screen turns black press and hold vol up and plug in your usb cable. Your pc must find your G6. Then download a stock rom and flash it with lgup and uppercut.
Click to expand...
Click to collapse
You're a godsent!!
Hello, Before starting this Thread i wanna say sorry for my bad english.
Want to Install Stock ROM Lollipop. But the System Cannot Flash/Install that ROM.
Previous, i'm using Ressurection Remix 5.8.5 . All Went Normally, Until i decided wanna back to Stock ROM and get this error.
Situations :
* The Device Stuck on Boot Logo, and No responsibility
* The Device cannot Reach Recovery, Adb, fastboot, even not detected in Device Manager when i Wanna try Flash using QFIL
* Vol Up+Down + Power Buttons Not Works, Only Blink Blue on screen and then reboot.
Chronologic
1. I'm using TWRP 3.2.1 , Wiped System, Data, Cache. And then start flashing Stock ROM
2. When Process, it says Update failed
3. Using Minimal ADB, I tried to flash Stock Lollipop Recovery. And failed.
4. Accidentally, i typed "Adb Reboot recovery.img" which should fastboot Boot Recovery.img
5. The Device rebooted and Stuck on Logo, Until Now
Anyone pls help, Any comment helpful very appreciated.
Thank You for ur attention.
Remove and re-insert the battery. Then hold volume down + power button and see if the phone boots into download mode. If it does, then connect it to a pc with adb installed and see if adb detects it. If all goes right, you could try to install twrp recovey and afterwards install stock firmware through it. Google search A6000_S056_150924_WC51.zip and download the firmware and copy it to the external sd card then flash using twrp.
Although guessing by the state of your phone it seems unlikely that this will work. But give it a try. Hope it helps.
Thanks! It Worked
user0u said:
Remove and re-insert the battery. Then hold volume down + power button and see if the phone boots into download mode. If it does, then connect it to a pc with adb installed and see if adb detects it. If all goes right, you could try to install twrp recovey and afterwards install stock firmware through it. Google search A6000_S056_150924_WC51.zip and download the firmware and copy it to the external sd card then flash using twrp.
Although guessing by the state of your phone it seems unlikely that this will work. But give it a try. Hope it helps.
Click to expand...
Click to collapse
I Try your Method, and its Worked. Now I can use my phone Use As usual.
Thank You very Much!
Thanks man you are so awesome successfully flashed Android lollipop ROM in my Lenovo A6000+ thank you so much
I need help tooo
user0u said:
Remove and re-insert the battery. Then hold volume down + power button and see if the phone boots into download mode. If it does, then connect it to a pc with adb installed and see if adb detects it. If all goes right, you could try to install twrp recovey and afterwards install stock firmware through it. Google search A6000_S056_150924_WC51.zip and download the firmware and copy it to the external sd card then flash using twrp.
Although guessing by the state of your phone it seems unlikely that this will work. But give it a try. Hope it helps.
Click to expand...
Click to collapse
I am having same issues but when its in download mode my pc shows alot of drives n asking me to format it n the downloder is not reading my phone n the fastboot is showing the remote error n adb doesnt detect my phone at all......i need helppp
Hello guys, I am at the brink of a mental breakdown because it seems like I bricked my 860€ S10+.
I tried to root it as instructed in wu's guide. I was able to flash the patched ap together with the firmwares other files. But when I rebooted Magisk wasn't installed nor activated. So I tried to reflash everything and I guess I ended up bricking my s10. So I flashed the stock firmware. That worked out.
And now I tried to flash the patched ap again but Odin gets stuck at system.img (upper screen said "DTBO" though) Nothing happens. And Odin does nothing as Task Manager tells me.
So now I tried to flash the stock firmware again and retry everything. But suddenly I can't even do that! Odin gets stuck at recovery.img and then does nothing. Reflashing, wiping data, using different usb ports, 3 different PCs. Nothing helped.
I mean before I was at least able to reflash the stock firmware and now even that doesn't work out. And now I am stuck with a phone that isn't rooted but still has all the disadvantages of a rooted s10 (knox apps etc.)
I don't know what to do anymore. Can anyone please help?
Sounds to me like a similar issue I had. I think your firmware files might be corrupted. I'd recommend re-downloading the latest firmware again from the SamFirm tool and give it another go.
What fixed this issue for me was redownloading odin, reinstalling the usb drivers and then restarting my phone and PC. Then try again, it'll finish the flash. Flash the completely stock firmware though, for some reason it only allowed me to flash the stock firmware and not the magisk one until I had a working phone. Mine would get stuck on the userdata bit.
Restart your pc. Should do the trick, i done it a few times with early release of twrp
mercifool said:
Restart your pc. Should do the trick, i done it a few times with early release of twrp
Click to expand...
Click to collapse
I did that, but unfortunately it didn't help :/
Chocolatetrain said:
What fixed this issue for me was redownloading odin, reinstalling the usb drivers and then restarting my phone and PC. Then try again, it'll finish the flash. Flash the completely stock firmware though, for some reason it only allowed me to flash the stock firmware and not the magisk one until I had a working phone. Mine would get stuck on the userdata bit.
Click to expand...
Click to collapse
hey, thanks for your reply! I tried to flash an older firmware before, that's why I wasn't able to even flash the stock firmware. So now I was able to flash the stock firmware but still when I try to flash the patched ap, whether I try only the patched AP or together with the whole firmware, it still gets stuck at system.img... And I redownloaded odin, reinstalled the USB driver and restarded phone and pc. didn't work...
FPSkillerPC said:
Sounds to me like a similar issue I had. I think your firmware files might be corrupted. I'd recommend re-downloading the latest firmware again from the SamFirm tool and give it another go.
Click to expand...
Click to collapse
hey man, thanks for your reply! It seems like I downloaded the wrong firmware earlier. Now I got the right firmware. I was able to flash the stock firmware at least! But still after repatching the correct ap file, odin gets stuck at system.img
thomas333 said:
hey man, thanks for your reply! It seems like I downloaded the wrong firmware earlier. Now I got the right firmware. I was able to flash the stock firmware at least! But still after repatching the correct ap file, odin gets stuck at system.img
Click to expand...
Click to collapse
Try copying the patched file magisk creates to the sd card (with any file manager) and copy it to your PC with a card reader. If you don't have sd or card reader Google the commands to copy with adb. MPT file transfer might corrupt the file. Also make sure that you fill the rest of the files from the firmware package (BL, User etc) don't flash just with AP. If you didn't fill them before try flashing with all files first, if it still fails try adb or sd card, your file must be corrupt.
How did you convert it to .tar for odin?
Hold down volume down and Bixby button while your phone is off and plug in your cable while it is connected to a computer you should get download mode from there you can re Flash the stock firmware After that if you want to root your phone and have TWRP recovery this is what I did for my s10 plus and It worked flawlessly:
1 make sure bootloader is unlocked
2 if it's not unlocked do a factory reset
3 Set up phone and skip everything
4 Turn developer mode on
5 make sure you have latest firmware so you can extract that AP file
6 Install magisk manager if you dont have it
7 Use magisk to patch AP file by hitting install as if you were going to install it then got to patch file and select AP file and it will start patching and create an file in your download folder
8 Take the new file and copy it to your computer
9 Install odin if you haven't
10 Put the new file in the AP slot in odin and uncheck auto reboot and everything else
11 Turn off phone
12 Hold vol down and bixby and plug in phone to computer to put it in download mode
13 Flash the AP file with odin
14 Once done flashing hold power and vol down till it turns off then quickly hold vol up with power and Bixby to boot to recovery
15 Wipe data and factory reset
16 Then select power off
17 Then like you were going to boot into recovery hold vol up with Bixby and power but once you see the 1st warning screen come back let the buttons go
18 It should boot up you phone like normal but now you have root
19 Now download the TWRP app, find your phone model and download the img file but don't flash it yet
20 Now open magisk and patch the file you just downloaded
21 Now you can flash the file that was just created with the TWRP app
22 You should have TWRP recovery now but to check turn off the phone and boot to recovery with the Bixby, vol up and power buttons then once you are done confirming go to reboot and select power off then boot the phone by holding the buttons like you would to get to recovery but only till the first warning screen comes back then let them go and it should boot back rooted like before
23 If you have any problems try to reboot as I just explained again and if that still doesn't work the device may have encrypted it self so you will have to boot back to recovery and select wipe, format data, type in yes and confirm then go back to wipe option and select factory reset then go to reboot, power off, and hold buttons like booting to recovery then let go when the first warning screen comes back
24 You will need to setup you device again but its unencrypted now...enjoy!!!
Im sure this dude has a crap type c cord. I had the same stoppage at system.img and i just changed my type c to usb.
NZnewbie said:
Im sure this dude has a crap type c cord. I had the same stoppage at system.img and i just changed my type c to usb.
Click to expand...
Click to collapse
Odin never worked with any USB 3.0 port. Has to be USB 2.0
Type C is a form of USB 3.0
Sent from my SM-G975U1 using XDA Labs