Database Users

Can't Boot Up Stock ROM Out of the BOX

Just received my Nexus 7 today. I tried booting it up right of the box when the google logo came out and then the screen went black. I thought it might only need recharging. so I plugged it in to charge and waited for the battery icon to show that its charging. I tried booting up again after three hours of charging, the google logo came out again and then the brightness of the screen lowers and I can still barely see the logo. The screen blacked out again and the X showed up and I thought it was booting when it disappeared quickly and it blacked out again. I waited for a while and nothing is showing up on the screen. I tried rebooting a million times and the same thing happens every time. I plugged the tablet to my PC and I can open the internal memory when nothing is showing on the screen after boot up. I went into fastboot mode and unlocked the bootloader and rooted the nexus and tried rebooting with the same result. I tried flashing the stock rom twice using the toolkit and again using adb with no luck. I'm trying to flash a custom rom to see if it fixes anything but I can't seem to boot into recovery either. Can someone show me how to flash a custom rom at fastboot by adb without using recovery? I tried searching for a solution but couldn't find anything. Did someone have the same problem?
I'm from Abu Dhabi and unfortunately I won't be able to return it without wasting a fortune on shipping.
Thanks in advance

Blue Reaper said:
Just received my Nexus 7 today. I tried booting it up right of the box when the google logo came out and then the screen went black. I thought it might only need recharging. so I plugged it in to charge and waited for the battery icon to show that its charging. I tried booting up again after three hours of charging, the google logo came out again and then the brightness of the screen lowers and I can still barely see the logo. The screen blacked out again and the X showed up and I thought it was booting when it disappeared quickly and it blacked out again. I waited for a while and nothing is showing up on the screen. I tried rebooting a million times and the same thing happens every time. I plugged the tablet to my PC and I can open the internal memory when nothing is showing on the screen after boot up. I went into fastboot mode and unlocked the bootloader and rooted the nexus and tried rebooting with the same result. I tried flashing the stock rom twice using the toolkit and again using adb with no luck. I'm trying to flash a custom rom to see if it fixes anything but I can't seem to boot into recovery either. Can someone show me how to flash a custom rom at fastboot by adb without using recovery? I tried searching for a solution but couldn't find anything. Did someone have the same problem?
I'm from Abu Dhabi and unfortunately I won't be able to return it without wasting a fortune on shipping.
Thanks in advance
Click to expand...
Click to collapse
I Think what you'll have to do is finding a recovery program like Odin. It seems like there might be something wrong at bootup maybe. I think it is the ROM. You have to find out how to flash the ROM again. If that doesn't work flash a custom ROM like CM10 or something.

Ryan35310 said:
I Think what you'll have to do is finding a recovery program like Odin. It seems like there might be something wrong at bootup maybe. I think it is the ROM. You have to find out how to flash the ROM again. If that doesn't work flash a custom ROM like CM10 or something.
Click to expand...
Click to collapse
Odin? isn't that for samsung.
Try booting your nexus 7 into the bootloader. Turn off device hold Volume UP and Volume DOWN and hold onto the power button.
You should now be in the bootloader.
If you are in bootloader you should be able to flash the stock rom again. Use this toolkit
http://forum.xda-developers.com/showthread.php?t=1809195 Option 9
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Install the correct drivers then install the toolkit as far as I am aware it has a option to restore stock image.
Hope this helps!!!

mulkman said:
Odin? isn't that for samsung.
Try booting your nexus 7 into the bootloader. Turn off device hold Volume UP and Volume DOWN and hold onto the power button.
You should now be in the bootloader.
If you are in bootloader you should be able to flash the stock rom again. Use this toolkit
http://forum.xda-developers.com/showthread.php?t=1809195 Option 9
Install the correct drivers then install the toolkit as far as I am aware it has a option to restore stock image.
Hope this helps!!!
Click to expand...
Click to collapse
Oh Sorry. I have A Galaxy Exhibit so I use Odin. I thought it was throughout Android. Oh well, I hope your solution helps him.

I tried flashing the stock ROM with the toolkit twice and I get the same thing. Anyone knows how to flash a custom ROM without using a recovery image? Thanks!

Blue Reaper said:
I tried flashing the stock ROM with the toolkit twice and I get the same thing. Anyone knows how to flash a custom ROM without using a recovery image? Thanks!
Click to expand...
Click to collapse
flash your roms/kernels in your custom recovery. educate yourself before you brick your device.

Blue Reaper said:
I tried flashing the stock ROM with the toolkit twice and I get the same thing. Anyone knows how to flash a custom ROM without using a recovery image? Thanks!
Click to expand...
Click to collapse
Use option 8 that will unlock your bootloader, root your device and flash custom recovery. Once done you will be able to flash any custom rom easily via Clockworkmod recovery
Hope that helps

simms22 said:
flash your roms/kernels in your custom recovery. educate yourself before you brick your device.
Click to expand...
Click to collapse
If you have read my first post or the title for that matter you would have already known that the device wasn't working OUT OF THE BOX. You would also know that I have already tried flashing a custom recovery without any success. Thanks for your input BTW
mulkman said:
Use option 8 that will unlock your bootloader, root your device and flash custom recovery. Once done you will be able to flash any custom rom easily via Clockworkmod recovery
Hope that helps
Click to expand...
Click to collapse
I have already unlocked my bootloader through mskip's toolkit and have rooted my device through wug's root toolkit because mskip's required me to enable debugging which wasn't possible in my situation. I tried flashing a custom recovery or even booting into one but it just loops and nothing happens.
I was wondering if I could use adb command prompt to flash a custom ROM through the bootloader if someone can give me the commands or a link to thread with instructions (I tried searching but couldn't find anything) Thanks!

Blue Reaper said:
If you have read my first post or the title for that matter you would have already known that the device wasn't working OUT OF THE BOX. You would also know that I have already tried flashing a custom recovery without any success. Thanks for your input BTW
I have already unlocked my bootloader through mskip's toolkit and have rooted my device through wug's root toolkit because mskip's required me to enable debugging which wasn't possible in my situation. I tried flashing a custom recovery or even booting into one but it just loops and nothing happens.
I was wondering if I could use adb command prompt to flash a custom ROM through the bootloader if someone can give me the commands or a link to thread with instructions (I tried searching but couldn't find anything) Thanks!
Click to expand...
Click to collapse
you really shouldnt use the root toolkits, they are more trouble and more confusing than doing it the right way. in a nutshell, this is the whole process for any nexus device.
1. fastboot oem unlock
2. fastboot flash a custom recovery
3. flash the su binaries or custom rom in your custom recovery
4. reboot and profit.
if you google fastboot recovery, im sure that youll find an answer. the fastboot process of flashing a recovery is the same for all android devices, just the file name is different.

No seriously, dont flash a Custom Recovery/Custom Rom at first !
I will tell you what to do step by step to get the Original Rom (Stock) working.
First ! Download the Stock rom from google https://dl.google.com/dl/android/aosp/nakasi-jro03d-factory-e102ba72.tgz
2. Get Fastboot, it is in the Android SDK or on the web(would be easier I think)
3. Open CMD/Terminal
4. (Linux/Mac Only otherwise skip this): Type sudo -s (It is going to ask for your password, type it.)
5. Run these command one by one :
fastboot erase boot
fastboot erase system
fastboot erase cache
fastboot erase userdata
fastboot erase recovery
6. Alright so now your device is empty, so any broken file is gone.
7. Extract the firmware you downloaded at first step (Dont extract the archive inside).
8. Type these command :
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot reboot-booloader
fastboot -w update image-nakasi-jro03d.zip
9. Wait until it is done and the device will boot up !

Blue Reaper said:
Just received my Nexus 7 today. I tried booting it up right of the box when the google logo came out and then the screen went black. I thought it might only need recharging. so I plugged it in to charge and waited for the battery icon to show that its charging. I tried booting up again after three hours of charging, the google logo came out again and then the brightness of the screen lowers and I can still barely see the logo. The screen blacked out again and the X showed up and I thought it was booting when it disappeared quickly and it blacked out again. I waited for a while and nothing is showing up on the screen. I tried rebooting a million times and the same thing happens every time. I plugged the tablet to my PC and I can open the internal memory when nothing is showing on the screen after boot up. I went into fastboot mode and unlocked the bootloader and rooted the nexus and tried rebooting with the same result. I tried flashing the stock rom twice using the toolkit and again using adb with no luck. I'm trying to flash a custom rom to see if it fixes anything but I can't seem to boot into recovery either. Can someone show me how to flash a custom rom at fastboot by adb without using recovery? I tried searching for a solution but couldn't find anything. Did someone have the same problem?
I'm from Abu Dhabi and unfortunately I won't be able to return it without wasting a fortune on shipping.
Thanks in advance
Click to expand...
Click to collapse
Sounds to me that your automatic brightness control is off......try this. Power up and after the Nexus X shows up and the screen goes black, give it about two or three minutes to finish booting. Then, with the power still on, take it out in the bright sunlight or shine a flashlight on the screen. If you see the start up options, then it is the brightness control and a simple adjustment in the settings will take care if it.
Good luck!!!

dparrothead1 said:
Sounds to me that your automatic brightness control is off......try this. Power up and after the Nexus X shows up and the screen goes black, give it about two or three minutes to finish booting. Then, with the power still on, take it out in the bright sunlight or shine a flashlight on the screen. If you see the start up options, then it is the brightness control and a simple adjustment in the settings will take care if it.
Good luck!!!
Click to expand...
Click to collapse
You beat me to it! I was going to post this right before I read your reply :silly:
"Thanks for all the help guys! So I found out what's wrong and it is one of the most frustrating defects I have ever encountered. When the screen was blacking out after boot up the device was actually working the whole time only the screen was off (as in ZERO brightness). The way I found out was when I tried rebooting into fastboot I heard a screenshot sound when pressing the power and volume down button. So I hooked up the tablet to my PC to take a look at what I captured. To my surprise, it was the welcome screen. I kept taking screenshots until I reached the settings to enable debugging ( Apparently, the rooting wasn't successful using wug's toolkit). After enabling debugging I was going to reboot but I had an idea. I thought if I used my Galaxy Nexus's LED light on the screen I might be able to see something. Stupid idea right? WRONG! The moment I pointed the light at the screen the screen magically brightened up and was working fine! I turned the screen off and on again and the screen was dim again. And once again turned on when I flashed my LED on it. I figured out it was the light sensor after reading a thread on androidforums...
I guess I'll have to deal with it, I don't use automatic brightness anyway
Thanks again! "

Once you get it going, you should be able to put it on auto and it should work just fine. And if it doesn't, at least you will know how to fix it.
Enjoy your N7, I know I do:laugh:

Blue Reaper said:
You beat me to it! I was going to post this right before I read your reply :silly:
"Thanks for all the help guys! So I found out what's wrong and it is one of the most frustrating defects I have ever encountered. When the screen was blacking out after boot up the device was actually working the whole time only the screen was off (as in ZERO brightness). The way I found out was when I tried rebooting into fastboot I heard a screenshot sound when pressing the power and volume down button. So I hooked up the tablet to my PC to take a look at what I captured. To my surprise, it was the welcome screen. I kept taking screenshots until I reached the settings to enable debugging ( Apparently, the rooting wasn't successful using wug's toolkit). After enabling debugging I was going to reboot but I had an idea. I thought if I used my Galaxy Nexus's LED light on the screen I might be able to see something. Stupid idea right? WRONG! The moment I pointed the light at the screen the screen magically brightened up and was working fine! I turned the screen off and on again and the screen was dim again. And once again turned on when I flashed my LED on it. I figured out it was the light sensor after reading a thread on androidforums...
I guess I'll have to deal with it, I don't use automatic brightness anyway
Thanks again! "
Click to expand...
Click to collapse
Hmm that sucks :/ If I were you, I would not deal with this, I would ask Google/Shop for a replacement. Why keeping something broken when you can get one fully working ? If you deal with google it is cool because you only send your broken device once you got your new one so that way you can keep using it all the time Also, it would be a pain to keep broken, everytime you flash a new rom, you would have the automatic brightness turned on by default :/

jamesst20 said:
Hmm that sucks :/ If I were you, I would not deal with this, I would ask Google/Shop for a replacement. Why keeping something broken when you can get one fully working ? If you deal with google it is cool because you only send your broken device once you got your new one so that way you can keep using it all the time Also, it would be a pain to keep broken, everytime you flash a new rom, you would have the automatic brightness turned on by default :/
Click to expand...
Click to collapse
It's not broken. Just a one time glitch!! :good:

dparrothead1 said:
It's not broken. Just a one time glitch!! :good:
Click to expand...
Click to collapse
Unsure about that, I've tried to reproduce the case and I can't seem to success to get a 0% Backlight.

Get an exchanged aka RMA it. The same thing happened to me. Get an exchange.

Knightsofwar210 said:
Get an exchanged aka RMA it. The same thing happened to me. Get an exchange.
Click to expand...
Click to collapse
Agreed, not working out of the box is Deff asking for an rma
Sent from my Rooted, LazyPanda, White "Destroy Mode" Evo

Why the heck would you try n flash it when it didnt work out the box there could be all sorts wrong with it..
Sent from my Nexus 7 using Tapatalk 2

jamesst20 said:
Unsure about that, I've tried to reproduce the case and I can't seem to success to get a 0% Backlight.
Click to expand...
Click to collapse
You can't reproduce it because it was a one time glitch!!!

[Q] Razr M will not boot up installing beats audio app

So i rooted my phone this morning using motofail2go and it was successful. after browsing around and stuff i come across a app called Beats Audio. I installed it and it said the phone needed to reboot. it turned off and turned on but when the motorola logo disappears nothing else happens. the screen will stay black. i thought wiping the data and cahce partitions the phone will go back to working condition but no luck it still did the same thing. i tired RSDlite 6.1.4 but after hitting start it immediately failed. in the boot options everything else besides AP Fastboot goes to a black screen and does nothing. when i looked around for the RSD tutorials they all said that RSD will recongize the device as XT907 but for me RSD showed it as Fastboot SCORPION_MINI S. can you please help me? i would be very greatful
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

If you do power and volume down buttons together will it boot then ?

jtommyj said:
If you do power and volume down buttons together will it boot then ?
Click to expand...
Click to collapse
i tried everything. i held the power and volume buttons and i get to the boot mode selection menu and my choices are
Normal bootup
Recovery
AP Fastboot
Factory
BP Tools
i clicked on everything and they all do the same thing which is the motorola logo will show for a few seconds like normal then it'll go to a black screen and do nothing.

AKG0214 said:
i tried everything. i held the power and volume buttons and i get to the boot mode selection menu and my choices are
Normal bootup
Recovery
AP Fastboot
Factory
BP Tools
i clicked on everything and they all do the same thing which is the motorola logo will show for a few seconds like normal then it'll go to a black screen and do nothing.
Click to expand...
Click to collapse
Go too ap fast boot mode on the device, plug it in too PC, start rsdlite 6.1.4, point rsd too the fast boot files "~680mb file" let it extract it, then after it fails, click the "browse files button" on rsd, it should be pointed too an XML file, "right-click" and edit the file, if not possible locate the file via windows explorer, once you right click and begin editing, you should remove any lines with the words "OEM " or "var" that means, lines such as "get var" or the "OEM fb-set-clear" lines, just delete them completely, and save the file.. try it again, if it fails just delete the line "gpt_main.bin" and you should have no errors,
Sorry for the formatting this was done on mobile asap, if you don't understand or cant do it, please locate the XML on your computer and attach it here, or PM me the XML and I will gladly edit it for you..

AKG0214 said:
i tried everything. i held the power and volume buttons and i get to the boot mode selection menu and my choices are
Normal bootup
Recovery
AP Fastboot
Factory
BP Tools
i clicked on everything and they all do the same thing which is the motorola logo will show for a few seconds like normal then it'll go to a black screen and do nothing.
Click to expand...
Click to collapse
I know you'll get to that menu by holding ~both~ volume buttons and the power but did you just do the volume down and power ?
It's a little unclear from your answer as that is supposed to be the failsafe boot mode and worked for me under similar circumstances

tadgerloks said:
Go too ap fast boot mode on the device, plug it in too PC, start rsdlite 6.1.4, point rsd too the fast boot files "~680mb file" let it extract it, then after it fails, click the "browse files button" on rsd, it should be pointed too an XML file, "right-click" and edit the file, if not possible locate the file via windows explorer, once you right click and begin editing, you should remove any lines with the words "OEM " or "var" that means, lines such as "get var" or the "OEM fb-set-clear" lines, just delete them completely, and save the file.. try it again, if it fails just delete the line "gpt_main.bin" and you should have no errors,
Sorry for the formatting this was done on mobile asap, if you don't understand or cant do it, please locate the XML on your computer and attach it here, or PM me the XML and I will gladly edit it for you..
Click to expand...
Click to collapse
i deleted all the lines that had oem and var into but also failed but i haven't tried delete the gpt_main.bin yet. i managed to get to the charging screen but it was at 14% and i want to try to turn it on at some point. but im not sure if it was the beats audio that messed up my phone. cuz when i rooted it i never thought of turning it off and rebooting it to see if any problems occurred but after reading tons of reviews about the app it seems like it was the app that caused it cuz a few other people came facing the same problem. but thanks you for the information i really appreciate the help

AKG0214 said:
i deleted all the lines that had oem and var into but also failed but i haven't tried delete the gpt_main.bin yet. i managed to get to the charging screen but it was at 14% and i want to try to turn it on at some point. but im not sure if it was the beats audio that messed up my phone. cuz when i rooted it i never thought of turning it off and rebooting it to see if any problems occurred but after reading tons of reviews about the app it seems like it was the app that caused it cuz a few other people came facing the same problem. but thanks you for the information i really appreciate the help
Click to expand...
Click to collapse
Let it charge too 60% before trying too flash from rsd, and keep the XML file edited then try again once its charged, I know mine didn't complete when I tried at 9% but after 60% I tried again and it went through flawlessly

tadgerloks said:
Let it charge too 60% before trying too flash from rsd, and keep the XML file edited then try again once its charged, I know mine didn't complete when I tried at 9% but after 60% I tried again and it went through flawlessly
Click to expand...
Click to collapse
i didnt know battery life was so crucial to recovery cuz i just tried the xml without editing it and i got to 17/22 so im going to try again at 70% cuz this phone kinda charges fast lol but thanks for all the help guys i really appreciate it.

The same happened to me and I just reflashed the ICS again and all is fine.
Sent from my magnificent Droid RAZR M using XDA Premium!

Yeah I reccomnd charging it , anything above 50% is fine, nd use the edited one, for some reason leaving it unedited causes problems, or sloppy restores

tadgerloks said:
Yeah I reccomnd charging it , anything above 50% is fine, nd use the edited one, for some reason leaving it unedited causes problems, or sloppy restores
Click to expand...
Click to collapse
i'll send you the stock xml doc for you to edit it if thats okay with you. this problem wouldnt matter as much if my phone was also used for work but seeing how my boss and my bosses boss contacts me at this phone and it "had" all my clients information on it and work orders.

Well I feel bad for your data, if you wiped through recovery, or when you restore through fast boot, here's hoping you had some stuff backed up ie contacts notes alarms calendars etc. But once the phone is working Google sync should help with that so no worries

tadgerloks said:
Well I feel bad for your data, if you wiped through recovery, or when you restore through fast boot, here's hoping you had some stuff backed up ie contacts notes alarms calendars etc. But once the phone is working Google sync should help with that so no worries
Click to expand...
Click to collapse
i left it on the charger all night and when i woke up i opend up RSD open the edited xml doc you sent me put th ephone is fast boot mode then hooked it up to the compter and hit start every goes well but once it hits system.img ext4 it fails after a few seconds.

i have to give mad props to everyone that helped my thank you so much my phone is back to woeking again but now ever time i turn in on its in ap fast boot but at the botton it says Fastboot Reason: Sticky hit factory_fastboot but i usually just go back to the boot selection menu and hit normal power up. it works though

To get rid of the sticky fast boot just flash it again, I had same issue, just restore one or 2 more times and it will go away, it is a hassle dealing with it after a while

tadgerloks said:
To get rid of the sticky fast boot just flash it again, I had same issue, just restore one or 2 more times and it will go away, it is a hassle dealing with it after a while
Click to expand...
Click to collapse
the weird thing is that when i select ap boot from the boot options screen and tried flashing it. it would quit at system.img.ext4 no matter what i did but i was messing with the volume buttons (out of boredom) and the ap fastboot came up instantly instead of the boot menu. i looked at the bottom and i dont remeber what it said but it was different then selecting it from boot menu. so i left it alone and attempted to flash it again and next thing i know it worked. and the sticky menu doesnt bother me as long as my phone works im happy lol so the issue is resolved and i can get back to work again lol here is proof
<--- epic game btw

AKG0214 said:
the weird thing is that when i select ap boot from the boot options screen and tried flashing it. it would quit at system.img.ext4 no matter what i did but i was messing with the volume buttons (out of boredom) and the ap fastboot came up instantly instead of the boot menu. i looked at the bottom and i dont remeber what it said but it was different then selecting it from boot menu. so i left it alone and attempted to flash it again and next thing i know it worked. and the sticky menu doesnt bother me as long as my phone works im happy lol so the issue is resolved and i can get back to work again lol here is proof
<--- epic game btw
Click to expand...
Click to collapse
Dead trigger?
Sent from my Xoom using xda app-developers app

Dyelon said:
Dead trigger?
Sent from my Xoom using xda app-developers app
Click to expand...
Click to collapse
Yupp dead trigger, gorgeous graphics too, runs like a dream on high settings

Except for me with the jb leak, I'm seeing lots of glitches in graphics compared to ics.
Sent from my XT907 using xda app-developers app

rav3nous said:
Except for me with the jb leak, I'm seeing lots of glitches in graphics compared to ics.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Well its working fine for me on jb, but hey every device is different I guess, and I hardly play it, trying too pass mc3 and nova 3 instead

a500 stuck at acer logo, stuck at booting recovery kernel image and no drivers

Hi. One time my a500 just get out of battery and turned off. I charged it and turned on and it stucked at acer logo 4ever. It also stuck at booting recovery kernel when pressing pwr + vol - . Nothing happens when im pressing pwr+vol+ . I installed clear win 7 pro x86 and installed usb drivers from acer site. When connecting tablet to PC it says its Unknown device and i cant upadate drivers Im depressed. What can i do?

marcin2010 said:
Hi. One time my a500 just get out of battery and turned off. I charged it and turned on and it stucked at acer logo 4ever. It also stuck at booting recovery kernel when pressing pwr + vol - . Nothing happens when im pressing pwr+vol+ . I installed clear win 7 pro x86 and installed usb drivers from acer site. When connecting tablet to PC it says its Unknown device and i cant upadate drivers Im depressed. What can i do?
Click to expand...
Click to collapse
I had the exact same thing happen to my A500 back in October. Have tried everything I could find on the net to restore it back to factory settings with no success. Of course it happened to me 2 months after the warranty ran out. To say Acer's support suck would be a complement.
Decided to give up on it and convert to one of the new Windows 8 hybrid tablets when available. Found the Android devices to be only good for email, surfing the net or playing around with useless apps that are gimmicky. At least with the windows 8 tablets you can run any of the programs that you run on your windows computer. They seem to have a similar price point as the Ipad but again, I think they are more practical for so many reasons.
I wish you luck and hope you have better luck then I did.
Cheers, TWC

marcin2010 said:
Hi. One time my a500 just get out of battery and turned off. I charged it and turned on and it stucked at acer logo 4ever. It also stuck at booting recovery kernel when pressing pwr + vol - . Nothing happens when im pressing pwr+vol+ . I installed clear win 7 pro x86 and installed usb drivers from acer site. When connecting tablet to PC it says its Unknown device and i cant upadate drivers Im depressed. What can i do?
Click to expand...
Click to collapse
Wots clear win 7? And why can't u update the drivers.
Wot ROM were u on? Maybe hard reset using rotation lock method.
A stock Update.zip might fix it, no drivers needed...
Have a read thru the first 2 guides in my SIG, you'll need yr cpuid for any unbrick method
Sent from my GT-I9300 using Tapatalk 2

clear - fresh installed (no messed drivers). I flashed new bootloader through APX. I were on full stock. Hard reset will clear my movies music and pictures from memory ? upadte zip doesnt works bcs recovery dont boot (only apx and fastboot now)

If you can get to fast boot mode wipe cache first and see if it boots... If it doesn't then flash a recovery.img via fast boot instead....make sure u have a compatible ICS ROM to flash once u have recovery
Sent from my GT-I9300 using Tapatalk 2

Problem is i dont know how to flash via fastboot :| I have ICS stock rom
RECOVERY IS RUNNING If i do wipe menu-wipe data wil i lost all my internal memory things like pictures?

marcin2010 said:
Problem is i dont know how to flash via fastboot :| I have ICS stock rom
RECOVERY IS RUNNING If i do wipe menu-wipe data wil i lost all my internal memory things like pictures?
Click to expand...
Click to collapse
No, thats all kept in a special folder "data/media". CWM Wipe data doesn't touch it unless you specifically enable it to do so.
Sent from my GT-I9300 using Tapatalk 2

ROM is working , big thanks

marcin2010 said:
ROM is working , big thanks
Click to expand...
Click to collapse
You're welcome. Did u just wipe cache from fastboot or did u have to flash a recovery.img?
Sent from my GT-I9300 using Tapatalk 2

i wiped cache ( i did this on another bundle too but didnt wrked)

marcin2010 said:
i wiped cache ( i did this on another bundle too but didnt wrked)
Click to expand...
Click to collapse
Cool thanks
Sent from my GT-I9300 using Tapatalk 2

hi buddy
i am also having a problem with my acer a500, stuck at the acer screen, and when i try to go in recovery, it says recovery verified failed, if you could help me get mine back up and running, i would greatly appreciate it, lol

cj28sc said:
i am also having a problem with my acer a500, stuck at the acer screen, and when i try to go in recovery, it says recovery verified failed, if you could help me get mine back up and running, i would greatly appreciate it, lol
Click to expand...
Click to collapse
Do u have v8? Flash recovery again.
If not best read root guide in my sig
Sent from my GT-I9300 using Tapatalk 2

marcin2010 said:
ROM is working , big thanks
Click to expand...
Click to collapse
So how did you do it? I've tried all the tricks and factory resets and toggle lock and nothing seems to get it to work. I'm guessing you flashed or something?

Can anyone help me with this issue? The BThunder app wants me to be in debug mode, but I can't get into it. Becasue I can not boot.

timsmooth said:
Can anyone help me with this issue? The BThunder app wants me to be in debug mode, but I can't get into it. Becasue I can not boot.
Click to expand...
Click to collapse
IF the auto flash tools do not work, you must use the manual nvflash method, if theres anything wrong it will give an error which you should post, along with what rom you were running.
To save yrself alot of trouble - go to the root guide in my sig and d/l babsector.rar - this will flash the v8/cwm and reset partitions - follow the instructions in that post - and be sure to do a full wipe b4 AND after flashing your rom - ICS/JB only
dibb

My tablet is a sucker
I have a HCL am7-a1 android. I tried to install CMW 5.0.2.0 , it installed, but failed to flash any ROM. afTER THAT i TRIED TO FLASH A NEW cwm ROM, and not my tablet gone dead. It is stuck at bootloader image. It wont go recovery console. ADB works, but fastboot does not work. Followed several posts but all in vain.
Look at the picture where I am stuck:
Model: HCL AM7-A1
ADB shows : HTC dream composite device.
Screen stuck at this picture,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I would like to think I am pretty tech savvy but I want to know what the hell happened in this case. It is similar to what the OP describes but not exact.
First let me set up what the hell happened. I was using Flash Fox to watch Marvel Agents of Shield latest episode and was also downloading a game from the Play store, When all of a sudden it just went black. The screen was still on but it was black. Then the Acer logo came on and it stayed on. I thought it froze and held the power button to shut it off. It powered down just fine. I pressed the power agian and the Acer logo came up and again just hung there. I became a little perplexed and figured I could maybe go into the boot recovery menu by pressing the vol + and power. The little text in the upper left came up saying:
Erasing cache before SD Update...
SD Update CMD: recovery
--update_package=SDCARD: update.zip
Booting recovery kernel image
The Android bot comes up with the spinning blue matrix of leadership in his chest and a status bar appears below but then go directly to the bot on the ground with his chest open and a red ! triangle. It just hangs there for a minute or so and then the Acer logo pops back up and just hangs.
I think I bricked it and through no fault of my own it seems. I mean **** the thing was only running Ice Cream sandwich OS. I am not sure the exact version. All I want to do is see if I can recover the stock OS and have my tablet back. If that is not possible and I have to use a different way to recover using a custom ROM I can do that too. It seems to me that I need a file update.zip on my SD card which I removed before recovering but there is no file on my card named that. If anyone could point me in the right direction it would be greatly appreciated.

stuck
I tried to flash cm10.2 rom but now im stuck on booting primary kernel image.need help

Just reflash skrilax unlocked bootloader
Sent from my GT-I9300 using Tapatalk

Stuck in "Recovery Booting..." loop after flashing jk's Hybrid TMO rom

Hey guys, long time lurker. I've never needed to post before but this is beyond me. Flashed JK's new hybrid rom, following his post exactly:
https://forum.xda-developers.com/verizon-s7-edge/development/rom-t3569416
It rebooted into aroma, ran, and on reboot showed the samsung lock screen, flashed a few times and now says "recovery booting". It's been trying to "boot" recovery for a day now. Flashes the blue text on and off. I've tried the button presses as much as I can to get it into download mode. It will stop flashing when I press Home+Down Vol, but upon release it comes back flashing again. Nothing seems to work, and it never connects to the PC to try Odin or any ADB method of rebooting/forcing download mode. Maybe I can try to drain the battery and go from there? Although that may take days at this point..
Just trying to avoid going to big red at this point.
Thanks!

nightwolf0829 said:
Hey guys, long time lurker. I've never needed to post before but this is beyond me. Flashed JK's new hybrid rom, following his post exactly:
https://forum.xda-developers.com/verizon-s7-edge/development/rom-t3569416
It rebooted into aroma, ran, and on reboot showed the samsung lock screen, flashed a few times and now says "recovery booting". It's been trying to "boot" recovery for a day now. Flashes the blue text on and off. I've tried the button presses as much as I can to get it into download mode. It will stop flashing when I press Home+Down Vol, but upon release it comes back flashing again. Nothing seems to work, and it never connects to the PC to try Odin or any ADB method of rebooting/forcing download mode. Maybe I can try to drain the battery and go from there? Although that may take days at this point..
Just trying to avoid going to big red at this point.
Thanks!
Click to expand...
Click to collapse
first of all were you trying this with a non verizon phone and did you use firmware in my OP or were you trying to flash verizon firmware. Hold Volume Key Down PWR Button and Home Key you have to press all three this take you to download mode reflash eng boot.img with odin then start over. If that dont work flash full firmware in Odin

jrkruse said:
first of all were you trying this with a non verizon phone and did you use firmware in my OP or were you trying to flash verizon firmware. Hold Volume Key Down PWR Button and Home Key you have to press all three this take you to download mode reflash eng boot.img with odin then start over. If that dont work flash full firmware in Odin
Click to expand...
Click to collapse
Hey jrkruse, I've got the Verizon branded S7 Edge. (bought in store.). I was using everything listed in your OP and made sure I got everything correct (the FlashFire settings and sequence as well). I've been running your roms+tweaks forever now, and was previously running the "Echoe" rom rooted and running well enough. (I think I've been using your stuff since my S3/S5 days a long time ago. Never had any issues following your methods until now. )
This exact setup/rom is what I was coming from:
https://forum.xda-developers.com/ve...t/g935-g930-echoerom-multicarrierusa-t3458535
The problem is the phone doesn't respond any key inputs. I've tried everything I can find for the key presses, and it always goes back to "Starting recovery..." text on a black screen. I let it just go for the entire day, and now that the battery is drained I do get an icon to plug it into the charger (so maybe it's not bricked totally yet?). As soon as I try to plug it in it tries to start the "Recovery" boot again without accepting my button inputs. ADB also still doesn't see the phone at all. I assume that some part of the BL is corrupt and it's stuck trying to start it still.. Is there a key press that I can do WHILE plugging it into the usb of my PC or charger to force download mode no matter what? (Like the HTC and maybe the s3 had?). I get the feeling my issue is just because I can't do a full "battery pull" with the soft keys anymore, so it never actually restarts the actual BL and all.
Would some pictures help explain?
Thanks again for all your work!

Here are a couple of pictures to explain a bit more:
The "Booting Recovery.." text that flashes briefly:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The "Charge your phone" picture I get once it's too low on battery:

nightwolf0829 said:
Here are a couple of pictures to explain a bit more:
The "Booting Recovery.." text that flashes briefly:

The "Charge your phone" picture I get once it's too low on battery:
The "Charge your phone" picture I get once it's too low on battery:

Click to expand...
Click to collapse
Pull your sim and sdcard out. Hold the volume down home and power button while phone is dead then plug in while holding those three

Tried that, still doesn't do anything it seems. The second I let go of home, it tried recovery again. Maybe it's just not fully dead somehow? I make-shifted a zip-tie to make the 'No Power, plug in' flash until it -should- be an otherwise dead phone. Am I right in thinking it should be a brick after this, and plugging in 'should' allow me to use Home,Pwr,and Vol Down to get into Odin mode?
Like suffocating your pc,maybe there is a better way to drain the battery all the way?:
Thanks again!

nightwolf0829 said:
Tried that, still doesn't do anything it seems. The second I let go of home, it tried recovery again. Maybe it's just not fully dead somehow? I make-shifted a zip-tie to make the 'No Power, plug in' flash until it -should- be an otherwise dead phone. Am I right in thinking it should be a brick after this, and plugging in 'should' allow me to use Home,Pwr,and Vol Down to get into Odin mode?
Like suffocating your pc,maybe there is a better way to drain the battery all the way?:
Thanks again!
Click to expand...
Click to collapse
Have you tried holding Volume UP + HOME +PWR

That just brings the "Booting Recovery..." flashing again... I also noticed it also doesn't vibrate at all, like they normally do on a startup. The "bzz" letting you know you can let go of PWR doesn't seem to happen ever either.

nightwolf0829 said:
That just brings the "Booting Recovery..." flashing again... I also noticed it also doesn't vibrate at all, like they normally do on a startup. The "bzz" letting you know you can let go of PWR doesn't seem to happen ever either.
Click to expand...
Click to collapse
Give me a run down on what happened during flash. Including firmware you were on etc. Maybe I can at least keep this from happening too someone else
---------- Post added at 08:41 PM ---------- Previous post was at 08:36 PM ----------
I'm thinking flashfire must have failed in flashing the bootloaders

Makes sense, so this is actually a brick I suppose?
S7 was running your Echoe Rom Port (the AROMA_Version 1.5, as in the OP of that thread.) No updates or changes other than updates to FlashFire and installed apps. Was previously a MM rooted phone before flashing the Echoe Rom. Ran the engineering boot setup from early 2017 (if there are any differences, I can only find the one root method). Sorry I cant open my FlashFire backup in order to check the versions of my BL/Firmware/Modem/etc. I can post the zip somewhere and send you if if there is a way to extract my software versions?
Followed your exact setup to Flash over to your TMO Hybrid rom as in your OP of this thread:
https://forum.xda-developers.com/verizon-s7-edge/development/rom-t3569416
I made sure to have the installs in the correct order and check all of the folders (and uncheck injection of SuperSU).
Phone rebooted up to the "Samsung S7" white unlock logo a couple of times, then rebooted into the "Recovery booting..." loop.
Side note, would the 300 Ohm USB dongle trick possibly work in this case? Or is the BL probably gone/corrupt and I'm fully bricked?
Thanks!

nightwolf0829 said:
Makes sense, so this is actually a brick I suppose?
S7 was running your Echoe Rom Port (the AROMA_Version 1.5, as in the OP of that thread.) No updates or changes other than updates to FlashFire and installed apps. Was previously a MM rooted phone before flashing the Echoe Rom. Ran the engineering boot setup from early 2017 (if there are any differences, I can only find the one root method). Sorry I cant open my FlashFire backup in order to check the versions of my BL/Firmware/Modem/etc. I can post the zip somewhere and send you if if there is a way to extract my software versions?
Followed your exact setup to Flash over to your TMO Hybrid rom as in your OP of this thread:
https://forum.xda-developers.com/verizon-s7-edge/development/rom-t3569416
I made sure to have the installs in the correct order and check all of the folders (and uncheck injection of SuperSU).
Phone rebooted up to the "Samsung S7" white unlock logo a couple of times, then rebooted into the "Recovery booting..." loop.
Side note, would the 300 Ohm USB dongle trick possibly work in this case? Or is the BL probably gone/corrupt and I'm fully bricked?
Thanks!
Click to expand...
Click to collapse
In settings in Flashfire did you check allow flashing bootloader then when you added the zip did you check to mount system

Not that this helps, but my galaxy tab 4 did something similar.
Installed the update firmware in Odin, rebooted, and it didn't get past the Samsung splash screen. Next reboot, exactly what you said... recovery rebooting after that.
The recovery was gone, but I could boot into download mode that gave me an error stating to use kies to install the firmware. Kies wouldn't recognize the device. Any flash attempt of os systems in Odin resulted in fails.
My issue was that the system partition got completely erased and set to 0. Therefore, it had no space to install anything.
Next, I flashed a stock recovery, but had the error on writing system due to the partition corruption. I had to flash twrp and change the system partition from 0 to whatever it should have been. After that, I could Odin firmware and was back in business.
Long story short, this probably doesn't help because we can't flash recoveries, but I wonder if your system partition got corrupted?
Sent from my SM-G930P using XDA-Developers Legacy app

jrkruse said:
In settings in Flashfire did you check allow flashing bootloader then when you added the zip did you check to mount system
Click to expand...
Click to collapse
Pretty sure I did, but I'm honestly unsure at this point. I tried following your post exactly, as always, but it is possible I skipped that step. I really don't think so as I checked it all multiple times.
Sorry I can't recall better.
Does this change any options I may of had for recovery? I'm sure it's super unlikely to repair at this point as Odin, and Windoze never sees the device at any point of any restart. I also opened it up and manually disconnected the battery just-in-case, as I figured it wasn't actually turning off. Still the same, wont boot into Download mode, Recovery just displays the blue booting text.
Let me know if anything I can get from the phone would help before I try to get it replaced one way or another.

lvpre said:
Not that this helps, but my galaxy tab 4 did something similar.
Installed the update firmware in Odin, rebooted, and it didn't get past the Samsung splash screen. Next reboot, exactly what you said... recovery rebooting after that.
The recovery was gone, but I could boot into download mode that gave me an error stating to use kies to install the firmware. Kies wouldn't recognize the device. Any flash attempt of os systems in Odin resulted in fails.
My issue was that the system partition got completely erased and set to 0. Therefore, it had no space to install anything.
Next, I flashed a stock recovery, but had the error on writing system due to the partition corruption. I had to flash twrp and change the system partition from 0 to whatever it should have been. After that, I could Odin firmware and was back in business.
Long story short, this probably doesn't help because we can't flash recoveries, but I wonder if your system partition got corrupted?
Sent from my SM-G930P using XDA-Developers Legacy app
Click to expand...
Click to collapse
I totally think something low-level is corrupt/gone. I bet it's the BL just based on the fact it shows only a black screen when I do the key press. I'm betting it's a brick, but I'm waiting to make sure jrkruse has anything he needs to stop this happening to anyone else before I try to replace it.

nightwolf0829 said:
I totally think something low-level is corrupt/gone. I bet it's the BL just based on the fact it shows only a black screen when I do the key press. I'm betting it's a brick, but I'm waiting to make sure jrkruse has anything he needs to stop this happening to anyone else before I try to replace it.
Click to expand...
Click to collapse
I put a warning and a work around in my thread
---------- Post added at 10:45 PM ---------- Previous post was at 10:43 PM ----------
nightwolf0829 said:
Pretty sure I did, but I'm honestly unsure at this point. I tried following your post exactly, as always, but it is possible I skipped that step. I really don't think so as I checked it all multiple times.
Sorry I can't recall better.
Does this change any options I may of had for recovery? I'm sure it's super unlikely to repair at this point as Odin, and Windoze never sees the device at any point of any restart. I also opened it up and manually disconnected the battery just-in-case, as I figured it wasn't actually turning off. Still the same, wont boot into Download mode, Recovery just displays the blue booting text.
Let me know if anything I can get from the phone would help before I try to get it replaced one way or another.
Click to expand...
Click to collapse
Tell big red that the nougat update fried your phone. Hopefully they will replace. Keep me updated

jrkruse said:
I put a warning and a work around in my thread
---------- Post added at 10:45 PM ---------- Previous post was at 10:43 PM ----------
Tell big red that the nougat update fried your phone. Hopefully they will replace. Keep me updated
Click to expand...
Click to collapse
Will do! Thanks again! Hope my phone was just a fluke thing.

nightwolf0829 said:
Makes sense, so this is actually a brick I suppose?
S7 was running your Echoe Rom Port (the AROMA_Version 1.5, as in the OP of that thread.) No updates or changes other than updates to FlashFire and installed apps. Was previously a MM rooted phone before flashing the Echoe Rom. Ran the engineering boot setup from early 2017 (if there are any differences, I can only find the one root method). Sorry I cant open my FlashFire backup in order to check the versions of my BL/Firmware/Modem/etc. I can post the zip somewhere and send you if if there is a way to extract my software versions?
Followed your exact setup to Flash over to your TMO Hybrid rom as in your OP of this thread:
https://forum.xda-developers.com/verizon-s7-edge/development/rom-t3569416
I made sure to have the installs in the correct order and check all of the folders (and uncheck injection of SuperSU).
Phone rebooted up to the "Samsung S7" white unlock logo a couple of times, then rebooted into the "Recovery booting..." loop.
Side note, would the 300 Ohm USB dongle trick possibly work in this case? Or is the BL probably gone/corrupt and I'm fully bricked?
Thanks!
Click to expand...
Click to collapse
Which version of his Hybrid ROM did you install?
I don't recall if the USB dongle is compatible with the S7, but I have one laying around and will see if it works on the S7.
You are using an S7 Edge, not a flat, right?

I can confirm that the USB jig does not work on my S7 flat.

Try holding down power, BOTH volume and and down and the home key. all at the same time.. dont release any buttons... just wait about 8-10 seconds... that brings up a different boot option screen. (reboot normal, safe boot. wipe
... I was under the impression I could flash the Hybrid mode running any rom if I was rooted and had flashfire.. I tried flashing Hybrid rom running Stang rom.. and also encountered boot loop.. and above it how I stopped the bootloop. Good luck and hope this works for you also.

ronschuck said:
Try holding down power, BOTH volume and and down and the home key. all at the same time.. dont release any buttons... just wait about 8-10 seconds... that brings up a different boot option screen. (reboot normal, safe boot. wipe
... I was under the impression I could flash the Hybrid mode running any rom if I was rooted and had flashfire.. I tried flashing Hybrid rom running Stang rom.. and also encountered boot loop.. and above it how I stopped the bootloop. Good luck and hope this works for you also.
Click to expand...
Click to collapse
Hey thanks for trying but I tried everything on that phone. Had to go to big red and get a replacement. Luckily they got me one without having to go through Assurion.

Recover bricked M3?

Hi guys, wondering if you could help me here.
1) I recently upgraded my M3 to Nougat by mistake and tried to use the "C100B009" full rom to downgrade to MM using "Power + Vol up + Vol down".
2) I was stuck in eRecovery after the update and I realized i missed out the rollback package. So i downloaded and extracted the contents of rollback package to "dload" folder and ran the update again. But it seems afterwards, the tablet was stuck on ""Your device is booting now", and the Power + Vol up + Vol down doesn't work anymore.
3) I managed to get into fastboot and bootloader was locked. So i issued the unlock command based on keys i had saved earlier. The command said it worked and it would reboot and wipe the phone.
4) After the reboot, it seems i'm again stuck in "Your device is booting now". I can't shut down the tablet as it would just reboot, vibrate twice and show the same message again. Eventually, it flat of battery.
5) I also don't seem to be able to go into fastboot anymore. Holding Vol down and plugging into computer still gets me the "Your device is booting now" message. Also, the tablet can't hold a charge. It will blink red. Seem to charge a little after a while, then power itself into "Your device is booting now" message, drain flat, and repeat the cycle again.
Anyone could give any advice on this or would i have to bring down to a service centre for replacement..... :crying:

If you had read here other threads you will be able to solve at least a big part of your problem.

I just had similar situation this weekend while trying updates. I let it die, then tried to boot by plugging into good AC adapter (not PC USB). It showed booting for a while. Eventually it just came up. I had done that dead battery, then little bit of charge multiple times. Good luck.

nostep said:
I just had similar situation this weekend while trying updates. I let it die, then tried to boot by plugging into good AC adapter (not PC USB). It showed booting for a while. Eventually it just came up. I had done that dead battery, then little bit of charge multiple times. Good luck.
Click to expand...
Click to collapse
Hmm, when you said it just came up, did you mean the tablet booted up normally? Or you meant you could go into fastboot after your staggered charging? Because i tried charging with AC adapter before, but the tablet turns itself on after a while, and then just runs itself flat again with the "Your device is booting now" message. I can't seem to trigger fastboot mode off it.

I had previously loaded half of c128b350 and needed to load the second half via twrp. I loaded the wrong twrp (4.1) and it was stuck trying to boot it. I cannot get into fastboot without OS working. Anyway after 10 hours it finally booted the half finished b350 and I managed to get the rest from there.

@fallen_13 do you solve this problems? I've got exactly problem as you
---------- Post added at 11:21 PM ---------- Previous post was at 11:21 PM ----------
[/COLOR @fallen_13 do you solve this problems? I've got exactly problem as you

romeo_coi said:
@fallen_13 do you solve this problems? I've got exactly problem as you
---------- Post added at 11:21 PM ---------- Previous post was at 11:21 PM ----------
[/COLOR @fallen_13 do you solve this problems? I've got exactly problem as you
Click to expand...
Click to collapse
I tried my luck and sent it into service centre. Been a month and still waiting for replacement since they didn't have stock.

fallen_13 said:
I tried my luck and sent it into service centre. Been a month and still waiting for replacement since they didn't have stock.
Click to expand...
Click to collapse
Just messed up with this sh!t 3 days ago
I've tried several ways I can search on xda, 4pda and google.... but still no luck.
The dead battery trick then "Volume (-) + USB plug in to pc" seem to be useless.
According to the confirmation of member MuHuCTP23 in 4pda thread below, there is only one user was able to boot tablet to bootloader after did a "fastboot oem unlock" when in rollback process, What a lucky guy! And him doesn't know how he managed to got device into bootloader.
http://4pda.ru/forum/index.php?showtopic=780572&st=2020#entry64535878
Now I'm reading from this post:
https://forum.xda-developers.com/huawei-p9lite/help/huawei-p9-lite-vns-l31-fastboot-adb-t3590158
And other threads about the "totally bricked Huawei android phone" becasue of "flashing rollback wrong ways".
Some users confirmed the trick "3 button in cold boot": press and hold power button untill device powers off then release power button, quickly press and hold Vol (-) button and connect the usb cable (which is already attached to pc) right before or exactly when device vibrates will able to take device into bootloader mode. But it's really matter about timing when connect the usb cable to device.
So I tried this way and it actually did something difference:
When connect usb cable at "wrong time", device starts with 3 options screen instead of the no option screen. It's a little bit confuse here, there're two bootloop screens:
1- The device shows: Your device is unlock... and under this device is trying to boot direct to recovery.
2- The device shows: Your device is unlock... and there're 3 options choice as normal, but whatever we choice it'll be stucked as well as before :silly:
And when I can connect usb to device at the "right time", it doesn't startup in bootloop but the screen with red bolt alert then again it starts again in bootloop. I think it was tried to boot itself to bootloader mode but due to the low battery it only shows the red bolt alert. This thing is very weird because AFAIK even if You totally drained the battery the bootloader will always show up.
....
After 3 days continous try and try, now I'm thinking about give it up and send it to the store, my tablet is being covered under 30 days return policy. The main problem here is I bought this tab from Japan but I'm living in Vietnam, so Idk if foreign customers will be treated the same way as domestic customers or not. I email to the support and waiting for the reply .

@romeo_coi
I believe you and i went through the same steps. I spent about 3 months researching the subject before giving in and sending to service centre. My guess is that after the unsuccessful rollback, when we unlock the bootloader, the process will erase data from the tablet. But maybe some partition information had changed, so after the erase completes, the tablet becomes hard bricked instead.
Anyway, i wish you luck on the return to Japan. One thing you can try before sending back is to drain the battery fully by taping down the power button. Once that happens, you will no longer see the red bolt alert. Then you can just report as an unable to power on issue.

fallen_13 said:
@romeo_coi
I believe you and i went through the same steps. I spent about 3 months researching the subject before giving in and sending to service centre. My guess is that after the unsuccessful rollback, when we unlock the bootloader, the process will erase data from the tablet. But maybe some partition information had changed, so after the erase completes, the tablet becomes hard bricked instead.
Anyway, i wish you luck on the return to Japan. One thing you can try before sending back is to drain the battery fully by taping down the power button. Once that happens, you will no longer see the red bolt alert. Then you can just report as an unable to power on issue.
Click to expand...
Click to collapse
-I don't think after re-unlock bootloader in rollback processing, it cannot erase data because mine was stucked right after device restart without successfully boot into erase data step. May be it caused due to wrong patritions flashing then some functions not working correctly as it should. And may be with some special tools, Huawei engineers can re-write the partritions and save the device.
-And about drained the battery before contacting the supplier, I think it will no help because they can easily plug a charger into device and found that we're messed arround with system modification. So I explained to them exactly how the deivce is but in another way: after received and used device in some days for testing, then I perform a factory reset to clean it up for my own settings but the device stuck at boot screen.... Hope they accepted and return another tab for me. If not, then I have luxury paperweight
-In this case, it may be weird and hard to believe but trust me, I'm working for a large chain store system in Vietnam (smartphone cate. of course) and people in my country sometimes did something they don't even f**king know what is it. I've seen some devices with the unlocking bootloder processing hasn't done completely by previous user, and the next users are f*cked already because they will never be noticed untill they do something such as update system, unlock bootloader again.. or even just perform a factory reset. Once these processing done (luckily) completely, devices will come back to the original state and safe for use. But in some cases, these processing taking errors then devices will be bricked. I think it's the most reasonable explanation why there're more and more OEMs accepted to covered "devices with software modifications" in warranty policy.
Below is the warranty policy of the Motorola X Pure 2015 for example:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Hi there,
I was in Japan and bought BTV-W09 on 11/29 and just returned back to Canada. (Mediapad M3 is not officially available in Canada.)
And right away I upgraded to Nougat but don't like it, so down graded back to 6.0 through 2 UPDATE.APPs via dload folder method.
I found that after the down grade,the fingerprint sensor/home button not working at all.
So I tried to repeat the process of installing UPDATE.APP again. And ended up exactly the same situation as you guys.
Booting stuck at "Huawei MediaPad" + "Powered by Android" screen. Even with proper charger hooked up, the battery drains and never charge enough to do anything.
I can not force shut down, can't go into recovery or nothing. But I managed to get into some sort of recover screen. ( Press Power till the screen gets blank, then plug USB while pressing Vol-. But the recovery requires HiSuite. Since my PC is Linux and I run Win7 via VirtualBox, without sufficient battery power I can't even utilize this method.
If you guys still trying to unbrick/restore, at least you can try go into that mode by pressing Vol- immediately after pressing Power and plug in USB.
I will leave it a while to see weather the battery charges, then use some native Windows PC and HiSuite and see what happens.
If everything fails, then I have to send back to Huawei Japan for repair or use it as a paper weight!
Please let me know the current status of yours.

x52-curcuma said:
Hi there,
I was in Japan and bought BTV-W09 on 11/29 and just returned back to Canada. (Mediapad M3 is not officially available in Canada.)
And right away I upgraded to Nougat but don't like it, so down graded back to 6.0 through 2 UPDATE.APPs via dload folder method.
I found that after the down grade,the fingerprint sensor/home button not working at all.
So I tried to repeat the process of installing UPDATE.APP again. And ended up exactly the same situation as you guys.
Booting stuck at "Huawei MediaPad" + "Powered by Android" screen. Even with proper charger hooked up, the battery drains and never charge enough to do anything.
I can not force shut down, can't go into recovery or nothing. But I managed to get into some sort of recover screen. ( Press Power till the screen gets blank, then plug USB while pressing Vol-. But the recovery requires HiSuite. Since my PC is Linux and I run Win7 via VirtualBox, without sufficient battery power I can't even utilize this method.
If you guys still trying to unbrick/restore, at least you can try go into that mode by pressing Vol- immediately after pressing Power and plug in USB.
I will leave it a while to see weather the battery charges, then use some native Windows PC and HiSuite and see what happens.
If everything fails, then I have to send back to Huawei Japan for repair or use it as a paper weight!
Please let me know the current status of yours.
Click to expand...
Click to collapse
Can try power + vol up for ~3 seconds, it shuts down, then let go (timing, if you keep holding it'll go back to the loop) and it should boot to this recovery screen with 2 options, restore factory and shutdown (not fastboot or twrp). Least that's what mine does W09.

piloki said:
Can try power + vol up for ~3 seconds, it shuts down, then let go (timing, if you keep holding it'll go back to the loop) and it should boot to this recovery screen with 2 options, restore factory and shutdown (not fastboot or twrp). Least that's what mine does W09.
Click to expand...
Click to collapse
Didn't work for me. It does not charge enough. Auto shut down after about 5 min. stuck at boot then shut down for 3~4 min. of charging, and repeating forever. Just before finishing this charging, press Vol up + USB plug-in takes me into Fastboot & Rescue mode. Seems like it is missing eRecovery. Anyways, it doesn't connect to HiSuite running on native Win7 as it does not give me the required non-debugging mode connection.
Later I will try flash eRecovery image via fastboot. Most likely it will not work though without USB-Debugging on.

Okay, fastboot does not work. I can send BOOT.img, RECOVERY.img etc to W09, but can not write them into it due to lack of debugging. When getting into fastboot & rescue mode it also shows the link for rescue detail, bu the site is non-existing.
Most of the instructions EMUI/Huawei provide are useless anyway.
My remaining options are getting very little now.

I guess there is no solution to this. HiSuite's System Recovery allows you to connect W09 without debugging, but the function supports only Mediapad T2. M3 is more than a year old model but Huawei can not support it is unbelievable!
So, I gave up.

x52-curcuma said:
I guess there is no solution to this. HiSuite's System Recovery allows you to connect W09 without debugging, but the function supports only Mediapad T2. M3 is more than a year old model but Huawei can not support it is unbelievable!
So, I gave up.
Click to expand...
Click to collapse
Ah sorry to hear. You try the sd card method?

piloki said:
Ah sorry to hear. You try the sd card method?
Click to expand...
Click to collapse
Yes, I have tried that as well. Nothing works. The worst part is, aside from poor Huawei support, the battery will not charge more than a few minutes worth.