my phoe is broken i need to flash twrp and i cant to do it ,i setup cyanogenmod recovery by mistake and this recovery is fault because i cant even transfer any files form computer to mobile .. i try to flash with sp tool but it give me error because my phone is broken ,i try also dirtycow v11 on my phone to try flash twrp but it cant read phone on the computer and i setup V21 rom ??
sorry for bad english
any HElp plaese?
meroher said:
any HElp plaese?
Click to expand...
Click to collapse
How you mean broken?
Can it boot to fastboot mode?
YEP IT CAN BOOT TO FASTBOOT ?! then what?
mrmazak said:
how you mean broken?
Can it boot to fastboot mode?
Click to expand...
Click to collapse
plaese man help me my mob is still broken ineed it now
meroher said:
plaese man help me my mob is still broken ineed it now
Click to expand...
Click to collapse
I don't get notified that you answer if you do not quote.
you only answered one of the questions. You did not tell what is "broke"
no help you if you do not know what you need help with.
mrmazak said:
I don't get notified that you answer if you do not quote.
you only answered one of the questions. You did not tell what is "broke"
no help you if you do not know what you need help with.
Click to expand...
Click to collapse
oki iget it
first i had a twrp recovery and i try to install other recovery so
i install this recovery
https://forum.xda-developers.com/r1-hd/development/beta-cyanogenmod-recovery-blu-r1-hd-t3462614
and this recovery cant let me to install any rom or to back to install twrp recovery
and blu cant boot up he freeze on blu white screen
any thing else i will tell you
thanks for you help
meroher said:
oki iget it
first i had a twrp recovery and i try to install other recovery so
i install this recovery
https://forum.xda-developers.com/r1-hd/development/beta-cyanogenmod-recovery-blu-r1-hd-t3462614
and this recovery cant let me to install any rom or to back to install twrp recovery
and blu cant boot up he freeze on blu white screen
any thing else i will tell you
thanks for you help
Click to expand...
Click to collapse
Ok you installed this cm recovery with twrp?
android is not booting. (v21)
the cm recovery does boot but not allow install anything.
And fastboot is loading.
probably need to fastboot flash boot.img , I will share a superSU patched version. (you do not need to root system if not wanted, but patched boot is needed to boot a moddified system)
and fastboot flash twrp.
download this zip.
extract files to your desktop
use these fastboot commands to test first
This one to boot the phone
Code:
fastboot boot %userprofile%\Desktop\su-boot.img
This one to boot twrp
Code:
fastboot boot %userprofile%\Desktop\twrp_p6601_7.1_recovery.img
mrmazak said:
Ok you installed this cm recovery with twrp?
android is not booting. (v21)
the cm recovery does boot but not allow install anything.
And fastboot is loading.
probably need to fastboot flash boot.img , I will share a superSU patched version. (you do not need to root system if not wanted, but patched boot is needed to boot a moddified system)
and fastboot flash twrp.
download this zip.
extract files to your desktop
use these fastboot commands to test first
This one to boot the phone
Code:
fastboot boot %userprofile%\Desktop\su-boot.img
This one to boot twrp
Code:
fastboot boot %userprofile%\Desktop\twrp_p6601_7.1_recovery.img
Click to expand...
Click to collapse
Quote:
FIRST WHEN SEE YOU POST I TRY THIS CODES BEFORE TRYING WITH YOUR CODES
Lets see how quick and easy this really is...
In the command line type:
Code:
fastboot devices
Seeing your serial number means we know all is good
Now lets type these commands:
Code:
fastboot erase system -w
fastboot erase boot
fastboot update superawesomerom.zip
Of course replace <superawesomerom.zip> with the correct file name
and last but not least:
Code:
fastboot reboot
THANKS IT WORKS BUT WHEN I GO TO RECOVERY IT GO TO BOOT directly again AND again
WHATS BROBLEAM !
meroher said:
Quote:
FIRST WHEN SEE YOU POST I TRY THIS CODES BEFORE TRYING WITH YOUR CODES
Lets see how quick and easy this really is...
In the command line type:
Code:
fastboot devices
Seeing your serial number means we know all is good
Now lets type these commands:
Code:
fastboot erase system -w
fastboot erase boot
fastboot update superawesomerom.zip
Of course replace <superawesomerom.zip> with the correct file name
and last but not least:
Code:
fastboot reboot
THANKS IT WORKS BUT WHEN I GO TO RECOVERY IT GO TO BOOT directly again AND again
WHATS BROBLEAM !
Click to expand...
Click to collapse
WOW
WTF
Idon't know who told you to use those commands, but I am not familiar with using
Code:
fastboot erase system -w
fastboot erase boot
fastboot update superawesomerom.zip
so i dont know what to tell you.
why do you say "it worked" but then say it "just boots again AND again"
to me that is not worked, that is mean it made bootloop. so not worked.
mrmazak said:
WOW
WTF
Idon't know who told you to use those commands, but I am not familiar with using
Code:
fastboot erase system -w
fastboot erase boot
fastboot update superawesomerom.zip
so i dont know what to tell you.
why do you say "it worked" but then say it "just boots again AND again"
to me that is not worked, that is mean it made bootloop. so not worked.
Click to expand...
Click to collapse
ok sorry
the mobile now in a bootloop as you say any solution to this issue and iam sorry again >>+
i get codes from here
https://forum.xda-developers.com/showpost.php?p=41374686&postcount=4
this post please stay with me to back up this phone
meroher said:
ok sorry
the mobile now in a bootloop as you say any solution to this issue and iam sorry again >>+
i get codes from here
https://forum.xda-developers.com/showpost.php?p=41374686&postcount=4
this post please stay with me to back up this phone
Click to expand...
Click to collapse
I am not aware of any zip file available to flash the way that guide had you try.
As it stands you wiped boot and system.
I am away from PC so typing is not as easy. I will be more detailed when I return.
Basically I suggest you to "flash" the boot.img I sent.
Then "boot" the recovery.
If the recovery then boots. Install a rom from my modifes stock roms thread.
oki i try install recovery but it same thing it go to white screen and restart again and again
i will wait for you to help me more thanks ><
mrmazak said:
I am not aware of any zip file available to flash the way that guide had you try.
As it stands you wiped boot and system.
I am away from PC so typing is not as easy. I will be more detailed when I return.
Basically I suggest you to "flash" the boot.img I sent.
Then "boot" the recovery.
If the recovery then boots. Install a rom from my modifes stock roms thread.
Click to expand...
Click to collapse
oki i will wait you thanks for your time
meroher said:
oki i will wait you thanks for your time
Click to expand...
Click to collapse
So this is what i suggest
use the files i gave before, unzipped to desktop.
This one to Flash boot.img
Code:
fastboot flash boot %userprofile%\Desktop\su-boot.img
This one to boot twrp.img
Code:
fastboot boot %userprofile%\Desktop\twrp_p6601_7.1_recovery.img
I expect that to give you a working twrp environment. Then go to linked thread and install really any version you want. But as you said you were on V21, so pick that one I supose.
https://forum.xda-developers.com/r1-hd/development/modified-8-3-stock-rom-t3602672
mrmazak said:
So this is what i suggest
use the files i gave before, unzipped to desktop.
This one to Flash boot.img
Code:
fastboot flash boot %userprofile%\Desktop\su-boot.img
This one to boot twrp.img
Code:
fastboot boot %userprofile%\Desktop\twrp_p6601_7.1_recovery.img
I expect that to give you a working twrp environment. Then go to linked thread and install really any version you want. But as you said you were on V21, so pick that one I supose.
https://forum.xda-developers.com/r1-hd/development/modified-8-3-stock-rom-t3602672
Click to expand...
Click to collapse
it works fine finally thanks very much for help :]:]:laugh::laugh:
Related
Can anyone advise me off the fastboot command to save a copy of my recovery image before I flash the new one please.
Burtrum57 said:
Can anyone advise me off the fastboot command to save a copy of my recovery image before I flash the new one please.
Click to expand...
Click to collapse
You can't "pull" from fastboot. The protocol doesn't work like that sadly. What you can do though, is download a kernel from the forums here on xda and:
Flash recovery image to boot partition:
fastboot flash boot <recovery.img>
Battery pull (or reboot) and do a normal boot
It'll boot into recovery.
Backup recovery parition.
Reboot to fastboot
Flash kernel back:
fastboot flash boot <kernel boot.img>
Flash recovery to correct spot:
fastboot flash recovery <recovery.img>
Sent from my 0PCV1 using XDA Free mobile app
Many thanks for that. It worked and now I have CWM recovery. And the first thing I did with it was ???? Make a backup and save that on my computer for just in case!!
Something like this
Code:
dd if=/dev/block/mmcblk0p41 of=/mnt/media_rw/ext_sd/recovery.img
should do it.
Burtrum57 said:
Can anyone advise me off the fastboot command to save a copy of my recovery image before I flash the new one please.
Click to expand...
Click to collapse
Burtrum57 said:
Many thanks for that. It worked and now I have CWM recovery. And the first thing I did with it was ???? Make a backup and save that on my computer for just in case!!
Click to expand...
Click to collapse
do you have it on Desire 510 64 bit ?
how i can get it ?
Hello everybody,
I was trying to reinstall the factory image on my Nexus 6 with a script and everything went wrong. Now when I reboot in recovery I have a menu (restart bootloader, recovery.....) but I can't see with my phone on my computer (ubuntu). I tried every mode on the phone menu : bootloader, recovery, factory mode, bar codes, bptools....but the phone doesn't mount on the computer.
So I'm not able to do anything on it. Any clues ?
Thanks.
Martin
Well, I made some progress. I found this and the command ''adb sideload''. But now, I'm stuck with ''you need adb 1.0.32 or newer'' to install a recovery on my Nexus.
Can't find an easy way to install a ''newer'' adb tools on my Ubuntu...
Now, i managed to update the adb version to 1.0.32. But I got the message when I ''adb sideload'' twrp-2.8.7.1-shamu.img:
E:footer is wrong
E:Signature verification failed
Installation aborted
Didn't have time to work on this for a while but still no anwser from anyone. Does someone know another forum where I could try to find any clues?
mchenier said:
Didn't have time to work on this for a while but still no anwser from anyone. Does someone know another forum where I could try to find any clues?
Click to expand...
Click to collapse
your answer..
thats not your recovery that youre booting into, thats your bootloader. and the only thing that works in the bootloader is fastboot. adb does not work in the bootloader. and you need to use fastboot to flash a factory image, not adb.
Ok, thanks. I just figure that out couple of minutes ago. I'm almost there. I was able to install TWRP on my Nexus 6. The problem now is when i tried to install ''image-shamu-mmb29q.zip'' with TWRP, it failed even if I wipe the cache and Dalvik cache before. And I don't know why.
It's says ''Error flashing zip
Ok, I have done it. Find that web page to help me: http://9to5google.com/2015/10/05/ho...nexus-5-nexus-6-nexus-7-nexus-9-nexus-player/
I thought I had to install the zip file with TWRP. The right action was that:
First, flash the bootloader and the radio, and then reboot the bootloader (radio only applies to some devices):
fastboot flash bootloader <bootloader file name here>.img fastboot flash radio <radio file name here>.img
fastboot reboot-bootloader
Flash the recovery, boot, system, and vendor images (vendor only applies to some devices):
fastboot flash recovery recovery.img fastboot flash boot boot.img fastboot flash system system.img fastboot flash vendor vendor.img
Recommended: For a full wipe, flash cache and userdata as well (userdata only applies to some devices):
fastboot flash cache cache.img fastboot flash userdata userdata.img
Reboot your device:
fastboot reboot
Thanks. I'm done.
sweet:
but all that information is here, on XDA, in the stickies. didn't you look?
simms22 said:
sweet:
but all that information is here, on XDA, in the stickies. didn't you look?
Click to expand...
Click to collapse
Don't know what the stickies are.
mchenier said:
Don't know what the stickies are.
Click to expand...
Click to collapse
this is a helpful sticky from the general thread http://forum.xda-developers.com/nexus-6/general/nexus-6-sticky-roll-thread-t3061066
they are important threads stuck, or stickied, to the top of the general section
Ok, thanks. I'll keep it for future references.
mchenier said:
Ok, thanks. I'll keep it for future references.
Click to expand...
Click to collapse
also, if your stuck somewhere, pm me. i would be happy to help.
simms22 said:
also, if your stuck somewhere, pm me. i would be happy to help.
Click to expand...
Click to collapse
Eh! thanks a lot.
I just installed Cyanogenmod on a Nexus 4. I have a collection to work with. Someday I might be good at it
Hello,
I recently flashed the latest TWRP beta for the OxygenOS 4.0.1 on my phone which has an unlocked bootloader. I managed to boot into recovery immediately after flashing the .img through my PC, so that's how I was able to install my SuperSU.
However, since I booted into the OS, anytime I'm trying to enter the TRWP recovery again, I'm stuck in the stock recovery which doesn't let me install anything. So the only way for me to boot into TWRP recovery is using my PC. Can anybody help me to fix that?
Thanks!
What command are you using to install TWRP to your bootpartition?
I think the correct one is something like:
Code:
fastboot flash recovery (file name).img
kwoad said:
What command are you using to install TWRP to your bootpartition?
I think the correct one is something like:
Code:
fastboot flash recovery (file name).img
Click to expand...
Click to collapse
Thanks for your reply! Exactly. And after installing it, I used the command 'fastboot boot TWRP.img", and that brought me into TWRP recovery. But I could only get there this way and still had the stock recovery.
Yuniboy said:
Thanks for your reply! Exactly. And after installing it, I used the command 'fastboot boot TWRP.img", and that brought me into TWRP recovery. But I could only get there this way and still had the stock recovery.
Click to expand...
Click to collapse
did you unlock bootloader first
Yuniboy said:
Thanks for your reply! Exactly. And after installing it, I used the command 'fastboot boot TWRP.img", and that brought me into TWRP recovery. But I could only get there this way and still had the stock recovery.
Click to expand...
Click to collapse
From what I understand, the command 'fastboot boot twrp.img' will boot the specified recovery once, but won't flash it to the device. So it has nothing to do with the recovery that is actually on your device. Perhaps something went wrong when you actually flashed twrp and it wasn't written at all.
xabat said:
did you unlock bootloader first
Click to expand...
Click to collapse
Thanks for both your replies. Yes, I did. An indicator is also that every time I boot up my system it even warns me that the bootloader is unlocked.
freepenguin84 said:
From what I understand, the command 'fastboot boot twrp.img' will boot the specified recovery once, but won't flash it to the device. So it has nothing to do with the recovery that is actually on your device. Perhaps something went wrong when you actually flashed twrp and it wasn't written at all.
Click to expand...
Click to collapse
Well, I flashed the twrp by booting into fastboot mode and then typing 'fastboot flash recovery twrp.img'. I don't know what's wrong there, so maybe you could help me out?
Yuniboy said:
Well, I flashed the twrp by booting into fastboot mode and then typing 'fastboot flash recovery twrp.img'. I don't know what's wrong there, so maybe you could help me out?
Click to expand...
Click to collapse
Unfortunately then I don't know how to help Because that's exactly what I did and I got TWRP running without any problem. If you flash via 'fastboot flash recovery' command will it be on the device after you reboot for the first time?
i remember, once i couldn't boot into recovery either when i used fastboot command. Then I flash recovery using tool below and it worked for me.
https://forum.xda-developers.com/oneplus-3t/development/toolkit-oneplus-3t-toolkit-unlock-t3507729
freepenguin84 said:
Unfortunately then I don't know how to help Because that's exactly what I did and I got TWRP running without any problem. If you flash via 'fastboot flash recovery' command will it be on the device after you reboot for the first time?
Click to expand...
Click to collapse
Apparently, you were right. I just wiped my device (accidentaly ) and flashed TWRP again, basically did the same steps as before, but now it works. Seems like somehow the installation of TWRP just failed on the first try. Thanks for your help!
xabat said:
i remember, once i couldn't boot into recovery either when i used fastboot command. Then I flash recovery using tool below and it worked for me.
https://forum.xda-developers.com/oneplus-3t/development/toolkit-oneplus-3t-toolkit-unlock-t3507729
Click to expand...
Click to collapse
Fortunately, it wasn't that bad. So the installation of TWRP failed somehow and I just reinstalled it. Thanks for your help!
kwoad said:
What command are you using to install TWRP to your bootpartition?
I think the correct one is something like:
Code:
fastboot flash recovery (file name).img
Click to expand...
Click to collapse
And For Samsung devices, any method via using ODIN
(Samsung E7/E700H)
freepenguin84 said:
Unfortunately then I don't know how to help Because that's exactly what I did and I got TWRP running without any problem. If you flash via 'fastboot flash recovery' command will it be on the device after you reboot for the first time?
Click to expand...
Click to collapse
Apparently "yes". Source this xda article- https://www.xda-developers.com/how-to-install-twrp/
I tried to create a custom boot logo using logo builder 1.6
I followed all the steps as mentioned in the thread for creating a logo.
After renaming logo.bin to logo.img , the next step was given to flash this image using twrp.
So, after flashing I got stuck on boot logo (the loop is the starting venom logo as for the venom kernel )and I cannot access twrp recovery nor can I flash anything using SP flash tool via laptop.
Please help ASAP
Wtf!! No one is replying
Should I ping devs then?
use fastboot
Nicconike said:
Wtf!! No one is replying
Should I ping devs then?
Click to expand...
Click to collapse
use fastboot mode to flash twrp then try to boot in it
download twrp and put it in a folder and open command prompt in it use this command fastboot flash recovery twrp.img
akshay_rajput said:
use fastboot mode to flash twrp then try to boot in it
download twrp and put it in a folder and open command prompt in it use this command fastboot flash recovery twrp.img
Click to expand...
Click to collapse
Thanks for your reply
None of the methods are working because phone was always looping in for bootlogo
But no issues just now I found a way , finally I can retrieve all internal data and clean wipe the ROM yayy!!
Now, i won't be using logo builder ever
Can anyone tell me what this (remote: Flashing is not allowed in Lock State).
What exactly is locked? Is my cell OEM unlocked?
I flashed the wrong TWRP (for the 2017 Red Magic-NX209J) and even though I have been able to unlock my cell via CMD commands; it remains permanently in fastboot mode?
If I send a CMD command to reboot it reboots straight back to fastboot mode.
No form of ADB connect seems to work an my windows PC cannot see/show the cell?
How the hell do I fix this? It's been in this state for a week.
Can anyone help?
Meaby try this?
Then, to unlock your bootloader, enter "fastboot oem nubia_unlock NUBIA_NX629J"
And meaby try the recovery backup instead of TWRP.
xronaldx said:
Meaby try this?
Then, to unlock your bootloader, enter "fastboot oem nubia_unlock NUBIA_NX629J"
And meaby try the recovery backup instead of TWRP.
Click to expand...
Click to collapse
Thanks for the suggestion. I have no recovery back up Is it possible to get past TWRP being locked and use CMD to flash the International or chinese ROM? Or recovery image?
Unless tools are developed to unbrick this device I am scared this problem might be permanent
Download this twrp, and then upload it to google drive or something so the rest of us can download it too .
Password is: 6i3i
https://pan.baidu.com/s/1ZdMPjm2fEwt...06770439204444
Secretcow said:
Download this twrp, and then upload it to google drive or something so the rest of us can download it too .
Password is: 6i3i
https://pan.baidu.com/s/1ZdMPjm2fEwt...06770439204444
Click to expand...
Click to collapse
Thanks but what do i do with it? Its all in an asain language?
Link not open bro
The TWRP does not work
Sorry. That link to the twrp does not result in a bootable twrp recovery for me.
I am starting to think my cell is not fixable.
I did not do that much wrong I just flashed the twrp for 2 models of red magic earlier. It only has a fastboot mode. I either get a boot screen then fastboot mode or a warning about the bootloader being unlocked.
Whatever is wrong with my cell prevents ADB connect an the cell is not able to be seen by windows.
This $1100 New Zealand dollar cellphone may be permanently bricked by my mistake.
I might just need to bin it an buy another one.
Lesson learned.
It confusing....
My cell acts like it has a softbrick (can turn off an on an has fastboot options and I have erased it an OEm an bootloader unlocked it)
And also behaves like a hard brick (resists every method of repair).
I just do not understand it or Nubia products. I am unfamiliar with this phone.
Does anyone have any clue how I can see this cell on my windows pc or ADB connect it an boot into TWRP?
Are there any Nubia repair software tools?
I already share nubia red magic 3 twrp check my all post
sandeepkhatri said:
I already share nubia red magic 3 twrp check my all post
Click to expand...
Click to collapse
Thanks for that. I'm talking about using CMD to totally wipe everything in the cell an reflash the Chinese ROM that came with it. Repair software. Might take months to develop software like that.
sandeepkhatri said:
I already share nubia red magic 3 twrp check my all post
Click to expand...
Click to collapse
Also it isn't a zip. It's some other kind of file. And does not boot into TWRP on my unit
So are you able to unlock your bootloader in its current state?
If you have an older TWRP installed maybe try changing the model on your bootloader command to match it:
fastboot oem nubia_unlock NUBIA_NX209J
If this works then flash the correct TWRP and the boot IMG from your original rom
fastboot flash recovery <new recovery>
fastboot reboot bootloader
Sent from my NX629J using Tapatalk
terrapin4 said:
So are you able to unlock your bootloader in its current state?
If you have an older TWRP installed maybe try changing the model on your bootloader command to match it:
fastboot oem nubia_unlock NUBIA_NX209J
If this works then flash the correct TWRP and the boot IMG from your original rom
fastboot flash recovery <new recovery>
fastboot reboot bootloader
Click to expand...
Click to collapse
Terrapin. Absolutely nothing worked. I am the 3rd person who has had this issue I know of. 2 other xda members had the same issue. One with TWRP like me an the other got stuck in fastboot mode after trying g to flash an apk of Gapps? I think these cells do not like tinkering. But your advice enabled me to be OEM and bootloader unlocked. But always.....straight back to fastboot mode no matter what I flash? My red magic 3 device is currently at a service center with a technician trying to solve the problem. I have 3 repayments left on my Xiaomi Mi9 that has zero flashing issues. O admit i.may be ignorant of the ways of Nubia ?
I did it
I extracted the file system.img
this is what I did ....
starting from the Chinese ROM http://ui.nubia.cn/rom/detail/62
Download download necessary files https://drive.google.com/drive/folders/16in6Jnyi4s5aIIuQwapQ1KK1LjysSfYm?usp=sharing
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash parameter parameter.img
fastboot reboot
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash system system.img
fastboot reboot
enter recovery, use a FAT32 pendrive format, add Chinese ROM, rename it (update.zip) to OTG flash.
Everything works again.
good luck.
emmegitony said:
I did it
I extracted the file system.img
this is what I did ....
starting from the Chinese ROM http://ui.nubia.cn/rom/detail/62
Download download necessary files https://drive.google.com/drive/folders/16in6Jnyi4s5aIIuQwapQ1KK1LjysSfYm?usp=sharing
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash parameter parameter.img
fastboot reboot
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash system system.img
fastboot reboot
enter recovery, use a FAT32 pendrive format, add Chinese ROM, rename it (update.zip) to OTG flash.
Everything works again.
good luck.
Click to expand...
Click to collapse
Thank God. Maybe the Chinese service guy I'm paying will get on xda an try your idea. I'm being lazy saying that lol. Thanks very very much. I will show your post to the service guy who has my red magic 3 or try it myself.
There's no way your a junior member working all this out. I'm a junior member listed as a senior member who makes rookie flashing errors with Chinese cellphones lol.
I will share if I can implement your ideas successfully. Thanks buddy my missus really loved this phone I felt really bad when I incapacitated it.
Fingers crossed.....
I have no idea how did you managed to flash the system.img
C:\adb>fastboot flash system system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
LE: After this error, somehow it manages to continue and flash all partitions of the system, but after above tutorial, the phone still reboots in fastboot mode and cannot access recovery
The solution is here:
https://forum.xda-developers.com/re...tboot-mode-t3937527/post79715050#post79715050
sakilxda said:
The solution is here:
https://forum.xda-developers.com/re...tboot-mode-t3937527/post79715050#post79715050
Click to expand...
Click to collapse
Thanks for the help. I do not understand some of the commands an cannot seem to get them right? And I do not understand why the instructions say to cmd flash the image (IMG) via command prompt (which just errors like the strange NON-HLOS command?) Then the instructions say to flash the Chinese rom via otg?
Are you supposed to flash the ROM twice?
Can someone please give me some more detailed instructions as this cell has been non functional about 2 months now.
Planning to fix it an give it to my partner
Bryceicle1971 said:
Thanks for the help. I do not understand some of the commands an cannot seem to get them right? And I do not understand why the instructions say to cmd flash the image (IMG) via command prompt (which just errors like the strange NON-HLOS command?) Then the instructions say to flash the Chinese rom via otg?
Are you supposed to flash the ROM twice?
Can someone please give me some more detailed instructions as this cell has been non functional about 2 months now.
Planning to fix it an give it to my partner
Click to expand...
Click to collapse
Hane you fixed the phone or not?
JerryYin said:
Hane you fixed the phone or not?
Click to expand...
Click to collapse
No still not working. Might try again when I have spare time. Very hard cellphone to fix
Bryceicle1971 said:
No still not working. Might try again when I have spare time. Very hard cellphone to fix
Click to expand...
Click to collapse
My suggestions is, download a full sd card update package, unlock the bootloader temporarily,extract the update file and flash the vbmeta.img to vbmeta partion, then flash the recovery.img to recovery partition, after that, try to boot into recovery through bootloader. You have to make sure that you use all the same file from same package, if you are use a low version vbmeta file to boot a high version system (or recovery ) it will not boot. the vbmeta is very important on this phone.