Can't sideload anything (No rom installed; Tried everything) - Nexus 4 Q&A, Help & Troubleshooting

Hello people, basically I'm experiencing a problem in which no ROMS will install and I have nothing on the phone itself to fall back on (all partitions wiped.)
I'm using the latest drivers, but the phone has a problem receiving commands via the bootloader for some reason. I've tried side-loading, flashing a zip normally, using the "Flash stock+unroot option" all via the "Nexus Root Tool-kit"; I've tried using the command prompt through Android SDK's ADB flashing tool, but it didn't work.
While trying to side-load via the Nexus root tool-kit it doesn't work, however while sending the command to boot into stock recovery it does show "downloading..." text at the bottom of the screen, but it freezes up and I have to hold power+volume down to get back into the bootloader successfully.
While trying to side-load via the command prompt through ADB side-loading (SDK) however, it recognizes my device and tries to install zip files but says at 1%, 2%, and 4% (depending on the file) and nothing really happens and after I cancel the sideload it says "can't open /tmp/update.zip (bad)", I then tried finding an update.zip file for the recovery but that didn't side-load either (nor TWRP; my preferred recovery)
This all happened after I stupidly downloaded+installed a previous version of CyanogenMod in which afterwards no processes would work, so I factory reset it and nothing's working (here I am.) Early on I hit root on the clockwork mod since it said it wasn't rooted (I hit it anyway, hence it already being rooted), that may be why I can't do anything in the first place (I did this before I even tried flashing a zip); I then wiped all of the partitions this morning, and no changes. I've also tried all 3 drivers for the Google bootloader (Naked drivers)
I'm using Clockwork recovery 6.0.5.0 legacy (non-touch) and have a Nexus 4 that's unlocked+rooted.
Please help, I've tried everything and have spent hours on end with Google searches and troubleshooting to try to fix this.

Have you tried the flash-all.bat file in the factory image while booted into fastboot?
Sent from my Nexus 5 using XDA Free mobile app

Don't see it
jd1639 said:
Have you tried the flash-all.bat file in the factory image while booted into fastboot?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I don't see a .bat file in either the the stock or liquidsmooth rom. Could you point me to a rom that has one so I may try this? Thanks

xXDustinoXx said:
I don't see a .bat file in either the the stock or liquidsmooth rom. Could you point me to a rom that has one so I may try this? Thanks
Click to expand...
Click to collapse
Google nexus 4 factory image. Download that and extract it using winrar or 7-zip
Sent from my Nexus 5 using XDA Free mobile app

Nothing...
jd1639 said:
Google nexus 4 factory image. Download that and extract it using winrar or 7-zip
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Darn, I was hoping it was going to work; On my phone in the command line it says:
(Before I sent the file)
sideload started...
Now send the package you want to apply
to the device with "adb sideload <filename>
(after I sent the file):
Restarting adbd...
Finding update package...
Opening update package...
E:/can't open /ta[/update.zip
(bad) (there's that error again, except it almost worked)
Installation aborted.

xXDustinoXx said:
Darn, I was hoping it was going to work; On my phone in the command line it says:
(Before I sent the file)
sideload started...
Now send the package you want to apply
to the device with "adb sideload <filename>
(after I sent the file):
Restarting adbd...
Finding update package...
Opening update package...
E:/can't open /ta[/update.zip
(bad) (there's that error again, except it almost worked)
Installation aborted.
Click to expand...
Click to collapse
Just boot into the bootloader with your device connected and double click the bat file. Don't boot into recovery and try to side load it
Sent from my Nexus 5 using XDA Free mobile app

"Downloading"
jd1639 said:
Just boot into the bootloader with your device connected and double click the bat file. Don't boot into recovery and try to side load it
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
The bootloader freezes up and shows "downloading..." on the screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

xXDustinoXx said:
The bootloader freezes up and shows "downloading..." on the screen
Click to expand...
Click to collapse
image url attatched for command prompt picture
What should I do?

xXDustinoXx said:
image url attatched for command prompt picture
What should I do?
Click to expand...
Click to collapse
I'm on my phone and can't see your image. What does it say?
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
I'm on my phone and can't see your image. What does it say?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
It says:
sending 'bootloader; <2500KB>...
FAILED <data transfer failure <unknown error>>
finsihed. total time:5.007s
rebooting into bootloader...
All the while the device is trying to download the data but freezes up as if it can't accept unsigned code (unrooted)?

xXDustinoXx said:
It says:
sending 'bootloader; <2500KB>...
FAILED <data transfer failure <unknown error>>
finsihed. total time:5.007s
rebooting into bootloader...
All the while the device is trying to download the data but freezes up as if it can't accept unsigned code (unrooted)?
Click to expand...
Click to collapse
Are you trying to flash while booted into recovery? You don't want to be in recovery, just the bootloader, vol down + power
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Are you trying to flash while booted into recovery? You don't want to be in recovery, just the bootloader, vol down + power
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, I was doing it with the bootloader, and I did try it via the adb side load just to see if that'd work after the bootloader wouldn't work

xXDustinoXx said:
Yes, I was doing it with the bootloader, and I did try it via the adb side load just to see if that'd work after the bootloader wouldn't work
Click to expand...
Click to collapse
Then you have something wrong with your device. If you try to relock the boot loader does it stay locked or does it remain unlocked?
fastboot oem lock
Then
fastboot oem device-info
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Then you have something wrong with your device. If you try to relock the boot loader does it stay locked or does it remain unlocked?
fastboot oem lock
Then
fastboot oem device-info
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
It was the cord the entire time, that was it! Can't believe that after all of these hours! It's now booting into android! Thanks so much for your help, greatly appreciated

xXDustinoXx said:
It was the cord the entire time, that was it! Can't believe that after all of these hours! It's now booting into android! Thanks so much for your help, greatly appreciated
Click to expand...
Click to collapse
Glad you got it working. Go figure, the cord
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Glad you got it working. Go figure, the cord
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah, I know right! Thanks again

Related

Motorola Tools [Specially for Noobs]

This thread is specially for people who are new in Motorola, and don't know how to solve their problems,
Click to expand...
Click to collapse
There are some necessary tools for all Motorola users that i'm trying to explain about them briefly :
Click to expand...
Click to collapse
1- Motorola Drivers
This is a must have software you have to install on pc or laptop, it's impossible for pc to detect your phone without this software, so do it
Click to expand...
Click to collapse
2- RSD lite
This is official software from Motorola to flash Fastboot files to the device, so you have to install the software on your pc or laptop,
After flashing a costum rom, you can revert to stock with this software, also when you are in a
bootloop you can go back to stock Rom with this software:
Click to expand...
Click to collapse
- download fastboot file you need from here
- extract it in a folder, you have a XML file here
- run RSD lite
- browse XML file to the empty box
- connect the phone to the pc via usb cable in AP Fastboot mode
- click start button on RSD & be patient to flash the files
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Some Tips of Razr i:​
- when the phone is freezed or you are in a bootloop, you can force the device to power down, just push & hold Vol - and Vol+ and
power buttons at the same time for 10 seconds, the phone will be shut down
- for going to boot menu, first turn off the phone, then push & hold Vol buttons and power button at the same time
for about 10seconds, then you will enter to boot menu, now use Vol - button to scroll and Vol + to select an option.
- for going to Stock Recovery, you have to select "recovery" in boot menu, then you'll see a black screen with Android triangle in the middle, now you have to push Vol - + buttons at the same time to enter to recovery
Click to expand...
Click to collapse
I'll update this post soooooon
is this helpful? feel free to push ------------------------------------------------------------------------------ THANK BUTTON
Reserved
Extra for newbies !!!
Maybe you can add official links of these tools...
Also, for Mac and Linux users there is sbf_flash: http://dl.opticaldelusion.org/sbf_flash?attredirects=0
Hi thanks for that - I have a Razr on its way to replace my Defy (running CM7 Maniac's version) - obviously I'll be wanting to root it, but wary of guarantee issues. I'm happy with the process of restoring a fastboot file - but can't see a T Mobile UK version on the link provided - has one been sourced yet? (I'm guessing that the Orange and T Mobile files are still different even though they are both now part of EE)
Cheers
Eserim
How to put the phone in fastboot?
Enviado desde mi XT890 usando Tapatalk 2
Deshabilitado said:
How to put the phone in fastboot?
Enviado desde mi XT890 usando Tapatalk 2
Click to expand...
Click to collapse
On computer: adb reboot-bootloader. On mobile: switch off. Power on holding volume down for approximately 10 seconds
Sent from my XT890 using xda premium
I m trying to flash CFC_signed_customer_8.7.1I-110_IFW-DE-32_RTEU.xml over my en.GB version but i get this message :
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
Fastboot command failed
Any help ?
Now i have another problem.
Everytime i start the phone i get into fastbook menu with the message:
Fastboot Reason: Flash Failure
Fastoot: max download size: 100mb
Fastboot menu disabled
What can i do ?
kourkoubas said:
I m trying to flash CFC_signed_customer_8.7.1I-110_IFW-DE-32_RTEU.xml over my en.GB version but i get this message :
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
Fastboot command failed
Any help ?
Now i have another problem.
Everytime i start the phone i get into fastbook menu with the message:
Fastboot Reason: Flash Failure
Fastoot: max download size: 100mb
Fastboot menu disabled
What can i do ?
Click to expand...
Click to collapse
Edit the xml file(with notepad) by removing gpt and motoboot line and then flash . It's been published on many threads by now.
Sent from Razr I
free2live said:
Edit the xml file(with notepad) by removing gpt and motoboot line and then flash . It's been published on many threads by now.
Sent from Razr I
Click to expand...
Click to collapse
Now i get this message
OEM fb_mode_set
Erasing userdata
Program dummy sp block for userdata
Erasing cache
Downloading...
Partition (boot) Security version downgraded
preflash validation failed for boot
Fastboot command failed
????
kourkoubas said:
Now i get this message
OEM fb_mode_set
Erasing userdata
Program dummy sp block for userdata
Erasing cache
Downloading...
Partition (boot) Security version downgraded
preflash validation failed for boot
Fastboot command failed
????
Click to expand...
Click to collapse
Are you bootloader unlocked? Were you on JB?
My trained monkey is using Android
free2live said:
Are you bootloader unlocked? Were you on JB?
My trained monkey is using Android
Click to expand...
Click to collapse
Ok i have managed to solve major issues .
Here my situation NOW ...
I have my Razr with BOOTLOADER UNLOCKED - ROm version 81.5.39001.XT890.retail.En.Gb and i m trying to install this retail.EN.Eu rom CFC_signed_customer_8.7.1I-110_IFW-DE-32_RTEU.xml.zip from the first post BUT i get a Failure message in Radio and System part of the installation.
What do i do wrong ???
JB could be rooted?
hello, everyone, i am a noob, could someone tell me, if i already updated to JB(official, without root), can i root my phone as this thread??? or How can i root it?
qinaotian said:
hello, everyone, i am a noob, could someone tell me, if i already updated to JB(official, without root), can i root my phone as this thread??? or How can i root it?
Click to expand...
Click to collapse
Follow this thread: http://forum.xda-developers.com/showthread.php?t=2123369:cowboy:
nice new's for noob's :good:
Nice for noobs like me
Enviado desde mi XT890 usando Tapatalk 2
noob question
how do i take a screenshot with the rarz i?
thx
ofteno said:
noob question
how do i take a screenshot with the rarz i?
thx
Click to expand...
Click to collapse
You can take a screenshot by pressing simultaneously power and volume down. Our you can search Google Play Store for apps that do that
Sent from my XT890 using xda premium
I've just ask a question in the specific section so sorry for posting again...
I have the message "Warning bootloader unlocked" on the phone after unlocking the bootloader and flashing cwm recovery.
With RSD lite we can go back to stock. This will erase the above message? Where can I find stock rom for flashing?
Thanks.
Can anyone describe using of Android kitchen for unpacking of zip with firmware?

Flashing a custom recovery

Hello! I know I have already posted a few threads about this, but I want to be 100% right, that's the only way to learn Android!
So I want to flash CWM touch recovery to my device, and I don't want to use any toolkits like I did before. The only thing I want to have from the toolkit now are drivers, because I won't uninstall them, seems pointless.
This is how I think you have to flash a recovery, but please correct me if I'm wrong!
1.Download fastboot files and place them in any directory (how many files are they? Do I have to extract them?
2.download customrecovery.img and place the file in the same directory as the fastboot files.
3.Open command prompt in that directory and type "fastboot flash recovery customrecovery.img"
Is this the full guide on how to install a recovery? Thanks in advance!
Sent from my Nexus 4 using xda app-developers app
In a nutshell, yes, you are correct. For more detailed answers:
1. Yes, place them in the same directory as your ADB drivers, that way you won't have to CD when switching between the two.
2. correct
3. this is correct, but you HAVE to be in bootloader mode.
So the order would be:
adb reboot bootloader
fastboot flash recovery customrecovery.img
Easy, and +1 for wanting to learn how to do things the proper way.
rickbosch said:
In a nutshell, yes, you are correct. For more detailed answers:
1. Yes, place them in the same directory as your ADB drivers, that way you won't have to CD when switching between the two.
2. correct
3. this is correct, but you HAVE to be in bootloader mode.
So the order would be:
adb reboot bootloader
fastboot flash recovery customrecovery.img
Easy, and +1 for wanting to learn how to do things the proper way.
Click to expand...
Click to collapse
Ok so the only files I need are adb drivers, fastboot drivers and the recovery. But do I have to extract any of them? Or just download and place them in the directory without changing the files?
Sent from my Nexus 4 using xda app-developers app
that would depend where you got them. I use this, because I don't want to download and install the SDK. Download the zip at the bottom of this post (http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1) named "platform-tools-v16.zip". Extract the contents to an easy to reach folder, I use C:\Android. Then when you want to use terminal commands shift+right click "open command window here", connect your device, ensure USB Debugging is on and that you've given ADB permissions when it asks for the RSA key. Then you can run "adb devices" to see if they work properly.
rickbosch said:
that would depend where you got them. I use this, because I don't want to download and install the SDK. Download the zip at the bottom of this post (http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1) named "platform-tools-v16.zip". Extract the contents to an easy to reach folder, I use C:\Android. Then when you want to use terminal commands shift+right click "open command window here", connect your device, ensure USB Debugging is on and that you've given ADB permissions when it asks for the RSA key. Then you can run "adb devices" to see if they work properly.
Click to expand...
Click to collapse
And when I've done all that I just have to reboot in bootloader mode and I can flash the recovery?
Sent from my Nexus 4 using xda app-developers app
Thibaultvw said:
And when I've done all that I just have to reboot in bootloader mode and I can flash the recovery?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Sent from my Nexus 4 using xda app-developers app
Thibaultvw said:
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
yessir.
Are ADB and fastboot correctly set up now? From now on I just have to download the recovery and I'm good to go?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thibaultvw said:
Are ADB and fastboot correctly set up now? From now on I just have to download the recovery and I'm good to go?
Click to expand...
Click to collapse
Boot your phone into bootloader mode, connect your phone to your PC with USB cable, run command "fastboot devices" to check if the driver is properly setup. If you can see your device ID then it is good to go.
Else, download google usb drivers here: http://developer.android.com/sdk/win-usb.html
This guy says you have to wipe data/factory reset. I dont think thats needed right? Cause he actually wipes his OS right?
http://youtu.be/nb_MweQpGbQ
You don't have to flash the user data image, but it could result in not getting past the boot screen on initial boot.
http://forum.xda-developers.com/showthread.php?t=2266654
Install Custom Recovery
We’ve 2 custom recoveries available yet for our Nexus 4 viz ClockworkMod and TWRP. ClockworkMod or CWM (in short) comes in 2 variants (Touch UI based & Non-Touch UI based). Below I have mentioned on how to flash each one of them using fastboot. For more info about these two recoveries, visit ClockworkMod and TeamWin websites.
Reboot your device into bootloader mode. Either manually, by powering off and then pressing Volume Down + Power buttons simultaneously or using the following command in CMD/Terminal.
Code:
adb reboot bootloader
Download the latest build of your desired recovery [CWM | TWRP]
Place the downloaded recovery image (.img) file on your desktop.
If in Windows, open CMD and cd it to the desktop using the following command
Code:
cd Desktop
If in OS X or Linux, open terminal and cd it to the desktop using the following command
Code:
cd ~/Desktop
To flash ClockworkMod Non-Touch, type in the following command:
Code:
fastboot flash recovery recovery-clockwork-x.x.x.x-mako.img
Replace x.x.x.x with the recovery build no. that you downloaded.
To flash ClockworkMod Touch, type in the following command:
Code:
fastboot flash recovery recovery-clockwork-touch-x.x.x.x-mako.img
Replace x.x.x.x with the recovery build no. that you downloaded.
To flash TWRP, type in the following command:
Code:
fastboot flash recovery openrecovery-twrp-x.x.x.x-mako.img
Replace x.x.x.x with the recovery build no. that you downloaded.
Once flashed, you will prompted on the CMD/Terminal itself.
Now, either reboot your device by using volume keys to highlight Reboot and select using Power button or reboot into the recovery by selecting Recovery mode.
Voila! The next to follow is to root or directly flash a Custom ROM, which is already rooted
And do I have to do a factory reset when that is done?
Thibaultvw said:
And do I have to do a factory reset when that is done?
Click to expand...
Click to collapse
Nope.
If you boot into recovery and see an android lying out with exclamation mark, use "fastboot format cache" in bootloader mode.
ksilver89 said:
Nope.
If you boot into recovery and see an android lying out with exclamation mark, use "fastboot format cache" in bootloader mode.
Click to expand...
Click to collapse
You mean if it boots in stock recovery?
Sent from my Nexus 4 using xda app-developers app
Thibaultvw said:
You mean if it boots in stock recovery?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
That will only happens when you use stock rom with install-recovery.sh. if you plan to use custom ROM, safely ignore it.
ksilver89 said:
That will only happens when you use stock rom with install-recovery.sh. if you plan to use custom ROM, safely ignore it.
Click to expand...
Click to collapse
I am currently running the stock rom without any mods, so CWM will stick?
And yes I'm planning to get back my old love CM as soon as it updates to 4.3
Sent from my Nexus 4 using xda app-developers app
Thibaultvw said:
I am currently running the stock rom without any mods, so CWM will stick?
And yes I'm planning to get back my old love CM as soon as it updates to 4.3
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
This is getting complication since the introduction of new rooting method for 4.3.....
A: You don't want root
Answer yes if CWM ask you to rename install-recovery.sh, otherwise it won't stick.
B: You want to root with SuperSU
After flashing SuperSU zip, answer No if CWM ask you to rename install-recovery.sh, because the file is modified by SuperSU and it is needed for the root to work.
ksilver89 said:
This is getting complication since the introduction of new rooting method for 4.3.....
A: You don't want root
Answer yes if CWM ask you to rename install-recovery.sh, otherwise it won't stick.
B: You want to root with SuperSU
After flashing SuperSU zip, answer No if CWM ask you to rename install-recovery.sh, because the file is modified by SuperSU and it is needed for the root to work.
Click to expand...
Click to collapse
I want root, so after flashing the supersu zip CWM will ask me? All right!
Will it ask me always after flashing something?
Sent from my Nexus 4 using xda app-developers app
Thibaultvw said:
I want root, so after flashing the supersu zip CWM will ask me? All right!
Will it ask me always after flashing something?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
It will ask every time when you want to reboot from CWM. Alternatively, you can use twrp.

Nexus 7 only boots into Fastboot Mode

Hello,
my Nexus 7 wasn't turned on since 3 weeks. Yesterday, I tried to boot it but it just shows the Google logo. The same with the Recovery. So I tried to install with N-Cry a Recovery, it shows that the installation was successfull, but it won't change everything. The same with the factory ROM, I tried it to install it via ADB, it shows that the installation was successfull, but it doesn't boot and still stucks in the Google-Screen. Know? What can I do? Is it a hardware problem? That would be terrible, because the gueranty ended august 2013.
Greetz!
Edit: If I try to Shut it down via fastboot, it shows Unrecoverable Bootloader Error.
DELETE
I am having an identical issue. I have experienced and resolved the battery issues before. This is not that. I've tried factory resets, toolkit stock flashes, toolkit OS updates, adb wipes and flashes. Everything always says successfully completed but it only boots to Google logo and occasionally freezes on the nexus logo.
Does anyone have more info on the N7's acutal boot process? I assume the Google logo is the POST. Is the Nexus logo provided by the bootloader, the kernel or after the OS starts running?
Is there a way to install a new bootloader?
Is there a win7 or Debian program program that will show in more detail every single line and process during the boot process?
Yea, there is a way, I've allready done it, but it doesn't boot anyway. With the Baseband Version sorry, but it's my fault, there cannot be a Baseband Version on my Grouper.
My Fastboot shows:
Product Name - grouper
Variant - grouper
HW Version: ER3
Baseband Version - N/A
Serial Number: 015XXXXXXXXXXX
Singing: Not defiened yet
LOCK STATE - UNLOCKED
fixed mine, conflicting driver issue and used pdanet versions instead of universal.
Thanks man. That could be work. I will try it later. Anybody another ideas?
Sent from my GT-I9300 using xda app-developers app
Push! Please, anybody any another ideas? The driver wasn't the problem, it doesn't turn on. I can do anything, flash with ADB, flash with different Toolkits...
PLEASE I need my tab...
PUSH! Please help. I tried it so much times, I deinstalled all drivers and install different drivers again... Please what could I do?
Hi, i have this problem but worse is that the buttons of my tablet are not working. It seems i can not boot pass the fastboot whenever i try to reboot (using Wug's Toolkit). Please, does anybody here who can help?
Have you tried flashing back to stock with fastboot?
Sent from my SGH-I997 using XDA Premium 4 mobile app
yes, i have tried that but it still won't pass fastboot. i don't know what's happening. i even tried disconnecting the power/volume buttton cable and tried rebooting again to check if it was the one causing the problem but still it did the same thing.
akerocks said:
yes, i have tried that but it still won't pass fastboot. i don't know what's happening. i even tried disconnecting the power/volume buttton cable and tried rebooting again to check if it was the one causing the problem but still it did the same thing.
Click to expand...
Click to collapse
So, you downloaded the factory image from google and flashed via fastboot from the pc?
Sent from my SGH-I997 using XDA Premium 4 mobile app
yes, using wug's toolkit
akerocks said:
yes, using wug's toolkit
Click to expand...
Click to collapse
No, not wugs. Forget toolkits. First, go here and download the factory image.
https://dl.google.com/dl/android/aosp/nakasig-kot49h-factory-83d93b5f.tgz
Unzip into same folder on pc where you have fastboot binary.
Next, boot to fastboot. Plug N7 to the pc. Open pc directory where fastboot is. Open a command window. (Click on an empty section of the folder so no files are highlighted, hold shift key on keyboard and right click with mouse. Choose "open command window here" from the dropdown)
Type these commands.
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
sleep 10
fastboot -w update image-nakasi-kot49h.zip
Sent from my SGH-I997 using XDA Premium 4 mobile app
hi, thank you for the reply. i followed your steps but this is what i got...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
akerocks said:
hi, thank you for the reply. i followed your steps but this is what i got...
Click to expand...
Click to collapse
The commands must correspond to the version you downloaded. Jkr16s....4.23...etc. Could you post a screenshot of the folder you have those files in? Ill see what the deal is
You unzipped the tar.gz, correct?
Sent from my SGH-I997 using XDA Premium 4 mobile app

			
				
akerocks said:
Click to expand...
Click to collapse
Here is the issue. When you downloaded the tar.gz file that the image-nakasi-kot49h.zip was in, ot also contains the bootloader and some files called .flash-all, .flash....etc. All thoes files need to be in this folder. The image cant be flashed without the bootloader being sucessfully flashed, and the -w command is not recognized withoit the .flash-all.... files. Unzip all the tar.gz contents into the folder and do it again. It will be fine.
Sent from my Nexus 7 using XDA Premium 4 mobile app

[Q] Google nexus 7 (2012) - Unrooting leads to total failure(no recovery, no boot up)

Dear developers and other users!
I have been looking for same issues but I was unable to find answer for my problem.
About a year ago I unlocked and rooted my nexus 7 tablet to use special apps on it.
Today I tried to unroot and lock my device. On my laptop the program(Nexus Root Toolkit) said it was successful so I just needed to reboot the tablet.
After rebooting it stopped on the Google screen with a "Booting failed" text on the top left corner like that:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I think I have uninstalled android from the device but I can't Intsall a new one because recovery mode doesn't work and Android is not going to boot.
I can only use Bootloader. Bootloader looks like that:
Once I started my tablet it started in bootloader mode but every other startup fails on Google screen.
Please help me to use my tablet as before without root.
What should I do and how should I do that to get it work again?
Any help would be highly appreciated ​
Download a factory image from here https://developers.google.com/android/nexus/images and follow this guide to flash it http://forum.xda-developers.com/showthread.php?t=1907796
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Sent from my GT-I8190 using Tapatalk
Carlyle_f said:
Download a factory image from here https://developers.google.com/android/nexus/images and follow this guide to flash it http://forum.xda-developers.com/showthread.php?t=1907796
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Sent from my GT-I8190 using Tapatalk
Click to expand...
Click to collapse
Thank you but I have one big problem... I wouldn't have any trouble if I could run the android os on my tablet BUT after starting up it fails to boot so I can't enable usb debugging which I need for pusshong the new firmware. I wouldn't have any problem if II could be able to access my android setting :/
But I will give a chance for everything.( I need to make my device work befora july 2 because I want to use it on my holiday )
Eurioin said:
Thank you but I have one big problem... I wouldn't have any trouble if I could run the android os on my tablet BUT after starting up it fails to boot so I can't enable usb debugging which I need for pusshong the new firmware. I wouldn't have any problem if II could be able to access my android setting :/
But I will give a chance for everything.( I need to make my device work befora july 2 because I want to use it on my holiday )
Click to expand...
Click to collapse
You don't use USB debugging or adb in fastboot to flash the factory image. Follow the link and read the instructions carefully.
#stayparanoid
Pirateghost said:
You don't use USB debugging or adb in fastboot to flash the factory image. Follow the link and read the instructions carefully.
#stayparanoid
Click to expand...
Click to collapse
Thank you It is still not working :/ in cmd after each command it writes waiting for device
Eurioin said:
Thank you It is still not working :/ in cmd after each command it writes waiting for device
Click to expand...
Click to collapse
Fix your drivers then. Fastboot is the surefire way to fix your issue.
#stayparanoid
Eurioin said:
Thank you It is still not working :/ in cmd after each command it writes waiting for device
Click to expand...
Click to collapse
Its much easier on a Linux machine. All you need to do is open terminal and type "sudo apt-get install android-tools-adb android-tools-fastboot" and hit enter. Then extract the .tar file and double click "flash-all.sh" and choose run in terminal. Absolutely no driver headaches.
If you have access to a Linux machine (mint/ubuntu) or if you can dualboot Linux, this will really help
Sent from my GT-I8190 using Tapatalk
I too have this same issue...
Exception is my Nexus is locked... everytime I try to unlock it, it tries to reboot and never comes back on...
What am I doing wrong?
Thanks for everyone I successfully made my tablet work by flashing a stock android 4.4.2
The solution:
1. I connected to my father's laptop (with Win7 on it and mine had Win8.1 so you MUSN'T try fixing on Win8.1 because of the drivers) because my laptop detected the device as undefined USB component and my father's laptop showed the tablet as Nexus 7.
2. I found a working adb&fastboot here
3. After the download is done unip the file and run RUN ME.bat and type fastboot for help
*If needed after running the RUN ME.bat file type
fastboot oem unlock
Click to expand...
Click to collapse
(this will unlock your bootloader which is necessarry
for the following steps)
4. After reconnecting my device and booting to bootloader mode and downloaded the new firmware (unzipped into the fastboot folder) type fastboot
fastboot update image-nakasi-kot49h (this was the firmware that I needed to "update")
Click to expand...
Click to collapse
5. After the fastboot started working and flashing the new OS (it takes about 5 or 10 minuntes) the tablet will restart and starts optimizing all te apps that you had before (that happened in my case).
6. If you want you can lock your bootloader by giving the fastboot this command:
fastboot oem lock
Click to expand...
Click to collapse
And now I am using Android 4.4.4 on my nexus 7 tablet
Eurioin said:
Thanks for everyone I successfully made my tablet work by flashing a stock android 4.4.2
The solution:
1. I connected to my father's laptop (with Win7 on it and mine had Win8.1 so you MUSN'T try fixing on Win8.1 because of the drivers) because my laptop detected the device as undefined USB component and my father's laptop showed the tablet as Nexus 7.
2. I found a working adb&fastboot here
3. After the download is done unip the file and run RUN ME.bat and type fastboot for help
*If needed after running the RUN ME.bat file type (this will unlock your bootloader which is necessarry
for the following steps)
4. After reconnecting my device and booting to bootloader mode and downloaded the new firmware (unzipped into the fastboot folder) type fastboot
5. After the fastboot started working and flashing the new OS (it takes about 5 or 10 minuntes) the tablet will restart and starts optimizing all te apps that you had before (that happened in my case).
6. If you want you can lock your bootloader by giving the fastboot this command:
And now I am using Android 4.4.4 on my nexus 7 tablet
Click to expand...
Click to collapse
I was hopeful that this would work for me.... I am using a win 8.1 machine and the downloaded fastboot and adb seemed to work fine.
I go to do a fastboot unlock and I get the following:
(bootloader) erasing userdata...
(bootloader) erasing userdata done...
(bootloader) erasing cache...
(bootloader) erasing cache done...
(bootloader) unlocking....
FAILED (remote: (Unknown error code))
finshed. total time: 7.902s
So..... Anyone ? The tablet does ask if I want to Unlock the Bootloader... I select yes and hit the power button to select... yet the tablet goes back to the android screen... The top of the screen says Unlocking now...... yet it doesn't...
Please help...

[Q] Cannot flash recovery or rsd anything on unlocked xt907

I flashed the fxz gpe(after flashing the official first) a few weeks ago on my daughter's phone. It worked well until one night she said there were issues. It would not stop force closing just about every app. I did not have a custom recovery on it at that time. I have since attempted to rsd the gpe, the official fxz, a custom recovery. I have used fastboot commands to attempt to wipe userdata etc. All of these say successful, but it reboots back to the broken gpe each time. When I try to use adb shell to mount system it tells me permission denied. Note, this phone is being used as a media and game device, so no sim card and is in airplane mode with wifi on generally. Any ideas guys?
What does rsdlite say when you attempt to flash the official from the Motorola firmware It doesn't make sense that (if it does) when you rsd the official that it boots back to the broken gpe... You could try house of moto and see if it works any better
Sent from my XT907 using XDA Premium 4 mobile app
ezknives said:
What does rsdlite say when you attempt to flash the official from the Motorola firmware It doesn't make sense that (if it does) when you rsd the official that it boots back to the broken gpe... You could try house of moto and see if it works any better
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
After rebooting it back to the bootloader it says pass. House of Moto did not work either unfortunately. I also used his RSD flasher. You are absolutely right when you say it doesn't make sense. That is why I am baffled at this point. I am able only to get in to settings if I am quick enough(launcher crashes if I hit home), I just tried to switch to dalvic as I noticed it was on Art. However when it rebooted, it went back to Art still...
Try booting to recovery as its stock recovery factory reset and clear cache partition then when you select reboot immediately hold the volume up n down then go straight to the fastboot screen from that menu and rsd the official from there... Let us know (I know how important it is to get it working I have a 2 year old with a droid 4 and its the end of the world when it dies I can't imagine if I were in your position...)
Sent from my XT907 using XDA Premium 4 mobile app
Custom Recovery
jamminjon82 said:
I flashed the fxz gpe(after flashing the official first) a few weeks ago on my daughter's phone. It worked well until one night she said there were issues. It would not stop force closing just about every app. I did not have a custom recovery on it at that time. I have since attempted to rsd the gpe, the official fxz, a custom recovery. I have used fastboot commands to attempt to wipe userdata etc. All of these say successful, but it reboots back to the broken gpe each time. When I try to use adb shell to mount system it tells me permission denied. Note, this phone is being used as a media and game device, so no sim card and is in airplane mode with wifi on generally. Any ideas guys?
Click to expand...
Click to collapse
When you're flashing anything, it's a good idea to return to factory settings first & flash a clean stock rom. But when you flash a custom recovery, you need to make sure that it doesn't boot up normally after it's done. If it boots normally it will replace your custom recovery with stock recovery. To avoid this, as soon as its done flashing and begins the normal boot process, press power&volumeup&down simultaneously and scroll down to recovery and go into this. After you do this once, you shouldn't face anymore problems.:good:
ezknives said:
Try booting to recovery as its stock recovery factory reset and clear cache partition then when you select reboot immediately hold the volume up n down then go straight to the fastboot screen from that menu and rsd the official from there... Let us know (I know how important it is to get it working I have a 2 year old with a droid 4 and its the end of the world when it dies I can't imagine if I were in your position...)
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
PrankCallPimp said:
When you're flashing anything, it's a good idea to return to factory settings first & flash a clean stock rom. But when you flash a custom recovery, you need to make sure that it doesn't boot up normally after it's done. If it boots normally it will replace your custom recovery with stock recovery. To avoid this, as soon as its done flashing and begins the normal boot process, press power&volumeup&down simultaneously and scroll down to recovery and go into this. After you do this once, you shouldn't face anymore problems.:good:
Click to expand...
Click to collapse
Just tried all of these suggestions and still have stock recovery and rebooting back to the same busted google play edition rom.
OK...just to be clear your using the 6.1.6 rsd lite and the 183.46.10 from sbf devoplers.org... Booting into fastboot letting rsd do its thing then allowing rsd boot the device and when it does it boots to the broken gpe?... let's see if more experienced individuals have an idea @RikRong @ATTACK
Sent from my XT907 using XDA Premium 4 mobile app
That's correct, also have redownloaded numerous times to verify that it didn't happen to be corrupt
Sent from my VS980 4G using Tapatalk
jamminjon82 said:
That's correct, also have redownloaded numerous times to verify that it didn't happen to be corrupt
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
Try and flash recovery with mfastboot but boot straight into recovery, then try and flash CM11 nightly.
Type
Code:
mfastboot flash recovery <recovery name>.img
Then
Code:
mfastboot reboot
as soon as you hit enter, press & hold volume up (+) which will take you into recovery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
still takes me back to this after following those commands
Sent from my VS980 4G using Tapatalk
commands I'm putting in
Sent from my VS980 4G using Tapatalk
jamminjon82 said:
still takes me back to this after following those commands
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
Did you run CMD with administrator rights?
ATTACK said:
Did you run CMD with administrator rights?
Click to expand...
Click to collapse
Just did and no luck
Sent from my VS980 4G using Tapatalk
jamminjon82 said:
Just did and no luck
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
Have you tried to mfastboot the images separately?
Code:
mfastboot flash...
Code:
modem NON-HLOS.bin
erase modemst1
erase modemst2
boot boot.img
recovery recovery.img
system system.img
erase cache
erase userdata
Just did and still booting into the same gpe Rom
Is there any more info that I can give you that would help us figure out what the heck is going on with this thing?
Sent from my VS980 4G using Tapatalk
jamminjon82 said:
Just did and still booting into the same gpe Rom
Is there any more info that I can give you that would help us figure out what the heck is going on with this thing?
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
When you did mfastboot reboot, did it reboot?
Have you tried other USB ports?
Did you get any errors with mfastboot?
Yes it reboots,zero errors reported
Sent from my VS980 4G using Tapatalk
Switched ports
Same as before
Sent from my VS980 4G using Tapatalk
Don't know if this info helps
Sent from my VS980 4G using Tapatalk
jamminjon82 said:
Don't know if this info helps
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
If you could would you please try this, I would like to see if ADB reads your partitions.
Boot to the OS and make sure ADB is on.
In CMD type
Code:
adb shell
Except the dialog that pops up on your phone.
Then Type
Code:
ls -al /dev/block/platform/msm_sdcc.1/by-name

Categories

Resources