Related
Hi folks,
atm I feel like a complete newb because I cant manage to root my xoom according to http://forum.xda-developers.com/showthread.php?t=1074979 with fastboot. (Can't flash through cwm since the device is stock 3.2)
What I have:
Motorola Xoom EU 3G (MZ601)
Android Version 3.2
Kernel 2.6.36.3
Firmware GAS_EMEA_USAEVRSTUTMDE_P016
What doesn't work:
As soon as I try to flash recovery my almighty command line says:
Code:
>fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
sending 'recovery' (3998 KB)...
OKAY [ 0.490s]
writing 'recovery'...
FAILED (command write failed (Unknown error))
finished. total time: 1.103s
My xoom shows "Starting Fastboot protocol support" as if nothing happened.
When I try to issue the command again immediatly, the error changes to:
Code:
>fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
sending 'recovery' (3998 KB)...
FAILED (remote: (00120000))
finished. total time: 0.274s
The xoom is showing "Failed to process command error(0x120000)".
Here is what I've done so far, aside from following the post mentioned above including all tipps in that thread.
tried three different cables for connecting the xoom to my PC, including the original one.
tried two different computers with three different OSs (x64 only so far)
tried to flash the image immediatly after the oem unlock without booting into system
tried everey single usb port on every system
tried updating chipset drivers as well as the usb drivers
I don't know what to try next. Could someone please give me a hint what to try next? I'm stuck here.
Thanks in advance & thanks for reading, Jan
jan_goose said:
Here is what I've done so far, aside from following the post mentioned above including all tipps in that thread.
tried three different cables for connecting the xoom to my PC, including the original one.
tried two different computers with three different OSs (x64 only so far)
tried to flash the image immediatly after the oem unlock without booting into system
tried everey single usb port on every system
tried updating chipset drivers as well as the usb drivers
I don't know what to try next. Could someone please give me a hint what to try next? I'm stuck here.
Thanks in advance & thanks for reading, Jan
Click to expand...
Click to collapse
Have you tried to check the md5-checksum of the image file?
llama-power said:
Have you tried to check the md5-checksum of the image file?
Click to expand...
Click to collapse
Hi, indeed, I forgot that. I've checked it and they are matching, so no luck here.
Does someone know if maybe 64bit systems could cause problems? (And what to do aside from buying a new PC ^^)
jan_goose said:
Hi, indeed, I forgot that. I've checked it and they are matching, so no luck here.
Does someone know if maybe 64bit systems could cause problems? (And what to do aside from buying a new PC ^^)
Click to expand...
Click to collapse
well, they could but on my 64bit system everything worked out fine. You could try installing a 32 bit OS, as your computer is likely compatible to that. I don't, however, believe that would do any good as it looks like your computer is doing what it should, only your xoom isn't... (to me, it looks like your computer is sending the file just fine but the xoom just doesn't want to flash that file to memory)...
what does fastboot getvar all return?
llama-power said:
what does fastboot getvar all return?
Click to expand...
Click to collapse
A command I wasn't aware of, thanks.
While charging, it says:
Code:
(bootloader) version-bootloader: 1049
(bootloader) product: xoom-cdma
(bootloader) secure: yes
(bootloader) model: MZ600
(bootloader) memory-info: 0x101:0x5454:0
(bootloader) mid: 001
(bootloader) version: 0.4
(bootloader) serialno: 037C710041XXXX
(bootloader) version-baseband: N_01.100.05P
(bootloader) version-baseband-2:
(bootloader) battery-status: 45%:7.847V:0.869A:21.37C
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
I'm a bit confused because it says "MZ600", but according to the tablet info when android has booted it is a MZ601.
I'm living in germany, where I've also bought the device and it's got a 3g module which i'm actually using.
jan_goose said:
While charging, it says:
Click to expand...
Click to collapse
did you just omit the (bootloader) iswarrantyvoid: yes or did that really not appear? Apart from that, everything looks just like on my device... Thus, I am officially out of ideas... I'd offer to have a look at your device next week as I'll be in your location then but I currently don't see how that would do any good...
jan_goose said:
I'm a bit confused because it says "MZ600", but according to the tablet info when android has booted it is a MZ601.
Click to expand...
Click to collapse
yeah, that distracted me at first too, but a friends MZ601 which is neither rooted nor unlocked, says the same, so I think thats fine...
Anyhow... sorry, no clue what's wrong with your device...:-(
can you flash a the recovery image from Motorola?
llama-power said:
can you flash a the recovery image from Motorola?
Click to expand...
Click to collapse
Actually, I couldn't.
I didn't even try before. This simple question of yours emerged something like a nerdrage from deep inside.
I looked sternly at my xoom and decided that I won't go down first.
Well, the rest was luck, but since I've tried it multiple times and it worked, here are the steps:
Start slowly with these lines (I know them by heart by now)
Code:
adb reboot bootloader
fastboot flash recovery recovery-solarnz-XXXXXX-XXXX.img
It will fail. Do the last line again, it will show error 0x120000.
Now you have to be quick as soon as you submitted the next line:
Code:
fastboot reboot
Unplug your device from the PC and start hitting the Volume down button immediatly (this means: do not tap and hold, press it multiple times) until the display says fastboot is ready .
Now re-plug the xoom to the PC again and re-do this:
Code:
fastboot flash recovery recovery-solarnz-XXXXXX-XXXX.img
This time, everything goes well.
If, like me, you are coming from stock, don't forget you must not reboot to system again, but directly to recovery and install something like Team EOS ROM.
I have no clue why it worked, but since I was so fascinated that I've tried it three times I guess one could say it's reproducable.
Good night and thanks to llama-power for being inspirational.
wow
jan_goose said:
Actually, I couldn't.
I didn't even try before. This simple question of yours emerged something like a nerdrage from deep inside.
I looked sternly at my xoom and decided that I won't go down first.
Well, the rest was luck, but since I've tried it multiple times and it worked, here are the steps:
Start slowly with these lines (I know them by heart by now)
Code:
adb reboot bootloader
fastboot flash recovery recovery-solarnz-XXXXXX-XXXX.img
It will fail. Do the last line again, it will show error 0x120000.
Now you have to be quick as soon as you submitted the next line:
Code:
fastboot reboot
Unplug your device from the PC and start hitting the Volume down button immediatly (this means: do not tap and hold, press it multiple times) until the display says fastboot is ready .
Now re-plug the xoom to the PC again and re-do this:
Code:
fastboot flash recovery recovery-solarnz-XXXXXX-XXXX.img
This time, everything goes well.
If, like me, you are coming from stock, don't forget you must not reboot to system again, but directly to recovery and install something like Team EOS ROM.
I have no clue why it worked, but since I was so fascinated that I've tried it three times I guess one could say it's reproducable.
Good night and thanks to llama-power for being inspirational.
Click to expand...
Click to collapse
i tried your method did not work i was also getting the error code what worked was using [Recovery] EOS recovery (R6) CWM Based and it pushed thru fastboot no problem just a heads up
Just to confirm...
jan_goose said:
A command I wasn't aware of, thanks.
While charging, it says:
Code:
(bootloader) version-bootloader: 1049
(bootloader) product: xoom-cdma
(bootloader) secure: yes
(bootloader) model: MZ600
(bootloader) memory-info: 0x101:0x5454:0
(bootloader) mid: 001
(bootloader) version: 0.4
(bootloader) serialno: 037C710041XXXX
(bootloader) version-baseband: N_01.100.05P
(bootloader) version-baseband-2:
(bootloader) battery-status: 45%:7.847V:0.869A:21.37C
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
I'm a bit confused because it says "MZ600", but according to the tablet info when android has booted it is a MZ601.
I'm living in germany, where I've also bought the device and it's got a 3g module which i'm actually using.
Click to expand...
Click to collapse
Did you verify if that information is correct? I get the same info from fastboot
Onedroidev said:
Did you verify if that information is correct? I get the same info from fastboot
Click to expand...
Click to collapse
I have no idea why the information seems to be wrong, but obviously it can be ignored, at least in my case.
As long as you've got a 3G module, it is not a MZ600, regardless what fastboot is saying.
I just got my new tablet today... it automatically did all it's updates while it was charging - I unlocked it following the tutorials and some strange issues started happening where the recovery ROMs I flashed couldn't see the system partitions. I tried a few different recovery ROMs (TWRP, CWM) but both did the same.
The problem, now when I try and flash anything using the bootloader, my command prompt claims it finished successfully, but my tablet's green flashing box stops flashing and does nothing until I hold on the power button to hard boot it.
Any ideas? Here's the information I've been able to gather:
Code:
PS C:\android-sdk\platform-tools> .\fastboot.exe -i 0x0b05 getvar all
(bootloader) version-bootloader: 1.0
(bootloader) version-baseband: 2.0
(bootloader) version: 0.4
(bootloader) serialno: 0asdfghjklzxcvbnm
(bootloader) mid: 001
(bootloader) product: Cardhu
(bootloader) secure: yes
(bootloader) unlocked: no
(bootloader) uart-on: yes
(bootloader) partition-size:bootloader: 0x0000000000800000
(bootloader) partition-type:bootloader: basic
(bootloader) partition-size:recovery: 0x0000000000800000
(bootloader) partition-type:recovery: basic
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: basic
(bootloader) partition-size:system: 0x0000000030000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001ac00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x00000006e5680000
(bootloader) partition-type:userdata: ext4
all:
finished. total time: 0.105s
PS C:\android-sdk\platform-tools> .\fastboot.exe -i 0x0b05 erase recovery
erasing 'recovery'...
OKAY [ 1.237s]
finished. total time: 1.238s
PS C:\android-sdk\platform-tools> .\fastboot.exe -i 0x0b05 flash recovery openrecovery-twrp-2.4.3.0-tf300t-JB.blob
sending 'recovery' (7670 KB)...
OKAY [ 2.099s]
writing 'recovery'...
OKAY [ 2.694s]
finished. total time: 4.795s
PS C:\android-sdk\platform-tools>
I can erase and getvar all day, but flash makes it freeze up.
I forgot to include that once it locks up, the fastboot command does this:
Code:
PS C:\android-sdk\platform-tools> ./fastboot -i 0x0B05 devices
???????????? fastboot
PS C:\android-sdk\platform-tools> ./fastboot -i 0x0B05 getvar all
getvar:all FAILED (command write failed (Unknown error))
finished. total time: 0.592s
PS C:\android-sdk\platform-tools>
kulm said:
I just got my new tablet today... it automatically did all it's updates while it was charging - I unlocked it following the tutorials and some strange issues started happening where the recovery ROMs I flashed couldn't see the system partitions. I tried a few different recovery ROMs (TWRP, CWM) but both did the same.
(bootloader) unlocked: no
Have you unlocked? Your posted information says no. If you are on 4.2 I can't say but previous firmware disallowed use of fastboot prior to unlocking.
Click to expand...
Click to collapse
tobdaryl said:
kulm said:
(bootloader) unlocked: no
Have you unlocked? Your posted information says no. If you are on 4.2 I can't say but previous firmware disallowed use of fastboot prior to unlocking.
Click to expand...
Click to collapse
I wondered the same thing - but I had TWRP working on it and it says on the top when I reboot "The device is unlocked"...
Click to expand...
Click to collapse
kulm said:
tobdaryl said:
I wondered the same thing - but I had TWRP working on it and it says on the top when I reboot "The device is unlocked"...
Click to expand...
Click to collapse
I have not seen this or read of this issue. Are you on the 4.2 version of software? If so you are in uncharted waters.
I didn't get the update and can't use the ota to install. I like many others are waiting for the asus firmware version.
I have read one reply where cwm didn't work on 4.2.
Something else I have never seen is the bootloader serial number displayed. You may wish to remove that line from your post. Just choose edit and delete that line, then save.
If on 4.2 this may indicate that cwm and twrp will require an update to work properly.
If you can use your tablet as is then I suggest doing so or flash stock JB firmware the most recent is 10.4.2.20 but for my use 10.4.2.18 has less lag and everything I need works properly.
I'll bookmark this thread and try to come back with some help after more research. Failing that maybe someone else will reply with a good suggestion.
Good Luck!
Please respond with your firmware version.
This is the standard method used to unlock the bootloader with fastboot. I can't use it since I'm not on 4.2 and won't suggest that you do; it is for information only at this point.
fastboot oem unlock
I suspect we would need to use the -i 0x0b05 as in fastboot -i 0x0b05 oem unlock.
Click to expand...
Click to collapse
tobdaryl said:
kulm said:
I have not seen this or read of this issue. Are you on the 4.2 version of software? If so you are in uncharted waters.
I didn't get the update and can't use the ota to install. I like many others are waiting for the asus firmware version.
I have read one reply where cwm didn't work on 4.2.
If on 4.2 this may indicate that cwm and twrp will require an update to work properly.
If you can use your tablet as is then I suggest doing so or flash stock JB firmware the most recent is 10.4.2.20 but for my use 10.4.2.18 has less lag and everything I need works properly.
I'll bookmark this thread and try to come back with some help after more research. Failing that maybe someone else will reply with a good suggestion.
Good Luck!
Please respond with your firmware version.
This is the standard method used to unlock the bootloader with fastboot. I can't use it since I'm not on 4.2 and won't suggest that you do; it is for information only at this point.
fastboot oem unlock
I suspect we would need to use the -i 0x0b05 as in fastboot -i 0x0b05 oem unlock.
Click to expand...
Click to collapse
Thanks for the response - the SN is bogus.So, when I boot without pushing vol up/down it goes to the "ASUS" logo screen with "device unlocked" at the top and it just sits... I can get into APX with vol up and fastboot with vol down.
With vol down this comes up at the top:
Code:
Key driver not found.. Booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.8-20130225" A03
Starting Fastboot USB download protocol
Then it has the typical RCK, Android and Wipe Data options.
When I choose RCK I get:
Code:
Booting Recovery kernel image
Booting Failed
Unrecoverable bootloader error (0x00000000)
The device hangs until I power cycle from there.
Click to expand...
Click to collapse
kulm said:
tobdaryl said:
Thanks for the response - the SN is bogus.So, when I boot without pushing vol up/down it goes to the "ASUS" logo screen with "device unlocked" at the top and it just sits... I can get into APX with vol up and fastboot with vol down.
With vol down this comes up at the top:
Code:
Key driver not found.. Booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-1.6.1.8-20130225" A03
Starting Fastboot USB download protocol
Then it has the typical RCK, Android and Wipe Data options.
When I choose RCK I get:
Code:
Booting Recovery kernel image
Booting Failed
Unrecoverable bootloader error (0x00000000)
The device hangs until I power cycle from there.
Click to expand...
Click to collapse
I am completely lost, if this is 4.2 that might be why. If you will give me your version I'll try to help you search and get an answer. Go to settings/about tablet/ and tell me what you have for build# and android version.
The serial# is not your tablet serial# but bootloader serial#. This may be in response to our recent petition to asus for the ability to unlock the bootloader in addition to the tablet unlock we now have.
If so this should allow nvflash for people on the JB bootloader.
Note: If you are on 4.2 you might look at settings and see if encryption is turned on, at least two have mentioned that it is on by default and it will cause various issues with fastboot and cwm or twrp.
Now that I think about it even on 4.1 encryption has caused some strange results.
Click to expand...
Click to collapse
tobdaryl said:
kulm said:
I am completely lost, if this is 4.2 that might be why. If you will give me your version I'll try to help you search and get an answer. Go to settings/about tablet/ and tell me what you have for build# and android version.
The serial# is not your tablet serial# but bootloader serial#. This may be in response to our recent petition to asus for the ability to unlock the bootloader in addition to the tablet unlock we now have.
If so this should allow nvflash for people on the JB bootloader.
Note: If you are on 4.2 you might look at settings and see if encryption is turned on, at least two have mentioned that it is on by default and it will cause various issues with fastboot and cwm or twrp.
Now that I think about it even on 4.1 encryption has caused some strange results.
Click to expand...
Click to collapse
I am on 4.2.1 and am having the same issue. I just checked and encryption is turned off on mine.
Click to expand...
Click to collapse
mistyv said:
tobdaryl said:
I am on 4.2.1 and am having the same issue. I just checked and encryption is turned off on mine.
Click to expand...
Click to collapse
Thanks for the update. I'll start searching also and report when I have some news.
Good Luck!
I'm finding several with fastboot issues as well as cwm and twrp issues but no resolutions yet.
I'll try to keep you posted if I get something positive.
Click to expand...
Click to collapse
My device is doin the same thing i would go into fastboot mode and the green box would just freeze up but when i push the recovery it says that is was successful b ut the device doesnt take the recovery then when i tried to push it again it fails can anyone help
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
ryuken11221 said:
My device is doin the same thing i would go into fastboot mode and the green box would just freeze up but when i push the recovery it says that is was successful b ut the device doesnt take the recovery then when i tried to push it again it fails can anyone help
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
Click to expand...
Click to collapse
That is what mine did and I thought it wasn't installing, but it actually did. Once I rebooted back into fastboot and selected RCK mine would boot into the recovery, but the internal and external sd card wouldn't mount. I tried TWRP and CWM, but no luck with either.
According to this thread http://forum.xda-developers.com/showthread.php?t=2180376 it is likely an encryption issue with 4.2.1 and we will have to wait till someone finds a fix. I was apparently wrong about the encryption on my earlier post.
ryuken11221 said:
My device is doin the same thing i would go into fastboot mode and the green box would just freeze up but when i push the recovery it says that is was successful b ut the device doesnt take the recovery then when i tried to push it again it fails can anyone help
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
Click to expand...
Click to collapse
I'm not finding answers to this problem; just questions.
I can't get 4.2 until Asus drops the file on their site.
At this point maybe everyone put this area on hold for a few days till we can get the full download and try to figure out what is happening and how to resolve these issues. Try to use your unit as it is for a few days and avoid possible bricks.
I have a full system dump of 4.2.1. Just extracting the bootloader and flashing it causes recovery to think it is encrypted. Custom recovery that is. Also I noticed that the 10.6.1.8 kernel doesn't like some updater-script commands. Finally there is a new file in /system/etc called recovery-resource.dat. I wonder if Asus has put some measures I in place to stop customising?
sbdags said:
I have a full system dump of 4.2.1. Just extracting the bootloader and flashing it causes recovery to think it is encrypted. Custom recovery that is. Also I noticed that the 10.6.1.8 kernel doesn't like some updater-script commands. Finally there is a new file in /system/etc called recovery-resource.dat. I wonder if Asus has put some measures I in place to stop customising?
Click to expand...
Click to collapse
Thanks for the good info. That explains a lot.
Were you using the update-binary from 10.6.1.8 or an earlier version?
Great catch. I just checked and we now have a different version of update-binary. Now I need to revisit my edify scripts.
Thanks!
Well I'm still running 4.1.1 I haven't be able to upgrade to 4.2 just as yet so I'm not sure what the issue with my device is I just restored it back to back to factory for work purposes and now I wanted to root it back and install recovery now this
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
tobdaryl said:
Thanks for the good info. That explains a lot.
Were you using the update-binary from 10.6.1.8 or an earlier version?
Great catch. I just checked and we now have a different version of update-binary. Now I need to revisit my edify scripts.
Thanks!
Click to expand...
Click to collapse
I haven't actually flashed all of it but tried to make it compatible with my TF700. I also tried 2 or 3 different updater binaries and they made no difference.
Specifically format now wanted 5 args where only needed 4 before. No idea what the 5th is. Package extract file didn't like me writing to /tmp but was OK with /data/media ..... Weird
Looks like a permissions thing?
sbdags said:
I haven't actually flashed all of it but tried to make it compatible with my TF700. I also tried 2 or 3 different updater binaries and they made no difference.
Specifically format now wanted 5 args where only needed 4 before. No idea what the 5th is. Package extract file didn't like me writing to /tmp but was OK with /data/media ..... Weird
Looks like a permissions thing?
Click to expand...
Click to collapse
Thanks for the help.
OK is this straying from what the topic is about just asking
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
ryuken11221 said:
OK is this straying from what the topic is about just asking
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
Click to expand...
Click to collapse
It is about the 4.2 rom and related issues; however I am done. Sorry for the interruption.
tobdaryl said:
It is about the 4.2 rom and related issues; however I am done. Sorry for the interruption.
Click to expand...
Click to collapse
Not a problem just wondering if I can get help with this just very very frustrating
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
Hello, first excuse me for my english , i'll try to be clear as possible.
I get a tf700t with bootloader trouble, i tought that it be easy to repair.
On the screen with asus logo there's write ''the device is unlocked'' then the owner told me CWM was installed on.
But when i try to go to recovery section (RCK) i have
Booting Recovery kernel image
Booting failed
Unrecovarable bootloader error (0x00000000)
Cannot go to cold boot too, it load nothing (bootloop).
I have fastboot but i cannot flash anything on it:
C:\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>fastboot getvar all(bootloader) version-bootloader: 1.0 (bootloader) version-baseband: 2.0
(bootloader) version: 0.4
(bootloader) serialno: 015d29955e67ec09
(bootloader) mid: 001
(bootloader) product: Cardhu
(bootloader) secure: yes
(bootloader) unlocked: no
(bootloader) partition-size:bootloader: 0x0000000000800000
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x0000000000800000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x0000000030000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001ac00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x00000006e5680000
(bootloader) partition-type:userdata: ext4
all:
finished. total time: 0.082s
Click to expand...
Click to collapse
And tying to wipe give me the same error message than the RCK.
And so my question is, will i be able to use fastboot or something else to flash recovery, boot,etc...
Thanks
Can you tell us your bootloader version (you can see it when booting with Volume Down + Power)?
Pretoriano80 said:
Can you tell us your bootloader version (you can see it when booting with Volume Down + Power)?
Click to expand...
Click to collapse
cardhu-user bootloader 1.00 e released by ww_epad-10.4.4.25
Acem31 said:
cardhu-user bootloader 1.00 e released by ww_epad-10.4.4.25
Click to expand...
Click to collapse
Have a look here - - > http://forum.xda-developers.com/showthread.php?t=2179759 <-- some users were able to recover from similar issue.
Be aware that the thread is for the TF300T so make sure you download the firmware for the TF700T if you decide to try that procedure.
Pretoriano80 said:
Have a look here - - > http://forum.xda-developers.com/showthread.php?t=2179759 <-- some users were able to recover from similar issue.
Be aware that the thread is for the TF300T so make sure you download the firmware for the TF700T if you decide to try that procedure.
Click to expand...
Click to collapse
Yup, i have all .img/.blob made for the tf700t.
I'll look the thread, and reply to give results, hope it will work.
Well, it work fine, indeed i think i'll soon make a tuto for those ho have the same problem, it should be usefull.
So, i recovered my bootloader, my recovery, then now i'll ty to install the stock rom, but my external SD i not recognize by the tf700t.
It should be easy to fix it. When it's done, i'll mark the thread like solved.
Your help was really usefull @Pretoriano80 !!
Acem31 said:
Well, it work fine, indeed i think i'll soon make a tuto for those ho have the same problem, it should be usefull.
So, i recovered my bootloader, my recovery, then now i'll ty to install the stock rom, but my external SD i not recognize by the tf700t.
It should be easy to fix it. When it's done, i'll mark the thread like solved.
Your help was really usefull @Pretoriano80 !!
Click to expand...
Click to collapse
Glad you managed to recover it.
Well it's harder to fix it. TWRP is unable to mount /System /Sdcard etc
Then i cannot use adb sideload with TWRP & CWM, so i'm still unable to put the rom on the devices.
An idea? I googled it, i didn't find any issue. I probably missed something :/
Well, i know what i miss.
When i turn on the device, i can see "this device is unlocked" or somethin like that.
But with:
fastboot getvar all
I have "unlocked: no" , that's why i'm unable to write any ROM on the system part.
The only way i know to re unlock, is using the ASUS unlock apk, but without any system installed...
Will i be able to unlock, or do something else to get the STOCK back?
It's impossibile that you locked the bootloader, so far there's no way to do it, not for end-users at least.
Edit: Have you tried to push the stock recovery via fastboot?
---------- Post added at 06:58 PM ---------- Previous post was at 06:51 PM ----------
You could try this:
1) Dowload the latest firmware from Asus site and extract the blob file to the same location where fastboot.exe is located
2) Boot device in fastboot mode then...
3) fastboot -i 0x0B05 flash staging blob
4) after sending and writing process is done restart with " fastboot -i 0x0B05 reboot"
If everything goes as expected you should have a full Asus firmware installed (and stock recovery)
Acem31 said:
fastboot getvar all
I have "unlocked: no" , that's why i'm unable to write any ROM on the system part.
Click to expand...
Click to collapse
Sounds reasonable, but mine also says "unlocked: no" and I have no problems flashing stuff.
Pretoriano80 said:
It's impossibile that you locked the bootloader, so far there's no way to do it, not for end-users at least.
Edit: Have you tried to push the stock recovery via fastboot?
---------- Post added at 06:58 PM ---------- Previous post was at 06:51 PM ----------
You could try this:
1) Dowload the latest firmware from Asus site and extract the blob file to the same location where fastboot.exe is located
2) Boot device in fastboot mode then...
3) fastboot -i 0x0B05 flash staging blob
4) after sending and writing process is done restart with " fastboot -i 0x0B05 reboot"
If everything goes as expected you should have a full Asus firmware installed (and stock recovery)
Click to expand...
Click to collapse
Huumm unexpected issue? When it restart, first it stay on the asus logo, so i press power + vol down to go fastboot and there, no more fastboot icon, but fastboot start directly(i still can choose RCK , Cold boot & wipe data)
Also, i have
"Key driver not found..booting OS"
I will retry as long as i have fastboot
Acem31 said:
Huumm unexpected issue? When it restart, first it stay on the asus logo, so i press power + vol down to go fastboot and there, no more fastboot icon, but fastboot start directly(i still can choose RCK , Cold boot & wipe data)
Also, i have
"Key driver not found..booting OS"
I will retry as long as i have fastboot
Click to expand...
Click to collapse
That's normal, it means that fastboot mode it's ON. No more USB icon in bootloader menu.
Inviato dal mio ASUS Transformer Pad TF700T con Tapatalk 4
---------- Post added at 07:20 PM ---------- Previous post was at 07:19 PM ----------
What happens when you choose RCK? You end-up with a dead Android?
Inviato dal mio ASUS Transformer Pad TF700T con Tapatalk 4
---------- Post added at 07:27 PM ---------- Previous post was at 07:20 PM ----------
And btw mate, give us more info... did you followed my advice, flash went good, wich bootloader version it shows now. This details could save your device and wrong info could brick it.
So far mh understanding is that the flash went fine but for some odd reason it doesn't boot the OS. I guess one of the reasons is because you switched from 4.1 to 4.2.1 so some old data is stopping the device from booting...just my wild guess.
Inviato dal mio ASUS Transformer Pad TF700T con Tapatalk 4
OFF TOPIC: where are you come from in italia?
The command running, as soon as it finish i'll tell you the result.
Acem31 said:
OFF TOPIC: where are you come from in italia?
The command running, as soon as it finish i'll tell you the result.
Click to expand...
Click to collapse
Yes,Rome-Italy.If the command is running at some point you should see a blu bar filling slowly.
Pretoriano80 said:
Yes,Rome-Italy.If the command is running at some point you should see a blu bar filling slowly.
Click to expand...
Click to collapse
Well, next time i'll go to calabria to see my cousin, i'll stop in Roma to make you a huge kiss! It works!
BIG BIG BIG BIG thanks! I'll mark the topic as resolved!
Grazie!
Acem31 said:
Well, next time i'll go to calabria to see my cousin, i'll stop in Roma to make you a huge kiss! It works!
BIG BIG BIG BIG thanks! I'll mark the topic as resolved!
Grazie!
Click to expand...
Click to collapse
No problem mate,i'm glad it's up and running again.
Edit: And you could use the "thanks" button too
Hi there!
I just had a go at flashing my new HTC One M8, and I'm stuck in recovery mode.
I followed these instructions:
androidcentral.us/2014/04/root-att-htc-one-m8/
But got the TWRP file from here because the original link was overloaded:
androidfiles.org/?developer=M8&folder=Recoveries
I essentially just ran:
Code:
fastboot-mac erase
cachefastboot-mac
flash boot recovery.img
fastboot-mac reboot
Then installed the SuperSU update zip. Now every time I try reboot into the Android system, it boots into recovery mode. If I boot into the bootloader, I get the option to boot using fastboot but that appears to fail (it returns me to the bootloader after a second). If I select hboot, it says "No image or wrong image!" after trying to load a .nbh file.
Any ideas?
BTW, I got the unlocked version from Amazon: amazon.com/HTC-One-M8-Unlocked-Warranty/dp/B00J3554KE/
marcog123 said:
hi there!
I just had a go at flashing my new htc one m8, and i'm stuck in recovery mode.
I followed these instructions:
Androidcentral.us/2014/04/root-att-htc-one-m8/
but got the twrp file from here because the original link was overloaded:
Androidfiles.org/?developer=m8&folder=recoveries
i essentially just ran:
Code:
fastboot-mac erase
cachefastboot-mac
flash boot recovery.img
fastboot-mac reboot
then installed the supersu update zip. Now every time i try reboot into the android system, it boots into recovery mode. If i boot into the bootloader, i get the option to boot using fastboot but that appears to fail (it returns me to the bootloader after a second). If i select hboot, it says "no image or wrong image!" after trying to load a .nbh file.
Any ideas?
Btw, i got the unlocked version from amazon: Amazon.com/htc-one-m8-unlocked-warranty/dp/b00j3554ke/
Click to expand...
Click to collapse
you flashed recovery to kernel partition! The guide is wrong as i read.
To flash recovery:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
BUT you will also need to flash the kernel again as you just messed it up!
Ouch! Ok, that sucks that steps I was following were wrong. :/ But at least I feel less like an idiot.
So I found a boot.img from here: http://forum.xda-developers.com/showthread.php?p=51580259 and flashed that. Now I'm not returning to the recovery screen, but to the bootloader always and it gives the same message about wrong image.
Here are the commands I ran:
Code:
./fastboot-mac erase cache
./fastboot-mac flash boot boot.img
./fastboot-mac flash recovery Recovery.img
./fastboot-mac reboot
marcog123 said:
Ouch! Ok, that sucks that steps I was following were wrong. :/ But at least I feel less like an idiot.
So I found a boot.img from here: http://forum.xda-developers.com/showthread.php?p=51580259 and flashed that. Now I'm not returning to the recovery screen, but to the bootloader always and it gives the same message about wrong image.
Here are the commands I ran:
Code:
./fastboot-mac erase cache
./fastboot-mac flash boot boot.img
./fastboot-mac flash recovery Recovery.img
./fastboot-mac reboot
Click to expand...
Click to collapse
can you stil enter fastboot mode?
Is fastboot mode the one where you see "FASTBOOT USB" in red on top? Cause I can get into that and connect to my phone from my laptop.
marcog123 said:
Is fastboot mode the one where you see "FASTBOOT USB" in red on top? Cause I can get into that and connect to my phone from my laptop.
Click to expand...
Click to collapse
Thats good. I'll help you get back working phone.
BUT i need some info:
Please tell me what bootloader is about:
HBoot and so on. Also i need to know if its an "UNLOCKED" phone sold by a carrier. Or a carrier free phone. Because you will need fittig software for each model.
The info on top of the bootloader screen?
Code:
M8_UL_CA PVT SHIP S-ON
HBOOT-3.16.0.0000
RADIO-1.15.2133156.UA03_2G
OpenDSP-v26.2.2-00538-M8974.0106
OS-1.12.1540.17
eMMC-boot 2048MB
Mar 3 2014,20:18:02.0
It's an unlocked (carrier free) phone sold by Amazon: amazon.com/HTC-One-M8-Unlocked-Warranty/dp/B00J3554KE/
Okay. Will get the right files.
Sent from my beloved HTC One S using (most time buggy) Tapatalk
The kernel you flashed is for "SPRINT" m8 and NOT COMPATIBLE to your device. Just don't flash any files as long as you don't know if theyre matching your phone please.
Did you flash the TWRP 2703 version?
Yes, 2.7.0.3.
Thanks so much for all your help so far! I hugely appreciate how quickly you're jumping on helping me.
marcog123 said:
Yes, 2.7.0.3.
Thanks so much for all your help so far! I hugely appreciate how quickly you're jumping on helping me.
Click to expand...
Click to collapse
can you enter TWRP?
by select "recovery" in bootloader
---------- Post added at 07:22 PM ---------- Previous post was at 07:17 PM ----------
marcog123 said:
Yes, 2.7.0.3.
Thanks so much for all your help so far! I hugely appreciate how quickly you're jumping on helping me.
Click to expand...
Click to collapse
can you enter TWRP?
by select "recovery" in bootloader
This kernel may work: http://androidfil.es/1mSt Don't flash it yet.
Yes, that gets me into TWRP!
marcog123 said:
Yes, that gets me into TWRP!
Click to expand...
Click to collapse
Just that you know, that is YOUR phone:
x.xx.1540.x - HTC One U.S. Developer Edition
I'm looking for a stock rom, if that is not possible you will have to use a custom rom
---------- Post added at 07:33 PM ---------- Previous post was at 07:32 PM ----------
marcog123 said:
Yes, that gets me into TWRP!
Click to expand...
Click to collapse
Have you installed adb on your laptop? BTW are you using a apple mac?
Download this rom please --> LINK
The rom includes stock kerne. Just download it and we'll try to flash just the included kernel file as it should get your device back working.
Otherwise you'll have to flash full rom via twrp.
Please tell me when your download is ready. And this time do yourself a favor and DON'T act on your own as long as you don't know what you're doing...
Oh my, thanks so much that worked!! You're awesome! I honestly had a feeling I'd lost my phone.
Glad you got it back alive
Sent from my beloved HTC One S using (most time buggy) Tapatalk
LS.xD said:
Glad you got it back alive
Sent from my beloved HTC One S using (most time buggy) Tapatalk
Click to expand...
Click to collapse
tnx brother i also make same mistek i flash recover in kernel and now only in recover same information as i see above but in device its not show os...version......i try to download your file but its link expire......please help me.
my htc one is stuck in recovery mode
i have a htc one from verizon ( unlocked) it was upgrading but was taking too long so i disconnect the phone ( big mistake i know) since that i turn on my phone and i got this :
ANDROID SYSTEM RECOVERY <3e>
at botton shows the following:
E:missing bitmap oem_unlock_bg
(code-1)
write host mode success
handle _cota_install: No CW files. Skip cw installation
hope you can help me
wachoforeal said:
i have a htc one from verizon ( unlocked) it was upgrading but was taking too long so i disconnect the phone ( big mistake i know) since that i turn on my phone and i got this :
ANDROID SYSTEM RECOVERY <3e>
at botton shows the following:
E:missing bitmap oem_unlock_bg
(code-1)
write host mode success
handle _cota_install: No CW files. Skip cw installation
hope you can help me
Click to expand...
Click to collapse
HTC One M7 or M8 ?
ls.xd said:
htc one m7 or m8 ?
Click to expand...
Click to collapse
htc one m8
wachoforeal said:
htc one m8
Click to expand...
Click to collapse
Flash TWRP in fastboot mode.
Install STOCK ROM in TWRP.
Phone will be fine again
i am downloading the software but how do i install?
---------- Post added at 05:55 PM ---------- Previous post was at 05:36 PM ----------
wachoforeal said:
i am downloading the software but how do i install?
Click to expand...
Click to collapse
i have a problem , i have just downloaded the twrp , but whenever i try to open, its a disc image , that is correct?
---------- Post added at 06:10 PM ---------- Previous post was at 05:55 PM ----------
Phone will be fine again
i have a problem , i have just downloaded the twrp , but whenever i try to open, its a disc image , is that correct?
---------- Post added at 06:40 PM ---------- Previous post was at 06:10 PM ----------
fella something is wrong , the twrp is a image file its not a program .
Phone will be fine again
Hello Everyone. Sorry Noob here. I just want to ask for help for my "bricked" htc u11. My HTC u11 wont boot after I upgraded it to OREO.
-Phone respond to Power button. But it just give me a blank screen and it vibrates.
-When connected to a charger, phone's screen blinks with battery icon and a lightning icon inside the battery icon. (I assumed it is not charging)
-Phone can enter Fastboot mode only using the button combination and fastboot can detects the device. ADB can't detect the device due to I can't find a way to enable DEVELOPERS option/USB debbuging because phone is dead and not booting to homescreen.
-CAN'T boot to recovery/bootloader/download mode
-Secure state : S-Off
-Device State: RELOCKED
-PC device manager can detect the phone under Android USB Devices as My HTC
I tried to flash TWRP but no luck. It wont boot to recovery. Everytime I choose "Boot to recovery" in Fastboot mode the phones turn off but wont boot to recovery. the phone turns off but after a seconds the screen blinks with the battery icon.
I dont know what to do now. I hope u can help me with this. Thank You in advance. Have a great day ahead!
not Tony Stark said:
Hello Everyone. Sorry Noob here. I just want to ask for help for my "bricked" htc u11. My HTC u11 wont boot after I upgraded it to OREO.
-Phone respond to Power button. But it just give me a blank screen and it vibrates.
-When connected to a charger, phone's screen blinks with battery icon and a lightning icon inside the battery icon. (I assumed it is not charging)
-Phone can enter Fastboot mode only using the button combination and fastboot can detects the device. ADB can't detect the device due to I can't find a way to enable DEVELOPERS option/USB debbuging because phone is dead and not booting to homescreen.
-CAN'T boot to recovery/bootloader/download mode
-Secure state : S-Off
-Device State: RELOCKED
-PC device manager can detect the phone under Android USB Devices as My HTC
I tried to flash TWRP but no luck. It wont boot to recovery. Everytime I choose "Boot to recovery" in Fastboot mode the phones turn off but wont boot to recovery. the phone turns off but after a seconds the screen blinks with the battery icon.
I dont know what to do now. I hope u can help me with this. Thank You in advance. Have a great day ahead!
Click to expand...
Click to collapse
Hello, let's try and see if anyone can help you.
First of all, you should give us some information on the firmware version you were using before upgrading to Oreo.
Try to restart it in fastbboot and then connect it to the PC and type the following commands:
- fastboot devices (if it works it should recognize the device and continue with the next command);
- fastboot getvar all (tell me the information you see on the line (bootloader) version-main:
Let us know...
paulpier007 said:
Hello, let's try and see if anyone can help you.
First of all, you should give us some information on the firmware version you were using before upgrading to Oreo.
Try to restart it in fastbboot and then connect it to the PC and type the following commands:
- fastboot devices (if it works it should recognize the device and continue with the next command);
- fastboot getvar all (tell me the information you see on the line (bootloader) version-main:
Let us know...
Click to expand...
Click to collapse
Hi thank you for your reply. Yes fastboot recognizes my Device. and heres the getvar all command result.
(bootloader) boot-mode:FASTBOOT
(bootloader) unlocked:no
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:MSM UFS
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache 0xE000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xDAD000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xEF000000
(bootloader) secure:yes
(bootloader) serialno:HT73G1800223
(bootloader) product:HTC_Phone
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
unfortunately I forgot the firmware version before i upgraded to oreo.
You could try to reflash oreo as you have soff, just grab an OTA file compatible with your cid and flash it in download mode
vegetaleb said:
You could try to reflash oreo as you have soff, just grab an OTA file compatible with your cid and flash it in download mode
Click to expand...
Click to collapse
I tried this already but I got an error. I'll try it again and post the error here. And i' ll check also the ota file. thanks for the reply
not Tony Stark said:
I tried this already but I got an error. I'll try it again and post the error here. And i' ll check also the ota file. thanks for the reply
Click to expand...
Click to collapse
Just flash you RUU again and you are good to go.
Most important thing: how did you update to Oreo?
Did you flash an OTA from SD card?
If yes did you pick the proper CID?
vegetaleb said:
Most important thing: how did you update to Oreo?
Did you flash an OTA from SD card?
If yes did you pick the proper CID?
Click to expand...
Click to collapse
Thru OTA
zopostyle said:
Just flash you RUU again and you are good to go.
Click to expand...
Click to collapse
Im downloading now the RUU. I will update u guys later. thanks for your help.
not Tony Stark said:
Thru OTA
Click to expand...
Click to collapse
Did you check the CID? a wrong CID can bring the phone
When going s-off via sunshine app it is only s-off till next reboot. After that it is s-on again and you can't flash firmware till you get to s-off again via sunshine app.
Trying to ruu the device is one way to go.
Send from the amazing HTC U11
zopostyle said:
Just flash you RUU again and you are good to go.
Click to expand...
Click to collapse
I downloaded the RUU and trries to flash it via fastboot. I tried the command " fastboot oem rebootRUU " but everytime i do this the phone just shut down and not booting with that black screen with htc logo. Then i need to do the buttons combination again to open the device to fastboot mode. I cant flash the RUU because i cant enter the RUU mode. I tried to flash the rom on fastboot mode and this is the error
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
any help guys? Thank you in advance
zopostyle said:
Just flash you RUU again and you are good to go.
Click to expand...
Click to collapse
vegetaleb said:
Did you check the CID? a wrong CID can bring the phone
Click to expand...
Click to collapse
Hello. I upgrsded to OREO officially. on phones settings - update.
Did you flash a custom bootloader before doign the update? You know like custom bootloader that don't show the warning message when you root your phone.
If so then it's the culprit because you have to flash back stock bootloader before trying a RUU or big OTA like nougat to Oreo.
So for now you have access to download mode?
vegetaleb said:
Did you check the CID? a wrong CID can bring the phone
Click to expand...
Click to collapse
Wrong cid and it won't flash.
Most likely took an ota on a rooted phone. Needs to be flashed back to stock.
*WARNING* do not s-on or relock the bootloader when you want to update. Just flash a signed ruu.zip from the external sdcard and you're good to go. It will unroot but it will leave s-off and unlocked bl alone. There is absolutely no reason whatsoever to s-on or lock the bootloader. Doing so will cause more problems than it solves.