Related
My Nexus One is stuck on boot screen and keeps recycling/vibrating. To condense information, here are bullet points of the situation:
-Nexus One 2.3.6 with unlocked bootloader
- PASSIMG.IMG is wrong or missing in HBOOT
-Can't access the sd root because I lost my sd adapter
-I've tried to fastboot recovery-RA-v2.2.1.img and Clockorange but I think that because I don't have the SU files in a folder titled SU on my sd, it doesn't go into the recovery menu
-When I cmd fastboot devices the serial comes up, but when I cmd adb devices, nothing comes up
-Can't access sd storage to move the SU folder via cmd
I've been working on this the past two days and searching and trying anything and everything. And nothing has worked. Any help would be great.
You don't need anything on your sdcard (or your sdcard itself for that matter) to put a custom recovery on your phone. Try this after putting your phone into fastboot mode and getting your cmd prompt up on the computer:
Code:
fastboot flash recovery "c:\location\to\recovery.img"
fastboot boot recovery "c:\location\to\recovery.img"
From here, try a factory reset.
And adb won't be able to see your phone until you are either in recovery or fully booted up in Android (only with USB Debugging enabled).
When I do "fastboot boot recovery recovery-RA-v2.2.1.img" it comes up cannot load recovery.
Any ideas?
And once that goes through, do I boot through recovery on the phone or through command prompt?
Thank you for the reply.
Is the recovery in the folder where you are typing the command? And have you verified that the md5 sum of the recovery is correct?
And, I always just change the command from flash to boot to boot into the recovery the first time. Otherwise, if you are running a stock Android version, your recovery might get restored back to the stock recovery (Android has checks in place for that).
Nevermind, I did get it to go through, but then my N1 reboots on its own and is still stuck at the bootscreen
Ok, do you want to continue running stock, or would you like to try a custom ROM? Because, it sounds like you will need to reload your ROM (assuming the Factory Reset/Data Wipe didn't work). They have a couple of rooted extremely close to stock versions on here, or you might want to give CM7 or MIUI a shot. I would also go and get temasek's system-only format since Amon_RA doesn't give you the option to format your /system partition. You can find the file in his mediafire folder http://mediafire.com/temasek
My original intentions were to put CM7 on my phone because Gingerbread began to crash a lot. So in that case, how am I supposed to install the CM7 ROM onto my phone if I can't get past the bootscreen?
So, the fastboot boot command doesn't work?
fastboot does work, adb doesn't
No, does the
Code:
fastboot boot recovery "c:\location\to\recovery.img"
get you into recovery? Or does it still freeze on the X screen (when you say bootscreen, I assume you mean the X)?
Sounds like the recovery isn't installing with fastboot? Do you get any error messages?
It will still freeze at the X and never boots into recovery.
seb0 said:
It will still freeze at the X and never boots into recovery.
Click to expand...
Click to collapse
I got exactly the same problem as you. Didn't you see my post?
Btw, the fastboot boot recovery "c:\location\to\recovery.img" command doesn't work, whoever gave that tips.
I got an idea, but not sure about it:
Get someone who has a working Nexus One to make an nandroid backup, and send the boot.img and system.img and fastboot it into our devices?
mrBira said:
Btw, the fastboot boot recovery "c:\location\to\recovery.img" command doesn't work, whoever gave that tips.
Click to expand...
Click to collapse
What do you mean it doesn't work? I know it works because I've used it many times. Does it give an error? Are you actually changing the c:\location\to\recovery.img to the proper location and name of the recovery file?
bassmadrigal said:
What do you mean it doesn't work? I know it works because I've used it many times. Does it give an error? Are you actually changing the c:\location\to\recovery.img to the proper location and name of the recovery file?
Click to expand...
Click to collapse
Yes ofc i got the path right. It gives this error:
"cannot load 'recovery'"
mrBira said:
Yes ofc i got the path right. It gives this error:
"cannot load 'recovery'"
Click to expand...
Click to collapse
That typically means that it can't find the file (which seems like it is looking for just recovery, not recovery.img or whatever the name is). Have you tried using tab completion to make sure it is the right filename?
bassmadrigal said:
That typically means that it can't find the file (which seems like it is looking for just recovery, not recovery.img or whatever the name is). Have you tried using tab completion to make sure it is the right filename?
Click to expand...
Click to collapse
If i write wrong filename it gives me another error. Yes the filename and path is 100% accurate.
I'm trying to fastboot flash system system.img to then fastboot boot boot.img to my N1 but everytime I flash the system.img it gets stuck a 1/4 of the way.
So basically, can someone please tell me how to get my N1 to stock so I can start from scratch with the CM7 flash?
Here is my system info:
-Nexus One (Unlocked) - T-Mobile service provider
-Android Version- 2.3.6
-Baseband Version- 32.41.00.32U_5.08.00.04
-Kernel Version- 2.6.35.7-59465-g42bad32 [email protected] #1
-Build Number- GRK39F
I have fastboot access but no adb access.
If you can provide the necessary files needed for this I would greatly appreciate it.
mrBira said:
If i write wrong filename it gives me another error. Yes the filename and path is 100% accurate.
Click to expand...
Click to collapse
Have you tried any additional recoveries? It has been awhile since I used that command, but I know it has worked in the past.
seb0 said:
I'm trying to fastboot flash system system.img to then fastboot boot boot.img to my N1 but everytime I flash the system.img it gets stuck a 1/4 of the way.
So basically, can someone please tell me how to get my N1 to stock so I can start from scratch with the CM7 flash?
Here is my system info:
-Nexus One (Unlocked) - T-Mobile service provider
-Android Version- 2.3.6
-Baseband Version- 32.41.00.32U_5.08.00.04
-Kernel Version- 2.6.35.7-59465-g42bad32 [email protected] #1
-Build Number- GRK39F
I have fastboot access but no adb access.
If you can provide the necessary files needed for this I would greatly appreciate it.
Click to expand...
Click to collapse
You won't have adb access unless you are in recovery or booted into Android with USB Debugging enabled.
Where did you get the system.img and boot.img files from?
http://forum.xda-developers.com/showthread.php?t=1061648
This was the only system.img and boot.img file I could find.
Here is the Lastest CM7 CWM 5.0.2.8 Recovery in PC49IMG.zip format.
No change log just got this build from building CM7 Sources for the Buzz so thought i pass it on like!
I have noticed though if you press the home and menu button the Selection bar goes up and down and search button now enters.
Feel free to mirror.
https://rapidshare.com/files/2097284807/PC49IMG.zip
Place on the root of your SDCard boot in to Hboot mode and it will want to flash say yes and reboot.
If your like me and are fastboot fans you can type.
fastboot devices
fastboot flash recovery recovery.img
fastboot reboot-bootloader
Enjoy!
hacktrix2006 said:
Here is the Lastest CM7 CWM 5.0.2.8 Recovery in PC49IMG.zip format.
No change log just got this build from building CM7 Sources for the Buzz so thought i pass it on like!
I have noticed though if you press the home and menu button the Selection bar goes up and down and search button now enters.
Feel free to mirror.
https://rapidshare.com/files/2097284807/PC49IMG.zip
Place on the root of your SDCard boot in to Hboot mode and it will want to flash say yes and reboot.
If your like me and are fastboot fans you can type.
fastboot devices
fastboot flash recovery recovery.img
fastboot reboot-bootloader
Enjoy!
Click to expand...
Click to collapse
will check this one out cheers
Thanks hacktrix2006 for share.+1 to you
No need to thank me, i just noticed it when building from the CM7 sources on my Android Cloud building Bot setup! If anything thank the CM7 team and Koash!
hacktrix2006 said:
No need to thank me, i just noticed it when building from the CM7 sources on my Android Cloud building Bot setup! If anything thank the CM7 team and Koash!
Click to expand...
Click to collapse
Yes,of course we thank to CM7 team and Koash aswell. But we thanks to you because you share with us ,our litle comunity of wildfire users
I have more to share soon after me a justice along with kssod has finished something nice for use all.
hacktrix2006 said:
I have more to share soon after me a justice along with kssod has finished something nice for use all.
Click to expand...
Click to collapse
That's cool ,i look forward for this
Do we gain something more than latest official version? Except the home/menu/search button differences.
Far as i can tell nothing to gain but just thought it be nice to share like!
Nice indeed and thanks for reply
Edit: i noticed the same things work in latest official.
Sent from my HTC Wildfire using Tapatalk 2 Beta-5
ive got trouble flashing on hboot mode. it checks the .zip file but dosent ask me if i want to flash it
---------- Post added at 11:17 AM ---------- Previous post was at 11:13 AM ----------
im having trouble on hboot it checks the .zip file but dosent ask me if i want to flash it ..
btw im new to flashing htc wildfire but not samsung galaxy mini
Could we eventually get a touch recovery made? That would be great. Thanks for building this!
Sent from my HTC Wildfire using xda premium
lokenok said:
ive got trouble flashing on hboot mode. it checks the .zip file but dosent ask me if i want to flash it
---------- Post added at 11:17 AM ---------- Previous post was at 11:13 AM ----------
im having trouble on hboot it checks the .zip file but dosent ask me if i want to flash it ..
btw im new to flashing htc wildfire but not samsung galaxy mini
Click to expand...
Click to collapse
if it won't work through the .zip file - try this:
Extract the zip, and rename to recovery.img to make it simple in ADB.
move the recovery.img to the same folder as your fastboot is in so it will be in ANDROID-SDK / TOOLS / recovery.img
as fastboot is located in ANDROID-SDK / TOOLS / fastboot.exe
then follow these commands EXACTLY as I tell you.
reboot phone in to bootloader - Power off, then HOLD volume down and press power, use volume keys for up and down and select fastboot.
now, open command line and start ADB - This part I expect you to know if you have a rooted phone, but humour me - the commands are " adb start-server"
remount, and open a shell - the commands are "adb remount", then enter "adb shell"
then enter the command "fastboot flash recovery recovery.img"
FINALLY, enter "fastboot reboot"
Recovery update complete... try rebooting into recovery to confirm this.
PLEASE NOTE - Some people have had issues with running fastboot through shell, if the above steps do not work try this: -
reboot phone in to bootloader - Power off, then HOLD volume down and press power, use volume keys for up and down and select fastboot.
now, open command line and start ADB - This part I expect you to know if you have a rooted phone, but humour me - the commands are " adb start-server"
Remount, "adb remount"
now we are ready to get started to flash this recovery, firstly you must navigate to your fastboot folder - fastboot is located in ANDROID-SDK / TOOLS / fastboot.exe - and launch cmd from the tools folder.
to do this you must first erase your current recovery and then flash the new recovery.img
So to wipe the recovery, when in terminal enter " fastboot erase recovery "
then enter the command "fastboot flash recovery recovery.img"
FINALLY, enter "fastboot reboot"
Recovery update complete... try rebooting into recovery to confirm this.
PLEASE NOTE please ensure you have entered these commands carefully or you will NOT have a recovery on your phone.
I AM NOT RESPONSIBLE FOR ANY MODIFICATIONS OR CHANGES YOU MAKE TO YOUR PHONE, I AM ONLY COMPILING THIS GUIDE TO HELP ALL USERS.
guys i have clockworkmod V4xxxx something... and thinking to upgrade to this 1... so can u tell me how to do it?? should i just enter recovery by pressing vol. down n power button and then flash this zip from my current clockworkmod??
You need to flash it via fastboot.
Flashing in recovery will give you temperory recovery. After reboot you will be reverted to your previous recovery.
Sent from my HTC Wildfire using XDA
Nakulkhanna said:
guys i have clockworkmod V4xxxx something... and thinking to upgrade to this 1... so can u tell me how to do it?? should i just enter recovery by pressing vol. down n power button and then flash this zip from my current clockworkmod??
Click to expand...
Click to collapse
First make a nandroid backup
Download the PC49IMG.zip file from the OP put on root of sdcard then power off , power on with volume down pressed and when it asks to update say yes wait to finish then power off
Remove sdcard use pc to delete PC49IMG.zip reinsert sdcard then power on
If you use custom partitions you need to boot in to cwm and restore your partitions and your backup that you made earlier then reboot
Nice, i'm using it now. Thx bro
using it now!
Worked like a charm, thanx!
It seems that after I flashed the recovery my phone gets stuck on the htc logo screen. And as mentioned above i deleted the update file after flashing
I rooted my phone without knowing about s-off and its s-on and i installed miui and i cant boot that room it gets to the miui logo and just sits there is there anyway at all to fix this
Edit:
ok now it wont turn i connect my usb to the phone and the orange light appears i get the sounds on windows saying its connected then it disconnects and then dose this over and over again so i have no idea what is going on please please help its really annoying me
If you are still s-on you need to manualy flash the boot.img or it will just boot loop. I use Flash Image GUI but there are other ways
Sent from my Vivid 4G using xda premium
Spectrejester said:
If you are still s-on you need to manualy flash the boot.img or it will just boot loop. I use Flash Image GUI but there are other ways
Sent from my Vivid 4G using xda premium
Click to expand...
Click to collapse
could u give me more info please
new problem
re edited to top post
Your battery is dead and cwm doesn't support off-mode charging, hence the reason you get the orange light but only for a moment. You can't charge the phone while its off..and you incorrectly flashed a custom rom. If you can find a way to charge your batt out of the phone you can fix this by either flashing the proper boot.IMG for the ROM from fastboot, or by running the appropriate ruu and starting from scratch. I highly recommend doing the s-off procedure. Its not difficult, and it makes customizing the phone so much simpler.
Sent from my PAC MAN Raider using XDA Premium
i have the same problem man did it just minutes before...i have only a black screen, the display gives a vibration feedback. i see the sdcards in windows but cant open them
What can i do help please!
Edit: Ok screen is on "htc" and keeps so for minutes and hours
Any solution?
N-rG said:
i have the same problem man did it just minutes before...i have only a black screen, the display gives a vibration feedback. i see the sdcards in windows but cant open them
What can i do help please!
Edit: Ok screen is on "htc" and keeps so for minutes and hours
Any solution?
Click to expand...
Click to collapse
Boot to bootloader (pwr and vol-). Does it say locked or unlocked? Does it say s-on or s-off? Select recovery. Does it still boot to custom recovery or do you get the android with the exclamation point? If the bootloader says locked, and you get the android with the !, you need to unlock the bootloader, fastboot flash a custom recovery, boot to that custom recovery, and flash your ROM. If bootloader is s-on, you'll also need to fastboot flash a boot.img that's compatible with the ROM you're flashing (can be found in the ROM's .zip)
homeslice976 said:
Boot to bootloader (pwr and vol-). Does it say locked or unlocked? Does it say s-on or s-off? Select recovery. Does it still boot to custom recovery or do you get the android with the exclamation point? If the bootloader says locked, and you get the android with the !, you need to unlock the bootloader, fastboot flash a custom recovery, boot to that custom recovery, and flash your ROM. If bootloader is s-on, you'll also need to fastboot flash a boot.img that's compatible with the ROM you're flashing (can be found in the ROM's .zip)
Click to expand...
Click to collapse
Thank you so much for your answer
It says "unlocked"
It says "s-on"
It boots to nothing. When i start the phone there is only standing "htc" nothing more happend. No explantion Mark But i can get into the bootloader.
Or what do you mean with "it still boot to custom recovery or do you get the android with the exclamation point?"
How do I do that with the boot.img? Please i am such a noob im so sorry i dont unterstand a lot im so angry about myself that i did it, please can you exactly tell me what i should do and what i need?
I did a backup before but there is no "boot.img"
And how can i use the boot.img wenn i cant get access to the sd memory?
N-rG said:
Thank you so much for your answer
It says "unlocked"
It says "s-on"
It boots to nothing. When i start the phone there is only standing "htc" nothing more happend. No explantion Mark But i can get into the bootloader.
Or what do you mean with "it still boot to custom recovery or do you get the android with the exclamation point?"
How do I do that with the boot.img? Please i am such a noob im so sorry i dont unterstand a lot im so angry about myself that i did it, please can you exactly tell me what i should do and what i need?
I did a backup before but there is no "boot.img"
And how can i use the boot.img wenn i cant get access to the sd memory?
Click to expand...
Click to collapse
When you boot to bootloader, scroll down and select recovery. What happens?
As far as flashing the boot.img, when you downloaded the ROM's .zip, inside the .zip should have been a file called boot.img. You need to drag that to the directory where you have fastboot installed, boot to bootloader, connect your phone, select fastboot. It should now say "fastboot usb". Now in the directory where you have fastboot and boot.img (with neither selected), shift+right click, choose "Open command window here". You need to enter "fastboot flash boot boot.img" and hit enter. Then reboot
At first, thaaank you so much for your help, i feel so lost....
Ah ok i understand, you mean the "[ROM][ICEss v 0.4][Stockish ICS/SENSE 3.6" -that is what i downloaded.
When i am in the bootloader menu and activate recovery the htc symbol appears with a white backround...nothing more happen for minutes
unfortuneately there is not boot.img in this zip
I did the whole procedure with the Vivid_All-In-One_Kit_v2.2 and not fastboot.
Ok i now downloaded fastboot and put it to c:/fastboot
I do what you say and reach your point " It should now say "fastboot usb" thats right, it works. But i dont have the boot.img where can i get it?
N-rG said:
At first, thaaank you so much for your help, i feel so lost....
Ah ok i understand, you mean the "[ROM][ICEss v 0.4][Stockish ICS/SENSE 3.6" -that is what i downloaded.
When i am in the bootloader menu and activate recovery the htc symbol appears with a white backround...nothing more happen for minutes
unfortuneately there is not boot.img in this zip
I did the whole procedure with the Vivid_All-In-One_Kit_v2.2 and not fastboot.
Ok i now downloaded fastboot and put it to c:/fastboot
I do what you say and reach your point " It should now say "fastboot usb" thats right, it works. But i dont have the boot.img where can i get it?
Click to expand...
Click to collapse
There's not a boot.img in the zip you downloaded? Then you need to read the thread and see what kernel they recommend, get the boot.img, and fastboot flash it. You're getting close.
It sounds like you may have lost your custom recovery along the way too (in which case more may have broke) - you'll need to get a custom recovery .img (wcx or twrp) and fastboot flash it (fastboot flash recovery <nameofrecovery>.img). Then fastboot flash boot.img, then boot to recovery and reflash the ROM and hopefully you'll be all set.
Thanks again, im getting closer! I read the whole thread and found that "Holics_Kernel_0730_S-ON" is recommended. I downloaded and found the boot.img I put it in the fastboot folder.
But i dont understand what do you mean with "you'll need to get a custom recovery .img (wcx or twrp)"
Do you mean the recovery i created with my old working Gingerbread or a recovery form the custom rum i downloaded?
When last, where can i get such a recovery.img?
Hey man btw. you gave me so much hope at the moment, thats incredible, thank you!
Check the dev section. Everything you will need is in the stickied threads. Twrp recovery also has its own thread
bypruv oculus
Okay i'll do meanwhile there is something new. I create use fastboot, the boot.img of the new kernel and do it with the command line like you said.
The phone now boots one step more to "htc quietly brilliant" and then restarts over and over again to this screen, like a loop.
---------- Post added at 11:42 PM ---------- Previous post was at 11:25 PM ----------
ahhh i reach Android System Recovry with several menus. I didnt find any help in google what i have to do now.
Backup google propritary System, nand backup, Nand Restore, Restore google proprietary System? Or something else?
No.. at this point you should wipe cache, dalvik cache, system, an data. This can all be done In Recovery's wipe menu. Them recovery should have a flash zip menu. Flash the ROM .zip
Put the brakes on!
I saw gingerbread...
When you boot to bootloader...
There is a line labeled hboot
What's the number next to it?
If its 1.85... you good...
If its 1.83... thou shalt find an ICS ruu for your carrier.
Almost none of the ROMs you find here run on 1.83
Sent from my Vivid 4G using Tapatalk 2
Good catch!
Hey,
i bring it to run! I restored every part manuall...system, cache, data. Only restore boot didnt work. I suggest its because Rom Manager/ClockworkMod didn't created such a file (boot.img) So i downloaded a custom kernel für Gingerbread.
Vola, handy startet, Os is on. Loggin into network worked!
BUT! I cannot use Wlan/wifi or mobile networking. I suppose its because the rom right?
I mentioned that i have the same phone here from my girlfriend.
How and can i make a boot.img of her phone? Please tell my how and then i have finished everything i hope
You can't. S*on devices can't flash boot.IMG or back up boot.IMG in recovery. You have to fast boot flash the boot.IMG. this is also why wifis broken
The kernel and ramdisk and some other things are packed into boot.IMG, and are made by ROM or kernel devs. Actually now that you're booting, you can use an app called flash image GUI to flash the boot.img
Ok I expressed something wrong, sorry (im not a native speaker u might noticed long before ^^ ). So i try again like I said i did the manuell recovery of everything except the boot.img.
Thats why i loaded this kernel for Gingerbread (http://forum.xda-developers.com/showthread.php?t=1351717) and installed the boot.img with fastboot "flash boot boot.img"
Fastboot said well done. Phone startet.
I think i understand what you are writing, but i dont understand which boot.img do you mean i need. I have no boot.img from my backup before flashing with custom rom without this boot.img i cant flash the not working one of the ICS on my phone am i right?
So thats why i thought i can take the phone of my girlfriend, create a boot.img and use it for my phone. So thats the only problem, i need working boot.img and then flash with fastboot oder the app you mentioned How to get the boot.img
okay...i'll tell you the steps I took that got me to said bootloop..
1. towelroot rooted
2. downloaded supersu from playstore, updated bianary via "normal"
3. tested root w/ xplore app / everything checked out..i had root
4. unlocked the bootloader (got rid of download mode to access fastboot and did the command "fastboot oem unlock"
5. busybox install w/ stericson app
6. flashed twrp via rom installer and a .img file (it was the 415 version I made sure)
7. download pac man rom and gapps from the threads OP and put them on internal memory
8. reboot into recovery
9 wiped dalvik cache/cache/system/data
10 flashed pacman and gapps
11 gapps flash failed, couldn't execute bianary....
at this point i'm not sure if the pacman rom failed also, i just saw the gapps one failed and figured i would boot into the pac man and grab PA gapps......once i hit reboot.....bootloop!
tried to do button combo's to get into recovery....either i'm doing it wrong.....or recovery is borked because of a bad flash...(i think i'm doing it wrong....i press down on volume up+down and power....when i see the logo i let go of power and then hold the power button again???
anyways..fastboot works....but "adb devices" see's nothing
any help is appriciated.....i think i'm just going to exchange it in the store and say it's bootlooping...it's within the 14 days i bought it...and then after that i don't think i'm going to root it..it's to risk for a temp phone till my nexus 6 comes in.....that one is easy to hack...this one is stupid.
derp a derp
it pays to read the QandA common questions and answers....it was on the bottom of that...how to get into recovery....everywhere else on the web was wrong! gah..lol and the gapps isn't what failed..it was the pacman rom...maybe i got a bad download..gonna re-downlaod and try again......
no go
got to recovery.....tried to flash the stock .zip in the thread......nope...eventually it wouldn't mount /system so yeah..i'm going to exchange it at the store and maybe just root it..nothing else..no custom roms for this badboy...not hack friendly
pychobj2001 said:
got to recovery.....tried to flash the stock .zip in the thread......nope...eventually it wouldn't mount /system so yeah..i'm going to exchange it at the store and maybe just root it..nothing else..no custom roms for this badboy...not hack friendly
Click to expand...
Click to collapse
This ROM has a bad boot.img at the moment. The current workaround is to replace the boot.img in the downloaded zip with the boot.img from my CM11 ROM here.
You did everything right, minus not reading thru this forum. Not downing you, but if you had, you would have known about what I stated in my previous paragraph.
If PAC-ROM flashed, you can then power down the device and enter fastboot mode. Extract the boot.img from my ROM to the folder where your copy of the fastboot executable lives, then type:
Code:
fastboot flash boot boot.img
When that's finished, type:
Code:
fastboot reboot
No need to get discouraged. It may take a day or two, but there's always someone who has an answer to your Android related questions
Thank you Shinobi, your solution helped me deal with my bootlooping that happened to me
Sent from my LG-D415 using XDA Free mobile app
Hello! Hoping someone can help and guide me in fixing my A2's bootloop. I already searched many forums online, but still no luck.
I flashed a permissiver_v5.zip in Evolution X Rom hoping that it will solve the random reboots, and I got bootloop. I successfully flashed the July stock rom through Miflash, hoping to boot into system, but still bootloop. I flashed the stock firmware and persist zip too in TWRP, but I also got mount persist error. I also need to use fastboot boot twrp.img to get into Twrp since it will disappear after clicking reboot recovery. I tried EDL, but then I got not enough storage error in Miflash.
Hopefully somebody can help me with steps!
LATEST UPDATE:
With the help of KevMetal, I can now use my phone after a week of being hardbricked. At first, my device can't boot to the bootloader or recovery, so what I did was to press the volume down and power button for some time and my phone was detected by the PC. So my device booted to EDL by itself, no need to open the phone. Then I used the 2018 version of MiFlash Tool and flashed the V.10.0.17 of stock Pie ROM from here: https://forum.xda-developers.com/mi-...-t3824849/amp/
After that, I flashed the persist.zip provided by KevMetal (browse in this thread) in recovery since I can't sideload the zip, and it worked fine. I then booted to system and finally there was no bootloop.
I then noticed that the IMEI was gone, so I tried to fix through some guides online but this one worked for me. https://medium.com/@shekhawatkoki/fi...1-2ed533548d32
Ronaldendoma said:
Hello! Hoping someone can help and guide me in fixing my A2's bootloop. I already searched many forums online, but still no luck.
I flashed a permissiver_v5.zip in Evolution X Rom hoping that it will solve the random reboots, and I got bootloop. I successfully flashed the July stock rom through Miflash, hoping to boot into system, but still bootloop. I flashed the stock firmware and persist zip too in TWRP, but I also got mount persist error. I also need to use fastboot boot twrp.img to get into Twrp since it will disappear after clicking reboot recovery. I tried EDL, but then I got not enough storage error in Miflash.
Hopefully somebody can help me with steps!
Click to expand...
Click to collapse
you are messing up ..stop ..
1.boot into fastboot
2. flash stock rom with miflash
3. boot back to fastboot
4. download orange fox or pitch black recovery that actually supports persist flashing
5. join global mi a2 telegram group download relevant persist like if mi a2 or mi x6 and on android 9 or 10
6. put it in adb folder
7. boot recovery ( don't flash)
8. in recovery activate sideload adb option
9. in command window run :adb sideload persist.zip ( persist must have this name in adb folder )
10. now reboot your phone
*in the beginning it will bootloop four or five times ..just leave it
***suddenly your phone will be back to new
***stop flashing permissver and other crap
Sent from my wayne using XDA Labs
KevMetal said:
you are messing up ..stop ..
1.boot into fastboot
2. flash stock rom with miflash
3. boot back to fastboot
4. download orange fox or pitch black recovery that actually supports persist flashing
5. join global mi a2 telegram group download relevant persist like if mi a2 or mi x6 and on android 9 or 10
6. put it in adb folder
7. boot recovery ( don't flash)
8. in recovery activate sideload adb option
9. in command window run :adb sideload persist.zip ( persist must have this name in adb folder )
10. now reboot your phone
*in the beginning it will bootloop four or five times ..just leave it
***suddenly your phone will be back to new
***stop flashing permissver and other crap
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Thank you so much for your reply. I really appreciate it. I admit that I am really wrong in flashing that permissiver zip. I just hoped that it will solve my random reboot issue, from this tutorial: https://www.google.com/url?sa=t&sou...BMAB6BAgCEAE&usg=AOvVaw2suOu9rYeTps71AvKuZbrA
So now, I already downloaded OrangeFox-R10.1_1-Stable-jasmine_sprout.zip for recovery and persist_restorer_6x.zip from the Telegram group, which is universal persist according to them.
But I just have some questions:
1. Do I need to wipe both a and b in recovery or use command fastboot -w before flashing the stock ROM?
2. After flashing stocK ROM in Miflash tool, it will start to boot to system, but in this case, bootloop, so am I right to press buttons to forcibly go to bootloader?
3. For #7 (boot to recovery), this means fastboot boot recovery.img?
4. For #9, if adb sideload doesn't work, can I flash persist in recovery instead?
Ronaldendoma said:
Thank you so much for your reply. I really appreciate it. I admit that I am really wrong in flashing that permissiver zip. I just hoped that it will solve my random reboot issue, from this tutorial: https://www.google.com/url?sa=t&sou...BMAB6BAgCEAE&usg=AOvVaw2suOu9rYeTps71AvKuZbrA
So now, I already downloaded OrangeFox-R10.1_1-Stable-jasmine_sprout.zip for recovery and persist_restorer_6x.zip from the Telegram group, which is universal persist according to them.
But I just have some questions:
1. Do I need to wipe both a and b in recovery or use command fastboot -w before flashing the stock ROM?
2. After flashing stocK ROM in Miflash tool, it will start to boot to system, but in this case, bootloop, so am I right to press buttons to forcibly go to bootloader?
3. For #7 (boot to recovery), this means fastboot boot recovery.img?
4. For #9, if adb sideload doesn't work, can I flash persist in recovery instead?
Click to expand...
Click to collapse
no install stock using miflash but don't wipe anything ..for this to work well don't install the recovery ..just boot
fastboot boot recovery.img
then using the adb sideload option you can flash the zip from your computer without decryting the internal storage
you can flash magisk the same way ..then you will have stock rooted with persist restored but without custom recovery and your device will remain encrypted ..
if you want custom recovery and install custom rom you can wipe and install but for stock don't do it ..flash persist and magisk from adb sideload without decrypting
2.yeah enter bootloader / fastboot with power button and volume button
4. it will work if done correctly ...if you want to flash from internal storage you will have to wipe and format data to decrypt internal syorage
Sent from my wayne using XDA Labs
KevMetal said:
you are messing up ..stop ..
1.boot into fastboot
2. flash stock rom with miflash
3. boot back to fastboot
4. download orange fox or pitch black recovery that actually supports persist flashing
5. join global mi a2 telegram group download relevant persist like if mi a2 or mi x6 and on android 9 or 10
6. put it in adb folder
7. boot recovery ( don't flash)
8. in recovery activate sideload adb option
9. in command window run :adb sideload persist.zip ( persist must have this name in adb folder )
10. now reboot your phone
*in the beginning it will bootloop four or five times ..just leave it
***suddenly your phone will be back to new
***stop flashing permissver and other crap
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
KevMetal said:
no install stock using miflash but don't wipe anything ..for this to work well don't install the recovery ..just boot
fastboot boot recovery.img
then using the adb sideload option you can flash the zip from your computer without decryting the internal storage
you can flash magisk the same way ..then you will have stock rooted with persist restored but without custom recovery and your device will remain encrypted ..
if you want custom recovery and install custom rom you can wipe and install but for stock don't do it ..flash persist and magisk from adb sideload without decrypting
2.yeah enter bootloader / fastboot with power button and volume button
4. it will work if done correctly ...if you want to flash from internal storage you will have to wipe and format data to decrypt internal syorage
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Thank you again.
I tried adb sideload before but was stuck at 0%, I missed something. I'll update here for the result once I can be back to PC.
KevMetal said:
you are messing up ..stop ..
1.boot into fastboot
2. flash stock rom with miflash
3. boot back to fastboot
4. download orange fox or pitch black recovery that actually supports persist flashing
5. join global mi a2 telegram group download relevant persist like if mi a2 or mi x6 and on android 9 or 10
6. put it in adb folder
7. boot recovery ( don't flash)
8. in recovery activate sideload adb option
9. in command window run :adb sideload persist.zip ( persist must have this name in adb folder )
10. now reboot your phone
*in the beginning it will bootloop four or five times ..just leave it
***suddenly your phone will be back to new
***stop flashing permissver and other crap
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
KevMetal said:
no install stock using miflash but don't wipe anything ..for this to work well don't install the recovery ..just boot
fastboot boot recovery.img
then using the adb sideload option you can flash the zip from your computer without decryting the internal storage
you can flash magisk the same way ..then you will have stock rooted with persist restored but without custom recovery and your device will remain encrypted ..
if you want custom recovery and install custom rom you can wipe and install but for stock don't do it ..flash persist and magisk from adb sideload without decrypting
2.yeah enter bootloader / fastboot with power button and volume button
4. it will work if done correctly ...if you want to flash from internal storage you will have to wipe and format data to decrypt internal syorage
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Thank you again.
I tried adb sideload before but was stuck at 0%, I maybe missed something. I'll update here for the result once I can be back to PC.
Ronaldendoma said:
Thank you again.
I tried adb sideload before but was stuck at 0%, I maybe missed something. I'll update here for the result once I can be back to PC.
Click to expand...
Click to collapse
ok yeah must be a mistake ..
do you understand that first you enter fastboot and boot the orange fox recovery ..only then you start the adb ..
BUT REMember first you need to toggle or activate adb from orange fox recovery (maybe you forgot this ? )
another thing it is very slow so wait very long
another thing the zip you want to flash must be in the adb folder and have the name you use
so
rename persist to persist.zip and put it in adb folder ..then put magisk zip and rename to magisk.zip :
adb sideload persist.zip
adb sideload magisk.zip
Sent from my wayne using XDA Labs
here is a photo where you need to activate adb
Sent from my wayne using XDA Labs
KevMetal said:
ok yeah must be a mistake ..
do you understand that first you enter fastboot and boot the orange fox recovery ..only then you start the adb ..
BUT REMember first you need to toggle or activate adb from orange fox recovery (maybe you forgot this ? )
another thing it is very slow so wait very long
another thing the zip you want to flash must be in the adb folder and have the name you use
so
rename persist to persist.zip and put it in adb folder ..then put magisk zip and rename to magisk.zip :
adb sideload persist.zip
adb sideload magisk.zip
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
I need to wait more, I think. Before this thread, I tried to adb sideload in TWRP but it took somewhat long and still 0%, so I just cancelled since I ran out of time.
KevMetal said:
here is a photo where you need to activate adb
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Regarding persist.zip, I am now confused because I asked in the group if the file persist_restorer_6x.zip is universal (either pie or 10, wayne or jasmine), they said yes, and another one said no. I searched in the group and found persist_restorer_a2.zip. I checked both files and they have the same filesize and contents.
So is there a thing like a universal persist for a2/6x, either for pie or 10? Or like what you said, only relevant persist depending on the os and device?
techieboy2020 said:
Regarding persist.zip, I am now confused because I asked in the group if the file persist_restorer_6x.zip is universal (either pie or 10, wayne or jasmine), they said yes, and another one said no. I searched in the group and found persist_restorer_a2.zip. I checked both files and they have the same filesize and contents.
So is there a thing like a universal persist for a2/6x, either for pie or 10? Or like what you said, only relevant persist depending on the os and device?
Click to expand...
Click to collapse
it is the same device.. so it is cross compatible ..it might just give an error if it checks the build prop ..obviously flash the A2..pie or q will just maybe be updated version or not but bettrr to flash corresponding if it exists
Sent from my wayne using XDA Labs
KevMetal said:
it is the same device.. so it is cross compatible ..it might just give an error if it checks the build prop ..obviously flash the A2..pie or q will just maybe be updated version or not but bettrr to flash corresponding if it exists
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
I see. I can't access my PC yet, but what if I still got bootloop after trying those steps, what must I do next? I'm worried for step #10.
Regarding the persist.zip, can you please check the zips below? The two have the same filesize and files inside, so maybe the two are just the same.
techieboy2020 said:
I see. I can't access my PC yet, but what if I still got bootloop after trying those steps, what must I do next? I'm worried for step #10.
Regarding the persist.zip, can you please check the zips below? The two have the same filesize and files inside, so maybe the two are just the same.
Click to expand...
Click to collapse
those are empty and won't work ..use this
https://www.dropbox.com/s/mimt4go8fert44c/persist good.zip?dl=0
Sent from my wayne using XDA Labs
KevMetal said:
those are empty and won't work ..use this
https://www.dropbox.com/s/mimt4go8fert44c/persist good.zip?dl=0
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Ok thank you so much. Will try this tomorrow.
Regarding the state of my device, I can't boot to system because of bootloop. If I press power and volume +, I got no command. If I press power and volume -, fastboot mode. My device's bootloader is already unlocked, and can be detected through fastboot.
techieboy2020 said:
Ok thank you so much. Will try this tomorrow.
Regarding the state of my device, I can't boot to system because of bootloop. If I press power and volume +, I got no command. If I press power and volume -, fastboot mode. My device's bootloader is already unlocked, and can be detected through fastboot.
Click to expand...
Click to collapse
you don't need to boot to system ...just boot the revovery and flash the zip ..
Sent from my wayne using XDA Labs
KevMetal said:
you don't need to boot to system ...just boot the revovery and flash the zip ..
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Got it. So the zip is compatible for either Pie or Android 10?
What's the best version for Miflash tool? I tried the newer version but it can't detect my device, and only the older version can detect. But it seems that the older version can't be trusted also since I still got persist error before.
For #10, my device will bootloop 4 to 5 times. So will it automatically turn off and on again until it will successfully boot? How long does it normally boot?
UPDATE:
KevMetal said:
you don't need to boot to system ...just boot the revovery and flash the zip ..
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
UPDATE:
So I flashed the Pie Rom (V.10.0.17.0) in the MiFlash Tool (v. 2016.04.01.0) and the flashing was successful. The device turned on and only remained at the Android One logo and turned off again. This repeated for another time and I then forced my device to fastboot mode through the buttons. I then flashed the latest Orange Fox Recovery and it was successful. Now, I checked the recovery and persist can't be mounted (can't put a check on the box), but I still continued to adb sideload mode. The sideloading for persist.zip started, but was stuck at 10%. I waited more and decided to disconnect and try to flash the zip on the device instead. I checked the active slot and it was b, so I thought changing to a will be able to mount persist. I thought that if I remain at b, I will still get mount persist error. I clicked "boot to recovery" and the screen turned off. After a while, the screen remained off and I tried to use the button combinations, and the screen was totally black (no fastboot, logo, animation, or even some light, etc). It's completely black, but I noticed that the device was still hot after a few minutes. I connected my device to the PC again and the MiFlash tool detected my device as Com10. I flashed the rom again but the flashing was not successful. I tried to uninstall the drivers and still, there is no hope for reflashing the rom (it's now detected as com4). If I try to use power combinations, the PC will make sounds like when you connect/ disconnect a device, meaning, my phone can still be detected by my PC. So is there still a hope for my phone?
techieboy2020 said:
UPDATE:
So I flashed the Pie Rom (V.10.0.17.0) in the MiFlash Tool (v. 2016.04.01.0) and the flashing was successful. The device turned on and only remained at the Android One logo and turned off again. This repeated for another time and I then forced my device to fastboot mode through the buttons. I then flashed the latest Orange Fox Recovery and it was successful. Now, I checked the recovery and persist can't be mounted (can't put a check on the box), but I still continued to adb sideload mode. The sideloading for persist.zip started, but was stuck at 10%. I waited more and decided to disconnect and try to flash the zip on the device instead. I checked the active slot and it was b, so I thought changing to a will be able to mount persist. I thought that if I remain at b, I will still get mount persist error. I clicked "boot to recovery" and the screen turned off. After a while, the screen remained off and I tried to use the button combinations, and the screen was totally black (no fastboot, logo, animation, or even some light, etc). It's completely black, but I noticed that the device was still hot after a few minutes. I connected my device to the PC again and the MiFlash tool detected my device as Com10. I flashed the rom again but the flashing was not successful. I tried to uninstall the drivers and still, there is no hope for reflashing the rom (it's now detected as com4). If I try to use power combinations, the PC will make sounds like when you connect/ disconnect a device, meaning, my phone can still be detected by my PC. So is there still a hope for my phone?
Click to expand...
Click to collapse
all of this couldn't happen if you only flashed permissiver ..what rom did you previously flash in slot b
anyway doesn't matter ..boot to fastboot with buttons ..boot ..NOT FLASH orange fox recovery
do all wipes
format data
install custom rom
install magisk
install persist
reboot to other standby slot ..
do all wipes
format data
install custom rom
install magisk
install persist
then reboot and phone will boot
use a latest custom rom Q with gapps included ....
follow all the instructions ..not only some ..don change them ..if it fails message me with screenshot
but the 10% problem over usb is a hardware , computer or most likely cable problem ..get a new cable ..or maybe you changed or damaged your screen improperly ..
anyway try the above
also download the most newest copy of miflash and use that to install drivers and flash if you want to flash stock and flash the latest stock amdroid ..
if your phone doesn't go into fastboot it is cos it is bricked in edl mode ..so flash latest stock with latest miflash ..
THEN FLASH PERSIST BY ONLY BOOTINGBrecovery
did you try to convert this A2 to Wayne amd triggered arb ? that could be why flashing stock pie goes to edl mode
Sent from my wayne using XDA Labs
Just FYI:
Since 10.0.2.0 till now I thought that persist.img is version-insensitive, as I flashed persist.img taken from 8.1 ROM into couple of versions of 9.0 without any problems (via my method published in "Guides...").
Last week I noticed that compass is "showing south", and tried to flash various versions of persist.img into active 11.0.12.0 - and was surprised to encounter "white screen of eternal booting" with non-native version of persist.img. So finally had to flash persist.img taken from 11.0.12.0 fastboot ROM image.
(Btw, my problem with compass seems to have 2 sides -1st is somewhat very big deviation at homeplace, and 2nd is that only 1st magnetic sensor is being calibrated while second magnetic sensor is not being calibrated by means I used).
KevMetal said:
all of this couldn't happen if you only flashed permissiver ..what rom did you previously flash in slot b
anyway doesn't matter ..boot to fastboot with buttons ..boot ..NOT FLASH orange fox recovery
do all wipes
format data
install custom rom
install magisk
install persist
reboot to other standby slot ..
do all wipes
format data
install custom rom
install magisk
install persist
then reboot and phone will boot
use a latest custom rom Q with gapps included ....
follow all the instructions ..not only some ..don change them ..if it fails message me with screenshot
but the 10% problem over usb is a hardware , computer or most likely cable problem ..get a new cable ..or maybe you changed or damaged your screen improperly ..
anyway try the above
also download the most newest copy of miflash and use that to install drivers and flash if you want to flash stock and flash the latest stock amdroid ..
if your phone doesn't go into fastboot it is cos it is bricked in edl mode ..so flash latest stock with latest miflash ..
THEN FLASH PERSIST BY ONLY BOOTINGBrecovery
did you try to convert this A2 to Wayne amd triggered arb ? that could be why flashing stock pie goes to edl mode
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
So I was able to use another laptop, and I managed to install adb, drivers, and MiFlash Tool. The 2018 version can now detect my phone, and I can now at least boot into fastboot. But my flashing is still not successful because I got stuck at system.img. The laptop freezes and I already tried to free up space in C: drive.