I was able to revive the phone that received the OTA and become bricks
It was also restored after downgrade firmware and receiving OTA
By clicking the link you will find various files
VERY IMPORTANT
Choose your model file and region, Otherwise, problems may occur
Always start with the lowest recovery bootloader
V30.70 -> V30.71 -> V30.B0 -> V30.B2 -> V30.B4 -> V30.B6 -> V30.B7 -> V30.B9 -> V30.BA -> V30.BC -> V30.BD -> V30.BE
some versions may not be due to the fact that the firmware is too old or did not go to the region
---------------
3 is located inside the archive folder
0_UnBrick << fastboot boot repair
1_Repair_Boot (RSD Lite) << recovery by RSD Lite GPT & BL
2_Flash_All_FW (RSD Lite) << copy the file to your Official firmware and flash by the RSD Lite
Click to expand...
Click to collapse
- shouldn't be afraid of Qualcomm HS-USB QDLoader 9008;
- do not change any files, pathes;
- can install drivers manually;
- need to install python-2.7.9 and pyserial-2.7.win32;
there is also a hybrid archives for those who pierced themselves 5.1 on a different model or region
eg XT*******_B7BE
they contain GPT with previous versions and new bottles V30.BE -it is very important for the owners of ATT & VZW
Please do not copy files to other file shares
the project is under constant development and refinement
Storage of files for restoration, please give the following links to it and not distribute the files
https://yadi.sk/d/Hz8MUEUThsp4f
Drivers, Soft there -> https://yadi.sk/d/p458Cy0XineRC
soon result in closed beta test
were tested
Moto XT1080M =firmware XT1058DE + OTA BLV30.BE -> Downgrade to XT1058BR 5.0+OTA = Brick restored to SU6-7
Moto XT1030 =firmware XT1058BR + OTA BLV30.BE -> Downgrade to XT1058BR 5.0+OTA = Brick restored to SU6-7
Moto XT1058 =firmware XT1058DE 5.1 + OTA BLV30.BE -> Downgrade to XT1058DE 5.0+OTA = Brick restored to stock
Moto XT1060DEV =firmware XT1052DE 5.1 + OTA BLV30.BE -> Downgrade to XT1060 4.4.4+OTA 212.163.3 = Brick restored to stock
Moto XT1058 Rogers 5.1 Bootloader 30.BE -> Downgrade to Stock 4.4.4 + OTA 212.144.12 = Brick restored to stock
for several days method will be finalized and available for use
Moto XT1060DEV =firmware XT1052DE 5.1 + OTA BLV30.BE -> Downgrade to XT1060 4.4.4+OTA 212.163.3 = Brick restored to stock
---------- Post added at 08:53 PM ---------- Previous post was at 08:50 PM ----------
My guide is not complete without CrashXXL finding concerning 30.BE, but what can I do - he is the Master ))) All kudos go to CrashXXL!
XT 1058 Rogers 5.1 Bootloader 30.BE -> Downgrade to Stock 4.4.4 + OTA 212.144.12 = Hard Brick -> restored to stock
THANK YOU Crash!!!
Penny flew
Would be awesome to be able to downgrade lower than 4.4.4
jahrule said:
Would be awesome to be able to downgrade lower than 4.4.4
Click to expand...
Click to collapse
downgrade the firmware can not be due to aircraft parts
you are stitched motoboot above qFuse burns jumper, return it to the reverse position can not be
CrashXXL said:
downgrade the firmware can not be due to aircraft parts
you are stitched motoboot above qFuse burns jumper, return it to the reverse position can not be
Click to expand...
Click to collapse
Makes sense. Thanks again for your great work. You working on a system write protection disable you need help on let me know.
I tried to fix the Boot loop that always boot into bootloader ended up hard bricked my phone. any chance ? was on 5.1
Gigahyperprime1 said:
I tried to fix the Boot loop that always boot into bootloader ended up hard bricked my phone. any chance ? was on 5.1
Click to expand...
Click to collapse
Now the method is tested until restored 5 out of 5
also addressed the issue of its free or paid access
<3
CrashXXL said:
Now the method is tested until restored 5 out of 5
also addressed the issue of its free or paid access
Click to expand...
Click to collapse
Tks man, still waiting for it
UPD
all files
Not there yet
CrashXXL said:
UPD
all files
Click to expand...
Click to collapse
Thanks a lot for putting the time to make this work... did not have much luck yet. I still can't get to the fast boot screen - after shorting to make the com por appear I flash step 0 but the phone stays on emergency download mode. If I attempt to manually induce a fastboot (by pressing volume down and power) the phone drops the com port from windows but does not enter fast boot. After that I have to short the system to make the com port appear again.
Battery is charged (I think) as I can measure 4.2 V on the multimeter I have a XT1058BR if that matters. Any clues to what is going on ? Suggestions ?
Thanks!
M.
cneto100 said:
Thanks a lot for putting the time to make this work... did not have much luck yet. I still can't get to the fast boot screen - after shorting to make the com por appear I flash step 0 but the phone stays on emergency download mode. If I attempt to manually induce a fastboot (by pressing volume down and power) the phone drops the com port from windows but does not enter fast boot. After that I have to short the system to make the com port appear again.
Battery is charged (I think) as I can measure 4.2 V on the multimeter I have a XT1058BR if that matters. Any clues to what is going on ? Suggestions ?
Thanks!
M.
Click to expand...
Click to collapse
write what version of firmware you standing?
but rather let it link
CrashXXL said:
write what version of firmware you standing?
but rather let it link
Click to expand...
Click to collapse
I was on Blur_Version.222.21.7.ghost_row.Brasil.en.BR.zip then attempted an OTA for 222.21.15, got into a bootloop - attempted to go back to 222.21.7 with resulted in a bricked device. .15 is the final one for 5.1 in Brazil while .7 is the latest soak test (for 5.1).
While on .7 I think I still had a 4.4.4 bootloader as I installed that by flashing a capture removing the gpt.bin and motoboot.bin from the xml.
M.
cneto100 said:
I was on Blur_Version.222.21.7.ghost_row.Brasil.en.BR.zip then attempted an OTA for 222.21.15, got into a bootloop - attempted to go back to 222.21.7 with resulted in a bricked device. .15 is the final one for 5.1 in Brazil while .7 is the latest soak test (for 5.1).
While on .7 I think I still had a 4.4.4 bootloader as I installed that by flashing a capture removing the gpt.bin and motoboot.bin from the xml.
M.
Click to expand...
Click to collapse
Forgot to mention that when I try to reset the phone by pressing the volume + / - and power at the same time the phone green light blinks . Other then that , there is no sing of life coming from it. ..... I know the green light might mean low batt, but as I said before the voltage seems high enough.
M.
https://yadi.sk/d/Hz8MUEUThsp4f/MBM
first try this one MBM-NG-V30.B7.ZIP
if not start, this MBM-NG-V30.BE.ZIP
Then flash the stock using XML -> Flash_noBL.xml copy in stock Firmware
your down load links dont seam to work? i have numerous bricked boards i will try your method
thank you for the effort, im not native english spoken, my question is: this procedure and files can aply to an moto g hard bricked? since some time ago i read a post with files of a moto g wich flash in a moto x with success., thanks for the response and the work you do.
It worked!
first try this one MBM-NG-V30.B7.ZIP
if not start said:
CrashXXL you are the man! It worked!!!! Not at first, but it worked. I tried first to flash both B7 and BE files you posted w/o success. The system would not leave the emergency download mode and would not get to fast boot. Then for some random reason I decided to run the second step from s5610 tutorial
"Wait 10 seconds, then launch next bat-file, and wait until finish:
RUN_moto_x_bootloader_flash.bat"
and then try to run the BL flash again and this time it worked ! Maybe you can explain me what happened.
In any case, once the system was on fastboot I did your step one and flashed gpt.bin and motorboat.bin . After that the system booted into android w/o any additional help . I will still flash a fresh system just in case.
Anyways, thanks really a lot for the help . I was already looking for used boards !
I actually need to thank S5610 for putting up his tutorial also.
Best for you all,
M.
Click to expand...
Click to collapse
xt1060 B7, i ran this command (qflash.exe -com7 -ramload MPRG8960.hex -mbn 33 MSM8960_bootloader_singleimage.bin -v -o) from the 0_ unbrick file and BAM fastboot! then from rsd lite i located (1_repair_boot (rsd lite)) and my once dead x now lives!
crashxxl all thanks to you!:good:
Related
I had rooted my 4.4.4 with kingroot, changed to SuperSU with supersume and unrooted with SuperSU. Then Iwent back to stock (all official no Knox) with Odin (4.4.4 (A500FUXXU1AOB4_A500FUATO1AOB1_A500FUXXU1AOB4_HOME.tar.md5).
Then I went from stock to 5.0.2 (A500FUXXU1BOE6_A500FUATO1BOE1_A500FUXXU1BOE6_HOME.tar.md5) with Odin.
Actually after updating from 4.4.4 to 5.0.2 (with odin) the phone converted a lot of apps during startup - Did this also take minutes for you guys ?
All fine and phone quite fast, but no chance to root with Kingroot.
So I wanted back to 4.4.4 I used Odin again and flashed the 4.4.4 as written above. I did not tick reboot in Odin and so I powered off the phone after Odin said that all was flashed OK.
Now the phone is off (body is cold) and not repsonding to POWER+HOME+VOL+(or -).
After searching in xda it looks like I should have flashed all except the bootloader or flashed another BL first. I am confused and frustrated.
Hope you can help !
deleted
deleted
did you try a soft reset? remove battery and sim card for 30 seconds and put back.
!!! Bat is built in !!!
- Jig (300kOhm between Pin 4 an 5/GND on USB plug) works on S5mini immediately after plug in.
- On Tab S (built in bat like my A5) one has to press power additionally to the JIG plugged in.
Still no luck on A5 (SM-A500FU)
1 Still no idea what I did wrong
2 How could I empty the bat ??? (I did not measure any power on the USB plug, so no chance to drain it and its 2300mA fully loaded)
Does the screen comes up when you plug jn the charger?
no nothing
gggg said:
no nothing
Click to expand...
Click to collapse
Try leaving it on charger for a few mins or maybe an hour. If that doesnt make it react then its a hard brick and woukd suggest a repair center.
Sent from my SM-G850F
THX ... I ll tried that ... no change
Could you guys please give me some ideas, what possibly could have gone wrong !
gggg said:
THX ... I ll tried that ... no change
Could you guys please give me some ideas, what possibly could have gone wrong !
Click to expand...
Click to collapse
Probably you can t downgrade the bootloader... If you plug it to your pc does odin show something?
You said you cant boot in download mode that means your stuck in a hard brick that you cant recover by yourself. I managed to unbrick devices that at least could boot in download mode, i think only a repair center can help you
No nothing. No, not even the JIG does work. (Usally after plugging the JIG an hitting POWER or supplying power from charger through the JIG plug, it should go to download mode). So I will give up on it.
But I still would like to know what I did wrong ... lots of others seem to downgrade without an issue:
http://forum.xda-developers.com/galaxy-alpha/general/downgrade-5-0-2-to-4-4-4-t3141337, http://forum.xda-developers.com/galaxy-alpha/general/downgrade-5-0-2-to-4-4-4-t3125264
gggg said:
I had rooted my 4.4.4 with kingroot, changed to SuperSU with supersume and unrooted with SuperSU. Then Iwent back to stock (all official no Knox) with Odin (4.4.4 (A500FUXXU1AOB4_A500FUATO1AOB1_A500FUXXU1AOB4_HOME.tar.md5).
Then I went from stock to 5.0.2 (A500FUXXU1BOE6_A500FUATO1BOE1_A500FUXXU1BOE6_HOME.tar.md5) with Odin.
Actually after updating from 4.4.4 to 5.0.2 (with odin) the phone converted a lot of apps during startup - Did this also take minutes for you guys ?
All fine and phone quite fast, but no chance to root with Kingroot.
So I wanted back to 4.4.4 I used Odin again and flashed the 4.4.4 as written above. I did not tick reboot in Odin and so I powered off the phone after Odin said that all was flashed OK.
Now the phone is off (body is cold) and not repsonding to POWER+HOME+VOL+(or -).
After searching in xda it looks like I should have flashed all except the bootloader or flashed another BL first. I am confused and frustrated.
Hope you can help !
Click to expand...
Click to collapse
You were meant to downgrade after making a full reset. However, failing to do that will still allow the phone to boot and it will be a soft brick. And recovery and boatloader shouldn't be affected and be perfectly functional.
Can you boot into recovery? If you can, do a full wipe and then install the ROM you desire.
droidqwerty said:
...
Click to expand...
Click to collapse
This is what I also dont understand .... because as I said no reaction at all (no recovery, download mode, not even with a JIG) ....
gggg said:
This is what I also dont understand .... because as I said no reaction at all (no recovery, download mode, not even with a JIG) ....
Click to expand...
Click to collapse
You mean no logo or even no turn-on vibration?
droidqwerty said:
You mean no logo or even no turn-on vibration?
Click to expand...
Click to collapse
yes
What happens when you plug it into charger?
My final opininon is that it needs service.
Sent from my SM-G850F
this downgrade from 502 to 444 than again 502 you have mess up with bootloader ,
I dont know who bootloader 502 or 444 FW but that you yourself make mess is true
all recommend avoiding the frequent downgrade of FW
hensk said:
this downgrade from 502 to 444 than again 502 you have mess up with bootloader ,
I dont know who bootloader 502 or 444 FW but that you yourself make mess is true
all recommend avoiding the frequent downgrade of FW
Click to expand...
Click to collapse
I went 4.4.4>5.0.2>4.4.4 - no more !
1 Can you please explain more in detail what caused the trouble in your opinion
2 How can this be avoided = how to to that with Odin / how to just flash Stock.tar without or with another Bootloader ?
3 Which bootloaders (primary and secondary??) should be flashed togerther with 4.4.4 or 5.0.2 ?
You should factory reset before downgrading, otherwise your phone would be soft bricked
You can find it here: ftp://fw.ydevices.com/YotaPhone2/Firmwares/RU/
Install either via OTA update if you're already on the 1.87 RU ROM like I am. On my device it first wanted to install the update only, about 67MB, but it failed to install; then the next time I checked for updates after reboot through the settings update menu, it downloaded the full file, about 0,99 GB. Then the update went all the way through. SuperSU is lost on the way, I will try if it still works through the recovery installation.
You can also install through Yotaflasher like it's explained here: http://forum.xda-developers.com/showthread.php?t=3247356
Didn't have time to test things out, but it's still Lollipop 5.0, so only bugfixes and some new yotapanel features I guess.
Enjoy!
Thanks for that muchly dude, hadn't checked that for a while.
Update seems to be stability improvements, power efficiency improvements and some yotamirror and panel improvements and features.
Its not 5.1, but it's an update, I'll take it.
And yeah, super glad moved to the RU ROM. Backing up now, will OTA flash update once that's done. SuperSU has been flashable everytime after an update so far so fingers crossed.
All up and running .
I was rooted, running RU 1.87 with TWRP - phone handled it all just fine - downloaded OTA, pressed install - it went to TWRP > flashed stock recovery back over itself > rebooted and installed.
Phone booted up, all working fine. Lost root - simple reboot and flash the SU.zip had sitting there from the last update. Cache and Dalvik wiped for good measure.
Reboot and all is well and back to normal but with a few improvements, lovely.
About as easy as it's even been done really.
Hope everyone else gets to enjoy the update through similarly smooth procedures .
Yeah, I ended up doing a fresh installation plus rooting, everything smooth. I'm never too sure what an update leaves behind.
It's really a great device, hopefully they'll keep updating things for a while. Of course version 6.0 would be welcomed... Apparently, by the numbering they use, next step would be either 1.2.xx with Android 5.1 or 2.x.xx with 6.0. Let's see.
Fair play, I toyed with idea of it, but was fresh from last install and honestly don't have the time to set everything up again.
My hope is they take all their good ideas from this and can at least join someone else in making a great device.
Saw a working bendy phone the other day, lets you turn pages on reading app by bending corner as you would a book etc. I thought if that could be combined with yota tech, then you have damn near the perfect tablet.
Honestly I don't think we'll get 5.1, let alone 6.0. They're refining their ideas in prep for Yotaphone 3, that and the possible tablet are their main focus right now.
Interestingly, the update flashed it's stock recovery over twrp - someone prepared for the possibility of root owners this time around. So they are still paying attention .
So any idea what's the difference between the EU and the RU rom? I mean there has to be some reason they are two separate roms.
To answer my own question: there isn't too many differences between EU and RU roms. I did a diff between the RU1.1.59 and EU1.1.60, and out of 2092 files, roughly 1900 of the files inside system.img were identical. The APKs were slightly different, but only slightly. So probably the difference comes from some differently named resources.
The RU version also has some additional apps which the EU version does not have, such as Esquire, Questions, Strelka and Vector. These are probably the main reason why they have different ROMs. They might only work in Russia.
Jeopardy said:
To answer my own question: there isn't too many differences between EU and RU roms. I did a diff between the RU1.1.59 and EU1.1.60, and out of 2092 files, roughly 1900 of the files inside system.img were identical. The APKs were slightly different, but only slightly. So probably the difference comes from some differently named resources.
The RU version also has some additional apps which the EU version does not have, such as Esquire, Questions, Strelka and Vector. These are probably the main reason why they have different ROMs. They might only work in Russia.
Click to expand...
Click to collapse
FYI the difference is essentially the product package configuration (app bundles that are pre-loaded) but there are also some differences between the resources used for the stock apps. One in particular (my personal fav ) is the dialler - the RU variant includes cyrillic characters regardless of language/locale setting (feature). The EU will give you a regular english-only dialler if you're using english locale settings
Vuche said:
You can find it here: ftp://fw.ydevices.com/YotaPhone2/Firmwares/RU/
Install either via OTA update if you're already on the 1.87 RU ROM like I am. On my device it first wanted to install the update only, about 67MB, but it failed to install; then the next time I checked for updates after reboot through the settings update menu, it downloaded the full file, about 0,99 GB. Then the update went all the way through. SuperSU is lost on the way, I will try if it still works through the recovery installation.
You can also install through Yotaflasher like it's explained here: http://forum.xda-developers.com/showthread.php?t=3247356
Didn't have time to test things out, but it's still Lollipop 5.0, so only bugfixes and some new yotapanel features I guess.
Enjoy!
Click to expand...
Click to collapse
Ho to flash the update zip file? I m stuck on 4.4.3...
does nyone know how to flash the file zip into the phone?? i have no idea how it works and i dont find any infos
Does the new update solve the keyboard sensitivity issue??
zute333 said:
numerous guides and how to's in this forum and across XDA, as well as google.
download fastboot + adb > boot to download mode > flash twrp via fastboot commands > boot into twrp > flash zip.
There's obviously more to it than that, up to you to do the research.
Click to expand...
Click to collapse
i'm using this post as a minimalistic guide for myself (so i keep it up with my "discoveries" )
and ofc for been helped by everyone who wants to help me because i am completely new to android world cause this is my first android phone ever!
so.. let's get started!
i downloaded [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
version 1.4.3 doesnt works for me so i downloaded the 1.3 as suggested and worked.
then i enabled the download mode following the procedure:
Turn off the phone, then press and hold the volume down key + the power key at the same time. This should boot you into download mode.
Click to expand...
Click to collapse
note: phone MUST be disconnected form pc to be turned off.
now..
*does install twrp invalidate warranty?
EDIT: answer is YES cause of
TWRP 2.8.5.0 YotaPhone 2 recovery image said:
Warning: It is currently not known how to re-lock the bootloader. This means you cannot completely undo the next step as of yet. This might have consequences for sending the device in for repairs, if they check for this, and deem it a (warranty) problem
Click to expand...
Click to collapse
*is installing TWRP a mandatory step?
EDIT: the answer is NO. it seems that the mandatory part is to unlock the bootloader (the bad part for the warranty.. and that can erase ur data..) and this can be done following this guide How to Install TWRP Recovery on YotaPhone 2 untill point 6 included - which i am reporting here for easy of use.
How to Install TWRP Recovery on YotaPhone 2 said:
How to Flash TWRP Recovery on YotaPhone 2
1 - Setup ADB and Fastboot on your Windows PC.
2 - Enable USB debugging from developer options on your YotaPhone 2.
3 - Connect it to PC with a USB cable, if it asks for debugging authorization, permit it.
4 - Go to the folder where you downloaded the TWRP recovery image from the download link above on your PC and open a command window inside that folder by doing “Shift + Right click” on any empty white space inside the folder, then select “Open command window here”.
5 - (Skip this if your bootloader is already unlocked) Now to unlock the bootloader, type in the following command:
└ Beware that unlocking the bootloader may wipe your phone’s data. Make sure to backup first before proceeding.
adb reboot bootloader
Click to expand...
Click to collapse
└ This will reboot your phone to bootloader mode
fastboot oem unlock
Click to expand...
Click to collapse
└ This will unlock bootloader on your device.
6 - Now if your phone has rebooted and is no longer in the bootloader mode, then boot it back into bootloader mode with the “adb reboot bootloader” command.
Click to expand...
Click to collapse
i already downloaded yotaflasher and the last RU firmware 5.0.0-RU1.1.99.zip
NOTE: Russian firmware seems to contain English language. i dont know how to change it later to the favorite one.
NOTE: you need to move the firmware files to the same location as the Flasher tool. Default one is C:\Program Files (x86)\yotaphone_flasher
i tryed to use yotaflasher right now while phone is in download mode and it says:
error: cannot open 'firmware/emnc_appsboot.mbn'
error: cannot open 'firmware/boot.img'
error: cannot open 'firmware/system.img'
error: cannot open 'firmware/recovery.img'
error: cannot open 'firmware/cache.img'
error: cannot open 'firmware/radio/NON-HLOS.bin'
error: cannot open 'firmware/radio/sbli.mbn'
error: cannot open 'firmware/radio/rpm.mbn'
error: cannot open 'firmware/radio/tz.mbn'
error: cannot open 'firmware/enmc_appsboots.mbn'
Would you like to flash userdata[Y/N]:
Click to expand...
Click to collapse
EDIT: placing the firmware in the right folder and unzipping ip let me flash my phone without using any bootloader. now i dont know why but is stucked showing android logo.
i dont know if this happened cause i used the last RU firmware on my stock 4.4.3 android or what..
what do i have to do?:crying::crying::crying:
tnx
Hello guys, I downloaded Lollipop from the ftp but installation fails: no MD5 file found!
I downloaded all russian versions and also the 1.6 EU version... but no way I always get this error.
I'm using TWRP 2.8.5, I guess the last one, and in the tutorials I see this version...
Does anyone know how to solve? :crying:
giocorrado said:
does nyone know how to flash the file zip into the phone?? i have no idea how it works and i dont find any infos
Click to expand...
Click to collapse
The info is described in various posts across the yotaphone forum. Are you rooted? If not then there also many many guides across the internet for that.
Not walking you through the whole process, sorry. We all had to learn, once you do it's all much easier.
It happens also to me...don't panic! press Volume up and the power button and when you enter in the bootloader select the downloading options, it will restart the phone with the "downloading" status
in the meanwhile with the yotaflasher select the option to downloads a firmware and try a different one. When the download is finished try to flash once again.
Melting Blaze said:
i already downloaded yotaflasher and the last RU firmware 5.0.0-RU1.1.99.zip
NOTE: Russian firmware seems to contain English language. i dont know how to change it later to the favorite one.
NOTE: you need to move the firmware files to the same location as the Flasher tool. Default one is C:\Program Files (x86)\yotaphone_flasher
i tryed to use yotaflasher right now while phone is in download mode and it says:
EDIT: placing the firmware in the right folder and unzipping ip let me flash my phone without using any bootloader. now i dont know why but is stucked showing android logo.
i dont know if this happened cause i used the last RU firmware on my stock 4.4.3 android or what..
what do i have to do?:crying::crying::crying:
tnx
Click to expand...
Click to collapse
I placed like you the rom downloaded through website in the firmware folder and flash got wrong. I was blocked on "powered by android" logo like you.
After this almost-bricking experience, I flashed 4.4.3 downloaded all through Flasher and phone was working again.
Then I tried to substitute 5.0 system.img in the folder downloaded through Flasher but no way... after flashing phone didn't boot.
I reflashed 4.4.3 back again and now is working.
I think that we can't put files in folder for Yota Flasher...
I cannot download last 5.0 EU version, like described here: http://forum.xda-developers.com/yot...ially-dead-t3312382/post65839167#post65839167
TKPL said:
I placed like you the rom downloaded through website in the firmware folder and flash got wrong. I was blocked on "powered by android" logo like you.
After this almost-bricking experience, I flashed 4.4.3 downloaded all through Flasher and phone was working again.
Then I tried to substitute 5.0 system.img in the folder downloaded through Flasher but no way... after flashing phone didn't boot.
I reflashed 4.4.3 back again and now is working.
I think that we can't put files in folder for Yota Flasher...
I cannot download last 5.0 EU version, like described here: http://forum.xda-developers.com/yot...ially-dead-t3312382/post65839167#post65839167
Click to expand...
Click to collapse
yeah i've done the same.
i founded the trick i hope
after my big mistake i have done this:
*i downloaded the last 4.4.3-S01-003-EU1.0.3.61a.zip then i flashed it. reminding to unzip it and put it in the right folder of the flasher. remind that this will delete ur data too prob.
*i checked for update on the phone in setting--> about phone --> sistem update
*it downloaded lollipop (android 5.0 Lollipop - 1Gb to download) :laugh:
*i took the 5.0.0-RU1.1.99.zip and flashed it
*u can choose english when the phone boot so dont worry about firmware to be RU
*i checked the firmware version doing the combo "Volume up and the power button" (press it while restarting)
*i changed the language of the phone in setting --> language (there is plenty of languages to choose. i choose mine, italian, but sometimes it happens to find something in english )
i downladed some app etc etc but i never used it for calls cause of the requested nano sim that i'm going to take tomorrow probably cause today i get stucked with trouble about my contacts.
hope to solve the problem for pass my contacts form my nokia N8 to yotaphone 2 quickly!
please let me know if it works for u too
JAMMANDROID said:
It happens also to me...don't panic! press Volume up and the power button and when you enter in the bootloader select the downloading options, it will restart the phone with the "downloading" status in the meanwhile with the yotaflasher select the option to downloads a firmware and try a different one. When the download is finished try to flash once again.
Click to expand...
Click to collapse
yeah. is exactly what i did, but super panicing like a chicken without head
Melting Blaze said:
yeah i've done the same.
i founded the trick i hope
after my big mistake i have done this:
*i downloaded the last 4.4.3-S01-003-EU1.0.3.61a.zip then i flashed it. reminding to unzip it and put it in the right folder of the flasher. remind that this will delete ur data too prob.
*i checked for update on the phone in setting--> about phone --> sistem update
*it downloaded lollipop (android 5.0 Lollipop - 1Gb to download) :laugh:
*i took the 5.0.0-RU1.1.99.zip and flashed it
*u can choose english when the phone boot so dont worry about firmware to be RU
*i checked the firmware version doing the combo "Volume up and the power button" (press it while restarting)
*i changed the language of the phone in setting --> language (there is plenty of languages to choose. i choose mine, italian, but sometimes it happens to find something in english )
i downladed some app etc etc but i never used it for calls cause of the requested nano sim that i'm going to take tomorrow probably cause today i get stucked with trouble about my contacts.
hope to solve the problem for pass my contacts form my nokia N8 to yotaphone 2 quickly!
please let me know if it works for u too
yeah. is exactly what i did, but super panicing like a chicken without head
Click to expand...
Click to collapse
I saw also an update this morning at home on wifi (I wait for the SIM too) because yesterday I flashed the 4.4.3-S01-003-EU1.0.51a: is not the 61 like yours and I received an update alert to 4.4.3-S01-003-EU1.0.3.56. I'm at work, I'll try this evening.
I haven't updated this morning because I was downloading a previous 5.0, the EU 1.44, but when flashing I had error "cannot load firmware/system.img". So I reflashed 4.4.3... I'll try again this evening
giocorrado said:
does nyone know how to flash the file zip into the phone?? i have no idea how it works and i dont find any infos
Click to expand...
Click to collapse
Hi, download YotaFlasher, it permits you to download and flash firmwares in an easy way, and you don't need to know any shell command
---------- Post added at 09:37 AM ---------- Previous post was at 09:25 AM ----------
giocorrado said:
does nyone know how to flash the file zip into the phone?? i have no idea how it works and i dont find any infos
Click to expand...
Click to collapse
TKPL said:
I saw also an update this morning at home on wifi (I wait for the SIM too) because yesterday I flashed the 4.4.3-S01-003-EU1.0.51a: is not the 61 like yours and I received an update alert to 4.4.3-S01-003-EU1.0.3.56. I'm at work, I'll try this evening.
I haven't updated this morning because I was downloading a previous 5.0, the EU 1.44, but when flashing I had error "cannot load firmware/system.img". So I reflashed 4.4.3... I'll try again this evening
Click to expand...
Click to collapse
Hello! I have 5.0!
After flashing and old version of 4.4.3 (my phone went with a 4.4.something branded Vodafone Italy, and they evidently don't give a fork about updates). With the 4.4.3 rev 1.0.51a I immediately received he update to 1.0.56a: I downloaded the 114MB, rebooted, and then got the update to 1.0.61a, around 63MB. I rebooted and then got finally the update to 5.0, 1GB :laugh:
I have only one problem now: the device doesn't recognize when I'm looking at the ink screen, and power button powers on the amoled... Even unlocking through swiping from bottom to top doesn't work. Option is correctly set, I tried to uncheck, reboot, wipe cache and check the option again but it not working well yet.
I have only one problem now: the device doesn't recognize when I'm looking at the ink screen, and power button powers on the amoled... Even unlocking through swiping from bottom to top doesn't work. Option is correctly set, I tried to uncheck, reboot, wipe cache and check the option again but it not working well yet.
Click to expand...
Click to collapse
seems that is the same for a lot of people if not everyone..
cause of this problem i am using this app gravity screen on/off.
it halves the problem cause now i have no problem for the amoled. and for problem i mean use the pwer button instead of simply swipe.
for the e-ink panel i still have to use the power button, only way it works.
Hi everybody,
[First of all I'm french, so sorry for my bad english...]
For the past 3 hours I've tried to downgrade my tablet from Android 5 to Android 4.
I've followed the instructions, but I'm "stuck" while I'm flashing with Flash Tool lite (v. 5.4.2.0), my tablet reboot on the desktop during the process.
What I've done so far ?
I've installed :
- PhoneFlashTool_4.4.4.1_external_win32.exe
- iSocUSB-Driver-Setup-1.2.0.exe
- IntelAndroidDrvSetup1.5.0.exe
Then, I understood that before to go back to KitKat, I needed to change the bios (return to kitkat bios). I used : restore-kitkat-bios-830-1050-v2
The procedure gone well (I think).
After that, I ran PhoneFlashTool_4.4.4.1, and I've ticked "force sparcing" to change size to 500mb, but when I've connected my tablet in USB Port (while it's on the droidboot screen), it didn't recognize my device...
So I've installed PlatformFlashToolLite_5.4.2.0_win32, instead.
With this version of the program my tablet is recognized, the flash started, but during the procedure my tablet reboot to the desktop, and after few minutes the connection is lost, and I've got an error message "flash failed".
I've tried to flash with debug usb tick, and not tick, same issue.
Few more info :
My tablet isn't rooted.
My computer is on Windows 7 64 bits Home Premium.
I don't really know what to do.
Is there something I did wrong ?
You need the kitkat rom to flash after you flash the bios
In the rom zip will be a flash.xml you select in phoneflashtool to flash the tab
Sent from my SM-G930F using Tapatalk
Thanks for your response pug1 !
I forgot to mention in my thread that yes, I click "browse" and select flash.xml from the "target_bin" folder.
Here's what I got in Flash tool Lite's box :
03/28/16 11:26:19.699 INFO : Flash file C:\Users\Daemon_Feunoyr\Downloads\Android\Yoga Tab 2\kitkat-YT2-1050F_S0198_150422_ROW\target_bin\flash.xml [Default] loaded
03/28/16 11:26:29.502 INFO : [Port 0/1/4] Start flashing the flash configuration with dnx_os start state for Baytrail1xxxxxxx
03/28/16 11:26:29.502 INFO : [Port 0/1/4] Reboot device Baytrail1xxxxxxx with Fastboot...
03/28/16 11:26:29.611 INFO : [Port 0/1/4] Starting flash ...
03/28/16 11:29:30.640 INFO : [Port 0/1/4] Device lost on 0/1/4
Click to expand...
Click to collapse
Go to http://forum.xda-developers.com/thi...-lenovo-yoga-tab-2-1050f-softbricked-t3319124 post 7 and there is all the files you need
Thanks, but I already have these archives :
- restore-kitkat-bios-830-1050-v2 (restore-kitkat-bios-830-1050-v2.exe)
- yogatablet2-flash-tools-20150812 (IntelAndroidDrvSetup1.9.0, iSocUSB-Driver-Setup-1.2.0, PhoneFlashTool_4.4.4.1_external_win32)
- kitkat-YT2-1050F_S0198_150422_ROW (target_bin (file), tools file (with the programs to flash...)
Isn't it enough ?
Do you think I need one of the file you posted on the other thread ? (I ask, because I have a very bad internet connection...)
I think I found what I did wrong.
I pressed volume up & power to go to the droidboot screen, instead of volume up and down + power (fastboot).
I succeed to flash KK with the tab in fastboot :victory:
Thanks for your time !
Now I need to look into how to root the tab.
To unlock the bootloader go here http://forum.xda-developers.com/thi...yoga-2-how-to-unlock-bootloader-t3320327,post 4
Does it means that I need to unlock the boatloader to root the tab ?
Yes, unlock the bootloader then use this. http://tinyurl.com/zoapeyh for permanent TWRP
Do not forget to update to lollipop BEFORE doing the boot unlock and TWRP
OK, thanks. I hope it's "easier" than downgrade :s
Can you do me a favor ? ^^"
I read your post on the other thread, and I'm confused... I don't really know what I should type in cmd.
Can you highlight (quotation marks, or put them in bold) the commands that I need to type, please ?
Open a CMD window on your computer and type cd c:\ to get to just a c prompt.
Then type fastboot flash ESP This bit then should read the full location of the unzipped file that is patched.
An example like mine is fastboot flash ESP c:/adb/1050f-esp-patched.img , this is how I did mine and I have an unlocked bootloader and permanent TWRP
Click to expand...
Click to collapse
Daemon_Feunoyr said:
OK, thanks. I hope it's "easier" than downgrade :s
Can you do me a favor ? ^^"
I read your post on the other thread, and I'm confused... I don't really know what I should type in cmd.
Can you highlight (quotation marks, or put them in bold) the commands that I need to type, please ?
Click to expand...
Click to collapse
Do the upgrade to lollipop first then come back here for the rest of the instructions.
After you do the upgrade and unlock the bootloader ,have a read here. http://forum.xda-developers.com/android/development/recovery-t3322990, it might be easier,the post is by surdu_petru.
I don't want to go back to Lollipop, there are too much bugs :/ (wifi, the screen flicker on internet browsers, sometimes the tablet reboot for no reason, etc.).
I had enough of Lollipop...
Anyway, I want to stay on KK.
Daemon_Feunoyr said:
I don't want to go back to Lollipop, there are too much bugs :/ (wifi, the screen flicker on internet browsers, sometimes the tablet reboot for no reason, etc.).
I had enough of Lollipop...
Anyway, I want to stay on KK.
Click to expand...
Click to collapse
O.K, like you I had many problems with lollipop but after doing all this plus one or two other mods,my 1050 is very fast and stable,BUT it might not be the same for others.
Maybe one day, when I'll be motivate lol I'm "exhausted" by my 4 hours of struggle with the downgrade XD
(I suppose there are lots of manip to do for lollipop to be stable =_=), and/or when Lenovo will release a stable version of Lollipop.
How do I root from KK ?
In tried with Kingo Root, but it stucks à 10 % for maybe ~ 10 minutes.
EDIT : Can I use this method ? (though I'm not sure I understand everything... x_x)
Daemon_Feunoyr said:
Maybe one day, when I'll be motivate lol I'm "exhausted" by my 4 hours of struggle with the downgrade XD
(I suppose there are lots of manip to do for lollipop to be stable =_=), and/or when Lenovo will release a stable version of Lollipop.
How do I root from KK ?
In tried with Kingo Root, but it stucks à 10 % for maybe ~ 10 minutes.
EDIT : Can I use this method ? (though I'm not sure I understand everything... x_x)
Click to expand...
Click to collapse
I am not sure but I don't think you can on Kitkat
No root at all on KK ?
Edit : My tab flickers in games -_-"
I might reconsider my decision to not upgrade to Lollipop... o/
Where can I find the rom without the two last updates ? (december and march... problems appeared with these 2 patchs...)
Edit 2 : Is that one of the 2 files you uploaded ?
If so, which one do I have to DL ?
YT2-1050F_USR_S000198_1504220313_WW21_ROW (1).zip
YT2-1050F_USR_S100031_1506111400_WW52_ROW-(L).zip
S100031. You will then have 3 update to get to S100256. I have zero problems on latest update
Sent from my SM-G930F using Tapatalk
Just remember if you upgrade and then root,you will not be able to take any more updates.
But saying all that, it's easy to get back to KitKat and start all over again.
OK, thanx both of you. :good:
I'll download YT2-1050F_USR_S100031_1506111400_WW52_ROW-(L).zip.
It's the same procedure with PhoneFlashTool/FlashToolLite ? :
- Vol up & down + Power (Fastboot mode)
- connect the tablet to the computer
- In PhoneFlashTool click browse and select flash.xml from the "target_bin" folder
- start to flash ?
For the Lollipop updates (not sure I want to (re)install them), if I wait a little bit before root my device, I guess it will show via OTA, no ?
Daemon_Feunoyr said:
OK, thanx both of you. :good:
I'll download YT2-1050F_USR_S100031_1506111400_WW52_ROW-(L).zip.
It's the same procedure with PhoneFlashTool/FlashToolLite ? :
- Vol up & down + Power (Fastboot mode)
- connect the tablet to the computer
- In PhoneFlashTool click browse and select flash.xml from the "target_bin" folder
- start to flash ?
For the Lollipop updates (not sure I want to (re)install them), if I wait a little bit before root my device, I guess it will show via OTA, no ?
Click to expand...
Click to collapse
Just do an ota of the first update to lollipop and then refuse the rest.
1 - Download This File and extract
https://drive.google.com/file/d/0ByH4eje3nMs-dl91VGk2SjRvdDg/view?usp=sharing
2 - Inside folder and double-click the bat file and a command window will be shown up.
------------------------------------------------------------------------------------------------------------
Flash orginal Firmware = Relock_and_format.bat
Relock Bootloader = Relock_and_format.bat
Unbrick = Relock_and_format.bat
Unroot = Relock_and_format.bat
Logo fix = OnlyLogo.bat
Repair Modem = OnlyModem.bat
Firmware version : Android 6.0 - XT1575_CLARK_RETUS_6.0_MPHS24.49-18-3 (Latest version) (24.201.3.clark_retus_en_US)
How is this different from the other recovery scripts/threads?
What specific version of firmware is included?
gpz1100 said:
How is this different from the other recovery scripts/threads?
What specific version of firmware is included?
Click to expand...
Click to collapse
this best. because, i test all other method but my phone did not relock.
When I tried this method, phone is relocked and everything work without error.
Thank you, thank you, thank you!
You are a life saver! This is the only method that worked for me after struggling for a couple of days trying to overcome errors wen I tried to flash stock and re-lock the bootloader. :good::good::good: Will this allow the OTA update and receive Motorola updates?
relock bl returns te warranty?
no. there is no reason to ever relock this phone.
So,if you want to receive Motorola OTA Updates, you only need to unroot and return to stock recovery?
Rotondo said:
relock bl returns te warranty?
Click to expand...
Click to collapse
No
You have to use motorola's website to get the unlock code. They know you unlocked, warranty still void.
I can't thank you enough for this thread!!! I've run through several of these and yours has been the only one to include the most recent security patch!!! You are a STAR!
Thank you for making this easy!
Awesome!
This worked beautifully, I can't thank you enough.
Update** Since using this to un soft brick my device, My bootloader seems to be in a weird place, It says "Device unlocked Status code 3". I followed directions from Motorollas site to relock boot loader nothing in ADB or Fastboot flashes. I tried re unlocking it fails. im not sure what happened. any suggestions would be great though! thanks.
THANK U!!!!
so I tried like 3 other methods to restore my xt1575 after I soft bricked it like an idiot... This was the easiest, quickest method by a long shot.... I wish I could shake ur hand sir! Thank u soooo much....
Edit : Now...it seems...my Bluetooth wont turn on....I've tried resetting network settings, clearing data under BT sharing in App Manager settings, and doing a full factory reset. Ive rebooted numerous times as well. I cannot, for the life of me , get BT to turn on! I'm about to flash TWRP, wipe, and install AICP... IDK..... has this ever happened to anyone? anyone got any idea's?
svensudels said:
so I tried like 3 other methods to restore my xt1575 after I soft bricked it like an idiot... This was the easiest, quickest method by a long shot.... I wish I could shake ur hand sir! Thank u soooo much....
Edit : Now...it seems...my Bluetooth wont turn on....I've tried resetting network settings, clearing data under BT sharing in App Manager settings, and doing a full factory reset. Ive rebooted numerous times as well. I cannot, for the life of me , get BT to turn on! I'm about to flash TWRP, wipe, and install AICP... IDK..... has this ever happened to anyone? anyone got any idea's?
Click to expand...
Click to collapse
The firmware and procedure in the OP are outdated, doing any flashing via a batch file is highly frowned upon as you cannot see if any piece fails and judging from the date of the OP the firmware is out of date.
Aside from that, if just the BT isn't working, you likely need to reflash the BT firmware... it should be included in the firmware you downloaded, go to that directory and execute "fastboot flash bluetooth BTFM.bin" to reflash the BT firmware partition. I am not sure what fastboot is included in this firmware archive, so it that fails try it as "mfastboot fastboot bluetooth BTFM.bin".
If BTFM.bin does not exist in this firmware archive, try over from scratch, look in my signature for a more up to date method of restoring stock and (optionally) relocking the bootloader.
acejavelin said:
The firmware and procedure in the OP are outdated, doing any flashing via a batch file is highly frowned upon as you cannot see if any piece fails and judging from the date of the OP the firmware is out of date.
Aside from that, if just the BT isn't working, you likely need to reflash the BT firmware... it should be included in the firmware you downloaded, go to that directory and execute "fastboot flash bluetooth BTFM.bin" to reflash the BT firmware partition. I am not sure what fastboot is included in this firmware archive, so it that fails try it as "mfastboot fastboot bluetooth BTFM.bin".
If BTFM.bin does not exist in this firmware archive, try over from scratch, look in my signature for a more up to date method of restoring stock and (optionally) relocking the bootloader.
Click to expand...
Click to collapse
THANK U! this worked 1st try! u sir, are a gentleman & a scholar!
svensudels said:
THANK U! this worked 1st try! u sir, are a gentleman & a scholar!
Click to expand...
Click to collapse
Glad you got it resolved.
Hello there! The link seems to be corrupted not available anymore . Where can I find the link?
Thank you for your excellent work
osk4rin said:
Hello there! The link seems to be corrupted not available anymore . Where can I find the link?
Thank you for your excellent work
Click to expand...
Click to collapse
This guide and it's files are outdated, and seems to be abandoned... look at one of the more current tutorials like the one in my signature maybe.
Need Help!,
Updated my xt1643 indian g4 plus to the June Security Patch (NPJS25.93.14-8) build.
Post that I unlocked the bootloader and installed AOSPX rom after which I wanted to go stock nougat.
I flashed the marshmallow rom and took the ota to nougat and now my screen is all black, not even being able to boot the device to fastboot.
By exploring the forums I got to know that I've hard bricked my device but this thing never happened before the june update.
I'm not even able to use the blank files method to revive my device:crying::crying:
Please help
Only choice
https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
drmuruga said:
Only choice
https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
Click to expand...
Click to collapse
thank you, but it did not work. Also I read around the forum that I would be needing the latest blank flash files which would be capable enough to be flashed on the June Security Rom(NPJS.25.93.14-8)
gautamchawla195 said:
thank you, but it did not work. Also I read around the forum that I would be needing the latest blank flash files which would be capable enough to be flashed on the June Security Rom(NPJS.25.93.14-8)
Click to expand...
Click to collapse
You must Press Power Button and Volume down for 2-3 Minutes and Hold them. ( Handy must be connected to the charger !!! )
This means more then 120 Seconds.Then your handy will boot to Recovery.
then navigate to "start" in recovery with volume buttons and hit "power button" that it starts normally.
Try this please it helped me....and say us if it worked for you !
this solutions helps if android gets freezed .I first tough also my handy was death.But it worked for me.
But remember it must be connected to charger and press more then 120 seconds and hold !!!This will work on all Motorola Handys with Android.
majo3000 said:
You must Press Power Button and Volume down for 2-3 Minutes and Hold them. ( Handy must be connected to the charger !!! )
This means more then 120 Seconds.Then your handy will boot to Recovery.
then navigate to "start" in recovery with volume buttons and hit "power button" that it starts normally.
Try this please it helped me....and say us if it worked for you !
this solutions helps if android gets freezed .I first tough also my handy was death.But it worked for me.
But remember it must be connected to charger and press more then 120 seconds and hold !!!This will work on all Motorola Handys with Android.
Click to expand...
Click to collapse
This is something new apart of which I've been researching around forums.
Btw, would work as per the given fix and keep you posted
gautamchawla195 said:
This is something new apart of which I've been researching around forums.
Btw, would work as per the given fix and keep you posted
Click to expand...
Click to collapse
Nupp, not working, I too think that I should wait for the full june security rom and post that the blank flash files to get my device alive again. I would please request someone to gain access to the blank flash files after the june rom is released.
June security update won't let you downgrade and has bricked many devices. You have to wait until full rom of 6/17 is released as you've said. If under warranty, you can send it in. If insured, you can try to kill your phone by dropping in water and collect insurance.
HueyT said:
June security update won't let you downgrade and has bricked many devices. You have to wait until full rom of 6/17 is released as you've said. If under warranty, you can send it in. If insured, you can try to kill your phone by dropping in water and collect insurance.
Click to expand...
Click to collapse
Yes, we would be needing the updated blank flash files for the june update, can you please tell me about how long the june blank flash files are released after the full fastboot rom is released as per the past experiences and would that increase chances for my device to get revived?
June full ROM lauched:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
How can I extract the blankflash from this ROM? It's possible? Please, help me! I didn't found in Google a way to get these files to save my moto g4+ hard briked
pekenolucas said:
June full ROM lauched:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
How can I extract the blankflash from this ROM? It's possible? Please, help me! I didn't found in Google a way to get these files to save my moto g4+ hard briked
Click to expand...
Click to collapse
Well, we're gonna need a copy first to see what's inside - that link keeps giving me access denied. Presumably it's only for service centres or for developers. Strange, it's working now...
This link is OK! I downloaded it right now using Chrome from my phone. I'm from Brazil.
pekenolucas said:
This link is OK! I downloaded it right now using Chrome from my phone. I'm from Brazil.
Click to expand...
Click to collapse
Ah, you're right - dunno why the link gave me access denied initially - it's downloading okay too now.
EDIT - just downloaded the ROM and had a look - no sign of a new blank flash that could help us unfortunately.
Looks like the only resolution, unfortunately, for a bricked device involving the NPJS25.93-14-8 update, (whether it was downgraded with a stock ROM, or you somehow downgraded from the June update, and then updated with the June OTA) is to send it for service or save up for a new device.
echo92 said:
Ah, you're right - dunno why the link gave me access denied initially - it's downloading okay too now.
Click to expand...
Click to collapse
echo92, can you plzz check and also ask vache and some of the other developers too, to go through the june rom and see if there's any file which we can use to revive our devices.
Edit: sorry, didn't saw ur reply
Gpt.bin from ROM have same archives from blankflash, but gpt.bin have 32kb and blankflash more than 3Mb! Anyone know how to put gpt.bin data inside blankflash to update the partition table and possible unbrick the device? It's just an idea!
pekenolucas said:
Gpt.bin from ROM have same archives from blankflash, but gpt.bin have 32kb and blankflash more than 3Mb! Anyone know how to put gpt.bin data inside blankflash to update the partition table and possible unbrick the device? It's just an idea!
Click to expand...
Click to collapse
is there anyway to edit contains of singleimage.bin ?
The blankflash stays the same.. only the gpt.bin and bootloader.img are to be changed accordingly
echo92 said:
Well, we're gonna need a copy first to see what's inside - that link keeps giving me access denied. Presumably it's only for service centres or for developers. Strange, it's working now...
Click to expand...
Click to collapse
Can you upload a copy if you've downloaded it? The link doesn't work now. Seems to have been removed.
gpt.bin of the latest firmware and singleimage.bin file from the Blankflash seems to be having the same contents.
I tried renaming gpt as singleimage and tried using blankflash
It didn't work. Also the size of both the files are not even comparable one is 32kb and another is 4mb
tywinlannister7 said:
The blankflash stays the same.. only the gpt.bin and bootloader.img are to be changed accordingly
Click to expand...
Click to collapse
Yes, but I think that Bootloader.img and GPT.bin are inside singleimage.bin data, because it rewrite these information on bricked phones. I don't know singleimage.bin have signed data. If it had signed data, no chance to patch/modify it!
I'll try some hex editor and run some tests!!!
zeomal said:
Can you upload a copy if you've downloaded it? The link doesn't work now. Seems to have been removed.
Click to expand...
Click to collapse
tywinlannister7's kindly uploaded the ROM for us [EDIT - link removed as the ROM appears to cause loss of SIM for some devices]