Hello everybody,
Here's the details of the actual situation i encounter with my lovely Atrix :
-Bought Retail in 2.2 in France
-Updated in 2.3.4 with Motorola tools
-Rooted Successfuly
-Bootloader unlocked (seems it was not necessary because it was a retail and updateed via Motorola tools, as i could read on other boards, can someone confirm this point please)
-Recovery changed to CWM 5.0.2.0 using ROM Manager
I can successfully backup and restore my phone to this state.
Tried to Flash CM7, iBlur! using CWM but everytime i have the same sequence :
Finding update package
Opening Update package
installing update
Installing aborted
without any other useful messages.
Here's the detailed informations about my phone :
System Version : 45.31.0.MB860.Retail.en.FR
Android Version : 2.3.4
Baseband Version : N_01.100.00R
Webtop Version : WT-1.2.0-133_38
Kernel Version (tried to flash a new one, but this didnt worked so i went back to original) :
2.6.32.9 [email protected]#3
APflex version :GAS_EMEA_USAOLYGBRTFR_P018
GAS_EMEA_USAOLYGBRTFR_A005
GAS_EMEA_USAOLYPRTEU_M001
Build Version : 4.5.2A-74_OLE-31
Moreover, since i unlocked the booloader, i can't use anymore the fingerprint reader, but this is not my priority actually.
Tried different things (while i was learning more on this phone)
- tried to put the rom on the SD-Ext instead of SD-int : nothing changes
- tried to rename to update.zip (understood later this wouldn't work anyway) : no changes
Thanks to you all for the time you will spend reading this
Flash latest Romracer's recovery instead of using Rom Manager.
Perform a full fastboot wipe prior to flashing a ROM.
reboot to recovery
wipe dalvik
wipe cache
reboot to fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot (to recovery)
flash ROM
when you flash, are you rebooting to CWM and then choosing to install, or trying to do the install from your current ROM (i.e. from ROM Manager)? I've had mixed success with choosing it from within the current ROM.
When you boot to CWM, are you choosing "apply update from sdcard", or are you going to "install zip from sdcard", then "choose zip from internal sdcard" and browsing to your zip'd rom? Again, mixed success with the first option - always have had to choose the second.
When you boot, do you see "unlocked" on the boot screen? I've never heard that Motorola actually followed through on unlocking the boot loader via the update but I could be wrong (and probably am, since I didn't do the OTA update).
@CaelanT : i will follow your instruction step by step - thanks
@tlazarus : - tried both (installing Rom from Rom manager under Android, and rebooting to CWM)
- tried both too (and from sd-ext and sd-int)
- i see Unlocked on my screen - but i did unlock the bootloader - i wasn told that, because i had a retail Atrix and did the update via Motorola tools, i wasn't forced to unlock the bootloader (i found several articles saying that , on GB update, Motorola will unlock the bootlader ...)
My skill and knowledge level on smartphones is low, but i'm familiar with rom flashing on other devices.
i'll give you a feedback asap
Thanks again !
Moto never gave us an unlocked bootloader. We got it from a leaked GB version.
@CaelanT :
ok so i did follow all the steps :
changed my recovery
wipe Dalvik and cache
erased all w/fastboot
reboot to recovery
at this point, everything went OK
tried to flash my rom
same result -"Installation aborted"
can't see what's wrong actually ...
What procedure, step by step, are you doing to flash the ROM?
Have you tried re-downloading the ROM's to make sure you didn't get a corrupted file set?
You could try flashing a Fruitcake from : http://forum.xda-developers.com/showthread.php?t=1163009
I would also recommend flashing SUPEROSR from : http://forum.xda-developers.com/showthread.php?t=1436843
This ROM is very good.
Make sure you are choosing "install zip from sdcard". In my experience it hasn't mattered whether I flash from internal or external.
ok so first of all, THANK YOU !
i did actually follow step by step the previous instruction you gave me.
I downloaded Neutrino, and finally i can now have a custom rom.
I guess i know now why i had some trouble flashing previously :
Bad wipe & clean
maybe not the correct CWM
Rom zip has to be on the internal sd.
anyway, you were really helpfull ... what a pity i can click "thanks" only once !
Glad you finally got it going!
Related
Frustration ! Still couldn´t update my At&t ATRIX to Gingerbread. Would really apreciate some help from the forum. Please !
Actual status: Original AT&T ATRIX 4G / System version 4.1.83.MB860.ATT.en.US / Android 2.2.2 /rooted (Gingerbreak)
To update I did the four following steps (as explained in the xda forum):
1. STEP Unlook Bootloader (to be able to flash CWM)
2. STEP Flash CWM (to be able to flash Gingerbread.img)
3. STEP Flash Gingerbread
4. Done
1. Unlock Bootloader
The first STEP "Unlock the bootloader" I did according to Kenneth Pennington on briefmobile
( http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader )
and the video from MobileTechVideos
( http://www.youtube.com/watch?v=H02N4p9vEg0 )
Thanks to both.
Every message is looking on my ATRIX as it it discribed / show on the video. My ATRIX shows "Unlocked" now on the boot screen.
-> So it seems the bootloader is unlocked.
I even did this twice (when I had no success with the update) and second time when I tiped
moto-fastboot oem unlock ####, I got the message that my bootloader is already unlocked.
Question: Is there any way to proove that it is unlocked ?
Question: Is the prove that CWM could be installed ?
2. Flash CWM
This step I did exactly how it is explained in the thread [Unlocked Only][Release]CWM Recovery Mod for Atrix 4G 2011-06-30 updated again!
( http://forum.xda-developers.com/showthread.php?t=1138541 )
Everything fine so far. When I booted my ATRIX in recovery mode, now the menu of CWM is shown.
I did a backup of my system with CWM without problems.
Question: Is there any possibility that something went wrong with the installation of CWM, even if the menu is displayed and backup is working ?
3. Flash Gingerbread
For this step I used the howto by Kenneth Pennington on briefmobile and his update Gingerbread-4.5.91.zip. Link in the same howto.
(http://briefmobile.com/download-android-2-3-4-gingerbread-for-motorola-atrix-4g)
No success. The update process starts and after "two" seconds it stopped with the following failure messages. First one with update on the external SD card, second one on the internal SD card.
Support:bbs.goapk.com
-- Installing: /sdcard/Gingerbread-4.5.91.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted
-- Installing: /internal/Gingerbread-4.5.91.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted
Any ideas ? What went wrong ? Would be really happy for support.
Try using this recovery..
http://forum.xda-developers.com/showthread.php?t=1204500
When booting up do you see the word unlocked up in the left corner? If so you are unlocked but I would recommend flashing romracers cwm. You might also have a corrupted file of 4.5.91. I would re download a new copy and put it in your sd card and see how that goes. Make sure to wipe/factory reset and wipe your davlik cache as well.
1.ATRIX-in-PT said:
-- Installing: /sdcard/Gingerbread-4.5.91.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted
-- Installing: /internal/Gingerbread-4.5.91.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted
Any ideas ? What went wrong ? Would be really happy for support.
Click to expand...
Click to collapse
Are you selecting "Install update" when in CWM? Cuz if you are, don't. I believe that is for official updates if you're unable to do them OTA.
Next, install romracer's recovery. You want "Install zip from SD Card". Exact wording might be a little off, but you get the idea. Locate your ROM and you should be good to go.
XRange, Phoneguy589, ghost_op. Thanks for your ideas.
@ XRange
Instead of CWM (Android Recovery) I should use the moto-fastboot (flash recovery) ? Is this an alternative method to CWM ?
@ Phoneguy589
Not sure if the file could be corrupted. Seemed a lot of people used this file for their update without any problems. In my opinion the problem related in some way to my phone, but in which way ?
Something missing ? Something (CWM?) not installed correctly ?
I can download the file again. Which was the file you used to update for example ?
Don't understand your "wipe/factory reset and wipe davlik cache". I haven't done any of these operations, as I never read about this in one of these howtos.
Should it be necessary ? Isn't CWM (on Android Recovery) working on such an early level (before any system is booted) that it really doesn't matter what is installed on the smartphone. Or am I wrong ?
@ ghost_op
Yes, I did the "Install from SD card". Tried both, internal and external.
Not clearing the previous data that was stored can cause an issue. Its usually a process every user does when installing a new rom. Davlik cache will be located under advanced in cwm. The file you downloaded may have not downloaded properly which is why I gave you the suggestion of re downloading the file just in case something during the transfer didn't properly copy.
I am confused now. It seems the Gingerbread.zip I downloaded has to be flashed with moto-fastboot.
OK. Three questions now:
- Is it possible to flash to Gingerbread with CWM or fastboot ?
- What is the difference to flash to Gingerbread with CWM or fastboot ? I mean the difference in a result.
- Is the img (zip) file the same to flash with CWM or fastboot, or is it different ? Has to be a proper one for fastboot and a different proper one for CWM ?
Because, now I think my problem is I got a wrong Gingerbread.img to flash with CWM. To be honest, if it is possible to update to Gingerbread in both ways (CWM and fastboot), I think the CWM method is a lot "better".
1.ATRIX-in-PT said:
I am confused now. It seems the Gingerbread.zip I downloaded has to be flashed with moto-fastboot.
OK. Three questions now:
- Is it possible to flash to Gingerbread with CWM or fastboot ?
- What is the difference to flash to Gingerbread with CWM or fastboot ? I mean the difference in a result.
- Is the img (zip) file the same to flash with CWM or fastboot, or is it different ? Has to be a proper one for fastboot and a different proper one for CWM ?
Because, now I think my problem is I got a wrong Gingerbread.img to flash with CWM. To be honest, if it is possible to update to Gingerbread in both ways (CWM and fastboot), I think the CWM method is a lot "better".
Click to expand...
Click to collapse
Based on the filename you originally posted, it definitely looks like you downloaded the .img files zip from the bottom of the briefmobile page. Fastboot would be used to install those manually, as opposed to all at once with CWM.
CWM and fastboot will both get you the same end result. They're just different ways of getting there. This should give you the correct CWM version.
CWM isn't better, just easier for some. It allows you to flash ROMS and other mods on the go, without having to be connected to a computer with fastboot. There is a script present in the CWM version that controls how the files are installed. That is why you were getting an error earlier, there was no script to tell the recovery what to do.
Thanks ghost_og for the link and Phoneguy589 for the tip "wipe/factory reset" and "cache". So the files are different for CWM and fastboot.
Now I looked into the zip file and the structure is the following:
Gingerbread-4.5.91.zip
boot.img
data.img
radio.img
system.img
webtop.img
-> This is the correct zip file for fastboot
Gingerbread-Atrix-Beta-4-5.zip
META-INF
osh
system
boot.img
The first three are directories with subdirectories a couple of files
-> This is the correct zip file for CWM
However I do not know, why the size of both files is quite different
Gingerbread-4.5.91.zip / 409,4 MB
Gingerbread-Atrix-Beta-4-5.zip / 298,6 MB
-> A difference of 100 MB (!). As both should have the same result, this seems to be strange.
-> Why the CWM file is labled Beta. Is it Beta compared with the fastboot file ?
So in the end what do you advise ?
- To update with fastboot and Gingerbread-4.5.91.zip (409,4 MB)
- To update with CWM and Gingerbread-Atrix-Beta-4-5.zip (298,6 MB)
Reading a lot of threads, I got the idea to brick the phone might be more easy with fastboot than with CWM (Android recovery). Maybe I am wrong. Luckily no experience (brick) yet.
YES we can. It is done.
In the end wasn't very difficult and just running fine without any issues. My problem was to be nervious (do not want my phone bricked, it's my only one) and as it was the first time for me to flash a ROM.
Don't want to write a new howto, there are the experts in the forum to do this. Only a short summery for anybody how has similar problems.
So my updated from Android 2.2.2 to Gingerbread was done in this way:
1. STEP Unlook Bootloader (to be able to flash CWM)
2. STEP Flash CWM (to be able to flash Gingerbread.img)
3. STEP Flash Gingerbread
4. STEP Reboot & Done
Two things which troubled me, because I overlooked first:
- you definitely need to remove "install_recovery.sh" in /system/etc/ otherwise you will get a problem with installation of CWM
- check that you get the right ROM image, because they are different for fastboot and CWM.
I can highly recommend to do the update with CWM
( http://forum.xda-developers.com/show....php?t=1138541 )
and with the ROM from Kenneth
( http://briefmobile.com/download-android-2-3-4-gingerbread-for-motorola-atrix-4g )
worked perfect for me.
Thank you for your support / ideas in the xda forum. Love this forum ! Thread can be closed.
I am trying to install TWRP but struggling
The phone is running ANdroid 6. I have unlocked the bootloader successfully.
I am using this link for TWRP, http://forum.xda-developers.com/z5-compact/orig-development/twrp-z5-compact-t3235161
Originally I downloaded the files from the 1st post but upon reboot it was stuck on the white curtain screen.
Upon research I found out that the above guide is for Android 5. This link is for android 6.
Now I have downloaded this new file. My question is do i just flash this new file now?
Or are there any extra steps required? Such as a new boot.img file after flashing the new recovery file?
Flash it if you want?
I've no idea what you mean with "this new file", or "extra steps" (extra compared with what?) so I can't help with that. In general, you just should follow the steps in one of the guides to install TWRP. There're plenty, and most of them have in common that they already explain how you can install them and what you need. Also in general, you don't have to add "extra steps" or leave steps out.
Ok thanks.
I have now got the latest TWRP file, https://www.androidfilehost.com/?fid=24499762636001943
The kernel im using is Latest AndroPlus Kernel V31.
So in bootloader i have fastboot flash recovery recovery.img to install TWRP
Then flashed the latest kernel using fastboot flash boot boot.img
I have rebooted the phone but now it keep booting into recovery, not the system.
Please can someone help?
Hi,
My friend gave me this phone to update the rom, but I'm facing a problem. Device was rooted, recovery is installed, but some really old one - it doesn't even say what kind of recovery it is. So I read that I need to update to TWRP 2.8.4.0 rev.2. Tried flashing it with TWRP apk, but after choosing it and hitting install, it reboots and goes into old recovery and I can't install new TWRP. Then I tried installing it with this guide: http://rootoreviews.com/root-Lenovo-P780-install-twrp-custom-recovery , but I'm getting error: partition 'recovery' not support flash.
Lastly I tried with SP Flash Tools, but I can't install drivers. After holding red button 2 seconds and plugging cable there is no device unknown to install drivers or any kind of device looking like this phone.
Can anyone help ?
Thanks
gunlok said:
Hi,
My friend gave me this phone to update the rom, but I'm facing a problem. Device was rooted, recovery is installed, but some really old one - it doesn't even say what kind of recovery it is. So I read that I need to update to TWRP 2.8.4.0 rev.2. Tried flashing it with TWRP apk, but after choosing it and hitting install, it reboots and goes into old recovery and I can't install new TWRP. Then I tried installing it with this guide: http://rootoreviews.com/root-Lenovo-P780-install-twrp-custom-recovery , but I'm getting error: partition 'recovery' not support flash.
Lastly I tried with SP Flash Tools, but I can't install drivers. After holding red button 2 seconds and plugging cable there is no device unknown to install drivers or any kind of device looking like this phone.
Can anyone help ?
Thanks
Click to expand...
Click to collapse
Hi. I have read your message and you have to do this:
First Tutorial.
I see that you have installed allready one custom recovery.
1. Download TWRP from here: http://forum.xda-developers.com/lenovo-p780/help/rooting-tutorial-kitkat-t2835605
2. After download putt the zip file to your root of your internal memory
3. Reboot to your current recovery and install twrp
4. After install power down your phone.
5. Start your phone again with all buttons pressed: Power + Volume up and Volume down.
6. Go to TWRP and do a full backup of your current firmware.
7. After full backup you can install any custom firmware you want.
8. I reccomend latest MIUI from AndreyZO, Mirror 9.
9. Good luck. If you have other questions write here.
Seccond Tutorial
1. Look in this post: http://forum.xda-developers.com/lenovo-p780/help/rooting-tutorial-kitkat-t2835605
2. Download TWRP_v2.8.4.0 rev2 and read twice that tutorial
3. Go to this post and download SP Flash Tool: https://drive.google.com/drive/folders/0B_B98oK4DpK1S1l2bXRkTGxhVFk
4. Go to this post and download latest stock KITKAT and drivers: http://forum.xda-developers.com/lenovo-p780/development/p780-row-s226-flash-flashtool-t2909202
5. When you install the drivers in windows 8,10 you must disable driver signing. Look on youtube.
6. Now you must flash new system.
7. Unpack stock Kitkat firmware.
8. Unpack TWRP.
9. Go to firmware folder and delete recovery.img and replace with TWRP
10. Flash the firmware.
11. After flash boot at least once. If by any chance your phone is Lenovo P780 speed edition, after this flash will not start. This means that you need the latest preloader. Download it from here: http://forum.xda-developers.com/lenovo-p780/help/lenovo-p780-chineese-speed-version-t2874161
12. After flash reboot in recovery by powering off the phone and start with all buttons pressed: Power + Volume up and Volume down.
13. Now you have last stock firmware with custom recovery installed. Go to TWRP and do a full backup of your current firmware.
14. After full backup you can install any custom firmware you want.
15. I reccomend latest MIUI from AndreyZO, Mirror 9.
16. Good luck. If you have other questions write here.
Tried to flash from this weird recovery, but I get error - look at pic.
I didnt flash this recovery, it must've been flashed by seller in my country. It looks like he way buying chinese versions and then flashing modified rom with polish language (very poorly translated).
Problem with sp flash tools is, I cant install usb driver. When Im in download mode I get the sound that usb device has been plugged in and after 1 second i get the unplugging sound. There is no unknown device in Device Manager, do I am not able to update the driver :/
gunlok said:
Tried to flash from this weird recovery, but I get error - look at pic.
I didnt flash this recovery, it must've been flashed by seller in my country. It looks like he way buying chinese versions and then flashing modified rom with polish language (very poorly translated).
Problem with sp flash tools is, I cant install usb driver. When Im in download mode I get the sound that usb device has been plugged in and after 1 second i get the unplugging sound. There is no unknown device in Device Manager, do I am not able to update the driver :/
Click to expand...
Click to collapse
That one is stock recovery. Proceed with the seccond tutorial.
One more question before I try to flash, I got CN verision, u answered to me in different thread:
stympy said:
Hi. Your layout is CN.
Look if you have custom recovery TWRP Installed.
If you have TWRP installed you can go to this post and install latest MIUI MINOVO.
Good luck.
Click to expand...
Click to collapse
So is that ROW Kit Kat ok for me ?
Yes it is ok as base firmware.
After you flash and install TWRP, you can install any custom firmware.
Send from my Lenovo P1 Vibe Pro with 3 Gb of RAM and 32 Gb of Internal Storage.
Ehh now in SP flash tool I get this error... I followed all steps :/
gunlok said:
Ehh now in SP flash tool I get this error... I followed all steps :/
Click to expand...
Click to collapse
Try version 5 and see what happens.
Send from my Lenovo P1 Vibe Pro with 3 Gb of RAM and 32 Gb of Internal Storage.
gunlok said:
Ehh now in SP flash tool I get this error... I followed all steps :/
Click to expand...
Click to collapse
Did you have any success with SP Flash tool v5?
Send from my Lenovo P1 Vibe Pro with 3 Gb of RAM and 32 Gb of Internal Storage.
Hi,
Sorry for delay, wasn't at home during weekend. Im flashing right now, but I had to use "Format all + download", cause only download showed error: "PMT changed for the ROM it must be download". Now I can flash the ROW version of custom rom or CN ?
Hmm I have still stock recovery not TWRP, although I replaced it with TWRP. File size matches perfectly...
Ok, worked but I flashed it with ROW version of recovery, making backup at the moment.
Got an error installing minovo_NOTE_6.12.1_ROW.zip, couldn't boot into recovery after so I decided to flash via SP Flash Tools one more time. After that booted into recovery and once more I have stock recovery xD I'm in serious WTF mode right now
Hmm I think I screwed something. After booting Kit Kat it says "Invalid imei" :/ I guess I will have to restore with MTK droid tools ? Can you guide me through that ?
gunlok said:
Hi,
Sorry for delay, wasn't at home during weekend. Im flashing right now, but I had to use "Format all + download", cause only download showed error: "PMT changed for the ROM it must be download". Now I can flash the ROW version of custom rom or CN ?
Hmm I have still stock recovery not TWRP, although I replaced it with TWRP. File size matches perfectly...
Ok, worked but I flashed it with ROW version of recovery, making backup at the moment.
Got an error installing minovo_NOTE_6.12.1_ROW.zip, couldn't boot into recovery after so I decided to flash via SP Flash Tools one more time. After that booted into recovery and once more I have stock recovery xD I'm in serious WTF mode right now
Hmm I think I screwed something. After booting Kit Kat it says "Invalid imei" :/ I guess I will have to restore with MTK droid tools ? Can you guide me through that ?
Click to expand...
Click to collapse
Hi. Look on this location:
http://forum.xda-developers.com/showthread.php?t=3174563
Send from my Lenovo P1 Vibe Pro with 3 Gb of RAM and 32 Gb of Internal Storage.
Sorry for annoying you once again. When I try to flash anything in TWRP I get error "unable to mount /system". I read that it could mean that system partition might have incorrect file system. What is the standard one for p780?
It happens when I flash the stock KK with TWRP recovery, then I want to flash Superuser. I need superuser to use MTKdroidtools to restore IMEI.
My biggest problem is when I boot the Stock KK after flashing and power OFF, I can't boot to TWRP recovery. Instead it's booting stock recovery. Only way to to boot to TWRP or any custom recovery (tried CWM) is only after fresh flashing with SPflashtools, but I can't flash superuser. If I format /system I can install superuser (no error unable to mount /system), but I have no system to boot to use MTKdroidtools.
This phone is driving me crazy....
UPDATE:
Ok i managed to restore everything, thanks for help. Can't flash custorm rom still but im making different thread.
Hello everyone, after a long attempt at unlocking the bootloader i finally got it, i flashed TWRP and got a prompt for encryption password, and my password wasn't working and i also tried default_password,so i read that the format data option will decrypt the phone and people said wouldn't do anything to system, so i did it and now everytime i reboot it boots straight into recovery no matter what i try, it will also boot into fastboot, so i tried to find a stock ROM for TA-1056 but couldn't find it anywhere, the only the i found was a single ROM for the TA-1060, can anyone help? i really appreciate it!
Completely Bricked
Me too need a stock rom of ta 1056. Please help if you could manage to provide a helping hand... ?
I had the same issue like yours, looping in twrp. then i tried to flash it with a so called stock rom from net, guess what it went completely bricked and I donnow what to do. ??
mrabudi said:
Hello everyone, after a long attempt at unlocking the bootloader i finally got it, i flashed TWRP and got a prompt for encryption password, and my password wasn't working and i also tried default_password,so i read that the format data option will decrypt the phone and people said wouldn't do anything to system, so i did it and now everytime i reboot it boots straight into recovery no matter what i try, it will also boot into fastboot, so i tried to find a stock ROM for TA-1056 but couldn't find it anywhere, the only the i found was a single ROM for the TA-1060, can anyone help? i really appreciate it!
Click to expand...
Click to collapse
It's simple. just get the stock recovery (and boot, optional) to flash it with fastboot and go to recovery and wipe it and you'll be ok.
and also using the twrp on this phone is not a great idea to wipe.
if you wanna wipe. please use "fastboot -w" to wipe the phone while bootloader is unlocked. or stock recovery to wipe.
Because twrp built this recovery with only formatting option was ext4 to /data and /cache. So the phone cannot operate properly. Which leads to fake failed decryption notification.
Data partition must need to be formatted under f2fs format.
And finding rom for this phone is pretty easy. Just find some nb0 file for this phone (any variant of this phone should work) and extract it with "nb0 extractor" and then flash it with SP Flash tool by mediatek.
That's my way. I don't know how will you do. But normally you only need the nb0 file and then flash it with OST LA (Nokia's flash tool based off Intel's SUT L1/L3 tool).
My Nokia 1 TA-1047 stuck at Nokia logo screen
Hi guys, sorry I'm newbie so after a long time surfing for solutions, I couldn't solve my own problem. That's why I come here to ask for your supports
Firstly I unlocked bootloader, installed TWRP and rooted my device and enjoyed it. But after decided to wipe (factory reset) this phone with TWRP, and my problem began...
1. I got stuck in TWRP loop booting. After that I tried to fastboot system.bin, cache.bin and recovery.bin from Stock Firmware but it still hung at Nokia logo booting
2. I still kept trying with SP Flash Tool, Miracle Box but there was still no hope:
- SP Flashtool v5_1548 gave me error: BROM ERROR: S_BROM_CMD_STARTCMD_FAIL (2005)
- Miracle Box 2.27A told me there was an error (i don't remember the code) occured in the location (i can't remember its code either)...
Anyone can solve it please help!!!! I love this phone much and as of now still suffering day by day since I can't do anything with it.
Kindly appreciate any suggestion and solution.
Thank you all!
cuantonhonhoi said:
Hi guys, sorry I'm newbie so after a long time surfing for solutions, I couldn't solve my own problem. That's why I come here to ask for your supports
Firstly I unlocked bootloader, installed TWRP and rooted my device and enjoyed it. But after decided to wipe (factory reset) this phone with TWRP, and my problem began...
1. I got stuck in TWRP loop booting. After that I tried to fastboot system.bin, cache.bin and recovery.bin from Stock Firmware but it still hung at Nokia logo booting
2. I still kept trying with SP Flash Tool, Miracle Box but there was still no hope:
- SP Flashtool v5_1548 gave me error: BROM ERROR: S_BROM_CMD_STARTCMD_FAIL (2005)
- Miracle Box 2.27A told me there was an error (i don't remember the code) occured in the location (i can't remember its code either)...
Anyone can solve it please help!!!! I love this phone much and as of now still suffering day by day since I can't do anything with it.
Kindly appreciate any suggestion and solution.
Thank you all!
Click to expand...
Click to collapse
So here's the thing. The rom you downloaded from internet (about 2 GB) or ripped from your phone and reflashing from flash tool will NOT WORK.
The first reason you can't flash the ROM was:
You got into flashing mode but you didn't do the right way so it failed the downloading DA for the phone. Try again and it should work (Don't go into fastboot mode)
2nd reason:
Because of the unsupported chip that MiracleBox read. It said the phone was 6573 or something while the phone chip is 6737M.
So the app will create the wrong version of the scatter for the phone. Leads to the flash tool app downloading the wrong command and Download Agent for the phone makes the phone can't be flashed.
You need to get the official nb0 file for this phone (TA-1060 or 66 should also works, mine was TA-1047. Since it's a universal ROM so any variant of the phone can also work) and then extract the ROM. Then you can get the scatter text file from that nb0 ROM and then flash it over flash tool (version 5 recommended, version 3 more likely not work).
Remember to look at line with partition "metadata" and then edit "boundary_check" to false.
PLUS:
If you flash it with your own dumped EMMC rom or flash it by dd-ing the partition in recovery will kinda work. But when you update the ROM over OTA (Google Play services's System Update app)
It will most likely bootlooped the phone when it's trying to verify the 2nd partition of the same recovery or kernel flashed into the phone (https://source.android.com/security/verifiedboot) and flash the updated one.)
So flashing from official ROM is mandatory.
And you can flash it over Intel's (Nokia modified) flash tool app SUTL3 (aka. OST LA) but I can't get it to work so you just stick with Flash Tool v5 from MediaTek and you'll be good.
Link:
The nb0 ROM (Security update around May 2018): https://drive.google.com/file/d/1XqwEAGG7GMaspzV2J_yzCxnRei8zsOJd/view
(Source: https://romprovider.com/2018/09/nokia-1-ta-1060-firmware/)
nb0 extractor, requires java installed (If extracting hurts your hard disk performance aka. frozen or lag. Don't worry, It actually works, DON'T DO ANYTHING. It will notify you once it's done.): https://forum.xda-developers.com/general/general/tool-unpack-repack-nb0-rom-t3495091
Smart Phone Flash Tool from MediaTek: https://spflashtools.com/
My fixed scatter file that actually works from nb0 file: https://drive.google.com/open?id=1gRoADGHBm4vIAw3NeDyc_h9QWj12XUrC
And don't use twrp for wiping the phone. Use "fastboot -w" to wipe or use stock recovery.
TWRP will wipe the data parition but in ext4 format and make the phone bootlooped. We need f2fs in order to make the phone's /data partition run correctly. (Unless you know how to make the phone not having encryption flag when booting up every first time. Or modify TWRP to wipe the /data partition with make_f2fs and not make_ext4 app. Or using make_f2fs in recovery to directly wipe /data partition over terminal, the actual partition is in /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/userdata.)
Or you just do this (I'm not tested it yet): Google "twrp f2fs format"
kutiz21 said:
So here's the thing. The rom you downloaded from internet (about 2 GB) or ripped from your phone and reflashing from flash tool will NOT WORK.
The first reason you can't flash the ROM was:
You got into flashing mode but you didn't do the right way so it failed the downloading DA for the phone. Try again and it should work (Don't go into fastboot mode)
2nd reason:
Because of the unsupported chip that MiracleBox read. It said the phone was 6573 or something while the phone chip is 6737M.
So the app will create the wrong version of the scatter for the phone. Leads to the flash tool app downloading the wrong command and Download Agent for the phone makes the phone can't be flashed.
You need to get the official nb0 file for this phone (TA-1060 or 66 should also works, mine was TA-1047) and then extract the ROM. Then you can get the scatter text file from that nb0 ROM and then flash it over flash tool (version 5 recommended, version 3 more likely not work).
Remember to hide/delete line with partition "metadata" in scatter.txt and you can flash it perfectly.
PLUS:
If you flash it with your own dumped EMMC rom or flash it by dd-ing the partition in recovery will kinda work. But when you update the ROM over OTA (Google Play services's System Update app)
It will most likely bootlooped the phone when it's trying to verify the 2nd partition of the same recovery or kernel flashed into the phone (https://source.android.com/security/verifiedboot) and flash the updated one.)
So flashing from official ROM is mandatory.
And you can flash it over Intel's (Nokia modified) flash tool app SUTL3 (aka. OST LA) but I can't get it to work so you just stick with Flash Tool v5 from MediaTek and you'll be good.
Link:
The nb0 ROM (Security update around May 2018): https://drive.google.com/file/d/1XqwEAGG7GMaspzV2J_yzCxnRei8zsOJd/view
(Source: https://romprovider.com/2018/09/nokia-1-ta-1060-firmware/)
nb0 extractor, requires java installed (If extracting hurts your hard disk performance aka. frozen or lag. Don't worry, It actually works, DON'T DO ANYTHING. It will notify you once it's done.): https://forum.xda-developers.com/general/general/tool-unpack-repack-nb0-rom-t3495091
Smart Phone Flash Tool from MediaTek: https://spflashtools.com/
My fixed scatter file that actually works from nb0 file: https://drive.google.com/open?id=1gRoADGHBm4vIAw3NeDyc_h9QWj12XUrC
And don't use twrp for wiping the phone. Use "fastboot -w" to wipe or use stock recovery.
TWRP will wipe the data parition but in ext4 format and make the phone bootlooped. We need f2fs in order to make the phone's /data partition run correctly. (Unless you know how to make the phone not having encryption flag when booting up every first time. Or modify TWRP to wipe the /data partition with make_f2fs and not make_ext4 app. Or using make_f2fs in recovery to directly wipe /data partition over terminal, the actual partition is in /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/userdata.)
Or you just do this (I'm not tested it yet): Google "twrp f2fs format"
Click to expand...
Click to collapse
Thanks for your comment. I have recently bought that version (TA-1047) and I see that is more complicated to root it securely than I thought… Your comment gave me hope to try it. So, could you please say me if it is posible to do it without breaking it? I will read your comment when I have more time but I thank you for it!
As I see there is only stock rom for TA-1060 version, but as you say it is posible to recover it in case of breaking it, isn't it?
Thanks. :fingers-crossed:
pabloluih said:
Thanks for your comment. I have recently bought that version (TA-1047) and I see that is more complicated to root it securely than I thought… Your comment gave me hope to try it. So, could you please say me if it is posible to do it without breaking it? I will read your comment when I have more time but I thank you for it!
As I see there is only stock rom for TA-1060 version, but as you say it is posible to recover it in case of breaking it, isn't it?
Thanks. :fingers-crossed:
Click to expand...
Click to collapse
It's really easy to root the phone actually. Just unlock bootloader, install twrp recovery and install magisk.
And if you broke the phone's ROM. Just bring it to Nokia. Or flash it by yourself with the ROM I linked above by SP Flash Tool software.
Anyway the ROM is universal. So any variant of the phone can be flashed. (Proves that the elabel partition has 5 certifications images for 5 different models)
Just take sometime and read my words there.
kutiz21 said:
It's really easy to root the phone actually. Just unlock bootloader, install twrp recovery and install magisk.
And if you broke the phone's ROM. Just bring it to Nokia. Or flash it by yourself with the ROM I linked above by SP Flash Tool software.
Anyway the ROM is universal. So any variant of the phone can be flashed. (Proves that the elabel partition has 5 certifications images for 5 different models)
Just take sometime and read my words there.
Click to expand...
Click to collapse
Many thanks! At the moment I achieved to root it with twrp. OEM unlock > installed twrp > fastboot -w > magisk.
At the moment all is okey but I have not been able to unencrypt DATA partition (I have done fastboot -w, but with no success, I have not tried TWRP format because of your advice). That's the only point I can complain about.
I hope I do not have to use the stock rom to unbrick, but I have your advice if I do.
Thanks again!
pabloluih said:
Many thanks! At the moment I achieved to root it with twrp. OEM unlock > installed twrp > fastboot -w > magisk.
At the moment all is okey but I have not been able to unencrypt DATA partition (I have done fastboot -w, but with no success, I have not tried TWRP format because of your advice). That's the only point I can complain about.
I hope I do not have to use the stock rom to unbrick, but I have your advice if I do.
Thanks again!
Click to expand...
Click to collapse
That's weird. If you unlocked the bootloader and install adb/fastboot (must be latest version. Older version will not recognize the phone, download platform-tools from google dev site, don't download adb tools off XDA) + Nokia's driver from emulated CD drive (every time you plug the phone to computer with official rom, you'll see it) properly then it should be able to work.
You need to check the fastboot device driver Device Manager (devmgmt.msc) and see if the driver is properly installed yet.
You can only use "fastboot -w" once the bootloader is unlocked. And booting up the phone. It will say the bootloader is in Orange state.
You need to unlock oem bootloader from developer settings when the stock rom is there. And in fastboot too
Here is how you unlock it:
Enable oem unlock from dev settings
Then reboot to fastboot mode (bootloader)
Do this:
"fastboot oem key "serial number string converted to md5, not imei strings" "
"fastboot oem unlock"
Volume up
Then you are actually unlocked the bootloader.
Unlock from developer settings only will not do the trick. It only allows you to have ability unlock the bootloader in fastboot.
If you stuck on the Encryption unsuccessful screen. Try wipe it with stock recovery or "fastboot -w" (if you properly unlocked the bootloader)
If you think you can't do anything anymore. Just flash the ROM provided you above.
If you need the extracted ROM for SP flash tool and the fastboot driver. I can link it to you.
Most of all drivers will automatically install off Windows Update if you're on Windows 10 (except the fastboot driver, and yes. SP flash tool drivers are also provided by Windows 10 too)
Also. You should update the phone to the latest software update when flashing stock rom too. Because newer builds for this phone is compatible-friendly with GSI rom (Treble ROMs like AOSP Android 9 or 8.1 by phhusson)
Updates on Android 9/10
pabloluih said:
Many thanks! At the moment I achieved to root it with twrp. OEM unlock > installed twrp > fastboot -w > magisk.
At the moment all is okey but I have not been able to unencrypt DATA partition (I have done fastboot -w, but with no success, I have not tried TWRP format because of your advice). That's the only point I can complain about.
I hope I do not have to use the stock rom to unbrick, but I have your advice if I do.
Thanks again!
Click to expand...
Click to collapse
Nokia might harden the security of the device so you can't use Magisk on stock rom.
This might help you after realizing that you want to install custom ROM again after upgrading to android 11 MIUI but you cannot install android 10 or 11 based ROM and stuck with either boot loop or android rescue party.
WARNING: This might wipe every writable partition. Charge your phone at least 20% or more to prevent from destroying these partitions.
Instructions:
1. Download firmware from here
2. Download full ROM (either recovery or fastboot) from here
3. Save the firmware zip file it in either internal storage or sdcard. Reboot to TWRP afterwards
4. Tap install and find the zip file in your storage and install. Wait for a couple of seconds to get done.
To install full ROM
Recovery
1. After installing firmware from recovery mode, don't reboot. If you reboot the system it will fail to boot. Boot to fastboot if you fail this step and flash a recovery image. Proceed with next step.
2. Install full ROM flashable zip from sdcard or internal storage.
3. Format /data. Reboot.
Using fastboot
1. Boot from fastboot mode
2. Extract full ROM fastboot zip file.
3. Open miflash and locate the fastboot folder.
4. Choose flash_all. Click start.
5. The phone reboots itself. Boot to recovery mode and wipe data.
All done. The phone is now downgraded from android 11 back to android 10.
Note: I got 2 anti triggered when attempting to downgrade the phone using recovery and fastboot without installing firmware zip file first. RIP me I guess I voided my warranty anyways so doesnt matter as I already applied some insurance for my device.
TL;DR: Installed Recovery will get erased as I mentioned in WARNING. Please don't skip every step.
Edit: since it made confusion, I split steps for recovery and fastboot mode.
Has anyone tried this procedure?
Im on 12.0.6.0(EU). Bootloader locked (wait 3days) so no TWRP. Want downgrade to 12.0.8.0(EU) and flash Pixelexperience ROM.
It will work?
I'm a bit confusing... Links inserted in first 2 points seem to be the same link. So what I've to download exactly?
I'm on 12.0.7.0 Android 10 but I'm curious to try 12.0.6.0 Android 11 stable beta released some days ago...
PYCON said:
I'm a bit confusing... Links inserted in first 2 points seem to be the same link. So what I've to download exactly?
I'm on 12.0.7.0 Android 10 but I'm curious to try 12.0.6.0 Android 11 stable beta released some days ago...
Click to expand...
Click to collapse
Its not the same. First one is cca. 80MB of size while full rom is 2.4GB for recovery and 4.4GB for fastboot.
I did this method yesterday and its working. No problems whatsoever.
The only thing i would add is you need both versions of rom - recovery and fastboot. Recovery when you flash for the first time in recovery and fastboot when you flash with Mi flash.
And my advice is, android 11 miui is really bad. Its not finished, it stutters a lot, u can't use third party launchers with gesture navigation (at least in my case, Nova lanucher), performance is bad.
Not worth any time.
Steelrock said:
Its not the same. First one is cca. 80MB of size while full rom is 2.4GB for recovery and 4.4GB for fastboot.
I did this method yesterday and its working. No problems whatsoever.
The only thing i would add is you need both versions of rom - recovery and fastboot. Recovery when you flash for the first time in recovery and fastboot when you flash with Mi flash.
And my advice is, android 11 miui is really bad. Its not finished, it stutters a lot, u can't use third party launchers with gesture navigation (at least in my case, Nova lanucher), performance is bad.
Not worth any time.
Click to expand...
Click to collapse
Ok, ok, good to know. I'm just curious... I'll remain with A10 till when A11 will be good enough to be used as a daily driver
Hi. Does this method requires unlocked bootloader? Thanks
hi. this method not working for me !
*phone is unlocked !
ar-rabbiar said:
hi. this method not working for me !
*phone is unlocked !
Click to expand...
Click to collapse
This error is normal because ur phone is unlocked....but the phone should reboot normal in the new ROM. It did not happen this way?
Alin45 said:
This error is normal because ur phone is unlocked....but the phone should reboot normal in the new ROM. It did not happen this way?
Click to expand...
Click to collapse
reboot with bootloop and again. and just miui 12 a11 or rom with selinux permissive working for flash.
The same in here. Bootloop, bootloop....
But if flash the a11 rom it works.
ar-rabbiar said:
hi. this method not working for me !
*phone is unlocked !
Click to expand...
Click to collapse
did you try to flash firmware file from twrp recovery first? also that error means that a checkpoint failed which you need to disable or remove in configuration settings.
tourofeio said:
The same in here. Bootloop, bootloop....
But if flash the a11 rom it works.
Click to expand...
Click to collapse
did you tried recovery or fastboot flashing? and did you installed firmware first before installing full rom?
endva3 said:
Has anyone tried this procedure?
Im on 12.0.6.0(EU). Bootloader locked (wait 3days) so no TWRP. Want downgrade to 12.0.8.0(EU) and flash Pixelexperience ROM.
It will work?
Click to expand...
Click to collapse
i only tried recovery method and it works fine after days of trying. 12.0.6 android 11 is still buggy and miui needs to fix it a lot. most of apps are not well optimized for this flavor.
Today unlocked bootloader. Flashing 12.0.8.0 (i have 12.0.6.0 A11).
Everything work perfect. No bootloop, bootloader relock and works fine
People are probaly skipping some steps.
1. Download Firmware small size files
2. Download full Firmware, both - fastboot and recovery (put it on SD card, small and recovery)
3. Install Twrp or Orangefox recovery (download it from somewhere)
4. Enter into recovery and install small firmware FIRST, dont reboot, install big firmware (recovery version) SECOND
5. do not reboot
6. format data
7. Now reboot into fastboot
8. Extract fastboot firmware zip into new folder on desktop
9. Start Mi flash, select that folder where u extracted files and tick "clean only" on the bottom of the Mi flash if u want to leave bootloader unlocked and from drop down menu near that pick "flash_all.bat".
Thats how i did it.
Steelrock said:
People are probaly skipping some steps.
1. Download Firmware small size files
2. Download full Firmware, both - fastboot and recovery (put it on SD card, small and recovery)
3. Install Twrp or Orangefox recovery (download it from somewhere)
4. Enter into recovery and install small firmware FIRST, dont reboot, install big firmware (recovery version) SECOND
5. do not reboot
6. format data
7. Now reboot into fastboot
8. Extract fastboot firmware zip into new folder on desktop
9. Start Mi flash, select that folder where u extracted files and tick "clean only" on the bottom of the Mi flash if u want to leave bootloader unlocked and from drop down menu near that pick "flash_all.bat".
Thats how i did it.
Click to expand...
Click to collapse
i did the same, but looking to partitions of system, product and vendor, i understand that flashing the files via recovery and fastboot they dont write in that partitions.
looks like the partitions are read only. thanks
I try to flash a custom rom like arrows os via recovery , the rom shows the boot logo of arrows rom, and then bootloop.
tourofeio said:
I try to flash a custom rom like arrows os via recovery , the rom shows the boot logo of arrows rom, and then bootloop.
Click to expand...
Click to collapse
Most probable, u forgot to do a Format data (yes) before reboot to system.
endva3 said:
Today unlocked bootloader. Flashing 12.0.8.0 (i have 12.0.6.0 A11).
Everything work perfect. No bootloop, bootloader relock and works fine
Click to expand...
Click to collapse
Did you flash it from the built-in recovery or with MiFlash? (My 167 hour waiting period ends tomorrow)
Solved people. change the version of the Mi Flash.