Related
So like a tard, I went and flashed a ROM for the One wanting a menu button. Unfortunately, this ROM was not specifically for a Sprint HTC One, but for the other One variants. Now my wifi and data are broken, and my phone constantly restarts itself, independent of the ROM I'm using ( I've flashed at least 3 ROMs to confirm this). Is there anything I can do to specifically re-flash the radios/prevent the constant restarting?
Boomchaos said:
So like a tard, I went and flashed a ROM for the One wanting a menu button. Unfortunately, this ROM was not specifically for a Sprint HTC One, but for the other One variants. Now my wifi and data are broken, and my phone constantly restarts itself, independent of the ROM I'm using ( I've flashed at least 3 ROMs to confirm this). Is there anything I can do to specifically re-flash the radios/prevent the constant restarting?
Click to expand...
Click to collapse
you have to flash a boot.img too- you shouldn't flash roms not specific to your phone, you'll brick it
Please read my post here before you brick your phone.
http://forum.xda-developers.com/showthread.php?p=40678263
Aldo101t said:
you have to flash a boot.img too- you shouldn't flash roms not specific to your phone, you'll brick it
Click to expand...
Click to collapse
I flashed viperBoy's stock Sprint ROM and that already had a boot.img in it. Are you saying I should flash that separately?
Boomchaos said:
I flashed viperBoy's stock Sprint ROM and that already had a boot.img in it. Are you saying I should flash that separately?
Click to expand...
Click to collapse
yes, if you are s-on not s-off you do, with s-on even if the rom has a boot image, it will not flash the boot.img you must pull the image boot from the rom zip and flash it via adb sdk tools in fastboot
Aldo101t said:
yes, if you are s-on not s-off you do, with s-on even if the rom has a boot image, it will not flash the boot.img you must pull the image boot from the rom zip and flash it via adb sdk tools in fastboot
Click to expand...
Click to collapse
Is there a particular order in flash the boot.img vs. the main rom? And should I have taken out the boot.img from the ROM before flashing the ROM? As in should the ROM not have the boot.img inside of it when being flashed?
Boomchaos said:
Is there a particular order in flash the boot.img vs. the main rom? And should I have taken out the boot.img from the ROM before flashing the ROM? As in should the ROM not have the boot.img inside of it when being flashed?
Click to expand...
Click to collapse
ROM first, then boot.img.
And no, flash as is or else you'll get errors.
CNexus said:
ROM first, then boot.img.
And no, flash as is or else you'll get errors.
Click to expand...
Click to collapse
Still restarting, and freezing up. Wifi works now though...baby steps haha.
Ok, i was looking for flashing a kernel on an Lg Optimus black (i do not own the device), but i really can't fins anything... Can someone be gentle with me and explain how to plug the device in fastboot mode and flash the kernel.... I work with the Xperia devices and there the life is easier xD. So the questions are:
1)Where can i find the drivers USB?
2)How to plug the device in fastboot mode??
3)How to unlock bootloader
and i think that when i achived those passages i know how to go on... maybe like this:
1- Enter in the folder with fastboot's files inside
2- press shift + right-click and then select open command prompt here
3- Type: fastboot flash boot boot.img
am i wrong?? Please tell all the things that can be helpfull, but only for me, maybe for others noobs like me that dosen't know anything about this device this post i think the can be very helpfull for lots of people. :laugh:
Thank you guys and for your time
p.s.: Sorry, for bad english
Enri1196 said:
Ok, i was looking for flashing a kernel on an Lg Optimus black (i do not own the device), but i really can't fins anything... Can someone be gentle with me and explain how to plug the device in fastboot mode and flash the kernel.... I work with the Xperia devices and there the life is easier xD. So the questions are:
1)Where can i find the drivers USB?
2)How to plug the device in fastboot mode??
3)How to unlock bootloader
and i think that when i achived those passages i know how to go on... maybe like this:
1- Enter in the folder with fastboot's files inside
2- press shift + right-click and then select open command prompt here
3- Type: fastboot flash boot boot.img
am i wrong?? Please tell all the things that can be helpfull, but only for me, maybe for others noobs like me that dosen't know anything about this device this post i think the can be very helpfull for lots of people. :laugh:
Thank you guys and for your time
p.s.: Sorry, for bad english
Click to expand...
Click to collapse
You can google these questions too..
Sent from my A2 using xda app-developers app
NC4777 said:
You can google these questions too..
Click to expand...
Click to collapse
but i can't find it out!!! plz if someone else have to answer like this plz stay away... Man please if it was a joke this wasn't funny i really don't know how to flash a new f*****g kernel, to flash cm10.1 nightly
The Optimus Black doesn't use fastboot. Everything is done through recovery.
Download Clockwork Mod from the Play store, use that app to flash a custom recovery.
Enter recovery by repeatedly pressing volume down at power up or use a reboot to recovery app.
To flash roms/kernels, copy to your sd card, boot into recovery, select install zip.
The bootloader is not locked, unless you have flashed the offical LG ICS rom with the smartflash tool. If you have and want to unlock it, just flash any froyo/gingerbread offical LG rom with smartflash, that will unlock.
1. Make sure you are rooted, if not, read Nooby's how-to on how to do it. It's a sticky in LGP970 section on xda.
2. Once rooted, you can install ROM Manager and flash cwm/twrp recovery from there. Give it root permissions when asked for.
3. Boot into recovery using ROM Manager or any other third-party app. Flash the .zip for the kernel you want. Make sure it is compatible with the ROM you are using.
4. Once kernel flashed, boot into the system.
Bootloader is generally unlocked unless you are running official ICS on your OB. If that is the case, don't do any of the above mentioned steps as you will end in a boot loop.
If on official ICS, use Smart Flash Tool to flash unlocked bootloader. You can follow instructions here on jockjoint's thread
Once bootloader is unlocked and you have flashed su.zip as per instructions in the previouslsy mentioned thread, boot into recovery (it's already there in the unlocked bootloader flash).
Once in there, flash a compatible kernel and ROM as per your needs/liking.
Ok guys, this is a sureshot guide for
PROBLEM
* anyone wanting to decrypt their op3 but stuck at 1+ boot screen(Or not able to boot any custom ROMs.) and only able to restore twrp backups
* After using fastboot format userdata twrp and about phone shows only 32gb phone memory(where the hell is my rest of 32gb )
* Fastboot format userdata resulting in Stuck at boot screen or simply an unbrick trick to return to Stock OOS in unencrypted stage
SOLUTION
1. Use method 2 of Mega unbrick guide to restore your phone to stock partitions found here
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
2. After the flashing is complete do not reboot the phone instead reboot directly into bootloader.
3. In fastboot mode flash modded twrp 3.0.2.22 using command ''fastboot flash recovery recovery.img'' found here
http://forum.xda-developers.com/devdb/project/?id=15934#downloads
4. Reboot directly into twrp and using mtp mode copy latest elemental x kernel or bluspark kernel zip for OOS and SYSTEM supersu.zip into the internal storage. System supersu.zip here OR directly proceed to step 8
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.78-201609011115.zip
5. Now flash system supersu.zip and directly after that kernel.zip
6. Now again reboot to recovery directly and from twrp boot into system.
7. After boot up you system should be decrypted. You can check in security settings.
8.Reboot recovery and flash required firmware + modem zip found here
http://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
9.wipe data +cache +dalvik +system
10. Flash any rom of your choice and go flashoholic, use multirom or whatever you want.
Pheww. Thanks.
Man, Finally the SystemRoot (V4A, MultiROM etc) as we discussed a couple of weeks back with this hassle at the Mega Unbrick and Decrypt guides threads...:highfive:
I saw your post on MultiROM but maybe it got moved I guess...
So are you able to cross flash anything now ?
thanks.
Ashtrix said:
Man, Finally the SystemRoot (V4A, MultiROM etc) as we discussed a couple of weeks back with this hassle at the Mega Unbrick and Decrypt guides threads...:highfive:
I saw your post on MultiROM but maybe it got moved I guess...
So are you able to cross flash anything now ?
thanks.
Click to expand...
Click to collapse
anything... even multirom works flawless.
I will give this a try, Or will try to Flash the EX then perform parts of this since they support Kexec, to see what works, I have data and lot of apps working them again is a real pita with my schedule...
Thanks but, this is basically what i have done to decrypt my op3, i just used the CypherOs ROM instead OxygenOs, fastboot format userdata, reboot to recovery, flash rom, flash elementalx, and i didnt flash Supersu(dont know if thats causing my problem, i dont think so), i also did fastboot format userdata without being stuck at boot logo and still no 32gb, dont know whats the problem
ach3fck said:
Thanks but, this is basically what i have done to decrypt my op3, i just used the CypherOs ROM instead OxygenOs, fastboot format userdata, reboot to recovery, flash rom, flash elementalx, and i didnt flash Supersu(dont know if thats causing my problem, i dont think so), i also did fastboot format userdata without being stuck at boot logo and still no 32gb, dont know whats the problem
Click to expand...
Click to collapse
its different fastboot format userdata causes this Dont know why. I suggest method in the OP. Read carefully and follow it.
nikhilsnigam said:
its different fastboot format userdata causes this Dont know why. I suggest method in the OP. Read carefully and follow it.
Click to expand...
Click to collapse
Aham, so the format userdata causes it, thanks for that. i want to ask you something, after restoring completely with Msmdownloadtool(method2) can i directly reboot to recovery then sideload CB 3.5.5 and then reboot to fastboot and continue with the tutorial? What im saying is my device is decrypted as long it doesnt boot, am i right?
ach3fck said:
Aham, so the format userdata causes it, thanks for that. i want to ask you something, after restoring completely with Msmdownloadtool(method2) can i directly reboot to recovery then sideload CB 3.5.5 and then reboot to fastboot and continue with the tutorial? What im saying is my device is decrypted as long it doesnt boot, am i right?
Click to expand...
Click to collapse
Yes you can but you will be encrypted again. so after msm method reboot fastboot and flash modded twrp. reboot recovery flash CB or OOS. flash supersu flash kernel. Agin flash twrp.img from recovery itself and reboot recovery. After that reboot system and you are good to go. Make sure you have enough system space before flashing supersu and kernel. frow twrp file manager delete unneeded system apps 1st. DO NOT REBOOT in between.
nikhilsnigam said:
Yes you can but you will be encrypted again. so after msm method reboot fastboot and flash modded twrp. reboot recovery flash CB or OOS. flash supersu flash kernel. Agin flash twrp.img from recovery itself and reboot recovery. After that reboot system and you are good to go. Make sure you have enough system space before flashing supersu and kernel. frow twrp file manager delete unneeded system apps 1st. DO NOT REBOOT in between.
Click to expand...
Click to collapse
But i need unlocked bootloader to flash twrp, so i guess i need to unlock after i use Msmdownload tool right?
ach3fck said:
But i need unlocked bootloader to flash twrp, so i guess i need to unlock after i use Msmdownload tool right?
Click to expand...
Click to collapse
your bootloader doesn't get locked
nikhilsnigam said:
your bootloader doesn't get locked
Click to expand...
Click to collapse
Sorry to bother you, but i have one more question, i used Msmdownloadtool before, but only in Qualcomm download mode, can i use fastboot or i have to boot to EDL(qualcomm download mode)? And again sorry for taking your time.
ach3fck said:
Sorry to bother you, but i have one more question, i used Msmdownloadtool before, but only in Qualcomm download mode, can i use fastboot or i have to boot to EDL(qualcomm download mode)? And again sorry for taking your time.
Click to expand...
Click to collapse
you have to use qualcomm download mode by switching off your phone. pressing vol up button and connecting to usb.
nikhilsnigam said:
you have to use qualcomm download mode by switching off your phone. pressing vol up button and connecting to usb.
Click to expand...
Click to collapse
Yeah, i know that, thanks a lot, will try later all of this since i have no time now, will report how it went.Thanks!
Hello all, i unlocked the bootloader on the xiaomi mi A2 , and i was trying to follow this guide :https://forum.xda-developers.com/mi-a2/how-to/tutorial-camera2api-gcam-root-t3842475 to install the gmcam, but after the point 5. i just rebooted the phone from the recovery, just cause i wanted to try it, after that is stucked in android 8.1 animation, but i have access to the recovery (even if the tool shouldnt have installed it), but dunno what can i do from the recovery, and the device can go in fastboot mode but is not recognized by adb, what can i do?
What version of software was your Mi A2, if it was V9.6.13.0.ODIMIFE, then download the full stock ROM from here
http://en.miui.com/download-353.html
In fastboot mode, adb is not working, fastboot commands works there.
Extract boot.img from images of downloaded ROM.
Put the boot.img in adb folder.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
it should start normally
If not, then flash every image like in this post.
https://forum.xda-developers.com/showpost.php?p=77302899&postcount=4
minnuss said:
What version of software was your Mi A2, if it was V9.6.13.0.ODIMIFE, then download the full stock ROM from here
http://en.miui.com/download-353.html
In fastboot mode, adb is not working, fastboot commands works there.
Extract boot.img from images of downloaded ROM.
Put the boot.img in adb folder.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
it should start normally
If not, then flash every image like in this post.
https://forum.xda-developers.com/showpost.php?p=77302899&postcount=4
Click to expand...
Click to collapse
Thanks for the help, but, I don't know why, ADB driver were not working properly, didnt recognize the phone so I couldnt follow this guide, and i couldnt switch off the phone either, it was stuck in bootloop, the only thing I was able to do is to put the device in fastboot mode using the button combination..
Luckly the Mi Flash tool was able to recognize the device so I flashed the stock rom with that and now everything is back to normal, I've just a question, the phone sais that the bootloader is still unlocked, is that true? Even if I've flashed from zero the stock rom?
fuffy841 said:
Thanks for the help, but, I don't know why, ADB driver were not working properly, didnt recognize the phone so I couldnt follow this guide, and i couldnt switch off the phone either, it was stuck in bootloop, the only thing I was able to do is to put the device in fastboot mode using the button combination..
Luckly the Mi Flash tool was able to recognize the device so I flashed the stock rom with that and now everything is back to normal, I've just a question, the phone sais that the bootloader is still unlocked, is that true? Even if I've flashed from zero the stock rom?
Click to expand...
Click to collapse
Yep, it's true. You have to relock the bootloader, but this cause full wipe. IMO there's no need to relock the bootloader if you not enable the usb dev mode.
Also, theres an option in mi flash tool to lock the bootloader after flash. Something like flash_all_lock
DO NOT use flash_all_lock_crc. This will cause dead wifi and Bluetooth modem.
I am stuck on the exact same issue. Can you explain in detail all the steps you followed.
Mine was updated to September patch and it is Indian variant.
---------- Post added at 06:16 PM ---------- Previous post was at 05:31 PM ----------
rt1279_isBITW said:
I am stuck on the exact same issue. Can you explain in detail all the steps you followed.
Mine was updated to September patch and it is Indian variant.
Click to expand...
Click to collapse
Nvm I was able to flash that rom but now after the phone locks once the touch is gone until I reboot the device.
Are there any hardware differences in my indian variant or did I just flash it wrong?
I used flash_all.bat and clean all option.
Daniesz said:
Yep, it's true. You have to relock the bootloader, but this cause full wipe. IMO there's no need to relock the bootloader if you not enable the usb dev mode.
Also, theres an option in mi flash tool to lock the bootloader after flash. Something like flash_all_lock
DO NOT use flash_all_lock_crc. This will cause dead wifi and Bluetooth modem.
Click to expand...
Click to collapse
Nono i want to keep the bootloader unlocked, that's why I asked ! Thanks man.
Nvm I was able to flash that rom but now after the phone locks once the touch is gone until I reboot the device.
Are there any hardware differences in my indian variant or did I just flash it wrong?
I used flash_all.bat and clean all option
Click to expand...
Click to collapse
I used the same option, cause it didnt work with the other ones.. I didnt have any issue so far tho, and I dont know about hardware differences, but I dont think a bad flash can cause this kind of problem, not sure tho. Maybe now that everything is working try to flash again a stock rom.
Any help please Im stuck in a boot loop and recovery and fastboot are inaccessible, so i cant send any commands? im forking on Mac OS but even ive installed a virtual PC to try some of the countless programs but no seams to work since the phone is not recognized.
designlab said:
Any help please Im stuck in a boot loop and recovery and fastboot are inaccessible, so i cant send any commands? im forking on Mac OS but even ive installed a virtual PC to try some of the countless programs but no seams to work since the phone is not recognized.
Click to expand...
Click to collapse
Anyway, through recovery, you can do nothing, it's useless.
About fastboot mode, you should need to have the bootloader unlocked, if this is the case, then just be sure, that the fastboot drivers are properly installed and updated onto your Mac.
How did you get this?
SubwayChamp said:
Anyway, through recovery, you can do nothing, it's useless.
About fastboot mode, you should need to have the bootloader unlocked, if this is the case, then just be sure, that the fastboot drivers are properly installed and updated onto your Mac.
How did you get this?
Click to expand...
Click to collapse
Bootloader unlocked, flashed MIUI 13 without root it was working fine, unfortunately ive run this commands to obtain root, see if give me a clue...
fastboot flash vbmeta vbmeta.img
fastboot format userdata
fastboot flash boot recovery.img
fastboot boot recovery.img
After these commands im in a bootloop without access to recovery or bootloader.
any help will be appreciated
designlab said:
Bootloader unlocked, flashed MIUI 13 without root it was working fine, unfortunately ive run this commands to obtain root, see if give me a clue...
fastboot flash vbmeta vbmeta.img
fastboot format userdata
fastboot flash boot recovery.img
fastboot boot recovery.img
After these commands im in a bootloop without access to recovery or bootloader.
any help will be appreciated
Click to expand...
Click to collapse
you ****ed your devicewith those commands, now wait until dischaged and try to enter fastboot mode to flash stock miui, btw for magisk just flash twrp then magisk and done, where tf you get that "guide" to root" ?
designlab said:
Bootloader unlocked, flashed MIUI 13 without root it was working fine, unfortunately ive run this commands to obtain root, see if give me a clue...
fastboot flash vbmeta vbmeta.img
fastboot format userdata
fastboot flash boot recovery.img
fastboot boot recovery.img
After these commands im in a bootloop without access to recovery or bootloader.
any help will be appreciated
Click to expand...
Click to collapse
You just needed to boot to the custom recovery of your choice, then, when booting to it, flash it, and from there, if you want, or if it is required by the custom ROM of your choice, then format data, but it is not required for rooting purposes.
Anyway, check if you have access either, to download or fastboot mode and flash the stock ROM.
tutibreaker said:
you ****ed your devicewith those commands, now wait until dischaged and try to enter fastboot mode to flash stock miui, btw for magisk just flash twrp then magisk and done, where tf you get that "guide" to root" ?
Click to expand...
Click to collapse
Thanks i've got them from this F..k guide here i already waited for discharge even opened device and removed battery no luck, the thing is that i've done this twice in order to fix it previous time got help from a guy but can't reach him, i believe they fixed with a PC computer i'm using MAC not sure how to access download mode? can you explain in detail please!
SubwayChamp said:
You just needed to boot to the custom recovery of your choice, then, when booting to it, flash it, and from there, if you want, or if it is required by the custom ROM of your choice, then format data, but it is not required for rooting purposes.
Anyway, check if you have access either, to download or fastboot mode and flash the stock ROM.
Click to expand...
Click to collapse
can you explain in detail please! no accses to fastboot or recovery, im working on MAC no sure how to access download mode?
designlab said:
Thanks i've got them from this F..k guide here i already waited for discharge even opened device and removed battery no luck, the thing is that i've done this twice in order to fix it previous time got help from a guy but can't reach him, i believe they fixed with a PC computer i'm using MAC not sure how to access download mode? can you explain in detail please!
Click to expand...
Click to collapse
in mac? the more releable options and windows and linux to install the firmware and recover the device, i check that page, that one of the hundred fake pages to flash twrp, the real one is this ( the one i use ) twrp miui 13 RN10s btw try to get a windows pc and try this: hard brick guide to enter fastboot mode, unplug the battery then plug in again and press vol - and power until fastboot message apperas
designlab said:
can you explain in detail please! no accses to fastboot or recovery, im working on MAC no sure how to access download mode?
Click to expand...
Click to collapse
To send an MTK device to download mode, is pretty easy, you don't need, specially in newer devices, to open it, even in a bricked state, you can do it.
BUT probably, you need a Windows PC, booting in a virtual machine, not always works as expected, so you should need to do some of these things:
- If you have some space in your HDD/SDD, at least 35 GB available, reserve a partition for Windows, install, preferably Windows 10, your Mac is capable to dualboot with.
- Also you can use these "virtual" versions of Windows, not sure if it works, but worth it to try, burn the ISO/s, on a USB pen drive, or a SD card with its holder.
WPE4Live - Browse /WPE4Live with Chrome Browser+MediaPlayer at SourceForge.net
Customized Windows Live System for daily use
sourceforge.net
Hiren's BootCD PE
After that, follow this guide https://www.hovatek.com/forum/thread-37957.html
Thanks for your response, it seams like a mission but im willing to try, it seams like MTK devices are trouble!