The title says it all.
It was fine yesterday, I came home today and it was stuck on the splash screen. Cant enter the recovery to factory reset, and it wont let me unlock the boot loader. But I can still access the fastboot mode. Any tips?
Anyone have any ideas what might be wrong?
fielddb said:
Anyone have any ideas what might be wrong?
Click to expand...
Click to collapse
use fastboot to restore a stock image.
This is what I get when I try to wipe the device.
{
"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"
}
Bump
Sent from my HTC One using xda app-developers app
Someone must know something
I saw this on one tablet. My guess is there is some emmc corruption. I was able to get around it by doing the factory flash over and over until it eventually went away, possibly because the emmc firmware locked some bad sectors out.
so my best bet would be to download the factory image from Google and spam the flash-all.bat file?
Looking back at my notes, the error was like yours and prevented unlock, which made flashing factory impossible. According to my notes I booted into recovery and wiped a few times.
Can you be more specific with the part about not being able to enter recovery?
What buttons did you press and what were the results?
Also have you rebooted your PC?
When I press enter recovery. The device goes to the Google splash screen and freezes.
And I have rebooted my PC, as well as trying two different PC with different OS's
fielddb said:
When I press enter recovery. The device goes to the Google splash screen and freezes.
And I have rebooted my PC, as well as trying two different PC with different OS's
Click to expand...
Click to collapse
Can you try
fastboot erase userdata
fastboot erase cache
fastboot oem unlock
D:\Program Files\Android\android-sdk\platform-tools>fastboot erase cache
erasing 'cache'...
FAILED (status read failed (Too many links))
finished. total time: 411.474s
D:\Program Files\Android\android-sdk\platform-tools>fastboot erase userdata
erasing 'userdata'...
FAILED (status read failed (Too many links))
finished. total time: 541.982s
D:\Program Files\Android\android-sdk\platform-tools>fastboot oem unlock
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
FAILED (status read failed (Too many links))
finished. total time: 315.871s
D:\Program Files\Android\android-sdk\platform-tools>
Click to expand...
Click to collapse
The device gets locked up here
I think your emmc is corrupted, possibly affecting the partition info.
There isn't a whole lot of info on how to recover from this.
sfhub said:
I think your emmc is corrupted, possibly affecting the partition info.
There isn't a whole lot of info on how to recover from this.
Click to expand...
Click to collapse
I'll just send it through RMA. Since it's not unlocked or rooted.
I just ran into the same issue. I think my memory is dead but I am in slightly deeper poop. I posted on another forum since XDA was down for a bit but here is what I wrote.
Hi everyone! My device just ran into some trouble and I couldn't find any other thread on here to help out so I am starting a new one. Here is what happened:
I was sitting on the computer and at the corner of my eye I saw my Nexus 7 (2013) reboot. After which it got stuck on the Google logo. Tried rebooting multiple times but still stuck at the logo (not the X screen but the screen that says Google in white letters). I had flashed TWRP so i decided to just factory reset the device. That was a no go as TWRP hangs on TEAMWIN screen.
At this point i said 'fuggit' and decided to restore factory images. I downloaded the two available images from google and both fail to restore as the flash-all throws up an error saying that it can't write to flash memory. I tried manually flashing with fastboot boot, recovery and system and got the same message.
Then I remembered that locking and unlocking the bootloader forces the factory reset so I decided to do that. While locking was successful I was unable to unlock the device as it tried to erase user data but it gets stuck with the message: 'erasing userdata...' and it doesn't go any further.
At this point I am out of ideas. I called a Google rep and tried to talk to a person but the representative I got was strictly working by the script and after I explained the issue I had (pretty much verbatim on whats above) she asked me if I had tried to reboot the device and then proceeded to ask me to reboot again. After we went through all the steps she was stumped and told me to contact manufacturer. Given that I had flashed a custom recovery and my bootloader is now locked and I can't flash stock recovery what are my options? Any ideas?
Click to expand...
Click to collapse
I called Asus and spoke to a rep that seemed to know of this issue and told me that the memory module might be bad. I am sending the unit in to be serviced or replaced. I'll post when I have any more info on this.
h77ps said:
I called Asus and spoke to a rep that seemed to know of this issue and told me that the memory module might be bad. I am sending the unit in to be serviced or replaced. I'll post when I have any more info on this.
Click to expand...
Click to collapse
Hey I have the same issue here... did you fix the problem or what happened?
h77ps said:
I called Asus and spoke to a rep that seemed to know of this issue and told me that the memory module might be bad. I am sending the unit in to be serviced or replaced. I'll post when I have any more info on this.
Click to expand...
Click to collapse
i have the same problem! just made a "ticket" about it on their website. unable to call support bc they're closed at the moment. did they replace your device?
Same problems for me now
Yesterday, touchscreen stopped responding, then a reboot and now it is stuck @ "Google Logo"
I tried flashing the factory image without wipe, then with wipe, then with erase + update + wipe. But i had no luck. Device seems to be dead. I will try to get a new N7 from the shop I bought it.
I've been battling this same issue for a couple days. Weird, have had mine since last August(!) with no real problems. Rooted but pretty much running stock since day one. Suddenly started being unresponsive after flashing CleanRom (not that I blame ROM), was able to get to TWRP to restore a stock backup, but then again no touchscreen response. Tried to reboot and now all I ever get is GOOGLE screen with unlocked bootloader symbol. I can boot to bootloader screen and have tried every imaginable way to wipe and flash stock again to no avail. Can't boot to recovery, nothing. Its ridiculous, but I'm screwed so far. No way I can return it now...unless maybe I relock bootloader and ASUS will do something for me. Please keep us posted any of you who resolve this!
Related
Ok, quick rundown of the issue........
My fiancee's Incredible has recently developed a problem with the power button. Somehow, it is indefinitely engaged as if the button is being held down all the time (but it's not). I have taken three screws out of the device to open the back panel just enough to troubleshoot the interior power button (removing the fourth screw with the VOID sticker would be a bad idea). Nothing seems to be fixing this issue. She wants to swap the phone out for a another one since it is still under warranty. But, of course, I have to downgrade the radio and unroot before this can be done.
Booting into HBOOT does nothing. As the power button is permanently engaged. I cannot nav with the volume button or make a selection. Only way out of there is to pull the battery. I can, however, get into Recovery and move about and make selections just fine with the optical button. I read where people have supposedly gotten the radio to flash from Recovery as opposed to HBOOT just fine. But, wanted to check with the community as to the correct process and if it can be done before I attempt anything else.
Also, is there a newer unroot method that does not require a manual radio downgrade? I've been with the Thunderbolt for quite a while now and have been out of the loop on the happenings with the DINC.
Any advice would be greatly appreciated.
Thanks.
EDIT: Btw, her DINC is currently running Nil's Gingersense with the 0808 radio. Also running the SuperCharge script to fix the sense rebooting issues.
The only way to flash a radio is thru hboot, or by using fastboot. If fastboot activates while plugged in to the pc try that.
The only way to get s-on again would be to downgrade the radio, and then use the flashable s-on.zip from the unrevoked site.
Also just wondering but if the power button is or acts like its stuck down, how do you power on the phone, does it just turn on when you insert the battery? Do you have to pull the battery to shut it off, how about when the screen goes off?
Nils BGS has trackball wake/unlock enabled by default, that's likely how they wake the phone.
I haven't used ADB to flash files so excuse my lack of experience but could the OP perform necessary radio downgrade using ADB to push files and manually install that way?
cmlusco said:
Also just wondering but if the power button is or acts like its stuck down, how do you power on the phone, does it just turn on when you insert the battery? Do you have to pull the battery to shut it off, how about when the screen goes off?
Click to expand...
Click to collapse
The phone turns on as soon as the battery is inserted. Really crappy thing about it is one time her battery ran completely down, and when the charger got inserted it went into an indefinite boot loop. The HTC splash screen hit, but since there was no juice in the battery it would shut off, then attempt it over and over and battery would never get a charge. Luckily we have a friend who also has an Inc, so we just swapped batteries with him and have made sure her phone/battery never completely runs down since.
Yes, Nil's rom has the ability to wake the phone with the trackball, and we set the screen to turn off after 15 seconds since we can't do it with the power button.
Can you tell me a little bit more about the fastboot method with USB? I've never done it that way before. Also, would it be possible to it using ADB shell as the other poster asked?
Thanks for your help.
Just looked it up. I think I have this. Will try later tonight when I get home.
If anyone feels the need to pass any further info along though, please do.
One last question though: If the phone should brick, does Verizon have the ability or do they bother going into the phone to see the data? In other words, if it bricks, and we swap it out per warranty, will they be able to tell the phone has been hacked?
Hackenstein said:
Just looked it up. I think I have this. Will try later tonight when I get home.
If anyone feels the need to pass any further info along though, please do.
One last question though: If the phone should brick, does Verizon have the ability or do they bother going into the phone to see the data? In other words, if it bricks, and we swap it out per warranty, will they be able to tell the phone has been hacked?
Click to expand...
Click to collapse
Fastboot is pretty simple once you get your pc set up with adb. You need to take a hboot flashable of tje radio you want and extract the radio.img from it, and stick it in the same folder as fastboot.exe. Then boot the phone in to hboot while connected to the pc. Hopefully it will activate hboot, and usb plug will be highlighted in red on the top of the hboot screen. Then open a cmd prompt on your pc and navigate to the folder where fastboot.exe is. Then type without quotes, " fastboot flash recovery recovery.img " and hit enter, it should copy the file to the phone and then flash it.
If the phone bricks somehow it shouldnt turn on at all, meaning verizon would not be able to access any info or tell if its been hacked. But if the phone still enters hboot where it says s-off at the top then they would know, and might give you the old sorry but you voided your warranty.
As far as i know there is no way to use adb to flash the radio, the only way you could use adb is to push the recovery.img to your phone somewhere and then use fastboot to flash it. Eg " fastboot flash recovery /system/radio.img ".
Thanks again for your info.
I have decided to wait until the replacement phone comes before I attempt to downgrade it. Because if I go back to the stock ROM, I assume it probably doesn't have Nil's param that allows the optical button to bring the phone out of sleep, which would render the phone completely useless after it powers on and the screen goes off.
I'm gonna have her call Verizon customer service and get a replacement shipped out. Or do they require you to send the phone in to them first?
I finally am able to get around to downgrading the radio on this DINC. The replacement came yesterday and I only have 5 days to get the buggy one post marked.
I've hit a bit of a road block with flashing the 07.28 radio in fastboot. I keep getting this error:
C:\Android>fastboot flash radio radio.img
sending 'radio' (22272 KB)... OKAY [ 3.178s]
writing 'radio'... FAILED (remote: not allowed)
finished. total time: 3.185s
I've also tried it from the platform tools dir:
C:\android-sdk-windows\platform-tools>fastboot flash radio radio.img
sending 'radio' (22272 KB)... OKAY [ 3.300s]
writing 'radio'... FAILED (remote: not allowed)
finished. total time: 3.305s
It just isn't working.
Fastboot is recognizing my device, FYI:
C:\android-sdk-windows\platform-tools>fastboot devices
HT132HJ01421 fastboot
Can anyone help?
Hackenstein said:
I finally am able to get around to downgrading the radio on this DINC. The replacement came yesterday and I only have 5 days to get the buggy one post marked.
I've hit a bit of a road block with flashing the 07.28 radio in fastboot. I keep getting this error:
C:\Android>fastboot flash radio radio.img
sending 'radio' (22272 KB)... OKAY [ 3.178s]
writing 'radio'... FAILED (remote: not allowed)
finished. total time: 3.185s
I've also tried it from the platform tools dir:
C:\android-sdk-windows\platform-tools>fastboot flash radio radio.img
sending 'radio' (22272 KB)... OKAY [ 3.300s]
writing 'radio'... FAILED (remote: not allowed)
finished. total time: 3.305s
It just isn't working.
Fastboot is recognizing my device, FYI:
C:\android-sdk-windows\platform-tools>fastboot devices
HT132HJ01421 fastboot
Can anyone help?
Click to expand...
Click to collapse
I believe I have found a way to flash the radio thru recovery. This is the way its done on an evo 4g, but im not positive it will work on an incredible. Its worth a try though, it will either flash and work or it wont flash at all. http://dinc.does-it.net/Incredible_C_Radio_2.15.00.07.28_Flashable.zip
cmlusco said:
I believe I have found a way to flash the radio thru recovery. This is the way its done on an evo 4g, but im not positive it will work on an incredible. Its worth a try though, it will either flash and work or it wont flash at all. http://dinc.does-it.net/Incredible_C_Radio_2.15.00.07.28_Flashable.zip
Click to expand...
Click to collapse
I was so hopeful there for a second.
I moved the file to the SD card, booted into Recovery, flashed the file and it said "Downgrading Radio", and a couple seconds later it went back to the main Recovery menu. Went into HBOOT to check it out, and it did not work
The 0808 radio is still intact.
Honestly, I'd like to just brick the phone at this point. But, I don't think I can even do that with the issues I have with the damn power button. I can't get anything to flash correctly.
One last thing -- just to make sure we're on the same page:
I chose "install zip from SD card" when I tried to flash the radio. What if I change the file name to "update" and select the "flash from update.zip" option? Might try that later when I get another shot at it (my fiancee had to get back to work so I'm without a battery to power the phone until she gets home later).
{
"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"
}
Success!!!!!!!
Finally got this mutha to cooperate. Somehow, the radio finally flashed in the bootloader. Then, I ran unrevoked s-on and ran the ROM downgrade. Superuser is gone and all is well. It will be a huge pleasure to send this SOB back to Verizon!
Thank you for all your advice and suggestions.
Hackenstein said:
Success!!!!!!!
Finally got this mutha to cooperate. Somehow, the radio finally flashed in the bootloader. Then, I ran unrevoked s-on and ran the ROM downgrade. Superuser is gone and all is well. It will be a huge pleasure to send this SOB back to Verizon!
Thank you for all your advice and suggestions.
Click to expand...
Click to collapse
Glad to hear it.
Hey guys
ive a problem
i have a rooted one x i already flashed android revolution 3.0 over it
but i wanted to change to android revolution lite 4.0
thats what ive done:
-download the "install-boot.bat"
-got to fastboot mode on my phone
-try to install the boot.bat ...but faild
-i think ive forgoten to superwibe... so ive done that
-again try to install boot.bat...wont work again
-try to go to recovery ...but just get a kind of a boot loop
-reinstall recovery
-still the same problem
i cant get into the recovery mode and cant boot the phone i never had this problem befor whit my android hd2
kind of "progress": now i can go to (i think it is) the start of the recovery mode: there is a lying htc phone whit a green circle with arrows but afer a while it turns into a standing htc phone whit a red exclamation mark
so what ive to do now??? i hope i havent broke the phone!!!! plz help me
Try erasing your cache in fastboot "fastboot erase cache" and see if that helps.
thanks for your reply but it says:
erasing 'cash' ...
FAILD <remote: not allowed>
finished. total time 0.067s
DAMNN no more guarantee
Okay I'm assuming that you have used fastboot before. And I assume that you have HTC drivers installed. I think your phone is going into bootloop because of the boot.img failed to flash.
I'm assuming that you are on the "fastboot USB" mode in your phone when you try to install the "install-boot.bat" right?
Because going into bootloader you start of with just HBOOT. You need to be in fastboot USB to flash boot.img
{
"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"
}
yes i was on fasboot usb mode ...
so i have to try intall "install-boot.bat" again?
i get this error report
which says that AdbWinAbi.dll is missing
You can try I guess. But if it fails again I am stumped on what to do? Maybe start from scratch and return to stock and then flash ARHD 4.0.0
ok and how can i do that?...becaus factory reset wont work either(i think because of the bootloop)
please i need your help!!!
I can't read what ever the text is but it looks like its failing due to a missing DLL
Sent from my HTC One X using xda premium
Why do you want to do that .bat thing? For changing ROM you go via CWM after you put the downloaded zip on the storage card...
And flashing the appropriate boot.img the particular chef is providing via fastboot and cmd window.
Did you do a backup of your original ROM via CWM? Did you do one of the rooted ROM?
You probably have to start from scratch...read the sticky in the devs section first..excellent guides put up there...good luck
Sent from my HTC One X using xda premium
Hi guys!
I've read a lot around the forums and can't find any info on my problem.
This topic was closest to my problem, so i hope i don't annoy anyone with posting here.
I've followed every step to unlock phone (and it's unlocked) everything went successfully until i came to the recovery part.
Every time i try to start recovery from bootloader my phone hangs on the HTC screen. No matter what i try to do, (tried to erase cache and install recovery again and again) it just hang.
Tried with two different CWM recoveries.
Anyone got an idea why that is? And what i can do to get into recovery mode?
Any help would be greatly appreciated!
I'm new to Android, but man, i love this forum. So much info!
In advance, thank you!
MrD
ive done a backup for my original rom but just a titum backup for the costumrom(so just the apps)
android revolution hd 3.1 and above need to flash the boot.bat thing..i know it sucks
when i stard from scratch..will it format the sd card?
MrDTrack5 said:
Hi guys!
I've read a lot around the forums and can't find any info on my problem.
This topic was closest to my problem, so i hope i don't annoy anyone with posting here.
I've followed every step to unlock phone (and it's unlocked) everything went successfully until i came to the recovery part.
Every time i try to start recovery from bootloader my phone hangs on the HTC screen. No matter what i try to do, (tried to erase cache and install recovery again and again) it just hang.
Tried with two different CWM recoveries.
Anyone got an idea why that is? And what i can do to get into recovery mode?
Any help would be greatly appreciated!
I'm new to Android, but man, i love this forum. So much info!
In advance, thank you!
MrD
Click to expand...
Click to collapse
which rom you tried to flash?
Diaeko said:
ive done a backup for my original rom but just a titum backup for the costumrom(so just the apps)
android revolution hd 3.1 and above need to flash the boot.bat thing..i know it sucks
when i stard from scratch..will it format the sd card?
Click to expand...
Click to collapse
starting from scratch won't format your SD card.
i found this... http://forum.xda-developers.com/showthread.php?t=1609190
but after a try my fastboot just let me reinstall recovery (which still wont work) but clear cash etc it keep saying FAILD (remote: not allowed)
what command are you typing? Are you typing "fastboot flash boot boot.img"? Or "fastboot flash recovery endeavoru_recovery_signed.img"?
im typing "fastboot flash recovery recovery.img" (i renamed the file from "..._recovery_...img" into "recovery.img")
and thats the only command that work
EDIT: i tried "fastboot flash boot boot.img" work to...but what does it change?
Okay. Well I am lost. Don't know how to help you out.
thank you for your help till now!!! but did you read the edit?
"EDIT: i tried "fastboot flash boot boot.img" work to...but what does it change?"
Flashing the boot.img only changes the kernel and of course boot.img of the ROM. Wrong boot.img can cause problems too.
Hello,
I'm a new member on this forum, I read all threads related with the problem which I have, and maybe I did something wrong but nothing helped with the phone.
The problem started one day, when the phone showed only the decrypt storage message:
"Decrypt unsuccessful. The password you entered is correct, but unfortunately your data is corrupt. To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google account."
The factory reset, suggested by the phone, returned the phone to the decrypt storage message. Recovery option and FACTORY RESET from HBOOT level comes back to the decrypt storage message again.
Somehow I managed to get the Android Recovery:
{
"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 above error comes up after Wipe Cache Partition and Wipe Data/Factory Reset
The only difference, now phone stocks on HTC Logo.
After applying an update via SDcard it shows:
HBOOT SDCard read:
RUU from https://forum.xda-developers.com/ht...ral/make-custom-recovery-htc-one-m8s-t3114245 for Voodaphone UK recognise the device is connected (when in fastboot mode) but on the beginning of the installation restarts the phone into bootloader mode, and phone tries to startup the system (so RUU software can not proceed, as the device is not connected). Even after manually restarting the phone (during the RUU installation process) to fastboot mode, it still shows the device is not connected.
The recovery via flashboot shows: ( I tried this with all types of recovery images)
I tried to flash firmware, using all firmwares from the above forum, with the same effect. Phone was verifying the certificates and fail, also remote access fail.
I tried unlock the bootloader via htcdev website, the phone accepted the unlock code, showed me the screen with an option to YES (unlock it), NO (keep it locked). After choosing YES, it still shows S-ON, and within cmd it says the oem is still locked. Tried this couple times with the same effect ( I requested for new unlock_code each time).
It looks like my options are running out, any advice? Maybe I did something wrong, could someone explain me step by step how to deal with this problem?
Btw, the phone MID and CID are:
Thank you for any advice.
Sorry for so massive imgs.
adiedi said:
Hello,
I'm a new member on this forum, I read all threads related with the problem which I have, and maybe I did something wrong but nothing helped with the phone.
The problem started one day, when the phone showed only the decrypt storage message:
"Decrypt unsuccessful. The password you entered is correct, but unfortunately your data is corrupt. To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google account."
The factory reset, suggested by the phone, returned the phone to the decrypt storage message. Recovery option and FACTORY RESET from HBOOT level comes back to the decrypt storage message again.
Somehow I managed to get the Android Recovery:
The above error comes up after Wipe Cache Partition and Wipe Data/Factory Reset
The only difference, now phone stocks on HTC Logo.
After applying an update via SDcard it shows:
HBOOT SDCard read:
RUU from https://forum.xda-developers.com/ht...ral/make-custom-recovery-htc-one-m8s-t3114245 for Voodaphone UK recognise the device is connected (when in fastboot mode) but on the beginning of the installation restarts the phone into bootloader mode, and phone tries to startup the system (so RUU software can not proceed, as the device is not connected). Even after manually restarting the phone (during the RUU installation process) to fastboot mode, it still shows the device is not connected.
The recovery via flashboot shows: ( I tried this with all types of recovery images)
I tried to flash firmware, using all firmwares from the above forum, with the same effect. Phone was verifying the certificates and fail, also remote access fail.
I tried unlock the bootloader via htcdev website, the phone accepted the unlock code, showed me the screen with an option to YES (unlock it), NO (keep it locked). After choosing YES, it still shows S-ON, and within cmd it says the oem is still locked. Tried this couple times with the same effect ( I requested for new unlock_code each time).
It looks like my options are running out, any advice? Maybe I did something wrong, could someone explain me step by step how to deal with this problem?
Btw, the phone MID and CID are:
Thank you for any advice.
Sorry for so massive imgs.
Click to expand...
Click to collapse
I could say only have you tried taking that sd card out before starting it up?
that screenshot looks like the one I got with sd card in and a bad ruu.
So taking out the sd card you should get the normal bootloader screen when you use the button combo.
m .
kruc Ire said:
I could say only have you tried taking that sd card out before starting it up?
that screenshot looks like the one I got with sd card in and a bad ruu.
So taking out the sd card you should get the normal bootloader screen when you use the button combo.
m .
Click to expand...
Click to collapse
Thx mate, I know to end the loop I have to take the SDcard out. I will try all RUUs once again, maybe I mess somewhere.
How did it turn out? What android version and build number do you have on there now?
You can't get s off from simply unlocking the bootloader via the HTC code. That is only (in some cases not at all) available by spending additional money at a method called 'sunshine'. However in many cases it isn't appropriate anyways for all users depends what you are trying to do. .
Every time I'm trying to run the "fastboot boot twrp-3.2.1-0-taimen.img" command for my Pixel 2 XL (or any twrp .img file for the P2XL for that matter except the alpha version), I am constantly stuck at "downloading 'boot.img' . . ." (attached image #2). Attached image #1 shows that I unlocked my bootloader.
On the computer terminal, the "downloading 'boot.img' . . ." message will stay there until I either start my phone again or restart the bootloader. I am also 100% certain I have been in the correct directory this entire time otherwise I don't think I would have even made it this far. Attached image #3 shows where the twrp.img file is. Line 1 on my terminal also shows that.
I'm at a loss. Any help would be appreciated.
{
"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'm assuming if I see "DEVICE STATE - unlocked" on the fastboot screen, the bootloader should be unlocked)
https://imgur.com/a/w4DWq
If the attached images do not load, then I have uploaded the images on Imgur
did you unlock the critical partition as well? Maybe that's the problem?
anthony.moua95 said:
Every time I'm trying to run the "fastboot boot twrp-3.2.1-0-taimen.img" command for my Pixel 2 XL (or any twrp .img file for the P2XL for that matter except the alpha version), I am constantly stuck at "downloading 'boot.img' . . ." (attached image #2). Attached image #1 shows that I unlocked my bootloader.
On the computer terminal, the "downloading 'boot.img' . . ." message will stay there until I either start my phone again or restart the bootloader. I am also 100% certain I have been in the correct directory this entire time otherwise I don't think I would have even made it this far. Attached image #3 shows where the twrp.img file is. Line 1 on my terminal also shows that.
I'm at a loss. Any help would be appreciated.
(I'm assuming if I see "DEVICE STATE - unlocked" on the fastboot screen, the bootloader should be unlocked)
Click to expand...
Click to collapse
Are you on 8.0 or 8.1? If on 8.1, did you update via OTA, side load, or factory image flash??
Badger50 said:
Are you on 8.0 or 8.1? If on 8.1, did you update via OTA, side load, or factory image flash??
Click to expand...
Click to collapse
I am on 8.1 and updated it via OTA.
anthony.moua95 said:
I am on 8.1 and updated it via OTA.
Click to expand...
Click to collapse
Hmmmm, interesting, dealing with another member on another thread having the same problem you are, except he side loaded 8.1.
I'm hoping one of the RC's or Developers can chime in. I think this is where the A/B partitions cause headaches. Reason being, after your OTA, you now are on partition B. I'm thinking that adb automatically recognizes partition A by default. So when you are trying to fastboot anything, there is essentially no OS to flash to. I think you may have to flash the stock factory image to both partitions to be able to root. Having said all that, I could be way off base, which is why I'm hoping for some help in this matter :good:
Have you tried a different cable yet?
Badger50 said:
Hmmmm, interesting, dealing with another member on another thread having the same problem you are, except he side loaded 8.1.
I'm hoping one of the RC's or Developers can chime in. I think this is where the A/B partitions cause headaches. Reason being, after your OTA, you now are on partition B. I'm thinking that adb automatically recognizes partition A by default. So when you are trying to fastboot anything, there is essentially no OS to flash to. I think you may have to flash the stock factory image to both partitions to be able to root. Having said all that, I could be way off base, which is why I'm hoping for some help in this matter :good:
Click to expand...
Click to collapse
Oh geeze, this is something I can't be bothered with at the moment with my current situation (living and working in Thailand). I appreciate all the input that you have given on this thread though! I think I will just keep my phone where it is at now then (unlocked bootloader, 0 modifications, 8.1.0). But I will continue to follow and see if there are any definitive or streamlined solutions to this potential problem in the (near) future. Adaway and Viper4Android are still very important enough reasons for me to root.
I will also add that when I tried rooting via the magisk method (patch_boot.img), I kept getting a message along the lines of
"target didn't report max-download-size
sending 'boot' (x KB)...
FAILED (remote: Requested download size is more than max allowed)
finished. total time: 0.123s"
Although even though despite always getting a message like this, I was able to somehow get root successfully one time. I decided to unroot and try to duplicate the root result but to no avail. Also got that annoying "internal problem with your device" message and followed @topjohnwu's tutorial only to get the "target didn't report max-download-size...FAILED (remote: Requested download dize is more than max allowed)" message again.
My laptop is currently running Manjaro (based on Arch Linux) but I can't imagine it being the reason I keep getting that "target didin't report max-download-size" message.
ilal2ielli said:
Have you tried a different cable yet?
Click to expand...
Click to collapse
Unfortunately I only have one USB-A to USB-C cable (a Sony one).
equlizer said:
did you unlock the critical partition as well? Maybe that's the problem?
Click to expand...
Click to collapse
I've tried numerous times and it always gave me a fail message or acknowledgement that my phone was already unlocked I'm giving up until I see a more streamlined answer to this potential problem
Make sure you adb/fastboot is up to date, it has caused many headaches for people trying to use older versions.
Badger50 said:
Hmmmm, interesting, dealing with another member on another thread having the same problem you are, except he side loaded 8.1.
I'm hoping one of the RC's or Developers can chime in. I think this is where the A/B partitions cause headaches. Reason being, after your OTA, you now are on partition B. I'm thinking that adb automatically recognizes partition A by default. So when you are trying to fastboot anything, there is essentially no OS to flash to. I think you may have to flash the stock factory image to both partitions to be able to root. Having said all that, I could be way off base, which is why I'm hoping for some help in this matter :good:
Click to expand...
Click to collapse
Exact thing happend to me. I sideloaded and I was stuck on partition B
I had to fully erase and start from scratch via full image method. Sucks but I got it going
anthony.moua95 said:
Unfortunately I only have one USB-A to USB-C cable (a Sony one).
Click to expand...
Click to collapse
I'd say try to get another cable ASAP, especially if anything else you do doesn't work.
When I first was attempting to unlock my bootloader, nothing worked when I was using third-party cables.
Luckily, my laptop had a USB-C port, so I was able to use the stock USB-C cable and I haven't had any problems since.
trim81 said:
Exact thing happend to me. I sideloaded and I was stuck on partition B
I had to fully erase and start from scratch via full image method. Sucks but I got it going
Click to expand...
Click to collapse
Kinda what I thought. How did you erase BTW? The interesting thing is that some of their adb commands won't work properly. Explain if you please how you did it so these guys can get back up to speed. Thanks for the input :good:
Badger50 said:
Kinda what I thought. How did you erase BTW? The interesting thing is that some of their adb commands won't work properly. Explain if you please how you did it so these guys can get back up to speed. Thanks for the input :good:
Click to expand...
Click to collapse
I'm on my mobile right now so I can't detail it but you would go to Google a site to download the full image. Then run the flashall command to wipe and start from scratch.
I was lucky I had a titanium backup for my apps.. I had to wipe eveything and start fresh.
trim81 said:
I'm on my mobile right now so I can't detail it but you would go to Google a site to download the full image. Then run the flashall command to wipe and start from scratch.
I was lucky I had a titanium backup for my apps.. I had to wipe eveything and start fresh.
Click to expand...
Click to collapse
Ok cool, that's the only way I know how to do it as well. Cool beans, thanks bro :good:
Hey, I had the exact same problem.
Posted a couple of times on the thread guide for root with magisk, ended with the same answer: fastboot/adb up to date ? Files where they should be ? (they dont need to be on the same folder as fastboot you know..., but they keep asking that...), and so on...
Tonight, latest attempt, instead of using my usb-c port, and my usb-a 3.0 port, I get back on my old laptop with 2.0 usb-a port and... It worked !
Just using 2.0 instead of 3.0 did the job ! You should try it
cavolo said:
Hey, I had the exact same problem.
Posted a couple of times on the thread guide for root with magisk, ended with the same answer: fastboot/adb up to date ? Files where they should be ? (they dont need to be on the same folder as fastboot you know..., but they keep asking that...), and so on...
Tonight, latest attempt, instead of using my usb-c port, and my usb-a 3.0 port, I get back on my old laptop with 2.0 usb-a port and... It worked !
Just using 2.0 instead of 3.0 did the job ! You should try it
Click to expand...
Click to collapse
Dude, if that's the answer, which it probably is, I'm gonna pull my hair out. Been trying everything I can to these folks out. And it's a flippin 8 dollar cable! Oh well, live and learn
I know tou probably did this already but I did not see it posted.
You did enable developer settings and enable oem unlock in developer settings?
Is there a solution to this issue? I have followed every set of directions I can find on XDA and beyond, wiped and wiped, locked and unlocked my phone a few different times. Tried different cables and different ports on my computer. No matter what I do, I am stuck at the "downloading boot" after trying to flash TWRP. Thanks in advance for any help.
Hi everyone,
I know this is posted a lot and I'm really sorry. But I couldn't find similar experiences to mine. Can someone spot my mistake?
1. I unlocked my bootloader using Xiaomi's official process
2. I used fastboot to flash and boot TWRP (twrp-3.4.0-0-ginkgo-willow-mauronofrio.img)
3. I wiped system, sdcard, cache partitions.
4. I tried to copy the crDroid zip from my PC to my phone but it wouldn't transfer. I tried adb push but I would get a Permission denied error.
5. I turned off the device (big mistake here) thinking I'd be able to boot TWRP recovery again. But trying to get into recovery (vol down+power) would give me a "System destroyed" screen.
6. I tried to re-flash and boot TWRP through fastboot but it would give me the error "Too many links".
7. At this point the device was soft bricked but I made a worse mistake. I tried to flash an official MIUI 11 image using MiFlash but after it finished the device would show a black screen and shut down after 1 second. Fastboot shows the fastboot logo but it also shut downs after 1 second. Computer doesn't recognize it.
Why did this happen? I sent the device to Mi's service center, but I want to know why it went so wrong so I don't make the same mistake again.
Sorry for the common question. Thank you all.
...
douteiful said:
Hi everyone,
I know this is posted a lot and I'm really sorry. But I couldn't find similar experiences to mine. Can someone spot my mistake?
1. I unlocked my bootloader using Xiaomi's official process
2. I used fastboot to flash and boot TWRP (twrp-3.4.0-0-ginkgo-willow-mauronofrio.img)
3. I wiped system, sdcard, cache partitions.
4. I tried to copy the crDroid zip from my PC to my phone but it wouldn't transfer. I tried adb push but I would get a Permission denied error.
5. I turned off the device (big mistake here) thinking I'd be able to boot TWRP recovery again. But trying to get into recovery (vol down+power) would give me a "System destroyed" screen.
6. I tried to re-flash and boot TWRP through fastboot but it would give me the error "Too many links".
7. At this point the device was soft bricked but I made a worse mistake. I tried to flash an official MIUI 11 image using MiFlash but after it finished the device would show a black screen and shut down after 1 second. Fastboot shows the fastboot logo but it also shut downs after 1 second. Computer doesn't recognize it.
Why did this happen? I sent the device to Mi's service center, but I want to know why it went so wrong so I don't make the same mistake again.
Sorry for the common question. Thank you all.
Click to expand...
Click to collapse
The system destroyed message is a common one. It's a result of avb (Android verified boot).
Simple solution is to disable this verity. Done by flashing in fastboot. It should have been part of the unlocking/ twrp guide. But it's not. This makes many people have this error.
Now as for the other issue. That sounds like the hard-brick error that comes from flashing ginkgo firmware on a willow device.
Ginkgo = note 8
Willow = note 8T
Afaik, this brick is not consumer repairable. I have not found any posts saying they had fixed this problem without service center.
mrmazak said:
The system destroyed message is a common one. It's a result of avb (Android verified boot).
Simple solution is to disable this verity. Done by flashing in fastboot. It should have been part of the unlocking/ twrp guide. But it's not. This makes many people have this error.
Click to expand...
Click to collapse
I could flash and boot TWRP first; I could adb push things too. Everything broke after I wiped the partitions. It's like everything became non-writable and I couldn't even boot TWRP recovery. adb push would say "Permission denied" and fastboot boot would say "Invalid command (Too many links)"
mrmazak said:
Now as for the other issue. That sounds like the hard-brick error that comes from flashing ginkgo firmware on a willow device.
Ginkgo = note 8
Willow = note 8T
Afaik, this brick is not consumer repairable. I have not found any posts saying they had fixed this problem without service center.
Click to expand...
Click to collapse
Yes, I think this is what happened with the MiFlash. My device was probably Willow. I sent it back to repair but I don't know yet if they will be willing to fix it.
douteiful said:
I could flash and boot TWRP first; I could adb push things too. Everything broke after I wiped the partitions. It's like everything became non-writable and I couldn't even boot TWRP recovery. adb push would say "Permission denied" and fastboot boot would say "Invalid command (Too many links)"
.
Click to expand...
Click to collapse
The "too many links" is a message you get when you type wrong commands..
Like example:
Fastboot flash flash boot boot.img
See There are too many commands/ links.
Let's hope the service center will fix you up.
Hello, I just wanted to know was your device in Warrenty?. And how much did the mi service center charged you? Thanks
mrmazak said:
The "too many links" is a message you get when you type wrong commands..
Like example:
Fastboot flash flash boot boot.img
See There are too many commands/ links.
Let's hope the service center will fix you up.
Click to expand...
Click to collapse
Thanks, but I'm pretty sure I entered the command correctly and it was among the lines of "FAILED (status read failed (Too many links))". I have searched for the error but nobody seems to know the cause.
LoadOP2 said:
Hello, I just wanted to know was your device in Warrenty?. And how much did the mi service center charged you? Thanks
Click to expand...
Click to collapse
I bought it only 1 week ago. It was new, so it's under warranty. But I haven't received a response from the service center yet. I don't know what will happen. I'll keep you posted.
douteiful said:
I bought it only 1 week ago. It was new, so it's under warranty. But I haven't received a response from the service center yet. I don't know what will happen. I'll keep you posted.
Click to expand...
Click to collapse
How can you unlock it so fast? I have read that It should take 30 days to unlock bootloader in official way.
OliveReeve said:
How can you unlock it so fast? I have read that It should take 30 days to unlock bootloader in official way.
Click to expand...
Click to collapse
I don't know if they changed it of it's because I had already unlocked a bootloader before (my previous Redmi Note 5) but it only asked to wait for 168 hours (7 days).
{
"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"
}
douteiful said:
Hi everyone,
I know this is posted a lot and I'm really sorry. But I couldn't find similar experiences to mine. Can someone spot my mistake?
1. I unlocked my bootloader using Xiaomi's official process
2. I used fastboot to flash and boot TWRP (twrp-3.4.0-0-ginkgo-willow-mauronofrio.img)
3. I wiped system, sdcard, cache partitions.
4. I tried to copy the crDroid zip from my PC to my phone but it wouldn't transfer. I tried adb push but I would get a Permission denied error.
5. I turned off the device (big mistake here) thinking I'd be able to boot TWRP recovery again. But trying to get into recovery (vol down+power) would give me a "System destroyed" screen.
6. I tried to re-flash and boot TWRP through fastboot but it would give me the error "Too many links".
7. At this point the device was soft bricked but I made a worse mistake. I tried to flash an official MIUI 11 image using MiFlash but after it finished the device would show a black screen and shut down after 1 second. Fastboot shows the fastboot logo but it also shut downs after 1 second. Computer doesn't recognize it.
Why did this happen? I sent the device to Mi's service center, but I want to know why it went so wrong so I don't make the same mistake again.
Sorry for the common question. Thank you all.
Click to expand...
Click to collapse
-You don't reboot to recovery after flashing twrp, it wont stick if you don't reboot it
-No problem for wiping system as ive done full wipe before, it will delete your os (needed for converting to cusrom)
-Tried to copy files into sdcard through twrp is not stable in my experience as i couldnt do it as well (not responding), i turned off device as well but it boot back to recovery quickly by it's own (im using latest twrp official), i dont force myself using adb anymore and just use external sdcard, copied rom directly with sdcard reader, install rom and got bootloop (back to recovery automatically, i format data and boot properly)
-You don't have system so turning off and try booting would be worst decision and because your twrp not stick, you can't go back neither
-Too many links is because adb commands is wrong
---------- Post added at 01:34 PM ---------- Previous post was at 01:26 PM ----------
OliveReeve said:
How can you unlock it so fast? I have read that It should take 30 days to unlock bootloader in official way.
Click to expand...
Click to collapse
i think you dont need to wait anymore, im unlocking my redmi just a few minutes, maybe because new added verification at latest miui unlock
OliveReeve said:
How can you unlock it so fast? I have read that It should take 30 days to unlock bootloader in official way.
Click to expand...
Click to collapse
lol no.. it's 168 hours usually if you do everything correctly
you should rebout to twrp after flashing it , also you didn't flash vbmeta (i don't know what it does,but mine was fixed once i flash it)
douteiful said:
Hi everyone,
I know this is posted a lot and I'm really sorry. But I couldn't find similar experiences to mine. Can someone spot my mistake?
1. I unlocked my bootloader using Xiaomi's official process
2. I used fastboot to flash and boot TWRP (twrp-3.4.0-0-ginkgo-willow-mauronofrio.img)
3. I wiped system, sdcard, cache partitions.
4. I tried to copy the crDroid zip from my PC to my phone but it wouldn't transfer. I tried adb push but I would get a Permission denied error.
5. I turned off the device (big mistake here) thinking I'd be able to boot TWRP recovery again. But trying to get into recovery (vol down+power) would give me a "System destroyed" screen.
6. I tried to re-flash and boot TWRP through fastboot but it would give me the error "Too many links".
7. At this point the device was soft bricked but I made a worse mistake. I tried to flash an official MIUI 11 image using MiFlash but after it finished the device would show a black screen and shut down after 1 second. Fastboot shows the fastboot logo but it also shut downs after 1 second. Computer doesn't recognize it.
Why did this happen? I sent the device to Mi's service center, but I want to know why it went so wrong so I don't make the same mistake again.
Sorry for the common question. Thank you all.
Click to expand...
Click to collapse
On step 5, you can still boot into recovery, the button is Vol up+power, but you press voldown+power(as you mentioned) will bring you to fastboot and get into System is destroyed screen. System is destroyed screen is normal. You just need to flash VBMETA. Your biggest mistakes and caresless is you dont do your research thoroughly. Risk is yours.
Make an habit to place your file to sdcard and always flash DMVERITY after anything you have done inside TWRP. DMVERITY is a must. In your case, vbmeta itself disable that force encryption and if you flash this, youll be able to enter fastboot mode.
Too many links means you dont enter the command correctly.
On steps 7 eventually will bring your phone back. I guess you got the indian version of RN8 where many people experiencing and posted on telegrams about this issues that they are unable to flash miui stock roms when that System is destroyed screen happen and end up bricking the phone. The only way and safest way to prevent this is, to flash VBMETA if you got the System is destroyed screen. Do not ever flash miui roms using miflash until you flashed that VBMETA. Then you are good to go flashing any roms using miflash
Update, something weird happened. I just got a message from the service center telling me that the phone had no issues, and they even showed me a video of it working (same IMEI). Which is weird because I'm pretty sure I hard bricked it. My guess is that they unbricked it and didn't tell me for some reason. Either way they didn't charge me any money so I'm happy. I'll get my device back next week and I'll check the things that you told me, particularly the model (ginkgo/willow).
Got my phone today. It's working. I don't know how they fixed it, and it's also unlocked. Just for the record, the Xiaomi ADB tool identifies it as a ginkgo, and the model number is M1908C3JH which is apparently ginkgo as well. If so, why did this all happen then?