I wanted to remove root, tried following some guides and so I came upon trying to uninstall magisk. I was prompted with two choices, "Restore images" and "Complete Uninstall".
I tried out Restore images first and it said "stock backup does not exist" so I then proceeded to do a complete uninstall. I got stuck then in recovery mode bootloop.
I therefore tried to go to my recovery by turning off my phone first and now it's in this perpetual charging state, I removed the connector but it's still "charging". Forcing it to turn off by holding the power button doesn't work 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"
}
I was scared of root so I tried removing it since it was rooted when I got it, but now here I am :crying::crying::crying: please help.
Thank you very much.
Try power button + Volume down for up to 10 seconds.....should shutdown and reboot after a few seconds of shutdown
(Meaning, it will shutdown and appear to just be off.....but it will actually start to reboot after a few seconds of nothing.....so be prepared/ready to do the button mash to boot to recovery......it will vibrate once as it begins to boot again....
*****edit.....
Sorry I'm in the wrong thread (different phone), but its possible you need to press and hold power plus volume up/or volume down.
Best of luck
Sent from my [device_name] using XDA-Developers Legacy app
Thank you for the suggestion, but sadly for me it doesn't work. My phone doesn't shutdown at all and is just in this perpetual charging state even after holding the power button for 30 seconds.
Hanzor said:
I wanted to remove root, tried following some guides and so I came upon trying to uninstall magisk. I was prompted with two choices, "Restore images" and "Complete Uninstall".
I tried out Restore images first and it said "stock backup does not exist" so I then proceeded to do a complete uninstall. I got stuck then in recovery mode bootloop.
I therefore tried to go to my recovery by turning off my phone first and now it's in this perpetual charging state, I removed the connector but it's still "charging". Forcing it to turn off by holding the power button doesn't work as well.
I was scared of root so I tried removing it since it was rooted when I got it, but now here I am :crying::crying::crying: please help.
Thank you very much.
Click to expand...
Click to collapse
Which rom version are you on? You need to boot into fastboot mode abs flash the same stock boot img. I may well have it to hand in my cloud folder. Lemme know the version, hopefully all will be well again
reg66 said:
Which rom version are you on? You need to boot into fastboot mode abs flash the same stock boot img. I may well have it to hand in my cloud folder. Lemme know the version, hopefully all will be well again
Click to expand...
Click to collapse
Is the rom like the OS version? I'm not sure but I have this RAW file in my pc. My uncle said to leave it here just in case, it's called "WW_ZS660KL_16.0631.1910.35_M3.13.33.30". I also have this "root&bootstockww191035.zip" file so maybe the 191035 is my OS version? If I remember correctly he said the phone is chinese and he had to do stuff to make it english.
It's either that or Android 9.0.
Hanzor said:
Is the rom like the OS version? I'm not sure but I have this RAW file in my pc. My uncle said to leave it here just in case, it's called "WW_ZS660KL_16.0631.1910.35_M3.13.33.30". I also have this "root&bootstockww191035.zip" file so maybe the 191035 is my OS version? If I remember correctly he said the phone is chinese and he had to do stuff to make it english.
It's either that or Android 9.0.
Click to expand...
Click to collapse
Oh, you need to be quite sure as the boot img needs to match the rom. When it was rooted do you remember ever updating it? I should have 1910.35 boot img hopefully, I'll check in a mo
reg66 said:
Oh, you need to be quite sure as the boot img needs to match the rom. When it was rooted do you remember ever updating it? I should have 1910.35 boot img hopefully, I'll check in a mo
Click to expand...
Click to collapse
I've never gotten to update it, I see other people have android 10 and such but mine doesn't see the update so I just left it be. Should be the same as when I got it.
Hanzor said:
I've never gotten to update it, I see other people have android 10 and such but mine doesn't see the update so I just left it be. Should be the same as when I got it.
Click to expand...
Click to collapse
OK, I'll be in soon, will have a hunt :good:
---------- Post added at 10:57 AM ---------- Previous post was at 10:10 AM ----------
Hanzor said:
I've never gotten to update it, I see other people have android 10 and such but mine doesn't see the update so I just left it be. Should be the same as when I got it.
Click to expand...
Click to collapse
Here's the link for both root and stock boot img's 1910.35_root and stock_imgs
Are you ok with the process or do you need guidance?
reg66 said:
OK, I'll be in soon, will have a hunt :good:
---------- Post added at 10:57 AM ---------- Previous post was at 10:10 AM ----------
Here's the link for both root and stock boot img's 1910.35_root and stock_imgs
Are you ok with the process or do you need guidance?
Click to expand...
Click to collapse
I'm not very familiar with how it works, if it's okay I would be glad to be guided.
Hanzor said:
I'm not very familiar with how it works, if it's okay I would be glad to be guided.
Click to expand...
Click to collapse
That's no problem, but I've been awake now for 2 days straight. I really can't focus on anything right now. Maybe later tonight or tomorrow. Sorry dude
reg66 said:
That's no problem, but I've been awake now for 2 days straight. I really can't focus on anything right now. Maybe later tonight or tomorrow. Sorry dude
Click to expand...
Click to collapse
That's alright, I'm fine with later or tommorow as well. Rest well, and thanks!
reg66 said:
That's no problem, but I've been awake now for 2 days straight. I really can't focus on anything right now. Maybe later tonight or tomorrow. Sorry dude
Click to expand...
Click to collapse
Hey man, hope you got to rest well! Here with just a fair bit of inquiry.
So, today I've tried looking for guides on sideloading. Got my phone to bootloader as well by depleting the battery then charging it up to be able to boot into bootloader.
I got my phone then to fastboot using the adb method, my device was recognized in the adb devices command as well. The problem is, fastboot devices don't show up any results. I'm scared to worsen the problem so I didn't continue past this point.
I could see my device in the device manager as well.
Am I on the right track?
Hanzor said:
Hey man, hope you got to rest well! Here with just a fair bit of inquiry.
So, today I've tried looking for guides on sideloading. Got my phone to bootloader as well by depleting the battery then charging it up to be able to boot into bootloader.
I got my phone then to fastboot using the adb method, my device was recognized in the adb devices command as well. The problem is, fastboot devices don't show up any results. I'm scared to worsen the problem so I didn't continue past this point.
I could see my device in the device manager as well.
Am I on the right track?
Click to expand...
Click to collapse
Hey dude, so sorry for the late reply, so damn tired!! You may well now be aware of some of this etc but I'll post any way so it's all there...
1. Download and install Minimal ADB and Fastboot app (windows). Install it on your PC to root of C drive
2. Download the root&bootstockww191035.zip and extract it to the Minimal ADB and Fastboot Folder (C:\Program Files (x86)\Minimal ADB and Fastboot) from here
3. Boot into fastboot mode ( from powered off, hold volume up then press and hold power button. Fastboot mode is the 1st screen you come across, the one with the options to Start, boot to recovery, etc...)
4. Still in fastboot mode, connect phone to pc using side port on phone.
5. Go to C:\Program Files (x86)\Minimal ADB and Fastboot and double click cmd-here.exe
6. Check your device is recognised in fastboot mode by the pc/laptop by typing 'fastboot devices' in cmd window. If it is recognised you will see a string of numbers and/or letters.
7. Type 'fastboot flash boot boot.img' in cmd window.
That's it, you should now have the correct boot img for your device flashed and hopefully it'll boot up again.
Good luck
reg66 said:
Hey dude, so sorry for the late reply, so damn tired!! You may well now be aware of some of this etc but I'll post any way so it's all there...
1. Download and install Minimal ADB and Fastboot app (windows). Install it on your PC to root of C drive
2. Download the root&bootstockww191035.zip and extract it to the Minimal ADB and Fastboot Folder (C:\Program Files (x86)\Minimal ADB and Fastboot) from here
3. Boot into fastboot mode ( from powered off, hold volume up then press and hold power button. Fastboot mode is the 1st screen you come across, the one with the options to Start, boot to recovery, etc...)
4. Still in fastboot mode, connect phone to pc using side port on phone.
5. Go to C:\Program Files (x86)\Minimal ADB and Fastboot and double click cmd-here.exe
6. Check your device is recognised in fastboot mode by the pc/laptop by typing 'fastboot devices' in cmd window. If it is recognised you will see a string of numbers and/or letters.
7. Type 'fastboot flash boot boot.img' in cmd window.
That's it, you should now have the correct boot img for your device flashed and hopefully it'll boot up again.
Good luck
Click to expand...
Click to collapse
Thanks for the time man, hopefully it does work.
Edit: IT WORKS!
Had a few hiccups which was fixed by disconnecting and reconnecting the cable after going into fastboot.
THANK YOU!
Seriously, THANK YOU!
Please have a good rest, and take care!
Hanzor said:
Thanks for the time man, hopefully it does work.
Edit: IT WORKS!
Had a few hiccups which was fixed by disconnecting and reconnecting the cable after going into fastboot.
THANK YOU!
Seriously, THANK YOU!
Please have a good rest, and take care!
Click to expand...
Click to collapse
Excellent. Glad it's all good again :good:
Related
Hello,
I while ago I decided to root my HTC to get some extra stuff. I used a guide on youtube that seemed to be reasonably well made and followed everystep of the process. But before I could root it I had to unlock the bootloader and install TWRP recovery. I got the latest version and proceeded to the next step, where I encountered my problem. After flashing the recovery everything seemed to be well except that my phone wasn't actually rooted. I decided to redo some of the last steps. This is where things get a bit tricky. I have done this quite a while ago (maybe 3-4 months) and don't exactly remember the steps that I repeated but I think I've also flashed TWRP a second time, as well as some other steps. And when it came to the part where I needed to use the recovery I found out that the recovery doesn't work. I can't press anything on the screen, I can however press the lock button and lock the device but when the *slide to unlock* appears it stops working again. I was running out of time and decided to leave it for another time but time has passed and I never really got the time to tinker with it any more since university started and I'm more busy then ever. This has left me with no ability to root or even update my phone.
This brings me to today, when I restored my phone completely forgetting what has happened. It got back to Android 4.1 and I can't do anything about it.
I hope to sort this out and finally root the phone. But even getting rid of TWRP to the original recovery so I could just update my phone would be very helpfull.
Thank you very much.
aleks945 said:
Hello,
I while ago I decided to root my HTC to get some extra stuff. I used a guide on youtube that seemed to be reasonably well made and followed everystep of the process. But before I could root it I had to unlock the bootloader and install TWRP recovery. I got the latest version and proceeded to the next step, where I encountered my problem. After flashing the recovery everything seemed to be well except that my phone wasn't actually rooted. I decided to redo some of the last steps. This is where things get a bit tricky. I have done this quite a while ago (maybe 3-4 months) and don't exactly remember the steps that I repeated but I think I've also flashed TWRP a second time, as well as some other steps. And when it came to the part where I needed to use the recovery I found out that the recovery doesn't work. I can't press anything on the screen, I can however press the lock button and lock the device but when the *slide to unlock* appears it stops working again. I was running out of time and decided to leave it for another time but time has passed and I never really got the time to tinker with it any more since university started and I'm more busy then ever. This has left me with no ability to root or even update my phone.
This brings me to today, when I restored my phone completely forgetting what has happened. It got back to Android 4.1 and I can't do anything about it.
I hope to sort this out and finally root the phone. But even getting rid of TWRP to the original recovery so I could just update my phone would be very helpfull.
Thank you very much.
Click to expand...
Click to collapse
The background information is helpful but you have given us nothing to go on.
Post a fastboot getvar all except remove the imei and serialno?
What are you trying to accomplish? Return to Stock? S-OFF?
majmoz said:
The background information is helpful but you have given us nothing to go on.
Post a fastboot getvar all except remove the imei and serialno?
What are you trying to accomplish? Return to Stock? S-OFF?
Click to expand...
Click to collapse
Tell me what background information do you need and I'll get everything.
The goal is to get a working recovery, which ever one it would be I don't really care. I just want to be able to update the firmware.
reboot into the bootloader. flash the latest twrp for your device using fastboot flash recovery recoverynamehere.zip
profit
jdgreat4 said:
reboot into the bootloader. flash the latest twrp for your device using fastboot flash recovery recoverynamehere.zip
profit
Click to expand...
Click to collapse
If you could give me a more detailed guide I would toatally do that, because I'm pretty noobish when it comes to this kind of stuff.
aleks945 said:
Tell me what background information do you need and I'll get everything.
The goal is to get a working recovery, which ever one it would be I don't really care. I just want to be able to update the firmware.
Click to expand...
Click to collapse
like he said before, post the output of "fastboot getvar all" except your IMEI and SERIALNO
---------- Post added at 11:06 AM ---------- Previous post was at 11:05 AM ----------
aleks945 said:
If you could give me a more detailed guide I would toatally do that, because I'm pretty noobish when it comes to this kind of stuff.
Click to expand...
Click to collapse
do you have adb and fastboot on your computer?
Do you have HTC drivers installed?
alray said:
like he said before, post the output of "fastboot getvar all" except your IMEI and SERIALNO
---------- Post added at 11:06 AM ---------- Previous post was at 11:05 AM ----------
do you have adb and fastboot on your computer?
Do you have HTC drivers installed?
Click to expand...
Click to collapse
I don't know what adb is, sorry. And no I don't, I had to do everything on my friend's laptop because it didn't seem to work on my machine (W8.1 compared to his W7).
Edit. But I do have acces to it pretty much all the time.
aleks945 said:
I don't know what adb is, sorry. And no I don't, I had to do everything on my friend's laptop because it didn't seem to work on my machine (W8.1 compared to his W7).
Click to expand...
Click to collapse
yes better to use windows 7
go ahead and download adb and fastboot from here: http://forum.xda-developers.com/showthread.php?t=2317790
download and install HTC sync from here: http://www.htc.com/us/support/software/htc-sync-manager.aspx
Once installed, uninstall HTC sync but keep the drivers installed
post back when done
alray said:
yes better to use windows 7
go ahead and download adb and fastboot from here: http://forum.xda-developers.com/showthread.php?t=2317790
download and install HTC sync from here: http://www.htc.com/us/support/software/htc-sync-manager.aspx
Once installed, uninstall HTC sync but keep the drivers installed
post back when done
Click to expand...
Click to collapse
The downloads are complete, just waiting on the instalation. The computer is quite old and slow unfortunatelly.
Thank you again
EDIT. Everything is done.
aleks945 said:
The downloads are complete, just waiting on the instalation. The computer is quite old and slow unfortunatelly.
Thank you again
EDIT. Everything is done.
Click to expand...
Click to collapse
ok so connect your phone with he usb cable to the computer, reboot it in bootloader mode (hold power and vol -). in bootloader select "fastboot"
then lauch the adb command prompt and type "fastboot getvar all". post the output here but edit out the imei and serialno before.
alray said:
ok so connect your phone with he usb cable to the computer, reboot it in bootloader mode (hold power and vol -). in bootloader select "fastboot"
then lauch the adb command prompt and type "fastboot getvar all". post the output here but edit out the imei and serialno before.
Click to expand...
Click to collapse
Here it is.
{
"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"
}
Link since image seems to be really tiny.
http://i.imgur.com/9cZZRA9.jpg
aleks945 said:
Here it is.
Link since image seems to be really tiny.
http://i.imgur.com/9cZZRA9.jpg
Click to expand...
Click to collapse
you can flash twrp 2.6.3.3
download the file and save it in the same folder where you have installed minimal adb and fastboot
then open the command prompt and with the phone in bootloader/fastboot mode enter these commands:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
What do you want to achieve then? Custom rooted rom? stock rooted rom (latest version)? or you simply what to root the rom you currently have?
alray said:
you can flash twrp 2.6.3.3
download the file and save it in the same folder where you have installed minimal adb and fastboot
then open the command prompt and with the phone in bootloader/fastboot mode enter these commands:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
What do you want to achieve then? Custom rooted rom? stock rooted rom (latest version)? or you simply what to root the rom you currently have?
Click to expand...
Click to collapse
Latest stock rooted ram would be the final goal.
aleks945 said:
Latest stock rooted ram would be the final goal.
Click to expand...
Click to collapse
you can flash this rom: http://www.androidrevolution.org/downloader/download.php?file=One_6.09.401.5_odexed.zip
its the stock rom for 6.09.401.5
alray said:
you can flash this rom: http://www.androidrevolution.org/downloader/download.php?file=One_6.09.401.5_odexed.zip
its the stock rom for 6.09.401.5
Click to expand...
Click to collapse
Doesn't my phone have to be rooted to be able to instal another rom?
aleks945 said:
Doesn't my phone have to be rooted to be able to instal another rom?
Click to expand...
Click to collapse
no just flash the rom from twrp recovery then you can root it if you want.
hello, I'm kinda desperate on installing recoveries on my phone
I'm following this guide over here
USB debugging mode is turned on, but it is not detected on the shell/command window
when I checked my device manager, my device driver is not found, I tried installing flash tool drivers, but I dunno where to search for these drivers, so I followed the way in this thread
and I found 4 drivers in the list:
- Android ADB interface
- Sony ADB interface
- Sony Composite ADB interface
- Sony Fastboot Interface
tried all the ADB interface but still give same result so I uninstalled the driver back to the way it was
Please help me as I'm really newbie at this and I wanna try Stryflex ROM, thanks
Note:
1. I already unlocked my bootloader, but someone in here said to unlock bootloader first so I assume that it will end the same way as LB
2. The error I received from the command window is "device not found"
3. Phone version C3502
4. currently still using stock ROM with 12.1.A.1.207 firmware, rooted with towelroot
5. I unlock the bootloader using the step on sony site
Bump, pls help anyone?
Sent from my C5302 using Tapatalk
Please explain to me what you are actually wanting to do?
TechnoSparks said:
Please explain to me what you are actually wanting to do?
Click to expand...
Click to collapse
I'm trying to install recoveries to my device, but the CWM tools on the link I gave above didn't detect my device
daryula said:
I'm trying to install recoveries to my device, but the CWM tools on the link I gave above didn't detect my device
Click to expand...
Click to collapse
I strongly advise for you to START with another way and also use TWRP as a default recovery. CWM (and inherently PhilZ) are very old unsupported recoveries.
If you insist, you might want to install DoomLord's driver pack and try again: http://forum.xda-developers.com/showthread.php?t=2635830
If you wish to follow my method, please follow this link: http://forum.xda-developers.com/showpost.php?p=64449411&postcount=4
TechnoSparks said:
I strongly advise for you to START with another way and also use TWRP as a default recovery. CWM (and inherently PhilZ) are very old unsupported recoveries.
If you insist, you might want to install DoomLord's driver pack and try again: http://forum.xda-developers.com/showthread.php?t=2635830
If you wish to follow my method, please follow this link: http://forum.xda-developers.com/showpost.php?p=64449411&postcount=4
Click to expand...
Click to collapse
Ok i will try your method, thanks
Sent from my C5302 using Tapatalk
daryula said:
Ok i will try your method, thanks
Sent from my C5302 using Tapatalk
Click to expand...
Click to collapse
Do report your findings
Also how did you post from tapatalk on C5302? Is it another SP?
TechnoSparks said:
Do report your findings
Also how did you post from tapatalk on C5302? Is it another SP?
Click to expand...
Click to collapse
Nope, this is my only device
Like i said, i cant install recoveries like what the tutorial above said because it's not detected
Hence i cannot proceed to other thing because of the fear of me failing to install cusrom
If i can install recoveries, i can backup (CMIIW) and it's at least reassuring me to do other things, this is my first time doing this so knowing nothing makes me confused and a bit terrified of I fail
Sent from my C5302 using Tapatalk
daryula said:
Nope, this is my only device
Like i said, i cant install recoveries like what the tutorial above said because it's not detected
Hence i cannot proceed to other thing because of the fear of me failing to install cusrom
If i can install recoveries, i can backup (CMIIW) and it's at least reassuring me to do other things, this is my first time doing this so knowing nothing makes me confused and a bit terrified of I fail
Sent from my C5302 using Tapatalk
Click to expand...
Click to collapse
So you're on stock ROM, i believe?
TechnoSparks said:
So you're on stock ROM, i believe?
Click to expand...
Click to collapse
yes I'm on stock rom, but I have root access and unlocked bootloader
daryula said:
yes I'm on stock rom, but I have root access and unlocked bootloader
Click to expand...
Click to collapse
Alright then my link before would definitely help you out
TechnoSparks said:
Alright then my link before would definitely help you out
Click to expand...
Click to collapse
the fastboot tools stated is the same fastboot tool used for unlocking the bootloader, am I right?
also do I need to put the img file on the same folder as the fastboot tools?
daryula said:
the fastboot tools stated is the same fastboot tool used for unlocking the bootloader, am I right?
also do I need to put the img file on the same folder as the fastboot tools?
Click to expand...
Click to collapse
yes, and yes.
You can also point to the absolute path of the img file, but that would be complicated so copying would be easier. (welcome to the world of consoles (not the game consoles (command prompt)))
TechnoSparks said:
yes, and yes.
You can also point to the absolute path of the img file, but that would be complicated so copying would be easier. (welcome to the world of consoles (not the game consoles (command prompt)))
Click to expand...
Click to collapse
I got this notification
{
"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"
}
should be an okay I guess?
thanks for the help
@TechnoSparks I think I got another problem now
I can't seem to reboot into system after I do full backup, it just shows black screen
what should I do?
I haven't done anything aside from doing backup
daryula said:
@TechnoSparks I think I got another problem now
I can't seem to reboot into system after I do full backup, it just shows black screen
what should I do?
I haven't done anything aside from doing backup
Click to expand...
Click to collapse
Can you explain everything, as if you're telling a story, in a chronological order? Remember, explain verbosely!
I need to sleep right now, hopefully i would able to reply to you in the next morning when i got enough information
Also, in the "hide" section of your previous post, there is nothing from inside..
TechnoSparks said:
Can you explain everything, as if you're telling a story, in a chronological order? Remember, explain verbosely!
I need to sleep right now, hopefully i would able to reply to you in the next morning when i got enough information
Also, in the "hide" section of your previous post, there is nothing from inside..
Click to expand...
Click to collapse
firstly I do install TWRP according to your guide over there using fastboot tools
the one with this command
Code:
fastboot flash boot twrp.img
then it shows message like this
http://www.iforce.co.nz/View.aspx?i=ivkcgknl.fyl.png
I then restart my device normally and it boots into recovery mode, in which then I make backup by selecting all the option to my external card, and proceed to reboot after it's done
it returns me to TWRP once again, and I reboot using "reboot system", it shows sony logo and then black screen for a few minutes, and I got sent back to TWRP once more, I've tried "reboot bootloader" menu too and the same result, I've repeat this for a lot of times and still same result pops out
sorry to bother you this late night and have a nice sleep
daryula said:
firstly I do install TWRP according to your guide over there using fastboot tools
the one with this command
Code:
fastboot flash boot twrp.img
then it shows message like this
http://www.iforce.co.nz/View.aspx?i=ivkcgknl.fyl.png
I then restart my device normally and it boots into recovery mode, in which then I make backup by selecting all the option to my external card, and proceed to reboot after it's done
it returns me to TWRP once again, and I reboot using "reboot system", it shows sony logo and then black screen for a few minutes, and I got sent back to TWRP once more, I've tried "reboot bootloader" menu too and the same result, I've repeat this for a lot of times and still same result pops out
sorry to bother you this late night and have a nice sleep
Click to expand...
Click to collapse
Oh i thought you were ready for flashing Stryflex!
Anyway the reason why it booted to the TWRP repeatedly is because of the reason that you flashed a recovery into the boot partition. Please re-read carefully the page that I linked you to
Anyway to boot back to your stock ROM, get yourself a "boot" stock component from this page: http://forum.xda-developers.com/showpost.php?p=62447987&postcount=3
Flash it in the TWRP
sorry for the trouble.
TechnoSparks said:
Oh i thought you were ready for flashing Stryflex!
Anyway the reason why it booted to the TWRP repeatedly is because of the reason that you flashed a recovery into the boot partition. Please re-read carefully the page that I linked you to
Anyway to boot back to your stock ROM, get yourself a "boot" stock component from this page: http://forum.xda-developers.com/showpost.php?p=62447987&postcount=3
Flash it in the TWRP
sorry for the trouble.
Click to expand...
Click to collapse
I forgot to put the rom to my SD card and I don't have card reader
what to do with the files?
oh nvm, I somehow managed to learn how to move my files via adb command
thanks again for your help
New issue: Live support team helped me flash my device back to stock. And I resume my day.
Eventually notification notified me of an update downloaded and I agree to install, and then it bootlooped on me.
What luck. Anyway what should I do now, technically my system wasn't wiped like before so I should have more options right?
boot into fastboot and flash all the .img files (except persist and recovery) found here https://build.nethunter.com/misc/oneplus3T/partitions/
make sure the files are in the same folder adb is in
the commands are
fastboot flash boot boot.img
fastboot flash system system.img
nicksmizzle said:
boot into fastboot and flash all the .img files (except persist and recovery) found here https://build.nethunter.com/misc/oneplus3T/partitions/
make sure the files are in the same folder adb is in
the commands are
fastboot flash boot boot.img
fastboot flash system system.img
Click to expand...
Click to collapse
Even if I had USB debugging turned off and no OS?
edit: I didn't realize two of those file were 3GB, that said do I flash system and system sparse? Those are system-sized flashes are those two different systems?
And is there a flashing order?
Ivalicenyan said:
Even if I had USB debugging turned off and no OS?
edit: I didn't realize two of those file were 3GB, that said do I flash system and system sparse? Those are system-sized flashes are those two different systems?
And is there a flashing order?
Click to expand...
Click to collapse
if you are in fastboot usb debugging is null. do boot and then system, don't worry about system sparse. boot and then system is the flashing order.
nicksmizzle said:
if you are in fastboot usb debugging is null. do boot and then system, don't worry about system sparse. boot and then system is the flashing order.
Click to expand...
Click to collapse
Do I assume dsp.img is another one I should ignore?
And: error: cannot load 'system.img'
Boot worked fine tho
Flash the stock recovery.img from that link. Then reboot into recovery. Select English, then Install from ADB. This will put you in ADB sideload. Then flash the full OTA zip by using the command adb sideload *name of the file*.
Sent from my OnePlus3T using XDA Labs
dustin_b said:
Flash the stock recovery.img from that link. Then reboot into recovery. Select English, then Install from ADB. This will put you in ADB sideload. Then flash the full OTA zip by using the command adb sideload *name of the file*.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
That sounds helpful but I'm not familiar with the commands.
But before I do, how sure are you will that work before I go for that? What I knew about flashing a new rom didn't help me due to an error, what nicksmizzle told me to do with flashing system in fastboot didn't work, what if tossing TWRP out the window and going back to stock just digs me even deeper in my hole?
Ivalicenyan said:
That sounds helpful but I'm not familiar with the commands.
But before I do, how sure are you will that work before I go for that? What I knew about flashing a new rom didn't help me due to an error, what nicksmizzle told me to do with flashing system in fastboot didn't work, what if tossing TWRP out the window and going back to stock just digs me even deeper in my hole?
Click to expand...
Click to collapse
It won't. The OTA's are made to be installed in stock recovery. You can check the OnePlus 3 community forums if you would like for more information. But installing the OTA on stock recovery is safe. And BTW, I have done it so I'm not just guessing or anything.
Sent from my OnePlus3T using XDA Labs
---------- Post added at 07:19 AM ---------- Previous post was at 07:14 AM ----------
Ivalicenyan said:
That sounds helpful but I'm not familiar with the commands.
But before I do, how sure are you will that work before I go for that? What I knew about flashing a new rom didn't help me due to an error, what nicksmizzle told me to do with flashing system in fastboot didn't work, what if tossing TWRP out the window and going back to stock just digs me even deeper in my hole?
Click to expand...
Click to collapse
Here's a video to kind of give you an idea of what to do. It's not the greatest but it's short. You will have to fastboot flash the stock recovery image first as the video doesn't cover that.
Sent from my OnePlus3T using XDA Labs
dustin_b said:
It won't. The OTA's are made to be installed in stock recovery. You can check the OnePlus 3 community forums if you would like for more information. But installing the OTA on stock recovery is safe. And BTW, I have done it so I'm not just guessing or anything.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
I went ahead and did that, but when I went to ADB sideload, my computer wouldn't recognize the device
and in cmd prompt it just says waiting on device
Ivalicenyan said:
I went ahead and did that, but when I went to ADB sideload, my computer wouldn't recognize the device
and in cmd prompt it just says waiting on device
Click to expand...
Click to collapse
What OS are you on ?
The command "adb devices" should give a device number as return, if not you may need to install an adb-driver on Win-Systems.
HTH,
Axel
s3axel said:
What OS are you on ?
The command "adb devices" should give a device number as return, if not you may need to install an adb-driver on Win-Systems.
HTH,
Axel
Click to expand...
Click to collapse
Windows 7, but don't I already have the drivers if I was able to install twrp or reflash stock recovery?
Also I did a google search but all im getting are adb drivers for nexus. Is there a generic one I can use somewhere?
Ivalicenyan said:
Windows 7, but don't I already have the drivers if I was able to install twrp or reflash stock recovery?
Click to expand...
Click to collapse
Well, when you are in adb sideload mode and the device is plugged in you should be able to see that in the Windows device manager. AFAIK the download mode (fastboot flashing) is different than adb mode and you may indeed need an adb-driver (just google it, its available quite easily on the web).
But before you do so: does "adb devices" return a device number ?
s3axel said:
Well, when you are in adb sideload mode and the device is plugged in you should be able to see that in the Windows device manager. AFAIK the download mode (fastboot flashing) is different than adb mode and you may indeed need an adb-driver (just google it, its available quite easily on the web).
But before you do so: does "adb devices" return a device number ?
Click to expand...
Click to collapse
Nope, thats what I implied in the 1st post without saying so, I said I ad no adb, as in no adb communication between my device and pc. I didnt think adb worked without usb debugging turned on because before I even created the thread I did over the flashing guide I used to install TWRP. devices didn't give me the serial like it did yesterday when I flashed twrp.
and I searched adb sideload opeplus 3 drivers and its just giving me oneplus i isntalled that came with the phone. Unless theres something specific I need, then im probably going to google the wrong thing
Ivalicenyan said:
Nope, thats what I implied in the 1st post without saying so, I said I ad no adb, as in no adb communication between my device and pc. I didnt think adb worked without usb debugging turned on because before I even created the thread I did over the flashing guide I used to install TWRP. devices didn't give me the serial like it did yesterday when I flashed twrp.
and I searched adb sideload opeplus 3 drivers and its just giving me oneplus i isntalled that came with the phone. Unless theres something specific I need, then im probably going to google the wrong thing
Click to expand...
Click to collapse
Sorry, misunderstood you there Well, I have recently used the download from this site for my OP3, so I hope it just works out
s3axel said:
Sorry, misunderstood you there Well, I have recently used the download from this site for my OP3, so I hope it just works out
Click to expand...
Click to collapse
Thanks for the drivers,.
says installation failed on the oneplus after 2-3 minutes
Ivalicenyan said:
Thanks for the drivers,. says installation failed on the oneplus after 2-3 minutes
Click to expand...
Click to collapse
Hmm, strange. Maybe you have a corrupt download ? Can you open the ZIP you downloaded in your first post with 7Zip or something alike ?
If the ZIP file seems fine (BTW, the one I downloaded has a MD5 checksum 0e2b4f9c7e7a1edf533f0d436ba48d95 - opens up OK for me but could not check flashing due to lack of OP3T ) it may help to follow along the instructions on factory resetting that can be found here. Just be careful, this is for OP3. #1 is already covered (given your downloaded ZIP is fine), #2 can be gotten from the link given in Post #2 in this thread.
Then you should hopefully have a clean basis to start from....
Cheers, Axel
s3axel said:
Hmm, strange. Maybe you have a corrupt download ? Can you open the ZIP you downloaded in your first post with 7Zip or something alike ?
If the ZIP file seems fine (BTW, the one I downloaded has a MD5 checksum 0e2b4f9c7e7a1edf533f0d436ba48d95 - opens up OK for me but could not check flashing due to lack of OP3T ) it may help to follow along the instructions on factory resetting that can be found here. Just be careful, this is for OP3. #1 is already covered (given your downloaded ZIP is fine), #2 can be gotten from the link given in Post #2 in this thread.
Then you should hopefully have a clean basis to start from....
Cheers, Axel
Click to expand...
Click to collapse
Got past step #5, it is recongnizing my serial is fastboot devices, but then I got to step #11
{
"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"
}
Ivalicenyan said:
Got past step #5, it is recongnizing my serial is fastboot devices, but then I got to step #11
Click to expand...
Click to collapse
OK, so far so good [emoji6] what happens if you type "adb devices" after that?
Gesendet von meinem SM-G935F mit Tapatalk
s3axel said:
OK, so far so good [emoji6] what happens if you type "adb devices" after that?
Gesendet von meinem SM-G935F mit Tapatalk
Click to expand...
Click to collapse
Ivalicenyan said:
Click to expand...
Click to collapse
It seems the daemon ist not running when first giving the command. As it should have started after the first command, what happens if you just repeat the "adb devices" for a second time?
Gesendet von meinem SM-G935F mit Tapatalk
Hello everybody please help me. I tried to Root my phone I unlocked the phone while getting help from “dreambo” then I unlocked the phone and download twrp recovery then when I tried to start phone it only showed me recovery menu sistem was not opening then tried to chech “dreambo” again then i saw a picture (picture 1) there I wrote “fastboot flash recovery boot.alpha.x.img” instead of “fastboot flash boot boot.alpha.x.img” and now phones recovery didnt open and become bootloop it shows logo then turn off (video 1) then i cant able to to put phone into “bootloader mode” . I know this phone doesn’t have stock rom how can i fix this phone ?
dreambo Thread: Root and TWRP 3.2.1 for Maze Alpha X 6/64
(picture 1)
{
"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"
}
(video 1)
video link: https://youtu.be/QYMCOQiExMg
Originally Posted
dreambo said:
I am almost sure that you have flashed the recovery image in the boot partition !
You have do that fastboot flash boot recovery.img instead of fastboot flash recovery recovery.img
To have your phone working, just flash the attached boot.img : fastboot flash boot boot.alpha.x.img
Click to expand...
Click to collapse
Edit: Way to solve Problem:
Stive very thanks to my friend after a long time I fixed the phone. In order to do UNBRICK phone download this from link and than put phone into charge than connect phone to computer with usb and open "Flash tool" program than add “MT6757_Android_scatterr.txt” file than put it “Frimware Upgrade” than download and wait until it finished.
Stive87 said:
Unbrick Maze Alpha X 6/64GB only phone is black screen and phone is total brick (format all partition).
https://drive.google.com/file/d/12t3MHsAWBlXyKm_ktJt9GKqZ9sOrFRVi/view
Rom is no official :
System : official rom for Maze Alpha B6/64GB . (! no update after - OTA !!),
boot, logo and recovery is normal (copy from original my phone).
Good luck.
Sorry for bad english, my french ^^
Click to expand...
Click to collapse
Stive87 said:
https://drive.google.com/file/d/12t3MHsAWBlXyKm_ktJt9GKqZ9sOrFRVi/view?usp=drivesdk
full rom V03 6/64GB Rom Ofifcial Stock
https://drive.google.com/file/d/1WjXKj8abnghy_OjfUW5TYkAppjWg0amH/view?usp=sharing
Click to expand...
Click to collapse
Thanks to everyone who helped!!
help please
rafaello21 said:
help please
Click to expand...
Click to collapse
Became interested in this phone since I found a 6/128 model for 160$. If fastboot is failing (maybe because of the different partition size?) I'd go with SPFlashTool: if I remember well phone only need to be swithed off when you start downloading the image, therefore it goes well with bootloping if you choose the right moment
matteo.de-leo said:
Became interested in this phone since I found a 6/128 model for 160$. If fastboot is failing (maybe because of the different partition size?) I'd go with SPFlashTool: if I remember well phone only need to be swithed off when you start downloading the image, therefore it goes well with bootloping if you choose the right moment
Click to expand...
Click to collapse
I bought it 170$ when it was on discount no matter what i do “bootloader mode” not works because of the error that i did and no one helps
rafaello21 said:
I bought it 170$ when it was on discount no matter what i do “bootloader mode” not works because of the error that i did and no one helps
Click to expand...
Click to collapse
That's exactly what I'm saying: SPFlashTool doesn't require your phone to be in fastboot mode, only to be switched of when you plug it in. I had the same problem with an Archos Sense 55S after treying to root it. I wasn't able to enter neither fastboot or recovery mode, therefore I flashed the stock rom with SPFT
matteo.de-leo said:
That's exactly what I'm saying: SPFlashTool doesn't require your phone to be in fastboot mode, only to be switched of when you plug it in. I had the same problem with an Archos Sense 55S after treying to root it. I wasn't able to enter neither fastboot or recovery mode, therefore I flashed the stock rom with SPFT
Click to expand...
Click to collapse
I would do it if i have Stock rom ? i am very disappointed because of bought this phone how is it possible that phone doesnt have stock rom is there any possibility to fix this without stock rom?
rafaello21 said:
I would do it if i have Stock rom i am very disappointed because of bought this phone how is it possible that phone doesnt have stock rom is there any possibility to fix this without stock rom?
Click to expand...
Click to collapse
Which model are you using, the 6/64 or the 6/128?
For the former you can use a TWRP Backup done by @dreambo in order to restore at least the boot and and recovery partition
https://forum.xda-developers.com/maze-alpha/development/recovery-twrp-3-2-1-maze-alpha-x-t3740575
while for the latter a link in this post (https://forum.xda-developers.com/maze-alpha/development/original-rom-t3720714) is given ( eventually as soon as my phone arrives I can dump the image):
Option 1) https://drive.google.com/drive/folde...ZyDQFgygsdkei2
Option 2) http://bit.ly/2GKcmYe
matteo.de-leo said:
Which model are you using, the 6/64 or the 6/128?
For the former you can use a TWRP Backup done by @dreambo in order to restore at least the boot and and recovery partition
https://forum.xda-developers.com/maze-alpha/development/recovery-twrp-3-2-1-maze-alpha-x-t3740575
while for the latter a link in this post (https://forum.xda-developers.com/maze-alpha/development/original-rom-t3720714) is given ( eventually as soon as my phone arrives I can dump the image):
Option 1) https://drive.google.com/drive/folde...ZyDQFgygsdkei2
Option 2) http://bit.ly/2GKcmYe
Click to expand...
Click to collapse
Hi, can i use this to restore my phone? And do you know how? I did a search in the web but didn't fin any solution.
ttl1982 said:
Hi, can i use this to restore my phone? And do you know how? I did a search in the web but didn't fin any solution.
Click to expand...
Click to collapse
Hi ttl1982, before giving an answer I should know what are we talking about. Is it the same phone? And which version? What is the current situation (bootlooping into TWRP, bootlooping into Android)? Even assuming we're still talking about the Maze Alpha X, there are still too much variables!
matteo.de-leo said:
Which model are you using, the 6/64 or the 6/128?
For the former you can use a TWRP Backup done by @dreambo in order to restore at least the boot and and recovery partition
https://forum.xda-developers.com/maze-alpha/development/recovery-twrp-3-2-1-maze-alpha-x-t3740575
while for the latter a link in this post (https://forum.xda-developers.com/maze-alpha/development/original-rom-t3720714) is given ( eventually as soon as my phone arrives I can dump the image):
Option 1) https://drive.google.com/drive/folde...ZyDQFgygsdkei2
Option 2) http://bit.ly/2GKcmYe
Click to expand...
Click to collapse
I have Maze Alpha X 6/64 model. If “bootloader mode” doesnt open how can i install ‘twrp’ ? About Thread article i read everything but my only problem is my phone dont open “bootloader mode”. And only solution is stock rom i think than you need SPFlashTool to install it. Maybe you know better than me how can i install “twrp” without opening “bootloader mode” ? I wrote above why this happened.
I click Power and Vol+ buttons as i show in the video phone turn of but doesn’t open “bootloader mode”
rafaello21 said:
I have Maze Alpha X 6/64 model. If “bootloader mode” doesnt open how can i install ‘twrp’ ? About Thread article i read everything but my only problem is my phone dont open “bootloader mode”. And only solution is stock rom i think than you need SPFlashTool to install it. Maybe you know better than me how can i install “twrp” without opening “bootloader mode” ? I wrote above why this happened.
I click Power and Vol+ buttons as i show in the video phone turn of but doesn’t open “bootloader mode”
Click to expand...
Click to collapse
No, even in the case you just want to boot into TWRP (and be able to use one of the backups provided in that post) you need to access fastboot mode. during bootlooping does your PC find the device with the "adb devices" command (namely, as soon as your phone boots up you'd spam this command via terminal)?
matteo.de-leo said:
Hi ttl1982, before giving an answer I should know what are we talking about. Is it the same phone? And which version? What is the current situation (bootlooping into TWRP, bootlooping into Android)? Even assuming we're still talking about the Maze Alpha X, there are still too much variables!
Click to expand...
Click to collapse
Hi, Thanks for your quick response. I will share some more info like you asked.
- Phone: Maze Alpha X
- Version: 6GB RAM/128GB Storage
- Current situation: It won't start at all (when connected to Windows PC i get the 'USB device not recognized' error, so it does see something)
My idea is the following:
- Install recovery with SPK flashtool
- Restore with backup (i have this from another thread) or the system dump.
The above does not work because i do not have the correct preloader file (so SPK flash tool does recognize the phone?).
ADB is not recognizing the phone, so it can't be done that way (as far as my knowledge goes).
I asked Maze several times to provide me the original rom but i get zero response, no matter on what channel i ask them.
matteo.de-leo said:
No, even in the case you just want to boot into TWRP (and be able to use one of the backups provided in that post) you need to access fastboot mode. during bootlooping does your PC find the device with the "adb devices" command (namely, as soon as your phone boots up you'd spam this command via terminal)?
Click to expand...
Click to collapse
I will try but phone turn off and one very quick. Is 1-2 seconds enough for doing what you are saying ? Twrp flash i have to do ? Is there any phone and have similar problem like this ? Can help with help of Video ? And i will try what you said and back to you thanks
ttl1982 said:
Hi, Thanks for your quick response. I will share some more info like you asked.
- Phone: Maze Alpha X
- Version: 6GB RAM/128GB Storage
- Current situation: It won't start at all (when connected to Windows PC i get the 'USB device not recognized' error, so it does see something)
I got this phone from my nephew. He broke it because he flashed the Maze Alpha (not X) 4GB RAM/64GB storage rom on it because he had TWRP bootloops.
My idea is the following:
- Install recovery with SPK flashtool
- Restore with backup (i have this from another thread) or the system dump.
The above does not work because i do not have the correct preloader file (so SPK flash tool does recognize the phone?).
ADB is not recognizing the phone, so it can't be done that way (as far as my knowledge goes).
I asked Maze several times to provide me the original rom but i get zero response, no matter on what channel i ask them.
Click to expand...
Click to collapse
I also wrote them several times about stock rom but they didn’t answer me i think company only think about money. Do we have to throw our phone to garbage because of one wrong thing ? What should i do ?
ttl1982 said:
My idea is the following:
- Install recovery with SPK flashtool
- Restore with backup (i have this from another thread) or the system dump.
Click to expand...
Click to collapse
Yes I was thinking the same. Eventually you do not need to install the recovery, restoring the bootloader should be enough: if the bootloader is already unlocked you can just boot into TWRP and from there restoring the backup previously copied into a SD card.
The above does not work because i do not have the correct preloader file (so SPK flash tool does recognize the phone?).
Click to expand...
Click to collapse
Why do you say you don't have the right one? Did SPFlashTool return you some error?
I asked Maze several times to provide me the original rom but i get zero response, no matter on what channel i ask them.
Click to expand...
Click to collapse
Well AFAIK Maze is completely done, no surprise if they do not answer. I'm reasonably sure that there's a way to dump these files from a working phone, if I'm right I'll try with mine
matteo.de-leo said:
No, even in the case you just want to boot into TWRP (and be able to use one of the backups provided in that post) you need to access fastboot mode. during bootlooping does your PC find the device with the "adb devices" command (namely, as soon as your phone boots up you'd spam this command via terminal)?
Click to expand...
Click to collapse
I tried when I click Power and Vol+ it does bootloop.But the only way to put phone into “bootloader mode” you need SPFlashTool. I dont know what can i do now. When phone was bootlooping i wrote several times “adb devices” but nothing happened
matteo.de-leo said:
Yes I was thinking the same. Eventually you do not need to install the recovery, restoring the bootloader should be enough: if the bootloader is already unlocked you can just boot into TWRP and from there restoring the backup previously copied into a SD card.
I will try this, maybe that works.
Why do you say you don't have the right one? Did SPFlashTool return you some error?
Yes, it says 'status preloader invalid'
Well AFAIK Maze is completely done, no surprise if they do not answer. I'm reasonably sure that there's a way to dump these files from a working phone, if I'm right I'll try with mine
Click to expand...
Click to collapse
That explains a lot. But it is still not acceptable to answer no one imo
---------- Post added at 10:48 PM ---------- Previous post was at 10:34 PM ----------
matteo.de-leo said:
Yes I was thinking the same. Eventually you do not need to install the recovery, restoring the bootloader should be enough: if the bootloader is already unlocked you can just boot into TWRP and from there restoring the backup previously copied into a SD card.
Why do you say you don't have the right one? Did SPFlashTool return you some error?
Well AFAIK Maze is completely done, no surprise if they do not answer. I'm reasonably sure that there's a way to dump these files from a working phone, if I'm right I'll try with mine
Click to expand...
Click to collapse
ttl1982 said:
That explains a lot. But it is still not acceptable to answer no one imo
Click to expand...
Click to collapse
I now get another error when flashing boot.img:
ERROR: STATUS_BROM_CMD_STARTCMD_FAIL
ttl1982 said:
ERROR: STATUS_BROM_CMD_STARTCMD_FAIL
Click to expand...
Click to collapse
As reported by another user on this website: https://forum.hovatek.com/thread-21351.html
The device attempted to power on before SP flash tool could flash files to it
Click to expand...
Click to collapse
Phone must be plugged (while switched off) to the USB port after having given the Download order to SP
---------- Post added at 09:38 PM ---------- Previous post was at 09:34 PM ----------
By the way, it seems that this very website (in particular here https://forum.hovatek.com/thread-468.html) hosts a guide to dump a Mediatek firmware SPFlashTool compatible, together with the necessary files, but guess what? You need to register in order to download them, something that I'll definitely do if it just lets me
ttl1982 said:
I now get another error when flashing boot.img:
Click to expand...
Click to collapse
Which boot.img you chose ?
matteo.de-leo said:
Phone must be plugged (while switched off) to the USB port after having given the Download order to SP
Click to expand...
Click to collapse
What should i do exactly to use SPFlashTool ? What alternative ? When I connect my phone to pc it turn off turn on then power volume + and - buttons randomly and than turn on turn off stoped now it looks like this in the picture . Than i checked “adb devices” it says “waiting for devices”. The thing that “dreambo” shared “boot.alpha.x.img” and can i adjust this with SPFlashTool and install it ?
rafaello21 said:
Which boot.img you chose ?
What should i do exactly to use SPFlashTool ? What alternative ? When I connect my phone to pc it turn off turn on then power volume + and - buttons randomly and than turn on turn off stoped now it looks like this in the picture . Than i checked “adb devices” it says “waiting for devices”. The thing that “dreambo” shared “boot.alpha.x.img” and can i adjust this with SPFlashTool and install it ?
View attachment 4518023
Click to expand...
Click to collapse
I have used the exact same boot.img as you did.
I was able to install ADB and fastboot on my Redmi Note 10 Pro (sweet). After I flashed the recovery and factory reset the device, I am unable to run the adb command to flash the zip file to the device. adb is working perfectly fine on my windows machine, but is not able to recognise my device. I am confused about how I should proceed to install the Pixel Experience 13 Plus edition of the ROM, and how I can configure my phone so that my PC recognises it since I have already factory reset the device so cannot boot back into MIUI.
Any help would be really appreciated, since it is my first time installing a custom rom. Apologies if I missed something, or if my query is not well versed.
Do you have TWRP recovery installed?
If yes click on the following buttons and swipe:
{
"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"
}
Then type the following in the terminal of your PC during your phone is connected to your PC via USB cable:
adb sideload <path on your PC to ROM.zip>
And if you want to flash Magisk before booting click on the same buttons as shown above again and type:
adb sideload <path on your PC to Magisk.zip>
That's it.
Now your phone should boot the ROM (e. g. PixelExperience) you have flashed.
Since I was installing Pixel Experience Plus 13, and they have officially recommended their custom recovery, I was using the Pixel Experience Recovery instead of TWRP
erehymnt said:
Since I was installing Pixel Experience Plus 13, and they have officially recommended their custom recovery, I was using the Pixel Experience Recovery instead of TWRP
Click to expand...
Click to collapse
I have never used the Pixel Experience Recovery and do not know if that one has "ADB sideload" feature as TWRP has.
Well, Pixel Experience Recovery is not needed to flash Pixel Experience ROM.
With TWRP you can flash any ROM.
Therefore I recommend you to download TWRP ...
Xiaomi Redmi Note 10 Pro
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
... and install it by booting into fastboot mode (hold "volume down" button + Power button) and typing following command in the terminal:
fastboot flash recovery <path on your PC to TWRP.img>
Afterwards hold "volume up" button + power button until it boots into TWRP recovery and do what I wrote you above.
minax007 said:
Do you have TWRP recovery installed?
If yes click on the following buttons and swipe:
Then type the following in the terminal of your PC during your phone is connected to your PC via USB cable:
adb sideload <Link to ROM.zip>
And if you want to flash Magisk before booting click on the same buttons as shown above again and type:
adb sideload <Link to Magisk.zip>
That's it.
Now your phone should boot the ROM (e. g. PixelExperience) you have flashed.
Click to expand...
Click to collapse
Unfortunately, the problem I'm facing is that adb is not able to recognise my device, so any adb commands I'm entering on my terminal are not being executed since the device isn't connected. Any way to fix this in particular?
minax007 said:
I have never used the Pixel Experience Recovery and do not know if that one has "ADB sideload" feature as TWRP has.
Well, Pixel Experience Recovery is not needed to flash Pixel Experience ROM.
With TWRP you can flash any ROM.
Therefore I recommend you to download TWRP ...
Xiaomi Redmi Note 10 Pro
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
... and install it by booting into fastboot mode (hold "volume down" button + Power button) and typing following command in the terminal:
fastboot flash recovery <path on your PC to TWRP.img>
Afterwards hold "volume up" button + power button until it boots into TWRP recovery and do what I wrote you above.
Click to expand...
Click to collapse
Okay I will try using TWRP once, thank you!
erehymnt said:
Unfortunately, the problem I'm facing is that adb is not able to recognise my device, so any adb commands I'm entering on my terminal are not being executed since the device isn't connected. Any way to fix this in particular?
Click to expand...
Click to collapse
Did you already install TWRP?
Does fastboot work in fastboot mode?
erehymnt said:
Okay I will try using TWRP once, thank you!
Click to expand...
Click to collapse
You are welcome!
Just write me if you run into issues, so that I can help you.
And don't worry if I respond with a delay (it is prayer time right now).
I don't see a problem with your device ... I have had similar issues and could resolve all of these.
minax007 said:
You are welcome!
Just write me if you run into issues, so that I can help you.
And don't worry if I respond with a delay (it is prayer time right now).
I don't see a problem with your device ... I have had similar issues and could resolve all of these.
Click to expand...
Click to collapse
I installed TWRP, it said the ROM flash was successful, but when I reboot my device, it still boots back to TWRP (i.e, the system doesn't boot the PixelExperience ROM).
Fastboot works in fastboot mode, only adb is disfunctional.
@minax007 I ended up wiping the system again, and after rebooting it fixed my issue. I have booted into the custom ROM now, thank you for your help!
erehymnt said:
@minax007 I ended up wiping the system again, and after rebooting it fixed my issue. I have booted into the custom ROM now, thank you for your help!
Click to expand...
Click to collapse
Wiping system is with this phone never needed. Why you've tried this?
erehymnt said:
@minax007 I ended up wiping the system again, and after rebooting it fixed my issue. I have booted into the custom ROM now, thank you for your help!
Click to expand...
Click to collapse
You are welcome.
In case you experience a problem again just post your questions in this great forum.
I know XDA developers since my first smart mobile, which was an XDA.
And I have always found a solution to the problems which you run into by time
Laptapper said:
Wiping system is with this phone never needed. Why you've tried this?
Click to expand...
Click to collapse
I don't know what the issue was earlier, I had mistakenly flashed a boot image earlier using fastboot (which was completely unnecessary and just me desperately finding a solution), and the phone would always reboot into the custom recovery since then.
Anyway, it's solved now, I'm glad I could figure out a solution to this, was scared that I had bricked my device!
minax007 said:
You are welcome.
In case you experience a problem again just post your questions in this great forum.
I know XDA developers since my first smart mobile, which was an XDA.
And I have always found a solution to the problems which you run into by time
Click to expand...
Click to collapse
Makes sense, I'll learn the process with time. Just a bit intimidating the first time since it poses the risk of bricking the device or causing some unintended damage.
erehymnt said:
I was able to install ADB and fastboot on my Redmi Note 10 Pro (sweet). After I flashed the recovery and factory reset the device, I am unable to run the adb command to flash the zip file to the device. adb is working perfectly fine on my windows machine, but is not able to recognise my device. I am confused about how I should proceed to install the Pixel Experience 13 Plus edition of the ROM, and how I can configure my phone so that my PC recognises it since I have already factory reset the device so cannot boot back into MIUI.
Any help would be really appreciated, since it is my first time installing a custom rom. Apologies if I missed something, or if my query is not well versed.
Click to expand...
Click to collapse
Hi
Device USB controller stuck in EDB mode that's why charging & ADB are not available
Fix
Remove the back cover
Disconnect the battery ribbon cable
Reconnect the battery
Thanks
erehymnt said:
Makes sense, I'll learn the process with time. Just a bit intimidating the first time since it poses the risk of bricking the device or causing some unintended damage.
Click to expand...
Click to collapse
Don't worry ... the devices of today (at least since appr. 10 years) are almost unbrickable ... in case you install the recovery correctly and just flash zip files.
And in case you still mess up things this is the forum to ask for help
lepusang said:
Hi
Device USB controller stuck in EDB mode that's why charging & ADB are not available
Fix
Remove the back cover
Disconnect the battery ribbon cable
Reconnect the battery
Thanks
Click to expand...
Click to collapse
Thanks for sharing your thoughts.
But he did not state that charing is not availble.