Related
Hi I am a newbie here and I have a Nexus one.
After unlock and rooted, i tried to enter the recovery mode. But I encounter problem. I cannot get into the green recovery mode. Instead I got an exclamation mark (!) warning with a little android standing on side of the mark. Can anybody tell me what I did wrong?
Thank you,
Jack
Did you flash amon-RA-1.7.0 yet?
You didn't install a custom recovery image. See the rooting guide here and it tells you how to do that.
No.. I only unlocked and rooted.
But I am not sure if my phone is rooted because it doesn't indicate that the phone is rooted after i run the superboot.bat file. The command prompt only came up for a sec and then gone.
When I open my phone. It is just like a new Nexus One. Except for unlocked sign when I boot up.
Thanks for the help
Jack
It's unlocked, now flash the recovery image, back-up, then wipe and flash Rom.
evilkorn said:
You didn't install a custom recovery image. See the rooting guide here and it tells you how to do that.
Click to expand...
Click to collapse
I followed the instruction here.. it didn't say I have to install a custom recovery image. Can you show me where? Thanks
***Informative Links*** - Read before clicking "New Thread"
http://forum.xda-developers.com/showthread.php?t=618768
Root the Nexus with ROM Links *Updated*
http://forum.xda-developers.com/showthread.php?t=612858
7. Flash Amons RA Recovery Image from here
Hi, thanks for the tip
I was able to boot into the recovery image and do a back up from there.
Now I am trying to flash the image into my Nexus one. But when I type fastboot-windows flash ... it says unknown partition and cannot recognize the file name..
can you please help again? thanks.
The terminal method from the phone is probably easier for you to do.
Most likely you didn't cd to the correct directory where the file is from command prompt. Give us a picture of what you did and the error and the steps you took to get to the point you are at because the guide and programs work.
hi.. i spent a lot of time reading and trying.. finally this is what i did to make it work
Step 1. fastboot-windows boot recover image file <-- this is how to got into recovery mode and back up
Step 2. fastboot-windows flash recovery recovery.image.file.name <-- this replace my original recovery flash and the little annoy android man is gone
I did backup again after Step 2. By now I think I realize that Step 1 is the same as Step 2. But no harm backing up two times..
I then installed a new rom into my N1.. everything looks fine now.. i will go ahead and try out some features..
Thank you for all the advices
Hi was wondering if any1 had a nanodroid image of the stock nexus 1 system i accdently deleted mine and now am stuck with a non working phone, ive tryed flashing different FRF files 1 boots but theres no screen.
if any1 can help thanks.
ok ive download the frf91 full but theres an issue when installing it it pops up with an error installing update. assert failed : !less_than_in and a long number, get prop("ro.build.date.ut"))
so what am i doing wrong ive reinstalled the started flash recovery
scoobyturbo said:
Hi was wondering if any1 had a nanodroid image of the stock nexus 1 system i accdently deleted mine and now am stuck with a non working phone, ive tryed flashing different FRF files 1 boots but theres no screen.
if any1 can help thanks.
ok ive download the frf91 full but theres an issue when installing it it pops up with an error installing update. assert failed : !less_than_in and a long number, get prop("ro.build.date.ut"))
so what am i doing wrong ive reinstalled the started flash recovery
Click to expand...
Click to collapse
i dont understand your last sentance.
do you have a working recovery ? if so, download whatever rom you like and flash it. wipe the phone first. should be fine.
ohgood said:
i dont understand your last sentance.
do you have a working recovery ? if so, download whatever rom you like and flash it. wipe the phone first. should be fine.[/QUOTe
yes i do have a working recovery i'm trying to get back to the standerd rom, but i cant seem to get it to install.
its a uk vodafone nexus 1 with unlocked Bootloader
Click to expand...
Click to collapse
You have Vodafone Nexus? Probably have SLCD? In that case, stock FRF91 won't work for you. You need Vodafone image. Or you could flash Korean version, KR_KT_... .
If you have unlocked bootloader, just unpack the ROM ZIP and do:
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
You can also do it for FRF91, if you don't have SLCD version.
Jack_R1 said:
You have Vodafone Nexus? Probably have SLCD? In that case, stock FRF91 won't work for you. You need Vodafone image. Or you could flash Korean version, KR_KT_... .
If you have unlocked bootloader, just unpack the ROM ZIP and do:
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
right big thanks to you phones now working again i ow u 1 spent the last 5 hrs trying to get it to work
once again THANK you very much
Click to expand...
Click to collapse
Hello community!!
I'm new to the HTC/Incredible S world, I have a rooted/cfw LG P500 and now I bought this great phone. Problem is that I updated it to the last official version before this try.
So I went to the official site and I followed successfully the HTC site steps to unlock the bootloader (golden card?) and now I'm trying to follow the guide
http://forum.xda-developers.com/showthread.php?t=1385084
But I have some problems.
First of all clearly the revolutionary program doesn't work (HBOOT 2.0).
I booted to the bootloader (power+volume down) and I had the error "main version is older" then I copied on the SD card the file for the recovery PG32IMG_Vivo_Gingerbread_S_KT_KR_2.32.1010.1_Radio_20.2810.30.085AU_3805.06.03.16_M_release_199684_signed.zip, I renamed it PG32IMG.zip, it loads it but when I press recovery it gives me an allert icon (the phone with a red triangle + red "!" ) and it does nothing.
I installed the SuperUser app like it is written in the post but when I type SU under the adb shell and it gives me "permission denied".
What could I do?
Is it even possible to downgrade it to a rootable/customable version?
If someone write a guide for rooting with the last update installed from original s-on step to step will be very util and a lot of people will be gratefull!
Inviato dal mio HTC Desire usando Tapatalk
Bootloader unlock and goldcard are 2 seperate things. Bootloader unlock is required at the moment for flashing recovery and superuser for rooting the phone.
Gold card is required for flashing another carriers rom.
Read this thread about recovery http://forum.xda-developers.com/showthread.php?t=1104765
After that you can enter recovery mode and flash a superuser zip file http://goo-inside.me/superuser/
My guide should be able to downgrade your rom and get s-off after that (if after researching you decide you require it) http://forum.xda-developers.com/showthread.php?t=1373697
Hope this helps
Thanks, I'm going to try this as soon as I can, I'll write back the results
edit:
It seems like I can't even pass the first step, the 4EXT Recovery Updater doesn't work, it crushes at EVERY menu item....
(I waited 5+minutes and I had the internet connection on).
I checked and the boot loader says "unlocked". Notice that my device is, of course, NOT rooted (at least for what I know for "rooted", it is still unlocked by the HTC official method)....
you need root to use the recovery updater.
download the recovery image and flash it in fastboot
Thanks it is finally working!!
I totally forgot that you flash with fastboot via windows console, not within the bootloader....
I hope to finally install something tonight, I'll post some news later.
Thanks again!
edit:
Nothing..I went successfully to the RUU downgrade part but that doesn't work, I tried from the normal system and it blocked because of the hboot version, then I tried within the phone fastboot phase and it blocked again, giving the security failed error...
sariel82 said:
Thanks it is finally working!!
I totally forgot that you flash with fastboot via windows console, not within the bootloader....
I hope to finally install something tonight, I'll post some news later.
Thanks again!
edit:
Nothing..I went successfully to the RUU downgrade part but that doesn't work, I tried from the normal system and it blocked because of the hboot version, then I tried within the phone fastboot phase and it blocked again, giving the security failed error...
Click to expand...
Click to collapse
Could I get a couple of screenshots to help with debugging please?
Sure, ASAP
Hi!
I have successfully rooted my phone on the last update 2.3.5
The steps I made:
1. Going to htcdev and unlocked the bootloader
2. Flashed a recovery image from clockworkmod.com
3. Installed SuperUser from clockworkmod.com using recovery
I collected the information from a few threads here and had no problem.
I didn't tested custom roms, all I wanted was to root and worked just fine.
I can detail my steps if someone need it.
edit:
It seems I cannot post the images, too noob ....
Anyway:
I had a photo of the phone in the custom recovery mode, another of the phone with the 4EXT recovery successfully flashing his recovery, another of the script of your post running with this message:
(no errors)
Do you have an unlocked bootloader from htcdev.com (I have)
y OR n:y
<waiting for device>
...
(bootloader) Lock successfully..
FAILED (status read failed (Too many links))
finished. total time: 0.239s
Note: run the RUU in fastboot mode
If all steps etc etc
Now if I try to run RUU NOT in fastboot mode I receive the message:
The Utility of ROM udating can't update the Android device.
Take a valid ROM updating Utility and try again
(I'm translating from Italian)
If I try to go to fastboot after running the script I need to go to hboot using volume down+power since you can go to fastboot only through bootloader and HIS first step is to check the bootloader file (am I right?)
so, since it is again LOCKED the custom boot file I was using PG32IMG_Vivo_Gingerbread_S_KT_KR_2.32.1010.1_Radio_20.2810.30.085AU_3805.06.03.16_M_release_199684_signed
doesn't work anymore and the old one neither so I have to unlock it again and it goes the loop......
So this is the situation, I hope I will be able to post some image soon...
sergiopat said:
Hi!
I have successfully rooted my phone on the last update 2.3.5
The steps I made:
1. Going to htcdev and unlocked the bootloader
2. Flashed a recovery image from clockworkmod.com
3. Installed SuperUser from clockworkmod.com using recovery
I collected the information from a few threads here and had no problem.
I didn't tested custom roms, all I wanted was to root and worked just fine.
I can detail my steps if someone need it.
Click to expand...
Click to collapse
Thanks, I did too the 3 steps, rooting my device successfully...
But I think I need to do a total S-OFF (deeper than the HTC one) to use the CFWs.
It should be like: follow the above 3 steps and:
4. use some script/console command to prepair the device
5. DOWNGRADE it to 2.2 or something
6. use the "revolutionary" Utility to S-OFF permanently
7. flash the ROMS from the recovery
I cannot pass the 4th step.
sariel82 said:
Thanks, I did too the 3 steps, rooting my device successfully...
But I think I need to do a total S-OFF (deeper than the HTC one) to use the CFWs.
It should be like: follow the above 3 steps and:
4. use some script/console command to prepair the device
5. DOWNGRADE it to 2.2 or something
6. use the "revolutionary" Utility to S-OFF permanently
7. flash the ROMS from the recovery
I cannot pass the 4th step.
Click to expand...
Click to collapse
OK, I thought you only wanted to root.
Thank you anyway
You don't need s-off for CFW's, just the unlocked bootloader. I cannot help you any further until I see screenshots as I'm getting lost in your descriptions. Ctrl prtscrn, paste in paint.
Well, I have the screenshots but I can't post web links in the forum (new user).
Let's see if I can flash some cfw in the mean time
Now I can post
The phone goes successfully in recovery mode:
http://imageshack.us/photo/my-images/406/img20111215194852.jpg/
Screen of the script with the error:
http://imageshack.us/photo/my-images/41/cmdok.png/
The screen of the phone while RUU got the error:
http://imageshack.us/photo/my-images/440/img20111215195909.jpg/
The RUU screen (translation in the posts above):
http://imageshack.us/photo/my-images/703/catturaruunotok.png/
Btw I tried to flash cyanogenmod, revHD e runnydroid following the instructions (wipe all, super wipe etc), every step was successfull, even the flash part (inistall zip from sdcard), but after the reboot it goes in boot loop (standard white HTC loading screen forever)
sariel82 said:
Now I can post
The phone goes successfully in recovery mode:
http://imageshack.us/photo/my-images/406/img20111215194852.jpg/
Screen of the script with the error:
http://imageshack.us/photo/my-images/41/cmdok.png/
The screen of the phone while RUU got the error:
http://imageshack.us/photo/my-images/440/img20111215195909.jpg/
The RUU screen (translation in the posts above):
http://imageshack.us/photo/my-images/703/catturaruunotok.png/
Btw I tried to flash cyanogenmod, revHD e runnydroid following the instructions (wipe all, super wipe etc), every step was successfull, even the flash part (inistall zip from sdcard), but after the reboot it goes in boot loop (standard white HTC loading screen forever)
Click to expand...
Click to collapse
After you flash a custom ROM in recovery, you have one last step to do to prevent the hang. You extract the boot.img file from the ROM's zip file and then manually flash it in FASTBOOT mode on the phone:
FASTBOOT flash boot [path to boot.img]
That totally solved the problem
Thank you ALL!!!
sariel82 said:
That totally solved the problem
Thank you ALL!!!
Click to expand...
Click to collapse
Hi,
Please list the methods you use from the start. I have also 2.3.5 and hboot 2.0. cant manage to downgrade, i always getting an error.
Thanks
htc developer site -> unlock bootloader
find and download this file:
PG32IMG_Vivo_Gingerbread_S_KT_KR_2.32.1010.1_Radio _20.2810.30.085AU_3805.06.03.16_M_release_199684_s igned.zip
copy it on the sd card and renamto to pg32IMG.zip
reboot in power+volume down mode
go in fastboot
from your pc use fastboot to flash this recovery:
http://forum.xda-developers.com/showthread.php?t=1104765
copy to sd card the superuser file:
http://goo-inside.me/superuser/
enter recovery mode and flash the zip
Then if u want to flash a custom rom you dont need to downgrade, just copy the zip into the sd card, flash it, copy on the sd card the boot.img you find inside the rom zip file and reboot in fastboot (power+volume down)
FASTBOOT flash boot [path to boot.img]
and reboot and the job is done!
I rooted my phone without knowing about s-off and its s-on and i installed miui and i cant boot that room it gets to the miui logo and just sits there is there anyway at all to fix this
Edit:
ok now it wont turn i connect my usb to the phone and the orange light appears i get the sounds on windows saying its connected then it disconnects and then dose this over and over again so i have no idea what is going on please please help its really annoying me
If you are still s-on you need to manualy flash the boot.img or it will just boot loop. I use Flash Image GUI but there are other ways
Sent from my Vivid 4G using xda premium
Spectrejester said:
If you are still s-on you need to manualy flash the boot.img or it will just boot loop. I use Flash Image GUI but there are other ways
Sent from my Vivid 4G using xda premium
Click to expand...
Click to collapse
could u give me more info please
new problem
re edited to top post
Your battery is dead and cwm doesn't support off-mode charging, hence the reason you get the orange light but only for a moment. You can't charge the phone while its off..and you incorrectly flashed a custom rom. If you can find a way to charge your batt out of the phone you can fix this by either flashing the proper boot.IMG for the ROM from fastboot, or by running the appropriate ruu and starting from scratch. I highly recommend doing the s-off procedure. Its not difficult, and it makes customizing the phone so much simpler.
Sent from my PAC MAN Raider using XDA Premium
i have the same problem man did it just minutes before...i have only a black screen, the display gives a vibration feedback. i see the sdcards in windows but cant open them
What can i do help please!
Edit: Ok screen is on "htc" and keeps so for minutes and hours
Any solution?
N-rG said:
i have the same problem man did it just minutes before...i have only a black screen, the display gives a vibration feedback. i see the sdcards in windows but cant open them
What can i do help please!
Edit: Ok screen is on "htc" and keeps so for minutes and hours
Any solution?
Click to expand...
Click to collapse
Boot to bootloader (pwr and vol-). Does it say locked or unlocked? Does it say s-on or s-off? Select recovery. Does it still boot to custom recovery or do you get the android with the exclamation point? If the bootloader says locked, and you get the android with the !, you need to unlock the bootloader, fastboot flash a custom recovery, boot to that custom recovery, and flash your ROM. If bootloader is s-on, you'll also need to fastboot flash a boot.img that's compatible with the ROM you're flashing (can be found in the ROM's .zip)
homeslice976 said:
Boot to bootloader (pwr and vol-). Does it say locked or unlocked? Does it say s-on or s-off? Select recovery. Does it still boot to custom recovery or do you get the android with the exclamation point? If the bootloader says locked, and you get the android with the !, you need to unlock the bootloader, fastboot flash a custom recovery, boot to that custom recovery, and flash your ROM. If bootloader is s-on, you'll also need to fastboot flash a boot.img that's compatible with the ROM you're flashing (can be found in the ROM's .zip)
Click to expand...
Click to collapse
Thank you so much for your answer
It says "unlocked"
It says "s-on"
It boots to nothing. When i start the phone there is only standing "htc" nothing more happend. No explantion Mark But i can get into the bootloader.
Or what do you mean with "it still boot to custom recovery or do you get the android with the exclamation point?"
How do I do that with the boot.img? Please i am such a noob im so sorry i dont unterstand a lot im so angry about myself that i did it, please can you exactly tell me what i should do and what i need?
I did a backup before but there is no "boot.img"
And how can i use the boot.img wenn i cant get access to the sd memory?
N-rG said:
Thank you so much for your answer
It says "unlocked"
It says "s-on"
It boots to nothing. When i start the phone there is only standing "htc" nothing more happend. No explantion Mark But i can get into the bootloader.
Or what do you mean with "it still boot to custom recovery or do you get the android with the exclamation point?"
How do I do that with the boot.img? Please i am such a noob im so sorry i dont unterstand a lot im so angry about myself that i did it, please can you exactly tell me what i should do and what i need?
I did a backup before but there is no "boot.img"
And how can i use the boot.img wenn i cant get access to the sd memory?
Click to expand...
Click to collapse
When you boot to bootloader, scroll down and select recovery. What happens?
As far as flashing the boot.img, when you downloaded the ROM's .zip, inside the .zip should have been a file called boot.img. You need to drag that to the directory where you have fastboot installed, boot to bootloader, connect your phone, select fastboot. It should now say "fastboot usb". Now in the directory where you have fastboot and boot.img (with neither selected), shift+right click, choose "Open command window here". You need to enter "fastboot flash boot boot.img" and hit enter. Then reboot
At first, thaaank you so much for your help, i feel so lost....
Ah ok i understand, you mean the "[ROM][ICEss v 0.4][Stockish ICS/SENSE 3.6" -that is what i downloaded.
When i am in the bootloader menu and activate recovery the htc symbol appears with a white backround...nothing more happen for minutes
unfortuneately there is not boot.img in this zip
I did the whole procedure with the Vivid_All-In-One_Kit_v2.2 and not fastboot.
Ok i now downloaded fastboot and put it to c:/fastboot
I do what you say and reach your point " It should now say "fastboot usb" thats right, it works. But i dont have the boot.img where can i get it?
N-rG said:
At first, thaaank you so much for your help, i feel so lost....
Ah ok i understand, you mean the "[ROM][ICEss v 0.4][Stockish ICS/SENSE 3.6" -that is what i downloaded.
When i am in the bootloader menu and activate recovery the htc symbol appears with a white backround...nothing more happen for minutes
unfortuneately there is not boot.img in this zip
I did the whole procedure with the Vivid_All-In-One_Kit_v2.2 and not fastboot.
Ok i now downloaded fastboot and put it to c:/fastboot
I do what you say and reach your point " It should now say "fastboot usb" thats right, it works. But i dont have the boot.img where can i get it?
Click to expand...
Click to collapse
There's not a boot.img in the zip you downloaded? Then you need to read the thread and see what kernel they recommend, get the boot.img, and fastboot flash it. You're getting close.
It sounds like you may have lost your custom recovery along the way too (in which case more may have broke) - you'll need to get a custom recovery .img (wcx or twrp) and fastboot flash it (fastboot flash recovery <nameofrecovery>.img). Then fastboot flash boot.img, then boot to recovery and reflash the ROM and hopefully you'll be all set.
Thanks again, im getting closer! I read the whole thread and found that "Holics_Kernel_0730_S-ON" is recommended. I downloaded and found the boot.img I put it in the fastboot folder.
But i dont understand what do you mean with "you'll need to get a custom recovery .img (wcx or twrp)"
Do you mean the recovery i created with my old working Gingerbread or a recovery form the custom rum i downloaded?
When last, where can i get such a recovery.img?
Hey man btw. you gave me so much hope at the moment, thats incredible, thank you!
Check the dev section. Everything you will need is in the stickied threads. Twrp recovery also has its own thread
bypruv oculus
Okay i'll do meanwhile there is something new. I create use fastboot, the boot.img of the new kernel and do it with the command line like you said.
The phone now boots one step more to "htc quietly brilliant" and then restarts over and over again to this screen, like a loop.
---------- Post added at 11:42 PM ---------- Previous post was at 11:25 PM ----------
ahhh i reach Android System Recovry with several menus. I didnt find any help in google what i have to do now.
Backup google propritary System, nand backup, Nand Restore, Restore google proprietary System? Or something else?
No.. at this point you should wipe cache, dalvik cache, system, an data. This can all be done In Recovery's wipe menu. Them recovery should have a flash zip menu. Flash the ROM .zip
Put the brakes on!
I saw gingerbread...
When you boot to bootloader...
There is a line labeled hboot
What's the number next to it?
If its 1.85... you good...
If its 1.83... thou shalt find an ICS ruu for your carrier.
Almost none of the ROMs you find here run on 1.83
Sent from my Vivid 4G using Tapatalk 2
Good catch!
Hey,
i bring it to run! I restored every part manuall...system, cache, data. Only restore boot didnt work. I suggest its because Rom Manager/ClockworkMod didn't created such a file (boot.img) So i downloaded a custom kernel für Gingerbread.
Vola, handy startet, Os is on. Loggin into network worked!
BUT! I cannot use Wlan/wifi or mobile networking. I suppose its because the rom right?
I mentioned that i have the same phone here from my girlfriend.
How and can i make a boot.img of her phone? Please tell my how and then i have finished everything i hope
You can't. S*on devices can't flash boot.IMG or back up boot.IMG in recovery. You have to fast boot flash the boot.IMG. this is also why wifis broken
The kernel and ramdisk and some other things are packed into boot.IMG, and are made by ROM or kernel devs. Actually now that you're booting, you can use an app called flash image GUI to flash the boot.img
Ok I expressed something wrong, sorry (im not a native speaker u might noticed long before ^^ ). So i try again like I said i did the manuell recovery of everything except the boot.img.
Thats why i loaded this kernel for Gingerbread (http://forum.xda-developers.com/showthread.php?t=1351717) and installed the boot.img with fastboot "flash boot boot.img"
Fastboot said well done. Phone startet.
I think i understand what you are writing, but i dont understand which boot.img do you mean i need. I have no boot.img from my backup before flashing with custom rom without this boot.img i cant flash the not working one of the ICS on my phone am i right?
So thats why i thought i can take the phone of my girlfriend, create a boot.img and use it for my phone. So thats the only problem, i need working boot.img and then flash with fastboot oder the app you mentioned How to get the boot.img
Any help please Im stuck in a boot loop and recovery and fastboot are inaccessible, so i cant send any commands? im forking on Mac OS but even ive installed a virtual PC to try some of the countless programs but no seams to work since the phone is not recognized.
designlab said:
Any help please Im stuck in a boot loop and recovery and fastboot are inaccessible, so i cant send any commands? im forking on Mac OS but even ive installed a virtual PC to try some of the countless programs but no seams to work since the phone is not recognized.
Click to expand...
Click to collapse
Anyway, through recovery, you can do nothing, it's useless.
About fastboot mode, you should need to have the bootloader unlocked, if this is the case, then just be sure, that the fastboot drivers are properly installed and updated onto your Mac.
How did you get this?
SubwayChamp said:
Anyway, through recovery, you can do nothing, it's useless.
About fastboot mode, you should need to have the bootloader unlocked, if this is the case, then just be sure, that the fastboot drivers are properly installed and updated onto your Mac.
How did you get this?
Click to expand...
Click to collapse
Bootloader unlocked, flashed MIUI 13 without root it was working fine, unfortunately ive run this commands to obtain root, see if give me a clue...
fastboot flash vbmeta vbmeta.img
fastboot format userdata
fastboot flash boot recovery.img
fastboot boot recovery.img
After these commands im in a bootloop without access to recovery or bootloader.
any help will be appreciated
designlab said:
Bootloader unlocked, flashed MIUI 13 without root it was working fine, unfortunately ive run this commands to obtain root, see if give me a clue...
fastboot flash vbmeta vbmeta.img
fastboot format userdata
fastboot flash boot recovery.img
fastboot boot recovery.img
After these commands im in a bootloop without access to recovery or bootloader.
any help will be appreciated
Click to expand...
Click to collapse
you ****ed your devicewith those commands, now wait until dischaged and try to enter fastboot mode to flash stock miui, btw for magisk just flash twrp then magisk and done, where tf you get that "guide" to root" ?
designlab said:
Bootloader unlocked, flashed MIUI 13 without root it was working fine, unfortunately ive run this commands to obtain root, see if give me a clue...
fastboot flash vbmeta vbmeta.img
fastboot format userdata
fastboot flash boot recovery.img
fastboot boot recovery.img
After these commands im in a bootloop without access to recovery or bootloader.
any help will be appreciated
Click to expand...
Click to collapse
You just needed to boot to the custom recovery of your choice, then, when booting to it, flash it, and from there, if you want, or if it is required by the custom ROM of your choice, then format data, but it is not required for rooting purposes.
Anyway, check if you have access either, to download or fastboot mode and flash the stock ROM.
tutibreaker said:
you ****ed your devicewith those commands, now wait until dischaged and try to enter fastboot mode to flash stock miui, btw for magisk just flash twrp then magisk and done, where tf you get that "guide" to root" ?
Click to expand...
Click to collapse
Thanks i've got them from this F..k guide here i already waited for discharge even opened device and removed battery no luck, the thing is that i've done this twice in order to fix it previous time got help from a guy but can't reach him, i believe they fixed with a PC computer i'm using MAC not sure how to access download mode? can you explain in detail please!
SubwayChamp said:
You just needed to boot to the custom recovery of your choice, then, when booting to it, flash it, and from there, if you want, or if it is required by the custom ROM of your choice, then format data, but it is not required for rooting purposes.
Anyway, check if you have access either, to download or fastboot mode and flash the stock ROM.
Click to expand...
Click to collapse
can you explain in detail please! no accses to fastboot or recovery, im working on MAC no sure how to access download mode?
designlab said:
Thanks i've got them from this F..k guide here i already waited for discharge even opened device and removed battery no luck, the thing is that i've done this twice in order to fix it previous time got help from a guy but can't reach him, i believe they fixed with a PC computer i'm using MAC not sure how to access download mode? can you explain in detail please!
Click to expand...
Click to collapse
in mac? the more releable options and windows and linux to install the firmware and recover the device, i check that page, that one of the hundred fake pages to flash twrp, the real one is this ( the one i use ) twrp miui 13 RN10s btw try to get a windows pc and try this: hard brick guide to enter fastboot mode, unplug the battery then plug in again and press vol - and power until fastboot message apperas
designlab said:
can you explain in detail please! no accses to fastboot or recovery, im working on MAC no sure how to access download mode?
Click to expand...
Click to collapse
To send an MTK device to download mode, is pretty easy, you don't need, specially in newer devices, to open it, even in a bricked state, you can do it.
BUT probably, you need a Windows PC, booting in a virtual machine, not always works as expected, so you should need to do some of these things:
- If you have some space in your HDD/SDD, at least 35 GB available, reserve a partition for Windows, install, preferably Windows 10, your Mac is capable to dualboot with.
- Also you can use these "virtual" versions of Windows, not sure if it works, but worth it to try, burn the ISO/s, on a USB pen drive, or a SD card with its holder.
WPE4Live - Browse /WPE4Live with Chrome Browser+MediaPlayer at SourceForge.net
Customized Windows Live System for daily use
sourceforge.net
Hiren's BootCD PE
After that, follow this guide https://www.hovatek.com/forum/thread-37957.html
Thanks for your response, it seams like a mission but im willing to try, it seams like MTK devices are trouble!