Hi I'm new, how have I got an acatel Idol 3 (6045 Y)
Well I'll have Idol 3 updated to version 6.0,
I'd like to know how I can go back / downgrade to Android 5
I've already done the hard reset, the cache wipe, but nothing stays the same
Greetings and thanks
Joselito.98 said:
Hi I'm new, how have I got an acatel Idol 3 (6045 Y)
Well I'll have Idol 3 updated to version 6.0,
I'd like to know how I can go back / downgrade to Android 5
I've already done the hard reset, the cache wipe, but nothing stays the same
Greetings and thanks
Click to expand...
Click to collapse
You need to downgrade, only with rom if someone have it.
persona78 said:
You need to downgrade, only with rom if someone have it.
Click to expand...
Click to collapse
With adb? Because it does not work for me, remote command unknown
I've tried everything, that error happens when flashing twrp
regards
Joselito.98 said:
With adb? Because it does not work for me, remote command unknown
I've tried everything, that error happens when flashing twrp
regards
Click to expand...
Click to collapse
Is because with the update you loose bootloader commands ( fastboot)
So, you need to root, after root install Rashr from Google play, with Rashr you can flash twrp, with twrp you can flash aboot.img from 5.0.2 version with a flash zip then you recover bootloader commands like this.
persona78 said:
Is because with the update you loose bootloader commands ( fastboot)
So, you need to root, after root install Rashr from Google play, with Rashr you can flash twrp, with twrp you can flash aboot.img from 5.0.2 version with a flash zip then you recover bootloader commands like this.
Click to expand...
Click to collapse
The problem is there, I want to twrp to do root.
The question is not to get recovery custon, but root
I tried it with adb, but I got the same error ...
regards
Joselito.98 said:
The problem is there, I want to twrp to do root.
The question is not to get recovery custon, but root
I tried it with adb, but I got the same error ...
regards
Click to expand...
Click to collapse
What he's saying is that without fastboot the only way you can flash a ROM is through TWRP. You need to root and then install TWRP, and then install the ROM. Also, if you're doing any kind of reflashing; to do so without a custom recovery is risky at best.
magus7091 said:
What he's saying is that without fastboot the only way you can flash a ROM is through TWRP. You need to root and then install TWRP, and then install the ROM. Also, if you're doing any kind of reflashing; to do so without a custom recovery is risky at best.
Click to expand...
Click to collapse
That's it, but I mean I can not flash the twrp nor the root, I get: unknown remote command
Joselito.98 said:
That's it, but I mean I can not flash the twrp nor the root, I get: unknown remote command
Click to expand...
Click to collapse
You get this because you don't have fastboot any more!!
Do you get this?
You must find another way to root, maybe kingroot!
persona78 said:
You get this because you don't have fastboot any more!!
Do you get this?
You must find another way to root, maybe kingroot!
Click to expand...
Click to collapse
If I have adb and fastboot, with kingroot not working
Now I make a video
Joselito.98 said:
That's it, but I mean I can not flash the twrp nor the root, I get: unknown remote command
Click to expand...
Click to collapse
Look at this thread to get TWRP and root. Works perfectly; I went through this procedure several times on 6045I. Just read carefully to understand the steps; there are couple of other threads that are linked from this one.
kt-Froggy said:
Look at this thread to get TWRP and root. Works perfectly; I went through this procedure several times on 6045I. Just read carefully to understand the steps; there are couple of other threads that are linked from this one.
Click to expand...
Click to collapse
Now take a look, and in step 1 put the twrp but only for idol 4, not for mine
Joselito.98 said:
Now take a look, and in step 1 put the twrp but only for idol 4, not for mine
Click to expand...
Click to collapse
Yes, the TWRP steps are described for Idol 4, but the process works perfectly fine for 6045. That thread is a compilation of steps from few other threads that are linked from there; some may not be specifically for our model, but they work. Just read carefully and make sure you understand. It's quite normal on XDA, when you find some info from another device's forum, and adapt it to your device. Like I said, I did this myself on 6045I at least 3-4 times, while fooling around with the phone after I got it.
kt-Froggy said:
Yes, the TWRP steps are described for Idol 4, but the process works perfectly fine for 6045. That thread is a compilation of steps from few other threads that are linked from there; some may not be specifically for our model, but they work. Just read carefully and make sure you understand. It's quite normal on XDA, when you find some info from another device's forum, and adapt it to your device. Like I said, I did this myself on 6045I at least 3-4 times, while fooling around with the phone after I got it.
Click to expand...
Click to collapse
But does it work with android 6?
And if I get the same error?
Hello ? Can someone help me please
kt-Froggy said:
Yes, the TWRP steps are described for Idol 4, but the process works perfectly fine for 6045. That thread is a compilation of steps from few other threads that are linked from there; some may not be specifically for our model, but they work. Just read carefully and make sure you understand. It's quite normal on XDA, when you find some info from another device's forum, and adapt it to your device. Like I said, I did this myself on 6045I at least 3-4 times, while fooling around with the phone after I got it.
Click to expand...
Click to collapse
Hello, I followed all the steps of this post, but there is a problem, idol 3 6045Y, there is no download mode, as you did
regards
PS: Thank you
Hi, why are not I going? I tried the sahara and firehose
I do everything well does not come out, no error, but at the time of starting the recovery leaves the factory.
I tried that twrp and also several more, but being all ok, I do not know why it's not going
regards
I have tried the Sahara again in every possible way.
And if with the sahara I try to put a rom with android 5?
And what about the flashtool?
regards
Joselito.98 said:
I have tried the Sahara again in every possible way.
And if with the sahara I try to put a rom with android 5?
Click to expand...
Click to collapse
You can't use Sahara & Firehose for flashing the ROM. It will only let you to flash the recovery (TWRP).
You have to understand that you need to go through several steps here...
1. Your goal is to downgrade to 5.x. You can't flash a 5.x official stock ROM, because the only way to flash stock is to use Mobile Upgrade Q, and you already got an update to 6.0 for your phone. Your only choice is to find a 5.x ROM that can be flashed from TWRP.
2. So, you need to install TWRP. I recommended using Sahara & Firehose, because this method works for me every time with no problems. I pointed you to the thread with ALL the information you need. If it doesn't work for you, I don't know why. Maybe you don't have the proper drivers installed? You need the drivers before you try doing anything with your phone from your PC. Maybe you have a bad USB cable or port? Maybe something else? I have no idea... I simply told you what works for me 100%.
3. There may be another way, if you somehow root you phone first, then flash TWRP using Rashr, for example. But I don't know how to root it. I only rooted it by flashing SuperSU, after I already had TWRP installed, so I can't help you with this...
Most importantly, you need to understand what you are doing, why you need to do specific steps, and the purpose of all the tools you use...
kt-Froggy said:
You can't use Sahara & Firehose for flashing the ROM. It will only let you to flash the recovery (TWRP).
You have to understand that you need to go through several steps here...
1. Your goal is to downgrade to 5.x. You can't flash a 5.x official stock ROM, because the only way to flash stock is to use Mobile Upgrade Q, and you already got an update to 6.0 for your phone. Your only choice is to find a 5.x ROM that can be flashed from TWRP.
2. So, you need to install TWRP. I recommended using Sahara & Firehose, because this method works for me every time with no problems. I pointed you to the thread with ALL the information you need. If it doesn't work for you, I don't know why. Maybe you don't have the proper drivers installed? You need the drivers before you try doing anything with your phone from your PC. Maybe you have a bad USB cable or port? Maybe something else? I have no idea... I simply told you what works for me 100%.
3. There may be another way, if you somehow root you phone first, then flash TWRP using Rashr, for example. But I don't know how to root it. I only rooted it by flashing SuperSU, after I already had TWRP installed, so I can't help you with this...
Most importantly, you need to understand what you are doing, why you need to do specific steps, and the purpose of all the tools you use...
Click to expand...
Click to collapse
Here you have all the procedure "well done" of how to download twrp with the sahara, and you will see that it does not work ...
https://vimeo.com/210311115
Related
I am trying to unlock my photons Q bootloader on the Motosite which is well known. I check it now a million times if I have a typo and I Dont.
The button with the "request unlock key " comes up, I hit it, and didnt recieve any mail. And I started last week doing it.
The Photon q has a GSM mod done by the almighty CornholioGSM, and I am using a connection from Germany. Since it is a Sprint photon, I thought that it might be discarded, because the ip it comes from is german ?..
Would be great to have someone telling me if there is another solution to this ..
I tried to flash with the locked bootloader the recovery, but get the message "invalid image size" on CWM or TWR.
I hope this Q is not too noob for all of you.
I would try motochopper or whatever the exploit was to unlock without Moto's assistance.
It may have been unlocked previously, (relocked for warranty swap) in which case I'm not sure you can use the site to re-unlock the device...
arrrghhh said:
I would try motochopper or whatever the exploit was to unlock without Moto's assistance.
It may have been unlocked previously, (relocked for warranty swap) in which case I'm not sure you can use the site to re-unlock the device...
Click to expand...
Click to collapse
First of all thank your for your answer ! Most likely you are right. Now my Q, I did read Motochopper just install SU and also gives root, but without touching the bootloader. Dont I need to unlock the bootloader if I want to install Cyanogen or any other Mod ? Maybe I understood that wrong.
x11-nice said:
First of all thank your for your answer ! Most likely you are right. Now my Q, I did read Motochopper just install SU and also gives root, but without touching the bootloader. Dont I need to unlock the bootloader if I want to install Cyanogen or any other Mod ? Maybe I understood that wrong.
Click to expand...
Click to collapse
Ok, motochopper did its job. Thank you for that ! ! ! I guess now I have to go on with Goomanager. :good:
x11-nice said:
Ok, motochopper did its job. Thank you for that ! ! ! I guess now I have to go on with Goomanager. :good:
Click to expand...
Click to collapse
If you're wanting to install TWRP, I think they have a new app now... TWRP Manager?
I've always installed recovery using fastboot on the Q, so I'm not very familiar with the apps .
arrrghhh said:
If you're wanting to install TWRP, I think they have a new app now... TWRP Manager?
I've always installed recovery using fastboot on the Q, so I'm not very familiar with the apps .
Click to expand...
Click to collapse
I tried the TWRP Manager, the manager shows me success for installing the TWRP recovery, but I cant access it. It switches back into Fastboot telling me flash failure. Actually I would like to install CM11. Well I will try to install the latest nightly and see whats happening. Hopefully it doesnt brick. :silly: Thanks for your help, I will let you know about success or fail.
x11-nice said:
I tried the TWRP Manager, the manager shows me success for installing the TWRP recovery, but I cant access it. It switches back into Fastboot telling me flash failure. Actually I would like to install CM11. Well I will try to install the latest nightly and see whats happening. Hopefully it doesnt brick. :silly: Thanks for your help, I will let you know about success or fail.
Click to expand...
Click to collapse
You need to install some sort of custom recovery in order to flash a custom ROM.
Open Recovery or TWRP are both fine. CWM is really old for our device, I can't recommend it.
arrrghhh said:
You need to install some sort of custom recovery in order to flash a custom ROM.
Open Recovery or TWRP are both fine. CWM is really old for our device, I can't recommend it.
Click to expand...
Click to collapse
So yesterday Motorola send me the messages with the codes which I apllied for almost 2 weeks ago... I guess the next days will arrive more.
Ofc I tried to unlock and it worked as expected. Now with fastboot flashing tto recovery 2.8.0.1 of TWRP went flawless. Actually I am really impressed how easy it worked, unlike using all the other tools like motochopper and TWRP Manager, which actually didnt solve the problem at all not having a unlocked bootloader.
Now my last Q: Which CM11 is the preferable choice for using it with the Photon. I dont care so much about Nightly or not. What I need is stable VPN and WIFI, and working mail and messenger like Cypher.
And! Thank you so much arrrghhh for all your advice and help. This forum and its users are really a great help to the community of android !
All DONE
Ok used TWRP 2.8.0.1 to install cm-11-20141012-NIGHTLY-moto_msm8960_jbbl and the PA-Gapps-Modular for 4.4.x. Great work on everyone who participated making this possible and developing the necessary tools.
Thanks again to Arrrghhh and Cornholio !
Hi Everyone!
Because of having issues i can´t fix on my OnePlus, i´m finally asking for some professional help here, as it´s getting more and more complicated and i don´t want to ruin my phone.
What was my plan?
Installing CM11S 44S on my OPO, which had the 05Q Version as factory setting.
Also i wanted to install a franco kernel.
I hoped, if i do both steps successfully, my OPO will have a good battery life (44S seemed to be the most efficient version, according to some forums).
What did i do so far?
First i set up an adb backup for my data, but not for the OS. However, i installed SDK plus tools and drivers.
Next step was installing a new recovery, which is able to flash a new version of CM11S, so i set up TWRP with fastboot, which means my device is "unlocked" now.
Everything worked well so far, i also made an backup in TWRP.
The problem:
I wanted to reboot my OPO at some point and TWRP asked me for rooting my device. Accidentally i swiped over so it started rooting process, but i didn´t want to root it, so i immediately shut the device down.
By now TWRP recovery/fastboot is working, but my OS 05Q is lost and i can´t install a new ROM because im getting the Report:
--
Checking for MD5 file...
Skipping MD5 check; no MD5 file found
Error flashing zip /<path to .zip file>
--
Can anyone help me to get 05Q back or the 44S with the franco kernel?
I know there might be some other threads that deal with similar problems, but actually none of them helped me so far. For example: do i need a fastboot image or signed flashable zips (which i have)? In which order do i install the kernel and the ROM?
Some Information:
I can access my device via fastboot and my OPO is also shown as a adb device on my MAC.
When starting in TWRP, i can also access the device in USB Mode, transfering files is also possible.
I´m not really competent with android modding or programming, so i will need some noob-friendly answers, but i bet you guys know how to help me out here.
Thank you very much for your help, i really don´t know what to do anymore.
EDIT:
I found out how to place a md5 file to the referring version, but it still sais: MD5 does not match.
I´m so done with it right now that i wish i had my OPO back as it was few days ago.
Well, i cant really help here as i have not face this problem but ur mistake was that u Immediately shut the device down the moment it was installing root. It may have corrupted the partitions of the phone and left it at that state, so maybe restoring the partitions of that section may help. Like i said im not knowledgeable about this
Agreed, you shouldn't have shut down the phone while it was modifying a partition. The root wouldn't have mattered anyway because you were about to overwrite the system partition by flashing a ROM. Go to my guide thread and look at section 8 to flash the stock images for the build you desire:
http://forum.xda-developers.com/showthread.php?t=2839471
Heisenberg said:
Agreed, you shouldn't have shut down the phone while it was modifying a partition. The root wouldn't have mattered anyway because you were about to overwrite the system partition by flashing a ROM. Go to my guide thread and look at section 8 to flash the stock images for the build you desire:
http://forum.xda-developers.com/showthread.php?t=2839471
Click to expand...
Click to collapse
Can i follow all these instructions altough im using a mac?
I will try it out today, hopefully this will fix the problem.
Thyrix said:
Can i follow all these instructions altough im using a mac?
I will try it out today, hopefully this will fix the problem.
Click to expand...
Click to collapse
Yes you can still use fastboot on a Mac, but you'll need to Google how to set it up on a Mac first.
Heisenberg said:
Yes you can still use fastboot on a Mac, but you'll need to Google how to set it up on a Mac first.
Click to expand...
Click to collapse
Alright, so fastboot is ready, but i need to know, if i will need one of those "unofficial stock rooted fashable zips" a fastboot image. or anything else? sorry to ask for
Can i trust an android version anyone rooted...?
Thyrix said:
Alright, so fastboot is ready, but i need to know, if i will need one of those "unofficial stock rooted fashable zips" a fastboot image. or anything else? sorry to ask for
Can i trust an android version anyone rooted...?
Click to expand...
Click to collapse
You need the fastboot images.
Heisenberg said:
You need the fastboot images.
Click to expand...
Click to collapse
Got stuck at step 2: It Terminal said error: cannot determine image filename for sbl1.mbn - although the name is correct and the file is in the correct folder :/
EDIT:
Fixed it, forgot to type sbl1 2 times, im sorry
And it worked, thank you sooooo much!!!
I was following this guide and after flashing the recovery, I seem to be unable to boot into the recovery mode. I can still boot into fastboot fine. I tried both TWRP 3.0.0 and the 20151227 experimental build mentioned in the guide.
I'm not sure what step I screwed up because none seemed to report an error while following that guide.
I ran into this thread where the OP seemed to maybe having the same issue and I waited at the logo for quite a while as suggested there.
search for the experimental twrp... you will find it here. only this one works with MM
http://forum.xda-developers.com/showpost.php?p=64520513&postcount=229
el3c said:
search for the experimental twrp... you will find it here. only this one works with MM
http://forum.xda-developers.com/showpost.php?p=64520513&postcount=229
Click to expand...
Click to collapse
I tried that before posting but in case I missed something, I tried that again with no progress.
At this point I'd be happy just going back to android 5.x but I'm not sure where to start in terms of removing the mm blobs from the guide I linked and getting a recovery that will actually work.
RagingRoosevelt said:
I tried that before posting but in case I missed something, I tried that again with no progress.
At this point I'd be happy just going back to android 5.x but I'm not sure where to start in terms of removing the mm blobs from the guide I linked and getting a recovery that will actually work.
Click to expand...
Click to collapse
Have you unlocked your bootloader?
fastboot oem unlock
Click to expand...
Click to collapse
then
fastboot flash recovery twrp-20151227-EXPERIMENTAL-shieldtablet-m.img
Click to expand...
Click to collapse
you find it here: http://forum.xda-developers.com/showpost.php?p=64520513&postcount=229
This is must work! I ve done this several times.
It is better to take this Guide...but use the TWRP from the link before: http://forum.xda-developers.com/shield-tablet/general/complete-guide-shield-tablet-k1-root-t3315965
el3c said:
Have you unlocked your bootloader?
then
you find it here: http://forum.xda-developers.com/showpost.php?p=64520513&postcount=229
This is must work! I ve done this several times.
It is better to take this Guide...but use the TWRP from the link before: http://forum.xda-developers.com/shield-tablet/general/complete-guide-shield-tablet-k1-root-t3315965
Click to expand...
Click to collapse
Yup, did both of those steps. What sort of output does fastboot give you when you flashed stuff? My working theory is that the fastboot client on the shield isn't performing the flash even though fastboot on my PC says that everything went OK.
el3c said:
Have you unlocked your bootloader?
then
you find it here: http://forum.xda-developers.com/showpost.php?p=64520513&postcount=229
This is must work! I ve done this several times.
It is better to take this Guide...but use the TWRP from the link before: http://forum.xda-developers.com/shield-tablet/general/complete-guide-shield-tablet-k1-root-t3315965
Click to expand...
Click to collapse
I ended up getting it fixed. It seems like it was an issue with the USB ports I tried. I plugged it into a different one and it seems to be working.
Hey Folks,
I recently stumbled upon Team MT's quite useful Huawei Multi-Tool – but didn't find anything about it in the Honor 10 Forum although it's compatible!
First of all I have no connection to Team MT at all, so this thread is just about the usefulness of the Tool and what you and I might experience using it.
Also I'm not responsible for any damages/issues caused by this tool.
The tool might come in handy for people that are uncomfortable using cmd/terminal commands or get confused too easily.
Of course there are still a lot of things that could go wrong so if you're not sure what you're doing or what the consequences might be, just don't flash anything.
To use the Multi-Tool, you'll have to have your bootloader unlocked and the phone connected to your pc with adb installed.
When the tool shows you the (right) phone model in the lower right, you're good to go.
With the help of the Multi-Tool, you can
ROOT your Honor 10 with Magisk
flash TWRP
flash STOCK RECOVERY
unlock various small features
All with just a few clicks.
You can download it at Team MT's website:
http://pro-teammt.ru/huawei-multi-tool/
I for instance used it to flash the stock recovery after I had installed TWRP, so I could get regular OTA updates through the system again.
I'm curious to see if there are other people that have used the tool as well or what people that just heard of it now will use it for.
Is an unlocked bootloader required for the tool to root the phone and flash custom recovery?
leAndroid91 said:
Is an unlocked bootloader required for the tool to root the phone and flash custom recovery?
Click to expand...
Click to collapse
Yes , unlocked bootloader is required
Btw where did you get your stock recovery? Cause I don't see Any stock recovery out there for colal10 model. Btw thanks for the info, gotta check it out
fosterqaz11 said:
Btw where did you get your stock recovery? Cause I don't see Any stock recovery out there for colal10 model. Btw thanks for the info, gotta check it out
Click to expand...
Click to collapse
You can back up stock recovery after flashing magisk
miststudent2011 said:
You can back up stock recovery after flashing magisk
Click to expand...
Click to collapse
https://www.addictivetips.com/mobil...ecovery-and-system-partition-images/&hl=en-IN
Will this work since I will have to backup without using twrp.
fosterqaz11 said:
https://www.addictivetips.com/mobil...ecovery-and-system-partition-images/&hl=en-IN
Will this work since I will have to backup without using twrp.
Click to expand...
Click to collapse
The link you provided is broken.
You can find the procedure here.
https://forum.xda-developers.com/showpost.php?p=75630973&postcount=3
miststudent2011 said:
The link you provided is broken.
You can find the procedure here.
https://forum.xda-developers.com/showpost.php?p=75630973&postcount=3
Click to expand...
Click to collapse
Ty turn out it was almost the same info
fosterqaz11 said:
Btw where did you get your stock recovery? Cause I don't see Any stock recovery out there for colal10 model. Btw thanks for the info, gotta check it out
Click to expand...
Click to collapse
The Stock recovery just appeared inside the Multi-Tool, where I was able to download and flash it, I didn't download or back up anything beforehand.
Isn't there some dropdown menu where you can choose the recovery to flash?
I've been flashing it onto my COL-AL10 AND my L29, so it works either way.
vollkornbaguette said:
The Stock recovery just appeared inside the Multi-Tool, where I was able to download and flash it, I didn't download or back up anything beforehand.
Isn't there some dropdown menu where you can choose the recovery to flash?
I've been flashing it onto my COL-AL10 AND my L29, so it works either way.
Click to expand...
Click to collapse
I didn't install the app yet
I'm gonna wait for gpu turbo update then maybe root
In trying to root my Nokia 3, I installed TWRP custom recovery but realised that I forgot to install magisk manager. Upon rebooting the phone out of TWRP recovery mode my Nokia 3 is now stuck in a boot loop such that whenever I turn the device off or reboot it, either from adb or TWRP, the device inevitably only reboots in fastboot mode. Even using the fastboot reboot command doesn't work and only boots it up again only for it to enter fastboot mode immediately.
This means that I can't access the phone as usual meaning I'm unable to download the magisk.zip file I need to install magisk. I tried cloning the git-master and sideloading that from my computer but it said invalid .zip format.
Any idea what I can do?
Are you sure you haven't deleted the ROM by accident?, that same thing happened to me before.
andres_vacal said:
Are you sure you haven't deleted the ROM by accident?, that same thing happened to me before.
Click to expand...
Click to collapse
I don't see how I might have done this seeing as I'd guess such a thing would only be possible if I had root on my device. I haven't rooted it yet.
But if I'm mistaken on that, using the TWRP file manager shows an empty /boot/ directory. Is there any way I can restore normal functionality to my device? I just need to be able to get magisk on there so I can install in through TWRP and then root the phone so I can get a custom ROM
Totalitor said:
I don't see how I might have done this seeing as I'd guess such a thing would only be possible if I had root on my device. I haven't rooted it yet.
But if I'm mistaken on that, using the TWRP file manager shows an empty /boot/ directory. Is there any way I can restore normal functionality to my device? I just need to be able to get magisk on there so I can install in through TWRP and then root the phone so I can get a custom ROM
Click to expand...
Click to collapse
But, in TWRP, when you go to reboot section, does it says "No OS Installed"? ( in the upper side )
andres_vacal said:
But, in TWRP, when you go to reboot section, does it says "No OS Installed"? ( in the upper side )
Click to expand...
Click to collapse
It doesn't. I suppose the contents of /boot just isn't visible because I haven't rooted the phone yet?
Totalitor said:
It doesn't. I suppose the contents of /boot just isn't visible because I haven't rooted the phone yet?
Click to expand...
Click to collapse
idts, have you tried to wipe and install constum ROM again?
andres_vacal said:
idts, have you tried to wipe and install constum ROM again?
Click to expand...
Click to collapse
No. I haven't installed a custom ROM. It was the default android 8.0 OS. I haven't been able to root the phone yet because I don't have magisk manager installed.
The only thing I've installed has been TWRP custom recovery. As I understand it, you can't even install custom ROMS unless the phone is already rooted.
Totalitor said:
No. I haven't installed a custom ROM. It was the default android 8.0 OS. I haven't been able to root the phone yet because I don't have magisk manager installed.
The only thing I've installed has been TWRP custom recovery. As I understand it, you can't even install custom ROMS unless the phone is already rooted.
Click to expand...
Click to collapse
No, you only look for the rom of your specific device, and then just flash it trought TWRP
andres_vacal said:
No, you only look for the rom of your specific device, and then just flash it trought TWRP
Click to expand...
Click to collapse
Ok then. I haven't actually been able to find any ROMS for the Nokia 3 other than the stock ROM.
Do you know of any custom ROMS for the device?
andres_vacal said:
No, you only look for the rom of your specific device, and then just flash it trought TWRP
Click to expand...
Click to collapse
I ran adb sideload on the update.zip file downloaded from here.
It seems to have restored my nokia 3 device's recovery to a stock recovery.
Attempting to reboot the device merely reboots it to the stock recovery mode. I cannot seem to get it to reboot into the phone's normal state.
In addition, adb, even while running under root permissions, can no longer detect the device.
I have tried wiping the device, factory resetting it, but the device refuses to reboot into it's normal mode. I can only reboot it into stock recovery or the bootloader.
Totalitor said:
I ran adb sideload on the update.zip file downloaded from here.
It seems to have restored my nokia 3 device's recovery to a stock recovery.
Attempting to reboot the device merely reboots it to the stock recovery mode. I cannot seem to get it to reboot into the phone's normal state.
In addition, adb, even while running under root permissions, can no longer detect the device.
I have tried wiping the device, factory resetting it, but the device refuses to reboot into it's normal mode. I can only reboot it into stock recovery or the bootloader.
Click to expand...
Click to collapse
Make sure bootloader is unlocked. In fact if it turned back into stock recovery is because the ROM is already installed. Try to repeat the instalation process using TWRP and try to use another version of the stock ROM.
andres_vacal said:
Make sure bootloader is unlocked. In fact if it turned back into stock recovery is because the ROM is already installed. Try to repeat the instalation process using TWRP and try to use another version of the stock ROM.
Click to expand...
Click to collapse
My phone randomly decided it'd revert back to TWRP custom recovery today but I still can't access the main operating mode of the phone. Do you know where I can find either a custom ROM for the Nokia 3 or the stock ROM? All instructions I find online seem to be in broken english so I'm having some difficulty following a lot of the guides as they're rather vague
andres_vacal said:
Make sure bootloader is unlocked. In fact if it turned back into stock recovery is because the ROM is already installed. Try to repeat the instalation process using TWRP and try to use another version of the stock ROM.
Click to expand...
Click to collapse
As mentioned in my previous post, my phone reverted back to TWRP custom recovery for some reason. I tried sideloading the Magisk.zip file and it said it successfully flashed it, but now my Android system has reverted back to the standard Android recovery, booting into it by default.
it says
"alps/NE1_00WW_FIH/NE1
7.1.1/NMF260/00WW_2_15A
/user/release-keys"
at the top.
Totalitor said:
The bootloader was unlocked at some point but I guess it must have locked itself again at some stage when I reset it. Though now that my phone seems to be stuck in bootloader mode and stock recovery mode exclusively, I'm not able to view the serial number in settings as that's something one may only do when the normal mode of the device can be accessed.
I'd use adb to retrieve the serial number of the device but adb doesn't seem to be able to detect my device. I have the necessary drivers on my computer and am running on root privileges but it seems it can't detect it if it's not in the normal operating mode. Any idea how I can get the serial number?
Click to expand...
Click to collapse
I think before flashing magisk we should make sure the OS is ok, can you write the specific phone model?, "Nokia 3" is not an specific number. Then we should be able to find at least a stock ROM.
andres_vacal said:
I think before flashing magisk we should make sure the OS is ok, can you write the specific phone model?, "Nokia 3" is not an specific number. Then we should be able to find at least a stock ROM.
Click to expand...
Click to collapse
It's a Nokia 3 TA-1032
Sorry, I should've specified.
Totalitor said:
It's a Nokia 3 TA-1032
Sorry, I should've specified.
Click to expand...
Click to collapse
Okay man, I did some research and found out that there is not so much info about the specific model but there is some people with the same problem. Found this thread useful so let's try out that.
Nokia 3 official Firmware India/UAE Region [ Links updated with Flash tool]
Hi All, Nokia 3, 5, 6 & 8 Official Firmware flashing tool is Known as OST ( Online Service Tool) Download link Nokia 3 Firmware :- https://mega.nz/#F!1ENgnThL!FyL9uYCC3Dq-16elThKAPg----- latest for Nokia 3 is v 2.15H Nokia 5 Firmware :-...
forum.xda-developers.com
andres_vacal said:
Okay man, I did some research and found out that there is not so much info about the specific model but there is some people with the same problem. Found this thread useful so let's try out that.
Nokia 3 official Firmware India/UAE Region [ Links updated with Flash tool]
Hi All, Nokia 3, 5, 6 & 8 Official Firmware flashing tool is Known as OST ( Online Service Tool) Download link Nokia 3 Firmware :- https://mega.nz/#F!1ENgnThL!FyL9uYCC3Dq-16elThKAPg----- latest for Nokia 3 is v 2.15H Nokia 5 Firmware :-...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks, But all of the links on that thread to nokia 3 firmware are dead. In the meantime I used the adb push command to upload the magisk.zip file to my device as well as the Lineage 14.1 custom ROM which I got from here and tried installing both of them using TWRP. TWRP said both were successful but on reboot, my phone is once again stuck in the orange state at the boot screen.
Totalitor said:
Thanks, But all of the links on that thread to nokia 3 firmware are dead. In the meantime I used the adb push command to upload the magisk.zip file to my device as well as the Lineage 14.1 custom ROM which I got from here and tried installing both of them using TWRP. TWRP said both were successful but on reboot, my phone is once again stuck in the orange state at the boot screen.
Click to expand...
Click to collapse
Ow, I didn't check that, my bad. Have you tried to flash only LOS?, generally the problem with LOS is that you need to have installed the stock ROM for it to function well, if you wipe and then flash LOS it will say "successful" but it won't start.
Or at least at my experience
andres_vacal said:
Are you sure you haven't deleted the ROM by accident?, that same thing happened to me before.
Click to expand...
Click to collapse
we've established that I must have somehow accidentally deleted the ROM in installing TWRP.
You mentioned you accidentally deleted the ROM. How did you go about fixing your problem?
I've looked everywhere online for Nokia 3 TA-1032 stock firmware but all I can find are dead google drive links. How did you fix your issue? Or was yours with a different model of phone?
Totalitor said:
we've established that I must have somehow accidentally deleted the ROM in installing TWRP.
You mentioned you accidentally deleted the ROM. How did you go about fixing your problem?
I've looked everywhere online for Nokia 3 TA-1032 stock firmware but all I can find are dead google drive links. How did you fix your issue? Or was yours with a different model of phone?
Click to expand...
Click to collapse
Mine was with an Asus, and the only way I could fix the horrible bootloop was managing to install the stock un-official ROM made from a well known developer. I just did a short research on this case, and all the solutions on internet say you need the ROM like I just told you, so I think there is no way if we cannot find a ROM for the device.