[GUIDE]How not to brick your device - Sony Xperia S, Acro S, Ion

Everyday I see posts about people Bricking( Soft bricking/Hard Bricking) their Xperia S, Ion,AcroS or any other Xperia.Most of the times it is because people know that they have to flash or root or to unlock bootloader but do not have a clear information about what it actually means
I am creating this thread in order to tell you what the terminologies actually mean and how to avoid these bricks
First things you should know:
What is Android??
Android is basically a linux based kernel Operating System for your phones(We probably have heard it a gazillion times)
What it actually means?
Android is an operating system for phones built on a linux kernel. Linux is nothing but a clone of Unix Operating System which is another operating system like Windows. One main feature of Linux is that it is open source unlike windows.
Example of Linux kernel based OS for computer includes Ubuntu
What is kernel?
Kernel is nothing but a bridge between your hardware and Software
What it actually means?
Kernel controls your software according to your systems hardware.So on a computer if you press a key(eg:a) on keyboard. Kernel tells the OS that the key a has been pressed and to interpret it accordingly.So on a phone if you touch the home button,The kernel tells your OS that home button has been pressed and to take action accordingly.
So now comes the question.What if you flash an incompatible kernel?
Simple. Think of your computer having nothing but the monitor and without any working hardware.(I have a keyboard with a defective 'm' key,irritates the hell out of me)...Same happens to your phone. Even the booting process needs the kernel and hence you get the dreaded Soft-Brick...
What is bootloader?
Bootloader is a partition on your device that tells the phone with OS to load
What it actually means?
In Windows you see C:,D: etc..one of them contain your windows folder. In linux,it is different in name,not the concept. In linux based OS like Ubuntu, the partitions are /boot,/home,/root,/system,/recovery.....just like c:,d:,e: etc....
in android stock, you will have /boot,/system,/root.../boot is nothing but the bootloader...and in our sony phones this /boot aka bootloader is locked
What does bootloader contain?
bootloader as the name suggests tells your phone which os to boot..in our case it is the stock rom or custom or whatever os u have on the phone. Pretty self explanatory.
What is Flashmode and fastboot?
Flashmode as the name suggests is a mode which allows you to flash stuff(ROM's,kernel etc) on your phone
Fastboot mode: fastboot mode is another mode on your phone that allows you to flash stuff as well as debug it
What it actually means?
Flashmode: Pretty self explanatory
fastboot: It is used by both flashtool as well as ADB. fastboot allows you to test your kernel or whatever you are flashing..
command: fastboot boot boot.img
This command will boot boot.img(containing kernel/recovery or both and ramdisk) on your phone but wont flash it i.e. a test run. If boot.img doesnt boot,you can just disconnect and restart
command: fastboot flash boot boot.img
This command will flash the boot.img on your phone and then start it with the new boot.img.
Now fastboot wont work with a locked bootloader.So you cannot flash anything on your phone that requires a fastboot flash if your bootloader or /boot partition on your phone is locked
What is flashtool?
Flashtool is a tool developed and maintained by Androxyde, Bin4ry ,Doomlord. This tool lets you do a lot of things to your phone but its main usage is to flash stock Roms, kernels or anything that comes in an ftf package on your phone
What it means to you?
If anything goes wrong. The first thing you would need is this tool to revert back to Stock ROM. So keep this tool ready in case you are entering into the world of flashing custom firmware
What all can go wrong?
Frankly a lot of things(including power cuts,battery going dead)..
What you can avoid?
First thing,read read and read...A custom ROM would have a list of compatible devices..Go through the post and see if your device is listed. If your device
is listed and compatible then you can proceed. Flashing an incompatible ROM will result in a soft brick or hard,depending upon what you are flashing
>Next check if ROM requires a locked bootloader or unlocked(Important)
>Next if you are planning on unlocking bootloader, its better to flash CWM first on your phone and then flash ROM through CWM
What is CWM?
CWM aka Clockworkmod is a custom recovery that allows you to do a host of stuff including flashing of ROMs or zip packages
What it means to you?
Every phone has a recovery partition just like i told in the partition section. However, Latest Sony phones including Xperia S,ION,Acro S do not have one. Now most phones have a stock recovery system which allows users to reset their phones if something goes wrong. But, just like Custom ROMs, We have Custom Recoveries like CWM aka ClockworkMod developed by Koush that has many more options like flashing packages,taking a backup.
So basically CWM would be used by you to take a backup of your current system first and then flash the ROM. Now if anything goes wrong and you get a softbrick, you can just go to CWM and restore your backup and voila!!your phone will be back to normal again
Key Points:
1. CWM needs root
2. Recovery partition is not included in Sony.So, CWM is incorporated into the kernel itself by the kernel developer. What this means to us is that we would need an unlocked bootloader for installing CWM as we would have to flash the CWM included kernel to the boot partition
>Next, Always double check the requirements of the ROM you are going to install(Important)
Ohh before i forget...What is this ROOT everyone talks about?
ROOT is nothing but administrative access to sensitive parts of your OS
What it means to you?
It is nothing but getting admin rights to your system,in our case its our phones. you wont have root access on your phones by default. one major reason for this is safety. So that people don't delete a system file by mistake and what not
With root you can do everything with your phone. Thanks to our devs, we have loads of methods available to root your phone. Good place to search would be the search button
Why are we talking about root??
Because it might be a prerequisite for your custom ROM or a part of another prerequisite for installing your ROM.
>Now double check requirements again. And don't skip any step
>Once you have met all the requirements. Lets start flashing.
Ok now what can go wrong. First low battery..phone went dead while flashing..solution: Please charge it atleast while you finish the other requirements
Laptop crashes(Very Bad luck)..Solution: Always prefer to have the ROM installed through CWM and a backup ready. If you are lucky enough, you will be able to boot into CWM to restore backup and start again.
If you are flashing through any other method, then dont worry, have flashtool ready and your stock firmware..(Check firmware before installing if its for your phone:Very Important)
Check Exclude TA partition in flashtool unless absolutely necessary
Note: If your phone is bricked, it is always better to flash your kernel first(personal opinion), Once that is done, you can easily flash the full firmware
And please wipe cache and dalvik cache after flashing a ROM through CWM: Half the people wont perform this step and then try to find solutions for the bootloop. You can do this either through the CWM or ADB. For ADB method, just search the forum
One last thing and very very important. For Phones running stock firmware with unlocked bootloader or custom FW based on stock kernel with unlocked bootloader. Don't do an OTA update as this will hardbrick your device. Better download an stock FTF of that firmware version and flash it via flashtools
If still your phone bricks then there is a very nice thread here http://forum.xda-developers.com/showthread.php?t=1849170 by Toledo_JAB on bricked phone recovery
In the next post i will add some more information like TA partition backup, some more info about Android..etc.....
In case i have forgotten anything or have given the wrong info, please let me know so that i can add/edit the OP

Reserved

Last one

may i recomend mesaging a mod or admin to pin this thread or are you already on that
Sent From The ACP HQ

Envious_Data said:
may i recomend mesaging a mod or admin to pin this thread or are you already on that
Sent From The ACP HQ
Click to expand...
Click to collapse
No bro.this is my first thread so don't know how to get it stocked

Dark Wraith said:
No bro.this is my first thread so don't know how to get it stocked
Click to expand...
Click to collapse
just PM a mod with a kind message (mod names can be found above the threads in a section)
( i dont realy know how but thats what people talk of so i assume asking a mod is the only way to pin a thread
not to hard to miss ;D
Sent From The ACP HQ

Envious_Data said:
just PM a mod with a kind message (mod names can be found above the threads in a section)
( i dont realy know how but thats what people talk of so i assume asking a mod is the only way to pin a thread
not to hard to miss ;D
Sent From The ACP HQ
Click to expand...
Click to collapse
Haha.. I'll ask if people read the thread mate and benefit from it..till now no such enthusiasm so we'll see

nice
nice

Add: -Don't clear emmc under clockworkmod. ;D
-SnowKatana ^_^~

Good
very easy to understand, Nicely explained...
I just want to know what is hard brick?

Related

[Q] Kernels?

Hi, I'm new to kernels but I just have one question before I think about going ahead with flashing one. I want to flash the Doomlord kernel on my Xperia Play R800i but I want to know if after I've flashed it I can go back to the original stock kernel if I want to and how I can do this? Can anyone shed some light into this? - Thanks
Yes, you can
---------- Post added at 12:42 AM ---------- Previous post was at 12:36 AM ----------
http://forum.xda-developers.com/showthread.php?t=1176502
Doomkernel v14 for stock FW .42/.58/.62
DooMLoRD said:
[ how to get back to stock kernel OR older versions of my kernel (v06 and lower) ]
download the stock wifi modules update.zip
extract the kernel.sin (or boot.img if u want to flash my older kernels) file from the stock FTF u used to flash this fimware
save the kernel.sin (or boot.img if u want to flash my older kernels) in the folder with fastboot binaries (fastboot.exe files)
save the wifi modules update.zip to sdcard (on phone)
reboot phone and enter recovery
flash the stock wifi modules update.zip
power down device
start device in fastboot mode
use the following command to flash the kernel.sin (or boot.img if u want to flash my older kernels)
Code:
fastboot flash boot kernel.sin
reboot phone and thats it u should now be on stock kernel (or my older kernel)
Click to expand...
Click to collapse
FTF files can be found here http://forum.xda-developers.com/showthread.php?t=1589399
fareeed said:
Hi, I'm new to kernels but I just have one question before I think about going ahead with flashing one. I want to flash the Doomlord kernel on my Xperia Play R800i but I want to know if after I've flashed it I can go back to the original stock kernel if I want to and how I can do this? Can anyone shed some light into this? - Thanks
Click to expand...
Click to collapse
Hey mate, if you are a beginner in flashing kernals be sure you have Flashtool installe dand ready to go. The classic way is to download the fastboot files and flash kernals through CMD which may be a bit difficult as you have to learn the codes and shiz. but to make your life easier install this little handy tool called flashtool.
http://androxyde.github.com/Flashtool/
1) I know download speed may be dodgy but trust me, easiest tool to use! After installing head over to its directory files and inside the "drivers" folder Run the application "Flashtool-drivers.exe" and go on and install everything. (can take a long time). Then after run the program without your phone hooked up with USB debugging on click on the flash icon (the first option from left) chose fastboot mode. Click on Reboot into fastboot mode via ADB. Then press "Select Kernal to Flash" and chose the desired kernal you have downloaded and after a couple of seconds you are good to go. An alternative way is to switch off the phone, hold the search button and plug in the usb into the phone. If you have done this correctly the LED should turn blue on the phone.
2) If you didn't like what you have now with your phone, you can set everything back to the way it was before as if you have never touched the phone. kernal would go back to defult as well. It's a very simple process and can be done through "Flashtool" (Notice: you will lose everything however, not personal files like photos though if you chose to flash the whole FTF along with system files). Simply make sure the phone is switched off and set it into flash mode by holding down the "back" button and inserting the USB into the phone. The LED should turn green now. Again click on the flash icon in flashtool but this time select "flashmode".
Here you will be flashing a stock ftf file to put everything back to the way it was. Bootloader must be unlocked however. You can chose to only reflash the Kernal only or Kernal and everything else like the ROM and Baseband.
You can download the tft file here: https://rapidshare.com/files/698194045/R800i_4.0.2.A.0.62__1253-4437_.ftf
This is stock firmware baseband 64. Put the file into the folder named "firmwares" in the directory of flashtool program. Then carry on from my instructions and after selecting the "flashmode" you will be faced by a window showing the ftf file you are about to flash. On the right side you will see options and by leaving the "exclude kernal" option UNTICKED and all other options TICKED, you can have your Kernal set back to default. But you can do your own combination depending on what you'd like. Then press ok and the process will begin, I don't know how long it will take as I have never reverted back to ONLY the default kernal. I usually just flash the whole FTF file leaving all options unticked but the "Wipe use data" and "Wipe cache". If at this stage you didn't do the process of putting the phone into flash mode as I instructed earlier it's fine. A window would open showing you animated instructions on how to to do it now. then it should automatically carry on with the process.
Goodluck
arian009 said:
Hey mate, if you are a beginner in flashing kernals be sure you have Flashtool installe dand ready to go. The classic way is to download the fastboot files and flash kernals through CMD which may be a bit difficult as you have to learn the codes and shiz. but to make your life easier install this little handy tool called flashtool.
http://androxyde.github.com/Flashtool/
1) I know download speed may be dodgy but trust me, easiest tool to use! After installing head over to its directory files and inside the "drivers" folder Run the application "Flashtool-drivers.exe" and go on and install everything. (can take a long time). Then after run the program without your phone hooked up with USB debugging on click on the flash icon (the first option from left) chose fastboot mode. Click on Reboot into fastboot mode via ADB. Then press "Select Kernal to Flash" and chose the desired kernal you have downloaded and after a couple of seconds you are good to go. An alternative way is to switch off the phone, hold the search button and plug in the usb into the phone. If you have done this correctly the LED should turn blue on the phone.
2) If you didn't like what you have now with your phone, you can set everything back to the way it was before as if you have never touched the phone. kernal would go back to defult as well. It's a very simple process and can be done through "Flashtool" (Notice: you will lose everything however, not personal files like photos though if you chose to flash the whole FTF along with system files). Simply make sure the phone is switched off and set it into flash mode by holding down the "back" button and inserting the USB into the phone. The LED should turn green now. Again click on the flash icon in flashtool but this time select "flashmode".
Here you will be flashing a stock ftf file to put everything back to the way it was. Bootloader must be unlocked however. You can chose to only reflash the Kernal only or Kernal and everything else like the ROM and Baseband.
You can download the tft file here: https://rapidshare.com/files/698194045/R800i_4.0.2.A.0.62__1253-4437_.ftf
This is stock firmware baseband 64. Put the file into the folder named "firmwares" in the directory of flashtool program. Then carry on from my instructions and after selecting the "flashmode" you will be faced by a window showing the ftf file you are about to flash. On the right side you will see options and by leaving the "exclude kernal" option UNTICKED and all other options TICKED, you can have your Kernal set back to default. But you can do your own combination depending on what you'd like. Then press ok and the process will begin, I don't know how long it will take as I have never reverted back to ONLY the default kernal. I usually just flash the whole FTF file leaving all options unticked but the "Wipe use data" and "Wipe cache". If at this stage you didn't do the process of putting the phone into flash mode as I instructed earlier it's fine. A window would open showing you animated instructions on how to to do it now. then it should automatically carry on with the process.
Goodluck
Click to expand...
Click to collapse
Wow, thanks for the really detailed explanation! I've used flashtool but have never flashed a kernel before. Your instructions are really detailed and helpful, thanks. So to my understanding I can get my bootloader unlocked, flash a kernel, mess around, then just flash the stock .ftf and everything including the kernel would be back as if I'd never touched the phone and had just purchased it new? - Thanks
fareeed said:
Wow, thanks for the really detailed explanation! I've used flashtool but have never flashed a kernel before. Your instructions are really detailed and helpful, thanks. So to my understanding I can get my bootloader unlocked, flash a kernel, mess around, then just flash the stock .ftf and everything including the kernel would be back as if I'd never touched the phone and had just purchased it new? - Thanks
Click to expand...
Click to collapse
Yes that is correct! Everything will be changed back to the way it used to be, including Kernal, System files and so on. Although you can now even relock the bootloader using tools provided by blagus, the drm keys are not retrievable, just saying incase you care but those are complex stuff that doesn’t apply to you as it makes no difference to system performance. I don't even know why some people may want to be able to retrieve it. My phone's touch screen stopped working a few months ago and I simply flashed that tft and relocked the bootloader and seemed like my warranty was intact evidently, hence they fixed my phone
From my understanding you still haven't unlocked the bootloader. Although for me seemed difficult at first, I followed these instructions linked on this web link below and in no time you will be flashing kernals and Roms.
http://wiki.cyanogenmod.com/wiki/Sony_Ericsson_Xperia_Play:_Full_Update_Guide
Only follow the guide to the point you have unlocked the bootloader. It continues showing you how to flash CM7 which is kinda outdated now. lol
arian009 said:
Yes that is correct! Everything will be changed back to the way it used to be, including Kernal, System files and so on. Although you can now even relock the bootloader using tools provided by blagus, the drm keys are not retrievable, just saying incase you care but those are complex stuff that doesn’t apply to you as it makes no difference to system performance. I don't even know why some people may want to be able to retrieve it. My phone's touch screen stopped working a few months ago and I simply flashed that tft and relocked the bootloader and seemed like my warranty was intact evidently, hence they fixed my phone
From my understanding you still haven't unlocked the bootloader. Although for me seemed difficult at first, I followed these instructions linked on this web link below and in no time you will be flashing kernals and Roms.
http://wiki.cyanogenmod.com/wiki/Sony_Ericsson_Xperia_Play:_Full_Update_Guide
Only follow the guide to the point you have unlocked the bootloader. It continues showing you how to flash CM7 which is kinda outdated now. lol
Click to expand...
Click to collapse
Oh right thanks for the instructions, greatly appreciated

[Q] Bricked A100

Hello everyone,
I accidentally flashed using CWM recovery the stock rom and over it the Flexreaper ROM.
Now the problem:
Booting normally: Boot verified failed
Booting recovery: Recovery verified failed
Fastboot: Yes it works, but it's locked, can't flash anything.
ADB is not available.
Any suggestions how to fix this or get a unlocked bootloader again ?
Greetings, sniperfield
sniperfield said:
Hello everyone,
I accidentally flashed using CWM recovery the stock rom and over it the Flexreaper ROM.
Now the problem:
Booting normally: Boot verified failed
Booting recovery: Recovery verified failed
Fastboot: Yes it works, but it's locked, can't flash anything.
ADB is not available.
Any suggestions how to fix this or get a unlocked bootloader again ?
Greetings, sniperfield
Click to expand...
Click to collapse
Sounds like you locked your bootloader while on a modded rom? If that is the case you hosed it, sorry to say. You need access to fast boot or adb to fix it, if you have neither its locked for good.
OK one thing, did you try booting with update.zip and holding volume down + power?
With luck it will install the stock rom so you can start over.
Tapatalked from my Galaxy S II.
pio_masaki said:
Sounds like you locked your bootloader while on a modded rom? If that is the case you hosed it, sorry to say. You need access to fast boot or adb to fix it, if you have neither its locked for good.
OK one thing, did you try booting with update.zip and holding volume down + power?
With luck it will install the stock rom so you can start over.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
Yes locked bootloader + modded rom
update.zip doesn't work (how should it with a broken recovery ?)
but i which update.zip you mean exactly ?
Is there any hope with APX-Mode maybe ?
sniperfield said:
Yes locked bootloader + modded rom
update.zip doesn't work (how should it with a broken recovery ?)
but i which update.zip you mean exactly ?
Is there any hope with APX-Mode maybe ?
Click to expand...
Click to collapse
APX mode has so far proven completely useless for us, we don't have the SBK keys for our device.
The update.zip method is, partly, activated BEFORE recovery is, if you watch the bootloader text while booting up holding volume down, you'll see it look for update.zip before moving on to recovery, and TWRP and CWM don't look for it on their own, unless its something extra just on our versions of the those recoveries.
If fastboot DOES work, the only thing I can really suggest is attempt flashing CWM recovery.img, but of course, the bootloader will likely block it. You could also attempt to flash the bootloader blob again, which will accept fastboot oem unlock, but the normal method is through android's system, not fasboot.
...or hell just throw fastboot oem unlock at it anyways. If the bootloader is still the same, just locked, they may just unlock it. If the bootloader was replaced, it won't work either.
Good days;
I also have a tablet brick from yesterday. And I am very angry. Tape-worm the tablet with CWM and for supues the unblocked bootloader. Tape-worm installed this room http: // forum.xda-developers.com/showthread.php? T=1574897 and empece to having problem with CWM, since not me leia the external card SD for what not podia to do backup, or to load a new rom. at the time I put to look and lei, that was a problem probably of compatibility of the card SD or that was returning to realize again everything the process of unfreezing of bootloader. and this way I did it. again this process, which was the same that it uses previously and I me work. Http: // forum.xda-developers.com/showthread.php? T=1557445.
I restart the tablet, and from this moment, have the logo of green maple tree, and a phrase of red color that he says: " recovery verified failed .... " it does not start the tablet, and it does not also leave me to enter the recovery. if I try to enter the recovery this message goes out for me.
Erasing cache before SD update...
SD update cmd: recovery -
update_package=SDCARD:update.zip
Booting kernel recovery image
please, I am driven to despair, have tried flashear with different roms, with distitnas cards mike SD, with formats in fat, fat32 and ntfs. and do not manage to do anything. I have tried to install again everything across the PC, but the PC neither recognizes me the tablet, when I connect it to the PC, even the connection of the usb nor is heard, since this one does not manage to be ignited completely. And I am not going to take her to the SAT to whom receive from me 100 €, , Since for other 100 € mas I buy myself the new nexus. but it gives me great anger, because really I like a heap this tablet and it was going less than two weeks with her. Please, to say to me what should be, if necesitais mas information, to say it to me. Thank you very much
pio_masaki said:
APX mode has so far proven completely useless for us, we don't have the SBK keys for our device.
The update.zip method is, partly, activated BEFORE recovery is, if you watch the bootloader text while booting up holding volume down, you'll see it look for update.zip before moving on to recovery, and TWRP and CWM don't look for it on their own, unless its something extra just on our versions of the those recoveries.
If fastboot DOES work, the only thing I can really suggest is attempt flashing CWM recovery.img, but of course, the bootloader will likely block it. You could also attempt to flash the bootloader blob again, which will accept fastboot oem unlock, but the normal method is through android's system, not fasboot.
...or hell just throw fastboot oem unlock at it anyways. If the bootloader is still the same, just locked, they may just unlock it. If the bootloader was replaced, it won't work either.
Click to expand...
Click to collapse
can you please give me a exact link for a update.zip ? there are so many different versions -.-
yes bootloader blocks recovery.img flash ...
how can i to flash a bootloader blob with locked fastboot ? ;o
tried already fastboot oem unlock, does not work, bootloader seems replaced
and thank you for trying to help me, if it's really bricked, i'm going to buy a nexus tablet 7 ;D

Installing CWM on LT26i on OSX

I've recently moved from windows to OSX and loving it so far, only problem is that even though I can follow how to install the CWM recovery perfectly fine while on windows, I am totally lost when it comes to OSX.
I tried following this guide:
http://forums.androidcentral.com/ne...-pc-linux-4-2-unlock-root-flash-recovery.html
but it seems even when i boot my phone in fastboot mode (blue light on while connected to usb), when i enter the commands in terminal i get stuck at <waiting for device>
I used to go from flashtool before but i have no idea how to do it on osx.
a few more details:
i have successfully unlocked the bootloader of my phone some months ago and I have been playing around with custom roms for a few months. Ive grown tired of it before and reflashed stock .55
apart from your unusual OS..
i think you should move this to Q&A section
anyway, i advice you to try TWRP recovery instead (goomanger is your friend)
kulapips said:
I've recently moved from windows to OSX and loving it so far, only problem is that even though I can follow how to install the CWM recovery perfectly fine while on windows, I am totally lost when it comes to OSX.
I tried following this guide:
http://forums.androidcentral.com/ne...-pc-linux-4-2-unlock-root-flash-recovery.html
but it seems even when i boot my phone in fastboot mode (blue light on while connected to usb), when i enter the commands in terminal i get stuck at <waiting for device>
I used to go from flashtool before but i have no idea how to do it on osx.
a few more details:
i have successfully unlocked the bootloader of my phone some months ago and I have been playing around with custom roms for a few months. Ive grown tired of it before and reflashed stock .55
Click to expand...
Click to collapse
mirhl said:
apart from your unusual OS..
i think you should move this to Q&A section
anyway, i advice you to try TWRP recovery instead (goomanger is your friend)
Click to expand...
Click to collapse
Yup wrong thread mate.
@mirhl: To install TWRP on the FOTA partition with GooManager you need a custom kernel, I don't think he has.
@kulapips: Your guide seems to be for Nexus 7 devices, I don't think it applies at all. About the question: Firstly, did you set up fastboot properly? There's a little guide for macs here. I can't confirm that it works, it seems so short to me. If I were you I'd just use VMWare or some other virtualization software to run a virtual Windows on your mac. Might be faster than looking for answers, OS X isn't the most popular OS for Android dev'ers. Like that you could use Flashtool and all the tools that are made for Windows, OS X might be a better OS but we just don't like Apple .
So if you've set up fastboot, you can fastboot a custom kernel. There's Advanced Stock ICS, Stock+, Forzaferrarileo, Elite... Those are the ones for .55 that I can think of off the top of my head. They all suffice, some have CWM, others have TWRP. If you want to have a certain kernel but with a different recovery, you could change the recovery in FOTA partition, although I can't confirm that all of those support this. Stock+ and Forzaferrari definitely do. I'm just pointing you in the right direction, I hope you find the threads I'm talking about in this forum.
DON'T flash the CWM recovery for locked bootloaders (thread by tommyrumbler or something), it's crap and you have an unlocked bootloader anyway, so just get the real deal and flash a custom kernel. If you were planning to install DooMLorD's JB leak, that's also a requirement.
thanks for moving the thread and the quick replies
maybe this might be easier, but before I used this guide to install CWM and worked flawlessly, i was actually thinking of maybe having the same process but for OSX
http://www.youtube.com/watch?v=tAotNyORw-s
I have considered just using VM's but I wanted to see for an OSX alternative.
Would it work to just flash an already rooted (or if possible one with recovery built in) .55 kernel?
PS
Yeah I get that asking for OSX tips on an Android forum is like shooting myself in the head

Afraid of bricking my phone, what should I be concerned?

Hello there,
So recently Ive been doing lots of crazy/funny stuff with my phone like testing different ROM and boot images. I'm trying to do things as secure as possible, reading lots of threads before attempting things and trying to make sanity checks on procedures I read here on XDA. Despite of that, Im still unsecure about some principles:
For what I got, on the process of phone booting from power ON, it all starts at boot ROM. Boot ROM then calls the bootloader. At this point I have the first question: These custom boot images we use to upload to phone are the bootloader, right? So, considering we are not touching boot ROM (at least its what I supose as I never saw any reference on how to change boot ROM), if I use fastboot and upload a wrong or bad boot image I will be able to restore another boot image. I mean, theres no danger of definetely bricking my phone while playing with boot images as boot ROM remains untouched?
When I use flashtool to upload ftf images it will flash everything, including the bootloader, right? Again, if I use a wrong/bad ftf file the Boot ROM remains untouched, so no danger of definetely bricking my phone?
Im tempted to test some Cyanogem fork for Xperia M (among other stuff) but need/want to have this sort of questions sorted out first.
Should I post such newb questionsl ike this in here or in the development section of forum?
Any clues?
Thanks
Sorry to be of no help(mostly because I dislike theory and like practice), but changing the bootloader using flash isn't possible because, at least I, have flashed 4.3 without unlocking bootloader.
About what part of XDA this should go on, it's probably the general discussion of XDA.
DanDare_77 said:
Hello there,
So recently Ive been doing lots of crazy/funny stuff with my phone like testing different ROM and boot images. I'm trying to do things as secure as possible, reading lots of threads before attempting things and trying to make sanity checks on procedures I read here on XDA. Despite of that, Im still unsecure about some principles:
For what I got, on the process of phone booting from power ON, it all starts at boot ROM. Boot ROM then calls the bootloader. At this point I have the first question: These custom boot images we use to upload to phone are the bootloader, right? So, considering we are not touching boot ROM (at least its what I supose as I never saw any reference on how to change boot ROM), if I use fastboot and upload a wrong or bad boot image I will be able to restore another boot image. I mean, theres no danger of definetely bricking my phone while playing with boot images as boot ROM remains untouched?
When I use flashtool to upload ftf images it will flash everything, including the bootloader, right? Again, if I use a wrong/bad ftf file the Boot ROM remains untouched, so no danger of definetely bricking my phone?
Im tempted to test some Cyanogem fork for Xperia M (among other stuff) but need/want to have this sort of questions sorted out first.
Should I post such newb questionsl ike this in here or in the development section of forum?
Any clues?
Thanks
Click to expand...
Click to collapse
if u mean kernel as boot img....and rom as boot rom...
then answer is...u will get hardbrick....
kernel is most important to run a device...it should have correct hardware files or else urs will be gone[more than 80% to end up on hardbrick...]...
and in boot rom[rom or system files] only libs,etc are important ...libs has ur hardware related files to make work correctly and etc has some permissions,bluetooth files,ur partition info,etc[all only for ur phones for hardware]...if u place other device libs,etc u may get hardbrick or hardware wont work as usual....app,fonts,framework can be placed from any but it wont let you boot unless u know how to port...

TWRP recovery not working on Blackview BV9500

Hi everybody,
I try to root my Blackview BV9500 by installing first TWRP recovery. I use fastboot mode on a linux laptop to do that.
I successfully flash the twrp recovery image, but after that, the phone don't boot in recovery anymore.
It try to boot into recovery, but it reboot in normal mode a few second after.
I tried also with the cmd "fastboot boot recovery.img".
When i flash back the original recovery image, it work, i can boot the original recovery without any problem.
Does anyone have the problem?
Some one can help me to find a solution?
I, too, am trying to do this. I have not yet flashed it... I was going to use the fastboot boot command to boot the recovery kernel before permanently flashing it, to make sure it would work, and in my googling I stumbled across this post. Serendipity! [Edit 3: Although, reading your post again, I see you tried that as well and it didn't succeed for you. For me, it simply tells me remote: command not found, so how were you able to even get that to work?]
All that said... I have the BV9500 Pro, specifically for the two-way radio, so I'm going to try to keep that little tidbit of hardware working in the process. I mainly just want to tweak the menus a bit, tweak the quick settings, get root, delete the Google crapps I won't be using...
On to your problem, though, I can't help much but maybe if we post back and forth our successes and failures we might be able to stumble through it together?
First, I assume you already have unlocked your bootloader? [Edit: Honestly, I'm not sure flashing the recovery would be allowed without first unlocking the bootloader]
[Edit 2: Perhaps this thread might be of help. Different model, but often the hardwares used by manufacturers are similar enough that the same steps generally work. ]
Thank you for the link, maybe i need to flash the complete rom with the twrp recovery with spflash tools, and it will work.
I will try and let you know, but i will make a backup of my rom before flashing it!
For your problem with fastboot, maybee it's because you need to install it. You can use the command "sudo apt-get install fastboot" on a terminal window if you are on linux.
If you want to enter the recovery mode, you don't need to use fastboot, you can simply enter it by pressing Volume Up and Power buttons together for a couple of seconds when your phone is off.
When Boot Mode appears release all keys.
To flash recovery with fastboot, you need first to enable the developer mode on your phone (go to "Settings > About phone" and make 7th tap on the build number, the Developer options will be unlocked and available), and unlock the bootloader of course.
here what is the process i made to flash the recovery :
- i use the command "adb devices" to check if the phone is well connected. (response is like "BV9500S320001179 device")
- then i enter in fastboot mode with "adb reboot bootloader" (phone reboot and ask confirmation for fastboot mode)
- check with command "fastboot devices"
- unlock the bootloader with the command "fastboot oem unlock" or "fastboot flashing unlock".
- flash the phone with the twrp recovery with "fastboot flash recovery recovery.img"
- reboot the phone in recovery mode with "fastboot boot recovery.img"
Normally the phone boot in twrp recovery.
Hope that will help you too.
I am too facing this problem. In case you got any solutions please let me know too.
Yves596 said:
For your problem with fastboot, maybee it's because you need to install it. You can use the command "sudo apt-get install fastboot" on a terminal window if you are on linux.
Click to expand...
Click to collapse
Yup. Already had fastboot installed for the LG G5 this phone replaced, the Galaxy Note 4 the LG replaced, the MyTouch 4G Slide the Galaxy replaced, my wife's old Galaxy S5 I used in the interims... LOL, I've got a working install. No, the "Remote: command not found" was returned from within.... Whether fastboot or adb, I forget now, but I was able to get the file to flash eventually, after reading your first post, but unfortunately the phone would not boot to it (nor Android). I thought I'd bricked it. Twice this happened. Each time, after about 5 minutes, it eventually booted to Android.
I flashed the recovery from the ROM in the link Blackview sent me and was able to boot their recovery just fine, so there's something in the TWRP that my particular phone doesn't like.
If you want to enter the recovery mode, you don't need to use fastboot, you can simply enter it by pressing Volume Up and Power buttons together for a couple of seconds when your phone is off.
When Boot Mode appears release all keys.
Click to expand...
Click to collapse
Thanks, I keep forgetting which keys to hold for recovery versus bootloader, so I use the adb command to be sure without having to keep a notepad nearby.
Clearly I don't do this as often as I used to.
(snip)
- flash the phone with the twrp recovery with "fastboot flash recovery recovery.img"
- reboot the phone in recovery mode with "fastboot boot recovery.img"
Normally the phone boot in twrp recovery.
Hope that will help you too.
Click to expand...
Click to collapse
Now that was something I haven't done since the T-Mobile G1 days. My understanding was that you CAN boot a recovery without flashing it first if you"fastboot boot {image filename}" but that didn't work for me either. I'm also assuming that the filename to flash can be anything because the device stores it to a partition, so it shouldn't have to be specifically "recovery-verified.img".
The recovery you have... Were you ever able to boot to it? If so, would you be willing to share a link to its download source, please?
I've got to run for a prior engagement, I'll check back later.
Thanks!
veronicadavis said:
I am too facing this problem. In case you got any solutions please let me know too.
Click to expand...
Click to collapse
I guess i find the reason why the modified recovery image won't boot.
I find an interesting information in a post of osm0sis (https://forum.xda-developers.com/showthread.php?t=2073775) were he say : "some newer MediaTek (MTK) devices use special image signing that adds a "BFBF" pre-header signature, so images will unpack/repack but most likely won't boot unless run through their internal signing tool."
After more search, i find an interesting publication (http://www.lieberbiber.de/2015/07/04/mediatek-details-partitions-and-preloader/) witch confirm that.
They say in conclusion of the publication :
"Yes, I can confirm that SignTool is able to add digital signature information to firmware images. Signed images have an additional header “BFBF” and some fluff which SP Flash Tool checks on a secure device. Apparently some manufacturers merely used the default MTK key for signing the images, making them no better off than a typical insecure MTK device."
So we have to find another way to install magisk to root it.
Root 9500/pro
Mine rooted already....you guys can check on 4pda russian forum
Note : do not use the 17.1 version of magisk there because after reboot the device will freeze if you resboot after twrp 1st install...instead flash 17.3+ or 18+ right after first install of twrp...
EDIT : dont mind the russian language in TWRP as you can change it to english once there
Yves596 said:
Hi everybody,
I try to root my Blackview BV9500 by installing first TWRP recovery. I use fastboot mode on a linux laptop to do that.
I successfully flash the twrp recovery image, but after that, the phone don't boot in recovery anymore.
It try to boot into recovery, but it reboot in normal mode a few second after.
I tried also with the cmd "fastboot boot recovery.img".
When i flash back the original recovery image, it work, i can boot the original recovery without any problem.
Does anyone have the problem?
Some one can help me to find a solution?
Click to expand...
Click to collapse
Hello I have same problem... Do you have that original recovery file? I don't have and I would like to get that back. Thanks.
DL this:
needrom. com/ download/bv9500pro- bv9500-root/ (delete spaces)
- Copy Magisk-v18.0.zip and disable_encryption_9500.zip to external SD-Card or OTG device
- backup your data from internal SD-Card
- do a factory reset and turn off phone without entering the setup guide after reboot, or wipe via recovery and power off
- Flash recovery.img using scatter.txt with SP Flash Tool
- boot into recovery with hold down vol + and power
- switch TWRP to your language and install Magisk-v18.0.zip and disable_encryption.zip
- reboot and update or install MagiskManager-v6.1.0.apk
Thanks to Jemmini from 4pda.ru
kanadali said:
DL this:
needrom. com/ download/bv9500pro- bv9500-root/ (delete spaces)
- Copy Magisk-v18.0.zip and disable_encryption_9500.zip to external SD-Card or OTG device
- backup your data from internal SD-Card
- do a factory reset and turn off phone without entering the setup guide after reboot, or wipe via recovery and power off
- Flash recovery.img using scatter.txt with SP Flash Tool
- boot into recovery with hold down vol + and power
- switch TWRP to your language and install Magisk-v18.0.zip and disable_encryption.zip
- reboot and update or install MagiskManager-v6.1.0.apk
Thanks to Jemmini from 4pda.ru
Click to expand...
Click to collapse
Thank you for your help and Jemmini help too, it work fine.
But on the firmware version 20180629.
Yves596 said:
Thank you for your help and Jemmini help too, it work fine.
But on the firmware version 20180629.
Click to expand...
Click to collapse
you can just download latest firmware and simply backup NVRAM etc with sp flash tool also flash with sp tool, you will have then working twrp with disabled encryption. there are tons of post regarding using sp flash tool on this forum
im using same phone and did these actions on first day and did not have any problem with twrp or magisk
Hi,
I've bought this phone in Pro version. I rooted my phone using needrom.com/download/bv9500pro-bv9500-root/ and adb after unlocking bootloader. Then I failed with errors. Then I used SPFlashTool in root mode with official 2018092919_s32v63c2k_jk_pro.rar rom (I don't find it anymore on the net but 1) I got it on Blackview official forum and 2) I have the file on my own PC) with format+Download and replace recovery with TWRP from Jemmini from 4pda.ru before flashing. OK.
Then I rooted again: format /data with TWRP, then install disable_encryption.zip, wipe dalvik, reboot on TWRP, then install Magisk, wipe dalvik, reboot normally.
Beware: TWRP is in Russian language at first boot, so to get it in English, first slide the first slide (allowing writing), then select 'Настройки', then the globe on top, then English, then 'Установитъ Язык'.
Hope this helps.
Then, this is my first rooted phone, so I plan to make a custom rom without Gapps (then maybe without Mediatek Ones and agold too) and remake all functionning with apps from Fdroid. Help needed on a manner of removing a system/vendor app properly. Help needed too to add V4A, as I could see max version supported is Nougat. I announce this here as my first post, but my project will be a full post. If someone want help please ask here or MP me
Note: an update of magisk is out (official 18.1), I installed it and my phone tells me a message that facial recognition was not working anymore then it only boots on TWRP... I reflashed it and my phone boots normally again. Wait and see...
Thanks to Jemmini from 4pda.ru again.
Bests Regards
nr0000000 said:
Hi,
I've bought this phone in Pro version. I rooted my phone using needrom.com/download/bv9500pro-bv9500-root/ and adb after unlocking bootloader. Then I failed with errors. Then I used SPFlashTool in root mode with official 2018092919_s32v63c2k_jk_pro.rar rom (I don't find it anymore on the net but 1) I got it on Blackview official forum and 2) I have the file on my own PC) with format+Download and replace recovery with TWRP from Jemmini from 4pda.ru before flashing. OK.
Then I rooted again: format /data with TWRP, then install disable_encryption.zip, wipe dalvik, reboot on TWRP, then install Magisk, wipe dalvik, reboot normally.
Beware: TWRP is in Russian language at first boot, so to get it in English, first slide the first slide (allowing writing), then select 'Настройки', then the globe on top, then English, then 'Установитъ Язык'.
Hope this helps.
Then, this is my first rooted phone, so I plan to make a custom rom without Gapps (then maybe without Mediatek Ones and agold too) and remake all functionning with apps from Fdroid. Help needed on a manner of removing a system/vendor app properly. Help needed too to add V4A, as I could see max version supported is Nougat. I announce this here as my first post, but my project will be a full post. If someone want help please ask here or MP me
Note: an update of magisk is out (official 18.1), I installed it and my phone tells me a message that facial recognition was not working anymore then it only boots on TWRP... I reflashed it and my phone boots normally again. Wait and see...
Thanks to Jemmini from 4pda.ru again.
Bests Regards
Click to expand...
Click to collapse
It'd be great to have another rom but I'm facing a problem with battery life. Basically mobile network standby drains 5000mah battery every day i turned off from developer option but still problem is there. I have checked every single post on Google but nobody has solution for this. U guys face this problem too?
kanadali said:
It'd be great to have another rom but I'm facing a problem with battery life. Basically mobile network standby drains 5000mah battery every day i turned off from developer option but still problem is there. I have checked every single post on Google but nobody has solution for this. U guys face this problem too?
Click to expand...
Click to collapse
New update has been released today. It solves some battery issues, but be very careful.
I installed it, having TWRP and now I'm stuck in TWRP. I've tried to wipe everything but I'm still in TWRP.
I'll try SPFlashTool ... hope it works.
Everything restored & updated.
Using SPFlashTool I flashed all files included in 2018092919_s32v63c2k_jk_pro.rar (including original recovery instead of TWRP).
After that, Android booted and then, using OTA, I updated to latest version.
Reflected_God said:
New update has been released today. It solves some battery issues, but be very careful.
I installed it, having TWRP and now I'm stuck in TWRP. I've tried to wipe everything but I'm still in TWRP.
I'll try SPFlashTool ... hope it works.
Click to expand...
Click to collapse
Could you please send me the link? Can't find it on blackview forum
kanadali said:
Could you please send me the link? Can't find it on blackview forum
Click to expand...
Click to collapse
The latest version is not on the forum. I installed via OTA.
But if you mean the previous firmware, there is one link on the blackview forum: http://bbs.blackview.hk/viewtopic.php?t=480235#p795494
SP Flash tools are well documented here: https://forum.xda-developers.com/showthread.php?t=1982587
And a complete list of blackview bv9500 / bv9500 pro files and instructions (in russian): https://4pda.ru/forum/index.php?showtopic=931296
Hope you find what you are looking for.
@kanadali,
for the moment I'm not facing battery drain because there is not simcard in it at this state of my modifications, sorry.
@Reflected_God,
I think this is the link I used, I use the 2018092919_s32v63c2k_jk_pro.rar rom for base.
For all others who faces big problems like me (facial recognition not working then reboot on twrp only, I could reflash my phone with SPFlashTool, the rom and twrp from Jemmini/4PDA in russian only (others don't work for me). I used Format + Download in root mode on Linux. Then format /data with TWRP, then install disable_encryption.zip, wipe dalvik, reboot on TWRP, then install Magisk, wipe dalvik, reboot normally. Do other things. To remove gapps I disabled/force stop it before remove with TWRP. Others apps I can't disable simply remove with TWRP. I test if I encounter bugs but none for the moment. If someone wants to know what I do I've made a LibreOffice Calc sheet log, which evolve when I have time
Hope this helps
Bests Regards
Need Files or a GOOD guide. bv9500 NOT PRO.
If someone could upload the exact files that they used, and the exact same steps, that would be great. Please mention what stock version you have and a link to the image if possible as well. I've followed numerous different guides, with multiple different rom versions, multiple different recovery imgs, used sp flash tool and adb/fastboot multiple times, tried making sure everything was unlocked before each try, have all the necessary drivers, and the closest I get to a functional twrp recovery is a green line that appears at the top of the boot screen before it reboots. Ive tried going to the source, the russian site, but all of the links are 404ed. if not for me, then it would be great to just have this all in one place. Thank you please future hero.
Please include exact program versions (ex SP Flash) as well if not zips of them. I am sorry to be asking so much in one post however I truly didn't know what else to do. And I am typically very good with my google fu xD
I currently have build number BV_BV9500_V1.0_20181026. That seems to matter I believe.
I second the notion.
I have the pro model. I have considered rooting it, but honestly, the phone works well enough as-is without root (for me). However, I'd LOVE to be able to play with different ROMs on this device **AS LONG AS I CAN MAINTAIN THE TWO-WAY UHF TRANSCEIVER FUNCTIONALITY** (i.e. not some "needs-a-network-of-some-kind" "walkie talkie app" like Zello but the real UHF two-way), and I'd LOVE the ability to play with the files associated with the radio to really explore the hardware's capabilities.
Unfortunately, this phone seems more popular in [North]eastern Asia than anywhere else so I don't think we're likely to get much on this forum regarding it unless and until BV become a popular name in the western hemisphere.

Categories

Resources