Hello everyone.
I'm new in the forum and I'm looking for help.
Habitually I try to solve my problems by myself but this time I need your help.
I recently acquired a pixel 3. And everything works fine until I had to flash the factory image.
I find the factory image file on google dev website and I follow the instructions.
I also tried different tutos but I always have the same issues.
My pixel 3 restart but I can't turn on WiFi.
My Bluetooth is ok
Finally, it feels like the pixel is more slowly since I flash the factory image. (Setting app crash half of the time).
Is anyone had the same issues or have a solutions ?
Thanks by advance.
totib38 said:
Hello everyone.
I'm new in the forum and I'm looking for help.
Habitually I try to solve my problems by myself but this time I need your help.
I recently acquired a pixel 3. And everything works fine until I had to flash the factory image.
I find the factory image file on google dev website and I follow the instructions.
I also tried different tutos but I always have the same issues.
My pixel 3 restart but I can't turn on WiFi.
My Bluetooth is ok
Finally, it feels like the pixel is more slowly since I flash the factory image. (Setting app crash half of the time).
Is anyone had the same issues or have a solutions ?
Thanks by advance.
Click to expand...
Click to collapse
Make sure you have the latest sdk platform tools, r28.
Then download the factory image again, it might have been corrupted. Use 7zip to extract the zip file.
Flash the factory image again using the flash-all batch file. Note, this will wipe your device.
If that doesn't work then you might have a hardware issue.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Make sure you have the latest sdk platform tools, r28.
Then download the factory image again, it might have been corrupted. Use 7zip to extract the zip file.
Flash the factory image again using the flash-all batch file. Note, this will wipe your device.
If that doesn't work then you might have a hardware issue.
Click to expand...
Click to collapse
Thanks for your answer.
I will retry tonight at home.
One more detail : so I have to modified flash-all batch file ?
In some discussion I saw some people delete -w of the script.
I will inform if the process is ok
totib38 said:
Thanks for your answer.
I will retry tonight at home.
One more detail : so I have to modified flash-all batch file ?
In some discussion I saw some people delete -w of the script.
I will inform if the process is ok
Click to expand...
Click to collapse
If you delete the -w it will not wipe your device. You can try that, but if problem still is there then include the -w. Wiping your device is a better trouble shooting solution but you will have to setup your device like it was new. It's up to you.
Sent from my [device_name] using XDA-Developers Legacy app
Thanks for your support.
I just tried several flash factory image but the result is always the same.
I can't turn on wifi setting ....
Everything else seems to work.
I'm really disappointed and I don't know what to do.
It seems there is a issue with vendor.img
After my first boot, I download Es explorer and I navigate in :
'System>vendor>ECT>wifi' and it seems files are missing compare to my others devices.
Is there a way to modify the field with root permission?
Maybe you need to unlock the critical partition before flashing?
gm007 said:
Maybe you need to unlock the critical partition before flashing?
Click to expand...
Click to collapse
Hello gm007
How can I unlock the critical partition before flashing ?
Thanks by advance ?
totib38 said:
Hello gm007
How can I unlock the critical partition before flashing ?
Thanks by advance ?
Click to expand...
Click to collapse
fastboot flashing unlock_critical
Not sure if it's needed.
this will wipe ur phone same as unlocking bootloader.
gm007 said:
fastboot flashing unlock_critical
Not sure if it's needed.
this will wipe ur phone same as unlocking bootloader.
Click to expand...
Click to collapse
It's failed...
It's indicate 'Invalid argument unlock_critical'
totib38 said:
Thanks for your support.
I just tried several flash factory image but the result is always the same.
I can't turn on wifi setting ....
Everything else seems to work.
I'm really disappointed and I don't know what to do.
It seems there is a issue with vendor.img
After my first boot, I download Es explorer and I navigate in :
'System>vendor>ECT>wifi' and it seems files are missing compare to my others devices.
Is there a way to modify the field with root permission?
Click to expand...
Click to collapse
I don't know what you're seeing in the etc folder but this is what I have in the pixel 3,
jd1639 said:
I don't know what you're seeing in the etc folder but this is what I have in the pixel 3,
Click to expand...
Click to collapse
Ah .....
Ok so the vendor.img should be ok.
I'm completely lost .
Everything works except that. And the phone has just a week so I don't think it's a hardware issue.
If I don't find the solution i will keep this device in my desk ?
totib38 said:
Ah .....
Ok so the vendor.img should be ok.
I'm completely lost .
Everything works except that. And the phone has just a week so I don't think it's a hardware issue.
If I don't find the solution i will keep this device in my desk [emoji25]
Click to expand...
Click to collapse
Did the wifi work when you first got the phone? When you flashed the factory image did you wipe the device or use the flash all with the -w removed? If you wiped the device I'm guessing it is a hardware issue.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Did the wifi work when you first got the phone? When you flashed the factory image did you wipe the device or use the flash all with the -w removed? If you wiped the device I'm guessing it is a hardware issue.
Click to expand...
Click to collapse
Yes the wifi worked at the first boot.
I'm guessing I have wipe the device and that's the reason wifi there is a problem.
Is there any way to recover wifi drivers or anything else ?
What are my possibilities ?
Go on a sav and change wifi hardware ?
totib38 said:
Yes the wifi worked at the first boot.
I'm guessing I have wipe the device and that's the reason wifi there is a problem.
Is there any way to recover wifi drivers or anything else ?
What are my possibilities ?
Go on a sav and change wifi hardware ?
Click to expand...
Click to collapse
I don't know how flahing the factory image would cause the problem. But a couple of things to check. First, make sure you're using the latest sdk platform tools (fastboot and adb), r28. Then make sure you're using the correct factory image, there one for docomo or something like that which is for the Japanese variant, and redownload it in case you got something corrupted.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
I don't know how flahing the factory image would cause the problem. But a couple of things to check. First, make sure you're using the latest sdk platform tools (fastboot and adb), r28. Then make sure you're using the correct factory image, there one for docomo or something like that which is for the Japanese variant, and redownload it in case you got something corrupted.
Click to expand...
Click to collapse
I will try again tonight but I have no hope
I use the last SDK platform tools r28.0.1
And I took the factory image from google devs website.
My Mac address is block on 02:00:00:00:00:00 to be more precise.
totib38 said:
It's failed...
It's indicate 'Invalid argument unlock_critical'
Click to expand...
Click to collapse
Seems you have outdated sdk try to remove and install the latest one as suggested above. Or try another pc.
gm007 said:
Seems you have outdated sdk try to remove and install the latest one as suggested above. Or try another pc.
Click to expand...
Click to collapse
It Is not because fastboot flashing unlock_critical is a command for pixel 3 XL ?
I got the pixel 3 device
totib38 said:
Hello everyone.
I'm new in the forum and I'm looking for help.
Habitually I try to solve my problems by myself but this time I need your help.
I recently acquired a pixel 3. And everything works fine until I had to flash the factory image.
I find the factory image file on google dev website and I follow the instructions.
I also tried different tutos but I always have the same issues.
My pixel 3 restart but I can't turn on WiFi.
My Bluetooth is ok
Finally, it feels like the pixel is more slowly since I flash the factory image. (Setting app crash half of the time).
Is anyone had the same issues or have a solutions ?
Thanks by advance.
Click to expand...
Click to collapse
I think you're platform-tools are not up to date. Download them from here:
https://developer.android.com/studio/releases/platform-tools
Put the facrory image in the same folder as the platform-tools and execute flash-all from there.
I thougt mine were up to date, but not everyting from the image got flashed.
With the latest platform tools everyting was ok.
rhino666 said:
I think you're platform-tools are not up to date. Download them from here:
https://developer.android.com/studio/releases/platform-tools
Put the facrory image in the same folder as the platform-tools and execute flash-all from there.
I thougt mine were up to date, but not everyting from the image got flashed.
With the latest platform tools everyting was ok.
Click to expand...
Click to collapse
Thanks for your help.
This is precisely the one I took yesterday and I always have the same issues
totib38 said:
Thanks for your help.
This is precisely the one I took yesterday and I always have the same issues
Click to expand...
Click to collapse
Then the only thing I can think of is for you to try another cable or computer.
Related
Hi Internet,
I was trying to flash Android M on my Nexus 9 (Wi-Fi only) today and ended up with errors such as: "system.ui has stopped working" or "android.process has stopped" because I wanted to see if I actually needed to do a factory reset for it to work properly (turns out I do). After that I've tried again and have run into some issues.
Firstly, after that Android M wasn't flashing at all and I have decided to abandon the idea of M and just go back to Lollipop. Now, I am trying to flash 5.1.1 and I keep on getting FAILED (remote: data length is too large) error when flashing my system partition. I'm flashing everything separately because if I try to do it as one image because I keep getting error: update package missing system.img errors. I have no trouble with flashing my bootloader and other partitions(boot, cache, recovery, etc), but that system partition just won't flash! I've tried 5.0, 5.1, 5.1.1 and I keep on getting these errors.
I have no idea what to do. Please help. I've spent the last 5 hours trying to figure it out and nothing has yet came up. I'm using a Mac, but I don't see how this might be causing an issue.
If you have any valuable information - please help!
I'm very comfortable with flashing and ROMs, in fact I've updated my N5 to M in 5 min, but I've never seen this error before and have no idea how to fix. All I found out is that, I think, it only happens on HTCs...
Solved: http://forum.xda-developers.com/showpost.php?p=61354553&postcount=14
I can't help you but I can tell you I had the same problem. After much frustration and many attempts to flash 5.1.1 it finally worked. I was ready to rma the device as I was sure something was wrong with it. Sorry I can't be more help as getting it to work was so random.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I can't help you but I can tell you I had the same problem. After much frustration and many attempts to flash 5.1.1 it finally worked. I was ready to rma the device as I was sure something was wrong with it. Sorry I can't be more help as getting it to work was so random.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Did you by any chance use any special image or was it a normal image from Google?
tarasmuz said:
Did you by any chance use any special image or was it a normal image from Google?
Click to expand...
Click to collapse
No,I used the factory image from Google. There were a number of times I got the image to flash, I flashed images separately, but got boot loops even after factory resets. Even got it to boot a couple of times but couldn't sign into Google. Wi-Fi would keep resetting and bring me back to the Google sign in. I'm still not convinced that there isn't something wrong with the device, bad nand? But it's working now. I haven't tried to flash anything since.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
No,I used the factory image from Google. There were a number of times I got the image to flash, I flashed images separately, but got boot loops even after factory resets. Even got it to boot a couple of times but couldn't sign into Google. Wi-Fi would keep resetting and bring me back to the Google sign in. I'm still not convinced that there isn't something wrong with the device, bad nand? But it's working now. I haven't tried to flash anything since.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I'm pretty sure that the device is fine. I flashed images before and had no problems at all.
If you haven't already, make sure nothing is running in the back ground on your pc that might be using ram. The complete system image has to load into ram and it's a pretty big file.
jd1639 said:
If you haven't already, make sure nothing is running in the back ground on your pc that might be using ram. The complete system image has to load into ram and it's a pretty big file.
Click to expand...
Click to collapse
I've just restarted and closed all the programs, but it didn't help. Going to be trying and will post if I manage to make it work. Thanks for your help!
You might have already tried this too, but re-download the factory image, check it's md5, then extract it. Might be a bad download or extraction. Then follow the long method in this, http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
jd1639 said:
You might have already tried this too, but re-download the factory image, check it's md5, then extract it. Might be a bad download or extraction. Then follow the long method in this, http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
Click to expand...
Click to collapse
Yeah, I've tried all of that. Also checked MD5 and it matches to the one on the website. The only thing I could think of is bad extraction. Will try another unarchiver.
tarasmuz said:
Yeah, I've tried all of that. Also checked MD5 and it matches to the one on the website. The only thing I could think of is bad extraction. Will try another unarchiver.
Click to expand...
Click to collapse
Just tried another unarchiver - no difference.
tarasmuz said:
Just tried another unarchiver - no difference.
Click to expand...
Click to collapse
What are you using? Use winrar or 7-zip
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
What are you using? Use winrar or 7-zip
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I'm on a Mac, so The Unarchiver and Archive Utility.
tarasmuz said:
Hi Internet,
I was trying to flash Android M on my Nexus 9 (Wi-Fi only) today and ended up with errors such as: "system.ui has stopped working" or "android.process has stopped" because I wanted to see if I actually needed to do a factory reset for it to work properly (turns out I do). After that I've tried again and have run into some issues.
Firstly, after that Android M wasn't flashing at all and I have decided to abandon the idea of M and just go back to Lollipop. Now, I am trying to flash 5.1.1 and I keep on getting FAILED (remote: data length is too large) error when flashing my system partition. I'm flashing everything separately because if I try to do it as one image because I keep getting error: update package missing system.img errors. I have no trouble with flashing my bootloader and other partitions(boot, cache, recovery, etc), but that system partition just won't flash! I've tried 5.0, 5.1, 5.1.1 and I keep on getting these errors.
I have no idea what to do. Please help. I've spent the last 5 hours trying to figure it out and nothing has yet came up. I'm using a Mac, but I don't see how this might be causing an issue.
If you have any valuable information - please help!
I'm very comfortable with flashing and ROMs, in fact I've updated my N5 to M in 5 min, but I've never seen this error before and have no idea how to fix. All I found out is that, I think, it only happens on HTCs...
Click to expand...
Click to collapse
Your Android SDK (fastboot) probably needs to be updated. Depending on how old it is, Google updated the SDK and fastboot to allow flashing these very large system.img files in early November, 2014.
cam30era said:
Your Android SDK (fastboot) probably needs to be updated. Depending on how old it is, Google updated the SDK and fastboot to allow flashing these very large system.img files in early November, 2014.
Click to expand...
Click to collapse
Yes! It worked! Turns out I was using this outdated fastboot file which wasn't allowing flashing newer system partitions. Fun fact: outdated fastboot file worked with N5, but didn't work with N9. Anyway, I updated my SDK though Android Studio and everything flashed perfectly. Many thanks to cam30era and jd1639.
tarasmuz said:
Yes! It worked! Turns out I was using this outdated fastboot file which wasn't allowing flashing newer system partitions. Fun fact: outdated fastboot file worked with N5, but didn't work with N9. Anyway, I updated my SDK though Android Studio and everything flashed perfectly. Many thanks to cam30era and jd1639.
Click to expand...
Click to collapse
I'm glad this worked out for you.
After factory resetting/reinstalling [Resurrection_Remix][Android 6.0.1, r_52][Kenzo], the "Unfortunately Setting Has Stopped" has started appearing whenever I try to access the Privacy setting to change the password/pin/pattern option. I also noticed that the Fingerprint scanner is no longer in the Privacy setting.
Under TWRP I have also tried wiping Dalvik / ART Cache, Data, Internal Storage, and Cache when reinstalling any other Custom ROMs and Gaap. The other custom ROMS I've installed are causing the Setting->Privacy option to crash also. All the searches I've made doesn't seem to fix the issue, particularly the searches in the Redmi section. Any suggestion would be helpful, thanks.
phonester said:
After factory resetting/reinstalling [Resurrection_Remix][Android 6.0.1, r_52][Kenzo], the "Unfortunately Setting Has Stopped" has started appearing whenever I try to access the Privacy setting to change the password/pin/pattern option. I also noticed that the Fingerprint scanner is no longer in the Privacy setting.
Under TWRP I have also tried wiping Dalvik / ART Cache, Data, Internal Storage, and Cache when reinstalling any other Custom ROMs and Gaap. The other custom ROMS I've installed are causing the Setting->Privacy option to crash also. All the searches I've made doesn't seem to fix the issue, particularly the searches in the Redmi section. Any suggestion would be helpful, thanks.
Click to expand...
Click to collapse
Flash radio.zip fix.and dont forget to flash gapps after flashing roms.
Sent from my Redmi Note 3 using Tapatalk
khan_pegasus said:
Flash radio.zip fix.and dont forget to flash gapps after flashing roms.
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
It worked, thanks.
link to download radio.zip?
This situation happens when you switch to an OFFICIAL Rom from an UNOFFICIAL one like Mokee or RR from Siddhesh or Santosh. This is because these ROMs lock the bootloader and cause other problems too.
Radio.zip may not always fix the problem. If you are really stuck, there is a lengthy process that is guaranteed to work.
1. Flash one of the MiUI Fastboot ROM (global or chinese stable works fine) for RN3SD with Mi Flash tool. Use Flash All in the options at the bottom.
2. If you had an officially unlocked bootloader, use the Mi Unlocker tool to unlock your bootloader. Otherwise, you need to follow the unofficial unlock guide.
3. Flash official TWRP or a variant if you now what you are doing. Refer to this thread if you are not sure which TWRP will work.
3a. Download and copy this file to internal storage - LazyFlasher. I have verified this file to work with MiUI7 and MiUI8 global.
3b Reboot the phone in fastboot mode. On your PC, copy the TWRP img file to the adb directory and open command window there. Rename it to recovery.img. Use this command
Code:
fastboot flash recovery recovery.img
3c Boot into recovery (using ADB or Vol-pwr button shortcut). DO NOT BOOT into the phone before you do this. Flash the Lazyflasher zip with TWRP. You could probably flash this using fastboot too, I just never tried it.
Dhanajay made a guide video here. The video is a little outdated, and the updated instructions are in the description and comments.
You phone is now rooted and you have TWRP. Happy flashing.
This method will soon be outdated as a graphical UI for ADB is already in progress. Others have done it before, but this one shows real promise. Check here for details.
It has been a few months now since the RN3SD launch and the time has come when unofficial ROMs are no longer the best option around. Most Official ROMs, including the ones from RR and XOSP among others work great now and are incredbilby smooth and efficient. The war for the best kernel is now starting, and custom kernels will be responsible for the next round of reasons for bricked phones. Be VERY careful when you are flashing a ROM with a custom kernel. Be prepared to do some legwork if things go wrong.
Joswin said:
link to download radio.zip?
Click to expand...
Click to collapse
http://builder.balika011.me/official-cm13/cm-13.0-RADIOS.zip
I would also recommend anyone having this issue to read this post.
talkaboom said:
http://builder.balika011.me/official-cm13/cm-13.0-RADIOS.zip
I would also recommend anyone having this issue to read this post.
Click to expand...
Click to collapse
Link isn't working...
Can you mirror it?
Joswin said:
Link isn't working...
Can you mirror it?
Click to expand...
Click to collapse
Seems to be down. Normally works. Give it some time.
But if you are moving from an unofficial ROM, flashing radios alone is unlikely to work. Radio zip fix is for undetected SIM and IMIE errors. Check your IMIE number in About Phone. If you are showing an IMIE number instead of '0', flashing radio may be pointless.
Joswin said:
Link isn't working...
Can you mirror it?
Click to expand...
Click to collapse
New Link available.
https://mega.nz/#!9hlljJKD!QmjwPqMOH...gOqWkEJ0QasGE4
talkaboom said:
New Link available.
This link needs a decryption key not provided. Why even post this?
Click to expand...
Click to collapse
virtualgates said:
This link needs a decryption key not provided. Why even post this?
Click to expand...
Click to collapse
Link is from August 8th. That **** has mirrored a hundred times by now.
Also, the problem is now tackled in a different way. If you're facing a similar issue, ask in the rom thread you are trying to flash.
If you are facing this problem now, just flash the correct CM firmware.
P.S. On XDA, please do not question why someone posted a link or method that did not work for you. Do your research. No one is obligated to solve your problems.
Flashed radio. Zip. Worked for me.
Sent from my Redmi Note 3 using Tapatalk
Hello talkaboom!
the link is not working anymore. Any chance to upload it again please? Thanks a lot!
So I am fond of flashing custom ROMs and stuff on my mido and I carry knowledge about what I'm doing. Day before yesterday I was flashing Oreo 8.1 ROMs via TWRP. Accidentally I deleted everything in "/" folder (I suppose its called root folder idk). Terminal gave output saying something like rm -rf i don't recall exactly .. i thought i didn't mess up so i went forward flashing AEX 5.1 Beta ROM. The ROM booted perfectly but only issue I got was No WiFi and data signals... I thought i messed up with firmware so i went ahead and flashed sock ROM via MI FLASH. It flashed successfully but when my device rebooted I started setting it up until it started rebooting again and again... It's not normal boot-loop... i am getting past Mi logo and even able to go through setup wizard but unable to complete it... when i start setting device up it freezes and then restarts and that's it!
what i have tried:
1) Flashing in EDL mode
2) Flashing TWRP/ RedWolf recovery and formatting data
3) Flashing Custom ROM (The issue persisits the device boots succesfully the reboots)
4) Tried flashing via QFIL but cant seem to make it work (fh_loader stops working)
Is it software issue or hardware? It must be software right? or else phone wouldnot have booted successfully
P.S: Under Device Info it shows MAC as 20:00:00:00:00:00 and WiFi wont turn on, same with Bluetooth (Mobile signals work perfectly)
I think i messed up with partitions someone PLEASE HELP!
addymishra said:
So I am fond of flashing custom ROMs and stuff on my mido and I carry knowledge about what I'm doing. Day before yesterday I was flashing Oreo 8.1 ROMs via TWRP. Accidentally I deleted everything in "/" folder (I suppose its called root folder idk). Terminal gave output saying something like rm -rf i don't recall exactly .. i thought i didn't mess up so i went forward flashing AEX 5.1 Beta ROM. The ROM booted perfectly but only issue I got was No WiFi and data signals... I thought i messed up with firmware so i went ahead and flashed sock ROM via MI FLASH. It flashed successfully but when my device rebooted I started setting it up until it started rebooting again and again... It's not normal boot-loop... i am getting past Mi logo and even able to go through setup wizard but unable to complete it... when i start setting device up it freezes and then restarts and that's it!
what i have tried:
1) Flashing in EDL mode
2) Flashing TWRP/ RedWolf recovery and formatting data
3) Flashing Custom ROM (The issue persisits the device boots succesfully the reboots)
4) Tried flashing via QFIL but cant seem to make it work (fh_loader stops working)
Is it software issue or hardware? It must be software right? or else phone wouldnot have booted successfully
P.S: Under Device Info it shows MAC as 20:00:00:00:00:00 and WiFi wont turn on, same with Bluetooth (Mobile signals work perfectly)
I think i messed up with partitions someone PLEASE HELP!
Click to expand...
Click to collapse
you actually messed up your device bad. basically the '/' directory has folders containing files which the linux os requires. there are dev scripts which perform the backend tasks, and if they all are deleted, well sorry to say, the device then is just an expensive paperweight. not sure how you are still able to boot. Basically rm -rf command deletes all the writable partitions of android. maybe the device is booting up on the support of blobs. but there are very little chances to get back normal. sorry but unable to help
MyNameIsRage said:
you actually messed up your device bad. basically the '/' directory has folders containing files which the linux os requires. there are dev scripts which perform the backend tasks, and if they all are deleted, well sorry to say, the device then is just an expensive paperweight. not sure how you are still able to boot. Basically rm -rf command deletes all the writable partitions of android. maybe the device is booting up on the support of blobs. but there are very little chances to get back normal. sorry but unable to help
Click to expand...
Click to collapse
Hey, I got it working up and fine. What actually helped was flashing the stock rom with QFIL tool. The device booted up successfully and right now I'm writing this with my mido only ? All the partitions have been recovered successfully and WiFi and Bluetooth are up and running too! The only issue is that QFIL wiped my IMEI. I'm sure there must be some way to write IMEI back. If you know you may help too ?
addymishra said:
Hey, I got it working up and fine. What actually helped was flashing the stock rom with QFIL tool. The device booted up successfully and right now I'm writing this with my mido only All the partitions have been recovered successfully and WiFi and Bluetooth are up and running too! The only issue is that QFIL wiped my IMEI. I'm sure there must be some way to write IMEI back. If you know you may help too
Click to expand...
Click to collapse
God save QFIL!
btw check this video for imei
https://www.youtube.com/watch?v=m9hq-FiDn58
MyNameIsRage said:
God save QFIL!
btw check this video for imei
https://www.youtube.com/watch?v=m9hq-FiDn58
Click to expand...
Click to collapse
No worries! Fixed it myself! Hahaha!! I'm so happy!! Thank you so much! God bless XDA!! ?????
addymishra said:
No worries! Fixed it myself! Hahaha!! I'm so happy!! Thank you so much! God bless XDA!!
Click to expand...
Click to collapse
lol, god bless our redmi note 4.
MyNameIsRage said:
lol, god bless our redmi note 4.
Click to expand...
Click to collapse
Yes!
addymishra said:
Yes!
Click to expand...
Click to collapse
Hey, I have the same problem with you. I tried to flash stock rom with QFIL tool but I get an error when downloading. I followed this guide
http://en.miui.com/thread-432217-1-1.html
I get the following error: Download Fail: FireHose Fail FHLoader Failrocess fail
any help?
Jimmy_979 said:
Hey, I have the same problem with you. I tried to flash stock rom with QFIL tool but I get an error when downloading. I followed this guide
http://en.miui.com/thread-432217-1-1.html
I get the following error: Download Fail: FireHose Fail FHLoader Failrocess fail
any help?
Click to expand...
Click to collapse
Hey, sorry for late I'm here now! Listen, I followed the same procedure as mentioned in Mi forum. I got the same error! It might say that fh_loader stopped working right? The solution was to flash stock miui rom. By stock I mean out of the box rom i.e. V8.1.10.0.MCFMIDI which you can find here: http://bigota.d.miui.com/V8.1.10.0....DI_20161228.0000.00_6.0_global_7557bfe334.tgz
Download the above linked ROM and flash it via QFIL (Run as administrator) and you should be good to go! I hope it works out! If you face any problem then keep me posted All the best!
addymishra said:
Hey, sorry for late I'm here now! Listen, I followed the same procedure as mentioned in Mi forum. I got the same error! It might say that fh_loader stopped working right? The solution was to flash stock miui rom. By stock I mean out of the box rom i.e. V8.1.10.0.MCFMIDI which you can find here: http://bigota.d.miui.com/V8.1.10.0....DI_20161228.0000.00_6.0_global_7557bfe334.tgz
Download the above linked ROM and flash it via QFIL (Run as administrator) and you should be good to go! I hope it works out! If you face any problem then keep me posted All the best!
Click to expand...
Click to collapse
Yeaaah it worked!!!!! Thank you a lot guys!!! And my imei numbers were there (I called *#06# to see). Now I have one question:
How can I install properly a custom rom without bricking my phone again?
Jimmy_979 said:
Yeaaah it worked!!!!! Thank you a lot guys!!! And my imei numbers were there (I called *#06# to see). Now I have one question:
How can I install properly a custom rom without bricking my phone again?
Click to expand...
Click to collapse
@Jimmy_979 Yessss i am so happppyyy for you alll!!! Dammmm @addymishra you should probably start a new thread describing how to fix this problem!
Jimmy_979 said:
Yeaaah it worked!!!!! Thank you a lot guys!!! And my imei numbers were there (I called *#06# to see). Now I have one question:
How can I install properly a custom rom without bricking my phone again?
Click to expand...
Click to collapse
Haha thats great congrats! Tip for custom rom installation is to follow install guide carefully and don't ever touch root partition lol! I've stopped flashing roms now... I'm on miui now permanently with bootloader locked lol
MyNameIsRage said:
@Jimmy_979 Yessss i am so happppyyy for you alll!!! Dammmm @addymishra you should probably start a new thread describing how to fix this problem!
Click to expand...
Click to collapse
Haha @MyNameIsRage I'm thinking so ???
I m stuck in this same problem
But i never tried qflash
Wellll
I buy new op5t but i still wnt back to rn4
Will tell ya guys tonight nd please help me with proper procrdure
I downloaded everything but wich file have to flash
Or any video out there?
Saved my rn4
Thank u all
Thnx alot
my phone keeps rebooting
addymishra said:
So I am fond of flashing custom ROMs and stuff on my mido and I carry knowledge about what I'm doing. Day before yesterday I was flashing Oreo 8.1 ROMs via TWRP. Accidentally I deleted everything in "/" folder (I suppose its called root folder idk). Terminal gave output saying something like rm -rf i don't recall exactly .. i thought i didn't mess up so i went forward flashing AEX 5.1 Beta ROM. The ROM booted perfectly but only issue I got was No WiFi and data signals... I thought i messed up with firmware so i went ahead and flashed sock ROM via MI FLASH. It flashed successfully but when my device rebooted I started setting it up until it started rebooting again and again... It's not normal boot-loop... i am getting past Mi logo and even able to go through setup wizard but unable to complete it... when i start setting device up it freezes and then restarts and that's it!
what i have tried:
1) Flashing in EDL mode
2) Flashing TWRP/ RedWolf recovery and formatting data
3) Flashing Custom ROM (The issue persisits the device boots succesfully the reboots)
4) Tried flashing via QFIL but cant seem to make it work (fh_loader stops working)
Is it software issue or hardware? It must be software right? or else phone wouldnot have booted successfully
P.S: Under Device Info it shows MAC as 20:00:00:00:00:00 and WiFi wont turn on, same with Bluetooth (Mobile signals work perfectly)
I think i messed up with partitions someone PLEASE HELP!
Click to expand...
Click to collapse
Pls bro am going Tru this same problem flashed through recovery flashed through fastboot but it keeps rebooting pls help me out with the exact steps u used to fix urs
addymishra said:
Hey, I got it working up and fine. What actually helped was flashing the stock rom with QFIL tool. The device booted up successfully and right now I'm writing this with my mido only All the partitions have been recovered successfully and WiFi and Bluetooth are up and running too! The only issue is that QFIL wiped my IMEI. I'm sure there must be some way to write IMEI back. If you know you may help too
Click to expand...
Click to collapse
I am in same problem on mido. Can you help me how to get in edl mode because QFIL Not detecting PORT.
Also my adb not detecting the device so i cant use adb commands.
But i can flash Stock ROM using MI Flash Tools.
Jimmy_979 said:
Yeaaah it worked!!!!! Thank you a lot guys!!! And my imei numbers were there (I called *#06# to see). Now I have one question:
How can I install properly a custom rom without bricking my phone again?
Click to expand...
Click to collapse
hey guyz i have the same problem , please help me i tried all written in the replies but faces the same problem in the QFIL.
please reply, i'm dead :"(
Hello everyone, I have recently flashed new custom ROM on my device - Realme 7 rmx 2151 and everything went as planned. I used unlocking and flashing guide new from XDA webpage... I flashed PixelPlus UI3.9 from here, XDA ... I was really loooking forward to try new things etc... and do not know where I messed up but can not turn ON Wi-Fi and BLUETOOTH. Please any advice ? Thank you in advance...
Could be a problem with the rom,try to flash evolution x to see if that works
Ok. thank you for advice, I will do that within a next two hours. lets try...
I Have just installed Evolution X And probleem still remains... I am pi**ed off where I went Wrong...anyway I appreciate your help.
RobertoSt25 said:
I Have just installed Evolution X And probleem still remains... I am pi**ed off where I went Wrong...anyway I appreciate your help.
Click to expand...
Click to collapse
Try restoring the persist partition.
RobertoSt25 said:
I Have just installed Evolution X And probleem still remains... I am pi**ed off where I went Wrong...anyway I appreciate your help.
Click to expand...
Click to collapse
Were you on a.87 before flashing the ROM?
SubwayChamp said:
Try restoring the persist partition.
Click to expand...
Click to collapse
I would if I knew how... I am newbie, but if you could help me out, I would be grateful.
OrthodoxOxygen said:
Were you on a.87 before flashing the ROM?
Click to expand...
Click to collapse
Not sure buddy, but honestly can say either 87 or 91....
RobertoSt25 said:
I would if I knew how... I am newbie, but if you could help me out, I would be grateful.
Click to expand...
Click to collapse
Unfortunately this is a very problematic device, if you didn't make a backup before... the ofp file doesn't contain one, so you need that someone else take a backup of persist partition from a good/working phone and upload the file for you, then you can flash it back using fastboot.
RobertoSt25 said:
I would if I knew how... I am newbie, but if you could help me out, I would be grateful.
Click to expand...
Click to collapse
Other people had this exact issue. It's the device firmware that you were on before flashing that is detrimental. Are you RMX2155 or RMX2151?
OrthodoxOxygen said:
Other people had this exact issue. It's the device firmware that you were on before flashing that is detrimental. Are you RMX2155 or RMX2151?
Click to expand...
Click to collapse
So I think, the best would be to purchase a new one as soon as possible , never mind, thats fine, I should have thought twice before I did something ... Its REALME RMX 2151 , but on the BACK of the phone its written model RMX 2155
SubwayChamp said:
Unfortunately this is a very problematic device, if you didn't make a backup before... the ofp file doesn't contain one, so you need that someone else take a backup of persist partition from a good/working phone and upload the file for you, then you can flash it back using fastboot.
Click to expand...
Click to collapse
Alright... I will be thinking of buying a new one probably , anyway I will give it a one more try and will do as you saying.. Taking a backup of persist has to be the exact same model RMX ? or could it be for example ONEPLUS ,completely different mobile ? Thanks.
RobertoSt25 said:
Alright... I will be thinking of buying a new one probably , anyway I will give it a one more try and will do as you saying.. Taking a backup of persist has to be the exact same model RMX ? or could it be for example ONEPLUS ,completely different mobile ? Thanks.
Click to expand...
Click to collapse
No, it must be from the same model, it is a very sensitive partition, used from other different device/model could brick your device.
I backed up one from my device while it was in bricked state, if this functionality weren't broken at this time then it would work for you, if you want to give it a try I'll upload it soon.
RobertoSt25 said:
So I think, the best would be to purchase a new one as soon as possible , never mind, thats fine, I should have thought twice before I did something ... Its REALME RMX 2151 , but on the BACK of the phone its written model RMX 2155
Click to expand...
Click to collapse
You don't need to uy a new one. You just need to reflash the correct firmware, and then reflash the ROM you're trying to use after that.
SubwayChamp said:
No, it must be from the same model, it is a very sensitive partition, used from other different device/model could brick your device.
I backed up one from my device while it was in bricked state, if this functionality weren't broken at this time then it would work for you, if you want to give it a try I'll upload it soon.
Click to expand...
Click to collapse
cheers buddy, I will give it a try for sure, but are you sure its ok to flash it from bricked device?
alright I will do that, what would you recon, how to flash it ? I mean the best and the easiest way to do that...? Thank you very much.
RobertoSt25 said:
cheers buddy, I will give it a try for sure, but are you sure its ok to flash it from bricked device?
Click to expand...
Click to collapse
If the firmware is not cased sensitive, then it shouldn't.
But to be completely sure backup first your persist partition, also you can back up the others aswell
Reboot to your custom recovery and type the next one by one:
adb shell
dd if=/dev/block//by-name/persist of=/sdcard/persist.img
After that, you'll have your persist image in the main directory of your sdcard (internal memory)
After that you can copy/transfer it directly to your PC (don't forget to keep it in a safe place, not in your device)
Or you can pull it with:
Exit first from the shell (just one time, in case you are not rooted) with:
exit
adb pull /sdcard/persist.img
This will copy (really pull/move) the file to the same directory where you ran the command.
You can flash it using fastboot.
SubwayChamp said:
If the firmware is not cased sensitive, then it shouldn't.
But to be completely sure backup first your persist partition, also you can back up the others aswell
Reboot to your custom recovery and type the next one by one:
adb shell
dd if=/dev/block//by-name/persist of=/sdcard/persist.img
After that, you'll have your persist image in the main directory of your sdcard (internal memory)
After that you can copy/transfer it directly to your PC (don't forget to keep it in a safe place, not in your device)
Or you can pull it with:
Exit first from the shell (just one time, in case you are not rooted) with:
exit
adb pull /sdcard/persist.img
This will copy (really pull/move) the file to the same directory where you ran the command.
You can flash it using fastboot.
Click to expand...
Click to collapse
lovely, you are No,1, I will do that exactly the way you described. Thank you very much for that.
I did everything exactly the way you said and still wifi and bluetooth won´t turn on my friend... Shoul I flash new custom ROM ?
RobertoSt25 said:
I did everything exactly the way you said and still wifi and bluetooth won´t turn on my friend... Shoul I flash new custom ROM ?
Click to expand...
Click to collapse
You just need to flash a.87 back onto your device. Did you need to follow an elaborate guide to unlock your phone's bootloader, or did you just submit an application via the DeepTest APK? I need to know this in order to link you the correct files to flash.
Hello, I'm fairly new here. I've tried flashing TWRP to my Android TV box, but now it's just constantly rebooting over and over again. How do i fix that? How do i access the recovery mode?
TV Box: https://www.androidtv-guide.com/pay-tv-provider/united-group-eon-ott-smart-box/
Fzloop said:
Hello, I'm fairly new here.
Click to expand...
Click to collapse
Fairly? You joined yesterday. You could hardly be fairer.
Fzloop said:
I've tried flashing TWRP to my Android TV box, but now it's just constantly rebooting over and over again.
Click to expand...
Click to collapse
The good news is that since it is bootlooping, the bootloader is probably okay.
For this model device running android 9, neither of the bootable partitions can be modified (while still running the original bootloader), even if the bootloader is unlocked, without causing a signature check failure. Since flashing some twrp version has modified the recovery partition, which is a bootable partition, the signature check is failing.
Fzloop said:
How do i fix that?
Click to expand...
Click to collapse
One way is to flash the original recovery partition back to the device using burn mode.
Fzloop said:
How do i access the recovery mode?
Click to expand...
Click to collapse
By holding the button on the device. You'll need the worldcup drivers and command line "update" burn mode tool (not the GUI burning tool).
If you have a copy of the original recovery partition, you'd just flash that with the update tool and be done.
If you don't have a copy of the original recovery partition, you can use the update tool to dump a different partition, like system, in order to learn which version of the firmware is installed on your box. Report the version here, and maybe some member will have the matching recovery partition that you can flash to your device using the update tool.
goapy said:
Fairly? You joined yesterday. You could hardly be fairer.
The good news is that since it is bootlooping, the bootloader is probably okay.
For this model device running android 9, neither of the bootable partitions can be modified (while still running the original bootloader), even if the bootloader is unlocked, without causing a signature check failure. Since flashing some twrp version has modified the recovery partition, which is a bootable partition, the signature check is failing.
One way is to flash the original recovery partition back to the device using burn mode.
By holding the button on the device. You'll need the worldcup drivers and command line "update" burn mode tool (not the GUI burning tool).
If you have a copy of the original recovery partition, you'd just flash that with the update tool and be done.
If you don't have a copy of the original recovery partition, you can use the update tool to dump a different partition, like system, in order to learn which version of the firmware is installed on your box. Report the version here, and maybe some member will have the matching recovery partition that you can flash to your device using the update tool.
Click to expand...
Click to collapse
I did join yesterday, but I've been using this forum for a while without posting.
I managed to fix the box on my own, turns out all i needed was an SD card and a ROM.
Fzloop said:
I managed to fix the box on my own, turns out all i needed was an SD card and a ROM.
Click to expand...
Click to collapse
An alternative ROM, or the original ROM?
If you installed an alternative ROM, you may have "fixed" your box, but you've also blown away your drm keys forever.
If you're happy with the result, that's all that matters.
Although you could have posted that your issue had been resolved. That would have saved me from wasting my time. I always regret replying to posts about the dv8519. This is the last one for me.
goapy said:
An alternative ROM, or the original ROM?
If you installed an alternative ROM, you may have "fixed" your box, but you've also blown away your drm keys forever.
If you're happy with the result, that's all that matters.
Although you could have posted that your issue had been resolved. That would have saved me from wasting my time. I always regret replying to posts about the dv8519. This is the last one for me.
Click to expand...
Click to collapse
Unfortunately, alternative. I'm still looking for the original.
My apologies for wasting your time. Have a great day.
Fzloop said:
Unfortunately, alternative. I'm still looking for the original.
My apologies for wasting your time. Have a great day.
Click to expand...
Click to collapse
Hi @Fzloop,
can you share the ROM?
xfenixxx said:
Hi @Fzloop,
can you share the ROM?
Click to expand...
Click to collapse
BoskoWifiBT
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Worked fine at first, but after playing with it a bit more the box just wouldn't boot, so be careful.
Fzloop said:
BoskoWifiBT
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Worked fine at first, but after playing with it a bit more the box just wouldn't boot, so be careful.
Click to expand...
Click to collapse
Thank you very much, I'll still give it a try.
Hello, I've tried flashing TWRP to my Android TV box, but now it's just constantly rebooting over and over again. How do i fix that? How do i access the recovery mode?
TV BOX https://www.androidtv-guide.com/pay-tv-provider/dhiraagu-tv-joybox/
box connected AMLOGIC usb burn tool. but error uboot/getresult/Diskinitial error