Hello there!
I have a Nexus 7 Device, I rooted it using a toolkit, everything was working great, then I messed up a little and I need to restore it using a Factory Image (a.k.a Stock ROM)...
The problem is, when I try to flash the .zip, it gives me the following error:
{
"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"
}
According to some tutorials, you type the following commands to flash a ROM:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot -w update ROM.zip
Click to expand...
Click to collapse
Because I'm afraid of something going wrong, I didn't erased any partition, so if for some reason the flashing procedure stops, I have the old data/partitions working because I didn't erased any, I just used the following command:
fastboot -w update ROM.zip
Click to expand...
Click to collapse
So, the questions are:
Do I need to erase the partitions first before trying to flash the Stock ROM?
Should I try flash each .img separately?
Additional Information:
Android is working, I'm able to boot with success.
Bootloader unlocked.
I didn't flashed any custom Bootloader/Recovery/ROM, everything is from Factory/Stock.
I have tested flashing the ROM under Windows and Linux (Ubuntu), it gives me the exact error.
The .zip I'm using isn't corrupted. (And it's directly from developers.google.com)
If flashing without erasing the partitions worked, I would erase them (To delete ALL data/trash) and flash it again...
P.S: First post!
I'm pretty sure the script erases those anyway... You could open it up and check though. Don't worry about the .sig files; that's normal. Check inside the .zip to make sure the system.img is actually in there. If it is, then extract it and try flashing it by itself.
In fact, if you just were trying to fix something you messed up, all you need is the system image anyway.
Sent from my Nexus 7 using Tapatalk HD
korockinout13 said:
I'm pretty sure the script erases those anyway... You could open it up and check though. Don't worry about the .sig files; that's normal. Check inside the .zip to make sure the system.img is actually in there. If it is, then extract it and try flashing it by itself.
In fact, if you just were trying to fix something you messed up, all you need is the system image anyway.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Hello!
Thanks for the answer, I tried to flash system.img and it worked, fastboot automatically erases the system partition.
I have now a clean system, thanks!
For other people with the same problem as me:
1 - Enter Fastboot Mode
2 - Extract system.img
3 - Run "fastboot flash system system.img"
4 - Enter Recovery Mode and do a "Factory Reset" (Optional, I guess)
5 - Enjoy!
Spenzert said:
fastboot automatically erases the system partition.
Click to expand...
Click to collapse
I wouldn't jump to that conclusion quite so readily.
It merely overwrote whatever contents were already there.
More or less the same result though, excepting some possibly inconsequential trash in the partition slack space.
cheers
bftb0 said:
I wouldn't jump to that conclusion quite so readily.
It merely overwrote whatever contents were already there.
More or less the same result though, excepting some possibly inconsequential trash in the partition slack space.
cheers
Click to expand...
Click to collapse
I believe fastboot really erased the partition, there's no "SuperSU" anymore and I have attached a screenshot of fastboot erasing the partition.
Cheers!
I wouldn't have believed it until I saw the picture... and now I believe! My bad!
I could swear I've done the same thing on other devices for a couple years now without the implicit erase happening. I wonder if it is a fastboot version difference.
If you don't mind me asking, what version of fastboot is that?
bftb0 said:
I wouldn't have believed it until I saw the picture... and now I believe! My bad!
I could swear I've done the same thing on other devices for a couple years now without the implicit erase happening. I wonder if it is a fastboot version difference.
If you don't mind me asking, what version of fastboot is that?
Click to expand...
Click to collapse
Android SDK Manager says "Rev. 16.0.1" (Platform-tools), maybe fastboot erased the partition first because I used "fastboot flash" instead of "fastboot update"...
A little off-topic:
I tried to root manually my Nexus and it's really easy, I might make an updated tutorial soon on how to root it manually
Have a good day!
Edit: I tried to flash TWRP (Recovery) and it didn't erased the partition first.
Related
Hello,
Sorry but I have ran into a pretty big problem and I was an idiot and did not make a NAN backup.
I am capable of going to the bootloader and I can flash recovery but I can't do much else as far as updating the bootloader from 4.18 to 4.23 (not a huge issue at least right now) but the bigger issue is that I cannot flash system.img as it will just timeout on "sending system" through fastboot. Sending myself a custom rom through ADB and attempting to flash recovery does not work either due to system partition errors. erased and retried to send system and no luck, continues to time out. I believe this might be due to my previous custom rom perhaps resizing the system partition too small? But shouldn't this be solved when erasing/using flash-all.bat??
Please not sure what to do at this point. I've been using the Nexus Root Toolkit trying to flash 4.2.2, as I don't have the bootloader for 4.3 on my device (can't update it anyhow.. again that's a problem but I should be able to at least flash 4.2.2 for right now?) and doing it manually with fastboot and ADB but I am have no luck getting system to write/finish sending.
Any recommendations would be greatly appreciated!!
You can boot into recovery (boot/stock ) directly from botloader via fastboot. Hard to say if it is usefull to you.
Unfortunately not. I can get to recovery and flash custom recoveries with no problem, it is sending the system.img and getting it to write the problem.
Is a picture of the problem, just times out when sending the system.img even if I leave it on for 1 hr.
{
"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"
}
The same happens at sending the bootloader you see but I disconnect and reconnect quick to make sure it gets past this (I have the 4.18 bootloader already loaded, and I cannot update this but this seems like a second issue compared to sending the system.img). Doing it manually through fastboot and flash-all.bat doesn't help, still times out. Sending myself a rom to flash through recovery doesn't work as I have system and cache partition issues that won't let it install.
Not sure what to do at this point other than keep trying and maybe I'll get luck?
xdaNoobTutorial said:
Unfortunately not. I can get to recovery and flash custom recoveries with no problem, it is sending the system.img and getting it to write the problem.
Is a picture of the problem, just times out when sending the system.img even if I leave it on for 1 hr.
The same happens at sending the bootloader you see but I disconnect and reconnect quick to make sure it gets past this (I have the 4.18 bootloader already loaded, and I cannot update this but this seems like a second issue compared to sending the system.img). Doing it manually through fastboot and flash-all.bat doesn't help, still times out. Sending myself a rom to flash through recovery doesn't work as I have system and cache partition issues that won't let it install.
Not sure what to do at this point other than keep trying and maybe I'll get luck?
Click to expand...
Click to collapse
Just to update ** I am using Windows 8 and think this might potentially be just a driver problem. Not sure exactly why, since I can easily write recovery and boot images... but this is the only thing I can think of preventing the bootloader and system to write/send?
*** UUPDATE********
Soooo Sucesss!
Was the mother front-dooring USB port the entire time. Tried it on another laptop /w Windows 7 and had issues, went back to my Winodws 8 and plugged it into my OTHER usb port (oddly enough, the USB 3.0 port) and SUCESS!!! Flashed the bootloader again (probably didn't need to but I wanted to for spite), flash recovery, flashed boot.img, flashed system.img, and started and now I am back at stock firmware ready to go play the dangerious game of custom roms again, since I never learn from my misfortunes.
Also oddly enough my data partition was taking up EVERYTHING too, so this might have added to the issues. Why it took up the entire free space on the internal sd I do not know, likely just a bunch of 0's for some reason or another. So formatting that through TWRP might have also helped.
For others who might run into this problem:
First of all wipe everything via fastboot or TWRP (i prefer fastboot in case)
fastboot erase system
fastboot erase data
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
then re-flash from the stock firmware from google (extract the .img files from the .zip on the tarball) and flash through flashboot
fastboot flash system system.img (or a custom ROM img if you'd like)
fastboot flash recovery recovery.img (or a custom recovery img if you'd like)
fastboot flash boot boot.img (or a custom boot img if you like)
MOST IMPORTANTLY IF YOU'RE NOT ABLE TO FLASH MAKE SURE YOU TRY OTHER USB PORTS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
HTH to anyone in the future
xdaNoobTutorial said:
*** UUPDATE********
Soooo Sucesss!
Was the mother front-dooring USB port the entire time. Tried it on another laptop /w Windows 7 and had issues, went back to my Winodws 8 and plugged it into my OTHER usb port (oddly enough, the USB 3.0 port) and SUCESS!!! Flashed the bootloader again (probably didn't need to but I wanted to for spite), flash recovery, flashed boot.img, flashed system.img, and started and now I am back at stock firmware ready to go play the dangerious game of custom roms again, since I never learn from my misfortunes.
Also oddly enough my data partition was taking up EVERYTHING too, so this might have added to the issues. Why it took up the entire free space on the internal sd I do not know, likely just a bunch of 0's for some reason or another. So formatting that through TWRP might have also helped.
For others who might run into this problem:
First of all wipe everything via fastboot or TWRP (i prefer fastboot in case)
fastboot erase system
fastboot erase data
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
then re-flash from the stock firmware from google (extract the .img files from the .zip on the tarball) and flash through flashboot
fastboot flash system system.img (or a custom ROM img if you'd like)
fastboot flash recovery recovery.img (or a custom recovery img if you'd like)
fastboot flash boot boot.img (or a custom boot img if you like)
MOST IMPORTANTLY IF YOU'RE NOT ABLE TO FLASH MAKE SURE YOU TRY OTHER USB PORTS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
HTH to anyone in the future
Click to expand...
Click to collapse
You just saved my ass! i was experiencing this exact problem! i could not for the life of me figure out why my shield tablet was flipping out when i tried to flash the system image! read this post, switched USB ports, and BOOM!
thanks dude!
Not sure what happened here with this freaking thing. I followed the instructions located here. I grabbed both the 4.4.2 and the 4.4.4 located here.
I applied 4.4.2 to go back to stock and the tablet didn't make it past the Nexus boot logo. So, I rebooted into the bootloader and then flashed 4.4.4 thinking there was an issue.
Same result. Still no boot.
Any ideas? Of course I didn't back squat up because I did this same exact thing on my Nexus5 and it worked flawlessly. So, I figured, why back up anything because it will work the same on this tablet.
No clue what the %&@(&% happened.
I also can't get into Recovery mode either.
usafle said:
Not sure what happened here with this freaking thing. I followed the instructions located here. I grabbed both the 4.4.2 and the 4.4.4 located here.
I applied 4.4.2 to go back to stock and the tablet didn't make it past the Nexus boot logo. So, I rebooted into the bootloader and then flashed 4.4.4 thinking there was an issue.
Same result. Still no boot.
Any ideas? Of course I didn't back squat up because I did this same exact thing on my Nexus5 and it worked flawlessly. So, I figured, why back up anything because it will work the same on this tablet.
No clue what the %&@(&% happened.
I also can't get into Recovery mode either.
Click to expand...
Click to collapse
How did you flash these update with fastboot?
Yup. Copied all the files in the factory images to "platform-tools". Opened a CMD prompt window and then typed "Flash-all"
lj50036 said:
How did you flash these update with fastboot?
Click to expand...
Click to collapse
Going to re-download the 4.4.2 and re-flash it.... see what happens. But so far, no joy on anything at the moment. Just stuck in a bootloop.
usafle said:
Yup. Copied all the files in the factory images to "platform-tools". Opened a CMD prompt window and then typed "Flash-all"
Click to expand...
Click to collapse
If using windows is the file called flash-all.bat ?
make sure if you are using windows that your CMD window is opened as Admin....
Can you do this again and post the input and output of the process here ?
Thx Josh
Yes Sir, I am.
I've done this:
Proceed with this step if you want to keep your data intact. If you skip this step, your data will be wiped. With your favorite text editor, edit (be careful not to run it by accident instead of editing) flash-all.bat (if you're on Windows) or flash-all.sh (Mac, Linux) and remove "-w" from the fastboot update command. For example, if the line reads fastboot -w update image-razor-jss15j.zip, it should now read fastboot update image-razor-jss15j.zip. The -w option instructs fastboot to wipe data.Which worked flawlessly on my N5 "upgrade".
I am an Admin user on this machine so the CMD prompt is Admin.
There are no errors either in the CMD prompt window or, the Tablet. Everything appears to transfer over without any issues / errors.
lj50036 said:
If using windows is the file called flash-all.bat ?
Click to expand...
Click to collapse
usafle said:
Yes Sir, I am.
I've done this:
Proceed with this step if you want to keep your data intact. If you skip this step, your data will be wiped. With your favorite text editor, edit (be careful not to run it by accident instead of editing) flash-all.bat (if you're on Windows) or flash-all.sh (Mac, Linux) and remove "-w" from the fastboot update command. For example, if the line reads fastboot -w update image-razor-jss15j.zip, it should now read fastboot update image-razor-jss15j.zip. The -w option instructs fastboot to wipe data.Which worked flawlessly on my N5 "upgrade".
I am an Admin user on this machine so the CMD prompt is Admin.
Click to expand...
Click to collapse
Yes, I have never had good luck with removing
Code:
fastboot -w
at this point with no recovery and not booting your data is lost...
So I would not modify it and see if you can get it to boot...
Thx Josh
{
"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"
}
Well there goes everything data wise. Freaking great. LOL
Boots up by removing
Code:
fastboot -w
and flashing. Dammit.
Thanks anyway for the assist.
lj50036 said:
Yes, I have never had good luck with removing
Code:
fastboot -w
at this point with no recovery and not booting your data is lost...
So I would not modify it and see if you can get it to boot...
Thx Josh
Click to expand...
Click to collapse
Hello together,
these were the steps to update to 5.1.1 (LMY47X) from 5.0.1 (LRX22C).
It was working for me - without loosing data.
Notes:
OTA didn't work cause of having custom recovery / root.
Maybe it was also in another thread here - but I didn't saw it
It work for me (WIFI-Version) - but might kill your device :crying:
from post #4: In case you using fastboot no very often - look here for more details: http://forum.xda-developers.com/showpost.php?p=60697487&postcount=26 - Thanks the.teejster
Steps
Make sure you have working fastboot on your PC
Download Factory Image and unzip it
Also unzip the included image-volantis-lmy47x.zip
Boot your Nexus 9 into fastboot (Shutdown device; Hold Vol-UP + Power on)
Flash bootloader & reboot
Code:
fastboot flash bootloader bootloader-flounder-3.44.1.0123.img
fastboot reboot-bootloader
Erase everthing but data partition
Code:
fastboot erase system
fastboot erase recovery
fastboot erase cache
fastboot erase boot
fastboot erase vendor
Flash the file (found in the unpacked image-volantis*zip)
Code:
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash vendor vendor.img
Reboot device
Optional: Root it again.
Download CF-Autoroot
Use the root-Scripts
Hope it helps and works for you.
One question. I am rooted and have twrp recovery. I this case : Why should we update recovery?
Alternatively, you could remove the "-w" flag from the flash-all.sh script and run it without losing data
A few key prerequisite items are missing in the OP..
I wrote up a similar "how to" over here :
http://forum.xda-developers.com/showpost.php?p=60697487&postcount=26
Hello,
I always upgraded android manually flashing while in fastboot.
Lastly i upgraded to 5.0.2 flawless, then yesterday i download 5.1.1 image and flashed as usual, to not lose data, bootloader/system/boot.
Now everytime i boot my tablet i get this error
{
"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"
}
And lot of apps force close (gmail opens, but when i try to open a mail fc, eurosport same, opens but when i reada news fc, and many other)while others works flawless.
I tried wiping everything, also userdata, but problem not solved.
What can i do?
I read here that someone when upgrade android also erase "vendor", it's the only thing i didnt do, but i never did it.
Please help, finally with 5.1.1 this device flies but now i can't use it!
Thanks.
What about Vendor and recovery ?
Please see my instructions linked about 2 posts up. Follow those exactly and you shouldn't lose any data and the upgrade should be fine.
Sayan1987 said:
Hello,
Lastly i upgraded to 5.0.2 flawless, then yesterday i download 5.1.1 image and flashed as usual, to not lose data, bootloader/system/boot.
Now everytime i boot my tablet i get this error
Click to expand...
Click to collapse
Sayan1987 said:
Hello,
I always upgraded android manually flashing while in fastboot.
Lastly i upgraded to 5.0.2 flawless, then yesterday i download 5.1.1 image and flashed as usual, to not lose data, bootloader/system/boot.
Now everytime i boot my tablet i get this error
And lot of apps force close (gmail opens, but when i try to open a mail fc, eurosport same, opens but when i reada news fc, and many other)while others works flawless.
I tried wiping everything, also userdata, but problem not solved.
What can i do?
I read here that someone when upgrade android also erase "vendor", it's the only thing i didnt do, but i never did it.
Please help, finally with 5.1.1 this device flies but now i can't use it!
Thanks.
Click to expand...
Click to collapse
try fastboot flash vendor vendor.img
For the fc you are experiencing, it is possibly due to the modified ART in 5.1.1 or you check if you have the latest Android Webview
I just thought I would throw this out here in case anyone needs or wants to know...
You do not need to flash the bootloader to upgrade from 5.0.2 to 5.1.1, I can not tell you if this will work coming from 5.0.1
Also after first boot and you flash twrp, you can boot to recovery then immediately reboot back to system. Twrp will install su for you. You'll just need to update the su apk in the market. No need to mess with any kind of su zip anymore.
That's all I have to add to an already great guide.
the.teejster said:
What about Vendor and recovery ?
Please see my instructions linked about 2 posts up. Follow those exactly and you shouldn't lose any data and the upgrade should be fine.
Click to expand...
Click to collapse
laill said:
try fastboot flash vendor vendor.img
For the fc you are experiencing, it is possibly due to the modified ART in 5.1.1 or you check if you have the latest Android Webview
Click to expand...
Click to collapse
Thanks guys flashing vendor fixed everything!!
All the forced closes, heat problems, May I ask are you really stock? No such problems here
Verstuurd vanaf mijn HIGHWAY SIGNS met Tapatalk
i have a Nexus 2012 7inch tablet (Wifi) that is soft bricked. (stuck at the perpetual moving colored dots screen).
when my tablet was still under warranty in 2013 it did have it's motherboard replaced when it wouldn't even turn on. now the problem is different, at least i can power it on and get into the bootloader. since the lollipop update it had been getting progressively laggy before finally 'crashing' and bootlooping.
i've tried the following:
1) first i attempted the tutorial located here: http://forums.androidcentral.com/go...1477-guide-nexus-7-factory-image-restore.html
i managed to wipe the device but not flash the images to the device.
2) then i used this tutorial http://forum.xda-developers.com/showthread.php?t=2588979 to install the adb drivers.
3) i have now used Wugs to attempt flash stock + unroot. everything seems to work until it gets to "sending 'system'" then it gives "FAILED <data transfer failure <Unknown error>>, also same error for sending 'userdata'and post-flash factory reset. same Unknown error.
i am also not sure which google images to use. i have tried nakasi 4.3 (JWR66Y), 4.4.4 (KTU84P), and 5.1.1 (LMY47V), and "any build" options.
so i'm not sure if it could be a driver issue or how to fix it further. fastboot seems to recognize the tablet while adb does not. i did not have it set in debugging mode.
i've attached the screen from Wugs...
{
"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"
}
stargirl29 said:
i have a Nexus 2012 7inch tablet (Wifi) that is soft bricked. (stuck at the perpetual moving colored dots screen).
when my tablet was still under warranty in 2013 it did have it's motherboard replaced when it wouldn't even turn on. now the problem is different, at least i can power it on and get into the bootloader. since the lollipop update it had been getting progressively laggy before finally 'crashing' and bootlooping.
i've tried the following:
1) first i attempted the tutorial located here: http://forums.androidcentral.com/go...1477-guide-nexus-7-factory-image-restore.html
i managed to wipe the device but not flash the images to the device.
2) then i used this tutorial http://forum.xda-developers.com/showthread.php?t=2588979 to install the adb drivers.
3) i have now used Wugs to attempt flash stock + unroot. everything seems to work until it gets to "sending 'system'" then it gives "FAILED <data transfer failure <Unknown error>>, also same error for sending 'userdata'and post-flash factory reset. same Unknown error.
i am also not sure which google images to use. i have tried nakasi 4.3 (JWR66Y), 4.4.4 (KTU84P), and 5.1.1 (LMY47V), and "any build" options.
so i'm not sure if it could be a driver issue or how to fix it further. fastboot seems to recognize the tablet while adb does not. i did not have it set in debugging mode.
i've attached the screen from Wugs...
Click to expand...
Click to collapse
Try flashing the images individually with fastboot. That's how I always do it. Be sure your platform tools are up to date as well.
fastboot
Evolution_Tech said:
Try flashing the images individually with fastboot. That's how I always do it. Be sure your platform tools are up to date as well.
Click to expand...
Click to collapse
i'm not really sure how to do that.
stargirl29 said:
i'm not really sure how to do that.
Click to expand...
Click to collapse
Download and unzip the factory image. Unzip two times until you have all the images. I.E. bootloader, radio, boot, system, recovery, userdata, cache.
Put them where fastboot can find them. I.E. platform tools folder.
Hopefully you know how to use fastboot.
Start by flashing bootloader.
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot bootloader
Then flash the rest.
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot format cache
fastboot flash cache cache.img
fastboot reboot
fastboot
Evolution_Tech said:
Download and unzip the factory image. Unzip two times until you have all the images. I.E. bootloader, radio, boot, system, recovery, userdata, cache.
Put them where fastboot can find them. I.E. platform tools folder.
Hopefully you know how to use fastboot.
Start by flashing bootloader.
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot bootloader
Then flash the rest.
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot format cache
fastboot flash cache cache.img
fastboot reboot
Click to expand...
Click to collapse
no i do not know how to use fastboot. but what you posted sounds exactly like the tutorial that i followed in step #1 that i mentioned above. i did the tutorial again last night and was able to flash the images this time, but it's still stuck in bootloop on startup.
stargirl29 said:
no i do not know how to use fastboot. but what you posted sounds exactly like the tutorial that i followed in step #1 that i mentioned above. i did the tutorial again last night and was able to flash the images this time, but it's still stuck in bootloop on startup.
Click to expand...
Click to collapse
Factory reset from recovery.
Evolution_Tech said:
Factory reset from recovery.
Click to expand...
Click to collapse
if you mean this, https://support.google.com/nexus/answer/4596836?hl=en
yes. that was the first thing i did. and always the first thing i try before using any toolkits or manual repairs.
i ran Wugs again today and FINALLY got it back to the sign in screen to setup the tablet. everything was going great. then i got back into the bootloader to lock the oem. and when it restarted i'm still getting the "optimizing apps x of 99" which is annoying but it seems my tablet is at least usable for now.
Sorry to say your in the same boat as a large number of people. These devices just up and died. Take a look around for #Nexus7Bricked
Google forums will also confirm this. At this time you have a nice paperweight. I've tried all the things you have (and spent probably 10 hours over a few months) and it still won't come up.
fixed it!
vipthomps said:
Sorry to say your in the same boat as a large number of people. These devices just up and died. Take a look around for #Nexus7Bricked
Google forums will also confirm this. At this time you have a nice paperweight. I've tried all the things you have (and spent probably 10 hours over a few months) and it still won't come up.
Click to expand...
Click to collapse
i fixed it with Wugs yesterday, finally! after 5 days of trying.
Hello,
I was on B336 and wanted to root it. All good, I followed the steps, and accidentally wiped cache&dalvik... Bootloop. Then I tried to downgrade to MM... No success... After that, something told me to wipe system, data, Dalvik, cache, everything except for Internal Storage, phone storage... I tried then to flash EMUI 5 beta 336... It didn't work. I tried then to flash Meticulus TWRP instead of Revolution TWRP... It did not work... I tried to dload MM stock, it did not work...
I'm stuck with:
-No OS
-Revolution TWRP
-Meticulus TWRP doesn't boot
Is there anything I can try to get it booting or I can throw the phone into the garbage bin?
I even tried to flash Meticulus TWRP with the RevolutionRecovery (I know, I know) and of course it did not work...
If you are with no OS
flash via fastboot system.img boot.img cust.img and recovery.img using app extractor
I don't remember the exact order (yes, you must flash them in a specific order)
diorenzo said:
If you are with no OS
flash via fastboot system.img boot.img cust.img and recovery.img using app extractor
I don't remember the exact order (yes, you must flash them in a specific order)
Click to expand...
Click to collapse
Found the order:
- Fastboot flash boot boot.img
- Fastboot flash system system.img
- Fastboot flash cust cust.img
But I can't understand the part about app extractor. Can you explain please?
There is an app called app extractor (you can easily find here in the forums)
You put your Update.app file (the one you should put on the dload folder) and the app extract you these files
After you flash them via adb
I had your problem and solved using this
(Sorry for my english)
@diorenzo Ok, I got it, I extract from the .APP file with Huawei Update Extractor. What should I do next?
Go on fastboot mode with the phone
And via pc flash the files
diorenzo said:
Go on fastboot mode with the phone
And via pc flash the files
Click to expand...
Click to collapse
I know that... I meant, after I flash those files... Is there something else?
Asphyxiate666 said:
I know that... I meant, after I flash those files... Is there something else?
Click to expand...
Click to collapse
Nope, just reboot and wait
(It can take a while)
diorenzo said:
Nope, just reboot and wait
(It can take a while)
Click to expand...
Click to collapse
Thank you very much man, I will try what you told me. I hope it will work.
Don't worry
Flashing system.img gives me an error:
sparse flash write failure
Click to expand...
Click to collapse
@diorenzo
What error?
diorenzo said:
What error?
Click to expand...
Click to collapse
{
"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"
}
Did you flash boot.img?
diorenzo said:
Did you flash boot.img?
Click to expand...
Click to collapse
Yes, and it flashed successfully.
Mmhh, really don't know
Try again
diorenzo said:
Mmhh, really don't know
Try again
Click to expand...
Click to collapse
Tried two times with no success... I'll try switching ports.
Sounds similar to what I had. Take a look here.
The solution in brief was:
1. Go into bootloader to flash recovery (I used Revolution Recovery)
2. In recovery, flash OEM info.
3. Then used the 3-button method to install stock version for the appropriate model (which I could see from OEM info).
4. Unlocked bootloader, triggering a factory reset. (I was stuck in infinite boot before this point.)
Click to expand...
Click to collapse
Zeruno said:
Sounds similar to what I had. Take a look here.
Click to expand...
Click to collapse
It was what i was thinking
I though he could flash recovery via fastboot (but i didn't remember he had to flash oeminfo)