Related
My tab started giving al kind of errors on internal apps and stuff so i shut it down and now it is in reboot loop.
I can get it into odin download mode or fastboot mode. But i cannot see it with adb or fastboot (it doesent show up when using adb devices or fastboot devices.
i can use odin to do a pda flash but outcome is stil the same.
also did nvflash from Retail 3.1 CWM Recovery, Root & full back up!
al goes fine but after that still no adb reboot recovery or adb devices
iam desperate please help me with this
renedg said:
My tab started giving al kind of errors on internal apps and stuff so i shut it down and now it is in reboot loop.
I can get it into odin download mode or fastboot mode. But i cannot see it with adb or fastboot (it doesent show up when using adb devices or fastboot devices.
i can use odin to do a pda flash but outcome is stil the same.
also did nvflash from Retail 3.1 CWM Recovery, Root & full back up!
al goes fine but after that still no adb reboot recovery or adb devices
iam desperate please help me with this
Click to expand...
Click to collapse
Here's what you do.
Download the file linked below
Download ODIN attached below
Once both are downloaded, extract PDA_SIGNED_P7105.tar
Boot your tablet into ODIN and plug it into your PC
Open the ODIN program on your PC and check the box next to PDA
Click the PDA button and navigate to the file you downloaded earlier
Press Start and let it flash
Once it is done, it will still boot loop.
You need to go into recovery (It will now be the default recovery) and wipe data/factory reset only.
Reboot and it should load up, however you will be on 3.0.1.
You can get back to 3.1 by rooting and installing recovery again or by using the update feature in the tablet's settings.
Good luck!
http://www.mediafire.com/?gcenefqc3khcc0c
renedg said:
My tab started giving al kind of errors on internal apps and stuff so i shut it down and now it is in reboot loop.
I can get it into odin download mode or fastboot mode. But i cannot see it with adb or fastboot (it doesent show up when using adb devices or fastboot devices.
i can use odin to do a pda flash but outcome is stil the same.
also did nvflash from Retail 3.1 CWM Recovery, Root & full back up!
al goes fine but after that still no adb reboot recovery or adb devices
iam desperate please help me with this
Click to expand...
Click to collapse
Please DO NOT ask Questions in the Development forum
Moving to General
When i have done this and go into recovery (power and left volume) i stil get usb icon and download (odin) and still no device found with adb or fastboot (driver i sbeing loaded so somehow my system does regonize it as fastboot or recovery device but with fastboot devices or adb devices still no device in list.
It is alive again. Thanks all who helped out
renedg said:
when i have done this and go into recovery (power and left volume) i stil get usb icon and download (odin) and still no device found with adb or fastboot (driver i sbeing loaded so somehow my system does regonize it as fastboot or recovery device but with fastboot devices or adb devices still no device in list.
Click to expand...
Click to collapse
it is alive again. Thanks all who helped out
You are the man! My IO Galaxy Tab 10.1 is alive again!
Thanks!
Hi All,
I am done the ODIN step, but it still in bootloop mode. I dont know how to do with the Fastboot recover mode. I tried with my Windows 7 and it can't recognized my fastboot driver and stay in the <waiting for device>. Is there any solution for me. Thank you so much.
ericc191 said:
Here's what you do.
Download the file linked below
Download ODIN attached below
Once both are downloaded, extract PDA_SIGNED_P7105.tar
Boot your tablet into ODIN and plug it into your PC
Open the ODIN program on your PC and check the box next to PDA
Click the PDA button and navigate to the file you downloaded earlier
Press Start and let it flash
Once it is done, it will still boot loop.
You need to go into recovery (It will now be the default recovery) and wipe data/factory reset only.
Reboot and it should load up, however you will be on 3.0.1.
You can get back to 3.1 by rooting and installing recovery again or by using the update feature in the tablet's settings.
Good luck!
Click to expand...
Click to collapse
Hello, I have also followed these directions however I am having issues rebooting into recovery using adb.
When I execute adb devices no devices are found.
Any additional help would be appreciated. Thanks
UPDATE:
Success!! I was able to correct the boot loop problem by installing fastboot on a linux machine and running sudo fastboot -w. Also my tablet was in fastboot mode (Power + Volume down, then Select the usb symbol).
Instructions for installing fastboot were found here http://forum.xda-developers.com/showpost.php?p=14675422&postcount=2
boot looping SOLVED! Honeycomb 3.1 google i/o galaxy tab 10.1
[IO TAB] Boot looping? Try this to get your tab back...
I had an issue with my IO 10.1 Tab boot looping. I imagine that this would work for retail as well but have not tried it.
This process will factory reset your device.
You will need fastboot and recovery.img to boot into recovery in order to perform a factory reset.
Fastboot & Stock IO recovery comes from this post as an attachment at the bottom.
You need adb to continue (windows).
1. Extract files to where adb resides (platform-tools folder in android SDk main folder) e.g
C:\Program Files\Android\android-sdk\platform-tools .
2. Plug your tab in to a power source and then hold down the power button until it shuts down. Wait until the tab displays the charging battery.
3. Press and hold the volume down (left button in landscape) and power buttons until the usb and odin icons show up. Volume down to move left and volume up to select the usb logo. Now you should be in fastboot. Plug the usb into your computer.
4. Time to fire up adb!
Start / run / cmd , cd\,
Than, cd to your platform-tools folder or wherever your adb is at. (should be in platform-tools inside of android-sdk-windows)
5. In cmd type "adb start-server" without quotes to start adb. All comands should exclude quotes.
6. Type "fastboot devices" your device serial should appear!If not:
Edit the “<PATH TO ANDROID SDK>\extras\google\usb_driver\android_winusb.inf” file and copy/paste the following lines and add them to the [Google.NTx86] section (for 32bit Windows) and/or [Google.NTamd64] (for 64bit Windows).
NO Empty line above this set, though galaxy tab 10.1v but works for all variants!(tab detected as adb xxx device)
;Galaxy Tab 10.1v
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&REV_9999&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6601
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
;
Download the fastboot zip attached to this post (includes both Win and Linux version) and extract the files to your “<PATH TO ANDROID SDK>\platform-tools” folder
7. Now, type "fastboot boot recovery.img"
8. Now you should boot into recovery. For "adb command lines" to work boot with clockworkmod recovery img (Command and files here: http://droidbasement.com/db-blog/?p=2032)
If you want to try other stuff like push a system restore, kernel or whatever, now you can. If you fail at it, you can always repeat the steps leading up to this point to get back to recovery.
9. Time to just get the tab back! Select "wipe data/factory reset" and confirm, clear cache.
10. After that is done select "reboot device".
Credits to JASKRU from rootwiki, with some additions and modifications extracted from different sources!
for rooting the tab install the zip file from this post in recovery mode (loading recovery.img from fastboot):
http://droidbasement.com/db-blog/?p=2054
P.S don't reboot into recovery with adb command "adb reboot recovery" as it doesn't work, correct way is with fastboot command as mentioned in step 7!
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
FIRST STEP: add the attached fastboot files into the container folder of adb (in sdk folder)
This is mine:
C:\Program Files\Android\android-sdk\platform-tools
of course I did that and mine is in the same folder as yours
I get to step six and thats when it gives me the error
E:\android-sdk-windows\platform-tools>fast boot devices
'fast' is not recognized as an internal or external command,
operable program or batch file.
also when I go to the left instead of odin this is my pic (in attachment)
NOW if I hit the power button and the right on in landscape mode I do get the android system recovery options says Android System Recovery <3e> (pic attached)
I have tried wiping date clearing cache as far as fastboot goes it still doesnt let me in fastboot eventhough im not sure at this point what fastboot even is
I finally got CWM 4.0.0.4 on it but now what because somehow im on 3.0.1 on my tab it wont charge and idk what to do
These steps were tested on 3.1.can you update your firmware from kies or on device?fastboot is needed to boot into the recovery image as in your pic which you already have managed being in older firmware.
E:\android-sdk-windows\platform-tools>fast boot devices
I believe something is still wrong, did you extract the contents of zip file in the platform-tools or the complete folder?Second, how was your tab once in fastboot recongnized by windows it should be as an adb. Device and not fastboot. Third, try manually installing the driver from extras folder, google, usb in android sdk. Last is your system 64bit or 32bit as the modification in inf file should be made accordingly. The only issue is driver or fastboot exe not being in adb folder.
Adding, once in recovery as in the pic, try command adb devices and let know if your device is detected hence you can push a restore fileto your device and reboot or push original recovery.zip file and apply it from sdcard (internal memory).
Last try odin option and flash firmware as tar file mentioned in this forum, try the bootloop or blank screen threads.
tried this route but it cannot find my device via ADB - used the PDANet driver - note i did not get a driver in the extras folder
ideas?
mughalgxt said:
These steps were tested on 3.1.can you update your firmware from kies or on device?fastboot is needed to boot into the recovery image as in your pic which you already have managed being in older firmware.
E:\android-sdk-windows\platform-tools>fast boot devices
I believe something is still wrong, did you extract the contents of zip file in the platform-tools or the complete folder?Second, how was your tab once in fastboot recongnized by windows it should be as an adb. Device and not fastboot. Third, try manually installing the driver from extras folder, google, usb in android sdk. Last is your system 64bit or 32bit as the modification in inf file should be made accordingly. The only issue is driver or fastboot exe not being in adb folder.
Adding, once in recovery as in the pic, try command adb devices and let know if your device is detected hence you can push a restore fileto your device and reboot or push original recovery.zip file and apply it from sdcard (internal memory).
Last try odin option and flash firmware as tar file mentioned in this forum, try the bootloop or blank screen threads.
Click to expand...
Click to collapse
solved my problem -
first fastboot.exe is located in the android-sdk\tools directory. i copied it to my android-sdk\platform-tools directory
Then i get into the tablet's fastboot mode (holding down power + volume down, then select the USB icon) i plug in the cable to my PC's USB, then go to device manager and you should see a fastboot device with an exclamation mark. right click on this and select update driver then navigate to android-sdk\extras\google\usb_driver directory and select android_winusb.inf - it should now install the driver
open up a cmd window and follow the instructions highlighted above starting at step 7
animatechnica said:
solved my problem -
first fastboot.exe is located in the android-sdk\tools directory. i copied it to my android-sdk\platform-tools directory
Then i get into the tablet's fastboot mode (holding down power + volume down, then select the USB icon) i plug in the cable to my PC's USB, then go to device manager and you should see a fastboot device with an exclamation mark. right click on this and select update driver then navigate to android-sdk\extras\google\usb_driver directory and select android_winusb.inf - it should now install the driver
open up a cmd window and follow the instructions highlighted above starting at step 7
Click to expand...
Click to collapse
IN Short, follow the steps in my previous post from 1st till end! Flashing the bootloader file from my thread in development section, is easiest way. Replacing fastboot with recovery option in bootscreen solves many issues for non-developers!
yes and i should add your method was very effective ! thanks
what threw me off initially was not finding the fastboot.exe which was in a different folder and the usbdriver - which needed to be installed separately and can be found by launching SDK manager, selecting Available packages-Third-party Add ons-Google Inc - Google USB Driver Package revision 4
mughalgxt said:
IN Short, follow the steps in my previous post from 1st till end! Flashing the bootloader file from my thread in development section, is easiest way. Replacing fastboot with recovery option in bootscreen solves many issues for non-developers!
Click to expand...
Click to collapse
Thanks!!!
This totally worked!
vokhoa408 said:
Thanks!!!
This totally worked!
Click to expand...
Click to collapse
Is this thing getting Ice cream sandwich?
that might solve all these problems.
Samsung Galaxy Tab 10.1 boot loop
Edit: *Fixed!* Ok, so here is my advice to all you other noobs who bricked your tablet, be AWARE that your tablet actually is conscious, it chooses when it wants to work. Just do everything it says on here, all the fixes I have listed, reboot a bunch of times, yell at it, and when you cry a true tear of pain and remorse, and it splashes down on the surface, it will recognize this and all of a sudden work. Booted to 3.0.1 and going to update, that all that is holy.
Hi Guys, I am having the same problem and need some expert advice please, I have a Samsung Galaxy Tab 10.1 with Android Honeycomb 3.1, running Windows XP Pro SP3
I've gone over every solution to this problem on xda over two days and none have worked for me, either that or i'm not doing it correctly.
I successfully rooted my Tab a few days ago, then tried to install a 'boosted' theme and everything is messed up now. When I boot it just hangs on the samsung loading screen, and it reboots to the same screen.
I have tried wiping data/factory reset in cwm
I have tried wiping cache partition
I have tried running Odin through downloading mode
I have adb and fastboot installed on my computer
I have Samsung Android adb interface driver in Device Manager
I have PDAnet installed
When I boot holding the volume down and power button to get the two options, the only two options I have are the Odin Downloading green guy on the right, and an icon with a box and an arrow coming out of it that takes me to CWM on the left.
So I cannot choose fastboot mode on the Tab, when I try to run 'fastboot flash system new.img' through cmd.exe it just says < waiting for device >
I"m a total noob to this and should have left well enough alone when I successfully rooted it, i'm sure I must be just missing a small step, if I could get a bit of guidance it would be greatly appreciated, thanks.
Dell Venue 7 BOOT PROBLEM
Hello,
I replaced frameworks-res.apk, and others, for change design, but now i can't boot my tab ! , it just booting booting booting booting and booting, factory reset not helped?, can you help me please?
It's Dell Venue 7 3730
ManXXXX said:
Hello,
I replaced frameworks-res.apk, and others, for change design, but now i can't boot my tab ! , it just booting booting booting booting and booting, factory reset not helped?, can you help me please?
It's Dell Venue 7 3730
Click to expand...
Click to collapse
You need to flash again the stock rom, the factory reset won't work.
You can found it here http://forum.xda-developers.com/showpost.php?p=51090040&postcount=2 and flashing through fastboot
I don't know what frameworks-res.apk you used, but maybe you forgot set the right permissions, or maybe you took the files for other device.
DL VN 7
Is there some tutorial for flash with fastboot??, i never did it, and i don't want destroy some other..
Go here to Dell's opensource site.. http://opensource.dell.com/releases/...loper-edition/
Link
No working link
ManXXXX said:
No working link
Click to expand...
Click to collapse
first
sorry for the late reply.
In the dell's opensource page there aren't files for the 3730 (i don't know why)
but, may be i'm wrong, there aren't tutorials for flashing in fastboot, i only found posts in xda's dell venue general forum.
i'll write here a guide if you still without founding a tutorial and for any others if found this post
you need:
intel usb drivershttps://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices , read the instruccions if you are in windows 8 (i'm on win7 so i cannot tell you if is the same method or not)
The tools for fastboot (there are in a folder called "google") is a little confused so better download @social-design-concepts miKIT_BATCH HERE (before continue let's say thanks to @social-design-concepts for his useful tool that also works for root ),extract wherever you want in your computer.
the files to flash HEREdownload the package for your device and once donwloaded extract where you want in your computer
NOW FOR FLASH
1.-
Install the intel android usb drivers, if you did this before, skip
2.-
Open the myKIT_BATCH folder and run the "runme.bat" file, then type ACCEPT, after that type 2 and press "enter" (the option 1 is for update the driver, in myKIT_BATCH's post 1 is explained) the font should be red.
3.-
boot into fastboot (press button "power" and button "volume down" at the same time) your tablet's screen will display a blue android with gears inside and below it the "droidboot" text and your device info in your device's top|left screen corner , if yes connect your tablet to pc to recognize it (if is the first time).
4.- Open a command window
after the pc recognizes your tablet unplug and plug again the usb cable, should be faster the recognicion this time.
Then in myKIT_BATCH window press "enter" to refresh, the font will become green and will display your device's info, if is going fine in the window type 4 and press "enter", will appear another window.
IF everything still going fine in the new command window type:
Code:
fastboot devices
will display your device's info
5.- let's start with fastboot
BUT first ENSURE THAT THE BATTERY HAVE A CONSIDERABLE CHARGED LEVEL
Unfortunately i don't know what happens if the tablet power off when flashing and if fastboot will work fine after so check your battery charge first
i need to tell you that the 1-4 steps are the most difficult steps (you should have at this time the rom downloaded and extracted only extract the downloaded package (the .7z file)
after this explained so let's start.
5.1.- WIPING
fastboot have some wipe commands so i will explain the 2 that i used:
Code:
fastboot erase cache
This code explains itself, you can try this code to verify that your device is connected
Code:
fastboot erase data
easy to use but powerful, this will erase app's data and also your internal storage (the 11GB that the tablet have to store files), unfortunately i used this without know and i lost 8GB of files
5.2.- NOW TO FLASH
works almost equal with the wipping commands so it's easy to explain.
let's start with system
for a easy explain you ned to open a window where the rom's files are stored in your pc and in the command shell type "fastboot flash system" and after that drag the system file (system.img.tar.gz) to the command window after dragging the file will appear in the command window the full path of the file
I.E i have a dell venue 8 3830 and i want to flash the jellybean 4.2.2 stock rom so i downloaded the Venue_8_WiFi_JB4.2.2v1.42_FLASHPKG and extract this in F:\VENUE 8 3830\stock rom folder so after type the command and drag and drop the system file in my command window will display this:
Code:
fastboot flash system F:\VENUE 3830\stock rom\VENUE_8_WIFI_JB4.2.2v1.42.system.img.gz
after this the command press "enter" and you don't need to do nothing (maybe your window will turn off and maybe you try to turn on but will keep off, don't worry only let fininsh) the fastboot program will start to prepare the file for upload to the tablet and after that to flash.
this will finish in 1-2 minutes.
NOW THE BOOT.IMG
is the same way than system but faster.
after finishing flashing system (when the window diplays the elapsed time) type: "fastboot flash boot" and drag and drop the boot.img file in the command window
I.E. in my device will be like this:
Code:
fastboot flash boot F:\VENUE 3830\stock rom\VENUE_8_WIFI_JB4.2.2v1.42.boot.img
press "enter" and will do the same like system prepare,upload and flash the file.
there are in the download package more file but only with BOOT and SYSTEM flashed your tab should boot
but if you want to flash the other images you need to type
for recovery:
Code:
fastboot flash recovery F:\VENUE 3830\stock rom\VENUE_8_WIFI_JB4.2.2v1.42.recovery.img
and for fastboot:
Code:
fastboot flash fastboot F:\VENUE 3830\stock rom\VENUE_8_WIFI_JB4.2.2v1.42.fastboot.img
for my example, for you will be change a little
thanks to all who read and understand this guide, bad english
you are free to comment this if i mistake
ADB Driver
Isrks said:
first
sorry for the late reply.
In the dell's opensource page there aren't files for the 3730 (i don't know why)
but, may be i'm wrong, there aren't tutorials for flashing in fastboot, i only found posts in xda's dell venue general forum.
i'll write here a guide if you still without founding a tutorial and for any others if found this post
you need:
intel usb drivershttps://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices , read the instruccions if you are in windows 8 (i'm on win7 so i cannot tell you if is the same method or not)
The tools for fastboot (there are in a folder called "google") is a little confused so better download @social-design-concepts miKIT_BATCH HERE (before continue let's say thanks to @social-design-concepts for his useful tool that also works for root ),extract wherever you want in your computer.
the files to flash HEREdownload the package for your device and once donwloaded extract where you want in your computer
NOW FOR FLASH
1.-
Install the intel android usb drivers, if you did this before, skip
2.-
Open the myKIT_BATCH folder and run the "runme.bat" file, then type ACCEPT, after that type 2 and press "enter" (the option 1 is for update the driver, in myKIT_BATCH's post 1 is explained) the font should be red.
3.-
boot into fastboot (press button "power" and button "volume down" at the same time) your tablet's screen will display a blue android with gears inside and below it the "droidboot" text and your device info in your device's top|left screen corner , if yes connect your tablet to pc to recognize it (if is the first time).
4.- Open a command window
after the pc recognizes your tablet unplug and plug again the usb cable, should be faster the recognicion this time.
Then in myKIT_BATCH window press "enter" to refresh, the font will become green and will display your device's info, if is going fine in the window type 4 and press "enter", will appear another window.
IF everything still going fine in the new command window type:
Code:
fastboot devices
will display your device's info
5.- let's start with fastboot
BUT first ENSURE THAT THE BATTERY HAVE A CONSIDERABLE CHARGED LEVEL
Unfortunately i don't know what happens if the tablet power off when flashing and if fastboot will work fine after so check your battery charge first
i need to tell you that the 1-4 steps are the most difficult steps (you should have at this time the rom downloaded and extracted only extract the downloaded package (the .7z file)
after this explained so let's start.
5.1.- WIPING
fastboot have some wipe commands so i will explain the 2 that i used:
Code:
fastboot erase cache
This code explains itself, you can try this code to verify that your device is connected
Code:
fastboot erase data
easy to use but powerful, this will erase app's data and also your internal storage (the 11GB that the tablet have to store files), unfortunately i used this without know and i lost 8GB of files
5.2.- NOW TO FLASH
works almost equal with the wipping commands so it's easy to explain.
let's start with system
for a easy explain you ned to open a window where the rom's files are stored in your pc and in the command shell type "fastboot flash system" and after that drag the system file (system.img.tar.gz) to the command window after dragging the file will appear in the command window the full path of the file
I.E i have a dell venue 8 3830 and i want to flash the jellybean 4.2.2 stock rom so i downloaded the Venue_8_WiFi_JB4.2.2v1.42_FLASHPKG and extract this in F:\VENUE 8 3830\stock rom folder so after type the command and drag and drop the system file in my command window will display this:
Code:
fastboot flash system F:\VENUE 3830\stock rom\VENUE_8_WIFI_JB4.2.2v1.42.system.img.gz
after this the command press "enter" and you don't need to do nothing (maybe your window will turn off and maybe you try to turn on but will keep off, don't worry only let fininsh) the fastboot program will start to prepare the file for upload to the tablet and after that to flash.
this will finish in 1-2 minutes.
NOW THE BOOT.IMG
is the same way than system but faster.
after finishing flashing system (when the window diplays the elapsed time) type: "fastboot flash boot" and drag and drop the boot.img file in the command window
I.E. in my device will be like this:
Code:
fastboot flash boot F:\VENUE 3830\stock rom\VENUE_8_WIFI_JB4.2.2v1.42.boot.img
press "enter" and will do the same like system prepare,upload and flash the file.
there are in the download package more file but only with BOOT and SYSTEM flashed your tab should boot
but if you want to flash the other images you need to type
for recovery:
Code:
fastboot flash recovery F:\VENUE 3830\stock rom\VENUE_8_WIFI_JB4.2.2v1.42.recovery.img
and for fastboot:
Code:
fastboot flash fastboot F:\VENUE 3830\stock rom\VENUE_8_WIFI_JB4.2.2v1.42.fastboot.img
for my example, for you will be change a little
thanks to all who read and understand this guide, bad english
you are free to comment this if i mistake
Click to expand...
Click to collapse
When i installing the driver, always: Install failed, i have Windows 10 and i added language code
ManXXXX said:
When i installing the driver, always: Install failed, i have Windows 10 and i added language code
Click to expand...
Click to collapse
I found this around here, is for windows 8 but maybe useful for Windows 10
https://software.intel.com/en-us/android/articles/how-to-install-intel-usb-driver-for-android-devices-on-windows-8
ADB Driver
Nah nah this, i think ADB driver.
ManXXXX said:
Nah nah this, i think ADB driver.
Click to expand...
Click to collapse
unfortunately i don't have a computer with windows 10 so i can't solve easily.
i found this googling, so with a little of faith :fingers-crossed: , is the same error than yours http://android.stackexchange.com/questions/118823/how-to-install-adb-drivers-on-windows-10-opoit's for the OPO, but is about the same "intalling adb driver", so could work
in a dessesperate attempt, you can use the update usb drivers in "myKit_BATCH" typing "1" after typyng "ACCEPT"
I fixed it with 15 seconds installer!, i gng try to fix tablet
But i found next problem, after connect tab to PC, just UNKNOWN, and tab is not showing in mykit
ManXXXX said:
But i found next problem, after connect tab to PC, just UNKNOWN, and tab is not showing in mykit
Click to expand...
Click to collapse
Ahh that's add driver not recognize your tablet, I suppose that you connect in fastboot mode,
Try using the option of update the adb driver in Mykit_BATCH, you don't lose nothing trying.
Other option is trying the dell's method http://opensource.dell.com/releases/Venue_8_3830_CloverTrail_plus/developer-edition/Download the pdf file and read the instructions from page 2 to page 9 if still not working
here is the sdk tools for windows that the pdf wants
I downloaded SDK tools, i installed Google usb driver, because it say not installed, when it was installing it said: Disable adb driver, ineffectual, error code -1, but after install it work good, so i will test with this, when no i will try another way, that u wrote here
Finally, tried method, no work, finally, update ADB no working for me, cuz installation always fail, next one DELL method, working but i found problem, dell wrote update driver via google extra with codes, BUT
My first code: USB\VID_413C&PID_B119&REV_????, ????, i think there is something wrong
My second code: USB\VID_413C&PID_B119, i think this one is alright, but then up
Finally with dell next page i'm in!, but my kit no working, in every command shut down, so i using windows cmd, it working too
Mhm bruh, no i'm in flash system, sending 'system' awesome, but it's more than 2 minutes , when it will work, omg u r awesome
Bruh, yay, i did it, thq u r master <33
ManXXXX said:
Bruh, yay, i did it, thq u r master <33
Click to expand...
Click to collapse
Are you telling that the dell method works?
The good new is that your tablet is back (with some problems in the way but work, ). after all now you know how to flash through fastboot. If anyelse goes wrong again, you know what to do
NOTE: Maybe your want to replace the framework-res again, but only will work if is for your device. So i recomend that you modify your stock framework-res by yourself (you can use images or xmls from other sources to your framework-res, this should be safer) using apktool manually or a program (there are some of them in xda, choose your favorite )
Yay 50% of dell method worked, just 50% because Dell have tutorial for setting up ADB service, after it i used your tut, thanks, and believe me i will not test it NEVER again.
This is an guide for when you bricked your ZTE Blade V9, or you destroyed OS without being able to flash with recovery mode(go to step 9).
There are some hacked webservers with articles and shady downloadlinks about this topic, use brain.
I think it can work with an locked oem, because i locked it at some piont earlier.
If your phone isnt showing up as device, give it 1-2 minutes.
Your Phone works even when its showing a black screen.
You do that on your own risk, Iam no ZTE developer.
1. Read the guide, know what you are doing.
2. Download "ZTE Terminal Software", "adb,fastboot,emmc", "ZTE drivers", Stock Rom (update.zip).
Also some "aboot" chinese-factory-testing-firmware which at least gets the phone booting (emmc_appsboot.mbn) from unofficialtwrp at page zte-blade-v9-twrp-3-2-root.
3. Prepare you stock system.img file from the stock rom to flash later. Get an dat to img converter (I used sdat2img.py [email protected]) and extract the img. Rename it to system.img.
4. Boot phone in download mode, the display may be dark but its there ... depends on your damage. Power + Vol- (If it wont work, try starting it normally)
5. Run PortManager from Terminal Software.
6. See COM4(DIAG) -> if anything other adjust drivers in Device Manager. "ZTE 3G Phone AT" should be the right one. There are also some Qualcomm usb drivers which work.
7. Select Port from PortManager as LINE1 USB in "ZTE Terminal Software".
You should now see COM3(DIAG) in ZTE Terminal Software.
8. Use emmcdl on COM3 to flash. Exclude recovery if you have a working/modded one.
I used the original recovery from the stock rom. (emmcdl -p COM3 -f prog_emmc_firehose_SDM450.mbn -b aboot emmc_appsboot.mbn & emmcdl -p COM3 -f prog_emmc_firehose_SDM450.mbn -b recovery recovery-orig.img)
9. Boot phone in recovery mode. Power + Vol+
10. Select "Reboot to bootloader".
11. Find your phone in ">\ fastboot devices".
12. Get the flashscript from file "\META-INF\com\google\android\updater-script" in the stock firmware "update.zip".
Get all extract commands like "package_extract_file("lksecapp.mbn", "/dev/block/bootdevice/by-name/lksecapp");" ;
13. Transfer them into fastboot flash commands and reflash all partitions. (exclude recovery if you have a working/modded one)
Flash your system.img file (step 3) to "system" .
If needed do the same with "vendor".
14. unlock oem.
15. Try restarting your Phone.
16. ???
17. Success !
18. Disable any updates from ZTE, update 1.4 will go good but 1.5 bricks the phone.
18.2 I updated to 1.5 and bricked the phone, because its a "mayor update".
18.3 Follow steps 4 to 8 and only flash the emmc_appsboot.mbn from the STOCK ROM .
19. Do a backup.
Known bugs:
- Wifi cant start -> try reflash (flash system first or including "vendor") or use simcard and hope that ZTE Android update will fix it.
- oem seems locked and unlocked at the same time - ?
Greetings
-deleted-
the phone reboots into recovery (I install the wrong recovery, that's why the bootloop), it does not enter the fastboot and when you enter the recovery it just turns off on the boot screen. I can't get into the system either. The bootloader is unlocked. I tried the SP flash tool and it gave me an error brom. And mtk-client, as I understand it, was fixed on miui 14. because there is also an error there. help me please
Hi, did you manage to solve this problem?
What have you tried with mtk client?
hi, I still haven't solved the problem. In mtkclent, I tried to flash the "boot.img" file through brom mode
If the boot flash was successful but you still cant access fastboot or recovery try reflashing the stock rom using brom mode
Step1: Setting up the files
Download the stock rom for your device (I prefer miuirom website)
Extract the downloaded rom
Check if Mediatek USB VCOM Drivers and UsbDK are installed correctly.
Set up mtkclient (follow official guide)
TIP:
After some research i found out that you can speed up the mtk process by modifying the mtk_daxflash.py file. (Source)
Open the file using notepad and search for this line:
Python:
dsize = min(length, 0x200)
And replace it with this:
Python:
dsize = min(length, 0x2004)
Step2: Fix your device
Open the command prompt in the mtk folder
Run this command WITHOUT your device plugged in:
WARNING! This will erase all data on the device
py -3 mtk wl <extractedrompath>\images\
(py -3 or python depending on the installed python version)
plug in your phone and put it in brom mode. the procedure should start immediately
This will flash all the files inside the images folder in the correct partitions (may take a while)
In the procedure you may see some partitions error but thats normal
When the first command is done run this second command:
py -3 mtk w boot_a "<extractedrompath>images\boot.img"
And this command:
py -3 mtk w boot_b"<extractedrompath>images\boot.img"
This will write the boot image to the boot_a and boot_b partition.
Now if everything succeded you should be able to boot into miui.
If not you should be able at least to boot into fastboot, try following step3
Step3: Flash the rom in fastboot (If required)
In the extracted rom path you should see a .bat and a .sh named flash_all.
Put your phone in fastboot mode and run the bat (Windows) or the sh (macOS/Linux) file.
If everything succeded you should have your phone working again .
Hope that your device will work again!
Tria13 said:
the phone reboots into recovery (I install the wrong recovery, that's why the bootloop), it does not enter the fastboot and when you enter the recovery it just turns off on the boot screen. I can't get into the system either. The bootloader is unlocked. I tried the SP flash tool and it gave me an error brom. And mtk-client, as I understand it, was fixed on miui 14. because there is also an error there. help me please
Click to expand...
Click to collapse
Please PM me if you want your device to be flashed using authorised Xiaomi Server.
I have the same device and I bricked it a while ago by flashing twrp and booting to recovery
From my understanding edl flashing can only be done with an authorized xiaomi account. I don't have one so I had to pay someone on telegram who had one and who could unbrick it. He used a modified version of SP Flash Tool. Although he struggled a bit he got it fixed the next day after I downgraded to windows 10. If you want to avoid bricking this device I recommend you don't use twrp altogether or be very cautious and only use twrp builds from the official telegram group. Compatibility depends on the kernel and android version. For now aosp-based roms have issues with the gpu anyways. (always under 100% load)
Also there is a mtk bootprotect magisk module which might help. (I don't think it will if you flash wrong twrp tho)
I hope these informations are somewhat useful
WolfnHex said:
If the boot flash was successful but you still cant access fastboot or recovery try reflashing the stock rom using brom mode
Step1: Setting up the files
Download the stock rom for your device (I prefer miuirom website)
Extract the downloaded rom
Check if Mediatek USB VCOM Drivers and UsbDK are installed correctly.
Set up mtkclient (follow official guide)
TIP:
After some research i found out that you can speed up the mtk process by modifying the mtk_daxflash.py file. (Source)
Open the file using notepad and search for this line:
Python:
dsize = min(length, 0x200)
And replace it with this:
Python:
dsize = min(length, 0x2004)
Step2: Fix your device
Open the command prompt in the mtk folder
Run this command WITHOUT your device plugged in:
WARNING! This will erase all data on the device
py -3 mtk wl <extractedrompath>\images\
(py -3 or python depending on the installed python version)
plug in your phone and put it in brom mode. the procedure should start immediately
This will flash all the files inside the images folder in the correct partitions (may take a while)
In the procedure you may see some partitions error but thats normal
When the first command is done run this second command:
py -3 mtk w boot_a "<extractedrompath>images\boot.img"
And this command:
py -3 mtk w boot_b"<extractedrompath>images\boot.img"
This will write the boot image to the boot_a and boot_b partition.
Now if everything succeded you should be able to boot into miui.
If not you should be able at least to boot into fastboot, try following step3
Step3: Flash the rom in fastboot (If required)
In the extracted rom path you should see a .bat and a .sh named flash_all.
Put your phone in fastboot mode and run the bat (Windows) or the sh (macOS/Linux) file.
If everything succeded you should have your phone working again .
Hope that your device will work again!
Click to expand...
Click to collapse
hello, thanks for the answer, but I already tried this and I got an error with kamakiri. In the git mtk client, the person was told that it was fixed for 14 miui.
Tria13 said:
hello, thanks for the answer, but I already tried this and I got an error with kamakiri. In the git mtk client, the person was told that it was fixed for 14 miui.
Click to expand...
Click to collapse
The thing is ---- Auth bypass is not yet available for your chipset type MT6895.
We have to wait until we can bypass auth to flash using SP Flash tool.
Tria13 said:
hello, thanks for the answer, but I already tried this and I got an error with kamakiri. In the git mtk client, the person was told that it was fixed for 14 miui.
Click to expand...
Click to collapse
im sorry to hear this
mvikrant97 is right. MT6895 is currently unsupported. you just have to wait
mvikrant97 said:
Please PM me if you want your device to be flashed using authorised Xiaomi Server.
Click to expand...
Click to collapse
Hi, sorry I didn't see your post earlier. Can you solve your phone problem with an authorized Xiaomi Server? You can write your telegram or something else by which I can write to you. Thanks for the answer
DEVICE INFORMATION
==================================
Device Name : TECNO Pouvoir 4
Model : TECNO LC7
Chipset : Mediatek MT6761
Processor : 4x 2.0 GHz ARM
Cores : Quad core
RAM : 3 GB
ROM : 32 GB
===================================
I take no responsibility for your actions and anyone who is willing to follow this guide should know the consequences as well. If you do not know what you are doing, please do not go ahead with this guide.
REFORMAT / FLASHING STOCK ROM (ANDROID 10) / UNBRICK
If you are trying to Clean/Reformat/Re-Flash the Stock ROM of your device you must download do the following...
- - - STOCK ROM DOWNLOAD LINK - - -
Android 10 ==> DOWNLOAD LINK
STEPS
run the "SWDLoader.exe" as administrator and click the "START" button once it finished loading
turn off your device completely, don't remove the battery.
press & hold the (VOL + & VOL -) and then plug in your device using the data cable
wait until the flashing is complete...
ANDROID 11 UPGRADE (This Will Erase Your Data | Backup your Files First)
If you want to upgrade your device from Android 10 to Android 11 you must do the following...
- - - ROM DOWNLOAD LINK - - -
Android 11 ==> DOWNLOAD LINK
STEPS
turn on the developer options & enable "USB DEBUGGING" & "OEM UNLOCKING"
copy the vbmeta.img from your stock firmware and copy it to your computer and put it inside of your ADB directory
run the ADB shell from your computer and execute the following commands.
ADB COMMANDS
Code:
adb reboot fastboot
fastboot flashing unlock
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
once you are done with the fastboot turn off your device completely
download the latest release of "SP FLASH TOOL" then run it and flash your firmware.
ROOTING (This Will Erase Your Data | Backup your Files First)
If you want to root your device here's what to do.
download the latest release of magisk.
- - Links - -
Magisk Official Web-page
GitHub Download Link
STEPS
turn on the developer options & enable "USB DEBUGGING"
extract the boot.img from your stock firmware and make a copy of it inside your device.
patch the boot.img using magisk
copy the patched boot.img created by magisk and copy the vbmeta.img from your stock firmware and copy it to your computer and put it inside of your ADB directory
rename the magisk patched img to boot.img
run the ADB shell and execute the following commands.
ADB COMMANDS
Code:
adb reboot fastboot
fastboot flashing unlock
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot reboot
Once your device completed rebooted congratulations your device is completely rooted and you are good to go.
IMEI FIX
If you accidentally deleted your device IMEI or having some issues with your IMEI here's what to do to restore your lost IMEI.
download the "MAUI META" tool from here.
DOWNLOAD LINK
STEPS
run the MAUI META tool
click the "RECONNECT" button, this should cause to blink the red circle.
once the circle is blinking green & red
turn off your device completely then connect it to your computer (P.S : don't press & hold any button just connect your phone while it's completely turned off)
this might take some time so be patient and wait for it to read your device.
select the "IMEI Download" this should cause a window to pop up.
once the window pops up for "IMEI DOWNLOD"
for "IMEI INCREASEMENT" = 0 enter you "IMEI" number on the blank field.
then Select Download to FLASH
once you finished flashing the IMEI for "SIM 1" continue on "SIM 2"
set the "IMEI INCREASEMENT" to 1 and enter your "IMEI" number on the blank field.
once you finished flashing the IMEI for sim 1 & sim 2 you may now click the disconnect button and unplug your device.
your device will automatically reboots once it get's unplug.
if your device didn't reboot just forced it but pressing & hold the power button.