Related
Hey guys,
I'm having some trouble with flashing a new ROM and now I've soft-bricked my device.
I was trying to flash from CROMi to CM11 so I wiped data, cache, dalvik using TWRP. But when i tried to flash CM11 M9, i would get the "failed" error. I tried flashing other ROMs but same result - "FAILED".
So I thought maybe it was the recovery. I downloaded a CWM recovery (in .zip) and tried to flash it. FAILED!
I tried to restore my device using the "Recover /Downgrade from Jelly Bean to ICS/Clean Factory Restore with custom recovery" method from this post. Since it is basically flashing the stock ROM, naturally it fails.
Now I'm out of ideas. How can I save my tablet?
Thanks for your help guys!
PS: I'm trying to install CMW via fastboot. When I press power + vol down, I get to the screen with "RCK, Android, Data Wipe"; I dont see the USB icon. How do i boot into fastboot?
You are in fastboot mode when you see the three icons. Read the tiny script.
Except for CM11 M9 you did not give us anything to work with.
Give us the version numbers of:
- CROMi-X you were running
- your bootloader
- your recovery
My best guess is you are trying to flash something with an incompatible recovery, but that's just a wild guess.....
And stop flashing willy nilly until you know what's going on. You can brick this tablet if you try hard enough, you know....
berndblb said:
You are in fastboot mode when you see the three icons. Read the tiny script.
Except for CM11 M9 you did not give us anything to work with.
Give us the version numbers of:
- CROMi-X you were running
- your bootloader
- your recovery
My best guess is you are trying to flash something with an incompatible recovery, but that's just a wild guess.....
And stop flashing willy nilly until you know what's going on. You can brick this tablet if you try hard enough, you know....
Click to expand...
Click to collapse
Hey bern,
Thanks for the reply.
My tablet got really slow so I decided to flash CM 11 M9, which is what I use on my Note 3.
I'm running TWRP 2.6.1.0. Not sure which CROMi I was running because I can't boot into Android. I did a data wipe prior to (attempting to) flashing CM11 and now it boots straight to recovery.
I read that TWRP is not compatible with CM11 and that I should flash CWM. But TWRP fails when I try to flash anything so I'm thinking I should attempt ADB sodeload or terminal command and load that way?
Thanks again
Edit: I downloaded CM11 M9 for tf700. I also tried various nightlies in case my original download was corrupt. It ends in failure
berndblb said:
You are in fastboot mode when you see the three icons. Read the tiny script.
Except for CM11 M9 you did not give us anything to work with.
Give us the version numbers of:
- CROMi-X you were running
- your bootloader
- your recovery
My best guess is you are trying to flash something with an incompatible recovery, but that's just a wild guess.....
And stop flashing willy nilly until you know what's going on. You can brick this tablet if you try hard enough, you know....
Click to expand...
Click to collapse
Hi berndblb!
I'm also having this problem and I see that you're quite active in the TF700 forum that you could help me out. I wouldnt say I'm an expert but I have tinkered with phones (mostly Samsung and Nexus devices) in the past so I am familiar with ADB, terminal commands, flashing ROMs, etc.
I'm running TWRP 2.6.1. I was running CROMi-X (not sure which version) and wanted to flash OmniROM. However, TWRP would show "error flashing zip" and "failed" in red. I tried flashing a few other zips including TWRP 2.7.1.1 and CWM (I readTWRP is not compatible with some ROMs) and I would still get the error and "failed".
So now, I can't boot into the OS to flash a recovery via fastboot or via CWM Rom Manager, nor can I flash anything in TWRP. I also attempted to flash TWRP 2.7.1.1 via terminal command
HTML:
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4[HTML]. I loads but it doesnt install when i restart my device.
What do you think I should try next? I'm getting pretty desperate at this point. Is my device bricked-bricked or can i salvage it?
Thanks!
oh.herro said:
Hi berndblb!
I'm also having this problem and I see that you're quite active in the TF700 forum that you could help me out. I wouldnt say I'm an expert but I have tinkered with phones (mostly Samsung and Nexus devices) in the past so I am familiar with ADB, terminal commands, flashing ROMs, etc.
I'm running TWRP 2.6.1. I was running CROMi-X (not sure which version) and wanted to flash OmniROM. However, TWRP would show "error flashing zip" and "failed" in red. I tried flashing a few other zips including TWRP 2.7.1.1 and CWM (I readTWRP is not compatible with some ROMs) and I would still get the error and "failed".
So now, I can't boot into the OS to flash a recovery via fastboot or via CWM Rom Manager, nor can I flash anything in TWRP. I also attempted to flash TWRP 2.7.1.1 via terminal command
HTML:
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4[HTML]. I loads but it doesnt install when i restart my device.
What do you think I should try next? I'm getting pretty desperate at this point. Is my device bricked-bricked or can i salvage it?
Thanks![/QUOTE]
Can you enter fastboot at all ?
Thx Josh
Click to expand...
Click to collapse
r3dal3rt said:
Hey bern,
Thanks for the reply.
My tablet got really slow so I decided to flash CM 11 M9, which is what I use on my Note 3.
I'm running TWRP 2.6.1.0. Not sure which CROMi I was running because I can't boot into Android. I did a data wipe prior to (attempting to) flashing CM11 and now it boots straight to recovery.
I read that TWRP is not compatible with CM11 and that I should flash CWM. But TWRP fails when I try to flash anything so I'm thinking I should attempt ADB sodeload or terminal command and load that way?
Thanks again
Edit: I downloaded CM11 M9 for tf700. I also tried various nightlies in case my original download was corrupt. It ends in failure
Click to expand...
Click to collapse
Right now the most important thing is the bootloader version ....
On the bootloader screen upper left there is a bootloader version in really small print ...
This is what we need to know ...
Thx Josh
lj50036 said:
Right now the most important thing is the bootloader version ....
On the bootloader screen upper left there is a bootloader version in really small print ...
This is what we need to know ...
Thx Josh
Click to expand...
Click to collapse
Exactly.
I also would like to know how you performed the wipe you mentioned. The tablet booting only and straight to recovery would indicate that you used 'Wipe Data' from the bootloader???
Also, do not use ROM Manager. It does not work well with the Transformers and can cause a lot of problems.
I have a feeling another user is going to benefit from your excellent unbrick guide, Josh...
Aren't you glad you wrote it?? [emoji12]
lj50036 said:
Can you enter fastboot at all ?
Thx Josh
Click to expand...
Click to collapse
Hi Josh. All i get is the Asus starting screen and "your device is unlocked". Power + vol down doesn't not take me to bootloader.
oh.herro said:
Hi Josh. All i get is the Asus starting screen and "your device is unlocked". Power + vol down doesn't not take me to bootloader.
Click to expand...
Click to collapse
No boot to recovery ?
No bootloader ?
No nvflash blob backups ?
If that is the case then you are not looking good ...
There is no way out of this one ...
We need fastboot or recovery one or the other ..
Sorry for the bad news ....
Thx Josh
oh.herro said:
Hi Josh. All i get is the Asus starting screen and "your device is unlocked". Power + vol down doesn't not take me to bootloader.
Click to expand...
Click to collapse
I agree with lj - not looking good. [emoji17]
Do you have adb access when it boots to the Asus splash screen?
Hello guys,
I have a problem, I hope you can help me with.
I used to have an EOS ROM. I decided to do factory reset and thats when my problems started. It didn't boot up anymore. After entering recovery I noticed it couldn't mount System partition. I tried reinstalling the ROM, but no success. Everytime I entered recovery, the System checkbox wasnt marked. So I decided to go back to stock, using http://androidforums.com/threads/return-your-xoom-to-stock.653230/. Now it is stuck at Logo screen and can't enter Recovery. (Goes to Reading ODM fuse, but not any further). I can still enter Fastboot and my laptop detects the tablet, when hooked up to it.
Please help me push the Recovery, cuz I'm getting "device not found" from ADB. I'm kinda lost here... Any help would be appreciated!
Update
I managed to install TWRP, but still can't mount System Partition. On wipe I get "Failed"when trying to clean the system part. I have tried Clockwork, it didn't help either.
Cmon guys! I don't want to JTAG it yet.
HexBox said:
Cmon guys! I don't want to JTAG it yet.
Click to expand...
Click to collapse
I am not very knowledgable about flashing, but one suggestion has come to my mind: if you can now get into TWRP (it wasn't clear whether you could based on your last post), try flashing a ROM without trying to clean the system partition. Just make sure the ROM matches the TWRP (i.e., big part ROM with big part TWRP).
Oh - another thought - folks in a number of threads have stated you need to explicitly follow both the recovery and ROM instructions for the XOOM. If you miss a step, people have had issues.
Hello, my tablet seems to be stuck in a boot loop and i've tried flashing the recovery and supersu again to no avail. I've also tried that exitrecovery zip floating around. I think I might have flashed a kernel by accident want trying to root.
Background
Tried using WinDroid Universal Android ToolKit. <- was successful in unlocking bootloader only. tried various times to install twrp but nothing would happen. The "recovery mode" in BL would just show android with caution triangle. I then used WinDroid's "commands" section to try and flash recovery. I may have flashed kernel instead? I have CWM 6.0.5.0. Help would be appreciated. This is what i get for trying to take the easy way out -_-.
Update: I tried "SHIELD TABLET RECOVERY IMAGE FLASHING INSTRUCTIONS" from nvidia itself and now it just hangs in the nvidia logo screen forever. I tried both the "flash-all.bat" and the manual line by line one. any clues?
If someone could tell me how to just make the wipe the whole thing i wouldn't mind restarting to root properly.
Any one got any info? =D
Cveezy said:
Any one got any info? =D
Click to expand...
Click to collapse
Its not hard, just restore it back to factory, a couple of quick google searches:
https://developer.nvidia.com/sites/...s/HowTo-Flash-SHIELDTablet-Recovery-Image.txt
http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
When you download the images make sure you do a MD5 on them.
The good news its very hard to kill this tablet, and very easy to unlock/flash/root.
jpierson said:
Its not hard, just restore it back to factory, a couple of quick google searches:
https://developer.nvidia.com/sites/...s/HowTo-Flash-SHIELDTablet-Recovery-Image.txt
http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
When you download the images make sure you do a MD5 on them.
The good news its very hard to kill this tablet, and very easy to unlock/flash/root.
Click to expand...
Click to collapse
I tried flashing and doing a full OTA rom install to no avail. I however unsure what MD5 is and would that have a effect on my outcome.
Cveezy said:
I tried flashing and doing a full OTA rom install to no avail. I however unsure what MD5 is and would that have a effect on my outcome.
Click to expand...
Click to collapse
You restored the recovery, boot, system, and userdata per the instructions and it still boot loops?
Check out this post:
http://forum.xda-developers.com/shield-tablet/help/help-stuck-nvidia-boot-screen-t3076462
jpierson said:
You restored the recovery, boot, system, and userdata per the instructions and it still boot loops?
Check out this post:
http://forum.xda-developers.com/shield-tablet/help/help-stuck-nvidia-boot-screen-t3076462
Click to expand...
Click to collapse
Yeah, its werid that its still stuck. I have tried doing it both way manual tell adb each file to flash and through the flash-all.bat way as well. Im going to try the link you sent in a bit.
How long did you let it sit at the boot logo? If you are booting on a clean install it may take a bit longer.
Just download and use fastboot (fastboot flash recovery image.img) to flash twrp. I'd suggest using adb/fastboot anyway since it's simple enough and a good thing to learn if you plan on doing this sort of thing. After that you can just flash from there. The ota zips, super su, etc. and wipe.
i cant really explain what i was doing but i was trying to root the phone and after rooting it i tried to fix an issue with twrp crashing. it ended up with me stuck in a bootloop that i cant get out of. i have basicly no experience in the stuff so i am in desperate need of help. you can reply to the forum or msg me on an a platform like discord (TobiS137#2131) preferably discord tho. thanks in advance! i really want it fixed asap so if you can help then please be quick. please reply under the thread if you have msg me on discord. i really need help.
TobiS137 said:
i cant really explain what i was doing but i was trying to root the phone and after rooting it i tried to fix an issue with twrp crashing. it ended up with me stuck in a bootloop that i cant get out of. i have basicly no experience in the stuff so i am in desperate need of help. you can reply to the forum or msg me on an a platform like discord (TobiS137#2131) preferably discord tho. thanks in advance! i really want it fixed asap so if you can help then please be quick. please reply under the thread if you have msg me on discord. i really need help.
Click to expand...
Click to collapse
Enter fastboot, flash official twrp.Flash magisk in twrp.
vrda08 said:
Enter fastboot, flash official twrp.Flash magisk in twrp.
Click to expand...
Click to collapse
can you help me further? as i said i am a huge newbie and i only understood a little of that. is there any other ways you can contact me?
vrda08 said:
Enter fastboot, flash official twrp.Flash magisk in twrp.
Click to expand...
Click to collapse
Can you explain what exactly were you doing ?!
Just hold the power button for 60 seconds or so, it should reboot normally. Did you flash twrp or just do fastboot boot twrp?
I'm new to this while A/B partition. I went through all the steps and my phone is rooted, with Magisk and TWRP. All seems to be fine. My question is this. When I boot to the recovery (TWRP) and choose the reboot option it defaults to Current Slot: Partition B. If I reboot to partition B it goes back to TWRP. I have to select Partition A to get the device to boot to the system.
Is this normal? Do I need to set it up in a different way?
samteeee said:
Can you explain what exactly were you doing ?!
Click to expand...
Click to collapse
i was trying to root the phone (wich i did) and then the twrp app that was on my phone after i had tried to install it using the img. it then turned into an ap that told me to update it in google play
after that was done i tried to flash it but everytime i tried it just crashed. a little time later after trying some more times i found that i started it in the bootloader and it ended up with me stuck in a bootloop. again i might not have explained enough. i am huge noob so i really need help.
ooshkamils said:
Just hold the power button for 60 seconds or so, it should reboot normally. Did you flash twrp or just do fastboot boot twrp?
Click to expand...
Click to collapse
i think i did fastboot boot twrp. still not sure tho :\ . Does it change anything that i use twrp enchilada or does that not matter?
ooshkamils said:
Just hold the power button for 60 seconds or so, it should reboot normally. Did you flash twrp or just do fastboot boot twrp?
Click to expand...
Click to collapse
i think i did fastboot boot twrp. still not sure tho :\
discord
ignore the "discord" title. i dont think the phone has an OS right now. when i turn it on it goes directly to twrp. if i reboot the system it just goes back to twrp recovery. i think i need a way to install an OS (preferably OxygenOS if that is even possible). i realised that you guys properbly won't msg on discord. you dont have to. you can use the forums . i just really want help to get my phone back up and running. it is a OnePlus 6 btw if that is important.
TobiS137 said:
i think i did fastboot boot twrp. still not sure tho :\
Click to expand...
Click to collapse
To keep TWRP as the phones recovery, you'd first need to do as you did "Fastboot boot twrp" but that command will only allow you to boot into TWRP through your pc or whatever you ran that command on. After you've entered that temporary recovery, you'll need the TWRP installer .zip file, and flash that inside of that temporary TWRP. Then you can reboot into recovery on your phone again since it has been installed to one of the partitions.
TobiS137 said:
ignore the "discord" title. i dont think the phone has an OS right now. when i turn it on it goes directly to twrp. if i reboot the system it just goes back to twrp recovery. i think i need a way to install an OS (preferably OxygenOS if that is even possible). i realised that you guys properbly won't msg on discord. you dont have to. you can use the forums . i just really want help to get my phone back up and running. it is a OnePlus 6 btw if that is important.
Click to expand...
Click to collapse
You have to flash magisk after flashing twrp or else you are going to get this bootloop you are talking about
phone open again
my phone is back up and running again. i changed the partitian slot from A( the broken one with no OS) to B(the unchanged one) and it is now working again. if anyone is having the same problem the try to change to the second slot. it happend in twrp enchilada 3.2.2-0 if it is important. thank you all for your support.
I may be mistaken but I believe all you need to do is flash magisk to get up and running again
hallo dare said:
You have to flash magisk after flashing twrp or else you are going to get this bootloop you are talking about
Click to expand...
Click to collapse
Why? You should be able to just flash the TWRP installer into TWRP and so its flashed into both boot_a and boot_b. It should boot ok to system from there, Magisk is just another mod to the boot partitions, like a custom kernel, etc. It should not be necessary at all, why you guys keep sayin Magisk is necessary for anything? it isn't.
RusherDude said:
Why? You should be able to just flash the TWRP installer into TWRP and so its flashed into both boot_a and boot_b. It should boot ok to system from there, Magisk is just another mod to the boot partitions, like a custom kernel, etc. It should not be necessary at all, why you guys keep sayin Magisk is necessary for anything? it isn't.
Click to expand...
Click to collapse
Because you do. The OP6 will not boot with custom recovery unless it's rooted. I believe this is because the recovery and boot partitions are merged on this device. You're welcome to bootloop all day if you don't believe us.
iElvis said:
Because you do. The OP6 will not boot with custom recovery unless it's rooted. I believe this is because the recovery and boot partitions are merged on this device. You're welcome to bootloop all day if you don't believe us.
Click to expand...
Click to collapse
Asking "why?" is not to not believe you, and the personal bootloop all day attack is out of the matter. TWRP is flashed on the ramdisk and should boot stock, unless something derped, if it doesn't boot I honeslty don't understand why, what is the exact reason? TWRP installer doesn't overwrite the boot, just patches it to have a mini recovery on it. It should boot...
RusherDude said:
Asking "why?" is not to not believe you, and the personal bootloop all day attack is out of the matter. TWRP is flashed on the ramdisk and should boot stock, unless something derped, if it doesn't boot I honeslty don't understand why, what is the exact reason? TWRP installer doesn't overwrite the boot, just patches it to have a mini recovery on it. It should boot...
Click to expand...
Click to collapse
I don't know for sure either, beyond what I said above. But everyone who has reported not flashing magisk has bootlooped.
If I sounded snippy, it was only because your post above was appearing to deny the reality of what is a very well-known issue with this phone.
iElvis said:
I don't know for sure either, beyond what I said above. But everyone who has reported not flashing magisk has bootlooped.
If I sounded snippy, it was only because your post above was appearing to deny the reality of what is a very well-known issue with this phone.
Click to expand...
Click to collapse
I am not denying anything! just surprised because on TWRP website they clearly state that no post-twrp-flashing step is needed:
https://twrp.me/oneplus/oneplus6.html
The OnePlus 6 uses the newer AB partition scheme first introduced on the Pixel 1. As such there is no recovery partition. Instead, the recovery is part of the boot image. You will temporarily boot TWRP to perform and later perform a more permanent TWRP installation. First download the TWRP zip file directly on your device. If you don't download the zip file to your device first for any reason, you will need to adb push the zip to the device because MTP is not currently working on the OnePlus 6 in TWRP. If you are unable to use adb, you can also use a USB stick with an OTG cable, if you have those handy. Power off the device. Hold volume up to get into fastboot mode. Run this command on your computer: fastboot boot twrp-3.2.1-0-enchilada.img
In TWRP, tap on Install and browse to the zip and install it (the zip will probably be in /sdcard/Downloads). TWRP will now be installed to both slots. TWRP is now installed and you can reboot and use your device as normal.
MTP is disabled because it causes a kernel panic sometimes with the stock kernel.
Click to expand...
Click to collapse
Maybe the issue here is that the unofficial TWRP that everyone used NEEDS magisk while the official doesn't?
RusherDude said:
Maybe the issue here is that the unofficial TWRP that everyone used NEEDS magisk while the official doesn't?
Click to expand...
Click to collapse
I think most people have moved to the official version. If it doesn't need magisk to avoid a bootloop, that's news to me. Not saying it's not the case, but I haven't seen any mention of it.
Goodmorning everyone
I have a problem on my TF300TG which I picked up from my drawer after a while
I upgraded to 7.1 nougat following the instructions given in the letter (very clear) but now my tablet does not start the system, I explain better:
it turns on and the writing unlock remains The device is unlocked with the ASUS logo in the Center but does not start.
I can go back to recover twrp at any time and reflect what I have repeated several times even with different versions but I always have the same problem.
I can also re-revise the original flash blob and start again
Giangi_TF300TG said:
I upgraded to 7.1 nougat following the instructions given in the letter (very clear) but now my tablet does not start the system, I explain better:
it turns on and the writing unlock remains The device is unlocked with the ASUS logo in the Center but does not start.
I can go back to recover twrp at any time.
Click to expand...
Click to collapse
First of all format data through Kang TWRP recovery. It may take until one hour. Be patient. Let it run. After that install rom, SUSuperuser and pico Gapps in one run.
Not boot again
ebonit said:
First of all format data through Kang TWRP recovery. It may take until one hour. Be patient. Let it run. After that install rom, SUSuperuser and pico Gapps in one run.
Click to expand...
Click to collapse
I just finished the procedure that you suggested that it did not return me errors but does not boot.
just restarted of the recovery mode updates the twrp restarts and remains nailed on the Asus screen if I want I can restart in recovery.
Any other suggestions?
Giangi_TF300TG said:
I just finished the procedure that you suggested that it did not return me errors but does not boot.
just restarted of the recovery mode updates the twrp restarts and remains nailed on the Asus screen if I want I can restart in recovery.
Any other suggestions?
Click to expand...
Click to collapse
Yes, you should do carefully a Buster99: https://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
This procedure brings you back on a clean stock rom Android 4.2 Jelly Bean. Then you have to flash Kang TWRP firstly.
PS: Attention! If you restart in recovery with the 3 icons, never touch the third one in order to "Wipe Data". It bricks your device!
ebonit said:
Yes, you should do carefully a Buster99: https://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
This procedure brings you back on a clean stock rom Android 4.2 Jelly Bean. Then you have to flash Kang TWRP firstly.
PS: Attention! If you restart in recovery with the 3 icons, never touch the third one in order to "Wipe Data". It bricks your device!
Click to expand...
Click to collapse
The factory reset has been done correctly the system has restarted correctly after reinserting the nougant yet the system does not boot the only thing that has changed and that now reboots into the loop by returning to the asus screen repeatedly
Giangi_TF300TG said:
The factory reset has been done correctly the system has restarted correctly after reinserting the nougant yet the system does not boot the only thing that has changed and that now reboots into the loop by returning to the asus screen repeatedly
Click to expand...
Click to collapse
It seems there has been a big misunderstanding by you. I advised to format data through Kang TWRP, but you did a factory reset, didn't you?.
Too many people mix up wipes and formats. Format only data means, not factory reset, not wipe - you format it ext4, then convert it to f2fs. Formatting in Kang TWRP takes until 1 hour. If it went faster you did not format. Kang TWRP does a deep format that rewrites everything in the partition. No moldy leftovers.
Now your device is in a boot loop, but not bricked. So doing a Buster99 is the only way to solve the problem. If you need help with fastboot, head over to the General section. Download and install "Minimal ADB and Fastboot" on your PC.
ebonit said:
It seems there has been a big misunderstanding by you. I advised to format data through Kang TWRP, but you did a factory reset, didn't you?.
Too many people mix up wipes and formats. Format only data means, not factory reset, not wipe - you format it ext4, then convert it to f2fs. Formatting in Kang TWRP takes until 1 hour. If it went faster you did not format. Kang TWRP does a deep format that rewrites everything in the partition. No moldy leftovers.
Now your device is in a boot loop, but not bricked. So doing a Buster99 is the only way to solve the problem. If you need help with fastboot, head over to the General section. Download and install "Minimal ADB and Fastboot" on your PC.
Click to expand...
Click to collapse
Excuse me surely I did not understand here now I follow your advice step by step.
Now I'm running a buster99 but I don't need ADB, I already have a fastboot working.
PS that is I'm starting fastboot not from adb but from a folder on my pc that is executing the buster commands
Then what do I reinsert the right Kang bootloader?
Excuse my ignorance
Giangi_TF300TG said:
Excuse me surely I did not understand here now I follow your advice step by step.
Now I'm running a buster99 but I don't need ADB, I already have a fastboot working.
PS that is I'm starting fastboot not from adb but from a folder on my pc that is executing the buster commands
Then what do I reinsert the right Kang bootloader?
Excuse my ignorance
Click to expand...
Click to collapse
Now my system is restarted with the original rom I reinsert twrp_tf300t_kang_2.8.7.2.img,
after how do I proceed?
Giangi_TF300TG said:
Now my system is restarted with the original rom I reinsert twrp_tf300t_kang_2.8.7.2.img,
after how do I proceed?
Click to expand...
Click to collapse
Congratulations, good job!
Please look here: https://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479
ebonit said:
Congratulations, good job!
Please look here: https://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479
Click to expand...
Click to collapse
I have already inserted this twrp tf300t kang 2.8.7.2.img, through fastboot do I have to do it with the linux procedure?
the system now has boot recovery and starts normally with the old system.
Now that I do I have to delete the given partition or do I flash the three roms?
Giangi_TF300TG said:
I have already inserted this twrp tf300t kang 2.8.7.2.img, through fastboot do I have to do it with the linux procedure?
the system now has boot recovery and starts normally with the old system. What does old system mean?
Click to expand...
Click to collapse
I'm sorry, but it is not easy to understand what you did. As far as I know your device is on stock rom Android 4.2 Jelly Bean. Correct?
The next step should be to flash (not insert!) "twrp_tf300t_kang_2.8.7.2_signed.zip" via fastboot. The command is: "fastboot -i 0x0B05 flash recovery foo.img". Replace foo.img with the recovery image name! Did you?
If yes, you may start the device into recovery. Kang TWRP should start. After that install through TWRP Nougatella #39, pico Gapps and Super SU from the external memory of your device in one run. That's it!
Please pay attention you did download the newest versions in post #1: https://forum.xda-developers.com/transformer-tf300t/development/rom-t3453702 !
ebonit said:
I'm sorry, but it is not easy to understand what you did. As far as I know your device is on stock rom Android 4.2 Jelly Bean. Correct?
The next step should be to flash (not insert!) "twrp_tf300t_kang_2.8.7.2_signed.zip" via fastboot. The command is: "fastboot -i 0x0B05 flash recovery foo.img". Replace foo.img with the recovery image name! Did you?
If yes, you may start the device into recovery. Kang TWRP should start. After that install through TWRP Nougatella #39, pico Gapps and Super SU from the external memory of your device in one run. That's it!
Please pay attention you did download the newest versions in post #1: https://forum.xda-developers.com/transformer-tf300t/development/rom-t3453702 !
Click to expand...
Click to collapse
Sorry I'm using google translate
So far I have flashed the recovery twrp_tf300t_kang_2.8.7.2.img.
I restarted in recovery mod TWRP and I installed the 3 zip in sequence through sd card
KatKiss-7.1_TF300T_039.zip, open_gapps-arm-7.1-pico-20200325.zip, SuperSU-v2.82-201705271822.zip all OK
I ran Wipe cache / dalvik
I restarted
performed a first start where the bar under ASUS quickly colored blue
It has restarted
but later stuck on ASUS. I don't know where I'm wrong
From the fact that you have not replied to my last message, I think we have given up.
Just one thing I'm curious to know are there versions of this Tablet with different hardware or different firmware (bios) you can update? I don't know I thought even if I had to have a rom already cooked and functioning on an equal tablet I could shoot it in a single flash
Giangi_TF300TG said:
Sorry I'm using google translate
I don't know where I'm wrong
Click to expand...
Click to collapse
I'm sorry, but I also don't know where have been wrong? How should I reply after so less information about the situation. There are many different possibilities.
Hopefully you have a backup of the system through TWRP after finishing the Buster99. If so, please start the TWRP recovery and restore the backup.
Search here for "TF300TG": https://forum.xda-developers.com/transformer-tf300t/development/rom-t3453702
ebonit said:
I'm sorry, but I also don't know where have been wrong? How should I reply after so less information about the situation. There are many different possibilities.
Hopefully you have a backup of the system through TWRP after finishing the Buster99. If so, please start the TWRP recovery and restore the backup.
Search here for "TF300TG": https://forum.xda-developers.com/transformer-tf300t/development/rom-t3453702
Click to expand...
Click to collapse
Sorry but once done the Buster99 procedure I don't need to do a restore of the Backup since the tablet restarts regularly with the original system I didn't perform any backup I didn't need it