Hey guys, so I just flashed MIUI V5 from this week and it worked like a charm, but then I tried updating to the .17 update that came out today, and it seemd to flash perfectly, but then my device rebooted and now it is stuck in a recovery bootloop, always boots to recovery, tried changing recoveries, wiping cache, data and dalvik and nothing so far.
I may be able to fix by just flashing a KDZ, but then ill loose all my data, do you guy know of any other solutions :/? Thanks
Info:
Model- E977
MIUI V5 official ported rom .16 android 4.4 release
Unlocked through Mako method
Philz touch official latest.
Galileo said:
Hey guys, so I just flashed MIUI V5 from this week and it worked like a charm, but then I tried updating to the .17 update that came out today, and it seemd to flash perfectly, but then my device rebooted and now it is stuck in a recovery bootloop, always boots to recovery, tried changing recoveries, wiping cache, data and dalvik and nothing so far.
I may be able to fix by just flashing a KDZ, but then ill loose all my data, do you guy know of any other solutions :/? Thanks
Info:
Model- E977
MIUI V5 official ported rom .16 android 4.4 release
Unlocked through Mako method
Philz touch official latest.
Click to expand...
Click to collapse
Same thing happened to me, i think kdz is the only way out. I didn't get to see the files and changes on 4.8.17 zip i thought it was unsigned and may had some other problems.
Galileo said:
Hey guys, so I just flashed MIUI V5 from this week and it worked like a charm, but then I tried updating to the .17 update that came out today, and it seemd to flash perfectly, but then my device rebooted and now it is stuck in a recovery bootloop, always boots to recovery, tried changing recoveries, wiping cache, data and dalvik and nothing so far.
I may be able to fix by just flashing a KDZ, but then ill loose all my data, do you guy know of any other solutions :/? Thanks
Info:
Model- E977
MIUI V5 official ported rom .16 android 4.4 release
Unlocked through Mako method
Philz touch official latest.
Click to expand...
Click to collapse
Did you try to flash 4.8.16 or others working rom again.
artit said:
Did you try to flash 4.8.16 or others working rom again.
Click to expand...
Click to collapse
Other working roms even nandroid backup won't work.
Happened to me last saturday. The only solution i did was to flash kdz. Im now using Ariti Miui. I guess it was fixed already in Miui site but i will not flash it again it may give me a bootloop again! :good:
WTF patch (4.8.17) will delete recovery.img??? (Updater script)
{
"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"
}
arpit85 said:
WTF patch (4.8.17) will delete recovery.img??? (Updater script)
...
Click to expand...
Click to collapse
That is only recovery.img file. It isn't recovery partition. But I wander what it did with recovery.img. Maybe that is the reason why you got recovery boot loop.
artit said:
That is only recovery.img file. It isn't recovery partition. But I wander what it did with recovery.img. Maybe that is the reason why you got recovery boot loop.
Click to expand...
Click to collapse
Yup, Kdz was the only solution for me, spent the day learning how to use ADB to pull out all my files, I think i recovered the most important stuff, and picked up a little bit of adb knowledge so all good, never had a good experience with MIUI Ota`s tho, only manual flashing from now on
Galileo said:
Yup, Kdz was the only solution for me, spent the day learning how to use ADB to pull out all my files, I think i recovered the most important stuff, and picked up a little bit of adb knowledge so all good, never had a good experience with MIUI Ota`s tho, only manual flashing from now on
Click to expand...
Click to collapse
Had just now done that bootloop. stuck. wtf. Tell me two things how do i adb pull in recovery step by step please. and second a good tutorial for a first time kdz flash. please help..>?
the same happened to me and I flashed kdz to fix it. It doesn't flash correctly I saw status 7 error.
Here a good tutorial in flashing KDZ. Hope it helps.
http://forum.xda-developers.com/showthread.php?t=2625044
nayneshdev said:
Had just now done that bootloop. stuck. wtf. Tell me two things how do i adb pull in recovery step by step please. and second a good tutorial for a first time kdz flash. please help..>?
Click to expand...
Click to collapse
Alright, first, do you know what ADB is? If not watch this: https://www.youtube.com/watch?v=MVXX-YdhRU0
The command to pull stuff from the phone is: adb pull "Directory you want to pull"
For example: adb pull /sdcard/
That should pull out everything in the internal storage to the adb folder.
It is mostly about logic, so after a few times of screwing up your phone and a few hours playing with commands and such you'll get used to it.
Today we got v 8.21. I wonder if the error still exist I'm about to update now, will report soon.
Edit: still recovery boot loop. Don't even try to update. Or you'll end up kdz the whole thing.
Edit: Anyone knows how to report to developer of the rom?
Related
PLEASE Help! How to Revert back to stock - CWM;Fastboot;Odin & ToolKit don't work!
Please help! Please teach me how I can revert my phone to stock so I can start all over again.
My phone reboots itself every min or so. I tried to fix it with no luck. ((The behavior of the phone makes me feel that the phone itself is in read only mode!)) That being said, I can still transfer file to the phone through USB. Anyway, I "think" the easiest way to fix it is to revert back to stock and start over again. I have tried the following but NOTHING works
In Android - Factory reset (the phone freeze and reset when press)
Under CWM - Wipe cache/data; flashing new rom; restoring old working CWM backups (CWM will run all my request but no changes were made after reboot)
Fastboot - recovery google stock img (Fastboot will sent the data to the phone but no changes were made after reboot)
Odin3 v1.85 - Added a PDF / .tar google stock rom (Odin successfully finished the whole process (PASS!) but no changes were made after reboot)
Galaxy Nexus ToolKit v7.5 - successfully finished flashing google stock image and newer CWM (Odin successfully finished the whole process but no changes were made after reboot)
I do see an error under CWM when restoring
"E:error in /cache/recovery/last_log
(Read-only file system)
Could I somehow made all my files read only? If so, any idea how to fix it?
I am using bigxie's JRO03C Deodexed Rom for weeks. Any advise will be appreciated! Thank you!
Nexus GSM
4.1.1 - bigxie's JRO03C Deodexed ROM
CWM 5.5.0.2
Baseband UGLC1
Kernel 3.0.31
Build number JR003c
Bootloader PRIMELC03
Not sure if it will be any different but I used Wug's toolkit and had success when the galaxy nexus toolkit didn't work for me. Hope that helps.
Sent from my Galaxy Nexus using xda app-developers app
hortonj54 said:
Not sure if it will be any different but I used Wug's toolkit and had success when the galaxy nexus toolkit didn't work for me. Hope that helps.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Thanks for your advise! I just tried Wug's Toolkit v1.5.2 with no luck. It does the same things as if I use fastboot to flash the stock image myself.
1/ fastboot bootloader... the phone said OKAY
2/ reboot bootloader
3/ fastboot radio... phone said OKAY
4/ reboot bootloader
5/ flash update image...flashboot said wrong bootloader & radio version...
Again, I feel my phone right now is in read-only mode. Neither programs and user can input or change anything. However, Android itself can make changes as I can see calendar reminder pop up. Arg... I am :crying::crying::crying:
Please anyone?? I really need to use my phone..!~!
Did you try factory reset before cwm? How bout running cwm through tool kid then flash
Sent from my Galaxy Nexus using xda premium
use this link: http://forum.xda-developers.com/showthread.php?t=1626895
I followed efrant's guide and many other similar guide. The phone will talk to my computer and will prompt "fastboot status - good" after each fastboot command; however, once I boot up the phone, nothing is changed! WTF... =(
{
"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"
}
https://www.dropbox.com/s/z7gi5q8jgicijje/log.png?m
1stHTCphone said:
I followed efrant's guide and many other similar guide. The phone will talk to my computer and will prompt "fastboot status - good" after each fastboot command; however, once I boot up the phone, nothing is changed! WTF... =(
https://www.dropbox.com/s/z7gi5q8jgicijje/log.png?m
Click to expand...
Click to collapse
tool kits should be illegal.
animal24 said:
tool kits should be illegal.
Click to expand...
Click to collapse
Most of the tool kits use Fastboot.... anyway.. I am at the point I will try anything... And I cannot sent the phone for repair since it has been rooted and unlocked bootloader...:crying::crying::crying:
1stHTCphone said:
I followed efrant's guide and many other similar guide. The phone will talk to my computer and will prompt "fastboot status - good" after each fastboot command; however, once I boot up the phone, nothing is changed! WTF... =(
https://www.dropbox.com/s/z7gi5q8jgicijje/log.png?m
Click to expand...
Click to collapse
Didn't understand what didn't change?
You should be in stock 4.04
If you are getting fc or seeing old files just do factory reset.
Or you can do this before you start flashing.
Fastboot erase cache
Fastboot erase boot
Fastboot erase system
Fastboot erase userdata
Now do the flash part
Fastboot flash boot boot.img
Etc.....
1stHTCphone said:
Most of the tool kits use Fastboot.... anyway.. I am at the point I will try anything... And I cannot sent the phone for repair since it has been rooted and unlocked bootloader...:crying::crying::crying:
Click to expand...
Click to collapse
Well, if fastboot is not working there is one of two things that I think could potentially be the problem:
-- You are using an older version of fastboot.exe. Not sure if it makes a difference, but it may. Get the latest version from here.
-- There is a hardware problem. In this case, you may still be able to flash stock using a custom recovery assuming you have one installed. See below.
1) Get the LA03 bootloader from here.
2) Get the XXLA1 radio from here.
3) Get the IMM76I stock kernel from here.
4) Drop the IMM76I system.img file (from the factory image) into the attached zip file.
5) Download the attached IMM76I recovery.
6) Flash all of them in CWM in that order.
Hey there and really sorry for taking your time with something that problably will be solved within minutes >,<,
I'm trying to flash my One X (with cid : HTC__Y13) with maXimus but it isn't cooperating.
I've come to the part where I'm supposed to install a custom recovery, where I now notice now that I have no Idea what a custom recovery is...
I know, I know... I should have read up more before, but I must be stupid or something cause I can't find it !
//Sincerly
iConfide
iConfide said:
Hey there and really sorry for taking your time with something that problably will be solved within minutes >,<,
I'm trying to flash my One X (with cid : HTC__Y13) with maXimus but it isn't cooperating.
I've come to the part where I'm supposed to install a custom recovery, where I now notice now that I have no Idea what a custom recovery is...
I know, I know... I should have read up more before, but I must be stupid or something cause I can't find it !
//Sincerly
iConfide
Click to expand...
Click to collapse
it is the device meant to flash ROMs...
{
"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"
}
Use the Net
This will Help u my friend.
www.google.com
It allows you to install roms ...mods ....and if you have s off you can flash kernels from it
matt95 said:
it is the device meant to flash ROMs...
Click to expand...
Click to collapse
Okay, I see. Was abit too worried to just take a chance with the recovery-tool there, thanks there!
iConfide said:
Okay, I see. Was abit too worried to just take a chance with the recovery-tool there, thanks there!
Click to expand...
Click to collapse
Okay, new problem !
Thought I managed to install everything, cause it booted up and so on.
But when I unlock the phone, it's stuck in flight-mode =(!
Some people really should not be trying to flash a phone !!!!!!
Sorry ! :banghead:
Wright down ALL the steps you did ! So we can provide good help .... guessing is no fun !
MarcelHofs said:
Some people really should not be trying to flash a phone !!!!!!
Sorry ! :banghead:
Wright down ALL the steps you did ! So we can provide good help .... guessing is no fun !
Click to expand...
Click to collapse
Yeah, sorry, I thought it would be as easy to flash my One X as it was with my o2x.
I checked the log (kept it open) and I see now that I failed to flash Fastboot KIT V8.5!
I also thought that I (like the old times) should have flashed the rom in the custom recovery, but I see that I should probably have done that in Windows aswell!
Partial correct , you need to flash the rom in recovery and the boot.img that is found in the rom.zip file with fastboot commands from pc to the phone in fastboot mode
And let's be honest, if you have to ask what a custom recovery is afterwards then the homework is not done !
The recovery is kinda like BIOS on Windows. This sentence really cleared up my thoughts.
Sent from my HTC One X using xda app-developers app
superioor said:
The recovery is kinda like BIOS on Windows. This sentence really cleared up my thoughts.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Great explanation!
Will re-use that if ever I need to
MarcelHofs said:
Partial correct , you need to flash the rom in recovery and the boot.img that is found in the rom.zip file with fastboot commands from pc to the phone in fastboot mode
And let's be honest, if you have to ask what a custom recovery is afterwards then the homework is not done !
Click to expand...
Click to collapse
I've found the boot.img and I tried to flash it through fastboot mode, just said Failed: Remote not allowed.
Like I said before about the recovery-thing : wanted to make sure I didn't **** things up (which I evidently did anyways).
And yes, I do understand your point about that the homework haven't been done.
I noticed (and read) the first time you wrote about "some people", I've gotten the point .
Promise that I will read up more!
Is your bootloader still unlocked ? Flashing recovery went oke ?
MarcelHofs said:
Is your bootloader still unlocked ? Flashing recovery went oke ?
Click to expand...
Click to collapse
Home in 1 1/2 hour. Bootloader is still unlocked and cwm is installed. Installed maximus through recovery but as said... can't get the phone out off airplane-mode :<.
Oke uhm the maximum rom is a ICS rom ? Not trying to flash a JB rom did you ?
And if the bootloader is unlocked you should flash the boot.img oke . Hmmm
You did
fastboot flash boot boot.img
With the command in dos prompt ?
MarcelHofs said:
Oke uhm the maximum rom is a ICS rom ? Not trying to flash a JB rom did you ?
And if the bootloader is unlocked you should flash the boot.img oke . Hmmm
You did
fastboot flash boot boot.img
With the command in dos prompt ?
Click to expand...
Click to collapse
maXimus is a JB-rom, yes.
Yes, fastboot flash boot boot.img is the command I used.
EDIT: I missed the point where I was supposed to extract and start a .bat-file, apparently it's been done before and I must have missed out on searching for that for some strange reason...
*snip snip*
Tried updating 8.0.1 to 8.5.0 using the otherwise promising OTA feature.
Unfortunately, it resulted in a complete cluster-f¤ck.
Yes, I did NOT do a full wipe during the update.
Now, I have no cell coverage at all. Airplane Mode is ON, "Closing".... When I go to Settings > About, the software information shows no Baseband version, so no baseband driver installled...(?)
Trying rebooting, entering TWRP recovery, clearing cache, dalvik cache, fixing permissions and rebooting again, but this fixed nothing...
Trying rebooting, entering TWRP recovery, resetting phone, but this fixed nothing...
Another example of ALWAYS having to doing a full wipe when updating customs ROMs, I gues...
Sigh...
I think there is something wrong with the ROM. I made a full whipe (came from ardh 12) and i have the same. No guide selecting network and flightmode is on and no service. I have tried reflashing and making a whipe after flash but still problem.
First i though it was a kernel issue but no boot.img in the rom-file.
*snip snip*
So, yes. I'm a total dimwit =).
Finally solved atleast, thanks alot for the help!
I think you have to flash a ICS rom. What is your hboot number ? Is you're hboot 1.12 then you can not flash a JB rom !
You can find hboot version in the bootloader menu
Try a ics rom and i think you will be fine !
Try this
Put Rom.zip on sd card
Extract boot.img and flash it in fastboot
Enter recovery and wipe/factory reset
Wipe all caches / dalvik cache
And charge the phone full first before going at it again ... might be good to do !
Flash Rom and reboot .... I will bet it boots up fine
Thanks for the help, but the rom is installed... and yes, it is JellyBean =).
View attachment primoc_boot_unsecure.imgPlease excuse my absence. I will not be watching this thread for the time being. Hopefully if you have any questions, they can be answered by using the search option or someone else with this device that happens to check this thread will be kind enough to help.
!#I'M BACK#!
soon enough we won't need this thread, because we will all be able to RUU lol-Dec 6, 2013
beaups said:
posted on rumrunner.us. should work for both primou and primoc. Note, it is highly recommended (mandatory?) to be on a normal sense-based ICS rom and using an unsecure (preferably stock based) kernel. If you get poor results with other configurations, don't bother asking for help please!
Click to expand...
Click to collapse
S-OFF is here rumrunner.us
Huge thanks to beaups
This rom is probably most compatible with rumrunner
The boot.img inside is unsecure so flash away and GO GET S-OFFED!!!
Here's the unsecure boot.img that I used to achieve s-off.
View attachment primoc_boot_unsecure.img
{
"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"
}
Added init.d support
Added Root Permissions with Chainfire's SuperSu
This ROM was cooked with dsixda's Android Kitchen
Thank you and credit goes out to the both of them.
CLICK HERE TO DOWNLOAD
I have posted this ROM for safetynet/fall-back purposes.
I've noticed fellas posting please help, I forgot/didn't make a backup.
This is for you. Worried and maybe even a little scared that your phone is now a beautiful paper weight.
This ROM is completely stock with added init.d support and root.
It is still odexed, and with stock kernel.( I'm still learning/attempting to build one with extra governors and over clocking abilities ).
Instructions below....
1. Unlock your Bootloader by following the instructions at htcdev
1a. If you've succesfully unlocked your Bootloader, that means you have your fastboot files on your PC and know in general how to use them.
2. Download an openrecovery of your choice. I personally use TeamWinRecoveryProject 2.2.0 without any issues at all. (See the attached File)
3. Place the recovery.img that you have chosen into your fastboot folder.
3a. Change the name of the .img to recovery.img (just easier that way when sending the flash command)
4. Now open a terminal while in the fastboot folder.
4a. On Windows- hold shift+right click the mouse then click open command terminal here.
4b. On Ubuntu- CTRL+ALT+T to open a terninal then cd fastboot.
5.fastboot flash recovery recovery.img
5a. ^^^^^ Type this into the terminal. ^^^^^
5b. You now have a custom/openrecovery.
6. After the recovery.img is flashed, reboot your Bootloader.
6a. fastboot reboot-bootloader
7. After booted back into bootloader, use your volume-down button to highlight Recovery.
Now press your Power button to select it.
7a. Now your are in Recovery!
8. Click Wipe, then Cashe, then Dalvick, then Factory Rest, then System.
8a. This will wipe all of your phone nice and clean for a fresh install.
9. Click Home, then Install, and find the ROM.zip, click it, then install. Let it finish installing the click Wipe Cashe/Dalvick.
10. Navigate back to the Home screen and click Reboot, then Bootloader
10a. I hope you have a copy of the ROM.zip on your PC.
11. Open the ROM.zip and copy/extract the boot.img from inside it and place it in your fastboot folder.
12. Open a terminal once again.
13.fastboot flash boot boot.img
13a. Let it finish.
14. fastboot reboot
15. Enjoy.
These instructions are for use with TWRP (TeamWinRecoveryProject) They may be different using CWMrecovery (ClockWorkMod).
I made a backup of my stock rom via twrp. Updated the kernel and installed shpongle. When I tried to go back to my stock via twrp it would not boot due to the kernel. I wonder if that will be the case here
lostboybinns said:
I made a backup of my stock rom via twrp. Updated the kernel and installed shpongle. When I tried to go back to my stock via twrp it would not boot due to the kernel. I wonder if that will be the case here
Click to expand...
Click to collapse
u flashed shpongle? that means u are GSM not CDMA so this ROM just simply won't work
as for returning to stock, u can always flash a sense kernel duh
This is for primoc CDMA Virgin Mobile
I just downloaded and flashed to test, everything is working....Just like stock
This should allow me to update my PRL, right?
YUP!
Turns out it was a network fluke?
wont flash for me, i get:
"error executing updater binary in zip
and
error flashing zip
going to try a full format of the sd card...
russellvone said:
Turns out it was a network fluke?
Click to expand...
Click to collapse
What was a network fluke?
I'll cross reference the updater-script to another one I've used on a different Rom I cooked and have been running for over two weeks..... See if there are any differences between the two.
lilrob1213 said:
What was a network fluke?
Click to expand...
Click to collapse
I was replying to zombiegirl's question about updating her/his PRL
Matt_the_Geek said:
wont flash for me, i get:
"error executing updater binary in zip
and
error flashing zip
going to try a full format of the sd card...
Click to expand...
Click to collapse
Ok I found a difference in the updater-script, the update binaries are identical so that shouldn't be the issue. Problem I have is that I don't have a working computer to fix the updater-script. It won't be until June 26th that I can apply it. Sorry for the inconvenience.
P.S. are you flashing with TWRP?
Yes sir, TWRP. and no worries, it apparently just isn't your ROM. Angry HTC and jmz's stock ROM both give the same error. even after a full format of the SD. Rhythmic Rom 1.4 works though, and is what I was running. Was trying to return the device to somewhat stock tho as im either going to sell it or let my gf use it, so I was hoping for stable and to have the charge LED and icons working, hopefully.
Matt_the_Geek said:
Yes sir, TWRP. and no worries, it apparently just isn't your ROM. Angry HTC and jmz's stock ROM both give the same error. even after a full format of the SD. Rhythmic Rom 1.4 works though, and is what I was running. Was trying to return the device to somewhat stock tho as im either going to sell it or let my gf use it, so I was hoping for stable and to have the charge LED and icons working, hopefully.
Click to expand...
Click to collapse
If you downgrade TWRP to 2.3 you should be fine.
Sent from my One V using xda premium
ah, I'm on 2.5, so I'll look into that...
did the downgrade to TWRP 2.3.0.0, still the only thing i can install is Rhythimc Rom, everything else fails to install... unless i just got some really crappy downloads, so i'm off to try to dl the roms again...
Actually, instead I swapped out recoveries for CWM. aaaand it worked.
I unlocked phone as normal and flashed twrp to slots A and B but in twrp it shows no internal storage, I tried every solution, but nothing worked. Only thing that worked was flashing xiaomi.eu stable via fastboot. When I enter twrp with xiaomi.eu flashed all files are shown, but i can't boot back into system (after restart it comes back to twrp). I don't really know what to do I can stick to stable xiaomi.eu, but I can't update it, I can't install any other custom rom, and MiFlash as always throws errors left and right. It's my first dual slot phone, before I didn't have any problems with other Xiaomi devices. I hope someone can help, things I tried:
-wipe everything
-change file format
-relock bootloader
-reflash twrp
-flashing different twrp
Thanks in advence if someone manage to help.
EDIT
I bought USB OTG adapter and can flash from usb stick, only problem is that i can't transfer files from PC to phone while in twrp.
Debeciak said:
I unlocked phone as normal and flashed twrp to slots A and B but in twrp it shows no internal storage, I tried every solution, but nothing worked. Only thing that worked was flashing xiaomi.eu stable via fastboot. When I enter twrp with xiaomi.eu flashed all files are shown, but i can't boot back into system (after restart it comes back to twrp). I don't really know what to do I can stick to stable xiaomi.eu, but I can't update it, I can't install any other custom rom, and MiFlash as always throws errors left and right. It's my first dual slot phone, before I didn't have any problems with other Xiaomi devices. I hope someone can help, things I tried:
-wipe everything
-change file format
-relock bootloader
-reflash twrp
-flashing different twrp
Thanks in advence if someone manage to help.
Click to expand...
Click to collapse
You relock the bootloader, with Xiaomi.eu ??
Are you able to get to TWRP?
If you are not able to use TWRP, find Xiaomi repair center to revive your device.
pl1992aw said:
You relock the bootloader, with Xiaomi.eu ??
Are you able to get to TWRP?
If you are not able to use TWRP, find Xiaomi repair center to revive your device.
Click to expand...
Click to collapse
I relocked and unlocked bootloader while there was no rom installed
I can enter twrp but i can't flash roms because internal storage is 0mb and on pc it's show unknow storage amount.
TWRP is in alpha
Debeciak said:
I relocked and unlocked bootloader while there was no rom installed
I can enter twrp but i can't flash roms because internal storage is 0mb and on pc it's show unknow storage amount.
Click to expand...
Click to collapse
Go into fastboot and boot twrp
Code:
fastboot boot twrp_file_name.img
Then format data
{
"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"
}
After it's done, reboot to fastboot and run the above command again to get to TWRP.
See if this help.
pl1992aw said:
Go into fastboot and boot twrp
Code:
fastboot boot twrp_file_name.img
Then format data
After it's done, reboot to fastboot and run the above command again to get to TWRP.
See if this help.
Click to expand...
Click to collapse
As I said I tried to wipe everything (including format data), pretty much everything that is on forum i tried it.
Robert314 said:
TWRP is in alpha
Click to expand...
Click to collapse
So it is twrp fault? And if it is will it maybe work in future?
Then MiFlash is your hope.
Use the 20210226 version.
Do not lock bootloader in MiFlash.
Post screenshots what error it's showing to you, so people know what it means.
pl1992aw said:
Then MiFlash is your hope.
Use the 20210226 version.
Do not lock bootloader in MiFlash.
View attachment 5345137
Post screenshots what error it's showing to you, so people know what it means.
Click to expand...
Click to collapse
Phone is stuck on POCO screen right now. I used offical eea rom.
Debeciak said:
Phone is stuck on POCO screen right now. I used offical eea rom.
Click to expand...
Click to collapse
Same as this:
https://forum.xda-developers.com/t/4284821/page-2#post-85174225
The answer to that problem from user:
https://forum.xda-developers.com/t/4284821/post-85174245
pl1992aw said:
Same as this:
https://forum.xda-developers.com/t/4284821/page-2#post-85174225
The answer to that problem from user:
https://forum.xda-developers.com/t/4284821/post-85174245
Click to expand...
Click to collapse
But my phone didn't reboot into setup, it's stuck on logo and isn't starting.
Debeciak said:
But my phone didn't reboot into setup, it's stuck on logo and isn't starting.
Click to expand...
Click to collapse
Wait for it.
It takes some time for first booting. (wait 10 minutes)
pl1992aw said:
Wait for it.
It takes some time for first booting.
Click to expand...
Click to collapse
I waited for like 15 minutes and I'm pretty sure the phone vibrates from time to time.
Debeciak said:
I waited for like 15 minutes and I'm pretty sure the phone vibrates from time to time.
Click to expand...
Click to collapse
I also am trying to download latest official rom but server is very bad and it's pretty slow.
Debeciak said:
I also am trying to download latest official rom but server is very bad and it's pretty slow.
Click to expand...
Click to collapse
You said your phone works if flashing xiaomi.eu stable via fastboot.
Maybe try Xiaomi.eu again, at least getting a working phone.
Then use the built-in updater to update. Hope this work.
pl1992aw said:
You said your phone works if flashing xiaomi.eu stable via fastboot.
Maybe try Xiaomi.eu again, at least getting a working phone.
Click to expand...
Click to collapse
I guess that's my only option but it's not ideal and I can only flash the one stable version that is avaible via fastboot. Thanks for trying to help if latest official won't work with MiFlash im gonna use xiaomi.eu. Maybe in the future twrp update will solve that issue.
Debeciak said:
I guess that's my only option but it's not ideal and I can only flash the one stable version that is avaible via fastboot. Thanks for trying to help if latest official won't work with MiFlash im gonna use xiaomi.eu. Maybe in the future twrp update will solve that issue.
Click to expand...
Click to collapse
Try the built-in updater to update.
I read somewhere here saying you can flash update zip through built-in updater. (Tap the MIUI 12 icon a few times)
Read from Xiaomi.eu tutorial to update:
https://xiaomi.eu/community/threads...all-xiaomi-eu-rom-for-xiaomi-redmi-k40.60379/
If following their tutorial but you still cannot update, you can ask them how to, or read some replies there to see if there's similar cases.
pl1992aw said:
Try the built-in updater to update.
I read somewhere here saying you can flash update zip through built-in updater. (Tap the MIUI 12 icon a few times)
Read from Xiaomi.eu tutorial to update:
https://xiaomi.eu/community/threads...all-xiaomi-eu-rom-for-xiaomi-redmi-k40.60379/
If following their tutorial but you still cannot update, you can ask them how to, or read some replies there to see if there's similar cases.
Click to expand...
Click to collapse
The tutorial is how to update in case rom is fastboot variant since twrp is avaible xiaomi.eu roms are twrp only. It's working fine I will wait for new twrp version and then try.
Worst thing is that I can't go back to stock rom.
I went through something like this as well.
As long as you can boot into fastboot. Then no worries. Just Flash the official stockrom. If something goes wrong. Reboot into fastboot (everytime you do something through fastboot. If you keep doing multiple processes, you'll keep having errors, always. Well that's what I went through. Rebooting into fastboot fixed my problem)
But your last pic declares that it was successfully flashed though.
Debeciak said:
The tutorial is how to update in case rom is fastboot variant since twrp is avaible xiaomi.eu roms are twrp only. It's working fine I will wait for new twrp version and then try.
Worst thing is that I can't go back to stock rom.
Click to expand...
Click to collapse
When u flash xiaomi.eu, u set up the pin/pattern code in order to decrypt the internal storage in twrp?
Idk what's happening there.
It's just, flash xiaomi.eu via fastboot, boot it and set up pin/pattern code, fastboot boot twrp.img, go to twrp, insert the pin or pattern to decrypt internal storage and flash the latest update from xiaomi eu, simple as that..
And I don't get what's the A or B slot thing, I didn't had to chose or touch any of that, I saw that thing in twrp but didn't touched it..
Hi, this is my first time rooting a phone.
I was able to unlock, flash TWRP, install and root my phone with Magisk following this video from Munchy
Following that, I installed ArrowOS and wiped (Format Data) with TWRP, as per this video from Munchy again.
But then I noticed that on boot, my Magisk app stated N/A, so I assumed I had to reroot the phone again, so I followed this video but I think I flashed the wrong boot.img, and arrowOS was unable to detect Wi-Fi at all.
I then tried to use this to restore stock MIUI following this tutorial and now my phone is stuck on this screen as per my attached picture. Selecting any option here just brings me back to the same screen no matter what I try, can anyone help?
This is what MiFlash looks like as well after everything:
{
"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"
}
Platform tools:
Use the 8/13/21 version of MiFlash. I had issues with the newer versions. I zipped up the 8/13 version and uploaded it. You can download it here:
https://drive.google.com/open?id=1-...pdlf&[email protected]&usp=drive_fs
ajsmsg78 said:
Use the 8/13/21 version of MiFlash. I had issues with the newer versions. I zipped up the 8/13 version and uploaded it. You can download it here:
https://drive.google.com/open?id=1-UZgUFVCl3YBAxZBBtVYjpG2L-wOpdlf&[email protected]&usp=drive_fs
Click to expand...
Click to collapse
It says I need permission to access it, just sent in the request, any chance you're the one who can grant me permission?
aatkaw said:
It says I need permission to access it, just sent in the request, any chance you're the one who can grant me permission?
Click to expand...
Click to collapse
Sorry, fixed. You can download now. Also, in MiFlash go into Configuration and uncheck Read Back Verify if It's checked.
ajsmsg78 said:
Sorry, fixed. You can download now. Also, in MiFlash go into Configuration and uncheck Read Back Verify if It's checked.
Click to expand...
Click to collapse
I MANAGED TO FLASH IT, YOU SAVED MY PHONE DUDE THANKS!
If you don't mind, I'm trying to do the following:
-Root the Poco F3
-Flash ArrowOS
Is there a tutorial somewhere I can follow that can get me both of the above? I think I was able to root it successfully first, but flashing arrowos caused the issue of the post
You need to boot twrp in fastboot (fastboot boot twrp) then flash twrp once you're booted into twrp
ajsmsg78 said:
You need to boot twrp in fastboot (fastboot boot twrp) then flash twrp once you're booted into twrp
Click to expand...
Click to collapse
Is this the TWRP I need to flash for the Poco F3?
aatkaw said:
Is this the TWRP I need to flash for the Poco F3?
Click to expand...
Click to collapse
Flash this one. It's Orangefox recovery. Basically TWRP but better.
https://drive.google.com/open?id=1-...lZ82&[email protected]&usp=drive_fs
ajsmsg78 said:
Flash this one. It's Orangefox recovery. Basically TWRP but better.
https://drive.google.com/open?id=1-_EqlMUtJWDBJACR_V_vSu9NkCMzlZ82&[email protected]&usp=drive_fs
Click to expand...
Click to collapse
Need permissions XD
aatkaw said:
Need permissions XD
Click to expand...
Click to collapse
Done. It's not too often an Arnold helps another Arnold on XDA lol
Haha nice, ok I'm here now, what should I be pressing?
aatkaw said:
Haha nice, ok I'm here now, what should I be pressing?
Click to expand...
Click to collapse
Now you can flash whatever rom you want. Just make sure the "install recovery after flashing" or whatever it says is checked. It will automatically flash Orangefox after the ROM so it sticks. Make sure it is checked when you flash any rom. If the ROM doesn't come with Gapps you flash the ROM first, reboot recovery then flash Gapps then Magisk, then Format data (not wipe data, format data) then restart and you should be good to go.
I'm glad you got that flashing error sorted out. I still get shivers in my spine when I see that error...