Related
After trying to install ICS on my folio 100 using Rom manager, the update to ICS failed. Now the Folio 100 starts normally, but it doesn’t react on the buttons (power + vol +, 3x power vol 1). It just starts normally and after that I can use everything the normal way. Except when I change language from English into Nederlands, it’s not saved and after a restart of the system it’s back in English again, including the time zone which will be back to GMT +00.00 which is very annoying. The only way to get rid of this is to reinstall Android 3. By the way, factory reset doesn’t reset anything. It just restarts the Folio.
Getting into recovery from the menu or from Rom manager won’t do the trick either. The only thing I can use is ABD. But the command “flash_image recovery recovery.img” gives an error: “Error scanning partitions: No such file or directory”. And the file is in the system-directory. So this is a dead end for me too. I searched the forum and the internet, tried several possibilities, but now I’m stuck. I’ve considered opening the Folio and to start it without NAND connected, but I haven’t tried this, because I still hope for a software solution. What will happen when I manually delete of format the internal SD? Is there anyone who can help me to get my folio into recovery one way or another? Data is lost already, so that’s no problem anymore in this case.
Fastboot command is: fastboot flash recovery recovery.x.y.z.img ... not flash_image recovery.img (name of the recovery ofc)
Ics ? CM9? If so just read the tutorial on the topic related its simple as hell...
Also best way to start an new: fast boot erase Linux/recovery/system/cache/userdata one after another then fastboot reboot (remove USB before it reboot) check the folio say magic mismatch error then reboot pressing long on power(6sec) then the recovery command.
Sent from my folio100 using XDA Premium HD app
Thanks but...
ReiverBlade said:
Fastboot command is: fastboot flash recovery recovery.x.y.z.img ... not flash_image recovery.img (name of the recovery ofc)
Ics ? CM9? If so just read the tutorial on the topic related its simple as hell...
Also best way to start an new: fast boot erase Linux/recovery/system/cache/userdata one after another then fastboot reboot (remove USB before it reboot) check the folio say magic mismatch error then reboot pressing long on power(6sec) then the recovery command.
Sent from my folio100 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks, but this isn't the solution. The main problem is that I can't get my Folio into fastboot/recovery mode anymore. After that updating is simple. Done it several times before. Do you have a suggestion how I can get it into fastboot/recovery mode. ADB wont work either.
Regards Erik
Weird... hum im not home but i will check that( full keyboard is easier to answer xD)
Sent from my GT-I9000 using XDA
ErikSnippe said:
Thanks, but this isn't the solution. The main problem is that I can't get my Folio into fastboot/recovery mode anymore. After that updating is simple. Done it several times before. Do you have a suggestion how I can get it into fastboot/recovery mode. ADB wont work either.
Regards Erik
Click to expand...
Click to collapse
Remove the sdcard!
Remove SD Card
stefannsv said:
Remove the sdcard!
Click to expand...
Click to collapse
I removed the external SD-card (to the right of the orange light). But that doesn't help. How can I remove the internal SD-card? I removed the back and the battery but I do not find a sd-card. Unmounting the internal SD-card doesn't do the trick either.
did You come in the recovery menu??
I think you flashed the ics withe the wrong recovery...
flash the old rom aigan (copy the update.zip in the sdcard and update the folio via recovery menu)
when that works, try aigan with fastboot to flash first boot, then recovery (but the right version!!)
stefannsv said:
did You come in the recovery menu??
I think you flashed the ics withe the wrong recovery...
flash the old rom aigan (copy the update.zip in the sdcard and update the folio via recovery menu)
when that works, try aigan with fastboot to flash first boot, then recovery (but the right version!!)
Click to expand...
Click to collapse
I think you're absolutely rigth about flashing the wrong recovery. Problem is that I can't come into a recovery menu (power + vol up). Fastboot won't work either (3xpower + vol up). I've used both before, so the configuration on my pc is right. Now al I have to do is boot into recovery or into fastboot. That's my problem, flashing with the working Honeycomb-version is no problem at al when I get into the recovery menu. Do you no what happens if I delete the complete /system/-directory on my folio? Is that an option to force the tab into recovery?
...and how want you delete the complete sys? do you mean with root explorer in rw-option?? thats very dangerous...can't you flash with rom manager?
Rom Manager
stefannsv said:
...and how want you delete the complete sys? do you mean with root explorer in rw-option?? thats very dangerous...can't you flash with rom manager?
Click to expand...
Click to collapse
I can access the internal sd-card using ADB. This way I should be able to delete/move/copy files. After puting the system-partionion in RW-state. In Adb shell the command "flash_image recover recover.img" gives an error "erros scanning partitions: No such file or directory". The image files exists! So I'm stuck there too.
I tried to use rommanager. It work once when i was installing ICS. After this it won't boot into recovery. When I use "Flash clockworkmod recovery" in Rommanager v5.0.0.6 i only get the following phone models: Advent Vega, Elocity A7, LG/T-mobile G2X, LGE Optimus 2x, Motorolo XOOM and Viewsonic Gtablet (smb_a1002) - bootloader 1.1. I tried all the phone models, but all they do is reboot the tablet. No choice will boot into recovery. Also tried clockworkmod recovery 2.5.1.4 but also no succes.
I do not know how to install clockworkmod 3.0.0.5 for Folio. I only can find an option to install it using recovery menu or fastboot. And both won't work on my tablet.
and you have put the recover.img file in the fastboot directory?
stefannsv said:
and you have put the recover.img file in the fastboot directory?
Click to expand...
Click to collapse
Where can i find the fastboot directory?
Here I've ad complain the Problem:
http://forum.xda-developers.com/showpost.php?p=23715985&postcount=467
the fastbootdirectory is in android-sdk-windows\platform-tools
There is the fastboot.exe too.
Put the two files in that directory, connect yout folio via usb in fastboot modus with your pc or laptop, make the described commands at windows shell.
stefannsv said:
Here I've ad complain the Problem:
http://forum.xda-developers.com/showpost.php?p=23715985&postcount=467
the fastbootdirectory is in android-sdk-windows\platform-tools
There is the fastboot.exe too.
Put the two files in that directory, connect yout folio via usb in fastboot modus with your pc or laptop, make the described commands at windows shell.
Click to expand...
Click to collapse
Still the main problem is that I can't put my folio into fastbootmode via usb.
so far only 2 things prevent my folio to go into fastboot: power cord and/or mini usb unplugged.
also you talk about removing internal SD but you know what they reffere as internal SD is : a chip soldered on the motherboard?Right?
one more thing lets make it clear: fasboot directory isnt fixed, for the sake of accessibility you can put it like me C:\tools_X
also renaming recovery5.0.0.4.img (the one from nopy) into recoveryA.img (i wonder if your error come because you write the wrong commande or if its because of recover.img instead of the right name for the file.)
last option before saying: you F***ed up your tablet if nothing mentioned above works
also side note: every answer from you after a recommendation from a user : contain a new error \\\ important your problem come from : not being able to go into fastboot mode or not being able to flash the recovery via fastboot (either due to : you putting the recovery img not in the right directory or input the wrong command) its important since 1st one is prolly f.u.b.a.r and the second one is recoverable by reading and doing step by step whats explain *exactely what is explain*
the only right command is : "fastboot flash recovery *name of the recovery*.img" and not Flash_recover recover.img as you write it 2 time now
Sent from my folio100 using XDA Premium HD app
ReiverBlade said:
so far only 2 things prevent my folio to go into fastboot: power cord and/or mini usb unplugged.
also you talk about removing internal SD but you know what they reffere as internal SD is : a chip soldered on the motherboard?Right?
one more thing lets make it clear: fasboot directory isnt fixed, for the sake of accessibility you can put it like me C:\tools_X
also renaming recovery5.0.0.4.img (the one from nopy) into recoveryA.img (i wonder if your error come because you write the wrong commande or if its because of recover.img instead of the right name for the file.)
last option before saying: you F***ed up your tablet if nothing mentioned above works
also side note: every answer from you after a recommendation from a user : contain a new error \\\ important your problem come from : not being able to go into fastboot mode or not being able to flash the recovery via fastboot (either due to : you putting the recovery img not in the right directory or input the wrong command) its important since 1st one is prolly f.u.b.a.r and the second one is recoverable by reading and doing step by step whats explain *exactely what is explain*
the only right command is : "fastboot flash recovery *name of the recovery*.img" and not Flash_recover recover.img as you write it 2 time now
Sent from my folio100 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for your help,
the fastboot command fastboot flash recovery......... doesn't work. My pc keeps waiting for the device. Which is to be expected while i can't boot my folio into fastboot-mode. The command i used before is in adb shell.
Can you tell me where to put recovery.img exactly on my folio? And what i should do after i,ve put it there. I can use a root-explorer on my folio and i can use adb push ...... to move or copy files. Also mounting system in rw-mode is no problem anymore. My folio is rooted and i can use it as root or su in adb-shell.
ErikSnippe said:
Thanks for your help,
the fastboot command fastboot flash recovery......... doesn't work. My pc keeps waiting for the device. Which is to be expected while i can't boot my folio into fastboot-mode. The command i used before is in adb shell.
Can you tell me where to put recovery.img exactly on my folio? And what i should do after i,ve put it there. I can use a root-explorer on my folio and i can use adb push ...... to move or copy files. Also mounting system in rw-mode is no problem anymore. My folio is rooted and i can use it as root or su in adb-shell.
Click to expand...
Click to collapse
Don't put the recovery.img into the folio! Copy it to your pc. In the folder where the fastboot.exe is. Then start your folio an go in the fastboot modus (power and three times volume up)
Connect your folio via mini-usb with your pc and open a windows shell(cmd).
Now type
fastboot erase recovery
Fastboot flash recovery nameoftherecoveryfile
stefannsv said:
Don't put the recovery.img into the folio! Copy it to your pc. In the folder where the fastboot.exe is. Then start your folio an go in the fastboot modus (power and three times volume up)
Connect your folio via mini-usb with your pc and open a windows shell(cmd).
Now type
fastboot erase recovery
Fastboot flash recovery nameoftherecoveryfile
Click to expand...
Click to collapse
I can't get into fastboot-mode with my folio!!!!!!! That's the whole problem. The pc stays waiting for the device!
ErikSnippe said:
I can't get into fastboot-mode with my folio!!!!!!! That's the whole problem. The pc stays waiting for the device!
Click to expand...
Click to collapse
install PDANet on your pc
ErikSnippe said:
I can't get into fastboot-mode with my folio!!!!!!! That's the whole problem. The pc stays waiting for the device!
Click to expand...
Click to collapse
Is the problem the fastboot modus at the folio or the connection to your pc?
Hello being the noob i am i cannot restore any roms to my prime i accedntally wiped the whole internal partition and currently only have twrp installed it is version 2.2.0 i cant seem to get it to show in windows nor do i know the command in twrp for the sd card as i have a rom on there but it wont let me access it. im pulling my hair out and at the moment my prime wont swich off as it just keeps turning itself on and going to the ee pad logo and stopping there
can someone please help me to get it working again its probably simple but ive about had enough !! also cant get adb to work as the drivers keep faling to install on my pc error 10
HELP !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Slight update used wsg unbricker and now running clockwork mod instead of twrp dont know if thats good or bad at lest it proves pushing stuff to it works to a degree
Uberjim said:
Hello being the noob i am i cannot restore any roms to my prime i accedntally wiped the whole internal partition and currently only have twrp installed it is version 2.2.0 i cant seem to get it to show in windows nor do i know the command in twrp for the sd card as i have a rom on there but it wont let me access it. im pulling my hair out and at the moment my prime wont swich off as it just keeps turning itself on and going to the ee pad logo and stopping there
can someone please help me to get it working again its probably simple but ive about had enough !! also cant get adb to work as the drivers keep faling to install on my pc error 10
HELP !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Slight update used wsg unbricker and now running clockwork mod instead of twrp dont know if thats good or bad at lest it proves pushing stuff to it works to a degree
Click to expand...
Click to collapse
Still trying to fix this I now have no recovery and just get the two icons wipe data and fast boot or it just keeps trying to load a Rom that isn't there so it sticks on the main logo screen if I could get it to show in windows that would be great but now I have no recovery I'm not sure how to even get it to install anything once I do !
deleted
As long as you have the fastboot logo, there should be hope. First, you will need to do whatever you can to get your computer to recognize fastboot mode. In order to do this, click on the fastboot icon on your prime and then plug your usb into your pc. What does windows say? Is the device showing in the windows device manager?
Sent from my SO-01C using xda app-developers app
kokopuphz said:
As long as you have the fastboot logo, there should be hope. First, you will need to do whatever you can to get your computer to recognize fastboot mode. In order to do this, click on the fastboot icon on your prime and then plug your usb into your pc. What does windows say? Is the device showing in the windows device manager?
Sent from my SO-01C using xda app-developers app
Click to expand...
Click to collapse
It shows up but then says failed to install driver will try it on different pc,s see if it works thanks for the replies seems fairly easy
Ive found on my device that it sometimes requests two different drivers. One for adb/fastboot, and one for mtp. I just cancel the one for mtp as they are not in the naked driver set, and windows then detects another different device.
Sent from my SO-01C using xda app-developers app
okay fast boot is working and the android bootloader device shows in installed drivers but when i type in adb devices nothing shows up ?
Uberjim said:
okay fast boot is working and the android bootloader device shows in installed drivers but when i type in adb devices nothing shows up ?
Click to expand...
Click to collapse
Okay, you're half way home! The reason why nothing shows in adb is because fastboot and adb are two completely different interfaces. When in fastboot, your device will be expecting the fastboot command only.
Now what you will have to do is find a recovery that is in the blob format. Cwm would probably be okay. Twrp would be good, however the new version requires the nvflash version of the bootloader.
Once you find the blob of the recovery you want, place this in the same folder as the file fastboot.exe
It should be in the same place as adb. If not, place the blob somewhere easy to remember.
Then in a command prompt, type
fastboot -i 0x0b05 flash recovery blobfilename
If you placed the blob in the same place as fastboot, then the above will be the blob filename, or better would be to include the path as well.
Sent from my SO-01C using xda app-developers app
Looks like this could help
http://forum.xda-developers.com/showthread.php?t=1662158
Sent from my PadFone using Tapatalk 2
hi guys and girls happy to report that thanks to the community my prime is aliiiive !!! used a utility off here called knives and forks to install adb and then downloaded fast boot and extracted to my users directory then used the fast boot command to push the blob to the prime into recovery then used adb push adb push virtuous_prime_s_9.4.2.21_v1.zip /sdcard/ and installed virtuous to get it running then it all shows up thankyou to everyone so happy took all of five minutes lol. my trip to london for 3 hours will be less boring now !!!:laugh::highfive:
Hi Xda members, I edited the touchpad.cfg file because i wanted to remove the water protection.. so when the phone started again the screen became totally unresponsive, i wanted to make a wipe but when i go to Android recovery shows an error saying "Failed to boot 2", is there a way to wipe the phone with all this problems? also i wanted to replace the file with the old one with adb or Android commander but the phone is not recognized on the pc because is pattern locked..
disjes said:
Hi Xda members, I edited the touchpad.cfg file because i wanted to remove the water protection.. so when the phone started again the screen became totally unresponsive, i wanted to make a wipe but when i go to Android recovery shows an error saying "Failed to boot 2", is there a way to wipe the phone with all this problems? also i wanted to replace the file with the old one with adb or Android commander but the phone is not recognized on the pc because is pattern locked..
Click to expand...
Click to collapse
Try using fastboot/adb to replace the touchpad.cfg file with a backup file, then reboot. If you're not sure how to use that try searching the forums or Google it. I really hope you have a copy of the original as that is the fastest way to replace that file and reboot. Hopefully that fixes your issue.
KillerKellerjr said:
Try using fastboot/adb to replace the touchpad.cfg file with a backup file, then reboot. If you're not sure how to use that try searching the forums or Google it. I really hope you have a copy of the original as that is the fastest way to replace that file and reboot. Hopefully that fixes your issue.
Click to expand...
Click to collapse
Hi KillerKellerjr, i've got a problem with fastboot, when i select fastboot it gets stucked in starting fastboot protocol support and adb does not recognize it.. drivers are already installed..
So I recently pulled my G Watch back out and installed the most recent OTA 6.0.1, installed TWRP, the custom kernel, and rooted it. Obviously all of that required ADB to function correctly. It did perfectly. I installed ADB using the 15 Second ADB Installer, and used WinDroid Toolkit to flash TWRP and get into recovery and do the rest, that by default installed the ClockworkMod ADB drivers, all of this on my Windows 10 PC.
Those drivers worked perfectly. Until today.
I did a fresh install of CM13 on my Nexus 5 phone, which my watch was paired to at the time. I wiped everything and started over, so I then went into my watches settings and did the Factory Reset so I could start fresh and resync up with my new rom install on my phone.
But when I try to connect via ADB or even try to list the devices it always states "Unauthorized"...
For whatever reason, no matter what I try it wont bring up the prompt on my phone to authorize this computer.
I revoked Debug permissions on both my watch and my phone, tried different usb ports, turned off and on debugging in all its forms on both my watch and phone, plus restarted all my devices and my PC. I have tried google's adb drivers as well.
Not sure what else there is to possibly try, seems I have covered all my bases here. Just doesn't make sense that it worked and now all the sudden it doesn't...
Glad I'm not the only one having this problem! I've tried same exact methods you mentioned with no luck. Hopefully someone knows what's going on here and provide a solution
Maybe deleting the keys in the computer will fix it. If it works with another computer, then it's the solution. On Mac, they are stored in a folder called .android in the home folder, if I recall correctly. Anyway it should be easy to find online how to delete the keys in the OS you're using.
What I did was first authorise my phone to my pc's adb then I copied adb_keys from /data/misc/adb/ on my phone to my pc. I then copied that while in TWRP on my LG G watch to the same directory /data/misc/adb/ and rebooted to system and voila adb access restored!
Thanks for your suggestions guys, but I officially give up figuring this out. Tried other computers and it still says "unauthorized." Tried both Windows 10 and Ubuntu and still the same error. Some thing's definitely happened since Wear 6.0 update or maybe invisible kernel for 6.0?
@Xmaster24 I would try your TWRP way, but I never installed it as I didn't see the need for it. I don't think there's a way to install it now without ADB, is there?
xymic said:
Thanks for your suggestions guys, but I officially give up figuring this out. Tried other computers and it still says "unauthorized." Tried both Windows 10 and Ubuntu and still the same error. Some thing's definitely happened since Wear 6.0 update or maybe invisible kernel for 6.0?
@Xmaster24 I would try your TWRP way, but I never installed it as I didn't see the need for it. I don't think there's a way to install it now without ADB, is there?
Click to expand...
Click to collapse
adb is absolutely not required. seeing as you are running 6.0.1 get the custom TWRP from my root guide here and follow the instructions on flashing the recovery. Seeing as you don't have adb you will just have to power off your watch and boot it up and swipe top left to bottom right as soon as you see something
Xmaster24 said:
adb is absolutely not required. seeing as you are running 6.0.1 get the custom TWRP from my root guide here and follow the instructions on flashing the recovery. Seeing as you don't have adb you will just have to power off your watch and boot it up and swipe top left to bottom right as soon as you see something
Click to expand...
Click to collapse
Aaaaaand we're back, Houston! Thanks a lot man. Works great now.
Hello
I have the same problem as author of this thread. How can I get authorize adb? I need it to push some files to internal memory.
I suffer the same problem.
Ok, I found solove for this problem. Just what you need is back to stock for example by this method: http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863 or manually("fastboot flash" command): http://forum.xda-developers.com/g-watch/development/how-to-to-stock-rooted-6-0-t3339875 If you will have bootloop, you need to factory reset in twrp and reboot. To boot into twrp when you have bootloop you must enter to bootloader mode and write in cmd "fastboot boot YourTwrpName.img" command. I used twrp from this topic: http://forum.xda-developers.com/g-watch/development/guide-how-to-root-lg-g-watch-6-0-1-t3320512 After all you can update your watch to actual android wear version and again root/ change kernel.
Sorry for my bad english. I am not native speaker.
koszanty said:
Ok, I found solove for this problem. Just what you need is back to stock for example by this method: http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863 or manually("fastboot flash" command): http://forum.xda-developers.com/g-watch/development/how-to-to-stock-rooted-6-0-t3339875 If you will have bootloop, you need to factory reset in twrp and reboot. To boot into twrp when you have bootloop you must enter to bootloader mode and write in cmd "fastboot boot YourTwrpName.img" command. I used twrp from this topic: http://forum.xda-developers.com/g-watch/development/guide-how-to-root-lg-g-watch-6-0-1-t3320512 After all you can update your watch to actual android wear version and again root/ change kernel.
Sorry for my bad english. I am not native speaker.
Click to expand...
Click to collapse
Sorry, but, with ADB in "unauthorized" state it can't be done.
Guys, read Xmaster24's posts in first page. That's how I fixed it.
turbomann said:
Sorry, but, with ADB in "unauthorized" state it can't be done.
Click to expand...
Click to collapse
Why? Fastboot is diffrent thing than adb and it should work without 'adb authorization'. I used this method and it worked for me.
xymic said:
Guys, read Xmaster24's posts in first page. That's how I fixed it.
Click to expand...
Click to collapse
If you don't have copy of adb keys on watch sdcard, probably you cant use his fix(or am I wrong?). By the way, how can I mange files in TWRP mode without working adb? In TWRP is special option/ command for mange files by PC or something like that? If I connect watch to PC I can't see it as mass storage.
koszanty said:
Why? Fastboot is diffrent thing than adb and it should work without 'adb authorization'. I used this method and it worked for me.
If you don't have copy of adb keys on watch sdcard, probably you cant use his fix(or am I wrong?). By the way, how can I mange files in TWRP mode without working adb? In TWRP is special option/ command for mange files by PC or something like that? If I connect watch to PC I can't see it as mass storage.
Click to expand...
Click to collapse
You had flash 5.1.1 and then upgrade to 6.0.1? Are there bootloader compatible?
koszanty said:
If you don't have copy of adb keys on watch sdcard, probably you cant use his fix(or am I wrong?). By the way, how can I mange files in TWRP mode without working adb? In TWRP is special option/ command for mange files by PC or something like that? If I connect watch to PC I can't see it as mass storage.
Click to expand...
Click to collapse
You only need to have adb_keys file on the phone not the watch. In my case, I was able to use adb perfectly fine while I was in TWRP. Basically here's what I did:
1. Copy adb_keys file from your phone to computer. It is located in /data/misc/adb. If you can't see the file, you probably have to authorize your phone first with your computer.
2. Flash TWRP recovery from XMaster24's link using fastboot on your watch.
3. Boot into recovery. You don't need go into any options. While on the recovery homescreen, Just use this command to transfer adb_keys file into your watch:
Code:
adb push adb_keys /data/misc/adb
You can check using "Files" option in recovery to see if the file is transferred into the watch.
4. Reboot your watch and you should be able to access adb now.
You can do it your way as well, but using xmaster24's method saves time, I think
xymic said:
You only need to have adb_keys file on the phone not the watch. In my case, I was able to use adb perfectly fine while I was in TWRP. Basically here's what I did:
1. Copy adb_keys file from your phone to computer. It is located in /data/misc/adb. If you can't see the file, you probably have to authorize your phone first with your computer.
2. Flash TWRP recovery from XMaster24's link using fastboot on your watch.
3. Boot into recovery. You don't need go into any options. While on the recovery homescreen, Just use this command to transfer adb_keys file into your watch:
Code:
adb push adb_keys /data/misc/adb
You can check using "Files" option in recovery to see if the file is transferred into the watch.
4. Reboot your watch and you should be able to access adb now.
You can do it your way as well, but using xmaster24's method saves time, I think
Click to expand...
Click to collapse
In my case adb doesn't worked at all
turbomann said:
You had flash 5.1.1 and then upgrade to 6.0.1? Are there bootloader compatible?
Click to expand...
Click to collapse
It's compatibile but can occur bootloop. If you will have bootloop, you must do that what I write some posts earlier.
I'm realised that my phone with MM do the same bug, unauthorized, I look for adb_keys file but folder ADB is empty, then only remains flash and update on the watch.
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