Hi guys
In the first sorry for bad english.
I have one asus FE170cg (k012) , its brick
History:
I update this device to 10_32_1_33_1 version with UpdateLauncher_K012_WW_10_32_1_33_1 file
after update my tablet has been restart but asus logo show nothing to do.
last night i download laste version UL-K012-WW-11.2.3.18.2-user from asus official site and flash on tablet:
first i flash 3 file extract version (fastboot , boot , splashscreen)
after that rename file to K012_sdupdate and copy to memory card (1g) , turn on tablet to driodboot and select recovery but my tablet not boot up to android.
Please help me for flash this tablet in driodboot by fastboot command.
when my tablet is off and i connect it to pc in device manager search one driver same name cloverview and shoma USB arm in tablet:crying::crying::crying::crying:
rezasony said:
Hi guys
In the first sorry for bad english.
I have one asus FE170cg (k012) , its brick
History:
I update this device to 10_32_1_33_1 version with UpdateLauncher_K012_WW_10_32_1_33_1 file
after update my tablet has been restart but asus logo show nothing to do.
last night i download laste version UL-K012-WW-11.2.3.18.2-user from asus official site and flash on tablet:
first i flash 3 file extract version (fastboot , boot , splashscreen)
after that rename file to K012_sdupdate and copy to memory card (1g) , turn on tablet to driodboot and select recovery but my tablet not boot up to android.
Please help me for flash this tablet in driodboot by fastboot command.
when my tablet is off and i connect it to pc in device manager search one driver same name cloverview and shoma USB arm in tablet:crying::crying::crying::crying:
Click to expand...
Click to collapse
go to droidboot and do factory reset.
Hi rezasony,
did you solve your problem?
##POSSIBLE SOLUTION##
First of all you have to identify what FW ver you have,
1. Start the TAB in Droidboot by pressing and HOLDING Volume UP and Power button until the menu appears,
2. Now you can see what FW Installed on your TAB,
3. Now go to ASUS Support Site and Download the same FW as your TAB,
4. After Downloading FW, Extract it and Copy .zip File to SD Card and rename it to k012_sdupdate.zip,
5. Now put back SD Card into TAB and Reboot into DroidBoot Mode,
6. Now Here is the Trick, You have to Plug the Charger in the TAB while Updating from SD So, Plug the Charger now then choose SD Update,
7. Wait until Update process finish then reboot your TAB,
>>DONE<<
#IN CASE THAT METHOD DIDN'T WORK FOR YOU TRY THIS ONE:
1. Extract this files from the FW zip file and copy them to fastboot folder,
fastboot.img
boot.img
splashscreen.img
Click to expand...
Click to collapse
2. Start your TAB in DroidBoot mode and via Fastboot excute this commands one by one,
fastboot erase cache
fastboot erase system
fastboot erase userdata
fastboot flash fastboot fastboot.img
fastboot flash boot boot.img
fastboot flash splashscreen splashscreen.img
Click to expand...
Click to collapse
3. Now Copy the same .zip File that you've extracted 3 .img files from to SD Card and rename it to k012_sdupdate.zip and Copy it again to the same SD Card but this time rename it to ASUS_BUNDLE.zip,
4. Put back SD Card into TAB and Reboot into DroidBoot then Plug Charger and Select SD Update,
>>DONE<<
#NOTE: SOLUTION TESTED BY ME MANY TIMES AND I'VE FIXED MORE THAN 10-TABS.
Related
My tab started giving al kind of errors on internal apps and stuff so i shut it down and now it is in reboot loop.
I can get it into odin download mode or fastboot mode. But i cannot see it with adb or fastboot (it doesent show up when using adb devices or fastboot devices.
i can use odin to do a pda flash but outcome is stil the same.
also did nvflash from Retail 3.1 CWM Recovery, Root & full back up!
al goes fine but after that still no adb reboot recovery or adb devices
iam desperate please help me with this
renedg said:
My tab started giving al kind of errors on internal apps and stuff so i shut it down and now it is in reboot loop.
I can get it into odin download mode or fastboot mode. But i cannot see it with adb or fastboot (it doesent show up when using adb devices or fastboot devices.
i can use odin to do a pda flash but outcome is stil the same.
also did nvflash from Retail 3.1 CWM Recovery, Root & full back up!
al goes fine but after that still no adb reboot recovery or adb devices
iam desperate please help me with this
Click to expand...
Click to collapse
Here's what you do.
Download the file linked below
Download ODIN attached below
Once both are downloaded, extract PDA_SIGNED_P7105.tar
Boot your tablet into ODIN and plug it into your PC
Open the ODIN program on your PC and check the box next to PDA
Click the PDA button and navigate to the file you downloaded earlier
Press Start and let it flash
Once it is done, it will still boot loop.
You need to go into recovery (It will now be the default recovery) and wipe data/factory reset only.
Reboot and it should load up, however you will be on 3.0.1.
You can get back to 3.1 by rooting and installing recovery again or by using the update feature in the tablet's settings.
Good luck!
http://www.mediafire.com/?gcenefqc3khcc0c
renedg said:
My tab started giving al kind of errors on internal apps and stuff so i shut it down and now it is in reboot loop.
I can get it into odin download mode or fastboot mode. But i cannot see it with adb or fastboot (it doesent show up when using adb devices or fastboot devices.
i can use odin to do a pda flash but outcome is stil the same.
also did nvflash from Retail 3.1 CWM Recovery, Root & full back up!
al goes fine but after that still no adb reboot recovery or adb devices
iam desperate please help me with this
Click to expand...
Click to collapse
Please DO NOT ask Questions in the Development forum
Moving to General
When i have done this and go into recovery (power and left volume) i stil get usb icon and download (odin) and still no device found with adb or fastboot (driver i sbeing loaded so somehow my system does regonize it as fastboot or recovery device but with fastboot devices or adb devices still no device in list.
It is alive again. Thanks all who helped out
renedg said:
when i have done this and go into recovery (power and left volume) i stil get usb icon and download (odin) and still no device found with adb or fastboot (driver i sbeing loaded so somehow my system does regonize it as fastboot or recovery device but with fastboot devices or adb devices still no device in list.
Click to expand...
Click to collapse
it is alive again. Thanks all who helped out
You are the man! My IO Galaxy Tab 10.1 is alive again!
Thanks!
Hi All,
I am done the ODIN step, but it still in bootloop mode. I dont know how to do with the Fastboot recover mode. I tried with my Windows 7 and it can't recognized my fastboot driver and stay in the <waiting for device>. Is there any solution for me. Thank you so much.
ericc191 said:
Here's what you do.
Download the file linked below
Download ODIN attached below
Once both are downloaded, extract PDA_SIGNED_P7105.tar
Boot your tablet into ODIN and plug it into your PC
Open the ODIN program on your PC and check the box next to PDA
Click the PDA button and navigate to the file you downloaded earlier
Press Start and let it flash
Once it is done, it will still boot loop.
You need to go into recovery (It will now be the default recovery) and wipe data/factory reset only.
Reboot and it should load up, however you will be on 3.0.1.
You can get back to 3.1 by rooting and installing recovery again or by using the update feature in the tablet's settings.
Good luck!
Click to expand...
Click to collapse
Hello, I have also followed these directions however I am having issues rebooting into recovery using adb.
When I execute adb devices no devices are found.
Any additional help would be appreciated. Thanks
UPDATE:
Success!! I was able to correct the boot loop problem by installing fastboot on a linux machine and running sudo fastboot -w. Also my tablet was in fastboot mode (Power + Volume down, then Select the usb symbol).
Instructions for installing fastboot were found here http://forum.xda-developers.com/showpost.php?p=14675422&postcount=2
boot looping SOLVED! Honeycomb 3.1 google i/o galaxy tab 10.1
[IO TAB] Boot looping? Try this to get your tab back...
I had an issue with my IO 10.1 Tab boot looping. I imagine that this would work for retail as well but have not tried it.
This process will factory reset your device.
You will need fastboot and recovery.img to boot into recovery in order to perform a factory reset.
Fastboot & Stock IO recovery comes from this post as an attachment at the bottom.
You need adb to continue (windows).
1. Extract files to where adb resides (platform-tools folder in android SDk main folder) e.g
C:\Program Files\Android\android-sdk\platform-tools .
2. Plug your tab in to a power source and then hold down the power button until it shuts down. Wait until the tab displays the charging battery.
3. Press and hold the volume down (left button in landscape) and power buttons until the usb and odin icons show up. Volume down to move left and volume up to select the usb logo. Now you should be in fastboot. Plug the usb into your computer.
4. Time to fire up adb!
Start / run / cmd , cd\,
Than, cd to your platform-tools folder or wherever your adb is at. (should be in platform-tools inside of android-sdk-windows)
5. In cmd type "adb start-server" without quotes to start adb. All comands should exclude quotes.
6. Type "fastboot devices" your device serial should appear!If not:
Edit the “<PATH TO ANDROID SDK>\extras\google\usb_driver\android_winusb.inf” file and copy/paste the following lines and add them to the [Google.NTx86] section (for 32bit Windows) and/or [Google.NTamd64] (for 64bit Windows).
NO Empty line above this set, though galaxy tab 10.1v but works for all variants!(tab detected as adb xxx device)
;Galaxy Tab 10.1v
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&REV_9999&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6601
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
;
Download the fastboot zip attached to this post (includes both Win and Linux version) and extract the files to your “<PATH TO ANDROID SDK>\platform-tools” folder
7. Now, type "fastboot boot recovery.img"
8. Now you should boot into recovery. For "adb command lines" to work boot with clockworkmod recovery img (Command and files here: http://droidbasement.com/db-blog/?p=2032)
If you want to try other stuff like push a system restore, kernel or whatever, now you can. If you fail at it, you can always repeat the steps leading up to this point to get back to recovery.
9. Time to just get the tab back! Select "wipe data/factory reset" and confirm, clear cache.
10. After that is done select "reboot device".
Credits to JASKRU from rootwiki, with some additions and modifications extracted from different sources!
for rooting the tab install the zip file from this post in recovery mode (loading recovery.img from fastboot):
http://droidbasement.com/db-blog/?p=2054
P.S don't reboot into recovery with adb command "adb reboot recovery" as it doesn't work, correct way is with fastboot command as mentioned in step 7!
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
FIRST STEP: add the attached fastboot files into the container folder of adb (in sdk folder)
This is mine:
C:\Program Files\Android\android-sdk\platform-tools
of course I did that and mine is in the same folder as yours
I get to step six and thats when it gives me the error
E:\android-sdk-windows\platform-tools>fast boot devices
'fast' is not recognized as an internal or external command,
operable program or batch file.
also when I go to the left instead of odin this is my pic (in attachment)
NOW if I hit the power button and the right on in landscape mode I do get the android system recovery options says Android System Recovery <3e> (pic attached)
I have tried wiping date clearing cache as far as fastboot goes it still doesnt let me in fastboot eventhough im not sure at this point what fastboot even is
I finally got CWM 4.0.0.4 on it but now what because somehow im on 3.0.1 on my tab it wont charge and idk what to do
These steps were tested on 3.1.can you update your firmware from kies or on device?fastboot is needed to boot into the recovery image as in your pic which you already have managed being in older firmware.
E:\android-sdk-windows\platform-tools>fast boot devices
I believe something is still wrong, did you extract the contents of zip file in the platform-tools or the complete folder?Second, how was your tab once in fastboot recongnized by windows it should be as an adb. Device and not fastboot. Third, try manually installing the driver from extras folder, google, usb in android sdk. Last is your system 64bit or 32bit as the modification in inf file should be made accordingly. The only issue is driver or fastboot exe not being in adb folder.
Adding, once in recovery as in the pic, try command adb devices and let know if your device is detected hence you can push a restore fileto your device and reboot or push original recovery.zip file and apply it from sdcard (internal memory).
Last try odin option and flash firmware as tar file mentioned in this forum, try the bootloop or blank screen threads.
tried this route but it cannot find my device via ADB - used the PDANet driver - note i did not get a driver in the extras folder
ideas?
mughalgxt said:
These steps were tested on 3.1.can you update your firmware from kies or on device?fastboot is needed to boot into the recovery image as in your pic which you already have managed being in older firmware.
E:\android-sdk-windows\platform-tools>fast boot devices
I believe something is still wrong, did you extract the contents of zip file in the platform-tools or the complete folder?Second, how was your tab once in fastboot recongnized by windows it should be as an adb. Device and not fastboot. Third, try manually installing the driver from extras folder, google, usb in android sdk. Last is your system 64bit or 32bit as the modification in inf file should be made accordingly. The only issue is driver or fastboot exe not being in adb folder.
Adding, once in recovery as in the pic, try command adb devices and let know if your device is detected hence you can push a restore fileto your device and reboot or push original recovery.zip file and apply it from sdcard (internal memory).
Last try odin option and flash firmware as tar file mentioned in this forum, try the bootloop or blank screen threads.
Click to expand...
Click to collapse
solved my problem -
first fastboot.exe is located in the android-sdk\tools directory. i copied it to my android-sdk\platform-tools directory
Then i get into the tablet's fastboot mode (holding down power + volume down, then select the USB icon) i plug in the cable to my PC's USB, then go to device manager and you should see a fastboot device with an exclamation mark. right click on this and select update driver then navigate to android-sdk\extras\google\usb_driver directory and select android_winusb.inf - it should now install the driver
open up a cmd window and follow the instructions highlighted above starting at step 7
animatechnica said:
solved my problem -
first fastboot.exe is located in the android-sdk\tools directory. i copied it to my android-sdk\platform-tools directory
Then i get into the tablet's fastboot mode (holding down power + volume down, then select the USB icon) i plug in the cable to my PC's USB, then go to device manager and you should see a fastboot device with an exclamation mark. right click on this and select update driver then navigate to android-sdk\extras\google\usb_driver directory and select android_winusb.inf - it should now install the driver
open up a cmd window and follow the instructions highlighted above starting at step 7
Click to expand...
Click to collapse
IN Short, follow the steps in my previous post from 1st till end! Flashing the bootloader file from my thread in development section, is easiest way. Replacing fastboot with recovery option in bootscreen solves many issues for non-developers!
yes and i should add your method was very effective ! thanks
what threw me off initially was not finding the fastboot.exe which was in a different folder and the usbdriver - which needed to be installed separately and can be found by launching SDK manager, selecting Available packages-Third-party Add ons-Google Inc - Google USB Driver Package revision 4
mughalgxt said:
IN Short, follow the steps in my previous post from 1st till end! Flashing the bootloader file from my thread in development section, is easiest way. Replacing fastboot with recovery option in bootscreen solves many issues for non-developers!
Click to expand...
Click to collapse
Thanks!!!
This totally worked!
vokhoa408 said:
Thanks!!!
This totally worked!
Click to expand...
Click to collapse
Is this thing getting Ice cream sandwich?
that might solve all these problems.
Samsung Galaxy Tab 10.1 boot loop
Edit: *Fixed!* Ok, so here is my advice to all you other noobs who bricked your tablet, be AWARE that your tablet actually is conscious, it chooses when it wants to work. Just do everything it says on here, all the fixes I have listed, reboot a bunch of times, yell at it, and when you cry a true tear of pain and remorse, and it splashes down on the surface, it will recognize this and all of a sudden work. Booted to 3.0.1 and going to update, that all that is holy.
Hi Guys, I am having the same problem and need some expert advice please, I have a Samsung Galaxy Tab 10.1 with Android Honeycomb 3.1, running Windows XP Pro SP3
I've gone over every solution to this problem on xda over two days and none have worked for me, either that or i'm not doing it correctly.
I successfully rooted my Tab a few days ago, then tried to install a 'boosted' theme and everything is messed up now. When I boot it just hangs on the samsung loading screen, and it reboots to the same screen.
I have tried wiping data/factory reset in cwm
I have tried wiping cache partition
I have tried running Odin through downloading mode
I have adb and fastboot installed on my computer
I have Samsung Android adb interface driver in Device Manager
I have PDAnet installed
When I boot holding the volume down and power button to get the two options, the only two options I have are the Odin Downloading green guy on the right, and an icon with a box and an arrow coming out of it that takes me to CWM on the left.
So I cannot choose fastboot mode on the Tab, when I try to run 'fastboot flash system new.img' through cmd.exe it just says < waiting for device >
I"m a total noob to this and should have left well enough alone when I successfully rooted it, i'm sure I must be just missing a small step, if I could get a bit of guidance it would be greatly appreciated, thanks.
I just want to pose a question:
My volume down button has been broken (peculiar build quality of these things ), but to the best of my current knowledge i'm safe. In CWM recovery i can always loop in the scroll to make the right decisions and to reach "fast boot" i don't need to use the "volume down". My question is then this: Is there any situation that I could happen to stumble upon in which I would need the down button to carry out an "unbricking process"/wipe/reseting? I have never had to use "fast boot" since all my issues jumping between firmwares have been resolved through CWM, and I don't want to just try "fast boot" now just to find I need the "volume down" to be able to restart the device
I don't think that button is needed for a major task, I think you're safe for now!
With the stock recovery you'll need it to use the update, but with cmw as you said it you don't need it, for fastboot/adb you don't need it, for now there's no major task that I can think of that that button is needed.
Enviado através do Tapatalk
Thanks for the swift answer! So if i for example flash FolioMod then I need to flash CWM in order to change to another firmware. How do one flash CWM without using stock recovery? ADB? Guide somewhere?
Heres a post i've found on another forum that explains how to set up fastboot:
Step 1 - Install fastboot driver for the Folio :
- Download PdaNet and install it on your PC, it will go till a point where it says it can't be installed and cancel itself but the magic is that the driver is installed.
Download PdaNet from www[dot]junefabrics[dot]com/android/download.php (i had to put the link that way cause the forum wont allow me to post outside links yet)
Step 2 - Download the tools needed to prepare the Folio
- Download and extract the following archive on your PC, these are the tools needed to erase the Folio and to flash the Honeycomb rom. You will only need what's inside the folder ToolsD...
Download from www[dot]box[dot]net/shared/4ugbev5jnx5fbp3v3u2e
Step 3 - Start fastboot mode on the Folio
- Start the tablet and at the TOSHIBA logo press 3 times Power and 1 time Vol+, then connect it to the PC. It should be detected by the driver we installed at step 1.
Step 4 - Erase the tablet and flash the new recovery (ClockWorkMod)
- Open a cmd window on your PC, go to the folder ToolsD we extracted at step 2 and type in the following commands :
Code:
fastboot erase userdata
fastboot erase system
fastboot erase cache
fastboot erase linux
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot reboot
Step 5 - Install the new rom from ClockWorkMod
- Once the reboot starts, at the TOSHIBA logo, press Power and Vol+ at the same time, then Vol+, then Vol-, then Vol+. You should be in ClockWorkMod recovery...
- Prepare a SD card with your favorite rom (for me it's Folio3x(HoneyComb 3.0.1) for Folio100 - VegaComb based), don't forget to unzip it, you should end with a update.zip file.
- Insert the SD card in the tablet and select - apply sdcard:update.zip, it should start the installation. If not chose - install zip from sdcard and choose the file. If you can't see it, either the sdcard is not formated correctly or it simply does not see the card, try to reboot the recovery with the sdcard inserted.
After these steps and once it's installed, it should reboot and start VEGACOMB. Please be patient, it takes a while to start... and do not forget to reboot after the initial setup to activate the wifi (yes it's a bug)!
If it still does not start, reflash it again (step 5) sometimes it just does not work on first try. What you can also try is to format the different partitions from ClockWorkMod recovery, there's a Mounts and Storage menu and after you mount all the possible partitions (some won't), format them all, reboot the recovery and start step 5 again.
Regards,
Luis
Click to expand...
Click to collapse
If you want to change your recovery, just replace the recovery.img on the ToolsD folder with the one you want, then on step 4 just do the following:
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot reboot
You dont need step 5.
I also think that if you remove the recovery.img from the update.zip before you flash the rom it will keep the recovery you have now, but i cant confirm that, anyway, if you need to change the recovery just do those steps.
I can access fastboot, and recovery.
however i am unable to boot into any ROM (AOKP or CM10)
the screen flash white, and the thing just offs.
even if I go back to stock now, this still happens
anyone encountered this before?
ideas to solve?
try to enter into recovery TWRP and choose wipe factory and system. then reboot into bootloader (fastboot) and flash recovery and recovery2 with recovery.img from official ROM. then put official's dload into microSD then reboot. it should flash official ROM.
still the same.
below is my attempt to reboot the tablet into stock recovery to install dload folder.
note the white screen, then the android robot, then switches off.
Hi! Can you solve your problem? I'm having the same with a S7-312u (AT&T version).
serverxeon said:
still the same.
below is my attempt to reboot the tablet into stock recovery to install dload folder.
note the white screen, then the android robot, then switches off.
Click to expand...
Click to collapse
Remove SD card and SIM card then turn off the device. plug the device to a computer via usb and press vol+ and vol- for 30 secs till you get all the yellow text on the screen. now press all buttons power , vol+ , vol- and your device should restart and no more white screen
me too same problem with
Mediapad 10 link s10-101u
white screen after wrong flash file
cant update again from sd card only fastboot working but computer never seen the device (fastboot devices) or (adb devices)
how can i reflash the device throw fastboot ?
RAZOR888 said:
me too same problem with
Mediapad 10 link s10-101u
white screen after wrong flash file
cant update again from sd card only fastboot working but computer never seen the device (fastboot devices) or (adb devices)
how can i reflash the device throw fastboot ?
Click to expand...
Click to collapse
no one here ?
Update..
device back to life again after flash it with fastboot
extract the UPDATE.APP with HuaweiUpdateExtractor
try to get in fastboot mode with usb cable
fastboot erase cache
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
you may need to update throw SD with Dlaoad folder
Hi,
I have a G500TG (ASUS_Z00YD) v12.0.0.38, 5..1 ,rooted, (Asus Live Phone) and need the recovery.img or some info about how to recreate/generate this img from these possible sources:
- the phone itself - it is not bricked but without the recovery mode I cant flash OTA files, zip or adb files;
- I did a backup before I done the procedure to install TWRP, flashed recovery.img, but no luck with TWRP working and now the recovery mode boot skips to Asus Logo screen, no more dead droidboot screen;
- The backup has (.backup extension) but no clue how to unzip it on PC to search for this file
- a firmware/rom from official Asus , but inside the zip file there is no recovery.img only boot.img
Checked previous thread "http://forum.xda-developers.com/android/help/asus-zenfone-zc500tg-root-request-t3282861/page7" but the recovery.img from this is for another model phone ZC500TG / Z00VD and as I discovered did not work with my phone.
Tried to reset to original configuration from phone but when it starts after the confirmation it boots to recovery mode cannot find recovery mode and boots back to phone.
Tried copying firmware zip on internal memory to force an OTA update but again without recovery mode, no luck.
So if I cannot restore the recovery.img it will be stuck until a big error occurs.
Ah I can access ADB and Fastboot commands from PC - Dont know how to rebuid recovery.img using SDK from Google...
Tried to use SPFlashTools but could not make MTK Preloader function in W7 tried various MTK drivers... I think all depends on that driver to solve this problem
Any helpful idea?
Thanks in advance
Hi everybody,
Sorry if my post already exists and if my english is bad but i really need help...
I tried to root my honor 7 so first i unlocked bootloader successfuly, i installed TWRP too and everything seemed work very good until last step where my phone didn't boot, i stayed stuck in boot logo... Then I done a factory reset with wipe cache, dalvik, data etc...
Now the only things i'm able to do are boot on recovery mode, eRecovery and on fastboot&rescue mode. I lost adb and fastboot and i'm not able to acess to the phone so i can't put a rom on the phone to install it...
If anyone could help me it would be very nice because I'm going crazy. Thank you !
My phone was up-to-date, i can't remember witch firmware i had but i think it was Android 6.0.1
samhot66 said:
Hi everybody,
Sorry if my post already exists and if my english is bad but i really need help...
I tried to root my honor 7 so first i unlocked bootloader successfuly, i installed TWRP too and everything seemed work very good until last step where my phone didn't boot, i stayed stuck in boot logo... Then I done a factory reset with wipe cache, dalvik, data etc...
Now the only things i'm able to do are boot on recovery mode, eRecovery and on fastboot&rescue mode. I lost adb and fastboot and i'm not able to acess to the phone so i can't put a rom on the phone to install it...
If anyone could help me it would be very nice because I'm going crazy. Thank you !
My phone was up-to-date, i can't remember witch firmware i had but i think it was Android 6.0.1
Click to expand...
Click to collapse
You didnt make any twrp backup??
If you have fastboot you can use Huawei update extractor to extract UPDATE.APP and flash boot.img and system.img directly to your device
Rayan19997 said:
If you have fastboot you can use Huawei update extractor to extract UPDATE.APP and flash boot.img and system.img directly to your device
Click to expand...
Click to collapse
Thank you for your reply. I'm able to enter in fastboot, i extracted boot.img and system.img from UPDATE.APP but i don't know what you mean by flash them because i have no link between the phone and the computer. I can't write on the phone, HiSuite tells that the phone is disconnected and explorer doesn't display the phone neither...
samhot66 said:
Thank you for your reply. I'm able to enter in fastboot, i extracted boot.img and system.img from UPDATE.APP but i don't know what you mean by flash them because i have no link between the phone and the computer. I can't write on the phone, HiSuite tells that the phone is disconnected and explorer doesn't display the phone neither...
Click to expand...
Click to collapse
OK it's good it works
I flashed with fastboot in command line and the reboot was magnificient !
Thank you !!!
I'm glad to see that you succeeded bro :cyclops:
how can u flash with fastboot while no connection to pc
samhot66 said:
OK it's good it works
I flashed with fastboot in command line and the reboot was magnificient !
Thank you !!!
Click to expand...
Click to collapse
how can u flash with fastboot while no connection to pc (as u said earlier)
if u did manage to connect to pc, please share how
thanks in advance
I'm not sure I understand the question but i'll try to explain.
I was not able to connect to PC apart with fastboot (reboot in fastboot mode and connect to PC). Once done, just open a terminal and type "fastboot flash boot <boot image file name>.img" then do the same with IMG (as said in this page .
Hope it will help you !
samhot66 said:
I'm not sure I understand the question but i'll try to explain.
I was not able to connect to PC apart with fastboot (reboot in fastboot mode and connect to PC). Once done, just open a terminal and type "fastboot flash boot <boot image file name>.img" then do the same with IMG (as said in this page .
Hope it will help you !
Click to expand...
Click to collapse
Read this carefully, this will restore youre phone:
1*.)No matter what youve done with this phone it will be cleanly installed like its fresh new, cause i had couple of problems and this method worked
1.)Download the latest b396 firmware
2.)format youre SD card with basic settings via Windows ( if you have a usb stick to connect youre SD card to computer like i do, if you cant connect youre SD card to computer, use another smartphone and format youre SD card with basic settings)- simply talking just format youre SD card
3.)create --->>>dload<<<--- folder like i wrote down without the --->>><<<--- stuff on youre SD card
4.)paste the update.app file to the dload folder
5.)insert youre SD card to phone
6.)this is the moment of truth hold down volume + & - key and power key all in once until the emui logo appears WARNING: remove all keys after logo appearing WARNING: if the logo doesnt appear even after 30sec. keep still holding until the logo appears
***If you get somekind of error i can help, if it worked youre a lucky guy