Related
Hi all
I am in urgent need of help to fix my Atrix 4G.
The Story:
I have an Atrix 4G. It was on 2.2.4 then official update came and I updated it to 2.2.6.
Then I was wondering about installing custom rom. This was my first time to install a custom rom. So I googled and found.
Code:
http://forum.xda-developers.com/showthread.php?t=1398819
Neutrino ROM V2.9 [14/08].
So I rooted and unlocked my fone. My fone was successfully rooted and unlocked and I restarted it and there was Unlocked written on Booting Screen.
In this procedure I had to reset the phone so it was back to 2.2.4.
After that I downloaded the above rom put in in SD Card and Downloaded Recovery APK from market and it asked to restart the phone with power adapter plugged to start so I did the same. And recovery started. Then following the instructions I installed the custom rom and it was installed successfully it was my first time so I didnt took any backups unfortunately. So after installation the phone did'nt actually start. It was stuck on Booting Screen with Moto Logo.
So I again googled and started to find the solution some said restart some said remove battery some said wait I tried all but no result.
Then I tried to install the stock rom.Following this
Code:
http://androidforums.com/atrix-4g-all-things-root/510778-flashing-back-stock.html
When i start to run RSD lite it says Creating Image and then throws an error like Unable to send RAM files.
Now I want to fix my Atrix 4g and there is no backup and no recovery mod.
My fone can go into options like Fastboot and RSD Protocol Mode. I mean I can access options on pressing Power and Volume Up/Down buttons.
Can any one please tell me solution? I will be very very thankful.
In fastboot flash recovery
fastboot devices
fastboot erase recovery
fastboot falsh recovery recovery.img
fastboot reboot
Go to recovery mode, try to wipe data, cache and dalvik. If you have Neutrino rom on your internal SDcard you can flash it with recovery.
ovitz said:
In fastboot flash recovery
fastboot devices
fastboot erase recovery
fastboot falsh recovery recovery.img
fastboot reboot
Go to recovery mode, try to wipe data, cache and dalvik. If you have Neutrino rom on your internal SDcard you can flash it with recovery.
Click to expand...
Click to collapse
I have erased data many time from the Android Recovery
And I think there will be no recovery.img. Where can I get it??
There is option of data and cache partition wipe but there is no option like Dalvik.
Can you please guide me it was my first time with custom roms and I didnt took any backups.
in fastboot package is recovery...
ovitz said:
in fastboot package is recovery...
Click to expand...
Click to collapse
Thanks, Fortunately my senior has installed Custom rom in it. And it is working fine with custom rom.
Are there other ways to flash a recovery with a locked bootloader?
My Problems:
I can't flash my stock recovery through fastboot with a locked bootloader.
I can't boot into my recovery because my current recovery is TWRP 2.5.0.1 and I have a locked bootloader.
I can't unlock my bootloader because I have used an IMEI Hack Tool and set my IMEI to 0 (I guess).
I can't boot into my ROM because I used an IMEI Hack Tool.
I can't Force Upgrade too (Vol Up + Down + Power). It only shows a pink/purple screen.
Solutions:
I can only flash a recovery with an unlocked bootloader.
I can only boot into a recovery with an unlocked bootloader (except for stock).
I can only unlock bootloader if my IMEI has restored.
I can only restore my IMEI if I can boot into my ROM.
I can only boot into my ROM if I have a stock recovery.
I can only Force Upgrade if I have restored my IMEI.
If I could only restore my IMEI through fastboot, that would be great!
So, please help!
You cant restore stock recovery ?
You cant enter to trwp ?
You cant restore IMEI cuz rom bootloop ?
You cant force flash stock firmware cuz fastboot is pink ?
I also "zero" my imei many times to flash stock firmware, but i allways can enter trwp and restore buckup or flash rom in zip
OmenHTX said:
You cant restore stock recovery ?
You cant enter to trwp ?
You cant restore IMEI cuz rom bootloop ?
You cant force flash stock firmware cuz fastboot is pink ?
I also "zero" my imei many times to flash stock firmware, but i allways can enter trwp and restore buckup or flash rom in zip
Click to expand...
Click to collapse
I can force upgrade now since i formatted my sd card. But the force upgrade fails at step 2/2.
.vonpatrick. said:
I can force upgrade now since i formatted my sd card. But the force upgrade fails at step 2/2.
Click to expand...
Click to collapse
If upgrade fail as step 2/2 your IMEI its not "zero" cuz IMEI block upgrading firmware from branded to nonbranded
OmenHTX said:
If upgrade fail as step 2/2 your IMEI its not "zero" cuz IMEI block upgrading firmware from branded to nonbranded
Click to expand...
Click to collapse
If my imei is not zero, then why can't i boot my phone?
And why can't i unlock my bootloader with my unlock code?
.vonpatrick. said:
If my imei is not zero, then why can't i boot my phone?
And why can't i unlock my bootloader with my unlock code?
Click to expand...
Click to collapse
OK, lest start from beggining
1.You must unlock bootloader by code ( first run check Lock / Unlock status ) (fastboot mod)
2. Flash TRWP (fastboot mod)
3. Flash SuperSU or Superuser zip (trwp)
4. Backup IMEI on running rom
5. Hack IMEI on running rom
6. Update phone by forceupdate flash update.app (rom in root of sd card > folder dload > update.app)
7. Run stock rom , lest install, shut down phone
8. Run TRWP to install SuperSU/Superuser zip
8. Restore IMEI (on working rom)
9. Go to TRWP and Wipe dalvik cache
10. Now you have working newest stock rom with root
So :
1. You cant have trwp in lockedbootloader
2. If update fail on 2/2 IMEI is not "zero"
3. Pink LCD on "update mod" = no rom in sd card
Next :
Hold Vol Down + Vol Up + Power to forceupdate firmware mod
Hold Vol Up + Power to run TRWP or stock recovery ( hold about 5s)
Hold Vol Down + Power for fastboot mod (5s-10s)
If you now have locked bootloader , with stock recovery, and force update fail, you cant unlock bootloader and flash trwp > Last hope is in "oryginal" rom, your IMEI will not block it.
OmenHTX said:
OK, lest start from beggining
1.You must unlock bootloader by code ( first run check Lock / Unlock status ) (fastboot mod)
2. Flash TRWP (fastboot mod)
3. Flash SuperSU or Superuser zip (trwp)
4. Backup IMEI on running rom
5. Hack IMEI on running rom
6. Update phone by forceupdate flash update.app (rom in root of sd card > folder dload > update.app)
7. Run stock rom , lest install, shut down phone
8. Run TRWP to install SuperSU/Superuser zip
8. Restore IMEI (on working rom)
9. Go to TRWP and Wipe dalvik cache
10. Now you have working newest stock rom with root
So :
1. You cant have trwp in lockedbootloader
2. If update fail on 2/2 IMEI is not "zero"
3. Pink LCD on "update mod" = no rom in sd card
Next :
Hold Vol Down + Vol Up + Power to forceupdate firmware mod
Hold Vol Up + Power to run TRWP or stock recovery ( hold about 5s)
Hold Vol Down + Power for fastboot mod (5s-10s)
If you now have locked bootloader , with stock recovery, and force update fail, you cant unlock bootloader and flash trwp > Last hope is in "oryginal" rom, your IMEI will not block it.
Click to expand...
Click to collapse
Wait, let me put this in summary:
1.
- I have a locked bootloader.
- I can't unlock the bootloader because it says "recovery image verify failed".
- It can only mean one thing: my IMEI must have changed.
2.
- I have a TWRP recovery.
- At first, my original recovery was the stock when I have a locked bootloader.
- Then I flashed the TWRP recovery even if I have a locked bootloader and didn't warned me. (Shoudn't it be accepted to be flashed since I have a locked bootloader).
- In my experience, if I have a stock recovery when I'll hack my IMEI, it will format my cache and data and let me boot into my phone.
- If I have a TWRP recovery when I'll hack my IMEI, it will only redirect me to the TWRP menu.
3.
- I can access Force Upgrade.
- But it doesn't show any text. (For example: it doesn't show if it is unpacking or installing, only a bar.)
- When I access Force Upgrade, the loading stops at 1/4 of the bar. (So I'm not really sure if it failed at step 2/2.)
So my questions are:
1. Why can't I unlock my bootloader with my original IMEI's unlock code if my IMEI is not "zero"?
2. Why is it when I Force Upgrade, it doesn't show any text?
3. Why did fastboot accepted the TWRP recovery being flashed when my bootloader was locked?
And, what do you mean by "original"? Do you mean the B182 firmware upgrade, not the B175?
After hacking IMEI you cant have stock recovery, cuz you need root for shell script. So its not making "auto wipe" to change OEM info.
TRWP should not be installed on lockbootloader, but i dont make it ...
So , do you have working trwp or not ?
Oryginal firmware ... version when you get with phone, like my Y300-0100 branded T-Mobile PL B167
OmenHTX said:
After hacking IMEI you cant have stock recovery, cuz you need root for shell script. So its not making "auto wipe" to change OEM info.
TRWP should not be installed on lockbootloader, but i dont make it ...
So , do you have working trwp or not ?
Oryginal firmware ... version when you get with phone, like my Y300-0100 branded T-Mobile PL B167
Click to expand...
Click to collapse
I am sure i have twrp.
If i have a stock recovery, i would be able to boot into recovery.
Based in my experience:
1. To hack the imei, you must first root your phone.
2.a. Next, the phone will reboot, but it won't boot into system.
2.b. Fastboot, force upgrade, and recovery is still accessible.
3.a. If you have a twrp recovery when you hacked the imei and rebooted, it will redirect you to the twrp menu.
3.b. If you tried to restore from twrp recovery, it still won't reboot into system.
3.c. If you have a stock recovery, it will directly boot into stock recovery and format your cache and data and reboot to system (still leaves your imei to zero)
4. If you go to force upgrade, you can flash any official roms (leaves your imei to zero)
5. After you have flashed a rom or was redirected to stock recovery, your phone will reboot.
6.a. Then root your phone and restore imei then your phone will reboot.
6.b. If you have a stock recovery, it will wipe your cache and data.
6.c. If you have a twrp recovery, it will redirect you to the twrp menu (you can manually reboot into system)
Am i right?
And where can i get the original rom for my b182? There's no local huawei store here.
.vonpatrick. said:
I am sure i have twrp.
If i have a stock recovery, i would be able to boot into recovery.
Click to expand...
Click to collapse
So why you dont run TRWP and flash any rom in zip ?
OmenHTX said:
So why you dont run TRWP and flash any rom in zip ?
Click to expand...
Click to collapse
Twrp is not accessible if you have a locked bootloader.
bricked
I have a big problem. My Ascend y300 started to work strange yesterday, my PC didnt see the internal sd nor the external SD correctly. Today I restarted it and now I get blue screen when I start it. I had TWRP installed, but when I try to access it, it gives blue screen aswell. Any solutions?
gery0518 said:
I have a big problem. My Ascend y300 started to work strange yesterday, my PC didnt see the internal sd nor the external SD correctly. Today I restarted it and now I get blue screen when I start it. I had TWRP installed, but when I try to access it, it gives blue screen aswell. Any solutions?
Click to expand...
Click to collapse
Try this through fastboot:
fastboot erase recovery
fastboot flash recovery <path to recovery.img>
.vonpatrick. said:
Try this through fastboot:
fastboot erase recovery
fastboot flash recovery <path to recovery.img>
Click to expand...
Click to collapse
My problem is a little bit more complex unfortunately. I tried what you said. When I push the buttons to enter fastboot, my phone dont freez at splashscreen and I get bluescreen. When I connect it to my PC my PC recognizes it though, BUT ADB cant see it. I reinstalled the drivers any times, without success.
gery0518 said:
My problem is a little bit more complex unfortunately. I tried what you said. When I push the buttons to enter fastboot, my phone dont freez at splashscreen and I get bluescreen. When I connect it to my PC my PC recognizes it though, BUT ADB cant see it. I reinstalled the drivers any times, without success.
Click to expand...
Click to collapse
What did you do anyway why it got the blue screen?
.vonpatrick. said:
What did you do anyway why it got the blue screen?
Click to expand...
Click to collapse
That is the most strange part of the story. I totally did nothing. I opened bootloader, installed twrp, rooted it, installed init.d support, installed a ramscript. The phone worked totally fine until yesterday. I did a restart yesterday and bumm, bluescreen. And I did nothing before this happened. Srsly, no problems detected, it came from nothing...
gery0518 said:
That is the most strange part of the story. I totally did nothing. I opened bootloader, installed twrp, rooted it, installed init.d support, installed a ramscript. The phone worked totally fine until yesterday. I did a restart yesterday and bumm, bluescreen. And I did nothing before this happened. Srsly, no problems detected, it came from nothing...
Click to expand...
Click to collapse
Can't you really boot into fastboot (Power + up)?
Hold it for like 10 seconds.
If it still shows blue screen, try connecting it to pc, maybe it'll read it.
Then erase recovery and flash twrp.
Wipe everything and restore a backup you made.
.vonpatrick. said:
Can't you really boot into fastboot (Power + up)?
Hold it for like 10 seconds.
If it still shows blue screen, try connecting it to pc, maybe it'll read it.
Then erase recovery and flash twrp.
Wipe everything and restore a backup you made.
Click to expand...
Click to collapse
Well, my problem is, that despite of the blue screen, fastboot seems to work. My pc sees my device, BUT ADB refuses to see it, and I dont know why. I will try it from win xp under virtualbox now.
hi Gery
How do you manage to get the phone into fastboot mode?
my y300 also enters blue screen everytime now. I try to press voldown + power for like 10 seconds, yet the fastboot command is not working.
gery0518 said:
Well, my problem is, that despite of the blue screen, fastboot seems to work. My pc sees my device, BUT ADB refuses to see it, and I dont know why. I will try it from win xp under virtualbox now.
Click to expand...
Click to collapse
Well, that's perfect! If the PC can read the device from fastboot, you can erase the recovery and flash the twrp and restore from backup. But if it still goes blue, flash the system, data, cache, boot, recovery from your twrp backup.
Recently bricked my honor 5x used fast boot to get it out of boot loop. (Because I tried to its update my phone with twrp)now when I try to re flash twrp it gets replaced by the stock recovery Everytime . Please help!
Samething happend to me... cannot flash twrp because when i restart phone after flashing twrp, it gets replaced by stock recovery.
What i do now is to boot to twrp instead of flashing using this command:
Code:
fastboot boot twrp-3.0.0-0-kiwi.img
Hopefully there is a solution for this flashing problem.
FREAK0N said:
Samething happend to me... cannot flash twrp because when i restart phone after flashing twrp, it gets replaced by stock recovery.
What i do now is to boot to twrp instead of flashing using this command:
Code:
fastboot boot twrp-3.0.0-0-kiwi.img
Hopefully there is a solution for this flashing problem.
Click to expand...
Click to collapse
you can't just reboot after flashing recovery ...you have to boot directly to twrp after the flash with power + volume up (Skip the fastboot reboot step)
the simple way is to copy kiwi_twrp_3-21_recovery.img to your sdcard
fastboot boot kiwi_twrp_3-21_recovery.img
now in twrp choose install / image / then choose kiwi_twrp_3-21_recovery.img
next choose reboot / recovery
you now have kiwi_twrp_3-21_recovery.img
from then on adb reboot recovery from android
or power + volume up will enter TWRP
clsA said:
you can't just reboot after flashing recovery ...you have to boot directly to twrp after the flash with power + volume up (Skip the fastboot reboot step)
the simple way is to copy kiwi_twrp_3-21_recovery.img to your sdcard
fastboot boot kiwi_twrp_3-21_recovery.img
now in twrp choose install / image / then choose kiwi_twrp_3-21_recovery.img
next choose reboot / recovery
you now have kiwi_twrp_3-21_recovery.img
from then on adb reboot recovery from android
or power + volume up will enter TWRP
Click to expand...
Click to collapse
Thanks alot... i wil try it later.
Too many Links is what ADB Says
RootMega said:
Too many Links is what ADB Says
Click to expand...
Click to collapse
why are you using adb ?
did you read the instructions i posted
I have the stock recovery.
I cant get into twrp.
I tried to flash then go straight to twrp which gets replaced by stock bootloader
Idk it gets replaced everytime
Okay the adb thing stopped I got into twrp by doing the fastboot thing but when i boot into recovery it goes to the stock recovery.
RootMega said:
Okay the adb thing stopped I got into twrp by doing the fastboot thing but when i boot into recovery it goes to the stock recovery.
Click to expand...
Click to collapse
I really don't know why you don't seem to get it
it's this simple
you fastboot boot kiwi_twrp_3-21_recovery.img
now while in TWRP copy kiwi_twrp_3-21_recovery.img to the phone
Also copy SuperSU-v2.64.zip (or newer) to the phone
after the files are copied choose Install / Image / kiwi_twrp_3-21_recovery.img
next choose install / SuperSU.zip
next choose Reboot / Recovery
you now have TWRP recovery and you can enter it by using power + volume up
or from an app on the phone (I use Quickboot) or from a pc with adb reboot recovery
I have the same problem, i tried with your method but the system continue to replace bootloader, impossible to keep twrp on recovery
Edit : I try to install Root Checker, it detect my phone is root but impossible to access to TWRP, very strange
clsA said:
you can't just reboot after flashing recovery ...you have to boot directly to twrp after the flash with power + volume up (Skip the fastboot reboot step)
the simple way is to copy kiwi_twrp_3-21_recovery.img to your sdcard
fastboot boot kiwi_twrp_3-21_recovery.img
now in twrp choose install / image / then choose kiwi_twrp_3-21_recovery.img
next choose reboot / recovery
you now have kiwi_twrp_3-21_recovery.img
from then on adb reboot recovery from android
or power + volume up will enter TWRP
Click to expand...
Click to collapse
Tried this on my KIW-L21, as this is the only way I did not try it yet...
Did not work, unfortunately, I assume the OP could have the same problem as I already posted in the TWRP thread:
http://forum.xda-developers.com/showpost.php?p=66678377&postcount=509
(It is a shame people spam this thread with unlocking problems, though)
EarlyMon mentioned something about dual recovery partitions here: http://forum.xda-developers.com/showpost.php?p=66838009&postcount=529
So regardless how many times I flash TWRP it wont stick until the next reboot to recovery, as it gets replaced by the stock one all the time.
I am thankful for every news on that topic and I would happily help(to the extent I am able to) getting TWRP back onto our phones :good:
P.S.: I am not quite sure if the OP has another problem in flashing the recovery, though.
Nekly said:
Tried this on my KIW-L21, as this is the only way I did not try it yet...
Did not work, unfortunately, I assume the OP could have the same problem as I already posted in the TWRP thread:
http://forum.xda-developers.com/showpost.php?p=66678377&postcount=509
(It is a shame people spam this thread with unlocking problems, though)
EarlyMon mentioned something about dual recovery partitions here: http://forum.xda-developers.com/showpost.php?p=66838009&postcount=529
So regardless how many times I flash TWRP it wont stick until the next reboot to recovery, as it gets replaced by the stock one all the time.
I am thankful for every news on that topic and I would happily help(to the extent I am able to) getting TWRP back onto our phones :good:
P.S.: I am not quite sure if the OP has another problem in flashing the recovery, though.
Click to expand...
Click to collapse
So you are booting TWRP
Installing / TWRP.Img in TWRP and Reboot recovery and your not booting to TWRP ?
Just my two cents into this thread: apparently (from my personal experience, and EarlyMon seems to back this up) the Honor 5X for whatever reason allows the installation of TWRP but still keeps Huawei's stock recovery in place, unlike most phones. What's more, it randomly (yeah, guessing it's not random obviously, but I don't have the slightest clue what the pattern might be) decides to boot into stock recovery while I use the same hardware keys that have continuously booted me into TWRP up until that point. This behavior led me to believe I had bricked my phone for a day, lol (I made a recent post about it on this forum, in case anyone cares).
Bottom line: if you can't boot into TWRP even though you made sure to install it correctly, try changing the key combo. Vol down + Power not working for you? Try Vol Up. Neither work? Try Vol Up + Down + Power. Spice it out and it might solve your problems.
clsA said:
So you are booting TWRP
Installing / TWRP.Img in TWRP and Reboot recovery and your not booting to TWRP ?
Click to expand...
Click to collapse
That is correct:
Connected Phone to PC
ADB reboot bootloader
fastboot boot kiwi.img
install image kiwi.img
reboot recovery
Tada, Stock eMUI Recovery :[
I really had hoped it would do the trick, though.
Nekly said:
That is correct:
Connected Phone to PC
ADB reboot bootloader
fastboot boot kiwi.img
install image kiwi.img
reboot recovery
Tada, Stock eMUI Recovery :[
I really had hoped it would do the trick, though.
Click to expand...
Click to collapse
what version of TWRP are you using ? whats the real file name ?
Has anyone tried flashing TWRP with TWRP Manager from the play store?
Sm0k3d 0uT said:
Has anyone tried flashing TWRP with TWRP Manager from the play store?
Click to expand...
Click to collapse
Been there and done that. Same outcome.
clsA said:
what version of TWRP are you using ? whats the real file name ?
Click to expand...
Click to collapse
The last approach was done with the one from the first post of the TWRP thread here on XDA(https://goo.gl/53xai9) "kiwi_twrp_3-21_recovery.img"
I also tried the TWRP images from https://twrp.me/devices/huaweihonor5x.html but always the same result.
I can try with a specific image, just give me a link and I'll try to flash it. :fingers-crossed:
Hey,
I wanted to do a nandroid backup so I did adb reboot recovery to go to TWRP, now I can't boot into system, I'm stuck in twrp, I can't even power off the phone it keeps booting up again and again. Please help i'm really lost. Thanks
I did boot to System but with another key combinaison (volume down + power) , I think it's all messed up and the phone thinks that the recovery is the default boot option.. idk how to change this
Nexx_ said:
I did boot to System but with another key combinaison (volume down + power) , I think it's all messed up and the phone thinks that the recovery is the default boot option.. idk how to change this
Click to expand...
Click to collapse
If you can reach the stock recovery, just put update.app file and install it. If you can't, try to flash boot.img and recovery.img manually. After that, try to install rom again.
memht said:
If you can reach the stock recovery, just put update.app file and install it. If you can't, try to flash boot.img and recovery.img manually. After that, try to install rom again.
Click to expand...
Click to collapse
Okay thank you, I will try flashing them manually because I have twrp
@DigiGoon Please can you help me with it?
You were on which system? Stock or any Custom ROM?
DigiGoon said:
You were on which system? Stock or any Custom ROM?
Click to expand...
Click to collapse
I was on stock b371
Okay follow these step, if you don't understand any step ask again. But follow these:
Download the UPDATE.APP of the Build number you were on before.
Extract system.img, boot.img, recovery.img, cust.img from that UPDATE.APP
Flash all these files via bootloader mode, to boot into bootloader mode, once a loop is over and you see blank screen on your phone, quickly press Vol DOWN button and while pressing it connect your phone to a PC. If this doesn't work and you get into recovery, then in recovery go to option Reboot, in that select Bootloader.
Once in bootloader mode, flash these files by firing these commands from a CMD, make sure files are situated in the same location where you open up the CMD.
Code:
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot flash boot boot.img
Now after your phone boots up normally, put the same UPDATE.APP from which these files were extracted in dload folder of your external SDcard.
Now switch off your phone and press all the three buttons(Vol UP + Vol DOWN + Power) simultaneously.
Flashing process will start.
Hope this helps.
DigiGoon said:
Okay follow these step, if you don't understand any step ask again. But follow these:
Download the UPDATE.APP of the Build number you were on before.
Extract system.img, boot.img, recovery.img, cust.img from that UPDATE.APP
Flash all these files via bootloader mode, to boot into bootloader mode, once a loop is over and you see blank screen on your phone, quickly press Vol DOWN button and while pressing it connect your phone to a PC. If this doesn't work and you get into recovery, then in recovery go to option Reboot, in that select Bootloader.
Once in bootloader mode, flash these files by firing these commands from a CMD, make sure files are situated in the same location where you open up the CMD.
Code:
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot flash boot boot.img
Now after your phone boots up normally, put the same UPDATE.APP from which these files were extracted in dload folder of your external SDcard.
Now switch off your phone and press all the three buttons(Vol UP + Vol DOWN + Power) simultaneously.
Flashing process will start.
Hope this helps.
Click to expand...
Click to collapse
Thank you a lot for helping me I'll try to follow the process as soon as I get windows on my Mac
@DigiGoon No need to flash system.img actually Just cust, boot and recovery is enough (i think). I forgot to tell cust but it's not necessary always.
memht said:
@DigiGoon No need to flash system.img actually Just cust, boot and recovery is enough (i think). I forgot to tell cust but it's not necessary always.
Click to expand...
Click to collapse
The way his phone is acting, system is the main thing he needs to flash.
Same kind of problem different dude
DigiGoon said:
Okay follow these step, if you don't understand any step ask again. But follow these:
Download the UPDATE.APP of the Build number you were on before.
Extract system.img, boot.img, recovery.img, cust.img from that UPDATE.APP
Flash all these files via bootloader mode, to boot into bootloader mode, once a loop is over and you see blank screen on your phone, quickly press Vol DOWN button and while pressing it connect your phone to a PC. If this doesn't work and you get into recovery, then in recovery go to option Reboot, in that select Bootloader.
Once in bootloader mode, flash these files by firing these commands from a CMD, make sure files are situated in the same location where you open up the CMD.
Code:
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot flash boot boot.img
Now after your phone boots up normally, put the same UPDATE.APP from which these files were extracted in dload folder of your external SDcard.
Now switch off your phone and press all the three buttons(Vol UP + Vol DOWN + Power) simultaneously.
Flashing process will start.
Hope this helps.
Click to expand...
Click to collapse
I'm having similar problem as OP. I get access to TWRP(by holding power+vol up), but not fastboot anymore. My TWRP is in chinese and but I found the reboot menu and the alternatives are: System, Power Off, Recovery and Download. I think i've tried them all and none of them brings me fastboot. I went into loop when I tried to install SuperSu through TWRP on stock rom. Is there hope? Yesterday I managed to get into fastboot, but can't remember what I did. I heard something about draining the battery and then theres hope?
mosoo said:
I'm having similar problem as OP. I get access to TWRP(by holding power+vol up), but not fastboot anymore. My TWRP is in chinese and but I found the reboot menu and the alternatives are: System, Power Off, Recovery and Download. I think i've tried them all and none of them brings me fastboot. I went into loop when I tried to install SuperSu through TWRP on stock rom. Is there hope? Yesterday I managed to get into fastboot, but can't remember what I did. I heard something about draining the battery and then theres hope?
Click to expand...
Click to collapse
Several options you got:
Install older SuperSU. I remember I had the same thing and the only way was to downgrade SuperSU. 2.5x, I think.
Try to access fastboot - turn off phone, keep vol- pressed and power up. Release vol- when you see fastboot screen. Try it with and without USB PC connection.
Try to deplete your battery. It works in other devices as after charging again, boot.img behaves differently. Don't ask me why, but if the phone charges as it is, no harm in trying.
Wipe all partitions - Dalvik, cache, data, internal storage and system. And then install a custom ROM from sdcard or USB-OTG. You can access H7 content from PC, through USB, while in TWRP.
Huawei eRecovery
I got into Huawei eRecovery EMUI, but when I try to "Download latest version and recovery" and connect to wifi it fails:"Getting package info failed". The other options are Reboot and Shutdown. Could this be useful?
Another question how to transfer to sd-card when in twrp. The phone is detected in windows as MTP thingy, but in adb shell no devices is found... I'm too noob for this.
Got into fastboot mode, and flashed all the imgs except system.img where I get error "cannot load"... Got the ADB drivers now, but still adb shell finds no devices. It appears that my TWRP is gone, and instead I get Huawei eRecovery. So my problem now is that I dont get system.img flashed, still stuck at honor-logo, and can't push files with adb, I get "no devices". Any tips?
Got it now, thank you very much! But what's the point in doing the last steps with dload when everything seems to be good?
mosoo said:
I got into Huawei eRecovery EMUI, but when I try to "Download latest version and recovery" and connect to wifi it fails:"Getting package info failed". The other options are Reboot and Shutdown. Could this be useful?
Another question how to transfer to sd-card when in twrp. The phone is detected in windows as MTP thingy, but in adb shell no devices is found... I'm too noob for this.
Got into fastboot mode, and flashed all the imgs except system.img where I get error "cannot load"... Got the ADB drivers now, but still adb shell finds no devices. It appears that my TWRP is gone, and instead I get Huawei eRecovery. So my problem now is that I dont get system.img flashed, still stuck at honor-logo, and can't push files with adb, I get "no devices". Any tips?
Got it now, thank you very much! But what's the point in doing the last steps with dload when everything seems to be good?
Click to expand...
Click to collapse
Please share your solution with others, so that your post can be referred.
Doing a forced updated (dload) gives the absolute assurance you flashed all the partitions correctly with all the *.img compressed files in the update.app file.
mosoo said:
Got it now, thank you very much! But what's the point in doing the last steps with dload when everything seems to be good?
Click to expand...
Click to collapse
When you flash the partitions manually, we are not flashing all of them, only some of them, and some partitions are not in regular img format, so by doing the three button update we can put all the partitions in their respective places.
Another benefit of doing force update is that if you don't know your build number and flashed system.img, cust.img etc of some other build then by doing a force update all the img files of same build are flashed.
Hello, I'm kind of new at this (this is my first post) so be gentle
So, the last few days I've been trying to install a new rom on my phone (Redmi Note 4X) and the problems started with the model. I only seem to find Redmi Note 4 roms, and as I've come to find, mine is supposed to be the mido one (correct me if I'm wrong though). I have unlocked the bootloader, I have installed and enabled the fastboot on my phone, so the next step was to install the latest TWRP.
There came more problems; I tried doing this through the app and it just wouln't flash it. So I found a guide on how to root my phone and install a new recovery through adb and I followed it. It didn't work. I couldn't find the right twrp version for my phone. When I finally did realise my phone needed mido, I found the latest from the TWRP website. It wouldn't load through adb again. I found a thread about a fixed mido version, which finally worked for me. But my brother who was helping me, and isn't as much of a noob as I am (he has flashed rom and recoveries many times on his Nexus 5X), decided that I necessarily need the latest twrp if I'm going to flash a new rom, so he flashed the new twrp through the old one, and soft bricked my phone (I think). So I'm searching for a guide to unbrick it. (Which I can't seem to find to work at least).
To conclude;
I have unlocked my bootloader
I have access to the fastboot
I tried to flash a recovery
I failed many times, but I managed it
I flashed the latest twrp and bricked my phone
I don't have access to the recovery
My phone is still on a bootloop
I am not sure about which phone model I have
Help!
Thanks in advance.
1. Just check your phone model on its box. If its Snapdragon version (Mido), then just install it via fastboot. (code: fastboot flash recovery twrp-midoxx.img). If you are success, then try to reboot to recovery (fastboot boot twrpmido-xx.img). After booted, then you just manage to rom.zip you want to install. If you don't have it, then download it before from your PC and push it to your phone. Or just enable Mtp checklis from TWRP n copy that file to your internal phone/sdcard. Wipe all/factory reset except internal storage. Then you dan install rom.zip normally. N reboot. (Note: if you are on MIUI and wanted to always stay on it, just flash the file called lazyflasher.zip. n' wipe cache n art cache only then reboot). Flashing custom recovery on stock MIUI Will manage the device Going to bootloop)
2. If you have mediatek version (nikel), searching the fastboot Rom from miui website and flash it normally via fastboot. (SP Flash tool)
Warning: flash the wrong rom file into wrong phone Will make your device brick. So becarefull n knowing what model/code name you have.
Dyt199412syam said:
1. Just check your phone model on its box. If its Snapdragon version (Mido), then just install it via fastboot. (code: fastboot flash recovery twrp-midoxx.img). If you are success, then try to reboot to recovery (fastboot boot twrpmido-xx.img). After booted, then you just manage to rom.zip you want to install. If you don't have it, then download it before from your PC and push it to your phone. Or just enable Mtp checklis from TWRP n copy that file to your internal phone/sdcard. Wipe all/factory reset except internal storage. Then you dan install rom.zip normally. N reboot. (Note: if you are on MIUI and wanted to always stay on it, just flash the file called lazyflasher.zip. n' wipe cache n art cache only then reboot). Flashing custom recovery on stock MIUI Will manage the device Going to bootloop)
2. If you have mediatek version (nikel), searching the fastboot Rom from miui website and flash it normally via fastboot. (SP Flash tool)
Warning: flash the wrong rom file into wrong phone Will make your device brick. So becarefull n knowing what model/code name you have.
Click to expand...
Click to collapse
Hello and thanks for the reply. I have the snapdragon version, but all I'm asking is how am I supposed to flash the lazyflasher without accessing the recovery? Through adb?
fionik said:
Hello and thanks for the reply. I have the snapdragon version, but all I'm asking is how am I supposed to flash the lazyflasher without accessing the recovery? Through adb?
Click to expand...
Click to collapse
Firstly, enter fastboot mode on your device. Connecting to pc and flashing the twrp for mido. "fastboot flash recovery twrp-mido.img". Then boot to it using " fastboot boot twrp-mido.img". Then you will enter the recovery (twrp) in a second. Copy the lazyflasher into your phone (enable mtp first in Mount option in twrp) that you downloaded from pc. Just flash the lazyflasher.zip and reboot.
And why you don't want to flash lazyflasher when it very easy to flash it using recovery twrp? adb? You mean android debugging? Actually, you cant flash a .zip file into your system partition except through fastboot mode. However, fastboot mode (in cmd) only recognize a .img file. I just try to tell you the easier method to make your device boot up.
Dyt199412syam said:
Firstly, enter fastboot mode on your device. Connecting to pc and flashing the twrp for mido. "fastboot flash recovery twrp-mido.img". Then boot to it using " fastboot boot twrp-mido.img". Then you will enter the recovery (twrp) in a second. Copy the lazyflasher into your phone (enable mtp first in Mount option in twrp) that you downloaded from pc. Just flash the lazyflasher.zip and reboot.
And why you don't want to flash lazyflasher when it very easy to flash it using recovery twrp? adb? You mean android debugging? Actually, you cant flash a .zip file into your system partition except through fastboot mode. However, fastboot mode (in cmd) only recognize a .img file. I just try to tell you the easier method to make your device boot up.
Click to expand...
Click to collapse
As I said above, I can only access the fastboot, and I get errors in the adb when I try to flash the twrp image.
fionik said:
As I said above, I can only access the fastboot, and I get errors in the adb when I try to flash the twrp image.
Click to expand...
Click to collapse
Share your error please.
Try fastboot boot twrp.img