Hi,
my Honor 7 is stucked in a reboot loop. Its just rebooting. I had a electricity blackout for few seconds when I was flashing SYSTEM.IMG (after CUST, RECOVERY, RECOVERY2 and BOOT.IMG) because i want to revert YodaROM to stock. I restarted the device and it went to bootloop (just restarting again and again). I can not get in to the fastboot or recovery, because every time i turn the phone (even when trying to get in recovery / fastboot) on it just reboots in a loop. Even after letting it discharge for over 7 hours, plugging it in a PC / charger starts showing the battery (not that charging annimated one) and then starts rebooting again. Any solution or the only one is repair service?
Sorry for my bad English. Thanks for your help.
You should be able to get in recovery if it starts booting except the recovery partition is broken. So i guess that's the case unless you maybe didn't Press the right Keys for recovery? I usally need a few tries, so are you sure you used the right combinition?
Sent from my Honor 7 using XDA Labs
lionboy33 said:
You should be able to get in recovery if it starts booting except the recovery partition is broken. So i guess that's the case unless you maybe didn't Press the right Keys for recovery? I usally need a few tries, so are you sure you used the right combinition?
Sent from my Honor 7 using XDA Labs
Click to expand...
Click to collapse
Volume up + Power button, few tries and same result. Same for Volume Up+Down+Power and for Power + Volume Down.
Even when I am cahrging phone is still restarting. (maybe bacause broken partition with that baterry animation (recovery?)).
I think you need to release the power button as you're on the boot screen and keep pressing vol up
Sent from my Honor 7 using XDA Labs
lionboy33 said:
I think you need to release the power button as you're on the boot screen and keep pressing vol up
Sent from my Honor 7 using XDA Labs
Click to expand...
Click to collapse
Nope, same effect. (rebboting in a loop)
tonakriz said:
Nope, same effect. (rebboting in a loop)
Click to expand...
Click to collapse
While bootlooping, is it being recognised by adb?
Sent from my Honor 7 using XDA Labs
---------- Post added at 11:09 PM ---------- Previous post was at 11:06 PM ----------
lionboy33 said:
While bootlooping, is it being recognised by adb?
Click to expand...
Click to collapse
Because then you can try to adb reboot -bootloader
Sent from my Honor 7 using XDA Labs
---------- Post added at 11:12 PM ---------- Previous post was at 11:09 PM ----------
lionboy33 said:
While bootlooping, is it being recognised by adb?
Sent from my Honor 7 using XDA Labs
---------- Post added at 11:09 PM ---------- Previous post was at 11:06 PM ----------
Because then you can try to adb reboot -bootloader
Click to expand...
Click to collapse
And: simple and maybe dumb idea, but are you sure the power button is functional and not pressed in unreleasable? I've seen that already
Sent from my Honor 7 using XDA Labs
lionboy33 said:
While bootlooping, is it being recognised by adb?
Sent from my Honor 7 using XDA Labs
Click to expand...
Click to collapse
No, its not recognised even by my system. I think that my BOOT.IMG was corrupt. I used Huawei UPDATE.APP extractor for extracting all *.IMGs (7zip could not extract SYSTEM.IMG and some others, but it can extract boot.img) size of 7 zip extracted boot.img is around 2 MB bigger than using that tool but it might be because of some encryption.
But if Boot.img and System.img were corrupt, the recovery should still be totally fine since it's seperated.
So we will succeed to enter it.
You said you already fully discharged it - how long was it totally empty/Have you tried turning it on a few times with empty battery to make sure its totally empty?
Sent from my Honor 7 using XDA Labs
---------- Post added at 11:23 PM ---------- Previous post was at 11:17 PM ----------
tonakriz said:
No, its not recognised even by my system. I think that my BOOT.IMG was corrupt. I used Huawei UPDATE.APP extractor for extracting all *.IMGs (7zip could not extract SYSTEM.IMG and some others, but it can extract boot.img) size of 7 zip extracted boot.img is around 2 MB bigger than using that tool but it might be because of some encryption.
Click to expand...
Click to collapse
And have you tried unbootlooping it using the Multi Tool?
Idk how far that works because I've never been in a bootloop on the h7 but you should try that.
Sent from my Honor 7 using XDA Labs
lionboy33 said:
But if Boot.img and System.img were corrupt, the recovery should still be totally fine since it's seperated.
So we will succeed to enter it.
You said you already fully discharged it - how long was it totally empty/Have you tried turning it on a few times with empty battery to make sure its totally empty?
Sent from my Honor 7 using XDA Labs
Click to expand...
Click to collapse
Yes, it was fully discahrged. I can try to discharge it more untill it dies totally. Now it just shows "low battery logo" when trying to turn it on.
Does not android loads like this?:
1. Reading booting microcode (hardcoded maybe)
2. Deciding if its jsut a normal boot, recovery or fastboot (using boot.img)
3. Loading selected boot partition (recovery, system, fastboot)
EDIT: Now i put it in a vice so its jsut holding power button to discharge it by showing permanently that "low battery logo"
tonakriz said:
Yes, it was fully discahrged. I can try to discharge it more untill it dies totally. Now it just shows "low battery logo" when trying to turn it on.
Does not android loads like this?:
1. Reading booting microcode (hardcoded maybe)
2. Deciding if its jsut a normal boot, recovery or fastboot (using boot.img)
3. Loading selected boot partition (recovery, system, fastboot)
Click to expand...
Click to collapse
I don't know in which order it works but today when I had to enter bootloader it didn't even show the bootlogo at all
Bootloader is there to rescue a phone, so it wouldn't really make sense to make it only able to use if only system.img is broken, though? NOTE: That was on another device, but it should be the same for all Androids I assume
Anyway, try to use the MultiTool and if that doesn't help, you might consider 100% discharging to leave the bootloop (as you said it continues starting and you can't even stop it from that?)
Sent from my Honor 7 using XDA Labs
lionboy33 said:
I don't know in which order it works but today when I had to enter bootloader it didn't even show the bootlogo at all
Bootloader is there to rescue a phone, so it wouldn't really make sense to make it only able to use if only system.img is broken, though?
Anyway, try to use the MultiTool and if that doesn't help, you might consider 100% discharging to leave the bootloop (as you said it continues starting and you can't even stop it from that?)
Sent from my Honor 7 using XDA Labs
Click to expand...
Click to collapse
System.img might be corrupted, but boot.img too. It stops restarting when "low battery logo" (just that red lightning bolts inside battery). Now when I hold Power Button it shows that low. bat. untill I release that button. I think that fastboot, recovery and system are dependent on boot.img.
tonakriz said:
System.img might be corrupted, but boot.img too. It stops restarting when "low battery logo" (just that red lightning bolts inside battery). Now when I hold Power Button it shows that low. bat. untill I release that button. I think that fastboot, recovery and system are dependent on boot.img.
Click to expand...
Click to collapse
So have you already tried "adb reboot bootloader" just as the Honor Screen appears?
Because it's definitely not hard bricked since it does try to boot and I cannot imagine you broke the Boot, bootloader AND Recovery
Sent from my Honor 7 using XDA Labs
Ok now its fulyl discharged. Any tips what should I try first?
tonakriz said:
Hi,
my Honor 7 is stucked in a reboot loop. Its just rebooting. I had a electricity blackout for few seconds when I was flashing SYSTEM.IMG (after CUST, RECOVERY, RECOVERY2 and BOOT.IMG) because i want to revert YodaROM to stock. I restarted the device and it went to bootloop (just restarting again and again). I can not get in to the fastboot or recovery, because every time i turn the phone (even when trying to get in recovery / fastboot) on it just reboots in a loop. Even after letting it discharge for over 7 hours, plugging it in a PC / charger starts showing the battery (not that charging annimated one) and then starts rebooting again. Any solution or the only one is repair service?
Sorry for my bad English. Thanks for your help.
Click to expand...
Click to collapse
Usually E-Recovery is untouched because it sits in a different partition.
Get update.app file from a full OTA and copy it to a dload folder inside phone or SD card.
Turn off phone with >30% battery.
Press vol+- and power simultaneously and let got those 3 buttons only when you see a working screen.
Normally it should start updating while wiping all partitions.
lionboy33 said:
So have you already tried "adb reboot bootloader" just as the Honor Screen appears?
Because it's definitely not hard bricked since it does try to boot and I cannot imagine you broke the Boot, bootloader AND Recovery
Sent from my Honor 7 using XDA Labs
Click to expand...
Click to collapse
I was spamming adb devices over 50 times per second (thanks Corsair K95 macros) and all of them were empty.
tonakriz said:
I was spamming adb devices over 50 times per second (thanks Corsair K95 macros) and all of them were empty.
Click to expand...
Click to collapse
Well, damn.
I'm going to sleep now, so let's try to solve this tomorrow
Maybe when you wake up tomorrow and it was fully discharged you can enter recovery
Sent from my Honor 7 using XDA Labs
zinko_pt said:
Usually E-Recovery is untouched because it sits in a different partition.
Get update.app file from a full OTA and copy it to a dload folder inside phone or SD card.
Turn off phone with >30% battery.
Press vol+- and power simultaneously and let got those 3 buttons only when you see a working screen.
Normally it should start updating while wiping all partitions.
Click to expand...
Click to collapse
Already tried. Since i flashed recovery and recovery2.img (that was erecovery) and both files were corrupt (7zip extracted img files from update.app could be opened as an archive, that extracted (which I used) could not)) I can not use this option.
lionboy33 said:
Well, damn.
I'm going to sleep now, so let's try to solve this tomorrow
Maybe when you wake up tomorrow and it was fully discharged you can enter recovery
Sent from my Honor 7 using XDA Labs
Click to expand...
Click to collapse
I hope so. Thank you for everything youve done.
https://www.youtube.com/watch?v=csv4iNc2AoY
This is whats happening
tonakriz said:
This is whats happening
Click to expand...
Click to collapse
Hey, I just booted my H7 into the bootloader to see how it works.. it did NOT show any Honor/bootscreen before it entered the bootloader so I conclude it doesn't need a working boot.img
Sent from my Honor 7 using XDA Labs
Related
Hi all,
My Transformer Prime will not boot past the initial Asus screen. It's remains stuck on this screen but when I hold power down, the device reboots. I am not able to get into recovery using power and vol down, then vol up. I cant turn the device off, it reboots every time. When I try to hold vol down while rebooting, the normal white writing doesn't appear, it just continues in the same loop at the Asus screen. I dont even get as far as the EeePad splash screen. I'm at a loss for what to try. I can get into recovery or fastboot and it wont connet to the pc. Am I screwed? All of the advice I can find needs recovery etc. The problem started when I tried to wipe the device. Could it have deleted the recovery image, rom etc? Any input would be greatly appreciated.
Thanks
santiago84 said:
Hi all,
My Transformer Prime will not boot past the initial Asus screen. It's remains stuck on this screen but when I hold power down, the device reboots. I am not able to get into recovery using power and vol down, then vol up. I cant turn the device off, it reboots every time. When I try to hold vol down while rebooting, the normal white writing doesn't appear, it just continues in the same loop at the Asus screen. I dont even get as far as the EeePad splash screen. I'm at a loss for what to try. I can get into recovery or fastboot and it wont connet to the pc. Am I screwed? All of the advice I can find needs recovery etc. The problem started when I tried to wipe the device. Could it have deleted the recovery image, rom etc? Any input would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
First, this belongs in q&a or general. Your problems have nothing to do with development.
Secondly, I posted a link a while back in the EOS3 ROM thread in reference to recovering from the exact scenario . The post includes which tools, drivers, and the process in detail on how I recovered down to the command for fast boot flashing the recovery ( which had a specific value for the device ).
EDIT:
Here is my detailed post. Try that and see if fastboot works for you. I was literally in the exact same boat not terribly long ago.
http://forum.xda-developers.com/showpost.php?p=33197007&postcount=508
MODS please move to the appropriate section.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
---------- Post added at 06:45 PM ---------- Previous post was at 06:30 PM ----------
Aso I forgot to ask.... were you already on a JB boot loader? If you were on ICS, make sure you download the ICS blob for twrp from the link and not the JB blob. That's crucial because if you flash the wrong recovery, you are screwed lol.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
santiago84 said:
I am not able to get into recovery using power and vol down, then vol up. I cant turn the device off, it reboots every time. When I try to hold vol down while rebooting, the normal white writing doesn't appear, it just continues in the same loop at the Asus screen.
Click to expand...
Click to collapse
I'm confused, you say here you cannot access the boot menu or recovery selection.
santiago84 said:
I can get into recovery or fastboot and it wont connet to the pc.
Click to expand...
Click to collapse
But here you say you can access recovery and fastboot which you would not be able to if what you said first was true.
lilstevie said:
I'm confused, you say here you cannot access the boot menu or recovery selection.
But here you say you can access recovery and fastboot which you would not be able to if what you said first was true.
Click to expand...
Click to collapse
He likely wiped all of his partitions ( including recovery ) like I did by accident. Fast boot was a pain in the arse for me until I used the -i command along with the new drivers. Hopefully my post resolved his issue.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Thank you for your response so far and apologies for putting the thread in the wrong section. The instructions given were great, only I am unable to get into fastboot. When I try and turn on the device holding vol down, it just boots normally. It doesn't give me the white writing and options I had before. I can't seem to turn the device off either. When I hold the power button it reboots, but doesn't shut down. What can I try to get into fast boot?
Thanks
Sent from my Galaxy Nexus using Tapatalk 2
pyraxiate said:
He likely wiped all of his partitions ( including recovery ) like I did by accident. Fast boot was a pain in the arse for me until I used the -i command along with the new drivers. Hopefully my post resolved his issue.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Sorry, it was a typo. I meant that I cant get into recovery or fastboot. No matter what I try. Ive never heard of fastboot disappearing. Any thoughts?
santiago84 said:
Sorry, it was a typo. I meant that I cant get into recovery or fastboot. No matter what I try. Ive never heard of fastboot disappearing. Any thoughts?
Click to expand...
Click to collapse
Did you do the nvflash process at any time and keep the blob files?
If you didn't and you cannot get to fastboot then I'm afraid that you are hard bricked
flumpster said:
Did you do the nvflash process at any time and keep the blob files?
If you didn't and you cannot get to fastboot then I'm afraid that you are hard bricked
Click to expand...
Click to collapse
No I didnt do the Nvflash. I unlocked and rooted a while ago, before nvflash was around and havent looked back since. Has anyone ever heard of fastboot being deleted? Ive always been able to get into it.
santiago84 said:
No I didnt do the Nvflash. I unlocked and rooted a while ago, before nvflash was around and havent looked back since. Has anyone ever heard of fastboot being deleted? Ive always been able to get into it.
Click to expand...
Click to collapse
Try holding the down and power button while its on to force shut down, then keep holding volume down as it reboots?
Also, what were you in the process of doing right before the issues began? Did you install something with a different bootloader? You could have wiped bootloader which means you are hosed . . . ..
Sent from my Transformer Prime TF201 using xda app-developers app
pyraxiate said:
Try holding the down and power button while its on to force shut down, then keep holding volume down as it reboots?
Also, what were you in the process of doing right before the issues began? Did you install something with a different bootloader? You could have wiped bootloader which means you are hosed . . . ..
I
Sent from my Transformer Prime TF201 using xda app-developers app
Click to expand...
Click to collapse
I've tried holding the buttons down while it reboots but nothing happens. If I hold the vol up and vol down while pressing power, the device turns off completely.
The problem started when I tried a factory reset in CWM. It crashed after a few seconds and the device rebooted. Not there doesnt appear to be anything on the device. I havent heard of CWM doing this before.
santiago84 said:
I've tried holding the buttons down while it reboots but nothing happens. If I hold the vol up and vol down while pressing power, the device turns off completely.
The problem started when I tried a factory reset in CWM. It crashed after a few seconds and the device rebooted. Not there doesnt appear to be anything on the device. I havent heard of CWM doing this before.
Click to expand...
Click to collapse
try volume up + power,if you see APX and you dont have nvflash then sent it back to ASUS and there is a charge to repair it.Sorry, happens to me
:crying::crying::crying::crying::crying::crying:
santiago84 said:
Sorry, it was a typo. I meant that I cant get into recovery or fastboot. No matter what I try. Ive never heard of fastboot disappearing. Any thoughts?
Click to expand...
Click to collapse
Without fastboot and nvflash there is no hope for recovery except for calling asus and requesting an RMA.
It sounds like your device has the boot to recovery flag, but with a broken recovery, something which the bootloader has no exit path from.
pyraxiate said:
You could have wiped bootloader which means you are hosed . . . ..
Click to expand...
Click to collapse
Without a bootloader you will not get any output from the device, the bootloader is what displays the asus splash screen. Without it the device would just drop into apx mode.
lilstevie said:
Without fastboot and nvflash there is no hope for recovery except for calling asus and requesting an RMA.
It sounds like your device has the boot to recovery flag, but with a broken recovery, something which the bootloader has no exit path from.
Without a bootloader you will not get any output from the device, the bootloader is what displays the asus splash screen. Without it the device would just drop into apx mode.
Click to expand...
Click to collapse
This is probably a silly question but if I send it back to asus for rma should I just claim complete ignorance as to how this happened? Or should I come clean? Has anyone done a rma before? Any idea of time scales or cost etc? Thanks
Sent from my Galaxy Nexus using Tapatalk 2
santiago84 said:
This is probably a silly question but if I send it back to asus for rma should I just claim complete ignorance as to how this happened? Or should I come clean? Has anyone done a rma before? Any idea of time scales or cost etc? Thanks
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Do not lie but don't tell the whole truth if you know what I mean
Don't go into too much info and get straight to the point, also don't show any technical knowledge.
"It doesn't turn on any more, it just flashes on a screen showing Asus".
"It wont turn off"
If you are lucky and they just look at it and not check what has happened they might just switch motherboard rather than messing with it.
Also try to run the battery out first. Harder to check
You shouldn't be covered at all because you agreed to that when you unlocked, but you might get lucky while staying truthful
p.s. I find my grandmother can get away with it more than me
Can someone help please i think ive bricked my sero 7 pro...i followed http://forum.xda-developers.com/show....php?t=2297246 post 2 to the t it seemed to root fine then i booted into recovery and it just said recovery and i couldnt get any further then it restarted and now its tsuck on the hisense logo for 45mins wont do anything if i hold volume up and power it says fastboot and nothing else if down and power it says recovery and nothing else tried the recovery mentioned in the other page nothing just stays on hisense logo
Me too?
jjsero7 said:
Can someone help please i think ive bricked my sero 7 pro...i followed http://forum.xda-developers.com/show....php?t=2297246 post 2 to the t it seemed to root fine then i booted into recovery and it just said recovery and i couldnt get any further then it restarted and now its tsuck on the hisense logo for 45mins wont do anything if i hold volume up and power it says fastboot and nothing else if down and power it says recovery and nothing else tried the recovery mentioned in the other page nothing just stays on hisense logo
Click to expand...
Click to collapse
I bought mine last week (UK version M470BSE not A) this is the 32GB version... Basically I managed to root it just fine but noticed that I couldn't get into CWM recovery? Would just stay on the 'Recovery' title screen. So after much reading on the thread I noticed that someone had the same problem and their solution was to put the tablet into 'Fastboot' mode and run the 'XERecovery.exe' but now my tablet is bricked I can tell you I'm not happy at all as I'll most probably have to destroy it in order to return it for a refund.
What was the outcome of your problem, did xboxexpert reply with an answer? Or did he just give you the following steps:
"First off, no I did not. It is definitely not bricked you can not brick this tablet thanks to my scripts.
Step 1: Remove all USB Cables and Hold Volume up and Power from a off state, you will see FASTBOOT on the tablet screen. Let go of power once you see FASTBOOT!
Step 2: Provided you have a USB cable and a PC you can plug it in now and run the recovery.exe from within the folder where my root script is located.
Step 3: By the time you read this if you followed the instructions XERecovery.exe told you to do you should have access to CWM Recovery go install a ROM."
If so that's bullsh*t! As without proper tools such as 'odin' like whats used for samsung flash recovery, we are SCREWED!!! I don't think Hisense are supporting this device like their competitors do in terms of technical resources etc.. Please let me know either way!
Cheers
itfreek said:
I bought mine last week (UK version M470BSE not A) this is the 32GB version... Basically I managed to root it just fine but noticed that I couldn't get into CWM recovery? Would just stay on the 'Recovery' title screen. So after much reading on the thread I noticed that someone had the same problem and their solution was to put the tablet into 'Fastboot' mode and run the 'XERecovery.exe' but now my tablet is bricked I can tell you I'm not happy at all as I'll most probably have to destroy it in order to return it for a refund.
What was the outcome of your problem, did xboxexpert reply with an answer? Or did he just give you the following steps:
"First off, no I did not. It is definitely not bricked you can not brick this tablet thanks to my scripts.
Step 1: Remove all USB Cables and Hold Volume up and Power from a off state, you will see FASTBOOT on the tablet screen. Let go of power once you see FASTBOOT!
Step 2: Provided you have a USB cable and a PC you can plug it in now and run the recovery.exe from within the folder where my root script is located.
Step 3: By the time you read this if you followed the instructions XERecovery.exe told you to do you should have access to CWM Recovery go install a ROM."
If so that's bullsh*t! As without proper tools such as 'odin' like whats used for samsung flash recovery, we are SCREWED!!! I don't think Hisense are supporting this device like their competitors do in terms of technical resources etc.. Please let me know either way!
Cheers
Click to expand...
Click to collapse
I just got my UK one aswell (32GB) and went through the same path, no CWN and recovery has screwed it for me too, any ideas. Its not even 2 hours old
Got fastboot access, does anyone have a UK sero image I can try or any other advise on how to recover my device ??? Anyone ????
Sorted
Just to let you know, that I got my UK 32GB unbricked.
Had to purchase another one (extreme I know !!!), got xboxexpert to dial in, grab an image of the new one and then fastboot into the bricked one and reflash it
All working now. Head over to his thread for the image files
Well pleased !!!!
Hisense Sero 7 Pro
Alpinestar777 said:
Just to let you know, that I got my UK 32GB unbricked.
Had to purchase another one (extreme I know !!!), got xboxexpert to dial in, grab an image of the new one and then fastboot into the bricked one and reflash it
All working now. Head over to his thread for the image files
Well pleased !!!!
Click to expand...
Click to collapse
Hi there,
My Sero 7 Pro is also having this same issue. But also in addition to this, it will not charge properly.
It hangs on the Hisense screen for a long time whilst connected via usb.
When I try to restart into update mode (up+down+power) it just states battery is too low.
I cannot get into fastboot neither as battery is too low?!
I was able to get into recovery before but since the battery has died, i cannot recharge it and do anything?!
Any ideas would be much appreciated!
It will charge
megabite said:
Hi there,
My Sero 7 Pro is also having this same issue. But also in addition to this, it will not charge properly.
It hangs on the Hisense screen for a long time whilst connected via usb.
When I try to restart into update mode (up+down+power) it just states battery is too low.
I cannot get into fastboot neither as battery is too low?!
I was able to get into recovery before but since the battery has died, i cannot recharge it and do anything?!
Any ideas would be much appreciated!
Click to expand...
Click to collapse
Megabite
I had exactly the samething. Plugged into mains for the entire day did not give me enough charge for fastboot !!!! Was abit of a nightmare but plug it into your pc as the charge is slower and leave there for a 30mins + Try to switch it off (hold power button) when it starts to charge. Did that as the mains was just not holding its charge.
It will charge you just need to keep it off. You just need a little bit of juice to get into recovery (fastboot) and then it will charge.
Alpinestar777 said:
Megabite
I had exactly the samething. Plugged into mains for the entire day did not give me enough charge for fastboot !!!! Was abit of a nightmare but plug it into your pc as the charge is slower and leave there for a 30mins + Try to switch it off (hold power button) when it starts to charge. Did that as the mains was just not holding its charge.
It will charge you just need to keep it off. You just need a little bit of juice to get into recovery (fastboot) and then it will charge.
Click to expand...
Click to collapse
Thanks! I will try this.
You wouldnt happen to have an image I can then reflash it with as my recovery was actually worked until the battery died.
Thanks again
---------- Post added at 11:21 PM ---------- Previous post was at 10:25 PM ----------
Alpinestar777 said:
Megabite
I had exactly the samething. Plugged into mains for the entire day did not give me enough charge for fastboot !!!! Was abit of a nightmare but plug it into your pc as the charge is slower and leave there for a 30mins + Try to switch it off (hold power button) when it starts to charge. Did that as the mains was just not holding its charge.
It will charge you just need to keep it off. You just need a little bit of juice to get into recovery (fastboot) and then it will charge.
Click to expand...
Click to collapse
Thanks for the advice, that worked!
Ok so I can fastboot and get into recovery now.
Only problem is that because I flashed a US rom without a backup of my previous UK 32gb rom and I am a bit stuck.
Could anybody help at all with a backup image or any other advice.
Thanks
megabite said:
Thanks! I will try this.
You wouldnt happen to have an image I can then reflash it with as my recovery was actually worked until the battery died.
Thanks again
---------- Post added at 11:21 PM ---------- Previous post was at 10:25 PM ----------
Thanks for the advice, that worked!
Ok so I can fastboot and get into recovery now.
Only problem is that because I flashed a US rom without a backup of my previous UK 32gb rom and I am a bit stuck.
Could anybody help at all with a backup image or any other advice.
Thanks
Click to expand...
Click to collapse
Its all in this link
http://forum.xda-developers.com/showthread.php?t=2297246
Alpinestar777 said:
Its all in this link
http://forum.xda-developers.com/showthread.php?t=2297246
Click to expand...
Click to collapse
I've also wiped the system etc so need a UK rom. There are only boot and kernel on the first post.
Thanks for your help though
Sent from my GT-I9300 using Tapatalk 2
uk rom
megabite said:
I've also wiped the system etc so need a UK rom. There are only boot and kernel on the first post.
Thanks for your help though
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Hi,
there is a UK rom on this page:
http://forum.xda-developers.com/showpost.php?p=41875861&postcount=2
Martin
Alpinestar777 said:
Just to let you know, that I got my UK 32GB unbricked.
Had to purchase another one (extreme I know !!!), got xboxexpert to dial in, grab an image of the new one and then fastboot into the bricked one and reflash it
All working now. Head over to his thread for the image files
Well pleased !!!!
Click to expand...
Click to collapse
Hi I got my Sero 7 pro bricked. I have CWM running. I can go to the recovery and able to install any ROM I want, however my tablet shows Hisense and then gets stuck for ever. I am not sure what I can do.
Also Windows can recoganize the device as MTP USB Device, with a yellow sign. The updating of driver doesn't seem to work. So I cannot see my device when I type "adb devices".
Thanks for all the help.
It's not meant to charge via USB. Plug it into an ac adaptor.
Sent from my M470BSA using xda app-developers app
My tablet is charged but is stuck after it displays Hisense Smart. It keeps on displaying forever. I tried other ROM also, but same results. Any ideas what I can do.
Thanks.
i am facing same problem now
megabite said:
Hi there,
My Sero 7 Pro is also having this same issue. But also in addition to this, it will not charge properly.
It hangs on the Hisense screen for a long time whilst connected via usb.
When I try to restart into update mode (up+down+power) it just states battery is too low.
I cannot get into fastboot neither as battery is too low?!
I was able to get into recovery before but since the battery has died, i cannot recharge it and do anything?!
Any ideas would be much appreciated!
Click to expand...
Click to collapse
when i try to on my hisense sero pro7 after 5/ hour charging it also shows red signal.
dogood1 said:
Hi I got my Sero 7 pro bricked. I have CWM running. I can go to the recovery and able to install any ROM I want, however my tablet shows Hisense and then gets stuck for ever. I am not sure what I can do.
Also Windows can recoganize the device as MTP USB Device, with a yellow sign. The updating of driver doesn't seem to work. So I cannot see my device when I type "adb devices".
Thanks for all the help.
Click to expand...
Click to collapse
whether did you find a solution?
I'm desperate and I have the same problem: (
people help us: (
darmonus said:
whether did you find a solution?
I'm desperate and I have the same problem: (
people help us: (
Click to expand...
Click to collapse
Are you using windows XP. Try these links for help.
http://forum.xda-developers.com/showthread.php?t=2130399
also make sure you have this driver installed.
Microsoft_User-Mode_Driver_Framework_Install-v1.0-WinXP
dogood1 said:
Are you using windows XP. Try these links for help.
http://forum.xda-developers.com/showthread.php?t=2130399
also make sure you have this driver installed.
Microsoft_User-Mode_Driver_Framework_Install-v1.0-WinXP
Click to expand...
Click to collapse
I use windows 7 but I do not know how I can Install oryginal rom .
My tablet is bricked . I can use just FASTBOOT.
darmonus said:
I use windows 7 but I do not know how I can Install oryginal rom .
My tablet is bricked . I can use just FASTBOOT.
Click to expand...
Click to collapse
You should be able to install the original rom via fastboot.
I'm assuming that you are at the point where "fastboot devices" shows devices...
You can start off by installing the stock recovery: http://forum.xda-developers.com/attachment.php?attachmentid=2000996&d=1369834980
fastboot flash --RECOVERY stock_boot.img --no-reboot
Then you can grab the stock ROM from the second post in xboxexpert's thread:
http://forum.xda-developers.com/showthread.php?t=2297246
fastboot flash zip [whateverStockRomyougrabbed.zip]
Reboot into recovery and do a factory reset.
I hope that helps. It certainly can't break things worse.
just bricked my tablet. its starting in recovery and thats it
I follow the next steps to make a factory reset but it stops... what should I do?
1.- press and hold the power + vol down buttons, it shows a first menu...
2.- select the recovery option and press the power button to chose...
3.- press and hold the power + vol up buttons, it shows a second menu...
4.- then chose the wipe data/factory reset option and wait...
5.- when finished select the reboot system now option and it should be done but!!
... but when I reboot the venue 3830 in this last step appears the dell logo screen and I been waiting for a 4 hours and nothing...
what can I do??... please help me!!
muckmulligan said:
I follow the next steps to make a factory reset but it stops... what should I do?
1.- press and hold the power + vol down buttons, it shows a first menu...
2.- select the recovery option and press the power button to chose...
3.- press and hold the power + vol up buttons, it shows a second menu...
4.- then chose the wipe data/factory reset option and wait...
5.- when finished select the reboot system now option and it should be done but!!
... but when I reboot the venue 3830 in this last step appears the dell logo screen and I been waiting for a 4 hours and nothing...
what can I do??... please help me!!
Click to expand...
Click to collapse
power off and connect charger let me know if it shows the charging animation , unfortunately it seems Intel's / Dell's method of hiding how long these devices actually take to boot (to the point its actually booting android ) is by using the splash screen ( which you see even it the boot.img and system.img get corrupt ) as the boot animation this makes it really hard to identify bootloops and corrupt partitions. but if you see the charging animation we at least know the boot.img is intact and we can continue to fixing the device.
social-design-concepts said:
power off and connect charger let me know if it shows the charging animation , unfortunately it seems Intel's / Dell's method of hiding how long these devices actually take to boot (to the point its actually booting android ) is by using the splash screen ( which you see even it the boot.img and system.img get corrupt ) as the boot animation this makes it really hard to identify bootloops and corrupt partitions. but if you see the charging animation we at least know the boot.img is intact and we can continue to fixing the device.
Click to expand...
Click to collapse
Hello SDC. Is there a way to remove this splash screen so that we can see the actual start up text?
GeeKerGurL said:
Hello SDC. Is there a way to remove this splash screen so that we can see the actual start up text?
Click to expand...
Click to collapse
not the start up text but we can get the splash screen removed to show the intel inside logo this at least allows you to know when it is actually booting , on mine i added an additional simple splash screen in install-recovery.sh so i see , intel inside , then starting su daemon , then the boot animation ,
though i wanna play with this tonight : http://www.xda-developers.com/android/chainfire-turns-your-bootanimation-into-a-logging-center/
social-design-concepts said:
not the start up text but we can get the splash screen removed to show the intel inside logo this at least allows you to know when it is actually booting , on mine i added an additional simple splash screen in install-recovery.sh so i see , intel inside , then starting su daemon , then the boot animation ,
though i wanna play with this tonight : http://www.xda-developers.com/android/chainfire-turns-your-bootanimation-into-a-logging-center/
Click to expand...
Click to collapse
Okie dokie. That chainfire file seems interesting, might try that soon too.
social-design-concepts said:
not the start up text but we can get the splash screen removed to show the intel inside logo this at least allows you to know when it is actually booting , on mine i added an additional simple splash screen in install-recovery.sh so i see , intel inside , then starting su daemon , then the boot animation ,
though i wanna play with this tonight : http://www.xda-developers.com/android/chainfire-turns-your-bootanimation-into-a-logging-center/
Click to expand...
Click to collapse
how did that go for u?
on my 3830, it shows intel inside, dell, then the logs, and back to dell after less than a minute
joanthanmajh said:
how did that go for u?
on my 3830, it shows intel inside, dell, then the logs, and back to dell after less than a minute
Click to expand...
Click to collapse
Same results though sick to see all that red on boot
Sent from my XT907 using XDA Free mobile app
... nothing appears... now I got a ROM but the tablet do not read the sd...
social-design-concepts said:
power off and connect charger let me know if it shows the charging animation , unfortunately it seems Intel's / Dell's method of hiding how long these devices actually take to boot (to the point its actually booting android ) is by using the splash screen ( which you see even it the boot.img and system.img get corrupt ) as the boot animation this makes it really hard to identify bootloops and corrupt partitions. but if you see the charging animation we at least know the boot.img is intact and we can continue to fixing the device.
Click to expand...
Click to collapse
Thank you SDC for help me... when the battery is empty the charging animation is showed...
Trying with the MY TOOL KIT...
muckmulligan said:
Thank you SDC for help me... when the battery is empty the charging animation is showed...
Click to expand...
Click to collapse
... I think nothing is happen... maybe the tablet is not working...
The message showed is...
Vampirefo Venue 8 v6.0.3.7
-- Installing: \external_sd/venue8_version-1.22-ota-signed_full_rooted.zip
Finding update package...
Opening update package...
Installing update...
... 4 hours has passed... really I´m not sure this is working... I think maybe I should buy a new brand chinese tablet... jejeje.
joanthanmajh said:
how did that go for u?
on my 3830, it shows intel inside, dell, then the logs, and back to dell after less than a minute
Click to expand...
Click to collapse
interesting I don't see intel, I see dell logo, before logcat output then I get logcat output until desktop.
I uploaded a video of my dell venue 8, perhaps we get same thing, I just misunderstood your post.
http://youtu.be/vl__nWqeH7I
vampirefo said:
interesting I don't see intel, I see dell logo, before logcat output then I get logcat output until desktop.
I uploaded a video of my dell venue 8, perhaps we get same thing, I just misunderstood your post.
http://youtu.be/vl__nWqeH7I
Click to expand...
Click to collapse
If you use the unbrick ( xsftk loader or any of the other Intel flashing tools that use it ) process to unbrick or early on root / bootloader unlock the process wipes the splash.img from the osip header leaving you with the Intel default Intel inside logo instead of the dell splash screen.
Sent from my XT907 using XDA Free mobile app
social-design-concepts said:
If you use the unbrick ( xsftk loader or any of the other Intel flashing tools that use it ) process to unbrick or early on root / bootloader unlock the process wipes the splash.img from the osip header leaving you with the Intel default Intel inside logo instead of the dell splash screen.
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
Ok so other than intel logo, everything else the same?
Sent from my Venue 8 3830 using Tapatalk
vampirefo said:
Ok so other than intel logo, everything else the same?
Sent from my Venue 8 3830 using Tapatalk
Click to expand...
Click to collapse
No on mine I only get logcat for a few seconds not all the way to boot
Sent from my XT907 using XDA Free mobile app
muckmulligan said:
... I think nothing is happen... maybe the tablet is not working...
The message showed is...
Vampirefo Venue 8 v6.0.3.7
-- Installing: \external_sd/venue8_version-1.22-ota-signed_full_rooted.zip
Finding update package...
Opening update package...
Installing update...
... 4 hours has passed... really I´m not sure this is working... I think maybe I should buy a new brand chinese tablet... jejeje.
Click to expand...
Click to collapse
what is this rom?
Code:
venue8_version-1.22-ota-signed_full_rooted.zip
Why are you trying to install it from CWM recovery?
---------- Post added at 09:38 AM ---------- Previous post was at 09:18 AM ----------
vampirefo said:
what is this rom?
Code:
venue8_version-1.22-ota-signed_full_rooted.zip
Why are you trying to install it from CWM recovery?
Click to expand...
Click to collapse
Ok after google
Code:
venue8_version-1.22-ota-signed_full_rooted.zip
https://software.intel.com/en-us/forums/topic/518378
I see no point in installing this version, honestly I can't think of why it was ever made, useless rom, all that is needed is ifwi.zip the rest is garbage. You only need ifwi.zip to unlock your bootloader.
Intel should have only released ifwi.zip, the rest of the stuff is really unless unneeded junk, LOL I never get why companies waste people's time, all they need to do now is release ifwi.zip for Venue 7 then it would also be unlocked.
vampirefo said:
what is this rom?
Code:
venue8_version-1.22-ota-signed_full_rooted.zip
Why are you trying to install it from CWM recovery?
---------- Post added at 09:38 AM ---------- Previous post was at 09:18 AM ----------
Ok after google
Code:
venue8_version-1.22-ota-signed_full_rooted.zip
https://software.intel.com/en-us/forums/topic/518378
I see no point in installing this version, honestly I can't think of why it was ever made, useless rom, all that is needed is ifwi.zip the rest is garbage. You only need ifwi.zip to unlock your bootloader.
Intel should have only released ifwi.zip, the rest of the stuff is really unless unneeded junk, LOL I never get why companies waste people's time, all they need to do now is release ifwi.zip for Venue 7 then it would also be unlocked.
Click to expand...
Click to collapse
They point was it couldn't see or install ota's
Sent from my XT907 using XDA Free mobile app
social-design-concepts said:
They point was it couldn't see or install ota's
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
I added the system to my dual boot setup.
vampirefo said:
interesting I don't see intel, I see dell logo, before logcat output then I get logcat output until desktop.
I uploaded a video of my dell venue 8, perhaps we get same thing, I just misunderstood your post.
http://youtu.be/vl__nWqeH7I
Click to expand...
Click to collapse
the new update for liveboot fixed it going back to dell
the did the dev edition so i have the intel inside logo
because in other way the tablet abort the installation...
vampirefo said:
what is this rom?
Code:
venue8_version-1.22-ota-signed_full_rooted.zip
Why are you trying to install it from CWM recovery?
I guess is a rom image for reinstall the system...
The entire history is...
1.- The intell venue 3830 device is crashed...
2.- One day I push the power button ready to play a game but the device show me an android robot with a red icon and the "sin comandos" legend...
3.- I enter the web in the search of a solution and trying the process:
- a.- hold power button + volume down and choose in the menu the recovery option.
- b.- when the android robot appears hold power button + volume up and choose the wipe data/factory reset option.
- c.- select the reboot system now option.
4.- This entire process should be restore my tablet but nooo!!
Then I have tried to learn what I have to do and I think is needed install a rom just as I do in a PC... format the computer and install an OS = format the tablet and install an android rom...
I´m not sure if is this correct or no but is what I´m trying to do...
can you help me please??
Click to expand...
Click to collapse
muckmulligan said:
vampirefo said:
what is this rom?
Code:
venue8_version-1.22-ota-signed_full_rooted.zip
Why are you trying to install it from CWM recovery?
I guess is a rom image for reinstall the system...
The entire history is...
1.- The intell venue 3830 device is crashed...
2.- One day I push the power button ready to play a game but the device show me an android robot with a red icon and the "sin comandos" legend...
3.- I enter the web in the search of a solution and trying the process:
- a.- hold power button + volume down and choose in the menu the recovery option.
- b.- when the android robot appears hold power button + volume up and choose the wipe data/factory reset option.
- c.- select the reboot system now option.
4.- This entire process should be restore my tablet but nooo!!
Then I have tried to learn what I have to do and I think is needed install a rom just as I do in a PC... format the computer and install an OS = format the tablet and install an android rom...
I´m not sure if is this correct or no but is what I´m trying to do...
can you help me please??
Click to expand...
Click to collapse
What OS did you have installed before you had problems? 4.2, 4.4, 4.3, ?
Click to expand...
Click to collapse
Jelly bean 4.2
vampirefo said:
muckmulligan said:
What OS did you have installed before you had problems? 4.2, 4.4, 4.3, ?
Click to expand...
Click to collapse
I have an android jelly bean 4.2
Click to expand...
Click to collapse
I decided to return my V10 back to stock, so I flashed the recovery, boot, and system img from this post.
Everything was successful, but now the phone won't boot. It just sits at the LG logo.
How long did you wait for it to boot? Did you factory reset? Not sure if you need to, I don't believe you do but might be an option.
If you still have twrp, flash this zip from @mikeyinid
http://forum.xda-developers.com/showthread.php?p=63660434
If you don't have twrp, perhaps reflashing the other images through fastboot again.
Sent from my LG-H901 using Xparent Skyblue Tapatalk 2
Warrior1975 said:
How long did you wait for it to boot? Did you factory reset? Not sure if you need to, I don't believe you do but might be an option.
If you still have twrp, flash this zip from @mikeyinid
http://forum.xda-developers.com/showthread.php?p=63660434
If you don't have twrp, perhaps reflashing the other images through fastboot again.
Sent from my LG-H901 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
I waited for almost 2 hours while the LG Mobile Support Tool was running. Still sits at the LG logo. Are there any other images available besides the one from TheJesus? The LG Support Tool recognizes the phone, but doesn't download anything when it tries to update recovery.
I also tried booting to recovery using the power + volume down button, still freezes at the LG logo
The LG Mobile support tool is deprecated. You now have to use LG Bridge. You should be able to get back to bootloader by
powering down the phone
Plugging in a micro usb from pc to phone
Hold vol⬇+power
When you see the LG logo release Power (while still holding vol⬇)
Press again the Power while holding vol⬇
Sent from my LG-H901 using Tapatalk
Does LG Bridge have the Update Recovery option like the support tool? I'm returning the phone & need to restore it completely back to stock
KAsp3rd said:
The LG Mobile support tool is deprecated. You now have to use LG Bridge. You should be able to get back to bootloader by
powering down the phone
Plugging in a micro usb from pc to phone
Hold vol+power
When you see the LG logo release Power (while still holding vol)
Press again the Power while holding vol
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
LG Bridge doesn't recognize the device. When I do vol+power, I can get to the Factory data reset screen, but after I select Yes, I get the little android for 2 seconds, then it goes back to the LG logo and freezes
Sounds like you are missing your recovery. Can you adb and fastboot? If so you can flash the stock recovery.img.
Link for recovery:
http://forum.xda-developers.com/showthread.php?p=63604156
Sent from my LG-H901 using Xparent Skyblue Tapatalk 2
captaindoobers said:
LG Bridge doesn't recognize the device. When I do vol+power, I can get to the Factory data reset screen, but after I select Yes, I get the little android for 2 seconds, then it goes back to the LG logo and freezes
Click to expand...
Click to collapse
Try it without your battery in (letting the usb on your pc power the device). I'll have a definitive answer on how to get into bootloader shortly. Just picked up my replacement device so I have to unlock and root my device again as well
Sent from my LG-H901 using Tapatalk
@captaindoobers: With your phone turned off. Hold Vol up and plug your phone into the USB (it must be plugged into your pc)
This should boot you to fastboot mode
Sent from my LG-H901 using Tapatalk
KAsp3rd said:
@captaindoobers: With your phone turned off. Hold Vol up and plug your phone into the USB (it must be plugged into your pc)
This should boot you to fastboot mode
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
When I did that, it flashed Download Mode for a second, and now I'm in a Firmware Update screen that's sitting at 0%.
adb still says device not found, and fastboot just says 'waiting for device"
KAsp3rd said:
@captaindoobers: With your phone turned off. Hold Vol up and plug your phone into the USB (it must be plugged into your pc)
This should boot you to fastboot mode
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
Keep in mind, all I did to get to this point was flash all 3 images from this post
http://forum.xda-developers.com/lg-v10/development/lg-h901-stock-img-files-boot-recovery-t3238638
fastboot flash boot boot.img
fastboot flash recovery stock_recovery.img
fastboot flash system system.img
All 3 flashes were successful (although flashing system.img only took about 4 seconds, which I thought should take much longer considering the size)
captaindoobers said:
Keep in mind, all I did to get to this point was flash all 3 images from this post
http://forum.xda-developers.com/lg-v10/development/lg-h901-stock-img-files-boot-recovery-t3238638
fastboot flash boot boot.img
fastboot flash recovery stock_recovery.img
fastboot flash system system.img
All 3 flashes were successful (although flashing system.img only took about 4 seconds, which I thought should take much longer considering the size)
Click to expand...
Click to collapse
I apologize, I told you wrong. You need to take the same steps but instead of volume up it is volume down.
To recap:
Make sure phone is powered off.
Make sure USB is plugged into PC.
With device powered down;
Press and hold the volume down key;
While holding volume down;
Insert microUSB plug into device.
That should get you to fastboot where you might be able to reflash twrp
KAsp3rd said:
I apologize, I told you wrong. You need to take the same steps but instead of volume up it is volume down.
To recap:
Make sure phone is powered off.
Make sure USB is plugged into PC.
With device powered down;
Press and hold the volume down key;
While holding volume down;
Insert microUSB plug into device.
That should get you to fastboot where you might be able to reflash twrp
Click to expand...
Click to collapse
that worked. I was able to reflash TWRP and flash the stock ROM. Thanks for your help!
captaindoobers said:
that worked. I was able to reflash TWRP and flash the stock ROM. Thanks for your help!
Click to expand...
Click to collapse
Glad we were able to finally figure this out. Now we'll have to remember this in the future.
Sent from my LG-H901 using Tapatalk
Think this thread is Gold @mgbotoe
Sent from my LG-H901 using Tapatalk
KwestJones said:
Think this thread is Gold @mgbotoe
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
Will be adding it to resource
Sent from my SM-N920T using Tapatalk
Is there a method of recovery if the bootloader was relocked and OEM unlocking was disabled?
KAsp3rd said:
The LG Mobile support tool is deprecated. You now have to use LG Bridge. You should be able to get back to bootloader by
I just want to thank you KASP
I was stuck for 12 Hours. Trying to get this thing into recovery
You sir are a god among men and I owe you a life debt.
Sincerely speaking
Click to expand...
Click to collapse
Think u have flash boot, flash system, reboot, then flash recovery?
Sent from my LG-H901 using Tapatalk
deleted
Hi guys, any help would be much appreciated! I have studied all threads on XDA on bricked and boot loop'ed Honor 5X phones. I'm not a complete noob -- I have been flashing CM/LineageOS for years on Nexus 4, 5, 7, 9 and 6P, and this is the first time I have been stumped.
My KIW-L24 has an early version of LineageOS 14.1, and also TWRP 3.1.1-0 on it. I used the LineageOS updater to download a later LineageOS build, and initiated the update. As expected, the phone rebooted into TWRP, briefly showed the TWRP boot screen, but then after about 1 second, the phone reboots to the Honor boot screen for about 3 seconds, and then boots back to TWRP ... and so the cycle repeats endlessly between the two boot screens until the battery dies.
I cannot seem to get the device into bootloader/fastboot mode so that I can reflash TWRP and/or LineageOS or stock ROM. I have tried every combination of hardware keys to get the phone into fastboot (including Power+Vol Down). I tried initiating the download mode back to stock with the update.app placed in /dload/ on the sdcard (Power+Vol Down+Vol Up). I tried plugging in the PC-USB cable + Vol Down. While plugged into the PC via USB cable, I tried issuing "adb reboot bootloader" while the TWRP screen momentarily pops up (I literally have a less than a half-second when adb recognizes the phone). All without any success.
I am truly stuck! Any ideas? I have a practically brand new paperweight at the moment. :crying: Thanks very much in advance for any suggestions!
Are you sure battery isnt flat ?
You can use twrp as fas as i understand.. Correct me if i am wrong..
You can download stock rom twrp backup for your model from repository thread and try to restore backup with twrp..
Thanks, but I cannot 'use' TWRP! If I could, my problems would be easily solved, I have plenty of experience re-flashing ROMs, boot images, radios, etc.
Also, the battery is fine. At full charge, the phone powers up and immediately enters the endless boot cycle I previously described.
As soon as the phone shows the TWRP boot screen, the phone reboots again. I cannot do anything at all with TWRP. As I previously wrote, I have even tried using adb to force a reboot into fastboot while the TWRP boot screen shows for that split second (the PC momentarily recognizes the USB Android device). Unfortunately , TWRP reboots the phone too quickly.
pet_zeus said:
Thanks, but I cannot 'use' TWRP! If I could, my problems would be easily solved, I have plenty of experience re-flashing ROMs, boot images, radios, etc.
Also, the battery is fine. At full charge, the phone powers up and immediately enters the endless boot cycle I previously described.
As soon as the phone shows the TWRP boot screen, the phone reboots again. I cannot do anything at all with TWRP. As I previously wrote, I have even tried using adb to force a reboot into fastboot while the TWRP boot screen shows for that split second (the PC momentarily recognizes the USB Android device). Unfortunately , TWRP reboots the phone too quickly.
Click to expand...
Click to collapse
Boot into boot loader by holding volume down and pushing in cable when huawei logo shows, I can tell you now its a bar-steward and may take many times before it actually does it !
---------- Post added at 02:53 PM ---------- Previous post was at 02:52 PM ----------
swukjay said:
Boot into boot loader by holding volume down and pushing in cable when huawei logo shows, I can tell you now its a bar-steward and may take many times before it actually does it !
Click to expand...
Click to collapse
If that doesnt work use e-recovery to restore phone and recovery to stock
---------- Post added at 03:07 PM ---------- Previous post was at 02:53 PM ----------
This may help https://forum.xda-developers.com/mate-8/general/fastboot-erecovery-recovery-upgrade-mode-t3543441
GOOD LUCK !
swukjay said:
Boot into boot loader by holding volume down and pushing in cable when huawei logo shows, I can tell you now its a bar-steward and may take many times before it actually does it !
If that doesnt work use e-recovery to restore phone and recovery to stock
Click to expand...
Click to collapse
Thanks, I just spent the another hour trying to enter Fastboot and eRecovery modes, and I must be missing something! At this point, no matter which button combination I press, I can't seem to affect the boot cycling of the phone (between TWRP and Honor boot screens).
Maybe relevant, but I am unable to even turn off the phone, it won't stop the alternating boot loop -- I don't believe in coincidences, but perhaps the power button just died? I had one Nexus 5 that started bootlooping because of the power button issue, but that was a very different behaviour than this -- the Honor deosn't get as far as booting to the OS.
GOOD LUCK !
Click to expand...
Click to collapse
Thank you, looks like I'll need some! Will update if I can figure out a way out...
pet_zeus said:
Thanks, I just spent the another hour trying to enter Fastboot and eRecovery modes, and I must be missing something! At this point, no matter which button combination I press, I can't seem to affect the boot cycling of the phone (between TWRP and Honor boot screens).
Maybe relevant, but I am unable to even turn off the phone, it won't stop the alternating boot loop -- I don't believe in coincidences, but perhaps the power button just died? I had one Nexus 5 that started bootlooping because of the power button issue, but that was a very different behaviour than this -- the Honor deosn't get as far as booting to the OS.
Thank you, looks like I'll need some! Will update if I can figure out a way out...
Click to expand...
Click to collapse
Sound to me like you flash Non VOLTE firmware on a Volte enabled modem thats causing the boot loop, the best course of action is to restore using e-recovery, that uses a separate recovery partition so hopefully wont boot loop, remember it may take a few times to boot and you must use a usb lead that is connected to a computer, a usb charger WILL NOT DO IT !
When it boots to e-recovery select download latest firmware, you will need to connect to wifi, just follow instructions and let it restore
pet_zeus said:
Thank you, looks like I'll need some! Will update if I can figure out a way out...
Click to expand...
Click to collapse
Erecovery should work, connect your USB to a computer and volume down + power
Another new user who posts when he has a problem and doesn't reply with an update as to what solution solved his problem, this constantly winds me up, new users who do this and dont update the thread should be kicked off
SOLVED!
Sorry for the delay of the update--I got busy and left my phone to collect dust for a while.
The ONLY solution that actually worked was to rip the phone apart and physically disconnect the battery ( !! ). Then, reconnecting the battery while holding down [Power] and [Vol -] got me into fastboot recovery, as per instructions in this thread (I had to avoid booting normally, or into recovery -- TWRP -- since either would put the phone back into the bootloop):
https://forum.xda-developers.com/honor-5x/how-to/guide-entering-fastboot-using-key-t3400869
After that, it was smooth sailing; I was able to kill TWRP by flashing RECOVERY.img that I extracted from stock B140 image (using Huawei extractor https://forum.xda-developers.com/showthread.php?t=2433454), then force-update to stock B331, then latest TWRP and LineageOS. One hiccup: for whatever reason, I needed to do a factory reset/wipe in TWRP before it would flash LineageOS without giving error 7, despite the fact that I had just flashed the stock image.
Thank you all for your help and input!