[Q] What can we flash without risking a hardbrick? - One (M7) Q&A, Help & Troubleshooting

May you be saluted,
I just wanted to open a thread that helps people understand what they can flash without risking a hard brick. I know there are several threads concerning this particular problem but no one of them is complete. But before listing some examples I wanna clarify what is meant by saying Hardbrick Softbrick.
Softbrick:
You are able to boot your phone in a state where you can flash software, for example the bootloader.
Under this category goes:
-Flashing boot.img
-Flashing custom roms
-Flashing recovery.img
-Uninstalling system appilications
Hardbrick:
You can't boot into the bootloader and your device can't be recognized by your computer. This means you F***ed up your device!
-Rom Update Utilities, RUUs (especially wrong hboot)
-Bootloader, hboot
Logicalierwise bricks will only result if you flashed a wrong file or something went wrong like you accidentally unplugged your device while flashing. Now maybe I am wrong and this list is definitely not complete so I'd be happy if some of you added a few examples, I'll add them to my post. And finally I don't know what's about flashing RADIOs/Basebands... Can I try them out like boot.img? I mean really flash a **** into this partition?

LibertyMarine said:
May you be saluted,
I just wanted to open a thread that helps people understand what they can flash without risking a hard brick. I know there are several threads concerning this particular problem but no one of them is complete. But before listing some examples I wanna clarify what is meant by saying Hardbrick Softbrick.
Softbrick:
You are able to boot your phone in a state where you can flash software, for example the bootloader.
Under this category goes:
-Flashing boot.img
-Flashing custom roms
-Flashing recovery.img
-Uninstalling system appilications
Hardbrick:
You can't boot into the bootloader and your device can't be recognized by your computer. This means you F***ed up your device!
-Rom Update Utilities, RUUs (especially wrong hboot)
-Bootloader, hboot
Now maybe I am wrong and this list is definitely not complete so I'd be happy if some of you added a few examples, I'll add them to my post. And finally I don't know what's about flashing RADIOs/Basebands... Can I try them out like boot.img? I mean really flash a **** into this partition?
Click to expand...
Click to collapse
I flashed a lot on my one, even hboot updates etc. but never had a hardbrick... As long as boot into hboot is possible you can en-brick everything.

Related

Questions before i root my G1

I bought a G1 2 days ago and i've been reading a lots of tutorials on how to root the phone, i have hacked/Modified every phone i've had so far (Motorola/Sony Ericsson/Nokia) and i would like to do the same with my G1 (That;s why i bought it for) the problem is that every tutorial i see wants me to downgrade to RC29 which isn't complicated but the problem is that it has the DMD64 update.
1- Is the rooting process the same for DMD64 or do i need something special to downgrade? i read about the goldcard but i also heard it was not necessary all the time.
2- Since this is my first time rooting , is there a way to make sure i don't brick my phone? like making a backup of the OS or whatever i need to fix it in case i brick it.
3-What are the latest/best files to root it things like Recovery, ROM, SPL (i don't fully understand what this is and how it is different from the recovery)
Thank You.
Frodcord said:
I bought a G1 2 days ago and i've been reading a lots of tutorials on how to root the phone, i have hacked/Modified every phone i've had so far (Motorola/Sony Ericsson/Nokia) and i would like to do the same with my G1 (That;s why i bought it for) the problem is that every tutorial i see wants me to downgrade to RC29 which isn't complicated but the problem is that it has the DMD64 update.
1- Is the rooting process the same for DMD64 or do i need something special to downgrade? i read about the goldcard but i also heard it was not necessary all the time.
2- Since this is my first time rooting , is there a way to make sure i don't brick my phone? like making a backup of the OS or whatever i need to fix it in case i brick it.
3-What are the latest/best files to root it things like Recovery, ROM, SPL (i don't fully understand what this is and how it is different from the recovery)
Thank You.
Click to expand...
Click to collapse
1: I have no idea if the rooting process is the same for DMD64 or not, but I do not see why it would be any different. But, I could be wrong. I was lucky enough to have RC29 when I purchased mine.
2: The only thing that you can do to make sure you do not brick your phone is to FOLLOW EACH STEP CAREFULLY! Do not skip steps, or add your own. This mainly applies to flashing the Radio and SPL. If you f*ck that up, you're bricked, heh.
3: This confused me at first as well.
What is a SPL? The SPL, or Second Program Loader, in conjunction with the IPL comprise a device's bootloader. Aside from bootstrapping Android, the bootloader also fulfills various diagnostic functions. One of these functions is the manipulation of data in the device's internal flash ram. Depending on the SPL installed, the user can apply a signed NBH file, flash nand images, and more. Note that the SPL is installed and operates independently of the Android build that runs atop it.
Click to expand...
Click to collapse
The recovery is kind of like pressing F8 when you are booting into Windows. It lets you make changes to your system, w/o booting the the complete Operating System (The Android OS in this case). Using the recovery menu, you can flash new ROMs, format your SD card, enable the USB Mass Storage so you can see the SD card within windows, do a factory reset on the device, open up a terminal to manually input commands, perform a backup of your device (you can back up most everything on it) which allows you to restore from that backup if you mess something up.
But, then there is your FastBoot screen as well. FastBoot is where you need to be to flash your SPL and Radio. I am not 100% sure as to the correct order of the flashing off the top of my head, but google around (or simply search this forum), and you will find all the info you need.
Not all ROMs require you to have the "Danger/Haykuro/Death SPL" though. Many of them will work on a stock SPL. However, if you do feel the need to try one of the ROMs that require you to use the Death SPL, you can find all the information about it here: http://code.google.com/p/android-roms/wiki/SPL.
Good luck with your new G1, and do NOT be afraid to ask for help if you need it. Nobody likes to see one of these devices get bricked
Thanks a lot for helping me I thought that the recovery was the f8 in a computer too but I still have my doubts about the spl and the radio. I'll try to root my phone tomorrow i'll give you guys an update after I get to 1.5.
Wish me luck xD.
Frodcord said:
Thanks a lot for helping me I thought that the recovery was the f8 in a computer too but I still have my doubts about the spl and the radio. I'll try to root my phone tomorrow i'll give you guys an update after I get to 1.5.
Wish me luck xD.
Click to expand...
Click to collapse
Remember, always RADIO BEFORE THE SPL. If you do decide to mess with SPL, make sure to flash engineering (or hard) first, and then flash Danger/Death SPL thru fastboot. This eliminates 99% chance of the brick.
Good luck.
borodin1 said:
Remember, always RADIO BEFORE THE SPL. If you do decide to mess with SPL, make sure to flash engineering (or hard) first, and then flash Danger/Death SPL thru fastboot. This eliminates 99% chance of the brick.
Good luck.
Click to expand...
Click to collapse
Lol how is he going to know what fastboot/adb is? OP, don't mess with the SPL and radio until you know what your doing. Flash a rom like cyanogen or Enom's AOSP if you don't want to mess with them.
Ok I've done it i am running 1.5 now so if a person comes asking about DMD64 (G1) now you know what to say. You don't need a goldcard or something else just the dreaimg.nbh and there is nothing to worry about.
I still don't fully understand the SPL and Radio part so i'll keep reading until i am ready to use a custom ROM.
so just root DMD64 the normal way?

[Q] Please help me with a brick =)

Basically situation is as follows - I have a phone that bricked after FOTA. I can't flash any RUUs since the version inside is higher. Jtag does not help, after full erase and rebuild of literally everything the phone remains a brick and still wants a firmware version higher than I can give it.
A few things I would like to ask. How do I flash OTA update to this phone?
I can install CWM thus have adb, I do have fastboot, I can change CID (at the moment i ve made it 11111111) I can make S-OFF.
How to perform a clean install of a custom rom only?
I am sure it is a SW brick since I managed to run it after install of a custom rom. BUT I decided to flash stock after that, and I can't repeat procedure. Any help and suggestions are apreciated. Anything will be helpfull.
Download the ROM you want, go into your Recovery and wipe Cache, Data, Davlik Cache (and SDcard if you want to) and then mount the storage via recovery and simply copy the .zip to your SDcard and install it after unmounting it.
Of course know how to flash roms from CWM))).
Sv: [Q] Please help me with a brick =)
Try s-off your phone then install a ruu.exe file that fits your cid.
Sent from my HTC Sensation using xda premium
I did that. It seems there is a problem since the phone once was 2.33 version but the latest ruu I can find is 2.31. I managed somehow flash it 2.31, but that is about it.
I am going to try to flash custom from your signature, and make the phone s-off, again...
Well it must be some strange HW error, since software wise I ve done literally everything.
skas_2002 said:
I did that. It seems there is a problem since the phone once was 2.33 version but the latest ruu I can find is 2.31. I managed somehow flash it 2.31, but that is about it.
I am going to try to flash custom from your signature, and make the phone s-off, again...
Click to expand...
Click to collapse
The fastboot flashables stock zip files i have for 2.33 are:
Runnymede_2.33.415.1_ARA
Runnymede_2.33.707.1_Asia_WWE
Runnymede_2.33.1113.1_Thailand
If you want any of these, i can upload for u
Ty, I found everything. The phone is has some kind of hardware fault i think. Too much work at the moment, I will post result once I get to it.
e-MMC problem. Not software related, even though it looked extremely software related .
if needed do i have : RUNNYMEDE_ICS_35_S_2.37.709.1_hTC_Asia_TW

Good start ?

Hi all, glad to find this
I have ..., guess what ? a RAZR i (Ok, it's a friend's one) that I repaired changing the mad battery after factory resets didn't do anything. Then found OTA was available, applied and the RAZR i was 4.1.2 IIRC and the new battery went OK. My mistake, another OTA went soon, which I applied too, making the RAZR i a 4.4.2 kitkat piece of crap (no more write access to sdcard, this is well known ... by the ones aware , know I'm one).
Then I thought I could make the phone free and search the web for days to try to understand, found a french forum which said I can't do anything without unlocking the bootloader, what I did.
They directed me there to remove the boot-logo-warning but that's a razr hd thread and nothing worked for me. I can't remember where I read I should have CWM to do this, but as the french guy said he rather like twrp I didn't do anything at the moment, only failed to flash some logo from fastboot with various errors....
Well, I'm there, and it's cool because I hope this is the good place to have answers to questions that are still in my mind for years, and 2/3 new ones... fortunately they'll overlap and self-resolve once I get one. I'm not at all skilled in android, I only flashed a phone in 2010 and that's why I still have android SKD in my ubuntu (I also have a xp box, but I couldn't do anything for my old Acer LiquidMT). As you see, I'm a vintage things amateur (... okay, I'm vintage too).
Now the scene is built, please let me dare ask what still puzzles me :
1) For the Razr i 4.4.2 (french from sfr-vodafone kia20.74 now used with another carrier) do I have to search a specifically dedicated recovery ? Parsing this RAZR i Q&A, I found twrp seems to the preferred recovery, but I'd rather like to get confirmation from skilled ones, and also for version.
2) And please tell me if I'm wrong thinking the [RECOVERY] Unofficial TWRP 3.0.2-0 thread aim is to bring support to the RAZR i which is not supported by official teamw.in ? (BTW, @Hazou, the 1st link in the thread - DataMedia - is dead)
3) Assumed I have to go the TWRP way and I only have currently the stock recovery, do I guess right the only way is download img.zip and extract then do
Code:
./fastboot flash recovery recovery.img
, then only after that the phone can be rooted ?
4) You see I'm puzzled here because I still don't have understood the logical path: is this one the good ? unlock boot loader -> fastboot flash reco -> is the device rooted at this point ? If not, install su from recovery option "install zip from sdcard", then it's done and I get a so called "rooted stock ROM" ? Then only I can figure installing a custom ROM if exists for the RAZR i ?
5) And I should always flash a custom ROM based on the same 4.4.2 android release as my current stock one AND disable OTA updates ?
I read so many threads with guys having issues with hard-bricked RAZR i and all are about ICS and JB, so I wander the only custom are for ICS or JB, and still don't understand why they want to revert back.
Thanks for advices.
1stStep said:
Hi all, glad to find this
I have ..., guess what ? a RAZR i (Ok, it's a friend's one) that I repaired changing the mad battery after factory resets didn't do anything. Then found OTA was available, applied and the RAZR i was 4.1.2 IIRC and the new battery went OK. My mistake, another OTA went soon, which I applied too, making the RAZR i a 4.4.2 kitkat piece of crap (no more write access to sdcard, this is well known ... by the ones aware , know I'm one).
Then I thought I could make the phone free and search the web for days to try to understand, found a french forum which said I can't do anything without unlocking the bootloader, what I did.
They directed me there to remove the boot-logo-warning but that's a razr hd thread and nothing worked for me. I can't remember where I read I should have CWM to do this, but as the french guy said he rather like twrp I didn't do anything at the moment, only failed to flash some logo from fastboot with various errors....
Well, I'm there, and it's cool because I hope this is the good place to have answers to questions that are still in my mind for years, and 2/3 new ones... fortunately they'll overlap and self-resolve once I get one. I'm not at all skilled in android, I only flashed a phone in 2010 and that's why I still have android SKD in my ubuntu (I also have a xp box, but I couldn't do anything for my old Acer LiquidMT). As you see, I'm a vintage things amateur (... okay, I'm vintage too).
Now the scene is built, please let me dare ask what still puzzles me :
1) For the Razr i 4.4.2 (french from sfr-vodafone kia20.74 now used with another carrier) do I have to search a specifically dedicated recovery ? Parsing this RAZR i Q&A, I found twrp seems to the preferred recovery, but I'd rather like to get confirmation from skilled ones, and also for version.
2) And please tell me if I'm wrong thinking the [RECOVERY] Unofficial TWRP 3.0.2-0 thread aim is to bring support to the RAZR i which is not supported by official teamw.in ? (BTW, @Hazou, the 1st link in the thread - DataMedia - is dead)
3) Assumed I have to go the TWRP way and I only have currently the stock recovery, do I guess right the only way is download img.zip and extract then do
Code:
./fastboot flash recovery recovery.img
, then only after that the phone can be rooted ?
4) You see I'm puzzled here because I still don't have understood the logical path: is this one the good ? unlock boot loader -> fastboot flash reco -> is the device rooted at this point ? If not, install su from recovery option "install zip from sdcard", then it's done and I get a so called "rooted stock ROM" ? Then only I can figure installing a custom ROM if exists for the RAZR i ?
5) And I should always flash a custom ROM based on the same 4.4.2 android release as my current stock one AND disable OTA updates ?
I read so many threads with guys having issues with hard-bricked RAZR i and all are about ICS and JB, so I wander the only custom are for ICS or JB, and still don't understand why they want to revert back.
Thanks for advices.
Click to expand...
Click to collapse
Hey 1stStep,
A lot off assumptions and questions. And most of them are right.
1. Afaik there are 2 recoveries for the RAZR I. Stock and my build TWRP 3.0.2-0 unofficial. (Thanks for the heads up about the link)
2. Answered in 1.
3. Yep. If your bootloader is unlocked it gives u the function to flash non-stock firmware to the phone. Stock firmware are signed to prevent normal users flashing wrong firmware. Firmware consist of a couple of images. Those images contain data for the partition, just like in your PC. Every image does something else. Most known are boot, data, system, recovery and cache. There are many more. Some needed, some unnecessary.
To answer your question: when u have flashed the TWRP recovery u override the stock one. The TWRP can flash zip files and images to the most known device partitions. From here on u can flash a superuser zip(gives root access on the current ROM/system). Make sure u have the right superuser zip. There are many.
4.
Path to root on stock:
Unlock bootloader->install custom recovery (TWRP)->install superuser zip->reboot and test root on device
Path to custom ROM:
Unlock bootloader->install custom recovery (TWRP)->install ROM zip and extra's if needed like (Gapps(needed for Google playstore and more))->reboot and play with your new ROM.
Off course if u already have the bootloader unlocked and installed a custom recovery, u can skip those.
In the recovery u can also make backups, called nandroid backup. Read up on them and everything u wanna do.
5. The only thing u never want/should do is flashing Android 4.0.4 stock firmware without prior modifications. This is because from 4.0.4 to 4.1.2 there was a change in bootloader (the thing u unlock). If u go back it corrupt a part of the firmware which is difficult to overcome or even impossible without some factory stuff. Everything above 4.1.2 is save. And can always be flashed. The latest stock is 4.4.2 (KIA 20.74) and latest available custom ROM is 4.4.4 (CM11 or soon Lineage 11).
Good luck!
Thanks so mush great dev to spend time and even surely repeat yourself (hope you're not under stress) for a newb.
In your answer for path to custom ROM you say "Unlock bootloader->install custom recovery (TWRP)->install ROM zip and extra's if needed like".
Do I have to understand custom ROMs are yet rooted (OOTB), or root yet made on stock will survive flashing the custom (I though flashing a custom was some kind of infant clear brain graft?
BTW, is it general good advice to test recovery before flashing? I found this in Moto Play unofficial recovery 3.0.2-r5 from Vache:
Code:
fastboot boot recovery.img
?
Thanks again
1stStep said:
Thanks so mush great dev to spend time and even surely repeat yourself (hope you're not under stress) for a newb.
Click to expand...
Click to collapse
Not at all , just replying if I have some time.
1stStep said:
In your answer for path to custom ROM you say "Unlock bootloader->install custom recovery (TWRP)->install ROM zip and extra's if needed like".
Do I have to understand custom ROMs are yet rooted (OOTB), or root yet made on stock will survive flashing the custom (I though flashing a custom was some kind of infant clear brain graft?
BTW, is it general good advice to test recovery before flashing? I found this in Moto Play unofficial recovery 3.0.2-r5 from Vache:
Code:
fastboot boot recovery.img
?
Thanks again
Click to expand...
Click to collapse
- Most custom roms are prerooted.
- Cyanogenmod/LineageOS are prerooted
- Root installed by a zip will not survive any system flashing (rom flashing)
- Any modification to your system partition will not survive and system flashing (rom flashing), though 1 exception:
- installed gapps package (google apps/play store etc.) will survive system flashing on cyanogenmod based roms. But only when updating the rom to a newer version on the same android version. So:
CM11 version 1 to CM11 version 2. (because of a special script in the install zip)
Pre testing a boot or recovery image is blocked on our bootloader. So u can't do it. It's a shame they did it. Working on any boot or recovery changes is a pain in the spoken ass.
If u flash the recovery with:
Code:
fastboot flash recovery recovery.img
there is nothing to be afraid off. The TWRP 3.0.2-0 recovery is well tested on this device.
Thank you again man for all detailed answer.
You're right, it's a shame all these locked things in our phones. I'm sure the guys that agree (our security, blah blah) with these ways to do won't be so happy the day their computers will be locked the same way.
bye bye Hazou.
[Edit] .... hmmm, how long does it take to flash? Yet a 1/4h elapsed and razr still says "Flashing recovery..."
Please, what is the md5 of the image (not the zip, this you give us)? Thanks
[Edit] : Downloaded twice and get md5sum 60dff26f3ee5e9338ee4a6f8cf7df098
but still same forever Flashing recovery ...
[Edit] : I've been puzzled for days being stuck in endless "Flashing recovery ..."
In the ended I decided, after saying 1 hour waiting a hypothetical "success/congrats message", NOT QUITTING the current fastboot screen, to select the recovery option in this very fastboot menu (on a Razr i : Vol- to highlight recovery item, then Vol+ to select) and bang I was in TWRP menu. What to do next once in, it is another story.

How do I install a custom ROM?

Hey XDA users,
My only experience with Android device modding was installing TWRP, SuperSU and CyanogenMod on my SM-T530. It seems that all modding information for my current phone is so scattered that I don't know where to start...
From what I have are telling me that I should unlock bootloader, flash an fstab.qcom file and flash a no-verity kernel before I go on flashing a custom ROM, but is it enough or I need something more than just those steps? I know how to make backups, but how different is it between different Android devices?
I know that I have to use ODIN for Samsung devices, but for Motorola, do I just use Fastboot to flash images?
There is a guide to getting twrp and root going here:
https://forum.xda-developers.com/moto-e5/how-to/guide-root-twrp-moto-e5-play-explained-t3856182
Once you have twrp you can flash roms from there. Instructions are usually included in each rom thread.
Will Rickards said:
There is a guide to getting twrp and root going here:
https://forum.xda-developers.com/moto-e5/how-to/guide-root-twrp-moto-e5-play-explained-t3856182
Once you have twrp you can flash roms from there. Instructions are usually included in each rom thread.
Click to expand...
Click to collapse
Thank you
c) Cause the Device to overheat, explode and/or catch fire, exceed SAR values,
exceed safe volume settings, and otherwise be unsafe, including creating the potential to
cause serious bodily injury, including death (while we understand this may seem harsh,
we do not know what you will do with the device once it is unlocked, and/or how it will
function if its software is altered, and therefore we want you to understand the potential
dangers)Íž and
Click to expand...
Click to collapse
Wait, can a device really overheat, explode or exceed SAR values when in custom ROM?

TWRP-Installation went badly wrong....

Hello Guys!
My device:
Redmi Note 9 Pro (European)
Bootloader-Status: Unlocked ✓
Root-Status: rooted ✓
Recovery-System: doesnt work x
Fastboot-Mode: does work ✓
As described above i stupidly flashed the wrong TWRP version to my device. Now i end up in a bootloop with the error code "System has been destroyed" and i can't get into the system anymore. Another big problem is that the device can't detected/recognized anymore by any console using adb and the Mi-Flash-Tool also can't see it as well ...
Does anyone have any solution or ideas for my problem? I bought the phone recently and don't have enough money to buy another ...
I would even pay money for the solution.
Someone said i have to flash the stock partitions back again. But which tool/method allows it me to flash the stock partitions back again? I have no idea how to flash ANYTHING without using adb or recovery mode ...
Thank You In Advance
"System Has Been Destroyed" means only three possibilities:
Partition SUPER has been modified,
Partition VBMETA has been modified,
or Partition CUST has been modified.
Just flash the stock partitions back again, but from the same version already present on the device.
VD171 said:
"System Has Been Destroyed" means only three possibilities:
Partition SUPER has been modified,
Partition VBMETA has been modified,
or Partition CUST has been modified.
wefawefdcwea
Just flash the stock partitions back again, but from the same version already present on the device.
Click to expand...
Click to collapse
ok thank you very much so far! I can see it's not possible to flash stock partitions using adb. can you tell me which tool or method i have to use to flash the stock partitions back again?
You can't flash partitions using adb.
Try spflashtool.
So was busy the whole day finding a solution.
My goals so far:
-installing spflashtool
-installing drivers for spflshtool
However i don't find any site where to download/buy stock partitions for redmi phones ...
Can you suggest a source for them? Are custom firmware's and custom ROM's the same ?
Have a nice day!
{Mod edit: Quoted post has been deleted}
I spent almost the last day watching videos on youtube on it and i wouldn't post something here if i had found someting....
Can You at least please tell me - Are custom firmware's and custom ROM's the same ?
All steps for spflashtool are same for all devices.
Keep trying.
Can You at least please tell me - Are custom firmware's and custom ROM's the same ?
Thats all in have to know....
you simply have to reflash your stock firmware again, Google your device firmware and phone Model, or search your model on androidhost.ru and flash using something like team mt multitool

Categories

Resources