Related
Hi all.
Im having some problems with this, and was hoping that some one here could help me.
I have unlocked my device, no problems.
Then i have installed CWM, no problems.
Now here my problems begin... I have copied a custom ROM zip file, onto my tablet. When i boot my tablet into CWM i get some errors in the bottom of the screen looking like this:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Now when i choose to "- Install zip from sdcard" and after that i choose "- Choose zip file from sdcard" i get this error: E:Can't mount /sdcard/
Then i try to select the "- Choose zip from internal storage" but then i get this error: E:Can't mount /emmc/
Basicly i cant do anything at all in CWM without getting errors, cant even whipe the cache or anything.
Can someone help me to find out what to do now. And hopefully how to solve this?
I can boot into my androind system without any problems.
Hope some one know's what to do. Thank you in advance.
Info:
TF300T
Android 4.2.1
Kernel 3.1.10-g6f31760
CWM-based Revovery v6.0.2.3
If there is anything else you need to know to be able to help me, please ask.
Have a good day.
CWM doesnt work with the 4.2 bootloader from ASUS. Only TWRP for bootloader 4.2 seems to work. You will have to flash TWRP 2.5.0.0-tf300t-4.2. Take note you need the TWRP version with the "-4.2" at the end. Flashing the incorrect TWRP version can brick your tablet.
Download http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.5.0.0-tf300t-4.2.blob.
Reboot tablet and hold volume down button while it's powering up to enter fastboot mode. Do not select any of the 3 icons (RCK, Android logo, Wipe Data) on tablet. Connect tablet to PC via USB cable.
On Windows PC, cmd window type:
fastboot -i 0x0B05 flash recovery openrecovery-twrp-2.5.0.0-tf300t-4.2.blob.
On tablet, wait until blue progress bar completely fills up.
On Windows PC, cmd window type:
fastboot reboot
That should replace your CWM with TWRP.
Hello ImmovableObject.
Thank you very much for you reply, that was excatly what was wrong.. Stupid me, not checking up on that. I actually flashed another version of TWRP, so i guess i was extreemly lucky that it did not brick my tablet.
But after i flashed the right TWRP its all good, everything is working as intented, and i can make backups and flash custom roms now. Thank you very much for your help
Have a good day all.
Jrod236 said:
Hello ImmovableObject.
Thank you very much for you reply, that was excatly what was wrong.. Stupid me, not checking up on that. I actually flashed another version of TWRP, so i guess i was extreemly lucky that it did not brick my tablet.
But after i flashed the right TWRP its all good, everything is working as intented, and i can make backups and flash custom roms now. Thank you very much for your help
Have a good day all.
Click to expand...
Click to collapse
You are very much welcomed! I'm glad it worked for you.
I found this useful when I was struggling with CWM as well, very glad I was careful to pick the 4.2 blob
Thanks for the help!
Holy Crap!
I can't believe how stupid I was! I ahve always despised CWM yet I was using it on my TF300T. After searching and searching for a fix I came onto this. Great job man!
THANK YOU FOR THIS!! I too stumbled around with CM Recovery for about 30 minutes, dumbfounded by the fact that it couldn't mount either the internal or external storage. I did some research and that's when I came across this post. I can't believe they don't make any mention in any of the tutorials that CM Recovery won't work with the newest 4.2 bootloader from Asus.
Your method did not work with my TF300T, Please assist
@ImmovableObject , I've tried your method but for some reason my Tablet did not reboot with the command "Fastboot reboot" and i still get CWM-based Recovery v6.0.2.3 for recovery instead of TWRP. it did say the flash was OKAY.
Please Please help
ImmovableObject said:
CWM doesnt work with the 4.2 bootloader from ASUS. Only TWRP for bootloader 4.2 seems to work. You will have to flash TWRP 2.5.0.0-tf300t-4.2. Take note you need the TWRP version with the "-4.2" at the end. Flashing the incorrect TWRP version can brick your tablet.
Download http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.5.0.0-tf300t-4.2.blob.
Reboot tablet and hold volume down button while it's powering up to enter fastboot mode. Do not select any of the 3 icons (RCK, Android logo, Wipe Data) on tablet. Connect tablet to PC via USB cable.
On Windows PC, cmd window type:
fastboot -i 0x0B05 flash recovery openrecovery-twrp-2.5.0.0-tf300t-4.2.blob.
On tablet, wait until blue progress bar completely fills up.
On Windows PC, cmd window type:
fastboot reboot
That should replace your CWM with TWRP.
Click to expand...
Click to collapse
mseck said:
@ImmovableObject , I've tried your method but for some reason my Tablet did not reboot with the command "Fastboot reboot" and i still get CWM-based Recovery v6.0.2.3 for recovery instead of TWRP. it did say the flash was OKAY.
Please Please help
Click to expand...
Click to collapse
That's strange.
Was your tablet running Android 4.2?
Try waiting a little longer (5 or more seconds) before issuing the "fastboot reboot" after the message that the flash was OKAY.
Things you could also try:
* Update your fastboot.exe to the latest version. You can do this via the Android SDK Manager on your computer. Fastboot is included under "Tools" > "Android SDK Platform-tools."
* Use a different USB cable.
* Connect cable to a different USB port on your computer.
ImmovableObject said:
CWM doesnt work with the 4.2 bootloader from ASUS. Only TWRP for bootloader 4.2 seems to work. You will have to flash TWRP 2.5.0.0-tf300t-4.2. Take note you need the TWRP version with the "-4.2" at the end. Flashing the incorrect TWRP version can brick your tablet.
Download http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.5.0.0-tf300t-4.2.blob.
Reboot tablet and hold volume down button while it's powering up to enter fastboot mode. Do not select any of the 3 icons (RCK, Android logo, Wipe Data) on tablet. Connect tablet to PC via USB cable.
On Windows PC, cmd window type:
fastboot -i 0x0B05 flash recovery openrecovery-twrp-2.5.0.0-tf300t-4.2.blob.
On tablet, wait until blue progress bar completely fills up.
On Windows PC, cmd window type:
fastboot reboot
That should replace your CWM with TWRP.
Click to expand...
Click to collapse
Thank you! Looking for days now. I installed TWRP 2.6 and CWM 5, 6 and touch. All the same problem. Flashed the TWRP from your link and everything works fine. Thank you
Raice.f4h said:
Thank you! Looking for days now. I installed TWRP 2.6 and CWM 5, 6 and touch. All the same problem. Flashed the TWRP from your link and everything works fine. Thank you
Click to expand...
Click to collapse
Hello.
I have TG300TG that only goes to CWM-based recovery v.6.0.1.3 and can not mount sd card. I've tried the mothod described here, but I can't get to fastboot mode. When I hold vol down it only goes to CWM again and again.
ImmovableObject said:
CWM doesnt work with the 4.2 bootloader from ASUS. Only TWRP for bootloader 4.2 seems to work. You will have to flash TWRP 2.5.0.0-tf300t-4.2. Take note you need the TWRP version with the "-4.2" at the end. Flashing the incorrect TWRP version can brick your tablet.
Reboot tablet and hold volume down button while it's powering up to enter fastboot mode. Do not select any of the 3 icons (RCK, Android logo, Wipe Data) on tablet. Connect tablet to PC via USB cable.
On Windows PC, cmd window type:
fastboot -i 0x0B05 flash recovery openrecovery-twrp-2.5.0.0-tf300t-4.2.blob.
On tablet, wait until blue progress bar completely fills up.
On Windows PC, cmd window type:
fastboot reboot
That should replace your CWM with TWRP.
Click to expand...
Click to collapse
Hello everyone.
I have same issue even with TWRP recovery 2.5.0.0
First of all when recovery starts i have a password request, don't know why but i press cancel and recovery starts normaly,
But when i select "install" i see internal storage (0 MB), nothing it's recognized into internal SD card.
I really need help for this issue, i'm in your hands guys :crying:
Device: TF300T
ROM: Asus Stock
ultimate_technologies said:
Hello.
I have TG300TG that only goes to CWM-based recovery v.6.0.1.3 and can not mount sd card. I've tried the mothod described here, but I can't get to fastboot mode. When I hold vol down it only goes to CWM again and again.
Click to expand...
Click to collapse
I have the same problem, to actually get back to the bootloader and select RCK or Android do this:
Once CMW is loaded open command and do
adb reboot-bootloader
that also enabled fastboot again but I'm still not able to load TWRP
---------- Post added at 01:50 AM ---------- Previous post was at 01:13 AM ----------
So just like the previous few posts I too installed CWM and I can't reflash TWRP.
Here's the output from the console:
D:\Android SDK\sdk\platform-tools>fastboot -i 0x0B05 flash recovery openrecovery
-twrp-2.5.0.0-tf300t-4.2.blob
sending 'recovery' (6448 KB)...
OKAY [ 2.699s]
writing 'recovery'...
OKAY [ 2.254s]
finished. total time: 4.955s
D:\Android SDK\sdk\platform-tools>fastboot devices
???????????? fastboot
D:\Android SDK\sdk\platform-tools>
Device is unresponsive to any commands and must be rebooted manually. Once I reboot the device loads to the CWM Recovery unless I run "adb reboot-bootloader" and then I can choose to boot the ROM. So at least it's not bricked.
Fix
Found this posted by buster.
So if you're TF300T is booting directly to recovery and you can't get to fastboot do what I post above:
1. Let recovery load
2. With recovery loaded you can now use adb. enter: adb reboot-bootloader
3. You should now be at the bootloader screen (RCK, Android, Wipe screen). Do this:
Originally Posted by Buster99 View Post
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back
i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot -i 0x0B05 erase system
fastboot -i 0x0B05 erase recovery
fastboot -i 0x0B05 erase userdata
fastboot -i 0x0B05 erase boot
fastboot -i 0x0B05 erase misc
fastboot -i 0x0B05 erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
cheers
-Buster
Click to expand...
Click to collapse
As Buster said
this was the first time i saw the loading bar while flashing
Click to expand...
Click to collapse
Before flashing I was not able to fastboot reboot-bootloader but this time I was.
Hope this helps
Many Thanks
Raice.f4h said:
Thank you! Looking for days now. I installed TWRP 2.6 and CWM 5, 6 and touch. All the same problem. Flashed the TWRP from your link and everything works fine. Thank you
Click to expand...
Click to collapse
All thanks for this thread, it solved my problem and now am rooted.
Again many thanks,
Gary
twpr is working
flashed twpr v2.5.0.0
works great so far, but it takes a little more time to load than cwm.
help!
right guys, I'm completely green when it comes to stuff like this so apologies if my questions are too daft.
I tried to root my tablet and forgot to back it up, tired few things I found online and got myself in a position where I can't use fastboot as my tablet is taking me to CWM recovery straight away and holding volume key and power makes no difference... any ideas? apart from throwing my table in a bin?
Hi there,
thanks to this forum I was able to flash several HTC phones sucessfully, but today I got perfectly stranded.
The original android version (jelly bean) of the Acer A700 was 4.1.1.
The plan was to get root access and put on CyanogenMod cm-10.1.0-RC5-a700.zip
Here is what I did:
- unlock the booloader (fastboot oem unlock)
- getting root access using easyroot.bat
I checked root access via "rootchecker" and everything appeared to be fine.
- Installing ClockWorkMod Recovery
- Under "recovery" I selected the A700 and also flashed the touch version of CWM
I opened up CWM and selected "reboot into recovery"
The A700 did was it was told and I got the usual CWM menue and could see the
desired cm-10.1.0-RC5 on my SD card
So far I was impressed how simple everything went and carried on flashing the CM10.1.
Before I did so I made a backup of the actual ROM on my SD card, then I selected
"wipe cache" an started the flashing process from the SD card.
Everything went fine and after a short time the rotating CyanogenMod Logo appeared.
However, the logo keeps on spinning an nothing else happens any more (20+ minutes)
I powered off the device and tried it again with the same result.
I also tried to press [power] + [vol -] to boot into recovery.
Letting go the [power] button and keeping the [vol-] button pressed after the device
vibrates for the first time brings up only "bootloader version JB365b3d3 (unlock mode)"
but the second line "loading recovery kernel image" does not appear anymore
In other words pressing the keys will show no difference to a normal start procedure.
When I connect the A400 with my PC and type in "adb devices" I get its number but the comment "offline"
In short, I have no idea what I could have done wrong nor how to access the device again
Is there someone out who can help me? - Thanks a lot in advance!
Comming from stock ROM, You must do Factory Reset / Wipe ALL to boot properly CM 10.1
About ADB, you must upgrade your Android SDK/ADB tools to the latest version, ADB changed a little with Android 4.2.2
With adb working, you can launch
adb reboot recovery
It should work, then make factory reset, and try to boot
Thanks a lot for the very fats response ... to be honest I thought, questions like mine are unlikely to be answered (oh no, not another dung-head who bricked his device)
However, I downloaded the latest adb version (dated 2013-05-22) and tried it again, but without success.
I can apply [pwr] + [vol-] ... [lock] to bring it into fastboot download mode.
At least the A700 shows the following lines:
Bootloader: Version JB-652b3d3 (unlock mode)
Bootloader: Version JB-652b3d3 (unlock mode) Starting Fastboot USB download protocol
Having achies this I tried to re-flash the initilally installed but now missing CWM
fastboot flash recovery root/recovery-clockwork-touch-6.0.2.3-a700.img
sending 'recovery' (5018 KB)...
OKAY[ 1. 326s]
wriiting 'recovery' ...
OKAY[ 1.154s]
finished. total time: 2.480s
fastboot erase cache
*** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY[ 0. 406s]
finished. total time: 0.406s
fastboot reboot
rebooting ...
finished. total time: 0.016s
Having done this I expected the CWM to be again on the A700, but when I start with [pwr] + [vol-] the A700 still does not boot into recovery.
Again I get this:
Bootloader: Version JB-652b3d3 (unlock mode)
followed by the nevern ending spinning CM10.1 logo ...
Without the adb running I'm pretty hopeless ... does a factory reset change anything at this stage?
You can try
fastboot boot root/recovery-clockwork-touch-6.0.2.3-a700.img
to go in recovery
and then in CWM
wipe all/factory reset
flash CM 10.1 again
flash gapps
reboot
We are ariborne, Sir!
Ereasing all partitions and flashing CWM again did the trick
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash recovery recovery-clockwork-6.0.2.3-a700.img
To be honest I don't understand why could not boot into recovery before?!
However all appears to be fine again!
Thanks a lot!
same problem
Hello, i have the same problem. I tried to flash CM with CWM but I didnt factory reset so my device is stuck. And i dont know anything about Sdk and Adb, can someone please explain to me how to do it
P.S: my bootloader was already unlocked so im very new to skd bull****, i dont know anything
2 hours I'm looking for a solution and this thead save my life
thanks for advises
the way I took is by the erasing all and fastboot boot recovery.img and after I install the last CM11 by the sdcard slot
Thanks a lot I can go to sleep
:good::good:
:angel:
Hi Guys,
Yesterday I installed the new TWRP 2.7.1.0. and that is when the problems started. Everytime when i loaded TWRP my screen got messed up and i got a split screen (At that time my ROM worked). So I tried to get back to a older TWRP, after a couple of tries i finally installed 2.4.4.0. But then I couldn't acces my internal memory nor my sdcard through TWRP(The ROM still worked fine). So i tried CWM, other TWRP's, still the same issue. To keep the story short, I eventually pressed on the WIPE button in Recovery ... And now I am stuck in TWRP. I can't load any zip files.. Is there any hope?
Tab: TF300T
A small update. After some trial and error i got my rom running again and i can also get in to recovery (Power button + volume down). Now I have erased the old TWRP with "fastboot erase recovery". But now I can't install a new recovery? I tried flashing a recovery and I am getting the messages "sending recovery ok", "writin recovery ok". But i don't see the loading bar on the tab...
I feel lonely here hehe.:laugh:
I resolved the issue and got my tablet running again, with the following steps:
Download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
http://support.asus.com/download.aspx?SLanguage=en&m=ASUS+Transformer+Pad+TF300T&os=8
Install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
If the PC doesn't recognize your tab, then try installing the universal naked drivers:
http://forum.xda-developers.com/showthread.php?t=2263822
Guide: http://forum.xda-developers.com/showthread.php?t=2139767
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
All credits to - Buster http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Hi to XDA comunity
... and happy festive season
I tried to install a new ROM. So, I followed tutorials and I have a huge problem
I passed to unlock the tablet
But, when I tried to install the new Recovery, the installation failed and now, the tablet doesn't want to boot
When I boot normaly, in recovery mode or Fastboot mode, I get this message :
Code:
Bootloader Version JB-653b3d3 (Unlock Mode)
Entering boot menu mode
Booting failed
Bootloader VJB-653b3d3(UnlockMode): Starting Fastboot USB download protocol
When I send "Fastboot device", the device is shown
When I send "Fastboot flash recovery twrp-2.6.3.0_a700.img"
Code:
sending 'recovert' <5736 KB>...
But still indefinitely
So I stop and retry and I obtain
downloading 'boot.img'...
FAILED <commande write failed <Unknow error>>
finished. total time: 0.???s
i tried to erase recovery and retry.
Tried with several USB cables.
I don't know what to do...
I guess it's a fastboot problem ? How can I found a fastboot file ?
Thanks for any help !
grimnnir said:
Hi to XDA comunity
... and happy festive season
I tried to install a new ROM. So, I followed tutorials and I have a huge problem
I passed to unlock the tablet
But, when I tried to install the new Recovery, the installation failed and now, the tablet doesn't want to boot
When I boot normaly, in recovery mode or Fastboot mode, I get this message :
Code:
Bootloader Version JB-653b3d3 (Unlock Mode)
Entering boot menu mode
Booting failed
Bootloader VJB-653b3d3(UnlockMode): Starting Fastboot USB download protocol
When I send "Fastboot device", the device is shown
When I send "Fastboot flash recovery twrp-2.6.3.0_a700.img"
Code:
sending 'recovert' <5736 KB>...
But still indefinitely
So I stop and retry and I obtain
downloading 'boot.img'...
FAILED <commande write failed <Unknow error>>
finished. total time: 0.???s
i tried to erase recovery and retry.
Tried with several USB cables.
I don't know what to do...
I guess it's a fastboot problem ? How can I found a fastboot file ?
Thanks for any help !
Click to expand...
Click to collapse
make sure you have the a700 and not the a701 or a510 etc etc....
also, you could try booting directly into fastboot:
1. power off
2. hold power and volume down, while you're doing that, constantly change the rotation switch from lock unlock lock unlock.... keep doing it for about 5 seconds
try flashing from here... it might give you the same result but worth a try.
other possible problems:
1. the recovery you downloaded is corrupt
2. the recovery you downloaded was not a working version
3. you might not have the right usb drivers installed
4. you might have used the wrong recovery commands
5. command (sometimes) needs to be Run as Administrator on Windows (right click)
6. you might have waited too long to reboot to recovery, or used the wrong method to do it
it might make it easier for you if you just rename recovery on computer to recovery.img (so you can just type fastboot flash recovery recovery.img)
also, I have uploaded a copy of the recovery I'm using (it's newer)
you can also try (while in fastboot)
Code:
fastboot boot twrp.img
(or any custom recovery)
It should boot without flashing, and from there you're will be able to flash firmware, ROM, etc...
Shreps said:
you can also try (while in fastboot)
Code:
fastboot boot twrp.img
(or any custom recovery)
It should boot without flashing, and from there you're will be able to flash firmware, ROM, etc...
Click to expand...
Click to collapse
it might be fine but personally I would not try that... recovery and boot are not to be confused and bootloaders are not to be messed with
hi
I would like to install twrp image, but adb says device not found, while on the list it sees, the serial nr is there..
I can even install the img, it writes 2x the okay, but doesn't boot. I'm stuck on fastboot screen, can I fix it?
When at the bootloader, you need to use fastboot commands, not adb.
So the command should be "fastboot boot imgname.img"
Hunter3U said:
When at the bootloader, you need to use fastboot commands, not adb.
So the command should be "fastboot boot imgname.img"
Click to expand...
Click to collapse
+1 for this.
Folks often mix up fastboot and adb. They are related, but different. Different operation requirements and functions.
adb:
- Only works in OS, or alternately in TWRP.
- Requires debugging toggled on in settings.
Fastboot:
- Only works in bootloader-fastboot mode.
- Does not require debugging to be toggled on.
Fastboot is typically what you want for unlocking bootloader, and booting TWRP (for root, etc.).
---------- Post added at 09:04 AM ---------- Previous post was at 09:00 AM ----------
ii9 said:
adb says device not found
I can even install the img, it writes 2x the okay, but doesn't boot. I'm stuck on fastboot screen, can I fix it?
Click to expand...
Click to collapse
Not completely clear based on your description. But is sounds like you are trying to do "adb devices" and then "fastboot flash twrp.img"?
In fastboot, you want to do "fastboot devices" (no quotes) and should see the phone's ID number in response.
Then you want to do "fastboot boot twrp.img" to boot TWRP, then flash the TWRP installer zip within TWRP. This is per the recommended install guide from the TWRP thread: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Although it's hard to determine exactly what you did wrong, unless you provide a more detailed sequence of what you did, and with the exact commands.
And to be clear, your bootloader is unlocked, correct?
well, sorry for being noob, for me was never a problem with older phones. I always managed to root, put twrp, change rom without any pc, but this double slot system kills me
so I managed to wipe everything before, vendor, sytem.., all
I wanted to put the havoc rom after formatting, but there was 5 local disks when I opened the phone folder on the pc, and obviously didn't copy the files on it. Therefore I did reboot to recovery, since that I had only the fastboot screen.
After that I unbricked it, all was fine again on the stock
After opened again the bootloader (yes, also before it was) installed the twrp.img, Installed the twrp zip, reboot it.
I followed the steps from havoc, but it said error 7, few times I tried. I reboooted the recovery again, and now I'm again the fastboot only, doesn't even show the warning msg about open bl, and doesn't go anywhere again.
I tried now with the fastboot command You gave, it says:
downloading 'boot.img'...
OKAY [ 1.265s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.312s
So I'm affraid I need to unbrick again.
If You can help me out, I'd apprecite :good: thanks!
Edit: I'm doing the unbrick again, but this time I'll wait for some info before I try the havoc. Also I'd love to get rid off this double slot thing, is there any way to do the normal method?
ii9 said:
*SNIP*
I tried now with the fastboot command You gave, it says:
downloading 'boot.img'...
OKAY [ 1.265s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.312s
So I'm affraid I need to unbrick again.
If You can help me out, I'd apprecite :good: thanks!
Edit: I'm doing the unbrick again, but this time I'll wait for some info before I try the havoc. Also I'd love to get rid off this double slot thing, is there any way to do the normal method?
Click to expand...
Click to collapse
I ran into the same error (and I have not been able to narrow down what causes it), and I had to fastboot flash boot twrp.img and actually flash TWRP to boot.
Once you flash TWRP to boot, and reboot your phone, you will be dropped right into TWRP.
Once in TWRP I was able to flash the stock boot image, then flash the TWRP installer zip, and finally Magisk. Basically you need to follow the instructions in the TWRP thread, with the only difference being that you flash TWRP to boot and not use fastboot boot. I hope to look into what the possible causes for this failure could be this weekend.
As for getting rid of slot A/B -- nope. That is part of the bootloader, so you will just have to get used to it. It is actually quite useful once you get the hang of it. For example, dual booting if you never intend to take OTA updates. It requires a bit of work to get setup (for example, you have to partition userdata since there is no userdata_a and userdata_b), and you need kernels and ROMs that understand the partitioning scheme.
-- Brian
Did you do fastboot flash boot imagename or fastboot flash recovery imagename
runningnak3d said:
I ran into the same error (and I have not been able to narrow down what causes it), and I had to fastboot flash boot twrp.img and actually flash TWRP to boot.
Once you flash TWRP to boot, and reboot your phone, you will be dropped right into TWRP.
Once in TWRP I was able to flash the stock boot image, then flash the TWRP installer zip, and finally Magisk. Basically you need to follow the instructions in the TWRP thread, with the only difference being that you flash TWRP to boot and not use fastboot boot. I hope to look into what the possible causes for this failure could be this weekend.
As for getting rid of slot A/B -- nope. That is part of the bootloader, so you will just have to get used to it. It is actually quite useful once you get the hang of it. For example, dual booting if you never intend to take OTA updates. It requires a bit of work to get setup (for example, you have to partition userdata since there is no userdata_a and userdata_b), and you need kernels and ROMs that understand the partitioning scheme.
-- Brian
Click to expand...
Click to collapse
I guess I lost it, time to accept the stock rom :crying:
I' not that old, but I can understand now why my grandma doesn't know even what is a phone
At the end I managed to do the unbrick again, after I installed havoc, I get rid of the error 7, and it showed me st like qualcomm crashdump, I was about to give up, but I went back to twrp installed again, now it's fine. Such a pity that it's not stable yet, I don't dare to touch after this..
tHanks for the info, in case I'll ever need I'll try to read again another 100x maybe I'll find out.
Bradl79 said:
Did you do fastboot flash boot imagename or fastboot flash recovery imagename
Click to expand...
Click to collapse
fastboot flash boot imagename
I did this
ii9 said:
I tried now with the fastboot command You gave, it says:
downloading 'boot.img'...
OKAY [ 1.265s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.312s
Click to expand...
Click to collapse
I think you are doing something wrong.
boot.img is basically a kernel, not TWRP.
Booting TWRP and flashing a boot.img are two completely different things.
It would help if you cut/paste the actual command you typed, so we can see what you did.
The command should be: fastboot boot twrp.img
That isn't what you did.
---------- Post added at 11:55 AM ---------- Previous post was at 11:48 AM ----------
ii9 said:
fastboot flash boot imagename
I did this
Click to expand...
Click to collapse
Nobody told you to do this.
The proper syntax is:
fastboot boot twrp.img
Seems similar, but this does something very different from the command you used. Syntax in fastboot/adb is absolutely ciritical. Always type fastboot and adb commands exactly as indicated, and double check everything before issuing the command.
fastboot boot twrp.img This boots the image file that is named. Note that you are not flashing anything with this command. Think of it as a remote boot of the TWRP file that is on your computer.
fastboot flash boot imagename This flashes the named file to the boot partition (basically the kernel)
If Havoc is the end goal here, from absolute stock start to finish it would be
1. Enable developer options
2. Enable oem unlock and usb debugging through the developer options menu (I also enable advanced reboot but not required)
3. Reboot to bootloader via the advanced reboot menu or through adb command "adb reboot bootloader"
4. While in bootloader, type in cmd, "fastboot oem unlock"
5. Allow bootloader unlock and wipe and let system reboot back to oos
6. Repeat steps 1-3 to get back to bootloader
7. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
8. Wipe Data and Dalvik (after data wipe, you might not be able to copy files to phone)
9. Reboot back to bootloader
10. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
11. Copy Havoc, TWRP.zip, GAPPS, Magisk to device (GAPPS and Magisk are optional...if not needed, skip the steps for them)
12. Flash Havoc and TWRP.zip through normal install process
13. Reboot to recovery
14. Flash Havoc and TWRP.zip through normal install process again
15. Reboot to recovery
16. Flash GAPPS and Magisk (If error 70 thrown with GAPPS install, reboot to system once and run through any setup then reboot back to recovery to flash)
17. Reboot system
As long as no other errors are thrown, you should now be in Havoc with GAPPS and Magisk installed
redpoint73 said:
Nobody told you to do this.
The proper syntax is:
fastboot boot twrp.img
Click to expand...
Click to collapse
Sorry, I messed up with the copy and paste, I didn't sleep too much in the last days for the hot, I'm a bit heavy in the head, pls exuse my bs. I also tried this one that you wrote, but didn't manage to boot still.. I have no clue what went wrong, but again, thanks, in case I can come back to read again.
Hunter3U said:
If Havoc is the end goal here, from absolute stock start to finish it would be
1. Enable developer options
2. Enable oem unlock and usb debugging through the developer options menu (I also enable advanced reboot but not required)
3. Reboot to bootloader via the advanced reboot menu or through adb command "adb reboot bootloader"
4. While in bootloader, type in cmd, "fastboot oem unlock"
5. Allow bootloader unlock and wipe and let system reboot back to oos
6. Repeat steps 1-3 to get back to bootloader
7. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
8. Wipe Data and Dalvik (after data wipe, you might not be able to copy files to phone)
9. Reboot back to bootloader
10. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
11. Copy Havoc, TWRP.zip, GAPPS, Magisk to device (GAPPS and Magisk are optional...if not needed, skip the steps for them)
12. Flash Havoc and TWRP.zip through normal install process
13. Reboot to recovery
14. Flash Havoc and TWRP.zip through normal install process again
15. Reboot to recovery
16. Flash GAPPS and Magisk (If error 70 thrown with GAPPS install, reboot to system once and run through any setup then reboot back to recovery to flash)
17. Reboot system
As long as no other errors are thrown, you should now be in Havoc with GAPPS and Magisk installed
Click to expand...
Click to collapse
Not exactly, the end goal to have a clean rom, with basic custumization, that even stock should include in my opinion, like disable headups.., extended screen etc. Plus without google staff, for me it's too strict. As in this moment not so many choice, havoc looked the most near to my wishes, in fact very nice after these hours, I guess I'll be fine with it when the bugs will disappear.
Anyway 1-7 was always without problem. Today after 2 unbrick and bl opening what I did is, through fastboot I entered to the img, from there I flashed the zip, reboot recovery to make sure it stays. I put files on the phone, wiped dalvik and data, install rom+twrp and as it is written here and also on that thread, I rebooted recovery. And I wanted to repeat the flash, but I had the internal storage 0mb thing. So I needed to format data (that's the solition I found) and reboot again, put back files, flash, reboot, flash again, and after I got that qualcomm crashdump screen. I hold the up+power to get back to twrp (or down, not sure) and I flashed again, but only once, so after it worked finally. Since that I'm fine
But sure I need to learn this stuff, it cannot be that I always face st that nobody else does
I hope the managed soon the ota for custom roms and we can do it easy and quick without setting the phone over and over again with all the apps, settings.. (probably only me in the world need to do so, as I start to loose it with the tech staff)
Poor phone is just couple of weeks old, but already saw everything
Thanks for writing
If it means anything to you, I use stock OOS+TWRP+Magisk+Renovate ICE+Xposed (to ignore the secure flag, otherwise Netflix doesn't work over HDMI). Everything works, including Google Pay.