Related
A friend of mine gave me his Prime in hopes of fixing it since I own one of my own. As far as what he told me he flashed the new Energy Rom properly and didn't like it so he did a TWRP restore to his old AndroWook 1.51 setup. This caused his Recovery to start acting quirky asking him for a password, but he could fully boot into the AndroWook no problem. But he really wanted the recovery to work to go to a different rom so he started flashing different recoveries to try and get it to work eventually leading him to the 'unsuccessful encryption' error. He hit reset now he is in a twrp loop that cannot recognize any files or even the external sd card. I hooked it up to my computer and while in twrp it is recognized by adb. I am only able to get to the bootloader screen through the adb reboot-bootloader command and it is recognized there by fastboot, but when I try to use a fastboot command the device freezes. I tried flashing recoveries and roms to no avail. I also tried the unbricking methods in that thread. Adb push does work but whenever I try to install something I get failure messages due to the tablet not being able to mount anything. I honestly think its hard bricked, am I right?
d1dd1y said:
A friend of mine gave me his Prime in hopes of fixing it since I own one of my own. As far as what he told me he flashed the new Energy Rom properly and didn't like it so he did a TWRP restore to his old AndroWook 1.51 setup. This caused his Recovery to start acting quirky asking him for a password, but he could fully boot into the AndroWook no problem. But he really wanted the recovery to work to go to a different rom so he started flashing different recoveries to try and get it to work eventually leading him to the 'unsuccessful encryption' error. He hit reset now he is in a twrp loop that cannot recognize any files or even the external sd card. I hooked it up to my computer and while in twrp it is recognized by adb. I am only able to get to the bootloader screen through the adb reboot-bootloader command and it is recognized there by fastboot, but when I try to use a fastboot command the device freezes. I tried flashing recoveries and roms to no avail. I also tried the unbricking methods in that thread. Adb push does work but whenever I try to install something I get failure messages due to the tablet not being able to mount anything. I honestly think its hard bricked, am I right?
Click to expand...
Click to collapse
Lets go thru this step at a time..
When you say he flashed the new energy rom do you mean he flashed the new tf300 port and he flashed the partitions.zip for the new bootloader?
If yes then when that flashed it installed a new TWRP also that is compatible with the new bootloader because the old TWRP was giving the password error you describe and wouldnt allow to flash anything.
Old roms are still compatible with the new bootloader so this is where it gets odd.. Restoring his Androwook rom should work just fine, also installing it from scratch should have worked fine but somehow it sounds like he also put the old TWRP back on there which isn't compatible with the new bootloader. Ask him if he had restore recovery switched on in TWRP and he restored that also or if he fastboot flashed back old TWRP.
Yes to your first question. He said the new TWRP 2.4.4.0 was working fine and he could see files and flash things via 2.4.4.0 but once he rebooted, the system would freeze on the reboot after a new install which is what made him flash to his older twrp version 2.4.0.0 which is what it is stuck on now. He flashed it via terminal emulator in androwook when it was working.
d1dd1y said:
Yes to your first question. He said the new TWRP 2.4.4.0 was working fine and he could see files and flash things via 2.4.4.0 but when he factory reset/wiped cache/dalvik then installed a rom his system would freeze on the reboot after a new install which is what made him flash to his older twrp version 2.4.0.0 which is what it is stuck on now. He flashed it via terminal emulator in androwook when it was working.
Click to expand...
Click to collapse
Right... well it was flashing the old TWRP that really messed things up. It would have been a silly little problem before.
Anyway, does he have access to nvflash files. Did he go thru the process to get his nvflash files when he was on ICS and back them up ?
If not, you say you can still get into adb. Now I know you can't push anything because the mounts are wrong in the old twrp he has flashed but did you try the recovery bootloop fix from adb?
"Make sure your Prime is in Recovery mode
Open a cmd line on your pc
Type: "adb shell"
You should see a "#" now
Once you have that "#", please type: dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1 and press [Enter]
Now type: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1 and press [Enter]
Exit the shell and reboot your Prime"
This wont fix your TWRP flashing problem but it might get you out of the TWRP loop that you are stuck in at the moment.
Report back and then we might have to see what we can do in fastboot.
Never used NVFlash, smh.
The truth eventually came out, he was trying to flash back to TWRP 2.4.4.0 via Terminal Emulator using the command:
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4 instead he typed
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p8 which put his system in this state. I did do those commands and went through the whole "Unbrick 1a and 1b" but didn't really do much as I was sent back to a TWRP that doesn;t recognize anything. I did use adb reboot-bootloader which does work and does send me to the bootloader. At the top of the bootloader screen it says:
Key Driver not found...Booting OS information about the bootloader and "Starting Fastboot USB download protocol" and I have the three options RCK, Android and Wipe Data. At this screen when I run fastboot devices I do get a hit.
Just ran those commands again, device booted back into the non functioning TWRP that is asking for a password and actually when I go to reboot the system TWRP tells me NO OS INSTALLED. When he pressed reset tablet it must have wiped his OS off the device.
d1dd1y said:
Never used NVFlash, smh.
The truth eventually came out, he was trying to flash back to TWRP 2.4.4.0 via Terminal Emulator using the command:
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4 instead he typed
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p8 which put his system in this state. I did do those commands and went through the whole "Unbrick 1a and 1b" but didn't really do much as I was sent back to a TWRP that doesn;t recognize anything. I did use adb reboot-bootloader which does work and does send me to the bootloader. At the top of the bootloader screen it says:
Key Driver not found...Booting OS information about the bootloader and "Starting Fastboot USB download protocol" and I have the three options RCK, Android and Wipe Data. At this screen when I run fastboot devices I do get a hit.
Just ran those commands again, device booted back into the non functioning TWRP that is asking for a password and actually when I go to reboot the system TWRP tells me NO OS INSTALLED. When he pressed reset tablet it must have wiped his OS off the device.
Click to expand...
Click to collapse
Not good..
Can you try something for me please.
Go to bootloader and you should automatically be in fastboot mode on new bootloader.
Bring up a shell and type
fastboot devices
and see how many are there
now extract the blob file out of the partitions.zip and place it where fastboot is and type
fastboot -i 0x0B05 flash system blob
see if you can get it to take.
I only have 1 device showing when I do fastboot devices and the Transformer is the only thing plugged into my PC. I ran that command but it seems that once I run it, the Prime freezes.The CMD prompt does give me "OKAY" for both sending and writing system. But it just looks like it freezes.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The prime is still stuck in the bootloader after i did the fastboot reboot its been about 10 minutes and not doing anything usually the green highlighter for the 3 options is pulsating but right now its not doing anything.
d1dd1y said:
I only have 1 device showing when I do fastboot devices and the Transformer is the only thing plugged into my PC. I ran that command but it seems that once I run it, the Prime freezes.The CMD prompt does give me "OKAY" for both sending and writing system. But it just looks like it freezes.
The prime is still stuck in the bootloader after i did the fastboot reboot its been about 10 minutes and not doing anything usually the green highlighter for the 3 options is pulsating but right now its not doing anything.
Click to expand...
Click to collapse
Hold power button down for 10 seconds and let it restart.
If a blue line starts to fill on restart let it complete.
No blue line straight to the 2.4.0.0 TWRP
d1dd1y said:
No blue line straight to the 2.4.0.0 TWRP
Click to expand...
Click to collapse
I'm running out of ideas without fastboot working.
Try running the same command again above but replace system with staging.
flumpster said:
I'm running out of ideas without fastboot working.
Try running the same command again above but replace system with staging.
Click to expand...
Click to collapse
Just did and received the same results. Time for him to contact ASUS and set up an RMA?
d1dd1y said:
Just did and received the same results. Time for him to contact ASUS and set up an RMA?
Click to expand...
Click to collapse
If you read the next few pages on the following link they all have a very similar problem on the tf300 forums when flashing wrong twrp
http://forum.xda-developers.com/showthread.php?t=2179874&page=5
Looks like thats where I'll be checking thanks so much for the help, I appreciate it!
First off, I don't know if this is the perfect place for this thread so I apologize in advance.
I have a HTC Evo 4G LTE and I accidentally wiped everything with TWRP. It can boot to the bootloader/fastboot menus and TWRP no problem, but I can't install anything. Maybe i'm just doing everything in the wrong order. Both the SD card and the Internal SD cards have been formatted to what they're supposed to be (caused me a bit of trouble at first). My phone is set to S-On, which is a pain in the ass, because from what I understand I can't turn it off to flash a new ROM without an OS, which I don't have. Every time I attempt to install the stock ROM for my device the phone restarts when attempting to install the kernel, included in the ROM. I borrowed my friend's identical phone, rooted it and installed TWRP, created a backup, moved the backup to my phone's ext SD card and attempted to recover off of that but my TWRP can't find any of the files, but they show up just fine with the file explorer.
I've properly srewed myself. Any advice?
windowpuncher said:
First off, I don't know if this is the perfect place for this thread so I apologize in advance.
I have a HTC Evo 4G LTE and I accidentally wiped everything with TWRP. It can boot to the bootloader/fastboot menus and TWRP no problem, but I can't install anything. Maybe i'm just doing everything in the wrong order. Both the SD card and the Internal SD cards have been formatted to what they're supposed to be (caused me a bit of trouble at first). My phone is set to S-On, which is a pain in the ass, because from what I understand I can't turn it off to flash a new ROM without an OS, which I don't have. Every time I attempt to install the stock ROM for my device the phone restarts when attempting to install the kernel, included in the ROM. I borrowed my friend's identical phone, rooted it and installed TWRP, created a backup, moved the backup to my phone's ext SD card and attempted to recover off of that but my TWRP can't find any of the files, but they show up just fine with the file explorer.
I've properly srewed myself. Any advice?
Click to expand...
Click to collapse
Since you are s-on you need to flash the rom twice.
BD619 said:
Since you are s-on you need to flash the rom twice.
Click to expand...
Click to collapse
I am new to ROM flashing, I just kind of got thrown into it, lol. Please elaborate? I'm assuming flashing is installing the rom with TWRP. I flash the rom, wipe cache/dalvik, then flash again? I'll try it then post results in a minute.
Result: Doesn't work, when it says "installing Kernel, please wait...", it stays on that message for a minute or so then the phone attempts to reboot into a nonexistant OS, effectively stopping itself so I have to restart into TWRP again with no progress made.
I think you want to let it reboot in between the two flashes. I have no idea why it makes a difference, but it does.
Sent from my EVO LTE using XDA Premium 4 mobile app
Read this:
http://forum.xda-developers.com/showthread.php?t=2443108
Some Sense ROM's include a kernel installer to help facilitate flashing while S-on. You'll need to check the ROM OP and see. Otherwise the kernel can be flashed via fastboot. For more info hit the top link in my sig.
Sent from my HTC device
fizbanrapper said:
I think you want to let it reboot in between the two flashes. I have no idea why it makes a difference, but it does.
Sent from my EVO LTE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It can't. It reboots while attempting to install the kernel then freezes because there's no OS to boot to.
Try flashing the kernel first. Extract the boot.img file from the ROM zip archive using your computer. Then, with the phone connected to the PC via USB, boot into the bootloader and go to fastboot. It should change to "fastboot USB". Then use the fastboot tool from a command prompt to verify connectivity and flash the kernel.
To verify connectivity, type fastboot devices. You should see your device's serial number of its connected properly.
To flash the kernel, type fastboot flash boot boot.img. If the boot.img file and fastboot executable are in different directories, you'll need to include the path to the file. Or just put them in the same directory.
Once you've flashed the kernel, try flashing the ROM through recovery again.
Sent from my EVO using Tapatalk
CornDogg said:
Try flashing the kernel first. Extract the boot.img file from the ROM zip archive using your computer. Then, with the phone connected to the PC via USB, boot into the bootloader and go to fastboot. It should change to "fastboot USB". Then use the fastboot tool from a command prompt to verify connectivity and flash the kernel.
To verify connectivity, type fastboot devices. You should see your device's serial number of its connected properly.
To flash the kernel, type fastboot flash boot boot.img. If the boot.img file and fastboot executable are in different directories, you'll need to include the path to the file. Or just put them in the same directory.
Once you've flashed the kernel, try flashing the ROM through recovery again.
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
Doesn't work. I can plug my phone in all I want but it will never change to fastboot usb. It stays in fastboot just fine and I can still boot TWRP, but there's no fastboot usb. I've reinstalled drivers and tried 32 bit LiveCD ubuntu. I may need to install firmware on this stupid phone.
From the main bootloader screen, you're pressing the power button on fastboot to go into fastboot, right? And from there you can never get it to go to fastboot USB?
Sent from my EVO using Tapatalk
If you're on the old partition layout have you followed my guide that I posted previously and tried to install MeanBean ROM?
Sent from my HTC device
CornDogg said:
From the main bootloader screen, you're pressing the power button on fastboot to go into fastboot, right? And from there you can never get it to go to fastboot USB?
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
Yes, that was the case.
HOWEVER, I screwed up again. I reinstalled Ubunto on my laptop and now fastboot usb works just fine.
Sometimes it hurts to live. Now I just need to find out how to flash with fastboot on ubuntu.
windowpuncher said:
Yes, that was the case.
HOWEVER, I screwed up again. I reinstalled Ubunto on my laptop and now fastboot usb works just fine.
Sometimes it hurts to live. Now I just need to find out how to flash with fastboot on ubuntu.
Click to expand...
Click to collapse
Progress.
To get the fastboot binaries on Ubuntu, you can either download and install the Android SDK and install the platform tools or go download DirtyRacun from unlimited.io. The binaries are included in the .tar archive. You may need to use the chmod command on the fastboot and adb binaries to add permissions to execute the binaries.
Once you have the binaries executable, the commands are the same, except you'll have to elevate with sudo. So, assuming you're working in the directory where you have the fastboot executable and the boot.img file, the commands would be:
sudo ./fastboot devices
sudo ./fastboot flash boot boot.img
CornDogg said:
Progress.
To get the fastboot binaries on Ubuntu, you can either download and install the Android SDK and install the platform tools or go download DirtyRacun from unlimited.io. The binaries are included in the .tar archive. You may need to use the chmod command on the fastboot and adb binaries to add permissions to execute the binaries.
Once you have the binaries executable, the commands are the same, except you'll have to elevate with sudo. So, assuming you're working in the directory where you have the fastboot executable and the boot.img file, the commands would be:
sudo ./fastboot devices
sudo ./fastboot flash boot boot.img
Click to expand...
Click to collapse
fter I
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is what happens. My phone just sits there, the screen doesn't change, but it does say Fastboot USB. I restarted my phone but it got stuck at the dev boot screen with legal warnings in red text.
Addition: Booted to recovery to flash the ROM zip, not just the boot image, still restarts when attempting to install the Kernel.
The screen on your phone won't change when flashing the kernel with fastboot. After flashing it, press the power button on Fastboot to go back to the main bootloader screen and go to recovery to get into TWRP. From there, flash the .zip of the ROM that you pulled boot.img from like you normally would from TWRP (Install, select .zip, wipe cache/data, etc).
CornDogg said:
The screen on your phone won't change when flashing the kernel with fastboot. After flashing it, press the power button on Fastboot to go back to the main bootloader screen and go to recovery to get into TWRP. From there, flash the .zip of the ROM that you pulled boot.img from like you normally would from TWRP (Install, select .zip, wipe cache/data, etc).
Click to expand...
Click to collapse
I just did this, and the phone gets stuck at the dev boot screen that says HTC with the red legal text.
Have you tried a different ROM? Maybe try CM or Viper 4G. If you go the Viper 4G route, try this one: http://forum.xda-developers.com/showthread.php?t=2124391
I think the newest Viper 4G changes the partition layout or something, so I think that would just further complicate things at the moment.
CornDogg said:
Have you tried a different ROM? Maybe try CM or Viper 4G. If you go the Viper 4G route, try this one: http://forum.xda-developers.com/showthread.php?t=2124391
I think the newest Viper 4G changes the partition layout or something, so I think that would just further complicate things at the moment.
Click to expand...
Click to collapse
Yeah, I think I'll try cyanogenmod or stock android. Thank you for the suggestion, now i'll go see if it works.
No problem. If you decide to go the CM route, deck's CM11 is pretty great.
http://forum.xda-developers.com/showthread.php?t=2518211
Good luck!
CornDogg said:
No problem. If you decide to go the CM route, deck's CM11 is pretty great.
http://forum.xda-developers.com/showthread.php?t=2518211
Good luck!
Click to expand...
Click to collapse
I went on with installing DirtyRacun (http://unlimited.io/jewel.htm) and made it to step 12. As my phone ws rebooting it once again got stuck at that HTC red text dev warning screen. So now i'm stuck again.
windowpuncher said:
I went on with installing DirtyRacun (http://unlimited.io/jewel.htm) and made it to step 12. As my phone ws rebooting it once again got stuck at that HTC red text dev warning screen. So now i'm stuck again.
Click to expand...
Click to collapse
I didn't use DirtyRacun to S-OFF (I used RumRunner), so I can't speak on this with much authority. Just to confirm I understand correctly, though, you flashed the RUU (step 9), rebooted into the bootloader (step 10), and re-did the HTC Dev Unlock (step 11). Then, as it's booting up into the ROM installed via the RUU, it gets stuck?
Were you able to get anywhere with flashing Cyanogenmod? Or did you just decide to go through the S-OFF process instead?
Will there be a TWRP version compatible with oxygen os V14 currently running on European Nord 2?
I tried previous TWRP guides for the Nord 2 but it didn't work.
Recovery OS's like TWRP works with all versions of the nord2 regardless of the update version.
More than likely you didn't follow all steps correctly. There are multiple mistakes you can make which results in the stock recovery OS being reflashed and the TWRP recovery being overwritten; I'm not completely sure of all the scenarios in which this happens, but you definitely made a miss-step somewhere.
I'm also running an EU nord variant with V14 and TWRP works fine, I've just noticed that after a few reboots TWRP partition gets overwritten by the stock OS again, in which case I just simply reflash the TWRP if i need to use it.
Zombnombs said:
Recovery OS's like TWRP works with all versions of the nord2 regardless of the update version.
More than likely you didn't follow all steps correctly. There are multiple mistakes you can make which results in the stock recovery OS being reflashed and the TWRP recovery being overwritten; I'm not completely sure of all the scenarios in which this happens, but you definitely made a miss-step somewhere.
I'm also running an EU nord variant with V14 and TWRP works fine, I've just noticed that after a few reboots TWRP partition gets overwritten by the stock OS again, in which case I just simply reflash the TWRP if i need to use it.
Click to expand...
Click to collapse
oh..ok i didn't know this. Thanls for the information
I actually followed the steps.
fastboot devices -> then flash the vbmeta -> then flash TWRP -> but then i cannot switch to the Recovery anymore.
Booting the phone works fine but i cannot access the recovery anymore and it always directly jumps me back to fastboot mode. I followed several videos and tutorials here but whatever i do what works for others seems to not work for me
Whenever i try it seems like the recovery is gone. Even stock recovery is not accessable anymore. I wonder what i did wrong or if i need to flash other files too.
Copaxy97 said:
oh..ok i didn't know this. Thanls for the information
I actually followed the steps.
fastboot devices -> then flash the vbmeta -> then flash TWRP -> but then i cannot switch to the Recovery anymore.
Booting the phone works fine but i cannot access the recovery anymore and it always directly jumps me back to fastboot mode. I followed several videos and tutorials here but whatever i do what works for others seems to not work for me
Whenever i try it seems like the recovery is gone. Even stock recovery is not accessable anymore. I wonder what i did wrong or if i need to flash other files too.
Click to expand...
Click to collapse
Assuming you've already unlocked bootloader and have all the mediatek drivers and ADB tools installed on your computer; Simply retry flashing vbmeta with the disable verity flag, then reflash twrp, and then reboot into recovery.
Make sure you've got a copy of the vbmeta.img and TWRP.img downloaded and place them in your ADB platform tools folder. Then run these commands
Make sure you shift-right click (for windows) on empty space in your platform tools folder and open powershel or command prompt (this is important), then send the following commands
Code:
fastboot devices
and wait for a response from your device to ensure it's connected
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
then
Code:
fastboot flash recovery [YourTWRPfileName]
eg my twrp file name is TWRPopn2.img so i type "fastboot flash recovery twrpopn2.img"
then
Code:
fastboot reboot recovery
Make sure your ADB terminal and phone both say the flash was succesful after each flash. If not, then you likely didn't flash the partition at all.
My guess is likely that you shift-right clicked to open the powershell window in the wrong folder, such as your desktop, in which case sending the flash commands cann't find the right file to flash? Just a theory. Definitely sounds like your recovery partition got wiped though. You could also try redownloading TWRP to make sure you're using the right version of it.
Zombnombs said:
Assuming you've already unlocked bootloader and have all the mediatek drivers and ADB tools installed on your computer; Simply retry flashing vbmeta with the disable verity flag, then reflash twrp, and then reboot into recovery.
Make sure you've got a copy of the vbmeta.img and TWRP.img downloaded and place them in your ADB platform tools folder. Then run these commands
Make sure you shift-right click (for windows) on empty space in your platform tools folder and open powershel or command prompt (this is important), then send the following commands
Code:
fastboot devices
and wait for a response from your device to ensure it's connected
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
then
Code:
fastboot flash recovery [YourTWRPfileName]
eg my twrp file name is TWRPopn2.img so i type "fastboot flash recovery twrpopn2.img"
then
Code:
fastboot reboot recovery
Make sure your ADB terminal and phone both say the flash was succesful after each flash. If not, then you likely didn't flash the partition at all.
My guess is likely that you shift-right clicked to open the powershell window in the wrong folder, such as your desktop, in which case sending the flash commands cann't find the right file to flash? Just a theory. Definitely sounds like your recovery partition got wiped though. You could also try redownloading TWRP to make sure you're using the right version of it.
Click to expand...
Click to collapse
Thanks for your help. I will try that again later.
What i can say i 100% opened the command prompt in the correct folder and the flash always said succesful.
I also thought about the command promt folder error before but it is correct. At least somehting got wiped (my recovery) but i simply cannot access it.
I will try again later and go over each step step by step and share ym results here. I hope i did a mistake because otherwise i don't know how to locate the problem.
Okey i did it again like the tutorial and also a second time like you said but it sadly didn't work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is my output from the command line. i use minimal ADB and fasstboot. But normal powershell by shift right click gives me the same output.
But when i try to reboot and boot into the recovery it just jumps to fastboot mode. So the stock recovery got flashed or removed then. But why i cannot boot into twrp?
Bootloader unlocked and based on the messages in the cmd everything fine.
Any ideas?
***Edit***
It worked now. If you ask me why, i don't know.
I did exactly the same in minimal adb and fastboot tools and on powershell. Both didn't work.
I did it in total 5 times and the last one in powershell randomly was succesful lol.
weird...
looks like the issue is more likely to do with your method of rebooting into recovery, as your reboot command did not seem to work.
Could be an issue with MinimalADB, or many other factors. If you're using the power button and volume keys combination, make sure you do it with your phone unplugged, as with the phone plugged in the combination boots to fastboot instead of recovery.
Zombnombs said:
looks like the issue is more likely to do with your method of rebooting into recovery, as your reboot command did not seem to work.
Could be an issue with MinimalADB, or many other factors. If you're using the power button and volume keys combination, make sure you do it with your phone unplugged, as with the phone plugged in the combination boots to fastboot instead of recovery.
Click to expand...
Click to collapse
Yeah might be true. I don't know.
I was trying to use twrp in my device to install a custom ROM, but when after flashing it i cant boot into it, i used sp flash tool and it does not recognise my device.
when booting through cmd i get this error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
this is the error that i get, i have unlocked bootloader
this might be useful to you guys i guess:
so please help me guys.
keep holding Volume Up while rebooting. do not release until you successfully entered TWRP recovery
Code:
fastboot flash recovery TWRP_lenovotb_7304f-030818.img
fastboot reboot
https://forum.xda-developers.com/t/...l-tb-7304f-hard-bricked.3934944/post-81607437
aIecxs said:
keep holding Volume Up while rebooting. do not release until you successfully entered TWRP recovery
Code:
fastboot flash recovery TWRP_lenovotb_7304f-030818.img
fastboot reboot
https://forum.xda-developers.com/t/...l-tb-7304f-hard-bricked.3934944/post-81607437
Click to expand...
Click to collapse
it doesnt works, held volume up just after i typed the command and brought me back to boot modes. there are 3 modes there: recovery mode, fastboot mode and normal mode.
selecting recovery mode would just show a android robot saying no command.
recovery mode is the right option. the no command screen is half way to stock recovery, flash twrp again. on the no command screen, press Power + Volume Up again to continue into recovery
aIecxs said:
the no command screen is stock recovery, flash twrp again
Click to expand...
Click to collapse
so i keep flashing until it happens?
aIecxs said:
the no command screen is stock recovery, flash twrp again
Click to expand...
Click to collapse
but it doesnt even boot into recovery now just boots into normal mode when selecting recovery mode. (only when connected to pc) but when removed from pc it boots into recovery mode and doesnt connect back to pc so fastboot command shows waiting for device.
What does the "no command" screen mean? (Trying to execute hard reset Recovery)
"The No Command screen means recovery checked the normal area (/cache) for an update file, like an OTA, and it didn't find one, so it had 'No Command' to execute. Androids stock recovery is intended for the normal, everyday user, giving them a menu they could easily access could cause lots of potentially angry people who are just playing around and reset their device by accident. Stock recovery, and its menu, are specifically engineered so that you have to take special steps to do anything. The No Command screen, meaning no automated script, is part of that safe guard."
source @acejavelin
aIecxs said:
What does the "no command" screen mean? (Trying to execute hard reset Recovery)
"The No Command screen means recovery checked the normal area (/cache) for an update file, like an OTA, and it didn't find one, so it had 'No Command' to execute. Androids stock recovery is intended for the normal, everyday user, giving them a menu they could easily access could cause lots of potentially angry people who are just playing around and reset their device by accident. Stock recovery, and its menu, are specifically engineered so that you have to take special steps to do anything. The No Command screen, meaning no automated script, is part of that safe guard."
source @acejavelin
Click to expand...
Click to collapse
ok, now i understood about the recovery menu, so to access the twrp recovery i would need to delete stock recovery i guess, but it would in turn brick my device so that just means i cant root my device, still going into root checker it says root availability is yes but it is hard to do it. so now im stuck on a roadblock...
no need to delete stock recovery, it's opposite. you're just not booting straight into recovery right after flashing, so twrp recovery got deleted:
aIecxs said:
(if you accidentially boot into android, twrp is gone, reflash and try again)
Click to expand...
Click to collapse
actually there are three different methods to root that device (I have linked) it's even possible on locked bootloader
your bootloader is unlocked already, so using fastboot is safest and most straightforward method
aIecxs said:
no need to delete stock recovery, it's opposite. you're just not booting straight into recovery right after flashing, so twrp recovery got deleted:
actually there are three different methods to root that device (I have linked) it's even possible on locked bootloader
your bootloader is unlocked already, so using fastboot is safest and most straightforward method
Click to expand...
Click to collapse
THERE ARE 3 METHODS!!!?? so ill just do the thing and see what happens.
VoxPlays08 said:
so ill just do the thing and see what happens.
Click to expand...
Click to collapse
This is exactly how people brick their devices. You must not do anything without understanding what you're doing...
why not just repeat post #2
aIecxs said:
This is exactly how people brick their devices. You must not do anything without understanding what you're doing...
why not just repeat post #2
Click to expand...
Click to collapse
Ok I'll reply if anything happens
maybe repeat download and make sure checksum matches?
Code:
certutil.exe -hashfile TWRP_lenovotb_7304f-030818.img MD5
bcb6aa10333edd89054f3bddca7abbdc
aIecxs said:
maybe repeat download and make sure checksum matches?
Code:
certutil.exe -hashfile TWRP_lenovotb_7304f-030818.img MD5
bcb6aa10333edd89054f3bddca7abbdc
Click to expand...
Click to collapse
checksum matches exactly
so flash it from fastboot and keep holding Volume Up while rebooting, select recovery mode
Im at the exact same spot, I can do the "fastboot flash recovery" but when rebooting, no matter what I press (when reboot) it always go to fastboot or normal boot..
the fastboot says its flashed ok in recovery, but I guess its overwritten when booting..
Stuck here..
If I choose recovery in fastboot using the Lenovo recovery and from there trying to flash with adb and 18.1 it erros out after 40% isch
I can use it but.. old.. and work wifi blocks me cuzzits old.
Hi, here I bring you a procedure for rooting your device using Magisk and Adb. I guess there is no need to say the risks involved in doing this.
First you'll need:
1. Having installed ADB on your pc, you can use this link: https://www.xda-developers.com/install-adb-windows-macos-linux/
2. Your device must have bootlader unlocked, here the process to do so: https://c.realme.com/in/post-details/1526491339024314368
3. The corresponding boot.img (In this thread you can find attached the file for RMX3301_11 global variant) or you can extracted by yourself from the ofp file using htis script https://github.com/bkerler/oppo_decrypt
Note: During the process I encountered that fastboot commands didn't seem to work, getting the message <<waiting for device>> when unloocking bootloader on windows 11.
This problem was caused due to the lack of proper drivers, if you face this problem there is a file with the needed drivers attached in this post as well.
Now rooting process:
1. You need to install the latest stable release of Magisk on your device, which you can find here: https://github.com/topjohnwu/Magisk
2. Copy the boot image to your device
3. Press the Install button in the Magisk card
4. Choose “Select and Patch a File” in method, and select the boot image, then connect your device via usb to your PC
5. Copy the patched image to your PC, move the file inside your platform-tools folder and rename it to patchedboot.img
6. Make sure usb debugging is turned on under developer options and give permission to your PC on your cellphone after typing the command adb devices on your ADB terminal
7. Type the command adb reboot bootloader
8. Once your device is on bootloader type de command fastboot devices to make sure your device is "attached".
9. Now type fastboot flash boot patchedboot.img
10. Reboot and open the Magisk app on your phone to check everything is ok.
Aditional stuff you might find useful:
Here you can find the Universal Safetynetfix module, which is working properly: https://github.com/blog2i2j/kdrag0n.._..safetynet-fix
You just need to flash it via magisk, reboot, turn on Zygysk and reboot again.
it is not work unlock app my phone
GT2 Pro RMX3301_11_A.16
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
arzuakay said:
it is not work unlock app my phone
GT2 Pro RMX3301_11_A.16
View attachment 5651113
Click to expand...
Click to collapse
[EU model] Unlock bootloader of European model
As you may know, at the time of writing it's not possible to unlock the bootloader of the European model. Fortunately there's a workaround. To know how it works, scroll to the end of the post. First of all, this is only for the European RMX3301...
forum.xda-developers.com
Where is the guide?
Please stop saying there is root or even bootloader unlock for the global variant. India is not "GLOBAL" aka the world, although you might like it to be.
Lol, I UBL EU Global phone with guide here on xda
Device doesn't boot anymore after flashing patchedboot.img
Ty
where is the boot.img for glabal RMX3301_11_C.13 android 13
Extract from Full OTA package.
It appears that Magisk 26.1 isnt able to root the GT2 Pro. I have flashed the patched boot image twice. First time it stuck around til I installed a module and restarted. Second time didnt even get root. I will try a third time with a canary version of Magisk.
Edit: Canary doesnt work either. Device keeps rebooting to bootloader. Flashed stock boot for now. Will try older version of magisk.
Edit2: Magisk 25.2 doesnt work either. All 3 versions flashed it just fine but device keeps reboot back to bootloader. Both slots too. Flashed back to stock boot.
I am on Indian version of Color Os 13.1 (C.19) so I assume India is not considered global. I will go flash a global rom I guess.
Magisk should work, drivers ok?
Stano36 said:
Magisk should work, drivers ok?
Click to expand...
Click to collapse
Flashes just fine as far as I can tell according to CMD (admin) but right after flashing, on reboot, it goes directly back to the bootloader (or switches to the other working slot). I just flashed the EUEX C.19 update using the OnePlus updater app and same thing.
Its weird because when I type "fastboot boot patchedboot.img" just to check if the patched boot image works, it boots fine with root working. But flashing using "fastboot flash boot patchedboot.com" goes into that "bricked" or "bootloop" status, whatever its called.
morphius88 said:
Flashes just fine as far as I can tell according to CMD (admin) but right after flashing, on reboot, it goes directly back to the bootloader (or switches to the other working slot). I just flashed the EUEX C.19 update using the OnePlus updater app and same thing.
Its weird because when I type "fastboot boot patchedboot.img" just to check if the patched boot image works, it boots fine with root working. But flashing using "fastboot flash boot patchedboot.com" goes into that "bricked" or "bootloop" status, whatever its called.
Click to expand...
Click to collapse
adb reboot bootloader
fastboot devices (identified)
fastboot flash boot patchedboot.img
fastboot reboot
Stano36 said:
adb reboot bootloader
fastboot devices (identified)
fastboot flash boot patchedboot.img
fastboot reboot
Click to expand...
Click to collapse
Thats pretty much exactly what I do. See screenshot attached from my last attempt using stable Magisk 26.1 patched boot image. The reboot goes back to bootloader.
morphius88 said:
Thats pretty much exactly what I do. See screenshot attached from my last attempt using stable Magisk 26.1 patched boot image. The reboot goes back to bootloader.
Click to expand...
Click to collapse
Use this command before flashing the patched boot.img and try again
fastboot set_active a
Click to expand...
Click to collapse
NumberOneDz said:
Use this command before flashing the patched boot.img and try again
Click to expand...
Click to collapse
I've tried that too, it does the same result in either slot.
The funny thing is, using "flash boot patchedboot.img" works fine but that is obviously temporary so I dont understand why it doesnt want to stick if the temporary rooted boot works fine.
Edit: see screenshot, I ran fastboot getvar all after flashing patched boot to both slots. I will flash stock boot to get back to a workable phone for now.
morphius88 said:
It appears that Magisk 26.1 isnt able to root the GT2 Pro. I have flashed the patched boot image twice. First time it stuck around til I installed a module and restarted. Second time didnt even get root. I will try a third time with a canary version of Magisk.
Edit: Canary doesnt work either. Device keeps rebooting to bootloader. Flashed stock boot for now. Will try older version of magisk.
Edit2: Magisk 25.2 doesnt work either. All 3 versions flashed it just fine but device keeps reboot back to bootloader. Both slots too. Flashed back to stock boot.
I am on Indian version of Color Os 13.1 (C.19) so I assume India is not considered global. I will go flash a global rom I guess.
Click to expand...
Click to collapse
You need to flash vbmeta with disabled verification:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Rapper_skull said:
You need to flash vbmeta with disabled verification:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Thank you for this. I think this did it. First time I had to disable verity on any phone to get root as far as I know.
I now have root and pass Safety Net.
@vanya.ag you might need to put that in your original post in case there are others that run into the same situation.