Hey,
I recently got a cheap, slightly used chinese version Nokia N1. But because without the Google Services its pretty much useless to me, I want to root it and install a custom ROM.
I followed 2 tutorials:
https://forum.xda-developers.com/nokia-n1/help/nokia-n1-root-t3125771
and
https://forum.xda-developers.com/nokia-n1/general/play-store-howto-t3118965
But I always get stuck on the part with the Recovery Launcher.
{
"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"
}
To give some background, here are the steps I did:
Because fastboot and the launcher won't see my device if its in MTP or PTP, I disabled both. That seems to work fine.
I "unlocked" oem in the developer settings and also allowed USB debugging.
I started the Recovery Launcher with admin privileges and used option T4.
It boots into recovery mode, but I just get errors all over the place bacause the device is still locked. So i just typed "fastboot oem unlock". Then T4 again.
Thats where this error occurs. From what I read, this should put me into a CWM recovery session. But it doesn't. It just stays in the fastboot mode window.
I'm pretty new to this android modding thing, so don't expect to much knowledge from me.
with much thanks
~David
Bump
I really hope bumps are allowed here
its seems from ur bootloader, try to re unlock with fastboot unlock oem. if you done try different recovery developed for ur devices.
nuzzydev said:
its seems from ur bootloader, try to re unlock with fastboot unlock oem. if you done try different recovery developed for ur devices.
Click to expand...
Click to collapse
The thing is, there are no other solutions out there I really know about. I searched google up and down and got no real result.
I think my problem is that my android version isn't 5.0.x, like almost every english tutorial suggests. It is 5.1.1.
oh God... my fault sorry
Related
Hello everybody!
I'm newbie in Android, but have a little experience in flashing several devices. I hope that dear guru of this Forum will help me; alone I already have not any ideas to do.
So. Here is the phone. It was played by the little child and now anyone does'nt know what was exactly did with the phone.
Now I have "body", that vibrates 7 times while booting and stops on the HTC logo. After that powers off only by long pressing "power" button.
When connecting to the PC it boots to bootloader and stops waiting user reaction:
{
"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 downloaded an "RUU_PROTO_U_ICS_40A_HTC_Europe_1.18.401.1_Radio_10.21.40.06U_1.10.40.23_release_295191_signed" and tried to do something. It recognizes the phone, shows me OS version (2.20.xxx) and suggested to flash to the lower version. It's no matter for me, what version of software will be installed on the phone: I just want this device work. It starts flashing, reboots the phone to fastboot mode and waits something (RUU writes "waiting for bootloader"), after some time RUU says "can't connect to the phone" and suggest only one button - "exit".
I decided to go further and starts reading about ADB and fastboot. Downloads a couple of stock recovery images with 2.20, but "fastboot flash recovery recovery.img" fails with an checksum error.
After reading some forums I found an answer, that it happens because of locked bootmanager. Ok, I'd start searching any information about that. Registered at htcdev.com, followed instructions and obtained the unlock_code.bin. Executing "fastboot flash unlocktoken unlock_code.bin" causes choise menu on the phone's screen: UNLOCK or DO NOT UNLOCK and what is the most interesting: when I choosing UNLOCK - pushing on "power" button to confirm my choise did'nt do anything. Like I'm not pushing anything. Selecting DO NOT UNLOCK - pushing on "power" couses reboot without any changes.
After all of that my ideas are ended....
Can anyone help me what to do? Or it is better&faster to throw this over a window?
Thank You very much for any ideas.
please help me I have been trying solutions for 2 months but nothing works. I also tried to do
1 go to wipe
2 go to advanced wipe
3 select date
4 repair or change flie system
5 change flile system ext 2
6 then replace ext 4
but it does not work. when i try to boot in to the system it goes into an infinite loading screen. please HELP (I used google translator because my english sucks)
@Boyko99
Either boot-loader broken or Android system corrupted. Re-flash Stock ROM.
I don't know if my answer came to you so I'll rewrite it
jwoegerbauer said:
@Boyko99
Either boot-loader broken or Android system corrupted. Re-flash Stock ROM.
Click to expand...
Click to collapse
could you tell me how to find the Stock ROM. I need help because I'm not very practical in modding
Boyko99 said:
could you tell me how to find the Stock ROM.
Click to expand...
Click to collapse
GIYF ...
i downloaded this now what should i do? and with what program?
jwoegerbauer said:
GIYF ...
Click to expand...
Click to collapse
i downloaded this now what should i do? and with what program?
{
"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"
}
@Boyko99
Because you avoided to name phone's brand/model in this thread's title you can't really get advised.
Anyway:
Assumed these requirements
got fulfilled, the USB-driver suitable to your phone is installed on PC,
then the basic steps to perform are
1) Unlock phone's boot-loader, if not done yet
2) flash the ROM
@jwoegerbauer
I can't start the phone so I don't know how to do it I'm stuck in twrp because if I try to turn it on it goes into a loop
@Boyko99
My POV:
This is the price that people who think they must improve (?) phone's Android, will say put up a better (?) ROM / Recovery than that what gets pre-installed by OEM/Carrier ( in their R&D department there are certainly no idiots sitting around ), pay.
@jwoegerbauer
i have a note 3 its the worts rom of all
Let me start by saying I am not rooted no twrp just plain stock , with locked bootloader. Also EU version.(V12.0.8.0.QJGEUXM)
A few months ago I downloaded the Android 11 Rom V12.0.6.0.RJGEUXM through the phone even though I am not on any trial program.
It installed easily on my phone , some people have had to use other methods...so I read.
Anyhow , I thought it was way too buggy and needed to downgrade.( Even after the the 2 other upgrades to V12.0.7.0.RJGEUXM. This is what I did to rollback if someone else is in the same boat.
I had to wait 3 days to unlock my bootloader,
Then I used the MiTool to select the ROM I wanted.
The problem then is the bootloader is still unlocked after you flash the new ROM, you need to use ADB command " OEM lock" to relock then phone , it should erase everything then go back stock. I am still learning with this Xiaomi device so I had to learn this from different sources and hope it helps somebody else out.
Soz if this is common knowledge or wrong part of forum!
thanks for the info but why did you downgrade did android 11 lags the phone or what
aymen peter said:
thanks for the info but why did you downgrade did android 11 lags the phone or what
Click to expand...
Click to collapse
1) WiFi issues and random reboots, when the phone booted (on its own accord) on reboot the wi fi took quite a few minutes ( over 5 minutes sometimes longer) to get back online.
2) The speaker volume seemed too quiet for video and calls.(on at full volume most of the time).
3) Not so polished, sometimes would be a bit laggy other times not.
At the minute Android 11 for the Poco is still Beta, I am sure these problems will get resolved. The moral of story ... Wait for OTA instead of forcing updates.
i used xiaomi flash tool to flash fastboot rom and selected this to keep unlocked bootloader
{
"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"
}
So I have this phone Xiaomi Redmi 10X, and I wanted to put Pixel Experience 11.0 in it, after seeing this thread on GitHub.
To my surprise, following steps on that link was not that easy!
I flashed MIUI 22.1.19 manually (not in the correct way), and I ended up with a hard bricked phone.
Yesterday, while Googling about that, I managed to run into a tool called MTKClient v2.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and it solved my problem, by flashing original firmware and got it correctly working with the default MIUI 13 system.
BUT, that wasnt enough for me, because I still wanted to put Pixel Experience in it since I like it so much and think it is so sexy!!! So I, without knowing what I was doing, erased all the partitions in my phone with that tool.
Now, I cant get it to connect to that tool to work or connect with my device. On the cmd behind though, I do get some hope after seeing that device is still recognized in some way, but that's all there is to it, it doesnt go further, only "Phone detected: Reading model info".
I've tried to wait and keep both volume buttons pressed at the same time, but to no avail.
Since this, I've tried several tools but none is working to reset my partition table to original state, since I think that's my problem.
Any idea how to fix it?
Jjflick said:
Did you try cross-patching it with a razor cable?
Click to expand...
Click to collapse
No. What is that?
Jjflick said:
Did you try cross-patching it with a razor cable?
Click to expand...
Click to collapse
Even if it connects, it shows no partitions to write over.
What it needs, is to first restore the erased partitions, I think, and then writing (flashing) the firmware into it.
Ok, so i got this random Huawei P20Lite right?
Back isnt pealed off, works fine, no damages.
BUT WAIT... About Works Fine... It Wont really boot up into The OS!!!
Somethimes shows this really weired Image when pluged in and charging the phone, or randomly:
A green Screen with a Red Square on Top and a Blue one Down.
{
"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"
}
Not My Picture
It will then boot up and greed you with A:
Again, not my Picture.
Acording to Huawei, You have to Use HiSuite to recover it.
1. Put the Phone into Fast Boot. AND conect to PC
2. Open HiSuite on Your PC and click on Recovery mode or whatever its called.
3. i donk know i forgot.
anyways, i get this nice little message
(In translated, this means That: Your Device doesnt support System Recovery.
Bro wth
Anyways, our phone story doesnt end there...
I tried doing it without the Computer.
using eRecovery!!! not surprising i know...
Still, it was stuck on booting animation trying to enter eRecovery.
According to Huawei, "this message is displayed when a system file is replaced or modified, or the system is manually updated to an unofficial version". They were responding to another user with the same issue as mine.
I think that this is the Issue. Still, the instructions to fix it, dont work. (as tested above.)
Tutorials show the eRecovery method without the PC.
Here are some info i found:
Another Guy having the same issue:
i forgot the link but someone else on XDA Had the same issue.
please help!!!
hello sir did you have any luck resolving this issue (I've purity much looked every were but I had no chance)