Related
So I recently grabbed me a Grouper recently to *cough* remember my first Android powerhouse (before I met the Optimus G) and decided to tinker with it as usual. I've owned 6 (now 7) different Groupers in this lifetime and have great experience with it, how to get those pesky drivers working, etc. This is my first 32GB model ever. Anyways, I unlocked the BL, rooted and flashed TWRP (thanks to WugFresh's toolkit) and decided to play with the newer roms (last time I owned one, KitKat was a rumor) and kernel combos. Anyways, I decided I prefer its stock performance and battery, and that maybe I'd use Xposed to tweak apperance instead. My mistake was, I should have flashed a flashable stock rom. But NOOOOO...I decided to flash it back to stock with the fastboot method (which we have various threads on, and toolkits including WugFresh's). Trying the manual method, I followed the following guide using a 4.4 image zip file:
http://forum.xda-developers.com/showthread.php?t=1907796
Claims that the sysem.img doesnt exist when it gets to that part. I extracted the entire file and it DOES exist. Anyways, I tried WugFresh's tk and sort of gives me the same ending (after literally almost an hour of waiting TWICE due to my old PC).
THERE WAS A GUIDE I SAW SOMEWHERE while Googling "how to" get back to stock on Google which actually point ou how to MANUALLY flash each .img yourself one by one via fastboot, which I really intended on doing instead of the above methods (DIY anyone?) but I can't find that guide and I'm not even sure if the post was here on XDA or Android Central. I should have done all Google search on the PC instead but ATM the tablet seemed more convenient for a search.
Anybody know the guide I am mentioning or know what I am talking about? I am assuming that method will solve my dilemma, and I like doing these things manually at times anyways....
EDIT: To my disappointment, found the post, but no good:
http://www.androidbeat.com/2013/11/flash-factory-image-nexus-device/
Apperantly everything flahes fine until it gets to the system.img part...adb/fastboot just freezes there and wont budge at all. Since I noticed that it did flash things, I've decided to flash TWRP and just flash a rom from my flash drive (thanks to a USB OTG) but I would still like to actually FIX the thing properly and return it 100% stock. Any ideas?
Crossvxm said:
I should have flashed a flashable stock rom. But NOOOOO...I decided to flash it back to stock with the fastboot method
Click to expand...
Click to collapse
I'm not sure what you mean by stock. Are you trying to flash a "Stock" rom from the community or the stock images provided by google?
If you are using nakasi-ktu84p image, the flash script contains:
Code:
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
sleep 10
fastboot -w update image-nakasi-ktu84p.zip
You can see here the exact process of getting back to stock.
The boot, cache, recovery, system, and userdata are erased.
Then an attempt to flash the bootloader. This will fail on nakasi-ktu84p and several images back.
Google has been negligent in addressing this issue.
I was able to find success with bootloader-grouper-4.23.img which I extracted from nakasi-krt16s.
You could save time and bandwidth from acquiring it here.
This bootloader also failed to flash for me!
If you have flashed a custom bootloader in the past, you may need to go all the way back to JDQ39 bootloader-grouper-4.18.img.
fastboot flash that, and then you will be able to flash 4.23 from krt16s.
Once you have passed this small ordeal you should be able to install the latest ROM.
In summary, you should be able to do the following from a system that has the fastboot binary:
Code:
EXTRACT nakasi-ktu84p-factory-76acdbe9.tgz
OVERWRITE bootloader-grouper-4.23.img with one acquired from krt16s
Code:
nakasi-ktu84p bootloader-grouper-4.23.img
MD5 = 5bdb2e87370cdb1a7ea14bb0c3e21390
krt16s bootloader-grouper-4.23.img
MD5 = df53028033c9eccf4fe5ba7bc198ce24
Code:
run flash-all.sh or flash-all.bat
PS.
I have been lured by the idea of stock stability, performance, and battery life. Something about Xposed seems dirty to me.
Battery life and Performance have always been better on a custom ROM / Kernel in my experience.
Stability can be rock solid when you've got a good system.
My favourite solution is to have the stock image installed and stripped down for size. This always you to boot in and update your apps from playstore.
I then install a custom ROM alongside via multiRom. This rom also has extras stripped out and no gapps installed.
From Rom 1 you can copy your apks into Rom 2 as needed.
I tend to avoid any apps that would be incompatible with this method!
crache said:
I'm not sure what you mean by stock. Are you trying to flash a "Stock" rom from the community or the stock images provided by google?
If you are using nakasi-ktu84p image, the flash script contains:
Code:
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
sleep 10
fastboot -w update image-nakasi-ktu84p.zip
You can see here the exact process of getting back to stock.
The boot, cache, recovery, system, and userdata are erased.
Then an attempt to flash the bootloader. This will fail on nakasi-ktu84p and several images back.
Google has been negligent in addressing this issue.
I was able to find success with bootloader-grouper-4.23.img which I extracted from nakasi-krt16s.
You could save time and bandwidth from acquiring it here.
This bootloader also failed to flash for me!
If you have flashed a custom bootloader in the past, you may need to go all the way back to JDQ39 bootloader-grouper-4.18.img.
fastboot flash that, and then you will be able to flash 4.23 from krt16s.
Once you have passed this small ordeal you should be able to install the latest ROM.
In summary, you should be able to do the following from a system that has the fastboot binary:
Code:
EXTRACT nakasi-ktu84p-factory-76acdbe9.tgz
OVERWRITE bootloader-grouper-4.23.img with one acquired from krt16s
Code:
nakasi-ktu84p bootloader-grouper-4.23.img
MD5 = 5bdb2e87370cdb1a7ea14bb0c3e21390
krt16s bootloader-grouper-4.23.img
MD5 = df53028033c9eccf4fe5ba7bc198ce24
Code:
run flash-all.sh or flash-all.bat
PS.
I have been lured by the idea of stock stability, performance, and battery life. Something about Xposed seems dirty to me.
Battery life and Performance have always been better on a custom ROM / Kernel in my experience.
Stability can be rock solid when you've got a good system.
My favourite solution is to have the stock image installed and stripped down for size. This always you to boot in and update your apps from playstore.
I then install a custom ROM alongside via multiRom. This rom also has extras stripped out and no gapps installed.
From Rom 1 you can copy your apks into Rom 2 as needed.
I tend to avoid any apps that would be incompatible with this method!
Click to expand...
Click to collapse
Your on the right track that's exactly what I was looking for, but to me it doesn't work on the system.img flashing part, it stays stuck there forever without a hint of movement at all. I left it flashing from 4am to 7am with no progress. I though it was working as the Windows Task Manager was showing fast boot constantly changing in CPU usage as it does when its at work. But sadly, it gets stuck there for good. Then closing fast boot won't work, I have to shut down the PC in order for it to leave
Crossvxm said:
Your on the right track that's exactly what I was looking for, but to me it doesn't work on the system.img flashing part, it stays stuck there forever without a hint of movement at all. I left it flashing from 4am to 7am with no progress. I though it was working as the Windows Task Manager was showing fast boot constantly changing in CPU usage as it does when its at work. But sadly, it gets stuck there for good. Then closing fast boot won't work, I have to shut down the PC in order for it to leave
Click to expand...
Click to collapse
I'm not familiar with the tools you are using. Have you used the commands directly from the command line, and what is the output?
crache said:
I'm not familiar with the tools you are using. Have you used the commands directly from the command line, and what is the output?
Click to expand...
Click to collapse
WugFresh is a toolkit made to root, unlock boot loader, relock, restore to stock, etc. And yeah I used the fastboot erase and fastboot flash commands via ADB/fast boot and as I said, everything goes well except the part where its time to flash the system.img, it just hangs there doing nothing. Tried and left it for several hours and still nothing
Try a different USB port on you computer or a different USB cable... or both.
Crossvxm said:
...
....it doesn't work on the system.img flashing part, it stays stuck there forever without a hint of movement at all.
...
Click to expand...
Click to collapse
Hi, Crossvxm...
This seems to be a relatively common problem, and I always seem to have it myself when fastboot flashing factory stock.
I've no idea why, but the fastboot connection seems to 'time-out' when fastboot flashing 'system.img'.
Now normally, and just prior to running any fastboot flash commands, you should run this command...
Code:
fastboot devices
This command doesn't actually do anything; it's essentially just diagnostic and is used to confirm you have a viable fastboot connection prior to flashing anything. If do you have a fastboot connection, you should see something like this (with the N7 booted into the bootloader)...
Code:
015d2d42xxxxxxxx fastboot
This is the Nexus 7's unique serial number followed by the word 'fastboot'. If you don't see this, then you likely have a driver problem...
...BUT HOWEVER, I KNOW I DON'T HAVE A DRIVER PROBLEM.. so when having problems with 'sending system', and upon opening a second command prompt window on my Windows laptop, and typing fastboot devices again, the Nexus 7's serial number now no longer appears... and this is AFTER the bootloader and boot img's have been sent and written successfully.
At this point, I can only conclude, and that for unknown reasons, my fastboot connection has 'died'... and 'sending system' is now permanently 'stuck'.
And the fastboot flash attempt has failed.
-----------------------------------------------------
The solution for me, was to change to a different USB port on my laptop. Another possibility might be to try a different USB cable... I haven't tried this... just a change of USB port on my laptop was sufficient, and the problem with flashing system.img was resolved.
Either way, reboot the N7's bootloader using a differerent USB port on your computer or a different USB cable... and attempt the flash again.
One final point... 'sending system' does take longer than the other .img's, probably due to it's size... but it really should take no longer than around 5 minutes... 10 minutes maximum.
Hope this helps... and good luck.
Rgrds,
Ged.
Hello to everybody, so i was thinking my nakasi was really dead this time, the last thing i did was flashing a 5.1.1 rom next when i rebooted got stuck on lolipop boot loop so i restarted the tablet
manually to access the recovery, and to my awe, i couldn't no more access the recovery ! (latest twrp) tried again and again nothing, no recovery no bootloader, can't start the OS
always stuck on google logo with the options above, start, bootloader, recovery etc, today i realized i could access the bootloader and fastboot mode (ADB recognize my device when i type fastboot devices)
so i tried flashing stock image and stuff with no luck, tried many stock roms, tried wug's toolkit and the flash all.bat still no luck, i get all kind of error messages here is a screenshot, help is really appreciated if there is anything i can do to save it :
View attachment 3305126
the problem seems to be that i can't write the things i send to the tablet via ADB, tried the NVflash recovery today and got :
View attachment 3306049
Have you tried not imputing the full file address as you have the emulator already running from that location.
So recovery command would be.
Fastboot flash recovery "name of recovery Img file here"
Just make sure that the image file is in the platform-tools folder.
Probably not your issue but its going to save you some typing.
Good luck
gaosphappy said:
Have you tried not imputing the full file address as you have the emulator already running from that location.
So recovery command would be.
Fastboot flash recovery "name of recovery Img file here"
Just make sure that the image file is in the platform-tools folder.
Probably not your issue but its going to save you some typing.
Good luck
Click to expand...
Click to collapse
Thank you for the tip I'll certainly use it, but i don't think it is the culprit since as you can see in the screenshots
the files get sent successfully but cannot be written, my bootloader is unlocked by the way
Homurato said:
Thank you for the tip I'll certainly use it, but i don't think it is the culprit since as you can see in the screenshots
the files get sent successfully but cannot be written, my bootloader is unlocked by the way
Click to expand...
Click to collapse
Did you try the latest factory image? I noticed you are flashing a very old bootloader, possibly the first one? 4.23 is the current version.
Where is flatline_grouper.img coming from? I've never seen that.
adomol said:
Did you try the latest factory image? I noticed you are flashing a very old bootloader, possibly the first one? 4.23 is the current version.
Where is flatline_grouper.img coming from? I've never seen that.
Click to expand...
Click to collapse
Hello kind sir, of course at first i tried the 5.1.1 full factory image with the NRT toolkit and got the same writing errors next i tried many bootloaders
(one of them found it here as a 100% working bootloader) the Flatline is the recovery of the NVflash tool where you can access it to unbrick full bricked N7s
if you got blobs.bin of your N7 backed up (clearly not my case)
the flashing writing error i get it with everything i try to flash, recoverys bootloader system etc
when i send them with the flash all command they got sent to the tablet okay, but when writing i get the errors
i don't know but there is a small informations if that can help, before it broke my system was in EXT4 and all the rest in F2FS
It's entirely possible your memory has failed. I'm reading more and more people running into corrupted memory issues.
You can get a replacement motherboard cheap on eBay if nothing else works.
fwayfarer said:
It's entirely possible your memory has failed. I'm reading more and more people running into corrupted memory issues.
You can get a replacement motherboard cheap on eBay if nothing else works.
Click to expand...
Click to collapse
I'm still hoping for a software solution since my fastboot works fine, I'll let the motherboard solution my last i guess
Hello some news about the still staggering situations : when the tablet is off and i put the charger i get the battery refiling animation ! so that mean the bootloader isn't broken
and i still can access fastboot mode, even when i push a bootloader i get a signature match message, but the problem is still that the things i push can't be written as i'm still getting a :
FAILED <Remote: <FileWriteFailed>> changed usb cables, changed ports, the last time the tablet was working i had the system on EXT4 and the rest on F2FS, maybe if i can convert everything to EXT4 ?
Hi everyone,
I've run out of ideas on this one and other threads couldn't really help me/were closed already.
I tried CM, stock android by Ivan and M1cha as well as some others, but about a month ago, I was curios for MIUI 6 based on Lollipop for my Mi2s and changed from M1cha's CM12 5.0.1.
Now that I've seen that Ivan published his 5.1.1 I wanted to try it out. He also provides us with a modified custom recovery that I wanted to flash.
First, I renamed the file to update.zip and tried to flash it in Mi-Recovery 2.0.1, which didn't work due to the failing signature verification.
Also, choosing update package in the Updater app in MIUI didn't work out, it immediately tells me something went wrong.
Then I thought, why not use fastboot? That worked before.
Not this time. I tried the simple way, meaning just fastboot flash recovery recovery.img: Then, bc it didn't work, I first erased the recovery partition and then flashed the recovery.img, which was still unsuccessful.
Whenever I try to enter recovery mode, my phone just gets stuck showing the MI logo and not doing anything.
I can reenter fastboot mode or simply reboot to the system as usual, except for when no system is installed.
When I gave up on the custom recovery thing, I simply tried to flash the ROM via update.zip methods, as well as via fastboot. None of them worked, either because the signature verification fails (stock recovery) or because the zip file does not contain the android-info.txt and the other txt file.
As mentioned above, upon entering fastboot -w and then flashing the recovery.img, I can suddenly enter recovery mode. This sucks!
TL;DR: No usual method of flashing either custom rom or recovery works (to my knowledge)
Can anyone help me? I know its stupid but I start feeling kind of boxed in on MIUI.
Thanks in advance
fastboot oem unlock
fastboot flash recovery recovery.img
unfortunately, that didn't work either...
leonfromotown said:
unfortunately, that didn't work either...
Click to expand...
Click to collapse
Do fastboot devices and tell us the output
SkiFire13 said:
Do fastboot devices and tell us the output
Click to expand...
Click to collapse
5b799fb fastboot
looks just the way it did before
Hello,
I tried to root my P8 Lite, which is something I've already done on a lot of other smartphones. So I first unlocked my bootloader, then I tried to follow a guide to root it. Everything was going smooth, but when I hit enter for the last time into the command line (at this point of the process, it just installed superSU) my phone rebootd and stucked on the huawei logo. After 20mn I decided it was enough, I unplugged it and hard rebooted it, but still stuck on huawei logo.
Since this, I wasn't able to reboot my phone, nor enter the fastboot/rescue mode. Now I tried on more time to enter the fastboot, and I don't know why but after a few time it showd up !
So basically my phone is now on fastboot mode, unlocked, and I come here to seek answers about the method to flash it and start again with a fresh android. I don't even know where to find the correct rom to flash, nor how to flash, if for instance I should use adb, etc.
If someone here is able to help me, that would be greatly appreciated.
By the way, I manually updated the phone to android 6 and EMUI 4.
Thank you a lot for enlightments.
Hello! Since you are in fastboot mode you can easily fix the issue. Just download a stock rom you wanna flash and use (you can try the new B588) and with the Huawei Update Extractor, extract the boot.img, recovery.img, cust.img, system.img from the UPDATE.APP file. Then flash these in the order i wrote them (using the fastboot command for example:
Code:
fastboot flash boot boot.img
, same thing for all of these just change the file names). That is how i fixed my last 2-3 bootloops. I would suggest looking here first though: https://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994 on Chapter 4. Hope this helps and good luck
Hi,
Thank you for your answer.
Problem is now, my phone ran out of bttery so not in fastboot mode anymore and I just can't figure out how to go back in fastboot anymore.
I tried to power on the phone while pressing vol up, wait for the huawei logo and wait for ten more seconds, nothing except a black screen. I tried vol down, both vol up and down, still nothing. Thing is, yesterday I don't even know how I managed to enter fastboot, I just tried, didn't work, so I put my phone on the bed, and ten minuts later I realized it was on fastboot mode. Informatics huh.
If you have any idea on how to go back in fastboot mode, I tried using adb, but it needs the phone to reach systm to be able to reboot.
By the way you talked about a specific rom, where can I find this one ?
Thank you again for your time.
EDIT : Ok I managed to reach fastboot, what I did was to plug it on my laptop, powered off, then pressed vol down and power on, and it worked. Informatics has its reasons...
Still interested into the rom ou talked. I'll try to find it on my own though. But if you got a link, I would be happy to download it.
EDIT2 : Ok I tried to flash, everything went good, but my huawei is still in its bootloop. I extracted the B588 rom, but there was way more than 4 img files. I still flashed only the four you and the link you gave me told me, but maybe I need to flash more than these 4 ?
Try this https://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994 <-- follow the " Bootloop/Softbrick" method if you cannot install the latest firmware directly. You may need to flash original recovery first too. Any recovery version will do they are all the same, find the how too under the "install TWRP" section, but basically it goes "enter fastboot, type fastboot flash recovery recovery.img" while you have recovery.img in the same directory.
[edit]
Also, if you are on MM you should not be using a batch file to root. Once you have TWRP installed, you need to flash 2 zips via TWRP. They can also be found in the mega thread.
yodaofborg said:
Try this https://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994 <-- follow the " Bootloop/Softbrick" method if you cannot install the latest firmware directly. You may need to flash original recovery first too. Any recovery version will do they are all the same, find the how too under the "install TWRP" section, but basically it goes "enter fastboot, type fastboot flash recovery recovery.img" while you have recovery.img in the same directory.
[edit]
Also, if you are on MM you should not be using a batch file to root. Once you have TWRP installed, you need to flash 2 zips via TWRP. They can also be found in the mega thread.
Click to expand...
Click to collapse
Single stable SuperSu v2.76 also works for builds less than b580.. For builds greater than that, use 2 zips method
Well, it obviously didn't
I instaled persona78's B600 mod on TWRP 3.0.2-0 and rebooted. Just boot logo. Nothing else. No recovery, no fastboot, nothing. After struggling a bit I mamaged to get into fastboot, but when I run adb command in Windows 8.1 it says "waiting for device" and that's it. I tried several tools and "kits" with more functions, one of them being TWRP.
Please help! Tommorow morning I have a working trip and I extremely need my phone, and in my country it's already 1:00 a.m.
I will be very thankful for any solution and fast response.
Thanks!
XTutorials said:
I instaled persona78's B600 mod on TWRP 3.0.2-0 and rebooted. Just boot logo. Nothing else. No recovery, no fastboot, nothing. After struggling a bit I mamaged to get into fastboot, but when I run adb command in Windows 8.1 it says "waiting for device" and that's it. I tried several tools and "kits" with more functions, one of them being TWRP.
Please help! Tommorow morning I have a working trip and I extremely need my phone, and in my country it's already 1:00 a.m.
I will be very thankful for any solution and fast response.
Thanks!
Click to expand...
Click to collapse
Try flashing it again and yes..
....B600 stays in boot logo for longer
HaiderHady said:
Try flashing it again and yes..
....B600 stays in boot logo for longer
Click to expand...
Click to collapse
I cannot acces NOTHING just fastboot. How I'm going to flash the rom again?
Linux saves phones, that is what I have to say.
Ran adb in windows: <waiting for device>
Ran adb in ubuntu: Revived my phone!
Thank god this phone is fixed, otherwise I couldn't continue my developing on PA
If you are truly in fastboot mode, with the green android dude (his name is Andy) and the white background then the command
fastboot devices
Click to expand...
Click to collapse
should return your device's serial number. Then you can go ahead and flash the 4 needed partions from the stock ROM with fastboot.
First of all, you need the 4 .img files for boot, recovery, cust and system.
You can get these as follows:
On this page you can find all ALE-L21 firmware. Find the latest. The latest FULL firmware for Europe region is C432B602 (Dual SIM) and C432B603 (Single SIM). Download the FULL version (not OTA) and use Huawei Update Extractor to extract boot, recovery, cust, and system as .img files
Open a command window in the folder with the files and rename them accodingly if you wish (e.g. 06.boot.img -> boot.img)
Then you can flash them in fastboot mode like this:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
fastboot flash system system.img
Click to expand...
Click to collapse
That last one may take a bit. Then you can do
fastboot reboot
Click to expand...
Click to collapse
JpegXguy said:
If you are truly in fastboot mode, with the green android dude (his name is Andy) and the white background then the command should return your device's serial number. Then you can go ahead and flash the 4 needed partions from the stock ROM with fastboot.
First of all, you need the 4 .img files for boot, recovery, cust and system.
You can get these as follows:
On this page you can find all Huawei firmware. Search (F3 or Ctrl+F) for ALE-L21 and find the latest firmware. (For example, if you search ALE-L21C432 the latest firmware is B600 as of the time of writing this) Download the FULL version (not OTA) and use Huawei Update Extractor to extract boot, recovery, cust, and system as .img files.
Open a command window in the folder with the files and rename them accodingly if you wish (e.g. 06.boot.img -> boot.img)
Then you can flash them in fastboot mode like this:
That last one may take a bit. Then you can do
Click to expand...
Click to collapse
Thanks for the help. But I already fixed my problem.
XTutorials said:
Thanks for the help. But I already fixed my problem.
Click to expand...
Click to collapse
Just in case someone stumbles upon this. I hate when the forum ends abruptly
JpegXguy said:
If you are truly in fastboot mode, with the green android dude (his name is Andy) and the white background then the command should return your device's serial number. Then you can go ahead and flash the 4 needed partions from the stock ROM with fastboot.
First of all, you need the 4 .img files for boot, recovery, cust and system.
You can get these as follows:
On this page you can find all ALE-L21 firmware. Find the latest. The latest FULL firmware for Europe region is C432B602 (Dual SIM) and C432B603 (Single SIM). Download the FULL version (not OTA) and use Huawei Update Extractor to extract boot, recovery, cust, and system as .img files
Open a command window in the folder with the files and rename them accodingly if you wish (e.g. 06.boot.img -> boot.img)
Then you can flash them in fastboot mode like this:
That last one may take a bit. Then you can do
Click to expand...
Click to collapse
it say partition length error please help