Okay, so after a lot of reading I'm still unable to get TWRP to flash on this device.
Thus far I've got full root with Kingo, Updated SU Binaries, and Busybox installed.
Upon the recovery portion of the process, I adb reboot into bootloader, but my fastboot driver doesn't seem to be quite correct. My computer will see it as an ADB Interface, but if I try
"fastboot flash recovery.img"
it will just hang on "Waiting for Device."
NabiLab doesn't ever see anything with "fastboot devices" either.
Anyone have any suggestions? I'm not an expert by any means, but if someone needs me to dump anything from my model I'd be more than willing. Oh, I also have a copy of the Source for this model as well.
Corbow6 said:
Okay, so after a lot of reading I'm still unable to get TWRP to flash on this device.
Thus far I've got full root with Kingo, Updated SU Binaries, and Busybox installed.
Upon the recovery portion of the process, I adb reboot into bootloader, but my fastboot driver doesn't seem to be quite correct. My computer will see it as an ADB Interface, but if I try
"fastboot flash recovery.img"
it will just hang on "Waiting for Device."
NabiLab doesn't ever see anything with "fastboot devices" either.
Anyone have any suggestions? I'm not an expert by any means, but if someone needs me to dump anything from my model I'd be more than willing. Oh, I also have a copy of the Source for this model as well.
Click to expand...
Click to collapse
You will manually have to force the Windows driver from ADB to fastboot, if you are truly in fastboot, thats why it hangs at waiting for device. What recovery are you flashing? Did someone make a recovery for that version that I missed somewhere?
Ah, I thought that might be the case, but I was a little unsure of how to go about that. I believe it truly is in fastboot, but no I don't believe anyone has specifically written a recovery for this model. Hoping to be able to use some that were compatible with the other Nabi models.
Corbow6 said:
Ah, I thought that might be the case, but I was a little unsure of how to go about that. I believe it truly is in fastboot, but no I don't believe anyone has specifically written a recovery for this model. Hoping to be able to use some that were compatible with the other Nabi models.
Click to expand...
Click to collapse
If you haven't already overwritten the stock recovery. You can get some stuff off the tablet if you have root and we could try and make a TWRP.
adb shell
su
dd if=/dev/block/platform/sdhci-tegra.3/by-name/SOS of=/sdcard/recovery.img
It's also good to do a
cat /proc/partitions
and save partitions info. Upload the recovery.img(it should be on your internal storage and not always visible depending on with what you are viewing the contents) and partition info.
aicjofs said:
If you haven't already overwritten the stock recovery. You can get some stuff off the tablet if you have root and we could try and make a TWRP.
adb shell
su
dd if=/dev/block/platform/sdhci-tegra.3/by-name/SOS of=/sdcard/recovery.img
It's also good to do a
cat /proc/partitions
and save partitions info. Upload the recovery.img(it should be on your internal storage and not always visible depending on with what you are viewing the contents) and partition info.
Click to expand...
Click to collapse
since there are few posts about this model of nabi jr, please checkit out this guide i made to install gapps : http://forum.xda-developers.com/android/development/guide-manually-install-play-store-fuhu-t3435200
help to improve and test would be apreciated.
You will manually have to force the Windows driver from ADB to fastboot,
Click to expand...
Click to collapse
can someone explain exactly how to do that?
slplsnphx said:
can someone explain exactly how to do that?
Click to expand...
Click to collapse
Most of this thread doesn't make sense, since there is no TWRP for this device. It's a Mediatek CPU and a lot of these things we have listed are for Nvidia devices.
Related
Boots into recovery every time. Tried cwm restore to earlier backup with no luck
Sent from my DROIDX using XDA App
reflashed gtabcomb. still boots to recevoery. does this mean nvflash time?
joshtb86 said:
reflashed gtabcomb. still boots to recevoery. does this mean nvflash time?
Click to expand...
Click to collapse
Try wiping the "misc" partition while in CWM: Boot the gTab into recovery mode, connect the USB cable to it and run adb on the PC:
Code:
C:\> [B]adb shell erase_image misc[/B]
(You may have to wipe the "bootbmp" partition, instead, on some gTabs, because those 2 partitions have switched places on them.)
Edit: Or, use the attached zip file to erase "misc". Just "install" the zip file as usual using CWM.
Edit2: As to why this "always boots into recovery" happens, see this post.
rajeevvp said:
Try wiping the "misc" partition while in CWM:
Code:
C:\> [B]adb shell erase_image misc[/B]
(You may have to wipe the "bootbmp" partition, instead, on some gTabs, because those 2 partitions have switched places on them.)
Click to expand...
Click to collapse
already reflashed. but will try that next time! thanks!
rajeevvp said:
Try wiping the "misc" partition while in CWM:
Code:
C:\> [B]adb shell erase_image misc[/B]
(You may have to wipe the "bootbmp" partition, instead, on some gTabs, because those 2 partitions have switched places on them.)
Click to expand...
Click to collapse
rajeevvp your are magical man!
Everytime I get in trouble I search for a solution and find, that you already solved it :-D
Same here.
After moving to BL 1.2 I used "reboot recovery" in advanced menu of CWM and got into boot loop.
I tried nvflashing new boot.img and also recovery.img, but in vain.
Erasing misc partition magically helped ;-)
THANKS!
johny.mnemonic said:
I tried nvflashing new boot.img and also recovery.img, but in vain.
Erasing misc partition magically helped ;-)
Click to expand...
Click to collapse
It isn't magic--just details gleaned from reading the CWM code. If it were magic, it would be mysterious, and therefore, less interesting, wouldn't it?
The misc partition is used for communication between the ROM/kernel, the bootloader, and CWM; and if the tablet is going into recovery mode everytime, then logically, wiping misc should fix things. However, I couldn't test this scenario on my gTab because of my switched misc/bootbmp partitions: if I select "Reboot Recovery", CWM would just erase my (first) boot splash screen instead of going into a boot loop.
The various other versions of CWM have these minor sorts of bugs and irritations. The recently posted CWM-4.0.1.5 is the least annoying and it is what I will be using from now on. It a) understands my switched misc/bootbmp partition, b) "Reboots Recovery" w/o boot loops, and c) does USB mounts correctly.
Thanks for telling me that the technique worked. I've suggested it on other threads, but, this is the first time a user has told me that it fixed their problem. Most often users will just use nvflash--unnecessarily, and superstitiously--instead of waiting for the correct solution.
Im having the same problem, stuck in Clockwork. I dont see any option to 'wipe Misc partition. I also can't find a command line where I could enter the command 'C:\> adb shell erase_image misc'.
How do I wipe out that partition from Clockwork?
adb quick install
rajeevvp said:
Try wiping the "misc" partition while in CWM: Boot the gTab into recovery mode, connect the USB cable to it and run adb on the PC:
Code:
C:\> [B]adb shell erase_image misc[/B]
(You may have to wipe the "bootbmp" partition, instead, on some gTabs, because those 2 partitions have switched places on them.)
Click to expand...
Click to collapse
This is FANTASTIC! It absolutely fixes the CWM loop - and it is simple! (Once you have ADB working on your computer.)
I thought that I had read somewhere (but I cannot find it now) that you only needed ADB and FASTBOOT to run simple ADB commands. Is there a SIMPLE install for ADB? For Windows & for Linux. That would be even more fantastic!
I would like to provide that to my readers who accidentally do the "reboot to recovery" when them really mean "reboot system now." That simple error is what causes the CWM loop.
raywaldo said:
I thought that I had read somewhere (but I cannot find it now) that you only needed ADB and FASTBOOT to run simple ADB commands.
Click to expand...
Click to collapse
FASTBOOT does not apply to the gTab which uses a different, and proprietary, bootloader. To run ADB commands you just need the adb binary and its (standard) libraries.
Is there a SIMPLE install for ADB? For Windows & for Linux. That would be even more fantastic!
Click to expand...
Click to collapse
As I mentioned above, on Linux, you just need the adb binary. You don't have to install the entire Android SDK. I don't use Windows, so I don't know much about ADB there, but, I suspect that even there you would only need the exe file, its libraries and the Google/VS(?) USB driver.
EDIT: adb installed, but not configured with the USB driver before stuck in my CWM bootloop and adb never recognizes the tablet, whether its in cwm, mounted or in apx mode. does anyone have any suggestions?
any suggestions?
i think i need to nvflash. unabvle to get drivers installed since my device wont boot, so cant configure adb to work correctly
Im running into this as well. I got the Android SDK installed but ADB says that no devices are attached. Windows recognizes the Tegra 2 device when its mounted fine. It appears to be using the microsoft driver though. I attempted to change to the "android_winusb.inf" driver, but it wouldnt let me install/change it. I am running Windows 7 64bit if that matters in regards to the driver.
Try nvflash if you're having problems with adb.
Thanks. nvflash says no usb device found though. I tried it with and without 'mount usb storage'.
Coldfirex said:
Thanks. nvflash says no usb device found though. I tried it with and without 'mount usb storage'.
Click to expand...
Click to collapse
Try the CWM-flashable zip file in post #3 of this thread.
That worked great, thanks!!!
This fix worked great! Much better than nvflashing and reinstalling everything.
Thanks.
Thanks!!!, fix thanks to this magical command.
rajeevvp said:
Try the CWM-flashable zip file in post #3 of this thread.
Click to expand...
Click to collapse
I could really use a little more direction on this... I've finally gained access to mt tablet bymounting the USB storage command in CWM. I have this zip file on my desktop, not sure what to do from there...
Pleaase help!
I kinda messed up about a month ago, I was wanting to root my HTC One so I could try some custom ROMS and experience other cool stuff
However, Me, feeling nervous decided to go the Cyanogenmod Installer route (You know this isn't gonna end well). And so I plugged in my device and everything was good and fine until It was unlocking my bootloader, it seemed to do the HTCDev one, I got the option to unlock it or lock it, and as soon as the device restarted the phone disconnected.
Some apps went missing, however I recently had a talk to a friend who said that is normal, and he recommended me to come here to get some help.
I can boot into the bootloader where you can go into fastboot and stuff, I can factory reset through the Android OS once its booted, however when I enter recovery in the bootloader, the screen goes black and a red exclamation mark shows up for about 5-10 minutes and then the device reboots into Android.
The same thing happens when I try to get Over the air updates, I can still get OTA updates, they just don't install.
So what I'm looking for is, can I relock my device and get it back to how it was before I ran Cyanogenmod installer and then maybe I can try root it manually and have more control over the situation.
I hope you guys can help me and I hope I can find a place on this forum
Thanks in advance guys!
First of all, it seems you shouldn't have started to mess with this at all...
now to fix this...
Download the latest recovery of your choice e.a. twrp. @ http://techerrata.com/browse/twrp2/m7 the normal one is the m7 i suppose? else go to the right section...
save it to your /sdcard directly or move it there. than for the eaz just rename it to twrp.img
open an terminal if installed on your device and type
su
than
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p34 (note command for the m7)
if you however don't have the capability to install an app because of missing gapps... which sounds like it...
install adb/fastboot on your pc with the htc drivers..
download the recovery image with your pc and rename it to twrp.img and put it at your fastboot file
turn off your device
keep holding volume down until a menu shows up
select fastboot from the menu
attach the device to your pc
open cmd and type fastboot devices (to see if you actually installed the right driver... and that it's recognizing it)
if it does
type:
fastboot flash recovery twrp.img
if that all succeeded, you can download gapps for the android version your using or flash something else with the working recovery..
goodluck!
Hawkysoft said:
First of all, it seems you shouldn't have started to mess with this at all...
now to fix this...
Download the latest recovery of your choice e.a. twrp. @ (It prevented me posting links) the normal one is the m7 i suppose? else go to the right section...
save it to your /sdcard directly or move it there. than for the eaz just rename it to twrp.img
open an terminal if installed on your device and type
su
than
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p34 (note command for the m7)
if you however don't have the capability to install an app because of missing gapps... which sounds like it...
install adb/fastboot on your pc with the htc drivers..
download the recovery image with your pc and rename it to twrp.img and put it at your fastboot file
turn off your device
keep holding volume down until a menu shows up
select fastboot from the menu
attach the device to your pc
open cmd and type fastboot devices (to see if you actually installed the right driver... and that it's recognizing it)
if it does
type:
fastboot flash recovery twrp.img
if that all succeeded, you can download gapps for the android version your using or flash something else with the working recovery..
goodluck!
Click to expand...
Click to collapse
Thank you! Will there be a risk in ruining my device?
And thank you once again! I definitley shouldn't have messed with this, but you gotta start somewhere right?
If I never took the risk of building my own computer then I never could have done it Its how we learn.
Anyways, I'm not sure about the terminal bit, I don't run linux and I don't have a mac? So, how would I have access to the terminal. Unless I somehow got it on my device (I don't know how to do that).
And one more question, once I've done the things you've told me to do I can just put Cyanogenmod on it?
Thanks once again
Oh, and I have got Gapps, if my Gapps you mean Google Apps, yes I have I've got Google play services, Google play, hangouts etc.
Thank you! Will there be a risk in ruining my device?
Click to expand...
Click to collapse
Further than now? i highly doubt it... unless you totally put in a wrong recovery which magically wud fk up the partitions?
And thank you once again! I definitley shouldn't have messed with this, but you gotta start somewhere right?
Click to expand...
Click to collapse
True, but babysteps mate...
Anyways, I'm not sure about the terminal bit, I don't run linux and I don't have a mac? So, how would I have access to the terminal. Unless I somehow got it on my device (I don't know how to do that).
Click to expand...
Click to collapse
Terminal should be on the phone, if not use command prompt in windows... u need to do a little research on the m7 forums which driver you need they probably have an m7 toolkit again if the one is the m7, as far as i knew it is.. than you could put the recovery.img in the folder of fastboot.exe and go there with command prompt and do what i've written before
And one more question, once I've done the things you've told me to do I can just put Cyanogenmod on it?
Click to expand...
Click to collapse
erhm ofcourse you can, however just download the rom instead of an installer...
p.s. you got gapps.. install an emulator oh... better solution... install flashify download the latest twrp and install it with that if u have proper root that is!
Hawkysoft said:
Further than now? i highly doubt it... unless you totally put in a wrong recovery which magically wud fk up the partitions?
True, but babysteps mate...
Terminal should be on the phone, if not use command prompt in windows... u need to do a little research on the m7 forums which driver you need they probably have an m7 toolkit again if the one is the m7, as far as i knew it is.. than you could put the recovery.img in the folder of fastboot.exe and go there with command prompt and do what i've written before
erhm ofcourse you can, however just download the rom instead of an installer...
p.s. you got gapps.. install an emulator oh... better solution... install flashify download the latest twrp and install it with that if u have proper root that is!
Click to expand...
Click to collapse
Thanks I don't have root, I've run rootchecker, and it says I don't have root.
And what if I do Cyanogenmod but I want to go back to HTC Sense (Doubt it though)
Will instlaling the recovery root my device? If not, how will I root it?
Oh and, how do I get fastboot and ADB?
I'm using an Empire ElectroniX D709 tablet, running Android 4.0.4. It's an old low-spec device, and I'm planning to use this device to improve my Android hacking skills.
I've asked the manufacturers to send me the stock ROM, which they did. Pretty cool!
The problem is that there's no flashing tool or instructions included, and the staff I spoke with did not know how to flash it either.
So now I'm on my own, with a big image file I don't know how to flash.
I tried to start a development thread at the Miscelleaneous Android Development section, but because I have almost no posts, I can't post there. So maybe this is a good place to ask. How can I flash or unpack this image?
You can find the ROM here: http://www.needrom.com/download/empire-electronics-d709/
Exeleration-G said:
I'm using an Empire ElectroniX D709 tablet, running Android 4.0.4. It's an old low-spec device, and I'm planning to use this device to improve my Android hacking skills.
I've asked the manufacturers to send me the stock ROM, which they did. Pretty cool!
The problem is that there's no flashing tool or instructions included, and the staff I spoke with did not know how to flash it either.
So now I'm on my own, with a big image file I don't know how to flash.
I tried to start a development thread at the Miscelleaneous Android Development section, but because I have almost no posts, I can't post there. So maybe this is a good place to ask. How can I flash or unpack this image?
You can find the ROM here: http://www.needrom.com/download/empire-electronics-d709/
Click to expand...
Click to collapse
You have to manually flash them using fastboot. Look up how to get fastboot and move the image(s) to the folder were fastboot.exe is located. Boot into your bootloader either via adb reboot bootloader or by physically doing it from the device. Now here is where most people fail. At the end of the file name, before the .img, it should be either boot, fastboot, recovery or system. If it is system, then do fastboot flash system nameofthesystemimg.img and if it is boot, you get the idea.
Thank you. Fastboot is a good idea. Problem is that I don't know which partition this .img file belongs to. I have the feeling that this file contains every partition, yet I'm not sure how to split it up so that I can flash each partition.
Exeleration-G said:
Thank you. Fastboot is a good idea. Problem is that I don't know which partition this .img file belongs to. I have the feeling that this file contains every partition, yet I'm not sure how to split it up so that I can flash each partition.
Click to expand...
Click to collapse
Will you mind sharing the whole file name? If it is an all partition img you can do fastboot flash all (I think). Just type fastboot and see the all option in the help menu.
Sent using a ks01lte (gt-i9506) running cm 13
RAZERZDAHACKER said:
Will you mind sharing the whole file name? If it is an all partition img you can do fastboot flash all (I think). Just type fastboot and see the all option in the help menu.
Sent using a ks01lte (gt-i9506) running cm 13
Click to expand...
Click to collapse
The full file name is D709_n.img. Theres an option fastboot flashall indeed.
Right now, I'm trying to get the device into fastboot, without success. Things I've tried until now:
Code:
adb reboot-bootloader
adb reboot bootloader
adb reboot fastboot
Every time, the device restarts and just enters the normal mode. I can get into stock recovery, but there's no option to restart to bootloader there.
Exeleration-G said:
The full file name is D709_n.img. Theres an option fastboot flashall indeed.
Right now, I'm trying to get the device into fastboot, without success. Things I've tried until now:
Code:
adb reboot-bootloader
adb reboot bootloader
adb reboot fastboot
Every time, the device restarts and just enters the normal mode. I can get into stock recovery, but there's no option to restart to bootloader there.
Click to expand...
Click to collapse
Hmmm, if you type adb devices, do you see your device there? If not, search online for drivers. If that does not work, google your device and how to get it to fastboot.
RAZERZDAHACKER said:
Hmmm, if you type adb devices, do you see your device there? If not, search online for drivers. If that does not work, google your device and how to get it to fastboot.
Click to expand...
Click to collapse
Yes, it's fully recognized, and I can adb in it just fine. I also get an adb prompt in recovery mode that lets me control the device. The only problem right now is getting this thing to fastboot.
Update
After googling its model number (crane-evb), I found out that this device can be flashed using LiveSuite (described here). It's nice to see the device back in its factory condition. Now I need to find a way to extract the partitions.
[QRCODE][/QRCODE]
Exeleration-G said:
Update
After googling its model number (crane-evb), I found out that this device can be flashed using LiveSuite (described here). It's nice to see the device back in its factory condition. Now I need to find a way to extract the partitions.
Click to expand...
Click to collapse
YaY! I was going to say that in stock recovery there is this option called update via adb or something but now that it is working, there is no need for that.
Hi,
this is a small tutorial to show you how to flash the recovery, also eRecovery, via command line / adb shell within Android.
Flashify and other apps never worked for me, so I used commands to flash it without the need of fastboot.
It's a small tutorial for those who never worked with commands like this.
Please notify me if something went wrong or if you found any other issues.
I wanted to make a small script but I stopped it because of the lack of available commands in Android.
DISCLAIMER:
Read this tutorial first.
Never flash custom recovery to eRecovery.
Never flash recoveries from different devices.
Don't try to flash other partitions with this commands if you don't want to risk a brick.
Requirements:
- Oreo / EMUI 8 installed, Nougat hast other partition names. Pie isn't supported by me until final release.
- working root access
- terminal emulator app (I recommend Termius, it's easy to use and has nice features, it's free to use)
> or a PC, and USB cable and working ADB, also USB Debugging enabled in developer settings
- recovery img files on your phone, I recommend it to put them into your user root /data/media/0/ (internal memory)
NOTE: All commands are case sensitive!
Now open your terminal app or open the adb shell.
Type following command to enable root access:
Code:
su
SuperSU will ask you for root access, grant it.
Following command is needed to figure out, which type of memory your phone has:
Code:
ls /dev/block/platform
There are two possible outputs:
If you've a device with the faster UFS memory, it's ff3b0000.ufs, if eMMC it's hi_mci.0.
From now I'll write MEMORY instead of ff3b0000.ufs or hi_mci.0.
For flashing the recovery fire up following command:
Code:
dd if=/PATH/TO/YOUR/RECOVERY.IMG of=/dev/block/platform/MEMORY/by-name/recovery_ramdisk_a
Example: dd if=/data/media/0/twrp_3.2.1.img of=/dev/block/platform/ff3b0000.ufs/by-name/recovery_ramdisk_a
The output should look like this:
Code:
65536+0 records in
65536+0 records out
33554432 bytes transferred in 0.247 secs (135847902 bytes/sec)
If not, check your command and file paths.
For flashin the eRecovery fire up following command:
Code:
dd if=/PATH/TO/YOUR/ERECOVERY.IMG of=/dev/block/platform/MEMORY/by-name/erecovery_ramdisk_a
Example: dd if=/data/media/0/ERECOVERY_RAMDI.IMG of=/dev/block/platform/ff3b0000.ufs/by-name/erecovery_ramdisk_a
IMPORTANT NOTE: DO NOT INSTALL TWRP IN THIS! Flash only stock eRecovery!
The dd command won't give you any progress output, so be a bit patient. It should be done in a few second, but don't close the terminal app or connection before you got any output.
Unix systems like Android will give an output if something went wrong, always.
I use this to flash new TWRP versions or to flash stock recovery before I update.
If you recently updated your phone, you still need to flash via fastboot, because you lost root during the update.
The dd commands also work with fastboot. Mostly you'll use "fastboot flash recovery_ramdisk", but if you need to flash eRecovery, you can use the dd command.
23. February 2019:
Pie should also work, but you have to remove the "_a" after the partition name.
Example:
dd if=/data/media/0/twrp_3.2.1.img of=/dev/block/platform/ff3b0000.ufs/by-name/recovery_ramdisk
Please report if it's working or not.
How to know the path to the recovery_ramdisk?? Is all devices the same?? I didn't get it right the 1st time .. it shows path is invalid
Sent from my VTR-L29 using Tapatalk
fr3ker said:
How to know the path to the recovery_ramdisk?? Is all devices the same?? I didn't get it right the 1st time .. it shows path is invalid
Sent from my VTR-L29 using Tapatalk
Click to expand...
Click to collapse
Should be the same on every device. Remember, case sensitive and use _ and not -.
Maybe it's different on non UFS devices, which one do you have?
Are you able to post a screenshot of your command and output?
Jannomag said:
Should be the same on every device. Remember, case sensitive and use _ and not -.
Maybe it's different on non UFS devices, which one do you have?
Are you able to post a screenshot of your command and output?
Click to expand...
Click to collapse
Maybe @fr3ker is not on Oreo? The recovery_ramdisk partition is only for Oreo. In Nougat it is just called recovery. I don't know how the Pie partitions are called.
M1chiel said:
Maybe @fr3ker is not on Oreo? The recovery_ramdisk partition is only for Oreo. In Nougat it is just called recovery. I don't know how the Pie partitions are called.
Click to expand...
Click to collapse
Also my thought, I wanted to add this to the requirements when I created this post but apparently I forgot this. Now it's added as first point.
Hi.
I have a hard bricked p10. When I connect to laptop it's says USB SER. It doesn't not turn on I can't access recovery with power + vol. I can't get into fastboot. Anyway I can access fastboot to flash kernel and erecovery?
Jannomag said:
I use this to flash new TWRP versions or to flash stock recovery before I update.
Click to expand...
Click to collapse
Is it mandatory to flash stock recovery before update? Is it applies only to ota update or ff method?
Yes, FF or OTA are using stock recovery to flash the update. With TWRP it won't work.
Updated?
@ Jannomag:
Have you checked this for Pie meanwhile?
I currently have the problem, not being able to enter fastboot with:
Code:
sudo adb reboot bootloader
Additionally, there's something I do not understand. For the dd-command for flashing, why is the input-file (if=) the file in "/dev/block/platform/..." and the output on the sd-card? Wouldn't mean flashing an img to the device, that if= on the sd (or connected PC) and of= the path to the device (phone)?
Blümchen Blau said:
@ Jannomag:
Have you checked this for Pie meanwhile?
I currently have the problem, not being able to enter fastboot with:
Code:
sudo adb reboot bootloader
Additionally, there's something I do not understand. For the dd-command for flashing, why is the input-file (if=) the file in "/dev/block/platform/..." and the output on the sd-card? Wouldn't mean flashing an img to the device, that if= on the sd (or connected PC) and of= the path to the device (phone)?
Click to expand...
Click to collapse
WTF....Why didn't I notice this terrible mistake! Thank you for reading my post completely, you're 100% correct, I'll correct this directly after I submit this post.
Huawei did also a small change at naming the recovery partition, which I'll update, too.
I had also the problem that I wasn't able to boot into fastboot by command before I fried my phone - I couldn't figure out the reason for this.
Again, thank you!
Jannomag said:
Again, thank you!
Click to expand...
Click to collapse
Your'e welcome! I did update now, but didn't need your (correct ) way to fastboot, because the method described by borgerapper did the trick for me to get into fastboot and flash the needed original recovery.
Thanks anyway!
hi all,
i have a rooted vivo air lte with supersu.
i wanted to install magisk with the manager 8.0.3 (the boot.img from stock rom i extracted to downloads folder) by choosing direct install.
now the phone hangs on the bootlogo.
i can boot into recovery and choose "apply update from adb"
i installed fastboot and adb on the pc.
in the terminal command "adb devices" i see "devicenr sideload".
when i enter fastboot devices, there is no device shown.
im not sure if i have unlocked the bootloader when i rooted the phone a year ago..
so what do i have to do now to get it booting again?
thanks for the help!
schlunk said:
in the terminal command "adb devices" i see "devicenr sideload".
Click to expand...
Click to collapse
Device is configured to get booted in "Sideload" mode what is a variant of ADB mode.
Try this
Code:
adb devices
adb reboot
to return to "Normal" mode.
no, this is what i have chosen in the recovery, otherwise i dont get any device listed in the terminal..
@schlunk
Once being in the Android Recovery Mode and you select option Reboot system the Android device simply gets restarted: the actually configured ADB mode herewith doesn't get changed / reset.
when i enter "adb reboot" in the terminal its "error closed"..
is ther e something i can sideload then to solve this, when the phone is waiting for the package to sideload?
thanks for helping!
schlunk said:
when i enter "adb reboot" in the terminal its "error closed"..
is ther e something i can sideload then to solve this, when the phone is waiting for the package to sideload?
thanks for helping!
Click to expand...
Click to collapse
QFIL is the answer.
this is a flasher like odin?
so can i just flash the boot.img, that magisk wrote back to the stock one?
and like i said im not sure if the bootloader is unlocked, does it play a role in this?
schlunk said:
this is a flasher like odin?
so can i just flash the boot.img, that magisk wrote back to the stock one?
and like i said im not sure if the bootloader is unlocked, does it play a role in this?
Click to expand...
Click to collapse
https://firmwarefile.com/blu-vivo-air-lte-v0010uu
https://www.youtube.com/watch?v=MdknZvaTwl4
thats exactly the file i downloaded to extract the boot.img and see what happend
i dont want to flash the complete stock firmware again with the risk that my phone is bricked after that.
there must be some easier solution for this??
cant i just flash what magisk messed up?
schlunk said:
there must be some easier solution for this??
cant i just flash what magisk messed up?
Click to expand...
Click to collapse
Nope, I don't think there is.
Depends if that boot is same that was in your device. See the video
and the thread too: https://forum.hovatek.com/thread-31476.html
The boot should be the same, the firmware is exactly the same like in the phone regarding the label.
So with this linked method, flashing a single partition means, the boot.img can be flashed solo, without the need of flashing the whole firmware?
And when that doesnt work, i still could flash the whole firmware then as last resort?
That what I would do... Good luck!