Related
Hi guys,
I would really appreciate any help getting out of this pickle (my first time trying to install a ROM).
Here's the situation:
- Running a Huawei P6-C00 Chinese phone
- Was interested in trying a custom ROM (e.g. CleanRom by @surdu_petru) in order to enable Google Apps
- Updated normally to B120 CN as instructed
- Rooted (using Root Wizard)
- Installed customer recovery (TWRP 2.6.3.3)
- Started flash process including advanced wipe in TWRP... wiped system, cache, davlik, etc... :crying:
- Realized that I didn't have the ROM .zip copied to the phone yet
Currently, I'm able to boot into TWRP but cannot connect using adb for sideload (TWRP just says starting sideload but never connects). What do you guys recommend? I don't have a backup of any working ROM or the stock image.
Is there a way to initiate a "standard" restore since I wiped all the caches? ...
Are there some tricks to getting ADB running so I can try to sideload the ROM again? ...
P6-C00 does not have an SD card, but is it possible to load the ROM onto a USB and read it from TWRP?
Thanks for any help!
Did u try connecting to adb?
Sent from my U9200 using XDA Premium 4 mobile app
some help
onetree said:
Hi guys,
I would really appreciate any help getting out of this pickle (my first time trying to install a ROM).
Here's the situation:
- Running a Huawei P6-C00 Chinese phone
- Was interested in trying a custom ROM (e.g. CleanRom by @surdu_petru) in order to enable Google Apps
- Updated normally to B120 CN as instructed
- Rooted (using Root Wizard)
- Installed customer recovery (TWRP 2.6.3.3)
- Started flash process including advanced wipe in TWRP... wiped system, cache, davlik, etc... :crying:
- Realized that I didn't have the ROM .zip copied to the phone yet
Currently, I'm able to boot into TWRP but cannot connect using adb for sideload (TWRP just says starting sideload but never connects). What do you guys recommend? I don't have a backup of any working ROM or the stock image.
Is there a way to initiate a "standard" restore since I wiped all the caches? ...
Are there some tricks to getting ADB running so I can try to sideload the ROM again? ...
P6-C00 does not have an SD card, but is it possible to load the ROM onto a USB and read it from TWRP?
Thanks for any help!
Click to expand...
Click to collapse
you can try it whith a linux pc (ubuntu)
i have the same problem
good luck!
onetree said:
Hi guys,
I would really appreciate any help getting out of this pickle (my first time trying to install a ROM).
Here's the situation:
- Running a Huawei P6-C00 Chinese phone
- Was interested in trying a custom ROM (e.g. CleanRom by @surdu_petru) in order to enable Google Apps
- Updated normally to B120 CN as instructed
- Rooted (using Root Wizard)
- Installed customer recovery (TWRP 2.6.3.3)
- Started flash process including advanced wipe in TWRP... wiped system, cache, davlik, etc... :crying:
- Realized that I didn't have the ROM .zip copied to the phone yet
Currently, I'm able to boot into TWRP but cannot connect using adb for sideload (TWRP just says starting sideload but never connects). What do you guys recommend? I don't have a backup of any working ROM or the stock image.
Is there a way to initiate a "standard" restore since I wiped all the caches? ...
Are there some tricks to getting ADB running so I can try to sideload the ROM again? ...
P6-C00 does not have an SD card, but is it possible to load the ROM onto a USB and read it from TWRP?
Thanks for any help!
Click to expand...
Click to collapse
Did you try it with fastboot?
Gesendet von meinem P6-U06 mit Tapatalk
ext4
taaeem said:
Did you try it with fastboot?
Gesendet von meinem P6-U06 mit Tapatalk
Click to expand...
Click to collapse
i know that he must use a linux pc that for the drivers
ext4 If say it right...
taaeem said:
Did you try it with fastboot?
Click to expand...
Click to collapse
Hi Taaeem,
Thanks for the hint. I read some posts on fastboot and tried the following, but could not get into fastboot mode.
Methods I tried
- Power off phone and then power on while holding vol-down button
- Select Reboot -> System option from TWRP, while holding volume down
- Select Reboot -> Bootloader option from TWRP
From what I understand, fastboot mode should be run from the /boot partition, which I didn't wipe. So any ideas how I can get into fastboot mode?
Thanks again!
Okay, I confirmed that I have at least some kind of fastboot access because I tried "fastboot reboot-bootloader" from command prompt on my PC, and it rebooted the phone (but the phone stayed on boot logo).
- Next time I get fastboot, should I run "fastboot flash [partition] [ROM-file.zip]"?
- If so, what partition should I specify? I'm confused about where this command will send the ROM file, and if so how do I find it from TWRP later on in order to install it?
Thank you!
One more update:
- Even though I'm stuck at boot logo when I try to enter fastboot mode, it looks like there is a somewhat working fastboot connection. I tried running "fastboot flash [partition] ROM.zip" but it fails after 16s ("remote: flash write failure" or "remote: partition does not exist"). I tried flashing to cache / data / system
Should I try @N!ELS huawei p6 suggestion of accessing by Linux? (I don't have one nearby) or am I using fastboot wrong?
Thanks!!
Also:
- I noticed that when I boot into TWRP the device shows as "..." in my system tray USB devices list.
- When I try to boot into fastboot mode, the device shows as "Android Sooner Single ADB Interface" (but phone is still stuck on boot logo)
- However I'm still not able to connect using ADB .. shows "error: device not found" in all cases)
- Finally, after powering off the phone does show the stock charging animation, which gives me hope that this can still be saved :crying:
onetree said:
One more update:
- Even though I'm stuck at boot logo when I try to enter fastboot mode, it looks like there is a somewhat working fastboot connection. I tried running "fastboot flash [partition] ROM.zip" but it fails after 16s ("remote: flash write failure" or "remote: partition does not exist"). I tried flashing to cache / data / system
Should I try @N!ELS huawei p6 suggestion of accessing by Linux? (I don't have one nearby) or am I using fastboot wrong?
Thanks!!
Also:
- I noticed that when I boot into TWRP the device shows as "..." in my system tray USB devices list.
- When I try to boot into fastboot mode, the device shows as "Android Sooner Single ADB Interface" (but phone is still stuck on boot logo)
- However I'm still not able to connect using ADB .. shows "error: device not found" in all cases)
- Finally, after powering off the phone does show the stock charging animation, which gives me hope that this can still be saved :crying:
Click to expand...
Click to collapse
fastboot mode on the P6 doesn't have any kind of ui for fastboot, so it stays on the boot logo, fastboot should work fine.
You could always find an USB OTG cable and connect a FAT32 partitioned mem stick with the .zip on it, TWRP allows flashing from USB memory as far as I know
You are definetely not out of hope, but im not sure about the compability of P6-U06 roms with the C00 variant.
onetree said:
One more update:
- Even though I'm stuck at boot logo when I try to enter fastboot mode, it looks like there is a somewhat working fastboot connection. I tried running "fastboot flash [partition] ROM.zip" but it fails after 16s ("remote: flash write failure" or "remote: partition does not exist"). I tried flashing to cache / data / system
Click to expand...
Click to collapse
Obviously you can't flash the whole zip file to every partition, infact you can't flash a .zip at all, atleast not in fastboot mode, .img extension is used. So don't try flashing the rom manually via fastboot, since you have a high risk of actually bricking the device, if not in the right hands.
Also when booted into TWRP, try "adb devices" in the cmd see if anything shows up.
onetree said:
One more update:
- Even though I'm stuck at boot logo when I try to enter fastboot mode, it looks like there is a somewhat working fastboot connection. I tried running "fastboot flash [partition] ROM.zip" but it fails after 16s ("remote: flash write failure" or "remote: partition does not exist"). I tried flashing to cache / data / system
Should I try @N!ELS huawei p6 suggestion of accessing by Linux? (I don't have one nearby) or am I using fastboot wrong?
Thanks!!
Also:
- I noticed that when I boot into TWRP the device shows as "..." in my system tray USB devices list.
- When I try to boot into fastboot mode, the device shows as "Android Sooner Single ADB Interface" (but phone is still stuck on boot logo)
- However I'm still not able to connect using ADB .. shows "error: device not found" in all cases)
- Finally, after powering off the phone does show the stock charging animation, which gives me hope that this can still be saved :crying:
Click to expand...
Click to collapse
Okay that's good when you are stuck at the logo and you can see your device at your PC you are in fastboot mode, from here you can work with fastboot commands NOT with ADB that will not work. Anyway isn't there a option in TWRP where you can mount your device to USB when that work you can just copy the files on your phone without to go with fastboot. When that don't work you must try to extract the .zip from the ROM you want to install and flash every image with fastboot I think that should work.
Gesendet von meinem P6-U06 mit Tapatalk
tauio111 said:
fastboot mode on the P6 doesn't have any kind of ui for fastboot, so it stays on the boot logo, fastboot should work fine.
You could always find an USB OTG cable and connect a FAT32 partitioned mem stick with the .zip on it, TWRP allows flashing from USB memory as far as I know
You are definetely not out of hope, but im not sure about the compability of P6-U06 roms with the C00 variant.
Obviously you can't flash the whole zip file to every partition, infact you can't flash a .zip at all, atleast not in fastboot mode, .img extension is used. So don't try flashing the rom manually via fastboot, since you have a high risk of actually bricking the device, if not in the right hands.
Also when booted into TWRP, try "adb devices" in the cmd see if anything shows up.
Click to expand...
Click to collapse
Okay so now I'm a bit paranoid about hard-bricking the device, and would rather not try my luck on a ROM that isn't approved for the P6-C00, haha...
At this point I just want to get a working OS installed (restore to the default for P6-C00 phone, even), and then maybe try to safely enable Google Apps. Any suggestions on how I can get this restored?
- I think the device came with a USB cable that is OTG.
- Seems like fastboot is also working, even though "fastboot getvar xxx" returns nothing useful
- ADB does not work while booted into TWRP (can't run shell, sideload, or list devices)
onetree said:
Okay so now I'm a bit paranoid about hard-bricking the device, and would rather not try my luck on a ROM that isn't approved for the P6-C00, haha...
At this point I just want to get a working OS installed (restore to the default for P6-C00 phone, even), and then maybe try to safely enable Google Apps. Any suggestions on how I can get this restored?
- I think the device came with a USB cable that is OTG.
- Seems like fastboot is also working, even though "fastboot getvar xxx" returns nothing useful
- ADB does not work while booted into TWRP (can't run shell, sideload, or list devices)
Click to expand...
Click to collapse
Download this rom for example https://disk.yandex.com/public/?hash=bhDlIAc5AqKh4RAB2IdatPdEfYVI9FH/Zky/UTGcH3M=
Extract the .z7 and run the flash_all.bat, this scripts flashes the rom via fastboot and you should get your device back up and running again. And from there you can update to a newer firmware version without problems.
If the bat doesn't work try this:
boot to fastboot
fastboot flash system system.img
fastboot flash cust cust.img
fastboot reboot recovery
Wipe cache and dalvik cache in twrp
tauio111 said:
Download this rom for example https://disk.yandex.com/public/?hash=bhDlIAc5AqKh4RAB2IdatPdEfYVI9FH/Zky/UTGcH3M=
Extract the .z7 and run the flash_all.bat, this scripts flashes the rom via fastboot and you should get your device back up and running again. And from there you can update to a newer firmware version without problems.
If the bat doesn't work try this:
boot to fastboot
fastboot flash system system.img
fastboot flash cust cust.img
fastboot reboot recovery
Wipe cache and dalvik cache in twrp
Click to expand...
Click to collapse
Thank you! I will try this tonight after work
tauio111 said:
Download this rom for example https://disk.yandex.com/public/?hash=bhDlIAc5AqKh4RAB2IdatPdEfYVI9FH/Zky/UTGcH3M=
Extract the .z7 and run the flash_all.bat, this scripts flashes the rom via fastboot and you should get your device back up and running again. And from there you can update to a newer firmware version without problems.
If the bat doesn't work try this:
boot to fastboot
fastboot flash system system.img
fastboot flash cust cust.img
fastboot reboot recovery
Wipe cache and dalvik cache in twrp
Click to expand...
Click to collapse
Thanks, tauio111! That worked and I now have a working phone again :victory:
I'm going to be a bit more careful about how to enable Google Apps... this is too much stress during the workweek haha.
Later on what do you think my best option would be?
- Wait for a confirmed easy to install ROM for P6-C00 that supports Google Apps
- Some other way to enable Google Apps with the standard firmware, since I am rooted?
Thanks :laugh:
onetree said:
Thanks, tauio111! That worked and I now have a working phone again :victory:
I'm going to be a bit more careful about how to enable Google Apps... this is too much stress during the workweek haha.
Later on what do you think my best option would be?
- Wait for a confirmed easy to install ROM for P6-C00 that supports Google Apps
- Some other way to enable Google Apps with the standard firmware, since I am rooted?
Thanks :laugh:
Click to expand...
Click to collapse
Easy, flash this via TWRP
tauio111 said:
Easy, flash this via TWRP
Click to expand...
Click to collapse
Thanks @tauio111 and everyone else who helped debug this.
I flashed stock recovery, updated official firmware to B120, re-flashed TWRP, flashed gapps, and now have a working phone with Gmail and Play Store!! :silly:
tauio111 said:
Download this rom for example https://disk.yandex.com/public/?hash=bhDlIAc5AqKh4RAB2IdatPdEfYVI9FH/Zky/UTGcH3M=
Extract the .z7 and run the flash_all.bat, this scripts flashes the rom via fastboot and you should get your device back up and running again. And from there you can update to a newer firmware version without problems.
If the bat doesn't work try this:
boot to fastboot
fastboot flash system system.img
fastboot flash cust cust.img
fastboot reboot recovery
Wipe cache and dalvik cache in twrp
Click to expand...
Click to collapse
I have the same problem and i do the same but nothing..
I tried to delete xposed installer and my phone stuck..
What can i do?
Edit:It s opened but i can t touch my screen.I try to put my password and i can t..
tauio111 said:
Download this rom for example (Removed to allow posting - faye2thesky)
Extract the .z7 and run the flash_all.bat, this scripts flashes the rom via fastboot and you should get your device back up and running again. And from there you can update to a newer firmware version without problems.
If the bat doesn't work try this:
boot to fastboot
fastboot flash system system.img
fastboot flash cust cust.img
fastboot reboot recovery
Wipe cache and dalvik cache in twrp
Click to expand...
Click to collapse
Heya Tauio111, I'm having the same problem as onetree and I've been frying my mind over this for the past 4 days before I came across your solution. I found that your link is no longer working, may I ask what that ROM is and where else I may find it? Thanks!
faye2thesky said:
Heya Tauio111, I'm having the same problem as onetree and I've been frying my mind over this for the past 4 days before I came across your solution. I found that your link is no longer working, may I ask what that ROM is and where else I may find it? Thanks!
Click to expand...
Click to collapse
A way that may help (i've done it with boot&recovery images). Using this tool http://forum.xda-developers.com/showthread.php?t=2433454 , might give you the *.img files necesary for flashing the stock rom through fast boot. All you need is to follow the instructions on the tool and have a stock rom (update.app file type), and some knowledge on how to use the fastboot.
Hi Guys,
I kinda did the same thing here.
I accidently wiped my system with TWRP v2.6.3.7
I also have a huawei ascend p6 u06
I didn't realize i never copied a rom to my device so i don't know how to install.
I can't seem to be able to use adb or fastboot and my device is not picked up by windows (8.1), it just says removable disk in my computer.
and under device manager it says P6-U06 under unknown devices.
I have tried to install a bunch of different drivers to attempt something but no luck.
Please help me.
Hi there,
I've been a bit of a [email protected] and fudged my Huawei P6. I Was on South African Vodacom Stock Jelly Bean Rom, read this forum and got so excited about the world out there that i thought, why don't i try flashing a rom, i've only bricked a sgs2 and lg-g2 before... I should know what to do by now (never done a day's computer course in my life!)!
So flashed kitkat beta and then tried to flash Kit Kat... I have left the phone for about a week in the hopes I'd come back to it & it would miraculously work as I've read a lot of the forum posts on here and have a gut feeling I'm screwed so hoping one of you Huawei P6 XDA Guru's can Help. From what I remember I did this...
1) Rooted the phone with SRS Root or Root Genius
2) After a few attemps managed to install official kitkat beta from dload/update.app from external SD Card so I could then install official Chinese KiTKAT rom or HYDRO Rom.
3) Played with the kitkat beta for a while all working (bar the beta crashes etc) ( I think at that point I intalled CWMOD or TWRP)
4) It was very late, I should have gone to bed, I'd had a few beers, but no I carried on & was planning to install Hydrorom & (Mis)understood got mixed up with official chinese kit kat rom installation
5) Booted into recovery & flashed official chinense kitkat rom with GAAPS ticked to flash as well (maybe that will tell you guys if I was using CWM or TWRP!)
5.0117...c) If my memory serves me right I didn't (4am idiot/tired/few beers/rushing etc) wipe dalvic or any of that... just flashed from external sd card ZIP streight over kitkat beta (aaaarrgh!)
6) Phone is now stuck in bootloop with Huawei Ascend words first, then loading a Huawei flower logo. Goes no further, just stays on until battery flat...
7) Left phone plugged into power with screen on for a day hoping it was just taking a while to flash rom... & nothing happened
8) Tried the following but hope I'm doing them all wrong and you GURU's will have a giggle at my comlete lack of skills:
a) reboot phone - no luckb) hold down power & +vol & -vol -... no luck just flower logo againc) every combination of power and two volume buttons - no luck just flower logod) putting folder dload/update.app on external sd card and using b)method to flash update - no luck just flower logoe) putting stock recovery.img on root of external sd card and doing b) - no luck just flower logof) putting all of extracted TWRP download " TWRP_Installer_20140414 on root folder of external sd card - no luckg) spending 4 hours finding a "how to remove the battery from huawei P6" link and watched a russian guy remove battery on you tube. Did that as read that can reset boot loader/recovery.... no luckh) downloaded various versions of Android SDK Tools. Phone shows up as a "please insert sd card" in windows file manager and appears "offline" when trying to access it from command prompt ADB etc
checked that HiSuite was stopped in Task Manager etc, reinstalled drivers etc. One problem I'm hoping you'll all say is 100% to blame for SDK Tools not working is I'm on latest update of Windows 8.1 64bit...
Edit: Read other forum... I see the red led when turning phone on as well...
Edit: Just installed propper android sdk tools not small made up file and now phone changed from showing "offline" to "unauthorised" in adb...
So, please help.
Fixed it
Ok managed to fix this and hope it will help others. Was up till 2am last night after deciding to give it another go after getting no replies! The main problem here must have been that as device was seen as unrecognized on PC and I couldn't get past boot screen so there was no way to allow debugging/authorize I.e. No pop up on phone as stuck in Hauwei flower screen.
Previously I Couldn't get fastboot or adb on PC to do anything, just kept saying phone was offline or unauthorized.
Rebooted phone from boot loop screen of huawei flower on screen holding power and - vol button for a long time until only boots to huawei ascend words logo (phone still plugged into PC), let go of both. PC makes sound to show there is USB device, now it doesn't boot the huawei flower screen just stays on the Hauwei ascend screen (I think normally this would open recovery etc), so maybe it is in recovery just not showing on screen... I don't know?!
Adb devices says no device however... And obviously no adb commands work at all...
However, fastboot commands for some reason work even though devices still shows nothing... so I tried various commands but what worked for me was typing the following in command promt on PC:
Fastboot flash boot boot.img (Stock)
Where all the img,zip,app files I was flashing were were in the platform-tools folder where adb and fastboot are.
Then
Fastboot flash recovery recovery.img. (Stock)
Then I think what did it, I was obviously on a broken twrp recovery... Was I flashed
Fastboot flash recovery twrp_2_6_3_3_recovery.img
To my amazement twrp touch recovery loaded and I could then go about wiping dalvik etc and reflashing all the correct files.
So I'm now finally running HYDROROM_V7
All the files I used are on the hydro rom page here so thanks to them for that! :
http://forum.xda-developers.com/showthread.php?t=2630208
Hope this works for all of you stuck in bootloop etc as I really thought my phone was stuffed!
Ciao
pommiesa said:
Ok managed to fix this and hope it will help others. Was up till 2am last night after deciding to give it another go after getting no replies! The main problem here must have been that as device was seen as unrecognized on PC and I couldn't get past boot screen so there was no way to allow debugging/authorize I.e. No pop up on phone as stuck in Hauwei flower screen.
Previously I Couldn't get fastboot or adb on PC to do anything, just kept saying phone was offline or unauthorized.
Rebooted phone from boot loop screen of huawei flower on screen holding power and - vol button for a long time until only boots to huawei ascend words logo (phone still plugged into PC), let go of both. PC makes sound to show there is USB device, now it doesn't boot the huawei flower screen just stays on the Hauwei ascend screen (I think normally this would open recovery etc), so maybe it is in recovery just not showing on screen... I don't know?!
Adb devices says no device however... And obviously no adb commands work at all...
However, fastboot commands for some reason work even though devices still shows nothing... so I tried various commands but what worked for me was typing the following in command promt on PC:
Fastboot flash boot boot.img (Stock)
Where all the img,zip,app files I was flashing were were in the platform-tools folder where adb and fastboot are.
Then
Fastboot flash recovery recovery.img. (Stock)
Then I think what did it, I was obviously on a broken twrp recovery... Was I flashed
Fastboot flash recovery twrp_2_6_3_3_recovery.img
To my amazement twrp touch recovery loaded and I could then go about wiping dalvik etc and reflashing all the correct files.
So I'm now finally running HYDROROM_V7
All the files I used are on the hydro rom page here so thanks to them for that! :
http://forum.xda-developers.com/showthread.php?t=2630208
Hope this works for all of you stuck in bootloop etc as I really thought my phone was stuffed!
Ciao
Click to expand...
Click to collapse
Hey very good that you managed to fix your problem, when I first read your question I didn't had any ideas on how to fix it. But you had a bootloop I think and when you press power and vol- until it reboots you come in the bootloader, on our device it only shows the bootlogo so its seems that it is stuck but actually you are in the boot loader and can use fastboot commands. So glad you fixed your problem.
Gesendet von meinem P6-U06
Hello!
I attempted to modify some system files (overwriting mine with LG v10 ones supplied in this thread: http://forum.xda-developers.com/g4/themes-apps/help-bringing-lg-v10s-camera-to-g4-t3223371) and my device ended up not going past the first boot screen (where the "Bootloader unlocked!" message appears).
Some facts:
- I have the H815 variant
- I have tried the drivers that come with LG Bridge and some others found on this forum.
- I have (officially) unlocked my bootloader, voiding my warranty
- The device gets stuck on the first boot screen (the one with text "Bootloader unlocked!"), led starts pulsing blue a second later.
- Logcat from boot is located at: pasteb in.com/64RZ3SgJ
- I have TWRP, but the press combination ( vol-down + power-button key, release for 1 sec, press them again) to boot into it doesn't work.
- I had Android 6.0 installed using the zip flashing method from recovery - with root.
- It does get past the first boot screen when I connect the micro-usb cable and it figures it has enough juice to turn on itself, but doesn't get past the boot animation then.
- I can access Download mode
- I tried flashing H81520A_00.kdz with LG Flash Tool 2014 (both normal and CSE mode), but it says: "Required info cannot be found. Contact the system administrator". Device doesn't react.
- I tried flashing older Europe Open H81510D.kdz with LG Flash Tool 2014, but it says: "Upgrade stopped due to an error." and wants me to try again (which didn't help). This message comes after a few seconds of attempting an upgrade to which my phone actually reacts - some text changes in download mode log box.
- (I did use LG Flash Tool 2014 in CDMA - DIAG mode)
- I tried using LG Update Recovery tool in LG Bridge. A similar error appeared making me retry the process, which doesn't work as well.
- Running any fastboot command yields in message: "< waiting for device >"
Please provide me with assistance as I've found other people with similar errors as well (even though their devices aren't bricked yet)
Edit 1: I discovered I had a short time window of ADB access after booting. I used the command "adb reboot recovery" and got into recovery mode. Will try to reflash system files.
Edit 2: Problem solved. Android booted up normally after reflashing the files. Gosh this was nerve-racking. Somebody should make a tutorial out of this.
Edit 3:
I was asked to write a more clear procedure, so here's my attempt. It is better than nothing. Again I suggest someone try to write a better explanation and verify that it works on other devices as well.
1. Have adb installed on your computer
2. Have the necessary drivers installed on your computer. I think I used these: http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
3. Have your phone turned completely off.
4. Test if adb works from the console, using the following command: "adb version"; if it doesn't google for how to add adb to system environment path.
5. Connect the computer and the device using a micro-usb cable. The device should detect that it is being charged and turn itself on, thinking that it has enough battery to do so. If it doesn't, do so yourself.
6. While the device is booting, you have (at least I had) a short time period while your device listens for commands. In console type the following command: "adb reboot recovery" (try this from immediately after the device starts booting until it works, if it doesn't try again). This should reboot your into recovery mode.
7. If you do not have system flashables on your device, google how to sideload zip files. Get them here: http://forum.xda-developers.com/g4/development/stock-h815-20a-stock-images-kdz-t3232282. Flash them (I flashed all, just in case, but system might be enough).
8. After flashing, you (if coming from any other rom) should clear data and cache as well.
9. Reboot the device and it should be working.
with flashtool impossible to rollback . and impossible to flash kdz 6.0... a lot of people with this issue
Somehow I managed to make adb recognize the device and provide me with logcat access. I posted the contents on pastebin: pasteb in.com/64RZ3SgJ
Edit: Problem solved. Description in 1st post.
gregor.eesmaa said:
Somehow I managed to make adb recognize the device and provide me with logcat access. I posted the contents on pastebin: pasteb in.com/64RZ3SgJ
Edit: Problem solved. Description in 1st post.
Click to expand...
Click to collapse
Could you write clear, detailed procedure ...
well thank you
---------- Post added at 09:05 PM ---------- Previous post was at 09:01 PM ----------
I have the same problem, I do not know how to go back
rotoko said:
Could you write clear, detailed procedure ...
well thank you
---------- Post added at 09:05 PM ---------- Previous post was at 09:01 PM ----------
I have the same problem, I do not know how to go back
Click to expand...
Click to collapse
There you go. Can't do any better as I am not an expert in how Android precisely works at this level.
have followed what you ahd done i.e try adb reboot recovery and can net get adb to find device
will try again later as not very well learned in android
uk h815
leegreggs said:
have followed what you ahd done i.e try adb reboot recovery and can net get adb to find device
will try again later as not very well learned in android
uk h815
Click to expand...
Click to collapse
Perhaps you should try running the command: "adb devices" to see whether it has connected until it has (just run it multiple times). Otherwise, are you experiencing same symptoms as me? Did you also overwrite the system with V10 files? I'm thinking that the time window was caused by the system attempting to read some media profiles while starting all the other processes behind.
gregor.eesmaa said:
Perhaps you should try running the command: "adb devices" to see whether it has connected until it has (just run it multiple times). Otherwise, are you experiencing same symptoms as me? Did you also overwrite the system with V10 files? I'm thinking that the time window was caused by the system attempting to read some media profiles while starting all the other processes behind.
Click to expand...
Click to collapse
No I've decided to go back to my LG g2 till either flashtool gets updated or till a tot & dll comes out
gregor.eesmaa said:
Hello!
I attempted to modify some system files (overwriting mine with LG v10 ones supplied in this thread: http://forum.xda-developers.com/g4/themes-apps/help-bringing-lg-v10s-camera-to-g4-t3223371) and my device ended up not going past the first boot screen (where the "Bootloader unlocked!" message appears).
Some facts:
- I have the H815 variant
- I have tried the drivers that come with LG Bridge and some others found on this forum.
- I have (officially) unlocked my bootloader, voiding my warranty
- The device gets stuck on the first boot screen (the one with text "Bootloader unlocked!"), led starts pulsing blue a second later.
- Logcat from boot is located at: pasteb in.com/64RZ3SgJ
- I have TWRP, but the press combination ( vol-down + power-button key, release for 1 sec, press them again) to boot into it doesn't work.
- I had Android 6.0 installed using the zip flashing method from recovery - with root.
- It does get past the first boot screen when I connect the micro-usb cable and it figures it has enough juice to turn on itself, but doesn't get past the boot animation then.
- I can access Download mode
- I tried flashing H81520A_00.kdz with LG Flash Tool 2014 (both normal and CSE mode), but it says: "Required info cannot be found. Contact the system administrator". Device doesn't react.
- I tried flashing older Europe Open H81510D.kdz with LG Flash Tool 2014, but it says: "Upgrade stopped due to an error." and wants me to try again (which didn't help). This message comes after a few seconds of attempting an upgrade to which my phone actually reacts - some text changes in download mode log box.
- (I did use LG Flash Tool 2014 in CDMA - DIAG mode)
- I tried using LG Update Recovery tool in LG Bridge. A similar error appeared making me retry the process, which doesn't work as well.
- Running any fastboot command yields in message: "< waiting for device >"
Please provide me with assistance as I've found other people with similar errors as well (even though their devices aren't bricked yet)
Edit 1: I discovered I had a short time window of ADB access after booting. I used the command "adb reboot recovery" and got into recovery mode. Will try to reflash system files.
Edit 2: Problem solved. Android booted up normally after reflashing the files. Gosh this was nerve-racking. Somebody should make a tutorial out of this.
Edit 3:
I was asked to write a more clear procedure, so here's my attempt. It is better than nothing. Again I suggest someone try to write a better explanation and verify that it works on other devices as well.
1. Have adb installed on your computer
2. Have the necessary drivers installed on your computer. I think I used these: http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
3. Have your phone turned completely off.
4. Test if adb works from the console, using the following command: "adb version"; if it doesn't google for how to add adb to system environment path.
5. Connect the computer and the device using a micro-usb cable. The device should detect that it is being charged and turn itself on, thinking that it has enough battery to do so. If it doesn't, do so yourself.
6. While the device is booting, you have (at least I had) a short time period while your device listens for commands. In console type the following command: "adb reboot recovery" (try this from immediately after the device starts booting until it works, if it doesn't try again). This should reboot your into recovery mode.
7. If you do not have system flashables on your device, google how to sideload zip files. Get them here: http://forum.xda-developers.com/g4/development/stock-h815-20a-stock-images-kdz-t3232282. Flash them (I flashed all, just in case, but system might be enough).
8. After flashing, you (if coming from any other rom) should clear data and cache as well.
9. Reboot the device and it should be working.
Click to expand...
Click to collapse
:crying::crying: i forget to enable usb debugging, now my pc can not connect to phone under downloadmode. And i can not use adb to let it reboot bootloader.
I think my dev is bricked for good. I used twrp and was not careful and wiped system. Now I cannot get into fastboot anymore and recovery does not work. It never shows up on USB. If I enter recovery, select yes to delete, it does nothing, just reboots with LG logo..
rav0r said:
I think my dev is bricked for good. I used twrp and was not careful and wiped system. Now I cannot get into fastboot anymore and recovery does not work. It never shows up on USB. If I enter recovery, select yes to delete, it does nothing, just reboots with LG logo..
Click to expand...
Click to collapse
I'm having the same problem. I wiped the device ready to install a new Rom and TWRP crashed. No adb or fastboot and it only loads onto the LG flash screen. There must be a way to do it as it's software problem, not hardware problem. How do they get the software onto the handset when first made, that's what I need I feel.
AndHD2 said:
I'm having the same problem. I wiped the device ready to install a new Rom and TWRP crashed. No adb or fastboot and it only loads onto the LG flash screen. There must be a way to do it as it's software problem, not hardware problem. How do they get the software onto the handset when first made, that's what I need I feel.
Click to expand...
Click to collapse
Same here, only a software issue. I cannot boot to download mode, and my device is locked.
Hi everyone,
I got Chinese version Note 8 Pro from Mi official store and unlocked bootloader after 7 days.
I downloaded Global MIUI 11 ROM via official miui download link, "ifelixit+FLASHER+TOOLKIT+Begonia" and installed ADB drivers etc.
After run ifelixit+FLASHER+TOOLKIT+Begonia.bat and pick 1, it installed recovery, then I'm able to boot into TWRP, and then I installed global rom from there, meanwhile wiped everything in it as I don't need China version rom. Phone reboot well and new global rom works great.
Then I try to install Magisk, I noticed recovery seems be restored to original, no worries, I re-run ifelixit+FLASHER+TOOLKIT+Begonia.bat and pick 1 to install TWRP again. Whatever I did, I cannot get TWRP back, when I hold power/+, it keep blank and will restart, but if I don't hold them, it can get into the system.
My first question is: 1. At this stage, is recovery crash already?
I didn't think too much and I get into system, install Magisk manager, let it to patch boot.img, I then use following command in fastboot mode
fastboot flash boot boot_patch.img
After I finished, I noticed maybe I can do TWRP here as well, then I also input
fastboot flash boot TWRP.img
After reboot, the phone is dead....No fastboot, NO recovery, no vibration. exactly described as here
[UNBRICK - stuck on DA mode / Authorised Service Account required]
https://forum.xda-developers.com/re...ide-unbrick-stuck-da-mode-authorised-t4000433
I re-think what I did, my question is
2. Will boot_patch.img Magisk patched not suitable for China phone with global rom?
3. Is fastboot dead because I installed recovery into boot via fastboot flash boot TWRP.img?
Thanks for your time and appreciated for any knowledgeable reply.
Flash your original boot.img for your original firmware or just download the xiaomitoolV2 and flash it that way. I see a lot of people flashing stock firmware using TWRP. Hence the v2 tool only works if your phone still fully boots. NOTE do not flash stock FW or UPDATE using TWRP you will brick the device. Chances are your FW didn't flash and just ADB CMD fatsboot flash boot ( then set BOOT.IMG ) in the CMD and get the devices booting again. Then use the V2 tool to flash the global firmware get that to stick then use the ifelixit tool to flash recovery once in recovery go advanced file mgr system-root at the bottom delete boot P then close AVB 2.0 then hit the install root button SU - magisk 19.4 will be installed. no need to wipe or format the phone ( DON'T FORGET TO WIPE CACHE & DALVIC.
---------- Post added at 09:00 AM ---------- Previous post was at 08:52 AM ----------
fastjohnson said:
Flash your original boot.img for your original firmware or just download the xiaomitoolV2 and flash it that way. I see a lot of people flashing stock firmware using TWRP. Hence the v2 tool only works if your phone still fully boots. NOTE do not flash stock FW or UPDATE using TWRP you will brick the device. Chances are your FW didn't flash and just ADB CMD fatsboot flash boot ( then set BOOT.IMG ) in the CMD and get the devices booting again. Then use the V2 tool to flash the global firmware get that to stick then use the ifelixit tool to flash recovery once in recovery go advanced file mgr system-root at the bottom delete boot P then close AVB 2.0 then hit the install root button SU - magisk 19.4 will be installed. no need to wipe or format the phone ( DON'T FORGET TO WIPE CACHE & DALVIC.
Click to expand...
Click to collapse
Remove the back off the phone and disconnect the battery for 5 min just to be sure hold the power button to clear all power left in the phone. Main objective is to get useage again fastboot or recovery. If you get recovery sideload your boot img and flash it on the next reboot twrp will be overridden.
fastjohnson said:
Flash your original boot.img for your original firmware or just download the xiaomitoolV2 and flash it that way. I see a lot of people flashing stock firmware using TWRP. Hence the v2 tool only works if your phone still fully boots. NOTE do not flash stock FW or UPDATE using TWRP you will brick the device. Chances are your FW didn't flash and just ADB CMD fatsboot flash boot ( then set BOOT.IMG ) in the CMD and get the devices booting again. Then use the V2 tool to flash the global firmware get that to stick then use the ifelixit tool to flash recovery once in recovery go advanced file mgr system-root at the bottom delete boot P then close AVB 2.0 then hit the install root button SU - magisk 19.4 will be installed. no need to wipe or format the phone ( DON'T FORGET TO WIPE CACHE & DALVIC.
---------- Post added at 09:00 AM ---------- Previous post was at 08:52 AM ----------
Remove the back off the phone and disconnect the battery for 5 min just to be sure hold the power button to clear all power left in the phone. Main objective is to get useage again fastboot or recovery. If you get recovery sideload your boot img and flash it on the next reboot twrp will be overridden.
Click to expand...
Click to collapse
Thanks. Currently my phone doesn't have reboot, no recovery, purely blank on screen, only power led shows when connecting via USB. In this situation, must open back case to disconnect the battery? I heard about it's free to go back to mi store and re flash it back. To open back case it won't have warranty anymore. Struggling....
idog8818 said:
Thanks. Currently my phone doesn't have reboot, no recovery, purely blank on screen, only power led shows when connecting via USB. In this situation, must open back case to disconnect the battery? I heard about it's free to go back to mi store and re flash it back. To open back case it won't have warranty anymore. Struggling....
Click to expand...
Click to collapse
I also have two bricked phones note 8 pro with no recovery, only white led shows when connecting via USB.
First bricked with TWRP and then flashed with false boot.img, second is bricked with OrangeFox-Unofficial-begonia.img.
I was open back case and disconnect the battery, stay 3 days but nothing working to reboot to fastboot or recovery.
Also I have already tried with short circuit test point to EDL mode but phone is still dead. I have downloaded many xiaomi and other tools and firmwares, installed all available usb drivers and reading all internet forums.
Please help!
Same
Hello,
I think I did the same error, flashing a wrong boot.img...
I tell you if I manage to do something.
hello, the solution to the problem is the battery is completely discharged until the device stops responding to any attempts to start using the key combination. unless you tried to flash a fastboot partition. the solution works after hard bricking after trying to upload incompatible twrp or other rom (I uploaded Chinese twrp on eu rom). ok, we start:
1. holding vol - and power plug in the usb cable (the buttons are released when the notification LED changes from very bright for a moment to slightly dimmed)
2. you will see the long unseen battery symbol with a lightning inside (i.e. a completely discharged battery, the charge status will begin to show the percentage)
3. Turn off the USB cable at 3 percent.
4. now an important thing - you need to start the phone only trying to enter the fastboot mode otherwise the phone will start to boot the system and get stuck again and you will have to unload it again
5. you will finally enter the fastboot , using only the software from xiaomi or xiaomi flash and fastboot rom
I succeeded after 2 weeks of waiting for it to discharge ...
I copied this tutorial from this partner klocek80 , and it worked perfectly
https://forum.xda-developers.com/showpost.php?p=81191977&postcount=72
danyv77 said:
hello, the solution to the problem is the battery is completely discharged until the device stops responding to any attempts to start using the key combination. unless you tried to flash a fastboot partition. the solution works after hard bricking after trying to upload incompatible twrp or other rom (I uploaded Chinese twrp on eu rom). ok, we start:
1. holding vol - and power plug in the usb cable (the buttons are released when the notification LED changes from very bright for a moment to slightly dimmed)
2. you will see the long unseen battery symbol with a lightning inside (i.e. a completely discharged battery, the charge status will begin to show the percentage)
3. Turn off the USB cable at 3 percent.
4. now an important thing - you need to start the phone only trying to enter the fastboot mode otherwise the phone will start to boot the system and get stuck again and you will have to unload it again
5. you will finally enter the fastboot , using only the software from xiaomi or xiaomi flash and fastboot rom
I succeeded after 2 weeks of waiting for it to discharge ...
I copied this tutorial from this partner klocek80 , and it worked perfectly
https://forum.xda-developers.com/showpost.php?p=81191977&postcount=72
Click to expand...
Click to collapse
This only helps when boot image is not damaged.
Duchan_xda said:
I also have two bricked phones note 8 pro with no recovery, only white led shows when connecting via USB.
First bricked with TWRP and then flashed with false boot.img, second is bricked with OrangeFox-Unofficial-begonia.img.
I was open back case and disconnect the battery, stay 3 days but nothing working to reboot to fastboot or recovery.
Also I have already tried with short circuit test point to EDL mode but phone is still dead. I have downloaded many xiaomi and other tools and firmwares, installed all available usb drivers and reading all internet forums.
Please help!
Click to expand...
Click to collapse
I'm with you. The boot image has error and when MTK realize it has something wrong it will NOT enter into fastboot. The only way to fix this is too use SP Flash Tool for deep flash. Mi store uses this way as well to fix the issue.
Try this:
https://c.mi.com/thread-2173190-1-0.html
ppthom said:
Try this:
https://c.mi.com/thread-2173190-1-0.html
Click to expand...
Click to collapse
This does NOT work. Please don't waste time on it.
:good:Thanks for clarifying this. Back to square one ...
idog8818 said:
Hi everyone,
I got Chinese version Note 8 Pro from Mi official store and unlocked bootloader after 7 days.
I downloaded Global MIUI 11 ROM via official miui download link, "ifelixit+FLASHER+TOOLKIT+Begonia" and installed ADB drivers etc.
After run ifelixit+FLASHER+TOOLKIT+Begonia.bat and pick 1, it installed recovery, then I'm able to boot into TWRP, and then I installed global rom from there, meanwhile wiped everything in it as I don't need China version rom. Phone reboot well and new global rom works great.
Then I try to install Magisk, I noticed recovery seems be restored to original, no worries, I re-run ifelixit+FLASHER+TOOLKIT+Begonia.bat and pick 1 to install TWRP again. Whatever I did, I cannot get TWRP back, when I hold power/+, it keep blank and will restart, but if I don't hold them, it can get into the system.
My first question is: 1. At this stage, is recovery crash already?
I didn't think too much and I get into system, install Magisk manager, let it to patch boot.img, I then use following command in fastboot mode
fastboot flash boot boot_patch.img
After I finished, I noticed maybe I can do TWRP here as well, then I also input
fastboot flash boot TWRP.img
After reboot, the phone is dead....No fastboot, NO recovery, no vibration. exactly described as here
[UNBRICK - stuck on DA mode / Authorised Service Account required]
https://forum.xda-developers.com/re...ide-unbrick-stuck-da-mode-authorised-t4000433
I re-think what I did, my question is
2. Will boot_patch.img Magisk patched not suitable for China phone with global rom?
3. Is fastboot dead because I installed recovery into boot via fastboot flash boot TWRP.img?
Thanks for your time and appreciated for any knowledgeable reply.
Click to expand...
Click to collapse
Are you recover your phone? I'm still waiting one year...
Duchan_xda said:
Are you recover your phone? I'm still waiting one year...
Click to expand...
Click to collapse
I didn`t find any background on your issue, just something like you actually have a device with white led light blinking.
I read this thread before (yes, some weeks ago) this happened to me yesterday https://forum.xda-developers.com/redmi-note-8-pro/how-to/guide-unlock-note-8-pro-authorised-t4168805 the short story is that I were trying to return to Miui 12 after of using some custom ROMs and something in the flashing process failed I mean it was an incomplete flashing and I assumed that most probably just the bootloader partition was damaged. The whole important fact in this situation is that you have yet available fastboot mode but like the splash partition with its image was gone I couldn `t see it and I were anyway in fastboot mode so I could flash the proper files to "unbrik" it. (my device is unlocked)
What you should try is connect it with PC while you`re pressing the volume down, enter to adb/fastboot environment and type fastboot commands to see if device is recogniced, you don`t have to hear constant reboot sounds or in this case press the power button simulating that you are powering off device.
Hi guys,
I tried to flash TWRP on my Wiko Lenny 4 earlier.
I used adb and fastboot to flash it, however the touchscreen wouldn't work and I was stuck at the "swipe to allow kernel modifications" screen in TWRP. No problem, I reboot in recovery mode, and switched to fastboot mode.
I found another TWRP image and, after flashing with
-> fastboot flash recovery twrp.img
I typed another command,
- >fastboot boot twrp.img.
Since then I am stuck at the Wiko boot screen, saying:
Orange State
Your device has been unlocked and can't be trusted (initially I unlocked OEM)
Your device will boot in 5 seconds
Whatever combination of power+vol up/down I try to use, it only reboots to this screen.
adb won't reconize any device, as well as fastboot. And both are up-to-date.
Perhaps there exists a recovery image that I can put on my sd card, and hopefully it will automatically boot on the sd card as I don't have any control right now.
If someone has an idea, please tell me.
thanks
[EDIT] Solved
Using this link https://aiomobilestuff.com/how-to-unbrick-wiko-stock-firmware-via-wiko-official-site/
I was able to download Wiko's recovery tool from https://customer-world.wikomobile.com/
After unzipping and starting the software, it automatically installed drivers (I guess, if it does not, mediatek usb wiko drivers can be used instead) and downloaded the software into the phone which works now.