Related
Hi.
I have T-mobile Nexus .. i rooted the phone fwe months back and running on 2.3.4 ... Since then i can't upgrade to any higher 2.3.6 or even 4.0.2 either manually or OTA.
Everytime the upgrade stuck on screen as attached in the photo.
Everytime I have to remove the battery to reset the phone
I even try to "reset to factory setting" but also the phone get stuck in the same screen shot
Can someone tell me what i need to do to solve this problem ?
You'll hate to unroot your phone and lock the bootloader.
Thanks for your fast reply,
How can I unroot your phone and lock the bootloader ?
Which recovery did you install when you rooted your phone? Can you boot into recovery (pull battery, volume up plus power button)? If so ... download a custom rom from proper development forum, place on sd card, boot into recovery, wipe data, dalvik, boot, and flash new rom. If none of this makes sense to you ... time to read up on the basics. Good luck ...
Thanks,
I used clockworkmod recovery ROM manager v5.0.0.6
Yes, I can boot into recovery but I can't do anything from there ... screen again get frozen at the snap shot i attached when i try to boot from recovey file or rom or an upgrade file
You should try putting a new ROM, best if you could an official ROM. Since the phone doesn't go past that screen, i think is because it doesn't have any ROM to go to. At least that's what happened to me. So wipe/format (from mount) everything, go to recovery/mount/mount USB, . Connect your phone to the PC, put the official ROM on SD, then "unmount USB", and instal from SD the ROM, then restart. I think it should work.
After you install the official ROM, you can proceed in locking the bootloader.
Good luck !
everfocus said:
Thanks,
I used clockworkmod recovery ROM manager v5.0.0.6
Yes, I can boot into recovery but I can't do anything from there ... screen again get frozen at the snap shot i attached when i try to boot from recovey file or rom or an upgrade file
Click to expand...
Click to collapse
Try reflashing CWM recovery in fastboot mode on your bootloader screen! fastboot flash recovery (path to your recovery img!) & if that helps, you can then flash a new rom in recovery console, then relock bootlloader in fastboot mode!!
Fastboot
Thanks all Guys for your help,
Still my problem is that I can't go to the recovery option in the fastboot mode.
When i choose it.. the phone stuck @ the black Google screen (Attached)
I uninstall Rom Recovery and Flash CWM again .. I didn't get the black screen any longer but the phone send me back to the fastboot menu when i choose recovery option ....
Thank you all guys for you help ...
I solved the problem ..
I tried to unroot my phone again using the steps in the following link
http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s-or-nexus-s-4g-new/
1 - At the step when I go to command line
C:\nexussrootnew>fastboot oem unlock
...
FAILED (remote: Already Unlocked)
finished. total time: 0.001s
2 - I moved to the next step
C:\nexussrootnew>fastboot flash recovery recovery3101.img
sending 'recovery' (4036 KB)...
OKAY [ 0.416s]
writing 'recovery'...
OKAY [ 0.528s]
finished. total time: 0.945s
Now I can enter the recovery mode and I think I can do upgrade to ICS via OTA or manually ...
Thanks and have a nice weekend all
Hellooooooooooooooooooooooooooooooooo!!!
this is my first thread in this forum, mi name is Nicolas and i ve a very big problem with my new tablet.
I was trying to install the new Jelly Bean (OS_Acer_RV09RC08.WW.GEN1_A41J_A) and everything was OK
I unlocked the bootloader .......and....
I try to root and just bricked....
Everytime i turn on the tablet i can see the "Acer logo" and the line: Bootloader Version JB-653b3d3 (Unlock Mode)
I cant get into the recovery mode.....
Sorry for my bad english....i need your help ppl!!!!
Thanks for ur time.
Nicolas.
May you can get into Fastboot mode and reflash the recovery.
Give it a try =)
Do you have a androids of your original ROM?
I did the exact same thing just yesterday...
If you have a JB image to work from, get it in fastboot mode and look at the thread on CWM Recovery 6.0.1.5...
Sent from my A700 using xda premium
thks for the replies.....
i downloaded the stock rom from the Acer web page
i tried with:
"adb reboot-bootloader" and NOTHING.....i ve the line: <waiting for the device> ....and ....5 min later nothing.
then:
tried to get the fastboot mode (vol + & PWR) and the tablet just get the same boot = nothing.
:crying:
freejack84 said:
thks for the replies.....
i downloaded the stock rom from the Acer web page
i tried with:
"adb reboot-bootloader" and NOTHING.....i ve the line: <waiting for the device> ....and ....5 min later nothing.
then:
tried to get the fastboot mode (vol + & PWR) and the tablet just get the same boot = nothing.
:crying:
Click to expand...
Click to collapse
To get into fastboot mode, it's the following combination;
- Press [vol-] + [power]
- As soon as the tablet vibrates, let go [power] then cycle your rotation lock button left and right till you see the the text start to appear.
Unless you;re going to try and fastboot a system image setup or recovery image or another boot.img, not sure what you wish to accomplish.
I would guess you would be better off installing maybe the GB full version JellyBean update.
Also, I understand there,s a a700 ICS service rom out there somewhere. That might help you also.
But these are just guesses at this point.
What would help, is to know exactly what you did to get yourself into this situation. Like What root procedure from what post? If you tried one of the ICS Boot.image flashes, when you had JB updated, well, no wonder it borked up. If that's the case, it's simple just to fastboot a JB Boot.img back in.
So which thread did you get the root procedure from EXACTLY?
One more thing, this thread belongs in Q&A Forum, so I put in a request to have it moved.
MD
Moscow Desire said:
To get into fastboot mode, it's the following combination;
- Press [vol-] + [power]
- As soon as the tablet vibrates, let go [power] then cycle your rotation lock button left and right till you see the the text start to appear.
Unless you;re going to try and fastboot a system image setup or recovery image or another boot.img, not sure what you wish to accomplish.
I would guess you would be better off installing maybe the GB full version JellyBean update.
Also, I understand there,s a a700 ICS service rom out there somewhere. That might help you also.
But these are just guesses at this point.
What would help, is to know exactly what you did to get yourself into this situation. Like What root procedure from what post? If you tried one of the ICS Boot.image flashes, when you had JB updated, well, no wonder it borked up. If that's the case, it's simple just to fastboot a JB Boot.img back in.
So which thread did you get the root procedure from EXACTLY?
One more thing, this thread belongs in Q&A Forum, so I put in a request to have it moved.
MD
Click to expand...
Click to collapse
Thks MD for ur instant reply.
Sorry for dont put my thread into the Q&A Forum. It was a mistake. Sorry again
My situation is: "like i remember" i tried to make the root with the "flash-ICS-patchedBoot.bat".....i know that BAT is for ICS and not for JB but i take that mistake doing the thing really fast. :angel:
Ok...i need them to get the fastboot with the JB Boot.img like you said.
The JB Boot.img is into the Rom??? because i saw the boot.img into the JB update.zip
Can u tell me the command to get that flash? Is "fastboot flash boot boot.img"?
Thks for ur patience
freejack84 said:
Thks MD for ur instant reply.
Sorry for dont put my thread into the Q&A Forum. It was a mistake. Sorry again
My situation is: "like i remember" i tried to make the root with the "flash-ICS-patchedBoot.bat".....i know that BAT is for ICS and not for JB but i take that mistake doing the thing really fast. :angel:
Ok...i need them to get the fastboot with the JB Boot.img like you said.
The JB Boot.img is into the Rom??? because i saw the boot.img into the JB update.zip
Can u tell me the command to get that flash? Is "fastboot flash boot boot.img"?
Thks for ur patience
Click to expand...
Click to collapse
It's no problem.
So you fastbooted an ICS boot.img on a JB rom
So, you need to see if you can manually get it into fastboot mode with the procedure I pointed out above (note it will probably wipe your user data, but who cares)
If you get it in fastboot mode, verify via windows device manager, then just put a JB Boot image in there. I have a little package in my Boot.image thread Full /System RW-Root. Don't use the boot mage in it, as it's for a 701. Just copy your JB boot.image in there and fastboot it. You have the correct command.
Verboth has a new rom, that contains an unsecure boot.img for the 700 JB. You can use that one also. It's what you were trying to do originally, just with a wrong image (ICS)
The reason ADB doesn't see it, is because the system isn't running. The newer CWM recoveries should have adb enabled through CWM, but I don't think you put that in yet.
Hopefully you'll get it fastbooted.
MD
Moscow Desire said:
It's no problem.
So you fastbooted an ICS boot.img on a JB rom
So, you need to see if you can manually get it into fastboot mode with the procedure I pointed out above (note it will probably wipe your user data, but who cares)
If you get it in fastboot mode, verify via windows device manager, then just put a JB Boot image in there. I have a little package in my Boot.image thread Full /System RW-Root. Don't use the boot mage in it, as it's for a 701. Just copy your JB boot.image in there and fastboot it. You have the correct command.
Verboth has a new rom, that contains an unsecure boot.img for the 700 JB. You can use that one also. It's what you were trying to do originally, just with a wrong image (ICS)
The reason ADB doesn't see it, is because the system isn't running. The newer CWM recoveries should have adb enabled through CWM, but I don't think you put that in yet.
Hopefully you'll get it fastbooted.
MD
Click to expand...
Click to collapse
Okay, so since I just did this, I'm going to try and give you a "how to" on how I fixed it...
MD and pawitp both are the authorities on this, but I think this will help and I a, sure they will correct me where I go wrong.
First, use the manual process for getting your A700 in fastboot.. power button + down vol, wait for the first buzz then release only the power button, wait for the second buzz then press the up volume button. Your tab should now be in fastboot mode.
Connect it to your computer.
Get a copy of the proper recovery image "recovery-a700-6015" and the following ROM ( http://forum.xda-developers.com/showthread.php?t=1952124) and save them to a directory where you can find it easily.
Pull the SD card from your tab and put the ROM from above in the base directory and put it back in your tab.
From the c prompt on your computer use the following fastboot command:
Fastboot devices
----#make sure that the computer sees your a700
Fastboot boot <save directory>recovery-a700-6015.img
----#your tab will reboot into CMR Recovery
In recovery format system, data, cache, dalvik
Still in recovery install the ROM from your external SD card.
The Aroma Installer will guide you through it, but make sure you tell it to install the new firmware.
Reboot.
You should be on the stock rooted ACER Great Britain release.
From there you can download and install CM10 (which is what I did), or any other ROM you would like.
Sent from my A700 using xda premium
well.......30 minutes with the tablet and:
I put the tablet in Recovery state with the last instructions.....but now i ve too much errors lines:
Important: all this error are "before" flash again the recovery
The recovery cant:
mount /cache/recovery/command
mount /cache/recovery/log
mount /cache/recovery/last_log
cant open cache/recovery/log
and.....
cant mount SDCARD, EXTERNALSD, SYSTEM, CACHE, etc etc...
when i try to flash again the recovery: <waiting the device> and nothing......i cant put the tablet in fastboot mode.
i have the same problem before. 無得整的, 要上acer換底版的
NEWS:
Finally i get the fastboot mode (Vol - & PWR and then CYCLE THE ROTATION LOCK). :good:
First: reflash the recovery and DONE
All the errors just gone.
Now.....install again the JB.....and DONE
My Acer go back to normally conditions. :victory:
Thks for ur support. :laugh:
freejack84 said:
NEWS:
Finally i get the fastboot mode (Vol - & PWR and then CYCLE THE ROTATION LOCK). :good:
First: reflash the recovery and DONE
All the errors just gone.
Now.....install again the JB.....and DONE
My Acer go back to normally conditions. :victory:
Thks for ur support. :laugh:
Click to expand...
Click to collapse
Uhmmmm.... didn't I state that the other day?
Glad you got it going Mate :good:
MD
thks ppl
freejack84 said:
NEWS:
Finally i get the fastboot mode (Vol - & PWR and then CYCLE THE ROTATION LOCK). :good:
:
Click to expand...
Click to collapse
I didnt have the same exact issue like the other users BUT this key combination to finally get back into fastboot during a hanging ACER logo bootup with a red failure msg at the corner was the LIFE SAFER!!!!!
VOL - (left button with two knobs) & PWR and then CYCLE THE ROTATION LOCK
tattoo this on your arms!!! :laugh:
LukeRG said:
I didnt have the same exact issue like the other users BUT this key combination to finally get back into fastboot during a hanging ACER logo bootup with a red failure msg at the corner was the LIFE SAFER!!!!!
VOL - (left button with two knobs) & PWR and then CYCLE THE ROTATION LOCK
tattoo this on your arms!!! :laugh:
Click to expand...
Click to collapse
LOL
pls step step explain ı recovery my tablet but ı want to back syock rom tablet internal storage not ready in pc ı cant see internal storage ı see only sc card camera dont workk how back to syock rom pls help..
thank's man
freejack84 said:
NEWS:
Finally i get the fastboot mode (Vol - & PWR and then CYCLE THE ROTATION LOCK). :good:
First: reflash the recovery and DONE
All the errors just gone.
Now.....install again the JB.....and DONE
My Acer go back to normally conditions. :victory:
Thks for ur support. :laugh:
Click to expand...
Click to collapse
Thank's... you just safe my problem today
u welcome .......
Hello everybody,
I think I have NOT exactly the same problem but very similar.
Let me explain how I got there:
I had JB bootloader and CM11 installed for long and working fine.
Last days I tried out the CM12.1 unofficial rom with successful installation.
I noticed that the camera focus was not working. Usually I never use the camera and was not sure if it worked before. So I went back to CM11 to look if it is rom dependent. In CM11 it still was not working and I went back to stock. The stock rom I found was Android 4.0.4 and I tried to make OTA update what showed me a “not allowed to your device” –error.
However, at this moment I was quite sure that the camera focus is a hardware defect and wanted to go on testing the new CM12.1. I installed it again from CWM recovery and it was not booting anymore.
The problem is, that the stock rom flashed an ICS bootloader which is not compatible anymore. I also cannot boot into recovery anymore but fastboot is working.
Power-On:
shows Bootloader Version ICS-MR1-a055314 (Unlock Mode) and nothing more
Power-On + Vol.Down:
Bootloader Version ICS-MR1-a055314 (Unlock Mode)
Erasing Cache before SD update…
SD update cnd: recovery
--update_package=SDCARD:update.zip
Booting recovery kernel image
Then for just a second CWM is shown:
CWM-based Recovery v6.0.5.1
Finding update package
E:unknown volume for path [SDCARD:update.zip]
E:Can't mount SDCARD:update.zip
Installation aborted.
Rebooting...
Then it holds on Bootloader Version ICS-MR1-a055314 (Unlock Mode)
I could not find any button combination to boot something else.
What I tried and what did not make any changes:
Flashing the recovery.img again
Erase userdata, cache, system
Please help me to boot up recovery again and flash a JB bootloader and new rom.
Thanks and kind regards,
Gandlz
Well, in between I found a solution and can answer my own question now:
The trick is to flash the CWM Recovery not to the recovery partition but to the boot partition. (fastboot flash boot recovery.img)
After restarting the tablet it boots directly into CWM Recovery.
I found a newer stock rom with jelly bean android and installed it to come back to JB-Bootloader. Now I could install CM10.2 CM11 or CM12.1 again.
The stock rom is from a german forum:
android-hilfe.de/thema/a700-zurueck-aufs-deutsche-stock-rom-flashen-anleitung-imagefile.329590
By the way: I’m running CM10.2.1 and it is very much faster than CM11 or CM12.1. I don’t need the newer features and like the old design even more. And also the camera focus is working now, so it is definitely a software issue with newer CM versions.
Best regards,
Gandlz
Hello guys sorry about this I'm new to all this. Okay so I unlocked the boot loader and rooted my tablet successfully . I installed cwm and I updated to 6.0.3.1 because it said there was a new update. But when I try to boot my tablet in to recovery mode or boot menu it says entering recovery kernel image but just stays there . I am not able to go on fastboot boot menu recovery mode anything . I am able to use the tablet normally tho but I am not able to go on recovery mode. Did I do somethingwrong or what should i do? I would appreciate some help. Thanks
Re :
Hello,
Did you find a solution ? I have exactly the same problem. My A700 is stuck on this message : "entering recovery kernel image".
I've tried to reinstall Recovery with CMW but the problem is the same !
I hope you have a solution for me
pH
Well, I am going to guess, if you can't do a fastboot flash recovery xxxxxxx.img, and it says successful, but you can't boot immediately to recovery, then more than likely the recovery partition is damaged. And unfortunately, there is little you can do for it except mainboard replacement.
You can try fastbooting a stock recovery image (you can find them here in the forums, just search "stock recovery". Should be ICS and JB available.
If that don't work, Acer Service Center. Acer won't give us the SBK (secure bootloader key) to be able to use NVFlash to diagnose/possibly repair partitions.
I would always advise to NOT USE the Rom Manager app to do a recovery. Reason, you really have 0 idea what it is installing, or who made it.
It's been two days since i have been trying and now it's driving me crazy. I am on stock marshmallow with unlocked bootloader and root. I was trying something (irrelevant here) , and now the phone won't boot into recovery.
No green light when the phone turns on to press the volume buttons to boot into recovery.
Tried adb commands but they just reboot the device. Tried flashing ftf files but still the recovery won't come up.
Tried each and every recovery image out there but still no luck.
The recovery flashes with success but adb returns error "no devices/emulators found"
Btw I'm installing twrp recovery. If anyone knows a solution to this problem, please help
Ikhlaq737373 said:
It's been two days since i have been trying and now it's driving me crazy. I am on stock marshmallow with unlocked bootloader and root. I was trying something (irrelevant here) , and now the phone won't boot into recovery.
Click to expand...
Click to collapse
Could be relevant, you never know.
Ikhlaq737373 said:
No green light when the phone turns on to press the volume buttons to boot into recovery.
Tried adb commands but they just reboot the device. Tried flashing ftf files but still the recovery won't come up.
Tried each and every recovery image out there but still no luck.
The recovery flashes with success but adb returns error "no devices/emulators found"
Btw I'm installing twrp recovery. If anyone knows a solution to this problem, please help
Click to expand...
Click to collapse
How did you manage to "successfully" flash a recovery if adb doesn't even find the device. Usually when I flashed a TWRP I just booted into fastboot and did a quick fastboot flash. Never had any issues with that whatsoever. Maybe try that.
Here's the full story. I first unlocked the bootloader and flashed twrp, rooted and everything went fine. After a couple of months i decided to install lineage os , so i booted into recovery and wiped data, system etc. But i forgot to copy the lineage os zip , so i switched off the device(despite the error message "no os installed"), removed memory card and put files on it and inserted the card back. After this procedure, the phone stopped booting into recovery. Ever since then i am able to flash stock ftf files and everything but the device won't enter recovery so I'm unable to root it again. I hope this will help you understand the situation
Somebody please help
Ikhlaq737373 said:
Somebody please help
Click to expand...
Click to collapse
Try an alternative route.
Fully flash a stock ftf .291. Everything will be up to date then and you'll have the latest bootloader.
Then try two things.
First try fastboot flashing the latest TWRP from Nailyk.
Then boot to recovery holding power and volume keys as you boot and it will boot directly to recovery.
You could also try fully flashing an ftf.
Then use adb to fastboot flash a custom stock based kernel like advanced kernel which includes TWRP 3.0.2.
Use that to boot to recovery the old way and voila you have recovery.
Dobsgw said:
Try an alternative route.
Fully flash a stock ftf .291. Everything will be up to date then and you'll have the latest bootloader.
Then try two things.
First try fastboot flashing the latest TWRP from Nailyk.
Then boot to recovery holding power and volume keys as you boot and it will boot directly to recovery.
You could also try fully flashing an ftf.
Then use adb to fastboot flash a custom stock based kernel like advanced kernel which includes TWRP 3.0.2.
Use that to boot to recovery the old way and voila you have recovery.
Click to expand...
Click to collapse
Are you talking about the .291 ftf obtained from xperifirm ? Does that include the bootloader ?
I'll try the second solution(advanced kernel), thanks.
Ikhlaq737373 said:
Are you talking about the .291 ftf obtained from xperifirm ? Does that include the bootloader ?
I'll try the second solution(advanced kernel), thanks.
Click to expand...
Click to collapse
Yeah that's the one. At the least it will set your phone back to factory settings and you can just start all he root tutorials from the beginning.
Option 2 should work for you.
You should definitely make sure your adb on your PC is working and make sure fastvoot is as well. Just to be sure its not the PC side of things.
I realize this is a bit of a necro-post but I thought it might help someone.
At some point TWRP on the Z3 Compact switched from Volume Up+Power to enter recovery to Volume Down+Recovery.
I spent about an hour trying to get into TWRP because every bit of documentation I read said you have to "power on and then press volume up several times" to get into recovery.
However that is NOT the case.
To get into TWRP after it's been flashed you have to hold Volume Down and Power at the same time, then release Power once the screen lights up.
Dobsgw said:
Yeah that's the one. At the least it will set your phone back to factory settings and you can just start all he root tutorials from the beginning.
Option 2 should work for you.
You should definitely make sure your adb on your PC is working and make sure fastvoot is as well. Just to be sure its not the PC side of things.
Click to expand...
Click to collapse
Thanks dear . It (advanced kernel) worked like a charm
I spent about an hour trying to get into TWRP because every bit of documentation I read said you have to "power on and then press volume up several times" to get into recovery.
However that is NOT the case.
To get into TWRP after it's been flashed you have to hold Volume Down and Power at the same time, then release Power once the screen lights up.
Click to expand...
Click to collapse
this little titbit just saved me. been hours on this!!
Can't get into Recovery and Custom ROM Android
C:\adb>fastboot flash recovery TWRP-Z3-recovery-Android10-2019-10-11-TESTING.img
sending 'recovery' (13310 KB)...
OKAY [ 0.687s]
writing 'recovery'...
OKAY [ 0.906s]
finished. total time: 1.594s
fastboot reboot-bootloader
However, I no longer get into recovery and the Android system, but I still get into Fastboot mode.
Now I thought I flashed the recovery again but I can't boot in there .....
majikfox said:
I realize this is a bit of a necro-post but I thought it might help someone.
At some point TWRP on the Z3 Compact switched from Volume Up+Power to enter recovery to Volume Down+Recovery.
I spent about an hour trying to get into TWRP because every bit of documentation I read said you have to "power on and then press volume up several times" to get into recovery.
However that is NOT the case.
To get into TWRP after it's been flashed you have to hold Volume Down and Power at the same time, then release Power once the screen lights up.
Click to expand...
Click to collapse
I signed in just to say thanks! And yes, people still use the Z3 lol
Hi there. I got trouble rooting my Blackview BV5500Pro with Android 9.0
Its not the first smartphone im rooting, so im not new to this. But im also not a professional or something, even english is not my native language so sorry for my bad grammar.
At first i tried the way i done this bevore to my smartphones:
1. Unlock OEM via Fastboot
2. Flash TWRP 3.3.0 (The only working twrp i found) to Recovery
3. Boot into TWRP.
To this point everything works fine.
But when i install Magisk 21.4. i get a bootloop.
also when i install SuperSu 2.8.2
So i tried to patch the boot image via Magiskmanager App 8.0.7.. Everything works fine. I can flash the patched boot image via fastboot, twrp or sp flash tool. But when i open Magisk after booting the patched image, there is no option to install Magisk or root the Phone. Only to patch the boot image. Even when i boot the patched image directly with fastboot.
Maybe somone here can help me.
Best regards, Jules.
Edit: I Also treid to install Liniage OS 17 and 18. Via fastboot, twrp and sp flash tool, but also get a bootloop.
Hi
I'm sorry, I cant't answer your question, but I have one to you: I'm trying to install LineageOS on a bv5500pro too (by the guide from here), but I'm stuck at the TWRP installation. Can you tell me how you managed to do it and do you have perhaps a link to the TWRP you used?
I did unlock the bootloader by toggling OEM Unlock in developer settings, then via fastboot: fastboot flashing unlock. Then reboot.
Then I pushed TWRP 3.2 (from this source here, from the tutorial here) by fastboot flash recovery recovery.img. When I tried then to boot directly after flashing into twrp recovery by holding vol up + power, then selecting recovery mode and confirming with vol down, it tries to boot normally instead of recovery. I think, my TWRP flashing didn't work properly. Booting into TWRP by fastboot boot recovery.img doesn't work either, there it reboots and tries to boot normally too. fastboot tells me that it loses connection (normal, since my phone reboots, I think?):
Code:
fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.017s]
booting...
FAILED (status read failed (No such device))
finished. total time: 23.457s
What I have to confess, is that I did wipe the system, data and cache partitions using fastboot erase <partition>, perhaps someone knows if I have problems with twrp because of that? (I know that I shouldn't have done this, sometimes curiosity is equal to stupidity...) I did this because I tried to install LineageOS without twrp. Was a bad idea, I know now...
I am on a HP proBook using Debian 10 with adb and fastboot installed. Not sure if MK65xx drivers are installed. Might this pose problems?
Thanks in advance to all here!
EDIT: Sorry, I forgot to mention a lot of things. I corrected some of them here. A more complete overview in another post can be found here.
hi, at least im not alone having trouble with the BV5500pro. I don't remember where i got the twrp exactly, but i uploaded it for you.
File-Upload.net - recovery-verified.rar
Datei: recovery-verified.rar. Die Datei wurde von einem User hochgeladen. Laden Sie auch kostenlos Dateien hoch mit File Upload.
www.file-upload.net
At first i flashed TWRP with fastboot. But then everytime i could boot in twrp only one time. After the next reboot the stock Recovery was reinstalled. So i used the Stock images
Blackview BV5500 Pro factory firmware (flash file)
This Blackview BV5500 Pro firmware flash file (stock ROM) can help you easily un-brick or restore your device to its default or factory state. If you have previously rooted or modified the system (or other) partition of the phone in any way, flashing this stock ROM will overwrite all existing...
www.leakite.com
and replaced the recovery-verified.img with the TWRB image and fashed everyting wit sp flashtool on my phone. After that TWRP was permanent.
Ok, great, thanks for your fast reply. I'll try it again with your image.
GiRonimoon said:
At first i flashed TWRP with fastboot. But then everytime i could boot in twrp only one time. After the next reboot the stock Recovery was reinstalled.
Click to expand...
Click to collapse
How did you boot into TWRP then? By Volume up + power, then selecting recovery mode and confirm with vol down? or by terminal/fastboot command?
edit: small grammar
By Volume up + power.
Thank you
Ok, quick update: Flashing worked, but reboot not, I think. I managed to boot into TWRP, but I managed too once with my image before (I forgot to mention), where the screen was then not responding. A complete description of my case can be found here on xda. Sorry for the late corrections that are made in this post, I'll correct them above...
Now after the flash with the image from GiRonimoon above, I can boot into TWRP and the TWRP start screen shows: TWRP Recovery Project 3.3.0-by *nemo-nemo* (4pda.ru), and when I'm in, the screen is not responding. It was like this with my first TWRP image too, so perhaps the flashing didn't work and I have still my old image which is not working?
GiRonimoon said:
By Volume up + power.
Click to expand...
Click to collapse
Ok. But when I boot into recovery, the exact things I do is:
1. phone powered off
2. Hold volume up + power until boot mode selection screen appears
3. Select recovery mode with volume up, then confirm with volume down
4. the phone reboots (screen goes black for about 1 sec), Blackview logo is shown (as well as a 'orange state' warning message), 5 sec delay because of orange state.
5. screen goes black for 1/2 sec
6. TWRP is open, screen not responding, asking for password for decryption
Exactly the same for booting into recovery via terminal/fastboot (just insert fastboot command at 1.). So since the phone reboots once in between, is it possible that my new TWRP is erased every time? Do your BV5500pro behaves also like this (except the orange state, I think)?
Thanks in advance
How long you are waiting? In my case TWRP needs a long time to start. At first i was thinking that it freezes at startup.
I just foubnd out that every boot into twrp causes a boot loop.. Even when i just boot twrp to see the versionnumber, and then reboot normaly.
GiRonimoon said:
How long you are waiting? In my case TWRP needs a long time to start. At first i was thinking that it freezes at startup.
I just foubnd out that every boot into twrp causes a boot loop.. Even when i just boot twrp to see the versionnumber, and then reboot normaly.
Click to expand...
Click to collapse
When I manage to boot into TWRP it's rather fast - I have to wait around 7 sec or so, maybe 10. But I only manage sometimes. Normally I have to do fastboot boot recovery.img, and after that do the normal steps to boot into recovery. If I try to boot into recovery, it just tries to boot normally (which ends in a bootloop)...
But I think I'll try to flash a stock rom and retry from there, as it was suggested here.