Related
I know there have been similar threads, and I'm sorry that I'm raising another one. But reading to all those old topics didn't help me.
It's a friend's i9020T, bought in the US, so returning it back would be a real problem. He never unlocked bootloader, never applied any custom ROMs or Recovery, always updated it over OTA, and sometime in November, after reboots, phone started to hang on Google logo. Usually, it helped to remove the battery and wait some time, but it doesn't any more. We tried to remove it for a full day, didn't helped.
I tried going into recovery and doing full wipe and cache wipe - didn't help
I tried to unlock the bootloader, can select 'Yes', apply it via Power button, but the phone hangs.
If I want to flash anything with fastboot (boot, system img), it complains about locked bootloader
I tried Odin as well, but can't trick the phone into download mode with both volume up and down, again reports to unlock the bootloader
Is there any way to and how to fix this? I cannot transfer anything to internal memory, have stock recovery?
Thanks a lot to all of those who are willing to help, and I've really want to somehow fix the phone, because I don't have here in Serbia where to repair it. Several mobile providers only imported i9023, so they can't fix i9020T
I'm having the exact same problem with a GT-i9020 so would be interested in any help on this!
May need to format phone. Basically reflash latest update via boot loader. Wipe system to factory. And wipe sd
Sent from my Full Android on Crespo using Tapatalk
RANDYRKELLY said:
May need to format phone. Basically reflash latest update via boot loader. Wipe system to factory. And wipe sd
Sent from my Full Android on Crespo using Tapatalk
Click to expand...
Click to collapse
but I downloaded 2.3.6 stock from here, unpacked in the same folder where adb and fastboot are, and tried to do fastboot flash boot boot.img and so, and didn't work, was bugging me that bootloader isn't unlock
Highl1 said:
but I downloaded 2.3.6 stock from here, unpacked in the same folder where adb and fastboot are, and tried to do fastboot flash boot boot.img and so, and didn't work, was bugging me that bootloader isn't unlock
Click to expand...
Click to collapse
That's the problem dude u don't unpack it. U need to leave as a update zip. Look on xda for the stock 4.0.3 update zip or wait till I provide link. U go thru stock recovery if unrooted, and flash with it. To unlock boot loader u need to be in fastboot and type fastboot oem unlock. But u wait first. Lets get it booted. I'll find link.
Sent from my Full Android on Crespo using Tapatalk
Read here
http://www.androidcentral.com/how-manually-update-your-gsm-nexus-s-ice-cream-sandwich
Sent from my Full Android on Crespo using Tapatalk
RANDYRKELLY said:
That's the problem dude u don't unpack it. U need to leave as a update zip. Look on xda for the stock 4.0.3 update zip or wait till I provide link. U go thru stock recovery if unrooted, and flash with it. To unlock boot loader u need to be in fastboot and type fastboot oem unlock. But u wait first. Lets get it booted. I'll find link.
Sent from my Full Android on Crespo using Tapatalk
Click to expand...
Click to collapse
I'll wait for your link and instructions, it's obvious that I am doing something wrong
Thanks mate!
RANDYRKELLY said:
Read here
http://www.androidcentral.com/how-manually-update-your-gsm-nexus-s-ice-cream-sandwich
Sent from my Full Android on Crespo using Tapatalk
Click to expand...
Click to collapse
But I have stock recovery and can't copy anything to internal memory, since my phone doesn't boot
Highl1 said:
I know there have been similar threads, and I'm sorry that I'm raising another one. But reading to all those old topics didn't help me.
It's a friend's i9020T, bought in the US, so returning it back would be a real problem. He never unlocked bootloader, never applied any custom ROMs or Recovery, always updated it over OTA, and sometime in November, after reboots, phone started to hang on Google logo. Usually, it helped to remove the battery and wait some time, but it doesn't any more. We tried to remove it for a full day, didn't helped.
I tried going into recovery and doing full wipe and cache wipe - didn't help
I tried to unlock the bootloader, can select 'Yes', apply it via Power button, but the phone hangs.
If I want to flash anything with fastboot (boot, system img), it complains about locked bootloader
I tried Odin as well, but can't trick the phone into download mode with both volume up and down, again reports to unlock the bootloader
Is there any way to and how to fix this? I cannot transfer anything to internal memory, have stock recovery?
Thanks a lot to all of those who are willing to help, and I've really want to somehow fix the phone, because I don't have here in Serbia where to repair it. Several mobile providers only imported i9023, so they can't fix i9020T
Click to expand...
Click to collapse
First download this : http://www.4shared.com/zip/2L09-JyW/Root_Nexus_S.html
Just unpack , connect your device and click run.bat - that will root your phone and installed new ClockWordMod Recovery
After that you need : remove install-recovery.sh just in .....
run in windows-> Start->at the search bar write cmd and navigate into your android sdk is installed
For me :
C:/"Programs and Files (x86)"/Android/android-sdk/tools/>adb shell
# rm /system/etc/install-recovery.sh
#exit
or with Root Explorer into system/etc/install-recovery.sh just renam it (ex. : .sh.old)
surdu_petru said:
First download this : http://www.4shared.com/zip/2L09-JyW/Root_Nexus_S.html
Just unpack , connect your device and click run.bat - that will root your phone and installed new ClockWordMod Recovery
After that you need : remove install-recovery.sh just in .....
run in windows-> Start->at the search bar write cmd and navigate into your android sdk is installed
For me :
C:/"Programs and Files (x86)"/Android/android-sdk/tools/>adb shell
# rm /system/etc/install-recovery.sh
#exit
or with Root Explorer into system/etc/install-recovery.sh just renam it (ex. : .sh.old)
Click to expand...
Click to collapse
Same thing mate, I ran it, click two times in console, can't unlock the bootloader, I always get stuck on it
Trying to update the drivers for Nexus S : http://www.4shared.com/rar/_bgEMHqk/Nexus_S_Drivers_x86__x64.html
and after that try to run.bat...Good luck!
I'll try today, but my problem is that adb cannot find the device, fastboot can
I would try downloading the full OTA from this thread, rename it to update.zip (for easy typing), place it in a directory where you can run fastboot, then use the command:
Code:
fastboot update update.zip
I got an error
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Should I create android-info.txt (how?) and place it into the zip (where?)
Thanks.
<edit> I saw this topic http://forum.xda-developers.com/showthread.php?t=1131588 and followed this http://forum.xda-developers.com/showthread.php?t=884416&highlight=STOCK but that as well complains about a locked bootloader </edit>
Is the problem solved？
szk5230 said:
Is the problem solved？
Click to expand...
Click to collapse
Not so far, I'm still having trouble with the phone, and no solution so far helped
Highl1 said:
I got an error
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Should I create android-info.txt (how?) and place it into the zip (where?)
Thanks.
<edit> I saw this topic http://forum.xda-developers.com/showthread.php?t=1131588 and followed this http://forum.xda-developers.com/showthread.php?t=884416&highlight=STOCK but that as well complains about a locked bootloader </edit>
Click to expand...
Click to collapse
Sorry my bad, haven't tried that before either...
If it bugs you the bootloader isn't unlcoked before flashing can't you just use
fastboot oem unlock
then commence with flashing your stock image?
Edit - Nevermind...I see you tried that.
any other suggestion? I'm out of ideas
I had this problem in December. I tried everything you tried without any luck so eventually took it back for warranty repair. Unfortunately I had some water damage from 9 months before so they wouldn't touch it. Luckily I got it replaced on my phone insurance but they said it couldn't repaired.
As far as I know it's a hardware fault. With CWM it looked like I could transfer files into the sd but they would disappear! I was able to use Fastboot and Odin but no joy. I had the same errors when trying to apply update using fastboot and never found answers about the "missing" files.
Sorry to come with bad news and good luck! I'm worried it'll happen to my replacement handset so keen to know if you resolve it.
Hi
Earlier I installed TWRP via Philz and that worked fine.
I then reset my phone and flashed Bigxie's Android L, again this worked fine.
I flashed the new radio for the same thread and that worked fine.
I then downloaded CF-Root from here:
http://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip
Ran the Windows Batch file all seemed to go well. Bootloader was unlocked and the big red android appears on screen.
Phone booted back to TWRP, a script ran and then my phone started constantly booting the the TWRP screen.
All I'm getting is teamwin flashing up.
If I power off it goes back to this loop.
Any way I can get this working again ?
Not worried about any data.. I've got all I need backed up.
Thanks
albert_htc said:
Hi
Earlier I installed TWRP via Philz and that worked fine.
I then reset my phone and flashed Bigxie's Android L, again this worked fine.
I flashed the new radio for the same thread and that worked fine.
I then downloaded CF-Root from here:
http://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip
Ran the Windows Batch file all seemed to go well. Bootloader was unlocked and the big red android appears on screen.
Phone booted back to TWRP, a script ran and then my phone started constantly booting the the TWRP screen.
All I'm getting is teamwin flashing up.
If I power off it goes back to this loop.
Any way I can get this working again ?
Not worried about any data.. I've got all I need backed up.
Thanks
Click to expand...
Click to collapse
dont use root toolkits.
flash the factory img via fastboot. then flash twrp again, flash a kernel that allows root, then flash the latest supersu.
Thanks for the reply.
Just want to claify to make sure I don't make it worse..
I've got the L image from Googles site, do I extract the factory.img from that ?
Then flash it using :
fastboot flash factory factory.img
Thanks
Think I may have made things worse..
I extracted the tgz file and while browsing double clicked the flash all batch file.
:silly: Not sure how the hell I clicked it twice.. but it's doing something.. .hopefully not killing my phone.
Any suggestions how I did myself out of this hole..
albert_htc said:
Think I may have made things worse..
I extracted the tgz file and while browsing double clicked the flash all batch file.
:silly: Not sure how the hell I clicked it twice.. but it's doing something.. .hopefully not killing my phone.
Any suggestions how I did myself out of this hole..
Click to expand...
Click to collapse
i dont think hitting it twice will do anything. but you might have to flash the img files separate, as in the flash-all is giving some ppl issues.
simms22 said:
i dont think hitting it twice will do anything. but you might have to flash the img files separate, as in the flash-all is giving some ppl issues.
Click to expand...
Click to collapse
Found out how I've managed to double click.. The trackpad on my laptop is playing up.
I'll have to remember to use a USB mouse with it.
The phone has just rebooted and is coming back up.
Thanks for the advise.. looks like it's working.
I'll start a new thread with a couple of follow up questions.
Thanks
simms22 said:
i dont think hitting it twice will do anything. but you might have to flash the img files separate, as in the flash-all is giving some ppl issues.
Click to expand...
Click to collapse
When doing this, is there any specific order to follow when flashing all the .img files separately? I am also getting errors stating recovery.sig and boot.sig are missing. Does installing separate also take care of this?
Jmurf said:
When doing this, is there any specific order to follow when flashing all the .img files separately? I am also getting errors stating recovery.sig and boot.sig are missing. Does installing separate also take care of this?
Click to expand...
Click to collapse
it appears that the flash-all is having issues and skipping. so by flashing them all individually, you will make sure to flash them all.
After Failing over and over, I finally was able to flash the latest NOUGAT Update provided in the other thread:
http://forum.xda-developers.com/moto-z/how-to/android-7-international-rollout-t3510790
Download the update.zip file "Blur_Version.24.21.46.griffin.retail.en.US.zip" from one of the posts
Main issue for me was i was on the wrong firmware, simple flash the "XT1650-03_GRIFFIN_ROGERS_MPL24.246-45_cid50_subsidy-RGRCA_regulatory-DEFAULT_CFC.xml" firmware by grabbing it from
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
Notice you need the MPL24.246-45 FIRMWARE , the number 45 plays a major role as it will be verified later. I was running the buildnumber MPL24.246-20 instead of 40
once you get that out of the way and are done flashing the MPL24.246-40 firmware, simply adb sideload the Blur_Version.24.21.46.griffin.retail.en.US.zip from your computer, reboot in stock recovery and then hold power and then press volume up and choose the option adb sideload
My sideload failed at 95%, however when i rebooted, it was running nougat
let me know how it goes for you guys
My bootloader is unlocked, and i did not relock it
This is really sad. They said it was going to be this week and a global roll out.
Nothing!
I can't wait until Samsung release the S8E.. Giving this phone to my 8 years old niece to have!
can u make some order here ?
what is your model ?
if u flashed 24.246-45 then u said it needs to be 40
then did u flash the 40 over 45 ?
thanks
hassanman1997 said:
Download the update.zip file "Blur_Version.24.21.46.griffin.retail.en.US.zip" from one of the posts
Main issue for me was i was on the wrong firmware, simple flash the "XT1650-03_GRIFFIN_ROGERS_MPL24.246-45_cid50_subsidy-RGRCA_regulatory-DEFAULT_CFC.xml" firmware by grabbing it from
Notice you need the MPL24.246-45 FIRMWARE , the number 45 plays a major role as it will be verified later. I was running the buildnumber MPL24.246-20 instead of 40
once you get that out of the way and are done flashing the MPL24.246-40 firmware,
Click to expand...
Click to collapse
This is really helpful. I hit the same snag when I tried to upgrade from -17 firmware.
Any chance you could upload the Canadian Rogers firmware (-45) to Mega? It's so painful waiting for 9 hours for it to fail a few minutes from the end.
Yeah I can try, but I won't be home until night, the only pain was waiting 9 hours, and the firmware is -45, I accidently wrote -40 , I don't think there is any firmware with-40
I tried all the above. Still fails for me.
---------- Post added at 05:14 PM ---------- Previous post was at 05:10 PM ----------
I think because the file has been replaced with a v2 so it's failing verification
I'm uploading the Rogers .45 firmware to mega right now. I'll update this post once its done uploading.
Link: https://mega.nz/#!nssGEDiT!hhLkcTM106hmqbH_fiWfAytEV-fgdlYOhUwpcd_sGJY
Downloaded straight from FileFactory and uploaded directly to Mega
Here is: XT1650-03_GRIFFIN_ROGERS_MPL24.246-45
https://drive.google.com/file/d/0Bw3YYHFxKQxVNTBLeWxadUFZOU0/view?usp=sharing
...Now, can someone help me figure out how to flash it? That would be awesome
svetius said:
Here is: XT1650-03_GRIFFIN_ROGERS_MPL24.246-45
https://drive.google.com/file/d/0Bw3YYHFxKQxVNTBLeWxadUFZOU0/view?usp=sharing
...Now, can someone help me figure out how to flash it? That would be awesome
Click to expand...
Click to collapse
Whats the status of your device right now? Are you purely stock? Rooted? Unlocked? TWRP or stock recovery?
Prfndhatrdofman said:
Whats the status of your device right now? Are you purely stock? Rooted? Unlocked? TWRP or stock recovery?
Click to expand...
Click to collapse
I flashed XT1650-03_GRIFFIN_ROGERS_MPL24.246-45 via this method:
http://forum.xda-developers.com/showpost.php?p=69065373&postcount=14
And while the flash was successful, strangely booting into the OS I'm still on -20.
So then I tried to sideload nougat, and it went up to 87% and failed, causing a bootloop. The bootloop can be fixed by manually flashing -45 again (which is so weird because it actually loads -20).
I am unrooted, bootloader locked.
svetius said:
I flashed XT1650-03_GRIFFIN_ROGERS_MPL24.246-45 via this method:
http://forum.xda-developers.com/showpost.php?p=69065373&postcount=14
And while the flash was successful, strangely booting into the OS I'm still on -20.
So then I tried to sideload nougat, and it went up to 87% and failed, causing a bootloop. The bootloop can be fixed by manually flashing -45 again (which is so weird because it actually loads -20).
I am unrooted, bootloader locked.
Click to expand...
Click to collapse
You got further than me. ADB Sideload wouldnt even look at the Nougat OTA zip. tried multiple ADB versions too
svetius said:
I flashed XT1650-03_GRIFFIN_ROGERS_MPL24.246-45 via this method:
http://forum.xda-developers.com/showpost.php?p=69065373&postcount=14
And while the flash was successful, strangely booting into the OS I'm still on -20.
So then I tried to sideload nougat, and it went up to 87% and failed, causing a bootloop. The bootloop can be fixed by manually flashing -45 again (which is so weird because it actually loads -20).
I am unrooted, bootloader locked.
Click to expand...
Click to collapse
Sideload was successful for me, but still completely in a bootloop as well..
for me it worked fine with ADB sideload.
my bootloader is unlocked, i tried locking it back to get official OTA but failed to lock it again.
I tried every method that was mentioned but failed over and over
so here is what I did:
1) removed all the personal files from phone (pictures, videos, texts etc) so i don't lose em
2) flashed the rogers [XT1650-03_GRIFFIN_ROGERS_MPL24.246-45_cid50_subsidy-RGRCA_regulatory-DEFAULT_CFC.xml] firmware by using mfastboot, make sure you grab the mfastbootv2, you can google and download it, use mfastboot and flash the firmware by command lines
3)after flashing, rebooted, set up the device and skipping a few steps to get into homescreen, and then powered off the phone.
4)downloaded Blur_Version.24.21.46.griffin.retail.en.US.zip and placed it in the adb folder, make sure you download the latest adb tools, you can google and find them easily too
5) extract the adb folder and place the Blur_Version.24.21.46.griffin.retail.en.US.zip in side that folder
6) reboot the phone and press volume to navigate to recovery, you should boot into stock recovery as you flashed stock firmware
7) hold power button and press volume up and youll see the menu, select update by ota and connect to the phone
8) open command line in the adb tools and use command to flash ota via adb
9) mine failed at 95% because of system image error, so instead of rebooting it, i used the command again and flashed the ota via adb, it failed again, however when i rebooted i was presented by the new red moto boot animation, there i knew it was updated to android N
*Delete*
hassanman1997 said:
After Failing over and over, I finally was able to flash the latest NOUGAT Update provided in the other thread:
http://forum.xda-developers.com/moto-z/how-to/android-7-international-rollout-t3510790
Download the update.zip file "Blur_Version.24.21.46.griffin.retail.en.US.zip" from one of the posts
Main issue for me was i was on the wrong firmware, simple flash the "XT1650-03_GRIFFIN_ROGERS_MPL24.246-45_cid50_subsidy-RGRCA_regulatory-DEFAULT_CFC.xml" firmware by grabbing it from
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
Notice you need the MPL24.246-45 FIRMWARE , the number 45 plays a major role as it will be verified later. I was running the buildnumber MPL24.246-20 instead of 40
once you get that out of the way and are done flashing the MPL24.246-40 firmware, simply adb sideload the Blur_Version.24.21.46.griffin.retail.en.US.zip from your computer, reboot in stock recovery and then hold power and then press volume up and choose the option adb sideload
My sideload failed at 95%, however when i rebooted, it was running nougat
let me know how it goes for you guys
My bootloader is unlocked, and i did not relock it
Click to expand...
Click to collapse
OK, so i got it working. But there were some difficulties.
I was on 24.246-45 already, but i installed TWRP and a custom kernel. I reflashed the recovery and boot from the BELL 24.246.45 firmware, and proceeded sideloading the update. It errored out, saying system was mounted r/w once (after I installed TWRP, but I never altered it beyond that).
So i flashed the system chunks from the firmware ( "mfastboot flash system system.img_sparsechunk.0" , "mfastboot flash system system.img_sparsechunk.1" etc.), then i retried the sideload, and it worked. The system information still says the build number is MPL24.246-45, but the android version is 7.0, everything seems to be working, including split screen, the new easter egg, quicklaunch ribbon, and new notifications.
gomisensei said:
... The system information still says the build number is MPL24.246-45, but the android version is 7.0, everything seems to be working, including split screen, the new easter egg, quicklaunch ribbon, and new notifications.
Click to expand...
Click to collapse
This should be only a "cosmetic" issue... probably you can fix it by editing build.prop...
enetec said:
This should be only a "cosmetic" issue... probably you can fix it by editing build.prop...
Click to expand...
Click to collapse
meh, i'm not really worried about it, at least not enough to guess what the version SHOULD be...
gomisensei said:
meh, i'm not really worried about it, at least not enough to guess what the version SHOULD be...
Click to expand...
Click to collapse
:laugh:
Does that actually work for other software channels as well?
I'm from india, my software chanel is retin (retail India) can I still flash the one that came for retus?
Sent from my Moto Z using XDA Labs
Hi
My Honor 6x is rooted with magikmask bootloader unlock and TWRP.
Actualy build BLN-L21C432B151 I want to update to BLN-L21C432B360 but I don't know how to do
Can some one help me please
do you ever received update from updater app
The OTA say's me to update if that's your question
then update dude .. after update your root will be removed , root again
Ok. Want to be sure when I was looking on internet some people said it's imposible to update with a bootloader unlock
I'll update and root again Thank's
just one other think if I update will I need to re unlock bootloader and TWRP ?
Deecy said:
Ok. Want to be sure when I was looking on internet some people said it's imposible to update with a bootloader unlock
I'll update and root again Thank's
just one other think if I update will I need to re unlock bootloader and TWRP ?
Click to expand...
Click to collapse
some times the bootloadet will lock after big updates so better to backup your data and then relock again and flash twrp
Deecy said:
Ok. Want to be sure when I was looking on internet some people said it's imposible to update with a bootloader unlock
I'll update and root again Thank's
just one other think if I update will I need to re unlock bootloader and TWRP ?
Click to expand...
Click to collapse
Did you manage to update your system? I tried everything, always getting an error that the update can't get verified.
I have a rooted, unlocked twrp system on android 7.0 EUMI 5.0 (BLN-L21,Honor 6x)
already tried to flash stock recovery, remove magisk(root), busybox but I still can't update the system.
I would really appreciate the help.
Try dload method with latest furmware
narshi shukla said:
Try dload method with latest furmware
Click to expand...
Click to collapse
That will also work.
citizenserious said:
Did you manage to update your system? I tried everything, always getting an error that the update can't get verified.
I have a rooted, unlocked twrp system on android 7.0 EUMI 5.0 (BLN-L21,Honor 6x)
already tried to flash stock recovery, remove magisk(root), busybox but I still can't update the system.
I would really appreciate the help.
Click to expand...
Click to collapse
You can do via dload only. Earlier i uswd to update just by flashing the stock recovery but recently on 6X this messed up badly may be volte and hence update failed and then it gave me to download the full firmware with prompt as your data partition is messed up amd needs to be fixed and after downloading the fill OTA update, got success. But then proceeded with debranding the next night
shashank1320 said:
You can do via dload only. Earlier i uswd to update just by flashing the stock recovery but recently on 6X this messed up badly may be volte and hence update failed and then it gave me to download the full firmware with prompt as your data partition is messed up amd needs to be fixed and after downloading the fill OTA update, got success. But then proceeded with debranding the next night
Click to expand...
Click to collapse
Hey brother, i tried many times to update from B360 to B365 (not full package, only 547MB) reflashing stock B360 recovery, but i always receive errors while recovery is verifying the package. I tried even dload method with .zip archives but i always achieve a failure and it is just boooooring :silly: You know other methods to try? Like adb or terminal emulator commands to update, or else... I cannot figure out how to correctly update my device. I have both B365 packages, FULL or partial OTA update downloaded. Thanks in advance
RedSkull23 said:
Hey brother, i tried many times to update from B360 to B365 (not full package, only 547MB) reflashing stock B360 recovery, but i always receive errors while recovery is verifying the package. I tried even dload method with .zip archives but i always achieve a failure and it is just boooooring :silly: You know other methods to try? Like adb or terminal emulator commands to update, or else... I cannot figure out how to correctly update my device. I have both B365 packages, FULL or partial OTA update downloaded. Thanks in advance
Click to expand...
Click to collapse
Cant believe you are facing issues now who helps every new user.
Nope bro. I still recommend to use dload only to flash full firmware. It should be full firmware and not the 547 MB.
Just to be in stock and use one of the app today, I relocked bootloader but then got the prompt as my data partition is damaged and need format. I allowed and then it was only erecovery and bootloader.
Then i unlocked and it went straight to twrp. And from there reboot to system works fine. I have the files and once really needed i will dload but problem with stock is that it doesn't have in-built call recording.
Edit-What is exact firmware BLN-L21CXYZB365?
shashank1320 said:
Nope bro. I still recommend to use dload only to flash full firmware. It should be full firmware and not the 547 MB.
Just to be in stock and use one of the app today, I relocked bootloader but then got the prompt as my data partition is damaged and need format. I allowed and then it was only erecovery and bootloader.
Then i unlocked and it went straight to twrp. And from there reboot to system works fine. I have the files and once really needed i will dload but problem with stock is that it doesn't have in-built call recording.
Edit-What is exact firmware BLN-L21CXYZB365?
Click to expand...
Click to collapse
Well let's say that looks like it's my turn now; Huawei mechanisms are much complicated sometimes, a little detail can let you puzzle an hour like and maybe it's only a joke. My previous device was a Samsung, so except common Android related functions EMUI is a new world for me. Only full firmware will work so, ok. Do i have to reinstall every app, or modify again my whole settings menu if i update using the full firmware package, i suppose..? What do you mean with "use one of the app today"? I didn't relocked bootloader because i thought that stock recovery could be enough. Overall, the risk to encounter an error like yours would be a bore, generally. Which files are you referring to, update files? My full build number is BLN-L21C432B360, I'm trying to update to B365.
However if you need call recording function (me too), there's a working method posted by an user in this thread https://forum.xda-developers.com/honor-6x/themes/callrecord-t3650864 that enables official call recording function from EMUI, check it. I followed this months ago on my BLN-L21, who had no call record at all by default in my firmware, and it flawlessly worked. I recommend it to you.
RedSkull23 said:
. Do i have to reinstall every app, or modify again my whole settings menu if i update using the full firmware package, i suppose..? What do you mean with "use one of the app today"?
I didn't relocked bootloader because i thought that stock recovery could be enough. Overall, the risk to encounter an error like yours would be a bore, generally. Which files are you referring to, update files? My full build number is BLN-L21C432B360, I'm trying to update to B365.
However if you need call recording function (me too), there's a working method posted by an user in this thread https://forum.xda-developers.com/honor-6x/themes/callrecord-t3650864 that enables official call recording function from EMUI, check it. I followed this months ago on my BLN-L21, who had no call record at all by default in my firmware, and it flawlessly worked. I recommend it to you.
Click to expand...
Click to collapse
I was using Tez app from play store but it didnt work may be because i am rooted with unlocked bootloader and need to bypass the safety check.
For call recording, I am already usimg a zip since debranding and works fine. I have Posted in 5C repository. But we need to be rooted for this with custom recovery.
If you are rooted then can take twrp backup and restore apps if on stock and non rooted then hisuite.
As far as i have tested on my 5c, dload won't wipe data but still i would recommend to have full backup brother.
---------- Post added at 11:31 AM ---------- Previous post was at 11:16 AM ----------
RedSkull23 said:
Only full firmware will work so, ok. Do i have to reinstall every app, or modify again my whole settings menu if i update using the full firmware package, i suppose..? What do you mean with "use one of the app today"? I didn't relocked bootloader because i thought that stock recovery could be enough. Overall, the risk to encounter an error like yours would be a bore, generally. Which files are you referring to, update files? My full build number is BLN-L21C432B360, I'm trying to update to B365.
.
Click to expand...
Click to collapse
BLN-L21C432B365 full firmware-
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1279/g104/v93141/f1/full/update.zip
shashank1320 said:
As far as i have tested on my 5c, dload won't wipe data but still i would recommend to have full backup brother.
---------- Post added at 11:31 AM ---------- Previous post was at 11:16 AM ----------
BLN-L21C432B365 full firmware-
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1279/g104/v93141/f1/full/update.zip
Click to expand...
Click to collapse
Surely I'll take a backup pal, i already got burned time ago and now i never do something without doing a nandroid backup bfore Thanks for the link, but i already have the FULL package downloaded OTA stored on my PC, so as suggested even by another user today I'll try again dload method but with full package other than partial one, it shouldn't erase my data and even if it should, I'll have a system image.
Only one thing now; in the folder where OTA was saved on my phone, as habit i found 3 packages; update.zip, update_data_public.zip and update_BLN-L21_hw_eu.zip. In this case, in dload folder on my phone i have to extract all the zips or only the main update.zip and leave the other two zipped?
RedSkull23 said:
Surely I'll take a backup pal, i already got burned time ago and now i never doing something without a nandroid backup bfore Thanks for the link, but i already have the FULL package downloaded OTA stored on my PC, so as suggested even by another user today I'll try again dload method but with full package other than partial one, it shouldn't erase my data and even if it should, I'll have a system image.
Only one thing now; in the folder where OTA was saved on my phone, as habit i found 3 packages; update.zip, update_data_public.zip and update_BLN-L21_hw_eu.zip. In this case, in dload folder on my phone i have to extract all the zips or only the main update.zip and leave the other two zipped?
Click to expand...
Click to collapse
Extract and use only main update.zip, put all files in dload and it will do.
Have backup but I just tested and flashed full B340 again on my phone and no data loss.
shashank1320 said:
Extract and use only main update.zip, put all files in dload and it will do.
Have backup but I just tested and flashed full B340 again on my phone and no data loss.
Click to expand...
Click to collapse
Thanks for the tip brother!
So this evening i tried to use only the extracted files from the main update.zip in dload folder; then, via ProjectMenu, i choose software upgrade and loaded the update after reflashing stock recovery for B360, that i took from your repository thread, since that time ago i didn't made a copy of my stock recovery before flashing TWRP. What i obtained was a soft-brick, i really don't know why on earth because usually it just fails at 5% while verifying the package and stop, it reboots to system... so i flashed again TWRP from fastboot and now i'm restoring my backup made today.
Crap, Huawei just CAN'T make things like updating OTA such difficult! I uninstalled Magisk before doing that, but i think that it fails because i miss a clean stock boot.img. Anyway WTF all these steps for an OTA is foolish.
I provided a guide how I managed to update my rooted device and keep all my stuff, settings and apps and reroot.
Just take a look here:
https://forum.xda-developers.com/ho...rootet-h6x-t3684758/post74102863#post74102863
I already did two successful updates with this method.
If there is a question just ask in that forum.
RedSkull23 said:
So this evening i tried to use only the extracted files from the main update.zip in dload folder; then, via ProjectMenu, i choose software upgrade and loaded the update after reflashing stock recovery for B360, that i took from your repository thread, since that time ago i didn't made a copy of my stock recovery before flashing TWRP. What i obtained was a soft-brick, i really don't know why on earth because usually it just fails at 5% while verifying the package and stop, it reboots to system... so i flashed again TWRP from fastboot and now i'm restoring my backup made today.
Crap, Huawei just CAN'T make things like updating OTA such difficult! I uninstalled Magisk before doing that, but i think that it fails because i miss a clean stock boot.img. Anyway WTF all these steps for an OTA is foolish.
Click to expand...
Click to collapse
Sorry to hear you that bro.
I myself flashed the same firmware yesterday to test this without backup (hisuite backup taken on 7th). I did via dload the same firmware and it was successful without any data loss, but yeah, I lost root, call recording feature that I flashed 20 days back.
I was planning to return to full stock because I know OTA will mess up if received on this state.
Not sure what went wrong buddy with your case. If it is due to any of the file in repository, I apologise for it.
After having the bootloader and FRP unlocked im now stuck since hours within the TWRP installation. I followed every guide I could find step by step with no success - but I found quite high amount of people having the same problem with apparently no solution.
However, I tried the ADB method, flashing TWRP to my BLN-L21 with EMUI 4.1.3. Obviously the flash process succeeded. But instead opening the TWRP screen, the 6x is stuck saying "device is booting..." for hours.
Same with the chinese tool. Stuck, too.
Yes, USB debugging is enabled and yes, OEM Lock is unlocked. Yes, I didn't reboot to system (used power and volume down instead). No success at all.
I'm quite sure, it's a tiny little mistake I make and I wonder, if there is anyone who did a TWRP installation successfully and knows, what I did the wrong way.
Thanks for your help.
Which TWRP you used?
RedSkull23 said:
Which TWRP you used?
Click to expand...
Click to collapse
Finally I managed to install TWRP and get it to work. The little mistake was really small; I had to unplug the device prior to boot to TWRP. :angel:
Unfortunately I did a full wipe (like I used to do on my old Nexus devices) and now I'm caught in a bootloop.
I can
- access fastboot mode (phone unlocked, FRP unlocked)
- access TWRP 3.0.2-0
Problem: I do not know which Firmware to flash, there are too many to choose from in Firmware Finder, although I know the product model BLN-L21.
Firmware Finder shows BLN-L21C10, BLN-L21C185, BLN-L21C432 and, in addition, three Berlin-L21xxx versions. Which is the right one and how is the correct procedure to flash?
Stock was Android 6.
Any idea?
C10 Russia
C185 Middle East
C432 Europe
Download firmware for your region and unzip.
Create folder on an SDCard named dload
Move update.app from firmware to dload
Turn phone off
Hold Vol + / Vol - / Power to force flash firmware
That worked like a charm!
Thank you very much for your support.
It could have been so easy - and took me hours.
Thanks again.
nakedtruthishere said:
That worked like a charm!
Thank you very much for your support.
It could have been so easy - and took me hours.
Thanks again.
Click to expand...
Click to collapse
No problem, glad I could help:good:
Dazed No More said:
C10 Russia
C185 Middle East
C432 Europe
Download firmware for your region and unzip.
Create folder on an SDCard named dload
Move update.app from firmware to dload
Turn phone off
Hold Vol + / Vol - / Power to force flash firmware
Click to expand...
Click to collapse
yes but you must extract the update.app from update.zip with the extraction tool then put on the sd card in the dload folder
trwilson1974 said:
yes but you must extract the update.app from update.zip with the extraction tool then put on the sd card in the dload folder
Click to expand...
Click to collapse
You have no idea what you are talking about.
Dazed No More said:
You have no idea what you are talking about
thanks
i have just done what i said and that is to unzip (extract) the update.zip file to get the update.app file.
that file (the update.app file) is what i put on my sdcard in the dload folder i created. It simply would not work until i unzipped the file.
It works for me! Im not sure why you are having issues mr Dazed No More..
Click to expand...
Click to collapse
trwilson1974 said:
Dazed No More said:
You have no idea what you are talking about
thanks
i have just done what i said and that is to unzip (extract) the update.zip file to get the update.app file.
that file (the update.app file) is what i put on my sdcard in the dload folder i created. It simply would not work until i unzipped the file.
It works for me! Im not sure why you are having issues mr Dazed No More..
Click to expand...
Click to collapse
The very first step of my instructions said to download to firmware and unzip it. Then you came and tried to correct me after the other person followed my steps and said it worked like a charm.
You also talk about extraction tool which is used to extract images from update.app. So maybe you know what you are taking about, you just need to say what you mean.
Click to expand...
Click to collapse
Dazed No More said:
trwilson1974 said:
The very first step of my instructions said to download to firmware and unzip it. Then you came and tried to correct me after the other person followed my steps and said it worked like a charm.
You also talk about extraction tool which is used to extract images from update.app. So maybe you know what you are taking about, you just need to say what you mean.
Click to expand...
Click to collapse
Ok im sorry for the confusion, i was honestly just trying to help. I will keep my opinions and comments to myself from now on!!!
Good day
Click to expand...
Click to collapse