Database Info

N8000 stuck in boot loop - HELP!

Ok,
GT-N8000 was on stock Samsung 4.1.2 Rom. Rooted using Chainfire, installed CWM 6.0.3.6 and then flashed a CM11 rom from here on XDA.
Rebooted happily, logged in, set-up the tablet and happily worked for about 24 hours.
Tablet at some point rebooted, got only as far as the first "Samsung Note 10.1" white text on the screen and the tablet refused to do anything else.
Can boot into CWM recovery
Can boot into Odin Mode "Downloading"
When booting into Recovery, I can browse all the options, but when selecting any action, the tablet reboots.
Have tried downloading a fresh stock rom (4.4.2 from Vietnam from Samfirmware), and flashing via ODIN. Odin seems to flash OK, but when the device reboots, straight back into "Samsung Note 10.1" screen.
After that flash, when trying to boot into recovery, it still goes to CWM and not the stock Recovery.
Have tried downloading a new PIT and flashing that when flashing the new stock ROM.
Have tried Googling several items, and here on XDA, but not entirely sure where to try next. Suggestions would be welcome.

cdinoz said:
Ok,
GT-N8000 was on stock Samsung 4.1.2 Rom. Rooted using Chainfire, installed CWM 6.0.3.6 and then flashed a CM11 rom from here on XDA.
Rebooted happily, logged in, set-up the tablet and happily worked for about 24 hours.
Tablet at some point rebooted, got only as far as the first "Samsung Note 10.1" white text on the screen and the tablet refused to do anything else.
Can boot into CWM recovery
Can boot into Odin Mode "Downloading"
When booting into Recovery, I can browse all the options, but when selecting any action, the tablet reboots.
Have tried downloading a fresh stock rom (4.4.2 from Vietnam from Samfirmware), and flashing via ODIN. Odin seems to flash OK, but when the device reboots, straight back into "Samsung Note 10.1" screen.
After that flash, when trying to boot into recovery, it still goes to CWM and not the stock Recovery.
Have tried downloading a new PIT and flashing that when flashing the new stock ROM.
Have tried Googling several items, and here on XDA, but not entirely sure where to try next. Suggestions would be welcome.
Click to expand...
Click to collapse
Have you tried full erase(factory reset) via recovery mate including the internal SD? And remove the external SD just to make sure, then reinstall the stock 4.4.2 firmware. Can I ask why did you install vietnam version when you are in Australia? Where did you get the pit file? Is it for 4.4.2?

filchi756 said:
Have you tried full erase(factory reset) via recovery mate including the internal SD? And remove the external SD just to make sure, then reinstall the stock 4.4.2 firmware. Can I ask why did you install vietnam version when you are in Australia? Where did you get the pit file? Is it for 4.4.2?
Click to expand...
Click to collapse
When in CWM and trying to full reset, the tablet reboots a few seconds after selecting the option. Have removed sim and sd card prior to flashing.
Vietnam was one of three roms I was d/l from Sam mobile. I was trying to grab various roms, but they were getting to 70/75% and then failing. I have also tried flashing now a Singapore rom and a German rom. Cannot find an Aussie stock rom on that site anywhere, or anywhere else for that matter, which will download.
Have successfully flashed other region roms on other Samsung devices, so assumed this model would be no different.
PIT file was a last resort effort, found here....http://forum.xda-developers.com/showthread.php?t=2730188
After flashing any stock rom, the tablet continues to not restart, but still let's me boot into CWM oddly (should flashing a stock rom via Odin reinstall stock Recovery?).

cdinoz said:
When in CWM and trying to full reset, the tablet reboots a few seconds after selecting the option. Have removed sim and sd card prior to flashing.
Vietnam was one of three roms I was d/l from Sam mobile. I was trying to grab various roms, but they were getting to 70/75% and then failing. I have also tried flashing now a Singapore rom and a German rom. Cannot find an Aussie stock rom on that site anywhere, or anywhere else for that matter, which will download.
Have successfully flashed other region roms on other Samsung devices, so assumed this model would be no different.
PIT file was a last resort effort, found here....http://forum.xda-developers.com/showthread.php?t=2730188
After flashing any stock rom, the tablet continues to not restart, but still let's me boot into CWM oddly (should flashing a stock rom via Odin reinstall stock Recovery?).
Click to expand...
Click to collapse
Suppose to be when you install full rom the custom recovery is erased and back to stock recovery. What version of pc Odin are you using? Try ver.1.85 or 3.07 if you haven't yet. And just to be sure have you installed any other 4.4.2 rom prior to stock 4.4.2?And maybe you can try philz recovery for custom recovery.

filchi756 said:
Suppose to be when you install full rom the custom recovery is erased and back to stock recovery. What version of pc Odin are you using? Try ver.1.85 or 3.07 if you haven't yet. And just to be sure have you installed any other 4.4.2 rom prior to stock 4.4.2?And maybe you can try philz recovery for custom recovery.
Click to expand...
Click to collapse
Odin - have tried 1.85, 3.07 and 3.09
Rom - When the tablet was on stock 4.1.2, was rooted following method (2) here: http://forum.xda-developers.com/showthread.php?t=1831152 and had installed CWM 6.0.3.6. After gaining root, copied zip files for this rom http://forum.xda-developers.com/showthread.php?t=2550308 to the externalSD and performed a factory reset, wiped data etc and flashed OminRom 4.4. This booted happily, and worked for about 24 / 36 hours (ish) when it's owner claimed it rebooted at some point, and came back only the the "Samsung Galaxy Note 10.1" white text boot screen, and went no further
Recovery - Since the issue first started, have tried various flavours of re-flashing CWM (both Touch and Non Touch), TWRP mostly from here: https://goo.im/devs/Darkman/Recoverys/ and a Philz Touch recovery sourced from here: http://forum.xda-developers.com/showthread.php?t=2202714
Each time have been flashed using Odin and using the .tar.md5 file types (as the CWM simply crashes and the tablet reboots now when trying to flash a zip via recovery). Have set Odin NOT to auto-reboot, however whilst Odin reported no obvious sign of error, upon reboot to Recovery, went straight to the previous CWM 6.0.3.6 recovery.
And now my head hurts......
Note: I did say in the opening post was a CM11 based rom, but it actually was an AOSP based rom,

cdinoz said:
Odin - have tried 1.85, 3.07 and 3.09
Rom - When the tablet was on stock 4.1.2, was rooted following method (2) here: http://forum.xda-developers.com/showthread.php?t=1831152 and had installed CWM 6.0.3.6. After gaining root, copied zip files for this rom http://forum.xda-developers.com/showthread.php?t=2550308 to the externalSD and performed a factory reset, wiped data etc and flashed OminRom 4.4. This booted happily, and worked for about 24 / 36 hours (ish) when it's owner claimed it rebooted at some point, and came back only the the "Samsung Galaxy Note 10.1" white text boot screen, and went no further
Recovery - Since the issue first started, have tried various flavours of re-flashing CWM (both Touch and Non Touch), TWRP mostly from here: https://goo.im/devs/Darkman/Recoverys/ and a Philz Touch recovery sourced from here: http://forum.xda-developers.com/showthread.php?t=2202714
Each time have been flashed using Odin and using the .tar.md5 file types (as the CWM simply crashes and the tablet reboots now when trying to flash a zip via recovery). Have set Odin NOT to auto-reboot, however whilst Odin reported no obvious sign of error, upon reboot to Recovery, went straight to the previous CWM 6.0.3.6 recovery.
And now my head hurts......
Note: I did say in the opening post was a CM11 based rom, but it actually was an AOSP based rom,
Click to expand...
Click to collapse
So that means you can't even install custom rom?Can I ask what version is written in download mode is it still N8000?

filchi756 said:
So that means you can't even install custom rom?Can I ask what version is written in download mode is it still N8000?
Click to expand...
Click to collapse
Correct. If I try to flash via CWM, the tablet goes thru the motion of flashing the rom (the bit where the developers ascii logo appears) followed by the little blue line telling you the custom rom is installing, and after a few seconds tells you that the flash is complete.
The giveaway is that this entire process takes about 15 seconds - and you just know that the rom has not flashed. The second is that immediately when it completes, the tablet (yes you've guessed what happens next...) just reboots back to the Samsung logo.
But yes, when in download mode, the tablet is definitely reporting as still as a GT-N8000. Its also has some other text (sorry the thing is not in front of me right now) about the binary counter of 3...?
Cheers

cdinoz said:
Correct. If I try to flash via CWM, the tablet goes thru the motion of flashing the rom (the bit where the developers ascii logo appears) followed by the little blue line telling you the custom rom is installing, and after a few seconds tells you that the flash is complete.
The giveaway is that this entire process takes about 15 seconds - and you just know that the rom has not flashed. The second is that immediately when it completes, the tablet (yes you've guessed what happens next...) just reboots back to the Samsung logo.
But yes, when in download mode, the tablet is definitely reporting as still as a GT-N8000. Its also has some other text (sorry the thing is not in front of me right now) about the binary counter of 3...?
Cheers
Click to expand...
Click to collapse
About the binary thats not a problem. So your problem now is error flashing via CWM right? Try Philz recovery mate in custom rom installing. And make sure your custom rom is fully working and tested mate. Try to open the zip in pc if it had any error. And how about installing a custom recovery any luck with it installing too?

filchi756 said:
About the binary thats not a problem. So your problem now is error flashing via CWM right? Try Philz recovery mate in custom rom installing. And make sure your custom rom is fully working and tested mate. Try to open the zip in pc if it had any error. And how about installing a custom recovery any luck with it installing too?
Click to expand...
Click to collapse
But there lies the problem.
I have tried flashing Philz both via Odin and via CWM.
It "appears" to flash in Odin, but when the tablet starts, its still CWM.
When flashing in CWM, it fails to flash. (I'll get you the error message when I'm back in front of the tablet).

So, here is Philz Recovery flashing in CWM, showing a successful flash:
{
"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"
}
[/IMG]
And after a reboot:
Still in CWM 6.0.3.6 (apologies for the terrible image - using my Tab Lite)

cdinoz said:
So, here is Philz Recovery flashing in CWM, showing a successful flash:
[/IMG]
And after a reboot:
Still in CWM 6.0.3.6 (apologies for the terrible image - using my Tab Lite)
Click to expand...
Click to collapse
lastly mate can you take a picture of you download mode were the binary is written.

cdinoz said:
So, here is Philz Recovery flashing in CWM, showing a successful flash:
[/IMG]
And after a reboot:
Still in CWM 6.0.3.6 (apologies for the terrible image - using my Tab Lite)
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...ot-charge-power-off-efs-t2809821/post54680214

[GUIDE] OREO Root for Japanese Snapdragon G950J(D) (SC-02J) (SCV36 - not tested)

After 3+ hrs of trial and error and help from awesome xda member Peter KIKI, I finally managed to root SC-02J (950J)(D) on the latest Oreo firmware.
Also huge thanks to tomatolei for his kernel which made this possible.
Requirements :
1. PC/Laptop
2. Latest Oreo firmware for SC-02J (Updato or Samfirm).
3. Latest TWRP for Snapdragon S8 - Link
4. Modified kernel (9500.img) thanks to @tomatolei
5. Wifi fix (optional) thanks to @Peter KIKI
DL : 9500.img and wifi fix - link (Updated)
Instructions :
1. Flash the latest Oreo firmware with Odin 3.13.1 . (This will erase your internal storage so backup anything important beforehand)
2. Boot up normally. (Skip Wifi and account setup to speed up the process)
3. Enable Developer Options and then enable OEM unlock.
4. Power off your device, boot in download mode.
5. Open Odin > go to Options tab and untick "Auto Reboot"
6. Flash TWRP (AP slot).
(Warning : After flashing TWRP, boot straight to recovery)
(Make sure to "Allow Modifications" when TWRP boots up)
7. Go to "Wipe" > "Format Data" > type "yes". then go to "Reboot" and select "Recovery"
8. Once in TWRP go to "Install" and Flash the "9500.img" as "boot".
9. Reboot to System, first boot might take longer than usual and reboot couple of times.
(Important : If wifi not working, skip the network and account setup)
10. After initial setup is done, power off and boot to recovery and flash Magisk 16.0 or newer.
(You'll also need to flash "wifi fix.zip" if your wifi isn't working)
UPDATE : TWRP Oreo data mount fix : Thanks @Peter KIKI
replace fstab.qcom in /system/vendor/etc/ with the one from attachments(unzip first).
* Xposed not tested.
** This method works on SC-02J or SCV36 loaded with SC-02J firmware.
***SCV36 with KDDI firmware not tested.
Credits :
@tomatolei for his 9500 kernel.
@Peter KIKI for helping me with this process and providing the wifi fix.
{
"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"
}
updated : model name.

texhno04 said:
After 3+ hrs of trial and error and help from awesome xda member Peter KIKI, I finally managed to root SC-02J (950J) on the latest Oreo firmware.
Also huge thanks to tomatolei for his kernel which made this possible.
Requirements :
1. PC/Laptop
2. Latest Oreo firmware for SC-02J (Updato or Samfirm).
3. Latest TWRP for Snapdragon S8 - Link
4. Modified kernel (9500.img) thanks to @tomatolei
5. Wifi fix (optional) thanks to @Peter KIKI
DL : 9500.img and wifi fix - link
Instructions :
1. Flash the latest Oreo firmware with Odin 3.13.1 . (This will erase your internal storage so backup anything important beforehand)
2. Boot up normally. (Skip Wifi and account setup to speed up the process)
3. Enable Developer Options and then enable OEM unlock.
4. Power off your device, boot in download mode.
5. Open Odin > go to Options tab and untick "Auto Reboot"
6. Flash TWRP (AP slot).
(Warning : After flashing TWRP, boot straight to recovery)
(Make sure to "Allow Modifications" when TWRP boots up)
7. Go to "Wipe" > "Format Data" > type "yes". then go to "Reboot" and select "Recovery"
8. Once in TWRP go to "Install" and Flash the "9500.img" as "boot".
9. Reboot to System, first boot might take longer than usual and reboot couple of times.
(Important : If wifi not working, skip the network and account setup)
10. After initial setup is done, power off and boot to recovery and flash Magisk 16.0 or newer.
(You'll also need to flash "wifi fix.zip" if your wifi isn't working)
* Xposed not tested.
** This method works on SC-02J or SCV36 loaded with SC-02J firmware.
***SCV36 with KDDI firmware not tested.
Credits :
@tomatolei for his 9500 kernel.
@Peter KIKI for helping me with this process and providing the wifi fix.
Click to expand...
Click to collapse
is there any custom rom for sc-02j?

nou90 said:
is there any custom rom for sc-02j?
Click to expand...
Click to collapse
Aurora ROM (with G950J kernel patch) for G9500 works with sc-02j.

texhno04 said:
After 3+ hrs of trial and error and help from awesome xda member Peter KIKI, I finally managed to root SC-02J (950J) on the latest Oreo firmware.
Also huge thanks to tomatolei for his kernel which made this possible.
Requirements :
1. PC/Laptop
2. Latest Oreo firmware for SC-02J (Updato or Samfirm).
3. Latest TWRP for Snapdragon S8 - Link
4. Modified kernel (9500.img) thanks to @tomatolei
5. Wifi fix (optional) thanks to @Peter KIKI
DL : 9500.img and wifi fix - link
Instructions :
1. Flash the latest Oreo firmware with Odin 3.13.1 . (This will erase your internal storage so backup anything important beforehand)
2. Boot up normally. (Skip Wifi and account setup to speed up the process)
3. Enable Developer Options and then enable OEM unlock.
4. Power off your device, boot in download mode.
5. Open Odin > go to Options tab and untick "Auto Reboot"
6. Flash TWRP (AP slot).
(Warning : After flashing TWRP, boot straight to recovery)
(Make sure to "Allow Modifications" when TWRP boots up)
7. Go to "Wipe" > "Format Data" > type "yes". then go to "Reboot" and select "Recovery"
8. Once in TWRP go to "Install" and Flash the "9500.img" as "boot".
9. Reboot to System, first boot might take longer than usual and reboot couple of times.
(Important : If wifi not working, skip the network and account setup)
10. After initial setup is done, power off and boot to recovery and flash Magisk 16.0 or newer.
(You'll also need to flash "wifi fix.zip" if your wifi isn't working)
* Xposed not tested.
** This method works on SC-02J or SCV36 loaded with SC-02J firmware.
***SCV36 with KDDI firmware not tested.
Credits :
@tomatolei for his 9500 kernel.
@Peter KIKI for helping me with this process and providing the wifi fix.
Click to expand...
Click to collapse
i have update all the fix in my thread it should work for you
https://forum.xda-developers.com/ga...g9550-g9500-phoenixo9-crf2-everytime-t3819774

SC-02J Aurora ROM Tutorial Please
texhno04 said:
Aurora ROM (with G950J kernel patch) for G9500 works with sc-02j.
Click to expand...
Click to collapse
Hi, Can You provide a step by step guide for Galaxy S8 SC-02J. Aurora Rom installation guide. I tried before and now my EFS (Baseband & IMEI) are unknown after installing the stock firmware. I have a screenshot of my IMEI Number.
If I install Aurora ROM, will my phone start working again?
Thank You.

SM G9500 Oreo 8.0 OK
Thank you for the guide.
I try this on my S8 China Version, and it's work.
1. Flash TWRP;
2. Format Data;
3. Flash Fusion Kernel;
4. Wait until all is good;
5. Reboot to recovery and flash the wifi fix zip;
6. Reboot, the magisk is here and rooted.

sorry i cant find nfc setup in anywhere

caocaolatre199x said:
sorry i cant find nfc setup in anywhere
Click to expand...
Click to collapse
NFC (Felica) will not work with modified kernel or root.

ghafupk said:
Hi, Can You provide a step by step guide for Galaxy S8 SC-02J. Aurora Rom installation guide. I tried before and now my EFS (Baseband & IMEI) are unknown after installing the stock firmware. I have a screenshot of my IMEI Number.
If I install Aurora ROM, will my phone start working again?
Thank You.
Click to expand...
Click to collapse
Unless you have an EFS backup, you will not get your Baseband/IMEI back.
but, there are paid services out there that can still fix bb/imei.
sorry

can someone give me a link of flashable kernel 9500 img its not flashable my phone in bootloop now SC-02J variant
edit: NVM i got it thnx for this

can i also use the wifi fix on my sc-03j?

Do you have frp lock?

hi, @tomatolei
humm, I would like to DL some file on your website, I can't make Baidu account, because i don't have phone number, so Could you upload some files other site?
i have galaxy s8+ HKG model, G9550.
Thank you.

texhno04 said:
NFC (Felica) will not work with modified kernel or root.
Click to expand...
Click to collapse
It's really annoying

I was wondering if you were still developing this device @texhno04?
I've been trying to root it with the latest Android Pie update, but didn't get any luck yet.
Did anyone try and succeed?

londonbabs said:
I was wondering if you were still developing this device @texhno04?
I've been trying to root it with the latest Android Pie update, but didn't get any luck yet.
Did anyone try and succeed?
Click to expand...
Click to collapse
sorry to say I moved on from S8. Never buying Snapdragon Samsung ever again they are the absolute worst when it comes to rooting and custom ROMs.
afaik, there isn't any rooting method available for G9500(HK/China Model) on Android Pie yet (HK/China and Japanese models share the same hardware).
keep in touch with @Peter KIKI, he helped me with Oreo root on Japanese S8.
I'm sure there will be a rooting method sooner or later for SCV36/SC-02J with the G9500 Pie kernel.

texhno04 said:
Never buying Snapdragon Samsung ever again they are the absolute worst when it comes to rooting and custom ROMs.
Click to expand...
Click to collapse
Yeah, I can't blame you on that.
I'm hoping to get good news with Fusion Kernel's project indeed. I'll sit tight and keep my fingers crossed. :fingers-crossed:
Thank you for your answer and for your previous work with Oreo, any support for this device is always greatly appreciated!

Hi, I've been following this suggestion to root my docomo phone. On step 9, right after I flash 9500.img as a boot, it's been bootlooping for 15 minutes. I am aware you mentioned it will take time and several reboots, but I think this is bootloop :crying:

pixie_laluna said:
Hi, I've been following this suggestion to root my docomo phone. On step 9, right after I flash 9500.img as a boot, it's been bootlooping for 15 minutes. I am aware you mentioned it will take time and several reboots, but I think this is bootloop :crying:
Click to expand...
Click to collapse
Deleted, my mistake thought docomo was a brand ??

@texhno04 Do you have a root solution on android 9 pie?

[RECOVERY][3.4.0-0][doha]Unofficial TWRP recovery for Moto G8 Plus (Testing)

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- Decrypt works
- Removed TWRP app
- Backup still have some problems use it carefully
- Fastboot boot works
- Touch works
- Vibration works
- Rom Flashing
Install guide:
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Run "fastboot boot recoveryimgfilename.img" in command line (if you want to have it permanently you should flash the installer)
5. If you will flash the installer and you are stock you need also to flash magisk or your phone will not boot again
6. Enjoy it
Other Install guide:
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Run "fastboot boot recoveryimgfilename.img" in command line
5. Copy the recoveryimgfilename.img in the phone memory
6. Go in advanced menu
7. Click on "Install Recovery Ramdisk"
{
"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"
}
8. Choose the recoveryimgfilename.img
9. Swipe to install
Tips:
If you alread have a twrp flashed you can only flash the new installer zip or the new installation method to update your TWRP (remember to flash again magisk or your system will not boot).
If you have some problems with backup, like 255 error or something similar please check this guide: https://forum.xda-developers.com/oneplus-6/how-to/255-error-twrp-backup-restore-999-t3801632
For the Bacups use always "system_image" and "vendor_image" instead of "system" and "vendor".
Download:
TWRP 3.4.0-0 Unofficial by mauronofrio
TWRP 3.4.0-0 Unofficial Installer by mauronofrio
TWRP 3.3.1-23 Unofficial by mauronofrio
TWRP 3.3.1-23 Unofficial Installer by mauronofrio
TWRP 3.3.1-19 Unofficial by mauronofrio
TWRP 3.3.1-19 Unofficial Installer by mauronofrio
TWRP 3.3.1-17 Unofficial by mauronofrio
TWRP 3.3.1-17 Unofficial Installer by mauronofrio
TWRP 3.3.1-16 Unofficial by mauronofrio
TWRP 3.3.1-16 Unofficial Installer by mauronofrio
Source code:
https://github.com/omnirom/android_bootable_recovery
https://github.com/mauronofrio/android_device_motorola_doha
My Telegram TWRP Support Group:
https://t.me/twrp_Mauronofrio
Donations:
Credits:
Thanks to @ath0 for hard testing
Thanks to vache for the help with touch fix
Thanks to @Electimon for some tips
Created 2020-02-27

TWRP 3.3.1-17 Motorola Moto G8 Plus (doha) by mauronofrio:
- Fixed touch for focaltech panels.
TWRP 3.3.1-17 Unofficial by mauronofrio
TWRP 3.3.1-17 Unofficial Installer by mauronofrio

Rom updates

TWRP 3.3.1-19 Motorola Moto G8 Plus (doha) by mauronofrio:
- Fixed Rom flashing;
- Partially fixed format data.
TWRP 3.3.1-19 Unofficial by mauronofrio
TWRP 3.3.1-19 Unofficial Installer by mauronofrio

sorry for my bad English..
so... if I want to stay in the stock rom and install TWRP, the only way is to root with magisk?
and after that the stock ROM rooted with magisk will be stable to daily use?

Hello thanks for the TWRP recovery port. It works great!
Now, a few days after I flashed it. Motorola pushed a firmware or security update . I didn't install it yet but I would like to. I think I have to go back to stock recovery in order to install the update. Might you have a guide on how to do this? I already have the stock rom downloaded but I don't know how to get the stock recovery

When flashing the installer or using the "Install Recovery Ramdisk" method, the touchscreen won't work

Hello,
I've got a Moto G8 Plus which I rooted using Magisk after unlocking the bootloader. It works just fine as it is, but I would like to install TWRP so I can have a backup of it. However, I'm afraid of installing TWRP and breaking something or losing the root.
Can I flash this version of TWRP over a Moto G8 Plus already rooted with Magisk without losing root or breaking Magisk or something else?

irex102 said:
Hello thanks for the TWRP recovery port. It works great!
Now, a few days after I flashed it. Motorola pushed a firmware or security update . I didn't install it yet but I would like to. I think I have to go back to stock recovery in order to install the update. Might you have a guide on how to do this? I already have the stock rom downloaded but I don't know how to get the stock recovery
Click to expand...
Click to collapse
That is just a security update let it be it will **** things up trust me

Hi there,
Thanks for your efforts puling together a TWRP for our phones!
I've got a question because I'm not quite clear about your response to the previous question about the security update. I've been using the stock recovery, rooted with Magisk and went through the whole process of accepting the security update and then re-rooted etc.
Will I wind up F'ing up my phone if I go to install your TWRP since I've already accepted the security update? Or would I be better off just compiling TWRP on my own ( it'll be my first foray into that area ) taking that route instead?
Any and all opinions welcome

Hamaruka said:
When flashing the installer or using the "Install Recovery Ramdisk" method, the touchscreen won't work
Click to expand...
Click to collapse
Same issue here. Works only when I fastboot boot off my laptop.

did not work for my phone, Moto G8 Power purchased 4/17/2020 fully unlocked bootloader, no root, attempted to boot to img, failed to boot.
[email protected]
sorry im doing a lot of research and looking, i basically accidentally soft bricked my phone, my wife and i have the exact same phone, and i cant seem to pull the factory images from it, nor can i make the various versions of OEM recovery images or boot loaders function on the phone.
maybe im just doing something wrong. pardon the typos.

FoxDroid1214 said:
did not work for my phone, Moto G8 Power purchased 4/17/2020 fully unlocked bootloader, no root, attempted to boot to img, failed to boot.
[email protected]
sorry im doing a lot of research and looking, i basically accidentally soft bricked my phone, my wife and i have the exact same phone, and i cant seem to pull the factory images from it, nor can i make the various versions of OEM recovery images or boot loaders function on the phone.
maybe im just doing something wrong. pardon the typos.
Click to expand...
Click to collapse
I have played a little with Moto G8 Plus (XT2019-1). And i'm not worried about brick it. Have done a few times, but always recovered with blankflash.. After blankflash it will start bootloader, and then i can flash stock firmware. I found Stock FW and also blankflash on lolinet. I prefer using Fastboot for flashing. Don't need TWRP for flashing. Have locked, and Unlocked bootloader many times..
If needed, i can make a description on how to use blankflash as it can be hard to get started..
Check lolinet for stock FW and blankflash.. You need to know code name for your phone..
mirrors.lolinet.com/firmware/moto/

can i flash latest magisk straight through twrp? or does it have to be the patch boot process?

Allright, I installed successfully TWRP (install to ramdisk) and Magisk, rooted phone is fine etc, but when I boot into recovery again touch does not work and I am stuck in bootloop into recovery until I flash both again. Any hints?

hendrack said:
Allright, I installed successfully TWRP (install to ramdisk) and Magisk, rooted phone is fine etc, but when I boot into recovery again touch does not work and I am stuck in bootloop into recovery until I flash both again. Any hints?
Click to expand...
Click to collapse
Seems a common bug, i need someone with which test this thing

What would testing imply?

My guess would be: flashing experimental twrp, praying it doesn't brick your phone, reading logs?

mauronofrio said:
Seems a common bug, i need someone with which test this thing
Click to expand...
Click to collapse
The same error any solution?

I could help by flashing the recoverys and submitting the logs but beyond that I'm helpless

[SOLVED] Poco X3 NFC - Bootloop after Wiping & Flashing Custom ROM

Hello, today I wiped Dalvik / ART Cache, Cache and Data because I wanted to install Custom ROM.
Maybe I also accidentally wiped Internal Storage or System. Then I flashed the Custom ROM. Now after the Custom ROM flashes again, the boot animation will hang and then the phone will restart shortly. I don't know how to solve this situation. I tried to flash the MIUI using the Xiaomi Mi Flash Tool, install the ROM through Fastboot, but nothing worked.
Please anyone know what to do with this? Thank you

DrakMC said:
Hello, today I wiped Dalvik / ART Cache, Cache and Data because I wanted to install Custom ROM.
Maybe I also accidentally wiped Internal Storage or System. Then I flashed the Custom ROM. Now after the Custom ROM flashes again, the boot animation will hang and then the phone will restart shortly. I don't know how to solve this situation. I tried to flash the MIUI using the Xiaomi Mi Flash Tool, install the ROM through Fastboot, but nothing worked.
Please anyone know what to do with this? Thank you
Click to expand...
Click to collapse
You didn't explain your Problem quite well. Does it reboot to fastboot or does it reboot to system? (aka a Bootloop). if it reboots to system, here's what to do:
Boot into a custom recovery (twrp/Orangefox) and flash the required recovery MIUI ROM mentioned in your custom ROM's thread instructions.
Flash the custom ROM/Gapps, followed by Formatting /data using the Advanced Options in the wipe menu.
Reboot.
If you can't find the format option (which is mandatory before a new boot of a custom ROM), you can use this command while in fastboot mode:
Code:
fastboot erase userdata
Formatting /data is required for Encrypted devices to reset the encryption key and avoid a Bootloop. Please refer to this thread for more Custom ROM flashing instructions. If all else fails, you could EDL flash your device through MI flash tool/Command line, this process costs money (you need an Authorized Xiaomi Account) to complete.

Thank you very much for your help!
Slim K said:
Does it reboot to fastboot or does it reboot to system? (aka a Bootloop).
Click to expand...
Click to collapse
It depends when. When the MIUI flashes through the Mi Flash Tool, the Poco logo is displayed and the phone restarts and the Poco logo is displayed again. All the time.
So I followed your instructions.
I would like to flash ArrowOS, but nowhere do they write what version of MIUI I need. That's why I flashed this version of MIUI through Mi Flash Tool: https://xiaomifirmwareupdater.com/miui/surya/stable/V12.0.8.0.QJGMIXM/
After I flashed MIUI using Mi Flash Tool and then I booted into TWRP and installed the downloaded ArrowOS. After installation, I went to the Wipe section and deleted the Data. Then I restarted the phone to System. The Poco logo was displayed and after a while the phone booted into TWRP. So I don't know where the problem is. (Before ArrowOS flashed, the cell phone tried to boot into the system, the Poco logo was still displayed, and then the phone restarted.)

DrakMC said:
Thank you very much for your help!
It depends when. When the MIUI flashes through the Mi Flash Tool, the Poco logo is displayed and the phone restarts and the Poco logo is displayed again. All the time.
So I followed your instructions.
I would like to flash ArrowOS, but nowhere do they write what version of MIUI I need. That's why I flashed this version of MIUI through Mi Flash Tool: https://xiaomifirmwareupdater.com/miui/surya/stable/V12.0.8.0.QJGMIXM/
After I flashed MIUI using Mi Flash Tool and then I booted into TWRP and installed the downloaded ArrowOS. After installation, I went to the Wipe section and deleted the Data. Then I restarted the phone to System. The Poco logo was displayed and after a while the phone booted into TWRP. So I don't know where the problem is. (Before ArrowOS flashed, the cell phone tried to boot into the system, the Poco logo was still displayed, and then the phone restarted.)
Click to expand...
Click to collapse
Again, when I say FORMAT, I meant formatting by typing ”yes".
Also, you haven't looked at the ArrowOS thread close enough, see:
{
"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"
}
It says latest R firmware, basically V12.0.7.0.RJGEUXM. Another point I mentioned is the fact that a recovery MIUI is flashable through TWRP/Orangefox and not Fastboot/Mi flash tool, It comes in a .zip archive.
Regarding returning to stock, have you tried booting into stock recovery after fastboot flash and factory resetting? That could work.

Okay, I downloaded this ROM: https://xiaomifirmwareupdater.com/miui/surya/stable beta/V12.0.7.0.RJGEUXM/
I tried it to install it in TWRP and I got error 1:
I'm using TWRP 3.5.2_10-1-surya.

DrakMC said:
Okay, I downloaded this ROM: https://xiaomifirmwareupdater.com/miui/surya/stable beta/V12.0.7.0.RJGEUXM/
I tried it to install it in TWRP and I got error 1:
View attachment 5307411
I'm using TWRP 3.5.2_10-1-surya.
Click to expand...
Click to collapse
Error 1 just means a mismatch between the underlying stock and the newly flashed ROM, just ignore it and flash ArrowOS, Format data and reboot. If it still doesn't work, then return to stock through fastboot. (I never encountered so many problems as you did)

I followed your instructions. When I turn on smartphone, the Poco logo is displayed, then the ArrowOS animation will appear and freezes. After a while, the mobile phone restarts and this is repeated over and over again. (If I flash MIUI using the Mi Flash Tool, I also have a bootloop.)

I finally fixed the bootloop!
It was enough to take persist.img and flash it in TWRP before flashing MIUI via Mi Flash Tool.
Thank you very much everyone for your help!

just logged to thank u, mine was bricked too since an unsuccessful downgrade try, and I forgot to disable lock option in MiFlash, so I needed to wait 1 week to unlock bootloader again. I've tried everything, but ur post have saved me. ty very much for ur help, this tip can help a lot of ppl in the future. have a great weekend!

sevachcomunist4 said:
just logged to thank u, mine was bricked too since an unsuccessful downgrade try, and I forgot to disable lock option in MiFlash, so I needed to wait 1 week to unlock bootloader again. I've tried everything, but ur post have saved me. ty very much for ur help, this tip can help a lot of ppl in the future. have a great weekend!
Click to expand...
Click to collapse
You're welcome! I'm glad I could help someone! It took me about 40+ hours to resolve this issue before trying all possible methods.

DrakMC said:
I finally fixed the bootloop!
It was enough to take persist.img and flash it in TWRP before flashing MIUI via Mi Flash Tool.
Thank you very much everyone for your help!
Click to expand...
Click to collapse
please give me link

DrakMC said:
I finally fixed the bootloop!
It was enough to take persist.img and flash it in TWRP before flashing MIUI via Mi Flash Tool.
Thank you very much everyone for your help!
Click to expand...
Click to collapse
You literally saved my life bro. Why??? Flashed 30 times from fastboot and nothing. Just did what you said and phone booted smooth like a charm.

DP FH said:
You literally saved my life bro. Why??? Flashed 30 times from fastboot and nothing. Just did what you said and phone booted smooth like a charm.
Click to expand...
Click to collapse
You are welcome. I'm glad I could help someone.
I was whole week without the phone until I've fixed it. It took me over 40 hours to fix the issue.

[RECOVERY][UNOFFICIAL]TWRP Recovery Project 3.5.2 Micromax IN 1 (E6746)

{
"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"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
*/Your warranty is now void.
We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or recoverys, kernels.
You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers./*
Click to expand...
Click to collapse
FLASH GUIDE
1. Unlocked your bootloader
2. Download twrp-3.5.2-e6746.img
3. Run this Following commands
1. adb reboot bootloader
2. fastboot --disable--verification flash vbmeta vbmeta.img
3. fastboot flash recovery twrp-3.5.2-e6746.img
4. fastboot reboot recovery
Click to expand...
Click to collapse
DOWNLOAD
Device Tree
Working
• Decryption
• fastbootd
• MTP & ADB
Bugs
• spam me in support group
• Tell me
Support group
• here
Credits
• TEAM WIN FOR TWRP
• @ZanGhoul in TG
• and @uknowndevice in TG

where is vbmeta.img
I am trying to backup stock recovery using
fastboot boot <recoveryname>.img
says ok but boots to stock recovery not TWRP.

sieger007 said:
where is vbmeta.img
I am trying to backup stock recovery using
fastboot boot <recoveryname>.img
says ok but boots to stock recovery not TWRP.
Click to expand...
Click to collapse
Much better fastboot flash twrp.img, but if you backup stock recovery, just try to pull it via adb

ok I dont have root. How can I backup recovery and other partitons without root

sieger007 said:
ok I dont have root. How can I backup recovery and other partitons without root
Click to expand...
Click to collapse
Try, reboot to recovery mode if, pc read your device adb pull /dev/block/by-name/recovery

mastersenpai05 said:
Try, reboot to recovery mode if, pc read your device adb pull /dev/block/by-name/recovery
Click to expand...
Click to collapse
that is the problem
fastboot boot recovery does not boot to TWRP & I dont have root - I am stuck

if I could temporarily install any custom recovery - problem is solved - Nandroid backup and adb pull. Problem is it keeps going back to stock recovery & i dont want to flash TWRP unless I back up stock recovery. Any thoughts ?

sieger007 said:
if I could temporarily install any custom recovery - problem is solved - Nandroid backup and adb pull. Problem is it keeps going back to stock recovery & i dont want to flash TWRP unless I back up stock recovery. Any thoughts ?
Click to expand...
Click to collapse
Yeah, stock rom issue need to root sir, but I will fix it sir.

sieger007 said:
if I could temporarily install any custom recovery - problem is solved - Nandroid backup and adb pull. Problem is it keeps going back to stock recovery & i dont want to flash TWRP unless I back up stock recovery. Any thoughts ?
Click to expand...
Click to collapse
Not in stock firmware sir? The stoc recovery.img?

mastersenpai05 said:
Not in stock firmware sir? The stoc recovery.img?
Click to expand...
Click to collapse
I meant I tried .... fastboot boot <thisTWRPfile>.img after running vmeta and it will still boot into stock recovery. If I boot in stock recovery - adb shell will not run cos stock recovery does not support it. Problem is there isnt so far stock firmware available , so if I mess up and no backup - I have to run to service center and more $

sieger007 said:
I meant I tried .... fastboot boot <thisTWRPfile>.img after running vmeta and it will still boot into stock recovery. If I boot in stock recovery - adb shell will not run cos stock recovery does not support it. Problem is there isnt so far stock firmware available , so if I mess up and no backup - I have to run to service center and more $
Click to expand...
Click to collapse
MICROMAX IN 1 E6746 http://mtk-p.micromaxinfo.com/product/E6746/Software/India/MMX_E6746_SW_V10.0._HW_V1.0_20210416.zip

mastersenpai05 said:
MICROMAX IN 1 E6746 http://mtk-p.micromaxinfo.com/product/E6746/Software/India/MMX_E6746_SW_V10.0._HW_V1.0_20210416.zip
Click to expand...
Click to collapse
thanks i will check it out. Just wanted to check if this TWRP support USB OTG.Want to transfer Nandroid backup to FLash Drive

sieger007 said:
thanks i will check it out. Just wanted to check if this TWRP support USB OTG.Want to transfer Nandroid backup to FLash Drive
Click to expand...
Click to collapse
Yes sir, I want to know that too. Not yet try but try to check then tell me

TWRP installed fine . OTG works. Now the other 3 letter problem .....OTA.
I got notification that update is available. It wont install via TWRP.
How do I install OTA. wrt THis guide .... this phone does not seem to fit ( this isn't A/B phone type A phone ) . WHat do I do ? restore stock recovery and boot and then restore TWRP and boot.patch.img ? Any clue ?

sieger007 said:
TWRP installed fine . OTG works. Now the other 3 letter problem .....OTA.
I got notification that update is available. It wont install via TWRP.
How do I install OTA. wrt THis guide .... this phone does not seem to fit ( this isn't A/B phone type A phone ) . WHat do I do ? restore stock recovery and boot and then restore TWRP and boot.patch.img ? Any clue ?
Click to expand...
Click to collapse
I don't think so if possible to use twrp in ota update, but you can use twrp for flashing recovery rom ( stock recovery rom)

mastersenpai05 said:
I don't think so if possible to use twrp in ota update, but you can use twrp for flashing recovery rom ( stock recovery rom)
Click to expand...
Click to collapse
I don't know what are the exact criteria for successful OTA update from a vague idea I think it check whether there is original boot and recovery image otherwise says no
in that case would flashing this DM verify no encrypt module remove this checking and after installing this we should be able to to install periodic OTA updates
or as a long-term procedure every time I have to install OTA I have to restore original boot and recovery or should I just restore recovery

as follow up - I could install OTA by restoring stock r'y . There isn't a need to restore boot. You can keep it this way or else if TWRP is restored the same proc ought to repeat before the next OTA.
I am attaching stock boot and recoveries here in case they could be of use.
Boot-recovery--mmx1

sieger007 said:
as follow up - I could install OTA by restoring stock r'y . There isn't a need to restore boot. You can keep it this way or else if TWRP is restored the same proc ought to repeat before the next OTA.
I am attaching stock boot and recoveries here in case they could be of use.
Boot-recovery--mmx1
Click to expand...
Click to collapse
Nice thank you so much! You can also join in micromax in 1 group in telegram

Update : it never worked. I thought it did but that update notice sprung and it wanted to do it all over again. I restored stock recovery. No Luck OTA's keep failing. I then restored stock Boot after removing magisk . Still got veriification error. My BL is unlocked. What does it take to get my OTA zip file working.... do I flash dm verify force encrypt . Why does it refuse. Should BL be locked as well anyone have luck push OTA update after rooting IN 1

Do you have kernel source code