Okay, so yesterday I was flashing from SlimBean to stock 4.3 on my Nexus 7. Okay, good no problem. After that I was using WugFresh's toolkit to update from 4.3-4.4 since my bootloader is unlocked and it wouldn't take the OTA. The cmd prompt said something akin to:
boot.sig not in archive
Recover.sig not in archive
And then it froze, for a bit before giving me the end message about the first reboot taking 5-10 minutes. OK, cool. I was still in fastboot mode, so I went ahead and volume upped to start. The Google image flashed, along with the unlock symbol, and in very tiny text at the top right says Booting Failed.... On the same screen off to the right is the arrow that says start, just like in bootloader. I'm freaking out because this is basically brand new, and I don't wanna NAFTA buy another.
Oh, and it's the 2012 Grouper/Nasaki WiFi only model.
Thanks in advance for any and all advice.
Sent from my GNEX running SlimBean
Just boot back to bootloader and flash a custom recovery through fastboot
Then boot back to this recovery and flash ROM of choice
If you want to go back to stock fully then drop the tool kits and just flash stock and relock bootloader
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Just boot back to bootloader and flash a custom recovery through fastboot
Then boot back to this recovery and flash ROM of choice
If you want to go back to stock fully then drop the tool kits and just flash stock and relock bootloader
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Alright I did that, erasing the non existent recovery as well. Now when I try to boot, its stuck at the Google logo. When I enter bootloader and select reboot recovery, it just goes to the screen with Google logo and the fastboot arrow
Sent from my GNEX running SlimBean
So through fastboot you ran
fastboot erase recovery
fastboot flash recovery recovery.img
And output said OK to both and the recovery you used was for grouper correct? The md5sum checked out right?
If so you may need to flash a factory image from google
https://developers.google.com/android/nexus/images
This time
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot update nameofupdate.zip
Oh and you may need to relock bootloader before update
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
So through fastboot you ran
fastboot erase recovery
fastboot flash recovery recovery.img
And output said OK to both and the recovery you used was for grouper correct? The md5sum checked out right?
If so you may need to flash a factory image from google
https://developers.google.com/android/nexus/images
This time
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot update nameofupdate.zip
Oh and you may need to relock bootloader before update
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Alright, so after i flashed the recovery, I attempted to boot into recovery. I am stuck at the google logo. But let me try the rest of the commands you gave me really quick.
Oh, and when I downloaded the factory image, I got a .tgz file, not a zip.
Sent from my GNEX running SlimBean
So the recovery.img you are flashing through fastboot says it worked but when you boot to it you get nothing? Is this correct? What recovery image are you flashing?
Can you try
fastboot boot recovery.img
Sent from my Nexus 7 using Tapatalk 2
Alright, I figured it out. The recovery was flashing right, but the file I had wouldn't stick for some reason. So I found the grouper TWRP .IMG file, flashed it, and it stayed. After that, it was as simple as pushing the file and flashing it all. Thank you so much for all of your help in this matter. Hope to see ya around the forums!!!
Sent from my Nexus 7 using xda app-developers app
Related
Use Rom Manager for best results when backing/restoring...
USB OTG Info:
USB OTG will show up as external_sd. If external_sd is not mounting, reboot recovery. You must enter recovery with usb already inserted.
Installation:
Inscrutions can be found here @ http://www.techgeekal.com/2013/03/1...ckworkmod-touch-recovery-v6-0-2-8-on-htc-one/(outdated)
Unlock bootloader at http://www.htcdev.com/bootloader/
Make sure fastboot is unchecked in power options and turn phone completely off
Boot into HBOOT then Fastboot
From fastboot. Use command "fastboot erase cache"
From fastboot. Use command "fastboot flash recovery recovery.img"
OR
Flash via Rom Manager(must have root already).
Video Tutorials:
How To Unlock The Bootloader EASIEST Method - https://www.youtube.com/watch?v=r0gzJdwCxX0
How To ROOT EASIEST METHOD - https://www.youtube.com/watch?v=S1KmsxO84UU
Downloads:
You can now flash in Rom Manager in rom if rooted
Classic - http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.3-m7att.img
OR
Touch - http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.3-m7att.img
PC USB Mass Storage:
You can't! http://teamw.in/DataMedia
Mirror for files http://d-h.st/users/flyhalf205/?fld_id=11322#files or http://www.clockworkmod.com/rommanager
Thanks for this. :good:
How do you flash recovery on fastboot? Is this a cmd line I have to do with pc?
Sent from my HTC One using Tapatalk 2
rgoyena said:
How do you flash recovery on fastboot? Is this a cmd line I have to do with pc?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Yep. Open up cmd and navigate to fastboot then run rhe command or flash with the toolkit
Sent from my ADR6425LVW using Tapatalk 2
Flyhalf205 said:
Yep. Open up cmd and navigate to fastboot then run rhe command or flash with the toolkit
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Do you flash supersu in recovery for root?
Sent from my HTC One using Tapatalk 2
rgoyena said:
Do you flash supersu in recovery for root?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Yep. That or superuser. Whichever one you prefer.
Sent from my ADR6425LVW using Tapatalk 2
CWM Touch is just flat out not working for me. I flash via fastboot, but when I try to reboot into recovery it fails and goes back to OS.
Hunt3r.j2 said:
CWM Touch is just flat out not working for me. I flash via fastboot, but when I try to reboot into recovery it fails and goes back to OS.
Click to expand...
Click to collapse
Make sire your turning phone completely off and boot into fastboot via power and volume down.
Sent from my ADR6425LVW using Tapatalk 2
Yep! Touch is working awesome for me!
I also had problems with the touch not working, so I switched to the non-touch version and it works fine.
i have the HTC one Dev edition. I just want someone to tell me that it's identical to the ATT version. AFAIK it is. I just want someone to confirm that for me before I go ahead flash the wrong thing and brick my phone
adityaksharma said:
i have the HTC one Dev edition. I just want someone to tell me that it's identical to the ATT version. AFAIK it is. I just want someone to confirm that for me before I go ahead flash the wrong thing and brick my phone
Click to expand...
Click to collapse
Flash away. It's fine. The dev edition is the same device as an unlocked 64 GB ATT phone
I have the device Bootloader unlocked and i
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I get a successfully sent, however i am unable to boot into recovery via cmd or bootloader
Any ideas?
Thanks
Drew
drewdatrip said:
I have the device Bootloader unlocked and i I get a successfully sent, however i am unable to boot into recovery via cmd or bootloader
Any ideas?
Thanks
Drew
Click to expand...
Click to collapse
make sure Fast Boot is NOT selected in Settings/Power. Then turn the phone COMPLETELY OFF and boot to Hboot then fastboot and flash recovery again. Then power off and reboot to hboot. If it says *Tampered* at the top your all set, if it doesn't, then recovery didn't take. I had to flash recovery 6 or 8 times, but I think the deciding factor was when I turned fast boot off in Settings.
Ok. In order to flash a boot.img do we have to rename it to boot.img.zip ? I'm trying to completely understand how to flash the boot.img using HTC dumlock rather than having to use the computer all the time for fast boot.
Sent from my HTCONE using Xparent Blue Tapatalk 2
treIII said:
Ok. In order to flash a boot.img do we have to rename it to boot.img.zip ? I'm trying to completely understand how to flash the boot.img using HTC dumlock rather than having to use the computer all the time for fast boot.
Sent from my HTCONE using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
To flash a boot.img. You must enter fastboot on the phone. and issue the fastboot command fastboot flash boot boot.img using a computer.
For some reason, I cannot enter recovery. I get the entering recovery screen, then it boots back to the boot screen and freezes there. Gonna try to fastboot flash the recovery img
Sent from my HTC One using xda premium
cdordon said:
For some reason, I cannot enter recovery. I get the entering recovery screen, then it boots back to the boot screen and freezes there. Gonna try to fastboot flash the recovery img
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Fastboot erase cache, then retry fastboot flashing your recovery
Sent from my HTC One using Tapatalk 2
cdordon said:
For some reason, I cannot enter recovery. I get the entering recovery screen, then it boots back to the boot screen and freezes there. Gonna try to fastboot flash the recovery img
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Also Make sure fast boot is turned off in settings. Then cold boot into hboot then fastboot then flash.
Sent from my ADR6425LVW using Tapatalk 2
Is this exactly the same as the CWM Recovery in the international HTC One M7 forum?
I got an HTC One today, and wanted to install MIUI, as it is very similar to iOS and I've been using an iPhone since the 3G came out. I've jailbroken most of my devices so I figured rooting it would be a fairly similar experience. I was wrong. It was complicated, but nothing I couldn't handle. I get to the point where I flashed MIUI through TWRP and then flashed my boot.img through terminal. Tried to boot and got stuck at the animation logo for 15 minutes. Started troubleshooting trying to figure it out. Tried reinstalling, etc. One time I went to advance wipe and chose cache, dalvik cache, and internal storage on accident and wiped it. Immediately realizing what I had done, I knew I ****ed up. Followed some instructions to do a ADB Sideload and it worked, flashed my boot.img again and now I'm still stuck in that loop.
I don't know what to do at this point. I'm downloading the stock RUU so I can maybe just relock the bootloader and try again. Please explain any procedures to me like I'm 5. I'm very new to Android, and compared to the one click jailbreaking available to the iPhone, this is a little messy.
Appreciate the help in advance.
Make sure you have the right version of MIUI. ADB push the zip in recovery and flash it. Don't flash boot.img.
What commands do I type in to cmd after i cd \Android into the folder with that stuff? I'm unsure of how to push the zip installation onto the phone in recovery mode.
Adb sideload sideload.zip
Sent from my HTC One using Tapatalk 4 Beta
Nick281051 said:
Adb sideload sideload.zip
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
No luck sideloading the zip file either. I know it's the right file...
Did you rename the file sideload.zip?
Sent from my HTC One using Tapatalk 4 Beta
Yup. Tried it as MIUI.zip, then sideload.zip
Don't really know where to go from here. I cannot get out of the boot loop no matter what I try. I've flashed the boot.img through terminal, I've flashed it through Hasoon's AIOK and I still get stuck there.
I'm lost.
CKRT said:
Don't really know where to go from here. I cannot get out of the boot loop no matter what I try. I've flashed the boot.img through terminal, I've flashed it through Hasoon's AIOK and I still get stuck there.
I'm lost.
Click to expand...
Click to collapse
I think you're fine with just choosing the zip file. You don't need to flash the boot.img. I've never had to flash a boot.img, just the zip file.
Do a factory reset, the Rom zip, and then flash. Only do those steps and see what happens.
Sent from my HTC One using xda premium
ngIfy which
I went ahead and used fastboot oem lock and executed the stock RUU. I'm up and running again with the stock stuff.
I really want to get MIUI up and running. Can anyone tell me what I need to do assuming I'm coming from a stock phone?
I know I need to:
Unlock bootloader again (with a terminal command or do I do the htcdev thing again?)
Flash a new recovery
Transfer the ROM
Flash the ROM
Restart to bootloader
Flash boot.img
Restart and hopefully have a working boot this time
Do I need to be doing anything with S-Off? I know the HTC Dev unlock only partially S-Off's..is that causing my problem?
Edit: using htcdev to unlock my bootloader isn't working. I get this message:
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
Is this because I already unlocked the bootloader before? If so how do I unlock the bootloader after relocking it?
Edit 2: I am dumb. I just reused my unlock_code.bin.
About to try to reflash. Wish me luck!
You don't have to flash a boot.img
Sent from my HTC One using xda app-developers app
dcemtp1 said:
You don't have to flash a boot.img
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Everything says it was done successfully, but I'm still hanging on the boot logo for MIUI. Didn't flash a boot.img.
EDIT:
IT WORKS! I cleared my cache/data/davlik by using the regular wipe and it worked!
I did all of the steps that i read and watched on youtube for the all in one toolkit by Hasoon2000... At the bootloader screen it says
*** Tampered ***
*** Unlocked ***
it will not let me do a flash recover, which I was going to use TWRP (Sprint Only)
any help would be useful, i have searched for the answer but im very new at this.
Thank you in advance.
HTC ONE (SPRINT)
fastboot flash recovery nameofrecovery.img
Best not to use toolkits
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
fastboot flash recovery nameofrecovery.img
Best not to use toolkits
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i dont understand, could you please elaborate?
gsxronchrome said:
i dont understand, could you please elaborate?
Click to expand...
Click to collapse
When i go into recover the "teamwin" logo comes on, the it promps me to to a menu which seems as if it would work with touch screen... when it says install it will not allow enter any option its almost as if its frozen and the touch screen does not work.
After a lot of searching i think i figured out what it was you were trying to say to me. I did what you said using TWRP the picture shows what happened after i opened the cmd window and typed the command. TWRP freezes up when i go into recovery. Am i doing something wrong?
Replace nameofrecovery.img with the actual name of the file, more info here
http://forum.xda-developers.com/showthread.php?t=2277112
You may have the wrong twrp image installed to your phone, I can think of a good reason why it freezes on you. So when in recovery you can not press any option? If this is the case I would look for a new copy of twrp specific to your device, check md5sum, then flash it with fastboot
fastboot erase recovery
fastboot flash recovery placethenameofrecoveryhere.img
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
Replace nameofrecovery.img with the actual name of the file, more info here
http://forum.xda-developers.com/showthread.php?t=2277112
You may have the wrong twrp image installed to your phone, I can think of a good reason why it freezes on you. So when in recovery you can not press any option? If this is the case I would look for a new copy of twrp specific to your device, check md5sum, then flash it with fastboot
fastboot erase recovery
fastboot flash recovery placethenameofrecoveryhere.img
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes it gets stuck in recovery... i cannot use the touchscreen at all...
i downloaded the newest twrp copy... i downloaded md5sum and i have no idea how to use that even after looking it up and searching through youtube. i have the new ".img" file on hand... i just need to find out how to erase the old one in order to install the new one and see if it works
here is the CMD screen
this is what happens when i open "minimal adb and fastboot" and type in the commands you sent me... the top one that says failed, is when the phone is in the fastboot usb screen... when it says waiting for device... the phone is just turned on
Being you are s-on (can confirm if you write down all info on phone when in bootloader mode) you probably don't have permission to erase recovery but you should be able to just overwrite it, so just
fastboot flash recovery twrporwhatever.img
Also I believe there is a way to gain s-off with your phone, once you get all this down than I suggest doing that but first get the proper recovery
Oh and there are many ways to check md5sum (just Google for one if the one I linked you isn't working) this just makes sure you had a good download of a file, a good idea to do it but not need
Sent from my Nexus 4 using XDA Premium 4 mobile app
I flash the recovery with the fastboot command. When I go into the recovery is shows either the teamwin or cwm screen, whichever I flash, then loops back to the HTC screen. Help!
booked said:
I flash the recovery with the fastboot command. When I go into the recovery is shows either the teamwin or cwm screen, whichever I flash, then loops back to the HTC screen. Help!
Click to expand...
Click to collapse
Go into boot loader and erase cache
Put the phone into fastboot mode open a command window and type fastboot erase cache and then try to flash the recovery and it will boot into it.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Jaggar345 said:
Put the phone into fastboot mode open a command window and type fastboot erase cache and then try to flash the recovery and it will boot into it.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
^ is what I meant
EDIT: Noob to flashing stock images here. Need help on how to get the image to install on the device. This is my first ever Nexus device
So there's a new 5.0.1 system image out. I'm rooted, and I remember reading somewhere that the official OTA process won't work if you have modifications to the System partition.
So, I just want to check what I should do. Thanks.
Fastboot flash the images. Then reroot.
Awesome. I'm new to fastboot, and this is my first Nexus device. What is the procedure for flashing an official System image with fastboot?
TenderloinShadow said:
Awesome. I'm new to fastboot, and this is my first Nexus device. What is the procedure for flashing an official System image with fastboot?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=56921581&postcount=33
That post left out flashing recovery. The download should have 6 files. I flashed recovery at the end (but I don't think it matters how you flash the files, I could be wrong though).
See link above, then you might as well just flash twrp recovery instead of factory recovery, then flash this SuperSU zip through recovery and you'll be rooted and updated.
Order of flash doesn't matter, and I wouldn't flash boot loader unless necessary.
di11igaf said:
See link above, then you might as well just flash twrp recovery instead of factory recovery, then flash this SuperSU zip through recovery and you'll be rooted and updated.
Order of flash doesn't matter, and I wouldn't flash boot loader unless necessary.
Click to expand...
Click to collapse
I had TWRP installed before loading up these images. I decided to not flash recovery.img thinking I would be okay; but when I tried to reboot into twrp, I soft bricked. So I would still install the recovery.img first and then twrp. Everything is working properly now.
ericplatham said:
I had TWRP installed before loading up these images. I decided to not flash recovery.img thinking I would be okay; but when I tried to reboot into twrp, I soft bricked. So I would still install the recovery.img first and then twrp. Everything is working properly now.
Click to expand...
Click to collapse
You're right, now that I think about it, I believe I had to do that as well last time I flashed a factory image.
I am unlocked, rooted and have custom recovery.... what is the procedure? Is fastboot the only way?
GatorsUF said:
I am unlocked, rooted and have custom recovery.... what is the procedure? Is fastboot the only way?
Click to expand...
Click to collapse
maybe I'll write up a guide, but download the factory image, extract it. In there is a zip file, extract it too. Then Google 15 second adb install xda. That'll set up fastboot on your pc. Then boot into the bootloader and in a command window opened in the folder where the bootloader image is located run the commands:
fastboot flash bootloader bootloader.img. Note, use the full name of the bootloader.img
fastboot reboot-bootloader
fastboot -w
Open the folder where the boot, system, cache, system, and vendor images are located. Open a command window in that folder and run the commands:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash vendor vendor.img
fastboot flash system system.img
Then you're done
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Then you're done
Click to expand...
Click to collapse
He will still have to reroot and flash custom recovery... but you got 95% of the process :laugh:
So we have to go through this for updates rather than flashing a modified firmware, eh? damn
rank78 said:
So we have to go through this for updates rather than flashing a modified firmware, eh? damn
Click to expand...
Click to collapse
Since its a small update you could probably get by just flashing the system and boot images. But I haven't tried it
Sent from my Nexus 5 using XDA Free mobile app
I'd flash everything as described to be safe, I just prefer simply flashing a zip and moving on.
Will updating thru adb wipe my device?
GatorsUF said:
Will updating thru adb wipe my device?
Click to expand...
Click to collapse
You're using thru fastboot, not adb. They're different. But to answer your question the command fastboot -w does wipe your device. You could try it without that command but it may cause problems. Back your device up to Google first. Google had gotten really good at restoring the device after a flash.
You could also try just flashing the system and boot images, run those fastboot commands only and not the other ones. It should update to 5.0.1 without a problem.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You're using thru fastboot, not adb. They're different. But to answer your question the command fastboot -w does wipe your device. You could try it without that command but it may cause problems. Back your device up to Google first. Google had gotten really good at restoring the device after a flash.
You could also try just flashing the system and boot images, run those fastboot commands only and not the other ones. It should update to 5.0.1 without a problem.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks, I have actually flashed a few times thru fastboot in the past so I'm not totally lost on the idea. I've always used tibu in the past, will Google restore my data too?
TenderloinShadow said:
EDIT: Noob to flashing stock images here. Need help on how to get the image to install on the device. This is my first ever Nexus device
So there's a new 5.0.1 system image out. I'm rooted, and I remember reading somewhere that the official OTA process won't work if you have modifications to the System partition.
So, I just want to check what I should do. Thanks.
Click to expand...
Click to collapse
Drag and Drop or Copy/Paste Images to {}
STEP #1
fastboot flash bootloader {bootloader.img}
fastboot reboot-bootloader
Step #2
fastboot erase recovery
fastboot format system
fastboot erase boot
fastboot format vendor
fastboot format cache
fastboot erase userdata {optional}
Step#3
fastboot flash recovery {recovery.img}
fastboot flash system {system.img}
fastboot flash boot {boot.img}
fastboot flash vendor {vendor.img}
fastboot flash cache {cache.img}
fastboot reboot-bootloader
Step #4
fastboot erase recovery
fastboot flash recovery {TWRP.img}
Step #5
got to TWRP recovery flash latest super su
reboot done enjoy
thanks @prdog1
fhem said:
Drag and Drop or Copy/Paste Images to {}
STEP #1
fastboot flash bootloader {bootloader.img}
fastboot reboot-bootloader
Step #2
fastboot erase recovery
fastboot format system
fastboot erase boot
fastboot format vendor
fastboot format cache
fastboot erase userdata {optional}
Step#3
fastboot flash recovery {recovery.img}
fastboot flash system {system.img}
fastboot flash boot {boot.img}
fastboot flash vendor {vendor.img}
fastboot flash cache {cache.img}
fastboot reboot-bootloader
Step #4
fastboot erase recovery
fastboot flash recovery {TWRP.img}
Step #5
got to TWRP recovery flash latest super su
reboot done enjoy
thanks @prdog1
Click to expand...
Click to collapse
Why erase recovery twice?
Just dont flash stock recovery
fhem said:
STEP #1
fastboot flash bootloader {bootloader.img}
Click to expand...
Click to collapse
Help, I'm getting the folllowing error message: error: cannot determine image filename for bootloader-flounder-3.43.0.0114.img
and now I'm stuck. I've not done this in ages but couldn't wait and now I don't know what to do.
Double_U said:
Help, I'm getting the folllowing error message: error: cannot determine image filename for bootloader-flounder-3.43.0.0114.img
and now I'm stuck. I've not done this in ages but couldn't wait and now I don't know what to do.
Click to expand...
Click to collapse
Hi, Double_U...
Are you sure you've typed the EXACT command..?
Code:
fastboot flash bootloader bootloader-flounder-3.43.0.0114.img
Reboot the bootloader, enter fastboot, and try again.
Rgrds,
Ged.