Database Info

[Q] Nexus S w/ CM 7.1.0 (no load & no recovery)

Can anyone help me with this Ive got a Nexus S, with the latest stable vers. of Cyanogen (update-cm-7.1.0-NS-signed) and ClockworkMod as the recovery image. Was working great then all of a sudden the phone will not load past the "Google" unlocked padlock image OR go into recovery mode. I can get into the bootloader alright (vol+ key & power button) and it confirms that the phone's still "UNLOCKED". All I get, on the screen, when I try to get into ClockworkMod is "Google" and the unlocked padlock image.
Can't even get into the SD card when I hook the phone up to my PC. Tried flashing CWM says that its sent and written but still wont load.
Any ideas how I can at least get into recovery mode? Once i'm in, in theory (if there's nothing terminal, hardware-wise) I can wipe the phone, mount the sd card, put a fresh vers. of CyanogenMod on it and start again.

Wrong section.

Soooooo moved.
Obligatory YOU MORON BLAH BLAH RABBLE RABBLE!!!!
....
Seriously though, what version of the Nexus S do you have? Just want to rule out any ID10T erros first. Second what CMW did you flash via fastboot? Thridly what was your fastboot command?

ackte11 said:
Can anyone help me with this Ive got a Nexus S, with the latest stable vers. of Cyanogen (update-cm-7.1.0-NS-signed) and ClockworkMod as the recovery image. Was working great then all of a sudden the phone will not load past the "Google" unlocked padlock image OR go into recovery mode. I can get into the bootloader alright (vol+ key & power button) and it confirms that the phone's still "UNLOCKED". All I get, on the screen, when I try to get into ClockworkMod is "Google" and the unlocked padlock image.
Can't even get into the SD card when I hook the phone up to my PC. Tried flashing CWM says that its sent and written but still wont load.
Any ideas how I can at least get into recovery mode? Once i'm in, in theory (if there's nothing terminal, hardware-wise) I can wipe the phone, mount the sd card, put a fresh vers. of CyanogenMod on it and start again.
Click to expand...
Click to collapse
How did you root it?
You just need to use fastboot to flash CWM & a new rom
Example for the rom:
fastboot update ROMFILENAME.ZIP -w
For more info on fastboot
http://wiki.cyanogenmod.com/wiki/Fastboot
Edit: There, got you the Cyanogenmod page. It's a step by step guide. Skip the bootloader unlocking section. Do all the rest.
http://wiki.cyanogenmod.com/wiki/Nexus_S:_Full_Update_Guide

slimdizzy said:
Soooooo moved.
Obligatory YOU MORON BLAH BLAH RABBLE RABBLE!!!!
....
Seriously though, what version of the Nexus S do you have? Just want to rule out any ID10T erros first. Second what CMW did you flash via fastboot? Thridly what was your fastboot command?
Click to expand...
Click to collapse
sorry bout posting in the wrong section. But Ive got the GT-I9020 version, Second I tried to flash versions 3.0.2.4-crespo, 4.0.0.2-crespo, and 5.0.2.0. Nothing responded.
$ fastboot flash recovery recovery-clockwork-4.0.0.2-crespo.img

ackte11 said:
sorry bout posting in the wrong section. But Ive got the GT-I9020 version, Second I tried to flash versions 3.0.2.4-crespo, 4.0.0.2-crespo, and 5.0.2.0. Nothing responded.
$ fastboot flash recovery recovery-clockwork-4.0.0.2-crespo.img
Click to expand...
Click to collapse
Do you have a working adb setup on your computer?
Put your device in fastboot mode ( VOL up + power button)
Make sure it's properly connected and interfacing with adb (you can type "adb devices" and you should see your device in the list)
If you don't see any string of characters after typing adb devices, then you don't have a working adb setup. You need either a standalone adb or the android SDK.

polobunny said:
How did you root it?
You just need to use fastboot to flash CWM & a new rom
Example for the rom:
fastboot update ROMFILENAME.ZIP -w
For more info on fastboot
---wiki.cyanogenmod.com/wiki/Fastboot
Edit: There, got you the Cyanogenmod page. It's a step by step guide. Skip the bootloader unlocking section. Do all the rest ---.cyanogenmod.com/wiki/Nexus_S:_Full_Update_Guide
Click to expand...
Click to collapse
tried that and got these results
$ fastboot update update-cm-7.1.0-NS-signed.zip -w
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt

I have the android sdk but after "adb devices" its saying command not found

ackte11 said:
I have the android sdk but after "adb devices" its saying command not found
Click to expand...
Click to collapse
on a mac? also what about "fastboot devices"?

Linux Ubuntu 11.04 and Windows 7 "fastboot devices" recognizes it and shows the serial number. adb on windows runs the command but just comes up blank

ackte11 said:
Linux Ubuntu 11.04 and Windows 7 "fastboot devices" recognizes it and shows the serial number. adb on windows runs the command but just comes up blank
Click to expand...
Click to collapse
Alright. Try to flash CWM recovery first, as stated in the Cyanogenmod guide. Then once that's done, boot back into CWM and flash CM7.

Did that and it says that everything goes through, move down to recovery and it just loops the "google" padlock screen

ackte11 said:
Did that and it says that everything goes through, move down to recovery and it just loops the "google" padlock screen
Click to expand...
Click to collapse
Ah okay, maybe a corrupted boot.img
Download the full 2.3.6 rom for your model
i9020a
i9020t/i9023
You can get the model in fastboot mode at the top if you're unsure of which you own.
Extract the ZIP contents and grab hold of boot.img. Flash this boot.img using fastboot
Example: fastboot flash boot boot.img
Once that is done, reboot to fastboot and flash CWM. Then from CWM flash superuser and whichever ROM you want.

polobunny said:
Ah okay, maybe a corrupted boot.img
Download the full 2.3.6 rom for your model
i9020a
i9020t/i9023
You can get the model in fastboot mode at the top if you're unsure of which you own.
Extract the ZIP contents and grab hold of boot.img. Flash this boot.img using fastboot
Example: fastboot flash boot boot.img
Once that is done, reboot to fastboot and flash CWM. Then from CWM flash superuser and whichever ROM you want.
Click to expand...
Click to collapse
Nothings working. flashed the boot then CWM still cant get into recovery. Just right back to the "google" page

I am not sure if this works on the nexus s but give it a try.
Instead of flashing the recovery try and boot it. Change the command to fastboot boot recovery .....instead of flash.

albundy2010 said:
I am not sure if this works on the nexus s but give it a try.
Instead of flashing the recovery try and boot it. Change the command to fastboot boot recovery .....instead of flash.
Click to expand...
Click to collapse
still no go.

i am having the exact same problem, my computer can see my phone, but nothing is working. anyone have any input??? it seems like i can not write to certain parts of the sd card, it says, FAILED (remote: Write Fail)
trying to run an update. see how the image says it was copied over correctly? ive also tried ereasing it as well..
{
"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"
}
No boot or recovery img

This post specifically helped me.
http://forum.xda-developers.com/showpost.php?p=19531979&postcount=30
just rename the file "install-recovery.sh" which is in the /etc folder. You can only access it with a root file manager (rootexplorer $4 on the market)
make sure your new file is not ending with .sh
It appears that this file keeps writing stock recovery to your phone. Once you erase it, flash CWM recovery and then flash your rom. Hope it helps.

Nice catch. Didn't even think about it getting rewritten every boot.
Sent from my Nexus S using xda premium

Stuck Rooting @ tf300t

hi guys,
i was following this thread guide http://forum.xda-developers.com/showthread.php?t=1668173
and while i'm on step 5, i accidentally pick the wipe data (available options are RCK, Android and Wipe Data)
now, i am stuck in this
{
"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"
}
and totally unable to mount sdcard, emmc. Hopefully my tablet hasn't bricked yet.

johnson234 said:
hi guys,
i was following this thread guide http://forum.xda-developers.com/showthread.php?t=1668173
and while i'm on step 5, i accidentally pick the wipe data (available options are RCK, Android and Wipe Data)
now, i am stuck in this View attachment 2454401 and totally unable to mount sdcard, emmc. Hopefully my tablet hasn't bricked yet.
Click to expand...
Click to collapse
I remember on the old bootloader that ended in and insta-brick, but idk which BL you are on.

cmendonc2 said:
I remember on the old bootloader that ended in and insta-brick, but idk which BL you are on.
Click to expand...
Click to collapse
By BL u mean bootloader? My stock bootloader is 4.2.1 Jelly Bean. I tried to dl the twrp.blob from the twrp website with -4.2 and try to use the terminal emulator thingy but it still boot into CWM based Recovery.
However, I just bought the ROM Toolbox Pro in Google Play and use the 'Flash Recovery' but it search my whole tablet and returns nothing while i have already copy and paste the twrp.blob into the/sdcard/

johnson234 said:
By BL u mean bootloader? My stock bootloader is 4.2.1 Jelly Bean. I tried to dl the twrp.blob from the twrp website with -4.2 and try to use the terminal emulator thingy but it still boot into CWM based Recovery.
However, I just bought the ROM Toolbox Pro in Google Play and use the 'Flash Recovery' but it search my whole tablet and returns nothing while i have already copy and paste the twrp.blob into the/sdcard/
Click to expand...
Click to collapse
Edit: I am a first timer a.k.a. newbie. Sorry for that if i don't understand the short form/ slang u used.

johnson234 said:
By BL u mean bootloader? My stock bootloader is 4.2.1 Jelly Bean. I tried to dl the twrp.blob from the twrp website with -4.2 and try to use the terminal emulator thingy but it still boot into CWM based Recovery.
However, I just bought the ROM Toolbox Pro in Google Play and use the 'Flash Recovery' but it search my whole tablet and returns nothing while i have already copy and paste the twrp.blob into the/sdcard/
Click to expand...
Click to collapse
Wait it boots into android? What exactly are you trying to do? Just install the Superuser binaries for root or get a custom ROM?

cmendonc2 said:
Wait it boots into android? What exactly are you trying to do? Just install the Superuser binaries for root or get a custom ROM?
Click to expand...
Click to collapse
I plan to root it into a custom rom but ended up installing cwm which I later found out to be incompatible with my device. This is because I thought that everyone need to undergo these three process (root>install recovery>install rom) now I'm trying to remove or replace this cwm with a twrp then I can start installing my custom rom. I have already root my tablet with supersu (kingo). Did I do anything wrong on my steps above? If yes, please enlighten me. Thanks
anyway, what's a super user binary?

johnson234 said:
I plan to root it into a custom rom but ended up installing cwm which I later found out to be incompatible with my device. This is because I thought that everyone need to undergo these three process (root>install recovery>install rom) now I'm trying to remove or replace this cwm with a twrp then I can start installing my custom rom. I have already root my tablet with supersu (kingo). Did I do anything wrong on my steps above? If yes, please enlighten me. Thanks
anyway, what's a super user binary?
Click to expand...
Click to collapse
OK download the -42 TWRP recovery for jellybean onto your computer. Use fastboot (http://forum.xda-developers.com/showthread.php?p=42407269) to flash the bootloader to your tablet with:
Code:
fastboot flash recovery TWRP.img -i 0x0b05
Then reboot into Android and reboot again into TWRP to flash a custom ROM.

cmendonc2 said:
OK download the -42 TWRP recovery for jellybean onto your computer. Use fastboot (http://forum.xda-developers.com/showthread.php?p=42407269) to flash the bootloader to your tablet with:
Code:
fastboot flash recovery TWRP.img -i 0x0b05
Then reboot into Android and reboot again into TWRP to flash a custom ROM.
Click to expand...
Click to collapse
Sorry to tell you but everytime i try to fastboot, (tried this even before posting the problem here) i get this error. Waiting for like 10mins, the 'waiting for device' message is still there.
Command I used,
fastboot flash recovery TWRP.img -i 0x0b05
Click to expand...
Click to collapse
After pressing enter, i get this
< waiting for device >
Click to expand...
Click to collapse
Edit; sorry for the screenshot, typed the command wrong but tried it with the correct 1 but the outcome still the same.

I'm thinking that is it usb drivers problem? currently running on Win8 Professional 64bit.

johnson234 said:
I'm thinking that is it usb drivers problem? currently running on Win8 Professional 64bit.
Click to expand...
Click to collapse
Fastboot utility is very sensitive to connection type. It can refuse to work on some laptops and usb ports on front pannel of desktop PC. Also do not use usb hub or tablet dock with fastboot. And if Windows device manager shows tablet as something like "asus bootloader interface" or "asus fastboot interface" (don't remember exact name) is probably shouldn't be a driver issue.

Graiden05 said:
Fastboot utility is very sensitive to connection type. It can refuse to work on some laptops and usb ports on front pannel of desktop PC. Also do not use usb hub or tablet dock with fastboot. And if Windows device manager shows tablet as something like "asus bootloader interface" or "asus fastboot interface" (don't remember exact name) is probably shouldn't be a driver issue.
Click to expand...
Click to collapse
It has these 2 (see attachment) and I even can use ASUS SYNC perfectly. So i guess the usb driver wont be a problem?

johnson234 said:
It has these 2 (see attachment) and I even can use ASUS SYNC perfectly. So i guess the usb driver wont be a problem?
View attachment 2457522
Click to expand...
Click to collapse
Did You know that to use fastboot tablet should be loaded in fastboot mode? If You connect it in fastboot mode and Windows shows no recognised fastboot or bootloader interface You need a proper driver.

So, you suggest that i need to use a different pc to do the fastboot thing? What are the drivers do i need to install? Where can i download it? Maybe my wind8 64bit professional got some flaw/bug. Thanks for helping. Will try it out when i get back home.

cmendonc2 said:
OK download the -42 TWRP recovery for jellybean onto your computer. Use fastboot (http://forum.xda-developers.com/showthread.php?p=42407269) to flash the bootloader to your tablet with:
Code:
fastboot flash recovery TWRP.img -i 0x0b05
Then reboot into Android and reboot again into TWRP to flash a custom ROM.
Click to expand...
Click to collapse
I get something like this. But when i reboot into android and reboot it, i still get boot into CWM recovery. Nothing changed

Update : I try flashing the TWRP recovery again, but now its freezing on the fastboot mode. Probably still installing. Hopefully everything went well and i can successfully install it.

Graiden05 said:
Did You know that to use fastboot tablet should be loaded in fastboot mode? If You connect it in fastboot mode and Windows shows no recognised fastboot or bootloader interface You need a proper driver.
Click to expand...
Click to collapse
After i run this command
fastboot -i 0x0b05 flash recovery TWRP.img
Click to expand...
Click to collapse
it freeze.(I have waiting for 30mins but still nothing significant comes up.)
There is three option to choose from (RCK, Android and WipeData)
Now under the "Device and Printer", there is a fastboot devices (unspecified). But when i see it in properties of this fastboot device, it's manufacturer is still under ClockworkMod. See attachment

Try this guide.

Install custom recovery and root on Cubot J5?

I have tried for a few days to install a custom recovery but no luck. Perhaps someone can give me some advice?
I have tried Mediatek (MTK) Auto TWRP recovery porter, version 1.5 but it didn´t work.
This aswell twrp-recovery-cubot-j5-root from getdroidtips but nope...
Chip on phone Mtk6580 and android 9.
Updated to the latest firmware release via spflashtool from cubot own site.
I guess that im to much of a newbie to get this done...
But atleast its updated, my main goal is to root the phone so thats why i need a custom recovery.
Thx in advance, and sorry for my english grammar, not my main language. :laugh:

jimboo80 said:
I have tried for a few days to install a custom recovery but no luck. Perhaps someone can give me some advice?
I have tried Mediatek (MTK) Auto TWRP recovery porter, version 1.5 but it didn´t work.
This aswell twrp-recovery-cubot-j5-root from getdroidtips but nope...
Chip on phone Mtk6580 and android 9.
Updated to the latest firmware release via spflashtool from cubot own site.
I guess that im to much of a newbie to get this done...
But atleast its updated, my main goal is to root the phone so thats why i need a custom recovery.
Thx in advance, and sorry for my english grammar, not my main language. :laugh:
Click to expand...
Click to collapse
My dear friend did you try:
https://www.cyanogenmods.org/how-to-root-cubot-j5-and-install-twrp-recovery/
btw why didn't Mediatek Auto TWRP recovery porter work? what was the issue?

I have the same problem the thread starter indicates in the title: I can install the TWRP recovery image that gopikrishnanrmg linked, but the installation of Magisk doesn't work. It says it installs successfully, but I can't get root rights and if I install the Magisk app, it says that Magisk is not installed. Magisk canary doesn't work either. Does someone have an idea what I might have done wrong? Or does that mean that the device is not supported by Magisk?

gopikrishnanrmg said:
My dear friend did you try:
btw why didn't Mediatek Auto TWRP recovery porter work? what was the issue?
Click to expand...
Click to collapse
Sorry for the late answer, life happens
I get it installed with that guide after unlocking flash state, but when it reboots it give me a message "orange state" and the phone resets.
and the recovery porter did not work for me, maybe i´m to old for this hehe was a while since i rooted a device, and i´m defenitly no hacker
btw if you need to look on the firmware cubot(dot)net has a downloadable link for the j5.

I have the same problem and I can't do anything about it, maybe some specific source or a hint in the form of YT

Has anyone figured out how to upload Twrp recovery to Cubot J5 ????

I was able to root Cubot J5.
CUBOT_J5_9061C_V14_20200506
Magisk 23.0(23000)
Cubot J5 is "Ramdisk No".
Must be booted in recovery mode.
Magisk in Recovery
Installation
The Magic Mask for Android
topjohnwu.github.io
Steps
1. Patch your boot.img and recovery.img with magisk
Img file can be downloaded
CUBOT FILE DOWNLOAD
Cubot Offical Website for Smartphones and Wearables. Simple and Trust, Cubot aims to be a credit worthy high-tech corporation in the world.
www.cubot.net
2.Edit the boot.img file with a hex editor.
Change 「736B69705F696E697472616D6673」 to 「77616E745F696E697472616D6673」
3.flashing the boot.img recovery.img and vbmeta.img .
vbmeta.img file can be downloaded
331 Cubot J5
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
fastboot flash boot magisk_patched-23000_boot_binay_edit.img
fastboot flash boot magisk_patched-23000_boot.img
fastboot flash recovery magisk_patched-23000_recovery.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
4.Must be booted in recovery mode to enter root state.
adb reboot recovery
or
Press and hold the Power key and the Volume UP key when booting.

たろう said:
I was able to root Cubot J5.
CUBOT_J5_9061C_V14_20200506
Magisk 23.0(23000)
Cubot J5 is "Ramdisk No".
Must be booted in recovery mode.
Magisk in Recovery
Installation
The Magic Mask for Android
topjohnwu.github.io
Steps
1. Patch your boot.img and recovery.img with magisk
Img file can be downloaded
CUBOT FILE DOWNLOAD
Cubot Offical Website for Smartphones and Wearables. Simple and Trust, Cubot aims to be a credit worthy high-tech corporation in the world.
www.cubot.net
2.Edit the boot.img file with a hex editor.
Change 「736B69705F696E697472616D6673」 to 「77616E745F696E697472616D6673」
3.flashing the boot.img recovery.img and vbmeta.img .
vbmeta.img file can be downloaded
331 Cubot J5
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
fastboot flash boot magisk_patched-23000_boot_binay_edit.img
fastboot flash recovery magisk_patched-23000_recovery.im
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
4.Must be booted in recovery mode to enter root state.
adb reboot recovery
or
Press and hold the Power key and the Volume UP key when booting.
Click to expand...
Click to collapse
I tried flashing your files but unfortunately got a bootloop again . I was on the same stock software, unlocked bootloader and tried to flash as you described.

weeman45 said:
I tried flashing your files but unfortunately got a bootloop again . I was on the same stock software, unlocked bootloader and tried to flash as you described.
Click to expand...
Click to collapse
Cause of bootloop.
1. vbmeta.img is not flushed.
2. The firmware version is different.
The version of this file is "CUBOT_J5_9061C_V14_20200506".
{
"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"
}

たろう said:
Cause of bootloop.
1. vbmeta.img is not flushed.
2. The firmware version is different.
The version of this file is "CUBOT_J5_9061C_V14_20200506".
Click to expand...
Click to collapse
Thanks for your reply! When i woke up today i thought i can just as well restore the stock rom but found the phone booting.
The boot was just taking way longer because of the factory reset (through oem unlock).
I just installed the root checker and it is working fine!
After years of having this phone and trying to root it you just saved it. Thank you!
Do you have plans to install GSI images on it as well?
*update* i'm able to boot a lineageos 18.1 GSI with your images. I flashed the system and afterwards your boot, recovery and vbmeta and it worked.
*update2* I wanted gApps so i tried the lineageos 19.1 image which was too big. After that i tried an AOSP one with lite gApps.
I think i messed up badly. I can't get back into fastboot and not even the spflash tool is able to flash something. When pressing Volume down+power it briefly detects it but won't write the firmware. I'll try different versions later and report back but for now it's dead
*uodate3* It's back again. I had to re-install the mediatek drivers for the tool to work. After a stock boot i was able to unlock the bootloader and install LOS again. I will go for an image with gapps next.
Thank you again for providing your images and support!

weeman45 said:
Thanks for your reply! When i woke up today i thought i can just as well restore the stock rom but found the phone booting.
The boot was just taking way longer because of the factory reset (through oem unlock).
I just installed the root checker and it is working fine!
After years of having this phone and trying to root it you just saved it. Thank you!
Do you have plans to install GSI images on it as well?
*update* i'm able to boot a lineageos 18.1 GSI with your images. I flashed the system and afterwards your boot, recovery and vbmeta and it worked.
*update2* I wanted gApps so i tried the lineageos 19.1 image which was too big. After that i tried an AOSP one with lite gApps.
I think i messed up badly. I can't get back into fastboot and not even the spflash tool is able to flash something. When pressing Volume down+power it briefly detects it but won't write the firmware. I'll try different versions later and report back but for now it's dead
*uodate3* It's back again. I had to re-install the mediatek drivers for the tool to work. After a stock boot i was able to unlock the bootloader and install LOS again. I will go for an image with gapps next.
Thank you again for providing your images and support!
Click to expand...
Click to collapse
I'm so glad to hear that.
I have no plans to install GSI images.

たろう said:
I'm so glad to hear that.
I have no plans to install GSI images.
Click to expand...
Click to collapse
You really helped a lot. I'm always glad to tinker with spare phones.
For anyone else stumbling upon this thread trying to install a GSI image: Here is how i succeeded.
1. Enable unlocking in your developer settings
2. Use "fastboot flashing unlock" to enable flashing (this performs a factory reset)
3. wipe your system partition with "fastboot erase system"
4. Flash your GSI image wizh "fastboot flash system 'path-to-your-GSI' "
5. flash the provided vbmeta with "fastboot --disable-verity --disable-verification flash vbmeta 'path-to-vbmeta.img' "
I had success with lineageos 18 A/B with gapps. Make sure that it's not too big in size or else you will get an error message stating it is too big.
If you have troubles getting into recovery/fastboot, use the SPflashtool to revover your stock firmware (be sure to NOT format all because you will lose your IMEI information in that process!) and try again

Hi,
i tried to root my Cubot J5 by doing the following:
flash system system.img (from CUBOT_J5_9061C_V14_20200506 .zip)
fastboot flash boot magisk_patched-23000_boot.img
fastboot flash recovery magisk_patched-23000_recovery.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
reboot in recovery mode
When check for root with root checker basic, systems says, that magisk is crashed several times. And after this root checker states that no root is granted.
Any idea?

pat2858 said:
Hi,
i tried to root my Cubot J5 by doing the following:
flash system system.img (from CUBOT_J5_9061C_V14_20200506 .zip)
fastboot flash boot magisk_patched-23000_boot.img
fastboot flash recovery magisk_patched-23000_recovery.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
reboot in recovery mode
When check for root with root checker basic, systems says, that magisk is crashed several times. And after this root checker states that no root is granted.
Any idea?
Click to expand...
Click to collapse
I have no idea.
if possible to initialize with flash tool and then try again.

Tried it, but no luck.
Don't know why magisk is crashing all the time.

pat2858 said:
Tried it, but no luck.
Don't know why magisk is crashing all the time.
Click to expand...
Click to collapse
Is the Magisk version 23?
I have not confirmed the latest version(24~)

OnePlus 8t KB2001 stuck in a loop

I shifted from apple to android recently and I decided to root my device OnePlus 8t KB2001 (I believe I have Android 12) as I wanted to install kali on it. Therefore I decided to follow instructions on this website. I did not type the steps because I did not want to lose out on any key details.
I performed all the steps till here:
I did not perform step 6, instead, I performed step 7 as I wanted to install TWRP Recovery on my phone permanently.
{
"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"
}
According to the instructions I was supposed to boot my device to TWRP. Since I am currently booted to Fastboot, I used the Volume Keys to bring up the Recovery option and hit the Power key to confirm the decision.
As per the instruction as soon as my OnePlus boots to TWRP, it will ask to decrypt data. I was supposed to simply enter my phone’s password/PIN to proceed ahead but this never happened. Instead, I am stuck in a situation where I am seeing the following screen:
I searched every single option and there's no Online Update (keep data) option. I am stuck in this loop for hours. Even the option of formatting data doesn't remove this RECOVERY.
I don't know if this information would help but I can enter the Fastboot Mode by tapping on "Advanced" and selecting "Reboot to fastboot mode".
It would be really helpful if someone can tell me a fix to this problem as I really don't want to throw this phone away as I just got it today.

You probably flashed a version of TWRP made for Android 11 while having Android 12. You can try flashing a compatible version (unofficial) which you can find here.

I have not had the exact problem you describe but I don't think you'll end up discarding your phone. Just plan to read a lot on the forums, try a lot of things and potentially spend several days working through the problem. Bookmark the useful instructions you find so you can return to re-read and make notes as you go along. Start with booting a different version of TWRP and see what happens. The images you posted are of the stock recovery, not TWRP recovery. Make sure the TWRP.img you are trying to boot resides in the folder that your command prompt is pointing to.

TheNewHEROBRINE said:
You probably flashed a version of TWRP made for Android 11 while having Android 12. You can try flashing a compatible version (unofficial) which you can find here.
Click to expand...
Click to collapse
Thank you for this link. I followed these steps and I am out of the continuous recovery loop. My phone now directly boots to Team Win Recovery Project. Although I have a feeling my phone no longer has any oxygen OS. I tried rebooting into System but I am taken back to the TWRP screen. Any idea what is happening?

FakeGemstone said:
I have not had the exact problem you describe but I don't think you'll end up discarding your phone. Just plan to read a lot on the forums, try a lot of things and potentially spend several days working through the problem. Bookmark the useful instructions you find so you can return to re-read and make notes as you go along. Start with booting a different version of TWRP and see what happens. The images you posted are of the stock recovery, not TWRP recovery. Make sure the TWRP.img you are trying to boot resides in the folder that your command prompt is pointing to.
Click to expand...
Click to collapse
Thank you, this really gives me hope that my money will not go to waste. Now I am just in the process of trying to find a solution where I can my make phone the way it was which is without having any TWRP

kooluser said:
Thank you for this link. I followed these steps and I am out of the continuous recovery loop. My phone now directly boots to Team Win Recovery Project. Although I have a feeling my phone no longer has any oxygen OS. I tried rebooting into System but I am taken back to the TWRP screen. Any idea what is happening?
Click to expand...
Click to collapse
I think I know what happened:
The OnePlus 8T is a device which uses a technology called Virtual A/B. In practice, it has two slots for the operating system called 'a' and 'b' of which only one is active at a time. When you do an OTA upgrade the upgrade gets installed to the inactive slot and then the phone is asked to switch slot on the next boot. If the phone can't boot after this slot switch, it will switch back to the previous slot to prevent bricking itself. So what I think it happened when you flashed the wrong TWRP is that the phone tried to boot into recovery from your current slot but failed because of incompatibility. Then, it switched the active slot to the inactive slot where you probability have another version of OxygenOS that can't boot (probably because it's older than your current one). After some attempts, the phone goes into recovery but this time it loads the stock one because it has switched slot and the recovery is subject to this Virtual A/B mechanism too.
If this is what happened you can do as follows:
- reboot into fastboot
- switch the active slot by doing
Code:
fastboot --set-active=other
- flash the correct TWRP you downloaded before on this slot by doing
Code:
fastboot flash recovery <recovery file name>.img
After doing this you should be able to boot both into the system and into TWRP.

TheNewHEROBRINE said:
I think I know what happened:
The OnePlus 8T is a device which uses a technology called Virtual A/B. In practice, it has two slots for the operating system called 'a' and 'b' of which only one is active at a time. When you do an OTA upgrade the upgrade gets installed to the inactive slot and then the phone is asked to switch slot on the next boot. If the phone can't boot after this slot switch, it will switch back to the previous slot to prevent bricking itself. So what I think it happened when you flashed the wrong TWRP is that the phone tried to boot into recovery from your current slot but failed because of incompatibility. Then, it switched the active slot to the inactive slot where you probability have another version of OxygenOS that can't boot (probably because it's older than your current one). After some attempts, the phone goes into recovery but this time it loads the stock one because it has switched slot and the recovery is subject to this Virtual A/B mechanisms too.
If this is what happened you can do as follows:
- reboot into fastboot
- switch the active slot by doing
Code:
fastboot --set-active=other
- flash the correct TWRP you downloaded before on this slot by doing
Code:
fastboot flash recovery <recovery file name>.img
After doing this you should be able to boot both into the system and into TWRP.
Click to expand...
Click to collapse
THANK YOU SO MUCH!!! THIS SOLUTION SOLVED MY PROBLEM!
I can't express how happy I am right now!! I really thought I lost my phone forever. My phone has now successfully booted up and I can now actually use this device

kooluser said:
THANK YOU SO MUCH!!! THIS SOLUTION SOLVED MY PROBLEM!
I can't express how happy I am right now!! I really thought I lost my phone forever. My phone has now successfully booted up and I can now actually use this device
Click to expand...
Click to collapse
I'm happy for you too

TheNewHEROBRINE said:
I'm happy for you too
Click to expand...
Click to collapse
I just have one more question, so now if I have to boot into TWRP what steps should I follow? As I still have to download Magisk on my phone to properly root it

Did you flash TWRP after switching slot? If so you should be able to boot into it by holding power and volume down while turning the phone on.

Yes I flashed the TWRP as you specified below
Code:
fastboot flash recovery <recovery file name>.img
and once I press the power and the lower volume button I am taken into fastboot option. Once I am there which option should I select? Start, recovery or something else?

kooluser said:
Yes I flashed the TWRP as you specified below
Code:
fastboot flash recovery <recovery file name>.img
and once I press the power and the lower volume button I am taken into fastboot option. Once I am there which option should I select? Start, recovery or something else?
Click to expand...
Click to collapse
To root your phone you can follow this guide: https://forum.xda-developers.com/t/...national-kb2000-kb2001-kb2003-kb2005.4178675/
You actually don't strictly need TWRP to root. I suggest that you always try to follow guides that are on XDA rather than searching for random websites with Google.

TheNewHEROBRINE said:
To root your phone you can follow this guide: https://forum.xda-developers.com/t/...national-kb2000-kb2001-kb2003-kb2005.4178675/
You actually don't strictly need TWRP to root. I suggest that you always try to follow guides that are on XDA rather than searching for random websites with Google.
Click to expand...
Click to collapse
Thank you for the link. To perform this step do I need to do anything special right now? As I believe TWRP is still on my phone

kooluser said:
Thank you for the link. To perform this step do I need to do anything special right now? As I believe TWRP is still on my phone
Click to expand...
Click to collapse
It's not a problem to have TWRP installed.

TheNewHEROBRINE said:
It's not a problem to have TWRP installed.
Click to expand...
Click to collapse
Thank you so much for helping me and solving all my queries

kooluser said:
I just have one more question, so now if I have to boot into TWRP what steps should I follow? As I still have to download Magisk on my phone to properly root it
Click to expand...
Click to collapse
You can install magisk from TWRP recovery.
Changing slots is also possible there.

Trying to fix corrupted boot file on oneplus 8 5g in2017 tmobile model (FIXED)

sorry if this is not the right place to ask this
After unlocking my bootloader i tried to flash twrp on my phone by using the command "fastboot flash recovery twrp-3.7.0_11-0-instantnoodle.img"
When i restarted the phone it got stuck in a bootloop
I've been searching for a way to fix it for hours now, but everytime i do something it feels like i make it worst, now my phone is showing me an error that reads "the current image(boot/recovery) have been destroyed"
I dont know what to do, please if you have an idea of how to go forward reply

Provenscroll said:
sorry if this is not the right place to ask this
After unlocking my bootloader i tried to flash twrp on my phone by using the command "fastboot flash recovery twrp-3.7.0_11-0-instantnoodle.img"
When i restarted the phone it got stuck in a bootloop
I've been searching for a way to fix it for hours now, but everytime i do something it feels like i make it worst, now my phone is showing me an error that reads "the current image(boot/recovery) have been destroyed"
I dont know what to do, please if you have an idea of how to go forward reply
Click to expand...
Click to collapse
Hi, try to download the firmware for your device and flash it to your phone.

Jan Skokan said:
Hi, try to download the firmware for your device and flash it to your phone.
Click to expand...
Click to collapse
Do you know where I could find the stock firmware?

Provenscroll said:
Do you know where I could find the stock firmware?
Click to expand...
Click to collapse
Try this

Jan Skokan said:
Try this
Click to expand...
Click to collapse
It's telling me to get a "download package". Do I have to pay for this?

First, are you sure your device bootloader is unlocked?
Two, are you able to enter fastboot menu?
Three, if you can enter fastboot, try to BOOT into twrp instead of FLASH
Example: fastboot boot twrp.img
Booting into TWRP is the instructions for the OnePlus Pro 9, maybe it may work on the 8?
MAKE SURE OEM lock is removed first!!!

immortalwon said:
First, are you sure your device bootloader is unlocked?
Two, are you able to enter fastboot menu?
Three, if you can enter fastboot, try to BOOT into twrp instead of FLASH
Example: fastboot boot twrp.img
Booting into TWRP is the instructions for the OnePlus Pro 9, maybe it may work on the 8?
MAKE SURE OEM lock is removed first!!!
Click to expand...
Click to collapse
I'm talking about the website with the package thing, when i tried to boot into twrp i got this error
./fastboot boot twrp-3.7.0_11-0-instantnoodle.img
Sending 'boot.img' (67276 KB) OKAY [ 1.949s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed

[OnePlus 8][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
Has old firmware you can download / flash. You can use a tool called Payload dumper on the firmware to extract all the sections and re-flash the sections you messed up. Can you get into the bootloader / fastboot screen and show me what it shows?
Re-download the twrp file for your device, rename it to twrp.img and try to do this command
Make sure you also have the correct drivers installed on your pc and disable driver signature enforcement:
fastboot boot twrp.img

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FastBoot Mode
PRODUCT_NAME - Kona
VARIANT - SM8 UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (Censored)
SECURE BOOT - yes
DEVICE STATE - unlocked

Provenscroll said:
View attachment 5863469
FastBoot Mode
PRODUCT_NAME - Kona
VARIANT - SM8 UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (Censored)
SECURE BOOT - yes
DEVICE STATE - unlocked
Click to expand...
Click to collapse
Ok the fact you can enter into this mode and it says device unlocked is good. I am not sure why it doesn't allow you to boot with the above mentioned command into recovery.
Please make sure like I previously mentioned you have latest platform tools, latest oneplus usb drivers and try to switch to a usb 2.0 port on your pc or laptop. Disable driver signature enforcement in windows before you try to install oneplus drivers.

I've should have mentioned this earlier but i'm doing most of this on a linux machine, but i have repeated the commands on a windows laptop doing everything that has been mentioned previously to similar results
Now when i try to boot Twrp it just hangs and no changes happen on my phone
.\fastboot boot twrp.img
Sending 'boot.img' (67276 KB)
and then nothing happens
When i try to flash recovery it also hangs
.\fastboot flash recovery twrp.img
and no response
I'll try this with a different cable and update this post

Provenscroll said:
I've should have mentioned this earlier but i'm doing most of this on a linux machine, but i have repeated the commands on a windows laptop doing everything that has been mentioned previously to similar results
Now when i try to boot Twrp it just hangs and no changes happen on my phone
.\fastboot boot twrp.img
Sending 'boot.img' (67276 KB)
and then nothing happens
When i try to flash recovery it also hangs
.\fastboot flash recovery twrp.img
and no response
I'll try this with a different cable and update this post
Click to expand...
Click to collapse
I think you corrupted a bunch of stuff when you used a linux machine to flash a recovery. The drivers are vastly different on a linux machine. You might have to use a MSM tool at this point, but I am not sure if the T-mobile version has one. Keep us updated on the new cable. Also try different usb ports as well.
Which android version did your phone have? I checked the official twrp website and it only supports A11 devices for oneplus 8.
@Provenscroll EDIT: I was just testing different slots a/b on fastboot and realized that when I changed to slot a, my inactive slot, I get the same error as you did with fastboot. Try to use the other slot if possible.

immortalwon said:
I was just testing different slots a/b on fastboot and realized that when I changed to slot a, my inactive slot, I get the same error as you did with fastboot. Try to use the other slot if possible.
Click to expand...
Click to collapse
So i tried this and it successfully flashed:
.\fastboot flash recovery_b twrp.img
Sending 'recovery_b' (67276 KB) OKAY [ 1.638s]
Writing 'recovery_b' OKAY [ 0.212s]
Finished. Total time: 2.093s
When I reboot into recovery though it just ends up at the boot/recovery error
immortalwon said:
Which android version did your phone have? I checked the official twrp website and it only supports A11 devices for oneplus 8.
Click to expand...
Click to collapse
My android was at 12 so that might explain why flashing twrp isn't working

immortalwon said:
I checked the official twrp website and it only supports A11 devices for oneplus 8.
Click to expand...
Click to collapse
Does the firmware i flash onto the phone also have to match the original android version?

Provenscroll said:
Does the firmware i flash onto the phone also have to match the original android version?
Click to expand...
Click to collapse
Yes I would try it on A11 first. But don't quote me on that because there is a reason I don't like using carrier based phones instead of fully unlocked phones. They come with unpredictable problems. Try at own risk. I would first try to boot into TWRP first on a11 firmware and then flash TWRP recovery with the option: "Install Recovery ramdisk" then select the .img file you downloaded from website. You can also use: Go to Advanced > Flash Current TWRP.
But the problem is: you need to be able to BOOT first into the recovery.
Heck I would try to boot with the a11 twrp right now just to see if it loads instead of using the flash command, if it boots up its a good sign but it probably won't have decryption support, all your files will look like random numbers. Your bootloader is unlocked so common sense dictates it should be able to boot the twrp.
Fastboot boot twrp.img
EDIT: Well I tried to boot unofficial a12 twrp onto my device and it didn't boot into it. So it might not work for you either. I am on stock oos 11 and the a11 version is the only one that boots.
This link might be able to help:
https://forum.xda-developers.com/t/...p-for-oneplus-8-8pro-official-beta-3.4341707/
I noticed at this link, they have different .img files then the official website. Give it a try. They mentioned flashing instead of booting, so it's slightly confusing.

Ok so I tried flashing a boot.img file I extracted from a payload I got from here
OnePlus Android 12 Tracker: Here are all the official OxygenOS 12 builds to download and install
OxygenOS 12 Open Beta builds based on Android 12 have begun rolling out to multiple OnePlus smartphones. Head on over for the download links!
www.xda-developers.com
and now theres a recovery screen:
I tried using format data to see what happens since my important data is already backed up, when i did this my phone rebooted into a setup screen but when i get to the point where i have to setup my network the screen hangs and the phone restarts. Maybe this is because the roms model number doesn't exactly align with my phone?

I got it in twrp!!

Provenscroll said:
I got it in twrp!!
View attachment 5866011
Click to expand...
Click to collapse
Nice work man, what did you do exactly?

immortalwon said:
Nice work man, what did you do exactly?
Click to expand...
Click to collapse
After flashing the boot.img that i mentioned before i was simply able to run the command fastboot boot recovery.img to get it into twrp

Provenscroll said:
After flashing the boot.img that i mentioned before i was simply able to run the command fastboot boot recovery.img to get it into twrp
Click to expand...
Click to collapse
Ok I am not sure what you should do at this point: flashing the recovery while in TWRP or simply booting into it future wise. I read on t-mobile devices, if you try to flash it might brick it but I am not sure.