Related
I have a big problem.
I unlocked the bootloader through Sony's developer-site, then tried to flash AndroPlus' kernel and TRWP. I had to try numerous times, since for some reason it refused to boot to TWRP, even though system booted fine.
Each time I started with flashing (Nordic) stock with Flashtool.
I finally got the tablet to boot to TWRP, but after trying to boot to system, it got stuck in a bootloop. I had to flash to stock again.
Now no matter what I try to fastboot, I get "FAILED (Remote: command not allowed". Flashtool seems to be able to re-unlock the bootloader, but it makes no difference.
If I try to unlock it through Sony, it gives the same error (so fastboot doesn't work _at all_).
Still boots to system fine.
Any help or maybe a solution even..?
USB-Hub?
@IlariJ
I had the same problem when I hooked up the tablet to my USB-Hub at the monitor.
Diving under the desk and connecting to an USB port at the PC did magic
DHGE said:
@IlariJ
I had the same problem when I hooked up the tablet to my USB-Hub at the monitor.
Diving under the desk and connecting to an USB port at the PC did magic
Click to expand...
Click to collapse
I tried with different cables and different ports, still the same error.. I even resorted to Sony PC Companion's fix-tool, so I guess I have the regular stock now. I tried to unlock the bootloader again the "official" way, but that error persists.
Flashtool seems to be able to unlock (and relock) the bootloader, but this makes no difference for fastboot.
This is weird since if it had bricked for some reason, the solution would be to wipe my ass with it, but since the system boots and works fine, a little hope still lives.
@AndroPlus , any suggestions?
IlariJ said:
I tried with different cables and different ports, still the same error.. I even resorted to Sony PC Companion's fix-tool, so I guess I have the regular stock now. I tried to unlock the bootloader again the "official" way, but that error persists.
Flashtool seems to be able to unlock (and relock) the bootloader, but this makes no difference for fastboot.
This is weird since if it had bricked for some reason, the solution would be to wipe my ass with it, but since the system boots and works fine, a little hope still lives.
@AndroPlus , any suggestions?
Click to expand...
Click to collapse
I'm still stuck with this.. Any help?
IlariJ said:
Any help?
Click to expand...
Click to collapse
Unfortunately not.
http://forum.xda-developers.com/z4-tablet/help/fastboot-getvar-retrieves-t3264589
IlariJ said:
I'm still stuck with this.. Any help?
Click to expand...
Click to collapse
Did you do anything with MyXperia?
@DHGE @jelbo
I can honestly say I don't recall doing anything with or to MyXperia. If I accidentally "let" it trigger itself, would this mean that fastboot becomes unusable? For good? Not even a full wipe + reflash could salvage?
Did you accidentally read the link I provided?
IlariJ said:
@DHGE @jelbo
I can honestly say I don't recall doing anything with or to MyXperia. If I accidentally "let" it trigger itself, would this mean that fastboot becomes unusable? For good? Not even a full wipe + reflash could salvage?
Click to expand...
Click to collapse
Reading the thread DHGE linked to it seems that MyXperia interference can result in the device being unable to unlock it's bootloader again. That's all I can say, I don't even have my Z4T yet
DHGE said:
Did you accidentally read the link I provided?
Click to expand...
Click to collapse
I'm sorry to ask this, but could you please be a bit more friendly? While IlariJ didn't mention he read your linked topic, he does provide useful info about what he's tried so far. If you know a solution or an answer, it's much more positive to just give him that, even though that might be 'you're out of luck'.
@DHGE Sorry, I didn't know I wasn't supposed to. My bad.
@jelbo ok, bummer. I really just found (and still find) it hard to believe that fastboot could get permanently messed up, so that even a total reset wouldn't, well, reset it. Thanks, though!
@AndroPlus @[NUT]
How-to get that TWRP recovery image flashed, so I can get recovery access on my Z4T?
Enter fastboot mode on Xperia z4. Then type in cmd: fastboot flash recovery <path to twrp_file>
U need the fastboot binary from Google
Hundsbuah said:
Enter fastboot mode on Xperia z4. Then type in cmd: fastboot flash recovery <path to twrp_file>
U need the fastboot binary from Google
Click to expand...
Click to collapse
Already tried with that..
Only gettings this message;
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
What to do..? :/
Destroyedbeauty said:
@AndroPlus @[NUT]
How-to get that TWRP recovery image flashed, so I can get recovery access on my Z4T?
Click to expand...
Click to collapse
Hi
You can get it at: https://dl.androplus.org/Xperia Z4 Tablet SGP712_SGP771/
Download twrp_2.8.7.0_(not)fixed.img
you must have the usb driver installed in your PC and adb and fastboot installed from google sdk
Is there still any update or solution to having MyXperia f'd up fastboot?
I tried to contact Sony that to my knowledge only unlocking the bootloader voids warranty, and since that's impossible because fastboot doesn't work, I should get this fixed. They didn't really refuse (at least after my hard convincing) and told me to contact the seller.
I did, and the seller said fastboot is more of a gimmick-possibility than a "assumed-to-work"-feature of Android (safe to say I don't agree). They sent links to different YouTube-videos on older devices, but I couldn't really find any solution or even a 100%-matching problem.
They also said that if I send this for repairing, the service company would only do a wipe/reset and then bounce the tablet back. Given that the Finnish Sony-service is notorious for making up water damage and/or "mechanic damage" to get to refuse warranty, I'm not really confident to send it there.
And also, to my knowledge the problem is much deeper than what a simple reset would solve, since I've done that and even re-flashed the firmware.
..how is it even possible for a simple software to break the whole fundament of the tablet? So bad even a complete wipe and reflash doesn't help?
IlariJ said:
Is there still any update or solution to having MyXperia f'd up fastboot?
I tried to contact Sony that to my knowledge only unlocking the bootloader voids warranty, and since that's impossible because fastboot doesn't work, I should get this fixed. They didn't really refuse (at least after my hard convincing) and told me to contact the seller.
I did, and the seller said fastboot is more of a gimmick-possibility than a "assumed-to-work"-feature of Android (safe to say I don't agree). They sent links to different YouTube-videos on older devices, but I couldn't really find any solution or even a 100%-matching problem.
They also said that if I send this for repairing, the service company would only do a wipe/reset and then bounce the tablet back. Given that the Finnish Sony-service is notorious for making up water damage and/or "mechanic damage" to get to refuse warranty, I'm not really confident to send it there.
And also, to my knowledge the problem is much deeper than what a simple reset would solve, since I've done that and even re-flashed the firmware.
..how is it even possible for a simple software to break the whole fundament of the tablet? So bad even a complete wipe and reflash doesn't help?
Click to expand...
Click to collapse
Lets unconfuse me here, i was never in the loop of your issue, but maybe I can help:
Your device won't boot to fastboot at all?
What's the status of your bootloader?
[NUT] said:
Lets unconfuse me here, i was never in the loop of your issue, but maybe I can help:
Your device won't boot to fastboot at all?
What's the status of your bootloader?
Click to expand...
Click to collapse
This is still the situation :
IlariJ said:
I have a big problem.
I unlocked the bootloader through Sony's developer-site, then tried to flash AndroPlus' kernel and TRWP. I had to try numerous times, since for some reason it refused to boot to TWRP, even though system booted fine.
Each time I started with flashing (Nordic) stock with Flashtool.
I finally got the tablet to boot to TWRP, but after trying to boot to system, it got stuck in a bootloop. I had to flash to stock again.
Now no matter what I try to fastboot, I get "FAILED (Remote: command not allowed". Flashtool seems to be able to re-unlock the bootloader, but it makes no difference.
If I try to unlock it through Sony, it gives the same error (so fastboot doesn't work _at all_).
Still boots to system fine.
Any help or maybe a solution even..?
Click to expand...
Click to collapse
So it seems like it boots to fastboot fine, even Command Prompt shows it listed as a fastboot device, but no command goes through.
[NUT] said:
Thanks for testing @Hundsbuah and @jelbo.
I'll have a new guide to follow on the same TWRP image later, let's see if I can get it to work properly with a little wiggling, trying to proof-of-concept here... and that isn't easy without the device at hand
---------- Post added at 10:36 AM ---------- Previous post was at 10:33 AM ----------
Ok, so your bootloader is 'unlocked' but fastboot still refuses to flash anything.
That's partially a good thing:
Can you boot to fastboot and then execute run 'fastboot oem unlock' on your pc/mac.
What does fastboot say about that?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
:crying:
IlariJ said:
:crying:
Click to expand...
Click to collapse
Can you try:
Code:
fastboot command list
if that says "command not allowed" as well, then your bootloader is probably relocked by means of flashmode.
Try to unlock your device again using @Androxyde's flashtool. After trying that, please attach the log from flashtool.
---------- Post added at 11:38 AM ---------- Previous post was at 11:24 AM ----------
jelbo said:
Code:
C:\Windows\system32>adb shell
~ # ←[6nbusybox lsof | grep touch
603 /system/vendor/bin/touch_fusion /dev/kmsg
603 /system/vendor/bin/touch_fusion socket:[1879]
603 /system/vendor/bin/touch_fusion /vendor/firmware/max11945.bin
~ # ←[6nkill -9 603
~ # ←[6numount /system
~ # ←[6n/vendor/bin/touch_fusion
/sbin/sh: /vendor/bin/touch_fusion: Permission denied
~ # ←[6nbusybox lsof | grep touch
~ # ←[6n/vendor/bin/touch_fusion /vendor/firmware/max11945.bin
/sbin/sh: /vendor/bin/touch_fusion: Permission denied
~ # ←[6n
Click to expand...
Click to collapse
Oh crap... should have known
I'm going to modify my step-guide...
[edit]
now updated.
[NUT] said:
Can you try:
Code:
fastboot command list
if that says "command not allowed" as well, then your bootloader is probably relocked by means of flashmode.
Try to unlock your device again using @Androxyde's flashtool. After trying that, please attach the log from flashtool.
Click to expand...
Click to collapse
Lists the commands as supposed to(?).
Should I try to unlock anyway?
Ok, so i both tried to unlock it thru adb and with the mi unlock tool. The problem is that adb doesn't find the device, tho i installed the drivers and even so i can't see anything related to xiaomi driver or qualcomm driver in device manager, only kedacom usb device, and mi unlock tool says Can't verify phone ; not connected to Mi Phone ( i went to mi cloud and logged into the account but it was in vain ). I really need help cuz i don't have any ideas left to recover at least the data on the phone. I also tried using another pc and it didn't work either...
And the thing is that i can hear the plug in sound when i plug in the usb to the pc and phone but, as i said, nothing shows up in device driver neither in adb devices command.
I also tried with my flash tool and it doesn't detect anything, my god, the phone is dead right now -.-
Did you turn on usb debugging?
AgentBuBu said:
Ok, so i both tried to unlock it thru adb and with the mi unlock tool. The problem is that adb doesn't find the device, tho i installed the drivers and even so i can't see anything related to xiaomi driver or qualcomm driver in device manager, only kedacom usb device, and mi unlock tool says Can't verify phone ; not connected to Mi Phone ( i went to mi cloud and logged into the account but it was in vain ). I really need help cuz i don't have any ideas left to recover at least the data on the phone. I also tried using another pc and it didn't work either...
And the thing is that i can hear the plug in sound when i plug in the usb to the pc and phone but, as i said, nothing shows up in device driver neither in adb devices command.
I also tried with my flash tool and it doesn't detect anything, my god, the phone is dead right now -.-
Click to expand...
Click to collapse
You must use developer rom to unlock bootloader
Hi, I'm having same headache... Have the Kate phone, installed Miflash, mipcuite, adb fastboot drivers.
adb devices returns a blank.
Other phones (sony, s5, note 4) show up no problem. In device manager (win 7 x64), shows up as Android ADB Interface.
(usb debugging is enabled).
with hardware id USB\VID_2717&PID_FF48&REV_0310&MI_01
In fastboot mode, shows up as Android Bootloader Interface and returns device id ok with fastboot devices.
Miflash detects it too.
should device manager also show Xiaomi Composite MDB Interface ?
After turning on USB debugging and connecting to the PC, did you authorize that PC at the pop-up dialog on the phone that shows up ?
EDIT: I mean that ( and should check "Always allow from this computer"):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm on Global beta 10.13 ROM, with USB Debugging on.
I keep getting the " MiPhone not connected/ unable to verfiy device" message while attempting ofifcial MiFlashUnlock procedure.
username mobile number
dandrake47 said:
I'm on Global beta 10.13 ROM, with USB Debugging on.
I keep getting the " MiPhone not connected/ unable to verfiy device" message while attempting ofifcial MiFlashUnlock procedure.
Click to expand...
Click to collapse
try logging in on miunlock tool and micloud with mobile no (as username)only. If it fails try tommorow. repetition can do no good.
I unlocked on stable rom 3 days ago on my first attempt of the day.
my last attempt was weeks ago (primarily because i thought it was a lost cause)
thread http://en.miui.com/thread-280561-1-1.html
reddevils4017 said:
try logging in on miunlock tool and micloud with mobile no (as username)only. If it fails try tommorow. repetition can do no good.
I unlocked on stable rom 3 days ago on my first attempt of the day.
my last attempt was weeks ago (primarily because i thought it was a lost cause)
thread http://en.miui.com/thread-280561-1-1.html
Click to expand...
Click to collapse
I tried that yesterday, waited til today, still no luck.
I did a clean wipe, flashbooting the rom over my data to see if it works (and to see if the battery drain issue with the latest update could be fixed) but no luck there either.
reddevils4017 said:
try logging in on miunlock tool and micloud with mobile no (as username)only. If it fails try tommorow. repetition can do no good.
I unlocked on stable rom 3 days ago on my first attempt of the day.
my last attempt was weeks ago (primarily because i thought it was a lost cause)
thread http://en.miui.com/thread-280561-1-1.html
Click to expand...
Click to collapse
Did you unlock the bootloader on stable? If that works I'll give it a try again.
Any idea which version of stayble you unlocked the bootloader on? Are you on Miu 7 or 8?
AwakenJornie said:
Did you unlock the bootloader on stable? If that works I'll give it a try again.
Any idea which version of stayble you unlocked the bootloader on? Are you on Miu 7 or 8?
Click to expand...
Click to collapse
stable global 8*0*5*0 use the link
---------- Post added at 06:11 PM ---------- Previous post was at 05:48 PM ----------
dandrake47 said:
I tried that yesterday, waited til today, still no luck.
I did a clean wipe, flashbooting the rom over my data to see if it works (and to see if the battery drain issue with the latest update could be fixed) but no luck there either.
Click to expand...
Click to collapse
fastboot ing developer rom right. i had a week gap b/w my attempts
oem unlocking is enable isnt it, under developer options
reddevils4017 said:
stable global 8*0*5*0 use the link
---------- Post added at 06:11 PM ---------- Previous post was at 05:48 PM ----------
fastboot ing developer rom right. i had a week gap b/w my attempts
oem unlocking is enable isnt it, under developer options
Click to expand...
Click to collapse
Global beta 6.10.13, OEM unlocking enabled. Still no luck. It keeps saying Could not Verify MiPhone at 50%
I need the sctok rom for my zte prestige N9132, please help with this problem.
Rom stock Zte prestige n9132
Hi, Did you get the stock rom of this device? if you did it please give me the information from where you download it, I also having this bootloop problem, Thank you:laugh:
I Need Rom Stock ZTE PRESTIGE N9132 BOOST MOBILE Please.. :crying:
I Need Rom Stock, My ZTE PRESTIGE N9132 Boost Mobile is Bricked, please give me the information from where you download :crying:
Feb. 23, 2017......Please Help
Please help, i have been everywhere on the net and tried every possible method presented. adb, side load, factory reset, wipe/cache. nothing works. rooted my phone, later unrooted because i was gonna take it to be fixed because softkeys stopped workin, but downloaded button savior instead. then eventually wanted mt phone root again. forgot to adb "reboot disemmcwp" first. long story short, bricked phone, stuck at zte logo. i can enter the recovery mode. but it will not allow me to update from sd card for some reason. my usb debugging is not turned on. and most importantly I cannot for the life of me find stock rom or any other rom for this damn phone. as mentioned, i already did factory reset and wiped my data but it did not solve issue. i read in another forum that disabling certain apps could cause a soft brick after doing a factory reset, i did have some apps disabled. so dont know if that is the cause. I know how to flash firmware, roms, and recoveries. But i cannot find a custom rom, or a custom recovery for the ZTE Prestige N9132......so can someone please give me a copy of the stock firmware, or kindly direct me as to where i can download it???? I have scoured the internet for literally 4 days now and cannot find any firmware for this model phone at all......PLEASE HELP!!
6/1/2017 Phone Softbricked
my phone is rooted but last night after it died on me it didn't want to charge it kept turning on and off so this morning I did a hard reset also I charged the physical battery and well after the hard reset it showed
missing bitmap stage_empy
(code-7)
missing bitmap stage_fill
(code-7)
It took a charge and would take me to the setup and then stop at Update Phone and wont go no further.
I already tried live chat with zte and all they want is to pay to get phone repaired
someone help we need the stock rom and I would appreciate it. Thanks
Had mine rooted too and working perfectly, but was trying to replace stock dailer with a custom one. I meant to uninstall the stupid Smart Contacts bloatware and freeze the dailer to see if that caused any problems. But instead I did that backwards by mistake, but I had made backups ... But for some reason couldn't get the backup to reinstall correctly. Titanium was saying the dailer was reinstalled but app crashed at startup. after several attempts I gave up and tried resetting phone to see if that my fix it since it was a default app. Well now I can't get past setup mode. Gets stuck in a loop trying to verify my google account. I also recall after I messed with dailer I couldn't get google to sync contacts, which is why I was so concerned about putting it back. Anyways no stock firmware to be found on net, guess I'm SOL. I think we sould make a post for how to root this phone, b ecause I was a process. And when noobs come looking to see we ask them to get that stack firmware for us before that root. I never did find an easy guide on here just had to search around till I found that piece of adb code that unlocked our bootloader and allowed us to root.
https://androidforums.com/threads/z...ax-and-other-zte-phones.1040331/#post-7317521
Code:
adb reboot disemmcwp
If we can get them to enter the adb code and then copy firmware with adb, would that work? Haven't fooled around with adb to much so I really don't know.
Edit: Just to clarify, I say we should make a new post explaining how to root this phone because the whole time I was searching how to root my prestige never once did this thread come up. If it did, I probably had been able to help those before me and those after me, but to late now... Now I'm in the same boat. Reminds me of the broken soda machine that people keep putting money in all day instead of some one taking time to put a note up warning others to not lose their money too. I'm not that person I now want to help stop other people from making the sames mistakes over and over that seems to be a pattern here.
I found really the only way to root the prestige is with 360 root, not sure if it's actually rooted but I can do everything a rooted phone can but it's only temporary, I have to re root it every time I turn it off or on. 360 is in Japanese but if you download an translation app such as Microsoft translate ( that's better than Google translate in my opinion ) you can pretty easily get your phone rooted. I've used king root and had it rooted for maybe 2 hours then it rebooted by itself and lost it but yeah 360 root in my opinion is the easiest way to root it without a computer.
I found and download firemware on easy-firmware.com/home/browse/category/id/27213/ but phone not seen in fastboot mode, update from sd card not work too. if volume + - and power on phone seen like zte handset diagnostic interface. Please help, how restore this phone?
Here is a stock rom 333770B2622N9132V1.0.0B12
mega.nz/#!avIDVZ5R!8PVq1KloLCyUiwd4kQsS5SrG4XJU0bdZv4F0Wa2KvVk that i found and uploaded there. The phone is set to recovery <3e> N9132V1.0.0B013, but after set this firmware in update from sd card, i get an error:
E: footer is wrong
E: signature verification failed
Fastboot not working, phone is not determined.
Help, how unbrick this device?
---------- Post added at 09:23 AM ---------- Previous post was at 09:20 AM ----------
mega.nz/#!avIDVZ5R!8PVq1KloLCyUiwd4kQsS5SrG4XJU0bdZv4F0Wa2KvVk
zte n9132 prestige brick
Am experiencing same thing as you are, i download my n9132 rom from easy-firmware.com, i just cant update it through recovery,i think probably what d cause, is d build number in d recovery
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
is not desame as dat of d download file
.
think if i can get a file dat match d bulid number in recovery, it will flash successfully
any solution to unbricking dis device, help guys @allexa1123
---------- Post added at 11:45 AM ---------- Previous post was at 11:42 AM ----------
Am experiencing same thing as you are, i download my n9132 rom from easy-firmware.com, i just cant update it through recovery,i think probably what d cause, is d build number in d recovery
is not desame as dat of d download file
.
think if i can get a file dat match d bulid number in recovery, it will flash successfully
any solution to unbricking dis device, help guys @allexa1123
I think not, because you have N9132V1.0.0B09 but in the downloaded file higher N9132V1.0.0B12 Therefore, it should be updated without replacement, most likely the firmware is broken. Unfortunately I can't restore this phone either. I think you can restore from ZTE Handset Diagnostic Interface(DFU), but how, somebody knows?
do u any any testpoint for dis device @Alexa1123
---------- Post added at 03:03 PM ---------- Previous post was at 02:50 PM ----------
i can actually flash it with NCK dongle or UMT QCFIRE
but it requires the device to be in Edl mode, and i dont have EDL Cable
if i can find any pinout or test point for d device
i will be able to point it in EDL Mode and flash it..
Do have any idea?
---------- Post added at 03:04 PM ---------- Previous post was at 03:03 PM ----------
i can actually flash it with NCK dongle or UMT QCFIRE
but it requires the device to be in Edl mode, and i dont have EDL Cable
if i can find any pinout or test point for d device
i will be able to point it in EDL Mode and flash it..
Do have any idea?
Am still waiting for solution
Sent from my iPhone using Tapatalk
there is no solution in the internet anywhere, phones probably will remain bricks with us) i try to flash qfill with different prog_emmc_firehose_8909 , but have an error
Sahara Version:0
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
в QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
в QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
what do you think, is d problem,
And nobody has even provided us with any solution for [email protected]
---------- Post added at 01:30 PM ---------- Previous post was at 01:28 PM ----------
If there is any way, we can boot the device to EDL Mode
unfortunately, I have not found any solution to this issue either. appealed in support of zte, but they did not give a link to the stock firmware. I'll try again through qfill
ok. please keep me posted
Any solution friend
Sent from my iPhone using Tapatalk
I'm in the same boat. Searched the whole web and just nothing, permanent brick?
Hi everyone!
It was yesterday, when I plugged a 3.5 audio jack from a speaker to my Xiaomi Redmi Note 4x (Mido), the LED light flash red, and the phone turned off.I tried to turn it on, and all I got is bootloop (Mi logo with Unlocked >> Mi logo with Android, again and again)
I did a full backup in TWRP, and flashed a new rom, AND... the bootloop continue...
So I did some researches, and found a solution:
After flash a new rom, make a backup of that rom using TWRP > go to Wipe > Wipe Dalvik/Cache and wipe Cache > restore the backup and reboot.
I passed the bootloop, the MIUI 9 logo show up, setup somethings like language, accept Terms and Conditions, and... wait, there's no wifi, no signal, and definitely can not sign in to Mi Account, can not do anything, just sit there and staring at the login screen...
Then I think about the full backup up there ^
Restored, no bootloop, no Mi Account, just stuck at lockscreen, its said wrong password > back to TWRP > Advance > File Manager > /data/system > delete gatekeeper.key (2 files), locksetting (3 files), reboot and I got in to the screen.
So the problems are, there is no Wifi, no MAC address, unknown baseband, no signal.
MEID, IMEI still there, TWRP, fastboot still working.
Can someone help me about this case please!
Thank you so much!
P/s: Sorry about my English, my bad presentation ^^
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Did you tried to flash full dev firmware with Mitools? That was useful for my when I lost my EFS folder.... But first, format data and system with TWRP.
ramping said:
Did you tried to flash full dev firmware with Mitools? That was useful for my when I lost my EFS folder.... But first, format data and system with TWRP.
Click to expand...
Click to collapse
Do you mean XiaoMiTool?
If XiaoMiTool, I tried once, and fall to bootloop
tunglam24111993 said:
Hi everyone!
It was yesterday, when I plugged a 3.5 audio jack from a speaker to my Xiaomi Redmi Note 4x (Mido), the LED light flash red, and the phone turned off.I tried to turn it on, and all I got is bootloop (Mi logo with Unlocked >> Mi logo with Android, again and again)
I did a full backup in TWRP, and flashed a new rom, AND... the bootloop continue...
So I did some researches, and found a solution:
After flash a new rom, make a backup of that rom using TWRP > go to Wipe > Wipe Dalvik/Cache and wipe Cache > restore the backup and reboot.
I passed the bootloop, the MIUI 9 logo show up, setup somethings like language, accept Terms and Conditions, and... wait, there's no wifi, no signal, and definitely can not sign in to Mi Account, can not do anything, just sit there and staring at the login screen...
Then I think about the full backup up there ^
Restored, no bootloop, no Mi Account, just stuck at lockscreen, its said wrong password > back to TWRP > Advance > File Manager > /data/system > delete gatekeeper.key (2 files), locksetting (3 files), reboot and I got in to the screen.
So the problems are, there is no Wifi, no MAC address, unknown baseband, no signal.
MEID, IMEI still there, TWRP, fastboot still working.
Can someone help me about this case please!
Thank you so much!
P/s: Sorry about my English, my bad presentation ^^
Click to expand...
Click to collapse
seems like a firmware issue, i would suggest u to format data and reinstall miui
Theres a thread on the dev subforum with firmware extracted from miui full rom. Flash that via twrp.
Maybe is firmware.
Look at this.
MyNameIsRage said:
seems like a firmware issue, i would suggest u to format data and reinstall miui
Click to expand...
Click to collapse
coldplug said:
Theres a thread on the dev subforum with firmware extracted from miui full rom. Flash that via twrp.
Click to expand...
Click to collapse
jqm_ said:
Maybe is firmware.
Look at this.
Click to expand...
Click to collapse
I've tried flash a few roms for a dozen times, the result return the same.
But I will try these after work.
Thank you guys so much! :fingers-crossed::fingers-crossed::fingers-crossed:
download the modem files for mido. flash the zip. that will solve this issue. i had the same problem. flashing the modem files solved it.
MyNameIsRage said:
seems like a firmware issue, i would suggest u to format data and reinstall miui
Click to expand...
Click to collapse
coldplug said:
Theres a thread on the dev subforum with firmware extracted from miui full rom. Flash that via twrp.
Click to expand...
Click to collapse
jqm_ said:
Maybe is firmware.
Look at this.
Click to expand...
Click to collapse
My lastest backup was from a global MIUI rom flashed via XiaoMiTool.
"mido_global_images_8.1.18_20180118.0000.00_7.0_global_c557dab2eb"
(this is what I got in XiaoMiTool/rom folder in my PC).
At that thread's step 4, after flash those things, when I reboot it's show "No OS Installed, continue?"
Tried several times, same result
AND: The backup I had after I get the bootloop, not a backup when my phone still working.
i have same issue 2 weeks ago
the solution is to restore a file qcn and xqcn of the same model of your device (the exact same model)
you can restore this files by a program called QPST and you have to install qualcom driver before use of program
to use program you have to put your device in diagnostic mode enable USB debug in developer mode then use this code *#*#717717#*#* to enter diagnostic mode ( no need for root to do this )
after this your device will work but you have to restore your serial number, IMEI, wifi mac, bluetooth mac use the qualcom special tool to do this.
if you don't have the mac of wifi and bluetooth keep the one given to you by the qcn file you restored as no chance to be on same network with the same device .
NB. you can try to get your serial, IMEI, mac adresses use qualcom special tool before you start anything, so you can restore them later, you must be in diagnostic mode also to use qualcom special tool.
dr.moh1976 said:
i have same issue 2 weeks ago
the solution is to restore a file qcn and xqcn of the same model of your device (the exact same model)
you can restore this files by a program called QPST and you have to install qualcom driver before use of program
to use program you have to put your device in diagnostic mode enable USB debug in developer mode then use this code *#*#717717#*#* to enter diagnostic mode ( no need for root to do this )
after this your device will work but you have to restore your serial number, IMEI, wifi mac, bluetooth mac use the qualcom special tool to do this.
if you don't have the mac of wifi and bluetooth keep the one given to you by the qcn file you restored as no chance to be on same network with the same device .
NB. you can try to get your serial, IMEI, mac adresses use qualcom special tool before you start anything, so you can restore them later, you must be in diagnostic mode also to use qualcom special tool.
Click to expand...
Click to collapse
Tried this method yesterday, and when I try to restore, there's always an error, like "this qcn is not for my device" something, even I force it to restore, there're still an error. (I already edit the QCN file to my IMEI)
But as I said, my IMEI still there, so I stop trying that.
Now I'm stuck at bootloop, AGAIN...
tunglam24111993 said:
Tried this method yesterday, and when I try to restore, there's always an error, like "this qcn is not for my device" something, even I force it to restore, there're still an error. (I already edit the QCN file to my IMEI)
But as I said, my IMEI still there, so I stop trying that.
Now I'm stuck at bootloop, AGAIN...
Click to expand...
Click to collapse
Have u tried flashing latest firmware through twrp and then flash rom?
akisg said:
Have u tried flashing latest firmware through twrp and then flash rom?
Click to expand...
Click to collapse
You mean first format, wipe > install firmware > install rom?
akisg said:
Have u tried flashing latest firmware through twrp and then flash rom?
Click to expand...
Click to collapse
You mean:
Format dada/Wipe all > install firmware.zip > install rom.zip?
Let me try!
Do a full wipe and install the global dev ROM using TWRP. I've had that issue and it was solved using that process. Just wipe system, data, caches then install the global dev ROM using TWRP. Backups that have the firmware and bootloader partition included won't work.
tunglam24111993 said:
Tried this method yesterday, and when I try to restore, there's always an error, like "this qcn is not for my device" something, even I force it to restore, there're still an error. (I already edit the QCN file to my IMEI)
But as I said, my IMEI still there, so I stop trying that.
Now I'm stuck at bootloop, AGAIN...
Click to expand...
Click to collapse
ok my frist prolem also was bootloop
i tried every thing for 1 month even opened my device and connected the test points to reflash room as hardbricked device.
and at once every thing goes right after many failed trials now fully working device.
my advice is to read every tetourial carefully and try to read it from many sources always some small parts are missing like the correct drivers , disable windows signature enforcement, run as administrator , types of port and COM seen in device manager.
i am sure your device will work cause i have the same and no one helped in maitenance and company tell they will replace the chipset.
already i reached hard brick once in my trials there was no fastboot nor EDL.
don't stop.
---------- Post added at 04:38 PM ---------- Previous post was at 04:33 PM ----------
"this qcn is not for my device"
i got that error too when i used the one provided from internet
then i tried again with qcn i take from a friend phone we buy same models at same time
and it worked fine and no error
this is why i told you to get qcn from the same exact model
Now I'm stuck at bootloop, AGAIN... [/QUOTE]
It's hardware problem.
There's one guy get the same issues with me, he take his phone to a repair service, they replace the mainboard.
I think because of the high power (idk how to say) of the speaker, it get my device shock?
However, I send my phone to a repair service too, and still waiting for their call.
Thank you guys for your support, I really appreciated!
Same happened with me exact same with speaker
tunglam24111993 said:
It's hardware problem.
There's one guy get the same issues with me, he take his phone to a repair service, they replace the mainboard.
I think because of the high power (idk how to say) of the speaker, it get my device shock?
However, I send my phone to a repair service too, and still waiting for their call.
Thank you guys for your support, I really appreciated!
Click to expand...
Click to collapse
Same happened with me exact same with speaker
tunglam24111993 said:
It's hardware problem.
There's one guy get the same issues with me, he take his phone to a repair service, they replace the mainboard.
I think because of the high power (idk how to say) of the speaker, it get my device shock?
However, I send my phone to a repair service too, and still waiting for their call.
Thank you guys for your support, I really appreciated!
Click to expand...
Click to collapse
Could you solve the problem?
Hi All,
Last week, my phone suddenly dead when I woke up in the morning. It stuck at Mi logo and only can access to Fastboot mode.
I have searched many threads and none of them helps.
I tried to use Mi flash but it said "error FAILED (remote: Partition flashing is not allowed)", I knew this is related the bootloader issue.
Then, I tried to unlock the bootloader but Mi Unlock said "couldn't unlock please add your account in miui" settings" after verify the phone.
The problem is I cannot turn on the device properly, how can i access the settings in the phone.
I don't mind to wipe all data but want to get the phone works as a spare device for me.
Any help would be much appreciated. Thanks in advance.:highfive:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Routemaster said:
Hi All,
Last week, my phone suddenly dead when I woke up in the morning. It stuck at Mi logo and only can access to Fastboot mode.
I have searched many threads and none of them helps.
I tried to use Mi flash but it said "error FAILED (remote: Partition flashing is not allowed)", I knew this is related the bootloader issue.
Then, I tried to unlock the bootloader but Mi Unlock said "couldn't unlock please add your account in miui" settings" after verify the phone.
The problem is I cannot turn on the device properly, how can i access the settings in the phone.
I don't mind to wipe all data but want to get the phone works as a spare device for me.
Any help would be much appreciated. Thanks in advance.:highfive:
Click to expand...
Click to collapse
EDL mode is the only way out of your trouble.
were you on MIUI rom? then try loading MIUI recovery and reset everything.
Geekn0ob said:
were you on MIUI rom? then try loading MIUI recovery and reset everything.
Click to expand...
Click to collapse
Original miui rom and cannot reach to recovery..no response when I tried to get in.
drnightshadow said:
EDL mode is the only way out of your trouble.
Click to expand...
Click to collapse
I used the EDL mode and flash successfully, but it still stuck on the Mi logo when I reboot the device..ah,....
Routemaster said:
Original miui rom and cannot reach to recovery..no response when I tried to get in.
Click to expand...
Click to collapse
If you are in original MIUI rom and if your bootloader is locked there is no reason your rom would be broken like the way you are describing. however even your EDL mode flashing didn't work so I think there might be hardware problem in your device...
Routemaster said:
I used the EDL mode and flash successfully, but it still stuck on the Mi logo when I reboot the device..ah,....
Click to expand...
Click to collapse
U choice the option clean all or save user data down right? When u save user data, then this the problem
Sent from my Mi Note 10 using XDA Labs
joke19 said:
U choice the option clean all or save user data down right? When u save user data, then this the problem
Sent from my Mi Note 10 using XDA Labs
Click to expand...
Click to collapse
clean all
Got exactly the same problem.
same problem stuck in mi, flash with test point, success and still stuck
please help, i have no money to buy new phone
thank you
flash with beta because with latest always error
use latest rom
thank you
drnightshadow said:
EDL mode is the only way out of your trouble.
Click to expand...
Click to collapse
if u don't mind can u plz describe the process
shops seem to be able to flash on a locked bootloader like this
but when we try it we can't what seems to be the problem?
BabaLiong said:
View attachment 5166353
same problem stuck in mi, flash with test point, success and still stuck
please help, i have no money to buy new phone
thank you
flash with beta because with latest always error
use latest rom
thank you
Click to expand...
Click to collapse
hey what was the solution i m in same stage as u were
amrittech said:
hey what was the solution i m in same stage as u were
Click to expand...
Click to collapse
nothing the phone die... imho emmc need to replace.. but if you replace the phone wont live along will die soon.. as far i read
Hi, Same happened with my redmi note 5. It stuck at mi logo screen and I can only go into the fastboot mode. The main issue is the device is locked and I don't have any mi account on this device. When I tried to flash it with this image whyred_global_images_V12.0.2.0.PEIMIXM_20201224.0000.00_9.0_global_561698251e.tgz, the MiFlashTool gives error that device is locked. Please help
drnightshadow said:
EDL mode is the only way out of your trouble.
Click to expand...
Click to collapse
When I try to access EDL mode every time, my PC says.
The last USB device you connected to this computer malfunctioned. and windows does not recognize it.
Ank0001 said:
When I try to access EDL mode every time, my PC says.
The last USB device you connected to this computer malfunctioned. and windows does not recognize it.
Click to expand...
Click to collapse
Try on another PC.. USB on your PC has trouble with drivers or fix the PC (guess windows, try clean reinstall)