I buddy of mine gave me this mytouch fender because he tried to root the phone and he's an idiot.
Now the phone is stuck at the "HTC Magic" splash screen and won't boot into android and won't boot into any kind of recover.
I can get into hboot though by holding down volume and power.
Where do I start? I have a Sprint Epic 4g that I rooted for my wife so I'm not a complete moron I just need a push in the right direction for this phone.
Start by post ALL fastboot info, ALL.
Plus the outcome of this command:
Code:
fastboot getvar version-main
I didn't want to get it wrong so I just took some pics
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Actually, I might be a little closer to a moron than you think.
(I just meant that I can follow directions easily enough to get through a guide or tutorial)
You are in a very good shape...
Download this combo i made for you:
EDIT new link: http://rapidshare.com/files/432674806/MagicFenderCombo.zip
Download my fastboot commander, magic version. (check my signature)
Download rom: http://cyanogenmod-mirror.local.host.name/desire/cm/stable/update-cm-6.0.2-Desire-signed.zip
Download gapps: http://cyanogenmod-mirror.local.host.name/gapps/gapps-mdpi-tiny-20101020-signed.zip
Guide:
1) boot into fastboot mode
2) Start my tool
3) using the first tab, load hboot, radio and recovery respectively.
4) Push "flash all"
5) If all good, go to misc tab and push "reboot device". If not, post here and do not reboot the device or shutdown the tool.
6)Your fastboot info should have changed now :0)
7) Reboot into recovery
8)choose usb-toggle
9)now you have your sdcard mounted in your OS. Move the rom and gapps to the root of the sdcard.
10)Unmount the sdcard
11)Flash the rom
12)Flash the gapps
13)Reboot and enjoy :0)
I assume you know how to use the custom recovery!!!!
Good luck.
everything looked good until it tried to flash recovery. I have my system running still and I haven't rebooted yet.
From your tool log window:
Feedback, criticism, ideas, improvments, thanks and appreciations are welcomed on the forum-thread.
............................................................
Operating system: Windows.
Tools folder and fastboot file(s) created.
The folder containing the IMG files was not found.
MagicFiles folder found.
hboot-1.33.2010.img found.
hboot-1.76.2007.img found.
radio_htc_pvt_32a_3.22.20.17.img found.
radio_htc_pvt_32a_6.35.16.19.img found.
recovery-ra-magic_6.35-v1.7.0.1.img found.
recovery-ra-sapphire-v1.7.0h.img found.
"Flash old" button enabled.
"Flash new" button enabled.
No Nandroid folder was not found - "Restore" button disabled.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
Radio version: 3.22.20.17.
SPL/hboot version: 1.33.2010.
product: sapphire.
mid: sapp31000.
security: off.
build-mode: eng.
-----------------------------------.
Print of device info SUCCESSFUL.
Hboot, radio & recovery files set - FlashAll button enabled.
STARTING FLASH OF CUSTOM FILES.
Flashing "radio" - PLEASE WAIT.
"radio" flash SUCCESSFUL.
Flashing "hboot" - PLEASE WAIT.
"hboot" flash SUCCESSFUL.
Flashing "recovery" - PLEASE WAIT.
"recovery" flash FAILURE.
FLASH OF CUSTOM FILES FAILURE - RECOVERY FAILURE.
I noticed on the phone that all the other progress bars fill up and disappear but when it gets to the purple progress bar and tries to flash recovery it just sits there without filling in any color at all.
Somebody else was telling me that I needed a "gold card" because this is a Fender T-Mobile phone?
Anyway, I still have the phone in the last state it was in when the recovery failed to flash and I haven't rebooted yet. Waiting to here what to do next.
Try to flash the recovery alone!!!
Also provide the info inside the "actual tab".
Do not reboot, do not shutdown the tool....
You do not need any goldcard... you have eng spl...
Don't worry... as long the hboot and radio was ok, you are in no harm :0)
Same result when I try to flash recovery alone.
"Actual output" tab:
###Calling fastboot with: getvar version-baseband###
version-baseband: 3.22.20.17
finished. total time: 0.000s
********************************
###Calling fastboot with: getvar version-bootloader###
version-bootloader: 1.33.2010
finished. total time: 0.000s
********************************
###Calling fastboot with: getvar product###
product: sapphire
finished. total time: 0.000s
********************************
###Calling fastboot with: getvar mid###
mid: SAPP31000
finished. total time: 0.000s
********************************
###Calling fastboot with: getvar security###
security: off
finished. total time: 0.000s
********************************
###Calling fastboot with: getvar build-mode###
build-mode: ENG
finished. total time: 0.000s
********************************
###Calling fastboot with: flash radio C:\Documents and Settings\jtb30262\Desktop\MagicFenderCombo\radio.img###
sending 'radio' (21504 KB)... OKAY [ 5.938s]
writing 'radio'... OKAY [ 37.688s]
finished. total time: 43.625s
********************************
###Calling fastboot with: flash hboot C:\Documents and Settings\jtb30262\Desktop\MagicFenderCombo\hboot_7201A_1.33.0013G_091021.nb0###
sending 'hboot' (512 KB)... OKAY [ 0.484s]
writing 'hboot'... OKAY [ 0.563s]
finished. total time: 1.047s
********************************
###Calling fastboot with: flash recovery C:\Documents and Settings\jtb30262\Desktop\MagicFenderCombo\recovery-RA-sapphire-v1.7.0G.img###
sending 'recovery' (4520 KB)... OKAY [ 1.719s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 33.531s
********************************
###Calling fastboot with: flash recovery C:\Documents and Settings\jtb30262\Desktop\MagicFenderCombo\recovery-RA-sapphire-v1.7.0G.img###
sending 'recovery' (4520 KB)... OKAY [ 1.719s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 33.531s
********************************
Ok... go misc tab. Select only the recovery in red square. Push "erase chosen partition". Now try to flash the recovery from the first tab again...
Remember to post the output from the "actual tab" here... i don't want the other info..
try to flash this instead:
http://rapidshare.com/files/387932920/recovery-RA-sapphire-v1.7.0G-cyan.img
It didn't work again after erasing recovery partition. Here's the output. I'm downloading that other file right now. You want me to flash that as recovery?
###Calling fastboot with: erase recovery###
erasing 'recovery'... OKAY [ 0.047s]
finished. total time: 0.047s
********************************
###Calling fastboot with: flash recovery C:\Documents and Settings\jtb30262\Desktop\MagicFenderCombo\recovery-RA-sapphire-v1.7.0G.img###
sending 'recovery' (4520 KB)... OKAY [ 1.704s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 33.522s
yes as recovery
also try this: http://www.androidspin.com/download...Y/&file=recovery-RA-sapphire-v1.6.2G-blue.img
tried cyan version and same result. The purple progress bar on the never starts to fill up.
###Calling fastboot with: flash recovery C:\Documents and Settings\jtb30262\Desktop\Fender\recovery-RA-sapphire-v1.7.0G-cyan.img###
sending 'recovery' (4528 KB)... OKAY [ 1.703s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 33.517s
********************************
mumilover said:
yes as recovery
also try this: http://www.androidspin.com/download...Y/&file=recovery-RA-sapphire-v1.6.2G-blue.img
Click to expand...
Click to collapse
same result:
###Calling fastboot with: flash recovery C:\Documents and Settings\jtb30262\Desktop\Fender\recovery-RA-sapphire-v1.6.2G-blue.img###
sending 'recovery' (4580 KB)... OKAY [ 1.703s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 33.517s
********************************
check your pm
Flash the eng spl again, the 1.33.2010... find it under magicfiles bundled with the tool.
If it goes well, then reboot into fastboot again... then try to flash the recovery... if it goes well, then flash the hboot that was meant to the fender (the one you downloaded to begin with) and, reboot if that want well to.
brotha its beastie here is your answer
You need to revert back to a HTBOOT that will accept the update. Here is your instructions.
http://forum.xda-developers.com/showthread.php?t=622530
... and here is some help for AFTER you have downgraded
you should be able to apply the directions the original gentlemen told you after you downgrade. in order to downgrade you MUST have a goldcard. If his solution does not work do not fear but follow this http://forum.xda-developers.com/showthread.php?t=623141 and THEN apply his fix. Let me know via text or not if this works ... and get your ass back to work you too brent!
beastiezee said:
you should be able to apply the directions the original gentlemen told you after you downgrade. in order to downgrade you MUST have a goldcard. If his solution does not work do not fear but follow this http://forum.xda-developers.com/showthread.php?t=623141 and THEN apply his fix. Let me know via text or not if this works ... and get your ass back to work you too brent!
Click to expand...
Click to collapse
Brent and work in the same sentence. That's an oxymoron isn't it?
Related
Hello, I would really appreciate some advice.
I had a Magic 32b which i rooted, flashed CM and passed on to my brother about an year ago. He now tried to flash another ROM and maybe bricked the phone.
He followed steps in [custom Radio/SPL for dummies][32B] http://forum.xda-developers.com/showthread.php?t=523680
He couldn't flash recovery mode because of an error ( signature verify fail) but he could load it via fastboot boot img and followed steps- 1-9 doing so. after superwipe and flashing radio he flashed Hboot and then couldn't get into recovery any more.
Now the phone has default recovery mode, and every time i try to flash an "update.zip" it gives me "signature verification failed".
Does not boot normally.
In fastboot cannot flash any recovery "signature verification failed" and when i try to load a recovery by fastboot boot recovery, it downloads it and then gets stuck at booting.
HBOOT-1.33.0013d
RADIO- 2.22.27.08
Any advice would be great.
Thanks in advance
hope this helps, seen it on other threads:
fastboot getvar version-main 1.75.162.3_R
fastboot getvar cid VODAP102
I know that i should make a goldcard to solve the problem, but if the phone only boots in recovery and fastboot, ADB commands do not work. Only fastboot commands work, so how can I make a goldcard?
The fix:
Download this file: https://rapidshare.com/files/1368708004/1.89.162.1.nbh
Download my fastboot commander tool found in my signature (not the magic version)
Using the tool, flash the file using the "Full zip" tab and do so inside fastboot mode.
It can take some time to finish....
Once done you should be back to stock 1.89.162.1 Vodafone Germany CRC24
From there, follow my root guide which is found in my signature...
Good luck
Thanks a lot for your response, I tried flashing the ZIP but failed
The weird thing is that it appears at S-ON, but i'm pretty sure that i had S-OFF an year ago when I flashed CM ROM, a new kernel and recovery on it ( otherwise it wouldn't have worked).
Is it possible to change the SPL from a good one to a perfected one with security? (at least that's what I think my brother did)
###Calling fastboot with: getvar version-baseband###
version-baseband: 2.22.27.08
finished. total time: 0.008s
********************************
###Calling fastboot with: getvar version-bootloader###
version-bootloader: 1.33.0013d
finished. total time: 0.002s
********************************
###Calling fastboot with: getvar product###
product: sapphire
finished. total time: 0.006s
********************************
###Calling fastboot with: getvar mid###
mid: SAPP10000
finished. total time: 0.001s
********************************
###Calling fastboot with: getvar security###
security: on
finished. total time: 0.002s
********************************
###Calling fastboot with: getvar build-mode###
build-mode: SHIP
finished. total time: 0.003s
********************************
###Calling fastboot with: flash zip
sending 'zip' (97795 KB)... OKAY [ 20.744s]
writing 'zip'... INFOsignature checking...
FAILED (remote: signature verify fail)
I have a nandroid Backup made, but i can't restore it
I'm open to any other suggestions.
and thanks again for at least giving mea little hope .
Try to put the nbh file in same directory as fastboot.exe then issue this command
Code:
fastboot flash nbh 1.89.162.1.nbh
Succeeded
I followed the last instructions and managed to setup the ROM.
after rooting and installing new radio , SPL and new ROM i'm now running Ginger Yoshi 1.2 and gave the phone back to my brother. Hope that i won't have to deal with it again and just stick to my SGS.
Thanks a lot for your support and applications.
I tried to donate, but I got some errors( I tried three times) and couldn't finish the transaction. I think that my bank does not see pay-pal as a trusted site and rejects the transaction.
No problem... glad it worked out for you.
You actually just helped me find a bug in the tool (the first one).
"Full rom" tab should automatically change the fastboot command depending on the rom type. In your case, it was nbh and not zip... this is gona be fixed :0)
Hi all,
I was trying to unroot my phone by simply loading the sappimg.zip which would have worked but it was for the vodafone version. Now my phone boots with the vodafone logo and stays there. I have access to hboot and fastboot, no recovery.
Sapphire Unknown 32A Ship S-ON H
Hboot-1.33.0009
CPLD-13
Radio-3.22.20.17
May 8 2009, 21:02:32
also it only loads the vodafone sappimg, others say "main version is older"
Download my fastboot commander from my signature and post here all device info.
###Calling fastboot with: getvar version-bootloader###
version-bootloader: 1.33.0009
finished. total time: -0.000s
********************************
###Calling fastboot with: getvar version-baseband###
version-baseband: 3.22.20.17
finished. total time: 0.000s
********************************
###Calling fastboot with: getvar version-main###
version-main: 2.16.151.1
finished. total time: 0.000s
********************************
###Calling fastboot with: getvar cid###
cid: T-MOB010�Ò˜"
finished. total time: -0.000s
********************************
###Calling fastboot with: getvar version-cpld###
version-cpld: 13
finished. total time: 0.010s
********************************
###Calling fastboot with: getvar product###
product: sapphire
finished. total time: -0.000s
********************************
###Calling fastboot with: getvar mid###
mid: SAPP31000
finished. total time: 0.000s
********************************
###Calling fastboot with: getvar security###
security: on
finished. total time: -0.000s
********************************
###Calling fastboot with: getvar build-mode###
build-mode: SHIP
finished. total time: 0.010s
********************************
###Calling fastboot with: flash radio C:\android-sdk-windows-1.5_r3\tools\radio.img###
sending 'radio' (21504 KB)... OKAY [ 6.915s]
writing 'radio'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 13.629s
********************************
Follow this guide and you should be ok: http://forum.xda-developers.com/showthread.php?t=734617
whenever I put that sappimg.zip on my phone it freezes at the unzipping. What do I do?
Ok I finally figured out how to fix it
On the red Vodafone screen, its waiting for you to input commands, put in these commands:
fastboot erase boot
fastboot erase system -w
fastboot erase recovery
now when you try to apply the 60.7mb sappimg.zip, it will work
next flash the special sappimg.zip on most root tutorial's
Then you work your way from there....
Thanks for your help though, much appreciated
I have a similar issue but my mt3g say remote partition is not existed when i bootfast erasing system-w. how do I correct it?
I am trying to flash my Nexus 7 entirely back to stock 4.3. I was following the guide that is sticky'd in this thread to flash the Google image. This is these are the errors I get:
Code:
C:\android-sdk\platform-tools>fastboot erase boot
erasing 'boot'...
OKAY [ 2.532s]
finished. total time: 2.535s
C:\android-sdk\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 0.032s]
finished. total time: 0.033s
C:\android-sdk\platform-tools>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.021s]
finished. total time: 0.022s
C:\android-sdk\platform-tools>fastboot erase system
erasing 'system'...
OKAY [ 0.021s]
finished. total time: 0.022s
C:\android-sdk\platform-tools>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.021s]
finished. total time: 0.022s
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-grouper-4.23.
img
sending 'bootloader' (2100 KB)...
OKAY [ 0.266s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 0.415s
Also the bootloader keeps freezing on me after I attempt this. I also am unable to restart bootloader by command or the selection, it just goes to a black screen and "fastboot devices" gives me ????????????? instead of my device ID. I can fix this by turning it off and booting back into the bootloader and it will properly display my device ID.
It is unlocked and on 4.23 that's listed there. What else can I do?
engagedtosmile - You should post this question in comminus' stickied thread. I read all 54 pages of it and he's very good at diagnosing the problem and helping to get it resolved.
engagedtosmile said:
I am trying to flash my Nexus 7 entirely back to stock 4.3. I was following the guide that is sticky'd in this thread to flash the Google image. This is these are the errors I get:
Code:
C:\android-sdk\platform-tools>fastboot erase boot
erasing 'boot'...
OKAY [ 2.532s]
finished. total time: 2.535s
C:\android-sdk\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 0.032s]
finished. total time: 0.033s
C:\android-sdk\platform-tools>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.021s]
finished. total time: 0.022s
C:\android-sdk\platform-tools>fastboot erase system
erasing 'system'...
OKAY [ 0.021s]
finished. total time: 0.022s
C:\android-sdk\platform-tools>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.021s]
finished. total time: 0.022s
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-grouper-4.23.
img
sending 'bootloader' (2100 KB)...
OKAY [ 0.266s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 0.415s
Also the bootloader keeps freezing on me after I attempt this. I also am unable to restart bootloader by command or the selection, it just goes to a black screen and "fastboot devices" gives me ????????????? instead of my device ID. I can fix this by turning it off and booting back into the bootloader and it will properly display my device ID.
It is unlocked and on 4.23 that's listed there. What else can I do?
Click to expand...
Click to collapse
Hi, engagedtosmile...
Yeah.. there is a known issue with the v4.23 bootloader.
Your problem could be the bootloader v4.23 from build JWR66Y.... try flashing the bootloader v4.23 from build JWR66V.
See this thread for details (a couple of people have uploaded the bootloader v4.23 from build JWR66V, for both 'grouper' and 'tilapia' Nexus 7's on this thread - when I find the time, I'm going to upload them myself... so I don't have to keep hunting out the link).
Hope this helps.
Rgrds,
Ged.
GedBlake said:
Hi, engagedtosmile...
Yeah.. there is a known issue with the v4.23 bootloader.
Your problem could be the bootloader v4.23 from build JWR66Y.... try flashing the bootloader v4.23 from build JWR66V.
See this thread for details (a couple of people have uploaded the bootloader v4.23 from build JWR66V, for both 'grouper' and 'tilapia' Nexus 7's on this thread - when I find the time, I'm going to upload them myself... so I don't have to keep hunting out the link).
Hope this helps.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thanks but I have done that as instructed in the sticky post (I ran into the error before but was able to flash it fine). I thought I would try to Lock the bootloader and unlock it again, it locked fine but now errors out when unlocking.
I am back to step 1 it seems.:crying:
engagedtosmile said:
Thanks but I have done that as instructed in the sticky post (I ran into the error before but was able to flash it fine). I thought I would try to Lock the bootloader and unlock it again, it locked fine but now errors out when unlocking.
I am back to step 1 it seems.:crying:
Click to expand...
Click to collapse
Have you tried changing to a different USB port on your PC... or a different USB cable, or even a different PC.
I know I've had difficulties, when trying to send/write to 'system', and changing to a different USB port usually resolves the problem... so it might be worth a shot.
Gotta be really careful when flashing bootloaders, as one false move can cause hardbrick, which is pretty grim.
Rgrds,
Ged.
GedBlake said:
Have you tried changing to a different USB port on your PC... or a different USB cable, or even a different PC.
I know I've had difficulties, when trying to send/write to 'system', and changing to a different USB port usually resolves the problem... so it might be worth a shot.
Gotta be really careful when flashing bootloaders, as one false move can cause hardbrick, which is pretty grim.
Rgrds,
Ged.
Click to expand...
Click to collapse
I will have to try it on my home PC later. I have tried different cables and ports on my work PC to no avail. It just won't unlock at all now.
My N7 "2012" kept freezing, so I put it in bootloader and tried to do a recovery mode reset to stock. It froze during the process.
Now, the only thing I can do is get it into bootloader mode manually by holding the buttons. It frezes if I choose any of the options from the bootloader screen including restarting the bootloader from the bootloader screen without holding power and volume.
I have tried the Nexus Root Toolkit a bunch of times with the "flash stock + unroot (soft bricked)" feature, testing different factory builds and the best results are below:
Flash Stock + Unroot...
------------------------------------------------------------------
erasing 'boot'...
OKAY [ 2.526s]
finished. total time: 2.526s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.200s]
finished. total time: 0.200s
erasing 'recovery'...
OKAY [ 0.016s]
finished. total time: 0.016s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.015s]
finished. total time: 0.015s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.015s]
finished. total time: 0.015s
sending 'bootloader' (2100 KB)...
OKAY [ 0.264s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 0.402s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.021s
< waiting for device >
PLEASE HELP! Keep in mind that I am a newb to messing with this stuff.
I have read forums and tried things that people suggested to others in similar situations, but I am pretty lost at this point. Keep in mind that my device is almost certainly wiped and definitely will not boot the OS.
Is your N7 the Wi-Fi or the 3G variant?
What was the name of the factory image you were trying to flash?
brad3626 said:
My N7 "2012" kept freezing, so I put it in bootloader and tried to do a recovery mode reset to stock. It froze during the process.
Now, the only thing I can do is get it into bootloader mode manually by holding the buttons. It frezes if I choose any of the options from the bootloader screen including restarting the bootloader from the bootloader screen without holding power and volume.
I have tried the Nexus Root Toolkit a bunch of times with the "flash stock + unroot (soft bricked)" feature, testing different factory builds and the best results are below:
PLEASE HELP! Keep in mind that I am a newb to messing with this stuff.
I have read forums and tried things that people suggested to others in similar situations, but I am pretty lost at this point. Keep in mind that my device is almost certainly wiped and definitely will not boot the OS.
Click to expand...
Click to collapse
After doing a bit of research, I've found out that there is a BAD version of the N7 2012 bootloader 4.23 floating around. The unsettling thing is that it's being supplied with a couple of the factory images that come straight from from the Google android devolpers page online. Anyway to make a long story short, I would try flashing the working version of the bootloader first off, then go from there with a factory reset. You can download the the working bootloader (bootloader-grouper-4.23.img) HERE --> h t t p : / / g o o . g l / q A D S A z (sorry about the spaces in the url, I'm new to the forum and can't post links yet, just delete the spaces)
BTW, its the same bootloader for N7 wifi OR 3G. md5 = df53028033c9eccf4fe5ba7bc198ce24
Here's how to install using fastboot:
1. Reboot To Your Bootloader On You Nexus 7 (Power off power button and volume down until you see bootloader screen)
2. Connect Your Nexus 7 To Your Computer
3. Open Up Command Prompt or terminal window (not sure if you are using windows/mac/linux)
4. CD to where you downloaded bootloader-grouper-4.23.img
5. Then type:
fastboot devices (to see if your N7 is connected correctly)
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
Then try the factory reset again.
If you don't have fastboot installed your computer you need it. Makes flashing your N7 a breeze... lock/unlock, custom recovery installs, going back to factory stock, all much more easy with fastboot.
You can get it from the android devolper site, h t t p : / / g o o . g l / 2 q p r for windows/mac/linux. All you need is the SDK tools, not the ADT bundle.
adomol said:
After doing a bit of research, I've found out that there is a BAD version of the N7 2012 bootloader 4.23 floating around. The unsettling thing is that it's being supplied with a couple of the factory images that come straight from from the Google android devolpers page online. Anyway to make a long story short, I would try flashing the working version of the bootloader first off, then go from there with a factory reset. You can download the the working bootloader (bootloader-grouper-4.23.img) HERE --> h t t p : / / g o o . g l / q A D S A z (sorry about the spaces in the url, I'm new to the forum and can't post links yet, just delete the spaces)
BTW, its the same bootloader for N7 wifi OR 3G. md5 = df53028033c9eccf4fe5ba7bc198ce24
Here's how to install using fastboot:
1. Reboot To Your Bootloader On You Nexus 7 (Power off power button and volume down until you see bootloader screen)
2. Connect Your Nexus 7 To Your Computer
3. Open Up Command Prompt or terminal window (not sure if you are using windows/mac/linux)
4. CD to where you downloaded bootloader-grouper-4.23.img
5. Then type:
fastboot devices (to see if your N7 is connected correctly)
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
Then try the factory reset again.
If you don't have fastboot installed your computer you need it. Makes flashing your N7 a breeze... lock/unlock, custom recovery installs, going back to factory stock, all much more easy with fastboot.
You can get it from the android devolper site, h t t p : / / g o o . g l / 2 q p r for windows/mac/linux. All you need is the SDK tools, not the ADT bundle.
Click to expand...
Click to collapse
Thank you for the help, unfortunately, it did not work.
I followed the instructions above, but the Nexus displayed "neither up nor cac partitions found" over and over
While cmd displayed:
C:\Users\Brad>fastboot devices
XXX fastboot
C:\Users\Brad>fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.281s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 3.213s
C:\Users\Brad>fastboot devices
XXX fastboot
C:\Users\Brad>fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.271s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 3.205s
Erovia said:
Is your N7 the Wi-Fi or the 3G variant?
What was the name of the factory image you were trying to flash?
Click to expand...
Click to collapse
Wi-Fi
I have tried every one that the NRT offered.
Just read this guide and download the latest factory image from here.
Good luck.
Erovia said:
Just read this guide and download the latest factory image from here.
Good luck.
Click to expand...
Click to collapse
I read that guide.
But that guide seems to be written with the assumption that the device can boot into the OS
No ADB device is found because I can only boot into bootloader.
That part is only for the driver installation. You can skip to the "Extract the Factory Image" part and follow it from there.
Erovia said:
That part is only for the driver installation. You can skip to the "Extract the Factory Image" part and follow it from there.
Click to expand...
Click to collapse
Following from "Extract the Factory Image" part, this is what I am getting:
C:\Users\Brad>cd \Users\brad\AppData\Local\Android\android-sdk\platform-tools
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot devices
XXX fastboot
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>adb reboot-bootlo
ader
error: device not found
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot oem unlo
ck
...
FAILED (command write failed (Unknown error))
finished. total time: 0.590s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase bo
ot
erasing 'boot'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase ca
che
erasing 'cache'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase re
covery
erasing 'recovery'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.022s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase sy
stem
erasing 'system'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase us
erdata
erasing 'userdata'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.018s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot flash bo
otloader bootloader-grouper-4.23.img
error: cannot load 'bootloader-grouper-4.23.img': Invalid argument
On the bootloader screen is your bootloader shown as "locked" or "unlocked" ?
Erovia said:
On the bootloader screen is your bootloader shown as "locked" or "unlocked" ?
Click to expand...
Click to collapse
lock state - unlocked
What's the output of fastboot -w update image-nakasi-kot49h.zip ?
Erovia said:
What's the output of fastboot -w update image-nakasi-kot49h.zip ?
Click to expand...
Click to collapse
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot -w updat
e image-nakasi-kot49h.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
error: out of memory
I have no idea what this "out of memory" error is. If I were you I would restart my computer, run fastboot from a cmd opened as Admin and try out different usb ports.
Erovia said:
I have no idea what this "out of memory" error is. If I were you I would restart my computer, run fastboot from a cmd opened as Admin and try out different usb ports.
Click to expand...
Click to collapse
I restarted, ran cmd as admin and tried every USB port and got this as the result each time:
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot -w updat
e image-nakasi-kot49h.zip
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: XXX
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.016s]
sending 'boot' (4992 KB)...
OKAY [ 5.460s]
writing 'boot'...
FAILED (remote: (FileWriteFailed))
finished. total time: 8.518s
The Nexus was frozen at this point and had to be manually forced to restart bootloader.
Do you have a valid warranty for the N7? I'm asking because it seems that your N7's internal memory got corrupted. I might not be right, but that's my best guess.
Erovia said:
Do you have a valid warranty for the N7? I'm asking because it seems that your N7's internal memory got corrupted. I might not be right, but that's my best guess.
Click to expand...
Click to collapse
Thanks for your help
I bought it 13 months ago (perfect timing, coincidentally, right?), so if I could find the receipt I would still be screwed.
I would still try to send it to Asus or Google. Maybe they repair it for a reasonable price.
(But if you plan to do that try to relock you bootloader with fastboot oem lock)
Erovia said:
I would still try to send it to Asus or Google. Maybe they repair it for a reasonable price.
(But if you plan to do that try to relock you bootloader with fastboot oem lock)
Click to expand...
Click to collapse
fastboot oem lock
...
(bootloader) Bootloader is locked now.
OKAY [ 36.032s]
finished. total time: 36.032s
But then the N7 freezes and after manually restarting in bootloader it is still unlocked.
Then send is as it is. You can't do any more about it.
Good luck.
Hello guys,
I know this question is very common but I have looked many posts and couldn't find any that solved my problem.
I am trying to flash the stock moto X pure edition (xt1575) again in my device. The trouble starts because fastboot doesn't work.
I already installed Motorola device manager (2.5.4) and booted windows without driver signature enforcement.
I tried adb-setup-1.4.3.exe and installing android SDK, but still get same trouble.
The phone works and get normally funcional when android is loaded, but no responde in fastboot screen!
I am using windows 10.15063.296 (creators update). When I open device manager, now I see "Motorola adb device" with an exclamation.
A lot of windows, especially windows 10, users seem to struggle with drivers. I use Linux and never have any problems.
Maybe you could give this a try. https://www.xda-developers.com/forget-windows-use-linux-is-a-usb-bootable-distro-for-your-android-recovery-needs-xda-spotlight/
jason2678 said:
A lot of windows, especially windows 10, users seem to struggle with drivers. I use Linux and never have any problems.
Maybe you could give this a try. https://www.xda-developers.com/forg...or-your-android-recovery-needs-xda-spotlight/
Click to expand...
Click to collapse
Thanks. After hours trying, I could get fastboot working.
The issue now is that I got "preflash failed" when trying the officially image available.
Enviado de meu XT1575 usando Tapatalk
Belotto said:
Thanks. After hours trying, I could get fastboot working.
The issue now is that I got "preflash failed" when trying the officially image available.
Enviado de meu XT1575 usando Tapatalk
Click to expand...
Click to collapse
Just on bootloader and gpt.bin, or everything?
That happens when you try to downgrade the partition table, but usually as long as you flash all the other parts successfully it works. Keep a close eye on the output when you flash modem; it tends to fail on the first try.
https://forum.xda-developers.com/showthread.php?t=2588979
This is the one... I had this on my window's 10. I upgraded to creators update and i doubted that this might not work but it did work for me
jason2678 said:
Just on bootloader and gpt.bin, or everything?
That happens when you try to downgrade the partition table, but usually as long as you flash all the other parts successfully it works. Keep a close eye on the output when you flash modem; it tends to fail on the first try.
Click to expand...
Click to collapse
I really wasn´t successful...
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> adb reboot-bootloader
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.370s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash motoboot motoboot.img
error: cannot load 'motoboot.img'
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (3687 KB)...
OKAY [ 0.137s]
writing 'logo'...
OKAY [ 0.200s]
finished. total time: 0.337s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (40960 KB)...
OKAY [ 1.518s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.888s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (41040 KB)...
OKAY [ 1.534s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.887s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash system system.img
target reported max download size of 536870912 bytes
sending sparse 'system' (509631 KB)...
OKAY [ 17.857s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 18.357s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot reboot
rebooting...
finished. total time: 0.016s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot erase userdata
erasing 'userdata'...
OKAY [ 6.423s]
finished. total time: 6.423s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot erase cache
erasing 'cache'...
OKAY [ 0.031s]
finished. total time: 0.031s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot oem lock
...
(bootloader) Please run fastboot oem lock begin first!
OKAY [ 0.015s]
finished. total time: 0.015s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot oem lock begin
...
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.017s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot oem lock
...
(bootloader) Please run fastboot oem lock begin first!
OKAY [ 0.000s]
finished. total time: 0.000s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US>
jason2678 said:
Just on bootloader and gpt.bin, or everything?
That happens when you try to downgrade the partition table, but usually as long as you flash all the other parts successfully it works. Keep a close eye on the output when you flash modem; it tends to fail on the first try.
Click to expand...
Click to collapse
Sagar_1401 said:
https://forum.xda-developers.com/showthread.php?t=2588979
This is the one... I had this on my window's 10. I upgraded to creators update and i doubted that this might not work but it did work for me
Click to expand...
Click to collapse
I have tried it before... wasn't working but i realized that i needed to push "allow oem unlock" and "usb debugging" buttons ... LOL.