Can't Install 03-15-2016 OTA Update - Blu Pure XL

Not sure if anyone else got the notification from Blu's "Wireless Update" tool about the update they released for the Pure XL. I didn't see any posts here about it. I'm currently unable to install the update, I keep getting this message about that "my system is damaged." And when I try to manually apply the downloaded update it fails.
I unrooted my phone, flashed the stock recovery, and even factory restored the phone. Short of reflashing a stock ROM I'm not sure what else to do to try and apply this update. I'd rather just wait for a Cyanogenmod ROM at this point than waste my time doing that. Anyone have any other ideas?

uchua said:
Not sure if anyone else got the notification from Blu's "Wireless Update" tool about the update they released for the Pure XL. I didn't see any posts here about it. I'm currently unable to install the update, I keep getting this message about that "my system is damaged." And when I try to manually apply the downloaded update it fails.
I unrooted my phone, flashed the stock recovery, and even factory restored the phone. Short of reflashing a stock ROM I'm not sure what else to do to try and apply this update. I'd rather just wait for a Cyanogenmod ROM at this point than waste my time doing that. Anyone have any other ideas?
Click to expand...
Click to collapse
You must also flash the stock boot and stock system then do a factory reset and it will let you install the update. Same thing happened to me last night and I finally figured it out. You can find the stock boot, stock recovery and stock system images in the development thread.

uchua said:
Not sure if anyone else got the notification from Blu's "Wireless Update" tool about the update they released for the Pure XL. I didn't see any posts here about it. I'm currently unable to install the update, I keep getting this message about that "my system is damaged." And when I try to manually apply the downloaded update it fails.
I unrooted my phone, flashed the stock recovery, and even factory restored the phone. Short of reflashing a stock ROM I'm not sure what else to do to try and apply this update. I'd rather just wait for a Cyanogenmod ROM at this point than waste my time doing that. Anyone have any other ideas?
Click to expand...
Click to collapse
Maybe it could have been a change made to the system by a 3rd party root application/xposed module you had installed prior to factory resetting (if you had any)?
That's all I can think of. If nothing else works, then you can just leave it be if you don't want to reflash stock ROM. The update is just to fix some bugs, so unless you were experiencing any of the issues listed in the update notes, you don't really need it.

droidboy29 said:
You must also flash the stock boot and stock system then do a factory reset and it will let you install the update. Same thing happened to me last night and I finally figured it out. You can find the stock boot, stock recovery and stock system images in the development thread.
Click to expand...
Click to collapse
I'm having the same issue as OP. I have the stock boot and stock system images...so is that all I need? Can I just flash them through ADB like I did with the recovery?

viol3t said:
I'm having the same issue as OP. I have the stock boot and stock system images...so is that all I need? Can I just flash them through ADB like I did with the recovery?
Click to expand...
Click to collapse
I believe you can flash them through fastboot and believe me the update is worth it. When you have a blu phone you take any update you can get lol.

droidboy29 said:
You must also flash the stock boot and stock system then do a factory reset and it will let you install the update. Same thing happened to me last night and I finally figured it out. You can find the stock boot, stock recovery and stock system images in the development thread.
Click to expand...
Click to collapse
I'm unable to find the stock boot, stock recovery or stock recovery images. I'm new here, hopefully you point to where they are? Also I'm sure there's a step-by-step thread on how to do the stock boot and so on?

mrjamesb36 said:
I'm unable to find the stock boot, stock recovery or stock recovery images. I'm new here, hopefully you point to where they are? Also I'm sure there's a step-by-step thread on how to do the stock boot and so on?
Click to expand...
Click to collapse
They are on page 23 of the development thread on this blu pure XL forum and you can either flash them through fastboot or flash them via SP flash tool using the gionee e8 or condor alure scatter text which both of those can be found in the development thread.

droidboy29 said:
They are on page 23 of the development thread on this blu pure XL forum and you can either flash them through fastboot or flash them via SP flash tool using the gionee e8 or condor alure scatter text which both of those can be found in the development thread.
Click to expand...
Click to collapse
thank you! I'll get on it right away

Hey all, I am sorry if this has been gone over before but I am getting an error when attempting to flash system.img through fastboot. Recovery and Boot (from page 23 development) flashed fine but when I flash the extracted system.img I get "load_file: could not allocate -1283457024 bytes Error: cannot load 'system.img'" I tried restarting fastboot but have not gotten past this error. Any ideas?

rkeene said:
Hey all, I am sorry if this has been gone over before but I am getting an error when attempting to flash system.img through fastboot. Recovery and Boot (from page 23 development) flashed fine but when I flash the extracted system.img I get "load_file: could not allocate -1283457024 bytes Error: cannot load 'system.img'" I tried restarting fastboot but have not gotten past this error. Any ideas?
Click to expand...
Click to collapse
You can try to flash your system.img using SP Flash Tool instead of fastboot. If you don't already have it, you can grab a copy, along with the scatter file for the phone from the Gionee E8 ROM (It's the Chinese variant, but specs and partition scheme are the same).
Make sure to deselect everything first (this is important, as you only need to flash system.img, and nothing else) and click the box under "location" for the "system" row to browse for your own system.img to flash (otherwise you'll accidentally flash parts of the Gionee phone to your phone)

droidboy29 said:
You must also flash the stock boot and stock system then do a factory reset and it will let you install the update. Same thing happened to me last night and I finally figured it out. You can find the stock boot, stock recovery and stock system images in the development thread.
Click to expand...
Click to collapse
how do you flash the system? i used fastboot to flash recovery and boot ,but when i try to flash system it give me error like the "target max download size..." is there other way to flash system.img?

I don't want to be that guy, but just a thought: Would it be too much to aggregate this information in a thread?
ALL BLU IMAGES, ROOT PROCESS, NECESSARY ROOT FILES
Or something. It seems really stupid to just constantly tell people oh, hey, lol it's on page 13 good luck. Just set up a master post and link this stuff. Hell, if I find some time I'd do it.

I too had the same issue. I looked a bit through the app and I was able to retrieve a list of all files it compares when determining if the system is "damaged".
It seems their update app checks the sha1 hash of certain files versus expected hash.
I have attached a log file from their update app which contains a list of all the files it checks (and their expected hashes).
The most important line is:
2016-03-30 02:51:15=======FotaUpdate: FotaUpdatenPackageUnzipAndCheck, checkResult = install-recovery.sh$libart-compiler.so$libart.so$libart.so$
This is a list of all files (split by '$') that do not match the expected hash.

I formated internal sd, removed sdcard1 and flashed recovery and system imgs and when the device is updating on the recovery it says "Error" with the droid and the exclamation red sign, what else can i do ?

Figured out how to update the phone
Flashed Stock BOOT and RECOVERY with Fastboot
Flashed Stock SYSTEM with SP Flash Tool
Data/Factory format including Internal Storage
Update without errors!

rkeene said:
Hey all, I am sorry if this has been gone over before but I am getting an error when attempting to flash system.img through fastboot. Recovery and Boot (from page 23 development) flashed fine but when I flash the extracted system.img I get "load_file: could not allocate -1283457024 bytes Error: cannot load 'system.img'" I tried restarting fastboot but have not gotten past this error. Any ideas?
Click to expand...
Click to collapse
Had the same issue, but i remember i did it each one by one til they worked.

superti3000 said:
how do you flash the system? i used fastboot to flash recovery and boot ,but when i try to flash system it give me error like the "target max download size..." is there other way to flash system.img?
Click to expand...
Click to collapse
Flash everything through SP flash tool it's just easier. Open SP flash tool click on scatter file, load the gionee e8 scatter file. Once that is done click on the top check mark to deselect all the fields. Double click on boot field and load stock BLU boot image, double click on recovery field and load stock BLU recovery image then double click on system and load stock BLU system image. Shut your phone off, plug your USB cable into your computer and hit download on SP flash tool. Now hold volume down on your phone while plugging your USB cable into the phone, you will see a red line for a few seconds at the bottom of SP flash tool. The line will then turn yellow and start counting the percentage of the flash. Once it has finished you will get a green check mark that says successful or something like that. You can then unplug your phone do a factory reset. Then once you go through all the start up stuff you can do the OTA update with no problems. SIDE NOTE: I lost my IMEIs doig the factory reset so make sure you have them written down somewhere in case you lose them and need to re-input them. There are Google videos on how to do that.

droidboy29 said:
Flash everything through SP flash tool it's just easier. Open SP flash tool click on scatter file, load the gionee e8 scatter file. Once that is done click on the top check mark to deselect all the fields. Double click on boot field and load stock BLU boot image, double click on recovery field and load stock BLU recovery image then double click on system and load stock BLU system image. Shut your phone off, plug your USB cable into your computer and hit download on SP flash tool. Now hold volume down on your phone while plugging your USB cable into the phone, you will see a red line for a few seconds at the bottom of SP flash tool. The line will then turn yellow and start counting the percentage of the flash. Once it has finished you will get a green check mark that says successful or something like that. You can then unplug your phone do a factory reset. Then once you go through all the start up stuff you can do the OTA update with no problems. SIDE NOTE: I lost my IMEIs doig the factory reset so make sure you have them written down somewhere in case you lose them and need to re-input them. There are Google videos on how to do that.
Click to expand...
Click to collapse
I did that but i got some error right after it turn red, it dindt turn yellow for like 10 secs and this pops up
BROM ERROR: S_DL_GET_DRAM_SETTING_FAIL (5054)
anything else i could try? i see alot people get it, all they said is that make sure you choose the right system.img and i did download it again
no luck
Kevin
thanks for your help btw

superti3000 said:
I did that but i got some error right after it turn red, it dindt turn yellow for like 10 secs and this pops up
BROM ERROR: S_DL_GET_DRAM_SETTING_FAIL (5054)
anything else i could try? i see alot people get it, all they said is that make sure you choose the right system.img and i did download it again
no luck
Kevin
thanks for your help btw
Click to expand...
Click to collapse
You should probably be working with the stock system image that you downloaded from this forum and the scatter file called "MTK6795_Android_scatter.txt". Try re-downloading either or both the stock system.img or the Gionee E8 firmware if you want to be sure that that isn't the issue first.
If you are still having issues, try to download and use USBDeview to uninstall every device that has to do with MediaTek, then plug in your Pure XL and boot it up to allow your computer to reinstall those devices.
Assuming you're on Windows, if that doesn't work, when you boot up your phone while it's plugged into your computer, try checking the MediaTek port that has "PreLoader" in its name (I forgot the exact name) that shows up under "Ports (COM + LPT)" in Device Manager. If you see it show up with an exclamation mark and it's Device Status in its Properties say something like "cannot start (error 10)", you may have to restart your Windows without Driver Signature Enforcement.

Short Circuit said:
You should probably be working with the stock system image that you downloaded from this forum and the scatter file called "MTK6795_Android_scatter.txt". Try re-downloading either or both the stock system.img or the Gionee E8 firmware if you want to be sure that that isn't the issue first.
If you are still having issues, try to download and use USBDeview to uninstall every device that has to do with MediaTek, then plug in your Pure XL and boot it up to allow your computer to reinstall those devices.
Assuming you're on Windows, if that doesn't work, when you boot up your phone while it's plugged into your computer, try checking the MediaTek port that has "PreLoader" in its name (I forgot the exact name) that shows up under "Ports (COM + LPT)" in Device Manager. If you see it show up with an exclamation mark and it's Device Status in its Properties say something like "cannot start (error 10)", you may have to restart your Windows without Driver Signature Enforcement.
Click to expand...
Click to collapse
Thank you so much, USBDeview is the one that worked for me tried so many different thing and it didnt work at all.

Related

[Q] How to revert back to stock everything without root on GT-i9020T?

How do I revert back after one-click root to the stock everything including radio, rom, build, etc. I am currently running Cynagon mod RC1 7 and have had numerous issues, I would just like a clean, simple cut answer so I can give this to someone for the holidays, any help would be mightly appreciated, as i've asked this in the past and can never seem to get a clear cut answer, thanks.
wierd165 said:
How do I revert back after one-click root to the stock everything including radio, rom, build, etc. I am currently running Cynagon mod RC1 7 and have had numerous issues, I would just like a clean, simple cut answer so I can give this to someone for the holidays, any help would be mightly appreciated, as i've asked this in the past and can never seem to get a clear cut answer, thanks.
Click to expand...
Click to collapse
Just flash a full rom, it should restore the radio, the recovery, and the OS. Then do a reset to factory defaults if you are paranoid.
Get the proper rom for you phone here:
http://forum.xda-developers.com/showthread.php?t=1063664
If you're on T-Mobile, you have an i9020-T, this should work for you. It is the full 2.3.6 image.
http://android.clients.google.com/p...a25375426.signed-soju-ota-189904.1ada2537.zip
Is this also working if you're coming from stock unrooted ICS 4.0.3 ?
And
Is there any risk of loosing IMEI if you're going full ROM ?
mahanddeem said:
Is this also working if you're coming from stock unrooted ICS 4.0.3 ?
And
Is there any risk of loosing IMEI if you're going full ROM ?
Click to expand...
Click to collapse
I have reverted back from 4.0.3 yesterday by reflashing the full 2.3.6 rom without any issues. I'm not sure I understand what you mean by losing IMEI.
My phone works just fine after doing this (more than once!).
pcbroch said:
Just flash a full rom, it should restore the radio, the recovery, and the OS. Then do a reset to factory defaults if you are paranoid.
Get the proper rom for you phone here:
http://forum.xda-developers.com/showthread.php?t=1063664
If you're on T-Mobile, you have an i9020-T, this should work for you. It is the full 2.3.6 image.
http://android.clients.google.com/p...a25375426.signed-soju-ota-189904.1ada2537.zip
Click to expand...
Click to collapse
Ok here's my problem i did the ics update earlier before you told me this and still having issues, now when I go to recovery I get a android with his chest open with a red caution sign on it...how could I just format everything, essentially make it the way it was out of box so I could start over...because of all the issues I'm currently having.
When you get to that point, you need to hold down power then press vol up. Then you will be able to flash the zip. You need to put the zip on the phone first though, unless you have CWM recovery, in which case you can mount the sdcard section and move it across then, and flash it after.
OK thanks...Just please let's summarize this
1.You were on I9020T bone stock , unrooted
2.You had GB 2.3.6
3.You updated manually (or OTA) to 4.0.3
4.You decided to revert to GB 2.3.6
5.You used exactly the same method of manual update (stock recovery after copying the .zip file and in this case the full ROM of 2.3.6 to SD)
6.You followed the stock recovery steps and chose the .zip 2.3.6..
7.After everything was setup , you booted into GB 2.3.6 without any problems
Is that right ? or better if you make the exact detailed steps you did to revert to GB 2.3.6 would be apreciated
Thanks
furiannn said:
When you get to that point, you need to hold down power then press vol up. Then you will be able to flash the zip. You need to put the zip on the phone first though, unless you have CWM recovery, in which case you can mount the sdcard section and move it across then, and flash it after.
Click to expand...
Click to collapse
Tried, but then I get this error:
--Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
assert failed: !less_than_int(1316544229. getprop("ro.build.date.utc"))
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
Any help?
I think u need a custom recovery to be able to revert back to gingerbread
Sent from my Nexus S using XDA App
Raver27 said:
I think u need a custom recovery to be able to revert back to gingerbread
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
how would I go about flashing the custom recovery? I tried to flash another full rom package with the recovery in it and like i said i got that error...
Do you have a folder in windows where you have been flashing stuff from, using fastboot?
If so, just get this recovery image http://forum.xda-developers.com/showthread.php?t=988686
Download either the blue or green 5023 image. Doesnt matter which just changes colour of mod place the file in the same folder as the fastboot.
Next, with the phone off and after attaching the phone to USB, turn it on while pressing vol-up and power. You should see the boot option screen, the fastboot screen. Leave the phone there.
Now go back to cmd window in windows, and browse to the folder where you have all the fastboot files and where you have put the above image file. Then type in the following:
fastboot flash recovery <image name.img> (without the < >)
press enter and it'll flash the recovery and then you can install the old version of android
furiannn said:
Do you have a folder in windows where you have been flashing stuff from, using fastboot?
If so, just get this recovery image http://forum.xda-developers.com/showthread.php?t=988686
Download either the blue or green 5023 image. Doesnt matter which just changes colour of mod place the file in the same folder as the fastboot.
Next, with the phone off and after attaching the phone to USB, turn it on while pressing vol-up and power. You should see the boot option screen, the fastboot screen. Leave the phone there.
Now go back to cmd window in windows, and browse to the folder where you have all the fastboot files and where you have put the above image file. Then type in the following:
fastboot flash recovery <image name.img> (without the < >)
press enter and it'll flash the recovery and then you can install the old version of android
Click to expand...
Click to collapse
I don't believe I have a folder as such, being a person who is not familiar with the lingo, etc of all this i rooted it with one-click mod, and just flash things through this, are you saying I can flash things externally? sorry to sound like a bum, but i'm trying to understand thanks.
No problem, we're all noobs once, hell i still am and only just coming to terms with it all! Just need to do a bit of researching, but heres the basics...
fastboot lets you flash stuff to the phone from windows, when the phone is attached to the USB and is in fastboot mode (just turned on, from vol-up/pwr).
Can unlock the boot loader and flash recovery images from there. Once thats done, most other stuff can be done from within the new recovery mode, clockworkmod being the one that everyone uses.
over at nexusshacks it's explained really well how to root your phone. And he provides a zip with everything you could want. That zip is the folder I was talking about in the last post. It comes with drivers to install when you first plug the USB in and the PC recognises the phone. Download the pack, install them drivers and then go back to my last post and take it from there
http://downloadandroidrom.com/file/NexusS/rooting/nexussrootnew.zip
EDIT: Also do a full wipe/data reset just before you flash the new rom
furiannn said:
No problem, we're all noobs once, hell i still am and only just coming to terms with it all! Just need to do a bit of researching, but heres the basics...
fastboot lets you flash stuff to the phone from windows, when the phone is attached to the USB and is in fastboot mode (just turned on, from vol-up/pwr).
Can unlock the boot loader and flash recovery images from there. Once thats done, most other stuff can be done from within the new recovery mode, clockworkmod being the one that everyone uses.
over at nexusshacks it's explained really well how to root your phone. And he provides a zip with everything you could want. That zip is the folder I was talking about in the last post. It comes with drivers to install when you first plug the USB in and the PC recognises the phone. Download the pack, install them drivers and then go back to my last post and take it from there
http://downloadandroidrom.com/file/NexusS/rooting/nexussrootnew.zip
EDIT: Also do a full wipe/data reset just before you flash the new rom
Click to expand...
Click to collapse
I'm using clockwork right now, but it seems to be corrupted, im running 4.0.3 right now on a full rom package, so your saying I should still do this? I think i may have done all that before, as the phone is rooted, but I used the one-click method instead.
Just download that file and then you'll have what you need on your pc to do what i mentioned above. Plug the phone in and reflash the new recovery which will not harm it, and then you'll be able to stick gingerbread or ICS back on. You gotta try things out otherwise you'll not understand what is going on. I dont know of any one click thing that will let you go back to default as it was before. After it flashes the new recovery, scroll down to "recovery" on the screen and press the power button, dont restart the system.
In hindsight, while the one click methods are easy to use, theyre getting used by people that dont do the necessary research to learn about the rooting and flashing process. This means you end up skipping so much that you learn about the whole rooting and flashing proocess when doing it manually, which in turn means you have more trouble getting out of it if you want it back to the way it was! No offence intended here, but you just need to man up and do it! All will be well

[Q]Help: Can't change custom rom

Hi,
I am new to this site and fairly new to rooting and stuff and need assistance with my Sony Xperia S (LT26i). If i am not in the right pace for this please point me in the right direction. I have installed a custom rom and custom recovery which let me upgrade from 4.1.2 to 4.3 which was working fine then when I flashed a different custom rom after that to get 4.4.1 I lost access to my custom recovery. The main issue is that I need help with changing the custom rom I have installed, for some reason I can no longer boot into TWRP or CWM (using power + vol up), the phone simply boots normally and skips the whole process therefore I cannot flash anything. I have looked for hours over the net on how to get into recovery but could not find a solution.
I also assumed that when installing custom recovery and custom roms that you would need to be rooted but when I check with Root Checker it says that I am not. So any assistance would be great
Bizzmagizz said:
Hi,
I am new to this site and fairly new to rooting and stuff and need assistance with my Sony Xperia S (LT26i). If i am not in the right pace for this please point me in the right direction. I have installed a custom rom and custom recovery which let me upgrade from 4.1.2 to 4.3 which was working fine then when I flashed a different custom rom after that to get 4.4.1 I lost access to my custom recovery. The main issue is that I need help with changing the custom rom I have installed, for some reason I can no longer boot into TWRP or CWM (using power + vol up), the phone simply boots normally and skips the whole process therefore I cannot flash anything. I have looked for hours over the net on how to get into recovery but could not find a solution.
I also assumed that when installing custom recovery and custom roms that you would need to be rooted but when I check with Root Checker it says that I am not. So any assistance would be great
Click to expand...
Click to collapse
try to root again or if it wont work, back to stock and start from begining
Paget96 said:
try to root again or if it wont work, back to stock and start from begining
Click to expand...
Click to collapse
Thanks for the feedback, because I am quite new to this stuff can you tell me what the best and easiest way to root the phone is? I have tried the root toolkit but it wont work with my rom i have atm. I cant access my recovery either so how would I go about getting back to stock rom?
Bizzmagizz said:
Thanks for the feedback, because I am quite new to this stuff can you tell me what the best and easiest way to root the phone is? I have tried the root toolkit but it wont work with my rom i have atm. I cant access my recovery either so how would I go about getting back to stock rom?
Click to expand...
Click to collapse
you have all here
follow this,and back to stock, then root again, install cwm or twrp recovery, and install what ever you want
http://xperiafirmware.com/8-firmware/13-sony-xperia-s-lt26
Do you know of any other site where I can get the firmware from?, when I try and extract the file after I download it it's corrupted. I have tried multiple times with no luck.
Bizzmagizz said:
Do you know of any other site where I can get the firmware from?, when I try and extract the file after I download it it's corrupted. I have tried multiple times with no luck.
Click to expand...
Click to collapse
witch android do you want?
---------- Post added at 01:54 PM ---------- Previous post was at 01:51 PM ----------
Here is 4.0.4
https://docs.google.com/file/d/0B_d8uWGbkaetLThpYzEwZUh5aTg/edit
steps:
how to install the newest Android 4.0.4 for Sony XPERIA S LT26i
a) first of all, check your firmware version (if you already have the newest one, you do not need this tutorial)
b) download and install latest Flashtool from here (mirrors Google Drive or Mega)
c) download also latest Android 4.0.4 (mirror) for Sony XPERIA S LT26i
d) paste the ftf file downloaded in step c) to folder „Firmware“ included in the XPERIA Flashtool
e) open the XPERIA Flashtool, click on flash and choose downloaded firmware, than click ok. Important - if you do not want to delete any data of your phone, just uncheck flashing userdata.sin file. All data will remain in your phone, but sometimes it can cause additional troubles. So it is better (and I recommend that) to do the backup of your personal data, than proceed with clean instalation and then restore your personal data.
f) turn off your phone and when Flashtool shows pop up window, connect phone to PC with holding volume down button
g) after few minutes all is done and your phone gets the new firmware
Here you got 3 ways to update good luck
http://androidteen.com/xperia-s-lt26i-update-to-android-4-1-2-jelly-bean-official-firmware-6-2-b-1-96/
Ok so I successfully downloaded the firmware file but I got an error when using the flash tool, I have attached the log if you can maybe help me out with what went wrong.
Bizzmagizz said:
Ok so I successfully downloaded the firmware file but I got an error when using the flash tool, I have attached the log if you can maybe help me out with what went wrong.
Click to expand...
Click to collapse
The clue's in the error message - you don't have the required drivers installed.
There's a directory named "drivers" under the main flashtool dir. Run flashtool-drivers.exe and install the appropriate drivers. I think "Common Drivers Viskan Board" is the one you need. I ended up installing all of them to get it to flash (which took ages).
Ok so I got it to work, all I had to do was hold down the vulumn down button for like an extra 5 seconds while it began to flash
Thanks for the help, I appreciate it
Bizzmagizz said:
Ok so I got it to work, all I had to do was hold down the vulumn down button for like an extra 5 seconds while it began to flash
Thanks for the help, I appreciate it
Click to expand...
Click to collapse
work??
dont forget to press thanks
Hello again
So I have successfully rooted the device and installed TWRP but as before I cannot seem to get into the recovery mode, when I boot the phone with "power and vol +" it doesn't boot into recovery but instead there is a quick glimpse of what I think is the recovery mode (I cant actually see it but something happens for a split second) but it flashes past way too fast then goes to the normal Sony logo and continues booting normally. I have tried this like at least 20 times in the last 2 weeks and have researched other ways to boot into recovery but I can't seem to find anyone with an answer. Do you know what could fix this? Or is there a way to boot into recovery using a computer?
Bizzmagizz said:
Hello again
So I have successfully rooted the device and installed TWRP but as before I cannot seem to get into the recovery mode, when I boot the phone with "power and vol +" it doesn't boot into recovery but instead there is a quick glimpse of what I think is the recovery mode (I cant actually see it but something happens for a split second) but it flashes past way too fast then goes to the normal Sony logo and continues booting normally. I have tried this like at least 20 times in the last 2 weeks and have researched other ways to boot into recovery but I can't seem to find anyone with an answer. Do you know what could fix this? Or is there a way to boot into recovery using a computer?
Click to expand...
Click to collapse
use this to reboot into recovery
ang go to reply, because I dont see you post
https://play.google.com/store/apps/details?id=pl.qbanin.reboot

Root BLU VIVO IV KITKAT 4.4.2

i am not responsible for damaged devices though this may not happen warning Please make backup of system after installing recovery MTK tools for some odd reason due to lack of proper drivers wont detect ur phone
Hello to all BLU vivo iv users this thread is for gaining root access after updating your blu vivo iv to 4.4.2 usually it can't be rooted properly u can get root via recovery install method but root explorer and other root apps will not get proper su access but it won't work or will fail constantly to complete system operations meaning u can't edit system at all!!!:crying:
I made an insecure boot.img with more adb access seeing that it does not have much developer options in settings it still wont but this boot img will allow proper root.
first u must install Carliv recovery from here not my work this is for Gionee elife s5.5 but vivo iv is same device so it's safe tested myself :http://elifes55.blogspot.com/2014/07/guidegionee-elife-s55-cwmroot-required.html
use mobile uncle from market and update recovery choose recovery.img first item at top of the list the downloaded recovery img must be in base of internal storage do not place in any folders!!!
after that reboot to recovery vol up + power scroll with vol keys power to select scrool to install zip then scroll down to install from internal sdcard choose "bootimgADB.zip" wait for install to finish wipe dalvik and cache (ps when doing this it takes about a min or two idk why just dont panic and think your phone is stuck)
after that procedure continue to rooting using Vroot / root genius
Vroot: http://vrootdownload.org/
Root genius: http://www.shuame.com/en/root/
download root checker from market to check for root
Screenshot
https://www.dropbox.com/s/1iyfst24ye3bm1s/Screenshot_2014-08-21-10-48-26.png
update
please install supersu.zip after boot img flash in recovery then root over with root genuis
Thanks a lot for that information. There is not a lot of help aroudn for Vivo iv owners!!!
I have a problem before i reach 4.4.2, as the OTA update will not install correctly.
I have a rooted phone, with recovery installed.
I downloaded the OTA update, installed it, then it booted to recovery and gave the following errors:
CWM automade 10.07.20014 00:34:23
E:Invalid command argument
Finding update package...
E:unknown volume for path [/storage/sdcard0/adupsfota/update.zip]
E:Can’t mount /storage/sdcard0/adupsfota/update.zip
Installation aborted.
Any idea what this means? I tried unrooting my phone, and installing the OTA update again, but it gave the same error. I have emailed Blu, but i'm sure they will be unhelpful. I've tried googlin, and other people (with different devices) with similar errors from OTA updates say you cannot install the update.zip directly from recovery otherwise it gives:
assert failed: getprop("ro.product.device" == "**********" || "ro.build.product" == "*************"
E:Error in /sdcard/downloaded_rom/***********.zip
...errors. Which from some peoples replies also gets their phone stuck on bootloop, so I don't want to try that.
Any ideas how to get this OTA kitkat update installed? Did yours update normally (with.without root/recovery)?
Thanks in advance
James666PKR said:
Thanks a lot for that information. There is not a lot of help aroudn for Vivo iv owners!!!
I have a problem before i reach 4.4.2, as the OTA update will not install correctly.
I have a rooted phone, with recovery installed.
I downloaded the OTA update, installed it, then it booted to recovery and gave the following errors:
CWM automade 10.07.20014 00:34:23
E:Invalid command argument
Finding update package...
E:unknown volume for path [/storage/sdcard0/adupsfota/update.zip]
E:Can’t mount /storage/sdcard0/adupsfota/update.zip
Installation aborted.
Any idea what this means? I tried unrooting my phone, and installing the OTA update again, but it gave the same error. I have emailed Blu, but i'm sure they will be unhelpful. I've tried googlin, and other people (with different devices) with similar errors from OTA updates say you cannot install the update.zip directly from recovery otherwise it gives:
assert failed: getprop("ro.product.device" == "**********" || "ro.build.product" == "*************"
E:Error in /sdcard/downloaded_rom/***********.zip
...errors. Which from some peoples replies also gets their phone stuck on bootloop, so I don't want to try that.
Any ideas how to get this OTA kitkat update installed? Did yours update normally (with.without root/recovery)?
Thanks in advance
Click to expand...
Click to collapse
did u try choose zip from internal then update.zip but still try to get the update.zip for me
yes it would install with root but not custom recovery i kept my stock recovery cuz i knew blu would be releasing KITKAT btw amigo OS ruined KITKAT its like if it didn't update at all
hmm u have the answer at the start custom recovery may not install an official rom update though i may be wrong but if u can get the update.zip where it downloaded on your storage i can poke around and design it to flash via custom recovery
please in future do NOT!!!! install custom recovery before official update it gives probs
since u have the recovery there is an miui rom u can try to install from gionee elife s5.5 make sure u backup though its based on 4.2.2
thanks very much! I will upload the update.zip. I really only need kitkat for an app I am trying to use (which only works on 4.3 and newer) so the MIUI rom won't be of use to me.
If you could have a poke around and create a custom recovery that will boot it, that would be amazing, I will upload the update.zip now. I would forever be in your gratitude.
Also is there a way of removing custom recovery from the phone?
---------- Post added at 09:24 PM ---------- Previous post was at 09:18 PM ----------
P.S. yes I also tried to install from zip using the custom recovery, but it said it couldn't mount /sdcard0 or /system or anything when I tried. I think the best option is for me to find a method of removing my custom recovery?
Th elink to the KitKat 4.4.2 update.zip is here: http://we.tl/FGgNDO2ts2
It will only be available online until the 31st August, so if anyone wants to download it/play with it etc... then do so before then.
Thanks a bunch!
P.S. I've bricked my phone trying to mess around in CWM... hoping my nandroid backup restores properly!
James666PKR said:
Th elink to the KitKat 4.4.2 update.zip is here: http://we.tl/FGgNDO2ts2
It will only be available online until the 31st August, so if anyone wants to download it/play with it etc... then do so before then.
Thanks a bunch!
P.S. I've bricked my phone trying to mess around in CWM... hoping my nandroid backup restores properly!
Click to expand...
Click to collapse
so u finally bricked it just soft brick right ?
notice something strange it says it can't mount storage yet it backed up your rom it's probably just update script that needs tweaking
Possible Vanilla KITKAT rom
took rom from blu life 8 ported it it booted but got stuck on starting apps once boot.img seems to be giving the errors just have to pull boot from life 8
Pretty sure i've hard bricked it now
Tried to flash the update.zip using SP flashtool, but my phone wont even turn on/go to recovery now.. Computer detects it, but just a blank screen ... going to see if fastboot works, then try and manually install the boot.img etc...
---------- Post added at 01:32 AM ---------- Previous post was at 01:10 AM ----------
If anyone has any idea how I can unbrick my phone I would be all ears...
I have tried all combinations of buttons, but the screen just won't turn on. When I press power+volume up+volume down, the flash on the back, flashes once... but thats it... why is there no information about bricked vivo iv's or gionee elife s5.5's on the internet
James666PKR said:
Pretty sure i've hard bricked it now
Tried to flash the update.zip using SP flashtool, but my phone wont even turn on/go to recovery now.. Computer detects it, but just a blank screen ... going to see if fastboot works, then try and manually install the boot.img etc...
---------- Post added at 01:32 AM ---------- Previous post was at 01:10 AM ----------
If anyone has any idea how I can unbrick my phone I would be all ears...
I have tried all combinations of buttons, but the screen just won't turn on. When I press power+volume up+volume down, the flash on the back, flashes once... but thats it... why is there no information about bricked vivo iv's or gionee elife s5.5's on the internet
Click to expand...
Click to collapse
if the computer still detects it it can be saved so its not totally dead the update.zip wont install via sp tool there is a gionee firmware u can try but it might kill the phone with certain files will just have to uncheck them does sp tool detect ur phone? i backed up my 4.2.2 system.img i'll upload it and then u can try it on sp tool
taalibj01 said:
if the computer still detects it it can be saved so its not totally dead the update.zip wont install via sp tool there is a gionee firmware u can try but it might kill the phone with certain files will just have to uncheck them does sp tool detect ur phone? i backed up my 4.2.2 system.img i'll upload it and then u can try it on sp tool
Click to expand...
Click to collapse
I've tried responding to your PM, but my messages aren't being registered as sent!
If you did recieve them (2 now) awesome, if not, write me here and i'll respond.
I would love to use your 4.2.2 image if you ocudl upload it. I would be forever grateful!
4.2.2 system.img
well here it is https://www.dropbox.com/s/gd95xz06j2oy6pb/system.img?dl=0
you may need to rename it to android.img maybe but try system first
hey could u upload the drivers u used for ur phone i installed almost every driver known to man kind and mtk tools still doesn't recognize the device
taalibj01 said:
well here it is https://www.dropbox.com/s/gd95xz06j2oy6pb/system.img?dl=0
you may need to rename it to android.img maybe but try system first
hey could u upload the drivers u used for ur phone i installed almost every driver known to man kind and mtk tools still doesn't recognize the device
Click to expand...
Click to collapse
Just downloading now.
I was using the drivers that windows installs 'from the phone' when you plug it into windows. Those drivers worked fine... I then started messing around with downloaded drivers (probably all the same ones you have tried) and all of them just did the same thing or didn't work.
FYI, MTK Tools no longer detects my phone. It only detected it when it was booted (in CWM for me, I never tried it when it was actually working, in the OS). My phone only gets detected in 'device manager' and 'SP flashtool' sometimes.
I can upload all the drivers I tried downloading, but I think the more drivers you install, the more incompatibility there is... In the end I downloaded USBDeview and uninstalled all the 'phone' related drivers on my computer, then just used the drivers that automatically get installed when you plug your phone in.
I'm just researching how to flash this system.img file you have uploaded (thanks), using SP Tools. If you've done it before could you let me know how? I don't want to mess anything else up now.
Thanks.
I managed to install Gionee Elife s5.5 ROM using SP Flashtool easily, and my phone now works!! Well, sort of.
The screen keeps freezing, touch screen keeps now working (have to press sleep button, to refresh it).
I am hoping the OTA update will fix all these problems! Fingers crossed...
I really want to get the Blu Vivo iv firmware though, as there are loads of chinese characters on this phone, even with English language on.
If anyone could backup their phone using MTK tools, and upload the entire backup for me and everyone else that needs it, that would be great! Then anyone who bricks their phone could unbrick it by flashing the firmware useing SP Flashtool!
Thanks for eveyrone's help especially taalibj01!!!! You are a legend!
Don't know how it's possible but here it is Blu Firmware files!!!!!
James666PKR said:
I managed to install Gionee Elife s5.5 ROM using SP Flashtool easily, and my phone now works!! Well, sort of.
The screen keeps freezing, touch screen keeps now working (have to press sleep button, to refresh it).
I am hoping the OTA update will fix all these problems! Fingers crossed...
I really want to get the Blu Vivo iv firmware though, as there are loads of chinese characters on this phone, even with English language on.
If anyone could backup their phone using MTK tools, and upload the entire backup for me and everyone else that needs it, that would be great! Then anyone who bricks their phone could unbrick it by flashing the firmware useing SP Flashtool!
Thanks for eveyrone's help especially taalibj01!!!! You are a legend!
Click to expand...
Click to collapse
https://www.dropbox.com/s/qt0i6d2og8ge0sc/BLU_D970l_V11_GENERICK_T8493.zip?dl=0
I hereby nominate you for a knight-hood. I will contact the Queen and get her to knight you 'Sir Amazing'!!! I'm downloading now, will let you know how it goes and if it all works correctly!!!
Blu vivo iv drivers
these drivers are for gionee and Blu vivo iv just install its auto install so its easy
https://www.dropbox.com/s/x8umdofqgwbjbr1/GN_Driver_V1.3.0_Test.rar?dl=0
https://www.dropbox.com/s/yk08ekq3hf23zs0/MauiMETA_exe_3G_v6.1336.1.rar?dl=0
taalibj01 said:
https://www.dropbox.com/s/qt0i6d2og8ge0sc/BLU_D970l_V11_GENERICK_T8493.zip?dl=0
Click to expand...
Click to collapse
If you have bricked your Blu Vivo iv, or installed a custom recovery therefore could not upate OTA to KitKat 4.4.2, look here!
So everyone who needs to flash the new KitKat firmware from Blu follow these instructions!
Download the following file: https://www.dropbox.com/s/qt0i6d2og8ge0sc/BLU_D970l_V11_GENERICK_T8493.zip?dl=0
(Supplied by the amazing 'taalibj01')
If you have not previously installed the MTK drivers (usually installs from the phone when you plug it into the computer) please download and install from here:
https://www.dropbox.com/s/x8umdofqgw..._Test.rar?dl=0
https://www.dropbox.com/s/yk08ekq3hf...336.1.rar?dl=0
Also download/extract SP Flash tool from here (latest version): http://androidxda.com/smart-phone-flash-tool
Before you start, when you connect your 'powered off' phone via USB cable whilst holding the up button, your phone should be recognised in 'device manager' as 'MTK COM USB (COM4)' or something similar, under the 'Ports (COM & LPT)' section. If it is not, then you need to install the relevant drivers (above).
Now you are ready to get started.
Turn off your Vivo iv phone and disconnect it from USB.
Unzip the BLU_D970l_V11_GENERICK_T8493.zip file to any location.
Open SP Flash Tool, and click the 'scatter-loading' button.
Navigate to the unzipped BLU_D970l_V11_GENERICK_T8493 firmware folder.
Double click the MT6592_Android_scatter.txt file
SP Flash Tool will then list all of the files it has read form the scatter file and automatically 'tick/check' each of the 'preloader/MBR/EBR1/UBOOT/BOTIMG etc... files.
Most guides will tell you to press the select 'Download' from the drop down menu, but I kept getting an error message, but if you highlight 'Firmware Upgrade' from the drop down box, you should be fine.
Click the 'Download' green button.
Now plug your phone in whilst holding 'volume up' button.
SP Tools should recognise the phone, and the bar along the bottom should turn RED. The phone will disconnect, then recconnect again after a few seconds, and the bar will turn Yellow and it will say 'Formatting', then it will Flash the files to your phone which should take 30 seconds or so.
After it is done, a nice green circle saying DONE will pop up. You can now disconnect your phone, wait a few seconds, then power on using the power button.
All Done!!! KITKAT is now installed on your bricked phone!
Enjoy!
Hello, thanks for making this thread! Not much help out there for this phone. I started following your instructions, and immediately ran into a problem. On the step below...
taalibj01 said:
use mobile uncle from market and update recovery choose recovery.img first item at top of the list the downloaded recovery img must be in base of internal storage do not place in any folders!!!
Click to expand...
Click to collapse
...I opened the Mobile Uncle app on my phone, went to update recovery option, and chose the recovery.img from my SD card. The app popped up a message that read...
Mobile Uncle said:
Please Root your Android first!!
Click to expand...
Click to collapse
I just got the phone a few days ago, and it had KitKat 4.4.2 already installed from the factory. What do I need to do? Thanks!
Well I solved the problem. I downloaded Kingo Root and it successfully rooted my phone! I ran Mobile Uncle to verify, and it confirmed my root status.
My question now is, should I install the Carliv recovery, and flash bootimgADB.zip? Or, am I good to go now? I have SuperSU v2.02 installed. Thanks!
---------- Post added at 09:55 AM ---------- Previous post was at 09:09 AM ----------
So, I went ahead and tried to install the recovery.img using Mobile Uncle. It ran for a second, then a pop-up asked to reboot into recovery mode. I hit ok, but it rebooted into the orange and grey stock android system recovery.
So, I figured I would try to install the bootimgADB.zip from SD card, but it just comes back with installation aborted.
Any thoughts?

After rooting my nexus 5 is not booting up with non stop booting animation

I have a nexus 5 16 GB and i downloaded the recent software update android 6.0.1 and then I decided to root and I used 'Nexus root toolkit v2.06' and first unlocked the bootloader and then rooted. Everything worked fine but after the process was complete it was rebooting and the booting animation went on and on for many hours and the device did not root. I really don't know what's going on. My purpose is to install a custom rom: cyanogenmod 12. Now what should I do ???? PLEASE HELP. When i try to enter recovery mode it shows a picture of the android mascot with opened back and exclamation and cannot enter command as well. and after some time the booting animation begins and goes on and on...
please help...
nexus_5_ said:
I have a nexus 5 16 GB and i downloaded the recent software update android 6.0.1 and then I decided to root and I used 'Nexus root toolkit v2.06' and first unlocked the bootloader and then rooted. Everything worked fine but after the process was complete it was rebooting and the booting animation went on and on for many hours and the device did not root. I really don't know what's going on. My purpose is to install a custom rom: cyanogenmod 12. Now what should I do ???? PLEASE HELP. When i try to enter recovery mode it shows a picture of the android mascot with opened back and exclamation and cannot enter command as well. and after some time the booting animation begins and goes on and on...
please help...
Click to expand...
Click to collapse
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
funnel71 said:
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
Click to expand...
Click to collapse
Thank you very much for the reply, I really do have no idea as to how to flash the factory image because i am very new in this area. Could you please recommend software and which factory image i should download, please ?? thanks very much.
:good:
funnel71 said:
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
Click to expand...
Click to collapse
Also, you mentioned a 'special kernel' what does that mean. All i want to do to my device is install cyanogenmod 12 and for that i believe it needs to be rooted, so i am really confused. What should I do know
I'm having this same problem, and unfortunately, when I start the phone on fastboot, I can not access the recovery mode in order to upload a factory image of nexus 5.
I used the new tool available her for quick flash, and now, I don't have a phone.
First, don't panic. Your phone is still very easy to recover. Unfortunately I can't get you a complete walkthrough here (for now at least), so I'll give you the main idea and you'll have to do your homework (as maybe you should have done before).
1. You need to get fastboot working on your computer. It's included in the Android sdk package, but there might be some easier way to get it. Google it. You might need drivers for your pc too. Google it as well.
2. Then you need to get into fastboot mode on your phone. To do it, hold down power button AND volume down button until it gets into fastboot mode. You will see an android on his back with the cover open. At this point, connect your phone to your pc, open a terminal on your pc and type "fastboot devices" without the quotes "". It should find your phone if fastboot is working. If it doesn't work go back to step 1.
3. Download TWRP recovery on your pc and place the img file in the same folder as your fastboot executable (not mandatory but easier). It can be found here https://dl.twrp.me/hammerhead/
4. Always in fastboot mode, type "fastboot flash recovery twrp-2.8.7.1-hammerhead.img" assuming you downloaded that file, which you should have by the way. It should install fine. If you haven't placed the file in the same directory as your fastboot executable, you will need to provide the path to your img file as well.
5. Then use the volume rocker to switch between modes and choose reboot recovery.
6. You should now be in TWRP recovery. At this point, download a custom kernel (anyone found on xda for hammerhead should do) and push it to your phone. It should be fairly simple with TWRP. Then flash your new kernel using install. It should help you get your phone booting normally. Alternatively, you can download a custom ROM like cm12.1 and flash it altogether. It will install everything needed for your phone to boot up too. Beware if flashing a ROM though, I strongly advice you to do a factory reset before flashing it. You will find that option in the wipe menu.
Hope it helps, let me know if you need further assistance.
Yesterday, I have tried everything to have my computer to recognize the "fastboot" command, and I installed like 2 or 3 different programs for that. With my old Windows 7, I have been able to push a flashed image to fix this issue, using the fastboot command, but with Windows 10, it's always telling me it's not a valid command. I'll keep trying it, otherwise, i'll have to "resurrect" my old Windows XP computer.
Also, I noticed now that, while trying to install the fastboot, as per some files that I could download, but no file has been copied into my computer, not even if I run it as admin.
fixed. but no RECOVERY mode options....
Hi Guys,
Thank you very much for the help, I have finally recovered the phone and running android 6.0 MRA58N but it is not rooted. Now if you don't mind could you teach me how to root because i have checked lots of videos and tuts but none worked for me...
IMPORTANT:
when i am in recovery mode why cannot I access options even when i press volume up + power button and release them at the same time...????
Thanks in advance.
Just flash a custom recovery via fastboot. Just make sure your bootloader is unlocked. Can't link though.
hi guys i have used nexus 5 mobile with cyanogenmod 14.1 .It worked properly in 1 year. after that suddenly switched off and it not properly boot up .i try to switch on my mobile , first it show google with unlock logo properly and when it show cyanogenmod logo it stuck and again show google with unlock logo....i try recovery mode to wipe and flash the same rom ....the process is interrupt at middle stage and again show the google..i try lots of time . after few try that process finished completely without interrupt. then use my mobile 1 day same as i used first time root. after that same problem occur on my mobile ..so help me guys
@[email protected], possible power button problem?

J4 plus (J415GB) bricked

Is there anyone here facing same with my situation? today i bricked my J4 plus, Dunno if its hard bricked or soft brick, I can't enter to download mode and system restore anymore. Im just trying to get oreo back because i fell little laggy on my current os (pie). I went to samsung service center and they told to use JTAG to get it fix but its too expensive for me to pay hundreds buck for this.
Thank you
its not bricked. your battery is full drained. i had the same problem and how i fixed!!! i presed all 3 buttons and put usb cable to my pc and my phone. it goes like bootloop starts and shuts. you will wait with pressed buttons from 5 to 10 mins depend how low is your battery. and finaly will go to download mode and you can flash it then!!!
Bricked my J4+
Can someone help me with a bricked J4+?
I wanted to install TWRP, I followed the guide to the letter on how to install TWRP.
After successfully flashing TWRP 3.2.3-0 and flashing RMM bypass zip (without booting to the OS) I also performed a Wipe Cache in TWRP.
I booted to the Samsung OS and the system overall felt laggy.
I performed a Factory Reset, still the system felt laggy.
I decided to use Odin and install the Samsung factory system (thus go back to Samsung OS).
I booted successfully and decided to give TWRP 3.2.3-0 another chance.
Odin resulted in FAIL when trying to flash with the following error: Can't open the specified file (line: 1892)
I tried different versions of Odin (from last to previous ones), different USB ports, I even tried another PC but no success.
I performed another factory reset and now the phone is hard bricked I guess because it will power on...try to get in stock recovery and Erase...and then power off. I can't get to download mode or stock recovery.
Any help I would highly appreciate it.
Thanks.
FL0R1AN said:
Can someone help me with a bricked J4+?
I wanted to install TWRP, I followed the guide to the letter on how to install TWRP.
After successfully flashing TWRP 3.2.3-0 and flashing RMM bypass zip (without booting to the OS) I also performed a Wipe Cache in TWRP.
I booted to the Samsung OS and the system overall felt laggy.
I performed a Factory Reset, still the system felt laggy.
I decided to use Odin and install the Samsung factory system (thus go back to Samsung OS).
I booted successfully and decided to give TWRP 3.2.3-0 another chance.
Odin resulted in FAIL when trying to flash with the following error: Can't open the specified file (line: 1892)
I tried different versions of Odin (from last to previous ones), different USB ports, I even tried another PC but no success.
I performed another factory reset and now the phone is hard bricked I guess because it will power on...try to get in stock recovery and Erase...and then power off. I can't get to download mode or stock recovery.
Any help I would highly appreciate it.
Thanks.
Click to expand...
Click to collapse
you didnt follow guide from letter to letter. is obviuosly you didnt do all you need to do. if you in pie update you need to flash twrp (you did) then NEED to format data(go to wipe choose format data(not wipe data,cache) write yes and swipe to format data.this step is important.then go to recovery again and flash pie patched boot.img and oreo enforcing.zip,then RMM bypass,and then you can do boot up your device.thanks.
rudi021 said:
you didnt follow guide from letter to letter. is obviuosly you didnt do all you need to do. if you in pie update you need to flash twrp (you did) then NEED to format data(go to wipe choose format data(not wipe data,cache) write yes and swipe to format data.this step is important.then go to recovery again and flash pie patched boot.img and oreo enforcing.zip,then RMM bypass,and then you can do boot up your device.thanks.
Click to expand...
Click to collapse
The part where I had to format the data...I have missed that. Thanks for pointing it out.
I took the phone to a repair shop because it is hard bricked and it needs jtag to unbrick it.
As soon as I have it back I will try again to install TWRP.
Thanks for the help, I appreciate it.
FL0R1AN said:
The part where I had to format the data...I have missed that. Thanks for pointing it out.
I took the phone to a repair shop because it is hard bricked and it needs jtag to unbrick it.
As soon as I have it back I will try again to install TWRP.
Thanks for the help, I appreciate it.
Click to expand...
Click to collapse
no need to thanks.btw if your device is unlocked you cant be bricked.just flash firmware you want and thats it.btw your device must be unlock to do this stuff(twrp,gsi,etc....) btw you can have read my guide for flashing gsi on samsung j4+.https://forum.xda-developers.com/galaxy-j4+/how-to/how-to-flash-gsi-genericsystemimage-to-t3942554.
if you have any question be free to ask.i will help you if i can.
rudi021 said:
no need to thanks.btw if your device is unlocked you cant be bricked.just flash firmware you want and thats it.btw your device must be unlock to do this stuff(twrp,gsi,etc....) btw you can have read my guide for flashing gsi on samsung j4+.https://forum.xda-developers.com/galaxy-j4+/how-to/how-to-flash-gsi-genericsystemimage-to-t3942554.
if you have any question be free to ask.i will help you if i can.
Click to expand...
Click to collapse
This is a phone from work and I did toggle EOM unlock and USB debugging in order to flash TWRP.
I did not enter any password, face unlock, pattern or sign in to google....nothing of the sort. As soon as I opened the phone from the box tried to install TWRP knowing it will erase everything after TWRP installation. I really hate Samsung UI and wanted to try Lineage OS or another custom ROM which is not laggy like ONE UI.
After installing TWRP the phone became very laggy (obviously I did not perform a format data...my bad) I did use Odin and flashed the corresponding firmware of the phone and it did that successfully.
I tried to give TWRP another shot by flashing it again but I was getting a FAIL in Odin with the following error: Can't open the specified file (line: 1892)
After this I tried to flash again the same Samsung firmware but kept getting the same FAIL and the same error: Can't open the specified file (line: 1892)
I have tried all versions of Odin but the same FAIL and same error.
Now I can't even get into Download mode or Samsung recovery mode.
I press Volume Up + Volume Down and insert the micro USB cable....the phone takes at least 10 seconds to power up (Samsung logo) and then I see a blue screen with Android robot trying to perform an Erase and then fails and the phone powers off immediately.
As soon as I get the phone I will check your link on XDA and try a GSI ROM.
Which one do you recommend...this is a work phone, all I care about is speed and fluidity and it has to be a daily driver.
FL0R1AN said:
This is a phone from work and I did toggle EOM unlock and USB debugging in order to flash TWRP.
I did not enter any password, face unlock, pattern or sign in to google....nothing of the sort. As soon as I opened the phone from the box tried to install TWRP knowing it will erase everything after TWRP installation. I really hate Samsung UI and wanted to try Lineage OS or another custom ROM which is not laggy like ONE UI.
After installing TWRP the phone became very laggy (obviously I did not perform a format data...my bad) I did use Odin and flashed the corresponding firmware of the phone and it did that successfully.
I tried to give TWRP another shot by flashing it again but I was getting a FAIL in Odin with the following error: Can't open the specified file (line: 1892)
After this I tried to flash again the same Samsung firmware but kept getting the same FAIL and the same error: Can't open the specified file (line: 1892)
I have tried all versions of Odin but the same FAIL and same error.
Now I can't even get into Download mode or Samsung recovery mode.
I press Volume Up + Volume Down and insert the micro USB cable....the phone takes at least 10 seconds to power up (Samsung logo) and then I see a blue screen with Android robot trying to perform an Erase and then fails and the phone powers off immediately.
As soon as I get the phone I will check your link on XDA and try a GSI ROM.
Which one do you recommend...this is a work phone, all I care about is speed and fluidity and it has to be a daily driver.
Click to expand...
Click to collapse
1. two possible mistake. 1.after you try flash firmware dont check user data,just check AP,BL,CP,CSC and flash firmware.2.no need to try old odin. all new firmware is work on new odin.just need to know what to checked to flash. about gsi all is good but i like Havoc OS, Lineage OS 16, RR,almost all.again you are welcome to ask help if you want.:good:
rudi021 said:
1. two possible mistake. 1.after you try flash firmware dont check user data,just check AP,BL,CP,CSC and flash firmware.2.no need to try old odin. all new firmware is work on new odin.just need to know what to checked to flash. about gsi all is good but i like Havoc OS, Lineage OS 16, RR,almost all.again you are welcome to ask help if you want.:good:
Click to expand...
Click to collapse
Hmmm I did check USER DATA. So that bricked my device. Thanks for letting me know.
FL0R1AN said:
Hmmm I did check USER DATA. So that bricked my device. Thanks for letting me know.
Click to expand...
Click to collapse
yeeeahhh. i am knowing that in hard way. you can check user data only if you have ORIGINAL firmware and not rooted phone(mean twrp),if you have rooted(twrp) then flash with or without user data. some firmwares on web can flash with user data, some cant.anyway as i say you can always ask for help.i will gladly help if i can. good luck.
rudi021 said:
yeeeahhh. i am knowing that in hard way. you can check user data only if you have ORIGINAL firmware and not rooted phone(mean twrp),if you have rooted(twrp) then flash with or without user data. some firmwares on web can flash with user data, some cant.anyway as i say you can always ask for help.i will gladly help if i can. good luck.
Click to expand...
Click to collapse
Thanks. I will wait for the phone to be unbricked and then will try TWRP again.
Can i install gsi rom if the phone is in oneui?
FL0R1AN said:
I press Volume Up + Volume Down and insert the micro USB cable....the phone takes at least 10 seconds to power up (Samsung logo) and then I see a blue screen with Android robot trying to perform an Erase and then fails and the phone powers off immediately .
Click to expand...
Click to collapse
What you're describing are symptoms of a flat battery and a direct boot to recovery.
To boot to download mode plug in the USB cable first then hold vol up, vol down and power until download mode appears.
There is absolutely no way TWRP caused the lag. TWRP runs in its own minimal OS environment and has no effect on a booted android OS whatsoever.
Lastly your device wasn't hard bricked, a device that powers on even if it doesn't boot is only soft bricked.
Usually recoverable using the right procedure.
ashyx said:
What you're describing are symptoms of a flat battery and a direct boot to recovery.
To boot to download mode plug in the USB cable first then hold vol up, vol down and power until download mode appears.
There is absolutely no way TWRP caused the lag. TWRP runs in its own minimal OS environment and has no effect on a booted android OS whatsoever.
Lastly your device wasn't hard bricked, a device that powers on even if it doesn't boot is only soft bricked.
Usually recoverable using the right procedure.
Click to expand...
Click to collapse
I managed to boot into the Revovery and perform a factory reset, now the phone booted normally.
I will try and install TWRP.
When these strange things happened the device had over 80% battery...at least that's what it showed on screen.
Now I see that indeed it was flat 0% and you were right to point out that this is a flat battery problem.
Thanks for the help I really appreciate it.
FL0R1AN said:
I managed to boot into the Revovery and perform a factory reset, now the phone booted normally.
I will try and install TWRP.
When these strange things happened the device had over 80% battery...at least that's what it showed on screen.
Now I see that indeed it was flat 0% and you were right to point out that this is a flat battery problem.
Thanks for the help I really appreciate it.
Click to expand...
Click to collapse
well like i told you it is not problem of twrp.but as senior member ashyx told in answer today device cant be hard bricked.just flash firmware and device will boot as normal. btw keep battery full
rudi021 said:
well like i told you it is not problem of twrp.but as senior member ashyx told in answer today device cant be hard bricked.just flash firmware and device will boot as normal. btw keep battery full
Click to expand...
Click to collapse
Yes Thanks. I am at 100% battery. Can I ask a few questions on how to install TWRP?
I am on Android 9.x.x PIE.
Install TWRP and immediately force reboot to recovery.
Flash the RMM bypass.
Format data
Boot to Samsung OS.
Is this procedure correct?
Thanks.
FL0R1AN said:
Yes Thanks. I am at 100% battery. Can I ask a few questions on how to install TWRP?
I am on Android 9.x.x PIE.
Install TWRP and immediately force reboot to recovery.
Flash the RMM bypass.
Format data
Boot to Samsung OS.
Is this procedure correct?
Thanks.
Click to expand...
Click to collapse
install twrp(in odin option uncheck Auto Reboot) ,format data reboot to recovery,flash oreo enforcing.zip,flash RMM,flash magisk(newest) then reboot.
rudi021 said:
install twrp,format data,flash oreo enforcing.zip,flash RMM,flash magisk(newest) then reboot.
Click to expand...
Click to collapse
Got it, Thanks.
FL0R1AN said:
Yes Thanks. I am at 100% battery. Can I ask a few questions on how to install TWRP?
I am on Android 9.x.x PIE.
Install TWRP and immediately force reboot to recovery.
Flash the RMM bypass.
Format data
Boot to Samsung OS.
Is this procedure correct?
Thanks.
Click to expand...
Click to collapse
It's correct, but if you want access to the data partition in twrp you need to also install the encryption patch.
You will also need to either install magisk or some other patch that disables dmverity.
ashyx said:
It's correct, but if you want access to the data partition in twrp you need to also install the encryption patch.
You will also need to either install magisk or some other patch that disables dmverity.
Click to expand...
Click to collapse
Got it, Thanks

Categories

Resources