Hey, I have an Archos Helium 45 that I put a custom ROM on a while ago, but today decided to revert to the stock ROM because it was having some issues. I must have done something wrong though, and softbricked my phone. Now this would be no problem if only I could enter recovery mode, however when I boot up my phone holding down the +volume and power button, all I get is a green screen, which is the fastboot mode. On this screen there is nothing I can select (just seems to be some tiny tiny white, unreadable text on the top). I'm guessing this is because I installed TWRP over the regular recovery.
When I first installed the custom ROM, I did something wrong and softbricked my phone too, and had the same problem of not being able to select anything on the green screen, but then I was able to use the command 'adb reboot recovery' via the PC to boot into recovery mode. However, now this does not work anymore, and when using 'adb devices', it returns an empty list. I still do get a code when using 'fastboot devices' though.
Does anyone have any solution to boot into recovery mode from the fastboot mode?
I read somewhere that I could try flashing the img files from the original ROM via fastboot one by one, however the only img file in ROM's zip file is boot.img.
I also tried updating the ROM using 'fastboot update update.zip' but then it says
Code:
archive does not contain 'android-info.txt'
error: update package 'update.zip' has no android-info.txt
Edit: Never mind, right after creating this thread I found out I could enter recovery mode simply by continuing to hold the +volume button and releasing the power button after the green screen... (and I also plugged it into my computer right when TWRP started, don't know if this was a requirement or coincidence) **** I spent all day looking for a fix and ended up finding it just by trying something.
I'm having issues with the stock ROM though, but at least I can install an other custom ROM and have a working phone.
Related
first off, i just wanted to state, before i get ripped into, i have spend the last 1.5 days reading everything i can find on any forum that comes back with search results for my issue. i've tried numerous drivers, different PC's, even a Linux Live CD system.
I cannot get my PC (win 7, 32 bit) to see my TF201 via ADB.
It is installed in the device manager with the "universal naked driver 0.7", and shows up as "Asus Transformer Prime ADB Interface". But whenever i try to connect via ADB to run the fix in this thread - http://forum.xda-developers.com/showthread.php?t=1514088 - i cannot see the device.
I have tried all of the mount/unmount options in CWM. nothing is working for me.
is there anyone that has run into this? And if so, have you found a resolution?
sorry if i'm coming off as the typical noob here, but i really have put in time researching the issue and attempting other fix-it routes before posting up a help thread.
Thanks!!
perch_44 said:
first off, i just wanted to state, before i get ripped into, i have spend the last 1.5 days reading everything i can find on any forum that comes back with search results for my issue. i've tried numerous drivers, different PC's, even a Linux Live CD system.
I cannot get my PC (win 7, 32 bit) to see my TF201 via ADB.
It is installed in the device manager with the "universal naked driver 0.7", and shows up as "Asus Transformer Prime ADB Interface". But whenever i try to connect via ADB to run the fix in this thread - http://forum.xda-developers.com/showthread.php?t=1514088 - i cannot see the device.
I have tried all of the mount/unmount options in CWM. nothing is working for me.
is there anyone that has run into this? And if so, have you found a resolution?
sorry if i'm coming off as the typical noob here, but i really have put in time researching the issue and attempting other fix-it routes before posting up a help thread.
Thanks!!
Click to expand...
Click to collapse
Update****
I was able to get it out of the boot loop, so that it will boot to the splash screen. well following instructions i've found online, when in CWM, i connected through ADB and pushed a copy of cm9.zip up to the internal storage.
yet, whenever i choose "install from zip" in CWM, it never finds the zip file.
i have done it a few times now and it says it copies up completely, but never actually shows up.
syntax i'm using: adb push cm9filename.zip "/sdcard/cm9filename.zip"
it takes about two minutes and gives me confirmation that it pushed x amount of bytes of data for the file, and says its done. I then go back to the tablet in CWM and choose install from sdcard, and it says there are no files.
I'm about ready to throw this thing in the trash and be done with it......
First of all make a small text file and zip it up for a test file that wont take long to push.
Now type adb push test.zip /data/media/
look if the file is showing where you go to install a rom.
If it is showing then push the rom to the same place then install it
flumpster said:
First of all make a small text file and zip it up for a test file that wont take long to push.
Now type adb push test.zip /data/media/
look if the file is showing where you go to install a rom.
If it is showing then push the rom to the same place then install it
Click to expand...
Click to collapse
If that fails, I had the same issue with cwm, I installed twrp via fastboot and haven't had the problem of the file not showing up after adb push. Fustrating I know.... I tired everything I could think of in cwm multiple reboots different usb ports... on an on......
Please HELP CWM Roocovery Loop!!!
perch_44 said:
Update****
I was able to get it out of the boot loop, so that it will boot to the splash screen. well following instructions i've found online, when in CWM, i connected through ADB and pushed a copy of cm9.zip up to the internal storage.
yet, whenever i choose "install from zip" in CWM, it never finds the zip file.
i have done it a few times now and it says it copies up completely, but never actually shows up.
syntax i'm using: adb push cm9filename.zip "/sdcard/cm9filename.zip"
it takes about two minutes and gives me confirmation that it pushed x amount of bytes of data for the file, and says its done. I then go back to the tablet in CWM and choose install from sdcard, and it says there are no files.
I'm about ready to throw this thing in the trash and be done with it......
Click to expand...
Click to collapse
I am having the same exact problem. It started when I tried to restore my stock backup that I made using CWM 5.8.2.0 coming from the CM rom. I am stuck in the CWM recovery screen and cant get ADB to see the TF Prime. I just get error: device not found. How did you manage to push a zip if ADB wasn't seeing your device? I have been looking for a fix for the last week now.
Forget CWM fastboot flash TWRP then load your rom via microsd.....
Danny80y said:
Forget CWM fastboot flash TWRP then load your rom via microsd.....
Click to expand...
Click to collapse
How do I flash TWRP when Im stuck CWM?
hellshavoc said:
How do I flash TWRP when Im stuck CWM?
Click to expand...
Click to collapse
The answer is in the post you quote, did you read it? Fastboot, see on twrp site.
Striatum_bdr said:
The answer is in the post you quote, did you read it? Fastboot, see on twrp site.
Click to expand...
Click to collapse
the problem is whenever it try to fastboot it just keeps saying waiting for device. I can put my TF prime in fastoot mode when I power on while holding down on vol it just goes right to CWM recovery and any adb command gives me no device found and I tried APX mode (holding vol up during power on) and tried to use NVFlash but that just gives me an error device not recognized. I have all the drivers installed. I used the naked drivers .7 and have cleared out all the old drivers too.
hellshavoc said:
the problem is whenever it try to fastboot it just keeps saying waiting for device. I can put my TF prime in fastoot mode when I power on while holding down on vol it just goes right to CWM recovery and any adb command gives me no device found and I tried APX mode (holding vol up during power on) and tried to use NVFlash but that just gives me an error device not recognized. I have all the drivers installed. I used the naked drivers .7 and have cleared out all the old drivers too.
Click to expand...
Click to collapse
you hold the volume down until the screen starts, then you let go and wait
whycali said:
you hold the volume down until the screen starts, then you let go and wait
Click to expand...
Click to collapse
As I stated above holding down Val down while turning on does not bring up the menu it still just boots right into CWM recovery. i have no option for fastboot or anything.
hellshavoc said:
As I stated above holding down Val down while turning on does not bring up the menu it still just boots right into CWM recovery. i have no option for fastboot or anything.
Click to expand...
Click to collapse
No, you hold Vol down + power then when the first screen with sentences appears you release everything DON'T touch anything, after 5 secondes you will end in a screen with three icons, with volume down youu select the usb icon in the middle, then volume up.
This procedure works even on locked devices except that in this case you don't have the usb icon, only the factory reset and cold reboot ones. So it's impossible you don't obtai this screen, it's hardware coded.
It is confusing but just keep trying till you get it!! Once there go to the TWRP site they have the file and the fastboot commands all set in a guide.
I have exactly the same problem than you.
I had the fastboot/adb connection (I used to push the rom by adb), but i tried to install a wrong version on gapps. Since then, I'm stock in the recovery mode without adb/fastboot connection.
If you find a solution for that, pleaze post it !!
Striatum_bdr said:
No, you hold Vol down + power then when the first screen with sentences appears you release everything DON'T touch anything, after 5 secondes you will end in a screen with three icons, with volume down youu select the usb icon in the middle, then volume up.
This procedure works even on locked devices except that in this case you don't have the usb icon, only the factory reset and cold reboot ones. So it's impossible you don't obtai this screen, it's hardware coded.
Click to expand...
Click to collapse
First of all I would thank Crowds he is the best reference that I've to return in case of any problem I face. (He doesn't sleep - any time I ask he immediately supports)
I bought Lenovo K910 and I've managed successfully to install new ROM "VIBEUI_v2.0_1443" and Gapps with Crowds support.
I advised two of my friends to buy this good and cheap phone. For one of them I installed the latest rom successfully. But with the other I had a big problem The phone stuck on Lenovo Logo.
I was trying to install TWRP 2.7.0.0 batch before installing my new ROM, but during installation and after the phone rebooting the batch command screen shows <Waiting for Device> and the phone is stuck on logo screen.
I tried to connect the phone to PC many times, but PC doesn't recognize the phone. When I try to turn off the phone by pressing the power buttons, the phone restart on logo screen like the shown in this video.
I've read in many site that I have to do the following:
Download and install "minimal adb and fastboot"
Just type on the command line without pressing Enter:
Code:
[COLOR="Blue"][B][I]fastboot [COLOR="Plum"][STRIKE]boot[/STRIKE][/COLOR] recovery.img[/I][/B][/COLOR]
you should place your recovery image file in "minimal adb and fastboot" directory
The phone should be disconnected from computer and completely off (press the Power button for 10 seconds - in my case the phone is restarting)
Press and hold both volume buttons, then connect the cable to the PC.
Once the phone vibrate, press Enter to execute the recovery command line
Click to expand...
Click to collapse
In my case when I press and hold power button the phone is restarting on logo screen so I have to wait for battery consumption
I tried many times with TWRP images but it failed...
I tried with CWM image and it succeeded to load, but I don't have otg cable to load recovery or ROM from usb storage (The problem was in installing TWRP and my ROM should has no problem)
I want to flash TWRP on phone not only loading by "minimal adb and fastboot".
I decided to flash TWRP 2.7.1.2 batch through modifying the batch file. I just used fastboot commands
Code:
[COLOR="blue"][I]fastboot oem device-info
fastboot oem unlock
fastboot oem device-info
fastboot [COLOR="Red"][U][B]flash[/B][/U][/COLOR] recovery data/recovery.img
fastboot flash aboot data/lock/emmc_appsboot.mbn
fastboot flash rpm data/lock/rpm.mbn
fastboot flash sbl1 data/lock/sbl1.mbn
fastboot flash dbi data/lock/sdi.mbn
fastboot flash tz data/lock/tz.mbn
fastboot reboot[/I][/COLOR]
Finally I succeeded to install Recovery and phone works well in the new recovery mode and the system mode that I've not update it yet
I want to share you the problem solution in brief:
Download and extract this file "flashrec TWRP v2.7.1.2" from here
Just select without executing "flashrec_Modified.bat" file from the extracted files.
The phone should be disconnected from computer and completely off (press the Power button for 10 seconds or wait for the battery to be almost empty)
Press and hold both volume buttons, then connect the cable to the PC.
Once the phone vibrate, press Enter to execute the recovery batch file
and as me the phone start the recovery mode in TWRP and can be rebooted in system without any problem
i must extract "flashrec TWRP v2.7.1.2 this file on phone or where? can u explain a
agsao said:
First of all I would thank Crowds he is the best reference that I've to return in case of any problem I face. (He doesn't sleep - any time I ask he immediately supports)
I bought Lenovo K910 and I've managed successfully to install new ROM "VIBEUI_v2.0_1443" and Gapps with Crowds support.
I advised two of my friends to buy this good and cheap phone. For one of them I installed the latest rom successfully. But with the other I had a big problem The phone stuck on Lenovo Logo.
I was trying to install TWRP 2.7.0.0 batch before installing my new ROM, but during installation and after the phone rebooting the batch command screen shows <Waiting for Device> and the phone is stuck on logo screen.
I tried to connect the phone to PC many times, but PC doesn't recognize the phone. When I try to turn off the phone by pressing the power buttons, the phone restart on logo screen like the shown in this video.
I've read in many site that I have to do the following:
In my case when I press and hold power button the phone is restarting on logo screen so I have to wait for battery consumption
I tried many times with TWRP images but it failed...
I tried with CWM image and it succeeded to load, but I don't have otg cable to load recovery or ROM from usb storage (The problem was in installing TWRP and my ROM should has no problem)
I want to flash TWRP on phone not only loading by "minimal adb and fastboot".
I decided to flash TWRP 2.7.1.2 batch through modifying the batch file. I just used fastboot commands
Code:
[COLOR="blue"][I]fastboot oem device-info
fastboot oem unlock
fastboot oem device-info
fastboot [COLOR="Red"][U][B]flash[/B][/U][/COLOR] recovery data/recovery.img
fastboot flash aboot data/lock/emmc_appsboot.mbn
fastboot flash rpm data/lock/rpm.mbn
fastboot flash sbl1 data/lock/sbl1.mbn
fastboot flash dbi data/lock/sdi.mbn
fastboot flash tz data/lock/tz.mbn
fastboot reboot[/I][/COLOR]
Finally I succeeded to install Recovery and phone works well in the new recovery mode and the system mode that I've not update it yet
I want to share you the problem solution in brief:
Download and extract this file "flashrec TWRP v2.7.1.2" from here
Just select without executing "flashrec_Modified.bat" file from the extracted files.
The phone should be disconnected from computer and completely off (press the Power button for 10 seconds or wait for the battery to be almost empty)
Press and hold both volume buttons, then connect the cable to the PC.
Once the phone vibrate, press Enter to execute the recovery batch file
and as me the phone start the recovery mode in TWRP and can be rebooted in system without any problem
Click to expand...
Click to collapse
Please explain me. idont know how to do
prxzero said:
Please explain me. idont know how to do
Click to expand...
Click to collapse
What Is your problem?
Is your phone stuck on logo screen? what were you doing to get the problem??
agsao said:
First of all I would thank Crowds he is the best reference that I've to return in case of any problem I face. (He doesn't sleep - any time I ask he immediately supports)
I bought Lenovo K910 and I've managed successfully to install new ROM "VIBEUI_v2.0_1443" and Gapps with Crowds support.
I advised two of my friends to buy this good and cheap phone. For one of them I installed the latest rom successfully. But with the other I had a big problem The phone stuck on Lenovo Logo.
I was trying to install TWRP 2.7.0.0 batch before installing my new ROM, but during installation and after the phone rebooting the batch command screen shows <Waiting for Device> and the phone is stuck on logo screen.
I tried to connect the phone to PC many times, but PC doesn't recognize the phone. When I try to turn off the phone by pressing the power buttons, the phone restart on logo screen like the shown in this video.
I've read in many site that I have to do the following:
In my case when I press and hold power button the phone is restarting on logo screen so I have to wait for battery consumption
I tried many times with TWRP images but it failed...
I tried with CWM image and it succeeded to load, but I don't have otg cable to load recovery or ROM from usb storage (The problem was in installing TWRP and my ROM should has no problem)
I want to flash TWRP on phone not only loading by "minimal adb and fastboot".
I decided to flash TWRP 2.7.1.2 batch through modifying the batch file. I just used fastboot commands
Code:
[COLOR="blue"][I]fastboot oem device-info
fastboot oem unlock
fastboot oem device-info
fastboot [COLOR="Red"][U][B]flash[/B][/U][/COLOR] recovery data/recovery.img
fastboot flash aboot data/lock/emmc_appsboot.mbn
fastboot flash rpm data/lock/rpm.mbn
fastboot flash sbl1 data/lock/sbl1.mbn
fastboot flash dbi data/lock/sdi.mbn
fastboot flash tz data/lock/tz.mbn
fastboot reboot[/I][/COLOR]
Finally I succeeded to install Recovery and phone works well in the new recovery mode and the system mode that I've not update it yet
I want to share you the problem solution in brief:
Download and extract this file "flashrec TWRP v2.7.1.2" from here
Just select without executing "flashrec_Modified.bat" file from the extracted files.
The phone should be disconnected from computer and completely off (press the Power button for 10 seconds or wait for the battery to be almost empty)
Press and hold both volume buttons, then connect the cable to the PC.
Once the phone vibrate, press Enter to execute the recovery batch file
and as me the phone start the recovery mode in TWRP and can be rebooted in system without any problem
Click to expand...
Click to collapse
Hi..
i just try to install CM12 to this device, with twrp 2.8.6.1 from master lie.
First time its working well, but suddenly this device restarting and stuck on the "lenovo" logo screen.
Every time i presh power button always restarting (like ON-OFF-ON-OFF forever).
when i connectto charger also restarting....
i cant go to twrp using vol- & pwr, when i use minimal adb cannot detected..
Can you help me...
Help
hi.
i try to do something to enable notifications on my lenovo vibe z.
i install new rom from needrom, but it didn't help. So i try to install other one, but i wipe my phone and restart without installed system.
Now when i go to twrp have just flashing teamwin logo, and only when phone is in this mode i can communicate through adb
i have checked many forums and try allot stuff to fix it but nothing works
Please Help!
U are not alone I also in same stage
Is there any one plz help
As long as the hardware is not physically broken, your K910 is unbrickable
http://www.teamsuperluminal.org/unbrick-lenovo-k910/
I followed the guide to revive my K910. You can refer to this forum post in which I documented my experiences:
http://www.teamsuperluminal.org/forums/topic/flash-back-to-lenovo-stock-just-temporarily/
nowbo said:
Is there any one plz help
Click to expand...
Click to collapse
Thanks for your reply
I will apply today. Hope for the best.
Will inform you as soon as this applied..
Have you fixed that problem?
Still at same stage
EcoDan said:
Have you fixed that problem?
Click to expand...
Click to collapse
Hi,
I am still on same stage (Black screen with lenovo logo). Try several ways but can't get out of this. Please help me If any one successful to startup this device or can get on the boot screen where I can do factory reset.
---------- Post added at 07:25 AM ---------- Previous post was at 07:21 AM ----------
wxppro said:
http://www.teamsuperluminal.org/unbrick-lenovo-k910/
I followed the guide to revive my K910. You can refer to this forum post in which I documented my experiences:
http://www.teamsuperluminal.org/forums/topic/flash-back-to-lenovo-stock-just-temporarily/
Click to expand...
Click to collapse
I Try this method but can't get out from that black screen ( Lenovo logo and powered by android)
My device is Lenovo Vibe shot Z90a40. I also try with boot unlock-er but nothing sitll work. So its about 20 days can't use my Lenovo Vibe Shot.
Please help me If you know how to get out of this issue..
Thanks
[/COLOR]
I Try this method but can't get out from that black screen ( Lenovo logo and powered by android)
My device is Lenovo Vibe shot Z90a40. I also try with boot unlock-er but nothing sitll work. So its about 20 days can't use my Lenovo Vibe Shot.
Please help me If you know how to get out of this issue..
Thanks[/QUOTE]
You need to carefully follow each steps in the method - if you short that magic pin and then connect the USB cable (with battery disconnected), your computer will report seeing the device at either COM port 9008 or 9006. Then you can download the factory image to revive the phone. Of course you need to have the right device driver installed. Like I said, as long as the hardware is not broken, this procedure will succeed for sure.
I love you man!
I love you man! I wish you all the happiness and wealth!:victory::victory::victory::angel::angel::highfive::highfive:
I have searched a lot on google and xda and havn't found an answer to my issue. Either I'm searching for the wrong thing or I have a very unique problem.
My basic problem is on two Nabi 2's I can't access the bootloader in order to be able to fastboot TWRP (or any other recovery). It just perpetually hangs.
Both tablets boot just fine. Both tablets are on 1.9.37. Both tablets can be factory wiped via the stock recovery.
Both tablets were rooted via TWRP 2.3.3.0 a few years ago in order to install gapps. I wanted to be able to upgrade the tablets to JB when it came out so I used Nabilablite to "return to stock". I followed all of the prompts and it appeared as though everything worked as desired. I downloaded the OTA update told it to install and never looked at the version again...I just assumed it installed. Handed the tablets back to the kids and everyone was happy. Apparently all I did was flash the stock recovery because they are still rooted and have gapps after several factory resets.
Now (a year later) I have realized I was a dufas and didn't actually effect the change I wanted.
If I hold Vol+ & Pwr buttons it loads to the recovery/boot menu with "boot normally" "fastboot protocol" "recovery kernal" and "forced recovery". If I boot normal, the tablet works fine but I can't update via OTA.
If I choose fastboot protocol it just hangs...for ever...HOW DO I FIX THIS!?!?!
If I choose recovery kernal it loads the stock recovery but still wont install any update OTA or otherwise, even from the sd card.
If I choose forced recovery nothing happens, it also appears to just hang.
If I hold Vol- & Pwr button the nabi logo flashes then the device turns off.
If I hold Vol+ & Vol- & Pwr buttons it appears to be the same as just Vol+ & Pwr.
With the tablet on and fully booted I can see it via ADB. I tried using the adb restart bootloader. The tablet reboots but then just hangs never actually loading the boot loader...
I found http://forum.xda-developers.com/showthread.php?t=2587543. But aicjofs mentions seeing a bootloader issue once before.
Usually when it hangs at the Nabi logo it means you don't have the USB cable plugged in or that the fastboot driver is not installed.(Check device manager and see if fastboot driver is installed/no exclimation point). If that's not the issue then it's the bootloader which I have only seen one person have that issue. Depending on which OTA's you have ran there was an update to a Jellybean bootloader so it's possible. That can be fixed with nvflash or placing the bootloader blob in the staging partition.
Also you can always get recovery back without fastboot in Android by dd'ing the recovery over.
For example if the recovery image is on the internal SD
dd if=/data/media/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
Click to expand...
Click to collapse
I have NO idea what dd'ing the recover over is...
Thank you for any help fixing this.
P.S. I have a 3rd tablet that I also used TWRP 2.3.3.0 on to root and install gapps with. I did NOT use nabilablite on that tablet to return to stock. Yesturday I used fastboot to flash TWRP 2.6(something) to flash a JB OTA update which worked fine. It was also able to download and install every other OTA update all the way to the most recent KK with no problems...
najman9 said:
I have searched a lot on google and xda and havn't found an answer to my issue. Either I'm searching for the wrong thing or I have a very unique problem.
My basic problem is on two Nabi 2's I can't access the bootloader in order to be able to fastboot TWRP (or any other recovery). It just perpetually hangs.
Both tablets boot just fine. Both tablets are on 1.9.37. Both tablets can be factory wiped via the stock recovery.
Both tablets were rooted via TWRP 2.3.3.0 a few years ago in order to install gapps. I wanted to be able to upgrade the tablets to JB when it came out so I used Nabilablite to "return to stock". I followed all of the prompts and it appeared as though everything worked as desired. I downloaded the OTA update told it to install and never looked at the version again...I just assumed it installed. Handed the tablets back to the kids and everyone was happy. Apparently all I did was flash the stock recovery because they are still rooted and have gapps after several factory resets.
Now (a year later) I have realized I was a dufas and didn't actually effect the change I wanted.
If I hold Vol+ & Pwr buttons it loads to the recovery/boot menu with "boot normally" "fastboot protocol" "recovery kernal" and "forced recovery". If I boot normal, the tablet works fine but I can't update via OTA.
If I choose fastboot protocol it just hangs...for ever...HOW DO I FIX THIS!?!?!
If I choose recovery kernal it loads the stock recovery but still wont install any update OTA or otherwise, even from the sd card.
If I choose forced recovery nothing happens, it also appears to just hang.
If I hold Vol- & Pwr button the nabi logo flashes then the device turns off.
If I hold Vol+ & Vol- & Pwr buttons it appears to be the same as just Vol+ & Pwr.
With the tablet on and fully booted I can see it via ADB. I tried using the adb restart bootloader. The tablet reboots but then just hangs never actually loading the boot loader...
I found http://forum.xda-developers.com/showthread.php?t=2587543. But aicjofs mentions seeing a bootloader issue once before.
I have NO idea what dd'ing the recover over is...
Thank you for any help fixing this.
P.S. I have a 3rd tablet that I also used TWRP 2.3.3.0 on to root and install gapps with. I did NOT use nabilablite on that tablet to return to stock. Yesturday I used fastboot to flash TWRP 2.6(something) to flash a JB OTA update which worked fine. It was also able to download and install every other OTA update all the way to the most recent KK with no problems...
Click to expand...
Click to collapse
EDIT: OOOPPS. I didn't see this was in the XDA Assist section. I'm not suppose to answer questions(I was just searching for Nabi questions and didn't notice this was XDA assist), dedicated XDAers just point you in the right direction in this section. Please ask the question again in the Nabi2 section and I'l come help you. http://forum.xda-developers.com/nabi-2
This might help answer some questions http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
If it just hangs at fastboot protocol then the USB connection isn't good or fastboot driver isn't installed most of the time. Can you verify fastboot shows up in device manager?(I know the 3rd tabet worked OK) .
Nabilabite doesn't do anything that should change the bootloader, and fastboot should still work as it did before.
dd'ing recovery over means that you use the root access you have in Android to flash the recovery partition instead of using fastboot. IT's just another way of getting the TWRP recovery on the tablet.
The stock recovery won't install the OTA because when you added Gapps it changed some fies and the OTA sees those files as invalid and will fail.
Forced recovery always looks blank screen. It's waiting for you to give it a bootloader to run(beyond the scope here).
You should be able to get back on track once you have TWRP loaded. It's one of 3 things. Bad USB connection, fastboot driver not installed right, bootloader damage. Check the first 2 issues despite the fact the 3rd tablet had no such problems.
One of the XDA smart guys fixed my error of posting this in the wrong section.
I'm running Windows 7 Ultimate and have installed and re-installed the drivers several times. When the tablet's are fully booted ADB has a good connection and sucessfully sends the command to reboot. So I don't believe there is a driver or USB cable error...
When the tablets hang on the fastboot protocol my computer makes the usb connecting noise but fails to install the drivers...
When I hit forced recovery I hear the unrecognized USB device sound...
These two things make me think I don't have the proper drivers installed...but I don't understand how the driver's work when the tablet is booted but not when trying to access the boot loader.
It appears as though I'm going to have to try the dd method if you are able to point me in that direction please.
EDIT: Now I'm thinking I really DON'T have the fastboot drivers installed. I just plugged the 2nd tablet that hands on the fastboot menu and fastboot failed. I also booted the tablet completly, the adb driver's installed correctly but the fastboot driver's did not...I have installed the 64 bit driver's included with nabilablite. I can't find any actual other downloads. The 15 second ADB installer didn't change anything...
najman9 said:
One of the XDA smart guys fixed my error of posting this in the wrong section.
I'm running Windows 7 Ultimate and have installed and re-installed the drivers several times. When the tablet's are fully booted ADB has a good connection and sucessfully sends the command to reboot. So I don't believe there is a driver or USB cable error...
When the tablets hang on the fastboot protocol my computer makes the usb connecting noise but fails to install the drivers...
When I hit forced recovery I hear the unrecognized USB device sound...
These two things make me think I don't have the proper drivers installed...but I don't understand how the driver's work when the tablet is booted but not when trying to access the boot loader.
It appears as though I'm going to have to try the dd method if you are able to point me in that direction please.
EDIT: Now I'm thinking I really DON'T have the fastboot drivers installed. I just plugged the 2nd tablet that hands on the fastboot menu and fastboot failed. I also booted the tablet completly, the adb driver's installed correctly but the fastboot driver's did not...I have installed the 64 bit driver's included with nabilablite. I can't find any actual other downloads. The 15 second ADB installer didn't change anything...
Click to expand...
Click to collapse
Uninstall those nablablite and try this one. http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
Or look at the other options in section 4 here http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
I'm sorry that probably many have asked the same quesiton, but I'm desperate. The case is I followed the guide on rootyourmobile dot com how-to-unlock-bootloader-install-twrp-and-root-huawei-honor-7 to unlock, install twrp and root. All went good until installing SuperSu through TWRP, where the installation process got cancelled and I'm now stuck at honor-logo. I can still access twrp(it's in chinese though), by holding volum up + power, but I dont manage to access fastboot mode.
I realize this is a way to go. I guess my problem is not getting into fastboot, I also tried all options under Reboot in TWRP. Should I let the battery run out? Any help is much appreciated. Hope my phone is not total garbage...
DigiGoon said:
Okay follow these step, if you don't understand any step ask again. But follow these:
Download the UPDATE.APP of the Build number you were on before.
Extract system.img, boot.img, recovery.img, cust.img from that UPDATE.APP
Flash all these files via bootloader mode, to boot into bootloader mode, once a loop is over and you see blank screen on your phone, quickly press Vol DOWN button and while pressing it connect your phone to a PC. If this doesn't work and you get into recovery, then in recovery go to option Reboot, in that select Bootloader.
Once in bootloader mode, flash these files by firing these commands from a CMD, make sure files are situated in the same location where you open up the CMD.
Code:
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot flash boot boot.img
Now after your phone boots up normally, put the same UPDATE.APP from which these files were extracted in dload folder of your external SDcard.
Now switch off your phone and press all the three buttons(Vol UP + Vol DOWN + Power) simultaneously.
Flashing process will start.
Hope this helps.
Click to expand...
Click to collapse
mosoo said:
I'm sorry that probably many have asked the same quesiton, but I'm desperate. The case is I followed the guide on rootyourmobile dot com how-to-unlock-bootloader-install-twrp-and-root-huawei-honor-7 to unlock, install twrp and root. All went good until installing SuperSu through TWRP, where the installation process got cancelled and I'm now stuck at honor-logo. I can still access twrp(it's in chinese though), by holding volum up + power, but I dont manage to access fastboot mode.
I realize this is a way to go. I guess my problem is not getting into fastboot, I also tried all options under Reboot in TWRP. Should I let the battery run out? Any help is much appreciated. Hope my phone is not total garbage...
Click to expand...
Click to collapse
No need to open a separate threat. Check your post.
Why are you quoting my post and starting a new thread with it?
I tried to root my phone using this guide, followed it down to the word and yet my phone's stuck in a bootloop. It keeps restarting to the Poco start screen.
Ive got the stock recovery, and for some odd reason fastboot commands work only in the "FASTBOOTD" screen and not the the "FASTBOOT" screen which you get from "adb reboot bootloader" command.
I try to shut it down and it boots up back again in the same screen and is stuck there.
Im clueless and I really dont know what to do. Some help would be greatly appreciated.
edit: I tried to use the stock recovery and wipe data. No progress.
I tried to connect the phone with the MIAssistant but the app doesnt recognise the device.
I tried using the MiFlash tool to flash the stock rom, it goes on infinitely. Im currently trying to use the SP Flash tool and MediaTek Bypass tool but I havnt got any progress yet.
I promise I'm never buying MediaTek devices ever again.
Careful with the Flash and Bypass tools, they can cause problems.
What can you achieve with the hardware buttons on the phone? Can you get it into recovery?
Fastbootd working but fastboot not sounds like a USB drivers problem - there are some driver options here.
aricooperdavis said:
Careful with the Flash and Bypass tools, they can cause problems.
What can you achieve with the hardware buttons on the phone? Can you get it into recovery?
Fastbootd working but fastboot not sounds like a USB drivers problem - there are some driver options here.
Click to expand...
Click to collapse
It was a driver issue, thanks for the link.
What I did to get out of the bootloop:
1. Download the latest Miui rom for your version, make sure it's the recovery version and not the fastboot one.
2. Press ALL the buttons, Vol+ Vol- and Power button to shut it down for a few seconds (assuming you can't switch it off as it keeps powering back up again).
3. After it's switched off, quickly press the power and vol- button until you see the FASTBOOT screen.
4. Connect with PC, make sure you have the proper drivers and have connected with the right USB port.
5. Download OrangeFox custom recovery. It is a unofficial custom recovery, so its stability is questionable. But it does the job here.
6. Copy the OrangeFox zip and the Miui rom file to your phone's SD card or any external storage which your phone can access.
7. In your PC, extract the OrangeFox zip folder in your platform-tools folder. (The folder where you run your cmd fastboot/adb commands)
8. Open up cmd, and enter the command:
fastboot flash boot recovery.img
9. Your phone should boot up to the OrangeFox recovery. If not switch the phone off (Step 2) and press power + vol+ button for booting up to the recovery.
10. Locate your OrangeFox zip installer file in the recovery and flash it.
11. Reboot to the recovery again.
12. Locate the Miui rom and flash that. Before swiping to flash the rom, there is a check box which says something like "flash OrangeFox once the rom has been flashed". If you want to keep OrangeFox as your recovery then check it, or else leave it unchecked. Flashing roms remove custom recoveries.
13. Your phone must reboot to miui.
NOTE: You can use fastboot commands to flash the rom but I'm not very familiar with fastboot commands (I actually forgot most of them). Hence I use the recovery method.
warhead1721972 said:
It was a driver issue, thanks for the link. Should I delete this post? It isnt much big of an issue imo.
Click to expand...
Click to collapse
Great, glad you got it sorted! No, leave it up, you never know someone might stumble across it and find it useful