Related
My almost two-year-old Hero froze this morning, so I had to take out the battery, but after this I've been unable to boot, it's stuck on the HeRO screen. I can't start recovery either, the only thing working is hboot / fastboot. Erasing user data using fastboot doesn't do anything.
Also, plugging the phone into charger doesn't signalize charging – the LED doesn't light up, and the PC doesn't recognize the phone either. Only fastboot does connect the phone to the PC, but adb doesn't work and all attempts to flash a new recovery or do anything else via fastboot end with "FAILED (remote: not allowed)":
Code:
c:\adb>fastboot devices
HT97JL903267 fastboot
c:\adb>fastboot boot recovery-RA-hero-v1.7.0.1.img
downloading 'boot.img'... FAILED (remote: not allow)
c:\adb>fastboot flash boot recovery-RA-hero-v1.7.0.1.img
sending 'boot' (3972 KB)... FAILED (remote: not allow)
I tried installing the official RUU updates (2.73.405.66, 2.73.405.5 and 1.76.405.1 too) but none of them could connect to the phone, Error [170]: USB Connection error.
I was using Elelinux-Hero-2.1-update1-Reloaded with radio 63.18.55.06SU_6.35.17.03 and recovery was Amon RA 1.6.2 I guess.
The phone did a similar thing 3 weeks ago but I was able to boot into recovery and erase data and cache and it worked fine afterwards. Now only fastboot is accessible.
Is there anything else I can do at this point or is the phone dead for good?
Disregard my previous post.
I left the phone booting for 30 minutes, the battery got uncomfortably hot, but the phone booted up eventually. Then I managed to install the official RUU from here.
It didn't solve anything though – it still takes around 20 minutes to boot, the touch screen doesn't work and I get an "android.process.acore" error all the time – but since the phone seems untouched (thanks to the RUU install) I can lodge a claim and get a replacement phone hopefully.
You could try putting HEROIMG.NBH on the sdcard and booting into hboot. If you go into fastboot and press vol-down it quickly scans for files on the SD, of which heroimg is one, and if it finds them, installs them.
Can't really help more than that. My phone did that last year, took it to the shop and ended up getting a new motherboard, cause the ROM chip was knackered.
One thing I would recommend though when you get it fixed is to flash an engineering bootloader, do if it breaks again you've got none of this "remote not allow" rubbish.
Of all the times to say disregard my last post.........
Sorry about that, thanks a lot though!
I suppose some hardware is broken in my Hero as well, I will take it back to the shop tomorrow.
Thanks again!
folks im at my nerves end... (hello btw)
firstly a thousand apologies to the mods if im posting this in the wrong place and a thousand apologies more to the rest of you for asking a question that has probably been answered time and time again.....
I can't get round it, iv been able to unlock bootloader and I thought that would have been the hardest part.... but I think I cant get my hands on the right, up to date files, in order to root my current system... iv been doing a ton of reading and just as many rooting attempts on my phone but to no avail......
the closest iv got in the command window was "error: device 'null' not found", to my understanding this is a driver related issue?...I dont know... if someone could hold my hand (im scared) and walk me through the process step by step I would be very, VERY grateful....
P.s; in exchange I can help you install CFW on a PSP.....lol right? (I actually made a pandora battery back in the day and im still rather proud of that)
UPDATE:........ So i think I was able to flash the proper Kernel (adroid plus kernal V42) but was unable to do flash recovery?
rootcheck says "root access is not properly installed on this device" still.....
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (14956 KB)...
OKAY [ 0.479s]
writing 'boot'...
OKAY [ 0.143s]
finished. total time: 0.624s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-2.8
.7.0-E6653-20151114_material.img
error: cannot load 'twrp-2.8.7.0-E6653-20151114_material.img'
UPDATE:
So i was able to do a flash recovery by renaiming the twrp file to simply twrp and adapting the code typed in the command window...... this caused my phone to soft brick or enter a bootloop....
after some swearing and more reading I was able to do a flash recovery with twrp-3.0.2-0-E5823.img (again by typing the exact name of the .img file in the command window....duuhhhh).... this allowed my phone to boot properly (thank God)... but root checker still says "root access is not properly installed on this device".....
I feel as if im close to my goal, what am I doing wrong!?......that soft brick served me as a cold shower and a lesson....this is kinda fun!
FINAL UPDATE:
BOOOM!!! success..... only took me all day...... still one thing though, i was unable to back my system due to lack of space on my SD card.... am I boned in this regard or can I create a back up later?
Thanks for the updates, i will try to follow your guide. how did you finally achieve success ?
Hey Rath,
First off im not responsibly for any damage caused to your device by the following guide....
....on to business...
Assuming your phones bootloader is unlocked, you have correctly installed ADB tools and the drivers required, allowed USB debugging and you know your build number you'll need to head over to this site...
https://kernel.andro.plus/kitakami_r2.html
scroll down....there you will see two sets of requirements one for the Xperia Z5 [E6653 / E6603] and one for the Xperia Z5 Compact [E5823 / E5803]
we are interested in the compact requirements.... you'll see that it says "32.2.A.5.11 -> v42 -" this means that for build number 32.2.A.5.11 you will need kernel version 42....
so keep scrolling down once you've figured out what version you need and click on "google drive V32 and later" for the Xperia Z5 Compact this will open a page with all the files inside (google drive)...either hover over with your mouse each file until you find "Z5C_AndroPlusKernel_v42.zip" or organize the files by clicking "last modified" in list view, this should show you the most recent file (v42) at the top of the list....
once you have found this file DL it and extract it to your desktop...copy ONLY the "boot.img" file into your platform-tools folder (android->sdk->platform-tools)....
next you'll need a recovery file or "twrp" to go with that, so head on over here...
https://www.androidfilehost.com/?fid=24459283995304864
and download that file, again copy it to your desktop (no need to extract) then copy this file as well to your platform-tools folder......copy the exact name of the file(TWRP-3.0.0.0-suzuran without the .img part...if youre on windows the .img will not show anyway..)...you'll need it later...
next open the command window by clicking on an empty space IN THE PLATFORM-TOOLS folder, then press shift+right click and select "open command window here" this will open adb tools...connect your phone via usb cable to your pc if it not already connected and type in the command window "adb devices" and hit enter....you should see your device listed...
if so type "adb reload bootloader" your phone should turn off and boot into bootloader (a blue led light should show in the top right corner of your phone)
if so type "fastboot devices" and hit enter...your device should show again on the list...
if so then type "fastboot flash boot boot.img" this will flash the kernel V.42 to your system....
you should see a couple of "OKAY"s and the time it took to flash the device....
next type "fastboot flash recovery *right click after the space and paste the exact name of the twrp file you copied earlier*.img
E.g: fastboot flash recovery TWRP-3.0.0.0-suzuran.img
and hit enter.... again you should see a couple of "OKAY"s and flashing times....
if all goes well you want to then type "fastboot reboot", your phone should then reboot...once you see a yellow light turn on on the top right corner press the down volume key several times until you enter the TWRP recovery menu.... if so, and the twrp is stable (ie it doesnt turn off on its own and reload) then the hardest part is done.....
click "reboot" on your phone and then click "system"...this will reboot your phone, this time let it run to see if it doenst get stuck in a bootloop....once your phone has loaded you'll want to install superSU....
go to the play store and DL rootchecker.... run the app and it will most likely tell you that your system isnt rooted yet (because we havent installed superSu) so head on over here...
http://www.supersu.com/download
scroll down and DL Recovery "Flashable.zip"...then take the file WITHOUT EXTRACTING IT and put it in the SD of your phone... reboot into recovery using the command window (adb reboot recovery) or turn off your phone, turn it back on and when you see the yellow light click volume down button repeatedly....
once in recovery select INSTALL click on the ZIP file you just added and the phone will install supersu, once done reboot your system and VOILA! check with the root checker app if your phone is root and have fun!....
I found this video to help me out a lot....he uses really old files and is rooting an xperia z5 but its essentially the same....
https://www.youtube.com/watch?v=dTlosea6SJE&t=709s
SwisSwiss said:
UPDATE:........ So i think I was able to flash the proper Kernel (adroid plus kernal V42) but was unable to do flash recovery?
rootcheck says "root access is not properly installed on this device" still.....
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (14956 KB)...
OKAY [ 0.479s]
writing 'boot'...
OKAY [ 0.143s]
finished. total time: 0.624s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-2.8
.7.0-E6653-20151114_material.img
error: cannot load 'twrp-2.8.7.0-E6653-20151114_material.img'
UPDATE:
So i was able to do a flash recovery by renaiming the twrp file to simply twrp and adapting the code typed in the command window...... this caused my phone to soft brick or enter a bootloop....
after some swearing and more reading I was able to do a flash recovery with twrp-3.0.2-0-E5823.img (again by typing the exact name of the .img file in the command window....duuhhhh).... this allowed my phone to boot properly (thank God)... but root checker still says "root access is not properly installed on this device".....
I feel as if im close to my goal, what am I doing wrong!?......that soft brick served me as a cold shower and a lesson....this is kinda fun!
FINAL UPDATE:
BOOOM!!! success..... only took me all day...... still one thing though, i was unable to back my system due to lack of space on my SD card.... am I boned in this regard or can I create a back up later?
Click to expand...
Click to collapse
i wonder if you backup the DRM keys\TA partition
In regards to why i was unable to create a back up right away? Not sure, think it was simply a matter of volume...
Had a crappy 4gb micro sd In there....
In case you bricked your watch, here is a tutorial how to unbrick the watch:
1. What is a "bricked" watch?
A bricked watch does no longer boot. It typically stops at the boot logo and waits forever. This can happen for example, if a flash of the system image failed and the boot image can no longer boot the system.
In such cases, you cannot reach adb from the command line, so there seems to be no way to recover the watch. Fortunately, it has been discovered how fastboot can be entered without a running system.
2. Procedure
Step 1: Get into fastboot
This is the most difficult part. @kiralex1995 has developed a procedure that will lead reproducible to boot the watch into fastboot mode, but it may take many tries (one user reported that it took him 30 min of tries).
Follow this guide: https://forum.xda-developers.com/sm...tches/amazfit-boot-fastboot-directly-t3546829
When you are in fastboot and see the fastboot logo, you have mastered the most difficult part.
Step 2: Choose a ROM to flash on the watch
There are currently three possible ROMs to choose from:
a.) The English AmazFit firmware 1.3.0n
Download the following file on your PC: https://mega.nz/#!xIkC1IQZ!bLLSN9BMvbp7zhZHg2oQq6p4ud-EFyUYkatCGKgHeS8
b) The Chinese AmazFit firmware 1.2.5a
Download the following file on your PC: https://mega.nz/#!tNdggR4b!VXmExGqdNixrj8pVLqTkAi_munmjF5RidRJP9L-LAXE
c) An old Chinese AmazFit firmware 0.9.50:
Download the following file on your PC: https://mega.nz/#!wY9mEQoI!0ARB0MaK0byjttgrPmJJQX4ZFdIXgHOUquxqFhghg7U
Step 3: Download flash script from xda
Download the attached flash script from this post to your PC.
Step 4: Unpack the archive on your PC
Depending on you PC choose the right method to extract the files in the ROM archive and the flash script.
Step 4: Boot the watch into special recovery
Check that your fastboot drivers see that watch (which should still show the fastboot logo):
'fastboot devices'
You should see your device listed. Otherwise check your fastboot driver installation on your PC. (Note: On Linux you sometimes need to use "sudo fastboot ...".)
Then boot the modded recovery that is included in the archive you unpacked in step 2.
'fastboot boot Amazfit-mod-recovery.img'
You will see a "FAILED" message on your commandline. This is normal.
On the watch you should see the recovery triangle and the text "No command".
Step 5: Transfer the ROM files and the flash script onto the watch
First check that you are now able to connect to your watch via adb:
'adb devices'
You should see your watch listed. Otherwise check you "adb driver" installation. For Windows take care that you use Khoushs universal adb drivers.
Then push the files to the watch:
'adb push boot.img /data/media/0/
adb push system.img.gz /data/media/0/
adb push md5s.txt /data/media/0/
adb push flash_rom.sh /data/media/0/'
Step 6: Enter the shell on the watch and check your files
After you have successfully transferred the files to the watch, you then enter the shell on the watch:
'adb shell'
You should see only a "#", meaning you have full root access.
Now switch drirectory to the sdcard
'cd /data/media/0/
ls'
You should see your files on the "sdcard", including the ones that were pushed before
7. Start flashing the files
Run the flash sccript with the following command on the watch:
'sh flash_rom.sh'
If everything worked correctly, you should see something like:
Code:
Validating images
boot.img.gz: OK
system.img.gz: OK
Starting to flash now. DO NOT TURN OFF OR REMOVE THE USB CABLE! Press Enter to continue or CTRL-C to stop!
Flashing boot.img
2304+0 records in
2304+0 records out
9437184 bytes (9.0MB) copied, 2.075793 seconds, 4.3MB/s
Flashing system.img
210944+0 records in
210944+0 records out
864026624 bytes (824.0MB) copied, 107.981352 seconds, 7.6MB/s
Finished
If you see any error message during or after flashing, then DO NOT REBOOT the watch, but get some help or analyse yourself, what went wrong. You can still reflash.
8. OPTIONAL: Delete the dalvik-cache
You can erase the dalvik-cache on the watch with the following command:
'rm -rf /data/dalvik-cache'
This will make the system "re-optimize" all apps when it boots (successfully) the next time. This is optional, as you could always do that later again.
9. Reboot the watch
If everything is ok, then you can reboot the watch
'reboot'
Your watch should boot normally into the flashed system, you downloaded. CONGRATULATIONS, you unbricked your watch!
Thank you for this post.
Neuer_User said:
In case you bricked your watch, here is a tutorial how to unbrick the watch:
1. What is a "bricked" watch?
A bricked watch does no longer boot. It typically stops at the boot logo and waits forever. This can happen for example, if a flash of the system image failed and the boot image can no longer boot the system.....[/B]
Click to expand...
Click to collapse
I'm so happy that my post help people. Thanks to your job and thanks to your rom @Neuer_User .
I wonder if it would be possible to create a rom with all google services included ?
First watch has just successfully been unbricked (1immortals watch) [emoji106] [emoji2]
kiralex1995 said:
I'm so happy that my post help people. Thanks to your job and thanks to your rom @Neuer_User .
I wonder if it would be possible to create a rom with all google services included ?
Click to expand...
Click to collapse
Yes, it would be possible. But you also need to look at connectivity. The watch checks does turn off wlan automatically.
@Neuer_User, you're a GOD !!!
All bow @Neuer_User , he is the true ruler of Amazfit, conquer of the M200 SoC, bringer of root to the MIPS platform ! all hail the king !!!
Neuer_User said:
Yes, it would be possible. But you also need to look at connectivity. The watch checks does turn off wlan automatically.
Click to expand...
Click to collapse
Well i guess constant WiFi would dramatically reduce the running time? On the other hand it might just be turned on for short periods, don't know how Google does that.
1immortal said:
@Neuer_User, you're a GOD !!!
All bow @Neuer_User , he is the true ruler of Amazfit, conquer of the M200 SoC, bringer of root to the MIPS platform ! all hail the king !!!
Click to expand...
Click to collapse
Congratulations and thanks to Neuer_User.
hi, after this step the watch reboot and restart the loop on logo. why?
'fastboot boot Amazfit-mod-recovery.img'
You will see a "FAILED" message on your commandline. This is normal.
On the watch you should see the recovery triangle and the text "No command".
edit: after more test, i'm not able to go to recovery mode. For an errore, when i try another time to go to Fastboot mode, i push 2 times the button and i ERASE ALL the watch, now i have a device called JZ4785 USB Boot Device.
There's some way to save this watch?
Thanks.
I think that you have entered some "Deep" flash mode - the JZ4785 is the SoC model, and you need to provide a driver for the flashing process.
please download this tool:
ftp://ftp.ingenic.com/DevSupport/Tools/USBBurner/cloner-1.2.0/cloner-1.2.0-windows_release.zip
you will need a 32 bit machine for running that.
it contains the drivers and the software for flashing. I hope that there's a way of creating a dump file of a working watch, and flashing it directly on yours.
1immortal said:
I think that you have entered some "Deep" flash mode - the JZ4785 is the SoC model, and you need to provide a driver for the flashing process.
please download this tool:
ftp://ftp.ingenic.com/DevSupport/Tools/USBBurner/cloner-1.2.0/cloner-1.2.0-windows_release.zip
you will need a 32 bit machine for running that.
it contains the drivers and the software for flashing. I hope that there's a way of creating a dump file of a working watch, and flashing it directly on yours.
Click to expand...
Click to collapse
This could indeed be the case. Noone of us ever entered that mode so far. It would be very good to understand, how you really got into that. It must have happened in the first step, where you were supposed to enter fastboot. Did you see the screen on the watch with the two options? There is a video in the link of @kiralex1995 post. Maybe you can comment, what exactly looked identical for you and where it exactly started to differ.
In case, you are really in that SOC flash mode, the Ingenic USBburner tool would indeed, probably, be the right tool to reflash the watch. As I mentioned, nobody here used that before. I have some experience with similar tools for the MTK platform. I believe that it should be possible to generate the necessary dump from a working watch, but this is all theory so far.
Where are you located?
well, nothing helped, there's no configs for the JZ4785, and there's no relevant information of partitions offset for flashing. we tried to flash both 1.2.5 and some generic ingenic image, with a lack of success as well
contacted ingenic for some clarification and some help, lets see where this lead to ...
Hello and thanks for tour support.
Also "launcher has stopped" i have to consider as a brick situation?
Palese led me know because i tried to update from chinese firmware but Now it doesn't work, i am able to start in fastboot mode
Thank you vero much fo and your advice
regarding the launcher errors, please try to unpair your watch and re-pair it again, it's a non-brick situation.
after i worte: fastboot boot Amazfit-mod-recovery.img . it says:
downloading 'boot.img'...
FAILED (command write failed (Unknown error))
finished. total time: 5.014s
alon1211 said:
after i worte: fastboot boot Amazfit-mod-recovery.img . it says:
downloading 'boot.img'...
FAILED (command write failed (Unknown error))
finished. total time: 5.014s
Click to expand...
Click to collapse
Try a different USB cable. Bad cables are known to produce that error.
This is pretty awesome! I used this to convert my Chinese Amazfit watch to English ROM, and it seems to work OK.
However, there's a piece missing from the bundle -- the recovery image. There's an OTA available, and I pulled the update.zip file using the Fastboot trick so the OS didn't load and delete it - then booted the "mod recovery". Here's that update.zip (to 1.3.2b): https://mega.nz/#!nIBDhLrR!7nQlWsn-TF4bsMNBSaTOfimY-vo-Z2R3dSavrDp1wsA
The OTA didn't succeed -- when it went to reboot to recovery and apply the update, it booted with Chinese text in recovery boot and failed with just one word - "Error". I'd imagine that's because recovery.img wasn't part of the bundle, so my watch still has the Chinese ROM recovery on it. Looking at the update.zip, it's fairly clear it's built in English - with English error messages in "updater-script".
I'm hunting around for the English ROM's recovery image, and will probably find it in the next few minutes, but figure I should mention this hole - and that this routine is also useful for converting to English. It'd been demonstrated before that you can run the English ROM just by flashing it (and boot.img), but no unified thread seems to exist for it yet (that I can find via Googling at least). :good:
edit: Literally 5 minutes later, bam. https://forum.xda-developers.com/showpost.php?p=71264431&postcount=599 - I downloaded that Fix_recovery bundle, pushed it to /data/media/0/ from the mod recovery, ran it, and it gave some errors but fell back to the "dd" method. So, all that's needed to get a complete English ROM flash is to add recovery.img and the line:
Code:
busybox dd if=recovery.img of=/dev/block/platform/jzmmc_v1.2.0/by-name/recovery bs=4096
Hi All,
I have just received my watch from a BT/WiFi issue repair.
I am not sure if they have fixed it as starting the watch and
I am getting "Unfortunately the launcher has stopped" message.
I do see the charging indicator but this is pretty much the only thing I see.
If I reboot pushing the button I get to the same point.
I see that this is an old problem. How do you guys fix this?
I do have adb shell access. Can I somehow reset to factory default using adb?
Thanks
Dimitar
dpenevdpenev said:
Hi All,
I have just received my watch from a BT/WiFi issue repair.
I am not sure if they have fixed it as starting the watch and
I am getting "Unfortunately the launcher has stopped" message.
I do see the charging indicator but this is pretty much the only thing I see.
If I reboot pushing the button I get to the same point.
I see that this is an old problem. How do you guys fix this?
I do have adb shell access. Can I somehow reset to factory default using adb?
Thanks
Dimitar
Click to expand...
Click to collapse
You can boot into the bootloader (fastboot) with "adb shell reboot bootloader". Then in fastboot you can tyoe "fastboot -w continue". That will boot the watch normally, but clear cache and all userdata.
Neuer_User said:
You can boot into the bootloader (fastboot) with "adb shell reboot bootloader". Then in fastboot you can tyoe "fastboot -w continue". That will boot the watch normally, but clear cache and all userdata.
Click to expand...
Click to collapse
Thanks Neuer_User,
what I did:
1. I have entered Fastboot as you explained. Fastboot logo on the watch
2. :~$fastboot devices
0123456789 fastboot
:~$fastboot -w continue (this in the Linux bash shell)
resuming boot...
FAILED (status read failed (No such device))
finished. total time: 6.395s
:~$
The watch reboots due to above
Or should I enter fastboot watch shell first?
The above procedure doesn't help.
Still I get "Unfortunately the launcher has stopped"
This should be on the original Chinese ROM 1.2.9 as far as I remember. It was long time ago I ship the watch to China for repair.
Should go to Pace ROM. what would you advice.
Thank you once again.
dpenevdpenev said:
Thanks Neuer_User,
what I did:
1. I have entered Fastboot as you explained. Fastboot logo on the watch
2. :~$fastboot devices
0123456789 fastboot
:~$fastboot -w continue (this in the Linux bash shell)
resuming boot...
FAILED (status read failed (No such device))
finished. total time: 6.395s
:~$
The watch reboots due to above
Or should I enter fastboot watch shell first?
The above procedure doesn't help.
Still I get "Unfortunately the launcher has stopped"
This should be on the original Chinese ROM 1.2.9 as far as I remember. It was long time ago I ship the watch to China for repair.
Should go to Pace ROM. what would you advice.
Thank you once again.
Click to expand...
Click to collapse
Hmm, if that doesn't work, try "fastboot erase cache" and "fastboot erase data". That will really completely delete all user and cache data. The next restart should take a long time.
Hi,
I'm new here, so please excuse me if I am posting in the wrong category.
So I tried to root my Doogee F7 (not the pro version) using fastboot and TWRP, and it resulted in a sort of bootloop where it says:
Code:
Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
And then it restarts and gives the same message again. This loop has been going on for some time and I can't stop it because the phone has a non-removable battery and I have tried every possible combination of buttons (i.e. Power + Volume Down + Volume Up).
The process I used in my attempt to root was as following:
1. I used
Code:
adb reboot bootloader
to go into fastboot. (I already set up everything like USB debugging and OEM unlocking in the developer options)
2. I then used
Code:
fastboot oem unlock
and pressed Volume Up to unlock the bootloader. All was successful.
3. I then tried to flash TWRP to recovery and I believe this is where everything went wrong. I flashed it using
Code:
fastboot flash recovery recovery.img
and it was successful, according to the command prompt:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery "C:\Users\momen\Downloads\recovery (1).img"
target reported max download size of 134217728 bytes
sending 'recovery' (12832 KB)...
OKAY [ 0.562s]
writing 'recovery'...
OKAY [ 0.213s]
finished. total time: 0.779s
4. After it finished I used
Code:
fastboot reboot
to reboot the phone and that's when it got stuck.
At the moment I am just letting my battery run out, as I have no other way of turning off the phone, and neither adb nor fastboot is working.
I don't really know if my device was even supported, but I followed the instructions on various websites stating that I should first unlock my bootloader, then flash TWRP, then flash superSU onto it, and my phone would be rooted. I used the latest TWRP image, and I think that was where I went wrong. Is there anything I can do to get my phone to work again?
Hey! i´m sorry for your phone, can you tell me any updates, is it fixed now? what happened? i am about to do the same process to root my Doogee F7 and i´m very worried that my phone gets bricked, so please, i need your recommendations.
I hope everything is alright with your phone.
solartediego said:
Hey! i´m sorry for your phone, can you tell me any updates, is it fixed now? what happened? i am about to do the same process to root my Doogee F7 and i´m very worried that my phone gets bricked, so please, i need your recommendations.
I hope everything is alright with your phone.
Click to expand...
Click to collapse
Ah yes, sorry for not updating. I managed to connect my phone to my PC again using the flash tool and then I could flash the original ROM back onto it. I found the ROM by Googling for a bit tho I dont have a link. Be aware that if you do this, it basically factory resets your phone, locking your bootloader again and all. If you do manage to root your phone please contact me as I still have not managed to do so.
Edit: This process of flashing back your ROM always works as long as your phone powers on, so don't worry too much about bricking your phone. I think I've bricked my phone over 20 times trying to root it, and it worked every single time.
Hello there. I suggest that you use "fastboot boot recovery.img" than using "fastboot flash" if you are not sure if the custom recovery works (or if you just want to test/try it). In this way, you'll just boot the custom recovery temporarily (and your stock recovery is still in tacked).
For rooting your device, first you'll need a working custom recovery for your device (you used TWRP, very first if it works or compatible with your device).
Insyder28 said:
Ah yes, sorry for not updating. I managed to connect my phone to my PC again using the flash tool and then I could flash the original ROM back onto it. I found the ROM by Googling for a bit tho I dont have a link. Be aware that if you do this, it basically factory resets your phone, locking your bootloader again and all. If you do manage to root your phone please contact me as I still have not managed to do so.
Edit: This process of flashing back your ROM always works as long as your phone powers on, so don't worry too much about bricking your phone. I think I've bricked my phone over 20 times trying to root it, and it worked every single time.
Click to expand...
Click to collapse
Hi.How you actually managed to connect your phone to PC using flash tool if you were in a bootloop and had no access to fastboot mode or recovery?
ciubsy2004 said:
Hi.How you actually managed to connect your phone to PC using flash tool if you were in a bootloop and had no access to fastboot mode or recovery?
Click to expand...
Click to collapse
Im interested too in your process to flash TWRP again, as i am in the same boot loop than you with a Doogee S60. I´ve waited till the battery ended, but now flash tool doesn´t recognize my phone. If i charge the battery, i get a boot loop again..
TheBidan said:
Im interested too in your process to flash TWRP again, as i am in the same boot loop than you with a Doogee S60. I´ve waited till the battery ended, but now flash tool doesn´t recognize my phone. If i charge the battery, i get a boot loop again..
Click to expand...
Click to collapse
I have managed to get the flash tool recognizing my phone.Had to keep pressed volume up,if i recall properly(or try volume down) before connecting usb cable to phone with flash tool opened and . It was a while ago though and i can't remember exactly which key was for sure. Hope this helps
EDIT: I plugged a USB 2.0 hub in my pc, and now it works flawlessly. I'm leaving this here if someone faces the same problem I had.
I'm a long time user of custom roms, I was in Paranoid Android but wanted to try MIUI 12. Now, after using it for some days, I wanted to go back, but fastboot doesn't allow to flash recovery (TWRP 3.3, official).
If i put fastboot.exe devices, the output is my ID
Code:
dbb4eed4 fastboot
However, If I put it for a second time, the output is the following, and my phone screen turns black, asking for a key to shutdown.
Code:
???????????? fastboot
For fastboot.exe flash recovery twrp.img, the output is the following, also turning the screen black.
Code:
Sending 'recovery' (31068 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
Both options regarding USB debugging are on (the second one asked for a Xiaomi ID), bootloader was unlocked long time ago.
Any ideas what's happening? Is MIUI 12 messing with fastboot?
Thanks in advance.
Did you did that after usb debugging turned on
Did you try command like adb shell?
If you did this usb debugging will pop up for the recognition with your pc to smartphone
Yes Miui ask for ID it is your phone number which was you put when you try to unlock bootloader
And for recovery try different recovery
I DO feel MIUI 12 messed up something on the internals. For example, earlier I was able to easily paste files to /system/xbin location, but after upgrading to MIUI 12 it has suddenly become read only. Very weird.
HearseRider said:
I DO feel MIUI 12 messed up something on the internals. For example, earlier I was able to easily paste files to /system/xbin location, but after upgrading to MIUI 12 it has suddenly become read only. Very weird.
Click to expand...
Click to collapse
It's because your space directory is full.
I had this problem there too, I solved it by reseting dalvik cache with twrp